Datasets:

Exploration-Lab

/

MM-TelecoBench

like 1

Follow

Exploration Lab 62

4.1.2.2 Successful RRC connection re-establishments

a) This measurement provides the number of successful RRC connection re-establishments for each re-establishment cause. b) CC. c) Receipt by the eNodeB/RN of an RRCConnectionReestablishmentComplete message following a RRC connection reestablishment request. Each RRCConnectionReestablishmentComplete message received is added to the relevant per reestablishment cause measurement. The possible causes are included in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]. The sum of all supported per cause measurements shall equal the total number of successful RRC connection re-establishments. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first. d) Each measurement is an integer value. The number of measurements is equal to the number of causes plus a possible sum value identified by the .sum suffix. e) The measurement name has the form RRC.ConnReEstabSucc.Cause where Cause identifies the establishment cause. f) EUtranCellFDD EUtranCellTDD g) Valid for packet switching. 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.1.2.2

4.5.1.3.1 Mobile Terminating CM Activity

When a CM sublayer entity in the network requests the MM sublayer to establish a MM connection, the MM sublayer will request the establishment of an RR connection to the RR sublayer if no RR connection to the desired mobile station exists. The MM sublayer is informed when the paging procedure is finished (see 3GPP TS 44.018[ None ] [84] subclause 3.3.2 and 3GPP TS 25.331[ None ] [23c]) and the mobile station shall enter the MM state WAIT FOR NETWORK COMMAND and stop the timer T3246 if running. In A/Gb mode, when an RR connection is established (or if it already exists at the time the request is received), the MM sublayer may initiate any of the MM common procedures (except IMSI detach); it may request the RR sublayer to perform the RR classmark interrogation procedure, and/or the security mode setting procedure. In Iu mode, when an RR connection is established (or if it already exists at the time the request is received), the MM sublayer may initiate any of the MM common procedures (except IMSI detach); it may request the RR sublayer to perform the security mode control procedure. When all MM and RR procedures are successfully completed which the network considers necessary, the MM sublayer will inform the requesting mobile terminating CM sublayer entity on the success of the MM connection establishment. If an RR connection already exists and no MM specific procedure is running, the network may also establish a new mobile terminating MM connection by sending a CM message with a new PD/TI combination. If the MS receives the first CM message in the MM states WAIT FOR NETWORK COMMAND or RR CONNECTION RELEASE NOT ALLOWED, the MS shall stop and reset the timers T3240 and T3241 and shall enter the MM state MM CONNECTION ACTIVE. In A/Gb mode, if the establishment of an RR connection is unsuccessful, or if any of the MM common procedures or the security mode setting fail, this is indicated to the CM layer with an appropriate error cause. In Iu mode, if the establishment of an RR connection is unsuccessful, or if any of the MM common procedures or the security mode control fail, this is indicated to the CM layer with an appropriate error cause. If an RR connection used for a MM specific procedure exists to the mobile station, the CM request may be rejected or delayed depending on implementation. When the MM specific procedure has been completed, the network may use the same RR connection for the delayed CM request. Only applicable in case of VGCS talking: In the MM CONNECTION ACTIVE (GROUP TRANSMIT MODE) the mobile station is in RR Group transmit mode. There shall be only one MM connection active. When in MM CONNECTION ACTIVE (GROUP TRANSMIT MODE) state, the MM sublayer in the network shall reject the request for the establishment of another MM connection by any CM layer. If the RR sublayer in the network indicates a request to perform a transfer of the mobile station from RR connected mode to RR Group transmit mode which will result in a transition from MM CONNECTION ACTIVE state to MM CONNECTION ACTIVE (GROUP TRANSMIT MODE) state in the MM sublayer, the MM sublayer shall not allow the transition if more than one MM connection is active with the mobile station.

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.5.1.3.1

8.10.2.1.4 Enhanced Downlink Control Channel Performance Requirement Type A - 4 Tx Antenna Port with Non-Colliding CRS Dominant Interferer

The purpose of this test is to verify the Enhanced Downlink Control Channel Performance Requirement Type A for PDCCH/PCFICH with 4 transmit antennas for the case of dominant interferer with the non-colliding CRS pattern and applying interference model defined in clause B.7.1. For the parameters specified in Table 8.10.2.1.4-1, the average probability of a missed downlink scheduling grant (Pm-dsg) shall be below the specified value in Table 8.10.2.1.4-2. In Table 8.10.2.1.4-1, Cell 1 is the serving cell, and Cell 2 is the aggressor cell. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1 and Cell, respectively. Table 8.10.2.1.4-1: Test Parameters for PDCCH/PCFICH Table 8.10.2.1.4-2: Minimum Performance for PDCCH/PCFICH for Enhanced Downlink Control Channel Performance Requirement Type A

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.10.2.1.4

19.3.3 Decorated NAI

The Decorated NAI shall take the form of a NAI and shall have the form 'homerealm!username@otherrealm' or 'Visitedrealm!homerealm!username@otherrealm' as specified in clause 2.7 of the IETF RFC 4282 [53]. The realm part of Decorated NAI consists of 'otherrealm', see the IETF RFC 4282 [53]. 'Homerealm' is the realm as specified in clause 19.2, using the HPLMN ID ('homeMCC' + 'homeMNC)'. 'Visitedrealm' is the realm built using the VPLMN ID ('VisitedMCC' + 'VisitedMNC)', 'Otherrealm' is: - the realm built using the PLMN ID (visitedMCC + visited MNC) if the service provider selected as a result of the service provider selection (see 3GPP TS 24.302[ Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networks; Stage 3 ] [77]) has a PLMN ID; or - a domain name of a service provider if the selected service provider does not have a PLMN ID (3GPP TS 24.302[ Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networks; Stage 3 ] [77]). When the username part of Decorated NAI includes the IMSI and the service provider has a PLMN ID, the Decorated NAI shall be built following the same steps as specified for Root NAI in clause 19.3.2. The result will be a decorated NAI of the form: - nai.epc.mnc<homeMNC>.mcc<homeMCC>.3gppnetwork.org !0<IMSI>@nai.epc.mnc<visitedMNC>.mcc<visitedMCC>.3gppnetwork.org for EAP AKA authentication. or - nai.epc.mnc<homeMNC>.mcc<homeMCC>.3gppnetwork.org !6<IMSI>@nai.epc.mnc<visitedMNC>.mcc<visitedMCC>.3gppnetwork.org for EAP AKA' authentication. For example, if the service provider has a PLMN ID and the IMSI is 234150999999999 (MCC = 234, MNC = 15) and the PLMN ID of the Selected PLMN is MCC = 610, MNC = 71, then the Decorated NAI takes the form either as: - nai.epc.mnc015.mcc234.3gppnetwork.org!0234150999999999@nai.epc.mnc071.mcc610.3gppnetwork.org for EAP AKA authentication or - nai.epc.mnc015.mcc234.3gppnetwork.org!6234150999999999@nai.epc.mnc071.mcc610.3gppnetwork.org for EAP AKA' authentication. For example, if the domain name of a service provider is 'realm.org' and IMSI-based permanent username is used, then the Decorated NAI takes the form either as: - nai.epc.mnc<homeMNC>.mcc<homeMCC>.3gppnetwork.org !0<IMSI>@realm.org for EAP AKA authentication or - nai.epc.mnc<homeMNC>.mcc<homeMCC>.3gppnetwork.org !6<IMSI>@realm.org for EAP AKA' authentication. If the UE has selected a WLAN that directly interworks with a service provider in the Equivalent Visited Service Providers (EVSP) list provided by the RPLMN, see 3GPP TS 23.402[ Architecture enhancements for non-3GPP accesses ] [77], clause 4.8.2b, then the decorated NAI is constructed to include the realm of this service provider and the realm of RPLMN. If the domain name of a service provider is 'realm.org' and IMSI-based permanent username is used, then the Decorated NAI with double decoration takes the form either as: - nai.epc.mnc<rplmnMNC>.mcc<rplmnMCC>.3gppnetwork.org !nai.epc.mnc<homeMNC>.mcc<homeMCC>.3gppnetwork.org!0<IMSI>@realm.org for EAP AKA authentication or - nai.epc.mnc<rplmnMNC>.mcc<rplmnMCC>.3gppnetwork.org !nai.epc.mnc<homeMNC>.mcc<homeMCC>.3gppnetwork.org!6<IMSI>@realm.org for EAP AKA' authentication. When the username part of Decorated NAI includes a Fast Re-authentication NAI, the Decorated NAI shall be built following the same steps as specified for the Fast Re-authentication NAI in clause 19.3.4. When the username part of Decorated NAI includes a Pseudonym, the Decorated NAI shall be built following the same steps as specified for the Pseudonym identity in clause 19.3.5.

3GPP TS 23.003

Numbering, addressing and identification

CT WG4

3GPP Series : 23 , Technical realization ("stage 2")

19.3.3

16.9.9.3 Sidelink Specific Consistent LBT Failure

SL-specific consistent LBT failure detection and recovery procedure is supported for SL-U. When the UE detects SL-specific consistent LBT failure, it performs the actions as specified in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [6]. SL-specific consistent LBT failure detection is per RB-set. A SL UE in RRC_CONNECTED can indicate SL-specific consistent LBT failure to the gNB using a SL MAC CE that indicates the RB set(s) where SL-specific consistent LBT failure was detected. A SL UE using mode 2 resource allocation triggers resource reselection and/or resource pool reselection upon SL-specific consistent LBT failure. In such case, resources in failed RB set(s) are excluded from resource (re)selection until consistent LBT failure on the RB set(s) is cancelled based on conditions in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [6]. The UE triggers SL RLF for all PC5-RRC connections when the UE has triggered SL-specific consistent LBT failure in all RB sets.

3GPP TS 38.300

NR; NR and NG-RAN Overall description; Stage-2

RAN2

3GPP Series : 38 , Radio technology beyond LTE

16.9.9.3

5.5.4.7 Event A6 (Neighbour becomes offset better than SCell)

The UE shall: 1> consider the entering condition for this event to be satisfied when condition A6-1, as specified below, is fulfilled; 1> consider the leaving condition for this event to be satisfied when condition A6-2, as specified below, is fulfilled; 1> for this measurement, consider the (secondary) cell corresponding to the measObjectNR associated to this event to be the serving cell. NOTE: The reference signal(s) of the neighbour(s) and the reference signal(s) of the SCell are both indicated in the associated measObjectNR. Inequality A6-1 (Entering condition) Mn + Ocn – Hys > Ms + Ocs + Off Inequality A6-2 (Leaving condition) Mn + Ocn + Hys < Ms + Ocs + Off The variables in the formula are defined as follows: Mn is the measurement result of the neighbouring cell, not taking into account any offsets. Ocn is the cell specific offset of the neighbour cell (i.e. cellIndividualOffset as defined within the associated measObjectNR), and set to zero if not configured for the neighbour cell. Ms is the measurement result of the serving cell, not taking into account any offsets. Ocs is the cell specific offset of the serving cell (i.e. cellIndividualOffset as defined within the associated measObjectNR, or cellIndividualOffset as defined within reportConfigNR), and is set to zero if not configured for the serving cell. Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigNR for this event). Off is the offset parameter for this event (i.e. a6-Offset as defined within reportConfigNR for this event). Mn, Ms are expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR. Ocn, Ocs, Hys, Off are expressed in dB.

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

5.5.4.7

8.19.4.1 Inter-gNB-DU switch from direct to indirect path

The signalling flow for U2N Remote UE switch from direct to indirect path with gNB-DU change is shown in Figure 8.19.4.1-1. Figure 8.19.4.1-1: U2N Remote UE Direct-to-indirect Path Switch with gNB-DU change procedure 1. The Uu measurement configuration and measurement report signalling is performed between U2N Remote UE and gNB-CU to evaluate both relay link measurement and Uu link measurement. The U2N Remote UE may report one or multiple candidate U2N Relay UE(s) and Uu measurement results after it measures/discovers the candidate U2N Relay UE(s). 2. The gNB-CU decides to switch the U2N Remote UE to a target U2N Relay UE under a different gNB-DU (i.e., target gNB-DU). 3. The reconfiguration to target U2N Relay UE is performed among U2N Relay UE, the target gNB-DU and gNB-CU, if the U2N Relay UE is in RRC_CONNECTED state. The gNB-CU sends an RRCReconfiguration message to the target U2N Relay UE. If the target Relay UE is in RRC_IDLE/INACTIVE state, this step is skipped and the configuration to the target U2N Relay UE is performed in Step 10. 4. gNB-CU sends the UE CONTEXT SETUP REQUEST message for the U2N Remote UE to the target gNB-DU, which contains the path switch configuration at least. 5. gNB-DU responds with the UE CONTEXT SETUP RESPONSE message to gNB-CU. 6. gNB-CU sends the UE CONTEXT MODIFICATION REQUEST message by including the RRCReconfiguration message to the source gNB-DU. The contents in the RRCReconfiguration message may include at least path switch configuration, PC5 Relay RLC channel configuration for relaying traffic, bearer mapping configuration and the associated radio bearer(s). 7. The source gNB-DU sends the RRCReconfiguration message to the U2N Remote UE. The U2N Remote UE stops UP and CP transmission over Uu after reception of RRCReconfiguration message from the gNB. 8. The source gNB-DU sends the UE CONTEXT MODIFICATION RESPONSE message to the gNB-CU. 9. The U2N Remote UE establishes PC5 connection with target U2N Relay UE. 10. The U2N Remote UE completes the path switch procedure by sending the RRCReconfigurationComplete message to the target gNB-DU via the target U2N Relay UE. In case the U2N relay UE is in RRC_IDLE/ INACTIVE state, when the U2N relay UE receives the RRCReconfigurationComplete message, the reception of the RRCReconfigurationComplete message will first trigger RRC setup/resume procedure for the U2N relay UE to enter RRC_CONNECTED state. 11. The target gNB-DU sends the UL RRC MESSAGE TRANSFER message to gNB-CU by including the RRCReconfigurationComplete message. 12. The gNB-CU sends an UE CONTEXT RELEASE COMMAND message to the source gNB-DU. 13. The source gNB-DU releases the UE context and responds the gNB-CU with an UE CONTEXT RELEASE COMPLETE message.

3GPP TS 38.401

NG-RAN; Architecture description

RAN3

3GPP Series : 38 , Radio technology beyond LTE

8.19.4.1

13.1.1.2 TLS protection based on 3gpp-Sbi-Target-apiRoot HTTP header

The NF uses the 3gpp-Sbi-Target-apiRoot HTTP header in the HTTP Request to convey the target FQDN to the SEPPs. If PRINS is used on the N32-f interface, the following applies: The sending SEPP shall use the 3gpp-Sbi-Target-apiRoot header to obtain the apiRoot to be used in the request URI of the protected HTTP Request. It removes the 3gpp-Sbi-Target-apiRoot header before forwarding the protected HTTP Request on the N32-f interface. If TLS is used on the N32 interface, the following applies: The sending SEPP shall replace the authority header in the HTTP Request with the FQDN of the receiving SEPP before forwarding the protected HTTP Request on the N32 interface. The sending SEPP shall not change the 3gpp-Sbi-Target-apiRoot header. NOTE: This solution does not require the SEPP to support TLS wildcard certificate for its domain name during TLS setup, nor the SEPP to generate a telescopic FQDN for the target FQDN.

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

13.1.1.2

6.6.3.5 Abnormal cases in the UE

The following abnormal cases can be identified: a) Expiry of timer T3493: On the first expiry of the timer T3493, the UE shall resend the REMOTE UE REPORT message and shall reset and restart timer T3493. This retransmission is repeated two times, i.e. on the third expiry of timer T3493, the UE shall abort the procedure and release any resources for this procedure. NOTE: After the abortion of the Remote UE Report procedure, the Remote UE Report procedure for the remote UE(s) can be restarted and how to restart the procedure is left to UE implementation.

3GPP TS 24.301

Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3

CT WG1

3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network

6.6.3.5

4.3.2.2 Authentication response by the mobile station

The mobile station shall be ready to respond upon an AUTHENTICATION REQUEST message at any time whilst a RR connection exists. With exception of the cases described in subclause 4.3.2.5.1, it shall process the challenge information and send back an AUTHENTICATION RESPONSE message to the network. If a SIM is inserted in the MS, the MS shall ignore the Authentication Parameter AUTN IE if included in the AUTHENTICATION REQUEST message and shall proceed as in case of a GSM authentication challenge. It shall not perform the authentication of the network described in subclause 4.3.2.5.1. In a GSM authentication challenge, the new GSM ciphering key calculated from the challenge information shall overwrite the previous GSM ciphering key and any previously stored UMTS ciphering key and UMTS integrity key shall be deleted. The new GSM ciphering key shall be stored on the SIM/USIM together with the ciphering key sequence number. In a UMTS authentication challenge, the new UMTS ciphering key, the new GSM ciphering key and the new UMTS integrity key calculated from the challenge information shall overwrite the previous UMTS ciphering key, GSM ciphering key and UMTS integrity key. The new UMTS ciphering key, GSM ciphering key and UMTS integrity key are stored on the USIM together with the ciphering key sequence number. Furthermore, in A/Gb mode when after the authentication procedure an A5 ciphering algorithm that requires a 128-bit ciphering key is taken into use, then a new GSM Kc128 shall also be calculated as described in the subclause 4.3.2.3a. The SIM/USIM will provide the mobile station with the authentication response, based upon the authentication challenge given from the ME. A UMTS authentication challenge will result in the USIM passing a RES to the ME. A GSM authentication challenge will result in the SIM/USIM passing a SRES to the ME. A ME supporting UMTS authentication challenge may support the following procedure: In order to avoid a synchronisation failure, when the mobile station receives an AUTHENTICATION REQUEST message, the mobile station shall store the received RAND together with the RES returned from the USIM in the volatile memory and associate it with CS domain. When the MS receives a subsequent AUTHENTICATION REQUEST message, if the stored RAND value for the CS domain is equal to the new received value in the AUTHENTICATION REQUEST message, then the mobile station shall not pass the RAND to the USIM, but shall immediately send the AUTHENTICATION RESPONSE message with the stored RES for the CS domain. If, for the CS domain, there is no valid stored RAND in the mobile station or the stored RAND is different from the new received value in the AUTHENTICATION REQUEST message, the mobile station shall pass the RAND to the USIM, shall override any previously stored RAND and RES with the new ones and start, or reset and restart timer T3218. The RAND and RES values stored in the mobile station shall be deleted and timer T3218, if running, shall be stopped: - upon receipt of a SECURITY MODE COMMAND (Iu mode only), CIPHERING MODE COMMAND (A/Gb mode only), CM_SERVICE_ACCEPT, CM_SERVICE_REJECT, LOCATION_UPDATING_ACCEPT or AUTHENTICATION REJECT message; - upon expiry of timer T3218; or - if the mobile station enters the MM state MM IDLE or NULL.

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.3.2.2

8.7.13 FDD DC (4 Rx)

The parameters specified in Table 8.7.13-1 are valid for all FDD tests for 4Rx capable UEs unless otherwise stated. Table 8.7.13-1: Common Test Parameters (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.13-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.13-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.13-2: Per-CC FRC for SDR test (FDD 64QAM) Table 8.7.13-3: Per-CC FRC for SDR test (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.13

5.33.2.3 Support for redundant transmission at transport layer

Redundant transmission can be supported within the 5G System without making any assumption on support for protocols such as IEEE FRER in the application layer (DN only) at the same time it can be supported without requiring redundant GTP-U tunnel over N3. The backhaul provides two disjoint transport paths between UPF and NG-RAN. The redundancy functionality within NG-RAN and UPF make use of the independent paths at transport layer. Support of redundant transmission at transport layer requires no 3GPP protocol impact. Following are the required steps: - UE establishes the PDU session for URLLC services. Based on DNN, S-NSSAI, knowledge of supporting redundant transmission at transport layer and other factors as described in clause 6.3.3, SMF selects a UPF that supports redundant transmission at transport layer for the PDU session. One N3 GTP-U tunnel is established between UPF and NG-RAN. The knowledge of supporting redundant transmission at transport layer can be configured in the SMF, or be configured in UPF and then obtained by the SMF via N4 capability negotiation during N4 Association setup procedure. - For DL data transmission, UPF sends the DL packets on N3 GTP-U tunnel. Redundant functionality in the UPF duplicates the DL data on the transport layer. Redundant functionality in the NG-RAN eliminates the received duplicated DL data and sends to NG-RAN. - For UL data transmission, NG-RAN sends the received UL packets on N3 GTP-U tunnel, the Redundant functionality in the NG-RAN performs the redundant handling on the backhaul transport layer. The Redundant functionality in the UPF eliminates the received duplicated UL data and sends to UPF.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

3GPP Series : 23 , Technical realization ("stage 2")

5.33.2.3

4.11.1.5.7 Establishment of S1-U bearer during Data Transport in Control Plane CIoT EPS Optimisation

The following changes are applied to clause 5.3.4B.4 (Establishment of S1-U bearer during Data Transport in Control Plane CIoT EPS Optimisation) in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13]: - Step 3: MME may steer the UE from EPC by rejecting the Control Plane Service Request with an appropriate cause value. The MME should take into account availability of 5GC to the UE and the Preferred and Supported Network Behaviour (see clause 5.31.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]) before steering the UE from EPC.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

3GPP Series : 23 , Technical realization ("stage 2")

4.11.1.5.7

5.3.8.3 Reception of the RRCRelease by the UE

The UE shall: 1> delay the following actions defined in this clause 60 ms from the moment the RRCRelease message was received or optionally when lower layers indicate that the receipt of the RRCRelease message has been successfully acknowledged, whichever is earlier; NOTE 0: When the RRCRelease message is received on a HARQ process with disabled HARQ feedback, and when STATUS reporting, as defined in TS 38.322[ NR; Radio Link Control (RLC) protocol specification ] [4], has not been triggered for a logical channel associated with the SRB1, the lower layers can be considered to have indicated that the receipt of the RRCRelease message has been successfully acknowledged. 1> stop timer T380, if running; 1> stop timer T320, if running; 1> if timer T316 is running; 2> stop timer T316; 2> if the UE supports RLF-Report for fast MCG recovery procedure: 3> set the elapsedTimeT316 in the VarRLF-Report to the value of the elapsed time of the timer T316; 3> set the pSCellId to the global cell identity of the PSCell, if available, otherwise to the physical cell identity and carrier frequency of the PSCell; 2> else: 3> clear the information included in VarRLF-Report, if any; 1> stop timer T350, if running; 1> stop timer T346g, if running; 1> if the AS security is not activated: 2> ignore any field included in RRCRelease message except waitTime; 2> perform the actions upon going to RRC_IDLE as specified in 5.3.11 with the release cause 'other' upon which the procedure ends; 1> if the RRCRelease message includes redirectedCarrierInfo indicating redirection to eutra: 2> if cnType is included: 3> after the cell selection, indicate the available CN Type(s) and the received cnType to upper layers; NOTE 1: Handling the case if the E-UTRA cell selected after the redirection does not support the core network type specified by the cnType, is up to UE implementation. 2> if voiceFallbackIndication is included: 3> consider the RRC connection release was for EPS fallback for IMS voice (see TS 23.502[ Procedures for the 5G System (5GS) ] [43]); 1> if the RRCRelease message includes the cellReselectionPriorities: 2> store the cell reselection priority information provided by the cellReselectionPriorities; 2> if the t320 is included: 3> start timer T320, with the timer value set according to the value of t320; 1> else: 2> apply the cell reselection priority information broadcast in the system information; 1> if deprioritisationReq is included and the UE supports RRC connection release with deprioritisation: 2> start or restart timer T325 with the timer value set to the deprioritisationTimer signalled; 2> store the deprioritisationReq until T325 expiry; NOTE 1a: The UE stores the deprioritisation request irrespective of any cell reselection absolute priority assignments (by dedicated or common signalling) and regardless of RRC connections in NR or other RATs unless specified otherwise. 1> if the RRCRelease includes the measIdleConfig: 2> if T331 is running: 3> stop timer T331; 3> perform the actions as specified in 5.7.8.3; 2> if the measIdleConfig is set to setup: 3> store the received measIdleDuration in VarMeasIdleConfig; 3> start timer T331 with the value set to measIdleDuration; 3> if the measIdleConfig contains measIdleCarrierListNR: 4> store the received measIdleCarrierListNR in VarMeasIdleConfig; 3> if the measIdleConfig contains measIdleCarrierListEUTRA: 4> store the received measIdleCarrierListEUTRA in VarMeasIdleConfig; 3> if the measIdleConfig contains validityAreaList: 4> store the received validityAreaList in VarMeasIdleConfig; 1> if the RRCRelease includes suspendConfig: 2> reset MAC and release the default MAC Cell Group configuration, if any; 2> apply the received suspendConfig except the received nextHopChainingCount; 2> if the sdt-Config is configured: 3> for each of the DRB in the sdt-DRB-List: 4> consider the DRB to be configured for SDT; 3> if sdt-SRB2-Indication is configured: 4> consider the SRB2 to be configured for SDT; 3> for each RLC bearer (except those associated with broadcast MRBs) that is not suspended: 4> re-establish the RLC entity as specified in TS 38.322[ NR; Radio Link Control (RLC) protocol specification ] [4]; 3> for SRB2 (if it is resumed) and for SRB1: 4> trigger the PDCP entity to perform SDU discard as specified in TS 38.323[ NR; Packet Data Convergence Protocol (PDCP) specification ] [5]; 3> if sdt-MAC-PHY-CG-Config is configured: 4> configure the PCell with the configured grant resources for SDT and instruct the MAC entity to start the cg-SDT-TimeAlignmentTimer; 2> if srs-PosRRC-Inactive is configured: 3> apply the configuration and instruct MAC to start the inactivePosSRS-TimeAlignmentTimer; 2> if srs-PosRRC-InactiveValidityAreaConfig is configured: 3> apply the configuration and instruct MAC to start the inactivePosSRS-ValidityAreaTAT; NOTE 1b: The Network should provide full configuration to UE for SRS for Positioning in RRC_INACTIVE. 2> perform the LTM configuration release procedure for the MCG and the SCG as specified in clause 5.3.5.18.7; 2> remove all the entries within the MCG and the SCG VarConditionalReconfig, if any; 2> remove the servingSecurityCellSetId within the VarServingSecurityCellSetID, if any; 2> for each measId of the MCG measConfig and for each measId of the SCG measConfig, if configured, if the associated reportConfig has a reportType set to condTriggerConfig: 3> for the associated reportConfigId: 4> remove the entry with the matching reportConfigId from the reportConfigList within the VarMeasConfig; 3> if the associated measObjectId is only associated to a reportConfig with reportType set to condTriggerConfig: 4> remove the entry with the matching measObjectId from the measObjectList within the VarMeasConfig; 3> remove the entry with the matching measId from the measIdList within the VarMeasConfig; 2> for NCR-MT, if NCR-FwdConfig is configured: 3> if the NCR-FwdConfig includes periodic forwarding resource configuration: 4> indicate to NCR-Fwd to continue forwarding only in accordance with the configured periodic forwarding resource set(s); 3> else: 4> indicate to NCR-Fwd to cease forwarding; 2> if the UE is acting as L2 U2N Remote UE and is not configured with MP: 3> if the PC5-RRC connection with the U2N Relay UE is determined to be released: 4> indicate upper layers to trigger PC5 unicast link release; 3> else (i.e., maintain the PC5 RRC connection): 4> establish or re-establish (e.g. via release and add) SL RLC entity for SRB1; 2> else: 3> re-establish RLC entities for SRB1; 2> if the RRCRelease message with suspendConfig was received in response to an RRCResumeRequest or an RRCResumeRequest1: 3> stop the timer T319 if running; 3> in the stored UE Inactive AS context: 4> replace the KgNB and KRRCint keys with the current KgNB and KRRCint keys; 4> replace the nextHopChainingCount with the value of nextHopChainingCount received in the RRCRelease message; 4> replace the cellIdentity with the cellIdentity of the cell the UE has received the RRCRelease message; 4> if the suspendConfig contains the sl-UEIdentityRemote (i.e. the UE is a L2 U2N Remote UE): 5> replace the C-RNTI with the value of the sl-UEIdentityRemote; 5> replace the physical cell identity with the value of the sl-PhysCellId in sl-ServingCellInfo contained in the discovery message received from the connected L2 U2N Relay UE; 4> else: 5> replace the C-RNTI with the C-RNTI used in the cell (see TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3]) the UE has received the RRCRelease message; 5> replace the physical cell identity with the physical cell identity of the cell the UE has received the RRCRelease message; 3> replace the nextHopChainingCount with the value associated with the current KgNB; 3> stop the timer T319a if running and consider SDT procedure is not ongoing; 2> else: 3> store in the UE Inactive AS Context the nextHopChainingCount received in the RRCRelease message, the current KgNB and KRRCint keys, the ROHC state, the EHC context(s), the UDC state, the stored QoS flow to DRB mapping rules, the application layer measurement configuration, the C-RNTI used in the source PCell, the cellIdentity and the physical cell identity of the source PCell, the NCR-FwdConfig (if configured), the spCellConfigCommon within ReconfigurationWithSync of the NR PSCell (if configured) and all other parameters configured except for: - parameters within ReconfigurationWithSync of the PCell; - parameters within ReconfigurationWithSync of the NR PSCell, if configured; - parameters within MobilityControlInfoSCG of the E-UTRA PSCell, if configured; - servingCellConfigCommonSIB; - sl-L2RelayUE-Config, if configured; - sl-L2RemoteUE-Config, if configured; - uav-Config, if configured; NOTE 1c: suspendConfig is not stored as part of UE Inactive AS Context, except for the fields explicitly specified. 3> store any previously or subsequently received application layer measurement report containers for which no segment, or full message, has been submitted to lower layers for transmission; 3> for each application layer measurement configuration for which configForRRC-IdleInactive is set to true: 4> initiate the procedure in 5.5b.1.2; NOTE 2: NR sidelink communication/discovery related configurations and logged measurement configuration are not stored as UE Inactive AS Context, when UE enters RRC_INACTIVE. 2> suspend all SRB(s) and DRB(s), except SRB0 and broadcast MRBs; 2> suspend all multicast MRB(s) associated with multicast session(s) not configured to receive in RRC_INACTIVE; 2> indicate PDCP suspend to lower layers of all DRBs and multicast MRBs associated with multicast session(s) not configured to receive in RRC_INACTIVE; 2> release Uu Relay RLC channel(s), if configured; 2> release PC5 Relay RLC channel(s), if configured; 2> release the SRAP entity, if configured; NOTE 2a: A L2 U2N Relay UE may re-establish the SL-RLC0, SL-RLC1 and SRAP entity after release. 2> if SL indirect path is configured: 3> release cell identity and relay UE ID configured in sl-IndirectPathAddChange; 3> indicate upper layers to trigger PC5 unicast link release of the SL indirect path; 2> if N3C indirect path is configured: 3> release n3c-IndirectPathAddChange; 3> consider the non-3GPP connection is not used; 2> if the UE is acting as a N3C relay UE: 3> release n3c-IndirectPathConfigRelay; 3> consider the non-3GPP connection is not used; 2> if the t380 is included: 3> start timer T380, with the timer value set to t380; 2> if the RRCRelease message is including the waitTime: 3> start timer T302 with the value set to the waitTime; 3> inform upper layers that access barring is applicable for all access categories except categories '0' and '2'; 2> if T390 is running: 3> stop timer T390 for all access categories; 3> perform the actions as specified in 5.3.14.4; 2> indicate the suspension of the RRC connection to upper layers; 2> if the UE is capable of L2 U2N Remote UE: 3> enter RRC_INACTIVE, and perform either cell selection as specified in TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [20], or relay selection as specified in clause 5.8.15.3, or both; 2> else: 3> enter RRC_INACTIVE and perform cell selection as specified in TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [20]; 2> if the suspendConfig includes resumeIndication: 3> perform the actions as if the UE received Paging message with the ue-Identity included in the PagingRecord matching the UE's stored fullI-RNTI, as specified in clause 5.3.2.3; 2> if the multicastConfigInactive is configured: 3> if the multicast PTM configuration is provided for a multicast session for which the UE is not indicated to stop monitoring the G-RNTI and the UE selects the same cell as the one on which it received RRCRelease: 4> apply the multicast PTM configuration as specified in 5.10.3; 4> monitor the Multicast MCCH-RNTI as specified in 5.10.2; 1> else: 2> perform the actions upon going to RRC_IDLE as specified in 5.3.11, with the release cause 'other'. NOTE 3: Whether to release the PC5 unicast link is left to L2 U2N Remote UE's implementation. NOTE 4: It is left to UE implementation whether to stop T430, if running, when going to RRC_INACTIVE.

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

5.3.8.3

10.4 Measurements to Support Scheduler Operation

Measurement reports are required to enable the scheduler to operate in both uplink and downlink. These include transport volume and measurements of a UEs radio environment. Uplink buffer status reports (BSR) are needed to provide support for QoS-aware packet scheduling. In NR, uplink buffer status reports refer to the data that is buffered in for a group of logical channels (LCG) in the UE. Four formats are used for reporting in uplink: - A short format to report only one BSR (of one LCG); - A flexible long format to report several BSRs (up to all eight LCGs); - An extended short format to report one BSR (of one LCG); - An extended long format to report several BSRs (up to all 256 LCGs). NOTE: The Extended versions of the BSR formats can only be used by IAB nodes. Uplink buffer status reports are transmitted using MAC signalling. When a BSR is triggered (e.g. when new data arrives in the transmission buffers of the UE), a Scheduling Request (SR) can be transmitted by the UE (e.g. when no resources are available to transmit the BSR). For IAB, the Pre-emptive BSR can be configured on the backhaul links. The Pre-emptive BSR is sent based on expected data rather than buffered data, as described in clause 4.7.3.3. Power headroom reports (PHR) are needed to provide support for power-aware packet scheduling. In NR, three types of reporting are supported: a first one for PUSCH transmission, a second one for PUSCH and PUCCH transmission in an LTE Cell Group in EN-DC (see TS 37.340[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 ] [21]) and a third one for SRS transmission on SCells configured with SRS only. In case of CA, when no transmission takes place on an activated SCell, a reference power is used to provide a virtual report. To allow network to detect UL power reduction, the PHR reports may also contain Power Management Maximum Power Reduction (P-MPR, see TS 38.101[ None ] -2 [35]) information that UE uses to ensure UE compliance with the Maximum Permissible Exposure (MPE) exposure regulation for FR2, which is set for limiting RF exposure on human body. Power headroom reports are transmitted using MAC signalling.

3GPP TS 38.300

NR; NR and NG-RAN Overall description; Stage-2

RAN2

3GPP Series : 38 , Radio technology beyond LTE

10.4

Annex C (Normative): MME/S4-SGSN mapping table between S11/S4 and NAS Cause values

The MME/S4-SGSN initiates session management requests towards the SGW and PGW or mobility management requests towards the source/target MME/S4-SGSN. If this operation is not successful, there are several possible cause codes, which need to be mapped to the appropriate cause codes over NAS to the UE. Additionally, the MME/S4-SGSN initiates session management requests towards the UE. If this operation is not successful, there are several possible NAS cause codes which need to be mapped to the appropriate GTP cause codes over S11/S4 interface towards the SGW. The MME/S4-SGSN should map these cause codes as defined in tables C.1 to C.5 unless specified otherwise in the tables. Table C.1: Mapping from S11/S4 to NAS Cause values – Rejection indication from SGW Table C.2: Mapping from S11/S4 to NAS Cause values – Acceptance indication from SGW Table C.3: Mapping from S11/S4 to NAS Cause values – Indication in request from SGW Table C.4: Mapping from NAS to S11/S4 Cause values – Rejection indication from MME/S4-SGSN Table C.5: Mapping from S3/S16 to NAS Cause values – Rejection indication from MME/S4-SGSN

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

Annex

– CondReconfigToAddModList

The IE CondReconfigToAddModList concerns a list of conditional reconfigurations to add or modify, with for each entry the condReconfigId and the associated fields. CondReconfigToAddModList information element -- ASN1START -- TAG-CONDRECONFIGTOADDMODLIST-START CondReconfigToAddModList-r16 ::= SEQUENCE (SIZE (1.. maxNrofCondCells-r16)) OF CondReconfigToAddMod-r16 CondReconfigToAddMod-r16 ::= SEQUENCE { condReconfigId-r16 CondReconfigId-r16, condExecutionCond-r16 SEQUENCE (SIZE (1..2)) OF MeasId OPTIONAL, -- Need M condRRCReconfig-r16 OCTET STRING (CONTAINING RRCReconfiguration) OPTIONAL, -- Cond condReconfigAdd ..., [[ condExecutionCondSCG-r17 OCTET STRING (CONTAINING CondReconfigExecCondSCG-r17) OPTIONAL -- Need M ]], [[ condExecutionCondPSCell-r18 SEQUENCE (SIZE (1..2)) OF MeasId OPTIONAL, -- Cond condReconfigCHO-WithSCG subsequentCondReconfig-r18 SubsequentCondReconfig-r18 OPTIONAL, -- Need M securityCellSetId-r18 SecurityCellSetId-r18 OPTIONAL, -- Need M scpac-ConfigComplete-r18 ENUMERATED {true} OPTIONAL -- Cond CPAC ]] } CondReconfigExecCondSCG-r17 ::= SEQUENCE (SIZE (1..2)) OF MeasId SubsequentCondReconfig-r18 ::= SEQUENCE { condExecutionCondToReleaseList-r18 CondExecutionCondToReleaseList-r18 OPTIONAL, -- Need N condExecutionCondToAddModList-r18 CondExecutionCondToAddModList-r18 OPTIONAL, -- Need N ... } CondExecutionCondToAddModList-r18 ::= SEQUENCE (SIZE (1.. maxNrofCondCells-r16)) OF CondExecutionCondToAddMod-r18 CondExecutionCondToAddMod-r18 ::= SEQUENCE { condReconfigId-r18 CondReconfigId-r16, condExecutionCond-r18 SEQUENCE (SIZE (1..2)) OF MeasId OPTIONAL, -- Need M condExecutionCondSCG-r18 OCTET STRING (CONTAINING CondReconfigExecCondSCG-r17) OPTIONAL, -- Need M ... } CondExecutionCondToReleaseList-r18 ::= SEQUENCE (SIZE (1.. maxNrofCondCells-r16)) OF CondReconfigId-r16 -- TAG-CONDRECONFIGTOADDMODLIST-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

4.7.7b Authentication and ciphering procedure used for GSM authentication challenge

The purpose of the authentication and ciphering procedure is threefold (see 3GPP TS 43.020[ Security related network functions ] [13]): - to permit the network to check whether the identity provided by the MS is acceptable or not; - to provide parameters enabling the MS to calculate a new GPRS GSM ciphering key; and - to let the network set the GSM ciphering mode (ciphering/no ciphering) and GSM ciphering algorithm. The authentication and ciphering procedure can be used for either: - authentication only; - setting of the GSM ciphering mode and the GSM ciphering algorithm only; or - authentication and the setting of the GSM ciphering mode and the GSM ciphering algorithm. The cases in which the authentication and ciphering procedure shall be used are defined in 3GPP TS 42.009[ Security aspects ] [5]. In A/Gb mode, the authentication and ciphering procedure is always initiated and controlled by the network. It shall be performed in a non ciphered mode because of the following reasons: - the network cannot decipher a ciphered AUTHENTICATION_AND_CIPHERING RESPONSE from an unauthorised MS and put it on the prohibited list; and - to be able to define a specific point in time from which on a new GPRS GSM ciphering key should be used instead of the old one. GSM authentication challenge shall be supported by a ME supporting GERAN or UTRAN. In A/Gb mode, the network should not send any user data during the authentication and ciphering procedure. A GSM security context is established in the MS and the network when a GSM authentication challenge is performed in A/Gb mode or in Iu mode. However, in Iu mode the MS shall not accept a GSM authentication challenge, if a USIM is inserted. After a successful GSM authentication challenge, the GPRS GSM ciphering key and the GPRS ciphering key sequence number, are stored both in the network and the MS.

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.7b

19.2.2.3 BM-SC in the home PLMN initiated multicast service deactivation

This section defines the BM-SC in the home PLMN initiated multicast service deactivation procedure. Figure 32b: BM-SC in the home PLMN initiated MBMS multicast service deactivation procedure 1. The BM-SC in home PLMN sends an ASR to the BM-SC in visited PLMN, indicating that the UE shall be removed from a specific multicast service. The session to be terminated is uniquely identified by the Diameter session-id. 2. The BM-SC in the visited PLMN sends an ASR to the GGSN indicating that the UE shall be removed from the multicast service. The session to be terminated is uniquely identified by the Diameter session-id. 3. Upon reception of the ASR, the GGSN sends an ASA to the BM-SC in visited PLMN. 4. Upon reception of the ASA, the BM-SC in visited PLMN sends an ASA to the BM-SC in home PLMN. 5. Upon reception of the ASR in step 3, the GGSN sends an MBMS UE Context Deactivation Request to the SGSN. The IP multicast address, APN and IMSI together identify the MBMS UE Context to be deleted by the SGSN. Steps 5 and 6 of Figure 30a in section 19.2.2.1 follows in roaming scenarios where service was provided in the home PLMN. Steps 5 and 6 of Figure 31a in section 19.2.2.2 follows in roaming scenarios where service was provided in the visited PLMN.

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

19.2.2.3

8.13.1.1.4 Minimum Requirement Four-Layer Spatial Multiplexing 4 Tx Antenna Port

The purpose of these tests is to verify the closed loop rank-four performance with wideband precoding with 4Tx and 4Rx under CA. For CA with 2 DL CCs, the requirements are specified in Table 8.13.1.1.4-3, based on single carrier requirement specified in Table 8.13.1.1.4-2, with the addition of the parameters in Table 8.13.1.1.4-1 and the downlink physical channel setup according to Annex C.3.2. The test coverage for different number of component carriers is defined in 8.1.2.4. Table 8.13.1.1.4-1: Test Parameters for Four-Layer Spatial Multiplexing (FRC) for CA Table 8.13.1.1.4-2: Single carrier performance for multiple CA configurations Table 8.13.1.1.4-3: Minimum performance (FRC) based on single carrier performance for CA with 2 DL 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.13.1.1.4

– MeasResultIdleNR

The IE MeasResultIdleNR covers the NR measurement results performed in RRC_IDLE and RRC_INACTIVE. MeasResultIdleNR information element -- ASN1START -- TAG-MEASRESULTIDLENR-START MeasResultIdleNR-r16 ::= SEQUENCE { measResultServingCell-r16 SEQUENCE { rsrp-Result-r16 RSRP-Range OPTIONAL, rsrq-Result-r16 RSRQ-Range OPTIONAL, resultsSSB-Indexes-r16 ResultsPerSSB-IndexList-r16 OPTIONAL }, measResultsPerCarrierListIdleNR-r16 SEQUENCE (SIZE (1.. maxFreqIdle-r16)) OF MeasResultsPerCarrierIdleNR-r16 OPTIONAL, ... } MeasResultsPerCarrierIdleNR-r16 ::= SEQUENCE { carrierFreq-r16 ARFCN-ValueNR, measResultsPerCellListIdleNR-r16 SEQUENCE (SIZE (1..maxCellMeasIdle-r16)) OF MeasResultsPerCellIdleNR-r16, ... } MeasResultsPerCellIdleNR-r16 ::= SEQUENCE { physCellId-r16 PhysCellId, measIdleResultNR-r16 SEQUENCE { rsrp-Result-r16 RSRP-Range OPTIONAL, rsrq-Result-r16 RSRQ-Range OPTIONAL, resultsSSB-Indexes-r16 ResultsPerSSB-IndexList-r16 OPTIONAL }, ... } ResultsPerSSB-IndexList-r16 ::= SEQUENCE (SIZE (1.. maxNrofIndexesToReport)) OF ResultsPerSSB-IndexIdle-r16 ResultsPerSSB-IndexIdle-r16 ::= SEQUENCE { ssb-Index-r16 SSB-Index, ssb-Results-r16 SEQUENCE { ssb-RSRP-Result-r16 RSRP-Range OPTIONAL, ssb-RSRQ-Result-r16 RSRQ-Range OPTIONAL } OPTIONAL } -- TAG-MEASRESULTIDLENR-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

8.13.2.5 User consent propagation in EN-DC

In the EN-DC case, the EM provides the MDT configuration to both MeNB and en-gNB independently. As specified in TS 32.422[ Telecommunication management; Subscriber and equipment trace; Trace control and configuration management ] [20] in Management based MDT getting user consent is required before activating the MDT functionality because of privacy and legal obligations. In the case of EN-DC user consent gets communicated to the MeNB at the UE context setup procedure using the INITIAL CONTEXT SETUP REQUEST message. In particular when the Management Based MDT Allowed IE is contained in the INITIAL CONTEXT SETUP REQUEST message, the MeNB stores it in the UE context and uses it, together with information in the Management Based MDT PLMN List IE, if available, to allow subsequent selection of the UE for management based MDT as specified in TS 32.422[ Telecommunication management; Subscriber and equipment trace; Trace control and configuration management ] [20]. The MeNB may also receive user consent information in the HANDOVER REQUEST message. The MeNB will forward the MDT user consent to the SgNB at EN-DC setup. In particular, if available in the UE context, the MeNB will include the Management Based MDT Allowed IE and the Management Based MDT PLMN List IE in the SGNB ADDITION REQUEST message to the SgNB. Furthermore, the user consent will be forwarded to the relevant gNB-CU-UP at the bearer context setup or to the gNB-DU by including the Management Based MDT PLMN List IE in the BEARER CONTEXT SETUP REQUEST or UE CONTEXT SETUP REQUEST. The signalling flow for User consent proposation in EN-DC is shown in Figure 8.13.2.5-1. Figure 8.13.2.5-1 User consent propagation in EN-DC 0. User Context information are made available at the MME. 1. The MME sends INITIAL CONTEXT SETUP REQUEST message to the MeNB, including Management Based MDT Allowed IE and the Management based MDT PLMN List IE to communicate user consent to the eNB. 2. The MeNB sends SGNB ADDITION REQUEST to the gNB-CU-CP at EN-DC setup. This request includes Management Based MDT Allowed IE and, optionally, the Management based MDT PLMN List IE, if available. 3a. The user consent is communicated to the gNB-DU at the UE context setup by including the Management based MDT PLMN List IE in the UE CONTEXT SETUP REQUEST. 3b. The user consent is communicated to the gNB-CU-UP at the bearer context setup by including the Management based MDT PLMN List IE in the BEARER CONTEXT SETUP REQUEST.

3GPP TS 38.401

NG-RAN; Architecture description

RAN3

3GPP Series : 38 , Radio technology beyond LTE

8.13.2.5

A.5 Release of QoS Flow with Explicit Signalling

The following figure shows an example message flow when the gNB receives a request to release a QoS flow from CN that involves explicit NAS signalling. NAS procedures details between gNB and 5GC can be found in TS 23.501[ System architecture for the 5G System (5GS) ] [3], TS 23.502[ Procedures for the 5G System (5GS) ] [22] and TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [26]. Figure A.5-1: Release of QoS Flow with Explicit Signalling 0. PDU session and DRB(s) have been already established. 1. gNB receives a PDU SESSION RESOURCE MODIFY REQUEST message from AMF to release a QoS flow. 2. The gNB decides to release corresponding the QFI to DRB mapping rule. Since the DRB also carries other QoS flows, the DRB is not released. 3. gNB sends an RRCReconfiguration message to UE to release the QFI to DRB mapping rule. 4. UE updates the AS QFI to DRB mapping rules to release this QFI to DRB mapping rule. 5. UE sends an RRCReconfigurationComplete message to gNB. 6. gNB sends a PDU SESSION RESOURCE MODIFY RESPONSE message to AMF.

3GPP TS 38.300

NR; NR and NG-RAN Overall description; Stage-2

RAN2

3GPP Series : 38 , Radio technology beyond LTE

A.5

8.59 Source Identification

The Source Identification information element is coded as depicted in Figure 8.59-1. Figure 8.59-1: Source Identification The Target Cell ID shall be same as the Octets 3 to 10 of the Cell Identifier IEI in 3GPP TS 48.018[ None ] [34]. Source Type values are specified in Table 8.59-1. If the Source Type is Cell ID, this indicates PS handover from GERAN A/Gb mode. In this case the coding of the Source ID field shall be same as the Octets 3 to 10 of the Cell Identifier IEI in 3GPP TS 48.018[ None ] [34]. If the Source Type is RNC ID, this indicates PS handover from GERAN Iu mode or for inter-RAT handover from UTRAN. In this case the Source ID field shall include a transparent copy of the corresponding parameter (see clause 8.2.2), the Source RNC-ID as specified within the "Source ID" parameter in 3GPP TS 25.413[ UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling ] [33]. NOTE: In fact, the ASN.1/PER encoded binary value of the "Source RNC ID" shall be copied into octets 14 to (n+4). Table 8.59-1: Source Type values and their meanings

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.59

5.5.2 Configurability

Configurability is the property that that the user can configure whether the use or the provision of a service should depend on whether a security feature is in operation. A service can only be used if all security features, which are relevant to that service and which are required by the configurations of the user, are in operation. The following configurability features are suggested: - Enabling/disabling user-USIM authentication: the user should be able to control the operation of user-USIM authentication, e.g., for some events, services or use. - Accepting/rejecting incoming non-ciphered calls: the user should be able to control whether the user accepts or rejects incoming non-ciphered calls; - Setting up or not setting-up non-ciphered calls: the user should be able to control whether the user sets up connections when ciphering is not enabled by the network; - Accepting/rejecting the use of certain ciphering algorithms: the user should be able to control which ciphering algorithms are acceptable for use.

3GPP TS 33.102

3G security; Security architecture

SA WG3

3GPP Series : 33 , Security aspects

5.5.2

4.2.9.4 AAA Server triggered Slice-Specific Authorization Revocation

Figure 4.2.9.4-1: AAA Server-initiated Network Slice-Specific Authorization Revocation procedure 1. The AAA-S requests the revocation of authorization for the Network Slice specified by the S-NSSAI in the AAA protocol Revoke Auth Request message, for the UE identified by the GPSI in this message. This message is sent to AAA-P if it is used. 2. The AAA-P, if present, relays the request to the NSSAAF. 3a-3b. The NSSAAF gets AMF ID from UDM using Nudm_UECM_Get with the GPSI in the received AAA message. If two different AMF addresses are received, the NSSAAF initiates the step 4 towards both AMFs. 3c. The NSSAAF provides an acknowledgement to the AAA protocol Re-Auth Request message. If the AMF is not registered in UDM the procedure is stopped here. 4. If the AMF is registered in UDM, the NSSAAF notifies the AMF to revoke the S-NSSAI authorization for the UE using Nnssaaf_NSSAA_RevocationNotification with the GPSI and S-NSSAI in the received AAA message. The callback URI of the notification for the AMF is derived via NRF as specified in TS 29.501[ 5G System; Principles and Guidelines for Services Definition; Stage 3 ] [62]. 5. If the UE is registered with the S-NSSAI in the Mapping Of Allowed NSSAI, the AMF updates the UE configuration to revoke the S-NSSAI from the current Allowed NSSAI, for any Access Type for which Network Slice Specific Authentication and Authorization had been successfully run on this S-NSSAI. The UE Configuration Update may include a request to Register if the AMF needs to be re-allocated. The AMF provides a new Allowed NSSAI to the UE by removing the S-NSSAI for which authorization has been revoked. The AMF provides new rejected NSSAIs to the UE including the S-NSSAI for which authorization has been revoked. If no S-NSSAI is left in Allowed NSSAI for an access after the revocation and a Default NSSAI exists that requires no Network Slice Specific Authentication or for which a Network Slice Specific Authentication did not previously fail over this access, then the AMF may provide a new Allowed NSSAI to the UE containing the Default NSSAI. If no S-NSSAI is left in Allowed NSSAI for an access after the revocation and no Default NSSAI can be provided to the UE in the Allowed NSSAI or a previous Network Slice Specific Authentication failed for the Default NSSAI over this access, then the AMF shall execute the Network-initiated Deregistration procedure for the access as described in clause 4.2.2.3.3 and it shall include in the explicit De-Registration Request message the list of Rejected S-NSSAIs, each of them with the appropriate rejection cause value. If there are PDU session(s) established that are associated with the revoked S-NSSAI, the AMF shall initiate the PDU Session Release procedure as specified in clause 4.3.4 to release the PDU sessions with the appropriate cause value. If the UE is registered but the S-NSSAI is not in the Mapping Of Allowed NSSAI, the AMF removes any status it may have kept of the corresponding S-NSSAI subject to Network Slice-Specific Authentication and Authorization in the UE context.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

3GPP Series : 23 , Technical realization ("stage 2")

4.2.9.4

10.5.6.15 MBMS protocol configuration options

The purpose of the MBMS protocol configuration options information element is to: - transfer protocol options associated with the bearer level of an MBMS context activation, and - transfer additional MBMS bearer related (protocol) data (e.g. configuration parameters, error codes or messages/events). The MBMS protocol configuration options is a type 4 information element with a minimum length of 3 octets and a maximum length of 253 octets. The MBMS protocol configuration options information element is coded as shown in figure 10.5.156/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.170/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.156/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : MBMS protocol configuration options information element Table 10.5.170/3GPP TR 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : MBMS protocol configuration options 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.6.15

15.3.3.2 Intra-system Automatic Neighbour Cell Relation Function

ANR relies on NCGI (see clause 8.2) and ANR reporting of E-UTRA cells as specified in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [2]. Figure 15.3.3.2-1: Automatic Neighbour Relation Function Figure 15.3.3.2-1 depicts an example where the NG-RAN node serving cell A has an ANR function. In RRC_CONNECTED, the NG-RAN node instructs each UE to perform measurements on neighbour cells. The NG-RAN node may use different policies for instructing the UE to do measurements, and when to report them to the NG-RAN node. This measurement procedure is as specified in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12] and TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [29]. 1. The UE sends a measurement report regarding cell B. This report contains Cell B's PCI, but not its NCGI/ECGI. When the NG-RAN node receives a UE measurement report containing the PCI, the following sequence may be used. 2. The NG-RAN node instructs the UE, using the newly discovered PCI as parameter, to read all the broadcast NCGI(s) /ECGI(s), TAC(s), RANAC(s), PLMN ID(s) and, for neighbour NR cells, NR frequency band(s) and the gNB ID length(s). To do so, the NG-RAN node may need to schedule appropriate idle periods to allow the UE to read the NCGI/ECGI from the broadcast channel of the detected neighbour cell. How the UE reads the NCGI/ECGI is specified in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12] and TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [29]. 3. When the UE has found out the new cell's NCGI(s) /ECGI(s), the UE reports all the broadcast NCGI(s)/ECGI(s) to the serving cell NG-RAN node. In addition, the UE reports all the tracking area code(s), RANAC(s), PLMN IDs and, for neighbour NR cells, NR frequency band(s), and the gNB ID length(s) that have been read by the UE. In case the detected NR cell does not broadcast SIB1, the UE may report noSIB1 indication as specified in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12]. 4. The NG-RAN node decides to add this neighbour relation, and can use PCI and NCGI(s)/ECGI(s) to: a. Lookup a transport layer address to the new NG-RAN node; b. Update the Neighbour Cell Relation List; c. If needed, setup a new Xn interface towards this NG-RAN node.

3GPP TS 38.300

NR; NR and NG-RAN Overall description; Stage-2

RAN2

3GPP Series : 38 , Radio technology beyond LTE

15.3.3.2

9.10 Reporting of CSI-RS Resource Indicator (CRI)

The purpose of this test is to verify that the reported CSI-RS Resource Indicator is accurate. The accuracy of CRI reporting for Tests in Section 9.10.1 is determined by: a) The ratio of the throughput obtained when transmitting based on the reported CRI and fixed precoder with multiple CSI-RS resources configured compared to that obtained when transmitting based on the fixed precoder with one CSI-RS resource configured: - is [70%] of the maximum throughput obtained at using fixed precoder and power scaling factor according to UE reported CRI value with multiple CSI-RS resources configured - is throughput obtained at using fixed precoder and power scaling factor according to the one configured CSI-RS resource - is specified based on CRS RE power b) Each candidate CRI value among 0, 1,…, K-1 shall be reported at least  % of the time at with multiple CSI-RS resources configured - The number of configured CSI-RS resources K is specific to a test. The accuracy of CRI reporting for Tests in Section 9.10.2 is determined by: a) The ratio of the throughput obtained when transmitting based on the reported CRI and fixed precoder with multiple CSI-RS resources configured compared to that obtained when transmitting based on the fixed precoder with one CSI-RS resource configured: - is [70%] of the maximum throughput obtained at using the CRI configured according to the CSI UE report - is throughput obtained at under assumption of single TP1 transmission b) CRI 2 value among 0, 1 and 2 shall be reported at least  % of the time at with 2 CSI-RS resources configured c) CRI 0 value among 0, 1 and 2 shall be reported at least β % of the time at with 2 CSI-RS resources configured - corresponds to [70%] of the maximum throughput under assumption of single TP1 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

9.10

5.27.1.5 Detection of (g)PTP Sync and Announce timeouts

The procedure described in this clause is applicable when the PTP instance in 5GS is configured to operate as a time-aware system or as a Boundary Clock, and the PTP grandmaster is external to the 5GS, and the BMCA procedure (Method a) is used as described in clause 5.27.1.6. The NW-TT processes Announce messages according to IEEE Std 1588 [126]. In particular, the NW-TT shall compute and maintain the time when the Announce and Sync timeout events occur for the PTP port in a Follower state. When the 5GS is configured to operate as a time-aware system, the NW-TT shall determine the Sync and Announce message interval for the PTP Port at the other end of the link to which the Follower PTP Port in 5GS is attached, as described in IEEE Std 802.1AS [104]. When the 5GS is configured to operate as a Boundary Clock, the NW-TT shall determine Announce interval based on the configuration of the Follower port in 5GS, as described in IEEE Std 1588 [126]. The configuration of PTP instances in DS-TT and NW-TT for Sync and Announce timeouts is described in clause K.2. Upon detection of the Sync or Announce timeout event, the NW-TT shall re-evaluate the DS-TT and NW-TT port states as described in clause 5.27.1.6.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

3GPP Series : 23 , Technical realization ("stage 2")

5.27.1.5

6.3.5.1.1 Minimum requirements

The minimum requirement for absolute power tolerance is given in Table 6.3.5.1.1-1 over the power range bounded by the Maximum output power as defined in subclause 6.2.2 and the Minimum output power as defined in subclause 6.3.2. For operating bands under NOTE 2 in Table 6.2.2-1, the absolute power tolerance as specified in Table 6.3.5.1.1-1 is relaxed by reducing the lower limit by 1.5 dB when the transmission bandwidth is confined within FUL_low and FUL_low + 4 MHz or FUL_high – 4 MHz and FUL_high. Table 6.3.5.1.1-1: Absolute power tolerance

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.1.1

5.3.1 IP address allocation 5.3.1.1 General

The procedures of clause 5.3.1 apply to UEs activating a PDN connection of PDN Type IPv4, IPv6 or IPv4v6. Part of it also applies for PDN Type Non-IP when SGi PtP Tunnelling based on UDP/IP, see clause 4.3.17.8, is used. The procedures of clause 5.3.1 do not apply to UEs activating a PDN connection of PDN Type Ethernet. A UE shall perform the address allocation procedures for at least one IP address (either IPv4 address or IPv6 prefix) after the default bearer activation if no IPv4 address is allocated during the default bearer activation. One of the following ways shall be used to allocate IP addresses for the UE: a) The HPLMN allocates the IP address to the UE when the default bearer is activated (dynamic or static HPLMN address); b) The VPLMN allocates the IP address to the UE when the default bearer is activated (dynamic VPLMN address); or c) The PDN operator or administrator allocates an (dynamic or static) IP address to the UE when the default bearer is activated (External PDN Address Allocation). The IP address allocated for the default bearer shall also be used for the dedicated bearers within the same PDN connection. IP address allocation for PDN connections, which are activated by the UE requested PDN connectivity procedure, is handled with the same set of mechanisms as those used within the Attach procedure. PDN types IPv4, IPv6 and IPv4v6 are supported. An EPS Bearer of PDN type IPv4v6 may be associated with one IPv6 prefix only or with both one IPv4 address and one IPv6 prefix. PDN type IPv4 is associated with an IPv4 address. PDN type IPv6 is associated with an IPv6 prefix. PDN types IPv4 and IPv6 are utilised for the UE and/or the PDN GW support IPv4 addressing only or IPv6 prefix only; or operator preferences dictate the use of a single IP version only, or the subscription is limited to IPv4 only or IPv6 only for this APN. In addition, PDN type IPv4 and IPv6 are utilised for interworking with nodes of earlier releases. The way that the UE sets the requested PDN type may be pre-configured in the device per APN. Unless otherwise configured (including when the UE does not send any APN), the UE sets the PDN type during the Attach or PDN Connectivity procedures based on its IP stack configuration as follows: - A UE which is IPv6 and IPv4 capable shall request for PDN type IPv4v6. - A UE which is only IPv4 capable shall request for PDN type IPv4. - A UE which is only IPv6 capable shall request for PDN type IPv6. - When the IP version capability of the UE is unknown in the UE (as in the case when the MT and TE are separated and the capability of the TE is not known in the MT), the UE shall request for PDN type IPv4v6. NOTE 1: At intersystem changes between GERAN/UTRAN and E-UTRAN there is a 1-to-1 mapping between PDP type IPv4v6 and PDN type IPv4v6 without re-negotiation of the PDP/PDN type used for a PDN connection. The HSS stores one PDN type per APN in the subscription data. During the Attach or UE requested PDN connectivity procedure the MME compares the requested PDN type to the PDN type in the subscription records for the given APN and sets the PDN type as follows: - If the requested PDN type is allowed by subscription, the MME sets the PDN type as requested. - If the requested PDN type is IPv4v6 and subscription data only allows PDN type IPv4 or only allows PDN type IPv6, the MME sets the PDN type according to the subscribed value. A reason cause shall be returned to the UE indicating that only the assigned PDN type is allowed. In this case the UE shall not request another PDN connection to the same APN for the other IP version during the existence of the PDN connection. - If the requested PDN type is IPv4 or IPv6, and either the requested PDN type or PDN type IPv4v6 are subscribed, the MME sets the PDN type as requested. Otherwise the PDN connection request is rejected. - If the requested PDN type is IPv4v6, and both IPv4 and IPv6 PDN types are allowed by subscription but not IPv4v6, the MME shall set the PDN type to IPv4 or IPv6 where the selection between IPv4 and IPv6 is implementation specific. The UE should then initiate the UE requested PDN connectivity procedure to this APN in order to activate a second PDN connection with the other single address PDN type which was not allocated by the network. NOTE 2: If the MT and TE are separated, the UE might not be able to use reason cause "single address bearers only" as a trigger for activating a second single-stack EPS bearer. The PDN GW may restrict the usage of a PDN type IPv4v6 as follows. - If the PDN GW receives a request for PDN type IPv4v6, but the PDN GW operator preferences dictate the use of IPv4 addressing only or IPv6 prefix only for this APN, the PDN type shall be changed to a single address PDN type (IPv4 or IPv6) and a reason cause shall be returned to the UE indicating that only the assigned PDN type is allowed. In this case the UE shall not request another PDN connection to the same APN for the other IP version during the existence of the PDN connection. - If the PDN GW receives a request for PDN type IPv4v6, but the MME does not set the Dual Address Bearer Flag due to the MME operator using single addressing per bearer to support interworking with nodes of earlier releases the PDN type shall be changed to a single IP version only and a reason cause shall be returned to the UE indicating that only single IP version per PDN connection is allowed. In this case the UE should request another PDN connection for the other IP version using the UE requested PDN connectivity procedure to the same APN with a single address PDN type (IPv4 or IPv6) other than the one already activated. During inter-RAT mobility between E-UTRAN and UTRAN/GERAN, an EPS bearer with PDN type IPv4v6 shall be mapped one-to-one to PDP type IPv4v6. During inter-RAT mobility between E-UTRAN and UTRAN/GERAN, an EPS bearer with PDN type IPv4 shall be mapped one-to-one to a PDP context of PDP type IPv4. An EPS bearer with PDN type IPv6 shall be mapped one-to-one to a PDP context of PDP type IPv6. It is the HPLMN operator that shall define in the subscription whether a dynamic HPLMN or VPLMN address may be used. The EPS UE may indicate to the network within the Protocol Configuration Options element that the UE wants to obtain the IPv4 address with DHCPv4, which is a deferred IPv4 address allocation option, or during the default bearer activation procedure. This implies the following behaviour both for static and dynamic address allocation: - the UE may indicate that it prefers to obtain an IPv4 address as part of the default bearer activation procedure. In such a case, the UE relies on the EPS network to provide IPv4 address to the UE as part of the default bearer activation procedure. - the UE may indicate that it prefers to obtain the IPv4 address after the default bearer setup by DHCPv4. That is, when the EPS network supports DHCPv4 and allows that, it does not provide the IPv4 address for the UE as part of the default bearer activation procedures. The network may respond to the UE by setting the PDN Address to 0.0.0.0. After the default bearer establishment procedure is completed, the UE uses the connectivity with the EPS and initiates the IPv4 address allocation on its own using DHCPv4. However, if the EPS network provides IPv4 address to the UE as part of the default bearer activation procedure, the UE should accept the IPv4 address indicated in the default bearer activation procedure. - if the UE sends no Address Allocation Preference, the PDN GW determines whether DHCPv4 is used between the UE and the PDN GW (for the deferred IPv4 address allocation) or not, based on per APN configuration Both EPS network elements and UE shall support the following mechanisms: a. IPv4 address allocation via default bearer activation, if IPv4 is supported. b. /64 IPv6 prefix allocation via IPv6 Stateless Address autoconfiguration according to RFC 4862 [18], if IPv6 is supported; Furthermore, the Protocol Configuration Options may be used during bearer activation to configure parameters which are needed for IP address allocation. Both EPS network elements and UE may support the following mechanisms: a. IPv4 address allocation and IPv4 parameter configuration after the attach procedure via DHCPv4 according to RFC 2131 [19] and RFC 4039 [25]; b. IPv6 parameter configuration via Stateless DHCPv6 according to RFC 8415 [94]. c. Allocation of IPv6 prefixes using DHCPv6 according to RFC 8415 [94]. EPS network elements may support the following mechanism: a. Allocation of a static IPv4 address and/or a static IPv6 prefix based on subscription data in the HSS. If the static IP address/prefix is not stored in the HSS subscription record, it may be configured on a per-user per-APN basis in the DHCP/Radius/Diameter server and the PDN GW retrieves the IP address/prefix for the UE from the DHCP/Radius/Diameter server. In this case, static IP address/prefix is allocated by the same procedures as the dynamic IP address/prefix allocation (i.e. in such cases it is transparent to the PDN GW if the IP address is static or dynamic). If the static IP address/prefix is stored in the HSS subscription record, during the default bearer establishment the PDN GW receives this static IP address/prefix from Serving GW. In this case the PDN GW shall deliver the received address/prefix to the UE. The static IP address/prefix is delivered to the UE in the same way as a dynamic IP address/prefix. Thus it is transparent to the UE whether the PLMN or the external PDN allocates the IP address and whether the IP address is static or dynamic. The following clauses describe how the above listed IP address allocation mechanisms work when GTP based S5/S8 is used. The way of working of the IP address allocation mechanisms for PMIP based S5/S8 can be found in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [2].The procedures can be used both for PLMN (VPLMN/HPLMN) or external PDN based IP address allocation. In order to support DHCP based IP address configuration, the PDN GW shall act as the DHCP server towards the UE for both HPLMN assigned dynamic and static IP addressing and for VPLMN assigned dynamic IP addressing. When DHCP is used for external PDN assigned addressing and parameter configuration, the PDN GW shall act as the DHCP server towards the UE and it shall act as the DHCP client towards the external DHCP server. The Serving GW does not have any DHCP functionality. It forwards packets, including DHCP packets, between the UE and the PDN GW. IPv6 Stateless Address autoconfiguration specified in RFC 4862 [18] is the basic mechanism to allocate /64 IPv6 prefix to the UE. During default bearer establishment, the PDN GW sends the IPv6 prefix and Interface Identifier to the S-GW, and then the S-GW forwards the IPv6 prefix and Interface Identifier to the MME or to the SGSN. The MME or the SGSN forwards the IPv6 Interface Identifier to the UE. The MME does not forward the IPv6 prefix to the UE. If the UE receives the IPv6 prefix from the SGSN during PDP Context Activation procedure, it shall ignore it.

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.1

14.7.2 Format of W-APN Operator Identifier

The W-APN Operator Identifier is composed of six labels. The last three labels shall be "pub.3gppnetwork.org". The second and third labels together shall uniquely identify the PLMN. The first label distinguishes the domain name as a W-APN. For each operator, there is a default W-APN Operator Identifier (i.e. domain name). This default W-APN Operator Identifier is derived from the IMSI as follows: "w-apn.mnc<MNC>.mcc<MCC>.pub.3gppnetwork.org" where: "mnc" and "mcc" serve as invariable identifiers for the following digits. <MNC> and <MCC> are derived from the components of the IMSI defined in clause 2.2. Alternatively, the default W-APN Operator Identifier is derived using the MNC and MCC of the VPLMN. See 3GPP TS 24.234[ 3GPP system to Wireless Local Area Network (WLAN) interworking; WLAN User Equipment (WLAN UE) to network protocols; Stage 3 ] [48] for more information. The default W-APN Operator Identifier is used in both non-roaming and roaming situations when attempting to translate a W-APN consisting only of a Network Identifier into the IP address of the PDG in the HPLMN. In order to guarantee inter-PLMN DNS translation, the <MNC> and <MCC> coding used in the "w-apn.mnc<MNC>.mcc<MCC>.pub.3gppnetwork.org" format of the W-APN OI shall be: - <MNC> = 3 digits - <MCC> = 3 digits If there are only 2 significant digits in the MNC, one "0" digit shall be inserted at the left side to fill the 3 digits coding of MNC in the W-APN OI. As an example, the W-APN OI for MCC 345 and MNC 12 is coded in the DNS as: "w-apn.mnc012.mcc345.pub.3gppnetwork.org".

3GPP TS 23.003

Numbering, addressing and identification

CT WG4

3GPP Series : 23 , Technical realization ("stage 2")

14.7.2

6.42.1 Description

The requirements below refer to a “mobile base station relay”, which is a mobile base station acting as a relay between a UE and the 5G network, i.e. providing a NR access link to UEs and connected wirelessly (using NR) through a donor NG-RAN to the 5G Core. Such mobile base station relay is assumed to be mounted on a moving vehicle and serve UEs that can be located inside or outside the vehicle (or entering/leaving the vehicle). NOTE: The radio link used between a mobile base station relay and served UEs, as well as between mobile base station relay and donor RAN, is assumed to be NR-Uu; in that regard, it should be clear that a mobile base station relay is different than a UE relay (which uses instead a PC5-based link to provide indirect connection to remote UEs). Few main underlying assumptions are: - requirements cover single-hop relay scenarios as baseline (multi-hop is not precluded); - legacy UEs are supported; - other stage-1 requirements (e.g. on wireless self-backhaul), as well as existing stage-2/3 functionalities and architecture options (e.g. IAB) do not assume or address full relay mobility (e.g. relays on board of moving vehicles), thus cannot cover the requirements below, which are intended to be specific to mobile base station relays; - the identified requirements do not intend to imply or exclude specific network/relay architectures and topology solutions (e.g. could be IAB based, or others); - the MNO managing mobile base station relays, and the RAN/5GC they connect to, can be a PLMN or an NPN operator.

3GPP TS 22.261

Service requirements for the 5G system

SA WG1

3GPP Series : 22 , Service aspects ("stage 1")

6.42.1

5.6.2.3 Paging for CS fallback to A/Gb or Iu mode 5.6.2.3.1 General

The network may initiate the paging procedure for CS fallback when the UE is IMSI attached for non-EPS services (see example in figure 5.6.2.3.1.1). The network should not initiate the paging procedure for CS fallback for a UE if the MME has stored paging restriction of the UE and the Paging restriction type in the stored paging restriction preferences is set to: a) "All paging is restricted"; or b) "All paging is restricted except for specified PDN connection(s)". Figure 5.6.2.3.1.1: Paging procedure for CS fallback to A/Gb or Iu mode To initiate the procedure when no NAS signalling connection exists and no paging restriction applied in the network for that paging, the EMM entity in the network requests the lower layer to start paging (see 3GPP TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [20], 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [23]). The EMM entity may provide the lower layer with a list of CSG IDs, including the CSG IDs of both the expired and the not expired subscriptions. If there is a PDN connection for emergency bearer services established, the EMM entity in the network shall not provide the list of CSG IDs to the lower layer. The paging message includes a UE Paging Identity set to either the UE's S-TMSI or the UE's IMSI, and a CN domain indicator set to "CS" in order to indicate that this is paging for CS fallback. NOTE: The timers T3413 and T3415 are not started in the network when the paging procedure is initiated for CS fallback. To notify the UE about an incoming mobile terminating CS service excluding SMS over SGs when a NAS signalling connection exists, the EMM entity in the network shall send a CS SERVICE NOTIFICATION message. This message may also include CS service related parameters (e.g. Calling Line Identification, SS or LCS related parameters). Upon reception of a paging indication, a UE that is IMSI attached for non-EPS services shall initiate a service request procedure or combined tracking area updating procedure as specified in clause 5.5.3.3.2. If the paging is received in EMM-IDLE mode, the UE shall respond immediately. Upon reception of a paging indication, if the network supports the reject paging request feature and the MUSIM UE decides not to accept the paging the UE may initiate a service request procedure to reject the paging as specified in clause 5.6.1.1. If the paging is received as a CS SERVICE NOTIFICATION message in EMM-CONNECTED mode, the UE may request upper layers input i.e. to accept or reject CS fallback before responding with an EXTENDED SERVICE REQUEST. The response is indicated in the CSFB response information element in the EXTENDED SERVICE REQUEST message in both EMM-IDLE and EMM-CONNECTED modes.

3GPP TS 24.301

Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3

CT WG1

3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network

5.6.2.3

5.2.3 User data and signalling data integrity

The UE shall support integrity protection and replay protection of user data between the UE and the gNB. The UE shall support integrity protection of user data at any data rate, up to and including, the highest data rate supported by the UE. The UE shall activate integrity protection of user data based on the indication sent by the gNB. The UE shall support integrity protection and replay protection of RRC and NAS-signalling. The UE shall implement the following integrity protection algorithms: NIA0, 128-NIA1, 128-NIA2 as defined in Annex D of the present document. The UE may implement the following integrity protection algorithm: 128-NIA3 as defined in Annex D of the present document. The UE shall implement the integrity algorithms as specified in TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [10] if it supports E-UTRA connected to 5GC. Integrity protection of the user data between the UE and the gNB is optional to use. NOTE: Integrity protection of user plane adds the overhead of the packet size and increases the processing load both in the UE and the gNB. Integrity protection of the RRC-signalling, and NAS-signalling is mandatory to use, except in the following cases: All NAS signalling messages except those explicitly listed in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [35] as exceptions shall be integrity-protected. All RRC signalling messages except those explicitly listed in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [22] as exceptions shall be integrity-protected with an integrity protection algorithm different from NIA0, except for unauthenticated emergency calls. The UE shall implement NIA0 for integrity protection of NAS and RRC signalling. NIA0 is only allowed for unauthenticated emergency session as specified in clause 10.2.2.

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

5.2.3

12.3.5.2 Frequency of inclusion

How often or when the sender includes the overload control information is implementation specific. The sender shall ensure that new/updated overload control information is propagated to the target receivers with an acceptable delay, such that the purpose of the information, (i.e. the effective overload control protection) is achieved. The following are some of the potential approaches the sender may implement for including the OCI IE: - the sender may include OCI IE towards a receiver only when the new/changed value has not already been provided to the given receiver; - the sender may include the OCI IE in a subset of the messages towards the receiver; - the sender may include the OCI IE periodically, i.e. include the information during a first period then cease to do so during a second period. The sender may also implement a combination of one or more of the above approaches. Besides, the sender may also include the OCI IE only in a subset of the applicable GTP-C messages. The receiver shall be prepared to receive the overload control information received in any of the GTP-C messages extended with an OCI IE and upon such reception, shall be able act upon the received information.

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.3.5.2

5.40.4 Registration for Disaster Roaming service

For a UE to receive Disaster Roaming service from a PLMN providing Disaster Roaming service, the UE sends a NAS Registration Request message with Registration Type value "Disaster Roaming Initial Registration" or "Disaster Roaming Mobility Registration Update": - When the AMF in the PLMN providing Disaster Roaming service receives a NAS Registration Request with Registration Type set to "Disaster Roaming Initial Registration" or "Disaster Roaming Mobility Registration Update"; - the AMF controls if the UE is allowed to access Disaster Roaming service in the area with Disaster Condition as specified in clause 4.2.2.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]; - the AMF may provide the Disaster Roaming service indication to AUSF and UDM as specified in clause 4.2.2.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] and TS 33.501[ Security architecture and procedures for 5G System ] [29]. The AMF may provide the Disaster Roaming service indication to SMF as specified in clause 4.3.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. NOTE 1: The AUSF and the UDM are configured with Disaster Condition via OAM based on operator policy and the request by the government agencies. Based on this local configuration and/or the Disaster Roaming service indication, the AUSF can execute authentication of the UE, and the UDM can provides the subscription data for a Disaster Roaming service to the AMF and/or the SMF. To support the Disaster Roaming service, the PLMN providing Disaster Roaming service is configured to support communication with the network entities in the HPLMN of the UE, i.e. configurations related to roaming interfaces for communication between serving PLMN and HPLMN shall be deployed in the affected entities. This communication between the PLMNs need only be enabled during the Disaster Condition. The Disaster Roaming service is limited to the impacted geographic area with Disaster Condition. The NG-RAN nodes and AMF in the PLMN providing Disaster Roaming service are configured with the area information, i.e. a list of TAIs which can be formulated by the PLMN providing the Disaster Roaming service based on the geographic area with Disaster Condition in the other PLMN(s). The AMF in the PLMN providing Disaster Roaming service provides the mobility restriction list to the NG-RAN as specified in clause 5.3.4.1.1 considering the area with Disaster Condition, and also indicating that EPC is not an allowed core network. NOTE 2: From the perspective of emergency services, a UE is following procedures as described in clause 4.24 of TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47] when registered for Disaster Roaming service.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

3GPP Series : 23 , Technical realization ("stage 2")

5.40.4

4.7.3 Bearer level QoS parameters

The EPS bearer QoS profile includes the parameters QCI, ARP, GBR and MBR, described in this clause. This clause also describes QoS parameters which are applied to an aggregated set of EPS Bearers: APN-AMBR and UE-AMBR. Each EPS bearer (GBR and Non-GBR) is associated with the following bearer level QoS parameters: - QoS Class Identifier (QCI); - Allocation and Retention Priority (ARP). A QCI is a scalar that is used as a reference to access node-specific parameters that control bearer level packet forwarding treatment (e.g. scheduling weights, admission thresholds, queue management thresholds, link layer protocol configuration, etc.), and that have been pre-configured by the operator owning the access node (e.g. eNodeB). A one-to-one mapping of standardized QCI values to standardized characteristics is captured in TS 23.203[ Policy and charging control architecture ] [6]. NOTE 1: On the radio interface and on S1, each PDU (e.g. RLC PDU or GTP-U PDU) is indirectly associated with one QCI via the bearer identifier carried in the PDU header. The same applies to the S5 and S8 interfaces if they are based on GTP. NOTE 2: When required by operator policy, the eNodeB can be configured to also use the ARP priority level in addition to the QCI to control bearer level packet forwarding treatment in the eNodeB for SDFs having high priority ARPs. The ARP shall contain information about the priority level (scalar), the pre-emption capability (flag) and the pre-emption vulnerability (flag). The primary purpose of ARP is to decide whether a bearer establishment / modification request can be accepted or needs to be rejected due to resource limitations (typically available radio capacity for GBR bearers). The priority level information of the ARP is used for this decision to ensure that the request of the bearer with the higher priority level is preferred. In addition, the ARP can be used (e.g. by the eNodeB) to decide which bearer(s) to drop during exceptional resource limitations (e.g. at handover). The pre-emption capability information of the ARP defines whether a bearer with a lower ARP priority level should be dropped to free up the required resources. The pre-emption vulnerability information of the ARP defines whether a bearer is applicable for such dropping by a pre-emption capable bearer with a higher ARP priority level. Once a bearer has been successfully established, the packet handling (e.g. scheduling and rate control) within the eNodeB, PDN GW, and Serving GW should be solely determined by the following EPS bearer QoS parameters: QCI, GBR and MBR, and by the AMBR parameters. However, when required by operator policy, the eNodeB can be configured to also use a bearer's ARP priority level in addition to the QCI to determine the relative priority of the SDFs for packet handling (e.g. scheduling and rate control) in the eNodeB as defined in TS 23.203[ Policy and charging control architecture ] [6] clause 6.1.7.2. This configuration applies only for bearers with high priority ARPs as defined in TS 23.203[ Policy and charging control architecture ] [6] clause 6.1.7.3. The ARP priority level may be used in addition to the QCI to determine the transport level packet marking, e.g. to set the DiffServ Code Point. The ARP is not included within the EPS QoS Profile sent to the UE. NOTE 3: The ARP should be understood as "Priority of Allocation and Retention"; not as "Allocation, Retention, and Priority". NOTE 4: Video telephony is one use case where it may be beneficial to use EPS bearers with different ARP values for the same UE. In this use case an operator could map voice to one bearer with a higher ARP, and video to another bearer with a lower ARP. In a congestion situation (e.g. cell edge) the eNodeB can then drop the "video bearer" without affecting the "voice bearer". This would improve service continuity. NOTE 5: The ARP may also be used to free up capacity in exceptional situations, e.g. a disaster situation. In such a case the eNodeB may drop bearers with a lower ARP priority level to free up capacity if the pre-emption vulnerability information allows this. Each GBR bearer is additionally associated with the following bearer level QoS parameters: - Guaranteed Bit Rate (GBR); - Maximum Bit Rate (MBR). The GBR denotes the bit rate that can be expected to be provided by a GBR bearer. The MBR limits the bit rate that can be expected to be provided by a GBR bearer (e.g. excess traffic may get discarded by a rate shaping function). See clause 4.7.4 for further details on GBR and MBR. GBR bearers are not supported by NB-IoT. The PDN GW uses the RAT Type to ensure that GBR bearers are not active when the UE is using NB-IoT. Each APN access, by a UE, is associated with the following QoS parameter: - per APN Aggregate Maximum Bit Rate (APN-AMBR). The subscribed APN-AMBR is a subscription parameter stored per APN in the HSS, which applies as APN-AMBR unless the APN-AMBR is modified by the MME (e.g in roaming scenarios and/or for usage of NB-IoT) or the PDN GW, based on local policy (e.g. for RAT Type = NB-IoT) or PCRF interactions. The APN-AMBR limits the aggregate bit rate that can be expected to be provided across all Non-GBR bearers and across all PDN connections of the same APN (e.g. excess traffic may get discarded by a rate shaping function). Each of those Non-GBR bearers could potentially utilize the entire APN-AMBR, e.g. when the other Non-GBR bearers do not carry any traffic. GBR bearers are outside the scope of APN-AMBR. The P-GW enforces the APN-AMBR in downlink. Enforcement of APN-AMBR in uplink is done in the UE and additionally in the P-GW. NOTE 6: All simultaneous active PDN connections of a UE that are associated with the same APN shall be provided by the same PDN GW (see clauses 4.3.8.1 and 5.10.1). APN-AMBR applies to all PDN connections of an APN. For the case of multiple PDN connections of an APN, if a change of APN-AMBR occurs due to local policy or the PDN GW is provided the updated APN-AMBR for each PDN connection from the MME or PCRF, the PDN GW initiates explicit signalling for each PDN connection to update the APN-AMBR value. Each UE in state EMM-REGISTERED is associated with the following bearer aggregate level QoS parameter: - per UE Aggregate Maximum Bit Rate (UE-AMBR). The UE-AMBR is limited by a subscription parameter stored in the HSS. The MME shall set the UE-AMBR to the sum of the APN-AMBR of all active APNs up to the value of the subscribed UE-AMBR. The UE-AMBR limits the aggregate bit rate that can be expected to be provided across all Non-GBR bearers of a UE (e.g. excess traffic may get discarded by a rate shaping function). Each of those Non-GBR bearers could potentially utilize the entire UE-AMBR, e.g. when the other Non-GBR bearers do not carry any traffic. GBR bearers are outside the scope of UE AMBR. The E-UTRAN enforces the UE-AMBR in uplink and downlink except for PDN connections using the Control Plane CIoT EPS Optimisation. The GBR and MBR denote bit rates of traffic per bearer while UE-AMBR/APN-AMBR denote bit rates of traffic per group of bearers. Each of those QoS parameters has an uplink and a downlink component. On S1_MME the values of the GBR, MBR, and AMBR refer to the bit stream excluding the GTP-U/IP header overhead of the tunnel on S1_U. The HSS defines, for each PDN subscription context, the 'EPS subscribed QoS profile' which contains the bearer level QoS parameter values for the default bearer (QCI and ARP) and the subscribed APN-AMBR value. The subscribed ARP shall be used to set the priority level of the EPS bearer parameter ARP for the default bearer while the pre-emption capability and the pre-emption vulnerability information for the default bearer are set based on MME operator policy. In addition, the subscribed ARP shall be applied by the P-GW for setting the ARP priority level of all dedicated EPS bearers of the same PDN connection unless a different ARP priority level setting is required (due to P-GW configuration or interaction with the PCRF). NOTE 7: The ARP parameter of the EPS bearer can be modified by the P-GW (e.g. based on interaction with the PCRF due to e.g. MPS user initiated session) to assign the appropriate pre-emption capability and the pre-emption vulnerability setting. The ARP pre-emption vulnerability of the default bearer should be set appropriately to minimize the risk of unnecessary release of the default bearer.

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.7.3

8.21.5 ECGI field

The coding of ECGI (E-UTRAN Cell Global Identifier) is depicted in Figure 8.21.5-1. Only zero or one ECGI field shall be present in ULI IE. Figure 8.21.5-1: ECGI field The E-UTRAN Cell Identifier (ECI) consists of 28 bits. The ECI field shall start with Bit 4 of octet e+3, which is the most significant bit. Bit 1 of Octet e+6 is the least significant bit. The coding of the E-UTRAN cell identifier is the responsibility of each administration. Coding using full hexadecimal representation (binary, not ASCII encoding) shall be used.

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.21.5

5.5.2 Conditions for sending TEID=0 in GTPv2-C header

If a peer's TEID is not available, the TEID field still shall be present in the header and its value shall be set to "0" in the following messages: - Create Session Request message on S2a/S2b/S5/S8 - Create Session Request message on S4/S11, if for a given UE, the SGSN/MME has not yet obtained the Control TEID of the SGW. - Create Indirect Data Forwarding Tunnel Request message on S4/S11, if the SGW selected by the MME/S4-SGSN for indirect data forwarding is different from the SGW used as anchor. - Identification Request/Response messages. - Forward Relocation Request message over the S10, S16 and N26 interfaces, and over the S3 interface during I-RAT handover when ISR is not active. - Forward Relocation Request message over the S3 interface during I-RAT handover between ISR associated nodes, when ISR is active for the UE, and if the node decides to allocate new S3 TEID-C. - Context Request message over the S10, S16, S3 and N26 interfaces. - Relocation Cancel Request message over the S10, S16, S3 and N26 interfaces, except for the case where the old SGSN/MME or AMF has already been assigned the Tunnel Endpoint Identifier Control Plane of the new SGSN/MME or AMF. - Relocation Cancel Response message over the S10, S16, S3 and N26 interfaces if the new SGSN/MME or AMF does not have the Tunnel Endpoint Identifier Control Plane of the old SGSN/MME or AMF. - Delete PDN Connection Set Request/Response messages. - Configuration Transfer Tunnel message. - RAN Information Relay message. - If a node receives a message and the TEID-C in the GTPv2 header of the received message is not known, it shall respond with "Context not found" Cause in the corresponding response message to the sender, the TEID used in the GTPv2-C header in the response message shall be then set to zero. - If a node receives a request message containing protocol error, e.g. Mandatory IE missing, which requires the receiver to reject the message as specified in clause 7.7, it shall reject the request message. For the response message, the node should look up the remote peer's TEID and accordingly set the GTPv2-C header TEID and the message cause code. As an implementation option, the node may not look up the remote peer's TEID and set the GTPv2-C header TEID to zero in the response message. However in this case, the cause code shall not be set to "Context not found". - MBMS Session Start Request message. - PGW Restart Notification / PGW Restart Notification Acknowledge messages. - Downlink Data Notification message sent on S11/S4 as part of the Network Triggered Service Restoration procedure (see 3GPP TS 23.007[ Restoration procedures ] [17]), and corresponding Downlink Data Notification Acknowledge and Downlink Data Notification Failure Indication if the SGW did not include the Sender F-TEID for Control Plane IE in the Downlink Data Notification message. - Stop Paging Indication message is sent to the the restarted CN node (or another node in the same pool) as part of the Network Triggered Service Restoration procedure with ISR (see 3GPP TS 23.007[ Restoration procedures ] [17]). - Suspend Notification and Suspend Acknowledge messages: over S16 interface; over S3 interface when ISR is not active. - PGW Downlink Triggering Notification message on S5 and S11/S4, PGW Downlink Triggering Acknowledge message on S11/S4, and PGW Downlink Triggering Acknowledge message on S5 if the PGW did not include the Sender F-TEID for Control Plane IE in the PGW Downlink Triggering Notification message. - UE Registration Query Request and UE Registration Query Response messages over S3 interface. NOTE: Legacy implementation conforming to earlier versions of this specification can send the Change Notification Request/Response messages on the TEID zero in spite of the peer's node TEID being available.

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

5.5.2

8.116 WLAN Offloadability Indication

WLAN Offloadability Indication IE is coded as depicted in Figure 8.116-1. Figure 8.116-1: WLAN Offloadability Indication Octet 5 indicates if WLAN Offload has been authorized for the UE: - Bit 8 to 3 Spare, for future use and set to zero. - Bit 2 – reflects the information available at the UE regarding E-UTRAN Offloadability. When set to '1', this indicates that the UE has been authorized to perform WLAN offload from E-UTRAN. When set to '0', this indicates that the UE has not been authorized to perform WLAN offload from E-UTRAN. - Bit 1 – reflects the information available at the UE regarding UTRAN Offloadability. When set to '1', this indicates that the UE has been authorized to perform WLAN offload from UTRAN. When set to '0', this indicates that the UE has not been authorized to perform WLAN offload from UTRAN.

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.116

5.4.4.1 UE radio capability information storage in the AMF

This clause applies when no radio capability signalling optimisation is used between a UE and the network. The UE Radio Capability information is defined in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27] and contains information on RATs that the UE supports (e.g. power class, frequency bands, etc). Consequently, this information can be sufficiently large that it is undesirable to send it across the radio interface at every transition of UE CM state in the AMF from CM-IDLE to CM-CONNECTED. To avoid this radio overhead, the AMF shall store the UE Radio Capability information during CM-IDLE state for the UE and RM-REGISTERED state for the UE and the AMF shall if it is available, send its most up to date UE Radio Capability information to the RAN in the N2 REQUEST message, i.e. INITIAL CONTEXT SETUP REQUEST or UE RADIO CAPABILITY CHECK REQUEST. NOTE 1: Due to issues with the handling of dynamic UMTS security parameters, the UTRA UE Radio Capability information is excluded from the information that is uploaded and stored in the AMF (see TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27]). The AMF deletes the UE radio capability when the UE RM state in the AMF transitions to RM-DEREGISTERED. When the AMF receives Registration Request with the Registration type set to Initial Registration or when it receives the first Registration Request after E-UTRA/EPC Attach with Registration type set to Mobility Registration Update, the AMF deletes the UE radio capability. The UE Radio Capability is maintained in the core network, even during AMF reselection. NOTE 2: The UE Radio Capability is not transferred to EPC during the inter-system mobility. If the UE's NG-RAN or E-UTRAN UE Radio Capability information changes while in CM-IDLE state, the UE shall perform the Registration procedure with the Registration type set to Mobility Registration Update and it also includes "UE Radio Capability Update". (For specific requirements for a UE operating in dual-registration mode see clause 5.17.2.1). When the AMF receives Mobility Registration Update Request with "UE Radio Capability Update" requested by the UE, it shall delete any UE Radio Capability information that it has stored for the UE. If the UE's NG-RAN UE Radio Capability information changes when the UE is in CM-IDLE with Suspend, NAS shall trigger AS to establish a new RRC connection and not resume the existing one in order to perform the Registration procedure with the Registration type set to Mobility Registration Update including "UE Radio Capability Update". As a result of this, the access stratum in the UE will discard the AS information and establish a new RRC connection as defined in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [51]. If the trigger to change the UE's NG-RAN or E-UTRAN UE Radio Capability information happens when the UE is in CM-CONNECTED state, the UE shall first enter CM-IDLE state and then perform the Registration procedure with the Registration type set to Mobility Registration Update and it also includes "UE Radio Capability Update". The RAN stores the UE Radio Capability information, received in the N2 message or obtained from the UE, for the duration of the UE staying in RRC_CONNECTED or RRC_INACTIVE state. Before any 5G SRVCC handover attempt from NG-RAN to UTRAN, the RAN retrieves the UE's UTRA UE Radio Capabilities from the UE. (For specific requirements for a UE operating in dual-registration mode see clause 5.17.2.1). If the AMF sends N2 REQUEST (i.e. INITIAL CONTEXT SETUP REQUEST or UE RADIO CAPABILITY CHECK REQUEST) message to NG-RAN without UE Radio Capability information in that message and there is no UE Radio Capability information available in RAN, this triggers the RAN to request the UE Radio Capability from the UE and to upload it to the AMF in the N2 UE RADIO CAPABILITY INFO INDICATION message. If a UE supports both NB-IoT and other RATs the UE handles the UE Radio capability information as follows: - When the UE is camping on NB-IoT the UE provides only NB-IoT UE radio capabilities to the network. - When the UE is not camping on NB-IoT, the UE provides UE radio capabilities for the RAT but not NB-IoT UE radio capabilities to the network. In order to handle the distinct UE radio capabilities, the AMF stores a separate NB-IoT specific UE Radio Capability information when the UE provides the UE Radio Capability information while camping on NB-IoT. When the UE is camping on NB-IoT, the AMF sends, if available, the NB-IoT RAT specific UE Radio Capability information to the E-UTRAN. When the UE is not camping on NB-IoT, the AMF sends, if available, UE radio capabilities for the RAT but not NB-IoT radio capabilities.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

3GPP Series : 23 , Technical realization ("stage 2")

5.4.4.1

15 Interworking between Packet Domains

The primary reason for the interworking between Packet Domains is to support roaming subscribers as described in 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [3]. The general model for both GPRS and EPS Packet Domain interworking is shown in figure 21. Figure 21: General interworking model for GPRS Packet Domains and EPS Packet Domains to support roaming subscribers. NOTE: There may be multiple Packet Domains of the same type which interwork each other, such as the case of interwork between two GPRS Packet Domains. For roaming subscribers that have a PDP address allocated from the HPLMN a forwarding route between the HPLMN and the VPLMN is created. This route is used for both mobile terminated and mobile originated data traffic. The communication is done via the BGs (Border Gateways) as described in 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [3]. The procedures to set the link between the SGSN in the VPLMN and the GGSN in the HPLMN are described in 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [3]. The inter-PLMN link may be any packet data network or dedicated link as described in 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [3]. The PLMN operators may have a dedicated inter-PLMN link to fulfil the QoS requirements of a certain protocol. In the case of interworking between EPS Packet Domains, S8 reference point is the inter-PLMN interface, linking PDN GW of HPLMN and Serving GW of VPLMN. The procedure for setting the link is described in 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [77] and TS 23.402[ Architecture enhancements for non-3GPP accesses ] [78].

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

15

8.1.2.12.2 Applicability rule and antenna connection for control channel tests

8.1.2.12.2.1 Applicability rule and antenna connection for control channel tests with 2Rx For 8Rx capable UEs, all single carrier tests specified in 8.2 to 8.8 for control channel with 2Rx are tested on any of the 2Rx supported RF bands by connecting 2 out of the 8Rx with data source from system simulator, and the other 6 Rx are connected with zero input, depending on UE’s declaration and AP configuration. Same requirements specified with 2Rx should be applied. For 8Rx capable UEs without any 2Rx supported RF bands and with 4Rx supported RF bands, all single carrier tests specified in 8.2 to 8.8 for control channel with 2Rx are tested on any of the 4Rx supported RF bands by duplicating the fading channel from each Tx antenna and add independent noise for each Rx antenna. The SNR requirements should be applied with 1.5 dB less than the number specified for 2Rx tests. For 8Rx capable UEs without any 2Rx and without 4Rx supported RF bands, all single carrier tests specified in 8.2 to 8.8 for control channel with 2Rx are tested on any of the 8Rx supported RF bands by duplicating the fading channel from each Tx antenna and add independent noise for each Rx antenna, as illustrated in Figure 8.1.2.12.1-1 and Figure 8.1.2.12.1-2. The SNR requirements should be applied with 1.5 dB less than the number specified for 2Rx tests. 8.1.2.12.2.2 Applicability rule and antenna connection for control channel tests with 4Rx For 8Rx capable UEs, all single carrier tests specified in 8.10 for control channel with 4Rx are tested on any of the 4Rx supported RF bands by connecting 4 out of the 8Rx with data source from system simulator, and the other 4 Rx are connected with zero input, depending on UE’s declaration and AP configuration. Same requirements specified with 4Rx should be applied. For 8Rx capable UEs without any 4Rx supported RF bands, all single carrier tests specified in 8.10 for control channel with 4Rx are tested on any of the 8Rx supported RF bands by duplicating the fading channel from each Tx antenna and add independent noise for each Rx antenna, as illustrated in Figure 8.1.2.12.1-3 and Figure 8.1.2.12.1-4. Same requirements specified with 4Rx should be applied.

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.1.2.12.2

10.5.4.21b Redirecting party BCD number

The purpose of the redirecting party BCD number information element is to identify the redirecting party. The redirecting party BCD number information element is coded as shown in figure 10.5.108a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The redirecting party BCD number is a type 4 information element. In the network to mobile station direction it has a minimum length of 3 octets and a maximum length of 19 octets. Figure 10.5.108a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Redirecting party BCD number information element NOTE 1: The contents of octets 3, 4, etc. are coded as shown in table 10.5.118/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The coding of octet 3a is defined in table 10.5.120/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . NOTE 2: If the redirecting party BCD number contains an odd number of digits, bits 5 to 8 of the last octet shall be filled with an end mark coded as "1111".

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.4.21b

4.12b.4.1 Service Request procedures

The Service Request procedure for devices that do not support 5G NAS signalling over WLAN access shall be used by a TWIF when the CM state in TWIF for a N5CW device is CM-IDLE over Trusted WLAN to request the re-establishment of the NAS signalling connection and the re-establishment of the user plane for all or some of the PDU Sessions which are associated to non-3GPP access. The Service Request procedure for N5CW devices shall be used by a TWIF when the CM state in TWIF for a N5CW device is CM-CONNECTED over trusted WLAN to request the re-establishment of the user plane for one or more PDU Sessions which are associated to non-3GPP access. This Service Request procedure shall be supported as specified in clause 4.12a.4.1 for the trusted non-3GPP access with the following modifications: - The trusted non-3GPP access is substituted by a trusted WLAN access point (TWAP). - The TNGF is substituted by the TWIF. - The TWIF sends and receives NAS messages on behalf of N5CW device. - The user plane between the N5CW device and TWIF is established with Yt' connection instead of IKEv2 signalling.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

3GPP Series : 23 , Technical realization ("stage 2")

4.12b.4.1

4.2.3.2 Number of E-RABs successfully modified the QoS parameter

a) This measurement provides the number of E-RABs successfully modified the QoS parameter. The measurement is split into subcounters per E-RAB QoS level (QCI). b) CC c) On transmission by the eNodeB/RN of an E-RAB MODIFY RESPONSE message, each E-RAB successfully modified the QoS parameter is added to the relevant measurement per QCI, the possible QCIs are included in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [9]. The sum of all supported per QCI measurements shall equal the total number of E-RABs successfully modified the QoS parameter. In case only a subset of per QCI measurements is supported, a sum subcounter will be provided first. d) Each measurement is an integer value. The number of measurements is equal to the number of QCIs plus a possible sum value identified by the .sum suffix. e) The measurement name has the form ERAB.ModQoSSuccNbr.QCI where QCI identifies the target E-RAB level quality of service class. 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.2.3.2

4.7.5.1 Normal and periodic routing area updating procedure

Periodic routing area updating is used to periodically notify the availability of the MS to the network. The value of the update type IE in the ROUTING AREA UPDATE REQUEST message shall indicate "periodic updating". The procedure is controlled in the MS by timer T3312. When timer T3312 expires, the periodic routing area updating procedure is started. Start and reset of timer T3312 is described in subclause 4.7.2.2. The normal routing area updating procedure is initiated: - when the MS detects a change of the routing area in state GMM-REGISTERED; - when the MS determines that GPRS resumption shall be performed; - when the MS needs to update the network with the new MS Radio Access Capability IE; - when the MS needs to update the network with the new DRX parameter IE; - in Iu mode, to re-synchronize the PMM mode of MS and network after RRC connection release with cause "Directed signalling connection re-establishment", see subclause 4.7.2.5; - in Iu mode, to re-synchronize the PMM mode of MS and network after inter-system change not due to PS handover from PMM-CONNECTED mode in Iu mode to A/Gb mode or S1 mode, if the MS performs an inter - system change back to Iu mode without sending a ROUTING AREA UPDATE REQUEST message while in A/Gb mode or a TRACKING AREA UPDATE REQUEST message while in S1 mode; - in Iu mode and A/Gb mode, after intersystem change from S1 mode, and the GMM receives an indication of "RRC connection failure" from lower layers due to lower layer failure while in S1 mode. In this case, if the TIN indicates "RAT-related TMSI", the MS shall set the TIN to "GUTI" before initiating the routing area updating procedure; - in A/Gb mode, after intersystem change from S1 mode if the TIN indicates "RAT-related TMSI", but the MS is required to perform routing area updating for IMS voice termination as specified in annex P.4; - when the MS enters GMM-REGISTERED.NORMAL-SERVICE and the TIN indicates "GUTI"; - when the MS has selected a CSG cell whose CSG identity and associated PLMN identity are not included in the Allowed CSG list;or in the Operator CSG list; - when the MS supports SRVCC and changes the mobile station classmark 2, mobile station classmark 3 or the supported codecs; - when the MS changes the MS network capability information; - when the UE's usage setting or the voice domain preference for E-UTRAN change in the MS; - when the MS activates mobility management for IMS voice termination as specified in annex P.2 and the TIN indicates "RAT-related TMSI"; - upon reception of a paging indication, using P-TMSI, if the timer T3346 is running and the MS is in state GMM-REGISTERED.ATTEMPTING-TO-UPDATE and the RAI of the current cell is same as the stored RAI; - in A/Gb mode, after intersystem change from S1 mode via cell change order procedure not due to CS fallback, if the TIN indicates "RAT-related TMSI"; in this case the MS shall set the TIN to "GUTI" before initiating the routing area updating procedure; - in A/Gb or Iu mode in NMO I, after intersystem change from S1 mode due to CS fallback, if the TIN indicates "GUTI" or if the routing area the MS is in is different from the registered routing area; - in A/Gb mode, after Inter RAT handover from S1 mode or Iu mode; - when the MS needs to request the use of PSM or needs to stop the use of PSM; - when the MS needs to request the use of eDRX or needs to stop the use of eDRX; - when a change in the PSM usage conditions at the MS requires a different timer T3312 value or different timer T3324 value; - when a change in the eDRX usage conditions at the MS requires different extended DRX parameters; or NOTE 1: A change in the PSM or eDRX usage conditions at the MS can include e.g. a change in the MS configuration, a change in requirements from upper layers or the battery running low at the MS. - when the Default_DCN_ID value changes, 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]. NOTE 2: The routing area updating procedure is initiated after deleting the DCN-ID list as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120], annex C. The ROUTING AREA UPDATE REQUEST message shall always be the first data sent by the MS when a routing area border is crossed. The routing area identification is broadcast on the broadcast channel(s). A normal routing area updating shall abort any ongoing GMM procedure. Aborted GMM procedures may be repeated after the normal routing area updating procedure has been successfully performed. The value of the update type IE included in the message shall indicate "RA updating". If the normal routing area updating procedure is initiated due to the reception of the paging indication while timer T3346 is running, the "follow-on request pending" indication shall be set to 1.

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.5.1

6.6.1.2.6 Abnormal cases on the network side

The following abnormal cases can be identified: a) Expiry of timer T3489: On the first expiry of the timer T3489, the MME shall resend the ESM INFORMATION REQUEST message and shall reset and restart timer T3489. This retransmission is repeated two times, i.e. on the third expiry of timer T3489, the MME shall abort the procedure, release any resources for this procedure and reject the associated PDN connectivity procedure including the ESM cause #53 "ESM information not received", in the PDN CONNECTIVITY REJECT message.

3GPP TS 24.301

Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3

CT WG1

3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network

6.6.1.2.6

– MeasConfig

The IE MeasConfig specifies measurements to be performed by the UE, and covers intra-frequency, inter-frequency and inter-RAT mobility as well as configuration of measurement gaps. MeasConfig information element -- ASN1START -- TAG-MEASCONFIG-START MeasConfig ::= SEQUENCE { measObjectToRemoveList MeasObjectToRemoveList OPTIONAL, -- Need N measObjectToAddModList MeasObjectToAddModList OPTIONAL, -- Need N reportConfigToRemoveList ReportConfigToRemoveList OPTIONAL, -- Need N reportConfigToAddModList ReportConfigToAddModList OPTIONAL, -- Need N measIdToRemoveList MeasIdToRemoveList OPTIONAL, -- Need N measIdToAddModList MeasIdToAddModList OPTIONAL, -- Need N s-MeasureConfig CHOICE { ssb-RSRP RSRP-Range, csi-RSRP RSRP-Range } OPTIONAL, -- Need M quantityConfig QuantityConfig OPTIONAL, -- Need M measGapConfig MeasGapConfig OPTIONAL, -- Need M measGapSharingConfig MeasGapSharingConfig OPTIONAL, -- Need M ..., [[ interFrequencyConfig-NoGap-r16 ENUMERATED {true} OPTIONAL -- Need R ]], [[ effectiveMeasWindowConfig-r18 SetupRelease {MeasWindowConfig-r18} OPTIONAL -- Need M ]] } MeasObjectToRemoveList ::= SEQUENCE (SIZE (1..maxNrofObjectId)) OF MeasObjectId MeasIdToRemoveList ::= SEQUENCE (SIZE (1..maxNrofMeasId)) OF MeasId ReportConfigToRemoveList ::= SEQUENCE (SIZE (1..maxReportConfigId)) OF ReportConfigId -- TAG-MEASCONFIG-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

4.2.7.2.3 Re-Creating NGAP UE-TNLA-bindings subsequent to NGAP UE-TNLA-binding release

If the AMF has released the NGAP UE-TNLA-binding in the 5G-AN node for a UE and the 5G-AN node needs to send an N2 message for this UE, the following applies: - The 5G-AN node checks the GUAMI stored in the UE context and the associated AMF: - If the GUAMI is available, 5G-AN selects the AMF which owns that GUAMI. - If GUAMI has been marked as unavailable (i.e. based on AMF unavailable status indication received from AMF) but one corresponding target AMF has been indicated, 5G-AN selects that target AMF even if the GUAMI has not been updated as available by the target AMF. - If GUAMI has been marked as unavailable (i.e. based on AMF unavailable status indication received from AMF) and no corresponding target AMF has been indicated, the 5G-AN selects an AMF from the AMF Set based on AMF Set ID of the GUAMI, as defined in clause 6.3.5 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. - The 5G-AN node creates an NGAP UE-TNLA-binding for the UE by selecting a TNL association from the available TNL associations permitted for the initial N2 message with the selected AMF, as defined in clause 5.21.1.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2],and sends the N2 message to the AMF via the selected TNL association. - The AMF may decide to use the TNL association selected by the 5G-AN or the AMF may modify the NGAP UE-TNLA-binding by triangular redirection. If the NGAP UE-TNLA-binding has been released for a UE and the AMF needs to send an N2 message for this UE, the following applies: - The AMF selects a TNL association from the available TNL associations for the target 5G-AN node and sends the N2 message via this TNL association. The target 5G-AN node creates an NGAP UE-TNLA-binding for the UE based on the TNL association selected by the AMF. The TNL association chosen by the AMF always takes precedence. NOTE: This addresses situations where 5G-AN node and AMF select a TNL association for a UE concurrently.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

3GPP Series : 23 , Technical realization ("stage 2")

4.2.7.2.3

4.8.4A.2 Redirection of the UE by the core network

The network that supports CIoT optimizations can redirect a UE between EPC and 5GCN as specified in subclause 5.31.3 of 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]. The network can take into account the UE's N1 mode capability or S1 mode capability, the CIoT network behaviour supported and preferred by the UE or the CIoT network behaviour supported by the network to determine the redirection. NOTE: It is assumed that the network would avoid redirecting the UE back and forth between EPC and 5GCN. The network redirects the UE to EPC by rejecting the registration request or service request with the 5GMM cause #31 "Redirection to EPC required" as specified in subclause 5.5.1.2.5, 5.5.1.3.5 and 5.6.1.5. Upon receipt of reject message, the UE disables the N1 mode capability for 3GPP access as specified in subclause 4.9.2 and enables the E-UTRA capability if it was disabled in order to move to EPC. When there is no ongoing registration procedure or service request procedure for a UE in 5GMM-CONNECTED mode, if the AMF determines to redirect the UE to EPC, the AMF shall initiate the generic UE configuration update procedure to indicate registration requested and release of the N1 NAS signalling connection not requested as described in subclause 5.4.4. The network then redirects the UE to EPC by rejecting the registration request as specified in subclause 5.5.1.3.5. The network that supports CIoT optimizations can also redirect a UE from EPC to 5GCN as specified in subclause 5.3.19.2 of 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

4.8.4A.2

6.3.1.2.1 PDU EAP message reliable transport procedure initiation

In order to initiate the PDU EAP message reliable transport procedure, the SMF shall create a PDU SESSION AUTHENTICATION COMMAND message. The SMF shall set the PTI IE of the PDU SESSION AUTHENTICATION COMMAND message to "No procedure transaction identity assigned". The SMF shall set the EAP message IE of the PDU SESSION AUTHENTICATION COMMAND message to the EAP-request message provided by the DN or generated locally. The SMF shall send the PDU SESSION AUTHENTICATION COMMAND message, and the SMF shall start timer T3590 (see example in figure 6.3.1.1). Upon receipt of the PDU SESSION AUTHENTICATION COMMAND message, if the UE provided a DNN during the PDU session establishment, the UE shall stop timer T3396, if it is running for the DNN provided by the UE. If the UE did not provide a DNN during the PDU session establishment, the UE shall stop the timer T3396 associated with no DNN if it is running. In an SNPN, the timer T3396 to be stopped includes: a) the timer T3396 applied for all the equivalent SNPNs, associated with the RSNPN or an equivalent SNPN, and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and b) the timer T3396 applied for the registered SNPN, associated with the RSNPN, and, if the UE supports access to an SNPN using credentials from a credentials holder, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running. Upon receipt of the PDU SESSION AUTHENTICATION COMMAND message, if the UE provided an S-NSSAI and a DNN during the PDU session establishment, the UE shall stop timer T3584, if it is running for the [S-NSSAI of the PDU session, DNN] combination. If the UE provided a DNN but did not provide an S-NSSAI during the PDU session establishment, the UE shall stop timer T3584, if it is running for the same [no S-NSSAI, DNN] combination provided by the UE. If the UE provided an S-NSSAI but did not provide a DNN during the PDU session establishment, the UE shall stop timer T3584, if it is running for the same [S-NSSAI, no DNN] combination provided by the UE. If the UE provided neither a DNN nor an S-NSSAI during the PDU session establishment, the UE shall stop timer T3584, if it is running for the same [no S-NSSAI, no DNN] combination provided by the UE. The timer T3584 to be stopped includes: a) in a PLMN: 1) the timer T3584 applied for all the PLMNs, if running; and 2) the timer T3584 applied for the registered PLMN, if running; or b) in an SNPN: 1) the timer T3584 applied for all the equivalent SNPNs, and associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and 2) the timer T3584 applied for the registered SNPN, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running. Upon receipt of the PDU SESSION AUTHENTICATION COMMAND message, if the UE provided an S-NSSAI during the PDU session establishment, the UE shall stop timer T3585, if it is running for the S-NSSAI of the PDU session. If the UE did not provide an S-NSSAI during the PDU session establishment, the UE shall stop the timer T3585 associated with no S-NSSAI if it is running. The timer T3585 to be stopped includes: a) in a PLMN: 1) the timer T3585 applied for all the PLMNs and for the access over which the PDU SESSION AUTHENTICATION COMMAND message is received, if running; 2) the timer T3585 applied for all the PLMNs and for both 3GPP access type and non-3GPP access type, if running; 3) the timer T3585 applied for the registered PLMN and for the access over which the PDU SESSION AUTHENTICATION COMMAND message is received, if running; and 4) the timer T3585 applied for the registered PLMN and for both 3GPP access type and non-3GPP access type, if running; or b) in an SNPN: 1) the timer T3585 applied for all the equivalent SNPNs and for the access over which the PDU SESSION AUTHENTICATION COMMAND message is received, associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; 2) the timer T3585 applied for all the equivalent SNPNs and for both 3GPP access type and non-3GPP access type, associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; 3) the timer T3585 applied for the registered SNPN and for the access over which the PDU SESSION AUTHENTICATION COMMAND message is received, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and 4) the timer T3585 applied for the registered PLMN and for both 3GPP access type and non-3GPP access type, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running. NOTE 1: Upon receipt of the PDU SESSION AUTHENTICATION COMMAND message for a PDU session, if the UE provided a DNN (or no DNN) and an S-NSSAI (or no S-NSSAI) when the PDU session is established, timer T3396 associated with the DNN (or no DNN, if no DNN was provided by the UE) is running, and timer T3584 associated with the DNN (or no DNN, if no DNN was provided by the UE) and the S-NSSAI (or no S-NSSAI, if no S-NSSAI was provided by the UE) is running, then the UE stops both the timer T3396 and the timer T3584. NOTE 2: Upon receipt of the PDU SESSION AUTHENTICATION COMMAND message for a PDU session, if the UE provided a DNN (or no DNN) and an S-NSSAI (or no S-NSSAI) when the PDU session is established, timer T3585 associated with the S-NSSAI (or no S-NSSAI, if no S-NSSAI was provided by the UE) is running, and timer T3584 associated with the DNN (or no DNN, if no DNN was provided by the UE) and the S-NSSAI (or no S-NSSAI, if no S-NSSAI was provided by the UE) is running, then the UE stops both the timer T3585 and the timer T3584. Upon receipt of a PDU SESSION AUTHENTICATION COMMAND message and a PDU session ID, using the NAS transport procedure as specified in subclause 5.4.5, the UE passes to the upper layers the EAP message received in the EAP message IE of the PDU SESSION AUTHENTICATION COMMAND message. Apart from this action and the stopping of timers T3396, T3584 and T3485 (if running), the authentication and authorization procedure initiated by the DN is transparent to the 5GSM layer of the UE.

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.3.1.2.1

6.3.2A.1 Minimum requirement for CA

For inter-band carrier aggregation with uplink assigned to two E-UTRA bands, the minimum output power is defined per carrier and the requirement is specified in subclause 6.3.2.1. If two contiguous component carriers are assigned to one E-UTRA band, the requirements in subclause 6.3.2A.1 apply for those component carriers. For intra-band contiguous and non-contiguous carrier aggregation the minimum output power is defined as the mean power in one sub-frame (1ms). The minimum output power shall not exceed the values specified in Table 6.3.2A.1-1. Table 6.3.2A.1-1: Minimum output power for intra-band contiguous and non-contiguous CA UE

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.2A.1

5.3.1.2 Re-establishment of the N1 NAS signalling connection

When the UE in 5GMM-CONNECTED mode over 3GPP access receives a fallback indication from lower layers, and the UE has no pending NAS procedure and no pending uplink user data for PDU session(s) with user-plane resources already established, the UE shall: a) enter 5GMM-IDLE mode; and b) initiate the registration procedure for mobility and periodic registration update and include the Uplink data status IE in the REGISTRATION REQUEST message indicating the PDU session(s) for which user-plane resources were active prior to receiving the fallback indication, if any (see subclause 5.5.1.3 for further details). When the UE in 5GMM-CONNECTED mode over 3GPP access receives a fallback indication from lower layers, and the UE has pending uplink user data for PDU session(s) with user-plane resources already established but no pending NAS procedure, the UE shall: a) enter 5GMM-IDLE mode; and b) initiate the service request procedure and include the Uplink data status IE in the SERVICE REQUEST message or the CONTROL PLANE SERVICE REQUEST message indicating the PDU session(s) for which user-plane resources were active prior to receiving the fallback indication (see subclause 5.6.1 for further details). When the UE in 5GMM-CONNECTED mode over 3GPP access receives a fallback indication from lower layers, and the UE has a pending registration procedure, a service request procedure, or a de-registration procedure, the UE shall: a) enter 5GMM-IDLE mode; b) proceed with the pending procedure; and c) if the pending procedure is a service request or registration procedure and the SERVICE REQUEST message, the CONTROL PLANE SERVICE REQUEST message or the REGISTRATION REQUEST message does not include UE request type IE with Request type value set to "NAS signalling connection release", the UE shall include the Uplink data status IE in the SERVICE REQUEST message, the CONTROL PLANE SERVICE REQUEST message, or in the REGISTRATION REQUEST message, indicating the PDU session(s) for which user-plane resources were not active prior to receiving a fallback indication from the lower layers and the UE has pending user data to be sent over 3GPP access, if any, and the PDU session(s) for which user-plane resources were active prior to receiving the fallback indication, if any (see subclauses 5.5.1.3 and 5.6.1 for further details). When the UE in 5GMM-CONNECTED mode over 3GPP access receives a fallback indication from lower layers, and the UE has a pending NAS procedure other than a registration procedure, a service request procedure, or a de-registration procedure, the UE shall: a) enter 5GMM-IDLE mode; b) initiate the service request procedure and include the Uplink data status IE in the SERVICE REQUEST message or the CONTROL PLANE SERVICE REQUEST message indicating the PDU session(s) for which user-plane resources were active prior to receiving the fallback indication, if any (see subclause 5.6.1 for further details); and c) upon successful service request procedure completion, proceed with any pending procedure. When the UE in 5GMM-CONNECTED mode over 3GPP access receives a fallback indication from lower layers, and the UE has no pending NAS procedure and no pending uplink user data for PDU session(s) with user-plane resources already established, and the UE was using network resources for 5G ProSe direct discovery over PC5 or 5G ProSe direct communication over PC5 (see 3GPP TS 23.304[ Proximity based Services (ProSe) in the 5G System (5GS) ] [6E]), the UE shall: a) enter 5GMM-IDLE mode; and b) initiate the service request procedure and include the Uplink data status IE in the SERVICE REQUEST message or the CONTROL PLANE SERVICE REQUEST message indicating the PDU session(s) for which user-plane resources were active prior to receiving the fallback indication, if any (see subclause 5.6.1 for further details). The UE which supports S-NSSAI location validity information, and which has received S-NSSAI location validity information from the AMF, shall include the Uplink data status IE in the REGISTRATION REQUEST message, the SERVICE REQUEST message, or the CONTROL PLANE SERVICE REQUEST message, to indicate the PDU session(s) for which user-plane resources were active prior to receiving the fallback indication, as described above, only if the UE is inside the NS-AoS with respect to the S-NSSAI which is associated with a PDU session. The cases above apply when the UE is in an allowed area or when the UE is not in a non-allowed area. When the UE: a) is in a non-allowed area or is not in an allowed area; b) is in 5GMM-CONNECTED mode over 3GPP access; c) receives a fallback indication from lower layers; and d) does not have signalling pending, the UE shall: a) enter 5GMM-IDLE mode; and b) initiate the registration procedure for mobility and periodic registration update. The UE shall not include the Uplink data status IE in the REGISTRATION REQUEST message except if the PDU session for which user-plane resources were active is an emergency PDU session, or if the UE is configured for high priority access in selected PLMN or SNPN. In the above cases when the UE receives a fallback indication from lower layers, if the UE is in non-allowed area or not in allowed area, the UE shall behave as specified in subclause 5.3.5.

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.1.2

5.4.1.2.3A Procedures related to EAP methods other than EAP-AKA' and EAP-TLS

5.4.1.2.3A.1 General This subclause applies when an EAP method: a) supporting mutual authentication; b) supporting EMSK or MSK generation; and c) other than EAP-AKA' and EAP-TLS; is used for primary authentication and key agreement in an SNPN. The UE may support acting as EAP peer of such EAP method as specified in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. The AUSF may support acting as EAP server of such EAP method as specified in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. The AAA server of the CH or the DCS may support acting as EAP server of such EAP method as specified in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]. When initiating an EAP based primary authentication and key agreement procedure using such EAP method, the network shall select an ngKSI value. If an ngKSI is contained in an initial NAS message during a 5GMM procedure, the network shall select a different ngKSI value. The network shall send the selected ngKSI value to the UE along with each EAP message. The network shall send the ABBA value as described in subclause 9.11.3.10 to the UE along with the EAP-request message and EAP-success message. When the EAP based primary authentication and key agreement procedure uses such EAP method: a) if: 1) the default UE credentials for primary authentication, if the UE is registering or registered for onboarding services in SNPN; or 2) credentials in the selected entry of the "list of subscriber data", if the UE is not registering or registered for onboarding services in SNPN; contain an indication to use MSK for derivation of KAUSF after success of primary authentication and key agreement procedure then the ME shall generate MSK as described in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24] otherwise the ME shall generate EMSK as described in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]; b) if the AUSF acts as the EAP server, the AUSF shall generate EMSK as described in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]; and c) if the AAA server of the CH or the DCS acts as the EAP server, the AAA server of the CH or the DCS shall generate MSK as described in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. When handling of an EAP-request message results into generation of MSK or EMSK, if: a) the default UE credentials for primary authentication, if the UE is registering or registered for onboarding services in SNPN; or b) credentials in the selected entry of the "list of subscriber data", if the UE is not registering or registered for onboarding services in SNPN; contain an indication to use MSK for derivation of KAUSF after success of primary authentication and key agreement procedure then the ME may generate a new KAUSF from the MSK otherwise the ME may generate a new KAUSF from the EMSK. If the ME generates a new KAUSF, the ME shall generate a new KSEAF from the new KAUSF, and the KAMF from the ABBA received together with the EAP-request message, and the new KSEAF as described in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24], and create a partial native 5G NAS security context identified by the ngKSI value received together with the EAP-request message in subclause 5.4.1.2.4.2, in the volatile memory of the ME. If the KAMF and the partial native 5G NAS security context are created, the ME shall store the KAMF in the created partial native 5G NAS security context. NOTE 1: Generation of the new KAUSF and the new KSEAF does not result into deletion of the valid KAUSF and the valid KSEAF, if any. The ME shall not use the new KAUSF in the verification of SOR transparent container and UE parameters update transparent container, if any are received, until receipt of an EAP-success message. When the AUSF acts as the EAP server and handling of an EAP response message results into generation of EMSK, the AUSF shall generate the KAUSF from the EMSK, and the KSEAF from the KAUSF as described in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. NOTE 2: When the AAA server of the CH or the DCS acts as the EAP server and handling of an EAP response message results into generation of MSK, the AAA server of the CH or the DCS provides (via the NSSAAF) the MSK and the SUPI to the AUSF. Upon reception of the MSK, the AUSF generates the KAUSF from the MSK, and the KSEAF from the KAUSF as described in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. NOTE 3: The AUSF provides the KSEAF and optionally the SUPI (unless the SEAF provided the AUSF with the SUPI before) to the SEAF as described in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. Upon reception of the KSEAF and optionally the SUPI, the SEAF generates the KAMF based on the ABBA, the KSEAF and the SUPI as described in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24], and provides ngKSI and the KAMF to the AMF. Upon reception of the ngKSI and the KAMF, the AMF creates a partial native 5G NAS security context identified by the ngKSI, and stores the KAMF in the created partial native 5G NAS security context. If the UE fails to authenticate the network, the UE shall start timer T3520 when the AUTHENTICATION RESPONSE message containing the EAP-response message is sent. Furthermore, the UE shall stop any of the retransmission timers that are running (e.g. T3510, T3517 or T3521). Upon receiving an AUTHENTICATION REQUEST message with the EAP message IE containing an EAP-request message from the network, the UE shall stop timer T3520, if running, and then process the EAP-request message as normally. If the network fails to authenticate the UE, the network handling depends upon the type of identity used by the UE in the initial NAS message, that is: - if the 5G-GUTI was used; or - if the SUCI was used. If the 5G-GUTI was used, the network should transport the EAP-failure message in the AUTHENTICATION RESULT message of the EAP result message transport procedure, initiate an identification procedure to retrieve SUCI from the UE and restart the EAP based primary authentication and key agreement procedure with the received SUCI. If the SUCI was used for identification in the initial NAS message or in a restarted EAP based primary authentication and key agreement procedure, or the network decides not to initiate the identification procedure to retrieve SUCI from the UE after an unsuccessful the EAP based primary authentication and key agreement procedure, the network should transport the EAP-failure message in an AUTHENTICATION REJECT message of the EAP result message transport procedure. If the EAP-failure message is received in an AUTHENTICATION REJECT message: a) if the AUTHENTICATION REJECT message has been successfully integrity checked by the NAS: 1) the UE shall set the update status to 5U3 ROAMING NOT ALLOWED, delete the stored 5G-GUTI, TAI list, last visited registered TAI and ngKSI. In case of SNPN, if the UE is neither registered for onboarding services in SNPN nor performing initial registration for onboarding services in SNPN and the UE does not support access to an SNPN using credentials from a credentials holder and does not support equivalent SNPNs, the entry of the "list of subscriber data" with the SNPN identity of the current SNPN shall be considered invalid until the UE is switched off or the entry is updated; In case of SNPN, if the UE is neither registered for onboarding services in SNPN nor performing initial registration for onboarding services in SNPN and the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs, or both, the UE shall consider the selected entry of the "list of subscriber data" as invalid until the UE is switched off or the entry is updated. In case of SNPN, if the UE is registered for onboarding services in SNPN or is performing initial registration for onboarding services in SNPN, the UE shall store the SNPN identity in the "permanently forbidden SNPNs" list for onboarding services, enter state 5GMM-DEREGISTERED.PLMN-SEARCH, and perform an SNPN selection or an SNPN selection for onboarding services according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]; and 2) if the UE is neither registered for onboarding services in SNPN nor performing initial registration for onboarding services in SNPN, the UE shall set the counter for "the entry for the current SNPN considered invalid for 3GPP access" events and the counter for "the entry for the current SNPN considered invalid for non-3GPP access" events in case of SNPN to UE implementation-specific maximum value. If the UE is registered for onboarding services in SNPN or performing initial registration for onboarding services in SNPN, the UE shall set the SNPN-specific attempt counter for the current SNPN to the UE implementation-specific maximum value; and b) if the AUTHENTICATION REJECT message is received without integrity protection, the UE shall start timer T3247 with a random value uniformly drawn from the range between 30 minutes and 60 minutes, if the timer is not running (see subclause 5.3.20). Additionally, if the UE is neither registered for onboarding services in SNPN nor performing initial registration for onboarding services in SNPN, the UE shall: 1) if the AUTHENTICATION REJECT message is received over 3GPP access, and the counter for "the entry for the current SNPN considered invalid for 3GPP access" events has a value less than a UE implementation-specific maximum value, proceed as specified in list item a) 1) of subclause 5.3.20.3 for the case that the 5GMM cause value received is #3; 2) if the AUTHENTICATION REJECT message is received over non-3GPP access, and the counter for "the entry for the current SNPN considered invalid for non-3GPP access" events has a value less than a UE implementation-specific maximum value, proceed as specified in list item a)-2) of subclause 5.3.20.3 for the case that the 5GMM cause value received is #3; or 3) otherwise: i) if the AUTHENTICATION REJECT message is received over 3GPP access: - the UE shall set the update status for 3GPP access to 5U3 ROAMING NOT ALLOWED, delete for 3GPP access only the stored 5G-GUTI, TAI list, last visited registered TAI and ngKSI; In case of SNPN, if the UE does not support access to an SNPN using credentials from a credentials holder and does not support equivalent SNPNs, the entry of the "list of subscriber data" with the SNPN identity of the current SNPN shall be considered invalid for 3GPP access until the UE is switched off or the entry is updated; In case of SNPN, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs, or both, the UE shall consider the selected entry of the "list of subscriber data" as invalid until the UE is switched off or the entry is updated; and - the UE shall set the counter for "the entry for the current SNPN considered invalid for 3GPP access" events to UE implementation-specific maximum value; and ii) if the AUTHENTICATION REJECT message is received over non-3GPP access: - the UE shall set the update status for non-3GPP access to 5U3 ROAMING NOT ALLOWED, delete for non-3GPP access only the stored 5G-GUTI, TAI list, last visited registered TAI and ngKSI. The entry of the "list of subscriber data" with the SNPN identity of the current SNPN shall be considered invalid for non-3GPP access until the UE is switched off or the entry is updated; and - the UE shall set the counter for "the entry for the current SNPN considered invalid for non-3GPP access" events to UE implementation-specific maximum value. If the UE is registered for onboarding services in SNPN or performing initial registration for onboarding services in SNPN, the UE shall: 1) if the SNPN-specific attempt counter for the SNPN sending the AUTHENTICATION REJECT message has a value less than a UE implementation-specific maximum value, increment the SNPN-specific attempt counter for the SNPN; or 2) otherwise, the UE shall set the update status to 5U3.ROAMING NOT ALLOWED, delete the stored 5G-GUTI, TAI list, last visited registered TAI, and ngKSI, store the SNPN identity in the "permanently forbidden SNPNs" list for onboarding services, enter state 5GMM-DEREGISTERED.PLMN-SEARCH, and perform an SNPN selection or an SNPN selection for onboarding services according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]. If the AUTHENTICATION REJECT message is received by the UE, the UE shall abort any 5GMM signalling procedure, stop any of the timers T3510, T3517, T3519 or T3521 (if they were running), enter state 5GMM-DEREGISTERED and delete any stored SUCI. Upon receiving an EAP-success message, the ME shall: a) delete the valid KAUSF and the valid KSEAF, if any; b) if the ME has not generated a new KAUSF and a new KSEAF and has not created a partial native 5G NAS security context when handling the EAP-request message which resulted into generation of EMSK as described above: 1) if: i) the default UE credentials for primary authentication, if the UE is registering or registered for onboarding services in SNPN; or ii) credentials in the selected entry of the "list of subscriber data", if the UE is not registering or registered for onboarding services in SNPN; contain an indication to use MSK for derivation of KAUSF after success of primary authentication and key agreement procedure then generate a new KAUSF from the MSK otherwise generate a new KAUSF from the EMSK; 2) generate a new KSEAF from the new KAUSF, and the KAMF from the ABBA that was received with the EAP-success message, and the KSEAF as described in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]; 3) create a partial native 5G NAS security context identified by the ngKSI value in the volatile memory of the ME; and 4) store the KAMF in the created partial native 5G NAS security context; and c) consider the new KAUSF to be the valid KAUSF, and the new KSEAF to be the valid KSEAF, reset the SOR counter and the UE parameter update counter to zero, store the valid KAUSF, the valid KSEAF, the SOR counter and the UE parameter update counter as specified in annex C, and use the valid KAUSF in the verification of SOR transparent container and UE parameters update transparent container, if any are received. The UE shall consider the procedure complete. Upon receiving an EAP-failure message, the UE shall delete the partial native 5G NAS security context and shall delete the new KAUSF and the new KSEAF, if any were created when handling the EAP-request message which resulted into generation of EMSK or MSK as described above. The UE shall consider the procedure complete. 5.4.1.2.3A.2 EAP-TTLS with two phases of authentication The UE may support acting as EAP peer of EAP-TTLS with two phases of authentication as specified in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24] and acting as peer of a legacy authentication protocol as specified in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. The AUSF may support acting as EAP server of EAP-TTLS with two phases of authentication as specified in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. The AAA server of the CH or the DCS may support acting a server of a legacy authentication protocol as specified in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. When EAP-TTLS with two phases of authentication as specified in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24] is used for primary authentication and key agreement in an SNPN: a) requirements in subclause 5.4.1.2.3A.1 shall apply in addition to requirements specified in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24] annex U; b) indication to use MSK for derivation of KAUSF after success of primary authentication and key agreement procedure is not included in: 1) the default UE credentials for primary authentication, if the UE is registering or registered for onboarding services in SNPN; or 2) credentials in the selected entry of the "list of subscriber data", if the UE is not registering or registered for onboarding services in SNPN; and c) the SUPI of the UE is in the form of a SUPI with the SUPI format "network specific identifier" containing a network-specific identifier. NOTE: Support of EAP-TTLS with two phases of authentication is based on the informative requirements as specified in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24].

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.1.2.3A

8.13.3.2.2 Minimum Requirement Dual-Layer Spatial Multiplexing 2 Tx Antenna Port for TDD PCell

The purpose of these tests is to verify the closed loop rank-two performance with wideband and frequency selective precoding. For TDD FDD CA with TDD PCell and 2DL CCs, the requirements are specified in Table 8.13.3.2.2-4 based on single carrier requirement specified in Table 8.13.3.2.2-2 and Table 8.13.3.2.2-3, with the addition of the parameters in Table 8.13.3.2.2-1 and the downlink physical channel setup according to Annex C.3.2. For TDD FDD CA with TDD PCell and 3DL CCs, the requirements are specified in Table 8.13.3.2.2-5 based on single carrier requirement specified in Table 8.13.3.2.2-2 and Table 8.13.3.2.2-3, with the addition of the parameters in Table 8.13.3.2.2-1 and the downlink physical channel setup according to Annex C.3.2. For TDD FDD CA with TDD PCell and 4DL CCs, the requirements are specified in Table 8.13.3.2.2-6 based on single carrier requirement specified in Table 8.13.3.2.2-2 and Table 8.13.3.2.2-3, with the addition of the parameters in Table 8.13.3.2.2-1 and the downlink physical channel setup according to Annex C.3.2. For TDD FDD CA with TDD PCell and 5DL CCs, the requirements are specified in Table 8.13.3.2.2-7 based on single carrier requirement specified in Table 8.13.3.2.2-2 and Table 8.13.3.2.2-3, with the addition of the parameters in Table 8.13.3.2.2-1 and the downlink physical channel setup according to Annex C.3.2. The test coverage for different number of component carriers is defined in 8.1.2.4. Table 8.13.3.2.2-1: Test Parameters for Multi-Layer Spatial Multiplexing (FRC) for CA Table 8.13.3.2.2-2: Single carrier performance with different bandwidths for multiple CA configurations for FDD SCell (FRC) Table 8.13.3.2.2-3: Single carrier performance with different bandwidths for multiple CA configurations for TDD PCell and SCell (FRC) Table 8.13.3.2.2-4: Minimum performance for multiple CA configurations with 2DL CCs (FRC) Table 8.13.3.2.2-5: Minimum performance for multiple CA configurations with 3DL CCs (FRC) Table 8.13.3.2.2-6: Minimum performance for multiple CA configurations with 4DL CCs (FRC) Table 8.13.3.2.2-7: Minimum performance for multiple CA configurations with 5DL CCs (FRC)

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.13.3.2.2

4.8.2 UE using satellite E-UTRAN access

In WB-S1 mode via satellite E-UTRAN access, the UE shall apply the value of the applicable NAS timer indicated in tables 10.2.1 and indicated in table 10.3.1 for WB-S1/CE mode. The NAS timer value obtained is used as described in the appropriate procedure clause of this specification. The NAS timer value shall be calculated at start of a NAS procedure and shall not be re-calculated until the NAS procedure is completed, restarted or aborted. When an MME that supports WB-S1 mode performs NAS signalling with a UE via satellite E-UTRAN access, the MME shall calculate the value of the applicable NAS timer indicated in tables 10.2.2 and indicated in table 10.3.2 for WB-S1/CE mode. The NAS timer value obtained is used as described in the appropriate procedure clause of this specification. The NAS timer value shall be calculated at start of a NAS procedure and shall not be re-calculated until the NAS procedure is completed, restarted or aborted. NOTE: When using satellite E-UTRAN access, the restriction on use of enhanced coverage indication from the network is not considered when applicable NAS timers are determined.

3GPP TS 24.301

Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3

CT WG1

3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network

4.8.2

8.15 Bearer Quality of Service (Bearer QoS)

Bearer Quality of Service (Bearer QoS) is transferred via GTP tunnels. The sending entity copies the value part of the Bearer l QoS into the Value field of the Bearer QoS IE. Figure 8.15-1: Bearer Quality of Service (Bearer QoS) Octet 5 represents the Allocation/Retention Priority (ARP) parameter. 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 ARP octet 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. Octet 6 contains the "QCI" value, as specified in 3GPP TS 23.203[ Policy and charging control architecture ] [48]. The UL/DL MBR and GBR fields are encoded as kilobits per second (1 kbps = 1000 bps) in binary value. The UL/DL MBR and GBR fields may require converting values in bits per second to kilobits per second when the UL/DL MBR and GBR values are received from an interface other than GTPv2 interface. If such conversions result in fractions, then the value of UL/DL MBR and GBR fields shall be rounded upwards. For non-GBR bearers, both the UL/DL MBR and GBR should be set to zero. The range of QCI, Maximum bit rate for uplink, Maximum bit rate for downlink, Guaranteed bit rate for uplink and Guaranteed bit rate for downlink are specified in 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [10]. NOTE: The encoding in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [23] and 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [10] is different from the encoding within this specification.

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.15

8.2.1.4.1C Minimum Requirement Single-Layer Spatial Multiplexing 2 Tx Antenna Ports (demodulation subframe overlaps with aggressor cell ABS and CRS assistance information are configured)

The requirements are specified in Table 8.2.1.4.1C-2, with the addition of parameters in Table 8.2.1.4.1C-1. The purpose is to verify the closed loop rank-one performance with wideband precoding if the PDSCH transmission in the serving cell takes place in subframes that overlap with ABS [9] of the aggressor cell with CRS assistance information. In Table 8.2.1.4.1C-1, Cell 1 is the serving cell, and Cell 2 and Cell 3 are the aggressor cells. The downlink physical channel setup for Cell 1 is according to Annex C.3.2 and for Cell 2 and Cell 3 is according to Annex C.3.3, respectively. The CRS assistance information [7] includes Cell 2 and Cell 3. Table 8.2.1.4.1C-1: Test Parameters for Single-Layer Spatial Multiplexing (FRC) – Non-MBSFN ABS Table 8.2.1.4.1C-2: Minimum Performance Single-Layer Spatial Multiplexing (FRC)– Non-MBSFN ABS

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.2.1.4.1C

– RRCSetup

The RRCSetup message is used to establish SRB1. Signalling radio bearer: SRB0 RLC-SAP: TM Logical channel: CCCH Direction: Network to UE RRCSetup message -- ASN1START -- TAG-RRCSETUP-START RRCSetup ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { rrcSetup RRCSetup-IEs, criticalExtensionsFuture SEQUENCE {} } } RRCSetup-IEs ::= SEQUENCE { radioBearerConfig RadioBearerConfig, masterCellGroup OCTET STRING (CONTAINING CellGroupConfig), lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension RRCSetup-v1700-IEs OPTIONAL } RRCSetup-v1700-IEs ::= SEQUENCE { sl-ConfigDedicatedNR-r17 SL-ConfigDedicatedNR-r16 OPTIONAL, -- Cond L2RemoteUE sl-L2RemoteUE-Config-r17 SL-L2RemoteUE-Config-r17 OPTIONAL, -- Cond L2RemoteUE nonCriticalExtension SEQUENCE {} OPTIONAL } -- TAG-RRCSETUP-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

6.1.3.3.3.3 Handling of network rejection due to SM cause other than SM cause #26

If the SM cause value is not #26 "insufficient resources" and the Back-off timer value IE is included, the MS takes different actions depending on the timer value received in the Back-off timer value IE (if the MS is an MS configured to use AC11 – 15 in selected PLMN, exceptions are specified in subclause 6.1.3.13): 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 PDP context modification procedure and PLMN and combination and not send another MODIFY PDP CONTEXT REQUEST message with exception of those identified in subclause 6.1.3.3, in the PLMN for the same until the back-off timer expires, the MS is switched off or the /USIM is removed; ii) if the timer value indicates that this timer is deactivated, the MS shall not send another MODIFY PDP CONTEXT REQUEST message with exception of those identified in subclause 6.1.3.3, in the PLMN for the same until the MS is switched off or the /USIM is removed; or iii) if the timer value indicates that this timer is zero, the MS may send an MODIFY PDP CONTEXT REQUEST message in the PLMN for the same . 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 #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 #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 PDP context modification 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 MODIFY PDP CONTEXT REQUEST message with exception of those identified in subclause 6.1.3.3, in the PLMN for the same APN. If the back-off timer is started upon receipt of a MODIFY PDP CONTEXT REQUEST 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 a MODIFY PDP CONTEXT REQUEST message for the same in the new PLMN, if the back-off timer is not running and is not deactivated for the PDP context modification procedure and the combination of new PLMN and APN; Furthermore as an implementation option, for the SM cause values #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 MODIFY PDP 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 does not include the Re-attempt indicator IE to indicate whether re-attempt in S1 mode is allowed, or the MS ignores the Re-attempt indicator IE, e.g. because the Back-off timer value IE is not included, then: - 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 apply the configured SM_RetryAtRATChange 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, to determine whether the MS may attempt a bearer resource modification procedure for the same PLMN and APN combination in S1 mode; and - 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 NAS configuration MO as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [135] is not available and the value for inter-system change is not configured in the USIM file NASCONFIG, then the MS behaviour regarding a bearer resource modification procedure for the same PLMN and APN combination in S1 mode is unspecified; and iii) if the network includes the Re-attempt indicator IE indicating 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 PDP context modification procedure with the value provided by the network, or deactivate the respective back-off timer as follows: - If the Re-attempt indicator IE additionally indicates that re-attempt in S1 mode is allowed, the MS shall start or deactivate the back-off timer for A/Gb and Iu mode only; and - otherwise the MS shall start or deactivate the back-off timer for A/Gb, Iu, and S1 mode. If the back-off timer for a PLMN and APN combination was started or deactivated in S1 mode upon receipt of a BEARER RESOURCE MODIFICATION REJECT message (see 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120]) and the network indicated that re-attempt in A/Gb or Iu mode is allowed, then this back-off timer does not prevent the MS from sending a MODIFY PDP CONTEXT REQUEST message in this PLMN for the same APN in A/Gb or Iu mode. If the network indicated that re-attempt in A/Gb or Iu mode is not allowed, the MS shall not send any MODIFY PDP CONTEXT REQUEST message in this PLMN for the same APN in A/Gb or Iu mode until the timer expires, the MS is switched off or the USIM is removed. 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.3.3.3

6.2.2 IP address allocation via NAS signalling

The UE shall set the PDN type IE in the PDN CONNECTIVITY REQUEST message, based on its IP stack configuration if it requests IP connectivity (e.g. the per APN settings specified in 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10]) as follows: a)- A UE, which is IPv6 and IPv4 capable and - has not been allocated an IP address for this APN, shall set the PDN type IE to IPv4v6. - has been allocated an IPv4 address for this APN and received the ESM cause #52 "single address bearers only allowed", and is requesting an IPv6 address, shall set the PDN type IE to IPv6. - has been allocated an IPv6 address for this APN and received the ESM cause #52 "single address bearers only allowed", and is requesting an IPv4 address, shall set the PDN type IE to IPv4. b) A UE, which is only IPv4 capable, shall set the PDN type IE to IPv4. c) A UE, which is only IPv6 capable, shall set the PDN type IE to IPv6. d) When the IP version capability of the UE is unknown in the UE (as in the case when the MT and TE are separated and the capability of the TE is not known in the MT), the UE shall set the PDN type IE to IPv4v6. If the UE wants to use DHCPv4 for IPv4 address assignment, it shall indicate that to the network within the Protocol configuration options IE in the PDN CONNECTIVITY REQUEST. If the UE wants to get PDN connectivity for non-IP, the UE shall set the PDN type IE in the PDN CONNECTIVITY REQUEST message to "non IP". If the UE wants to get PDN connectivity for Ethernet, the UE shall set the PDN type IE in the PDN CONNECTIVITY REQUEST message to "Ethernet". On receipt of the PDN CONNECTIVITY REQUEST message sent by the UE, the network when allocating an IP address shall take into account the PDN type IE, the operator policies of the home and visited network, and the user's subscription data and: - if the UE requests for PDN type IPv4v6, but the subscription is limited to IPv4 only or IPv6 only for the requested APN, the network shall override the PDN type requested by the UE to be limited to a single address PDN type (IPv4 or IPv6). In the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message sent to the UE, the network shall set the PDN type value to either "IPv4" or "IPv6" and the ESM cause value to #50 "PDN type IPv4 only allowed", or #51 "PDN type IPv6 only allowed", respectively. The UE shall not subsequently initiate another UE requested PDN connectivity procedure to the same APN to obtain a PDN type different from the one allowed by the network until: a) the UE is registered to a new PLMN; b) void; c) the UE is switched off; or d) the USIM is removed. NOTE 1: Request to send another PDN CONNECTIVITY REQUEST message with a specific PDN type has to come from upper layers. - if the UE requests PDN type IPv4v6, but the PDN GW configuration dictates the use of IPv4 addressing only or IPv6 addressing only for this APN, the network shall override the PDN type requested by the UE to limit it to a single address PDN type (IPv4 or IPv6). In the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message sent to the UE, the network shall set the PDN type value to either "IPv4" or "IPv6" and the ESM cause value to #50 "PDN type IPv4 only allowed", or #51 "PDN type IPv6 only allowed", respectively. The UE shall not subsequently initiate another UE requested PDN connectivity procedure to the same APN to obtain a PDN type different from the one allowed by the network until: a) the UE is registered to a new PLMN; b) void; c) the UE is switched off; or d) the USIM is removed. NOTE 2: Request to send another PDN CONNECTIVITY REQUEST message with a specific PDN type has to come from upper layers. - if the UE requests PDN type IPv4v6, but the operator uses single addressing per bearer, e.g. due to interworking with nodes of earlier releases, the network shall override the PDN type requested by the UE to a single IP version only. In the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message sent to the UE, the network shall set the PDN type value to either "IPv4" or "IPv6" and the ESM cause value to #52 "single address bearers only allowed". The UE should subsequently request another PDN connection for the other IP version using the UE requested PDN connectivity procedure to the same APN with a single address PDN type (IPv4 or IPv6) other than the one already activated; NOTE 3: If the MT and TE are separated, the UE might not be able to use ESM cause #52 "single address bearers only allowed" as a trigger for activating a second single-IP-stack EPS bearer context. - if the network sets the PDN type to IPv4 or IPv4v6, the network shall include an IPv4 address in the PDN address information. In this case, if the IPv4 address is to be configured using DHCPv4, the network shall set the IPv4 address to 0.0.0.0; and - if the network sets the PDN type to IPv6 or IPv4v6, the network shall include the interface identifier that the UE shall use for the link local address in the PDN address information. The network shall include the PDN type and the PDN address information within the PDN address IE in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message sent to the UE.

3GPP TS 24.301

Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3

CT WG1

3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network

6.2.2

6.10.3.2 Derivation of keys

The UE and MN shall derive the security key KSN of the SN as defined in Annex A.16 of the present document. The SN RRC and UP keys shall be derived from the KSN both at the SN and the UE using the function given in Annex A.7 of TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [10] if the SN is a ng-eNB or using the function given in Annex A.8 of the present specification if the SN is a gNB. Once all the SN RRC and UP keys have been derived from the KSN, the SN and UE may delete the KSN.

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

6.10.3.2

5.1.2.2 eNodeB - S-GW

Legend: - GPRS Tunnelling Protocol for the user plane (GTP-U): This protocol tunnels user data between eNodeB and S-GW. - User Datagram Protocol (UDP): This protocol transfers user data. UDP is defined in RFC 768 [26]. Figure 5.1.2.2-1: User Plane for eNodeB – S-GW NOTE: Refer to TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5] for the corresponding user plane for the HeNB Subsystem - S-GW.

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.1.2.2

9.5 Reporting of Rank Indicator (RI)

The purpose of this test is to verify that the reported rank indicator accurately represents the channel rank. The accuracy of RI (CQI) reporting is determined by the relative increase of the throughput obtained when transmitting based on the reported rank compared to the case for which a fixed rank is used for transmission. Transmission mode 4 is used with the specified CodebookSubSetRestriction in section 9.5.1, transmission mode 9 is used with the specified CodebookSubSetRestriction in section 9.5.2 and transmission mode 3 is used with the specified CodebookSubSetRestriction in section 9.5.3, and transmission mode 10 is used with the specified CodebookSubSetRestriction in section 9.5.5. For fixed rank 1 transmission in sections 9.5.1, 9.5.2 and 9.5.5, the RI and PMI reporting is restricted to two single-layer precoders, For fixed rank 2 transmission in sections 9.5.1, 9.5.2 and 9.5.5, the RI and PMI reporting is restricted to one two-layer precoder, For follow RI transmission in sections 9.5.1 and 9.5.2, the RI and PMI reporting is restricted to select the union of these precoders. Channels with low and high correlation are used to ensure that RI reporting reflects the channel condition. For fixed rank 1 transmission in section 9.5.3, the RI reporting is restricted to single-layer, for fixed rank 2 transmission in section 9.5.3, the RI reporting is restricted to two-layers. For follow RI transmission in section 9.5.3, the RI reporting is either one or two layers.

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.5

5.1.2 Scenario

A UAS is made up of a UAV and a UAV controller which is a physical device used by a UAV operator. One UAV controller may command and control one UAV or a fleet of UAVs. The UAV and the UAV controller both have certain credentials and identities which are factory set, related to the status of the UAS or UAV operator, or related to the operating scenario. This includes unique 3GPP credentials and identities. The communication between the UAV controller and UAV is done via 3GPP communication service offered by MNO. Detection of UAS communication is possible in an MNO network and if UE subscription does not allow such communication it is rejected. Permission for a UE to function as an aerial UE in the 3GPP network can be identified via subscription information. The network may use this information to perform the necessary control and apply relevant functions. Based on this subscription information uplink power adjustment and frequency band alteration can be applied in order UAS communication not to have impact on other types of communication. In addition to UAS subscription information UE can indicate a radio capability to the network which may be used to identify a UE with relevant functions for UAS communication in a 3GPP network. In this scenario, the UAS has been switched on in order for the UAV operator to fly the UAV using the UAV controller. The UAV operator pairs the UAV and the UAV controller for UAS operation through some mechanism. The UAV passes UAV data to onboard 3GPP UE. The UE authenticates with MNO. In parallel to the attach request, the UE sends the UAV data & 3GPP identifiers to the Unmanned Aerial System Traffic Management (UTM), requesting initial permission to attach to the network to fly and using certain services provided by UTM. Subject to national regulatory UTM requirements, a UAS may need to go through several authentication and authorization processes before a UAS can be fully operated, e.g. after finishing the initial authentication for establish connection with the UTM, a UAV may need to go through additional application level authentication to activate some UTM services, such as flight monitoring or collision avoidance service. Therefore, a UAS may need to provide different UAS identity data according to the level of the authorization and authentication process required by the UAS. If the request towards UTM is coming from UE without subscription information for drone communication, then the request shall be rejected. The same operation is done by the UAV controller using its own credentials and identifiers. During the initial authorization procedures, the MNO and UTM need to be able to associate the UAV and the UAV controller as a UAS. If the UTM rejects a request for some reasons, e.g. incorrect identities or credentials, or UAS element(s) are operating in the area which is prohibited, the MNO rejects the attach request of the UAV and/or UAV controller of the UAS. If both registration requests are accepted for the UAS, the UAV operator can use the UAV controller to fly the UAV by transmitting commands from the UAV controller to the UAV via 3GPP network.

3GPP TS 22.825

Study on Remote Identification of Unmanned Aerial Systems (UAS)

SA WG1

3GPP Series : 22 , Service aspects ("stage 1")

5.1.2

10.5.5.34 User Plane integrity indicator

The purpose of the User Plane integrity indicator information element is to indicate to the MS that it shall integrity protect user plane data in LLC layer. The User Plane integrity indicator is allocated by the network and sent with the ATTACH ACCEPT message or ROUTING AREA UPDATE ACCEPT message to the mobile station. The User Plane integrity indicator information element is coded as shown in figure 10.5.5.34-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.5.34-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . In A/Gb mode, in the case when a UMTS security context is established and if the MS supports integrity protection, , the purpose of the User Plane integrity indicator information element is to request the MS to start integrity protection of user plane data in LLC layer. The User Plane integrity indicator is a type 1 information element. Figure 10.5.5.34-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] User Plane integrity indicator information element Table 10.5.5.34-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : User Plane integrity indicator 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.34

17.7 Gmb specific AVPs 17.7.0 General

Table 10 describes the Gmb specific Diameter AVPs. The Vendor-Id header of all Gmb specific AVPs defined in the present specification shall be set to 3GPP (10415). The Gmb specific AVPs require to be supported to be compliant to the present specification. All AVPs in table 10 are mandatory within Gmb interface unless otherwise stated. Table 10: Gmb specific AVPs Table 11 lists the set of Diameter AVPs that are not Gmb specific, but are reused from other Diameter applications by the Gmb interface. A reference is done to the specifications where the AVPs are specified. This set of AVPs requires to be supported to be compliant to the present specification. Table 11: Gmb reused AVPs from other Diameter applications. NOTE: Diameter Base AVPs are not listed as support of them is mandated by IETF RFC 6733 [111].

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

17.7

9.3.19.1 Release complete (network to mobile station direction)

This message is sent from the network to the mobile station to indicate that the network has released the transaction identifier and that the mobile station shall release the transaction identifier. See table 9.69/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Message type: RELEASE COMPLETE Significance: local (note) Direction: network to mobile station direction Table 9.69/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : RELEASE COMPLETE message content (network to mobile station direction) NOTE: This message has local significance; however, it may carry information of global significance when used as the first call clearing 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

9.3.19.1

4.10 Support of MUSIM features

A network and a MUSIM UE may support one or more of the MUSIM features (i.e. the NAS signalling connection release, the paging indication for voice services, the reject paging request, the paging restriction and the paging timing collision control). If MUSIM UE supports one or more MUSIM features, the UE indicates support of one or more MUSIM features during the attach procedure and the normal tracking area updating procedure. If the UE has indicated support of the NAS signalling connection release or the reject paging request or both and the UE supports the paging restriction, the UE indicates support of the paging restriction. If the UE indicates support of one or more MUSIM features and the network decides to accept one or more MUSIM features, the network indicates the support of one or more MUSIM features during the attach procedure and the normal tracking area updating procedure. The network only indicates the support of the paging restriction together with the support of either NAS signalling connection release or the reject paging request. The network does not indicate support for any MUSIM feature to the UE during the attach for emergency bearer services. If a UE stops fulfilling the condition to be considered a MUSIM UE as defined in subclause 3.1, and the UE has negotiated support of one or more MUSIM features, then the UE shall initiate a normal tracking area update procedure to indicate that all the MUSIM features are not supported as specified in clause 5.5.3.2. A MUSIM UE operating in NB-S1 mode or in WB-S1 mode CE mode B does not indicate the support for paging indication for voice services during the attach procedure or the normal tracking area update procedure towards the network.

3GPP TS 24.301

Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3

CT WG1

3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network

4.10

4.5.1.8 MM connection establishment due to SRVCC or vSRVCC handover

An MM connection can be established locally in the MS due to an SRVCC or vSRVCC handover (see 3GPP TS 23.216[ Single Radio Voice Call Continuity (SRVCC); Stage 2 ] [126]), i.e. without dedicated MM signalling. That is the case when the MS has: - a voice media stream carried over the PS domain that is handed over to the CS domain in A/Gb mode or Iu mode via SRVCC; - a voice media stream and a video media stream of a single session carried over the PS domain in S1 mode that is handed over to the CS domain in Iu mode via vSRVCC; - a voice media stream and a video media stream of a single session carried over the PS domain in S1 mode but only the voice media stream is handed over to the CS domain in A/Gb mode via SRVCC; or - a voice media stream carried over the PS domain in N1 mode that is handed over to the CS domain in Iu mode via 5G-SRVCC handover from NG-RAN to UTRAN. An MS in MM state MM IDLE shall establish the MM connection locally when it receives an indication from lower layers that either a voice only SRVCC handover or a voice and video SRVCC handover was completed successfully. After completing MM connection establishment, the MM layer shall indicate "MM connection establishment due to SRVCC handover" or "MM connection establishment due to vSRVCC handover" to the upper layer and shall enter state MM CONNECTION ACTIVE.

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.5.1.8

8.3.8.4 Re-attempt indicator

The network may include this IE only if it includes the Back-off timer value IE and the 5GSM cause value is not #26 "insufficient resources", #37 "5GS QoS not accepted", #44 "Semantic errors in packet filter(s)", #45 "Syntactical error in packet filter(s)", #46 "out of LADN service area", #59 "unsupported 5QI value", #67 "insufficient resources for specific slice and DNN", #69 "insufficient resources for specific slice", #83 "Semantic error in the QoS operation", or #84 "Syntactical error in the QoS operation".

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.8.4

– N3C-IndirectPathConfigRelay

The IE N3C-IndirectPathConfigRelay indicates the N3C indirect path related configuration used by N3C relay UE in MP. N3C-IndirectPathConfigRelay information element -- ASN1START -- TAG-N3C-INDIRECTPATHCONFIGRELAY-START N3C-IndirectPathConfigRelay-r18 ::= SEQUENCE { n3c-MappingToReleaseList-r18 SEQUENCE (SIZE (1..maxLC-ID)) OF SL-RemoteUE-RB-Identity-r17 OPTIONAL, -- Need N n3c-MappingToAddModList-r18 SEQUENCE (SIZE (1..maxLC-ID)) OF N3C-MappingToAddMod-r18 OPTIONAL, -- Need N ... } N3C-MappingToAddMod-r18 ::= SEQUENCE { n3c-RemoteUE-RB-Identity-r18 SL-RemoteUE-RB-Identity-r17, n3c-RLC-ChannelUu-r18 Uu-RelayRLC-ChannelID-r17 OPTIONAL, -- Need M ... } -- TAG-N3C-INDIRECTPATHCONFIGRELAY-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

13b.2 BM-SC interworking model of MBMS GW

The control plane and user plane protocol stacks of the MBMS GW for interworking with BM-SC are illustrated in Figure 16j , Figure 16k and Figure 16l. The figures include the following protocols: - The "Diameter" SGmb application, as specified in clause 20. - The Control part of the Evolved GPRS Tunnelling Protocol for EPS, GTPv2-C, as specified in 3GPP TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [81]. - The User Datagram Protocol,UDP, as specified in IETF RFC 768 [15]. - The Transmission Control Protocol, TCP, as specified in IETF RFC 793 [18] - The Stream Control Transmission Protocol, SCTP, as specified in IETF RFC 4960 [109]. - The Packet Data Convergence Protocol, PDCP, as specified in 3GPP TS 25.323[ None ] [107]. - The MBMS synchronisation protocol, SYNC, as specified in 3GPP TS 25.446[ MBMS synchronisation protocol (SYNC) ] [106]. - The Internet Protocol, IP. - L1 and L2 transport protocols for IP (various options exist). Figure 16j: The control plane protocol stacks of MBMS GW for interworking with BM-SC Figure 16k: The user plane protocol stacks of MBMS GW for interworking with BM-SC for multicast Figure 16l: The user plane protocol stacks of MBMS GW for interworking with BM-SC for broadcast A BM-SC sends user plane data to an MBMS GW either by IP unicast (default), or by IP multicasting. Through the control plane communication a BM-SC provides an MBMS GW with necessary data, so that MBMS GW could forward the user plane data downlink either by multicast (default) or by unicast. PDCP is not used when the MBMS service is broadcasted in the E-UTRAN, refer to 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [94].

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

13b.2

4.15.3.2.8 Information flow for downlink data delivery status with UPF buffering

The procedure is used if the SMF requests the UPF to buffer packets. The procedure describes a mechanism for the Application Function to subscribe to notifications about downlink data delivery status. The downlink data delivery status notifications relates to high latency communication, see also clauses 4.24.2 and 4.2.3.3. Cancelling is done by sending Nnef_EventExposure_Unsubscribe request identifying the subscription to cancel with Subscription Correlation ID. Steps 2 to 5 are not applicable in the cancellation case. Figure 4.15.3.2.8-1: Information flow for downlink data delivery status with UPF buffering 1. AF interacts with NEF to subscribe DDD status event in SMF as described in steps 0-6 of clause 4.15.3.2.5. In the case of subscription cancelling and SMF having interacted with the PCF during event subscription, the SMF reports to the PCF the unsubscribe of the DDD status event. The PCF updates or removes the PCC rule and this triggers the SMF to update or remove the corresponding PDR in the UPF. In case of home-routed PDU Session, the SMF unsubscribes the DDD status event from the V-SMF which in turn updates the N4 information (deactivating the notifications) in the V-UPF. In case of PDU Session with I-SMF, the SMF provides updated N4 information (deactivating the notifications) to the I-SMF which in turn updates the I-UPF. 2. If the UPF is configured to apply extended buffering, step 2 is executed immediately after step 1. Otherwise, step 2 is executed when the SMF is informed that the UE is unreachable via a Namf_Communication_N1N2MessageTransfer service operation as described in clause 4.2.3 and the SMF then also updates the PDR(s) for flows requiring extended buffering to requests the UPF to buffer downlink packets. If the DDD status event with traffic descriptor has been received in the SMF in step 1, if extended DL Data buffering in the UPF applies, the SMF checks whether an installed PDR for the Traffic Descriptor exists and if so, requests the UPF to provide the requested type(s) of notifications. If PCC is not used and there is no installed PDR with the exact same traffic descriptor, the SMF copies the installed PDR that would have previously matched the incoming traffic described by the traffic descriptor, but provides that traffic descriptor, a higher priority and the requested type(s) of notifications. If PCC is used and if the "DDD Status event subscription with Traffic Descriptor" PCRT is set as defined in clause 6.1.3.5 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20], the SMF interacts with the PCF and forwards the traffic descriptor before contacting the UPF; the PCF then updates an existing PCC rule or provides a new PCC rule taking into consideration the traffic descriptor for the subscribed DDD status event. NOTE: If a new PCC rule is provided by the PCF for the DDD status event detection, the PCF populates the PCC rules as defined in clause 6.1.3.5 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. In the case of home-routed PDU Session, the V-SMF generates the N4 information (activating the notifications) for the V-UPF based on local configuration. In the case of PDU Session with I-SMF, the SMF provides N4 information (activating the notifications) to the I-SMF based on local policy or the "DDD Status event subscription with Traffic Descriptor" PCRT from PCF. The I-SMF updates the I-UPF with this N4 information. For home-routed PDU Session or PDU Session with I-SMF, steps 3-4 below are performed by V-SMF/V-UPF or I-SMF/I-UPF. 3. The UPF reports when there is buffered or discarded traffic matching the received PDR to the SMF. The SMF detects that previously buffered packets can be transmitted by the fact that the related PDU session becomes ACTIVE. 4. The SMF sends the Nsmf_EventExposure_Notify with Downlink Delivery Status event message to NEF. 5. The NEF sends Nnef_EventExposure_Notify with Downlink Delivery Status event message to AF.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

3GPP Series : 23 , Technical realization ("stage 2")

4.15.3.2.8

5.2.18.2.3 Nucmf_Provisioning_Update service operation

Service operation name: Nucmf_Provisioning_Update Description: The consumer updates the list of IMEI/TAC values a UCMF dictionary entry (or a list of entries) applies to for a Manufacturer-assigned UE Radio Capability ID. For each UE Radio Capability ID provided, (a list of) UE model(s) IMEI/TAC value(s) to be added or removed to the related UCMF entry is provided. Inputs, Required: Update Type (one of "Add IMEI/TAC Values" or "Remove IMEI/TAC Values") and: - If Update Type is "Add IMEI/TAC Values", the (list of) UE Radio Capability ID(s) of the UCMF dictionary entry(ies) to be updated and the related additional (list of) IMEI/TAC(s); or - If Update Type is "Remove IMEI/TAC Values", the (list of) UE Radio Capability ID(s) of the UCMF dictionary entry(ies) to be updated and the related (list of) IMEI/TAC(s) to be removed. Inputs, Optional: None. Outputs, Required: None. Outputs, Optional: None.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

3GPP Series : 23 , Technical realization ("stage 2")

5.2.18.2.3

10.5.1.5 Mobile Station Classmark 1

The purpose of the Mobile Station Classmark 1 information element is to provide the network with information concerning aspects of high priority of the mobile station equipment. This affects the manner in which the network handles the operation of the mobile station. The Mobile Station Classmark information indicates general mobile station characteristics and it shall therefore, except for fields explicitly indicated, be independent of the frequency band of the channel it is sent on. The Mobile Station Classmark 1 information element is coded as shown in figure 10.5.5/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.5/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The Mobile Station Classmark 1 is a type 3 information element with 2 octets length. Figure 10.5.5/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Mobile Station Classmark 1 information element Table 10.5.5/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Mobile Station Classmark 1 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.1.5

6.22.1 Description

Depending on operator's policies, deployment scenarios, subscriber profiles, and available services, different criterion will be used in determining which access attempt should be allowed or blocked when congestion occurs in the 5G System. These different criteria for access control are associated with Access Identities and Access Categories. The 5G system will provide a single unified access control where operators control accesses based on these two. In unified access control, each access attempt is categorized into one or more of the Access Identities and one of the Access Categories. Based on the access control information applicable for the corresponding Access Identity and Access Category of the access attempt, the UE performs a test whether the actual access attempt can be made or not. The unified access control supports extensibility to allow inclusion of additional standardized Access Identities and Access Categories and supports flexibility to allow operators to define operator-defined Access Categories using their own criterion (e.g. network slicing, application, and application server). NOTE: Clauses 4.1 through 4.4a of TS 22.011[ Service accessibility ] are obsolete and replaced by clause 6.22.2 of this specification. However, when a UE is configured for EAB according to TS 22.011[ Service accessibility ] , the UE is also configured for delay tolerant service for 5G system.

3GPP TS 22.261

Service requirements for the 5G system

SA WG1

3GPP Series : 22 , Service aspects ("stage 1")

6.22.1

16.10.5.4 Reception of MBS Multicast data

For multicast service, gNB may deliver MBS multicast data packets using the following methods: - PTP Transmission: gNB individually delivers separate copies of MBS data packets to each UEs independently, i.e., gNB uses UE-specific PDCCH with CRC scrambled by UE-specific RNTI (e.g., C-RNTI) to schedule UE-specific PDSCH which is scrambled with the same UE-specific RNTI. - PTM Transmission: gNB delivers a single copy of MBS data packets to a set of UEs, e.g., gNB uses group-common PDCCH with CRC scrambled by group-common RNTI to schedule group-common PDSCH which is scrambled with the same group-common RNTI. If a UE is configured with both PTM and PTP transmissions, a gNB dynamically decides whether to deliver multicast data by PTM leg and/or PTP leg for a given UE based on the protocol stack defined in clause 16.10.3, based on information such as MBS Session QoS requirements, number of joined UEs, UE individual feedback on reception quality, and other criteria. The same QoS requirements apply regardless of the decision. PTP transmission is not supported for MBS multicast session data reception for UEs in RRC_INACTIVE state. SPS is not supported for MBS multicast session data reception for UEs in RRC_INACTIVE state.

3GPP TS 38.300

NR; NR and NG-RAN Overall description; Stage-2

RAN2

3GPP Series : 38 , Radio technology beyond LTE

16.10.5.4

4.4.1.1 Average DL cell PDCP SDU bit-rate

a) This measurement provides the average cell bit-rate of PDCP SDUs on the downlink. This represents the ingress rate of user plane traffic to the eNodeB/RN (via X2 or S1). The measurement is split into subcounters per E-RAB QoS level (QCI). b) CC c) This measurement is obtained by accumulating the number of bits entering the eNodeB/RN, and then dividing the sum by the measurement period . The measurement is performed at the PDCP SDU level. PDCP SDUs that are forwarded over the X2/S1 to another eNodeB during handover shall be deducted from the bit count – if this results in a negative bit count the bit count shall be set to zero. Separate counters are maintained for each QCI. The sum of all supported per QCI measurements shall equal the total DL cell PDCP SDU bit-rate. In case only a subset of per QCI measurements is supported, a sum subcounter will be provided first. d) Each measurement is an integer value representing the bit-rate measured in kbit/s. The number of measurements is equal to the number of QCIs plus a possible sum value identified by the .sum suffix. e) The measurement name has the form DRB.PdcpSduBitrateDl.QCI where QCI identifies the E-RAB level quality of service class. f) EUtranCellFDD EUtranCellTDD g) Valid for packet switched traffic h) EPS i) One usage of this measurement is to support the KPI "E-UTRAN data Energy Efficiency" defined in [13].

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.1.1

9.3.5.2.1 FDD

For the parameters specified in Table 9.3.5.2.1-1, and using the downlink physical channels specified in Annex C, the minimum requirements are specified in Table 9.3.5.2.1-2 and by the following a) the ratio of the throughput obtained when transmitting the transport format indicated by each reported wideband CQI index subject to an interference source with specified DIP and that obtained when transmitting the transport format indicated by each reported wideband CQI index subject to a white Gaussian noise source shall be ≥ ; b) when transmitting the transport format indicated by each reported wideband CQI index subject to an interference source with specified DIP, the average BLER for the indicated transport formats shall be greater than or equal to 2%. Table 9.3.5.2.1-1 Fading test for two antennas (FDD) Table 9.3.5.2.1-2 Minimum requirement (FDD)

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.3.5.2.1

5.30.2.10 Onboarding of UEs for SNPNs 5.30.2.10.1 General

Onboarding of UEs for SNPNs allows the UE to access an Onboarding Network (ONN) for the purpose of provisioning the UE with SNPN credentials for primary authentication and other information to enable access to a desired SNPN, i.e. (re-)select and (re-)register with SNPN. To provision SNPN credentials in a UE that is configured with Default UE credentials (see clause 5.30.2.10.2.4), the UE selects an SNPN as ONN and establishes a secure connection with that SNPN referred to as Onboarding SNPN (ON-SNPN), see more details in clause 5.30.2.10.2. NOTE: If the UE is already provisioned with a set of SNPN credentials or credentials owned by a Credentials Holder and needs to be provisioned with an additional set of SNPN credentials, the UE can access an SNPN using the network selection in SNPN access mode as described in clause 5.30.2.4, normal registration (i.e. not registration for onboarding) and normal PDU Session (i.e. not a restricted PDU Session used for onboarding) and then leverage the SNPN's User Plane connection to get access to a PVS. The PVS address can be provided in the same way as when the Onboarding Network is a PLMN. To provision SNPN credentials in a UE that is equipped with a USIM configured with PLMN credentials, the UE selects a PLMN as ONN and establishes a secure connection with that PLMN, see more details in clause 5.30.2.10.3. After the secure connection is established, the UE is provisioned with SNPN credentials and possibly other data to enable discovery, (re-)selection and (re-)registration for a desired SNPN, see more details in clause 5.30.2.10.4. ON-SNPN and SO-SNPN can be roles taken by either an SNPN or different SNPNs. It is possible for the same network to be in both roles with respect to a specific UE.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

3GPP Series : 23 , Technical realization ("stage 2")

5.30.2.10

5.2.5.2.2 Npcf_AMPolicyControl_Create service operation

Service operation name: Npcf_AMPolicyControl_Create Description: NF Service Consumer can request the creation of an AM Policy Association and by providing relevant parameters about the UE context to the PCF. Inputs, Required: SUPI. Inputs, Optional: Information provided by the AMF, such as Access Type, Permanent Equipment Identifier, GPSI, User Location Information, UE Time Zone, Serving Network identifier (PLMN ID, or PLMN ID and NID, see clause 5.34 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]), RAT type, List of subscribed Service Area Restrictions, subscribed RFSP Index, the Allowed NSSAI, Partially Allowed NSSAI, S-NSSAI(s) rejected partially in the RA, Rejected S-NSSAI(s) for the RA, Pending NSSAI, Target NSSAI, GUAMI, Subscribed UE-AMBR, Network Slice Replacement supported for the UE (see clause 5.15.19 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]), Internal Group (see clause 5.9.7 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]), subscription notification indication, backup AMF(s) (if NF Type is AMF). Backup AMF(s) are sent only once by the AMF to the PCF in its first interaction with the PCF, list of NWDAF instance Ids and corresponding Analytics ID(s). Outputs, Required: AM Policy Association ID. Outputs, Optional: The requested access and mobility related policy information as defined in clause 6.5 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20] and Policy Control Request Trigger(s) of AM Policy Association as defined in clause 6.1.2.5 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. See clause 4.2.2.2.2 (step 16) for the detail usage of this service operation for AMF. In step 16, the AMF requests the PCF to apply operator policies for the UE. See clause 4.16.1.2 (steps 2 and 3) for the detail usage of this service operation for AMF. In step 2, the AMF requests the PCF to apply operator policies for the UE; in step 3, the PCF acknowledges AMF with requested policy.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

3GPP Series : 23 , Technical realization ("stage 2")

5.2.5.2.2

6.4.1 Cipher key and integrity key setting

Authentication and key setting are triggered by the authentication procedure and described in 6.3. Authentication and key setting may be initiated by the network as often as the network operator wishes. Key setting can occur as soon as the identity of the mobile subscriber (i.e. P-TMSI, TMSI or IMSI) is known by the VLR/SGSN. The CK and IK are stored in the VLR/SGSN and transferred to the RNC when needed. The CK and IK for the CS domain are stored on the USIM and updated at the next authentication from this domain as specified in subclause 6.8.1.5. The CK and IK for the PS domain are stored on the USIM and updated at the next authentication from this domain as specified in subclause 6.8.1.5. If an authentication procedure is performed during a connection (PS or CS mode), the new cipher key CK and integrity key IK shall be taken in use in both the RNC and the ME as part of the security mode set-up procedure (see 6.4.5) that follows the authentication procedure.

3GPP TS 33.102

3G security; Security architecture

SA WG3

3GPP Series : 33 , Security aspects

6.4.1

6.8.7.1 UMTS security context

A UMTS security context in GSM BSS is only established for UMTS subscribers with a ME that is capable of UMTS AKA and connected to a R99+ VLR/SGSN. At the network side, two cases are distinguished: a) In case of an intersystem change to a UTRAN controlled by the same SGSN, the UMTS cipher/integrity keys CK and IK agreed during the latest UMTS AKA procedure are sent to the target RNC. b) In case of an intersystem change to a UTRAN controlled by another SGSN, the initial SGSN sends the UMTS cipher/integrity keys CK and IK agreed during the latest UMTS AKA procedure to the (new) SGSN controlling the target RNC. The new SGSN becomes the new anchor point for the service. The new SGSN then stores the UMTS cipher/integrity keys CK and IK and sends them to the target RNC. At the user side, in both cases, the ME applies the UMTS cipher/integrity keys CK and IK received from the USIM during the latest UMTS AKA procedure.

3GPP TS 33.102

3G security; Security architecture

SA WG3

3GPP Series : 33 , Security aspects

6.8.7.1

5.9.2.4 Requirements on the Service Communication Proxy (SCP)

The SCP has interfaces with Network Functions (NF) and peer SCPs within the PLMN (or SNPN). The interface between the SCP and the NFs and between the two SCPs shall fulfil the following requirements: - Mutual authentication shall be performed between the SCP and NFs, and between the two SCPs within the PLMN (or SNPN). - All communication between the SCP and NFs and between SCPs shall be confidentiality, integrity and replay protected. If SCP endpoints are co-located with the NFs, the above two requirements may be satisfied by colocation. The SCP shall provide confidentiality, integrity and replay protection for its internal communication over SCP internal network interfaces. NOTE 1: All parties communicating through the SCP need to trust the SCP to correctly handle the messages passing through it. If the signalling message (service/subscription request or notification message) from the sending NF does not include the PLMN ID in the 3gpp-Sbi-Originating-Network-Id header and the sending SCP can determine the PLMN-ID value to be included in the 3gpp-Sbi-Originating-Network-Id header, the sending SCP should include it.

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

5.9.2.4

6.1.3 Unacknowledged allocation of a temporary identity

If the serving network does not receive an acknowledgement of the successful allocation of a temporary identity from the user, the network shall maintain the association between the new temporary identity TMSIn and the IMSI and between the old temporary identity TMSIo (if there is any) and the IMSI. For a user-originated transaction, the network shall allow the user to identify itself by either the old temporary identity TMSIo or the new temporary identity TMSIn. This allows the network to determine the temporary identity stored in the mobile station. The network shall subsequently delete the association between the other temporary identity and the IMSI, to allow the temporary identity to be allocated to another user. For a network-originated transaction, the network shall identify the user by its permanent identity (IMSI). When radio contact has been established, the network shall instruct the user to delete any stored TMSI. When the network receives an acknowledgement from the user, the network shall delete the association between the IMSI and any TMSI to allow the released temporary identities to be allocated to other users. Subsequently, in either of the cases above, the network may initiate the normal TMSI reallocation procedure. Repeated failure of TMSI reallocation (passing a limit set by the operator) may be reported for O&M action.

3GPP TS 33.102

3G security; Security architecture

SA WG3

3GPP Series : 33 , Security aspects

6.1.3

6.7.1 Minimum requirement

User Equipment(s) transmitting in close vicinity of each other can produce intermodulation products, which can fall into the UE, or eNode B receive band as an unwanted interfering signal. The UE intermodulation attenuation is defined by the ratio of the mean power of the wanted signal to the mean power of the intermodulation product when an interfering CW signal is added at a level below the wanted signal at each of the transmitter antenna port with the other antenna port(s) if any is terminated. Both the wanted signal power and the intermodulation product power are measured through E-UTRA rectangular filter with measurement bandwidth shown in Table 6.7.1-1. The requirement of transmitting intermodulation is prescribed in Table 6.7.1-1. Table 6.7.1-1: Transmit Intermodulation

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.1

– SSB-MTC

The IE SSB-MTC is used to configure measurement timing configurations, i.e., timing occasions at which the UE measures SSBs. SSB-MTC information element -- ASN1START -- TAG-SSB-MTC-START SSB-MTC ::= SEQUENCE { periodicityAndOffset CHOICE { sf5 INTEGER (0..4), sf10 INTEGER (0..9), sf20 INTEGER (0..19), sf40 INTEGER (0..39), sf80 INTEGER (0..79), sf160 INTEGER (0..159) }, duration ENUMERATED { sf1, sf2, sf3, sf4, sf5 } } SSB-MTC2 ::= SEQUENCE { pci-List SEQUENCE (SIZE (1..maxNrofPCIsPerSMTC)) OF PhysCellId OPTIONAL, -- Need M periodicity ENUMERATED {sf5, sf10, sf20, sf40, sf80, spare3, spare2, spare1} } SSB-MTC2-LP-r16 ::= SEQUENCE { pci-List SEQUENCE (SIZE (1..maxNrofPCIsPerSMTC)) OF PhysCellId OPTIONAL, -- Need R periodicity ENUMERATED {sf10, sf20, sf40, sf80, sf160, spare3, spare2, spare1} } SSB-MTC3-r16 ::= SEQUENCE { periodicityAndOffset-r16 CHOICE { sf5-r16 INTEGER (0..4), sf10-r16 INTEGER (0..9), sf20-r16 INTEGER (0..19), sf40-r16 INTEGER (0..39), sf80-r16 INTEGER (0..79), sf160-r16 INTEGER (0..159), sf320-r16 INTEGER (0..319), sf640-r16 INTEGER (0..639), sf1280-r16 INTEGER (0..1279) }, duration-r16 ENUMERATED {sf1, sf2, sf3, sf4, sf5}, pci-List-r16 SEQUENCE (SIZE (1..maxNrofPCIsPerSMTC)) OF PhysCellId OPTIONAL, -- Need M ssb-ToMeasure-r16 SetupRelease { SSB-ToMeasure } OPTIONAL -- Need M } SSB-MTC4-r17 ::= SEQUENCE { pci-List-r17 SEQUENCE (SIZE (1..maxNrofPCIsPerSMTC)) OF PhysCellId OPTIONAL, -- Need M offset-r17 INTEGER (0..159) } SSB-MTC-AdditionalPCI-r17 ::= SEQUENCE { additionalPCIIndex-r17 AdditionalPCIIndex-r17, additionalPCI-r17 PhysCellId, periodicity-r17 ENUMERATED { ms5, ms10, ms20, ms40, ms80, ms160, spare2, spare1 }, ssb-PositionsInBurst-r17 CHOICE { shortBitmap BIT STRING (SIZE (4)), mediumBitmap BIT STRING (SIZE (8)), longBitmap BIT STRING (SIZE (64)) }, ss-PBCH-BlockPower-r17 INTEGER (-60..50) } AdditionalPCIIndex-r17 ::= INTEGER(1..maxNrofAdditionalPCI-r17) -- TAG-SSB-MTC-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

4.4.4.1 Location updating initiation by the mobile station

Any timer used for triggering the location updating procedure (e.g. T3211, T3212) is stopped if running. As no RR connection exists at the time when the location updating procedure has to be started, the MM sublayer within the mobile station will request the RR sublayer to establish a RR connection and enter state WAIT FOR RR CONNECTION (LOCATION UPDATE). The procedure for establishing an RR connection is described in 3GPP TS 44.018[ None ] [84] subclause 3.3 and 3GPP TS 25.331[ None ] [23c]. The mobile station initiates the location updating procedure by sending a LOCATION UPDATING REQUEST message to the network, starts the timer T3210 and enters state LOCATION UPDATING INITIATED. The location updating type information element shall indicate what kind of updating is requested. If the MS is configured for "AttachWithIMSI" as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [135] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [112] and the selected PLMN is neither the registered PLMN nor in the list of equivalent PLMNs, the MS shall include the IMSI in the Mobile identity IE in the LOCATION UPDATING REQUEST message. If the mobile station is configured to use CS fallback and SMS over SGs, or SMS over SGs only, and TIN indicates "RAT-related TMSI" the mobile station shall set the TIN to "P-TMSI" unless the mobile station had already received the EMM cause #18 during a combined attach procedure (see subclause 5.5.1.3.4.3 of 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120]) or a combined tracking area updating procedure (see subclause 5.5.3.3.4.3 of 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120]) on the same PLMN, but not disabled the E-UTRAN capability.

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.4.4.1

5.4.4.5 Abnormal cases in the UE

The following abnormal cases can be identified: a) Transmission failure of the CONFIGURATION UPDATE COMPLETE message with TAI change from lower layers If the current TAI is not in the TAI list, the generic UE configuration update procedure shall be aborted and a registration procedure for mobility and periodic registration update shall be initiated. If the current TAI is still part of the TAI list, it is up to the UE implementation how to re-run the ongoing procedure that triggered the generic UE configuration update procedure. b) Transmission failure of CONFIGURATION UPDATE COMPLETE message indication without TAI change from lower layers It is up to the UE implementation how to re-run the ongoing procedure that triggered the generic UE configuration update procedure. c) Generic UE configuration update and de-registration procedure collision If the UE receives CONFIGURATION UPDATE COMMAND message after sending a DEREGISTRATION REQUEST message and the access type included in the DEREGISTRATION REQEUST message is same as the access in which the CONFIGURATION UPDATE COMMAND message is received, then the UE shall ignore the CONFIGURATION UPDATE COMMAND message and proceed with the de-registration procedure. Otherwise, the UE shall proceed with both the procedures. d) Void e) Generic UE configuration update and service request procedure collision If the SERVICE REQUEST message does not include UE request type IE with Request type value set to "NAS signalling connection release" and the UE receives a CONFIGURATION UPDATE COMMAND message before the ongoing service request procedure has been completed, the UE shall proceed with both the procedures. If the SERVICE REQUEST message includes UE request type IE with Request type value set to "NAS signalling connection release" and the UE receives a CONFIGURATION UPDATE COMMAND message before the ongoing service request procedure has been completed, the UE shall ignore the CONFIGURATION UPDATE COMMAND message and proceed with the service request procedure. f) "CAG information list" is received and the UE is operating in SNPN access operation mode If the UE receives the CAG information list IE in the CONFIGURATION UPDATE COMMAND message and the UE is operating in SNPN access operation mode, the UE shall ignore the content of CAG information list IE.

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.5

9.9.4.28 Serving PLMN rate control

The purpose of the Serving PLMN rate control information element is to indicate the maximum number of uplink ESM DATA TRANSPORT messages including User data container IEs the UE is allowed to send via a PDN connection per 6 minute interval (see 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10]). The Serving PLMN rate control information element is coded as shown in figure 9.9.4.28.1. The Serving PLMN rate control is a type 4 information element with 4 octets length. Figure 9.9.4.28.1: Serving PLMN rate control information element Serving PLMN rate control value (octet 3 to octet 4) is a binary encoded integer indicating the maximum number of uplink ESM DATA TRANSPORT messages including User data container IEs the UE is allowed to send per 6 minute interval. The Serving PLMN rate control value is an integer equal to or higher than 10. The Serving PLMN rate control value FFFFH indicates that the maximum number of uplink ESM DATA TRANSPORT messages including User data container IEs the UE is allowed to send per 6 minute interval is not restricted.

3GPP TS 24.301

Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3

CT WG1

3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network

9.9.4.28

4.16.5.1 SMF initiated SM Policy Association Modification

The SMF may initiate the SM Policy Association Modification procedure if a Policy Control Request Trigger is met. NOTE 1: When SMF instance is changed within the same SMF set the callback URI can be updated via this procedure. Figure 4.16.5.1-1: SMF initiated SM Policy Association Modification For local breakout roaming, the interaction with HPLMN (e.g. step 2) is not used. In local breakout roaming, the V-PCF interacts with the UDR of the VPLMN. 1. When a Policy Control Request Trigger condition is met the SMF requests to update (Npcf_SMPolicyControl_Update) the SM Policy Association and provides information on the conditions that have been met as specified in clause 5.2.5.4.5. If the SMF is notified by NRF that the stored PCF instance is not reachable, it should query the NRF for PCF instances within the PCF set and select another instance (see clause 6.3.1.0 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]). The QoS constraints from the VPLMN are provided by the H-SMF to the H-PCF in the home routed roaming scenario as defined in clause 4.3.2.2.2. 2. When an AF has subscribed to an event that is met due to the report from the SMF, the PCF reports the event to the AF or TSCTSF by invoking the Npcf_PolicyAuthorization_Notify service operation. If the SMF has reported that new 5GS Bridge/Router information has been detected and no AF session exists for this PDU session yet: - If integration with TSN applies (see clause 5.28 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]), then the PCF informs a pre-configured TSN AF using the Npcf_PolicyAuthorization_Notify (User-plane Node ID, the port number of the DS-TT port, MAC address of the DS-TT Ethernet port for the PDU Session and UE-DS-TT Residence Time (if available)) service operation for the event of "5GS Bridge/Router information Notification" as described in clause 6.1.3.18 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. - Otherwise, i.e. if the integration with TSN does not apply, the PCF may inform discovered and selected TSCTSF (as described in clause 6.3.24 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]) using the Npcf_PolicyAuthorization_Notify (User Plane Node ID, UE-DS-TT Residence Time (if available), the port number for the PDU session and MAC address of the DS-TT Ethernet port for Ethernet type PDU Session or IP address for IP type PDU Session, MTU size for IPv4 or IPv6 (if available)) service operation for the event of "5GS Bridge/Router information Notification" as described in clause 6.1.3.18 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. In the case of private IPv4 address being used for IP type PDU Session, the Npcf_PolicyAuthorization_Notify also contains DNN and S-NSSAI of the PDU Session. NOTE 2: For a given DNN and S-NSSAI, it is assumed that the network only needs to deploy one or TSCTSF Set in this Release of the specification. When the TSN AF or TSCTSF receives the Npcf_PolicyAuthorization_Notify message and no AF session exists for this PDU Session, the TSN AF shall use the Npcf_PolicyAuthorization service described in clause 5.2.5.3 to request creation of a new AF session specific to the received MAC address of the DS-TT Ethernet port of the PDU Session, while the TSCTSF shall use the Npcf_PolicyAuthorization service to request creation of a new AF session specific to the received MAC address of the DS-TT Ethernet port (if available, for Ethernet type PDU Session) or IP address (for IP type PDU Session) of the PDU Session. In the case of private IPv4 address being used for IP type PDU Session, the TSCTSF shall use the Npcf_PolicyAuthorization service to request creation of a new AF session specific to the received IP address, DNN and S-NSSAI of the IP type PDU Session. The TSN AF or TSCTSF shall then use the Npcf_PolicyAuthorization service to subscribe for notifications for 5GS Bridge/Router information Notification event over the newly established AF session. The TSN AF or TSCTSF may provide a Port or User-Plane Management Information Container for the PDU Session and related port number in the Npcf_PolicyAuthorization creation request. If the SMF has reported PMIC with port number or UMIC, then the PCF also provides these information elements to the TSN AF or TSCTSF. When integration with TSN applies (see clause 5.28 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]), the TSN AF calculates the bridge delay for each port pair, using the UE-DS-TT Residence Time of the DS-TT Ethernet port(s) for the 5GS bridge indicated by the 5GS user-plane Node ID. 3. 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. 4. The PCF makes a policy decision as described in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. The PCF may determine that updated or new policy information needs to be sent to the SMF. If the SMF reported accumulated usage for the PDU session in step 1 the PCF deducts the value from the remaining allowed usage for the subscriber, DNN and S-NSSAI in the UDR by invoking Nudr_DM_Update (SUPI, DNN, S-NSSAI, Policy Data, Remaining allowed Usage data, updated data) service operation. If the SMF reported accumulated usage for a MK(s) in step 1 the PCF deducts the value from the remaining allowed usage for the MK in the UDR by invoking Nudr_DM_Update (SUPI, DNN, S-NSSAI, Policy Data, Remaining allowed Usage data, updated data (including MK(s))) service operation. When new PCF instance is selected in step 1, the new PCF should invoke Nbsf_Management_Update service operation to update the binding information in BSF. In the non-roaming case, the PCF may subscribe to Analytics from NWDAF as defined in clause 6.1.1.3 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. In the home-routed roaming scenario, the H-PCF ensures that the QoS constraints provided by the VPLMN are taken into account as described in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. NOTE 3: 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. 5. The PCF answers with a Npcf_SMPolicyControl_Update response with updated policy information about the PDU Session determined in step 4.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

3GPP Series : 23 , Technical realization ("stage 2")

4.16.5.1

5.3.19.2 Redirection of the UE by the core network

The network that supports CIoT optimizations can redirect a UE between EPC and 5GCN as specified in clause 5.31.3 of 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [58]. The network can take into account the UE's N1 mode capability or S1 mode capability, the CIoT network behaviour supported and preferred by the UE or the CIoT network behaviour supported by the network to determine the redirection. NOTE: It is assumed that the network would avoid redirecting the UE back and forth between EPC and 5GCN. The network redirects the UE to 5GCN by rejecting the attach request, or tracking area update request, or service request with the EMM cause #31 "Redirection to 5GCN required" as specified in clause 5.5.1.2.5, 5.5.1.3.5, 5.5.3.2.5, 5.5.3.3.5 and 5.6.1.5. Upon receipt of reject message, the UE disables the E-UTRA capability as specified in clause 4.5 and enables the N1 mode capability if it was disabled in order to move to 5GCN. The network that supports CIoT optimizations can also redirect a UE from 5GCN to EPC as specified in clause 4.8.4A.2 of 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54].

3GPP TS 24.301

Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3

CT WG1

3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network

5.3.19.2

6.5.3 UE requested bearer resource allocation procedure 6.5.3.1 General

The purpose of the UE requested bearer resource allocation procedure is for a UE to request an allocation of bearer resources for a traffic flow aggregate. The UE requests a specific QoS demand (QCI) and optionally sends a GBR requirement for a new traffic flow aggregate. If accepted by the network, this procedure invokes a dedicated EPS bearer context activation procedure (see clause 6.4.2) or an EPS bearer context modification procedure (see clause 6.4.3). If there is a PDN connection for emergency bearer services established, the UE shall not request additional bearer resources for this PDN connection.

3GPP TS 24.301

Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3

CT WG1

3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network

6.5.3

28.7.9 Decorated NAI format for SUCI 28.7.9.1 General

The Decorated NAI format for SUCI shall take the form of a NAI and shall have the form 'Homerealm!username@otherrealm' as specified in clause 2.7 of the IETF RFC 4282 [53]. The username part of Decorated NAI shall contain the username of the NAI format for SUCI as specified in clause 28.7.3. 'Homerealm' shall be the realm of the NAI format for SUCI as specified in clause 28.7.3, unless specified otherwise in relevant clauses. The realm part of Decorated NAI consists of 'otherrealm', see the IETF RFC 4282 [53]. Otherrealm' is the realm built using the PLMN ID (visited MCC + visited MNC) of the visited PLMN selected by the UE. In case of the SNPN senarios, the "Otherrealm" is the realm build using the SNPN ID (PLMN ID + NID, where PLMN ID + NID are MCC + MNC + NID of the non-subscribed SNPN). The 'Homerealm' and the 'otherealm' may be preceded by one or more labels for specific use cases of the Decorated NAI format for SUCI, e.g. for 5G NSWO (see clause 28.7.9.2). The result is a decorated NAI should take the form as mentioned below: <one or more labels>.mnc<homeMNC>.mcc<homeMCC>.3gppnetwork.org!<username of SUCI in NAI format>@<one or more labels>.mnc<visitedMNC>.mcc<visitedMCC>.3gppnetwork.org For the SNPN scenarios where the credential holder is a subscribed SNPN, the decorated NAI should have the form as mentioned below: <one or more labels>.nid<subscribedSNPNNID>.mnc<subscribedSNPNMNC>.mcc<subscribedSNPNMCC>.3gppnetwork.org!<username of SUCI in NAI format>@<one or more labels>.nid<nonsubscribedSNPNNID>.mnc<nonsubscribedSNPNMNC>.mcc<nonsubscribedSNPNMCC>.3gppnetwork.org For the SNPN scenarios where the credential holder is an HPLMN, the decorated NAI should have the form as mentioned below: <one or more labels>.mnc< homeMNC>.mcc< homeMNC>.3gppnetwork.org!<username of SUCI in NAI format>@<one or more labels>.nid<nonsubscribedSNPNNID>.mnc<nonsubscribedSNPNMNC>.mcc<nonsubscribedSNPNMCC>.3gppnetwork.org NOTE: In 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [139], the term "subscribed SNPN" refers to the SNPN for which UE has a subscription.The term "subscribedSNPNMCC" hence, refers to the MCC of the SNPN to which the UE is subscribed. The term "subscribedSNPNMNC" also refers to the MNC of the SNPN to which the UE is subscribed.

3GPP TS 23.003

Numbering, addressing and identification

CT WG4

3GPP Series : 23 , Technical realization ("stage 2")

28.7.9

M.5 IAB inter-CU topology adaptation and backhaul RLF recovery procedure

In case of the inter-CU migration as specified in TS 38.401[ NG-RAN; Architecture description ] [78], the IAB-MT is migrated from a source IAB-donor-CU to a target IAB-donor-CU. The migrating IAB-node becomes a boundary IAB-node since its IAB-DU retains F1AP with the source IAB-donor-CU after its IAB-MT obtains RRC connectivity with the target IAB-donor-CU (c.f. TS 38.401[ NG-RAN; Architecture description ] [78]). In case IPsec tunnel mode is used for F1 interface protection, the migrating/descendant/Recovery IAB-node may use MOBIKE (IETF RFC 4555 [111]) to migrate the IPsec tunnel to the new IP outer addresses as specified in TS 38.401[ NG-RAN; Architecture description ] [78].

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

M.5

4.23.9.0 Overview

The procedures in this clause describe the Addition, Removal and Change of PDU Session Anchor (PSA2), Branching Point or UL CL controlled by I-SMF. They all rely on following principles: 1. When a (new) I-SMF is inserted (e.g. as described in clause 4.23.7 or clause 4.23.11), the I-SMF provides the DNAI list it supports to the SMF. This list is assumed to remain constant during the N16a association between the I-SMF and the SMF for a PDU Session. 2. Based on the DNAI list information received from I-SMF, the SMF may then at any time provide or update the list of DNAI(s) of interest for this PDU Session to I-SMF. This may take place e.g. when the I-SMF provides the DNAI list it supports or when new or updated or removed PCC rule(s) is/are received by the SMF as defined in clause 4.23.6. This list of DNAI(s) of interest for this PDU Session indicates to the I-SMF the list of DNAI(s) candidate for local traffic steering within the PDU Session. An indication of whether Multi-homing is possible is also provided to the I-SMF and the I-SMF uses this information to decide whether multi-homing can be used for the PDU Session. 3. Whenever the I-SMF has inserted or removed or changed a local offload capability the I-SMF invokes a Nsmf_PDUSession_Update Request to indicate to the SMF the list of corresponding DNAI(s). Based on this indication the SMF invokes a Nsmf_PDUSession_Update Request to send the corresponding N4 information to the I-SMF. 4. Then SMF may then at any time invoke a Nsmf_PDUSession_Update Request to send N4 information to the I-SMF. 5. The I-SMF may at any time send a Nsmf_PDUSession_Update Request to forward to the SMF N4 events received from a local UPF; this may e.g. correspond to traffic reporting. 6. When source I-SMF is to be removed from a PDU Session (e.g. at I-SMF change or removal), the SMF issues the N4 information targeting the UL CL/BP (s) and L-PSA(s) controlled by this I-SMF, including requests to release the corresponding N4 Sessions. If the N9 forwarding tunnel to support the EAS session continuity controlled by I-SMF(s) is not established between the source ULCL and the target UL CL, when the Source I-SMF receives a Nsmf_PDUSession_ReleaseSMContext Request from AMF, it initiates a data forwarding timer (if indirect data forwarding applies) before releasing the resources of the PDU Session. When the Source I-SMF has received N4 release from SMF, it releases the UL CL/BP (s) and L-PSA(s) resources either directly if no data forwarding timer is started, or at the expiry of the data forwarding timer. Otherwise if the N9 forwarding tunnel to support the EAS session continuity controlled by I-SMF(s) is established between the source UL CL and target UL CL, the source I-SMF releases the UL CL/BP (s) and L-PSA(s) after no active traffic over the N9 forwarding tunnel. When IPv6 multi-homing is used and an I-SMF is removed, the SMF re-configure the UE to not use the original IP prefix @L-PSA(s).

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

3GPP Series : 23 , Technical realization ("stage 2")

4.23.9.0