Search is not available for this dataset
doc_id
int64 1
6.72k
⌀ | Section
stringlengths 5
247
⌀ | Content
stringlengths 501
147k
⌀ | Source
stringclasses 456
values | Document Title
stringclasses 22
values | Working Group
stringclasses 21
values | Series Subject
stringclasses 9
values | Subclause
stringlengths 1
13
⌀ |
|---|---|---|---|---|---|---|---|
5,301 | 5.3.2 User data and signalling data confidentiality | The gNB shall support ciphering of user data between the UE and the gNB. The gNB shall activate ciphering of user data based on the security policy sent by the SMF. The gNB shall support ciphering of RRC-signalling. The gNB shall implement the following ciphering algorithms: - NEA0, 128-NEA1, 128-NEA2 as defined in Annex D of the present document. The gNB may implement the following ciphering algorithm: - 128-NEA3 as defined in Annex D of the present document. Confidentiality protection of user data between the UE and the gNB is optional to use. Confidentiality protection of the RRC-signalling is optional to use. Confidentiality protection should be used whenever regulations permit. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 5.3.2 |
5,302 | 5.3.20.2 Requirements for UE in a PLMN | The UE shall maintain: - a list of PLMN-specific attempt counters (see 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]). The maximum number of possible entries in the list is implementation dependent. This list is applicable to access attempts via 3GPP access only; - a list of PLMN-specific attempt counters for non-3GPP access, if the UE supports non-3GPP access. The maximum number of possible entries in the list is implementation dependent. This list is applicable to access attempts via non-3GPP access only; - a list of PLMN-specific N1 mode attempt counters for 3GPP access. The maximum number of possible entries in the list is implementation dependent. This list is applicable to access attempts via 3GPP access only; - a list of PLMN-specific N1 mode attempt counters for non-3GPP access, if the UE supports non-3GPP access. The maximum number of possible entries in the list is implementation dependent. This list is applicable to access attempts via non-3GPP access only; - one counter for "SIM/USIM considered invalid for GPRS services" events (see 3GPP TS 24. 008 [12]); - one counter for "USIM considered invalid for 5GS services over non-3GPP access" events, if the UE supports non-3GPP access; and - a list of PLMN-specific attempt counters for the determined PLMN with disaster condition, if the UE supports MINT. The maximum number of possible entries in the list is implementation dependent. This list is applicable to access attempts via 3GPP access only. A UE supporting non-EPS services shall maintain one counter for "SIM/USIM considered invalid for non-GPRS services" events (see 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [12]). The UE shall store the above lists of attempt counters and the event counters in its non-volatile memory. The UE shall erase the lists and reset the event counters to zero when the UICC containing the USIM is removed. The counter values shall not be affected by the activation or deactivation of MICO mode or power saving mode (see 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]). The UE implementation-specific maximum value for any of the above counters shall not be greater than 10. NOTE 1: Different counters can use different UE implementation-specific maximum values. If the UE receives a REGISTRATION REJECT or SERVICE REJECT message without integrity protection with 5GMM cause value #3, #6, #7, #11, #12, #13, #15, #27, #31, #62, #72, #73 or #80 before the network has established secure exchange of NAS messages for the N1 NAS signalling connection, the UE shall stop timer T3510 or T3517 if running, and start timer T3247 (see 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [12]) with a random value uniformly drawn from the range between 30 minutes and 60 minutes, if the timer is not running, and take the following actions: 1) if the 5GMM cause value received is #3, #6 or #7, and: a) if the 5GMM cause value is received over 3GPP access, the UE shall: i) if the UE is already registered over another access: - store the current TAI in the list of "5GS forbidden tracking areas for roaming", memorize the current TAI was stored in the list of "5GS forbidden tracking areas for roaming" for non-integrity protected NAS reject message and enter the state 5GMM-DEREGISTERED.LIMITED-SERVICE; and - search for a suitable cell in another tracking area according to 3GPP TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [28] or 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [25C]; or ii) otherwise, if the counter for "SIM/USIM considered invalid for GPRS services" events has a value less than a UE implementation-specific maximum value, - set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete 5G-GUTI, last visited registered TAI, TAI list and ngKSI for 3GPP access; - if the 5GMM cause value received is #3 or #6, delete the list of equivalent PLMNs if any; - increment the counter for "SIM/USIM considered invalid for GPRS services" events; - if the 5GMM cause value received is #3 or #6, and if the counter for "SIM/USIM considered invalid for non-GPRS services" events has a value less than a UE implementation-specific maximum value, increment the counter; - if a registration procedure was performed, reset the registration attempt counter and if a service request procedure was performed, reset the service request attempt counter; - if the UE is operating in single-registration mode, handle the EMM parameters EMM state, EPS update status, EPS attach attempt counter, tracking area updating attempt counter or service request attempt counter, 4G-GUTI, TAI list, eKSI as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] for the case when the EPS attach, tracking area updating procedure or service request procedure is rejected with the EMM cause of the same value in a NAS message without integrity protection; - store the current TAI in the list of "5GS forbidden tracking areas for roaming", memorize the current TAI was stored in the list of "5GS forbidden tracking areas for roaming" for non-integrity protected NAS reject message and enter the state 5GMM-DEREGISTERED.LIMITED-SERVICE; and - search for a suitable cell in another tracking area according to 3GPP TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [28] or 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [25C]; and as a UE implementation option, the UE may perform registration attempt over the non-3GPP access, if non-3GPP access is available, and the USIM is not considered invalid for 5GS services over non-3GPP access; and iii) otherwise proceed as specified in subclauses 5.5.1 and 5.6.1; b) if the 5GMM cause value is received over non-3GPP access, the UE shall: i) if the UE is already registered over another access: - enter the state 5GMM-DEREGISTERED.LIMITED-SERVICE; and - may perform registration attempt over the non-3GPP access if another access point for non-3GPP access is available; or ii) otherwise, if the counter for "USIM considered invalid for 5GS services over non-3GPP access" events has a value less than a UE implementation-specific maximum value, - set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete the 5G-GUTI, last visited registered TAI, TAI list and ngKSI for non-3GPP access; - enter the state 5GMM-DEREGISTERED.LIMITED-SERVICE; - increment the counter for "USIM considered invalid for 5GS services over non-3GPP access" events; and as a UE implementation option, the UE may either perform registration attempt over the non-3GPP access if another access point for non-3GPP access is available, or if 3GPP access is available, and the SIM/USIM is not considered invalid for 5GS services over 3GPP access, perform registration attempt over the 3GPP access; and NOTE 2: How to select another access point for non-3GPP access is implementation specific. iii) otherwise proceed as specified in subclauses 5.5.1 and 5.6.1; 2) if the 5GMM cause value received is #12, #13 or #15, the UE shall proceed as specified in subclauses 5.5.1 and 5.6.1. Additionally, the UE may: a) if the 5GMM cause value is received over 3GPP access, non-3GPP access is available, the UE is not registered over non-3GPP access yet, and the USIM is not considered invalid for 5GS services over non-3GPP access, perform registration attempt over the non-3GPP access; or b) if the 5GMM cause value is received over non-3GPP access, 3GPP access is available, the UE is not registered over 3GPP access yet, and the USIM is not considered invalid for 5GS services over 3GPP access, perform registration attempt over the 3GPP access; 3) if the 5GMM cause value received is #11 or #73 and the UE is in its HPLMN or EHPLMN: a) if the 5GMM cause value is received over 3GPP access, the UE shall: - set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete, the 5G-GUTI, last visited registered TAI, TAI list, ngKSI for 3GPP access and the list of equivalent PLMNs. Additionally, if a registration procedure was performed, the UE shall reset the registration attempt counter and if a service request procedure was performed, reset the service request attempt counter; - if the 5GMM cause value received is #11 and the UE is operating in single-registration mode, handle the EMM parameters EMM state, EPS update status, EPS attach attempt counter, tracking area updating attempt counter or service request attempt counter, 4G-GUTI, TAI list, eKSI as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] for the case when the EPS attach, tracking area updating procedure or service request procedure is rejected with the EMM cause of the same value in a NAS message without integrity protection; - if the 5GMM cause value received is #73 and the UE is operating in single-registration mode, the UE shall in addition set the EPS update status to EU3 ROAMING NOT ALLOWED and shall delete any 4G-GUTI, last visited registered TAI, TAI list and eKSI. Additionally, the UE shall reset the attach attempt counter or tracking area updating attempt counter, and enter the state EMM-DEREGISTERED; - store the current TAI in the list of "5GS forbidden tracking areas for roaming", memorize the current TAI was stored in the list of "5GS forbidden tracking areas for roaming" for non-integrity protected NAS reject message and enter the state 5GMM-DEREGISTERED.LIMITED-SERVICE; and - search for a suitable cell in another tracking area according to 3GPP TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [28] or 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [25C]; and as a UE implementation option, the UE may perform registration attempt over the non-3GPP access, if non-3GPP access is available, the UE is not registered over non-3GPP access yet, and the USIM is not considered invalid for 5GS services over non-3GPP access; b) if the 5GMM cause value is received over non-3GPP access, the UE shall: - set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete the 5G-GUTI, last visited registered TAI, TAI list and ngKSI for non-3GPP access. Additionally, if a registration procedure was performed, the UE shall reset the registration attempt counter and if a service request procedure was performed, reset the service request attempt counter; and - enter the state 5GMM-DEREGISTERED.LIMITED-SERVICE. As a UE implementation option, the UE may perform registration attempt over the non-3GPP access if another access point for non-3GPP access is available, or if 3GPP access is available, the UE is not registered over 3GPP access yet, and the USIM is not considered invalid for 5GS services over 3GPP access, perform registration attempt over the 3GPP access; 4) if the 5GMM cause value received is #11 or #73 and the UE is not in its HPLMN or EHPLMN, in addition to the UE requirements specified in subclause 5.5.1 and 5.6.1: - if the message was received via 3GPP access and if the PLMN-specific attempt counter for the PLMN sending the reject message has a value less than a UE implementation-specific maximum value, the UE shall increment the PLMN-specific attempt counter for the PLMN; or - if the message was received via non-3GPP access and if the PLMN-specific attempt counter for non-3GPP access for the PLMN sending the reject message has a value less than a UE implementation-specific maximum value, the UE shall increment the PLMN-specific attempt counter for non-3GPP access for the PLMN; 5) if the 5GMM cause value received is #27, the UE shall proceed as specified in subclauses 5.5.1 and 5.6.1. Additionally, if the PLMN-specific N1 mode attempt counter for the respective access type and for the PLMN sending the reject message has a value less than a UE implementation-specific maximum value, the UE shall increment this counter for the PLMN; 6) if the 5GMM cause value received is #72, the UE shall proceed as specified in subclauses 5.5.1 and 5.6.1. Additionally, if the PLMN-specific N1 mode attempt counter for non-3GPP access for the PLMN sending the reject message has a value less than a UE implementation-specific maximum value, the UE shall increment this counter for the PLMN; 7) if the 5GMM cause value received is #31 for a UE that has indicated support for CIoT optimizations, the UE may discard the message or alternatively the UE should: - set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2); - store the current TAI in the list of "5GS forbidden tracking areas for roaming", memorize the current TAI was stored in the list of "5GS forbidden tracking areas for roaming" for non-integrity protected NAS reject message; and - search for a suitable cell in another tracking area according to 3GPP TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [28] or 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [25C]; and 8) if the 5GMM cause value received is #62, the UE may discard the message or alternatively the UE should: - set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2); - store the current TAI in the list of "5GS forbidden tracking areas for roaming", memorize the current TAI was stored in the list of "5GS forbidden tracking areas for roaming" for non-integrity protected NAS reject message; and - search for a suitable cell in another tracking area according to 3GPP TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [28] or 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [25C]. 9) if the 5GMM cause value received is #80, the UE shall proceed as specified in subclauses 5.5.1. If the PLMN-specific attempt counter of the PLMN which sent the reject message for the determined PLMN with disaster condition has a value less than a UE implementation-specific maximum value, the UE shall increment the PLMN-specific attempt counter of the PLMN which sent the reject message for the determined PLMN with disaster condition. Upon expiry of timer T3247, the UE shall: - remove all tracking areas from the list of "5GS forbidden tracking areas for regional provision of service" and the list of "5GS forbidden tracking areas for roaming", which were stored in these lists for non-integrity protected NAS reject message; - set the USIM to valid for 5GS services for 3GPP access, if: - the counter for "SIM/USIM considered invalid for GPRS services" events has a value less than a UE implementation-specific maximum value; - set the USIM to valid for 5GS services for non-3GPP access, if: - the counter for "USIM considered invalid for 5GS services over non-3GPP access" events has a value less than a UE implementation-specific maximum value; - set the USIM to valid for non-EPS services, if: - the counter for "SIM/USIM considered invalid for non-GPRS services" events has a value less than a UE implementation-specific maximum value; - for each PLMN-specific attempt counter that has a value greater than zero and less than a UE implementation-specific maximum value, remove the respective PLMN from the extension of the "forbidden PLMNs" list; - for each PLMN-specific attempt counter for non-3GPP access that has a value greater than zero and less than a UE implementation-specific maximum value, remove the respective PLMN from the list of "forbidden PLMNs for non-3GPP access to 5GCN"; - re-enable the N1 mode capability for 3GPP access and, for each PLMN-specific N1 mode attempt counter for 3GPP access that has a value greater than zero and less than a UE implementation-specific maximum value, remove the respective PLMN from the list of PLMNs where N1 mode is not allowed for 3GPP access (see 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]); - re-enable the N1 mode capability for non-3GPP access and, for each PLMN-specific N1 mode attempt counter for non-3GPP access that has a value greater than zero and less than a UE implementation-specific maximum value, remove the respective PLMN from the list of PLMNs where N1 mode is not allowed for non-3GPP access; - if the UE is supporting A/Gb mode or Iu mode, perform the actions as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [12] for the case when timer T3247 expires; - if the UE is supporting S1 mode, perform the actions as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] for the case when timer T3247 expires; - initiate a registration procedure, if still needed, dependent on 5GMM state and 5GS update status, or perform PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]; and - for each PLMN-specific attempt counter of the PLMN which sent the reject message for the determined PLMN with disaster condition that has a value greater than zero and less than a UE implementation-specific maximum value, consider the PLMN which sent the reject message is available for disaster roaming service for the respective determined PLMN with disaster condition. When the UE is switched off, the UE shall, for each PLMN-specific attempt counter that has a value greater than zero and less than the UE implementation-specific maximum value, remove the respective PLMN from the list of "forbidden PLMNs". When the USIM is removed, the UE should perform this action. When the UE is switched off, the UE shall, for each PLMN-specific attempt counter for non-3GPP access that has a value greater than zero and less than the UE implementation-specific maximum value, remove the respective PLMN from the list of "forbidden PLMNs for non-3GPP access to 5GCN". When the USIM is removed, the UE should perform this action. When the UE is switched off, the UE shall, for each PLMN-specific attempt counter of the PLMN which sent the reject message for the determined PLMN with disaster condition that has a value greater than zero and less than the UE implementation-specific maximum value, consider the PLMN is available for disaster roaming service for the respective determined PLMN with disaster condition. When the USIM is removed, the UE should perform this action. NOTE 3: If the respective PLMN was stored in the extension of the "forbidden PLMNs" list, then according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] the UE will delete the contents of this extension when the UE is switched off or the USIM is removed. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.3.20.2 |
5,303 | X.8.2.1 Policies configured locally in Roaming entry NWDAF producer | Figure X.8.2.1-1: Protection of analytics exchange when policies configured locally in Roaming entry NWDAF Pre-requisites: - Roaming entry NWDAF producer, i.e. NWDAFp shall be pre-configured with a list of allowed analytics per PLMN. - If token-based authorization is used, NWDAFc shall have acquired an access token from the PLMN2 to consume the services exposed in Nwdaf_RoamingAnalytics_Subscribe/Request APIs. Step 1: NWDAFc sends Nnwdaf_RoamingAnalytics_Subscribe/Request message to NWDAFp to request analytics. Step 2: The roaming entry NWDAFp shall verify the service request, including verifying token and the visited PLMN ID and determine whether the requested analytics are allowed to be exposed to NWDAFc in PLMN1 by pre-configured policies. Step 3: The roaming entry NWDAFp shall apply the security policies per consumer (PLMN) to the requested analytics and decide on their anonymization, restriction or desensitization based on operator’s policy. NOTE: The anonymization, restriction or desensitization mechanisms of analytics are left for implementation. Step 4: NWDAFp returns the requested and processed analytics to NWDAFc. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | X.8.2.1 |
5,304 | 5.3.3.2.3 CM-CONNECTED state | A UE in CM-CONNECTED state has a NAS signalling connection with the AMF over N1. A NAS signalling connection uses an RRC Connection between the UE and the NG-RAN and an NGAP UE association between the AN and the AMF for 3GPP access. A UE can be in CM-CONNECTED state with an NGAP UE association that is not bound to any TNLA between the AN and the AMF. See clause 5.21.1.2 for details on the state of NGAP UE association for an UE in CM-CONNECTED state. Upon completion of a NAS signalling procedure, the AMF may decide to release the NAS signalling connection with the UE. In the CM-CONNECTED state, the UE shall: - enter CM-IDLE state whenever the AN signalling connection is released (entering RRC_IDLE state over 3GPP access or when the release of the UE-N3IWF connectivity over untrusted non-3GPP access or the UE-TNGF connectivity over trusted non-3GPP access is detected by the UE), see TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [28] for 3GPP access. When the UE CM state in the AMF is CM-CONNECTED, the AMF shall: - enter CM-IDLE state for the UE whenever the logical NGAP signalling connection and the N3 user plane connection for this UE are released upon completion of the AN Release procedure as specified in TS 23.502[ Procedures for the 5G System (5GS) ] [3]. The AMF may keep a UE CM state in the AMF in CM-CONNECTED state until the UE de-registers from the core network. A UE in CM-CONNECTED state can be in RRC_INACTIVE state, see TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27]. When the UE is in RRC_INACTIVE state the following applies: - UE reachability is managed by the RAN, with assistance information from core network; - UE paging is managed by the RAN. - UE monitors for paging with UE's CN (5G S-TMSI) and RAN identifier. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.3.3.2.3 |
5,305 | 6.3.4 AUSF discovery and selection | In the case of NF consumer based discovery and selection, the following applies: - The AMF and the NSWOF perform AUSF selection to allocate an AUSF Instance that performs authentication between the UE and 5G CN in the HPLMN. The AMF and the NSWOF shall utilize the NRF to discover the AUSF instance(s) unless AUSF information is available by other means, e.g. locally configured on AMF and on NSWOF. The AUSF selection function in the AMF and in the NSWOF selects an AUSF instance based on the available AUSF instances (obtained from the NRF or locally configured in the AMF). - The UDM shall utilize the NRF to discover the AUSF instance(s) unless AUSF information is available by other means, e.g. locally configured on UDM. The UDM selects an AUSF instance based on the available AUSF instance(s) obtained from the NRF or based on locally configured information, and information stored (by the UDM) from a previously successful authentication. AUSF selection is applicable to both 3GPP access and non-3GPP access. The AUSF selection function in AUSF NF consumers or in SCP should consider one of the following factors when available: 1. Home Network Identifier (e.g. MNC and MCC, realm) of SUCI/SUPI (by an NF consumer in the Serving network) along with the selected NID (provided by the NG-RAN) in the case of SNPN, Routing Indicator and optionally Home Network Public Key identifier (e.g. in the case that Routing Indicator is not enough to provide SUPI range granularity). NOTE 1: The UE provides the SUCI, which contains the Routing Indicator and Home Network Public Key identifier as defined in TS 23.003[ Numbering, addressing and identification ] [19], to the AMF during initial registration and to the NSWOF during NSWO authentication. The AMF can provide the UE's Routing Indicator and optionally Home Network Public Key identifier to other AMFs as described in TS 23.502[ Procedures for the 5G System (5GS) ] [3]. NOTE 2: The usage of Home Network Public Key identifier for AUSF discovery is limited to the scenario where the AUSF NF consumers belong to the same PLMN as AUSF. NOTE 3: In the case of SNPN and if the UE provides an IMSI type SUCI to the AMF and the SUCI provided by UE or the SUPI derived from the SUCI is for an SNPN served by the AMF, the AMF uses the selected NID provided by the NG-RAN together with the selected PLMN ID (from IMSI) or the Routing Indicator provided by the UE within the SUCI for selection of AUSF. In the case of SNPN and the UE provides an NSI type SUCI to the AMF, the AMF uses the Home Network Identifier and Routing Indicator of SUCI/SUPI for selection of AUSF. When the UE's Routing Indicator is set to its default value as defined in TS 23.003[ Numbering, addressing and identification ] [19], the AUSF NF consumer can select any AUSF instance within the home network for the UE. 2. AUSF Group ID the UE's SUPI belongs to. NOTE 4: The AMF can infer the AUSF Group ID the UE's SUPI belongs to, based on the results of AUSF discovery procedures with NRF. The AMF provides the AUSF Group ID the SUPI belongs to other AMFs as described in TS 23.502[ Procedures for the 5G System (5GS) ] [3]. 3. SUPI; e.g. the AMF selects an AUSF instance based on the SUPI range the UE's SUPI belongs to or based on the results of a discovery procedure with NRF using the UE's SUPI as input for AUSF discovery. NOTE 5: In the case of Onboarding via ON-SNPN, AUSF instances supporting UE onboarding can be registered in NRF or locally configured in the AMF. The AMF in ON-SNPN can discover and select AUSF instance(s) supporting UE onboarding based on the MCC and MNC or realm part in Home Network Identifier of the SUCI/SUPI provided by the onboarding UE. In the case of delegated discovery and selection in SCP, the AUSF NF consumer shall send all available factors to the SCP. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.3.4 |
5,306 | 23.3.2.3.4 Element Manager | The Element Manager (EM) FQDN shall be derived as follows. The "em" <system> label is added in front of the operator's OAM realm domain name: em.oam.mnc<MNC>.mcc<MCC>.3gppnetwork.org If particular operator deployment scenarios where there are multiple Element Managers (one per vendor), the <vendor ID> label is added in front of the "em" label: vendor<ViD>.em.oam.mnc<MNC>.mcc<MCC>.3gppnetwork.org An example of a EM FQDN is: MCC = 123; MNC = 45; ViD = abcd; which gives the EM FQDN: "em.oam.mnc045.mcc123.3gppnetwork.org" and "vendorabcd.em.mnc045.mcc123.3gppnetwork.org". | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 23.3.2.3.4 |
5,307 | 4.4.2.3 Average number of active UEs per QCI | a) This measurement provides the average number of UEs that have DTCH data queued on the downlink, or have DTCH data queued on the uplink, or both. This measurement can’t be calculated from the Average number of active UEs on the DL per QCI and Average number of active UEs on the UL per QCI according to 2 out of 3 approach.The measurement is split into subcounters per E-RAB QoS level (QCI). For an eNodeB serving one or more RNs, the measurement refers to the number of active UEs conneted directly to the eNodeB, excluding RNs. The measurement is also applicable to RNs. b) SI c) This measurement is obtained according to the definition in 3GPP TS 36.314[ Evolved Universal Terrestrial Radio Access (E-UTRA); Layer 2 - Measurements ] [11]. Separate counters are maintained for each QCI. d) Each measurement is an integer value. The number of measurements is eaqul to the number of QCIs plus a possible sum value identified by the .sum suffix. e) The measurement name has the form DRB.UEActive.QCI Where QCI identifies the E-RAB level quality of service class. f) EUtranCellFDD EUtranCellTDD g) Valid for packet switched traffics h) EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.4.2.3 |
5,308 | – SIB15 | SIB15 contains configurations of disaster roaming information. SIB15 information element -- ASN1START -- TAG-SIB15-START SIB15-r17 ::= SEQUENCE { commonPLMNsWithDisasterCondition-r17 SEQUENCE (SIZE (1..maxPLMN)) OF PLMN-Identity OPTIONAL, -- Need R applicableDisasterInfoList-r17 SEQUENCE (SIZE (1..maxPLMN)) OF ApplicableDisasterInfo-r17 OPTIONAL, -- Need R lateNonCriticalExtension OCTET STRING OPTIONAL, ... } ApplicableDisasterInfo-r17 ::= CHOICE { noDisasterRoaming-r17 NULL, disasterRelatedIndication-r17 NULL, commonPLMNs-r17 NULL, dedicatedPLMNs-r17 SEQUENCE (SIZE (1..maxPLMN)) OF PLMN-Identity } -- TAG-SIB15-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,309 | 5.8.9.8.2 Actions related to transmission of RemoteUEInformationSidelink message | When entering RRC_IDLE or RRC_INACTIVE, or upon change in any of the information in the RemoteUEInformationSidelink while in RRC_IDLE or RRC_INACTIVE, the L2 U2N Remote UE shall: 1> if the UE has SIB request information to provide (e.g. the UE has not stored a valid version of a SIB, in accordance with clause 5.2.2.2.1, of one or several required SIB(s) in accordance with clause 5.2.2.1 and the requested SIB has not been indicated in RemoteUEInformationSidelink message to the L2 U2N Relay UE before): 2> include sl-RequestedSIB-List in the RemoteUEInformationSidelink to indicate the requested SIB(s); 1> if the UE has not stored a valid version, in accordance with clause 5.2.2.2.1, of one or several posSIB(s) that the UE requires for a positioning operation, and the requested posSIB has not been indicated in RemoteUEInformationSidelink message to the L2 U2N Relay UE before, and the connected L2 U2N relay UE set posSIB-ForwardingSupported to supported: 2> include sl-RequestedPosSIB-List in the RemoteUEInformationSidelink to indicate the requested posSIB(s); 1> if the UE needs the SFN-DFN offset based on the request from upper layers and the connected L2 U2N relay UE set sfn-DFN-OffsetSupported to supported: 2> set sl-SFN-DFN-OffsetRequested to true; 1> if the UE has paging related information to provide (e.g. the UE has not sent sl-PagingInfo-RemoteUE in the RemoteUEInformationSidelink message to the L2 U2N Relay UE before), set sl-PagingInfo-RemoteUE as follows: 2> if the L2 U2N Remote UE is in RRC_IDLE: 3> include ng-5G-S-TMSI in the sl-PagingIdentityRemoteUE; 3> if the UE specific DRX cycle is configured by upper layer, set sl-PagingCycleRemoteUE to the value of UE specific Uu DRX cycle configured by upper layer; 2> else if the L2 U2N Remote UE is in RRC_INACTIVE: 3> include ng-5G-S-TMSI and fullI-RNTI in the sl-PagingIdentityRemoteUE; 3> if the UE specific DRX cycle is configured by upper layer, 4> set sl-PagingCycleRemoteUE to the minimum value of UE specific Uu DRX cycles (configured by upper layer and configured by RRC); 3> else: 4> set sl-PagingCycleRemoteUE to the value of UE specific DRX cycle configured by RRC; 1> submit the RemoteUEInformationSidelink message to lower layers for transmission; When entering RRC_CONNECTED, if L2 U2N remote UE had sent sl-RequestedSIB-List, sl-RequestedPosSIB-List, and/or sl-PagingInfo-RemoteUE, the L2 U2N Remote UE shall: 1> set the sl-RequestedSIB-List to the value release if requested before; 1> set the sl-RequestedPosSIB-List to the value release if requested before; 1> set the sl-PagingInfo-RemoteUE to the value release if sent before; 1> submit the RemoteUEInformationSidelink message to lower layers for transmission; Upon any change in the need of SFN-DFN offset while in RRC_CONNECTED, the L2 U2N Remote UE shall: 1> if the UE needs the SFN-DFN offset based on the request from upper layers and the connected L2 U2N relay UE set sfn-DFN-OffsetSupported to supported: 2> set sl-SFN-DFN-OffsetRequested to true; 1> submit the RemoteUEInformationSidelink message to lower layers for transmission; The L2 U2N Remote UE in RRC_CONNECTED shall: 1> if the UE is configured with sl-IndirectPathAddChange set to setup, and not configured with split SRB1 with duplication: 2> include connectionForMP; Editor's Note: FFS whether there is other condition to include the new indication, e.g. explicit NW indication, or RRC state of the L2 U2N Relay UE. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.9.8.2 |
5,310 | 5.5.1.3.4 Mobility and periodic registration update accepted by the network | If the registration update request has been accepted by the network, the AMF shall send a REGISTRATION ACCEPT message to the UE. NOTE 0: If the AMF receives the registration update request over non-3GPP access and detects that the N3IWF used by the UE is compatible with only part of the allowed NSSAI and the UE has not indicated its support for slice-based N3IWF selection in the REGISTRATION REQUEST message, the AMF accepts the registration update request. NOTE 0A: If the AMF receives the registration update request over non-3GPP access and detects that the TNGF used by the UE is compatible with only part of the allowed NSSAI and the UE has not indicated its support for slice-based TNGF selection in the REGISTRATION REQUEST message, the AMF accepts the registration update request. If timer T3513 is running in the AMF, the AMF shall stop timer T3513 if a paging request was sent with the access type indicating non-3GPP and the REGISTRATION REQUEST message includes the Allowed PDU session status IE. If timer T3565 is running in the AMF, the AMF shall stop timer T3565 when a REGISTRATION REQUEST message is received. For each of the information elements: 5GMM capability, S1 UE network capability, and UE security capability, the AMF shall store all octets received from the UE in the REGISTRATION REQUEST message, up to the maximum length defined for the respective information element. NOTE 1: This information is forwarded to the new AMF during inter-AMF handover or to the new MME during inter-system handover to S1 mode. The 5G-GUTI reallocation shall be part of the registration procedure for mobility registration update. The 5G-GUTI reallocation should be part of the registration procedure for periodic registration update. During the registration procedure for mobility registration update, if the AMF has not allocated a new 5G-GUTI by the generic UE configuration update procedure, the AMF shall include in the REGISTRATION ACCEPT message the new assigned 5G-GUTI. If the UE has set the CAG bit to "CAG supported" in the 5GMM capability IE of the REGISTRATION REQUEST message and the AMF needs to update the "CAG information list" stored in the UE, the AMF shall include the CAG information list IE or the Extended CAG information list IE in the REGISTRATION ACCEPT message. NOTE 2: The "CAG information list" can be provided by the AMF and include no entry if no "CAG information list" exists in the subscription. NOTE 2A: If the UE supports extended CAG information list, the CAG information list can be included either in the CAG information list IE or Extended CAG information list IE. If the UE does not support extended CAG information list, the CAG information list shall not be included in the Extended CAG information list IE. If a 5G-GUTI or the SOR transparent container IE is included in the REGISTRATION ACCEPT message, the AMF shall start timer T3550 and enter state 5GMM-COMMON-PROCEDURE-INITIATED as described in subclause 5.1.3.2.3.3. If the Operator-defined access category definitions IE or the Extended emergency number list IE ,the CAG information list IE or the Extended CAG information list IE are included in the REGISTRATION ACCEPT message, the AMF shall start timer T3550 and enter state 5GMM-COMMON-PROCEDURE-INITIATED as described in subclause 5.1.3.2.3.3. If the UE has set the RCMP bit to "Sending of REGISTRATION COMPLETE message for negotiated PEIPS parameters supported" in the 5GMM capability IE of the REGISTRATION REQUEST message and if the PEIPS assistance information IE is included in the REGISTRATION ACCEPT message, the AMF shall start timer T3550 and enter state 5GMM-COMMON-PROCEDURE-INITIATED as described in subclause 5.1.3.2.3.3. If the UE is not in NB-N1 mode and the UE has set the RACS bit to "RACS supported" in the 5GMM Capability IE of the REGISTRATION REQUEST message, the AMF may include either a UE radio capability ID IE or a UE radio capability ID deletion indication IE in the REGISTRATION ACCEPT message. If the UE radio capability ID IE or the UE radio capability ID deletion indication IE is included in the REGISTRATION ACCEPT message, the AMF shall start timer T3550 and enter state 5GMM-COMMON-PROCEDURE-INITIATED as described in subclause 5.1.3.2.3.3. The AMF may include a new TAI list for the UE in the REGISTRATION ACCEPT message. The new TAI list shall not contain both tracking areas in NB-N1 mode and tracking areas not in NB-N1 mode. The UE, upon receiving a REGISTRATION ACCEPT message, shall delete its old TAI list and store the received TAI list. If there is no TAI list received, the UE shall consider the old TAI list as valid. If the registration area contains TAIs belonging to different PLMNs, which are equivalent PLMNs, and a) the UE already has stored allowed NSSAI for the current registration area, the UE shall store the allowed NSSAI for the current registration area in each of the allowed NSSAIs which are associated with each of the PLMNs in the registration area; b) the UE already has stored rejected NSSAI for the current registration area, the UE shall store the rejected NSSAI for the current registration area in each of the rejected NSSAIs which are associated with each of the PLMNs in the registration area; c) the UE already has stored rejected NSSAI for the failed or revoked NSSAA, the UE shall store the rejected NSSAI for the failed or revoked NSSAA in each of the rejected NSSAIs which are associated with each of the PLMNs in the registration area; d) the UE already has stored rejected NSSAI for the maximum number of UEs reached, the UE shall store the rejected NSSAI for the maximum number of UEs reached in each of the rejected NSSAIs which are associated with each of the PLMNs in the registration area; e) the UE already has stored pending NSSAI, the UE shall store the pending NSSAI in each of the pending NSSAIs which are associated with each of the PLMNs in the registration area; and f) the UE already has stored partially rejected NSSAI, the UE shall store the partially rejected NSSAI in each of the partially rejected NSSAIs which are associated with each of the PLMNs in the registration area. NOTE 3: When assigning the TAI list, the AMF can take into account the eNodeB's capability of support of CIoT 5GS optimization. The AMF may also include a list of equivalent PLMNs in the REGISTRATION ACCEPT message. Each entry in the list contains a PLMN code (MCC+MNC). The UE shall store the list as provided by the network, and if there is no emergency PDU session established, the UE shall remove from the list any PLMN code that is already in the forbidden PLMN list as specified in subclause 5.3.13A. If the UE is not registered for emergency services and there is an emergency PDU session established, the UE shall remove from the list of equivalent PLMNs any PLMN code present in the forbidden PLMN list as specified in subclause 5.3.13A, when the emergency PDU session is released. In addition, the UE shall add to the stored list the PLMN code of the registered PLMN that sent the list. The UE shall replace the stored list on each receipt of the REGISTRATION ACCEPT message. If the REGISTRATION ACCEPT message does not contain a list, then the UE shall delete the stored list. The AMF of a PLMN shall not include a list of equivalent SNPNs. If the ESI bit of the 5GMM capability IE of the REGISTRATION REQUEST message is set to "equivalent SNPNs supported", the AMF of a SNPN may include a list of equivalent SNPNs in the REGISTRATION ACCEPT message. If the UE is registered for onboarding services in SNPN, the AMF shall not include a list of equivalent SNPNs in the REGISTRATION ACCEPT message. Each entry in the list contains an SNPN identity. The UE shall store the list as provided by the network. If there is no emergency PDU session established and the UE is not registered for onboarding services in SNPN, the UE shall remove from the list any SNPN identity that is already in: - the "permanently forbidden SNPNs" list or the "temporarily forbidden SNPNs" list, if the SNPN was not selected according to subclause 4.9.3.1.1 bullet a0) and subclause 4.9.3.2.1 bullet a0) of 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]; or - the "permanently forbidden SNPNs for access for localized services in SNPN" list or the " temporarily forbidden SNPNs for access for localized services in SNPN" list, if the SNPN was selected according to subclause 4.9.3.1.1 bullet a0) or subclause 4.9.3.2.1 bullet a0) of 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]. If the UE is not registered for emergency services and there is an emergency PDU session established, the UE shall remove from the list of equivalent SNPNs any SNPN identity present in the "permanently forbidden SNPNs" list or the "temporarily forbidden SNPNs" list, when the emergency PDU session is released. The UE shall add to the stored list the SNPN identity of the registered SNPN that sent the list. The UE shall replace the stored list on each receipt of the REGISTRATION ACCEPT message. If the REGISTRATION ACCEPT message does not contain a list, then the UE shall delete the stored list. The AMF of an SNPN shall not include a list of equivalent PLMNs. NOTE 3AA: If N1 mode was disabled for an SNPN due to reception of 5GMM cause #27 or #62, the UE implementation ensures that it does not register to this SNPN due to being part of the list of "equivalent SNPNs" received while registered in another SNPN. If the UE is not registered for emergency services, and if the PLMN identity of the registered PLMN is a member of the forbidden PLMN list as specified in subclause 5.3.13A, any such PLMN identity shall be deleted from the corresponding list(s). The AMF may include new service area restrictions in the Service area list IE in the REGISTRATION ACCEPT message. The UE, upon receiving a REGISTRATION ACCEPT message with new service area restrictions shall act as described in subclause 5.3.5. If the Service area list IE is not included in the REGISTRATION ACCEPT message, any tracking area in the registered PLMN and its equivalent PLMN(s) in the registration area, or in the registered SNPN, is considered as an allowed tracking area as described in subclause 5.3.5. The AMF shall include the MICO indication IE in the REGISTRATION ACCEPT message only if the MICO indication IE was included in the REGISTRATION REQUEST message, the AMF supports and accepts the use of MICO mode. If the AMF supports and accepts the use of MICO mode, the AMF may indicate "all PLMN registration area allocated" in the MICO indication IE in the REGISTRATION ACCEPT message. If "all PLMN registration area allocated" is indicated in the MICO indication IE, the AMF shall not assign and include the TAI list in the REGISTRATION ACCEPT message. If the REGISTRATION ACCEPT message includes an MICO indication IE indicating "all PLMN registration area allocated", the UE shall treat all TAIs in the current PLMN as a registration area and delete its old TAI list. If "strictly periodic registration timer supported" is indicated in the MICO indication IE in the REGISTRATION REQUEST message, the AMF may indicate "strictly periodic registration timer supported" in the MICO indication IE and may include the T3512 value IE in the REGISTRATION ACCEPT message. If the timer value received in T3512 IE is different from the already stored value of the timer T3512 and the timer T3512 is running, the UE shall restart T3512 with the new value received in the T3512 value IE. The AMF shall include an active time value in the T3324 IE in the REGISTRATION ACCEPT message if the UE requested an active time value in the REGISTRATION REQUEST message and the AMF accepts the use of MICO mode and the use of active time. If the UE does not include MICO indication IE in the REGISTRATION REQUEST message, then the AMF shall disable MICO mode if it was already enabled. If the AMF supports and accepts the use of MICO, and the UE included the Requested T3512 value IE in the REGISTRATION REQUEST message, then the AMF shall take into account the T3512 value requested when providing the T3512 value IE in the REGISTRATION ACCEPT message. NOTE 3A: The T3512 value assigned to the UE by AMF can be different from the T3512 value requested by the UE. AMF can take several factors into account when assigning the T3512 value, e.g. local configuration, expected UE behaviour, UE requested T3512 value, UE subscription data, network policies. The AMF may include the T3512 value IE in the REGISTRATION ACCEPT message only if the REGISTRATION REQUEST message was sent over the 3GPP access. The AMF may include the non-3GPP de-registration timer value IE in the REGISTRATION ACCEPT message only if the REGISTRATION REQUEST message was sent for the non-3GPP access. If the UE indicates support of the N1 NAS signalling connection release in the REGISTRATION REQUEST message and the network decides to accept the N1 NAS signalling connection release, then the AMF shall set the N1 NAS signalling connection release bit to "N1 NAS signalling connection release supported" in the 5GS network feature support IE of the REGISTRATION ACCEPT message. If the UE indicates support of the paging indication for voice services in the REGISTRATION REQUEST message and the network decides to accept the paging indication for voice services, then the AMF shall set the paging indication for voice services bit to "paging indication for voice services supported" in the 5GS network feature support IE of the REGISTRATION ACCEPT message. If the UE receives the REGISTRATION ACCEPT message with the paging indication for voice services bit set to "paging indication for voice services supported", the UE NAS layer informs the lower layers that paging indication for voice services is supported. Otherwise, the UE NAS layer informs the lower layers that paging indication for voice services is not supported. If the UE indicates support of the reject paging request in the REGISTRATION REQUEST message and the network decides to accept the reject paging request, then the AMF shall set the reject paging request bit to "reject paging request supported" in the 5GS network feature support IE of the REGISTRATION ACCEPT message. If the UE indicates support of the paging restriction in the REGISTRATION REQUEST message, and the AMF sets: - the reject paging request bit to "reject paging request supported"; - the N1 NAS signalling connection release bit to "N1 NAS signalling connection release supported"; or - both of them; in the 5GS network feature support IE of the REGISTRATION ACCEPT message, and the network decides to accept the paging restriction, then the AMF shall set the paging restriction bit to "paging restriction supported" in the 5GS network feature support IE of the REGISTRATION ACCEPT message. If the MUSIM UE does not include the Paging restriction IE in the REGISTRATION REQUEST message, the AMF shall delete any stored paging restriction for the UE and stop restricting paging. If the MUSIM UE requests the release of the NAS signalling connection, by setting Request type to "NAS signalling connection release" in the UE request type IE included in the REGISTRATION REQUEST message, and the AMF supports the N1 NAS signalling connection release, the AMF shall initiate the release of the NAS signalling connection after the completion of the registration procedure for mobility and periodic registration update. If the UE requests restriction of paging by including the Paging restriction IE and the AMF supports the paging restriction, the AMF: - if accepts the paging restriction, shall include the 5GS additional request result IE in the REGISTRATION ACCEPT message and set the Paging restriction decision to "paging restriction is accepted". The AMF shall store the paging restriction of the UE and enforce these restrictions in the paging procedure as described in subclause 5.6.2; or - if rejects the paging restriction, shall include the 5GS additional request result IE in the REGISTRATION ACCEPT message and set the Paging restriction decision to "paging restriction is rejected", and shall discard the received paging restriction. The AMF shall delete any stored paging restriction for the UE and stop restricting paging. If the UE requests "control plane CIoT 5GS optimization" in the 5GS update type IE, indicates support of control plane CIoT 5GS optimization in the 5GMM capability IE and the AMF decides to accept the requested CIoT 5GS optimization and the registration request, the AMF shall indicate "control plane CIoT 5GS optimization supported" in the 5GS network feature support IE of the REGISTRATION ACCEPT message. If the UE has indicated support for the control plane CIoT 5GS optimizations, and the AMF decides to activate the congestion control for transport of user data via the control plane, then the AMF shall include the T3448 value IE in the REGISTRATION ACCEPT message. If the AMF decides to deactivate the congestion control for transport of user data via the control plane, then the AMF shall delete the stored control plane data back-off time for the UE and the AMF shall not include timer T3448 value IE in the REGISTRATION ACCEPT message. If: - the UE in NB-N1 mode is using control plane CIoT 5GS optimization; and - the network is configured to provide the truncated 5G-S-TMSI configuration for control plane CIoT 5GS optimizations; the AMF shall include the Truncated 5G-S-TMSI configuration IE in the REGISTRATION ACCEPT message and set the "Truncated AMF Set ID value" and the "Truncated AMF Pointer value" in the Truncated 5G-S-TMSI configuration IE based on network policies. The AMF shall start timer T3550 and enter state 5GMM-COMMON-PROCEDURE-INITIATED as described in subclause 5.1.3.2.3.3. For inter-system change from S1 mode to N1 mode in 5GMM-IDLE mode, if the UE has included a ngKSI indicating a current 5G NAS security context in the REGISTRATION REQUEST message by which the REGISTRATION REQUEST message is integrity protected, the AMF shall take one of the following actions: a) if the AMF retrieves the current 5G NAS security context as indicated by the ngKSI and 5G-GUTI sent by the UE, the AMF shall integrity check the REGISTRATION REQUEST message using the current 5G NAS security context and integrity protect the REGISTRATION ACCEPT message using the current 5G NAS security context; b) if the AMF cannot retrieve the current 5G NAS security context as indicated by the ngKSI and 5G-GUTI sent by the UE, the AMF shall treat the REGISTRATION REQUEST message fails the integrity check and take actions as specified in subclause 4.4.4.3; or c) if the UE has not included an Additional GUTI IE, the AMF may treat the REGISTRATION REQUEST message as in the previous item, i.e. as if it cannot retrieve the current 5G NAS security context. NOTE 4: The handling described above at failure to retrieve the current 5G NAS security context or if no Additional GUTI IE was provided does not preclude the option for the AMF to perform a primary authentication and key agreement procedure and create a new native 5G NAS security context. For inter-system change from S1 mode to N1 mode in 5GMM-CONNECTED mode, the AMF shall integrity check REGISTRATION REQUEST message using the current K'AMF as derived when triggering the handover to N1 mode (see subclause 4.4.2.2). The AMF shall verify the received UE security capabilities in the REGISTRATION REQUEST message. The AMF shall then take one of the following actions: a) if the REGISTRATION REQUEST does not contain a valid KSIAMF in the Non-current native NAS key set identifier IE, the AMF shall remove the non-current native 5G NAS security context, if any, for any 5G-GUTI for this UE. The AMF shall then integrity protect and cipher the REGISTRATION ACCEPT message using the security context based on K'AMF and take the mapped 5G NAS security context into use; or b) if the REGISTRATION REQUEST contains a valid KSIAMF in the Non-current native NAS key set identifier IE and: 1) the AMF decides to take the native 5G NAS security context into use, the AMF shall initiate a security mode control procedure to take the corresponding native 5G NAS security context into use and then integrity protect and cipher the REGISTRATION ACCEPT message using the corresponding native 5G NAS security context; and 2) otherwise, the AMF shall then integrity protect and cipher the REGISTRATION ACCEPT message using the security context based on K'AMF and take the mapped 5G NAS security context into use. NOTE 5: In above bullet b), it is recommended for the AMF to initiate a security mode control procedure to take the corresponding native 5G NAS security context into use. If the UE has included the service-level device ID set to the CAA-level UAV ID in the Service-level-AA container IE of the REGISTRATION REQUEST message, and if: - the UE has a valid aerial UE subscription information; and - the UUAA procedure is to be performed during the registration procedure according to operator policy; and - there is no valid successful UUAA result for the UE in the UE 5GMM context, then the AMF shall initiate the UUAA-MM procedure with the UAS-NF as specified in 3GPP TS 23.256[ Support of Uncrewed Aerial Systems (UAS) connectivity, identification and tracking; Stage 2 ] [6AB] and shall include a service-level-AA pending indication in the Service-level-AA container IE of the REGISTRATION ACCEPT message. The AMF shall store in the UE 5GMM context that a UUAA procedure is pending. The AMF shall start timer T3550 and enter state 5GMM-COMMON-PROCEDURE-INITIATED as described in subclause 5.1.3.2.3.3. If the UE has included the service-level device ID set to the CAA-level UAV ID in the Service-level-AA container IE of the REGISTRATION REQUEST message, and if: - the UE has a valid aerial UE subscription information; - the UUAA procedure is to be performed during the registration procedure according to operator policy; and - there is a valid successful UUAA result for the UE in the UE 5GMM context, then the AMF shall include a service-level-AA response in the Service-level-AA container IE of the REGISTRATION ACCEPT message and set the SLAR field in the service-level-AA response to "Service level authentication and authorization was successful". If the AMF determines that the UUAA-MM procedure needs to be performed for a UE, the AMF has not received the service -level device ID set to the CAA-level UAV ID in the Service-level-AA container IE of the REGISTRATION REQUEST message from the UE and the AMF decides to accept the UE to be registered for other services than UAS services based on the user's subscription data and the operator policy, the AMF shall accept the registration update request and shall mark in the UE's 5GMM context that the UE is not allowed to request UAS services. If the UE supports MINT, the AMF may include the List of PLMNs to be used in disaster condition IE in the REGISTRATION ACCEPT message. If the UE supports MINT, the AMF may include the Disaster roaming wait range IE in the REGISTRATION ACCEPT message. If the UE supports MINT, the AMF may include the Disaster return wait range IE in the REGISTRATION ACCEPT message. NOTE 6: The AMF can determine the content of the "list of PLMN(s) to be used in disaster condition", the value of the disaster roaming wait range and the value of the disaster return wait range based on the network local configuration. If the AMF received the list of TAIs from the satellite NG-RAN as described in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8], and determines that, by UE subscription and operator's preferences, any but not all TAIs in the received list of TAIs is forbidden for roaming or for regional provision of service, the AMF shall include the TAI(s) in: a) the Forbidden TAI(s) for the list of "5GS forbidden tracking areas for roaming" IE; or b) the Forbidden TAI(s) for the list of "5GS forbidden tracking areas for regional provision of service" IE; or c) both; in the REGISTRATION ACCEPT message. NOTE 7A: Void. If the UE has set the Reconnection to the network due to RAN timing synchronization status change (RANtiming) bit to "Reconnection to the network due to RAN timing synchronization status change supported" in the 5GMM capability IE of the REGISTRATION REQUEST message, the AMF may include the RAN timing synchronization IE with the RecReq bit set to "Reconnection requested" in the REGISTRATION ACCEPT message. If the AMF receives the mobility and periodic registration request along with along with the mobile IAB-indication over N2 reference point (see TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [31]) from an UE and the UE is authorized to operate as an MBSR based on the subscription information and local policy (see 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]), the AMF shall include the Feature authorization indication IE in the REGISTRATION ACCEPT message and shall set the MBSRAI field to "authorized to operate as MBSR". If the AMF receives the mobility and periodic registration request along with along with the mobile IAB-indication over N2 reference point (see TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [31]) from a UE and the UE is not authorized operate as an MBSR based on the subscription information and local policy but can operate as a UE, the AMF shall include the Feature authorization indication IE in the REGISTRATION ACCEPT message and shall set the MBSRAI field to "not authorized to operate as MBSR but allowed to operate as a UE". If the UE supports user plane positioning using LCS-UPP, SUPL or both, the AMF shall set the LCS-UPP bit and the SUPL bit in the 5GS network feature support IE of the REGISTRATION ACCEPT message as specified in 3GPP TS 24.572[ 5G System (5GS); User plane Location Services (LCS) protocols and procedures; Stage 3 ] [64]. Upon receipt of the REGISTRATION ACCEPT message, the UE shall reset the registration attempt counter and service request attempt counter, enter state 5GMM-REGISTERED and set the 5GS update status to 5U1 UPDATED. If the UE receives the REGISTRATION ACCEPT message from a PLMN, then the UE shall reset the PLMN-specific attempt counter for that PLMN for the specific access type for which the message was received. The UE shall also reset the PLMN-specific N1 mode attempt counter for that PLMN for the specific access type for which the message was received. If the message was received via 3GPP access, the UE shall reset the counter for "SIM/USIM considered invalid for GPRS services" events and the counter for "SIM/USIM considered invalid for non-GPRS services", if any. If the message was received via non-3GPP access, the UE shall reset the counter for "USIM considered invalid for 5GS services over non-3GPP" events. If the UE receives the REGISTRATION ACCEPT message from an SNPN, then the UE shall reset the SNPN-specific attempt counter for the current SNPN for the specific access type for which the message was received. If the message was received via 3GPP access, the UE shall reset the counter for "the entry for the current SNPN considered invalid for 3GPP access" events. If the message was received via non-3GPP access, the UE shall reset the counter for "the entry for the current SNPN considered invalid for non-3GPP access" events. If the REGISTRATION ACCEPT message included a T3512 value IE, the UE shall use the value in T3512 value IE as periodic registration update timer (T3512). If the T3512 value IE is not included, the UE shall use the value currently stored, e.g. from a prior REGISTRATION ACCEPT message. If the REGISTRATION ACCEPT message include a T3324 value IE, the UE shall use the value in the T3324 value IE as active time timer (T3324). If the REGISTRATION ACCEPT message does not include a T3324 value IE, UE shall not start the timer T3324 until a new value is received from the network. If the REGISTRATION ACCEPT message included a non-3GPP de-registration timer value IE, the UE shall use the value in non-3GPP de-registration timer value IE as non-3GPP de-registration timer. If non-3GPP de-registration timer value IE is not included, the UE shall use the value currently stored, e.g. from a prior REGISTRATION ACCEPT message. If non-3GPP de-registration timer value IE is not included and there is no stored non-3GPP de-registration timer value in the UE, the UE shall use the default value of the non-3GPP de-registration timer. If the REGISTRATION ACCEPT message contains a 5G-GUTI, the UE shall return a REGISTRATION COMPLETE message to the AMF to acknowledge the received 5G-GUTI, stop timer T3519 if running, and delete any stored SUCI. The UE shall provide the 5G-GUTI to the lower layer of 3GPP access if the REGISTRATION ACCEPT message is sent over the non-3GPP access, and the UE is in 5GMM-REGISTERED in both 3GPP access and non-3GPP access in the same PLMN. If the REGISTRATION ACCEPT message contains a) the Network slicing indication IE with the Network slicing subscription change indication set to "Network slicing subscription changed"; b) a Configured NSSAI IE with a new configured NSSAI for the current PLMN or SNPN and optionally the mapped S-NSSAI(s) for the configured NSSAI for the current PLMN or SNPN; c) an NSSRG information IE with a new NSSRG information; d) an Alternative NSSAI IE with a new alternative NSSAI; e) an S-NSSAI location validity information in the Registration accept type 6 IE container IE with a new S-NSSAI location validity information; or f) an S-NSSAI time validity information IE with a new S-NSSAI time validity information, the UE shall return a REGISTRATION COMPLETE message to the AMF to acknowledge the successful update of the network slicing information. If the UE has set the RCMAN bit to "Sending of REGISTRATION COMPLETE message for NSAG information supported" in the 5GMM capability IE of the REGISTRATION REQUEST message and if REGISTRATION ACCEPT message contains the NSAG information IE, the UE shall return REGISTRATION COMPLETE message to the AMF to acknowledge the reception of the NSAG information IE. NOTE 7B: When the UE receives the NSSRG information IE, the UE may provide the NSSRG information to lower layers for the purpose of NSAG-aware cell reselection. If the REGISTRATION ACCEPT message contains the CAG information list IE or the Extended CAG information list IE and the UE had set the CAG bit to "CAG supported" in the 5GMM capability IE of the REGISTRATION REQUEST message, the UE shall: a) replace the "CAG information list" stored in the UE with the received CAG information list IE or the Extended CAG information list IE when received in the HPLMN or EHPLMN; b) replace the serving VPLMN's entry of the "CAG information list" stored in the UE with the serving VPLMN's entry of the received CAG information list IE or the Extended CAG information list IE when the UE receives the CAG information list IE or the Extended CAG information list IE in a serving PLMN other than the HPLMN or EHPLMN; or NOTE 7: When the UE receives the CAG information list IE or the Extended CAG information list IE in a serving PLMN other than the HPLMN or EHPLMN, entries of a PLMN other than the serving VPLMN, if any, in the received CAG information list IE or the Extended CAG information list IE are ignored. c) remove the serving VPLMN's entry of the "CAG information list" stored in the UE when the UE receives the CAG information list IE or the Extended CAG information list IE in a serving PLMN other than the HPLMN or EHPLMN and the CAG information list IE or the Extended CAG information list IE does not contain the serving VPLMN's entry. The UE shall store the "CAG information list" received in the CAG information list IE or the Extended CAG information list IE as specified in annex C. If the received "CAG information list" includes an entry containing the identity of the registered PLMN, the UE shall operate as follows. a) if the UE receives the REGISTRATION ACCEPT message via a CAG cell,none of the CAG-ID(s) supported by the current CAG cell is authorized based on the "Allowed CAG list" of the entry for the registered PLMN in the received "CAG information list", and: 1) the entry for the registered PLMN in the received "CAG information list" does not include an "indication that the UE is only allowed to access 5GS via CAG cells", then the UE shall enter the state 5GMM-REGISTERED.LIMITED-SERVICE and shall search for a suitable cell according to 3GPP TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [28] or 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [25C] with the updated "CAG information list"; or 2) the entry for the registered PLMN in the received "CAG information list" includes an "indication that the UE is only allowed to access 5GS via CAG cells" and: i) if one or more CAG-ID(s) are authorized based on the "Allowed CAG list" of the entry for the registered PLMN in the received "CAG information list", the UE shall enter the state 5GMM-REGISTERED.LIMITED-SERVICE and shall search for a suitable cell according to 3GPP TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [28] with the updated "CAG information list"; or ii) if no CAG-ID is authorized based on the "Allowed CAG list" of the entry for the registered PLMN in the received "CAG information list" and: A) the UE does not have an emergency PDU session, then the UE shall enter the state 5GMM-REGISTERED.PLMN-SEARCH and shall apply the PLMN selection process defined in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] with the updated "CAG information list"; or B) the UE has an emergency PDU session, then the UE shall perform a local release of all PDU sessions associated with 3GPP access except for the emergency PDU session and enter the state 5GMM-REGISTERED.LIMITED-SERVICE; or b) if the UE receives the REGISTRATION ACCEPT message via a non-CAG cell and the entry for the registered PLMN in the received "CAG information list" includes an "indication that the UE is only allowed to access 5GS via CAG cells" and: 1) if one or more CAG-ID(s) are authorized based on the "allowed CAG list" for the registered PLMN in the received "CAG information list", the UE shall enter the state 5GMM-REGISTERED.LIMITED-SERVICE and shall search for a suitable cell according to 3GPP TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [28] with the updated "CAG information list"; or 2) if no CAG-ID is authorized based on the "Allowed CAG list" of the entry for the registered PLMN in the received "CAG information list" and: i) the UE does not have an emergency PDU session, then the UE shall enter the state 5GMM-REGISTERED.PLMN-SEARCH and shall apply the PLMN selection process defined in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] with the updated "CAG information list"; or ii) the UE has an emergency PDU session, then the UE shall perform a local release of all PDU sessions associated with 3GPP access except for the emergency PDU session and enter the state 5GMM-REGISTERED.LIMITED-SERVICE. If the received "CAG information list" does not include an entry containing the identity of the registered PLMN and the UE receives the REGISTRATION ACCEPT message via a CAG cell, the UE shall enter the state 5GMM-REGISTERED.LIMITED-SERVICE and shall search for a suitable cell according to 3GPP TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [28] or 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [25C] with the updated "CAG information list". If the REGISTRATION ACCEPT message contains the Operator-defined access category definitions IE, the Extended emergency number list IE, the CAG information list IE or the Extended CAG information list IE, the UE shall return a REGISTRATION COMPLETE message to the AMF to acknowledge reception of the operator-defined access category definitions or the extended local emergency numbers list or the CAG information list. If the UE has set the RCMAP bit to " Sending of REGISTRATION COMPLETE message for negotiated PEIPS assistance information supported " in the 5GMM capability IE of the REGISTRATION REQUEST message and if REGISTRATION ACCEPT message contains the Negotiated PEIPS assistance parameters IE, the UE shall return a REGISTRATION COMPLETE message to the AMF to acknowledge reception of the Negotiated PEIPS assistance parameters IE. If the REGISTRATION ACCEPT message contains the UE radio capability ID IE or the UE radio capability ID deletion indication IE, the UE shall return a REGISTRATION COMPLETE message to the AMF to acknowledge reception of the UE radio capability ID IE or the UE radio capability ID deletion indication IE. If the T3448 value IE is present in the received REGISTRATION ACCEPT message and the value indicates that this timer is neither zero nor deactivated, the UE shall: a) stop timer T3448 if it is running; and b) start timer T3448 with the value provided in the T3448 value IE. If the UE is using 5GS services with control plane CIoT 5GS optimization, the T3448 value IE is present in the REGISTRATION ACCEPT message and the value indicates that this timer is either zero or deactivated, the UE shall ignore the T3448 value IE and proceed as if the T3448 value IE was not present. If the UE in 5GMM-IDLE mode initiated the registration procedure for mobility and periodic registration update and the REGISTRATION ACCEPT message does not include the T3448 value IE and if timer T3448 is running, then the UE shall stop timer T3448. Upon receiving a REGISTRATION COMPLETE message, the AMF shall stop timer T3550 and change to state 5GMM-REGISTERED. The 5G-GUTI, if sent in the REGISTRATION ACCEPT message, shall be considered as valid, the PEIPS assistance information, if sent in the REGISTRATION ACCEPT message, shall be considered as valid, and the UE radio capability ID, if sent in the REGISTRATION ACCEPT message, shall be considered as valid. If the 5GS update type IE was included in the REGISTRATION REQUEST message with the SMS requested bit set to "SMS over NAS supported" and: a) the SMSF address is stored in the UE 5GMM context and: 1) the UE is considered available for SMS over NAS; or 2) the UE is considered not available for SMS over NAS and the SMSF has confirmed that the activation of the SMS service is successful; or b) the SMSF address is not stored in the UE 5GMM context, the SMSF selection is successful and the SMSF has confirmed that the activation of the SMS service is successful; then the AMF shall set the SMS allowed bit of the 5GS registration result IE in the REGISTRATION ACCEPT message as specified in subclause 5.5.1.2.4. If the UE 5GMM context does not contain an SMSF address or the UE is not considered available for SMS over NAS, then the AMF shall: a) store the SMSF address in the UE 5GMM context if not stored already; and b) store the value of the SMS allowed bit of the 5GS registration result IE in the UE 5GMM context and consider the UE available for SMS over NAS. If SMSF selection in the AMF or SMS activation via the SMSF is not successful, or the AMF does not allow the use of SMS over NAS, then the AMF shall set the SMS allowed bit of the 5GS registration result IE to "SMS over NAS not allowed" in the REGISTRATION ACCEPT message. If the 5GS update type IE was included in the REGISTRATION REQUEST message with the SMS requested bit set to "SMS over NAS not supported" or the 5GS update type IE was not included in the REGISTRATION REQUEST message, then the AMF shall: a) mark the 5GMM context to indicate that the UE is not available for SMS over NAS; and NOTE 8: The AMF can notify the SMSF that the UE is deregistered from SMS over NAS based on local configuration. b) set the SMS allowed bit of the 5GS registration result IE to "SMS over NAS not allowed" in the REGISTRATION ACCEPT message. When the UE receives the REGISTRATION ACCEPT message, if the UE is also registered over another access to the same PLMN, the UE considers the value indicated by the SMS allowed bit of the 5GS registration result IE as applicable for both accesses over which the UE is registered. If the 5GS update type IE was included in the REGISTRATION REQUEST message with the NG-RAN-RCU bit set to "UE radio capability update needed", the AMF shall delete the stored UE radio capability information or the UE radio capability ID, if any. The AMF shall include the 5GS registration result IE in the REGISTRATION ACCEPT message. If the 5GS registration result value in the 5GS registration result IE indicates: a) "3GPP access", the UE: - shall consider itself as being registered to 3GPP access; and - if in 5GMM-REGISTERED state over non-3GPP access and on the same PLMN or SNPN as 3GPP access, shall enter state 5GMM-DEREGISTERED.ATTEMPTING-REGISTRATION over non-3GPP access and set the 5GS update status to 5U2 NOT UPDATED over non-3GPP access; or b) "Non-3GPP access", the UE: - shall consider itself as being registered to non-3GPP access; and - if in the 5GMM-REGISTERED state over 3GPP access and is on the same PLMN or SNPN as non-3GPP access, shall enter the state 5GMM-DEREGISTERED.ATTEMPTING-REGISTRATION over 3GPP access and set the 5GS update status to 5U2 NOT UPDATED over 3GPP access; or c) "3GPP access and non-3GPP access", the UE shall consider itself as being registered to both 3GPP access and non-3GPP access. If the UE is not currently registered for emergency services and the emergency registered bit of the 5GS registration result IE in the REGISTRATION ACCEPT message is set to "Registered for emergency services", the UE shall consider itself registered for emergency services and shall locally release all non-emergency PDU sessions, if any. In roaming scenarios, the AMF shall provide mapped S-NSSAI(s) for the configured NSSAI, the allowed NSSAI, the partially allowed NSSAI, the rejected NSSAI (if Extended rejected NSSAI IE is used), the partially rejected NSSAI, the pending NSSAI or NSSRG information when included in the REGISTRATION ACCEPT message. The AMF shall include the allowed NSSAI for the current PLMN or SNPN, in roaming scenarios, and shall include the mapped S-NSSAI(s) for the allowed NSSAI contained in the requested NSSAI (i.e. Requested NSSAI IE or Requested mapped NSSAI IE) from the UE, in the REGISTRATION ACCEPT message if the UE included the requested NSSAI in the REGISTRATION REQUEST message and the AMF allows one or more S-NSSAIs for the current PLMN or SNPN in the Requested NSSAI IE or one or more mapped S-NSSAIs in the Requested NSSAI IE or Requested mapped NSSAI IE. Additionally, if the AMF allows one or more subscribed S-NSSAIs for the UE, the AMF may include the allowed subscribed S-NSSAI(s) in the allowed NSSAI in the REGISTRATION ACCEPT message. The S-NSSAI associated with each of the active PDN connections for which interworking to 5GS is supported, shall be included in the allowed NSSAI if the UE included the UE status IE with the EMM registration status set to "UE is in EMM-REGISTERED state" in the REGISTRATION REQUEST message and the AMF supports N26 interface. The AMF may also include rejected NSSAI in the REGISTRATION ACCEPT message if the UE is not registered for onboarding services in SNPN. If the UE has set the ER-NSSAI bit to "Extended rejected NSSAI supported" in the 5GMM capability IE of the REGISTRATION REQUEST message, the rejected NSSAI shall be included in the Extended rejected NSSAI IE in the REGISTRATION ACCEPT message; otherwise the rejected NSSAI shall be included in the Rejected NSSAI IE in the REGISTRATION ACCEPT message. If the UE is registered for onboarding services in SNPN, the AMF shall not include rejected NSSAI in the REGISTRATION ACCEPT message. If the UE has indicated the support for partial network slice and the AMF determines one or more S-NSSAI(s) in the requested NSSAI are to be included in the partially rejected NSSAI as specified in subclause 4.6.2.11, the AMF shall include the Partially rejected NSSAI IE in the Registration accept type 6 IE container IE of the REGISTRATION ACCEPT message. If the UE receives the Partially rejected NSSAI IE in the Registration accept type 6 IE container IE of the REGISTRATION ACCEPT message, the UE shall store the partially rejected NSSAI as specified in subclause 4.6.2.2. If the UE has set the ER-NSSAI bit to "Extended rejected NSSAI supported" in the 5GMM capability IE of the REGISTRATION REQUEST message, the rejected NSSAI contains S-NSSAI(s) which was included in the requested NSSAI but rejected by the network associated with rejection cause(s); otherwise the rejected NSSAI contains S-NSSAI(s) which was included in the requested NSSAI but rejected by the network associated with rejection cause(s) with the following restrictions: a) rejected NSSAI for the current PLMN or SNPN shall not include an S-NSSAI for the current PLMN or SNPN which is associated to multiple mapped S-NSSAIs and some of these but not all mapped S-NSSAIs are not allowed; and b) rejected NSSAI for the current registration area shall not include an S-NSSAI for the current PLMN or SNPN which is associated to multiple mapped S-NSSAIs and some of these but not all mapped S-NSSAIs are not allowed. NOTE 9: The UE that does not support extended rejected NSSAI can avoid requesting an S-NSSAI associated with a mapped S-NSSAI, which was included in the previous requested NSSAI but neither in the allowed NSSAI nor in the rejected NSSAI in the consequent registration procedures. If the UE indicated the support for network slice-specific authentication and authorization, and if the requested NSSAI (i.e. the Requested NSSAI IE or the Requested mapped NSSAI IE) includes one or more S-NSSAIs subject to network slice-specific authentication and authorization, the AMF shall in the REGISTRATION ACCEPT message include: a) the allowed NSSAI containing the S-NSSAI(s) or the mapped S-NSSAI(s), if any: i) which are not subject to network slice-specific authentication and authorization and are allowed by the AMF; or ii) for which the network slice-specific authentication and authorization has been successfully performed; aa) the partially allowed NSSAI containing the S-NSSAI(s) or the mapped S-NSSAI(s), if any: i) which are not subject to network slice-specific authentication and authorization and are allowed by the AMF; or ii) for which the network slice-specific authentication and authorization has been successfully performed; b) optionally, the rejected NSSAI; ba) optionally, the partially rejected NSSAI; c) pending NSSAI containing one or more S-NSSAIs for which network slice-specific authentication and authorization (except for re-NSSAA) will be performed or is ongoing, and one or more S-NSSAIs from the pending NSSAI which the AMF provided to the UE during the previous registration procedure for which network slice-specific authentication and authorization will be performed or is ongoing, if any; and d) the "NSSAA to be performed" indicator in the 5GS registration result IE set to indicate that the network slice-specific authentication and authorization procedure will be performed by the network, if the allowed NSSAI is not included in the REGISTRATION ACCEPT message. If the UE is not registered for onboarding services in SNPN, the UE indicated the support for network slice-specific authentication and authorization, and: a) the UE did not include the requested NSSAI in the REGISTRATION REQUEST message or none of the S-NSSAIs in the requested NSSAI in the REGISTRATION REQUEST message are allowed; b) all default S-NSSAIs are subject to network slice-specific authentication and authorization; and c) the network slice-specific authentication and authorization procedure has not been successfully performed for any of the default S-NSSAIs, the AMF shall in the REGISTRATION ACCEPT message include: a) the "NSSAA to be performed" indicator in the 5GS registration result IE to indicate that the network slice-specific authentication and authorization procedure will be performed by the network; and b) pending NSSAI containing one or more default S-NSSAIs for which network slice-specific authentication and authorization will be performed or is ongoing and one or more S-NSSAIs from the pending NSSAI which the AMF provided to the UE during the previous registration procedure for which network slice-specific authentication and authorization will be performed or is ongoing (if any); and c) optionally, the rejected NSSAI. If the UE is not registered for onboarding services in SNPN, the UE indicated the support for network slice-specific authentication and authorization, and: a) the UE did not include the requested NSSAI in the REGISTRATION REQUEST message or none of the S-NSSAIs in the requested NSSAI in the REGISTRATION REQUEST message are allowed; and b) one or more default S-NSSAIs are not subject to network slice-specific authentication and authorization or the network slice-specific authentication and authorization procedure has been successfully performed for one or more default S-NSSAIs; the AMF shall in the REGISTRATION ACCEPT message include: a) pending NSSAI containing one or more default S-NSSAIs for which network slice-specific authentication and authorization will be performed or is ongoing (if any) and one or more S-NSSAIs from the pending NSSAI which the AMF provided to the UE during the previous registration procedure for which network slice-specific authentication and authorization will be performed or is ongoing (if any); b) allowed NSSAI containing S-NSSAI(s) for the current PLMN or SNPN each of which corresponds to a default S-NSSAI which are not subject to network slice-specific authentication and authorization or for which the network slice-specific authentication and authorization has been successfully performed; c) allowed NSSAI containing one or more default S-NSSAIs, as the mapped S-NSSAI(s) for the allowed NSSAI in roaming scenarios, which are not subject to network slice-specific authentication and authorization or for which the network slice-specific authentication and authorization has been successfully performed; and d) optionally, the rejected NSSAI; and e) optionally, the partially rejected NSSAI. If the UE did not include the requested NSSAI in the REGISTRATION REQUEST message or none of the S-NSSAIs in the requested NSSAI in the REGISTRATION REQUEST message are allowed, the allowed NSSAI shall not contain default S-NSSAI(s) that are subject to NSAC. If the subscription information includes the NSSRG information, the S-NSSAIs of the allowed NSSAI shall be associated with at least one common NSSRG value. If the network has pending NSSAI, the S-NSSAIs in the pending NSSAI and allowed NSSAI shall be associated with at least one common NSSRG value. When the REGISTRATION ACCEPT includes a pending NSSAI, the pending NSSAI shall contain all S-NSSAIs for which network slice-specific authentication and authorization (except for re-NSSAA) will be performed or is ongoing from the requested NSSAI of the REGISTRATION REQUEST message that was received over the 3GPP access, non-3GPP access, or both the 3GPP access and non-3GPP access. If the UE supports extended rejected NSSAI and the AMF determines that maximum number of UEs reached for all S-NSSAIs in the requested NSSAI as specified in subclause 4.6.2.5, the AMF shall include the rejected NSSAI containing one or more S-NSSAIs with the rejection cause "S-NSSAI not available due to maximum number of UEs reached" in the Extended rejected NSSAI IE in the REGISTRATION ACCEPT message. In addition, the AMF may include a back-off timer value for each S-NSSAI with the rejection cause "S-NSSAI not available due to maximum number of UEs reached" included in the Extended rejected NSSAI IE of the REGISTRATION ACCEPT message. To avoid that large numbers of UEs simultaneously initiate deferred requests, the network should select the value for the backoff timer for each S-NSSAI for the informed UEs so that timeouts are not synchronised. If the UE does not indicate support for extended rejected NSSAI and the maximum number of UEs has been reached, the AMF should include the rejected NSSAI containing one or more S-NSSAIs with the rejection cause "S-NSSAI not available in the current registration area" in the Rejected NSSAI IE and should not include these S-NSSAIs in the allowed NSSAI in the REGISTRATION ACCEPT message. NOTE 10: Based on network policies, the AMF can include the S-NSSAI(s) for which the maximum number of UEs has been reached in the rejected NSSAI with rejection causes other than "S-NSSAI not available in the current registration area". If the UE indicates for the support network slice usage control and the AMF determines to provide the on-demand NSSAI, the AMF shall include the On-demand NSSAI IE in the REGISTRATION ACCEPT message. If the UE supports network slice usage control and the AMF determines to provide the on-demand NSSAI, the AMF shall include the On-demand NSSAI IE in the REGISTRATION ACCEPT message. If the UE receives the On-demand NSSAI IE in the REGISTRATION ACCEPT message, the UE shall store the on-demand NSSAI as specified in subclause 4.6.2.2. If the AMF has a new configured NSSAI for the current PLMN or SNPN, the AMF shall include the configured NSSAI for the current PLMN or SNPN in the REGISTRATION ACCEPT message. NOTE 10A: A new configured NSSAI can be available at the AMF following an indication that the subscription data for network slicing has changed. The AMF may include a new configured NSSAI for the current PLMN or SNPN in the REGISTRATION ACCEPT message if: a) the REGISTRATION REQUEST message did not include a requested NSSAI and the UE is not registered for onboarding services in SNPN; b) the REGISTRATION REQUEST message included a requested NSSAI containing an S-NSSAI that is not valid in the serving PLMN or SNPN; c) the REGISTRATION REQUEST message included a requested NSSAI containing an S-NSSAI with incorrect mapped S-NSSAI(s); d) the REGISTRATION REQUEST message included the Network slicing indication IE with the Default configured NSSAI indication bit set to "Requested NSSAI created from default configured NSSAI"; e) the REGISTRATION REQUEST message included the requested mapped NSSAI; f) the S-NSSAIs of the requested NSSAI in the REGISTRATION REQUEST message are not associated with any common NSSRG value, except for the case that the AMF, based on the indication received from the UDM as specified in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8], has provided all subscribed S-NSSAIs in the configured NSSAI to a UE who does not support NSSRG; NOTE 11: If the S-NSSAIs of the requested NSSAI in the REGISTRATION REQUEST message are not associated with any common NSSRG value, it is possible that at least one of the S-NSSAIs is not included in any of new allowed NSSAI, new (extended) rejected NSSAI (if applicable), and new pending NSSAI (if applicable). g) the UE is in 5GMM-REGISTERED state over the other access and the S-NSSAIs of the requested NSSAI in the REGISTRATION REQUEST message over the current access and the allowed NSSAI over the other access are not associated with any common NSSRG value; h) the REGISTRATION REQUEST message included a 5GS mobile identity IE containing a mapped 5G-GUTI and did not include an Additional GUTI IE; or i) the REGISTRATION REQUEST message included an Additional GUTI IE containing a valid native 5G-GUTI which was not allocated by the current PLMN or SNPN. The AMF may include a new configured NSSAI for the current PLMN or SNPN in the REGISTRATION ACCEPT message if the REGISTRATION REQUEST message includes a requested NSSAI containing an S-NSSAI and the S-NSSAI time validity information, if available, indicates that the S-NSSAI is not available (see 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]). In this case, if the TempNS bit of the 5GMM capability IE in the REGISTRATION REQUEST message is set to: a) "S-NSSAI time validity information supported" and the S-NSSAI time validity information indicates that the S-NSSAI will: 1) become available again, then the AMF shall also send S-NSSAI time validity information; or 2) not become available again, then the AMF shall not include the S-NSSAI in the new configured NSSAI; or b) "S-NSSAI time validity information not supported" and the AMF sends a new configured NSSAI, then the AMF shall not include the S-NSSAI in the new configured NSSAI. If a new configured NSSAI for the current PLMN or SNPN is included and the UE is roaming, the AMF shall also include the mapped S-NSSAI(s) for the configured NSSAI for the current PLMN or SNPN in the REGISTRATION ACCEPT message. In this case the AMF shall start timer T3550 and enter state 5GMM-COMMON-PROCEDURE-INITIATED as described in subclause 5.1.3.2.3.3. If a new configured NSSAI for the current PLMN or SNPN is included, the subscription information includes the NSSRG information, and the NSSRG bit in the 5GMM capability IE of the REGISTRATION REQUEST message is set to: a) "NSSRG supported", then the AMF shall include the NSSRG information in the REGISTRATION ACCEPT message; or b) "NSSRG not supported", then the configured NSSAI shall include S-NSSAIs each of which is associated with all the NSSRG value(s) of the default S-NSSAI(s), or the configured NSSAI shall include, based on the indication received from the UDM as specified in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8], all subscribed S-NSSAIs even if these S-NSSAIs do not share any common NSSRG value. If the AMF needs to update the NSSRG information and the UE has set the NSSRG bit to "NSSRG supported" in the 5GMM capability IE of the REGISTRATION REQUEST message, then the AMF shall include the new NSSRG information in the REGISTRATION ACCEPT message. In addition, the AMF shall start timer T3550 and enter state 5GMM-COMMON-PROCEDURE-INITIATED as described in subclause 5.1.3.2.3.3. If the UE supports S-NSSAI time validity information and the AMF needs to update the S-NSSAI time validity information, then the AMF shall include the S-NSSAI time validity information IE in the REGISTRATION ACCEPT message. In addition, the AMF shall start timer T3550 and enter state 5GMM-COMMON-PROCEDURE-INITIATED as described in subclause 5.1.3.2.3.3. If the UE supports S-NSSAI location validity information and the AMF needs to update the S-NSSAI location validity information, then the AMF shall include the S-NSSAI location validity information IE in the Registration accept type 6 IE container IE of the REGISTRATION ACCEPT message. In addition, the AMF shall start timer T3550 and enter state 5GMM-COMMON-PROCEDURE-INITIATED as described in subclause 5.1.3.2.3.3. The AMF shall include the Network slicing indication IE with the Network slicing subscription change indication set to "Network slicing subscription changed" in the REGISTRATION ACCEPT message if the UDM has indicated that the subscription data for network slicing has changed. In this case the AMF shall start timer T3550 and enter state 5GMM-COMMON-PROCEDURE-INITIATED as described in subclause 5.1.3.2.3.3. If the S-NSSAI(s) associated with the existing PDU session(s) of the UE is not included in the requested NSSAI (i.e. Requested NSSAI IE or Requested mapped NSSAI IE) of the REGISTRATION REQUEST message, the AMF shall perform a local release of the PDU session(s) associated with the S-NSSAI(s) except for a PDU session associated with DNN and S-NSSAI in the AMF onboarding configuration data and shall request the SMF to perform a local release of those PDU session(s). The UE that has indicated the support for network slice-specific authentication and authorization receiving the pending NSSAI in the REGISTRATION ACCEPT message shall store the S-NSSAI(s) in the pending NSSAI as specified in subclause 4.6.2.2. If the registration area contains TAIs belonging to different PLMNs, which are equivalent PLMNs, the UE shall store the received pending NSSAI for each of the equivalent PLMNs as specified in subclause 4.6.2.2. If the pending NSSAI is not included in the REGISTRATION ACCEPT message and the "NSSAA to be performed" indicator is not set to "Network slice-specific authentication and authorization is to be performed" in the 5GS registration result IE of the REGISTRATION ACCEPT message, then the UE shall delete the pending NSSAI for the current PLMN and its equivalent PLMN(s) or SNPN, if existing, as specified in subclause 4.6.2.2. The UE receiving the rejected NSSAI in the REGISTRATION ACCEPT message takes the following actions based on the rejection cause in the rejected S-NSSAI(s): "S-NSSAI not available in the current PLMN or SNPN" The UE shall add the rejected S-NSSAI(s) in the rejected NSSAI for the current PLMN or SNPN as specified in subclause 4.6.2.2 and shall not attempt to use this S-NSSAI(s) in the current PLMN or SNPN over any access until switching off the UE, the UICC containing the USIM is removed, the entry of the "list of subscriber data" with the SNPN identity of the current SNPN is updated, or the rejected S-NSSAI(s) are removed as described in subclause 4.6.2.2. "S-NSSAI not available in the current registration area" The UE shall add the rejected S-NSSAI(s) in the rejected NSSAI for the current registration area as specified in subclause 4.6.2.2 and shall not attempt to use this S-NSSAI(s) in the current registration area over the current until switching off the UE, the UE moving out of the current registration area, the UICC containing the USIM is removed, the entry of the "list of subscriber data" with the SNPN identity of the current SNPN is updated, or the rejected S-NSSAI(s) are removed as described in subclause 4.6.2.2. "S-NSSAI not available due to the failed or revoked network slice-specific authentication and authorization" The UE shall store the rejected S-NSSAI(s) in the rejected NSSAI for the failed or revoked NSSAA as specified in subclause 4.6.2.2 and shall not attempt to use this S-NSSAI in the current PLMN or SNPN over any access until switching off the UE, the UICC containing the USIM is removed, the entry of the "list of subscriber data" with the SNPN identity of the current SNPN is updated, or the rejected S-NSSAI(s) are removed as described in subclause 4.6.1 and 4.6.2.2. "S-NSSAI not available due to maximum number of UEs reached" Unless the back-off timer value received along with the S-NSSAI is zero, the UE shall add the rejected S-NSSAI(s) in the rejected NSSAI for the maximum number of UEs reached as specified in subclause 4.6.2.2 and shall not attempt to use this S-NSSAI in the current PLMN or SNPN over the current access until switching off the UE, the UICC containing the USIM is removed, the entry of the "list of subscriber data" with the SNPN identity of the current SNPN is updated, or the rejected S-NSSAI(s) are removed as described in subclauses 4.6.1 and 4.6.2.2. NOTE 12: If the back-off timer value received along with the S-NSSAI in the rejected NSSAI for the maximum number of UEs reached is zero as specified in subclause 10.5.7.4a of 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [12], the UE does not consider the S-NSSAI as the rejected S-NSSAI. If there is one or more S-NSSAIs in the rejected NSSAI with the rejection cause "S-NSSAI not available due to maximum number of UEs reached", then for each S-NSSAI, the UE shall behave as follows: a) stop the timer T3526 associated with the S-NSSAI, if running; b) start the timer T3526 with: 1) the back-off timer value received along with the S-NSSAI, if a back-off timer value is received along with the S-NSSAI that is neither zero nor deactivated; or 2) an implementation specific back-off timer value, if no back-off timer value is received along with the S-NSSAI; and c) remove the S-NSSAI from the rejected NSSAI for the maximum number of UEs reached when the timer T3526 associated with the S-NSSAI expires. If the UE sets the NSSAA bit in the 5GMM capability IE to "Network slice-specific authentication and authorization not supported", and: a) if the Requested NSSAI IE only includes the S-NSSAI(s) subject to network slice-specific authentication and authorization and one or more default S-NSSAIs (containing one or more S-NSSAIs each of which may be associated with a new S-NSSAI) which are not subject to network slice-specific authentication and authorization are available, the AMF shall in the REGISTRATION ACCEPT message include: 1) the allowed NSSAI or the partially allowed NSSAI containing S-NSSAI(s) for the current PLMN or SNPN each of which corresponds to a default S-NSSAI which are not subject to network slice-specific authentication and authorization; 2) the allowed NSSAI or the partially allowed NSSAI containing the default S-NSSAIs, as the mapped S-NSSAI(s) for the allowed NSSAI in roaming scenarios, which are not subject to network slice-specific authentication and authorization; and 3) the rejected NSSAI containing the S-NSSAI(s) subject to network slice specific authentication and authorization with the rejection cause indicating "S-NSSAI not available in the current PLMN or SNPN", except if the UE has not set the ER-NSSAI bit to "Extended rejected NSSAI supported" in the 5GMM capability IE of the REGISTRATION REQUEST message and the S-NSSAI(s) is associated to multiple mapped S-NSSAIs and some of these but not all mapped S-NSSAIs are subject to NSSAA; or b) if the Requested NSSAI IE includes one or more S-NSSAIs subject to network slice-specific authentication and authorization, the AMF shall in the REGISTRATION ACCEPT message include: 1) the allowed NSSAI or the partially allowed NSSAI containing the S-NSSAI(s) or the mapped S-NSSAI(s) which are not subject to network slice-specific authentication and authorization; and 2) the rejected NSSAI containing: i) the S-NSSAI(s) subject to network slice specific authentication and authorization with the rejection cause indicating "S-NSSAI not available in the current PLMN or SNPN", except if the UE has not set the ER-NSSAI bit to "Extended rejected NSSAI supported" in the 5GMM capability IE of the REGISTRATION REQUEST message and the S-NSSAI(s) is associated to multiple mapped S-NSSAIs and some of these but not all mapped S-NSSAIs are subject to NSSAA; and ii) the S-NSSAI(s) which was included in the requested NSSAI but rejected by the network associated with the rejection cause indicating "S-NSSAI not available in the current PLMN or SNPN" or the rejection cause indicating "S-NSSAI not available in the current registration area", if any. For a REGISTRATION REQUEST message with a 5GS registration type IE indicating "mobility registration updating", if the UE does not indicate support for network slice-specific authentication and authorization, the UE is not registered for onboarding services in SNPN, and: a) the UE is not in NB-N1 mode; and b) if: 1) the UE did not include the requested NSSAI in the REGISTRATION REQUEST message; or 2) none of the S-NSSAIs in the requested NSSAI in the REGISTRATION REQUEST message are allowed; and one or more default S-NSSAIs which are not subject to network slice-specific authentication and authorization are available, the AMF shall: a) put the allowed S-NSSAI(s) for the current PLMN or SNPN each of which corresponds to a default S-NSSAI and not subject to network slice-specific authentication and authorization in the allowed NSSAI of the REGISTRATION ACCEPT message; b) put the default S-NSSAIs and not subject to network slice-specific authentication and authorization, as the mapped S-NSSAI(s) for the allowed NSSAI in roaming scenarios, in the allowed NSSAI of the REGISTRATION ACCEPT message; and c) determine a registration area such that all S-NSSAIs of the allowed NSSAI are available in the registration area. During a registration procedure for mobility and periodic registration update for which the 5GS registration type IE indicates: a) "periodic registration updating"; or b) "mobility registration updating" and the UE is in NB-N1 mode; and the UE is not registered for onboarding services in SNPN, the AMF: a) may provide a new allowed NSSAI, a new partially allowed NSSAI, or both to the UE; b) shall provide a pending NSSAI to the UE if the UE has indicated the support for network slice-specific authentication and authorization and there are S-NSSAIs for which network slice-specific authentication and authorization (except for re-NSSAA) will be performed or is ongoing for the current PLMN or SNPN; or c) may provide both a new allowed NSSAI and a pending NSSAI to the UE; in the REGISTRATION ACCEPT message. Additionally, if a pending NSSAI is provided without an allowed NSSAI and no S-NSSAI is currently allowed for the UE, the REGISTRATION ACCEPT message shall include the 5GS registration result IE with the "NSSAA to be performed" indicator set to "Network slice-specific authentication and authorization is to be performed". If the REGISTRATION ACCEPT message contains the Network slicing indication IE with the Network slicing subscription change indication set to "Network slicing subscription changed", the UE shall delete the network slicing information for each and every PLMN or SNPN except for the current PLMN or SNPN as specified in subclause 4.6.2.2 and remove all tracking areas from the list of "5GS forbidden tracking areas for roaming" which were added due to rejection of S-NSSAI due to "S-NSSAI not available in the current registration area". If the REGISTRATION ACCEPT message contains the allowed NSSAI, then the UE shall store the included allowed NSSAI together with the PLMN identity of the registered PLMN or the SNPN identity of the registered SNPN and the registration area as specified in subclause 4.6.2.2. If the registration area contains TAIs belonging to different PLMNs, which are equivalent PLMNs, the UE shall store the received allowed NSSAI in each of allowed NSSAIs which are associated with each of the PLMNs. For each of the PDU session(s) active in the UE: - if the allowed NSSAI contains an HPLMN S-NSSAI (e.g. mapped S-NSSAI, in roaming scenarios) matching to the HPLMN S-NSSAI of the PDU session, the UE shall locally update the S-NSSAI associated with the PDU session to the corresponding S-NSSAI received in the allowed NSSAI; and - if the allowed NSSAI does not contain an HPLMN S-NSSAI (e.g. mapped S-NSSAI, in roaming scenarios) matching to the HPLMN S-NSSAI of the PDU session, the UE may perform a local release of the PDU session except for an emergency PDU session, if any, and except for a PDU session established when the UE is registered for onboarding services in SNPN, if any. NOTE 13: According to 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8], also the AMF will determine which PDU sessions can no longer be supported based on the new allowed NSSAI, and it will cause a release on the UE side either by indicating in the PDU session status IE which PDU sessions are inactive on the network side or by triggering the SMF to initiate a release via 5GSM signalling. If the REGISTRATION ACCEPT message contains a configured NSSAI IE with a new configured NSSAI for the current PLMN or SNPN and optionally the mapped S-NSSAI(s) for the configured NSSAI for the current PLMN or SNPN, the UE shall store the contents of the configured NSSAI IE as specified in subclause 4.6.2.2. In addition, if the REGISTRATION ACCEPT message contains: a) an NSSRG information IE, the UE shall store the contents of the NSSRG information IE as specified in subclause 4.6.2.2. If the UE receives a Configured NSSAI IE in the REGISTRATION ACCEPT message and no NSSRG information IE, the UE shall delete any stored NSSRG information, if any, as specified in subclause 4.6.2.2; b) an S-NSSAI location validity information IE in the Registration accept type 6 IE container IE, the UE shall store the contents of the S-NSSAI location validity information as specified in subclause 4.6.2.2. If the UE receives a Configured NSSAI IE in the REGISTRATION ACCEPT message and no S-NSSAI location validity information IE, the UE shall delete any stored S-NSSAI location validity information as specified in subclause 4.6.2.2; c) an S-NSSAI time validity information IE, the UE shall store the contents of the S-NSSAI time validity information IE as specified in subclause 4.6.2.2. If the UE receives a Configured NSSAI IE in the REGISTRATION ACCEPT message and no S-NSSAI time validity information IE, the UE shall delete any stored S-NSSAI time validity information as specified in subclause 4.6.2.2; or d) an On-demand NSSAI IE, the UE shall store the contents of the On-demand NSSAI IE as specified in subclause 4.6.2.2. If the UE receives a Configured NSSAI IE in the REGISTRATION ACCEPT message and no On-demand NSSAI IE, the UE shall delete any stored on-demand NSSAI as specified in subclause 4.6.2.2. The UE shall stop any slice deregistration inactivity timer associated with an S-NSSAI which is deleted from the on-demand NSSAI. If the UE has set the NSAG bit to "NSAG supported" in the 5GMM capability IE of the REGISTRATION REQUEST message over 3GPP access, the AMF may include the NSAG information IE in the REGISTRATION ACCEPT message. Up to 4 NSAG entries are allowed to be associated with a TAI list in the NSAG information IE. If the UE has set the RCMAN bit to "Sending of REGISTRATION COMPLETE message for NSAG information supported" in the 5GMM capability IE of the REGISTRATION REQUEST message and if the NSAG information IE is included in the REGISTRATION ACCEPT message, the AMF shall start timer T3550 and enter state 5GMM-COMMON-PROCEDURE-INITIATED as described in subclause 5.1.3.2.3.3. NOTE 13A: How the AMF selects NSAG entries to be included in the NSAG information IE is implementation specific, e.g. take the NSAG priority and the current registration area into account. NOTE 13B: If the NSAG for the PLMN and its equivalent PLMN(s) have different associations with S-NSSAIs, then the AMF includes a TAI list for the NSAG entry in the NSAG information IE. NOTE 13C: If the NSAG for the PLMN and its equivalent PLMN(s) have different associations with S-NSSAIs, then the AMF includes a TAI list for the NSAG entry in the NSAG information IE. If the UE receives the NSAG information IE in the REGISTRATION ACCEPT message, the UE shall store the NSAG information as specified in subclause 4.6.2.2. If the UE supports network slice replacement and the AMF determines to provide the mapping information between the S-NSSAI to be replaced and the alternative S-NSSAI to the UE, then the AMF shall include the Alternative NSSAI IE, the Allowed NSSAI IE including the alternative S-NSSAI, if not included in the current allowed NSSAI, and the Configured NSSAI IE including the alternative S-NSSAI, if not included in the current configured NSSAI, in the REGISTRATION ACCEPT message. If the AMF determines that the S-NSSAI which has been replaced is available, then the AMF shall provide the updated alternative NSSAI excluding the S-NSSAI which has been replaced and the corresponding alternative S-NSSAI in the Alternative NSSAI IE in the REGISTRATION ACCEPT message. If the AMF determines that all the S-NSSAI(s) which have been replaced are available, then the AMF shall provide the Alternative NSSAI IE with Length of Alternative NSSAI contents set to 0 in the REGISTRATION ACCEPT message. In addition, the AMF shall start timer T3550 and enter state 5GMM-COMMON-PROCEDURE-INITIATED as described in subclause 5.1.3.2.3.3. If the UE receives the Alternative NSSAI IE in the REGISTRATION ACCEPT message, the UE shall store the alternative NSSAI as specified in subclause 4.6.2.2. If the UE has indicated the support for partial network slice and the AMF determines one or more S-NSSAI(s) in the requested NSSAI are to be included in the partially allowed NSSAI as specified in subclause 4.6.2.11, the AMF shall include the Partially allowed NSSAI IE in the Registration accept type 6 IE container IE of the REGISTRATION ACCEPT message. If the UE receives the Partially allowed NSSAI IE in the Registration accept type 6 IE container IE of the REGISTRATION ACCEPT message, the UE shall store the partially allowed NSSAI as specified in subclause 4.6.2.2. If the REGISTRATION ACCEPT message: a) includes the 5GS registration result IE with the "NSSAA to be performed" indicator set to "Network slice-specific authentication and authorization is to be performed"; b) includes a pending NSSAI; c) does not include an allowed NSSAI; d) does not include a partially allowed NSSAI; the UE: a) shall not perform the registration procedure for mobility and periodic registration update with the Uplink data status IE except for emergency services; b) shall not initiate a service request procedure except for emergency services, for responding to paging or notification over non-3GPP access, for cases f), i), m) and o) in subclause 5.6.1.1; c) shall not initiate a 5GSM procedure except for emergency services, indicating a change of 3GPP PS data off UE status, or to request the release of a PDU session; and d) shall not initiate the NAS transport procedure except for sending a CIoT user data container, SMS, an LPP message, a UPP-CMI container, an SLPP message, a location services message, an SOR transparent container, a UE policy container or a UE parameters update transparent container; until the UE receives an allowed NSSAI, a partially allowed NSSAI, or both. During a registration procedure for mobility and periodic registration update for which the 5GS registration type IE indicates: a) "mobility registration updating" and the UE is in NB-N1 mode; or b) "periodic registration updating"; if the REGISTRATION ACCEPT message includes the 5GS registration result IE with the "NSSAA to be performed" indicator not set to "Network slice-specific authentication and authorization is to be performed" and the message does not contain an allowed NSSAI and no new allowed NSSAI, the UE shall consider the previously received allowed NSSAI as valid. During a registration procedure for mobility and periodic registration update for which the 5GS registration type IE indicates: a) "mobility registration updating"; or b) "periodic registration updating"; if the REGISTRATION ACCEPT message includes the 5GS registration result IE with the "NSSAA to be performed" indicator set to "Network slice-specific authentication and authorization is to be performed" and the message contains a pending NSSAI, the UE shall delete any stored allowed NSSAI as specified in subclause 4.6.2.2. If the Uplink data status IE is included in the REGISTRATION REQUEST message: a) if the AMF determines that the UE is in non-allowed area or is not in allowed area, and the PDU session(s) indicated by the Uplink data status IE is non-emergency PDU session(s) or the UE is not configured for high priority access in selected PLMN or SNPN, the AMF shall include the PDU session reactivation result IE in the REGISTRATION ACCEPT message indicating that user-plane resources for the corresponding PDU session(s) cannot be re-established, and shall include the PDU session reactivation result error cause IE with the 5GMM cause set to #28 "Restricted service area"; b) otherwise, the AMF shall: 1) indicate the SMF to re-establish the user-plane resources for the corresponding PDU session; 2) include PDU session reactivation result IE in the REGISTRATION ACCEPT message to indicate the user-plane resources re-establishment result of the PDU sessions for which the UE requested to re-establish the user-plane resources; and 3) determine the UE presence in LADN service area (see subclause 6.2.6) and forward the UE presence in LADN service area towards the SMF, if the corresponding PDU session is a PDU session for LADN. If the Uplink data status IE is not included in the REGISTRATION REQUEST message and the REGISTRATION REQUEST message is sent for the trigger d) in subclause 5.5.1.3.2, the AMF may indicate the SMF to re-establish the user-plane resources for the PDU sessions. If the registration procedure for mobility registration update is triggered for non-3GPP access path switching from the old non-3GPP access to the new non-3GPP access and there are: a) one or more single access PDU sessions whose user plane resources are associated to the old non-3GPP access but whose PDU session ID(s) are not indicated in the Uplink data status IE in the REGISTRATION REQUEST message; or b) one or more MA PDU sessions whose PDU session ID(s) are not indicated in the Uplink data status IE in the REGISTRATION REQUEST message; the AMF shall not release those PDU session(s) and shall release the user plane resources of the old non-3GPP access of those PDU session(s), so that the UE or the network can re-establish user-plane resources on the new non-3GPP access by triggering a service request procedure. If a PDU session status IE is included in the REGISTRATION REQUEST message: a) for single access PDU sessions, the AMF shall: 1) perform a local release of all those PDU sessions which are not in 5GSM state PDU SESSION INACTIVE on the AMF side associated with the access type the REGISTRATION REQUEST message is sent over, but are indicated by the UE as being in 5GSM state PDU SESSION INACTIVE. If any of those PDU sessions is associated with one or more MBS multicast sessions, the SMF shall consider the UE as removed from the associated multicast MBS sessions; and 2) include a PDU session status IE in the REGISTRATION ACCEPT message to indicate which PDU sessions associated with the access type the REGISTRATION ACCEPT message is sent over are not in 5GSM state PDU SESSION INACTIVE in the AMF; and b) for MA PDU sessions: 1) for all those PDU sessions which are not in 5GSM state PDU SESSION INACTIVE and have user plane resources being established or established on the access the REGISTRATION REQUEST message is sent over on the AMF side, but are indicated by the UE as no user plane resources are being established or established: i) for PDU sessions having user plane resources being established or established only on the access the REGISTRATION REQUEST message is sent over, the AMF shall perform a local release of all those PDU sessions. If the MA PDU session is associated with one or more multicast MBS sessions, the SMF shall consider the UE as removed from the associated multicast MBS sessions; and ii) for PDU sessions having user plane resources being established or established on both accesses, the AMF shall perform a local release on the user plane resources associated with the access type the REGISTRATION REQUEST message is sent over. If the REGISTRATION REQUEST message is sent over 3GPP access and the MA PDU session is associated with one or more multicast MBS sessions, the SMF shall consider the UE as removed from the associated multicast MBS sessions; and 2) the AMF shall include a PDU session status IE in the REGISTRATION ACCEPT message to indicate which MA PDU sessions having the corresponding user plane resources are being established or established on the AMF side on the access the REGISTRATION ACCEPT message is sent over. If the Allowed PDU session status IE is included in the REGISTRATION REQUEST message, the AMF shall: a) for a 5GSM message from each SMF that has indicated pending downlink signalling only, forward the received 5GSM message via 3GPP access to the UE after the REGISTRATION ACCEPT message is sent; b) for each SMF that has indicated pending downlink data only: 1) notify the SMF that reactivation of the user-plane resources for the corresponding PDU session(s) associated with non-3GPP access cannot be performed if the corresponding PDU session ID(s) are not indicated in the Allowed PDU session status IE; and 2) notify the SMF that reactivation of the user-plane resources for the corresponding PDU session(s) associated with non-3GPP access can be performed if the corresponding PDU session ID(s) are indicated in the Allowed PDU session status IE. c) for each SMF that have indicated pending downlink signalling and data: 1) notify the SMF that reactivation of the user-plane resources for the corresponding PDU session(s) associated with non-3GPP access cannot be performed if the corresponding PDU session ID(s) are not indicated in the Allowed PDU session status IE; 2) notify the SMF that reactivation of the user-plane resources for the corresponding PDU session(s) associated with non-3GPP access can be performed if the corresponding PDU session ID(s) are indicated in the Allowed PDU session status IE; and 3) discard the received 5GSM message for PDU session(s) associated with non-3GPP access; and d) include the PDU session reactivation result IE in the REGISTRATION ACCEPT message to indicate the successfully re-established user-plane resources for the corresponding PDU sessions, if any. If the PDU session reactivation result IE is included in the REGISTRATION ACCEPT message indicating that the user-plane resources have been successfully reactivated for a PDU session that was indicated by the UE in the Allowed PDU session status IE as allowed to be re-established over 3GPP access, the UE considers the corresponding PDU session to be associated with the 3GPP access. If the user-plane resources of a PDU session have been successfully reactivated over the 3GPP access, the AMF and SMF update the associated access type of the corresponding PDU session. If the PDU session reactivation result IE is included in the REGISTRATION ACCEPT message indicating that the user-plane resources cannot be established for a PDU session that was indicated by the UE in the Allowed PDU session status IE as allowed to be re-established over 3GPP access, the UE considers the corresponding PDU session to be associated with the non-3GPP access. If an EPS bearer context status IE is included in the REGISTRATION REQUEST message, the AMF handles the received EPS bearer context status IE as specified in 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9]. If the EPS bearer context status information is generated for the UE during the inter-system change from S1 mode to N1 mode as specified in 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9] and the AMF supports N26 interface, the AMF shall include an EPS bearer context status IE in the REGISTRATION ACCEPT message to indicate the UE which mapped EPS bearer contexts are active in the network. If the user-plane resources cannot be established for a PDU session, the AMF shall include the PDU session reactivation result IE in the REGISTRATION ACCEPT message indicating that user-plane resources for the corresponding PDU session cannot be re-established, and: a) if the user-plane resources cannot be established because the SMF indicated to the AMF that the UE is located out of the LADN service area (see 3GPP TS 29.502[ 5G System; Session Management Services; Stage 3 ] [20A]), the AMF shall include the PDU session reactivation result error cause IE with the 5GMM cause set to #43 "LADN not available"; b) if the user-plane resources cannot be established because the SMF indicated to the AMF that only prioritized services are allowed (see 3GPP TS 29.502[ 5G System; Session Management Services; Stage 3 ] [20A]), the AMF shall include the PDU session reactivation result error cause IE with the 5GMM cause set to #28 "restricted service area"; c) if the user-plane resources cannot be established because the SMF indicated to the AMF that the resource is not available in the UPF (see 3GPP TS 29.502[ 5G System; Session Management Services; Stage 3 ] [20A]), the AMF shall include the PDU session reactivation result error cause IE with the 5GMM cause set to #92 "insufficient user-plane resources for the PDU session"; d) if the user-plane resources cannot be established because the SMF indicated to the AMF that the S-NSSAI associated with the PDU session is unavailable due to NSAC (see 3GPP TS 29.502[ 5G System; Session Management Services; Stage 3 ] [20A]), the AMF shall include the PDU session reactivation result error cause IE with the 5GMM cause set to #69 "insufficient resources for specific slice"; or e) otherwise, the AMF may include the PDU session reactivation result error cause IE to indicate the cause of failure to re-establish the user-plane resources. NOTE 14: It is up to UE implementation when to re-send a request for user-plane re-establishment for the associated PDU session after receiving a PDU session reactivation result error cause IE with a 5GMM cause set to #92 "insufficient user-plane resources for the PDU session". NOTE 15: The UE can locally start a back-off timer after receiving a PDU session reactivation result error cause IE with a 5GMM cause set to #69 "insufficient resources for specific slice". The value of the back-off timer is up to UE implementation. Upon expiry of the back-off timer, the UE can re-send a request for user-plane re-establishment for the associated PDU session. If the AMF needs to initiate PDU session status synchronization the AMF shall include a PDU session status IE in the REGISTRATION ACCEPT message to indicate the UE: - which single access PDU sessions associated with the access the REGISTRATION ACCEPT message is sent over are not in 5GSM state PDU SESSION INACTIVE in the AMF; and - which MA PDU sessions are not in 5GSM state PDU SESSION INACTIVE and having user plane resources established in the AMF on the access the REGISTRATION ACCEPT message is sent over. The AMF may include the LADN information IE in the REGISTRATION ACCEPT message as described in subclause 5.5.1.2.4. The UE, upon receiving the REGISTRATION ACCEPT message with the LADN information IE, shall delete its old LADN information (if any) and store the received new LADN information. If the UE has set the LADN-DS bit to "LADN per DNN and S-NSSAI supported" in the 5GMM capability IE of the REGISTRATION REQUEST message, the AMF may include the Extended LADN information IE in the Registration accept type 6 IE container IE in the REGISTRATION ACCEPT message as described in subclause 5.5.1.2.4. The UE, upon receiving the REGISTRATION ACCEPT message with the Registration accept type 6 IE container IE which includes the Extended LADN information IE, shall delete its old extended LADN information (if any) and store the received new extended LADN information. If: - the UE does not support LADN per DNN and S-NSSAI; - the UE is subscribed to the LADN DNN for a single S-NSSAI only; and - the AMF only has the extended LADN information; the AMF may decide to provide the LADN service area for that LADN DNN of the extended LADN information as the LADN information and include the LADN information in the LADN information IE of the CONFIGURATION UPDATE COMMAND message. NOTE 15A: If the LADN service area is configured per DNN and S-NSSAI, in order to serve the UEs that do not support LADN per DNN and S-NSSAI, it is recommended that the LADN DNN is only served by a single S-NSSAI. NOTE 15B: In case of the UE is subscribed to the LADN DNN for multiple S-NSSAIs, the AMF can treat this as no extended LADN information is available. If the UE does not support LADN per DNN and S-NSSAI and the AMF has neither the LADN information nor the extended LADN information, the AMF shall not provide any LADN information to the UE. If the AMF does not include the LADN information IE or Extended LADN information IE in the Registration accept type 6 IE container IE in the REGISTRATION ACCEPT message during registration procedure for mobility and periodic registration update, the UE shall delete its old LADN information or old extended LADN information respectively. If the PDU session status IE is included in the REGISTRATION ACCEPT message: a) for single access PDU sessions, the UE shall perform a local release of all those PDU sessions associated with the access type the REGISTRATION ACCEPT message is sent over which are not in 5GSM state PDU SESSION INACTIVE or PDU SESSION ACTIVE PENDING on the UE side, but are indicated by the AMF as being in 5GSM state PDU SESSION INACTIVE. If a locally released PDU session is associated with one or more multicast MBS sessions, the UE shall locally leave the associated multicast MBS sessions; and b) for MA PDU sessions, for all those PDU sessions which are not in 5GSM state PDU SESSION INACTIVE and have the corresponding user plane resources being established or established in the UE on the access the REGISTRATION ACCEPT message is sent over, but are indicated by the AMF as no user plane resources are being established or established: 1) for MA PDU sessions having the corresponding user plane resources being established or established only on the access the REGISTRATION ACCEPT message is sent over, the UE shall perform a local release of those MA PDU sessions. If a locally released MA PDU session is associated with one or more multicast MBS sessions, the UE shall locally leave the associated multicast MBS sessions; and 2) for MA PDU sessions having user plane resources being established or established on both accesses, the UE shall perform a local release on the user plane resources on the access the REGISTRATION ACCEPT message is sent over. If the user plane resources over 3GPP access are released and the MA PDU session is associated with one or more multicast MBS sessions, the UE shall locally leave the associated multicast MBS sessions. If: a) the UE included a PDU session status IE in the REGISTRATION REQUEST message; b) the UE is operating in the single-registration mode; c) the UE is performing inter-system change from S1 mode to N1 mode in 5GMM-IDLE mode; and d) the UE has received the IWK N26 bit set to "interworking without N26 interface supported"; the UE shall ignore the PDU session status IE if received in the REGISTRATION ACCEPT message. If the EPS bearer context status IE is included in the REGISTRATION ACCEPT message, the UE shall locally delete all those QoS flow descriptions and all associated QoS rules, if any, which are associated with inactive EPS bearer contexts as indicated by the AMF in the EPS bearer context status IE. If the UE included S1 mode supported indication in the REGISTRATION REQUEST message, the AMF supporting inter-system change with EPS shall set the IWK N26 bit to either: a) "interworking without N26 interface not supported" if the AMF supports N26 interface; or b) "interworking without N26 interface supported" if the AMF does not support N26 interface in the 5GS network feature support IE in the REGISTRATION ACCEPT message. The UE supporting S1 mode shall operate in the mode for inter-system interworking with EPS as follows: a) if the IWK N26 bit in the 5GS network feature support IE is set to "interworking without N26 interface not supported", the UE shall operate in single-registration mode; b) if the IWK N26 bit in the 5GS network feature support IE is set to "interworking without N26 interface supported" and the UE supports dual-registration mode, the UE may operate in dual-registration mode; or NOTE 16: The registration mode used by the UE is implementation dependent. c) if the IWK N26 bit in the 5GS network feature support IE is set to "interworking without N26 interface supported" and the UE only supports single-registration mode, the UE shall operate in single-registration mode. The UE shall store the received interworking without N26 interface indicator for inter-system change with EPS as specified in annex C.1 and treat it as valid in the entire PLMN and its equivalent PLMN(s). The network informs the UE about the support of specific features, such as IMS voice over PS session, location services (5G-LCS), emergency services, emergency services fallback, ATSSS and non-3GPP access path switching, in the 5GS network feature support information element. In a UE with IMS voice over PS session capability, the IMS voice over PS session indicator, Emergency services support indicator and Emergency services fallback indicator shall be provided to the upper layers. The upper layers take the IMS voice over PS session indicator into account when selecting the access domain for voice sessions or calls. When initiating an emergency call, the upper layers take the IMS voice over PS session indicator, Emergency services support indicator and Emergency services fallback indicator into account for the access domain selection. When the UE determines via the IMS voice over PS session indicator that the network does not support IMS voice over PS sessions in N1 mode, then the UE shall not perform a local release of any persistent PDU session if the AMF does not indicate that the PDU session is in 5GSM state PDU SESSION INACTIVE via the PDU session status IE. When the UE determines via the Emergency services support indicator that the network does not support emergency services in N1 mode, then the UE shall not perform a local release of any emergency PDU session if user-plane resources associated with that emergency PDU session are established if the AMF does not indicate that the PDU session is in 5GSM state PDU SESSION INACTIVE via the PDU session status IE. In a UE with LCS capability, location services indicators (5G-LCS) shall be provided to the upper layers. In a UE with the capability for ATSSS, the network support for ATSSS shall be provided to the upper layers. If the UE receives the 5GS network feature support IE with the ATSSS support indicator set to "ATSSS not supported", the UE shall perform a local release of the MA PDU session, if any. If a locally released MA PDU session is associated with one or more multicast MBS sessions, the UE shall locally leave the associated multicast MBS sessions. In a UE that supports non-3GPP access path switching, the network support for non-3GPP access path switching shall be provided to the upper layers. If the UE receives the 5GS network feature support IE with the non-3GPP access path switching bit set to "non-3GPP access path switching not supported", the UE shall not perform the registration procedure for mobility registration update for non-3GPP access path switching. NOTE 16A: If the UE is registered to different PLMNs over 3GPP and non-3GPP accesses, the UE uses the capability received over non-3GPP access to determine whether to initiate the registration procedure for mobility registration update for non-3GPP path switching. The AMF shall set the EMF bit in the 5GS network feature support IE to: a) "Emergency services fallback supported in NR connected to 5GCN and E-UTRA connected to 5GCN" if the network supports the emergency services fallback procedure when the UE is in an NR cell connected to 5GCN or an E-UTRA cell connected to 5GCN; b) "Emergency services fallback supported in NR connected to 5GCN only" if the network supports the emergency services fallback procedure when the UE is in an NR cell connected to 5GCN and does not support the emergency services fallback procedure when the UE is in an E-UTRA cell connected to 5GCN; c) "Emergency services fallback supported in E-UTRA connected to 5GCN only" if the network supports the emergency services fallback procedure when the UE is in an E-UTRA cell connected to 5GCN and does not support the emergency services fallback procedure when the UE is in an NR cell connected to 5GCN; or d) "Emergency services fallback not supported" if network does not support the emergency services fallback procedure when the UE is in any cell connected to 5GCN. NOTE 17: If the emergency services are supported in neither the EPS nor the 5GS homogeneously, based onoperator policy, the AMF will set the EMF bit in the 5GS network feature support IE to "Emergency services fallback not supported". NOTE 18: Even though the AMF's support of emergency services fallback is indicated per RAT, the UE's support of emergency services fallback is not per RAT, i.e. the UE's support of emergency services fallback is the same for both NR connected to 5GCN and E-UTRA connected to 5GCN. If the UE indicates support for restriction on use of enhanced coverage in the REGISTRATION REQUEST message and: a) in WB-N1 mode, the AMF decides to restrict the use of CE mode B for the UE, then the AMF shall set the RestrictEC bit to "CE mode B is restricted"; b) in WB-N1 mode, the AMF decides to restrict the use of both CE mode A and CE mode B for the UE, then the AMF shall set the RestrictEC bit to " Both CE mode A and CE mode B are restricted"; or c) in NB-N1 mode, the AMF decides to restrict the use of enhanced coverage for the UE, then the AMF shall set the RestrictEC bit to "Use of enhanced coverage is restricted", in the 5GS network feature support IE in the REGISTRATION ACCEPT message. Access identity 1 is only applicable while the UE is in N1 mode. Access identity 2 is only applicable while the UE is in N1 mode. When the UE is registered to the same PLMN or SNPN over 3GPP and non-3GPP access, the UE and the AMF maintain one MPS indicator and one MCS indicator that are common to both 3GPP and non-3GPP access. When the UE is registered to different PLMNs or SNPNs over 3GPP access and non-3GPP access, the UE maintains two MPS indicators and two MCS indicators separately for different accesses i.e., an MPS indicator and an MCS indicator for the 3GPP access and another MPS indicator and an MCS indicator for the non-3GPP access. For both 3GPP and non-3GPP access, the access identity is determined according to subclause 4.5.2: - if the UE is not operating in SNPN access operation mode: a) the network informs the UE that the use of access identity 1 is valid in the RPLMN or equivalent PLMN by setting the MPS indicator bit of the 5GS network feature support IE to "Access identity 1 valid", in the REGISTRATION ACCEPT message. Based on operator policy, the AMF sets the MPS indicator bit in the REGISTRATION ACCEPT message based on the MPS priority information in the user's subscription context obtained from the UDM; b) upon receiving a REGISTRATION ACCEPT message with the MPS indicator bit set to "Access identity 1 valid": - via 3GPP access; or - via non-3GPP access if the UE is registered to the same PLMN over 3GPP access and non-3GPP access; the UE shall act as a UE with access identity 1 configured for MPS, as described in subclause 4.5.2, in all NG-RAN of the registered PLMN and its equivalent PLMNs. The MPS indicator bit in the 5GS network feature support IE provided in the REGISTRATION ACCEPT message is valid in all NG-RAN of the registered PLMN and its equivalent PLMNs until the UE receives a REGISTRATION ACCEPT message or a CONFIGURATION UPDATE COMMAND message with the MPS indicator bit set to "Access identity 1 not valid": - via 3GPP access; or - via non-3GPP access if the UE is registered to the same PLMN over 3GPP access and non-3GPP access; or until the UE selects a non-equivalent PLMN over 3GPP access; b1) upon receiving a REGISTRATION ACCEPT message with the MPS indicator bit set to "Access identity 1 valid": - via non-3GPP access; or - via 3GPP access if the UE is registered to the same PLMN over 3GPP access and non-3GPP access; the UE shall act as a UE with access identity 1 configured for MPS, as described in subclause 4.5.2, in non-3GPP access of the registered PLMN and its equivalent PLMNs. The MPS indicator bit in the 5GS network feature support IE provided in the REGISTRATION ACCEPT message is valid in non-3GPP access of the registered PLMN and its equivalent PLMNs until the UE receives a REGISTRATION ACCEPT message or a CONFIGURATION UPDATE COMMAND message with the MPS indicator bit set to "Access identity 1 not valid": - via non-3GPP access; or - via 3GPP access if the UE is registered to the same PLMN over 3GPP access and non-3GPP access; or until the UE selects a non-equivalent PLMN over non-3GPP access; c) during ongoing active PDU sessions that were set up relying on the MPS indicator bit being set to "Access identity 1 valid", if the network indicates in a registration update that the MPS indicator bit is reset to "Access identity 1 not valid", then the UE shall no longer act as a UE with access identity 1 configured for MPS as described in subclause 4.5.2 unless the USIM contains a valid configuration for access identity 1 in RPLMN or equivalent PLMN. In the UE, the ongoing active PDU sessions are not affected by the change of the MPS indicator bit; d) the network informs the UE that the use of access identity 2 is valid in the RPLMN or equivalent PLMN by setting the MCS indicator bit of the 5GS network feature support IE to "Access identity 2 valid", in the REGISTRATION ACCEPT message. Based on operator policy, the AMF sets the MCS indicator bit in the REGISTRATION ACCEPT message based on the MCS priority information in the user's subscription context obtained from the UDM; e) upon receiving a REGISTRATION ACCEPT message with the MCS indicator bit set to "Access identity 2 valid": - via 3GPP access; or - via non-3GPP access if the UE is registered to the same PLMN over 3GPP access and non-3GPP access; the UE shall act as a UE with access identity 2 configured for MCS, as described in subclause 4.5.2, in all NG-RAN of the registered PLMN and its equivalent PLMNs. The MCS indicator bit in the 5GS network feature support IE provided in the REGISTRATION ACCEPT message is valid in all NG-RAN of the registered PLMN and its equivalent PLMNs until the UE receives a REGISTRATION ACCEPT message or a CONFIGURATION UPDATE COMMAND message with the MCS indicator bit set to "Access identity 2 not valid": - via 3GPP access; or - via non-3GPP access if the UE is registered to the same PLMN over 3GPP access and non-3GPP access; or until the UE selects a non-equivalent PLMN over 3GPP access; e1) upon receiving a REGISTRATION ACCEPT message with the MCS indicator bit set to "Access identity 2 valid": - via non-3GPP access; or - via 3GPP access if the UE is registered to the same PLMN over 3GPP access and non-3GPP access; the UE shall act as a UE with access identity 2 configured for MCS, as described in subclause 4.5.2, in non-3GPP access of the registered PLMN and its equivalent PLMNs. The MCS indicator bit in the 5GS network feature support IE provided in the REGISTRATION ACCEPT message is valid in non-3GPP access of the registered PLMN and its equivalent PLMNs until the UE receives a REGISTRATION ACCEPT message or a CONFIGURATION UPDATE COMMAND message with the MCS indicator bit set to "Access identity 2 not valid": - via non-3GPP access; or - via 3GPP access if the UE is registered to the same PLMN over 3GPP access and non-3GPP access; or until the UE selects a non-equivalent PLMN over non-3GPP access; and f) during ongoing active PDU sessions that were set up relying on the MCS indicator bit being set to "Access identity 2 valid", if the network indicates in a registration update that the MCS indicator bit is reset to "Access identity 2 not valid", then the UE shall no longer act as a UE with access identity 2 configured for MCS as described in subclause 4.5.2 unless the USIM contains a valid configuration for access identity 2 in RPLMN or equivalent PLMN. In the UE, the ongoing active PDU sessions are not affected by the change of the MCS indicator bit; or - if the UE is operating in SNPN access operation mode: a) the network informs the UE that the use of access identity 1 is valid in the RSNPN or equivalent SNPN by setting the MPS indicator bit of the 5GS network feature support IE to "Access identity 1 valid", in the REGISTRATION ACCEPT message. Based on operator policy, the AMF sets the MPS indicator bit in the REGISTRATION ACCEPT message based on the MPS priority information in the user's subscription context obtained from the UDM; b) upon receiving a REGISTRATION ACCEPT message with the MPS indicator bit set to "Access identity 1 valid": - via 3GPP access; or - via non-3GPP access if the UE is registered to the same SNPN over 3GPP access and non-3GPP access; the UE shall act as a UE with access identity 1 configured for MPS, as described in subclause 4.5.2A, in all NG-RAN of the registered SNPN and its equivalent SNPNs. The MPS indicator bit in the 5GS network feature support IE provided in the REGISTRATION ACCEPT message is valid in all NG-RAN of the registered SNPN and its equivalent SNPNs until the UE receives a REGISTRATION ACCEPT message or a CONFIGURATION UPDATE COMMAND message with the MPS indicator bit set to "Access identity 1 not valid": - via 3GPP access; or - via non-3GPP access if the UE is registered to the same SNPN over 3GPP access and non-3GPP access; or until the UE selects a non-equivalent SNPN over 3GPP access; b1) upon receiving a REGISTRATION ACCEPT message with the MPS indicator bit set to "Access identity 1 valid": - via non-3GPP access; or - via 3GPP access if the UE is registered to the same SNPN over 3GPP access and non-3GPP access; the UE shall act as a UE with access identity 1 configured for MPS, as described in subclause 4.5.2A, in non-3GPP access of the registered SNPN and its equivalent SNPNs. The MPS indicator bit in the 5GS network feature support IE provided in the REGISTRATION ACCEPT message is valid in non-3GPP access of the registered SNPN and its equivalent SNPNs until the UE receives a REGISTRATION ACCEPT message or a CONFIGURATION UPDATE COMMAND message with the MPS indicator bit set to "Access identity 1 not valid": - via non-3GPP access; or - via 3GPP access if the UE is registered to the same SNPN over 3GPP access and non-3GPP access; or until the UE selects a non-equivalent SNPN over non-3GPP access; c) during ongoing active PDU sessions that were set up relying on the MPS indicator bit being set to "Access identity 1 valid", if the network indicates in a registration update that the MPS indicator bit is reset to "Access identity 1 not valid", then the UE shall no longer act as a UE with access identity 1 configured for MPS as described in subclause 4.5.2A unless the unified access control configuration in the "list of subscriber data" stored in the ME (see 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]) indicates the UE is configured for access identity 1 in the RSNPN or equivalent SNPN. In the UE, the ongoing active PDU sessions are not affected by the change of the MPS indicator bit; d) the network informs the UE that the use of access identity 2 is valid in the RSNPN or equivalent SNPN by setting the MCS indicator bit of the 5GS network feature support IE to "Access identity 2 valid", in the REGISTRATION ACCEPT message. Based on operator policy, the AMF sets the MCS indicator bit in the REGISTRATION ACCEPT message based on the MCS priority information in the user's subscription context obtained from the UDM; e) upon receiving a REGISTRATION ACCEPT message with the MCS indicator bit set to "Access identity 2 valid": - via 3GPP access; or - via non-3GPP access if the UE is registered to the same SNPN over 3GPP access and non-3GPP access; the UE shall act as a UE with access identity 2 configured for MCS, as described in subclause 4.5.2A, in all NG-RAN of the registered SNPN and its equivalent SNPNs. The MCS indicator bit in the 5GS network feature support IE provided in the REGISTRATION ACCEPT message is valid in all NG-RAN of the registered SNPN and its equivalent SNPNs until the UE receives a REGISTRATION ACCEPT message or a CONFIGURATION UPDATE COMMAND message with the MCS indicator bit set to "Access identity 2 not valid": - via 3GPP access; or - via non-3GPP access if the UE is registered to the same SNPN over 3GPP access and non-3GPP access; or until the UE selects a non-equivalent SNPN; e1) upon receiving a REGISTRATION ACCEPT message with the MCS indicator bit set to "Access identity 2 valid": - via non-3GPP access; or - via 3GPP access if the UE is registered to the same SNPN over 3GPP access and non-3GPP access; the UE shall act as a UE with access identity 2 configured for MCS, as described in subclause 4.5.2A, in non-3GPP access of the registered SNPN and its equivalent SNPNs. The MCS indicator bit in the 5GS network feature support IE provided in the REGISTRATION ACCEPT message is valid in non-3GPP access of the registered SNPN and its equivalent SNPNs until the UE receives a REGISTRATION ACCEPT message or a CONFIGURATION UPDATE COMMAND message with the MCS indicator bit set to "Access identity 2 not valid": - via non-3GPP access; or - via 3GPP access if the UE is registered to the same SNPN over 3GPP access and non-3GPP access; or until the UE selects a non-equivalent SNPN over non-3GPP access; and f) during ongoing active PDU sessions that were set up relying on the MCS indicator bit being set to "Access identity 2 valid", if the network indicates in a registration update that the MCS indicator bit is reset to "Access identity 2 not valid", then the UE shall no longer act as a UE with access identity 2 configured for MCS as described in subclause 4.5.2A unless the unified access control configuration in the "list of subscriber data" stored in the ME (see 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]) indicates the UE is configured for access identity 2 in the RSNPN or equivalent SNPN. In the UE, the ongoing active PDU sessions are not affected by the change of the MCS indicator bit. If the UE has set the Follow-on request indicator to "Follow-on request pending" in the REGISTRATION REQUEST message, or the network has downlink signalling pending, the AMF shall not immediately release the NAS signalling connection after the completion of the registration procedure. If the UE is authorized to use V2X communication over PC5 reference point based on: a) at least one of the following bits in the 5GMM capability IE of the REGISTRATION REQUEST message set by the UE, or already stored in the 5GMM context in the AMF during the previous registration procedure as follows: 1) the V2XCEPC5 bit to "V2X communication over E-UTRA-PC5 supported"; or 2) the V2XCNPC5 bit to "V2X communication over NR-PC5 supported"; and b) the user's subscription context obtained from the UDM as defined in 3GPP TS 23.287[ Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services ] [6C]; the AMF should not immediately release the NAS signalling connection after the completion of the registration procedure. If the UE is authorized to use A2X communication over PC5 reference point based on: a) at least one of the following bits in the 5GMM capability IE of the REGISTRATION REQUEST message set by the UE, or already stored in the 5GMM context in the AMF during the previous registration procedure as follows: 1) the A2XEPC5 bit to "A2X over E-UTRA-PC5 supported"; or 2) the A2XNPC5 bit to "A2X over NR-PC5 supported"; and b) the user's subscription context obtained from the UDM as defined in 3GPP TS 23.256[ Support of Uncrewed Aerial Systems (UAS) connectivity, identification and tracking; Stage 2 ] [6C]; the AMF should not immediately release the NAS signalling connection after the completion of the registration procedure. If the UE is authorized to use 5G ProSe services based on: a) at least one of the following bits in the 5GMM capability IE of the REGISTRATION REQUEST message set by the UE, or already stored in the 5GMM context in the AMF during the previous registration procedure as follows: 1) the 5G ProSe direct discovery bit to "5G ProSe direct discovery supported"; or 2) the 5G ProSe direct communication bit to "5G ProSe direct communication supported"; and b) the user's subscription context obtained from the UDM as defined in 3GPP TS 23.304[ Proximity based Services (ProSe) in the 5G System (5GS) ] [6E]; the AMF should not immediately release the NAS signalling connection after the completion of the registration procedure. If the UE indicates support of ranging and sidelink positioning in the REGISTRATION REQUEST message and the network supports ranging and sidelink positioning, the AMF shall set the ranging and sidelink positioning supported bit to "Ranging and sidelink positioning supported" in the 5GS network feature support IE of the REGISTRATION ACCEPT message. If the UE has included the Non-3GPP path switching information IE in the REGISTRATION REQUEST message with the NSONR bit set to "non-3GPP path switching while using old non-3GPP resources requested" and the AMF supports non-3GPP path switching while using old non-3GPP resources , the AMF shall not release the user plane resources of the old non-3GPP access of the PDU sessions supporting non-3GPP access path switching and whose PDU session IDs are included in the Uplink data status IE of the REGISTRATION REQUEST message until the user plane resources of the new non-3GPP access are established. Otherwise, the AMF shall release the user plane resources of the old non-3GPP access before proceeding with the registration procedure. If the UE has triggered the registration procedure for mobility registration update for non-3GPP access path switching from the old non-3GPP access to the new non-3GPP access and the UE receives the REGISTRATION ACCEPT message over the new non-3GPP access, the UE shall consider itself as de-registered for 5GS services over the old non-3GPP access. If the Requested DRX parameters IE was included in the REGISTRATION REQUEST message, the AMF shall include the Negotiated DRX parameters IE in the REGISTRATION ACCEPT message and replace any stored Negotiated DRX parameter and use it for the downlink transfer of signalling and user data. The AMF may set the Negotiated DRX parameters IE based on the received Requested DRX parameters IE and operator policy if available. If the Requested NB-N1 mode DRX parameters IE was included in the REGISTRATION REQUEST message and replace any stored Negotiated NB-N1 mode DRX parameters and use it for the downlink transfer of signalling and user data in NB-N1 mode, the AMF shall include the Negotiated NB-N1 mode DRX parameters IE in the REGISTRATION ACCEPT message. The AMF may set the Negotiated NB-N1 mode DRX parameters IE based on the received Requested NB-N1 mode DRX parameters IE and operator policy if available. The AMF shall include the Negotiated extended DRX parameters IE in the REGISTRATION ACCEPT message only if the Requested extended DRX parameters IE was included in the REGISTRATION REQUEST message, and the AMF supports and accepts the use of eDRX. The AMF may set the Negotiated extended DRX parameters IE based on the received Requested extended DRX parameters IE, operator policy, information from NG-RAN and the user's subscription context obtained from the UDM if available. If the network cannot derive the UE's identity from the 5G-GUTI because of e.g. no matching identity/context in the network, failure to validate the UE's identity due to integrity check failure of the received message, the AMF may operate as described in subclause 5.5.1.2.4 and include a PDU session status IE indicating all PDU sessions are in 5GSM state PDU SESSION INACTIVE in the AMF. If the UE included in the REGISTRATION REQUEST message the UE status IE with the EMM registration status set to "UE is in EMM-REGISTERED state" and the AMF does not support N26 interface, the AMF shall operate as described in subclause 5.5.1.2.4. If the UE has indicated support for service gap control in the REGISTRATION REQUEST message, a service gap time value is available in the 5GMM context, the AMF may include the T3447 value IE set to the service gap time value in the REGISTRATION ACCEPT message. If the UE requests ciphering keys for ciphered broadcast assistance data in the REGISTRATION REQUEST message and the AMF has valid ciphering key data applicable to the UE's subscription and current tracking area, then the AMF shall include the ciphering key data in the Ciphering key data IE of the REGISTRATION ACCEPT message. If the UE supports WUS assistance information and the AMF supports and accepts the use of WUS assistance information for the UE, then the AMF shall determine the negotiated UE paging probability information for the UE, store it in the 5GMM context of the UE, and if the UE does not have an active emergency PDU session, the AMF shall include it in the Negotiated WUS assistance information IE in the REGISTRATION ACCEPT message. The AMF may consider the UE paging probability information received in the Requested WUS assistance information IE when determining the negotiated UE paging probability information for the UE. NOTE 19: Besides the UE paging probability information requested by the UE, the AMF can take local configuration or previous statistical information for the UE into account when determining the negotiated UE paging probability information for the UE. If the UE sets the NR-PSSI bit to "NR paging subgrouping supported" in the 5GMM capability IE in the REGISTRATION REQUEST message and the AMF supports and accepts the use of PEIPS assistance information for the UE, then the AMF shall determine the Paging subgroup ID for the UE, store it in the 5GMM context of the UE, and include it in the Negotiated PEIPS assistance information IE in the REGISTRATION ACCEPT message or in the Updated PEIPS assistance information IE in the CONFIGURATION UPDATE COMMAND message as part of the registration procedure. The AMF may consider the UE paging probability information received in the Requested PEIPS assistance information IE when determining the Paging subgroup ID for the UE. NOTE 20: Besides the UE paging probability information when provided by the UE, the AMF can also take local configuration, whether the UE is likely to receive IMS voice over PS session calls, UE mobility pattern or previous statistical information for the UE or information provided by the NG-RAN into account when determining the Paging subgroup ID for the UE. If the UE set the UN-PER bit to "unavailability period supported" in the 5GMM capability IE in the REGISTRATION REQUEST message and the AMF supports and accepts the use of unavailability period for the UE, then the AMF shall set the UN-PER bit to "unavailability period supported" in the 5GS network feature support IE in the REGISTRATION ACCEPT message. If the UE provided the Unavailability information IE in the REGISTRATION REQUEST message, then the AMF shall: a) determine the Unavailability period duration value as: - A value that was provided by the UE; or - A value that was determined by the AMF based on satellite coverage availability information; and the AMF shall store the Start of unavailability period value. When the time of the Start of unavailability period arrives, the AMF shall consider the UE as unreachable until the UE registers for normal service again without providing an unavailability information and the Start of unavailability period; b) store the received unavailability period duration, if any; and c) release the signalling connection immediately after the completion of the registration procedure. If the UE set the Unavailability type to "unavailability due to discontinuous coverage" in the Unavailability information IE and the UE provides the Unavailability information IE in the REGISTRATION REQUEST message then: a) if the AMF is able to determine a UE out-of-coverage period based on satellite coverage availability information and the value of the Unavailability information IE in the REGISTRATION REQUEST message if available, the AMF shall store the determined unavailability period duration and provide the expected unavailability duration to the UE by including the Unavailability period duration IE in the REGISTRATION ACCEPT message; and b) the AMF shall determine the Unavailability period duration value as: - A value that was provided by the UE; or - A value that was determined by the AMF based on satellite coverage availability information; and the AMF shall store the Start of unavailability period value. When the Start of unavailability period starts, the AMF shall consider the UE as unreachable until the UE registers for normal service again without providing the CLI bit set to "Coverage loss due to discontinuous coverage" in the 5GS update type IE. The AMF may determine the periodic registration update timer value based on the stored value of the received unavailability period duration, or based on a network determined unavailability period duration when the unavailability period duration is not provided by the UE. If the UE does not provide the Unavailability information IE in the REGISTRATION REQUEST message, the AMF shall delete any stored value of the Unavailability information IE if exists. If the UE receives the Unavailability configuration IE with a value of the unavailability period duration in the REGISTRATION ACCEPT message, then the UE may either: a) delete a UE determined value and start using the received value; or b) discard the received value and use a UE determined value. If due to regional subscription restrictions or access restrictions the UE is not allowed to access the TA or due to CAG restrictions the UE is not allowed to access the cell, but the UE has an emergency PDU session established, the AMF may accept the REGISTRATION REQUEST message and indicate to the SMF to perform a local release of all non-emergency PDU sessions (associated with 3GPP access if it is due to CAG restrictions) and informs the UE via the PDU session status IE in the REGISTRATION ACCEPT message. The AMF shall not indicate to the SMF to release the emergency PDU session. If the AMF indicated to the SMF to perform a local release of all non-emergency PDU sessions (associated with 3GPP access if it is due to CAG restrictions), the network shall behave as if the UE is registered for emergency services and shall set the emergency registered bit of the 5GS registration result IE to "Registered for emergency services" in the REGISTRATION ACCEPT message. If the REGISTRATION ACCEPT message includes the PDU session reactivation result error cause IE with the 5GMM cause set to #28 "Restricted service area", the UE shall enter the state 5GMM-REGISTERED.NON-ALLOWED-SERVICE and behave as specified in subclause 5.3.5. If the REGISTRATION ACCEPT message includes the SOR transparent container IE and: a) the SOR transparent container IE does not successfully pass the integrity check (see 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]); and b) if the UE attempts obtaining service on another PLMNs or SNPNs as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] annex C; then the UE shall release locally the established NAS signalling connection after sending a REGISTRATION COMPLETE message. If the REGISTRATION ACCEPT message includes the SOR transparent container IE and the SOR transparent container IE successfully passes the integrity check (see 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]), the ME shall store the received SOR counter as specified in annex C and proceed as follows: a) the UE shall proceed with the behaviour as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] annex C; and b) if the registration procedure is performed over 3GPP access and the UE attempts obtaining service on another PLMNs or SNPNs as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] annex C then the UE may release locally the established NAS signalling connection after sending a REGISTRATION COMPLETE message. Otherwise the UE shall send a REGISTRATION COMPLETE message and not release the current N1 NAS signalling connection locally. If an acknowledgement is requested in the SOR transparent container IE of the REGISTRATION ACCEPT message, the UE acknowledgement is included in the SOR transparent container IE of the REGISTRATION COMPLETE message. In the SOR transparent container IE carrying the acknowledgement, the UE shall set the ME support of SOR-CMCI indicator to "SOR-CMCI supported by the ME". Additionally, if the UE supports access to an SNPN using credentials from a credentials holder and the UE is not operating in SNPN access operation mode, the UE may set the ME support of SOR-SNPN-SI indicator to "SOR-SNPN-SI supported by the ME". Additionally, if the UE supports access to an SNPN providing access for localized services in SNPN, the UE shall set the ME support of SOR-SNPN-SI-LS indicator to "SOR-SNPN-SI-LS supported by the ME". If the SOR transparent container IE successfully passes the integrity check (see 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]), and: a) the SOR transparent container IE indicates a list of preferred PLMN/access technology combinations is provided and the list type indicates "PLMN ID and access technology list", then the ME shall replace the highest priority entries in the "Operator Controlled PLMN Selector with Access Technology" list stored in the ME and shall proceed with the behaviour as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] annex C. If the SOR-CMCI is present and the Store SOR-CMCI in ME indicator is set to "Store SOR-CMCI in ME" then the UE shall store or delete the SOR-CMCI in the non-volatile memory of the ME as described in annex C.1; b) the list type indicates "secured packet", then the ME shall behave as if a SMS is received with protocol identifier set to SIM data download, data coding scheme set to class 2 message and SMS payload as secured packet contents of SOR transparent container IE. The SMS payload is forwarded to UICC as specified in 3GPP TS 23.040[ Technical realization of the Short Message Service (SMS) ] [4A]; or c) the SOR transparent container IE indicates "HPLMN indication that 'no change of the "Operator Controlled PLMN Selector with Access Technology" list stored in the UE is needed and thus no list of preferred PLMN/access technology combinations is provided'", the UE operates in SNPN access operation mode and the SOR transparent container IE includes SOR-SNPN-SI, the ME shall replace SOR-SNPN-SI of the selected entry of the "list of subscriber data" or associated with the selected PLMN subscription, as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] with the received SOR-SNPN-SI. If the SOR-CMCI is present and the Store SOR-CMCI in ME indicator is set to "Store SOR-CMCI in ME" then the UE shall store or delete the SOR-CMCI in the non-volatile memory of the ME as described in annex C.1; and the UE shall proceed with the behaviour as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] annex C. If the SOR transparent container IE does not pass the integrity check successfully, then the UE shall discard the content of the SOR transparent container IE. If required by operator policy, the AMF shall include the NSSAI inclusion mode IE in the REGISTRATION ACCEPT message (see table 4.6.2.3.1 of subclause 4.6.2.3). Upon receipt of the REGISTRATION ACCEPT message: a) if the message includes the NSSAI inclusion mode IE, the UE shall operate in the NSSAI inclusion mode indicated in the NSSAI inclusion mode IE over the current access within the current PLMN and its equivalent PLMN(s), if any, or the current SNPN, in the current registration area; or b) otherwise: 1) if the UE has NSSAI inclusion mode for the current PLMN or SNPN and access type stored in the UE, the UE shall operate in the stored NSSAI inclusion mode; 2) if the UE does not have NSSAI inclusion mode for the current PLMN or SNPN and the access type stored in the UE and if the UE is performing the registration procedure over: i) 3GPP access, the UE shall operate in NSSAI inclusion mode D in the current PLMN or SNPN and the current access type; ii) untrusted non-3GPP access, the UE shall operate in NSSAI inclusion mode C in the current PLMN and the current access type; or iii) trusted non-3GPP access, the UE shall operate in NSSAI inclusion mode D in the current PLMN and the current access type; or 3) if the 5G-RG does not have NSSAI inclusion mode for the current PLMN and wireline access stored in the 5G-RG, and the 5G-RG is performing the registration procedure over wireline access, the 5G-RG shall operate in NSSAI inclusion mode B in the current PLMN and the current access type. The AMF may include operator-defined access category definitions in the REGISTRATION ACCEPT message. If there is a running T3447 timer in the AMF and the Uplink data status IE is included or the Follow-on request indicator is set to "Follow-on request pending" in the REGISTRATION REQUEST message, the AMF shall ignore the Uplink data status IE or that the Follow-on request indicator is set to "Follow-on request pending" and proceed as if the Uplink data status IE was not received or the Follow-on request indicator was not set to "Follow-on request pending" except for the following case: - the PDU session indicated by the Uplink data status IE is emergency PDU session; - the UE is configured for high priority access in selected PLMN; - the REGISTRATION REQUEST message is as a paging response; or - the UE is establishing an emergency PDU session or performing emergency services fallback. If the UE receives Operator-defined access category definitions IE in the REGISTRATION ACCEPT message and the Operator-defined access category definitions IE contains one or more operator-defined access category definitions, the UE shall delete any operator-defined access category definitions stored for the RPLMN and shall store the received operator-defined access category definitions for the RPLMN. If the UE receives the Operator-defined access category definitions IE in the REGISTRATION ACCEPT message and the Operator-defined access category definitions IE contains no operator-defined access category definitions, the UE shall delete any operator-defined access category definitions stored for the RPLMN. If the REGISTRATION ACCEPT message does not contain the Operator-defined access category definitions IE, the UE shall not delete the operator-defined access category definitions stored for the RPLMN. If the UE has indicated support for service gap control in the REGISTRATION REQUEST message and: - the REGISTRATION ACCEPT message contains the T3447 value IE, then the UE shall store the new T3447 value, erase any previous stored T3447 value if exists and use the new T3447 value with the timer T3447 next time it is started; or - the REGISTRATION ACCEPT message does not contain the T3447 value IE, then the UE shall erase any previous stored T3447 value if exists and stop the timer T3447 if running. If the REGISTRATION ACCEPT message contains the Truncated 5G-S-TMSI configuration IE, then the UE shall store the included truncated 5G-S-TMSI configuration and return a REGISTRATION COMPLETE message to the AMF to acknowledge reception of the truncated 5G-S-TMSI configuration. NOTE 21: The UE provides the truncated 5G-S-TMSI configuration to the lower layers. If the UE is not in NB-N1 mode, the UE has set the RACS bit to "RACS supported" in the 5GMM Capability IE of the REGISTRATION REQUEST message, and the REGISTRATION ACCEPT message includes: a) a UE radio capability ID deletion indication IE set to "Network-assigned UE radio capability IDs deletion requested", the UE shall delete any network-assigned UE radio capability IDs associated with the RPLMN or RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, the selected entry of the "list of subscriber data" or the selected PLMN subscription stored at the UE, then the UE shall initiate a registration procedure for mobility and periodic registration update as specified in subclause 5.5.1.3.2 over the existing N1 NAS signalling connection; or b) a UE radio capability ID IE, the UE shall store the UE radio capability ID as specified in annex C. If the registration procedure for mobility and periodic registration update was initiated and there is a request from the upper layers to perform "emergency services fallback" pending, the UE shall restart the service request procedure after the successful completion of the mobility and periodic registration update. When AMF re-allocation occurs in the registration procedure for mobility and periodic registration update, if the new AMF receives in the 5GMM context of the UE the indication that the UE is registered for onboarding services in SNPN, the new AMF may start an implementation specific timer for onboarding services when the registration procedure for mobility and periodic registration update is successfully completed. If the UE has included the service-level device ID set to the CAA-level UAV ID in the Service-level-AA container IE of the REGISTRATION REQUEST message and the REGISTRATION ACCEPT message contains the service-level-AA pending indication in the Service-level-AA container IE, the UE shall return a REGISTRATION COMPLETE message to the AMF to acknowledge reception of the service-level-AA pending indication, and the UE shall not attempt to perform another registration procedure for UAS services until the UUAA-MM procedure is completed, or to establish a PDU session for USS communication or a PDU session for C2 communication until the UUAA-MM procedure is completed successfully. If the UE has included the service-level device ID set to the CAA-level UAV ID in the Service-level-AA container IE of the REGISTRATION REQUEST message and the REGISTRATION ACCEPT message does not contain the service-level-AA pending indication in the Service-level-AA container IE, the UE shall consider the UUAA-MM procedure is not triggered. If the UE is registered for onboarding services in SNPN or the network determines that the UE's subscription only allows for configuration of SNPN subscription parameters in PLMN via the user plane, the AMF may start an implementation specific timer for onboarding services, if not running already, when the network considers that the UE is in 5GMM-REGISTERED (i.e. the network receives the REGISTRATION COMPLETE message from UE). NOTE 22: If the AMF considers that the UE is in 5GMM-IDLE, when the implementation specific timer for onboarding services expires and the network considers that the UE is still in state 5GMM-REGISTERED, the AMF can locally de-register the UE; or if the UE is in 5GMM-CONNECTED, the AMF can initiate the network-initiated de-registration procedure (see subclause 5.5.2.3). NOTE 23: The value of the implementation specific timer for onboarding services needs to be large enough to allow a UE to complete the configuration of one or more entries of the "list of subscriber data" taking into consideration that configuration of SNPN subscription parameters in PLMN via the user plane or onboarding services in SNPN involves third party entities outside of the operator's network. If the UE receives the List of PLMNs to be used in disaster condition IE in the REGISTRATION ACCEPT message and the UE supports MINT, the UE shall delete the "list of PLMN(s) to be used in disaster condition" stored in the ME together with the PLMN ID of the RPLMN, if any, and may store the "list of PLMN(s) to be used in disaster condition" included in the List of PLMNs to be used in disaster condition IE in the ME together with the PLMN ID of the RPLMN. If the UE receives the Disaster roaming wait range IE in the REGISTRATION ACCEPT message and the UE supports MINT, the UE shall delete the disaster roaming wait range stored in the ME, if any, and store the disaster roaming wait range included in the Disaster roaming wait range IE in the ME. If the UE receives the Disaster return wait range IE in the REGISTRATION ACCEPT message and the UE supports MINT, the UE shall delete the disaster return wait range stored in the ME, if any, and store the disaster return wait range stored included in the Disaster return wait range IE in the ME. If the 5GS registration type IE is set to "disaster roaming mobility registration updating" and: a) the MS determined PLMN with disaster condition IE is included in the REGISTRATION REQUEST message, the AMF shall determine the PLMN with disaster condition in the MS determined PLMN with disaster condition IE; b) the MS determined PLMN with disaster condition IE is not included in the REGISTRATION REQUEST message and the Additional GUTI IE is included in the REGISTRATION REQUEST message and contains 5G-GUTI of a PLMN of the country of the PLMN providing disaster roaming, the AMF shall determine the PLMN with disaster condition in the PLMN identity of the 5G-GUTI; c) the MS determined PLMN with disaster condition IE and the Additional GUTI IE are not included in the REGISTRATION REQUEST message and: 1) the 5GS mobile identity IE contains 5G-GUTI of a PLMN of the country of the PLMN providing disaster roaming, the AMF shall determine the PLMN with disaster condition in the PLMN identity of the 5G-GUTI; or 2) the 5GS mobile identity IE contains SUCI of a PLMN of the country of the PLMN providing disaster roaming, the AMF shall determine the PLMN with disaster condition in the PLMN identity of the SUCI; or d) the MS determined PLMN with disaster condition IE is not included in the REGISTRATION REQUEST message, NG-RAN of the PLMN providing disaster roaming broadcasts disaster roaming indication and: - the Additional GUTI IE is included in the REGISTRATION REQUEST message and contains 5G-GUTI of a PLMN of a country other than the country of the PLMN providing disaster roaming; or - the Additional GUTI IE is not included and the 5GS mobile identity IE contains 5G-GUTI or SUCI of a PLMN of a country other than the country of the PLMN providing disaster roaming; the AMF shall determine the PLMN with disaster condition based on the disaster roaming agreement arrangement between mobile network operators. NOTE 24: The disaster roaming agreement arrangement between mobile network operators is out scope of 3GPP. If the AMF determines that a disaster condition applies to the PLMN with disaster condition, and the UE is allowed to be registered for disaster roaming services, the AMF shall set the Disaster roaming registration result value bit in the 5GS registration result IE to "no additional information" in the REGISTRATION ACCEPT message. If the AMF determines that the UE can be registered to the PLMN for normal service, the AMF shall set the Disaster roaming registration result value bit in the 5GS registration result IE to "request for registration for disaster roaming service accepted as registration not for disaster roaming service " in the REGISTRATION ACCEPT message. If the UE indicates "disaster roaming mobility registration updating" in the 5GS registration type IE in the REGISTRATION REQUEST message and the 5GS registration result IE value in the REGISTRATION ACCEPT message is set to: - "request for registration for disaster roaming service accepted as registration not for disaster roaming service", the UE shall consider itself registered for normal service. If the PLMN identity of the registered PLMN is a member of the forbidden PLMN list as specified in subclause 5.3.13A, any such PLMN identity shall be deleted from the corresponding list(s). If UE supports S1 mode, the UE shall initiate the registration procedure for mobility and periodic registration update and indicate that S1 mode is supported as described in subclause 5.5.1.3.2; or - "no additional information", the UE shall consider itself registered for disaster roaming. If the UE receives the Forbidden TAI(s) for the list of "5GS forbidden tracking areas for roaming" IE in the REGISTRATION ACCEPT message and the TAI(s) included in the IE is not part of the list of "5GS forbidden tracking areas for roaming", the UE shall store the TAI(s) belonging to the serving PLMN or equivalent PLMN(s) and ignore the TAI(s) which do not belong to the serving PLMN or equivalent PLMN(s) included in the IE into the list of "5GS forbidden tracking areas for roaming" and remove the TAI(s) from the stored TAI list if present. If the UE receives the Forbidden TAI(s) for the list of "5GS forbidden tracking areas for regional provision of service" IE in the REGISTRATION ACCEPT message and the TAI(s) included in the IE is not part of the list of "5GS forbidden tracking areas for regional provision of service", the UE shall store the TAI(s) belonging to the serving PLMN or equivalent PLMN(s) and ignore the TAI(s) which do not belong to the serving PLMN or equivalent PLMN(s) included in the IE into the list of "5GS forbidden tracking areas for regional provision of service" and remove the TAI(s) from the stored TAI list if present. If the ESI bit of the 5GMM capability IE of the REGISTRATION REQUEST message is set to "equivalent SNPNs supported", and the serving SNPN changes, the AMF shall indicate the NID of the serving SNPN in the REGISTRATION ACCEPT message. The UE shall determine the SNPN identity of the RSNPN from the NID received in the REGISTRATION ACCEPT message and the MCC and the MNC of the new 5G-GUTI. If the UE supporting the reconnection to the network due to RAN timing synchronization status change receives the RAN timing synchronization IE with the RecReq bit set to "Reconnection requested" in the REGISTRATION ACCEPT message, the UE shall operate as specified in subclauses 5.3.1.4, 5.5.1.3.2 and 5.6.1.1. If the UE supports discontinuous coverage, the AMF may include the Discontinuous coverage maximum time offset IE in the REGISTRATION ACCEPT message. If the UE receives, the Discontinuous coverage maximum time offset IE in the REGISTRATION ACCEPT message, the UE shall replace any previously received maximum time offset value on the same satellite NG-RAN RAT type and PLMN with the latest received timer value. If for discontinuous coverage the AMF includes Unavailability configuration IE in the REGISTRATION ACCEPT message and sets the End of unavailability report bit to “UE does not need to report end of unavailability”, the UE is not requied to initiate the registration procedure for mobility registration update when the unavailability period duration has ended. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.1.3.4 |
5,311 | – IMS-Parameters | The IE IMS-Parameters is used to convey capabilities related to IMS. IMS-Parameters information element -- ASN1START -- TAG-IMS-PARAMETERS-START IMS-Parameters ::= SEQUENCE { ims-ParametersCommon IMS-ParametersCommon OPTIONAL, ims-ParametersFRX-Diff IMS-ParametersFRX-Diff OPTIONAL, ... } IMS-Parameters-v1700 ::= SEQUENCE { ims-ParametersFR2-2-r17 IMS-ParametersFR2-2-r17 OPTIONAL } IMS-ParametersCommon ::= SEQUENCE { voiceOverEUTRA-5GC ENUMERATED {supported} OPTIONAL, ..., [[ voiceOverSCG-BearerEUTRA-5GC ENUMERATED {supported} OPTIONAL ]], [[ voiceFallbackIndicationEPS-r16 ENUMERATED {supported} OPTIONAL ]] } IMS-ParametersFRX-Diff ::= SEQUENCE { voiceOverNR ENUMERATED {supported} OPTIONAL, ... } IMS-ParametersFR2-2-r17 ::= SEQUENCE { voiceOverNR-r17 ENUMERATED {supported} OPTIONAL, ... } -- TAG-IMS-PARAMETERS-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,312 | 10.5.5.30 Location Area Identification 2 | The purpose of the Location Area Identification 2 information element is to provide an unambiguous identification of location areas within the area covered by the 3GPP system. The Location Area Identification 2 information element is coded as shown in figure 10.5.5.30/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.5.30/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The Location Area Identification 2 is a type 4 information element with 7 octets length. Figure 10.5.5.30/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Location Area Identification 2 information element Table 10.5.5.30/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Location Area Identification 2 information element | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.5.30 |
5,313 | 4.3.11 E-UTRAN Sharing Function | E-UTRAN Sharing is an agreement between operators and shall be transparent to the user. This implies that an E-UTRAN UE needs to be able to discriminate between core network operators available in a shared radio access network and that these operators can be handled in the same way as operators in non-shared networks. E-UTRAN terminals support E-UTRAN Sharing. An E-UTRAN Sharing architecture allows different core network operators to connect to a shared radio access network. The operators do not only share the radio network elements, but may also share the radio resources themselves. In addition to this shared radio access network the operators may or may not have additional dedicated radio access networks, like for example, 3G or 2G radio access networks. For E-UTRAN both Multi-Operator Core Network (MOCN) configuration and Gateway Core Network (GWCN) configuration as defined in TS 23.251[ Network sharing; Architecture and functional description ] [24] are supported over the S1 reference point. E-UTRAN terminals shall support shared networks and hence, only functions for "Supporting UEs" in TS 23.251[ Network sharing; Architecture and functional description ] [24] applies for E-UTRAN Sharing. E-UTRAN Radio Access Network Sharing functions is further described in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]. In networks that support network sharing as defined in TS 23.251[ Network sharing; Architecture and functional description ] [24], for a UE in state ECM-CONNECTED, the Handover Restriction List provided by the core-network to the radio access network is also used to inform the radio access network about the Selected PLMN and equivalent PLMNs as defined in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36]. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3.11 |
5,314 | A.17 Monitoring of RNReconfiguration | The purpose of RNReconfiguration related procedure is to configure/reconfigure the RN subframe configuration and/or to update the system information relevant for the RN in RRC_CONNECTED. The system information and subframe configuration is very important for RN, but the RN does not need to apply the system information acquisition and change monitoring procedures, if configured with an RN subframe configuration. Upon change of any system information relevant to an RN, E-UTRAN provides the system information blocks containing the relevant system information to RNs with an RN subframe configuration via dedicated signalling using the RNReconfiguration message. This dedicated signalling replaces any stored system information acquired through the system information acquisition procedure. Because the RN is semi-duplex, to avoid the transmission conflict between access link (between UE and RN) and backhaul link (between RN and DeNB), the subframe of RN is semi-statically assigned (see TR 36.814) and the configuration information is included in the RNReconfiguration message. During the RN operation, failures of backhaul link will cause unsuccessful RN reconfiguration. In that case, RN will not get any response from DeNB. The defined performance counter will help to compute how many respose messages are missing. Depending on this result, operators could easily make network planning to consider fix or optimize the backhaul link quality. | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | A.17 |
5,315 | 9.8.5 PMI reporting with PUCCH 1-1 (CSI Reference Symbol) | The minimum performance requirements of PMI reporting are defined based on the precoding gain, expressed as the relative increase in throughput when the transmitter is configured according to the UE reports compared to the case when the transmitter is using random precoding, respectively. When the transmitter uses random precoding, for each PDSCH allocation a precoder is randomly generated and applied to the PDSCH. A fixed transport format (FRC) is configured for all requirements. The requirements are specified in terms of the ratio In the definition of γ, tue is 70% of the maximum throughput obtained at SNRfollow using the precoders configured according to the UE reports, and trnd is the throughput measured at SNRfollow with random precoding. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.8.5 |
5,316 | 6.23.1 Description | The QoS requirements specified for particular services such as URLLC services, vertical automation communication services, and V2X, mandate QoS guarantees from the network. However, the network cannot always guarantee the required QoS of the service. An example reason for this shortcoming is that the latency and/or packet error rate increase due to interference in a radio cell. In such cases, it is critical that the application and/or application server is notified in a timely manner. Hence, the 5G system should be able to support QoS monitoring/assurance for URLLC services, V2X and vertical automation. For more information on QoS assurance see Annex F. Vertical automation systems are locally distributed and are typically served by wired and wireless communication networks of different types and with different characteristics. If the operation of the system or one of its sub-processes does not work properly, there is a need for quickly finding and eliminating the related error or fault in order to avoid significant operation and thus financial losses. To that end, automation devices and applications implement diagnosis and error-analysis algorithms, as well as predictive maintenance features. Due to their inherent challenges, wireless communication systems are usually under suspicion in case an error occurs in a distributed automation application. Therefore, diagnosis and fault analysis features for 5G systems are required. The 5G system needs to provide sufficient monitoring information as input for such diagnosis features. QoS monitoring can be used for the following activities: - assessing and assuring the dependability of network operation; - assessing and assuring the dependability of the communication services; - excluding particular communication errors; - identifying communication errors; - analysing the location of an error including the geographic location of the involved network component (UE; front-haul component; core node); - activation of application-related countermeasures. This section provides requirements for both functionality and service exposure. In addition, the service exposure requirements on QoS monitoring in 22.101 [6], clause 29.2 apply. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.23.1 |
5,317 | 5.1.4.2 Coordination between 5GMM for 3GPP access and EMM with N26 interface | A UE that is not registered shall be in state EMM-DEREGISTERED and state 5GMM-DEREGISTERED for 3GPP access. In N1 mode, upon successful completion of a registration procedure over 3GPP access, the UE operating in single-registration mode shall enter substates 5GMM-REGISTERED.NORMAL-SERVICE or 5GMM-REGISTERED.NON-ALLOWED-SERVICE as described in subclause 5.3.5.2 for 3GPP access and EMM-REGISTERED.NO-CELL-AVAILABLE. The UE shall reset the registration attempt counter for 3GPP access and the attach attempt counter (see 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]). At inter-system change from S1 mode to N1 mode, the UE shall enter substates 5GMM-REGISTERED.NORMAL-SERVICE or 5GMM-REGISTERED.NON-ALLOWED-SERVICE as described in subclause 5.3.5.2 for 3GPP accessand EMM-REGISTERED.NO-CELL-AVAILABLE and initiate a registration procedure for mobility and periodic registration update over 3GPP access indicating "mobility registration updating" in the 5GS registration type IE of the REGISTRATION REQUEST message (see subclause 5.5.1.3). In S1 mode, upon successful completion of an attach or tracking area updating procedure, the UE operating in single-registration mode shall enter substates 5GMM-REGISTERED.NO-CELL-AVAILABLE for 3GPP access and EMM-REGISTERED.NORMAL-SERVICE. The UE shall reset the registration attempt counter for 3GPP access and the attach attempt counter or tracking area updating attempt counter (see 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]). At inter-system change from N1 mode to S1 mode when there is no active PDU session for which interworking with EPS is supported as specified in subclause 6.1.4.1, and EMM-REGISTERED without PDN connection is not supported by the UE or the MME, the UE shall enter state 5GMM-DEREGISTERED for 3GPP access and state EMM-DEREGISTERED and then initiate the EPS attach procedure. If EMM-REGISTERED without PDN connection is supported by the UE and the MME, the UE shall enter substates EMM-REGISTERED.NORMAL-SERVICE and 5GMM-REGISTERED.NO-CELL-AVAILABLE for 3GPP access and initiate a tracking area updating procedure. At inter-system change from N1 mode to S1 mode when there is at least one active PDU session for which interworking with EPS is supported as specified in subclause 6.1.4.1, the UE shall enter substates EMM-REGISTERED.NORMAL-SERVICE and 5GMM-REGISTERED.NO-CELL-AVAILABLE for 3GPP access and initiate a tracking area updating procedure (see 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]). | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.1.4.2 |
5,318 | 8.69 MBMS Session Duration | The MBMS Session Duration is defined in 3GPP TS 23.246[ Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description ] [37]. The MBMS Session Duration information element indicates the estimated session duration of the MBMS service data transmission if available. The payload shall be encoded as per the MBMS-Session-Duration AVP defined in 3GPP TS 29.061[ Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) ] [38], excluding the AVP Header fields (as defined in IETF RFC 3588 [39], clause 4.1). Figure 8.69-1: MBMS Session Duration | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 8.69 |
5,319 | 6.1.3.8.2.3 Handling of network rejection due to SM cause other than SM cause #26 | If the SM cause value is different from #26 "insufficient resources", and the Back-off timer value IE is included, the MS shall take different actions depending on the timer value received in the Back-off timer value IE: i) if the timer value indicates neither zero nor deactivated, the MS shall start the back-off timer with the value provided in the Back-off timer value IE for the MBMS context activation procedure and PLMN and APN combination. The MS shall not send another ACTIVATE MBMS CONTEXT REQUEST message in the PLMN for the same APN that was sent by the MS until the back-off timer expires, the MS is switched off or the SIM/USIM is removed; ii) if the timer value indicates that this timer is deactivated, the MS shall not send another ACTIVATE MBMS CONTEXT REQUEST message in the PLMN for the same APN that was sent by the MS until the MS is switched off or the SIM/USIM is removed; and iii) if the timer value indicates that this timer is zero, the MS may send an ACTIVATE MBMS CONTEXT REQUEST message in the PLMN for the same APN. If the Back-off timer value IE is not included, then the MS shall ignore the Re-attempt indicator IE provided by the network, if any. i) Additionally, if the SM cause value is #8 "operator determined barring", #27 "missing or unknown APN", #32 "service option not supported", or #33 "requested service option not subscribed", the MS shall proceed as follows: - if the MS is registered in its HPLMN or in a PLMN that is within the EHPLMN list (if the EHPLMN list is present), the MS shall behave as described above in the present subclause, using the configured SM_RetryWaitTime value as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [135] or in USIM file NASCONFIG as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [112], if available, as back-off timer value; and - otherwise, if the MS is not registered in its HPLMN or in a PLMN that is within the EHPLMN list (if the EHPLMN list is present), or if the SM_RetryWaitTime value is not configured, the MS shall behave as described above in the present subclause using the default value of 12 minutes for the back-off timer. ii) For SM cause values different from #8 "operator determined barring", #27 "missing or unknown APN", #32 "service option not supported", or #33 "requested service option not subscribed", the MS behaviour regarding the start of a back-off timer is unspecified. The MS shall not stop any back-off timer upon a PLMN change or inter-system change. If the network indicates that a back-off timer for the MBMS context activation procedure and PLMN and APN combination is deactivated, then it remains deactivated upon a PLMN change or inter-system change. NOTE 1: This means the back-off timer can still be running or be deactivated for the given SM procedure and PLMN and APN combination when the MS returns to the PLMN or when it performs inter-system change back from S1 mode to A/Gb or Iu mode. Thus the MS can still be prevented from sending another ACTIVATE MBMS CONTEXT REQUEST message in the PLMN for the same APN. If the back-off timer is started upon receipt of an ACTIVATE MBMS CONTEXT REJECT message (i.e. the timer value was provided by the network, a configured value is available or the default value is used as explained above) or the back-off timer is deactivated, the MS behaves as follows: i) after a PLMN change the MS may send an ACTIVATE MBMS CONTEXT REQUEST message for the same APN in the new PLMN, if the back-off timer is not running and is not deactivated for the MBMS context activation procedure and the combination of new PLMN and APN; Furthermore as an implementation option, for the SM cause values #8 "operator determined barring", #27 "missing or unknown APN", #32 "service option not supported" or #33 "requested service option not subscribed", if the network does not include a Re-attempt indicator IE, the MS may decide not to automatically send another ACTIVATE MBMS CONTEXT REQUEST message for the same APN, if the MS registered to a new PLMN which is in the list of equivalent PLMNs. ii) if the network includes the Re-attempt indicator IE, the MS shall ignore any indication provided in the IE regarding whether re-attempt in S1 mode is allowed. If the Re-attempt indicator IE indicates that re-attempt in an equivalent PLMN is not allowed, then depending on the timer value received in the Back-off timer value IE, for each combination of a PLMN from the equivalent PLMN list and the APN the MS shall start a back-off timer for the MBMS context activation procedure with the value provided by the network, or deactivate the respective back-off timer. NOTE 2: The back-off timer is used to describe a logical model of the required MS behaviour. This model does not imply any specific implementation, e.g. as a timer or timestamp. NOTE 3: Reference to back-off timer in this section can either refer to use of timer T3396 or to use of a different packet system specific timer within the MS. Whether the MS uses T3396 as a back-off timer or it uses different packet system specific timers as back-off timers is left up to MS implementation. This back-off timer is stopped when the MS is switched off or the SIM/USIM is removed. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.1.3.8.2.3 |
5,320 | 5.10.4 MME triggered Serving GW relocation | The MME triggered Serving GW relocation procedure for E-UTRAN is depicted in figure 5.10.4-1. The procedure allows the MME to trigger Serving GW relocation due to events other than those described in the mobility scenarios (see clause 5.3.3.1 and clause 5.5.1). Such scenario exists during the establishment of a SIPTO at local network PDN connection with stand-alone GW or during the establishment of a SIPTO above RAN PDN connection. Figure 5.10.4-1: MME triggered Serving GW relocation 1. The Serving GW relocation procedure may be triggered by the MME due to events that may benefit from a Serving GW relocation other than those described in the mobility events scenarios. 2. If the MME determines that the Serving GW is to be relocated then it selects a new Serving GW according to clause 4.3.8.2. The MME sends a Create Session Request (bearer context(s) with PDN GW addresses and TEIDs (for GTP-based S5/S8) or GRE keys (for PMIP-based S5/S8) at the PDN GW(s) for uplink traffic, eNodeB address(es) and TEIDs for downlink user plane for the existing EPS bearers, the Protocol Type over S5/S8, Serving Network) message per PDN connection to the new Serving GW. The new Serving GW allocates the S-GW addresses and TEIDs for the uplink traffic on S1_U reference point (one TEID per bearer). The Protocol Type over S5/S8 is provided to Serving GW which protocol should be used over S5/S8 interface. If the PDN GW requested UE's location info, the MME also includes the User Location Information IE in this message. If the PDN GW requested UE's User CSG information (determined from the UE context), the MME includes the User CSG Information IE in this message if the User CSG Information has changed. 3. The new Serving GW assigns addresses and TEIDs (one per bearer) for downlink traffic from the PDN GW. The Serving GW allocates DL TEIDs on S5/S8. It sends a Modify Bearer Request (Serving GW addresses for user plane and TEID(s), Serving Network) message per PDN connection to the PDN GW(s). The S-GW also includes User Location Information IE and/or UE Time Zone IE and/or User CSG Information IE if it is present in step 2. The PDN GW updates its context field and returns a Modify Bearer Response (Charging Id, MSISDN, etc.) message to the Serving GW. The MSISDN is included if the PDN GW has it stored in its UE context. The PDN GW starts sending downlink packets to the new GW using the newly received address and TEIDs. These downlink packets will use the new downlink path via the new Serving GW to the eNodeB. This step is performed for all connected PDN-GWs for that specific UE. 4. The new Serving GW sends a Create Session Response (Serving GW addresses and uplink TEID(s) for user plane) message back to the MME. The MME starts a timer, to be used in step 6. 5. The MME sends a Bearer Modify Request (Serving GW addresses and uplink TEID(s) for user plane, Secondary RAT usage data request) message to eNodeB. The eNodeB starts using the new Serving GW address(es) and TEID(s) for forwarding subsequent uplink packets and sends a Bearer Modify Response message to the MME. If the PLMN has configured secondary RAT usage reporting, the MME may request the eNodeB for Secondary RAT usage data in the Bearer Modify request message. If the eNodeB has Secondary RAT usage data, it provides it in the Bearer Modify Response message. 5a. If Secondary RAT usage data is included in the previous message and if PDN GW Secondary RAT usage reporting is active, the MME uses the Secondary RAT usage data reporting procedure as described in clause 5.7A.3 figure 5.7A.3-2 to provide this information to the Serving GW and PDN GW. The MME includes a flag that the Serving GW shall not process this information and forward it to the PDN GW. 6. When the timer has expired after step 4, the MME releases the bearer(s) in the old Serving GW by sending a Delete Session Request message (Cause, Operation Indication, Secondary RAT usage data). The operation Indication flag is not set, that indicates to the old Serving GW that the old Serving GW shall not initiate a delete procedure towards the PDN GW. The old Serving GW acknowledges with Delete Session Response messages. The MME includes the Secondary RAT usage data if the eNodeB had provided it to the MME in step 5. If the Serving GW relocation procedure towards a new Serving GW fails, based on operator policy, the MME should go back to the old Serving GW and disconnects the affected PDN connections (e.g. SIPTO at local network) that are no longer allowed to remain connected. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.10.4 |
5,321 | 28.7.11 NAI format for CP-PRUK ID | The NAI format for CP-PRUK ID shall have the form username@realm as specified in clause 2.2 of IETF RFC 7542 [126]. The realm part shall be in the form: "prose-cp.5gc.mnc<MNC>.mcc<MCC>.3gppnetwork.org" The username part of the NAI shall take one of the following forms: "rid<routing indicator>.pid<CP-PRUK ID*>" - the <routing indicator> part is the "Routing Indicator" as specified in clause 2.2B. - the <CP-PRUK ID*> part is the hexadecimal representation of the CP-PRUK ID* specified in clause A.3 of 3GPP TS 33.503[ Security Aspects of Proximity based Services (ProSe) in the 5G System (5GS) ] [142]. The maximum length of a CP-PRUK ID in NAI format is 254 octets. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 28.7.11 |
5,322 | 20 Usage of Diameter on SGmb interface 20.1 General | Signalling between MBMS GW and BM-SC is exchanged at SGmb reference point. The MBMS GW uses the SGmb interface: - to receive indication of session start, session update and session stop messages, which shall cause the MBMS GW, MME/SGSN and E-UTRAN/UTRAN to set up/tear down the appropriate resources for the service. For further details, see 3GPP TS 23.246[ Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description ] [65]; - to enable the BM-SC and MBMS GW to detect an SGmb path failure or the restart of the peer MBMS node. For further details, see 3GPP TS 23.007[ Restoration procedures ] [104]. - to enable the BM-SC to transfer the M1 interface information of local MBMS information. For further details, see 3GPP TS 23.285[ Architecture enhancements for V2X services ] [112]. NOTE: The localized MBMS architecture refers to Annex B of 3GPP TS 23.285[ Architecture enhancements for V2X services ] [112]. The SGmb application is defined as an IETF vendor specific Diameter application, where the vendor is 3GPP. The vendor identifier assigned by IANA to 3GPP (http://www.iana.org/assignments/enterprise-numbers) is 10415. The SGmb application identifier value assigned by IANA is 16777292. The SGmb application identifier value shall be included in the Auth-Application-Id AVP. The BM-SC and the MBMS GW shall advertise the support of the SGmb application by including the value of the application identifier in the Auth-Application-Id AVP and the value of the 3GPP (10415) in the Vendor-Id AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands as specified in IETF RFC 6733 [111], i.e. as part of the Vendor-Specific-Application-Id AVP. The Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands are specified in the Diameter Base Protocol. | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 20 |
5,323 | 8.86 Allocation/Retention Priority (ARP) | Allocation/Retention Priority (ARP) is coded as depicted in Figure 8.86-1. Figure 8.86-1: Allocation/Retention Priority (ARP) The meaning and value range of the parameters within the ARP are defined in 3GPP TS 29.212[ Policy and Charging Control (PCC); Reference points ] [29]. The bits within the octet 5 are: - Bit 1 – PVI (Pre-emption Vulnerability): See 3GPP TS 29.212[ Policy and Charging Control (PCC); Reference points ] [29], clause 5.3.47 Pre-emption-Vulnerability AVP. - Bit 2 – spare - Bits 3 to 6 – PL (Priority Level): See 3GPP TS 29.212[ Policy and Charging Control (PCC); Reference points ] [29], clause 5.3.45 Priority-Level AVP. PL encodes each priority level defined for the Priority-Level AVP as the binary value of the priority level. - Bit 7 – PCI (Pre-emption Capability): See 3GPP TS 29.212[ Policy and Charging Control (PCC); Reference points ] [29], clause 5.3.46 Pre-emption-Capability AVP. - Bit 8 – spare. | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 8.86 |
5,324 | 6.1 Protocol Data Units 6.1.1 General | A MAC PDU is a bit string that is byte aligned (i.e. multiple of 8 bits) in length. In the figures in clause 6.1, bit strings are represented by tables in which the most significant bit is the leftmost bit of the first line of the table, the least significant bit is the rightmost bit on the last line of the table, and more generally the bit string is to be read from left to right and then in the reading order of the lines. The bit order of each parameter field within a MAC PDU is represented with the first and most significant bit in the leftmost bit and the last and least significant bit in the rightmost bit. MAC SDUs are bit strings that are byte aligned (i.e. multiple of 8 bits) in length. An SDU is included into a MAC PDU from the first bit onward. The MAC entity shall ignore the value of Reserved bits in downlink MAC PDUs and in MAC PDUs received in sidelink. | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.1 |
5,325 | 6.3.5A.2.1 Minimum requirements | For inter-band carrier aggregation with uplink assigned to two E-UTRA bands, the relative power tolerance is specified when the power of the target and reference sub-frames on each component carrier exceed the minimum output power as defined in subclause 6.3.2A and the total power is limited by PUMAX as defined in subclause 6.2.5A. The requirements shall apply on each component carrier with all component carriers active. The UE transmitter shall have the capability of changing the output power independently on all component carriers in the uplink and: a) the requirements for all combinations of PUSCH and PUCCH transitions per component carrier is given in Table 6.3.5.2.1-1. b) for SRS the requirements for combinations of PUSCH/PUCCH and SRS transitions between subframes given in Table 6.3.5.2.1-1 apply per component carrier when the target and reference subframes are configured for either simultaneous SRS or simultaneous PUSCH. c) for RACH the requirements apply for the primary cell and are given in Table 6.3.5.2.1-1. For component carriers with Frame Structure Type 3 the requirements for the target sub-frame relative to the power of the most recently transmitted reference sub-frame shall be met with a transmission gap ≤ 40 ms. For intra-band contiguous carrier aggregation bandwidth class B, C and D and intra-band non-contiguous carrier aggregation, the requirements apply when the power of the target and reference sub-frames on each component carrier exceed -20 dBm and the total power is limited by PUMAX as defined in subclause 6.2.5A. For the purpose of these requirements, the power in each component carrier is specified over only the transmitted resource blocks. The UE shall meet the following requirements for transmission on both assigned component carriers when the average transmit power per PRB is aligned across both assigned carriers in the reference sub-frame: a) for all possible combinations of PUSCH and PUCCH transitions per component carrier, the corresponding requirements given in Table 6.3.5.2.1-1; b) for SRS transitions on each component carrier, the requirements for combinations of PUSCH/PUCCH and SRS transitions given in Table 6.3.5.2.1-1 with simultaneous SRS of constant SRS bandwidth allocated in the target and reference subrames; c) for RACH on the primary component carrier, the requirements given in Table 6.3.5.2.1-1 for PRACH. For a) and b) above, the power step P between the reference and target subframes shall be set by a TPC command and/or an uplink scheduling grant transmitted by means of an appropriate DCI Format. For a), b) and c) above, two exceptions are allowed for each component carrier for a power per carrier ranging from -20 dBm to PUMAX,c as defined in subclause 6.2.5. For these exceptions the power tolerance limit is ±6.0 dB in Table 6.3.5.2.1-1. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.3.5A.2.1 |
5,326 | 5.3.4.1.2 Management of Service Area Restrictions | This clause describes Service Area Restrictions for 3GPP access. For Service Area Restrictions when using wireline access, see TS 23.316[ Wireless and wireline convergence access support for the 5G System (5GS) ] [84]. A Service Area Restriction may contain one or more (e.g. up to 16) entire Tracking Areas each or the Service Area Restriction may be set as unlimited (i.e. contain all Tracking Areas of the PLMN). The UE's subscription data in the UDM includes a Service Area Restriction which may contain either Allowed or Non-Allowed Areas–specified by using explicit Tracking Area identities and/or other geographical information (e.g. longitude/latitude, zip code, etc). The geographical information used to specify Allowed or Non-Allowed Area is only managed in the network, and the network will map it to a list of TAs before sending Service Area Restriction information to the PCF, NG-RAN and UE. When the AMF assigns a limited allowed area to the UE, the AMF shall provide the UE with Service Area Restrictions which consist of either Allowed Areas or Non-Allowed Areas. The Allowed Areas included in the Service Area Restrictions can be pre-configured and/or dynamically assigned by the AMF. The Allowed Area may alternatively be configured as unlimited i.e. it may contain all Tracking Areas of the PLMN. The Registration Area of a UE in the Non-Allowed Area should consist of a set of TAs which belongs to a Non-Allowed Area of the UE. The Registration Area of a UE in the Allowed Area should consist of a set of TAs which belongs to an Allowed Area of the UE. The AMF provides the Service Area Restriction in the form of TA(s), which may be a subset of full list stored in UE's subscription data or provided by the PCF, to the UE during the Registration procedure. NOTE: As the finest granularity for Service Area Restrictions are at TA level, subscriptions with limited geographical extent, like subscriptions for Fixed Wireless Access, will be allocated one or a few TAs and will consequently be allowed to access services in a larger area than in e.g. a FWA system. The limited allowed area may also be limited by the AMF by a maximum allowed number of Tracking Areas, even though this limitation is not sent to the UE. If maximum allowed number of Tracking Areas is used in combination with Allowed Area, the maximum allowed number of Tracking Areas indicates (to the AMF) the maximum number of TAs allowed in limited allowed area inside the Allowed Area. If maximum allowed number of Tracking Areas is used in combination with Non-Allowed Area, the maximum allowed number of Tracking Areas indicates (to the AMF) the maximum number of TAs allowed in limited allowed area outside of the Non-Allowed Area. The UDM stores the Service Area Restrictions of a UE as part of the UE's subscription data. The PCF in the serving network may (e.g. due to varying conditions such as UE's location, application in use, time and date) further adjust Service Area Restrictions of a UE, either by expanding an Allowed Area or by reducing a Non-Allowed Area or by increasing the maximum allowed number of Tracking Areas. If NWDAF is deployed, the PCF may use analytics (i.e. statistics or predictions) on UE mobility from NWDAF (see TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [86]) to adjust Service Area Restrictions. The UDM and the PCF may update the Service Area Restrictions of a UE at any time. For the UE in CM-CONNECTED state the AMF updates the UE and RAN immediately. For UE in CM-IDLE state the AMF may page the UE immediately or store the updated service area restriction and update the UE upon next signalling interaction with the UE, as defined in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]. During registration, if the Service Area Restrictions of the UE is not present in the AMF, the AMF fetches from the UDM the Service Area Restrictions of the UE that may be further adjusted by the PCF. The serving AMF shall enforce the Service Area Restrictions of a UE. A limited allowed area given by a maximum allowed number of Tracking Areas, may be dynamically assigned by the AMF adding any not yet visited (by the UE) Tracking Areas to the limited allowed area until the maximum allowed number of Tracking Areas is reached (i.e. the AMF adds new TAs to the limited allowed area until the number of TAs is equal to the maximum allowed number of Tracking Areas). The AMF deletes the list of TAs that have been used up under the maximum allowed number of Tracking Areas quota at every Initial Registration. For a UE in CM-CONNECTED state the AMF shall indicate the Service Area Restrictions of this UE to the RAN, using a Mobility Restriction List. The UE shall store the received Service Area Restrictions and, if there is previously stored Service Area Restrictions, replace them with the newly received information. If the Service Area Restrictions include a limited allowed area, the Service Area Restrictions are applicable for the Tracking areas indicated in Service Area Restrictions. If the Service Area Restrictions included an unlimited allowed area, the received Service Area Restrictions are either applicable for the registered PLMN and its equivalent PLMN(s) that are available in the Registration Area, or the registered SNPN that is available in the Registration Area. The RAN uses the Service Area Restrictions for target cell selection in Xn and N2 based handover. Upon change of serving AMF due to mobility, the old AMF may provide the new AMF with the Service Area Restrictions of the UE that may be further adjusted by the PCF. The network may perform paging for a UE to update Service Area Restrictions with Generic UE Configuration Update procedure (see clause 4.2.4 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]). In the case of roaming, the Service Area Restrictions are transferred from the UDM via the serving AMF to the serving PCF in the visited network. The serving PCF in the visited network may further adjust the Service Area Restrictions. Support for Service Area Restrictions with NR satellite access is described in clause 5.4.11.8. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.3.4.1.2 |
5,327 | 4.3.12.4 PDN GW selection function (3GPP accesses) for Emergency Services | When a PDN GW is selected for IMS emergency services support, the PDN GW selection function described in clause 4.3.8.1 for normal bearer services is applied to the Emergency APN or the MME selects the PDN GW directly from the MME Emergency Configuration Data. If the PDN GW selection function described in clause 4.3.8.1 is used it shall always derive a PDN GW in the visited PLMN, which guarantees that also the IP address is allocated by the visited PLMN. In networks that support handover between E-UTRAN and HRPD accesses, the MME selects a PDN GW that is statically configured in the MME Emergency Configuration Data. In networks that support handover between E-UTRAN and WLAN accesses, when the UE has been authorized but has not been authenticated, the MME selects the PDN GW that is statically configured in the MME Emergency Configuration Data. The PDN GW selection does not depend on subscriber information in the HSS since emergency service support is a local, not subscribed service. The MME Emergency Configuration Data contains the Emergency APN which is used to derive a PDN GW, or the MME Emergency Configuration Data may also contain the statically configured PDN GW for the Emergency APN. In the case of GateWay Core Network sharing, the MME shall support separate MME Emergency Configuration Data for each of the sharing PLMNs. In the case of GateWay Core Network sharing and PDN GW selection for the Emergency APN, the MME shall be able to take the selected PLMN ID into account to derive a PDN GW. This functionality is used by the Attach procedure and by the UE Requested PDN Connectivity procedure, in both cases when establishing emergency bearer services. NOTE: It is assumed that the PDN GW that is statically configured in the MME Emergency Configuration Data is the same as the PDN GW configured in WLAN and HRPD accesses. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3.12.4 |
5,328 | E.2 Delegated I-SMF discovery | Figure E.2: Delegated Discovery of I-SMF The following impacts are applicable to clause 4.23.5 (PDU Session Establishment procedure) to support delegated SMF discovery: 1. If the AMF supports delegated SMF discovery and is configured to apply it, the AMF sends an Nsmf_PDUSession_CreateSMContext Request together with discovery and selection parameters to a SCP. The discovery and selection parameters include S-NSSAI, DNN, TAI that corresponds to the UE location required SMF capability (e.g. support of ATSSS). 2. [Optional] The SCP sends an Nnrf_NFDiscovery Request to the NRF. The request includes discovery and selection parameters received from AMF in step 1. 3. [Optional] The SCP gets Nnrf_NFDiscovery service response. The response may include one or more profile(s) of SMF(s). Depending on the available information, the SCP may either execute steps in Case A or in Case B. Case A There are, either in the NRF response or discovered by the SCP, one or more SMF instances that support Discovery and selection crireria set by the AMF. 4. The SCP selects an SMF instance. 5. The SCP forwards the Nsmf_PDUSession_CreateSMContext Request to the selected SMF instance. Case B There is, either in the NRF response or discovered by the SCP, no SMF instance that supports Discovery and selection criteria set by the AMF. 6. The SCP returns an Nsmf_PDUSession_CreateSMContext Response to the AMF with an error 'NF not found' 7. The AMF sends Nnrf_NFDiscovery Request to the NRF. The AMF may indicate the maximum number of SMF instances to be returned by the NRF. 8. The AMF gets Nnrf_NFDiscovery service response with one or more profile(s) of SMF(s). 9. The AMF selects an SMF instance endpoint. 10. The AMF builds a Nsmf_PDUSession_CreateSMContext Request that contains the endpoint (e.g. URI) of the selected SMF in the body of the request. If the AMF supports delegated SMF discovery and is configured to apply it, the AMF sends the Nsmf_PDUSession_CreateSMContext Request to a SCP together with Discovery and selection parameters that include S-NSSAI, TAI that corresponds to the UE location, i.e. parameter for I-SMF selection. 11. [Optional] The SCP sends an Nnrf_NFDiscovery Request to the NRF. The request includes Discovery and selection parameters received from AMF (including the TAI that corresponds to the UE location). 12. [Optional] The SCP gets Nnrf_NFDiscovery service response. The response may include one or more profile(s) of I-SMF(s). 13. The SCP selects an I-SMF instance that supports the TAI. 14. The SCP forwards the Nsmf_PDUSession_CreateSMContext Request received from the AMF to the selected I-SMF instance. 15. If the I-SMF does not support delegated SMF discovery or is not configured to apply it (Case A), the I-SMF sends Nsmf_PDUSession_Create Request directly to the SMF. Otherwise (Case B), the I-SMF sends the Nsmf_PDUSession_Create Request to the SCP but adds Discovery & Selection parameter set to the SMF endpoint received from AMF. In both cases the I-SMF uses the received endpoint (e.g. URI) of the selected SMF to construct the target destination to be addressed. NOTE: The Nsmf_PDUSession_Create Request sent by the I-SMF in Case A and in Case B is the same apart from the Discovery & Selection parameter. The Nsmf_PDUSession_Create Request received by the SMF in Case A and in Case B is the same. 16. The SCP forwards the Nsmf_PDUSession_Create Request to the selected SMF instance indicated in step 15. The procedure continues as described in clause 4.3.2.2.2 from Step 7. Difference comparing to procedure defined in clause 4.3.2.2.2, the V-SMF and V-UPF are replaced by I-SMF and I-UPF and H-SMF and H-UPF are replaced by SMF and UPF(PSA) respectively. Also only the S-NSSAI with the value defined by the serving PLMN is sent to the SMF. When the I-SMF responds to AMF with Nsmf_PDUSession_CreateSMContext Response as in clause 4.3.2.2.2 in Step 3b, if the AMF has not stored the SMF Service Area for the I-SMF, the AMF shall obtain the SMF Service Area for the concerned I-SMF from the NRF using the Nnrf_NFManagement_NFStatusSubscribe service operation. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | E.2 |
5,329 | – ServingCellConfigCommonSIB | The IE ServingCellConfigCommonSIB is used to configure cell specific parameters of a UE's serving cell in SIB1. ServingCellConfigCommonSIB information element -- ASN1START -- TAG-SERVINGCELLCONFIGCOMMONSIB-START ServingCellConfigCommonSIB ::= SEQUENCE { downlinkConfigCommon DownlinkConfigCommonSIB, uplinkConfigCommon UplinkConfigCommonSIB OPTIONAL, -- Need R supplementaryUplink UplinkConfigCommonSIB OPTIONAL, -- Need R n-TimingAdvanceOffset ENUMERATED { n0, n25600, n39936 } OPTIONAL, -- Need S ssb-PositionsInBurst SEQUENCE { inOneGroup BIT STRING (SIZE (8)), groupPresence BIT STRING (SIZE (8)) OPTIONAL -- Cond FR2-Only }, ssb-PeriodicityServingCell ENUMERATED {ms5, ms10, ms20, ms40, ms80, ms160}, tdd-UL-DL-ConfigurationCommon TDD-UL-DL-ConfigCommon OPTIONAL, -- Cond TDD ss-PBCH-BlockPower INTEGER (-60..50), ..., [[ channelAccessMode-r16 CHOICE { dynamic NULL, semiStatic SemiStaticChannelAccessConfig-r16 } OPTIONAL, -- Cond SharedSpectrum discoveryBurstWindowLength-r16 ENUMERATED {ms0dot5, ms1, ms2, ms3, ms4, ms5} OPTIONAL, -- Need R highSpeedConfig-r16 HighSpeedConfig-r16 OPTIONAL -- Need R ]], [[ channelAccessMode2-r17 ENUMERATED {enabled} OPTIONAL, -- Cond SharedSpectrum2 discoveryBurstWindowLength-v1700 ENUMERATED {ms0dot125, ms0dot25, ms0dot5, ms0dot75, ms1, ms1dot25} OPTIONAL, -- Need R highSpeedConfigFR2-r17 HighSpeedConfigFR2-r17 OPTIONAL, -- Need R uplinkConfigCommon-v1700 UplinkConfigCommonSIB-v1700 OPTIONAL -- Need R ]], [[ enhancedMeasurementLEO-r17 ENUMERATED {true} OPTIONAL -- Need R ]], [[ ra-ChannelAccess-r17 ENUMERATED {enabled} OPTIONAL -- Cond SharedSpectrum2 ]], [[ downlinkConfigCommon-v1760 DownlinkConfigCommonSIB-v1760 OPTIONAL, -- Need R uplinkConfigCommon-v1760 UplinkConfigCommonSIB-v1760 OPTIONAL -- Need R ]] } -- TAG-SERVINGCELLCONFIGCOMMONSIB-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,330 | 4.2.3 Non-roaming reference architecture | Figure 4.2.3-1 depicts the non-roaming reference architecture. Service-based interfaces are used within the Control Plane. Figure 4.2.3-1: Non-Roaming 5G System Architecture NOTE: If an SCP is deployed it can be used for indirect communication between NFs and NF services as described in Annex E. SCP does not expose services itself. Figure 4.2.3-2 depicts the 5G System architecture in the non-roaming case, using the reference point representation showing how various network functions interact with each other. Figure 4.2.3-2: Non-Roaming 5G System Architecture in reference point representation NOTE 1: N9, N14 are not shown in all other figures however they may also be applicable for other scenarios. NOTE 2: For the sake of clarity of the point-to-point diagrams, the UDSF, NEF and NRF have not been depicted. However, all depicted Network Functions can interact with the UDSF, UDR, NEF and NRF as necessary. NOTE 3: The UDM uses subscription data and authentication data and the PCF uses policy data that may be stored in UDR (refer to clause 4.2.5). NOTE 4: For clarity, the UDR and its connections with other NFs, e.g. PCF, are not depicted in the point-to-point and service-based architecture diagrams. For more information on data storage architectures refer to clause 4.2.5. NOTE 5: For clarity, the NWDAF(s), DCCF, MFAF and ADRF and their connections with other NFs, are not depicted in the point-to-point and service-based architecture diagrams. For more information on network data analytics architecture refer to TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [86]. NOTE 6: For clarity, the 5G DDNMF and its connections with other NFs, e.g. UDM, PCF are not depicted in the point-to-point and service-based architecture diagrams. For more information on ProSe architecture refer to TS 23.304[ Proximity based Services (ProSe) in the 5G System (5GS) ] [128]. NOTE 7: For clarity, the TSCTSF and its connections with other NFs, e.g. PCF, NEF, UDR are not depicted in the point-to-point and service-based architecture diagrams. For more information on TSC architecture refer to clause 4.4.8. NOTE 8: For exposure of the QoS monitoring information as specified in clause 5.8.2.18, exposure of data collected for analytics as specified in clause 5.2.26.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3], and exposure of the TSC management information as specified in clause 5.8.5.14, direct interaction between UPF and NFs can be supported via the Nupf interface (see clause 4.2.16). NOTE 9: For clarity, the EASDF and its connections with SMF is not depicted in the point-to-point and service-based architecture diagrams. For more information on edge computing architecture refer to TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [130]. Figure 4.2.3-3 depicts the non-roaming architecture for UEs concurrently accessing two (e.g. local and central) data networks using multiple PDU Sessions, using the reference point representation. This figure shows the architecture for multiple PDU Sessions where two SMFs are selected for the two different PDU Sessions. However, each SMF may also have the capability to control both a local and a central UPF within a PDU Session. Figure 4.2.3-3: Applying Non-Roaming 5G System Architecture for multiple PDU Session in reference point representation Figure 4.2.3-4 depicts the non-roaming architecture in the case of concurrent access to two (e.g. local and central) data networks is provided within a single PDU Session, using the reference point representation. Figure 4.2.3-4: Applying Non-Roaming 5G System Architecture for concurrent access to two (e.g. local and central) data networks (single PDU Session option) in reference point representation Figure 4.2.3-5 depicts the non-roaming architecture for Network Exposure Function, using reference point representation. Figure 4.2.3-5: Non-Roaming Architecture for Network Exposure Function in reference point representation NOTE 1: In Figure 4.2.3-5, Trust domain for NEF is same as Trust domain for SCEF as defined in TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [36]. NOTE 2: In Figure 4.2.3-5, 3GPP Interface represents southbound interfaces between NEF and 5GC Network Functions e.g. N29 interface between NEF and SMF, N30 interface between NEF and PCF, etc. All southbound interfaces from NEF are not shown for the sake of simplicity. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2.3 |
5,331 | 8.7.11 TDD FDD CA (4 Rx) | The parameters specified in Table 8.7.11-1 are valid for all TDD FDD CA tests for 4Rx capable UEs unless otherwise stated. Table 8.7.11-1: Common Test Parameters (TDD FDD CA) For UE not supporting 256QAM, the TB success rate shall be higher than 85% when PDSCH are scheduled with FRC in Table 8.7.11-2 with the downlink physical channel setup according to Annex C.3.2. For UE supporting 256QAM, the TB success rate shall be higher than 85% when PDSCH are scheduled with FRC in Table 8.7.11-3 with the downlink physical channel setup according to Annex C.3.2. For UE supporting 256QAM, the requirement with 64QAM is not applicable. The TB success rate is defined as 100%*NDL_correct_rx/ (NDL_newtx + NDL_retx), where NDL_newtx is the number of newly transmitted DL transport blocks, NDL_retx is the number of retransmitted DL transport blocks, and NDL_correct_rx is the number of correctly received DL transport blocks. The TB success rate shall be sustained during at least 300 frames. Table 8.7.11-2: Per-CC FRC for SDR test (TDD-FDD 64QAM) Table 8.7.11-3: Per-CC FRC for SDR test (TDD-FDD 256QAM) CA configuration, bandwidth combination and MIMO layer on each CC is determined by following procedure. - Select one CA bandwidth combination among all supported CA configurations with bandwidth combination and MIMO layer on each CC that leads to largest equivalent aggregated bandwidth among all CA bandwidth combinations supported by UE. Equivalent aggregated bandwidth is defined as where is number of CCs, and is MIMO layer and bandwidth of CC . - When there are multiple sets of {CA configuration, bandwidth combination, MIMO layer} with same largest aggregated bandwidth, select one among sets with largest number of 4 layer CCs. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.7.11 |
5,332 | 6.31.2.2 Disaster Condition | The 3GPP system shall enable UEs to obtain information that a Disaster Condition applies to a particular PLMN or PLMNs. NOTE: If a UE has no coverage of its HPLMN, then obtains information that a Disaster Condition applies to the UE's HPLMN, the UE can register with a PLMN offering Disaster Roaming service. The 3GPP system shall support means for a PLMN operator to be aware of the area where Disaster Condition applies. The 3GPP system shall be able to support provision of service to Disaster Inbound Roamer only within the specific region where Disaster Condition applies. The 3GPP system shall be able to provide efficient means for a network to inform Disaster Inbound roamers that a Disaster Condition is no longer applicable. Subject to regulatory requirements or operator’s policy, the 3GPP system shall support a PLMN operator to be made aware of the failure or recovery of other PLMN(s) in the same country when the Disaster Condition is applies, or when the Disaster Condition is not applicable. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.31.2.2 |
5,333 | 5.2.6.25.6 Nnef_TimeSynchronization_CapsSubscribe operation | Service operation name: Nnef_TimeSynchronization_CapsSubscribe Description: The AF requests the subscription to receive notifications about time synchronization capabilities for a list of UE(s) or a group of UEs or any UEs using DNN/S-NSSAI combination, for which the NEF authorizes the request and invokes the corresponding service operation with TSCTSF (clause 5.2.27.2.6). Event Filters are used to specify the conditions to match for notifying the event. If there are no conditions to match then the Event Filter is not provided. The Event Filters supported by the service are described in Table 5.2.27.2.6-1. Inputs, Required: As specified in clause 5.2.27.2.6. Inputs, Optional: As specified in clause 5.2.27.2.6. Outputs, Required: Operation execution result indication and in the case of successful operation, any outputs as specified in clause 5.2.27.2.6. Outputs, Optional: As specified in clause 5.2.27.2.6. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.6.25.6 |
5,334 | 8.7.2 TDD (single carrier and CA) | The parameters specified in Table 8.7.2-1 are valid for all TDD tests unless otherwise stated. Table 8.7.2-1: Common Test Parameters (TDD) For UE not supporting 256QAM, the requirements are specified in Table 8.7.2-3, with the addition of the parameters in Table 8.7.2-2 and the downlink physical channel setup according to Annex C.3.2. The test points are applied to UE category and bandwidth combination with maximum aggregated bandwidth as specified inTable 8.7.2-4. The TB success rate shall be sustained during at least 300 frames. For UE supporting 256QAM, the requirements are specified in Table 8.7.2-6, with the addition of the parameters in Table 8.7.2-5 and the downlink physical channel setup according to Annex C.3.2. The test points are applied to UE category and bandwidth combination with maximum aggregated bandwidth as specified inTable 8.7.2-7. The TB success rate shall be sustained during at least 300 frames. For UE supporting 256QAM, the requirement in Table 8.7.2-3 is not applicable. For UE supporting 256QAM and category 9/10 and category 13, the requirements are specified in both Table 8.7.2-3 and Table 8.7.2-6, with the addition of the parameters in Table 8.7.2-2 and in Table 8.7.2-5 respectivly. The downlink physical channel setup according to Annex C.3.2. The test points are applied to UE category and bandwidth combination with maximum aggregated bandwidth as specified inTable 8.7.2-4 and in Table 8.7.2-7 for the category 9/10 and category 13, the TB success rate shall be sustained during at least 300 frames. The test coverage for different number of component carriers is defined in 8.1.2.4. Table 8.7.2-2: test parameters for sustained downlink data rate (TDD 64QAM) Table 8.7.2-3: Minimum requirement (TDD 64QAM) Table 8.7.2-4: Test points for sustained data rate (FRC 64QAM) Table 8.7.2-5: test parameters for sustained downlink data rate (TDD 256QAM) Table 8.7.2-6: Minimum requirement (TDD 256QAM) Table 8.7.2-7: Test points for sustained data rate (FRC 256QAM) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.7.2 |
5,335 | 6.6.1B Occupied bandwidth for UL-MIMO | For UE supporting UL-MIMO, the requirements for occupied bandwidth is specified at each transmit antenna connector. The occupied bandwidth is defined as the bandwidth containing 99 % of the total integrated mean power of the transmitted spectrum on the assigned channel at each transmit antenna connector. For UE with two transmit antenna connectors in closed-loop spatial multiplexing scheme, the occupied bandwidth at each transmitter antenna shall be less than the channel bandwidth specified in Table 6.6.1B-1. The requirements shall be met with the UL-MIMO configurations specified in Table 6.2.2B-2. Table B-1: Occupied channel bandwidth If UE is configured for transmission on single-antenna port, the requirements in subclause 6.6.1 apply. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.6.1B |
5,336 | – RRCSetupComplete | The RRCSetupComplete message is used to confirm the successful completion of an RRC connection establishment. Signalling radio bearer: SRB1 RLC-SAP: AM Logical channel: DCCH Direction: UE to Network RRCSetupComplete message -- ASN1START -- TAG-RRCSETUPCOMPLETE-START RRCSetupComplete ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { rrcSetupComplete RRCSetupComplete-IEs, criticalExtensionsFuture SEQUENCE {} } } RRCSetupComplete-IEs ::= SEQUENCE { selectedPLMN-Identity INTEGER (1..maxPLMN), registeredAMF RegisteredAMF OPTIONAL, guami-Type ENUMERATED {native, mapped} OPTIONAL, s-NSSAI-List SEQUENCE (SIZE (1..maxNrofS-NSSAI)) OF S-NSSAI OPTIONAL, dedicatedNAS-Message DedicatedNAS-Message, ng-5G-S-TMSI-Value CHOICE { ng-5G-S-TMSI NG-5G-S-TMSI, ng-5G-S-TMSI-Part2 BIT STRING (SIZE (9)) } OPTIONAL, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension RRCSetupComplete-v1610-IEs OPTIONAL } RRCSetupComplete-v1610-IEs ::= SEQUENCE { iab-NodeIndication-r16 ENUMERATED {true} OPTIONAL, idleMeasAvailable-r16 ENUMERATED {true} OPTIONAL, ue-MeasurementsAvailable-r16 UE-MeasurementsAvailable-r16 OPTIONAL, mobilityHistoryAvail-r16 ENUMERATED {true} OPTIONAL, mobilityState-r16 ENUMERATED {normal, medium, high, spare} OPTIONAL, nonCriticalExtension RRCSetupComplete-v1690-IEs OPTIONAL } RRCSetupComplete-v1690-IEs ::= SEQUENCE { ul-RRC-Segmentation-r16 ENUMERATED {true} OPTIONAL, nonCriticalExtension RRCSetupComplete-v1700-IEs OPTIONAL } RRCSetupComplete-v1700-IEs ::= SEQUENCE { onboardingRequest-r17 ENUMERATED {true} OPTIONAL, nonCriticalExtension RRCSetupComplete-v1800-IEs OPTIONAL } RRCSetupComplete-v1800-IEs ::= SEQUENCE { ncr-NodeIndication-r18 ENUMERATED {true} OPTIONAL, musim-CapRestrictionInd-r18 ENUMERATED {true} OPTIONAL, flightPathInfoAvailable-r18 ENUMERATED {true} OPTIONAL, measConfigReportAppLayerAvailable-r18 ENUMERATED {true} OPTIONAL, mobileIAB-NodeIndication-r18 ENUMERATED {true} OPTIONAL, nonCriticalExtension SEQUENCE{} OPTIONAL } RegisteredAMF ::= SEQUENCE { plmn-Identity PLMN-Identity OPTIONAL, amf-Identifier AMF-Identifier } -- TAG-RRCSETUPCOMPLETE-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,337 | 4.4.3.1 Average DL PDCP SDU delay | This measurement provides the average (arithmetic mean) PDCP SDU delay on the downlink. The measurement is split into subcounters per E-RAB QoS level (QCI). If there is one or more RNs served in a cell, for that cell the eNodeB performs each measurement separately for packets transmitted between the eNodeB and UEs and for packets transmitted between the E-UTRAN and RNs. The measurement is also applicable to RNs. DER (n=1) This measurement is obtained according to the definition in 3GPP TS 36.314[ Evolved Universal Terrestrial Radio Access (E-UTRA); Layer 2 - Measurements ] [11]. Each measurement is an integer value representing the mean delay in ms. The number of measurements is equal to the number of QCIs plus a possible sum value identified by the .sum suffix. The measurement name has the form DRB.PdcpSduDelayDl.QCI, which indicates the PDCP SDU delay between the eNodeB (or RN) and UE DRB.PdcpSduDelayDlRN.QCI, which indicates the PDCP SDU delay between the E-UTRAN and RN. where QCI identifies the E-RAB level quality of service class. EUtranCellFDD EUtranCellTDD Valid for packet switched traffic EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.4.3.1 |
5,338 | 5.5.7 DTMF protocol control procedure | Dual Tone Multi Frequency (DTMF) is an inband one out of four plus one out of four signalling system primarily used from terminal instruments in telecommunication networks. The support of DTMF in the network is described in 3GPP TS 23.014[ Support of Dual Tone Multi-Frequency (DTMF) signalling ] [12]. The mobile station shall be capable of transmitting DTMF messages as specified in this subclause if and only if the mobile station has the user connection for speech attached and an appropriate channel is available. The transaction identifier used by the DTMF messages shall be that of the attached speech call. NOTE 1: The present document means that DTMF messages can generally be sent in the active state of a call in speech transmission mode or when a traffic channel is available during setup or release and the progress indicator IE has been received. NOTE 2: Since the DTMF protocol messages are sent in a store and forward mode on the signalling channels the control of the device at the far end may be delayed dependent on the load or quality of the channels. NOTE 3: The procedures described in this paragraph support DTMF only in the direction mobile station to network. A mobile station supporting multimedia CAT during the alerting phase of a mobile originated multimedia call establishment should also be capable of transmitting DTMFs during a multimedia call as specified in subclause 5.3.6.5. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.7 |
5,339 | 6.3.5.2 Relative Power tolerance | The relative power tolerance is the ability of the UE transmitter to set its output power in a target sub-frame relatively to the power of the most recently transmitted reference sub-frame if the transmission gap between these sub-frames is ≤ 20 ms. For PRACH transmission, the relative tolerance is the ability of the UE transmitter to set its output power relatively to the power of the most recently transmitted preamble. The measurement period for the PRACH preamble is specified in Table 6.3.4.2-1. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.3.5.2 |
5,340 | 5.16.6 Mission Critical Services | According to TS 22.280[ Mission Critical Services Common Requirements (MCCoRe); Stage 1 ] [37], a Mission Critical Service (MCX Service) is a communication service reflecting enabling capabilities Mission Critical Applications and provided to end users from Mission Critical Organizations and mission critical applications for other businesses and organizations (e.g. utilities, railways). An MCX Service is either Mission Critical Push To Talk (MCPTT) as defined in TS 23.379[ Functional architecture and information flows to support Mission Critical Push To Talk (MCPTT); Stage 2 ] [38], Mission Critical Video (MCVideo) as defined in TS 23.281[ Functional architecture and information flows to support Mission Critical Video (MCVideo); Stage 2 ] [39], or Mission Critical Data (MCData) as defined in TS 23.282[ Functional architecture and information flows to support Mission Critical Data (MCData); Stage 2 ] [40] and represents a shared underlying set of requirements between two or more MCX Service types. MCX Services are not restricted only to the ones defined in this clause and such services can also have priority treatment, if defined via operator's policy and/or local regulation. MCX Services are based on the ability to invoke, modify, maintain and release sessions with priority, and deliver the priority media packets under network congestion conditions. As specified in clause 6.8 of TS 22.261[ Service requirements for the 5G system ] [2], MCX Users require 5GS functionality that allows for real-time, dynamic, secure and limited interaction with the QoS and policy framework for modification of the QoS and policy framework by authorized users. The limited interaction is based on operator policy, and provides specific limitations on what aspects of the QoS and policy framework an authorized MCX User can modify. MCX Services are supported in a roaming environment when roaming agreements are in place and where regulatory requirements apply. An MCX-subscribed UE obtains priority access to the Radio Access Network by using the Unified Access Control mechanism according to TS 22.261[ Service requirements for the 5G system ] [2]. This mechanism provides preferential access to UEs based on its assigned Access Identity. If an MCX-subscribed UE belongs to the special Access Identity as defined in TS 22.261[ Service requirements for the 5G system ] [2], the UE has preferential access to the network compared to ordinary UEs in periods of congestion. MCX subscription allows users to receive priority services, if the network supports MCX. MCX subscription entitles a USIM with special Access Identity. NOTE 1: For Mission Critical Services that require low latency and zero packet loss even for the first downlink packet(s), periodic keep-alive packets during interruptions of media transmission (e.g. Floor Idle as specified in TS 23.379[ Functional architecture and information flows to support Mission Critical Push To Talk (MCPTT); Stage 2 ] [38], referenced by TS 23.289[ Mission Critical services over 5G System; Stage 2 ] [184]), which is sent over user plane of PDU session, can be used so that the UE is kept in RRC_CONNECTED state without being paged when unicast transmission is used. It is up to the implementation, the periodicity of the keep-alive packets configured in the AF can consider NG-RAN's configuration. NOTE 2: For support of Mission Critical Services that require low latency and zero packet loss when using MBS, see TS 23.247[ Architectural enhancements for 5G multicast-broadcast services ] [121]. MCX Services leverage the foundation of the 5G QoS Model as defined in clause 5.7, and 5G Policy Control as defined in clause 5.14. It requires that the necessary subscriptions are in place for both the 5G QoS Profile and the necessary Policies. In addition, MCX Services leverage priority mechanism as defined in clause 5.22. The terminating network identifies the priority of the MCX Service session and applies priority treatment, including paging with priority, to ensure that the MCX Service session can be established with priority to the terminating user (either an MCX User or normal user). Priority treatment for MCX Service includes priority message handling, including priority treatment during authentication, security, and Mobility Management procedures. Priority treatment for MCX Service sessions require appropriate ARP and 5QI (plus 5G QoS characteristics) setting for QoS Flows according to the operator's policy. NOTE 3: Use of QoS Flows for MCX Service sessions with non-standardized 5QI values enables the flexible assignment of 5G QoS characteristics (e.g. Priority Level). When a MCX Service session is requested by an MCX User, the following principles apply in the network: - QoS Flows employed in a MCX Service session shall be assigned ARP value settings appropriate for the priority of the MCX User. - Setting ARP pre-emption capability and vulnerability of QoS Flows related to a MCX Service session, subject to operator policies and depending on national/regional regulatory requirements. - Pre-emption of non-MCX Users over MCX Users during network congestion situations, subject to operator policy and national/regional regulations. Priority treatment is applicable to IMS based multimedia services and priority PDU connectivity services. Relative PDU priority decisions for MCX Service sessions are based on real-time data of the state of the network and/or based on modification of the QoS and policy framework by authorized users as described in clause 6.8 of TS 22.261[ Service requirements for the 5G system ] [2]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.16.6 |
5,341 | 5.4A.5 Mapping to physical resources | The block of complex-valued symbols shall be multiplied with the amplitude scaling factor in order to conform to the transmit power specified in Clause 5.1.2.1 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4], and mapped in sequence starting with to resource elements. SPUCCH uses one or more resource block in the frequency domain and is mapped to either a slot or a subslot in the time domain. Within the physical resource block(s) used for transmission, the mapping of to resource elements on antenna port and not used for transmission of reference signals shall be in increasing order of first , then . The starting symbol for each subslot number is provided by Table 5.4A.4.5-1 for subslot-SPUCCH. For slot-SPUCCH the starting symbol is for the slot the SPUCCH is transmitted in. Table 5.4A.5-1: Starting symbol for subslot-SPUCCH mapping The relation between the index and the antenna port number is given by Table 5.2.1-1. The physical resource blocks () within which the transmission of SPUCCH is carried out in slot depends on the SPUCCH format and whether frequency hopping is enabled or not. In case of slot-SPUCCH format 1, 1a, 1b and frequency hopping disabled, the PRB used is determined as described in clause 5.4.3 for PUCCH format 1, 1a, 1b. In case of slot-SPUCCH format 3, the PRB used is given by For the other SPUCCH formats, it is determined by Table 5.4A.5-2, Table 5.4A.5-3 and Table 5.4A.5-4. Table 5.4A.5-2: for slot-SPUCCH format 1, 1a, 1b with frequency hopping enabled Table 5.4A.5-3: for slot-SPUCCH format 4 Table 5.4A.5-4: for subslot-SPUCCH format 1, 1a, 1b, 4 The variable depends on the SPUCCH format as defined in Table 5.4A.5-5. Table 5.4A.5-5: for SPUCCH In case of subslot-SPUCCH, there is a configuration restriction that each SPUCCH resource in the resource set, of up to four resources, , shall map to the same pair of PRBs () This restriction applies separately to each of n1SubslotSPUCCH-AN-List and sr-SubslotSPUCCH-Resource in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [9]. In case of simultaneous transmission of sounding reference signal and SPUCCH when there is one serving cell configured, the shortened SPUCCH format shall be used where the last SC-FDMA symbol in the second slot of a subframe shall be left empty. | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.4A.5 |
5,342 | 6.40.1 Description | Artificial Intelligence (AI)/Machine Learning (ML) is being used in a range of application domains across industry sectors. In mobile communications systems, mobile devices (e.g. smartphones, automotive, robots) are increasingly replacing conventional algorithms (e.g. speech recognition, image recognition, video processing) with AI/ML models to enable applications. The 5G system can at least support three types of AI/ML operations: - AI/ML operation splitting between AI/ML endpoints The AI/ML operation/model is split into multiple parts according to the current task and environment. The intention is to offload the computation-intensive, energy-intensive parts to network endpoints, whereas leave the privacy-sensitive and delay-sensitive parts at the end device. The device executes the operation/model up to a specific part/layer and then sends the intermediate data to the network endpoint. The network endpoint executes the remaining parts/layers and feeds the inference results back to the device. - AI/ML model/data distribution and sharing over 5G system Multi-functional mobile terminals might need to switch the AI/ML model in response to task and environment variations. The condition of adaptive model selection is that the models to be selected are available for the mobile device. However, given the fact that the AI/ML models are becoming increasingly diverse, and with the limited storage resource in a UE, it can be determined to not pre-load all candidate AI/ML models on-board. Online model distribution (i.e. new model downloading) is needed, in which an AI/ML model can be distributed from a NW endpoint to the devices when they need it to adapt to the changed AI/ML tasks and environments. For this purpose, the model performance at the UE needs to be monitored constantly. - Distributed/Federated Learning over 5G system The cloud server trains a global model by aggregating local models partially-trained by each end devices. Within each training iteration, a UE performs the training based on the model downloaded from the AI server using the local training data. Then the UE reports the interim training results to the cloud server via 5G UL channels. The server aggregates the interim training results from the UEs and updates the global model. The updated global model is then distributed back to the UEs and the UEs can perform the training for the next iteration. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.40.1 |
5,343 | 6.1.3.3 PDP context modification procedure | The PDP context modification procedure is invoked by the network or by the MS, in order to: - inform about the change of the 3GPP PS data off UE status for a PDN connection; - change the QoS negotiated; - change the Radio priority level; or - change the TFT, negotiated during the PDP context activation procedure, the secondary PDP context activation procedure or at previously performed PDP context modification procedures. Depending on the selected Bearer Control Mode being 'MS only' or 'MS/NW', the MS or the network respectively may also create and delete a TFT of an active default PDP context. The PDP context modification procedure can be initiated by the network or the MS at any time when a PDP context is active. The network and the MS shall manage packet filter identifiers for the packet filters each modifies or deletes. The network and the MS shall manage packet filter evaluation precedence for the packet filters each modifies.If the MS changes a TFT, which is not assigned to a default PDP context, the MS shall ensure that at least one packet filter applicable for the uplink direction remains among the packet filters created by the MS in that TFT, or no own packet filters . If the network changes a TFT, which is not ass igned to a default PDP context, the network shall ensure that at least one packet filter applicable for the uplink direction remains among the TFT packet filters created by the network in that TFT, or no own packet filters. The MS supporting S1 mode shall not modify the QoS of the first PDP context that was established within the PDN connection. The MS not supporting S1 mode should not modify the QoS of the first PDP context that was established within the PDN connection (see 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [74]). To indicate a change of 3GPP PS data off UE status for a PDN connection, the MS shall include the protocol configuration options IE in the MODIFY PDP CONTEXT REQUEST message and set the 3GPP PS data off UE status only if the network included the 3GPP PS data off support indication for the PDN connection established by the PDP context activation procedure. The MS behaves as described in subclause 4.7.1.10. When the PDP context modification procedure is used to indicate a change of 3GPP PS data off UE status for a PDN connection (see subclause 4.7.1.10), the UE shall initiate the PDP context modification procedure even if the timer T3396 or the back-off timer is running or is deactivated. The PDP context modification procedure may also be invoked by the MS, in order to upgrade the maximum bit rate and to trigger the re-establishment of the radio access bearer for an activated PDP context which is preserved in the MS with maximum bit rate values of 0kbit/s for both uplink and downlink (see 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [74]). NOTE 1: As described in 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [74], the MS only preserves PDP contexts with a TFT including packet filter(s) set by the MS. If - the PDP Context Modification request is accepted by the network but the radio access bearer is not established; or - the PDP Context Modification request is rejected with cause "insufficient resources" (see subclause 6.1.3.3.3), then the MS is not required to start a new PDP Context Modification procedure or to start a Service Request procedure in order to trigger the re-establishment of the radio access bearer. If there is a PDN connection for emergency bearer services established, the MS shall not request a modification of bearer resources for this PDN connection. The network requested PDP context modification procedure may also be used to update the PDP address when external PDP address allocation is performed, in which case the MS receives the PDP address in the MODIFY PDP CONTEXT REQUEST (Network to MS direction) message. NOTE 2: The procedure may be initiated by the network due to an inter-SGSN Routing Area Updating when a PDP context is active. The network requested PDP context modification procedure may also be used to update the WLAN offload indication, in which case the MS receives the updated WLAN offload indication in the MODIFY PDP CONTEXT REQUEST (Network to MS direction) message. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.1.3.3 |
5,344 | 8.118 Integer Number | Integer Number is coded as depicted in Figure 8.118-1. Figure 8.118-1: Integer Number The Integer Number value is encoded with the number of octets defined in the Length field, e.g. when n=2, the range of the integer number value is from 0 to 65535. The Integer Number value shall be encoded as further described below for the following information elements: - Maximum Wait Time IE: the length shall be set to 2, i.e. the integer number value shall be encoded as a 16 bit unsigned integer. - DL Buffering Suggested Packet Count IE: the length shall be set to 1 or 2; - UE Usage Type IE: the length shall be set to 1, i.e. the integer number value shall be encoded as a 8 bit unsigned integer as specified in clause 7.3.202 of 3GPP TS 29.272[ Evolved Packet System (EPS); Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol ] [70]. - Remaining Running Service Gap Timer IE: the length shall be set to 4, i.e. the integer number value shall be encoded as a 32 bit unsigned integer. - DL Data Packet Size IE: the length shall be set to 2, i.e. the integer number value shall be encoded as a 16 bit unsigned integer. | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 8.118 |
5,345 | – SL-ReportConfigList | The IE SL-ReportConfigList concerns a list of SL measurement reporting configurations to add or modify for a destination. SL-ReportConfigList information element -- ASN1START -- TAG-SL-REPORTCONFIGLIST-START SL-ReportConfigList-r16 ::= SEQUENCE (SIZE (1..maxNrofSL-ReportConfigId-r16)) OF SL-ReportConfigInfo-r16 SL-ReportConfigInfo-r16 ::= SEQUENCE { sl-ReportConfigId-r16 SL-ReportConfigId-r16, sl-ReportConfig-r16 SL-ReportConfig-r16, ... } SL-ReportConfigId-r16 ::= INTEGER (1..maxNrofSL-ReportConfigId-r16) SL-ReportConfig-r16 ::= SEQUENCE { sl-ReportType-r16 CHOICE { sl-Periodical-r16 SL-PeriodicalReportConfig-r16, sl-EventTriggered-r16 SL-EventTriggerConfig-r16, ... }, ... } SL-PeriodicalReportConfig-r16 ::= SEQUENCE { sl-ReportInterval-r16 ReportInterval, sl-ReportAmount-r16 ENUMERATED {r1, r2, r4, r8, r16, r32, r64, infinity}, sl-ReportQuantity-r16 SL-MeasReportQuantity-r16, sl-RS-Type-r16 SL-RS-Type-r16, ... } SL-EventTriggerConfig-r16 ::= SEQUENCE { sl-EventId-r16 CHOICE { eventS1-r16 SEQUENCE { s1-Threshold-r16 SL-MeasTriggerQuantity-r16, sl-ReportOnLeave-r16 BOOLEAN, sl-Hysteresis-r16 Hysteresis, sl-TimeToTrigger-r16 TimeToTrigger, ... }, eventS2-r16 SEQUENCE { s2-Threshold-r16 SL-MeasTriggerQuantity-r16, sl-ReportOnLeave-r16 BOOLEAN, sl-Hysteresis-r16 Hysteresis, sl-TimeToTrigger-r16 TimeToTrigger, ... }, ... }, sl-ReportInterval-r16 ReportInterval, sl-ReportAmount-r16 ENUMERATED {r1, r2, r4, r8, r16, r32, r64, infinity}, sl-ReportQuantity-r16 SL-MeasReportQuantity-r16, sl-RS-Type-r16 SL-RS-Type-r16, ... } SL-MeasReportQuantity-r16 ::= CHOICE { sl-RSRP-r16 BOOLEAN, ... } SL-MeasTriggerQuantity-r16 ::= CHOICE { sl-RSRP-r16 RSRP-Range, ... } SL-RS-Type-r16 ::= ENUMERATED {dmrs, sl-prs, spare2, spare1} -- TAG-SL-REPORTCONFIGLIST-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,346 | 5.7.1.2a Alternative QoS Profile | The Alternative QoS Profile(s) can be optionally provided for a GBR QoS Flow with Notification control enabled. If the corresponding PCC rule contains the related information (as described in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]), the SMF shall provide, in addition to the QoS profile, a prioritized list of Alternative QoS Profile(s) to the NG-RAN. If the SMF provides a new prioritized list of Alternative QoS Profile(s) to the NG-RAN (if the corresponding PCC rule information changes), the NG-RAN shall replace any previously stored list with it. An Alternative QoS Profile represents a combination of QoS parameters PDB, PER, Averaging Window and GFBR to which the application traffic is able to adapt. For delay-critical GBR QoS flows, an Alternative QoS Profile may also include an MDBV. NOTE 1: There is no requirement that the GFBR monotonically decreases, nor that the PDB or PER monotonically increase as the Alternative QoS Profiles become less preferred. When the NG-RAN sends a notification to the SMF that the QoS profile is not fulfilled, the NG-RAN shall, if the currently fulfilled values match an Alternative QoS Profile, include also the reference to the Alternative QoS Profile to indicate the QoS that the NG-RAN currently fulfils (see clause 5.7.2.4). The NG-RAN shall enable the SMF to determine when an NG-RAN node supports the Alternative QoS feature but cannot fulfil even the least preferred Alternative QoS Profile. NOTE 2: To reduce the risk that GBR QoS Flows are released in case of RAN resource limitations (and then experience difficulties in being re-established), Application Functions can set the least preferred Alternative Service Requirement to an undemanding level. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.7.1.2a |
5,347 | – PhysicalCellGroupConfig | The IE PhysicalCellGroupConfig is used to configure cell-group specific L1 parameters. PhysicalCellGroupConfig information element -- ASN1START -- TAG-PHYSICALCELLGROUPCONFIG-START PhysicalCellGroupConfig ::= SEQUENCE { harq-ACK-SpatialBundlingPUCCH ENUMERATED {true} OPTIONAL, -- Need S harq-ACK-SpatialBundlingPUSCH ENUMERATED {true} OPTIONAL, -- Need S p-NR-FR1 P-Max OPTIONAL, -- Need R pdsch-HARQ-ACK-Codebook ENUMERATED {semiStatic, dynamic}, tpc-SRS-RNTI RNTI-Value OPTIONAL, -- Need R tpc-PUCCH-RNTI RNTI-Value OPTIONAL, -- Need R tpc-PUSCH-RNTI RNTI-Value OPTIONAL, -- Need R sp-CSI-RNTI RNTI-Value OPTIONAL, -- Need R cs-RNTI SetupRelease { RNTI-Value } OPTIONAL, -- Need M ..., [[ mcs-C-RNTI RNTI-Value OPTIONAL, -- Need R p-UE-FR1 P-Max OPTIONAL -- Cond MCG-Only ]], [[ xScale ENUMERATED {dB0, dB6, spare2, spare1} OPTIONAL -- Cond SCG-Only ]], [[ pdcch-BlindDetection SetupRelease { PDCCH-BlindDetection } OPTIONAL -- Need M ]], [[ dcp-Config-r16 SetupRelease { DCP-Config-r16 } OPTIONAL, -- Need M harq-ACK-SpatialBundlingPUCCH-secondaryPUCCHgroup-r16 ENUMERATED {enabled, disabled} OPTIONAL, -- Cond twoPUCCHgroup harq-ACK-SpatialBundlingPUSCH-secondaryPUCCHgroup-r16 ENUMERATED {enabled, disabled} OPTIONAL, -- Cond twoPUCCHgroup pdsch-HARQ-ACK-Codebook-secondaryPUCCHgroup-r16 ENUMERATED {semiStatic, dynamic} OPTIONAL, -- Cond twoPUCCHgroup p-NR-FR2-r16 P-Max OPTIONAL, -- Need R p-UE-FR2-r16 P-Max OPTIONAL, -- Cond MCG-Only nrdc-PCmode-FR1-r16 ENUMERATED {semi-static-mode1, semi-static-mode2, dynamic} OPTIONAL, -- Cond MCG-Only nrdc-PCmode-FR2-r16 ENUMERATED {semi-static-mode1, semi-static-mode2, dynamic} OPTIONAL, -- Cond MCG-Only pdsch-HARQ-ACK-Codebook-r16 ENUMERATED {enhancedDynamic} OPTIONAL, -- Need R nfi-TotalDAI-Included-r16 ENUMERATED {true} OPTIONAL, -- Need R ul-TotalDAI-Included-r16 ENUMERATED {true} OPTIONAL, -- Need R pdsch-HARQ-ACK-OneShotFeedback-r16 ENUMERATED {true} OPTIONAL, -- Need R pdsch-HARQ-ACK-OneShotFeedbackNDI-r16 ENUMERATED {true} OPTIONAL, -- Need R pdsch-HARQ-ACK-OneShotFeedbackCBG-r16 ENUMERATED {true} OPTIONAL, -- Need R downlinkAssignmentIndexDCI-0-2-r16 ENUMERATED { enabled } OPTIONAL, -- Need S downlinkAssignmentIndexDCI-1-2-r16 ENUMERATED {n1, n2, n4} OPTIONAL, -- Need S pdsch-HARQ-ACK-CodebookList-r16 SetupRelease {PDSCH-HARQ-ACK-CodebookList-r16} OPTIONAL, -- Need M ackNackFeedbackMode-r16 ENUMERATED {joint, separate} OPTIONAL, -- Need R pdcch-BlindDetectionCA-CombIndicator-r16 SetupRelease { PDCCH-BlindDetectionCA-CombIndicator-r16 } OPTIONAL, -- Need M pdcch-BlindDetection2-r16 SetupRelease { PDCCH-BlindDetection2-r16 } OPTIONAL, -- Need M pdcch-BlindDetection3-r16 SetupRelease { PDCCH-BlindDetection3-r16 } OPTIONAL, -- Need M bdFactorR-r16 ENUMERATED {n1} OPTIONAL -- Need R ]], [[ -- start of enhanced Type3 feedback pdsch-HARQ-ACK-EnhType3ToAddModList-r17 SEQUENCE (SIZE(1..maxNrofEnhType3HARQ-ACK-r17)) OF PDSCH-HARQ-ACK-EnhType3-r17 OPTIONAL, -- Need N pdsch-HARQ-ACK-EnhType3ToReleaseList-r17 SEQUENCE (SIZE(1..maxNrofEnhType3HARQ-ACK-r17)) OF PDSCH-HARQ-ACK-EnhType3Index-r17 OPTIONAL, -- Need N pdsch-HARQ-ACK-EnhType3SecondaryToAddModList-r17 SEQUENCE (SIZE(1..maxNrofEnhType3HARQ-ACK-r17)) OF PDSCH-HARQ-ACK-EnhType3-r17 OPTIONAL, -- Need N pdsch-HARQ-ACK-EnhType3SecondaryToReleaseList-r17 SEQUENCE (SIZE(1..maxNrofEnhType3HARQ-ACK-r17)) OF PDSCH-HARQ-ACK-EnhType3Index-r17 OPTIONAL, -- Need N pdsch-HARQ-ACK-EnhType3DCI-FieldSecondaryPUCCHgroup-r17 ENUMERATED {enabled} OPTIONAL, -- Cond twoPUCCHgroup pdsch-HARQ-ACK-EnhType3DCI-Field-r17 ENUMERATED {enabled} OPTIONAL, -- Need R -- end of enhanced Type3 feedback -- start of triggering of HARQ-ACK re-transmission on a PUCCH resource pdsch-HARQ-ACK-Retx-r17 ENUMERATED {enabled} OPTIONAL, -- Need R pdsch-HARQ-ACK-RetxSecondaryPUCCHgroup-r17 ENUMERATED {enabled} OPTIONAL, -- Cond twoPUCCHgroup -- end of triggering of HARQ-ACK re-transmission on a PUCCH resource -- start of PUCCH Cell switching pucch-sSCell-r17 SCellIndex OPTIONAL, -- Need R pucch-sSCellSecondaryPUCCHgroup-r17 SCellIndex OPTIONAL, -- Cond twoPUCCHgroup pucch-sSCellDyn-r17 ENUMERATED {enabled} OPTIONAL, -- Need R pucch-sSCellDynSecondaryPUCCHgroup-r17 ENUMERATED {enabled} OPTIONAL, -- Cond twoPUCCHgroup pucch-sSCellPattern-r17 SEQUENCE (SIZE(1..maxNrofSlots)) OF INTEGER (0..1) OPTIONAL, -- Need R pucch-sSCellPatternSecondaryPUCCHgroup-r17 SEQUENCE (SIZE(1..maxNrofSlots)) OF INTEGER (0..1) OPTIONAL, -- Cond twoPUCCHgroup -- end of PUCCH Cell switching uci-MuxWithDiffPrio-r17 ENUMERATED {enabled} OPTIONAL, -- Need R uci-MuxWithDiffPrioSecondaryPUCCHgroup-r17 ENUMERATED {enabled} OPTIONAL, -- Cond twoPUCCHgroup simultaneousPUCCH-PUSCH-r17 ENUMERATED {enabled} OPTIONAL, -- Need R simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup-r17 ENUMERATED {enabled} OPTIONAL, -- Cond twoPUCCHgroup prioLowDG-HighCG-r17 ENUMERATED {enabled} OPTIONAL, -- Need R prioHighDG-LowCG-r17 ENUMERATED {enabled} OPTIONAL, -- Need R twoQCLTypeDforPDCCHRepetition-r17 ENUMERATED {enabled} OPTIONAL, -- Need R multicastConfig-r17 SetupRelease { MulticastConfig-r17 } OPTIONAL, -- Need M pdcch-BlindDetectionCA-CombIndicator-r17 SetupRelease { PDCCH-BlindDetectionCA-CombIndicator-r17 } OPTIONAL -- Need M ]], [[ simultaneousSR-PUSCH-diffPUCCH-Groups-r17 ENUMERATED {enabled} OPTIONAL -- Cond twoPUCCHgroup ]], [[ intraBandNC-PRACH-simulTx-r17 ENUMERATED {enabled} OPTIONAL -- Need R ]], [[ pdcch-BlindDetection4-r17 SetupRelease { PDCCH-BlindDetection4-r17 } OPTIONAL -- Need M ]], [[ simultaneousPUCCH-PUSCH-SamePriority-r17 ENUMERATED {enabled} OPTIONAL, -- Need R simultaneousPUCCH-PUSCH-SamePriority-SecondaryPUCCHgroup-r17 ENUMERATED {enabled} OPTIONAL -- Cond twoPUCCHgroup ]], [[ ncr-RNTI-r18 RNTI-Value OPTIONAL, -- Cond NCR cellDTRX-DCI-config-r18 SetupRelease { CellDTRX-DCI-config-r18 } OPTIONAL -- Need M ]] } PDSCH-HARQ-ACK-EnhType3-r17 ::= SEQUENCE { pdsch-HARQ-ACK-EnhType3Index-r17 PDSCH-HARQ-ACK-EnhType3Index-r17, applicable-r17 CHOICE { perCC SEQUENCE (SIZE (1..maxNrofServingCells)) OF INTEGER (0..1), perHARQ SEQUENCE (SIZE (1..maxNrofServingCells)) OF BIT STRING (SIZE (16)) }, pdsch-HARQ-ACK-EnhType3NDI-r17 ENUMERATED {true} OPTIONAL, -- Need R pdsch-HARQ-ACK-EnhType3CBG-r17 ENUMERATED {true} OPTIONAL, -- Need S ..., [[ perHARQ-Ext-r17 SEQUENCE (SIZE (1..maxNrofServingCells)) OF BIT STRING (SIZE (32)) OPTIONAL -- Need R ]] } PDSCH-HARQ-ACK-EnhType3Index-r17 ::= INTEGER (0..maxNrofEnhType3HARQ-ACK-1-r17) PDCCH-BlindDetection ::= INTEGER (1..15) DCP-Config-r16 ::= SEQUENCE { ps-RNTI-r16 RNTI-Value, ps-Offset-r16 INTEGER (1..120), sizeDCI-2-6-r16 INTEGER (1..maxDCI-2-6-Size-r16), ps-PositionDCI-2-6-r16 INTEGER (0..maxDCI-2-6-Size-1-r16), ps-WakeUp-r16 ENUMERATED {true} OPTIONAL, -- Need S ps-TransmitPeriodicL1-RSRP-r16 ENUMERATED {true} OPTIONAL, -- Need S ps-TransmitOtherPeriodicCSI-r16 ENUMERATED {true} OPTIONAL -- Need S } PDSCH-HARQ-ACK-CodebookList-r16 ::= SEQUENCE (SIZE (1..2)) OF ENUMERATED {semiStatic, dynamic} PDCCH-BlindDetectionCA-CombIndicator-r16 ::= SEQUENCE { pdcch-BlindDetectionCA1-r16 INTEGER (1..15), pdcch-BlindDetectionCA2-r16 INTEGER (1..15) } PDCCH-BlindDetection2-r16 ::= INTEGER (1..15) PDCCH-BlindDetection3-r16 ::= INTEGER (1..15) PDCCH-BlindDetection4-r17 ::= INTEGER (1..15) MulticastConfig-r17 ::= SEQUENCE { pdsch-HARQ-ACK-CodebookListMulticast-r17 SetupRelease { PDSCH-HARQ-ACK-CodebookList-r16} OPTIONAL, -- Need M type1CodebookGenerationMode-r17 ENUMERATED { mode1, mode2} OPTIONAL -- Need M } PDCCH-BlindDetectionCA-CombIndicator-r17 ::= SEQUENCE { pdcch-BlindDetectionCA1-r17 INTEGER (1..15) OPTIONAL, -- Need R pdcch-BlindDetectionCA2-r17 INTEGER (1..15) OPTIONAL, -- Need R pdcch-BlindDetectionCA3-r17 INTEGER (1..15) } CellDTRX-DCI-config-r18 ::= SEQUENCE { cellDTRX-RNTI-r18 RNTI-Value, sizeDCI-2-9-r18 INTEGER (1..140) } -- TAG-PHYSICALCELLGROUPCONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,348 | 5.7.3.5 Actions related to transmission of SCGFailureInformation message | The UE shall set the contents of the SCGFailureInformation message as follows: 1> if the UE initiates transmission of the SCGFailureInformation message due to T310 expiry: 2> set the failureType as t310-Expiry; 1> else if the UE initiates transmission of the SCGFailureInformation message due to T312 expiry: 2> set the failureType as other and set the failureType-v1610 as t312-Expiry; 1> else if the UE initiates transmission of the SCGFailureInformation message to provide reconfiguration with sync failure information for an SCG: 2> set the failureType as synchReconfigFailureSCG; 1> else if the UE initiates transmission of the SCGFailureInformation message to provide random access problem indication from SCG MAC: 2> if the random access procedure was initiated for beam failure recovery: 3> set the failureType as other and set the failureType-v1610 as beamFailureRecoveryFailure; 2> else: 3> set the failureType as randomAccessProblem; 1> else if the UE initiates transmission of the SCGFailureInformation message to provide indication from SCG RLC that the maximum number of retransmissions has been reached: 2> set the failureType as rlc-MaxNumRetx; 1> else if the UE initiates transmission of the SCGFailureInformation message due to SRB3 IP check failure: 2> set the failureType as srb3-IntegrityFailure; 1> else if the UE initiates transmission of the SCGFailureInformation message due to Reconfiguration failure of NR RRC reconfiguration message: 2> set the failureType as scg-reconfigFailure; 1> else if the UE initiates transmission of the SCGFailureInformation message due to consistent uplink LBT failures: 2> set the failureType as other and set the failureType-v1610 as scg-lbtFailure; 1> else if connected as an IAB-node and the SCGFailureInformation is initiated due to the reception of a BH RLF indication on BAP entity from the SCG: 2> set the failureType as other and set failureType-v1610 as bh-RLF; 1> else if the UE initiates transmission of the SCGFailureInformation message due to beam failure of the PSCell while the SCG is deactivated: 2> set the failureType as other and set failureType-v1610 as beamFailure; 1> include and set MeasResultSCG-Failure in accordance with 5.7.3.4; 1> for each MeasObjectNR configured by a MeasConfig associated with the MCG, and for which measurement results are available: 2> include an entry in measResultFreqList; 2> if there is a measId configured with the MeasObjectNR and a reportConfig which has rsType set to ssb: 3> set ssbFrequency in measResultFreqList to the value indicated by ssbFrequency as included in the MeasObjectNR; 2> if there is a measId configured with the MeasObjectNR and a reportConfig which has rsType set to csi-rs: 3> set refFreqCSI-RS in measResultFreqList to the value indicated by refFreqCSI-RS as included in the associated measurement object; 2> if a serving cell is associated with the MeasObjectNR: 3> set measResultServingCell in measResultFreqList to include the available quantities of the concerned cell and in accordance with the performance requirements in TS 38.133[ NR; Requirements for support of radio resource management ] [14]; 2> set the measResultNeighCellList in measResultFreqList to include the best measured cells, ordered such that the best cell is listed first, and based on measurements collected up to the moment the UE detected the failure, and set its fields as follows; 3> ordering the cells with sorting as follows: 4> based on SS/PBCH block if SS/PBCH block measurement results are available and otherwise based on CSI-RS; 4> using RSRP if RSRP measurement results are available, otherwise using RSRQ if RSRQ measurement results are available, otherwise using SINR; 3> if the UE supports SCG failure information for mobility robustness optimization for conditional PSCell change or addition, for each neighbour cell, if any, included in measResultListNR in measResultFreqList: 4> if the neighbour cell is one of the candidate cells for which the reconfigurationWithSync is included in the secondaryCellGroup in the MCG VarConditionalReconfig (for CPA or inter-SN CPC in NR-DC) or SCG VarConditionalReconfig (for intra-SN CPC) at the moment of the detected SCG failure (radio link failure at PSCell or PSCell change or addition failure): 5> if the first entry of choConfig corresponds to a fulfilled execution condition at the moment of SCG failure; or 5> if the second entry of choConfig, if available, corresponds to a fulfilled execution condition at the moment of SCG failure: 6> set firstTriggeredEvent to the execution condition condFirstEvent corresponding to the first entry of choConfig or to the execution condition condSecondEvent corresponding to the second entry of choConfig, whichever execution condition was fulfilled first in time; 6> set timeBetweenEvents to the elapsed time between the point in time of fulfilling the condition in choConfig that was fulfilled first in time, and the point in time of fulfilling the condition in choConfig that was fulfilled second in time, if both the first execution condition corresponding to the first entry and the second execution condition corresponding to the second entry in the choConfig were fulfilled; 3> for each neighbour cell included: 4> include the optional fields that are available. NOTE 1: The measured quantities are filtered by the L3 filter as configured in the mobility measurement configuration. The measurements are based on the time domain measurement resource restriction, if configured. Exclude-listed cells are not required to be reported. NOTE 2: Field measResultSCG-Failure is used to report available results for NR frequencies the UE is configured to measure by SCG RRC signalling. 1> if available, set the locationInfo as in 5.3.3.7 according to the otherConfig associated with the NR MCG. 1> if the UE supports SCG failure for mobility robustness optimization: 2> if the failureType is set to synchReconfigFailureSCG; or 2> if the failureType is set to randomAccessProblem and the SCG failure was declared while T304 was running: 3> set perRAInfoList to indicate the performed random access procedure related information as specified in 5.7.10.5. 3> set the failedPSCellId to the physical cell identity and carrier frequency of the target PSCell of the failed PSCell change; 3> set the previousPSCellId to the physical cell identity and carrier frequency of the source PSCell associated to the last received RRCReconfiguration message including reconfigurationWithSync for the SCG, if available; 3> set the timeSCGFailure to the elapsed time since the last execution of RRCReconfiguration message including the reconfigurationWithSync for the SCG until declaring the SCG failure; 2> else: 3> set the failedPSCellId to the physical cell identity and carrier frequency of the PSCell in which the SCG failure was declared; 3> if the last RRCReconfiguration message including the reconfigurationWithSync for the SCG was received to enter the PSCell in which the SCG failure was declared: 4> set the timeSCGFailure to the elapsed time since the last execution of RRCReconfiguration message including the reconfigurationWithSync for the SCG until declaring the SCG failure; 4> set the previousPSCellId to the physical cell identity and carrier frequency of the source PSCell associated to the last received RRCReconfiguration message including reconfigurationWithSync for the SCG; 1> release successPSCell-Config configured by the source PSCell, if available. The UE shall submit the SCGFailureInformation message to lower layers for transmission. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.7.3.5 |
5,349 | 5.7.1.11 QoS aspects of home-routed roaming | In the case of home-routed roaming, the V-SMF may apply VPLMN policies related with the SLA negotiated with the HPLMN or with QoS values supported by the VPLMN. Such policies may result in a situation that the V-SMF does not accept the PDU Session or does not accept some of the QoS Flows requested by the H-SMF. QoS constraints represent the QoS that the VPLMN can accept for the QoS Flow associated with the default QoS rule and the PDU Session based on SLA or based on QoS values supported by the VPLMN. The QoS constraints may contain 5QI, 5QI Priority Level and ARP for the QoS Flow associated with the default QoS rule and highest Session-AMBR accepted by the VPLMN. NOTE: For this Release of the specification, QoS constraints apply only to the non-GBR default QoS Flow. At PDU Session Establishment for home-routed roaming, to reduce the risk of PDU Session establishment failure due to QoS from the HPLMN not being compliant with SLA, the V-SMF may provide the VPLMN local policy in QoS constraints to the H-SMF as specified in clause 4.3.2.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. For intra-5GS mobility with V-SMF insertion or V-SMF change (e.g. inter-PLMN mobility), as specified in clause 4.23 of TS 23.502[ Procedures for the 5G System (5GS) ] [3], the new/target V-SMF may validate the currently applied QoS against the QoS constraints. The new/target V-SMF provides QoS constraints to the H-SMF during the mobility procedure. The new/target V-SMF may temporarily accept a higher QoS even if the currently applied QoS exceeds the QoS constraints. Alternatively, for the QoS parameters related with the QoS constraints, the V-SMF may locally downgrade these values before providing the corresponding QoS profiles to 5G AN. The V-SMF may decide to release the PDU Session if the HPLMN does not provide updated QoS compliant with the QoS constraints after the mobility procedure. For IMS voice service (e.g. the IMS DNN defined by the GSMA), the V-SMF, based on local policy, may override the ARP received from HPLMN over N16 if the ARP indicates priority not in line with the local policy in VPLMN. The ARP override in the serving PLMN applies to both the QoS Flow associated with the default QoS rule and the QoS Flows for IMS voice, to apply the same allocation and retention priority for all users (i.e. roamers and non-roamers). For MPS (clause 5.16.5), the same allocation and retention priority is applied to all MPS service users (i.e. roamers and non-roamers), when roaming agreements are in place and where regulatory requirements apply. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.7.1.11 |
5,350 | 13.3.1.3 IPv6 parameter configuration via stateless DHCPv6 | A UE that has obtained an IPv6 address can use stateless DHCP to request other configuration information such as a list of DNS recursive name servers or SIP servers. For 3GPP networks if such IPv6 configuration parameters are locally provisioned in the P-GW, the P-GW returns the requested parameters to the UE via its DHCPv6 server function. For trusted non-3gpp access networks, if such IPv6 configuration parameters are locally provisioned in the P-GW, the P-GW may return the requested parameters to the UE via its DHCPv6 server function or the P-GW may return the IPv6 configuration parameters to the non-3gpp access network and then the non-3GPP access network may send the parameters to the UE via its DHCPv6 server function. When the non-3GPP access network is a trusted WLAN network, the PGW always returns the IPv6 configuration parameters to the TWAN via GTP/PMIP message, and then the TWAN sends the parameters to the UE via its DHCPv6 server function. When an external DHCP6 server in a PDN is used to obtain the requested parameters, which is the use case covered in this subclause, the P-GW acts as a DHCPv6 client towards the external DHCPv6 server while acting a DHCPv6 server towards the UE. The IPv6 parameter configuration via stateles DHCPv6 function in the UE, the P-GW and the external DHCPv6 Server shall be compliant to RFC 3736 [80]. An example signalling flow for the GGSN is described in Subclause 13.2.2. For the P-GW, the signalling flow is same with the following modifications: - For 3GPP access networks, the P-GW sends Router Advertisement for GTP-based S5/S8. In the case of PMIP-based S5/S8, the S-GW sends the Router Advertisement. For trusted non-3GPP access networks, the trusted non-3GPP access network sends the Router Advertisement for PMIP S2a.When the non-3GPP access network is a trusted WLAN network, the TWAN sends the Router Advertisement As stated above, the P-GW acts as a DHCPv6 server towards the UE, while acting as a DHCPv6 client towards the external DHCPv6 server. | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 13.3.1.3 |
5,351 | 5.15.18 Support for Network Slices with Network Slice Area of Service not matching deployed Tracking Areas 5.15.18.1 General | The network support for a Network Slice is defined on a per Tracking Area granularity. It may be beneficial to deploy some Network Slices such that the Network Slice have a limited geographical availability that is not matching existing Tracking Area boundaries. The operator can in this case decide to change the topology of the Tracking Areas so they match the boundaries of the Network Slice, or the operator may configure resources for the Network Slices in the cells of TAs where the Network Slices are to be available, and in areas of the TAs where the network slice is defined to be not available the cells are configured with zero resources. The AMF receives from the OAM the information on availability of a network slice when the granularity is smaller than TA, i.e. if the NS-AoS includes TAs where the network slice is not available in some cells of the TA. In order to optimize the end-to-end behaviour, the AMF can, based on NS-AoS information received from OAM, configure supporting UEs with S-NSSAI location availability information, and the network may need to monitor the S-NSSAI usage and enforce the NS-AoS e.g. if the UE does not support the S-NSSAI location availability information. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.15.18 |
5,352 | 5.3.1 User-to-USIM authentication | This feature provides the property that access to the USIM is restricted until the USIM has authenticated the user. Thereby, it is ensured that access to the USIM can be restricted to an authorised user or to a number of authorised users. To accomplish this feature, user and USIM must share a secret (e.g. a PIN) that is stored securely in the USIM. The user gets access to the USIM only if he/she proves knowledge of the secret. This security feature is implemented by means of the mechanism described in TS 31.101[ UICC-terminal interface; Physical and logical characteristics ] [5]. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 5.3.1 |
5,353 | C.1 Purpose | This annex describes principles that shall be used when the calling MS specifies information during call setup regarding low layer capabilities required in the network and by the destination terminal. Refer also to 3GPP TS 27.001[ General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS) ] [36]. NOTE: In this context and throughout this annex the term "called user" is the end point entity which is explicitly addressed. This may also be an explicitly addressed interworking unit (IWU) (see ITU-T I.500-Series Recommendations and ITU-T Recommendation X.31 case a). | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | C.1 |
5,354 | 4.9.4 OAM aspects | The transport connection between the NCR-node and its OAM may be provided by the NCR-MT's PDU session. A Network-Controlled Repeater may be configured with a list of allowed gNB cell(s) that the NCR-MT is allowed to connect with, and/or a list of forbidden gNB cell(s) that the NCR-MT is not allowed to connect with. The information on the physical beam(s) used by NCR-Fwd for access link may be provided by OAM to the gNB and the Network-Controlled Repeater for operation. How to characterize and provide the physical beams of NCR-Fwd is up to implementation. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 4.9.4 |
5,355 | Annex I (informative): Guidance for contributors to this specification | The following guidance is provided for drafting figures for this specification that contain specific steps which are different in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [2] due to the PMIP-based S5/S8 interface: - Message flows to this specification will contain the complete procedures applicable for GTP-based S5/S8 only. - In this specification, clause(s) of a message flow that is different for PMIP-based S5/S8 interface are shown surrounded by shaded box indexed by an upper-case letter in ascending order, e.g. "A", "B", "C", etc. For example, at the bottom of the flow, the following text should be included: "NOTE: Procedure steps (A) and (B) for an PMIP-based S5/S8 interface are defined in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [2]." - Further guidance for drafting procedures for TS 23.402[ Architecture enhancements for non-3GPP accesses ] [2] can be found in that specification itself. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | Annex |
5,356 | 10.1.6.1 Time and frequency structure | The physical layer random access preamble is based on single-subcarrier frequency-hopping symbol groups. A symbol group is illustrated in Figure 10.1.6.1-1, consisting of a cyclic prefix of length and a sequence of identical symbols with total length. The total number of symbol groups in a preamble repetition unit is denoted by . The number of time-contiguous symbol groups is given by . The parameter values for frame structures 1 and 2 are listed in Tables 10.1.6.1-1 and 10.1.6.1-2, respectively. Figure 10.1.6.1-1: Random access symbol group Table 10.1.6.1-1: Random access preamble parameters for frame structure type 1 Table 10.1.6.1-2: Random access preamble parameters for frame structure type 2 The preamble consisting of symbol groups shall be transmitted times. For frame structure type 2, when an invalid uplink subframe overlaps the transmission of symbol groups without a gap, the symbol groups are dropped. For frame structure type 2, the transmission of symbol groups are aligned with the subframe boundary. The transmission of a random-access preamble, if triggered by the MAC layer, is restricted to certain time and frequency resources. A NPRACH configuration provided by higher layers contains the following: - NPRACH resource periodicity (nprach-Periodicity), - frequency location of the first subcarrier allocated to NPRACH (nprach-SubcarrierOffset), - number of subcarriers allocated to NPRACH (nprach-NumSubcarriers), - number of starting sub-carriers allocated to UE initiated random access (nprach-NumCBRA-StartSubcarriers), - number of NPRACH repetitions per attempt (numRepetitionsPerPreambleAttempt), - NPRACH starting time (nprach-StartTime), - Fraction for calculating starting subcarrier index for the range of NPRACH subcarriers reserved for indication of UE support for multi-tone msg3 transmission (nprach-SubcarrierMSG3-RangeStart). NPRACH transmission can start only time units after the start of a radio frame fulfilling . For frame structure type 1, after transmissions of time units for preamble formats 0 and 1, or time units for preamble format 2, a gap of time units shall be inserted. NPRACH configurations where are invalid. The NPRACH starting subcarriers allocated to UE initiated random access are split in two sets of subcarriers, and , where the second set, if present, indicate UE support for multi-tone msg3 transmission. The frequency location of the NPRACH transmission is constrained within sub-carriers, and within subcarriers when preamble format 2 as described in Table 10.1.6.1-1 is configured. Frequency hopping shall be used within the 12 subcarriers and 36 subcarriers when preamble format 2 as described in Table 10.1.6.1-1 is configured, where the frequency location of the ith symbol group is given by where . The quantity depends on the frame structure. For frame structure type 1: - if , for preamble formats 0 and 1 as described in Table 10.1.6.1-1: where with being the subcarrier selected by the MAC layer from , and the pseudo random sequence is given by clause 7.2. The pseudo random sequence generator shall be initialised with . - if , for preamble format 2 as described in Table 10.1.6.1-1: where with being the subcarrier selected by the MAC layer from , and the pseudo random sequence is given by clause 7.2. The pseudo random sequence generator shall be initialised with . For frame structure type 2: - if , for preamble formats 0, 1, and 2 as described in Table 10.1.6.1-2: where with being the subcarrier selected by the MAC layer from , and the pseudo random sequence is given by clause 7.2. The pseudo random sequence generator shall be initialised with . - if , for preamble formats 0-a, 1-a, as described in Table 10.1.6.1-2: where with being the subcarrier selected by the MAC layer from , and the pseudo random sequence is given by clause 7.2. The pseudo random sequence generator shall be initialised with . | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 10.1.6.1 |
5,357 | 13.2 Application layer security on the N32 interface 13.2.1 General | The internetwork interconnect allows secure communication between service-consuming and a service-producing NFs in different PLMNs. Security is enabled by the Security Edge Protection Proxies of both networks, henceforth called cSEPP and pSEPP respectively. The SEPPs enforce protection policies regarding application layer security thereby ensuring integrity and confidentiality protection for those elements to be protected. It is assumed that there are interconnect providers between cSEPP and pSEPP. The interconnect provider the cSEPP's operator has a business relationship with is called cIPX, while the interconnect provider the pSEPP's operator has a business relationship with is called pIPX. There could be further interconnect providers in between cIPX and pIPX, but they are assumed to be transparent and simply forward the communication. The SEPPs use JSON Web Encryption (JWE, specified in RFC 7516 [59]) for protecting messages on the N32-f interface, and the IPX providers use JSON Web Signatures (JWS, specified in RFC 7515 [45]) for signing their modifications needed for their mediation services. For illustration, consider the case where a service-consuming NF sends a message to a service-producing NF. If this communication is across PLMN operators over the N32-f interface, as shown in Figure 13.2.1-1 below, the cSEPP receives the message and applies symmetric key based application layer protection, as defined in clause 13.2 of the present document. The resulting JWE object is forwarded to intermediaries. The pIPX and cIPX can offer services that require modifications of the messages transported over the interconnect (N32) interface. These modifications are appended to the message as digitally signed JWS objects which contain the desired changes. The pSEPP, which receives the message from pIPX, validates the JWE object, extracts the original message sent by the NF, validates the signature in the JWS object and applies patches corresponding to the modifications by intermediaries. The pSEPP then forwards the message to the destination NF. The N32 interface consists of: - N32-c connection, for management of the N32 interface, and - N32-f connection, for sending of JWE and JWS protected messages between the SEPPs. The application layer security protocol for the N32 interface described in clause 13.2 of the present document is called PRINS. Figure 13.2.1-1: Overview of PRINS | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 13.2 |
5,358 | 5.3.8.3A SGSN-initiated Detach procedure with ISR activated | The SGSN-Initiated Detach procedure with ISR activated is illustrated in Figure 5.3.8.3A-1. Refer to clause 6.6.2.1 of TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7] for the SGSN-initiated Detach procedure when ISR is not activated. Figure 5.3.8.3A-1: SGSN-Initiated Detach Procedure with ISR activated NOTE 1: For a PMIP-based S5/S8, procedure steps (A) are defined in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [2]. Steps 3, 4 and 5 concern GTP based S5/S8. 1. The SGSN initiated detach procedure is either explicit (e.g. by O&M intervention) or implicit. The SGSN may implicitly detach a UE, if it has not had communication with UE for a long period of time. The SGSN does not send the Detach Request (Detach Type) message to the UE for implicit detach. The implicit detach is local to the SGSN, i.e. an MME registration will not be detached. If the UE is in PMM-CONNNECTED state the SGSN may explicitly detach the UE by sending a Detach Request message to the UE. The Detach Type may be set to re-attach in which case the UE should re-attach at the end of the detach process. If the UE is in PMM-IDLE state the SGSN pages the UE. If this Detach procedure is due to the UE's Detach Request via a CSG cell which the UE is not allowed to access, i.e. the CSG subscription for this CSG ID and associated PLMN is absent or expired, the SGSN shall send a Detach Request to UE with an appropriate cause indicating the UE is not allowed to access this CSG. 2. Any EPS Bearer Context information in the Serving GW regarding this particular UE and related to the SGSN is deactivated by the SGSN sending Delete Session Request (LBI, User Location Information (ECGI)) message per PDN connection to the Serving GW. If the UE Time Zone has changed, the SGSN includes the UE Time Zone IE in this message. 3. Because the Serving GW receives this message in ISR activated state, the Serving GW deactivates ISR, releases the SGSN related EPS Bearer context information and acknowledges with Delete Session Response (Cause). 4. Because ISR is activated, the SGSN sends Detach Notification (Cause) message to the associated MME. The cause indicates whether it is a local or complete detach. 5. If cause indicates complete detach then the MME sends a Delete Session Request (LBI, User Location Information (ECGI)) message per PDN connection to the Serving GW. If Cause indicates local detach then MME deactivates ISR and steps 5 to 9 shall be skipped. If the UE Time Zone has changed, the MME includes the UE Time Zone IE in this message. 6. The Serving GW sends a Delete Session Request (LBI, User Location Information (ECGI or CGI/SAI)) message per PDN connection to the PDN GW. This message indicates that all bearers belonging to that PDN connection shall be released. If the MME and/or SGSN sends UE's Location Information and/or UE Time Zone in step 2 and/or step 5, the S-GW includes the User Location Information and/or UE Time Zone Information with the least age in this message. 7. The PDN GW acknowledges with Delete Session Response (Cause) message. 8. The PDN GW employs an IP CAN Session Termination procedure as defined in TS 23.203[ Policy and charging control architecture ] [6] with the PCRF to indicate to the PCRF that the EPS Bearer(s) are released if a PCRF is configured. If requested by the PCRF the PDN GW indicates User Location Information and/or UE Time Zone Information to the PCRF as defined in TS 23.203[ Policy and charging control architecture ] [6]. 9. The Serving GW acknowledges with Delete Session Response (Cause) message. 10. The MME sends Detach Acknowledge message to the SGSN. 11. If the UE receives the Detach Request message from the SGSN in the step 1, the UE sends a Detach Accept message to the SGSN any time after step 1. If the UE receives Detach Request from the SGSN via a CSG cell with the cause indicating the UE is not allowed to access this CSG, the UE shall remove this CSG ID and associated PLMN from its Allowed CSG list, if present. 12. After receiving the Detach Accept message, if Detach Type did not request the UE to make a new attach, then the 3G SGSN releases the PS signalling connection. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.3.8.3A |
5,359 | J.3 ISR activation | The information flow in Figure J.3-1 shows an example of ISR activation. For explanatory purposes the figure is simplified to show the MM parts only. The process starts with an ordinary Attach procedure not requiring any special functionality for support of ISR. The Attach however deletes any existing old ISR state information stored in the UE. With the Attach request message, the UE sets its TIN to "GUTI". After attach with MME, the UE may perform any interactions via E-UTRAN without changing the ISR state. ISR remains deactivated. One or more bearer contexts are activated on MME, Serving GW and PDN GW, which is not shown in the figure. The first time the UE reselects GERAN or UTRAN it initiates a Routing Area Update. This represents an occasion to activate ISR. The TIN indicates "GUTI" so the UE indicates a P-TMSI mapped from a GUTI in the RAU Request. The SGSN gets contexts from MME. When the MME sends the context to the SGSN, the MME includes the ISR supported indication only if the involved S-GW supports the ISR. After the ISR activated, both CN nodes keep these contexts because ISR is being activated. The SGSN establishes a control relation with the Serving GW, which is active in parallel to the control connection between MME and Serving GW (not shown in figure). The RAU Accept indicates ISR activation to the UE. The UE keeps GUTI and P-TMSI as registered, which the UE memorises by setting the TIN to "RAT-related TMSI". The MME and the SGSN are registered in parallel with the HSS. After ISR activation, the UE may reselect between E-UTRAN and UTRAN/GERAN without any need for updating the network as long as the UE does not move out of the RA/TA(s) registered with the network. The network is not required to activate ISR during a RAU or TAU. The network may activate ISR at any RAU or TAU that involves the context transfer between an SGSN and an MME. The RAU procedure for this is shown in Figure J.3-1. ISR activation for a UE, which is already attached to GERAN/UTRAN, with a TAU procedure from E-UTRAN works in a very similar way. Figure J.3-1: ISR Activation example | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | J.3 |
5,360 | 5.5.1.5 Determining virtual cell identity for sequence generation | The definition of depends on the type of transmission. Transmissions associated with PUSCH: - if no value for is configured by higher layers or if the PUSCH transmission corresponds to a Random Access Response Grant or a retransmission of the same transport block as part of the contention based random access procedure, - otherwise. Transmissions associated with SPUCCH/PUCCH: - if no value for is configured by higher layers, - otherwise. Basic sounding reference signals: - if the higher-layer parameter srs-VirtualCellID is configured and srs-VirtualCellID-AllSRS is configured as TRUE, where equals the higher-layer parameter srs-VirtualCellID - otherwise. Additional sounding reference signals: - if no value for is configured by the higher-layer parameter srs-VirtualCellID - otherwise. | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.5.1.5 |
5,361 | 5.3.13 Lists of 5GS forbidden tracking areas | If the UE is not operating in SNPN access operation mode, the UE shall store a list of "5GS forbidden tracking areas for roaming", as well as a list of "5GS forbidden tracking areas for regional provision of service". Otherwise the UE shall store a list of "5GS forbidden tracking areas for roaming": - per SNPN; and - if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, per entry of the "list of subscriber data" or, if the UE supports access to an SNPN using credentials from a credentials holder, PLMN subscription; and store a list of "5GS forbidden tracking areas for regional provision of service": - per SNPN; and - if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, per entry of the "list of subscriber data" or, if the UE supports access to an SNPN using credentials from a credentials holder, PLMN subscription. Within the 5GS, these lists are managed independently per access type, i.e., 3GPP access or wireline access. These lists shall be erased when: a) the UE is switched off, the UICC containing the USIM is removed, an entry of the "list of subscriber data" with the subscribed SNPN identity identifying the current SNPN is updated or, if the UE supports access to an SNPN using credentials from a credentials holder, the entry of the "list of subscriber data" associated with the lists is updated; and b) periodically (with a period in the range 12 to 24 hours). Over 3GPP access, when the lists are erased, the UE performs cell selection according to 3GPP TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [28] or 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [25C]. If the UE is not operating in SNPN access operation mode a tracking area shall be removed from the list of "5GS forbidden tracking areas for roaming", as well as the list of "5GS forbidden tracking areas for regional provision of service", if the UE receives the tracking area in the TAI list or the Service area list of "allowed tracking areas" in REGISTRATION ACCEPT message or a CONFIGURATION UPDATE COMMAND message. The UE operating in SNPN access operation mode shall remove a tracking area from the list of "5GS forbidden tracking areas for roaming" as well as the list of "5GS forbidden tracking areas for regional provision of service" for: - the selected SNPN; and - when the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, for the selected entry of the "list of subscriber data" or, when the UE supports access to an SNPN using credentials from a credentials holder, the selected PLMN subscription; if the UE receives the tracking area in the TAI list or the Service area list of "allowed tracking areas" in REGISTRATION ACCEPT message or a CONFIGURATION UPDATE COMMAND message. The UE shall not remove the tracking area from "5GS forbidden tracking areas for roaming" or "5GS forbidden tracking areas for regional provision of service" if the UE is registered for emergency services. In N1 mode over 3GPP access, the UE shall update the suitable list whenever a REGISTRATION REJECT, SERVICE REJECT or DEREGISTRATION REQUEST message is received with the 5GMM cause #12 "tracking area not allowed", #13 "roaming not allowed in this tracking area", #15 "no suitable cells in tracking area", or #62 "no network slices available". In N1 mode over 3GPP access, if the UE receives the "5GS forbidden tracking areas for roaming" IE or the "5GS forbidden tracking areas for regional provision of service" IE in the REGISTRATION REJECT, SERVICE REJECT, DEREGISTRATION REQUEST, REGISTRATION ACCEPT or SERVICE ACCEPT message, the UE update the suitable list with the received TAI(s) belonging to the serving PLMN or equivalent PLMN(s) and ignore the TAI(s) which do not belong to the serving PLMN or equivalent PLMN(s) included in the IE. If the UE receives ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message provided with S-NSSAI and the PLMN ID in the Protocol configuration options IE or Extended protocol configuration options IE (see subclause 6.5.1.3 of 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]), the UE may remove the corresponding tracking area from the "5GS forbidden tracking areas for roaming". Over wireline access, the 5G-RG, the W-AGF acting on behalf of an FN-RG or the W-AGF acting on behalf of an N5GC device shall update the suitable list whenever a REGISTRATION REJECT, SERVICE REJECT or DEREGISTRATION REQUEST message is received with the 5GMM cause #12 "tracking area not allowed" or #13 "roaming not allowed in this tracking area". NOTE: In this release of the specification, for untrusted non-3GPP access and trusted non-3GPP access, neither the list of "5GS forbidden tracking areas for roaming" nor the list of "5GS forbidden tracking areas for regional provision of service" is maintained by the UE since the UE is not able to determine the corresponding TAI. Each list shall accommodate 40 or more TAIs. When the list is full and a new entry has to be inserted, the oldest entry shall be deleted. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.3.13 |
5,362 | 5.27.1.9 Support for derivation of Uu time synchronization error budget | The AF may request a specific time synchronization error budget when requesting a time synchronization service employing the (g)PTP-based or 5G access stratum-based time distribution method. If the AF includes a time synchronization error budget in its request, the TSCTSF uses it to derive an error budget available for the NG-RAN to provide the 5G access stratum time via the Uu interface to each targeted UE (referred to as Uu time synchronization error budget hereafter). The Time Synchronization Subscription data may optionally contain the authorized Uu time synchronization error budget. When the TSCTSF receives an AF request with a specific time synchronization error budget for the time synchronization service, the TSCTSF validates the Uu time synchronization error budget as described in clause 5.27.1.11. To derive the Uu time synchronization error budget for each targeted UE, the TSCTSF takes the following into account: - selected time synchronization distribution method (i.e. 5G access stratum-based time distribution or (g)PTP-based time distribution); - Uu time synchronization error budget in the Time Synchronization Subscription data defined in clause 5.27.1.11; - in the case of the (g)PTP-based time distribution: - whether 5GS operates as a boundary clock and acts as a GM; - whether a clock connected to the DS-TT/NW-TT acts as a GM; - PTP port states; - a CN part and a Device part of the time synchronization error budget (both parts may be predefined at the TSCTSF, or calculated by the 5GS using the implementation-specific means). If the AF does not include a time synchronization error budget, the TSCTSF uses a preconfigured time synchronization error budget to derive the Uu time synchronization error budget. TheTSCTSF provides a 5G access stratum time distribution indication and the derived Uu time synchronization error budget to NG-RAN as described in clause 4.15.9.4 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. Based on this, NG-RAN provides the 5G access stratum time to the UE according to the Uu interface time synchronization error budget as provided by the TSCTSF (if supported by UE and NG-RAN). During Handover, Service Request, mobility registration and AM policy modification procedure, the AMF may provide the 5G access stratum time distribution indication and the Uu time synchronization error budget to NG-RAN as described in clause 4.15.9.4 of TS 23.502[ Procedures for the 5G System (5GS) ] [3], if needed. NOTE: This release of the specification assumes that deployments ensure that the targeted UEs and the NG-RAN nodes serving those UEs support Rel-17 propagation delay compensation as defined in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.27.1.9 |
5,363 | 6.12.3 Subscription temporary identifier | A new 5G-GUTI shall be sent to a UE only after a successful activation of NAS security. The 5G-GUTI is defined in TS 23.003[ Numbering, addressing and identification ] [19]. Upon receiving Registration Request message of type "initial registration" or "mobility registration update" from a UE, the AMF shall send a new 5G-GUTI to the UE in the registration procedure. Upon receiving Registration Request message of type "periodic registration update" from a UE, the AMF should send a new 5G-GUTI to the UE in the registration procedure. Upon receiving Service Request message sent by the UE in response to a Paging message, the AMF shall send a new 5G-GUTI to the UE. This new 5G-GUTI shall be sent before the current NAS signalling connection is released or the N1 NAS signalling connection is suspended. Upon receiving an indication from the lower layers that the RRC connection has been resumed for a UE in 5GMM-IDLE mode with suspend indication in response to a Paging message, the AMF shall send a new 5G-GUTI to the UE. This new 5G-GUTI shall be sent before the current NAS signalling connection is released or the suspension of the N1 NAS signalling connection. NOTE 1: It is left to implementation to re-assign 5G-GUTI more frequently than in cases mentioned above, for example after a Service Request message from the UE not triggered by the network. NOTE 2: It is left to implementation to generate 5G-GUTI containing 5G-TMSI that uniquely identifies the UE within the AMF. 5G-TMSI generation should be following the best practices of unpredictable identifier generation. A new I-RNTI shall be sent to a UE only after a successful activation of AS security. On transition of UE to RRC INACTIVE state requested by gNB during RRC Resume procedure or RNAU procedure, the gNB shall assign a new I-RNTI to the UE. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.12.3 |
5,364 | 15.5.2.8 Successful PSCell Addition/Change Report | For the analysis of successful PSCell addition/change, the UE supports Successful PSCell Addition/Change Report (SPR) based on the configuration by network, if received, and makes the SPR available to the network as specified in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12]. The UE stores the SPR until the SPR is fetched by the network or for 48 hours after the SPR is recorded. The UE makes the SPR available to gNB(s). When a gNB fetches the SPR from UE, it forwards the SPR to the MN that was serving the UE at the time the SPR was generated by using the ACCESS AND MOBILITY INDICATION message over Xn or by means of the Uplink RAN configuration transfer procedure and Downlink RAN configuration transfer over NG. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 15.5.2.8 |
5,365 | 5.3.13.1d RRC connection resume for multicast reception | In RRC_INACTIVE state, if configured with MBS multicast reception in RRC_INACTIVE, the UE shall: 1> if the RRC connection resume procedure is triggered for multicast reception at reception of SIB1, as specified in 5.2.2.4.2; or 1> if the PTM configuration is not available in the cell after cell selection or reselection for a multicast session that the UE has joined for which the UE is not indicated to stop monitoring the G-RNTI; or 1> if mbs-NeighbourCellList acquired in the previous cell indicates that a multicast session that the UE has joined for which the UE is not indicated to stop monitoring the G-RNTI is not provided for RRC_INACTIVE in the current serving cell; or 1> if the measured RSRP or RSRQ for serving cell as specified in TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [20] is below the threshold indicated by thresholdIndex for a multicast session that the UE has joined: 2> initiate RRC connection resume procedure in 5.3.13.2 with resumeCause set to mt-Access. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.13.1d |
5,366 | 6.2.8 Handling of S-NSSAI based congestion control | The network may detect and start performing S-NSSAI based congestion control when one or more S-NSSAI congestion criteria as specified in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8] are met. If the UE does not provide a DNN for a non-emergency PDU session, then the network uses the selected DNN. If the UE does not provide an S-NSSAI for a non-emergency PDU session, then the network uses the selected S-NSSAI. In case of PLMN or SNPN, in the UE, 5GS session management timers T3584 for the S-NSSAI based congestion control are started and stopped on a per S-NSSAI, DNN and PLMN or SNPN basis. If the 5GSM congestion re-attempt indicator IE with the ABO bit set to "The back-off timer is applied in all PLMNs or equivalent SNPNs " is included in the 5GSM message with the 5GSM cause value #67 "insufficient resources for specific slice and DNN", then the UE applies the timer T3584 for all the PLMNs or all the equivalent SNPNs. Otherwise, the UE applies the timer T3584 for the registered PLMN or the registered SNPN. If the timer T3584 applies for all the PLMNs or all the equivalent SNPNs, the timer T3584 starts when the UE is registered in a VPLMN or an unsubscribed SNPN and the S-NSSAI is provided by the UE during the PDU session establishment, the timer T3584 is associated with the [mapped S-NSSAI, DNN] combination of the PDU session. In case of PLMN or SNPN, in the UE, 5GS session management timers T3585 for the S-NSSAI based congestion control are started and stopped on a per S-NSSAI and PLMN or SNPN basis. If the 5GSM congestion re-attempt indicator IE with the ABO bit set to "The back-off timer is applied in all PLMNs or all equivalent SNPNs " is included in the 5GSM message with the 5GSM cause value #69 "insufficient resources for specific slice", then the UE applies the timer T3585 for all the PLMNs or all the equivalent SNPNs. Otherwise, the UE applies the timer T3585 for the registered PLMN or registered SNPN. If the timer T3585 applies for all the PLMNs or all the equivalent SNPNs, the timer T3585 starts when the UE is registered in a VPLMN or an unsubscribed SNPN and the S-NSSAI is provided by the UE during the PDU session establishment, the timer T3585 is associated with the mapped S-NSSAI of the PDU session. Additionally, if the 5GSM congestion re-attempt indicator IE with the CATBO bit set to "The back-off timer is applied in the current access type" is included in the 5GSM message with the 5GSM cause value #69 "insufficient resources for specific slice", then the UE applies the timer T3585 for the current access type. Otherwise, the UE applies the timer T3585 for both 3GPP access type and non-3GPP access type and the UE shall stop any running timer T3585 for the applied PLMN or SNPN and for the access different from the access from which the message is received. In case of SNPN, if the UE does not support access to an SNPN using credentials from a credentials holder and equivalent SNPNs, in the UE 5GS session management timers T3584 for the S-NSSAI based congestion control are started and stopped on a per S-NSSAI, DNN and SNPN basis. If the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, in the UE 5GS session management timers T3584 for the S-NSSAI based congestion control are started and stopped on a per S-NSSAI, DNN, SNPN and selected entry of the "list of subscriber data" or selected PLMN subscription basis. In case of SNPN, if the UE does not support access to an SNPN using credentials from a credentials holder and equivalent SNPNs, in the UE 5GS session management timers T3585 for the S-NSSAI based congestion control are started and stopped on a per S-NSSAI and SNPN basis. If the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, in the UE 5GS session management timers T3585 for the S-NSSAI based congestion control are started and stopped on a per S-NSSAI, SNPN and selected entry of the "list of subscriber data" or selected PLMN subscription basis. If the timer T3584 or timer T3585 was provided during the PDU session establishment procedure, the S-NSSAI associated with T3584 or T3585, respectively is the S-NSSAI, including no S-NSSAI, provided by the UE during the PDU session establishment. If the timer T3584 is provided during the PDU session modification or PDU session release procedure, the UE behaves as follows: The DNN associated with T3584 is the DNN provided by the UE during the PDU session establishment. If no S-NSSAI but DNN is provided by the UE along the PDU SESSION ESTABLISHMENT REQUEST message, then T3584 is associated with no S-NSSAI and the DNN provided to the network during the PDU session establishment. If the PDN connection was established when in the S1 mode, then T3584 is associated with no S-NSSAI. If no DNN but S-NSSAI is provided by the UE along the PDU SESSION ESTABLISHMENT REQUEST message, then T3584 is associated with no DNN and the S-NSSAI of the PDU session. If no DNN and no S-NSSAI is provided by the UE along the PDU SESSION ESTABLISHMENT REQUEST message, then T3584 is associated with no DNN and no S-NSSAI. For this purpose, the UE shall memorize the DNN and the S-NSSAI provided to the network during the PDU session establishment. The timer T3584 associated with no DNN and an S-NSSAI will never be started due to any 5GSM procedure related to an emergency PDU session. If the timer T3584 associated with no DNN and an S-NSSAI is running, it does not affect the ability of the UE to request an emergency PDU session. If the timer T3585 was provided during the PDU session modification or PDU session release procedure, the UE behaves as follows: if an S-NSSAI was provided by the UE during the PDU session establishment, then T3585 is associated with the S-NSSAI of the PDU session. If no S-NSSAI is provided by the UE along the PDU SESSION ESTABLISHMENT REQUEST message, then T3585 is associated with no S-NSSAI. If the PDN connection was established when in the S1 mode, then T3585 is associated with no S-NSSAI. If T3584 is running or is deactivated, then the UE is not allowed to initiate the: a) PDU session establishment procedure; b) PDU session modification procedure; or c) NAS transport procedure for sending CIoT user data; for the respective [S-NSSAI, no DNN] or [S-NSSAI, DNN] combination unless the UE is a UE configured for high priority access in selected PLMN or SNPN or to report a change of 3GPP PS data off UE status. In a PLMN, if the timer T3584 is running or is deactivated for all the PLMNs and is associated with an S-NSSAI other than no S-NSSAI, then a) the UE registered in the HPLMN is not allowed to initiate the: 1) PDU session establishment procedure; 2) PDU session modification procedure; or 3) NAS transport procedure for sending CIoT user data; when the [S-NSSAI, no DNN] or [S-NSSAI, DNN] combination provided by the UE during the PDU session establishment is the same as the [S-NSSAI, no DNN] or [S-NSSAI, DNN] combination associated with the timer T3584 unless the UE is a UE configured for high priority access in selected PLMN or to report a change of 3GPP PS data off UE status; and b) the UE registered in a VPLMN is not allowed to initiate the: 1) PDU session establishment procedure; 2) PDU session modification procedure; or 3) NAS transport procedure for sending CIoT user data; when the [mapped S-NSSAI, no DNN] or [mapped S-NSSAI, DNN] combination provided by the UE during the PDU session establishment is the same as the [S-NSSAI, no DNN] or [S-NSSAI, DNN] combination associated with the timer T3584 unless the UE is a UE configured for high priority access in selected PLMN or to report a change of 3GPP PS data off UE status. In a PLMN, if the timer T3584 is running or is deactivated for all the PLMNs and is associated with [no S-NSSAI, no DNN] or [no S-NSSAI, DNN] combination, then the UE is not allowed to initiate the: a) PDU session establishment procedure; b) PDU session modification procedure; or c) NAS transport procedure for sending CIoT user data; for [no S-NSSAI, no DNN] or [no S-NSSAI, DNN] combination in any PLMN unless the UE is a UE configured for high priority access in selected PLMN or to report a change of 3GPP PS data off UE status. In an SNPN, if the UE supports equivalent SNPNs, the timer T3584 is running or is deactivated for all the equivalent SNPNs, is associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, with an S-NSSAI other than no S-NSSAI, and with the RSNPN or an equivalent SNPN: a) the UE registered in the subscribed SNPN is not allowed to initiate the: 1) PDU session establishment procedure; or 2) PDU session modification procedure; when the [S-NSSAI, no DNN] or [S-NSSAI, DNN] combination provided by the UE during the PDU session establishment is the same as the [S-NSSAI, no DNN] or [S-NSSAI, DNN] combination associated with the timer T3584 unless the UE is a UE configured for high priority access in the RSNPN or to report a change of 3GPP PS data off UE status; and b) the UE registered in a non-subscribed is not allowed to initiate the: 1) PDU session establishment procedure; or 2) PDU session modification procedure; when the [mapped S-NSSAI, no DNN] or [mapped S-NSSAI, DNN] combination provided by the UE during the PDU session establishment is the same as the [S-NSSAI, no DNN] or [S-NSSAI, DNN] combination associated with the timer T3584 unless the UE is a UE configured for high priority access in RSNPN or to report a change of 3GPP PS data off UE status. In an SNPN, if the UE supports equivalent SNPNs, the timer T3584 is running or is deactivated for all the equivalent SNPNs, is associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, with [no S-NSSAI, no DNN] or [no S-NSSAI, DNN] combination, and with the RSNPN or an equivalent SNPN, then the UE is not allowed to initiate the: a) PDU session establishment procedure; or b) PDU session modification procedure; for [no S-NSSAI, no DNN] or [no S-NSSAI, DNN] combination unless the UE is a UE configured for high priority access in the RSPN or to report a change of 3GPP PS data off UE status. If T3585 is running or is deactivated, then the UE is neither allowed to initiate the PDU session establishment procedure nor the PDU session modification procedure for the respective S-NSSAI unless the UE is a UE configured for high priority access in selected PLMN or SNPN or to report a change of 3GPP PS data off UE status. In a PLMN, if the timer T3585 is running or is deactivated for all the PLMNs and is associated with an S-NSSAI other than no S-NSSAI, then a) the UE registered in the HPLMN is not allowed to initiate the: 1) PDU session establishment procedure; 2) PDU session modification procedure; or 3) NAS transport procedure for sending CIoT user data; when the S-NSSAI provided by the UE during the PDU session establishment is the same as the S-NSSAI associated with timer T3585 unless the UE is a UE configured for high priority access in selected PLMNs or to report a change of 3GPP PS data off UE status; and b) the UE registered in a VPLMN is not allowed to initiate the: 1) PDU session establishment procedure; 2) PDU session modification procedure; or 3) NAS transport procedure for sending CIoT user data; when the mapped S-NSSAI provided by the UE during the PDU session establishment is the same as the S-NSSAI associated the timer T3585 unless the UE is a UE configured for high priority access in selected PLMN or to report a change of 3GPP PS data off UE status. In a PLMN, if the timer T3585 is running or is deactivated for all the PLMNs and is associated with no S-NSSAI, then the UE is not allowed to initiate the: a) PDU session establishment procedure; b) PDU session modification procedure; c) NAS transport procedure for sending CIoT user data; for no S-NSSAI in any PLMN unless the UE is a UE configured for high priority access in selected PLMN or to report a change of 3GPP PS data off UE status.In an SNPN, if the UE supports equivalent SNPNs, the timer T3585 is running or is deactivated for all the equivalent SNPNs, is associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, with an S-NSSAI other than no S-NSSAI, and with the RSNPN or an equivalent SNPN: a) the UE registered in the subscribed SNPN is not allowed to initiate the: 1) PDU session establishment procedure; or 2) PDU session modification procedure; when the S-NSSAI provided by the UE during the PDU session establishment is the same as the S-NSSAI associated with timer T3585 unless the UE is a UE configured for high priority access in the RSNPN or to report a change of 3GPP PS data off UE status; and b) the UE registered in a non-subscribed SNPN is not allowed to initiate the: 1) PDU session establishment procedure; or 2) PDU session modification procedure; when the mapped S-NSSAI provided by the UE during the PDU session establishment is the same as the S-NSSAI associated the timer T3585 unless the UE is a UE configured for high priority access in the RSNPN or to report a change of 3GPP PS data off UE status. In an SNPN, if the UE supports equivalent SNPNs, the timer T3585 is running or is deactivated for all the equivalent SNPNs, is associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, with no S-NSSAI, and with the RSNPN or an equivalent SNPN, then the UE is not allowed to initiate the: a) PDU session establishment procedure; or b) PDU session modification procedure; for no S-NSSAI unless the UE is a UE configured for high priority access in RSNPN or to report a change of 3GPP PS data off UE status. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.2.8 |
5,367 | 7.7.3 GTP Message of Invalid Length | If a GTP entity receives a message, which is too short to contain the respective GTPv2 header, the GTP-PDU shall be silently discarded. Apart from a piggybacked GTP message or an Echo Request message, if a GTP entity receives a Request message within an IP/UDP packet of a length that is inconsistent with the value specified in the Length field of the GTP header, then the receiving GTP entity should log the error and shall send the Response message with Cause IE value set to "Invalid Length". Apart from a piggybacked GTP message, if a GTP entity receives a Response message within an IP/UDP packet of a length that is inconsistent with the value specified in the Length field of the GTP header, then the receiving GTP entity should log the error and shall silently discard the message. If a GTP entity receives two GTP messages (triggered response message and a piggybacked initial message) within an IP/UDP packet of a length that is inconsistent with the total length of the two concatenated messages as indicated by Length fields of the GTP headers, then the receiving GTP entity should log the error and return an appropriate Response message with Cause IE value set to "Invalid overall length of the triggered response message and a piggybacked initial message". That is: - for a Create Session Response message together with a piggybacked Create Bearer Request message, a Create Bearer Response message should be returned with the above Cause value. - for a Create Bearer Response message together with a piggybacked Modify Bearer Request message, a Modify Bearer Response message should be returned with the above Cause value. | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 7.7.3 |
5,368 | 5.17.2.2.2 Mobility for UEs in single-registration mode | When the UE supports single-registration mode and network supports interworking procedure with the N26 interface: - For idle mode mobility from 5GS to EPS, the UE performs either TAU or Attach procedure with EPS GUTI mapped from 5G-GUTI sent as old Native GUTI, as described in clause 4.11.1.3.2.1 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] and indicates that it is moving from 5GC. The UE includes in the RRC message a GUMMEI mapped from the 5G-GUTI and indicates it as a native GUMMEI and should in addition indicate it as "Mapped from 5G-GUTI". The MME retrieves the UE's MM and SM context from 5GC. For connected mode mobility from 5GS to EPS, either inter-system handover or RRC Connection Release with Redirection to E-UTRAN is performed. At inter-system handover, the AMF selects target MME based on 2 octet TAC format used in the Target ID as specified in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [34]. During the TAU or Attach procedure the HSS+UDM cancels any AMF registration associated with the 3GPP access (but not AMF registration associated with the non-3GPP access): an AMF that was serving the UE over both 3GPP and non-3GPP accesses does not consider the UE as deregistered over non 3GPP access. - For the first TAU after 5GC initial Registration, the UE and MME for the handling of UE Radio Capabilities follow the procedures as defined in clause 5.11.2 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [26] for first TAU after GERAN/UTRAN Attach. NOTE 1: MMEs supporting interworking with N26 interface are not required to process the indication from the UE that it is moving from 5GC and will assume that the UE is moving from another MME. - For idle mode mobility from EPC to 5GC, the UE performs mobility Registration procedure with the 5G GUTI mapped from EPS GUTI and indicates that it is moving from EPC. The UE derives GUAMI from the native 5G-GUTI and includes GUAMI in the RRC message to enable RAN to route to the corresponding AMF (if available). If the UE holds no native 5G-GUTI, then the UE provides in the RRC message a GUAMI mapped from the EPS GUTI and indicates it as "Mapped from EPS". The AMF and SMF retrieve the UE's MM and SM context from EPC. For connected mode mobility from EPC to 5GC, either inter-system handover or RRC Connection Release with Redirection to NG-RAN is performed. At inter-system handover, the MME selects target AMF based on TAC used in the Target ID as specified in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [34]. During the Registration procedure, the HSS+UDM cancels any MME registration. NOTE 2: During a transition period, the source eNB may be configured via O&M to know that the MME is not upgraded and thus supports only 2 octet TAC. The Target ID for the NG-RAN node is set as "Target eNB ID" in the existing IEs as defined in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [34]. For both idle mode and connected mode mobility from EPC to 5GC: - The UE includes the native 5G-GUTI as an additional GUTI in the Registration request; the AMF uses the native 5G-GUTI to retrieve MM context identified by the 5G-GUTI from old AMF or from UDSF (if UDSF is deployed and the old AMF is within the same AMF set). - If this is the first mobility event for a PDU Session that was established while being connected to EPC, the UE shall trigger the PDU Session Modification procedure and: - should indicate the support of Reflective QoS to the network (i.e. SMF) if the UE supports Reflective QoS functionality. If the UE indicated support of Reflective QoS, the network may provide a Reflective QoS Timer (RQ Timer) value to the UE; - shall indicate the number of supported packet filters for signalled QoS rules, if the UE supports more than 16 packet filters for the PDU Session. The network shall store this information so that subsequent mobility events do not require another signalling of it. - should indicate the support of Multi-homed IPv6 PDU session to the network (i.e. SMF) if the UE supports Multi-homed IPv6 PDU session. If the UE indicated support of Multi-homed IPv6 PDU session, the network shall consider that this PDU session is supported to use multiple IPv6 prefixes. - should provide the UE Integrity Protection Maximum Data Rate to the network (i.e. SMF). The network shall consider that the maximum data rate per UE for user-plane integrity protection supported by the UE is valid for the lifetime of the PDU session. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.17.2.2.2 |
5,369 | 3.2 Symbols | For the purposes of the present document, the following symbols apply: || Concatenation Å Exclusive or f1 Message authentication function used to compute MAC f1* Message authentication function used to compute MAC-S f2 Message authentication function used to compute RES and XRES f3 Key generating function used to compute CK f4 Key generating function used to compute IK f5 Key generating function used to compute AK in normal procedures f5* Key generating function used to compute AK in re-synchronisation procedures K Long-term secret key shared between the USIM and the AuC | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 3.2 |
5,370 | 6.4.6 Protection of initial NAS message | The initial NAS message is the first NAS message that is sent after the UE transitions from the idle state. The UE shall send a limited set of IEs (called the cleartext IEs) including those needed to establish security in the initial message when it has no NAS security context. When the UE has a NAS security context, the UE shall send a message that has the complete initial NAS message ciphered in a NAS Container along with the cleartext IEs with whole message integrity protected. The complete initial message is included in the NAS Security Mode Complete message in a NAS Container when needed (e.g. AMF cannot find the used security context) in the latter case and always in the former case as described below. In case, the UE selects a PLMN other than Registered PLMN/EPLMN in the 5GMM-IDLE state and the UE has a NAS security context containing the NEA0, then the UE shall discard the NAS security context and shall follow the procedure specified in this clause for protection of initial NAS message. The protection of the initial NAS message proceeds as shown in Figure 6.4.6-1. Figure 6.4.6-1: Protecting the initial NAS message Step 1: The UE shall send the initial NAS message to the AMF. If the UE has no NAS security context, the initial NAS message shall only contain the cleartext IEs, i.e. subscription identifiers (e.g. SUCI or GUTIs), UE security capabilities, ngKSI, indication that the UE is moving from EPC, Additional GUTI, and IE containing the TAU Request in the case idle mobility from LTE. If the UE has a NAS security context, the message sent shall contain the information given above in cleartext and the complete initial NAS message ciphered in a NAS container which is ciphered. With a NAS security context, the sent message shall also be integrity protected. In the case that the initial NAS message was protected and the AMF has the same security context, then steps 2 to 4 may be omitted In this case the AMF shall use the complete initial NAS message that is in the NAS container as the message to respond to.. Step 2: If the AMF is not able to find the security context locally or from last visited AMF, or if the integrity check fails, then the AMF shall initiate an authentication procedure with the UE. If the AMF fetches old security context from the last visited AMF, the AMF may decipher the NAS container with the same security context, and get the initial NAS message, then the step 2b to 4 may be omitted. If the AMF fetches new K AMF from the last visited AMF (receiving keyAmfChangeInd), the step 2b may be omitted. Step 3: If the authentication of the UE is successful, the AMF shall send the NAS Security Mode Command message. If the initial NAS message was protected but did not pass the integrity check (due either to a MAC failure or the AMF not being able to find the used security context) or the AMF could not decrypt the complete initial NAS message in the NAS container (due to receiving "keyAmfChangeInd" from the last visited AMF), then the AMF shall include in the Security Mode Command message a flag requesting the UE to send the complete initial NAS message in the NAS Security Mode Complete message. Step 4: The UE shall send the NAS Security Mode Complete message to the network in response to a NAS Security Mode Command message. The NAS Security Mode Complete message shall be ciphered and integrity protected. Furthermore the NAS Security Mode Complete message shall include the complete initial NAS message in a NAS Container if either requested by the AMF or the UE sent the initial NAS message unprotected. The AMF shall use the complete initial NAS message that is in the NAS container as the message to respond to. Step 5: The AMF shall send its response to the Initial NAS message. This message shall be ciphered and integrity protected. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.4.6 |
5,371 | 6.5.1D Frequency error for ProSe | The UE modulated carrier frequency for ProSe sidelink transmissions shall be accurate to within ±0.1 PPM observed over a period of one time slot (0.5 ms) compared to the carrier frequency received from the synchronization source. The synchronization source can be E-UTRA Node B or a ProSe UE transmitting sidelink synchronization signals. When UE is configured for simultaneous E-UTRA ProSe sidelink and E-UTRA uplink transmissions for inter-band E-UTRA ProSe / E-UTRA bands specified in Table 5.5D-2, the requirements in subclause 6.5.1D apply for ProSe transmission and the requirements in subclause 6.5.1 apply for uplink transmission. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.5.1D |
5,372 | 8.65 Node Type | Node Type is coded as this is depicted in Figure 8.65-1. Figure 8.65-1: Node Type Node type values are specified in Table 8.65-1. Table 8. 65-1: Node Type values If with a Release Access Bearers Request, or Suspend Notification, or Resume an SGW receives a semantically erroneus/unexpected Originating Node, then the following applies: - If SGW has an active connection to an MME, but the Originating Node IE contains value "SGSN", then the SGW shall not release the user plane and shall send a response to the SGSN with some appropriate cause value. - If SGW has an active connection to an S4-SGSN, but the Originating Node IE contains value "MME", then the SGW shall not release the user plane and shall send a response to the MME with some appropriate cause value. | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 8.65 |
5,373 | 4.16.5.2 PCF initiated SM Policy Association Modification | The PCF may initiate SM Policy Association Modification procedure based on internal PCF event or triggered by other peers of the PCF (AF, NWDAF, CHF, UDR and TSCTSF). Figure 4.16.5.2-1: PCF initiated SM Policy Association Modification This procedure may be triggered by a local decision of the PCF or based on triggers from other peers of the PCF (AF, NWDAF, CHF, UDR and TSCTSF): An SM Policy Association is established, with the PCF as described in clause 4.16.4 before this procedure is triggered. For local breakout roaming, the interaction with HPLMN (e.g. step 1b and step 2) is not used. In local breakout roaming, the V-PCF interacts with the UDR of the VPLMN. 1a. Alternatively, optionally, the AF, NEF or TSCTSF provides/revokes service information to the PCF e.g. due to AF session signalling, by invoking Npcf_PolicyAuthorization_Create Request or Npcf_PolicyAuthorization_Update Request or Npcf_PolicyAuthorization_Subscribe Request service operation. The PCF responds to the AF, NEF or TSCTSF. 1b. Alternatively, optionally, the CHF provides a Spending Limit Report to the PCF as described in clause 4.16.8. and responds to the CHF. 1c. Alternatively, optionally, the UDR notifies the PCF about a policy subscription change by invoking Nudr_DM_Notify (Notification correlation Id, Policy Data, SUPI, updated data, "PDU Session Policy Control Data" | "Remaining allowed Usage data"); if the PCF uses the 5G VN group data and subscribes to 5G VN group data change, the UDR notifies the PCF about the 5G VN group data change by invoking Nudr_DM_Notify (Notification correlation Id, Subscription Data, Group Data). The PCF responds to the UDR. 1d. Alternatively, optionally, some internal event (e.g. timer, or local decision based on analytics information requested and received from NWDAF) occurs at the PCF. The analytics (i.e. Analytics ID) which can be requested from NWDAF are described in clause 6.1.1.3 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. 2. If the PCF determines a change to policy counter status reporting is required, it may alter the subscribed list of policy counters using the Initial, Intermediate or Final Spending Limit Report Retrieval procedures as defined in clause 4.16.8. NOTE 1: The PCF ensures that information received in step 1 and 2 can be used by later policy decisions. NOTE 2: For local breakout roaming, PDU Session policy control subscription information and Remaining allowed usage subscription information for monitoring control as defined in clause 6.2.1.3 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20] are not available in V-UDR and V-PCF uses locally configured information according to the roaming agreement with the HPLMN operator. 3. The PCF makes a policy decision. The PCF may determine that updated or new policy information need to be sent to the SMF. In the non-roaming case, the PCF may also decide to subscribe to a new Analytics ID from NWDAF as described in clause 6.1.1.3 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. If the AF provided a Background Data Transfer Reference ID in step 1a, the PCF may retrieve it from the UDR by invoking the Nudr_DM_Query (BDT Reference Id, Policy Data, Background Data Transfer) service. 4. If the PCF has determined that SMF needs updated policy information in step 3 or if the PCF has received a Port Management Information Container for the PDU Session and related port number from the AF or TSCTSF in step 1a, the PCF issues a Npcf_SMPolicyControl_UpdateNotify request with possibly updated policy information about the PDU Session. If the PCF has received a subscription for 5GS Bridge/Router information Notification in Step 1a, the PCF can include a subscription for SMF event for "5GS Bridge/Router information" associated with the PDU Session into the Npcf_SMPolicyControl_UpdateNotify request. In this case, if the SMF has stored the 5GS Bridge/Router information and has not reported the event to the PCF, the SMF notifies the PCF for the event of "5GS Bridge/Router Information ". If the PCF has received a Npcf_PolicyAuthorization_Unsubscribe request to unsubscribe for 5GS Bridge/Router information Notification, the PCF can remove the subscription for SMF event for "5GS Bridge/Router information" associated with the PDU Session and issue a Npcf_SMPolicyControl_UpdateNotify request with the updated policy information about the PDU Session. NOTE 3: If the TSCTSF receives a Requested 5GS delay and the TSCTSF does not have the 5GS Bridge/Router information for the AF-session, the TSCTSF can subscribe for the 5GS Bridge/Router information from the PCF by triggering a Npcf_PolicyAuthorization_Subscribe request. If the PCF has received a subscription to notification on BAT offset along with the TSC Assistance Container from TSCTSF in step 1a, the PCF can include a subscription to notification on BAT offset associated with the PDU Session into the Npcf_SMPolicyControl_UpdateNotify request. 5. The SMF acknowledges the PCF request with a Npcf_SMPolicyControl_UpdateNotify response. If the Npcf_SMPolicyControl_UpdateNotify request is received from new PCF instance in the PCF Set, the SMF store the SM policy association towards the new PCF instance. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.16.5.2 |
5,374 | 6.7.1F Minimum requirement for category NB1 and NB2 | The UE category NB1 and NB2 transmitter intermodulation attenuation is defined by the ratio of the mean power of the wanted signal to the mean power of the intermodulation product as defined in Table 6.7.1F-1 when an interfering CW signal is added at a level below the wanted signal at the transmitter antenna port. Both the wanted signal power and the intermodulation product power are measured through rectangular filter with measurement bandwidth shown in Table 6.7.1F-1. Table 6.7.1F-1: UE category NB1 and NB2 transmitter IM requirement | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.7.1F |
5,375 | 5.10.1 Downlink | After a Semi-Persistent downlink assignment is configured, the MAC entity shall consider sequentially that the Nth assignment occurs in the TTI for which: - subframe SPS is used: - (10 * SFN + subframe) = [(10 * SFNstart time + subframestart time) + N * semiPersistSchedIntervalDL] modulo 10240. - slot or subslot SPS is used: - (10 * SFN * sTTI_Number_Per_Subframe + subframe * sTTI_Number_Per_Subframe + sTTI_number) = [(10 * SFNstart time * sTTI_Number_Per_Subframe + subframestart time * sTTI_Number_Per_Subframe + sTTIStartTimeDl) + N * semiPersistSchedIntervalDL-sTTI] modulo (10240 * sTTI_Number_Per_Subframe). Where SFNstart time, subframestart time and sTTIStartTimeDl are the SFN, subframe and sTTI_number, respectively, at the time the configured downlink assignment were (re-)initialised. The sTTI_Number_Per_Subframe is 6 when subslot TTI is configued and 2 when slot TTI is configured for short TTI operation. sTTI_number refers to the index of the short TTI, i.e., index of subslot or slot within the subframe. For BL UEs or UEs in enhanced coverage SFNstart time and subframestart time refer to SFN and subframe of the first transmission of PDSCH where configured downlink assignment was (re-)initialized. | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.10.1 |
5,376 | 3.8 Structure of an IP v6 address | One or more IP address domains could be allocated to each PLMN. The IP v6 address structure is defined in RFC 2373 [15]. An IP v6 address may be allocated to an MS either permanently or temporarily during a connection with the network If the dynamic IPv6 stateless address autoconfiguration procedure is used, then each PDP context, or group of PDP contexts sharing the same IP address, is assigned a unique prefix as defined in 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [3]. As described in RFC 2462 [21] and RFC 3041 [22], the MS can change its interface identifier without the GPRS network being aware of the change. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 3.8 |
5,377 | – SL-RLC-BearerConfig | The IE SL-RLC-BearerConfig specifies the SL RLC bearer configuration information for NR sidelink communication. SL-RLC-BearerConfig information element -- ASN1START -- TAG-SL-RLC-BEARERCONFIG-START SL-RLC-BearerConfig-r16 ::= SEQUENCE { sl-RLC-BearerConfigIndex-r16 SL-RLC-BearerConfigIndex-r16, sl-ServedRadioBearer-r16 SLRB-Uu-ConfigIndex-r16 OPTIONAL, -- Cond LCH-SetupOnly sl-RLC-Config-r16 SL-RLC-Config-r16 OPTIONAL, -- Cond LCH-Setup sl-MAC-LogicalChannelConfig-r16 SL-LogicalChannelConfig-r16 OPTIONAL, -- Cond LCH-Setup ..., [[ sl-RLC-BearerConfigIndex-v1800 SL-RLC-BearerConfigIndex-v1800 OPTIONAL -- Need S ]] } -- TAG-SL-RLC-BEARERCONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,378 | 12.2.4.3 Elements of APN load control | To allow for an effective APN load control, at least the following information (in addition to the other applicable information for load control as defined in clause 12.2.5.1.2) is required to be advertised by the PGW, as part of the APN level load information: APN: The APN for which the PGW wants to advertise the load information. APN-Load-Metric: It indicates the current resource utilization for a particular APN, as a percentage, compared to the total resources reserved for that APN at the target PGW. Its computation is implementation dependent and it has same characteristics as "Load-Metric", as described in clause 12.2.5.1.2.2, when applied at the APN level. APN-relative-capacity: It indicates the total resources configured for a given APN, compared to the total resources of the target PGW, as a percentage. It is a static parameter and does not change unless the resources configured for the APN change. Using APN-relative-capacity and the DNS weight-factor of the given PGW, the source node can judge the PGW's APN related resources as compared other PGWs in the network, i.e. the PGW's APN-weight-factor can be calculated by multiplying the APN-relative-capacity and DNS-weight-factor of the PGW (PGW's-APN-weight-factor = PGW's-APN-relative-capacity X DNS-weight-factor). For the following example configuration: PGW1-APN1-relative-capacity = 50%; PGW2-APN1- relative-capacity = 20%; PGW3-APN1- relative-capacity = 10% PGW1-weight-factor = 20; PGW2-weight-factor = 20; PGW3-weight-factor = 60; The APN level weight-factor for each of the PGWs can be calculated as below: PGW1-APN1-weight-factor = 50% X 20 = 10. PGW2-APN1-weight-factor = 20% X 20 = 4. PGW3-APN1-weight-factor = 10% X 60 = 6. Thus, based on the APN-weight-factor it can be concluded that the PGW1 has highest APN1 related resources reserved, as compared to the other PGWs in the network. Hence the source node should use this information to favour PGW1 over other PGWs for APN1 related new session requests. | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 12.2.4.3 |
5,379 | 4.7.15 GMM eCall inactivity procedure | The GMM eCall inactivity procedure is applicable only to an eCall only mobile station (as determined by information configured in USIM) that is capable of eCall over IMS and attached for GPRS services. The procedure shall be started when: - the mobile station is in PMM-IDLE mode (Iu mode) or packet idle mode; - the mobile station is in MM IDLE state; - the mobile station is in any GMM-REGISTERED substate except GMM-REGISTERED.NO-CELL-AVAILABLE or GMM-REGISTERED.PLMN-SEARCH; and - one of the following conditions applies: - timer T3242 expires or is found to have already expired and timer T3243 is not running; - timer T3243 expires or is found to have already expired and timer T3242 is not running; or - timers T3242 and T3243 expire or have found to have already expired. The mobile station shall then stop other running timers (e.g. T3311, T3312) and shall: - if the mobile station is also attached for non-GPRS services and the network operates in network operation mode I, perform a combined GPRS detach procedure for GPRS and non-GPRS services; - if the mobile station is also attached for non-GPRS services and the network operates in network operation mode II, perform a GPRS detach procedure for GPRS services and an IMSI detach procedure; and - if the mobile station is not attached for non-GPRS services, perform a GPRS detach procedure for GPRS services. The mobile station shall then enter MM Idle eCALL INACTIVE state, delete any LAI, TMSI, ciphering key sequence number stored in the SIM/USIM, delete any RAI, P-TMSI, P-TMSI signature and GPRS ciphering key sequence number stored, delete any GUTI, TAI list, last visited registered TAI, list of equivalent PLMNs, KSI and set the update state to U4 Updating Disabled. While in eCALL INACTIVE state, the mobile station shall behave as specified in subclause 4.4.7. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.15 |
5,380 | – LocationMeasurementInfo | The IE LocationMeasurementInfo defines the information sent by the UE to the network to assist with the configuration of measurement gaps for location related measurements. LocationMeasurementInfo information element -- ASN1START -- TAG-LOCATIONMEASUREMENTINFO-START LocationMeasurementInfo ::= CHOICE { eutra-RSTD EUTRA-RSTD-InfoList, ..., eutra-FineTimingDetection NULL, nr-PRS-Measurement-r16 NR-PRS-MeasurementInfoList-r16 } EUTRA-RSTD-InfoList ::= SEQUENCE (SIZE (1..maxInterRAT-RSTD-Freq)) OF EUTRA-RSTD-Info EUTRA-RSTD-Info ::= SEQUENCE { carrierFreq ARFCN-ValueEUTRA, measPRS-Offset INTEGER (0..39), ... } NR-PRS-MeasurementInfoList-r16 ::= SEQUENCE (SIZE (1..maxFreqLayers)) OF NR-PRS-MeasurementInfo-r16 NR-PRS-MeasurementInfo-r16 ::= SEQUENCE { dl-PRS-PointA-r16 ARFCN-ValueNR, nr-MeasPRS-RepetitionAndOffset-r16 CHOICE { ms20-r16 INTEGER (0..19), ms40-r16 INTEGER (0..39), ms80-r16 INTEGER (0..79), ms160-r16 INTEGER (0..159), ... }, nr-MeasPRS-length-r16 ENUMERATED {ms1dot5, ms3, ms3dot5, ms4, ms5dot5, ms6, ms10, ms20}, ... } -- TAG-LOCATIONMEASUREMENTINFO-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,381 | 6.21.2.2 Indirect network sharing | The 5G system shall be able to support Indirect Network Sharing between the Shared NG-RAN and one or more Participating NG-RAN Operators’ core networks, by means of the connection being routed through the Hosting NG-RAN Operator’s core network. NOTE 1: Requirements of Indirect Network Sharing assume no impact on UE. NOTE 2: For more information on Indirect Network Sharing see Annex I. The following requirements apply to Indirect Network Sharing: Indirect Network Sharing shall be transparent to the user. NOTE 3: This requirement is aligned with the existing requirement in 3GPP TS 22.101[ Service aspects; Service principles ] [6] clause 4.9. The following existing service requirements related to network sharing in 3GPP TS 22.101[ Service aspects; Service principles ] [6] apply: - clause 4.2.1, - clause 28.2.3, and - clause 28.2.5. Subject to the agreement between the hosting and participating operator, the 5G system shall support a means to enable a UE of the Participating NG-RAN Operator to: - access their subscribed PLMN services when accessing a Shared NG-RAN, and/or, - obtain its subscribed services, including Hosted Services, of participating operator via a Shared NG-RAN. Based on operator policy, the 5G system shall support a mechanism to enable an authorized UE with a subscription to a Participating Operator to select and access a Shared NG-RAN. Based on operator policy, the 5G system shall support access control for an authorized UE accessing a Shared NG-RAN and be able to apply differentiated access control for different Shared NG-RANs when more than one Shared NG-RAN are available for the Participating Operator to choose from. Based on operator policy, the 5G system shall enable the Participating Operator to provide steering information in order to assist a UE with access network selection amongst the Hosting Operator’s available Shared RAN(s). The 5G system shall support service continuity for UEs that are moving between different Shared NG-RANs and/or between a Shared NG-RAN and a non-Shared NG-RAN networks. The 5G system shall be able to provide a UE accessing a Shared NG-RAN network with positioning service in compliance with regulatory requirements. Subject to regulatory requirements and mutual agreement between the participating operators and the hosting operator, the requirements to support regulatory services, e.g., PWS or emergency calls apply to Indirect Network Sharing. In case of Indirect Network Sharing and subject to agreement between operators the 5G system shall enable the Shared NG-RAN of a hosting operator to provide services for inbound roaming users. The 5G core network shall be able to support collection of charging information associated with a UE accessing a Shared NG-RAN using Indirect Network Sharing, which refers to the resource usage of hosting operator’s core network. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.21.2.2 |
5,382 | 5.4.4.6 Abnormal cases on the network side | The following abnormal cases can be identified: a) Expiry of timer T3555. The network shall, on the first expiry of the timer T3555, retransmit the CONFIGURATION UPDATE COMMAND message and shall reset and start timer T3555. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3555, the procedure shall be aborted. In addition, if the CONFIGURATION UPDATE COMMAND message includes the 5G-GUTI IE, the network shall behave as described in case b)-1) below. b) Lower layer failure. If a lower layer failure is detected before the CONFIGURATION UPDATE COMPLETE message is received and: 1) if the CONFIGURATION UPDATE COMMAND message includes the 5G-GUTI IE, the old and the new 5G-GUTI shall be considered as valid until the old 5G-GUTI can be considered as invalid by the AMF. If a new TAI list was provided in the CONFIGURATION UPDATE COMMAND message, the old and new TAI list shall also be considered as valid until the old TAI list can be considered as invalid by the AMF. Additionally, if the Updated PEIPS assistance information IE in the CONFIGURATION UPDATE COMMAND message includes a new Paging subgroup ID and the UE is previously assigned a different Paging subgroup ID then, the AMF shall consider both, the old and new Paging subgroup IDs as valid until the old Paging subgroup ID can be considered as invalid by the AMF. During this period the AMF: i) may first use the old 5G-S-TMSI from the old 5G-GUTI and the old Paging subgroup ID, if any, for paging within the area defined by the old TAI list for an implementation dependent number of paging attempts for network originated transactions. If a new TAI list was provided in the CONFIGURATION UPDATE COMMAND message, the new TAI list should also be used for paging. Upon response from the UE, the AMF may re-initiate the CONFIGURATION UPDATE COMMAND. If the Updated PEIPS assistance information IE in the CONFIGURATION UPDATE COMMAND message includes a new Paging subgroup ID, then the AMF may re-initiate the CONFIGURATION UPDATE COMMAND. If the response is received from a tracking area within the old and new TAI list, the network shall re-initiate the CONFIGURATION UPDATE COMMAND message. If no response is received to the paging attempts, the network may use the new 5G-S-TMSI from the new 5G-GUTI and the new Paging subgroup ID, if any, for paging for an implementation dependent number of paging attempts. In this case, if a new TAI list was provided with new 5G-GUTI in the CONFIGURATION UPDATE COMMAND message, the new TAI list shall be used instead of the old TAI list. Upon response from the UE the AMF shall consider the new 5G-GUTI and the new PEIPS assistance information as valid and the old 5G-GUTI and the old PEIPS assistance information as invalid. ii) shall consider the new 5G-GUTI as valid if it is used by the UE and, additionally, the new TAI list as valid if it was provided with this 5G-GUTI in the CONFIGURATION UPDATE COMMAND message; and iii) may use the identification procedure followed by a new generic UE configuration update procedure if the UE uses the old 5G-GUTI; or 2) if the CONFIGURATION UPDATE COMMAND message does not include the 5G-GUTI IE and: i) the CONFIGURATION UPDATE COMMAND message does not contain the Allowed NSSAI IE, the Rejected NSSAI IE, the Extended rejected NSSAI IE, or the Updated PEIPS assistance information IE, the network shall abort the procedure; or ii) the CONFIGURATION UPDATE COMMAND message contains the Allowed NSSAI IE, the Rejected NSSAI IE, the Extended rejected NSSAI IE, or the Updated PEIPS assistance information IE, the network shall either abort the procedure or retransmit the CONFIGURATION UPDATE COMMAND message on expiry of the timer T3555. The retransmission shall not be repeated more than four times. If the retransmission is repeated for four times, the network shall abort the procedure. c) Generic UE configuration update and UE initiated de-registration procedure collision. If the network receives a DEREGISTRATION REQUEST message before the ongoing generic UE configuration update procedure has been completed, the network shall abort the generic UE configuration update procedure and shall progress the de-registration procedure. d) Generic UE configuration update and registration procedure for mobility and periodic registration update collision If the network receives a REGISTRATION REQUEST message before the ongoing generic UE configuration update procedure has been completed, the network shall abort the generic UE configuration update procedure and shall progress the registration procedure for mobility and periodic registration update procedure. e) Generic UE configuration update and service request procedure collision If the network receives a SERVICE REQUEST message before the ongoing generic UE configuration update procedure has been completed and the SERVICE REQUEST message does not include UE request type IE with Request type value set to "NAS signalling connection release", both the procedures shall be progressed. If the network receives a SERVICE REQUEST message before the ongoing generic UE configuration update procedure has been completed and the SERVICE REQUEST message includes UE request type IE with Request type value set to "NAS signalling connection release", the network shall abort the generic UE configuration update procedure and shall progress the service request procedure. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.4.4.6 |
5,383 | 5.1.1.2 Number of RNReconfiguration Completed | a) This measurement provides the number of RNReconfiguration completed received by DeNB b) CC c) On receipt by the DeNB of a RNReconfigurationComplete message from RN. Each RNReconfigurationComplete message received is added to the relevant measurement. The message is included in 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]. d) Each measurement is an integer value. e) The measurement name has the form RRC.RNReconCmptNbr f) DeNBCapability g) Valid for packet switched traffic h) EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 5.1.1.2 |
5,384 | 4.26.3 NF/NF Service Context Transfer Pull procedure | Figure 4.26.3-1: NF/NF Service Context Pull procedure 1. When triggered, the Target NF/NF Service as an NF Service Consumer requests a Context (e.g. UE context or SM context) from the Source NF as a NF Service Producer. This may trigger several other procedures that ensure all necessary NF/NF services are being updated and set up with necessary information about the new context location. NOTE 1: Which procedures need to be executed and what information needs to be updated is part of the specific context transfer procedures as specified in clause 4.26.5. 2. The NF Service Consumer receives the Context and the operation was successful. When all procedures have been executed successfully the Target NF/NF Service can continue to serve the original NF Service Consumers of the Source NF/NF Service, which e.g. can be shut down gracefully. NOTE 2: After resumption of a new service transaction, it may be necessary to contact the UE using existing procedures. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.26.3 |
5,385 | 6.13.2 Requirements | The following set of requirements complement the requirements listed in 3GPP TS 22.146[ Multimedia Broadcast/Multicast Service (MBMS); Stage 1 ] [7], TS 22.246[ Multimedia Broadcast/Multicast Service (MBMS) user services; Stage 1 ] [8] and TS 22.101[ Service aspects; Service principles ] [6], clause 32. The 5G system shall support operation of downlink only broadcast/multicast over a specific geographic area (e.g. a cell sector, a cell or a group of cells). The 5G system shall support operation of a downlink only broadcast/multicast system over a wide geographic area in a spectrally efficient manner for stationary and mobile UEs. The 5G system shall enable the operator to reserve 0% to 100% of radio resources of one or more radio carriers for the delivery of broadcast/multicast content. The 5G network shall allow the UE to receive content via a broadcast/multicast radio carrier while a concurrent data session is ongoing over another radio carrier. The 5G system shall be able to support broadcast/multicast of UHD streaming video (e.g. 4K/8K UHD). NOTE 1: Taking into account the bandwidth needs for different streaming video resolution. The 5G network shall allow the operator to configure and broadcast multiple quality levels (i.e. video resolutions) of broadcast/multicast content for the same user service in a stand-alone 3GPP based broadcast/multicast system. The 5G network shall support parallel transfer of multiple quality levels (i.e. video resolutions) of broadcast/multicast content for the same user service to the same UE taking into account e.g. UE capability, radio characteristics, application information. The 5G system shall support parallel transfer of multiple multicast/broadcast user services to a UE. The 5G system shall support a stand-alone multicast/broadcast network comprising of multiple cells with inter-site distances of up to 200 km. The 5G system shall support multicast/broadcast via a 5G satellite access network, or via a combination of a 5G satellite access network and other 5G access networks. The 5G system shall support interworking of 5G multicast/broadcast with non-3GPP digital terrestrial broadcast networks. NOTE 1A: Any impact on the non-3GPP digital terrestrial broadcast standard is out of scope of 3GPP standardization. The 5G system shall be able to setup or modify a broadcast/multicast service area within [1s]. NOTE 2: For MCPTT related KPIs see 3GPP TS 22.179[ Mission Critical Push to Talk (MCPTT); Stage 1 ] [30], clause 6.15. The 5G system shall be able to apply QoS, priority and pre-emption to a broadcast/multicast service area. The 5G system shall support downlink parallel transfer of the same content, via broadcast/multicast and/or unicast, such that all receiver group members in a given area receive the media at the same time according to user perception. NOTE 3: In this context user perception refers to a difference in delay of typically less than 20 ms. The 5G system shall support a mechanism to inform a media source of relevant changes in conditions in the system (e.g. capacity, failures). The 5G system shall provide means for a media source to provide QoS requirement requests to the broadcast/multicast service. The 5G system shall provide means for the broadcast/multicast service to inform the media source of the available QoS, including modification of available QoS characteristics and availability of the broadcast/multicast service. The 5G system shall be able to support broadcast/multicast of voice, data and video group communication, allowing at least 800 concurrently operating groups per geographic area. NOTE 4: In this context "concurrently operating groups" means that the associated media streams are delivered concurrently. The 5G system shall support delivery of the same UE-originated data in a resource-efficient manner in terms of service bit rate to UEs distributed over a large geographical area. The 5G system shall allow a UE to request a communication service to simultaneously send data to different groups of UEs at the same time. The 5G system shall allow different QoS policy for each group the UE communicates with. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.13.2 |
5,386 | 9.1.1 Format of APN Network Identifier | The APN Network Identifier shall contain at least one label and shall have, after encoding as defined in clause 9.1 above, a maximum length of 63 octets. An APN Network Identifier shall not start with any of the strings "rac", "lac", "sgsn" or "rnc", and it shall not end in ".gprs", i.e. the last label of the APN Network Identifier shall not be "gprs". Further, it shall not take the value "*". In order to guarantee uniqueness of APN Network Identifiers within or between GPRS/EPS PLMN, an APN Network Identifier containing more than one label shall correspond to an Internet domain name. This name should only be allocated by the PLMN if that PLMN belongs to an organisation which has officially reserved this name in the Internet domain. Other types of APN Network Identifiers are not guaranteed to be unique within or between GPRS/EPS PLMNs. An APN Network Identifier may be used to access a service associated with a GGSN/PGW. This may be achieved by defining: - an APN which corresponds to a FQDN of a GGSN/PGW, and which is locally interpreted by the GGSN/PGW as a request for a specific service, or - an APN Network Identifier consisting of 3 or more labels and starting with a Reserved Service Label, or an APN Network Identifier consisting of a Reserved Service Label alone, which indicates a GGSN/PGW by the nature of the requested service. Reserved Service Labels and the corresponding services they stand for shall be agreed between operators who have GPRS/EPS roaming agreements. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 9.1.1 |
5,387 | – UECapabilityInformationSidelink | The UECapabilityInformationSidelink message is used to transfer UE radio access capabilities. It is only applied to unicast of NR sidelink communication. Signalling radio bearer: SL-SRB3 RLC-SAP: AM Logical channel: SCCH Direction: UE to UE UECapabilityInformationSidelink message -- ASN1START -- TAG-UECAPABILITYINFORMATIONSIDELINK-START UECapabilityInformationSidelink ::= SEQUENCE { rrc-TransactionIdentifier-r16 RRC-TransactionIdentifier, criticalExtensions CHOICE { ueCapabilityInformationSidelink-r16 UECapabilityInformationSidelink-r16-IEs, criticalExtensionsFuture SEQUENCE {} } } UECapabilityInformationSidelink-r16-IEs ::= SEQUENCE { accessStratumReleaseSidelink-r16 AccessStratumReleaseSidelink-r16, pdcp-ParametersSidelink-r16 PDCP-ParametersSidelink-r16 OPTIONAL, rlc-ParametersSidelink-r16 RLC-ParametersSidelink-r16 OPTIONAL, supportedBandCombinationListSidelinkNR-r16 BandCombinationListSidelinkNR-r16 OPTIONAL, supportedBandListSidelink-r16 SEQUENCE (SIZE (1..maxBands)) OF BandSidelinkPC5-r16 OPTIONAL, appliedFreqBandListFilter-r16 FreqBandList OPTIONAL, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension UECapabilityInformationSidelink-v1700-IEs OPTIONAL } UECapabilityInformationSidelink-v1700-IEs ::= SEQUENCE { mac-ParametersSidelink-r17 MAC-ParametersSidelink-r17 OPTIONAL, supportedBandCombinationListSidelinkNR-v1710 BandCombinationListSidelinkNR-v1710 OPTIONAL, nonCriticalExtension UECapabilityInformationSidelink-v1800-IEs OPTIONAL } UECapabilityInformationSidelink-v1800-IEs ::= SEQUENCE { sfn-DFN-OffsetSupported-r18 ENUMERATED { supported } OPTIONAL, posSIB-ForwardingSupported-r18 ENUMERATED { supported } OPTIONAL, pdcp-ParametersSidelink-r18 PDCP-ParametersSidelink-r18 OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } PDCP-ParametersSidelink-r18 ::= SEQUENCE { pdcp-DuplicationSRB-sidelink-r18 ENUMERATED {supported} OPTIONAL, pdcp-DuplicationDRB-sidelink-r18 ENUMERATED {supported} OPTIONAL, ... } MAC-ParametersSidelink-r17 ::= SEQUENCE { drx-OnSidelink-r17 ENUMERATED {supported} OPTIONAL, ... } AccessStratumReleaseSidelink-r16 ::= ENUMERATED { rel16, rel17, rel18, spare5, spare4, spare3, spare2, spare1, ... } PDCP-ParametersSidelink-r16 ::= SEQUENCE { outOfOrderDeliverySidelink-r16 ENUMERATED {supported} OPTIONAL, ... } BandCombinationListSidelinkNR-r16 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombinationParametersSidelinkNR-r16 BandCombinationListSidelinkNR-v1710 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombinationParametersSidelinkNR-v1710 BandCombinationParametersSidelinkNR-r16 ::= SEQUENCE (SIZE (1..maxSimultaneousBands)) OF BandParametersSidelink-r16 BandCombinationParametersSidelinkNR-v1710 ::= SEQUENCE (SIZE (1..maxSimultaneousBands)) OF BandParametersSidelink-v1710 BandParametersSidelink-v1710 ::= SEQUENCE { --32-5a-1 tx-IUC-Scheme1-Mode2Sidelink-r17 ENUMERATED {supported} OPTIONAL, --32-5b-1 tx-IUC-Scheme2-Mode2Sidelink-r17 ENUMERATED {n4, n8, n16} OPTIONAL } BandSidelinkPC5-r16 ::= SEQUENCE { freqBandSidelink-r16 FreqBandIndicatorNR, --15-1 sl-Reception-r16 SEQUENCE { harq-RxProcessSidelink-r16 ENUMERATED {n16, n24, n32, n64}, pscch-RxSidelink-r16 ENUMERATED {value1, value2}, scs-CP-PatternRxSidelink-r16 CHOICE { fr1-r16 SEQUENCE { scs-15kHz-r16 BIT STRING (SIZE (16)) OPTIONAL, scs-30kHz-r16 BIT STRING (SIZE (16)) OPTIONAL, scs-60kHz-r16 BIT STRING (SIZE (16)) OPTIONAL }, fr2-r16 SEQUENCE { scs-60kHz-r16 BIT STRING (SIZE (16)) OPTIONAL, scs-120kHz-r16 BIT STRING (SIZE (16)) OPTIONAL } } OPTIONAL, extendedCP-RxSidelink-r16 ENUMERATED {supported} OPTIONAL } OPTIONAL, --15-10 sl-Tx-256QAM-r16 ENUMERATED {supported} OPTIONAL, --15-12 lowSE-64QAM-MCS-TableSidelink-r16 ENUMERATED {supported} OPTIONAL, ..., [[ --15-14 csi-ReportSidelink-r16 SEQUENCE { csi-RS-PortsSidelink-r16 ENUMERATED {p1, p2} } OPTIONAL, --15-19 rankTwoReception-r16 ENUMERATED {supported} OPTIONAL, --15-23 sl-openLoopPC-RSRP-ReportSidelink-r16 ENUMERATED {supported} OPTIONAL, --13-1 sl-Rx-256QAM-r16 ENUMERATED {supported} OPTIONAL ]], [[ --32-5a-2 rx-IUC-Scheme1-PreferredMode2Sidelink-r17 ENUMERATED {supported} OPTIONAL, --32-5a-3 rx-IUC-Scheme1-NonPreferredMode2Sidelink-r17 ENUMERATED {supported} OPTIONAL, --32-5b-2 rx-IUC-Scheme2-Mode2Sidelink-r17 ENUMERATED {n5, n15, n25, n32, n35, n45, n50, n64} OPTIONAL, --32-6-1 rx-IUC-Scheme1-SCI-r17 ENUMERATED {supported} OPTIONAL, --32-6-2 rx-IUC-Scheme1-SCI-ExplicitReq-r17 ENUMERATED {supported} OPTIONAL, --32-7 scheme2-ConflictDeterminationRSRP-r17 ENUMERATED {supported} OPTIONAL ]], [[ -- R4 45-2: SL reception in intra-carrier guard band sl-ReceptionIntraCarrierGuardBand-r18 ENUMERATED {supported} OPTIONAL ]] } -- TAG-UECAPABILITYINFORMATIONSIDELINK-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,388 | 8.3.10.1 Message definition | The PDU SESSION MODIFICATION COMPLETE message is sent by the UE to the SMF in response to the PDU SESSION MODIFICATION COMMAND message and indicates an acceptance of the PDU SESSION MODIFICATION COMMAND message. See table 8.3.10.1.1. Message type: PDU SESSION MODIFICATION COMPLETE Significance: dual Direction: UE to network Table 8.3.10.1.1: PDU SESSION MODIFICATION COMPLETE message content NOTE: It is possible for UEs compliant with version 15.3.0 of this specification to include the 5GSM cause IE with IEI 59 in the PDU SESSION MODIFICATION COMPLETE message, and therefore the IEI 59 cannot be used for other optional IEs other than the 5GSM cause IE for future extensions of the PDU SESSION MODIFICATION COMPLETE message. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 8.3.10.1 |
5,389 | – RF-Parameters | The IE RF-Parameters is used to convey RF-related capabilities for NR operation. RF-Parameters information element -- ASN1START -- TAG-RF-PARAMETERS-START RF-Parameters ::= SEQUENCE { supportedBandListNR SEQUENCE (SIZE (1..maxBands)) OF BandNR, supportedBandCombinationList BandCombinationList OPTIONAL, appliedFreqBandListFilter FreqBandList OPTIONAL, ..., [[ supportedBandCombinationList-v1540 BandCombinationList-v1540 OPTIONAL, srs-SwitchingTimeRequested ENUMERATED {true} OPTIONAL ]], [[ supportedBandCombinationList-v1550 BandCombinationList-v1550 OPTIONAL ]], [[ supportedBandCombinationList-v1560 BandCombinationList-v1560 OPTIONAL ]], [[ supportedBandCombinationList-v1610 BandCombinationList-v1610 OPTIONAL, supportedBandCombinationListSidelinkEUTRA-NR-r16 BandCombinationListSidelinkEUTRA-NR-r16 OPTIONAL, supportedBandCombinationList-UplinkTxSwitch-r16 BandCombinationList-UplinkTxSwitch-r16 OPTIONAL ]], [[ supportedBandCombinationList-v1630 BandCombinationList-v1630 OPTIONAL, supportedBandCombinationListSidelinkEUTRA-NR-v1630 BandCombinationListSidelinkEUTRA-NR-v1630 OPTIONAL, supportedBandCombinationList-UplinkTxSwitch-v1630 BandCombinationList-UplinkTxSwitch-v1630 OPTIONAL ]], [[ supportedBandCombinationList-v1640 BandCombinationList-v1640 OPTIONAL, supportedBandCombinationList-UplinkTxSwitch-v1640 BandCombinationList-UplinkTxSwitch-v1640 OPTIONAL ]], [[ supportedBandCombinationList-v1650 BandCombinationList-v1650 OPTIONAL, supportedBandCombinationList-UplinkTxSwitch-v1650 BandCombinationList-UplinkTxSwitch-v1650 OPTIONAL ]], [[ extendedBand-n77-r16 ENUMERATED {supported} OPTIONAL ]], [[ supportedBandCombinationList-UplinkTxSwitch-v1670 BandCombinationList-UplinkTxSwitch-v1670 OPTIONAL ]], [[ supportedBandCombinationList-v1680 BandCombinationList-v1680 OPTIONAL ]], [[ supportedBandCombinationList-v1690 BandCombinationList-v1690 OPTIONAL, supportedBandCombinationList-UplinkTxSwitch-v1690 BandCombinationList-UplinkTxSwitch-v1690 OPTIONAL ]], [[ supportedBandCombinationList-v1700 BandCombinationList-v1700 OPTIONAL, supportedBandCombinationList-UplinkTxSwitch-v1700 BandCombinationList-UplinkTxSwitch-v1700 OPTIONAL, supportedBandCombinationListSL-RelayDiscovery-r17 OCTET STRING OPTIONAL, -- Contains PC5 BandCombinationListSidelinkNR-r16 supportedBandCombinationListSL-NonRelayDiscovery-r17 OCTET STRING OPTIONAL, -- Contains PC5 BandCombinationListSidelinkNR-r16 supportedBandCombinationListSidelinkEUTRA-NR-v1710 BandCombinationListSidelinkEUTRA-NR-v1710 OPTIONAL, sidelinkRequested-r17 ENUMERATED {true} OPTIONAL, extendedBand-n77-2-r17 ENUMERATED {supported} OPTIONAL ]], [[ supportedBandCombinationList-v1720 BandCombinationList-v1720 OPTIONAL, supportedBandCombinationList-UplinkTxSwitch-v1720 BandCombinationList-UplinkTxSwitch-v1720 OPTIONAL ]], [[ supportedBandCombinationList-v1730 BandCombinationList-v1730 OPTIONAL, supportedBandCombinationList-UplinkTxSwitch-v1730 BandCombinationList-UplinkTxSwitch-v1730 OPTIONAL, supportedBandCombinationListSL-RelayDiscovery-v1730 BandCombinationListSL-Discovery-r17 OPTIONAL, supportedBandCombinationListSL-NonRelayDiscovery-v1730 BandCombinationListSL-Discovery-r17 OPTIONAL ]], [[ supportedBandCombinationList-v1740 BandCombinationList-v1740 OPTIONAL, supportedBandCombinationList-UplinkTxSwitch-v1740 BandCombinationList-UplinkTxSwitch-v1740 OPTIONAL ]], [[ supportedBandCombinationList-v1760 BandCombinationList-v1760 OPTIONAL, supportedBandCombinationList-UplinkTxSwitch-v1760 BandCombinationList-UplinkTxSwitch-v1760 OPTIONAL ]], [[ supportedBandCombinationList-v1770 BandCombinationList-v1770 OPTIONAL, supportedBandCombinationList-UplinkTxSwitch-v1770 BandCombinationList-UplinkTxSwitch-v1770 OPTIONAL ]], [[ supportedBandCombinationList-v1800 BandCombinationList-v1800 OPTIONAL, supportedBandCombinationList-UplinkTxSwitch-v1800 BandCombinationList-UplinkTxSwitch-v1800 OPTIONAL, supportedBandCombinationListSL-U2U-Relay-r18 SEQUENCE { supportedBandCombinationListSL-U2U-RelayDiscovery-r18 OCTET STRING OPTIONAL, -- Contains PC5 -- BandCombinationListSidelinkNR-r16 supportedBandCombinationListSL-U2U-DiscoveryExt BandCombinationListSL-Discovery-r17 OPTIONAL } OPTIONAL ]] } RF-Parameters-v15g0 ::= SEQUENCE { supportedBandCombinationList-v15g0 BandCombinationList-v15g0 OPTIONAL } RF-Parameters-v16a0 ::= SEQUENCE { supportedBandCombinationList-v16a0 BandCombinationList-v16a0 OPTIONAL, supportedBandCombinationList-UplinkTxSwitch-v16a0 BandCombinationList-UplinkTxSwitch-v16a0 OPTIONAL } RF-Parameters-v16c0 ::= SEQUENCE { supportedBandListNR-v16c0 SEQUENCE (SIZE (1..maxBands)) OF BandNR-v16c0 } BandNR ::= SEQUENCE { bandNR FreqBandIndicatorNR, modifiedMPR-Behaviour BIT STRING (SIZE (8)) OPTIONAL, mimo-ParametersPerBand MIMO-ParametersPerBand OPTIONAL, extendedCP ENUMERATED {supported} OPTIONAL, multipleTCI ENUMERATED {supported} OPTIONAL, bwp-WithoutRestriction ENUMERATED {supported} OPTIONAL, bwp-SameNumerology ENUMERATED {upto2, upto4} OPTIONAL, bwp-DiffNumerology ENUMERATED {upto4} OPTIONAL, crossCarrierScheduling-SameSCS ENUMERATED {supported} OPTIONAL, pdsch-256QAM-FR2 ENUMERATED {supported} OPTIONAL, pusch-256QAM ENUMERATED {supported} OPTIONAL, ue-PowerClass ENUMERATED {pc1, pc2, pc3, pc4} OPTIONAL, rateMatchingLTE-CRS ENUMERATED {supported} OPTIONAL, channelBWs-DL CHOICE { fr1 SEQUENCE { scs-15kHz BIT STRING (SIZE (10)) OPTIONAL, scs-30kHz BIT STRING (SIZE (10)) OPTIONAL, scs-60kHz BIT STRING (SIZE (10)) OPTIONAL }, fr2 SEQUENCE { scs-60kHz BIT STRING (SIZE (3)) OPTIONAL, scs-120kHz BIT STRING (SIZE (3)) OPTIONAL } } OPTIONAL, channelBWs-UL CHOICE { fr1 SEQUENCE { scs-15kHz BIT STRING (SIZE (10)) OPTIONAL, scs-30kHz BIT STRING (SIZE (10)) OPTIONAL, scs-60kHz BIT STRING (SIZE (10)) OPTIONAL }, fr2 SEQUENCE { scs-60kHz BIT STRING (SIZE (3)) OPTIONAL, scs-120kHz BIT STRING (SIZE (3)) OPTIONAL } } OPTIONAL, ..., [[ maxUplinkDutyCycle-PC2-FR1 ENUMERATED {n60, n70, n80, n90, n100} OPTIONAL ]], [[ pucch-SpatialRelInfoMAC-CE ENUMERATED {supported} OPTIONAL, powerBoosting-pi2BPSK ENUMERATED {supported} OPTIONAL ]], [[ maxUplinkDutyCycle-FR2 ENUMERATED {n15, n20, n25, n30, n40, n50, n60, n70, n80, n90, n100} OPTIONAL ]], [[ channelBWs-DL-v1590 CHOICE { fr1 SEQUENCE { scs-15kHz BIT STRING (SIZE (16)) OPTIONAL, scs-30kHz BIT STRING (SIZE (16)) OPTIONAL, scs-60kHz BIT STRING (SIZE (16)) OPTIONAL }, fr2 SEQUENCE { scs-60kHz BIT STRING (SIZE (8)) OPTIONAL, scs-120kHz BIT STRING (SIZE (8)) OPTIONAL } } OPTIONAL, channelBWs-UL-v1590 CHOICE { fr1 SEQUENCE { scs-15kHz BIT STRING (SIZE (16)) OPTIONAL, scs-30kHz BIT STRING (SIZE (16)) OPTIONAL, scs-60kHz BIT STRING (SIZE (16)) OPTIONAL }, fr2 SEQUENCE { scs-60kHz BIT STRING (SIZE (8)) OPTIONAL, scs-120kHz BIT STRING (SIZE (8)) OPTIONAL } } OPTIONAL ]], [[ asymmetricBandwidthCombinationSet BIT STRING (SIZE (1..32)) OPTIONAL ]], [[ -- R1 10: NR-unlicensed sharedSpectrumChAccessParamsPerBand-r16 SharedSpectrumChAccessParamsPerBand-r16 OPTIONAL, -- R1 11-7b: Independent cancellation of the overlapping PUSCHs in an intra-band UL CA cancelOverlappingPUSCH-r16 ENUMERATED {supported} OPTIONAL, -- R1 14-1: Multiple LTE-CRS rate matching patterns multipleRateMatchingEUTRA-CRS-r16 SEQUENCE { maxNumberPatterns-r16 INTEGER (2..6), maxNumberNon-OverlapPatterns-r16 INTEGER (1..3) } OPTIONAL, -- R1 14-1a: Two LTE-CRS overlapping rate matching patterns within a part of NR carrier using 15 kHz overlapping with a LTE carrier overlapRateMatchingEUTRA-CRS-r16 ENUMERATED {supported} OPTIONAL, -- R1 14-2: PDSCH Type B mapping of length 9 and 10 OFDM symbols pdsch-MappingTypeB-Alt-r16 ENUMERATED {supported} OPTIONAL, -- R1 14-3: One slot periodic TRS configuration for FR1 oneSlotPeriodicTRS-r16 ENUMERATED {supported} OPTIONAL, olpc-SRS-Pos-r16 OLPC-SRS-Pos-r16 OPTIONAL, spatialRelationsSRS-Pos-r16 SpatialRelationsSRS-Pos-r16 OPTIONAL, simulSRS-MIMO-TransWithinBand-r16 ENUMERATED {n2} OPTIONAL, channelBW-DL-IAB-r16 CHOICE { fr1-100mhz SEQUENCE { scs-15kHz ENUMERATED {supported} OPTIONAL, scs-30kHz ENUMERATED {supported} OPTIONAL, scs-60kHz ENUMERATED {supported} OPTIONAL }, fr2-200mhz SEQUENCE { scs-60kHz ENUMERATED {supported} OPTIONAL, scs-120kHz ENUMERATED {supported} OPTIONAL } } OPTIONAL, channelBW-UL-IAB-r16 CHOICE { fr1-100mhz SEQUENCE { scs-15kHz ENUMERATED {supported} OPTIONAL, scs-30kHz ENUMERATED {supported} OPTIONAL, scs-60kHz ENUMERATED {supported} OPTIONAL }, fr2-200mhz SEQUENCE { scs-60kHz ENUMERATED {supported} OPTIONAL, scs-120kHz ENUMERATED {supported} OPTIONAL } } OPTIONAL, rasterShift7dot5-IAB-r16 ENUMERATED {supported} OPTIONAL, ue-PowerClass-v1610 ENUMERATED {pc1dot5} OPTIONAL, condHandover-r16 ENUMERATED {supported} OPTIONAL, condHandoverFailure-r16 ENUMERATED {supported} OPTIONAL, condHandoverTwoTriggerEvents-r16 ENUMERATED {supported} OPTIONAL, condPSCellChange-r16 ENUMERATED {supported} OPTIONAL, condPSCellChangeTwoTriggerEvents-r16 ENUMERATED {supported} OPTIONAL, mpr-PowerBoost-FR2-r16 ENUMERATED {supported} OPTIONAL, -- R1 11-9: Multiple active configured grant configurations for a BWP of a serving cell activeConfiguredGrant-r16 SEQUENCE { maxNumberConfigsPerBWP-r16 ENUMERATED {n1, n2, n4, n8, n12}, maxNumberConfigsAllCC-r16 INTEGER (2..32) } OPTIONAL, -- R1 11-9a: Joint release in a DCI for two or more configured grant Type 2 configurations for a given BWP of a serving cell jointReleaseConfiguredGrantType2-r16 ENUMERATED {supported} OPTIONAL, -- R1 12-2: Multiple SPS configurations sps-r16 SEQUENCE { maxNumberConfigsPerBWP-r16 INTEGER (1..8), maxNumberConfigsAllCC-r16 INTEGER (2..32) } OPTIONAL, -- R1 12-2a: Joint release in a DCI for two or more SPS configurations for a given BWP of a serving cell jointReleaseSPS-r16 ENUMERATED {supported} OPTIONAL, -- R1 13-19: Simultaneous positioning SRS and MIMO SRS transmission within a band across multiple CCs simulSRS-TransWithinBand-r16 ENUMERATED {n2} OPTIONAL, trs-AdditionalBandwidth-r16 ENUMERATED {trs-AddBW-Set1, trs-AddBW-Set2} OPTIONAL, handoverIntraF-IAB-r16 ENUMERATED {supported} OPTIONAL ]], [[ -- R1 22-5a: Simultaneous transmission of SRS for antenna switching and SRS for CB/NCB /BM for intra-band UL CA -- R1 22-5c: Simultaneous transmission of SRS for antenna switching and SRS for antenna switching for intra-band UL CA simulTX-SRS-AntSwitchingIntraBandUL-CA-r16 SimulSRS-ForAntennaSwitching-r16 OPTIONAL, -- R1 10: NR-unlicensed sharedSpectrumChAccessParamsPerBand-v1630 SharedSpectrumChAccessParamsPerBand-v1630 OPTIONAL ]], [[ handoverUTRA-FDD-r16 ENUMERATED {supported} OPTIONAL, -- R4 7-4: Report the shorter transient capability supported by the UE: 2, 4 or 7us enhancedUL-TransientPeriod-r16 ENUMERATED {us2, us4, us7} OPTIONAL, sharedSpectrumChAccessParamsPerBand-v1640 SharedSpectrumChAccessParamsPerBand-v1640 OPTIONAL ]], [[ type1-PUSCH-RepetitionMultiSlots-v1650 ENUMERATED {supported} OPTIONAL, type2-PUSCH-RepetitionMultiSlots-v1650 ENUMERATED {supported} OPTIONAL, pusch-RepetitionMultiSlots-v1650 ENUMERATED {supported} OPTIONAL, configuredUL-GrantType1-v1650 ENUMERATED {supported} OPTIONAL, configuredUL-GrantType2-v1650 ENUMERATED {supported} OPTIONAL, sharedSpectrumChAccessParamsPerBand-v1650 SharedSpectrumChAccessParamsPerBand-v1650 OPTIONAL ]], [[ enhancedSkipUplinkTxConfigured-v1660 ENUMERATED {supported} OPTIONAL, enhancedSkipUplinkTxDynamic-v1660 ENUMERATED {supported} OPTIONAL ]], [[ maxUplinkDutyCycle-PC1dot5-MPE-FR1-r16 ENUMERATED {n10, n15, n20, n25, n30, n40, n50, n60, n70, n80, n90, n100} OPTIONAL, txDiversity-r16 ENUMERATED {supported} OPTIONAL ]], [[ -- R1 36-1: Support of 1024QAM for PDSCH for FR1 pdsch-1024QAM-FR1-r17 ENUMERATED {supported} OPTIONAL, -- R4 22-1 support of FR2 HST operation ue-PowerClass-v1700 ENUMERATED {pc5, pc6, pc7} OPTIONAL, -- R1 24: NR extension to 71GHz (FR2-2) fr2-2-AccessParamsPerBand-r17 FR2-2-AccessParamsPerBand-r17 OPTIONAL, rlm-Relaxation-r17 ENUMERATED {supported} OPTIONAL, bfd-Relaxation-r17 ENUMERATED {supported} OPTIONAL, cg-SDT-r17 ENUMERATED {supported} OPTIONAL, locationBasedCondHandover-r17 ENUMERATED {supported} OPTIONAL, timeBasedCondHandover-r17 ENUMERATED {supported} OPTIONAL, eventA4BasedCondHandover-r17 ENUMERATED {supported} OPTIONAL, mn-InitiatedCondPSCellChangeNRDC-r17 ENUMERATED {supported} OPTIONAL, sn-InitiatedCondPSCellChangeNRDC-r17 ENUMERATED {supported} OPTIONAL, -- R1 29-3a: PDCCH skipping pdcch-SkippingWithoutSSSG-r17 ENUMERATED {supported} OPTIONAL, -- R1 29-3b: 2 search space sets group switching sssg-Switching-1BitInd-r17 ENUMERATED {supported} OPTIONAL, -- R1 29-3c: 3 search space sets group switching sssg-Switching-2BitInd-r17 ENUMERATED {supported} OPTIONAL, -- R1 29-3d: 2 search space sets group switching with PDCCH skipping pdcch-SkippingWithSSSG-r17 ENUMERATED {supported} OPTIONAL, -- R1 29-3e: Support Search space set group switching capability 2 for FR1 searchSpaceSetGrp-switchCap2-r17 ENUMERATED {supported} OPTIONAL, -- R1 26-1: Uplink Time and Frequency pre-compensation and timing relationship enhancements uplinkPreCompensation-r17 ENUMERATED {supported} OPTIONAL, -- R1 26-4: UE reporting of information related to TA pre-compensation uplink-TA-Reporting-r17 ENUMERATED {supported} OPTIONAL, -- R1 26-5: Increasing the number of HARQ processes max-HARQ-ProcessNumber-r17 ENUMERATED {u16d32, u32d16, u32d32} OPTIONAL, -- R1 26-6: Type-2 HARQ codebook enhancement type2-HARQ-Codebook-r17 ENUMERATED {supported} OPTIONAL, -- R1 26-6a: Type-1 HARQ codebook enhancement type1-HARQ-Codebook-r17 ENUMERATED {supported} OPTIONAL, -- R1 26-6b: Type-3 HARQ codebook enhancement type3-HARQ-Codebook-r17 ENUMERATED {supported} OPTIONAL, -- R1 26-9: UE-specific K_offset ue-specific-K-Offset-r17 ENUMERATED {supported} OPTIONAL, -- R1 24-1f: Multiple PDSCH scheduling by single DCI for 120kHz in FR2-1 multiPDSCH-SingleDCI-FR2-1-SCS-120kHz-r17 ENUMERATED {supported} OPTIONAL, -- R1 24-1g: Multiple PUSCH scheduling by single DCI for 120kHz in FR2-1 multiPUSCH-SingleDCI-FR2-1-SCS-120kHz-r17 ENUMERATED {supported} OPTIONAL, -- R4 14-4: Parallel PRS measurements in RRC_INACTIVE state, FR1/FR2 diff parallelPRS-MeasRRC-Inactive-r17 ENUMERATED {supported} OPTIONAL, -- R1 27-1-2: Support of UE-TxTEGs for UL TDOA nr-UE-TxTEG-ID-MaxSupport-r17 ENUMERATED {n1, n2, n3, n4, n6, n8} OPTIONAL, -- R1 27-17: PRS processing in RRC_INACTIVE prs-ProcessingRRC-Inactive-r17 ENUMERATED {supported} OPTIONAL, -- R1 27-3-2: DL PRS measurement outside MG and in a PRS processing window prs-ProcessingWindowType1A-r17 ENUMERATED {option1, option2, option3} OPTIONAL, prs-ProcessingWindowType1B-r17 ENUMERATED {option1, option2, option3} OPTIONAL, prs-ProcessingWindowType2-r17 ENUMERATED {option1, option2, option3} OPTIONAL, -- R1 27-15: Positioning SRS transmission in RRC_INACTIVE state for initial UL BWP srs-AllPosResourcesRRC-Inactive-r17 SRS-AllPosResourcesRRC-Inactive-r17 OPTIONAL, -- R1 27-16: OLPC for positioning SRS in RRC_INACTIVE state - gNB olpc-SRS-PosRRC-Inactive-r17 OLPC-SRS-Pos-r16 OPTIONAL, -- R1 27-19: Spatial relation for positioning SRS in RRC_INACTIVE state - gNB spatialRelationsSRS-PosRRC-Inactive-r17 SpatialRelationsSRS-Pos-r16 OPTIONAL, -- R1 30-1: Increased maximum number of PUSCH Type A repetitions maxNumberPUSCH-TypeA-Repetition-r17 ENUMERATED {supported} OPTIONAL, -- R1 30-2: PUSCH Type A repetitions based on available slots puschTypeA-RepetitionsAvailSlot-r17 ENUMERATED {supported} OPTIONAL, -- R1 30-3: TB processing over multi-slot PUSCH tb-ProcessingMultiSlotPUSCH-r17 ENUMERATED {supported} OPTIONAL, -- R1 30-3a: Repetition of TB processing over multi-slot PUSCH tb-ProcessingRepMultiSlotPUSCH-r17 ENUMERATED {supported} OPTIONAL, -- R1 30-4: The maximum duration for DM-RS bundling maxDurationDMRS-Bundling-r17 SEQUENCE { fdd-r17 ENUMERATED {n4, n8, n16, n32} OPTIONAL, tdd-r17 ENUMERATED {n2, n4, n8, n16} OPTIONAL } OPTIONAL, -- R1 30-6: Repetition of PUSCH transmission scheduled by RAR UL grant and DCI format 0_0 with CRC scrambled by TC-RNTI pusch-RepetitionMsg3-r17 ENUMERATED {supported} OPTIONAL, sharedSpectrumChAccessParamsPerBand-v1710 SharedSpectrumChAccessParamsPerBand-v1710 OPTIONAL, -- R4 25-2: Parallel measurements on cells belonging to a different NGSO satellite than a serving satellite without scheduling restrictions -- on normal operations with the serving cell parallelMeasurementWithoutRestriction-r17 ENUMERATED {supported} OPTIONAL, -- R4 25-5: Parallel measurements on multiple NGSO satellites within a SMTC maxNumber-NGSO-SatellitesWithinOneSMTC-r17 ENUMERATED {n1, n2, n3, n4} OPTIONAL, -- R1 26-10: K1 range extension k1-RangeExtension-r17 ENUMERATED {supported} OPTIONAL, -- R1 35-1: Aperiodic CSI-RS for tracking for fast SCell activation aperiodicCSI-RS-FastScellActivation-r17 SEQUENCE { maxNumberAperiodicCSI-RS-PerCC-r17 ENUMERATED {n8, n16, n32, n48, n64, n128, n255}, maxNumberAperiodicCSI-RS-AcrossCCs-r17 ENUMERATED {n8, n16, n32, n64, n128, n256, n512, n1024} } OPTIONAL, -- R1 35-2: Aperiodic CSI-RS bandwidth for tracking for fast SCell activation for 10MHz UE channel bandwidth aperiodicCSI-RS-AdditionalBandwidth-r17 ENUMERATED {addBW-Set1, addBW-Set2} OPTIONAL, -- R1 28-1a: RRC-configured DL BWP without CD-SSB or NCD-SSB bwp-WithoutCD-SSB-OrNCD-SSB-RedCap-r17 ENUMERATED {supported} OPTIONAL, -- R1 28-3: Half-duplex FDD operation type A for (e)RedCap UE halfDuplexFDD-TypeA-RedCap-r17 ENUMERATED {supported} OPTIONAL, -- R1 27-15b: Positioning SRS transmission in RRC_INACTIVE state configured outside initial UL BWP posSRS-RRC-Inactive-OutsideInitialUL-BWP-r17 PosSRS-RRC-Inactive-OutsideInitialUL-BWP-r17 OPTIONAL, -- R4 15-3 UE support of CBW for 480kHz SCS channelBWs-DL-SCS-480kHz-FR2-2-r17 BIT STRING (SIZE (8)) OPTIONAL, channelBWs-UL-SCS-480kHz-FR2-2-r17 BIT STRING (SIZE (8)) OPTIONAL, -- R4 15-4 UE support of CBW for 960kHz SCS channelBWs-DL-SCS-960kHz-FR2-2-r17 BIT STRING (SIZE (8)) OPTIONAL, channelBWs-UL-SCS-960kHz-FR2-2-r17 BIT STRING (SIZE (8)) OPTIONAL, -- R4 17-1 UL gap for Tx power management ul-GapFR2-r17 ENUMERATED {supported} OPTIONAL, -- R1 25-4: One-shot HARQ ACK feedback triggered by DCI format 1_2 oneShotHARQ-feedbackTriggeredByDCI-1-2-r17 ENUMERATED {supported} OPTIONAL, -- R1 25-5: PHY priority handling for one-shot HARQ ACK feedback oneShotHARQ-feedbackPhy-Priority-r17 ENUMERATED {supported} OPTIONAL, -- R1 25-6: Enhanced type 3 HARQ-ACK codebook feedback enhancedType3-HARQ-CodebookFeedback-r17 SEQUENCE { enhancedType3-HARQ-Codebooks-r17 ENUMERATED {n1, n2, n4, n8}, maxNumberPUCCH-Transmissions-r17 ENUMERATED {n1, n2, n3, n4, n5, n6, n7} } OPTIONAL, -- R1 25-7: Triggered HARQ-ACK codebook re-transmission triggeredHARQ-CodebookRetx-r17 SEQUENCE { minHARQ-Retx-Offset-r17 ENUMERATED {n-7, n-5, n-3, n-1, n1}, maxHARQ-Retx-Offset-r17 ENUMERATED {n4, n6, n8, n10, n12, n14, n16, n18, n20, n22, n24} } OPTIONAL ]], [[ -- R4 22-2 support of one shot large UL timing adjustment ue-OneShotUL-TimingAdj-r17 ENUMERATED {supported} OPTIONAL, -- R1 25-2: Repetitions for PUCCH format 0, and 2 over multiple slots with K = 2, 4, 8 pucch-Repetition-F0-2-r17 ENUMERATED {supported} OPTIONAL, -- R1 25-11a: 4-bits subband CQI for NTN and unlicensed cqi-4-BitsSubbandNTN-SharedSpectrumChAccess-r17 ENUMERATED {supported} OPTIONAL, -- R1 25-16: HARQ-ACK with different priorities multiplexing on a PUCCH/PUSCH mux-HARQ-ACK-DiffPriorities-r17 ENUMERATED {supported} OPTIONAL, -- R1 25-20a: Propagation delay compensation based on Rel-15 TA procedure for NTN and unlicensed ta-BasedPDC-NTN-SharedSpectrumChAccess-r17 ENUMERATED {supported} OPTIONAL, -- R1 33-2b: DCI-based enabling/disabling ACK/NACK-based feedback for dynamic scheduling for multicast ack-NACK-FeedbackForMulticastWithDCI-Enabler-r17 ENUMERATED {supported} OPTIONAL, -- R1 33-2e: Multiple G-RNTIs for group-common PDSCHs maxNumberG-RNTI-r17 INTEGER (2..8) OPTIONAL, -- R1 33-2f: Dynamic multicast with DCI format 4_2 dynamicMulticastDCI-Format4-2-r17 ENUMERATED {supported} OPTIONAL, -- R1 33-2i: Supported maximal modulation order for multicast PDSCH maxModulationOrderForMulticast-r17 CHOICE { fr1-r17 ENUMERATED {qam256, qam1024}, fr2-r17 ENUMERATED {qam64, qam256} } OPTIONAL, -- R1 33-3-1: Dynamic Slot-level repetition for group-common PDSCH for TN and licensed dynamicSlotRepetitionMulticastTN-NonSharedSpectrumChAccess-r17 ENUMERATED {n8, n16} OPTIONAL, -- R1 33-3-1a: Dynamic Slot-level repetition for group-common PDSCH for NTN and unlicensed dynamicSlotRepetitionMulticastNTN-SharedSpectrumChAccess-r17 ENUMERATED {n8, n16} OPTIONAL, -- R1 33-4-1: DCI-based enabling/disabling NACK-only based feedback for dynamic scheduling for multicast nack-OnlyFeedbackForMulticastWithDCI-Enabler-r17 ENUMERATED {supported} OPTIONAL, -- R1 33-5-1b: DCI-based enabling/disabling ACK/NACK-based feedback for dynamic scheduling for multicast ack-NACK-FeedbackForSPS-MulticastWithDCI-Enabler-r17 ENUMERATED {supported} OPTIONAL, -- R1 33-5-1h: Multiple G-CS-RNTIs for SPS group-common PDSCHs maxNumberG-CS-RNTI-r17 INTEGER (2..8) OPTIONAL, -- R1 33-10: Support group-common PDSCH RE-level rate matching for multicast re-LevelRateMatchingForMulticast-r17 ENUMERATED {supported} OPTIONAL, -- R1 36-1a: Support of 1024QAM for PDSCH with maximum 2 MIMO layers for FR1 pdsch-1024QAM-2MIMO-FR1-r17 ENUMERATED {supported} OPTIONAL, -- R4 14-3 PRS measurement without MG prs-MeasurementWithoutMG-r17 ENUMERATED {cpLength, quarterSymbol, halfSymbol, halfSlot} OPTIONAL, -- R4 25-7: The number of target LEO satellites the UE can monitor per carrier maxNumber-LEO-SatellitesPerCarrier-r17 INTEGER (3..4) OPTIONAL, -- R1 27-3-3 DL PRS Processing Capability outside MG - buffering capability prs-ProcessingCapabilityOutsideMGinPPW-r17 SEQUENCE (SIZE(1..3)) OF PRS-ProcessingCapabilityOutsideMGinPPWperType-r17 OPTIONAL, -- R1 27-15a: Positioning SRS transmission in RRC_INACTIVE state for initial UL BWP with semi-persistent SRS srs-SemiPersistent-PosResourcesRRC-Inactive-r17 SEQUENCE { maxNumOfSemiPersistentSRSposResources-r17 ENUMERATED {n1, n2, n4, n8, n16, n32, n64}, maxNumOfSemiPersistentSRSposResourcesPerSlot-r17 ENUMERATED {n1, n2, n3, n4, n5, n6, n8, n10, n12, n14} } OPTIONAL, -- R2: UE support of CBW for 120kHz SCS channelBWs-DL-SCS-120kHz-FR2-2-r17 BIT STRING (SIZE (8)) OPTIONAL, channelBWs-UL-SCS-120kHz-FR2-2-r17 BIT STRING (SIZE (8)) OPTIONAL ]], [[ -- R1 30-4a: DM-RS bundling for PUSCH repetition type A dmrs-BundlingPUSCH-RepTypeA-r17 ENUMERATED {supported} OPTIONAL, -- R1 30-4b: DM-RS bundling for PUSCH repetition type B dmrs-BundlingPUSCH-RepTypeB-r17 ENUMERATED {supported} OPTIONAL, -- R1 30-4c: DM-RS bundling for TB processing over multi-slot PUSCH dmrs-BundlingPUSCH-multiSlot-r17 ENUMERATED {supported} OPTIONAL, -- R1 30-4d: DMRS bundling for PUCCH repetitions dmrs-BundlingPUCCH-Rep-r17 ENUMERATED {supported} OPTIONAL, -- R1 30-4e: Enhanced inter-slot frequency hopping with inter-slot bundling for PUSCH interSlotFreqHopInterSlotBundlingPUSCH-r17 ENUMERATED {supported} OPTIONAL, -- R1 30-4f: Enhanced inter-slot frequency hopping for PUCCH repetitions with DMRS bundling interSlotFreqHopPUCCH-r17 ENUMERATED {supported} OPTIONAL, -- R1 30-4g: Restart DM-RS bundling dmrs-BundlingRestart-r17 ENUMERATED {supported} OPTIONAL, -- R1 30-4h: DM-RS bundling for non-back-to-back transmission dmrs-BundlingNonBackToBackTX-r17 ENUMERATED {supported} OPTIONAL ]], [[ -- R1 33-5-1e: Dynamic Slot-level repetition for SPS group-common PDSCH for multicast maxDynamicSlotRepetitionForSPS-Multicast-r17 ENUMERATED {n8, n16} OPTIONAL, -- R1 33-5-1g: DCI-based enabling/disabling NACK-only based feedback for SPS group-common PDSCH for multicast nack-OnlyFeedbackForSPS-MulticastWithDCI-Enabler-r17 ENUMERATED {supported} OPTIONAL, -- R1 33-5-1i: Multicast SPS scheduling with DCI format 4_2 sps-MulticastDCI-Format4-2-r17 ENUMERATED {supported} OPTIONAL, -- R1 33-5-2: Multiple SPS group-common PDSCH configuration on PCell sps-MulticastMultiConfig-r17 INTEGER (1..8) OPTIONAL, -- R1 33-6-1: DL priority indication for multicast in DCI priorityIndicatorInDCI-Multicast-r17 ENUMERATED {supported} OPTIONAL, -- R1 33-6-1a: DL priority configuration for SPS multicast priorityIndicatorInDCI-SPS-Multicast-r17 ENUMERATED {supported} OPTIONAL, -- R1 33-6-2: Two HARQ-ACK codebooks simultaneously constructed for supporting HARQ-ACK codebooks with different priorities -- for unicast and multicast at a UE twoHARQ-ACK-CodebookForUnicastAndMulticast-r17 ENUMERATED {supported} OPTIONAL, -- R1 33-6-3: More than one PUCCH for HARQ-ACK transmission for multicast or for unicast and multicast within a slot multiPUCCH-HARQ-ACK-ForMulticastUnicast-r17 ENUMERATED {supported} OPTIONAL, -- R1 33-9: Supporting unicast PDCCH to release SPS group-common PDSCH releaseSPS-MulticastWithCS-RNTI-r17 ENUMERATED {supported} OPTIONAL ]], [[ -- R1 41-3-1a UE automomous TA adjustment when cell-reselection happens posUE-TA-AutoAdjustment-r18 ENUMERATED {supported} OPTIONAL, -- R1 41-4-6a support a Rel-17 single DCI scheduling positioning SRS resource sets across the linked carriers -- for SRS bandwidth aggregation in RRC_CONNECTED state posJointTriggerBySingleDCI-RRC-Connected-r18 ENUMERATED {supported} OPTIONAL, -- R1 41-5-1a PRS measurement with Rx frequency hopping in RRC_INACTIVE for RedCap UEs dl-PRS-MeasurementWithRxFH-RRC-InactiveforRedCap-r18 ENUMERATED {supported} OPTIONAL, -- R1 41-5-1b PRS measurement with Rx frequency hopping in RRC_IDLE for RedCap UEs dl-PRS-MeasurementWithRxFH-RRC-IdleforRedCap-r18 ENUMERATED {supported} OPTIONAL, -- R1 42-4: Cell DTX and/or DRX operation based on RRC configuration nes-CellDTX-DRX-r18 ENUMERATED {cellDTXonly, cellDRXonly, both} OPTIONAL, -- R1 42-5: Cell DTX/DRX operation triggered by DCI format 2_9 nes-CellDTX-DRX-DCI2-9-r18 ENUMERATED {supported} OPTIONAL, -- R1 45-6: UE-based TA measurement ue-TA-Measurement-r18 INTEGER (1..8) OPTIONAL, -- R1 45-7: TA indication in cell switch command ta-IndicationCellSwitch-r18 ENUMERATED {supported} OPTIONAL, -- R1 50-1: Multi-PUSCHs for Configured Grant multiPUSCH-CG-r18 ENUMERATED {n16, n32} OPTIONAL, -- R1 50-1a: Multiple active multi-PUSCHs configured grant configurations for a BWP of a serving cell multiPUSCH-ActiveConfiguredGrant-r18 SEQUENCE { maxNumberConfigsPerBWP ENUMERATED {n1, n2, n4, n8, n12}, maxNumberConfigsAllCC-FR1 INTEGER (2..32), maxNumberConfigsAllCC-FR2 INTEGER (2..32) } OPTIONAL, -- R1 50-2: UCI indication of unused CG-PUSCH transmission occasions cg-PUSCH-UTO-UCI-Ind-r18 ENUMERATED {supported} OPTIONAL, -- R1 50-3: PDCCH monitoring resumption after UL NACK pdcch-MonitoringResumptionAfterUL-NACK-r18 ENUMERATED {supported} OPTIONAL, -- R1 51-1: support for 3MHz channel bandwidth support-3MHz-ChannelBW-r18 ENUMERATED {supported} OPTIONAL, -- R1 51-2: support 12 PRB CORESET0 support-12PRB-CORESET0-r18 ENUMERATED {supported} OPTIONAL, -- R1 52-1: Reception of NR PDCCH candidates overlapping with LTE CRS REs nr-PDCCH-OverlapLTE-CRS-RE-r18 SEQUENCE { overlapInRE-r18 ENUMERATED {oneSymbolNoOverlap, someOrAllSymOverlap}, overlapInSymbol-r18 ENUMERATED {symbol2,symbol1And2} } OPTIONAL, -- Editor's Note: someOrAllSymOverlap considers to be supported in overlapInRE-r18 only if RAN4 performance requirements for -- someOrAllSymOverlap are not defined -- R1 52-1a: Reception of NR PDCCH candidates overlapping with LTE CRS REs with multiple non-overlapping CRS rate matching patterns nr-PDCCH-OverlapLTE-CRS-RE-MultiPatterns-r18 ENUMERATED {supported} OPTIONAL, -- R1 52-1b: NR PDCCH reception that overlaps with LTE CRS within a single span of 3 consecutive OFDM symbols that is within the -- first 4 OFDM symbols in a slot nr-PDCCH-OverlapLTE-CRS-RE-Span-3-4-r18 ENUMERATED {supported} OPTIONAL, -- R1 52-2: Two LTE-CRS overlapping rate matching patterns within NR 15 kHz carrier overlapping with LTE carrier (regardless of -- support or configuration of multi-TRP) twoRateMatchingEUTRA-CRS-patterns-3-4-r18 SEQUENCE { maxNumberPatterns-r18 INTEGER (2..6), maxNumberNon-OverlapPatterns-r18 INTEGER (1..3) } OPTIONAL, -- R1 52-2a: Two LTE-CRS overlapping rate matching patterns with two different values of coresetPoolIndex within NR 15 kHz carrier -- overlapping with LTE carrier overlapRateMatchingEUTRA-CRS-Patterns-3-4-Diff-CS-Pool-r18 ENUMERATED {supported} OPTIONAL, -- R1 53-3: Support RLM/BM/BFD measurements based on NCD-SSB within active BWP ncd-SSB-BWP-Wor-r18 ENUMERATED {supported} OPTIONAL, -- R1 53-4: Support Support RLM/BM/BFD measurements based on CSI-RS when CD-SSB is outside active BWP rlm-BM-BFD-CSI-RS-OutsideActiveBWP-r18 ENUMERATED {supported} OPTIONAL, -- R1 55-3: Multiple PUSCHs scheduling by single DCI for non-consecutive slots in FR1 multiPUSCH-SingleDCI-NonConsSlots-r18 ENUMERATED {supported} OPTIONAL, -- R1 55-2d: single-symbol DL-PRS used in RTT-based Propagation delay compensation pdc-maxNumberPRS-ResourceProcessedPerSlot-r18 SEQUENCE { fr1-r18 SEQUENCE { scs-15kHz-r18 ENUMERATED {n1, n2, n4, n6, n8, n12, n16, n24, n32, n48, n64} OPTIONAL, scs-30kHz-r18 ENUMERATED {n1, n2, n4, n6, n8, n12, n16, n24, n32, n48, n64} OPTIONAL, scs-60kHz-r18 ENUMERATED {n1, n2, n4, n6, n8, n12, n16, n24, n32, n48, n64} OPTIONAL }, fr2-r18 SEQUENCE { scs-60kHz-r18 ENUMERATED {n1, n2, n4, n6, n8, n12, n16, n24, n32, n48, n64} OPTIONAL, scs-120kHz-r18 ENUMERATED {n1, n2, n4, n6, n8, n12, n16, n24, n32, n48, n64} OPTIONAL } } OPTIONAL, -- R4 27-2: LowerMSD for inter-band NR CA and EN-DC lowerMSD-r18 SEQUENCE (SIZE (1..maxLowerMSD-r18)) OF LowerMSD-r18 OPTIONAL, -- R4 31-2 Beam sweeping factor reduction for FR2 unknown SCell activation beamSweepingFactorReduction-r18 SEQUENCE { reduceForCellDetection ENUMERATED {n1, n2, n4, n6}, reduceForSSB-L1-RSRP-Meas INTEGER (0..7) } OPTIONAL, -- R4 35-2: the requirements defined for ATG UE with antenna array or omni-direction antenna requirements. antennaArrayType-r18 ENUMERATED {supported} OPTIONAL, locationBasedCondHandoverATG-r18 ENUMERATED {supported} OPTIONAL, -- R4 35-3: rated maximum output power value range from 23dBm to 40dBm with 1dB as granularity at maximum modulation order and full -- PRB configurations. maxOutputPowerATG-r18 INTEGER (1..18) OPTIONAL, eventA4BasedCondHandoverNES-r18 ENUMERATED {supported} OPTIONAL, nesBasedCondHandoverWithDCI-r18 ENUMERATED {supported} OPTIONAL, rachLessHandoverNTN-r18 ENUMERATED {supported} OPTIONAL, locationBasedCondHandoverEMC-r18 ENUMERATED {supported} OPTIONAL, mt-CG-SDT-r18 ENUMERATED {supported} OPTIONAL, posSRS-RRC-InactiveInitialUL-BWP-r18 ENUMERATED {supported} OPTIONAL, posSRS-RRC-InactiveOutsideInitialUL-BWP-r18 ENUMERATED {supported} OPTIONAL, cg-SDT-PeriodicityExt-r18 ENUMERATED {supported} OPTIONAL ]] } BandNR-v16c0 ::= SEQUENCE { pusch-RepetitionTypeA-v16c0 ENUMERATED {supported} OPTIONAL, ... } LowerMSD-r18 ::= SEQUENCE { aggressorband1-r18 FreqBandIndicatorNR, aggressorband2-r18 FreqBandIndicatorNR OPTIONAL, msd-Information-r18 SEQUENCE (SIZE (1..maxLowerMSDInfo-r18)) OF MSD-Information-r18 } MSD-Information-r18 ::= SEQUENCE { msd-Type-r18 ENUMERATED {harmonic, harmonicMixing, crossBandIsolation, imd2, imd3, imd4, imd5, all, spare8, spare7, spare6, spare5,spare4, spare3, spare2, spare1}, msd-PowerClass-r18 ENUMERATED {pc1dot5, pc2, pc3}, msd-Class-r18 ENUMERATED {classI, classII, classIII, classIV, classV, classVI, classVII, classVIII } } -- Editor note: The power class related part can be updated further pending RAN4 discussion. -- TAG-RF-PARAMETERS-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,390 | 4.23.16.2 Handover of a PDU Session procedure from 3GPP to untrusted non-3GPP access (non-roaming and roaming with local breakout) | When a PDU Session is handover from 3GPP access with an I-SMF to untrusted non-3GPP access (non-roaming and roaming with local breakout), the following steps take place: 1) Step 1 of clause 4.9.2.2. 2) Step 2 of clause 4.9.2.2. 3) The step 3 in clause 4.9.2.4.2 is executed involving I-SMF instead of V-SMF, with following differences: - Figure 4.3.4.3-1 step 14 involving I-SMF instead of V-SMF. - Figure 4.3.4.3-1 step 16a: The SMF invokes Nsmf_PDUSession_StatusNotify (Release) indicating the release is due to a PDU Session Handover out of the I-SMF. - Figure 4.3.4.3-1 step 16b: the I-SMF invoke the Nsmf_PDUSession_SMContexStatusNotify (Release) indicating the Release is due to a PDU Session Handover out of the I-SMF: the AMF determines that only the SMcontext with the I-SMF is to be released but that the PDU Session is not released. The steps 2 to 3 above shall be repeated for all PDU Sessions to be moved from 3GPP access to untrusted non-3GPP access. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.23.16.2 |
5,391 | 5.18.4 Network selection by the network | The NG-RAN uses the selected PLMN/SNPN (provided by the UE at RRC establishment, or, provided by the AMF/source NG-RAN at N2/Xn handover) to select target cells for future handovers (and radio resources in general) appropriately. The network should not move the UE to another available PLMN/SNPN, e.g. by handover, as long as the selected PLMN/SNPN is available to serve the UE's location. In the case of handover or network controlled release to a PLMN in a shared network: - When multiple PLMN IDs are broadcasted in a cell selected by NG-RAN, NG-RAN shall select a target PLMN, taking into account the prioritized list of PLMN IDs provided via Mobility Restriction List from AMF. - For Xn based HO procedure, Source NG-RAN indicates the selected PLMN ID to the target NG-RAN, see TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27]. - For N2 based HO procedure, the NG-RAN indicates a selected PLMN ID to the AMF as part of the TAI sent in the HO required message. Source AMF uses the TAI information supplied by the source NG-RAN to select the target AMF/MME. The source AMF should forward the selected PLMN ID to the target AMF/MME. The target AMF/MME indicates the selected PLMN ID to the target NG-RAN/eNB so that the target NG-RAN/eNB can select target cells for future handover appropriately. - For RRC connection release with redirection to E-UTRAN procedure, NG-RAN decides the target network by using PLMN information as defined in the first bullet. A change in serving PLMN is indicated to the UE as part of the UE registration with the selected network via 5G-GUTI in 5GS. In the case of handover or network controlled release to an SNPN in a shared network, the following applies: - When multiple SNPN IDs are broadcasted in a cell selected by NG-RAN, NG-RAN shall select a target SNPN, taking into account the prioritized list of SNPN IDs provided via Mobility Restriction List from AMF. - For Xn based HO procedure, Source NG-RAN indicates the selected SNPN ID to the target NG-RAN, see TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27]. - For N2 based HO procedure, the NG-RAN indicates a selected SNPN ID to the AMF together with the TAI sent in the HO required message. Source AMF uses the selected SNPN ID together with the TAI information supplied by the source NG-RAN to select the target AMF. The source AMF should forward the selected SNPN ID to the target AMF. The target AMF indicates the selected SNPN ID to the target NG-RAN so that the target NG-RAN can select target cells for future handover appropriately. A change in serving SNPN is indicated to the UE as part of the UE registration with the selected network. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.18.4 |
5,392 | 7.1.2 NF Service Consumer - NF Service Producer interactions | The end-to-end interaction between two Network Functions (Consumer and Producer) within this NF service framework follows two mechanisms, irrespective of whether Direct Communication or Indirect Communication is used: - "Request-response": A Control Plane NF_B (NF Service Producer) is requested by another Control Plane NF_A (NF Service Consumer) to provide a certain NF service, which either performs an action or provides information or both. NF_B provides an NF service based on the request by NF_A. In order to fulfil the request, NF_B may in turn consume NF services from other NFs. In Request-response mechanism, communication is one to one between two NFs (consumer and producer) and a one-time response from the producer to a request from the consumer is expected within a certain timeframe. The NF Service Producer may also add a Binding Indication (see clause 6.3.1.0) in the Response, which may be used by the NF Service Consumer to select suitable NF service producer instance(s) for subsequent requests. For indirect communication, the NF Service Consumer copies the Binding Indication into the Routing Binding indication, that is included in subsequent requests, to be used by the SCP to discover a suitable NF service producer instance(s). Figure 7.1.2-1: "Request-response" NF Service illustration - "Subscribe-Notify": A Control Plane NF_A (NF Service Consumer) subscribes to NF Service offered by another Control Plane NF_B (NF Service Producer). Multiple Control Plane NFs may subscribe to the same Control Plane NF Service. NF_B notifies the results of this NF service to the interested NF(s) that subscribed to this NF service. The subscription request shall include the notification endpoint, i.e. a Notification Target Address and a Notification Correlation ID (e.g. the callback URL) of the NF Service Consumer to which the event notification from the NF Service Producer should be sent to. NOTE 1: The notification endpoint can be a URL and contains both the Notification Target Address and the Notification Correlation ID. The NF Service Consumer may add a Binding Indication (see clause 6.3.1.0) in the subscribe request, which may be used by the NF Service Producer to discover a suitable notification endpoint. For indirect communication, the NF Service Producer copies the Binding Indication into the Routing Binding Indication, that is included in the response, to be used by the SCP to discover a suitable notification target. The NF Service Producer may also add a Binding Indication (see clause 6.3.1.0) in the subscribe response, which may be used by the NF Service Consumer (or SCP) to select suitable NF service producer instance(s) or NF producer service instance. In addition, the subscription request may include notification request for periodic updates or notification triggered through certain events (e.g. the information requested gets changed, reaches certain threshold etc.). The subscription for notification can be done through one of the following ways: - Explicit subscription: A separate request/response exchange between the NF Service Consumer and the NF Service Producer; or - Implicit subscription: The subscription for notification is included as part of another NF service operation of the same NF Service; or - Default notification endpoint: Registration of a notification endpoint for each type of notification the NF consumer is interested to receive, as a NF service parameter with the NRF during the NF and NF service Registration procedure as specified in clause 4.17.1 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. The NF Service Consumer may also add a Binding Indication (see clause 6.3.1.0) in the response to the notification request, which may be used by the NF Service Producer to discover a suitable notification endpoint. For indirect communication, the NF Service Producer copies the Binding Indication into the Routing Binding indication that is included in subsequent notification requests. The binding indication is then used by the SCP to discover a suitable notification target. Figure 7.1.2-2: "Subscribe-Notify" NF Service illustration 1 A Control Plane NF_A may also subscribe to NF Service offered by Control Plane NF_B on behalf of Control Plane NF_C, i.e. it requests the NF Service Producer to send the event notification to another consumer(s). In this case, NF_A includes the notification endpoint, i.e. Notification Target Address) and a Notification Correlation ID, of the NF_C in the subscription request. NF_A may also additionally include the notification endpoint and a Notification Correlation ID of NF A associated with subscription change related Event ID(s), e.g. Subscription Correlation ID Change, in the subscription request, so that NF_A can receive the notification of the subscription change related event. The NF_A may add Binding Indication (see clause 6.3.1.0) in the subscribe request. Figure 7.1.2-3: "Subscribe-Notify" NF Service illustration 2 Routing of the messages for the NF interaction mechanisms above may be direct, as shown in the figures 7.1.2-1 to 7.1.2-3, or indirect. In the case of Indirect Communication, an SCP is employed by the NF service consumer. The SCP routes messages between NF service consumers and NF service producers based on the Routing Binding Indication if available, and may do discovery and associated selection of the NF service producer on behalf of a NF service consumer. Figure 7.1.2-4 shows the principle for a request-response interaction and figure 7.1.2-5 shows an example of a subscribe-notify interaction. Figure 7.1.2-4: Request response using Indirect Communication Figure 7.1.2-5: Subscribe-Notify using Indirect Communication NOTE: The subscribe request and notify request can be routed by different SCPs. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 7.1.2 |
5,393 | 5.3.8 Detach procedure 5.3.8.1 General | The Detach procedure allows: - the UE to inform the network that it does not want to access the EPS any longer, and - the network to inform the UE that it does not have access to the EPS any longer. The UE is detached either explicitly or implicitly: - Explicit detach: The network or the UE explicitly requests detach and signal with each other. - Implicit detach: The network detaches the UE, without notifying the UE. This is typically the case when the network presumes that it is not able to communicate with the UE, e.g. due to radio conditions. Four detach procedures are provided when the UE accesses the EPS through E-UTRAN. The first detach procedure is UE-initiated detach procedure and other detach procedures are network-initiated detach procedure: - UE-Initiated Detach Procedure. In the ISR activated case the UE initiated detach is split into two sub procedures, one for UE camping on E-UTRAN and one for UE camping on GERAN/UTRAN; - MME-Initiated Detach Procedure; - SGSN-Initiated Detach procedure with ISR activated; - HSS-Initiated Detach Procedure. NOTE 1: The MME and the UE may enter EMM-DEREGISTERED state without the above procedures. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.3.8 |
5,394 | 8.7.15 TDD FDD DC (4 Rx) | The parameters specified in Table 8.7.15-1 are valid for all TDD FDD tests for 4Rx capable UEs unless otherwise stated. Table 8.7.15-1: Common Test Parameters (TDD FDD) For UE not supporting 256QAM, the TB success rate shall be higher than 85% when PDSCH are scheduled with FRC in Table 8.7.15-2 with the downlink physical channel setup according to Annex C.3.2. For UE supporting 256QAM, the TB success rate shall be higher than 85% when PDSCH are scheduled with FRC in Table 8.7.15-3 with the downlink physical channel setup according to Annex C.3.2. For UE supporting 256QAM, the requirement with 64QAM is not applicable. The TB success rate is defined as 100%*NDL_correct_rx/ (NDL_newtx + NDL_retx), where NDL_newtx is the number of newly transmitted DL transport blocks, NDL_retx is the number of retransmitted DL transport blocks, and NDL_correct_rx is the number of correctly received DL transport blocks. The TB success rate across CGs shall be sustained during at least 300 frames. Table 8.7.15-2: Per-CC FRC for SDR test (TDD-FDD 64QAM) Table 8.7.15-3: Per-CC FRC for SDR test (TDD-FDD 256QAM) DC configuration, bandwidth combination and MIMO layer on each CC is determined by following procedure. - Select one DC bandwidth combination among all supported DC configurations with bandwidth combination and MIMO layer on each CC that leads to largest equivalent aggregated bandwidth among all DC bandwidth combinations supported by UE. Equivalent aggregated bandwidth is defined as where is number of CCs, and is MIMO layer and bandwidth of CC . - When there are multiple sets of {DC configuration, bandwidth combination, MIMO layer} with same largest aggregated bandwidth, select one among sets with largest number of 4 layer CCs. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.7.15 |
5,395 | 4.1.3.1.3 Substates of state GMM-REGISTERED | The state GMM-REGISTERED is subdivided into several substate as explained below. The substates pertain to the whole MS (ME alone if no SIM/USIM is inserted, or ME plus SIM/USIM). 4.1.3.1.3.1 GMM-REGISTERED.NORMAL-SERVICE User data and signalling information may be sent and received. 4.1.3.1.3.2 GMM-REGISTERED.SUSPENDED (A/Gb mode only) The MS shall enter this substate when entering dedicated mode and when the MS limitations makes it unable to communicate on GPRS channels. In this substate, no user data should be sent and no signalling information shall be sent. The MS shall leave this substate when leaving dedicated mode. 4.1.3.1.3.3 GMM-REGISTERED.UPDATE-NEEDED The MS has to perform a routing area updating procedure, but its access class is not allowed in the cell due to access class control (see subclause 4.1.1.2.1). The procedure will be initiated as soon as access is granted (this might be due to a cell-reselection or due to change of the access classes allowed in the current cell). No GMM procedure except routing area updating shall be initiated by the MS in this substate. In this substate, no user data and no signalling information shall be sent. 4.1.3.1.3.4 GMM-REGISTERED.ATTEMPTING-TO-UPDATE A routing area updating procedure failed due to a missing response from the network. The MS retries the procedure controlled by timers and a GPRS attempt counter. No GMM procedure except routing area updating shall be initiated by the MS in this substate. No data shall be sent or received. 4.1.3.1.3.5 GMM-REGISTERED.NO-CELL-AVAILABLE GPRS coverage has been lost or PSM is active in the MS. If PSM is active, the MS can deactivate PSM at any time by activating the AS layer when the MS needs to send mobile originated signalling or user data. Otherwise, the MS shall not initiate any GMM procedures except of cell (and PLMN) reselection. Figure 4.1b/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] :GMM main states in the MS 4.1.3.1.3.6 GMM-REGISTERED.LIMITED-SERVICE A cell is selected, which is known not to be able to provide normal service. The MS will remain in this sub-state until a cell is selected which is able to provide normal service. 4.1.3.1.3.7 GMM-REGISTERED.ATTEMPTING-TO-UPDATE-MM A combined routing area updating procedure or a combined GPRS attach procedure was successful for GPRS services only. The MS retries the procedure controlled by timers and a GPRS attempt counter. User data and signalling information may be sent and received. 4.1.3.1.3.8 GMM-REGISTERED.IMSI-DETACH-INITIATED The MS performs a combined GPRS detach procedure for non-GPRS services only (detach type "IMSI Detach"). This state is entered if the MS is attached for GPRS and non-GPRS services in a network that operates in network mode I and wants to detach for non-GPRS services only. User data and signalling information may be sent and received. 4.1.3.1.3.9 GMM-REGISTERED.PLMN-SEARCH The mobile station is searching for PLMNs. This substate is left either when a cell has been selected (the new substate is NORMAL-SERVICE or LIMITED-SERVICE) or when it has been concluded that no cell is available at the moment (the new substate is NO-CELL-AVAILABLE). | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.1.3.1.3 |
5,396 | 8.8 Messages with semantically incorrect contents | When a message with semantically incorrect contents is received, the foreseen reactions of the procedural part of 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] (i.e. of clauses 3, 4, 5, 6) are performed. If however no such reactions are specified, the MS shall ignore the message except for the fact that, if an RR connection exists, it returns a status message (STATUS, or MM STATUS depending on the PD) with cause value # 95 "semantically incorrect message". If the message was a GMM message the GMM-STATUS message with cause #95 "semantically incorrect message" shall be returned. If the message was an SM message the SM-STATUS message with cause # 95 "semantically incorrect message" shall be returned. The network should follow the same procedure except that a status message is not normally transmitted. Semantic checking of the Facility information element value part (defined in 3GPP TS 24.08[ None ] 0 [24]) is the subject of the technical specifications 3GPP TS 24.010[ Mobile radio interface layer 3; Supplementary services specification; General aspects ] [21] and the 3GPP TS 24.08[ None ] x series. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 8.8 |
5,397 | 4.16.1.10 Number of Successful prepared SN terminated bearers at Secondary Node Additions | a) This measurement provides the number of Successful SN terminated bearers at Secondary Node Additions. b) CC c) On transmission by the MN of an SGNB ADDITION REQUEST ACKNOWLEDGE message (TS 36.423[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 Application Protocol (X2AP) ] [10]) to SN when Secondary Node Additions with SN terminated bearers. Each successful ERAB added to the relevant measurement per bearer type. The sum of all supported per bearer type measurements shall equal the total number of E-RABs successfully setup. In case only a subset of per bearer type measurements is supported, a sum subcounter will be provided first. SGNB Addition Trigger Indication (TS 36.423[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 Application Protocol (X2AP) ] [10]) excludes SN change, inter-eNB HO, intra-eNB HO. d) Each measurement is an integer value. e) The measurement name has the form ERAB.SNAdditionSuccPrepAtSnAddition, ERAB. SNAdditionSuccPrepAtSnAddition.SCG, ERAB. SNAdditionSuccPrepAtSnAddition.SCGSplit. f) EUtranCellFDD EUtranCellTDD g) Valid for packet switched traffic h) EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.16.1.10 |
5,398 | 4.23.12.3 EPS to 5GS mobility registration procedure (Idle and Connected State) using N26 interface with I-SMF insertion | For EPS to 5GS Mobility registration procedure using N26 with I-SMF insertion, the procedure "EPS to 5GS Mobility Registration Procedure (Idle and Connected State) using N26 interface" defined in clause 4.11.1.3.3 for the home routed-roaming case are re-used, with the following change: - The V-SMF is replaced by I-SMF and H-SMF is replaced by SMF, V-UPF is replaced by I-UPF. - The V-SMF selection is replaced by the I-SMF selection. - The V-CN Tunnel Info is replaced by Tunnel Info at I-UPF, H-CN Tunnel Info is replaced by Tunnel Info at UPF(PSA). | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.23.12.3 |
5,399 | – DMRS-UplinkConfig | The IE DMRS-UplinkConfig is used to configure uplink demodulation reference signals for PUSCH. DMRS-UplinkConfig information element -- ASN1START -- TAG-DMRS-UPLINKCONFIG-START DMRS-UplinkConfig ::= SEQUENCE { dmrs-Type ENUMERATED {type2} OPTIONAL, -- Need S dmrs-AdditionalPosition ENUMERATED {pos0, pos1, pos3} OPTIONAL, -- Need S phaseTrackingRS SetupRelease { PTRS-UplinkConfig } OPTIONAL, -- Need M maxLength ENUMERATED {len2} OPTIONAL, -- Need S transformPrecodingDisabled SEQUENCE { scramblingID0 INTEGER (0..65535) OPTIONAL, -- Need S scramblingID1 INTEGER (0..65535) OPTIONAL, -- Need S ..., [[ dmrs-Uplink-r16 ENUMERATED {enabled} OPTIONAL -- Need R ]] } OPTIONAL, -- Need R transformPrecodingEnabled SEQUENCE { nPUSCH-Identity INTEGER(0..1007) OPTIONAL, -- Need S sequenceGroupHopping ENUMERATED {disabled} OPTIONAL, -- Need S sequenceHopping ENUMERATED {enabled} OPTIONAL, -- Need S ..., [[ dmrs-UplinkTransformPrecoding-r16 SetupRelease {DMRS-UplinkTransformPrecoding-r16} OPTIONAL -- Need M ]] } OPTIONAL, -- Need R ..., [[ dmrs-TypeEnh-r18 ENUMERATED {enabled} OPTIONAL -- Need R ]] } DMRS-UplinkTransformPrecoding-r16 ::= SEQUENCE { pi2BPSK-ScramblingID0 INTEGER(0..65535) OPTIONAL, -- Need S pi2BPSK-ScramblingID1 INTEGER(0..65535) OPTIONAL -- Need S } -- TAG-DMRS-UPLINKCONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,400 | W.4.4 Security handling in network sharing scenario | In Multiple-Operator Core Network (MOCN) network sharing scenarios, if MBS content protection is needed, then the content may be protected at the application layer (c.f., W.4.2). NOTE 1: The content protection mechanism used at the application layer is outside the scope of 3GPP. If service-layer security specified in clause W.4.1.3 of the present document is used in MOCN network sharing scenarios, the AF may be required to generate the MSK, MSK ID, MTK and MTK ID common to the participating PLMNs. The AF provides the generated MSK, MSK ID, MTK and MTK ID to the MBSSF(s) of the participating PLMNs, when creating broadcast MBS sessions and also when key update is required. Furthermore, it is up to the AF to select a MCC and MNC among the PLMNs for the Key Domain ID. As mentioned in clause 6.3.2.1 of TS 33.246[ 3G Security; Security of Multimedia Broadcast/Multicast Service (MBMS) ] [102], the UE should not try to use the MCC and MNC in another context, e.g., the UE should not compare the received MCC || MNC to parameters in radio level. NOTE 2: Security aspects between the AF and the MBSSF(s) is outside the scope of 3GPP. NOTE 3: If the MBSSF uses MSK and MTK generated by itself to protect the traffic, the resource sharing during network sharing will not be used. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | W.4.4 |
Subsets and Splits
No saved queries yet
Save your SQL queries to embed, download, and access them later. Queries will appear here once saved.