Datasets:

Exploration-Lab

/

MM-TelecoBench

like 1

Follow

Exploration Lab 62

C.3.1 Profile 1: management of sequence numbers which are partly time-based

Generation of sequence numbers: This follows the general scheme for the generation of sequence numbers specified in Annex C.1.1.1. The following parameter values are suggested for reference: Time unit of the clock: 1 second Length of in bits = 5. Length of SEQ2 in bits = n : 24 This means that GLC will wrap around after p = 2n = 224 seconds = 194 days. This ensures that most users will have become active at least once during this period. This implies a length of SEQ1 in bits = 19. Start conditions: Choose SQNHE = 0 for all users and GLC = 1. Arrival rate temporarily higher than clock rate: Choose D = 216. D may be chosen quite large as long as the conditions in C.1.1.1 (4)(ii) and (iii) are satisfied. Choosing D = 216 = 65536 means that the condition in C.1.1.1 (4)(i) is satisfied unless more than 65536 requests for batches arrive within over 18 hours which is practically impossible. Verification of sequence numbers in the USIM: This follows the handling of sequence numbers in the USIM specified in Annex C.2. Length of the array: a = 32. This satisfies the requirement in section 6.3.2 that the mechanism for the verification of sequence numbers shall ensure that a sequence number can still be accepted if it is among the last x sequence numbers generated. Protection against wrap around: Choose = 228. Choosing = 228 means that an attack to force the counter in the USIM to wrap around would require at least SEQmax/ = 215 > 32.000 successful authentications (cf. note 6 of C.2.3). We have > p, as required in note 7 of C.2.3. Age limit for sequence numbers: The use of such a limit is optional. The choice of a value for the parameter L affects only the USIM. It has no impact on the choice of other parameters and it entirely up to the operator, depending on his security policy. Therefore no particular value is suggested here. To give an example: if the policy stipulates that authentication vectors older than x seconds shall be rejected then L has to be set to x as the time unit of the clock is 1 second. User anonymity: the value of SQN does not allow to trace the user over longer periods. Therefore, there may be no need to conceal SQN by an anonymity key as specified in section 6.3.

3GPP TS 33.102

3G security; Security architecture

SA WG3

3GPP Series : 33 , Security aspects

C.3.1

4.2.5.3 UE Activity Notification procedure

The UE Activity Notification procedure is illustrated in figure 4.2.5.3-1. Figure 4.2.5.3-1: UE Activity Procedure 0. Event has been subscribed in the AMF for UE reachability for DL traffic or for UE reachability status change. 1a. For a UE in CM-IDLE, the AMF receives (N1) NAS signalling implying UE is reachable for DL traffic, e.g. a Registration Request or Service Request message from the UE, the AMF performs step 2; 1b. For a UE in CM-CONNECTED, if the AMF has initiated the N2 Notification procedure in Step 4 of clause 4.2.5.2 and when the AMF receives a (N2) UE Notification (see clause 4.8.3) or a (N2) Path Switch Request (see clause 4.9.1.2) implying UE is reachable for DL traffic from the NG-RAN, the AMF performs step 2. Otherwise, i.e. UE is in CM-CONNECTED and AMF has not initiated N2 Notification procedure, the AMF performs step 2; or 1c. The UE's reachability state changes from reachable to unreachable, then AMF performs step 2. 2a. For event subscription of "UE reachable for DL traffic", if the AMF has an MM context for the UE and the URRP-AMF information flag associated with the subscribing NF is set to report once that the UE is reachable for DL traffic, the AMF initiates the Namf_EventExposure_Notify service operation (SUPI, UE Reachable) message (or Nudm_UECM_Registration service operation when applicable) to the UDM following step 1a or step 1b. The AMF clears the corresponding URRP-AMF information if applicable for the UE. 2a1. When the UDM receives the Namf_EventExposure_Notify service operation (SUPI, UE-Reachable) message or Nudm_UECM_Registration service from AMF for a UE that has URRP-AMF information flag set in the UDM, it triggers appropriate notifications to the service-related entities associated with the URRP-AMF information flag that have subscribed to the UDM for UE Reachability notifications. If SMSF is registered, it also triggers appropriate notifications to the service-related entities associated with the URRP-AMF information flag that have subscribed to the UDM for UE reachability for SMS delivery notification (e.g. SMS-GMSC, HSS). UDM clears the URRP-AMF information for the UE. If no SMSF is registered and there are service-related entities subscribed to the UDM for the UE reachability for SMS delivery notification, the UDM clears the URRP-AMF information for the UE but does not notify any service-related entity. When the UDM receives the Nudm_UECM_Registration service from SMSF for a UE that has service-related entities subscribed to the UDM for the UE reachability for SMS delivery notification and no URRP-AMF flag set in the UDM, the UDM triggers appropriate notifications to the service-related entities that have subscribed to the UDM for UE reachability for SMS delivery notification). NOTE: The UE Reachability Notification is sent by the UDM using different interfaces/services depending on the service-related entity. For example, an SBI capable service-related entity can receive the notification using the Nudm_EventExposure_Notify service operation (if previously subscribed) while an SMS-SC can get the notification as described in TS 23.040[ Technical realization of the Short Message Service (SMS) ] [7] based on the SC address stored in the MWD list. 2b. If in step 0 the AMF received Namf_EventExposure_Subscribe_service operation directly from an NF authorised to receive direct notifications in the case of UE reachability status change, or the UDM indicated that the notification needs to be sent directly to the NF in the case of UE reachability for DL traffic, the AMF initiates the Namf_EventExposure_Notify service operation (SUPI, UE reachability state) message directly to the NF.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.2.5.3

D.6.4 UPSI list

The purpose of the UPSI list information element is to transfer from the UE to the PCF a list of UPSIs. The UPSI list information element is coded as shown in figure D.6.4.1, figure D.6.4.2, and table D.6.4.1. The UPSI list information element has a minimum length of 3 octets and a maximum length of 65532 octets. NOTE: A PCF implementing a previous version of the present specification will expect the UPSI list information element to have a minimum length of 10 octets and could be unable to decode a UPSI list information element with a length of 3 octets i.e. a UPSI list information element not containing any UPSI. Figure D.6.4.1: UPSI list information element Figure D.6.4.2: UPSI sublist Table D.6.4.1: UPSI list information element

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

D.6.4

7.7.3.1 Syntactically incorrect optional IEs

The UE shall treat all optional IEs that are syntactically incorrect in a Type 6 IE container information element as not present in the Type 6 IE container information element. The network shall take the same approach. EXAMPLE 1: If the Type 6 IE container information element includes 2 type 6 information elements, and the first one is syntactically incorrect, the receiver ignores the first information element and continues with the processing of the second one. EXAMPLE 2: If the remaining value part of a Type 6 IE container information element is too short to contain a complete type 6 information element, the receiver ignores these octets and continues with the processing of the octets following the Type 6 IE container information element, if there are any.

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

7.7.3.1

9.11.4.27 Port management information container

The purpose of the Port management information container information element is to transport a port management service message as specified in clause 8 of 3GPP TS 24.539[ 5G System (5GS); Network to TSN translator (TT) protocol aspects; Stage 3 ] [19BA]. The Port management information container information element is coded as shown in figure 9.11.4.27.1 and table 9.11.4.27.1. The Port management information container is a type 6 information element with a minimum length of 4 octets and a maximum length of 65538 octets. Figure 9.11.4.27.1: Port management information container information element Table 9.11.4.27.1: Port management information container information element

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

9.11.4.27

5.2.6.4.5 Nnef_ParameterProvision_Get service operation

Service operation name: Nnef_ParameterProvision_Get Description: The consumer gets the UE related information (e.g. Expected UE Behaviour, Network Configuration parameters, ECS Address Configuration Information). Inputs, Required: GPSI or UE addressing information, AF Identifier, requested information (e.g. Expected UE Behaviour, Network Configuration parameters, ECS Address Configuration Information). Inputs, Optional: None. Outputs, Required: Requested data, Operation execution result indication. Outputs, Optional: External Identifier (representing an AF specific UE Identifier).

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

5.2.6.4.5

9.3.4.1 Handover with SRVCC operation

The source NR node decides to handover the UE with ongoing IMS voice from NR to UTRAN according the following principles: - The source NR node determines that the UE supports UTRA and requests the UE to send its UTRA radio access capabilities to the NG-RAN; - The source NR node configures target RAT measurement and reporting; - The source NR node determines based on the radio conditions and the indication that SRVCC operation is possible that handover to UTRAN should be initiated; - The source NR node initiates the handover preparation only for the ongoing IMS voice and provides the indication to AMF that the handover is towards UTRAN together with the target UTRAN Node ID. The source NR node also provides an indication to the target UTRAN that the incoming handover originates from 5G. The SRVCC proceeds as specified in TS 23.216[ Single Radio Voice Call Continuity (SRVCC); Stage 2 ] [34]; - The source NR node ensures that the size of the source-to-target container does not exceed the limits that can be handled by the interfaces involved in the handover; NOTE: For SRVCC handover, the size limit of the inter-node source-to-target container is 2560 octets (see AN-APDU in TS 29.002[ Mobile Application Part (MAP) specification ] [44]). - Radio resources are prepared in the target RAT before the handover; - The RRC reconfiguration message from the target RAT is delivered to the source NR node via a transparent container and is passed to the UE by the source NR node in the handover command; - In-sequence and lossless handovers are not supported; - Only voice bearer is handed over to target RAT; - Security procedures for handover to UTRA follows the procedures as specified in TS 33.501[ Security architecture and procedures for 5G System ] [5]; - Only handover to UTRA-FDD is supported.

3GPP TS 38.300

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

RAN2

3GPP Series : 38 , Radio technology beyond LTE

9.3.4.1

6.1.1 Physical channels

A downlink physical channel corresponds to a set of resource elements carrying information originating from higher layers and is the interface defined between TS 36.212[ Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and channel coding ] [3] and the present document TS 36.211[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation ] . The following downlink physical channels are defined: - Physical Downlink Shared Channel, PDSCH - Physical Broadcast Channel, PBCH - Physical Multicast Channel, PMCH - Physical Control Format Indicator Channel, PCFICH - Physical Downlink Control Channel, PDCCH - Physical Hybrid ARQ Indicator Channel, PHICH - Enhanced Physical Downlink Control Channel, EPDCCH - MTC Physical Downlink Control Channel, MPDCCH - Short Physical Downlink Control Channel, SPDCCH

3GPP TS 36.211

Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation

RAN1

3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology

6.1.1

8.19.3 Remote UE RRC Inactive to other states

The signalling flow for Remote UE from RRC Inactive to other states is shown in Figure 8.19.3-1. Figure 8.19.3-1: Remote UE RRC Resume procedure 1. The U2N Remote UE and the U2N Relay UE perform discovery procedure, and establish PC5 connection using NR ProSe procedure. This step may be omitted if PC5 connection was established. 2. The U2N Remote UE sends an RRCResumeRequest message to the U2N Relay UE via PC5 RLC Relay Channel. 3~10. The gNB-CU allocates the local ID of the U2N Remote UE if the U2N Relay UE does not have it. The details of those steps can be referred to clause 8.19.1. 11. After receiving the local ID of the U2N Remote UE, the U2N Relay UE sends the RRCResumeRequest message of the U2N Remote UE to gNB-DU. 12. The gNB-DU allocates a C-RNTI and a gNB-DU UE F1AP ID for the U2N Remote UE and sends the INITIAL UL RRC MESSAGE TRANSFER message to gNB-CU by encapsulating the RRCResumeRequest message of the U2N Remote UE. In addition, the local ID of the U2N Remote UE, the gNB-DU UE F1AP ID of the U2N Relay UE and the sidelink configuration container for at least the PC5 Relay RLC channel configuration for relaying of U2N Remote UE’s SRB1 are included in the INITIAL UL RRC MESSAGE TRANSFER message. 13. The gNB-CU configures the U2N Relay UE with PC5 Relay RLC channel, Uu Relay RLC channel and bearer mapping for relaying of U2N Remote UE’s SRB1. According to the configuration from gNB-CU, the U2N Relay UE establishes a PC5 Relay RLC channel for relaying of U2N Remote UE’s SRB1 over PC5 and establishes a Uu Relay RLC channel for relaying of U2N Remote UE’s SRB1 over Uu. NOTE 1: This step may be performed earlier, e.g., via steps 5~8. 14~19. The details of those steps can be referred to Steps 5~10 in clause 8.6.2. For L2 U2N relay, the RRC message(s) between the U2N Remote UE and the gNB-DU are relayed via the U2N Relay UE; Steps 14~15 may additionally perform the configurations of PC5 Relay RLC channel(s) for relaying of U2N Remote UE’s SRB2 and DRBs. 20. The gNB-CU establishes additional Uu Relay RLC channels between the gNB-DU and the U2N Relay UE, and additional PC5 Relay RLC channels for the U2N Relay UE for relaying of U2N Remote UE’s DRBs and SRBs. Also, such step may configure the bearer mapping between U2N Remote UE’s DRB/SRB and PC5/Uu Relay RLC channel at the U2N Relay UE. NOTE 2: This step may be performed earlier.

3GPP TS 38.401

NG-RAN; Architecture description

RAN3

3GPP Series : 38 , Radio technology beyond LTE

8.19.3

5.2.2.2.1 SIB validity

The UE shall apply the SI acquisition procedure as defined in clause 5.2.2.3 upon cell selection (e.g. upon power on), cell-reselection, return from out of coverage, after reconfiguration with sync completion, after entering the network from another RAT, upon receiving an indication that the system information has changed, upon receiving a PWS notification, upon receiving request (e.g., a positioning request) from upper layers; and whenever the UE does not have a valid version of a stored SIB or posSIB or a valid version of a requested SIB. When the UE acquires a MIB or a SIB1 or an SI message in a serving cell as described in clause 5.2.2.3, and if the UE stores the acquired SIB, then the UE shall store the associated areaScope, if present, the first PLMN-Identity in the PLMN-IdentityInfoList for non-NPN-only cells or the first NPN identity (SNPN identity in case of SNPN, or PNI-NPN identity in case of PNI-NPN) in the NPN-IdentityInfoList for NPN-only cells, the cellIdentity, the systemInformationAreaID, if present, and the valueTag, if present, as indicated in the si-SchedulingInfo for the SIB. If the UE stores the acquired posSIB, then the UE shall store the associated areaScope, if present, the cellIdentity, the systemInformationAreaID, if present, the valueTag, if provided in assistanceDataSIB-Element, and the expirationTime if provided in assistanceDataSIB-Element. The UE may use a valid stored version of the SI except MIB, SIB1, SIB6, SIB7 or SIB8 e.g. after cell re-selection, upon return from out of coverage or after the reception of SI change indication. The valueTag and expirationTime for posSIB is optionally provided in assistanceDataSIB-Element, as specified in TS 37.355[ LTE Positioning Protocol (LPP) ] [49]. A L2 U2N Remote UE in RRC_IDLE or RRC_INACTIVE can inform the interested SIB(s) to the connected L2 U2N Relay UE as defined in clause 5.8.9.8.2 and receive the SIB(s) from the L2 U2N Relay UE as defined in clause 5.8.9.9.3. A L2 U2N Remote UE in RRC_CONNECTED receives SIB1 and other SIB(s) in RRCReconfiguration message and performs on-demand SI request if required, as defined in clause 5.2.2.3.5 and 5.2.2.3.6. The L2 U2N Remote UE in RRC_IDLE or RRC_INACTIVE or RRC_CONNECTED is not required to obtain SI over Uu interface, but it may decide to perform the SI acquisition procedure over Uu interface as defined in clause 5.2.2.3 by UE implementation. NOTE: The storage and management of the stored SIBs in addition to the SIBs valid for the current serving cell is left to UE implementation. The UE shall: 1> delete any stored version of a SIB after 3 hours from the moment it was successfully confirmed as valid; 1> for each stored version of a SIB: 2> if the areaScope is associated and its value for the stored version of the SIB is the same as the value received in the si-SchedulingInfo for that SIB from the serving cell: 3> if the UE is NPN capable and the cell is an NPN-only cell: 4> if the first NPN identity included in the NPN-IdentityInfoList, the systemInformationAreaID and the valueTag that are included in the si-SchedulingInfo for the SIB received from the serving cell are identical to the NPN identity, the systemInformationAreaID and the valueTag associated with the stored version of that SIB: 5> consider the stored SIB as valid for the cell; 3> else if the first PLMN-Identity included in the PLMN-IdentityInfoList, the systemInformationAreaID and the valueTag that are included in the si-SchedulingInfo for the SIB received from the serving cell are identical to the PLMN-Identity, the systemInformationAreaID and the valueTag associated with the stored version of that SIB: 4> consider the stored SIB as valid for the cell; 2> if the areaScope is not present for the stored version of the SIB and the areaScope value is not included in the si-SchedulingInfo for that SIB from the serving cell: 3> if the UE is NPN capable and the cell is an NPN-only cell: 4> if the first NPN identity in the NPN-IdentityInfoList, the cellIdentity and valueTag that are included in the si-SchedulingInfo for the SIB received from the serving cell are identical to the NPN identity, the cellIdentity and the valueTag associated with the stored version of that SIB: 5> consider the stored SIB as valid for the cell; 3> else if the first PLMN-Identity in the PLMN-IdentityInfoList, the cellIdentity and valueTag that are included in the si-SchedulingInfo for the SIB received from the serving cell are identical to the PLMN-Identity, the cellIdentity and the valueTag associated with the stored version of that SIB: 4> consider the stored SIB as valid for the cell; 1> for each stored version of a posSIB: 2> if the areaScope is associated and its value for the stored version of the posSIB is the same as the value received in the posSIB-MappingInfo for that posSIB from the serving cell and the systemInformationAreaID included in the si-SchedulingInfo is identical to the systemInformationAreaID associated with the stored version of that posSIB: 3> if the valueTag (see TS 37.355[ LTE Positioning Protocol (LPP) ] [49]) for the posSIB received from the serving cell is identical to the valueTag associated with the stored version of that posSIB; or if the expirationTime (see TS 37.355[ LTE Positioning Protocol (LPP) ] [49]) associated with the stored posSIB has not been expired: 4> consider the stored posSIB as valid for the cell; 2> if the areaScope is not present for the stored version of the posSIB and the areaScope value is not included in the posSIB-MappingInfo for that posSIB from the serving cell and the cellIdentity for the posSIB received from the serving cell is identical to the cellIdentity associated with the stored version of that posSIB: 3> if the valueTag (see TS 37.355[ LTE Positioning Protocol (LPP) ] [49]) for the posSIB received from the serving cell is identical to the valueTag associated with the stored version of that posSIB; or if the expirationTime (see TS 37.355[ LTE Positioning Protocol (LPP) ] [49]) associated with the stored posSIB has not been expired: 4> consider the stored posSIB as valid for the cell;

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

5.2.2.2.1

I.9.2.4.1 Secondary authentication using DCS

After successful primary authentication as described in I.9.2.2 (i.e. primary authentication without using DCS), upon the establishment of the Onboarding PDU Session, the ON-SNPN may trigger secondary authentication procedure with the DCS using Default UE credentials for secondary authentication, as described in clause 11.1. NOTE: If both primary and secondary authentication use a certificate-based authentication method like e.g. EAP-TLS, and if required by the use case, it is possible to configure the UE with the same client certificates for Default UE credentials for secondary authentication as for the Default UE credentials for primary authentication.

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

I.9.2.4.1

8.7.6 FDD (DC)

The parameters specified in Table 8.7.6-1 are valid for all FDD DC tests unless otherwise stated. Table 8.7.6-1: Common Test Parameters (FDD) For UE not supporting 256QAM, the requirements are specified in Table 8.7.6-2, with the addition of the parameters in Table 8.7.6-1 and the downlink physical channel setup according to Annex C.3.2. The test points are applied to UE category and bandwidth combination with maximum aggregated bandwidth as specified inTable 8.7.6-3. The TB success rate across CGs shall be sustained during at least 300 frames. For UE supporting 256QAM, the requirements are specified in Table 8.7.6-4, with the addition of the parameters in Table 8.7.6-1 and the downlink physical channel setup according to Annex C.3.2. The test points are applied to UE category and bandwidth combination with maximum aggregated bandwidth as specified inTable 8.7.6-5. The TB success rate across CGs shall be sustained during at least 300 frames. For UE supporting 256QAM, the requirements in Table 8.7.6-2 are not applicable. The applicability of ther requirements are specified in Clause 8.1.2.3A. Table 8.7.6-2: Minimum requirement (DC 64QAM) Table 8.7.6-3: Test points for sustained data rate (FRC DC 64QAM) Table 8.7.6-4: Minimum requirement (DC 256QAM) Table 8.7.6-5: Test points for sustained data rate (FRC DC 256QAM)

3GPP TS 36.101

Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception

RAN4

3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology

8.7.6

9.3.6 Mapping to physical resources

The block of complex-valued symbols shall be multiplied with the amplitude scaling factor in order to conform to the transmit power specified in [4], and mapped in sequence starting with to physical resource blocks on antenna port and assigned for transmission of PSSCH. The mapping to resource elements corresponding to the physical resource blocks assigned for transmission and not used for transmission of reference signals shall be in increasing order of first the index , then the index, starting with the first slot in the subframe. If Transmission Format of SCI format 1 is set to 1, the resource elements in the last SC-FDMA symbol within a subframe shall not considered in the mapping process. Otherwise, the resource elements in the last SC-FDMA symbol within a subframe shall be counted in the mapping process but not transmitted. If sidelink frequency hopping is disabled the set of physical resource blocks to be used for transmission is given by where is obtained from [4, clause 14.1.1.2.1]. If sidelink frequency hopping with type 1 hopping is enabled, the set of physical resource blocks to be used for transmission is given by [4]. If sidelink frequency hopping with predefined hopping pattern is enabled, the set of physical resource blocks to be used for transmission is given by the sidelink control information together with a predefined pattern in clause 5.3.4 with the following exceptions: - only inter-subframe hopping shall be used - the number of subbands is given by higher layers as described in [4, clause 14.1.1.2] - the quantity is given by higher layers as described in [4, clause 14.1.1.2] - the quantity where is given by clause 9.2.4 - the quantity - the pseudo-random sequence generator is initialized at the start of each slot fulfilling with the initialization value given by hoppingParameter-r12 in [9] - the quantity shall be replaced by , given by [4, clause 14.1.1.2.1] - for sidelink transmission mode 1 - - for sidelink transmission mode 2 - where is given by [4, clause 14.1.3] - the quantity shall be replaced by , given by [4, clause 14.1.1.4] - the physical resource block to use for transmission with given by [4, clause 14.1.3]

3GPP TS 36.211

Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation

RAN1

3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology

9.3.6

5.3.5.18.1 LTM configuration

The network configures the UE with one or more LTM candidate configurations within the LTM-Config IE. In NR-DC, the UE may receive two independent ltm-Config: - an ltm-Config associated with the MCG that is included within an RRCReconfiguration message received via SRB1; and - an ltm-Config associated with the SCG that is included within an RRCReconfiguration message either received via SRB3, or, alternatively, embedded in an RRCReconfiguration message received via SRB1. In case the UE receives two independent ltm-Config: - the UE maintains two independent VarLTM-Config, one associated with each ltm-Config; - the UE maintains two independent VarLTM-ServingCellNoResetID, one associated with each ltm-Config; - the UE maintains two independent VarLTM-ServingCellUE-MeasuredTA-ID, one associated with each ltm-Config; - the UE independently performs all the procedures in clause 5.3.5.18 for each ltm-Config and the associated VarLTM-Config, VarLTM-ServingCellNoResetID, and VarLTM-ServingCellUE-MeasuredTA-ID unless explicitly stated otherwise. The UE shall perform the following actions based on the received LTM-Config IE: 1> if the received LTM-Config includes ltm-ReferenceConfiguration set to setup: 2> if the current VarLTM-Config includes an ltm-ReferenceConfiguration: 3> replace the ltm-ReferenceConfiguration value within VarLTM-Config with the received ltm-ReferenceConfiguration; 2> else: 3> store the received ltm-ReferenceConfiguration in VarLTM-Config; 1> else (the received LTM-Config includes ltm-ReferenceConfiguration set to release): 2> remove ltm-ReferenceConfiguration in VarLTM-Config; 1> if the received LTM-Config includes ltm-ServingCellNoResetID: 2> if the current VarLTM-ServingCellNoResetID includes an ltm-ServingCellNoResetID: 3> replace the ltm-ServingCellNoResetID value within VarLTM-ServingCellNoResetID with the received ltm-ServingCellNoResetID; 2> else: 3> store the received ltm-ServingCellNoResetID in VarLTM-ServingCellNoResetID; 1> if the received LTM-Config includes ltm-ServingCellUE-MeasuredTA-ID: 2> if the current VarLTM-ServingCellUE-MeasuredTA-ID includes an ltm-ServingCellUE-MeasuredTA-ID: 3> replace the ltm-ServingCellUE-MeasuredTA-ID value within VarLTM-ServingCellUE-MeasuredTA-ID with the received ltm-ServingCellUE-MeasuredTA-ID; 2> else: 3> store the received ltm-ServingCellUE-MeasuredTA-ID in VarLTM-ServingCellUE-MeasuredTA-ID; 1> if the received LTM-Config includes ltm-CSI-ResourceConfigToReleaseList: 2> perform the LTM CSI resource configuration release as specified in 5.3.5.18.4; 1> if the received LTM-Config includes ltm-CSI-ResourceConfigToAddModList: 2> perform the LTM CSI resource configuration addition or modification as specified in 5.3.5.18.5; 1> if the received LTM-Config includes the ltm-CandidateToReleaseList: 2> perform the LTM candidate configuration release as specified in 5.3.5.18.2; 1> if the received LTM-Config includes the ltm-CandidateToAddModList: 2> perform the LTM candidate configuration addition or modification as specified in 5.3.5.18.3.

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

5.3.5.18.1

6.3.4.3 Slot / Sub frame boundary time mask for subframe TTI

The sub frame boundary time mask defines the observation period between the previous/subsequent sub–frame and the (reference) sub-frame. A transient period at a slot boundary within a sub-frame is only allowed in the case of Intra-sub frame frequency hopping. For the cases when the subframe contains SRS the time masks in subclause 6.3.4.4 apply. There are no additional requirements on UE transmit power beyond that which is required in subclause 6.2.2 and subclause 6.6.2.3 Figure 6.3.4.3-1: Transmission power template for Frame Structure Type 1 and Frame Structure Type 2 For Frame Structure Type 3 the sub-frame boundary time mask is specified in Figure 6.3.4.3-1A when the bit indicating the PUSCH ending symbol in the associated DCI has value ‘1’ and the PUSCH starting position is modified by in the following subframe (clause 6.3.4.1); denotes the duration of the ending SC-FDMA symbol. the OFF power requirement applies 5 s after the end of the last symbol transmitted. Figure 6.3.4.3-1A: Transmission power template when the bit in the associated DCI indcating the PUSCH ending symbol has value ‘1' for Frame Structure Type 3 For Frame Structure Type 3 the first slot boundary time mask is specified in Figure 6.3.4.3-1B when the PUSCH mode is 3 indicated in DCI [4]. The PUSCH starting position modified by relative to the start of the sub-frame as indicated in the associated DCI, where and the basic time unit are specified in TS 36.211[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation ] [4]. At the end of the first slot or with denoting the duration of one SC-FDMA symbol when the bit indicating the PUSCH ending symbol in the associated DCI is either fourth or seventh symbol as specified in TS 36.212[ Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and channel coding ] [5], respectively; the OFF power requirement applies 5 s after the end of the last symbol transmitted. Figure 6.3.4.3-1B: Transmission power template for the first slot in one subframe for Frame Structure Type 3 For Frame Structure Type 3 the second slot boundary time mask is specified in Figure 6.3.4.3-1C when the PUSCH mode is 2 indicated in DCI [4]. The PUSCH starting position modified by relative to the start of the second slot as indicated in the associated DCI, where and the basic time unit are specified in TS 36.211[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation ] [4]. At the end of the second slot or with denoting the duration of one SC-FDMA symbol when the bit indicating the PUSCH ending symbol in the associated DCI is either thirteenth or fourteenth symbol as specified in TS 36.212[ Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and channel coding ] [5], respectively; the OFF power requirement applies 5 s after the end of the last symbol transmitted. For Frame Structure Type 3 the second slot boundary time mask specified in Figure 6.3.4.3-1C can also be applied when the PUSCH mode is 1 indicated in DCI [4] and transmition starts at the eighth symbol. The PUSCH starting position relative to the start of the second slot. At the end of the second slot or with denoting the duration of one SC-FDMA symbol when the bit indicating the PUSCH ending symbol in the associated DCI is either thirteenth or fourteenth symbol as specified in TS 36.212[ Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and channel coding ] [5], respectively; the OFF power requirement applies 5 s after the end of the last symbol transmitted. Figure 6.3.4.3-1C: Transmission power template for the second slot in one subframe for Frame Structure Type 3

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

.1 Delete Session Request

The direction of this message shall be from MME/S4-SGSN to SGW, from SGW to PGW and from TWAN/ePDG to PGW (see Table 6.1-1). A Delete Session Request message shall be sent on the S11 interface by the MME to the SGW and on the S5/S8 interface by the SGW to the PGW for a UE having at least one PDN connection through the SGW and PGW, as part of the procedures: - EUTRAN Initial Attach - UE, HSS or MME Initiated Detach - UE or MME Requested PDN Disconnection It shall also be sent on the S4 interface by the SGSN to the SGW, and on the S5/S8 interface by the SGW to the PGW as part of - MS, HLR or SGSN initiated detach procedure - Combined GPRS/IMSI Attach - MS and SGSN Initiated PDN connection Deactivation Procedure using S4 On the S11 interface by the MME to the SGW as part of the procedures: - Tracking Area Update with SGW Change - S1 Based Handover with SGW Change - X2 Based Handover with SGW Relocation - E-UTRAN to UTRAN Iu mode Inter RAT handover with SGW change - E-UTRAN to GERAN A/Gb mode Inter RAT handover with SGW change - Inter RAT handover cancel with SGW change - MME to Gn/Gp SGSN combined hard handover and SRNS relocation procedure - MME to SGSN Routing Area Update - E-UTRAN to Gn/Gp SGSN Inter RAT handover - S1 Based handover cancel with SGW change - Optimised Active Handover: E-UTRAN Access to CDMA2000 HRPD Access - MME triggered Serving GW relocation And on the S4 interface by the SGSN to the SGW as part of - Enhanced Serving RNS Relocation with SGW relocation using S4 - Routing Area Update with SGW change - SGSN to MME Tracking Area Update with SGW change - SRNS Relocation Cancel Procedure Using S4 - Inter RAT with SGW change handover cancel - Serving RNS relocation with SGW change - UTRAN Iu mode to E-UTRAN Inter RAT handover with SGW change - GERAN A/Gb mode to E-UTRAN Inter RAT handover with SGW change - S4 SGSN to Gn/Gp SGSN Routeing Area Update - S4 SGSN to Gn/Gp SGSN Serving RNS Relocation Procedures - S4 SGSN to Gn/Gp SGSN PS handover Procedures - S4-SGSN triggered Serving GW relocation The message shall also be sent on the S2b interface by the ePDG to the PGW as part of procedures: - UE/ePDG Initiated Detach with GTP on S2b - UE Requested PDN Disconnection with GTP on S2b - HSS/AAA Initiated Detach with GTP on S2b The message shall also be sent on the S2a interface by the TWAN to the PGW as part of procedures: - UE/TWAN Initiated Detach and UE/TWAN Requested PDN Disconnection in WLAN on GTP S2a - HSS/AAA Initiated Detach in WLAN on GTP S2a This message may also be sent on S5/S8 interface by the SGW to the PGW: - If Downlink Data Notification Acknowledge message with Context not found cause value is received. During the detach procedure, if ISR is active and SGW receives a Delete Session Request, the SGW shall deactivate the ISR. NOTE: The SGW can determine if it is a detach procedure based on e.g. it receives a Delete Session Request message for the last PDN Connection. When ISR is active, during the Detach procedure the SGW shall forward the Delete Session Request message to the PGW on the S5/S8 interface after receiving both of the messages sent from the MME and the SGSN for the same PDN Connection. If there are any procedure collisions, the Delete Session Request shall have precedence over any other Tunnel Management message. During the handover procedure the Delete Session Request message shall not release the indirect data forwarding tunnels. Possible Cause values are: - "ISR deactivation ". - "Network Failure". - "QoS parameter mismatch". Table .1-1 specifies the presence of the IEs in the message. Table 7.2.9.1-1: Information Elements in a Delete Session Request Table 7.2.9.1-2: Overload Control Information within Delete Session Request

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

.1

Annex A (informative): Layer 2 handling for bearer type change

This clause provides for information an overview on L2 handling for bearer type change in MR-DC, with and without a security key change due to a change of the termination point. Table A-1: L2 handling for bearer type change with and without a security key change due to a change of the termination point. NOTE 1: For EN-DC and NGEN-DC MCG, NE-DC SCG: the MAC/RLC behaviour depends on the solution selected by the network. It can be PCell handover (for EN-DC and NGEN-DC) or PSCell change (for NE-DC), which triggers MAC reset and RLC re-establishment. Alternatively, the logical channel identity can be changed, either via RLC bearer release and add for the same DRB (including RLC re-establishment), or via reconfiguration of the RLC bearer with RLC-re-establishment. For EN-DC and NGEN-DC SCG, NE-DC MCG, NR-DC MCG and SCG: the MAC/RLC behaviour depends on the solution selected by the network. It can be reconfiguration with sync, with MAC reset and RLC re-establishment. Alternatively, the logical channel identity can be changed via RLC bearer release and add. NOTE 2: Void NOTE 3: For EN-DC and NGEN-DC: Re-establishment and release. For NE-DC and NR-DC: Release. NOTE 4: For NE-DC: Re-establishment and release. For EN-DC, NGEN-DC and NR-DC: Release.

3GPP TS 37.340

Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2

RAN2

3GPP Series : 37 , Multiple radio access technology aspects

Annex

6.2.8 Guard period for narrowband and wideband retuning

For BL/CE UEs, a guard period of at most OFDM symbols is created for Rx-to-Rx and Tx-to-Rx frequency retuning between two consecutive subframes. - If the higher layer parameter ce-RetuningSymbols is set, then equals ce-RetuningSymbols, otherwise . - If the higher layer parameter ce-pdsch-maxBandwidth-config is set to 5 MHz, then the rules for guard period creation defined in the remainder of this clause apply not for retuning between narrowbands but for retuning between widebands and for transmissions involving multiple widebands. - If the UE is configured with CEModeA and higher layer parameter ce-PDSCH-FlexibleStartPRB-AllocConfig, the rules for guard period creation defined in the remainder of this clause apply for retuning between tuning narrowbands defined for the allocation resources not fully within one narrowband defined in Clause 6.2.7 as the consecutive 6PRBs starting from if is aligned with RBG boundary, or the consecutive 6PRBs ending at if is aligned with RBG boundary, where and are defined in Table 7.1.6.3-2 [4]. - If the UE is configured with CEModeB and higher layer parameter ce-PDSCH-FlexibleStartPRB-AllocConfig, the rules for guard period creation defined in the remainder of this clause apply for retuning between the tuning narrowband defined as the narrowband shifted according to Table 6.2.7-1. - If the UE retunes from a first downlink narrowband to a second downlink narrowband with a different center frequency, a guard period is created by the UE not receiving at most OFDM symbols in the second narrowband. - If the UE retunes from a first uplink narrowband to a second downlink narrowband with a different center frequency for frame structure type 2, a guard period is created by the UE not receiving at most OFDM symbols in the second narrowband. Furthermore, for BL/CE UEs configured with the higher layer parameter srs-UpPtsAdd, a guard period of at most OFDM or SC-FDMA symbols is created for Rx-to-Tx frequency retuning within a special subframe for frame structure type 2. Primarily, the TDD guard period (GP) specified in clause 4.2 serves as the guard period for narrowband retuning, and if GP is not sufficient then additional guard period is created by the UE according to: - If SRS is configured to be transmitted in the first UpPTS symbol, the additional guard period is created by the UE not receiving at most DwPTS symbols in the first narrowband. - If SRS is configured to be transmitted in the second UpPTS symbol but not in the first UpPTS symbol, the additional guard period is created by the UE primarily by not transmitting the first UpPTS symbol and (if ) secondarily by not receiving the last DwPTS symbol.

3GPP TS 36.211

Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation

RAN1

3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology

6.2.8

8.13.3.4.2 Minimum Requirement Enhanced Performance Requirement Type A – Single-layer Spatial Multiplexing with TM9 interference model (User-Specific Reference Symbols) for TDD PCell

The purpose of these tests is to verify closed loop rank one performance on one of the antenna ports 7 or 8 without a simultaneous transmission on the other antenna port in the serving cell when the PDSCH transmission in the serving cell is interfered by PDSCH of one dominant interfering cell applying transmission mode 9 interference model defined in clause B.5.4. In 8.13.3.4.2-1, Cell 1 is the serving cell, and Cell 2 is the interfering cell. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1 and Cell 2, respectively. For TDD FDD CA with TDD PCell with 2 DL CCs, the requirements are specified in Table 8.13.3.4.2-4, based on single carrier requirement specified in Table 8.13.3.4.2-2 and Table 8.13.3.4.2-3, with the addition of the parameters in Table 8.13.3.4.2-1 and the downlink physical channel setup according to Annex C.3.2. Table 8.13.3.4.2-1: Test Parameters for Testing CDM-multiplexed DM RS (single layer) with TM9 interference model for CA Table 8.13.3.4.2-2: Single carrier performance for Enhanced Performance Requirement Type A, CDM-multiplexed DM RS for FDD SCell (FRC) Table 8.13.3.4.2-3: Single carrier performance for Enhanced Performance Requirement Type A, CDM-multiplexed DM RS for TDD PCell (FRC) Table 8.13.3.4.2-4: 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.3.4.2

16.3a.2 Accounting Update

During the life of an IP-CAN bearer some information related to this bearer may change. Upon occurrence of the following events, the P-GW may send RADIUS Accounting Request Interim-Update to the AAA server: RAT change, S-GW address change and QoS change. Interim updates are also used when the IPv4 address is allocated/released/re-allocated for deferred IPv4 addressing for the PDN type IPv4v6. When the P-GW receives a signalling request (e.g. Modify Bearer Request in case of GTP-based S5/S8) that indicates the occurrence of one of these chargeable events, the P-GW may send an Accounting Request Interim-Update to the AAA server to update the necessary information related to this bearer. The P-GW need not wait for the RADIUS AccountingResponse message from the AAA server before sending the response for the triggering signalling message (e.g. Modify Bearer Response). The P-GW may delete the bearer if the AccountingResponse is not received from the AAA. The P-GW may also send interim updates at the expiry of an operator configured time limit. The following Figure 25a.2 is an example message flow to show the procedure of RADIUS accounting update, which applicable for GTP based S5/S8: Figure 25a.2: RADIUS accounting update for Modify Bearer Request

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

16.3a.2

6.1.3.4.2 PDP context deactivation initiated by the network

In order to deactivate a PDP context, the network sends a DEACTIVATE PDP CONTEXT REQUEST message to the MS and starts timer T3395. The message contains the transaction identifier in use for the PDP context to be deactivated and a cause code that typically indicates one of the following causes: # 8: Operator Determined Barring; # 25: LLC or SNDCP failure (A/Gb mode only); # 26: insufficient resources; # 36: regular deactivation; # 38: network failure; # 39: reactivation requested. #112: APN restriction value incompatible with active PDP context; or #113: Multiple accesses to a PDN connection not allowed. The MS shall, upon receipt of this message, reply with a DEACTIVATE PDP CONTEXT ACCEPT message. Upon receipt of the DEACTIVATE PDP CONTEXT ACCEPT message, the network shall stop the timer T3395. If the DEACTIVATE PDP CONTEXT REQUEST message includes the cause #39 "reactivation requested", the PDP context was activated by the MS, and the MS sent an APN for the establishment of the PDN connection, the MS shall stop timer T3396 if it is running for the APN sent by the MS. The MS should then re-activate the PDP context. If the MS did not send an APN for the establishment of the PDN connection and the request type was different from "emergency", the MS shall stop the timer T3396 associated with no APN if it is running, and should re-activate the PDP context without including an APN. Additionally, the MS should re-activate the PDP contexts that were originally activated by the MS and released by the network as a result of this PDP context deactivation procedure. If the DEACTIVATE PDP CONTEXT REQUEST message was received for an emergency PDN connection, the MS shall not stop the timer T3396 associated with no APN if it is running. The MS should then re-initiate the PDP context activation procedure for the emergency PDN connection. NOTE: User interaction is necessary in some cases when the MS cannot re-activate the PDP context(s) automatically. If a detach is requested by the HLR for an MS that has PDP contexts for emergency services, the SGSN shall send a DEACTIVATE PDP CONTEXT REQUEST message to the MS for all the PDP contexts that are not PDP contexts for emergency services. If the network operates in network operation mode I, ISR is activated and the MS has indicated support of EMM combined procedures in MS network capability, when the SGSN receives the request from the Serving GW for deactivating the last remaining PDP context, then the SGSN shall perform a detach procedure for non-GPRS services only as described in subclause .2. In A/Gb mode, both the MS and the network shall initiate local release of the logical link if it is not used by another PDP context. In Iu mode, the network shall initiate the release of Radio Access Bearer associated with this PDP context. If the SM cause value is #26 "insufficient resources", the network may include a value for timer T3396 in the DEACTIVATE PDP CONTEXT REQUEST message. If the SM cause value is #26 "insufficient resources" and T3396 value IE is included: - the MS shall take different actions depending on the timer value received for timer T3396 (if the MS is configured for dual priority, exceptions are specified in subclause 6.1.3.12; if the MS is an MS configured to use AC11 – 15 in selected PLMN, exceptions are specified in subclause 6.1.3.11): i) if the timer value indicates neither zero nor deactivated, the MS shall stop the timer T3396 associated with the corresponding APN, if it is running. The MS shall start timer T3396 with received value and not send another ACTIVATE PDP CONTEXT REQUEST, ACTIVATE SECONDARY PDP CONTEXT REQUEST or MODIFY PDP CONTEXT REQUEST message with exception of those identified in subclause 6.1.3.3, for the same APN until timer T3396 expires or the timer T3396 is stopped. If the MS did not send an APN for the establishment of the PDN connection and the request type was different from "emergency", the MS shall stop timer T3396 associated with no APN, if it is running. The MS shall then start timer T3396 with the value provided in the Back-off timer value IE and not send another ACTIVATE PDP CONTEXT REQUEST without an APN and with request type different from "emergency", or another ACTIVATE SECONDARY PDP CONTEXT REQUEST or MODIFY PDP CONTEXT REQUEST message with exception of those identified in subclause 6.1.3.3, for a non-emergency PDN connection established without an APN sent by the MS, until timer T3396 expires or timer T3396 is stopped. The MS shall not stop timer T3396 upon a PLMN change or inter-system change; ii) if the timer value indicates that this timer is deactivated, the MS shall not send another ACTIVATE PDP CONTEXT REQUEST, ACTIVATE SECONDARY PDP CONTEXT REQUEST or MODIFY PDP CONTEXT REQUEST message with exception of those identified in subclause 6.1.3.3, for the same APN until the MS is switched off or the SIM/USIM is removed or the MS receives a REQUEST PDP CONTEXT ACTIVATION, REQUEST SECONDARY PDP CONTEXT ACTIVATION or MODIFY PDP CONTEXT REQUEST message with exception of those identified in subclause 6.1.3.3, for the same APN from the network or a DEACTIVATE PDP CONTEXT REQUEST message including SM cause #39 "reactivation requested" for a PDP context which was activated by the MS for the same APN from the network. If the MS did not send an APN for the establishment of the PDN connection and the request type was different from "emergency", the MS shall not send another ACTIVATE PDP CONTEXT REQUEST without an APN and with request type different from "emergency", or another ACTIVATE SECONDARY PDP CONTEXT REQUEST or MODIFY PDP CONTEXT REQUEST with exception of those identified in subclause 6.1.3.3, for a non-emergency PDN connection established without an APN sent by the MS, until the MS is switched off or the SIM/USIM is removed or the MS receives any of the following messages: a REQUEST PDP CONTEXT ACTIVATION without an APN, a REQUEST SECONDARY PDP CONTEXT ACTIVATION or MODIFY PDP CONTEXT REQUEST message for a non-emergency PDN connection established without an APN sent by the MS, or a DEACTIVATE PDP CONTEXT REQUEST message including SM cause #39 "reactivation requested" for a PDP context which was activated by the MS for a non-emergency PDN connection established without APN sent by the MS. The timer T3396 remains deactivated upon a PLMN change or inter-system change; and iii) if the timer value indicates that this timer is zero, the MS: - shall stop timer T3396 associated with the corresponding APN, if running, and may send another ACTIVATE PDP CONTEXT REQUEST, ACTIVATE SECONDARY PDP CONTEXT REQUEST or MODIFY PDP CONTEXT REQUEST message for the same APN; and - if the MS did not send an APN for the establishment of the PDN connection and the request type was different from "emergency", the MS shall stop timer T3396 associated with no APN, if running, and may send an ACTIVATE PDP CONTEXT REQUEST message without an APN, or another ACTIVATE SECONDARY PDP CONTEXT REQUEST or MODIFY PDP CONTEXT REQUEST message for a non-emergency PDN connection established without an APN sent by the MS. - If the timer T3396 is running when the MS enters state GMM-DEREGISTERED, the MS remains switched on, and the SIM/USIM in the MS remains the same, then timer T3396 is kept running until it expires or it is stopped. - if the MS is switched off when the timer T3396 is running, the MS shall behave as follows when the MS is switched on and the SIM/USIM in the MS remains the same: - let t1 be the time remaining for T3396 timeout at switch off and let t be the time elapsed between switch off and switch on. If t1 is greater than t, then the timer shall be restarted with the value t1 – t. If t1 is equal to or less than t, then the timer need not be restarted. If the MS is not capable of determining t, then the MS shall restart the timer with the value t1; and - if prior to switch off, timer T3396 was running because an ACTIVATE PDP CONTEXT REQUEST, ACTIVATE SECONDARY PDP CONTEXT REQUEST or MODIFY PDP CONTEXT REQUEST message containing the low priority indicator set to "MS is configured for NAS signalling low priority" was rejected with timer T3396, and if timer T3396 is restarted at switch on, then the MS configured for dual priority shall handle session management requests as indicated in subclause 6.1.3.12. If the T3396 value IE is not included, the MS shall proceed with deactivation procedure and then send DEACTIVATE PDP CONTEXT ACCEPT message.

3GPP TS 24.008

Mobile radio interface Layer 3 specification; Core network protocols; Stage 3

CT WG1

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

6.1.3.4.2

7.6.2.1H Minimum requirements for LTE based 5G terrestrial broadcast

The throughput shall be ≥ 95% of the maximum throughput as represented by a reported BLER of <5% for the reference measurement channels as specified in Annex A.3.18 with parameters specified in Table 7.6.2.1H-1 and 7.6.2.1H-2. For Table 7.6.2.1H-2 in frequency range 1, 2 and 3, up to exceptions are allowed for spurious response frequencies in each assigned frequency channel when measured using a 1MHz step size, where is the number of resource blocks in the downlink transmission bandwidth configuration (see Figure 5.6H-1). For these exceptions the requirements of subclause 7.7 Spurious response are applicable. Table 7.6.2.1H-1: Out-of-band blocking parameters Table 7.6.2.1H-2: Out of band blocking

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

7.6.2.1H

5.5.3.3.2 Combined tracking area updating procedure initiation

The UE operating in CS/PS mode 1 or CS/PS mode state EMM-REGISTERED, shall initiate the combined tracking area updating procedure: a) when the UE that is attached for both EPS and non-EPS services detects that the current TAI is not in the list of tracking areas that the UE previously registered in the MME, unless the UE is configured for "AttachWithIMSI" as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17] and is entering a tracking area in a new PLMN that is neither the registered PLMN nor in the list of equivalent PLMNs; b) when the UE that is attached for EPS services wants to perform an attach for non-EPS services. In this case the EPS update type IE shall be set to "combined TA/LA updating with IMSI attach"; c) when the UE performs an intersystem change from A/Gb mode to S1 mode and the EPS services were previously suspended in A/Gb mode; d) when the UE performs an intersystem change from A/Gb or Iu mode to S1 mode, and the UE previously either performed a combined GPRS attach procedure, an IMSI attach procedure, a location area updating procedure or a combined routing area updating procedure, in A/Gb or Iu mode, or moved to A/Gb or Iu mode from S1 mode through an SRVCC handover or moved to Iu mode from S1 mode through an vSRVCC handover. In this case the EPS update type IE shall be set to "combined TA/LA updating with IMSI attach"; e) when the UE enters EMM-REGISTERED.NORMAL-SERVICE and the UE's TIN indicates "P-TMSI"; f) when the UE receives an indication from the lower layers that the RRC connection was released with cause "load balancing TAU required"; g) when the UE deactivated EPS bearer context(s) locally while in EMM-REGISTERED, because it was not able or not allowed to establish a NAS signalling connection, and then returns to EMM-REGISTERED.NORMAL-SERVICE and no EXTENDED SERVICE REQUEST message, CONTROL PLANE SERVICE REQUEST message or DETACH REQUEST message is pending to be sent by the UE; h) when the UE changes any one of the UE network capability information, the MS network capability information or the N1 UE network capability information; i) when the UE changes the UE specific DRX parameter; j) when the UE receives an indication of "RRC Connection failure" from the lower layers and has no signalling or user uplink data pending (i.e. when the lower layer requests NAS signalling connection recovery); k) when due to manual CSG selection the UE has selected a CSG cell whose CSG identity and associated PLMN identity are not included in the UE's Allowed CSG list or in the UE's Operator CSG list; l) when the UE reselects an E-UTRAN cell while it was in GPRS READY state or PMM-CONNECTED mode; m) when the UE supports SRVCC to GERAN or UTRAN or supports vSRVCC to UTRAN, and changes the mobile station classmark 2 or the supported codecs, or the UE supports SRVCC to GERAN and changes the mobile station classmark 3; n) when the UE changes the radio capability for GERAN or cdma2000® or both; o) when the UE's usage setting or the voice domain preference for E-UTRAN change in the UE; p) when the UE activates mobility management for IMS voice termination as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13], annex P.2, and the TIN indicates "RAT-related TMSI"; q) when the UE performs an intersystem change from A/Gb mode to S1 mode and the TIN indicates "RAT-related TMSI", but the UE is required to perform tracking area updating for IMS voice termination as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13], annex P.4; r) upon reception of a paging indication, if the UE is in state EMM-REGISTERED.ATTEMPTING-TO-UPDATE and the paging indication uses S-TMSI or it uses IMSI with domain indicator set to ″CS″; NOTE 1: As an implementation option, the MUSIM UE is allowed to not respond to paging based on the information available in the paging message, e.g. voice service indication. s) when the UE needs to update the network with EPS bearer context status due to local de-activation of EPS bearer context(s) as specified in clause 6.5.1.4A; t) when the UE performs an intersystem change from A/Gb or Iu mode to S1 mode, and the UE has previously performed the MM connection establishment for CS fallback emergency calls (see 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13], clause 4.5.1.5a) without performing a location area updating procedure or combined routing area updating procedure while camping on a location area which is different from the stored location area. In this case, the EPS update type IE shall be set to "combined TA/LA updating with IMSI attach"; u) when the UE performs an intersystem change from A/Gb or Iu mode to S1 mode, and the MM update status is U2 NOT UPDATED. In this case the EPS update type IE shall be set to "combined TA/LA updating with IMSI attach"; v) when the UE needs to request the use of PSM or needs to stop the use of PSM; w) when the UE needs to request the use of eDRX or needs to stop the use of eDRX; x) when a change in the eDRX usage conditions at the UE requires different extended DRX parameters; y) when a change in the PSM usage conditions at the UE requires a different timer T3412 value or different timer T3324 value; NOTE 2: A change in the PSM or eDRX usage conditions at the UE can include e.g. a change in the UE configuration, a change in requirements from upper layers or the battery running low at the UE. z) when the CIoT EPS optimizations the UE needs to use, change in the UE; za) when the Default_DCN_ID value changes, as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] or in USIM file NASCONFIG as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]; NOTE 3: The tracking area updating procedure is initiated after deleting the DCN-ID list as specified in annex C. zb) when the UE performs inter-system change from N1 mode to S1 mode in EMM-IDLE mode, the UE operates in single-registration mode, and conditions specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] apply; zc) when the UE in EMM-IDLE mode changes the radio capability for E-UTRAN; zd) when the UE performs inter-system change from N1 mode to S1 mode in EMM-CONNECTED mode; ze) when the UE in EMM-IDLE mode changes the radio capability for NG-RAN; zf) in WB-S1 mode, when the UE has received a UE radio capability ID deletion indication IE set to "Network-assigned UE radio capability IDs deletion requested"; zg) when the UE needs to use the WUS assistance, stop to use the WUS assistance, or change the conditions for using the WUS assistance; or zh) when the UE in EMM-IDLE mode needs to inform the network that a UE radio capability information update is required due to a cell change between E-UTRAN and satellite E-UTRAN cells. For case c, if the TIN indicates "RAT-related TMSI" and the EPS services were not resumed before returning to S1 mode, the UE shall set the TIN to "P-TMSI" before initiating the combined tracking area updating procedure. For cases n, zc, ze and zh the UE shall include a UE radio capability information update needed IE in the TRACKING AREA UPDATE REQUEST message. NOTE 3a: For cases n, zc, ze and zh if the UE supports RACS irrespective whether the UE has an applicable UE radio capability ID for the new UE radio configuration in the selected PLMN the UE radio capability information update needed IE is included in the TRACKING AREA UPDATE REQUEST message. If the UE is in the EMM-CONNECTED mode and the UE changes the radio capability for E-UTRAN or for NG-RAN, the UE may locally release the established NAS signalling connection and enter the EMM-IDLE mode. Then, the UE shall initiate the combined tracking area updating procedure including a UE radio capability information update needed IE in the TRACKING AREA UPDATE REQUEST message. For case l, if the TIN indicates "RAT-related TMSI", the UE shall set the TIN to "P-TMSI" before initiating the combined tracking area updating procedure. For case r, the "active" flag in the EPS update type IE shall be set to 1. If the paging is received for CS fallback, the UE shall send the EXTENDED SERVICE REQUEST message to the MME by using the existing NAS signalling connection after the completion of the tracking area updating procedure. If the TRACKING AREA UPDATE ACCEPT message includes a UE radio capability ID deletion indication IE set to "Network-assigned UE radio capability IDs deletion requested", the UE shall proceed with sending the EXTENDED SERVICE REQUEST message. To initiate a combined tracking area updating procedure the UE sends the message TRACKING AREA UPDATE REQUEST to the network, starts timer T3430 and changes to state EMM-TRACKING-AREA-UPDATING-INITIATED. The value of the EPS update type IE in the message shall indicate "combined TA/LA updating" unless explicitly specified otherwise. If the UE initiates the combined tracking area updating procedure for EPS services and "SMS only", the UE shall indicate "SMS only" in the additional update type IE. The UE shall include the TMSI status IE if no valid TMSI is available. Furthermore, if the UE has stored a valid location area identification, the UE shall include it in the Old location area identification IE in the TRACKING AREA UPDATE REQUEST message. If the UE has stored a valid TMSI, the UE shall include the TMSI based NRI container IE in the TRACKING AREA UPDATE REQUEST message. The UE shall include the EPS bearer context status IE in TRACKING AREA UPDATE REQUEST message: a) for the case g; b) for the case s; c) for the case zb; d) if the UE has established PDN connection(s) of "non IP" or Ethernet PDN type; and e) if the UE: 1) locally deactivated at least one dedicated EPS bearer context upon an inter-system mobility from WB-S1 mode to NB-S1 mode in EMM-IDLE mode; 2) locally deactivated at least one dedicated EPS bearer context upon an inter-system change from WB-N1 mode to NB-S1 mode in EMM-IDLE mode for the UE operating in single-registration mode (see clause 6.4.2.1); or 3) locally deactivated at least one default EPS bearer context upon an inter-system change from N1 mode to NB-S1 mode in EMM-IDLE mode for the UE operating in single-registration mode (see clause 6.5.0). In WB-S1 mode, if the UE supports RACS the UE shall set the RACS bit to "RACS supported" in the UE network capability IE of the TRACKING AREA UPDATE REQUEST message. For cases n, zc, ze and zh, in WB-S1 mode, if the UE supports RACS and the UE has an applicable UE radio capability ID for the new UE radio configuration in the selected PLMN, the UE shall set the URCIDA bit to "UE radio capability ID available" in the UE radio capability ID availability IE of the TRACKING AREA UPDATE REQUEST message. For all cases except cases n, zc, ze and zh, in WB-S1 mode, if the UE has an applicable UE radio capability ID for the current UE radio configuration in the selected PLMN, the UE shall set the URCIDA bit to "UE radio capability ID available" in the UE radio capability ID availability IE of the TRACKING AREA UPDATE REQUEST 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

5.5.3.3.2

5.8.2.5 Control of User Plane Forwarding 5.8.2.5.1 General

The SMF controls user-plane packet forwarding for traffic detected by a PDR by providing a FAR with instructions to the UPF, including: - Forwarding operation information; - Forwarding target information. The details of the forwarding target and operation will depend on the scenario and is described below. The following forwarding functionality is required by the UPF: - Apply N3 /N9 tunnel related handling, i.e. encapsulation. - Forward the traffic to/from the SMF, e.g. as described in Table 5.8.2.5.2-1. - Forward the SM PDU DN Request Container from SMF to DN-AAA server - Forward the traffic according to locally configured policy for traffic steering. - Forward the traffic according to N4 rules of a 5G VN group for 5G VN group communication. - Forward the traffic to/from the EASDF. Data forwarding between the SMF and UPF is transmitted on the user plane tunnel established on N4 interface, defined in TS 29.244[ Interface between the Control Plane and the User Plane nodes ] [65].

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.8.2.5

B.7 Derivation of Kc' from Kc for UTRAN/GERAN to HSPA SRVCC handover

This input string is used for GSM subscribers when there is a need to derive GPRS Kc' from the 64-bit Kc during mapping the security contexts from UTRAN/GERAN to HSPA. The input parameter Key is the concatenation of Kc || Kc || Kc || Kc || (which are 64 bits each), and the output Kc' is the 64 most significant bits of the KDF output. - FC = 0x34 - P0 = NONCEMSC - L0 = length of NONCEMSC (i.e. 0x00 0x10) CK'PS || IK'PS shall be derived from GPRS Kc' using the key conversion functions c4 and c5 defined in this specification.

3GPP TS 33.102

3G security; Security architecture

SA WG3

3GPP Series : 33 , Security aspects

B.7

5.4.1.3.5 Authentication not accepted by the network

If the authentication response (RES) returned by the UE is not valid, the network response 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 initiate an identification procedure to retrieve SUCI from the UE and restart the 5G AKA 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 5G AKA 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 5G AKA based primary authentication and key agreement procedure, the network should send an AUTHENTICATION REJECT message to the UE. The network shall maintain, if any, the 5GMM-context and 5G NAS security context of the UE unchanged. Upon receipt of an AUTHENTICATION REJECT message, 1) if the AUTHENTICATION REJECT message has been successfully integrity checked by the NAS: 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 PLMN, the USIM shall be considered invalid until switching off the UE or the UICC containing the USIM is removed. 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. Additionally, the UE shall consider the USIM as invalid for the current SNPN until switching off or the UICC containing the USIM is removed. 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 for 3GPP access until the UE is switched off or the entry is updated. Additionally, the UE shall consider the USIM as invalid for the entry until switching off or the UICC containing the USIM is removed. 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 - if the UE is neither registered for onboarding services in SNPN nor performing initial registration for onboarding services in SNPN, the UE shall set: i) the counter for "SIM/USIM considered invalid for GPRS services" events, the counter for "USIM considered invalid for 5GS services over non-3GPP access" events, and the counter for "SIM/USIM considered invalid for non-GPRS services" events if maintained by the UE, in case of PLMN; or ii) 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 - if the UE is operating in single-registration mode, the UE shall handle EMM parameters, 4G-GUTI, last visited registered TAI, TAI list and eKSI as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] for the case when the authentication procedure is not accepted by the network. The USIM shall be considered as invalid also for non-EPS services until switching off or the UICC containing the USIM is removed; and 2) if the AUTHENTICATION REJECT message is received without integrity protection and if timer T3516 or T3520 is running, 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: a) if the AUTHENTICATION REJECT message is received over 3GPP access, and the counter for "SIM/USIM considered invalid for GPRS services" events in case of PLMN or the counter for "the entry for the current SNPN considered invalid for 3GPP access" events in case of SNPN has a value less than a UE implementation-specific maximum value, proceed as specified in subclause 5.3.20, list item 1)-a) of subclause 5.3.20.2 (if the UE is not operating in SNPN access operation mode) or list item a)-1) of subclause 5.3.20.3 (if the UE is operating in SNPN access operation mode) for the case that the 5GMM cause value received is #3; b) if the AUTHENTICATION REJECT message is received over non-3GPP access, and the counter for "USIM considered invalid for 5GS services over non-3GPP access" events in case of PLMN or the counter for "the entry for the current SNPN considered invalid for non-3GPP access" events in case of SNPN has a value less than a UE implementation-specific maximum value, proceed as specified in subclause 5.3.20, list item 1)-b) of subclause 5.3.20.2 (if the UE is not operating in SNPN access operation mode) or list item a)-2) of subclause 5.3.20.3 (if the UE is operating in SNPN access operation mode) for the case that the 5GMM cause value received is #3. c) 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 PLMN, the UE shall consider the USIM as invalid for 5GS services via 3GPP access and non-EPS service until switching off the UE or the UICC containing the USIM is removed. In case of SNPN, the UE shall consider 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. Additionally, the UE shall consider the USIM as invalid for the current SNPN via 3GPP access until switching off or the UICC containing the USIM is removed. - The UE shall set: - the counter for "SIM/USIM considered invalid for GPRS services" events and the counter for "SIM/USIM considered invalid for non-GPRS services" events if maintained by the UE, in case of PLMN; or - the counter for "the entry for the current SNPN considered invalid for 3GPP access" events in case of SNPN; to UE implementation-specific maximum value. - If the UE is operating in single-registration mode, the UE shall handle 4G-GUTI, TAI list and eKSI as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] for the case when the authentication procedure is not accepted by the network. The USIM shall be considered as invalid also for non-EPS services until switching off or the UICC containing the USIM is removed; 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; - in case of PLMN, the UE shall consider the USIM as invalid for 5GS services via non-3GPP access until switching off the UE or the UICC containing the USIM is removed. In case of SNPN, the UE shall consider the entry of the "list of subscriber data" with the SNPN identity of the current SNPN as invalid for non-3GPP access until the UE is switched off or the entry is updated. Additionally, the UE shall consider the USIM as invalid for the current SNPN and for non-3GPP access until switching off or the UICC containing the USIM is removed; and - the UE shall set: - the counter for "USIM considered invalid for 5GS services over non-3GPP access" events to UE implementation-specific maximum value in case of PLMN; or - the counter for "the entry for the current SNPN considered invalid for non-3GPP access" events to UE implementation-specific maximum value in case of SNPN. 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, T3516, T3517, T3519, T3520 or T3521 (if they were running), enter state 5GMM-DEREGISTERED and delete any stored SUCI. Depending on local requirements or operator preference for emergency services, if the UE initiates a registration procedure with 5GS registration type IE set to "emergency registration" and the AMF is configured to allow emergency registration without user identity, the AMF needs not follow the procedures specified for the authentication failure in the present subclause. The AMF may continue a current 5GMM specific procedure.

3GPP TS 24.501

Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3

CT WG1

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

5.4.1.3.5

4.22.3 Authorization of C2 communication

The 5GS supports USS authorization of C2 communication for pairing of UAV and UAV-C. The pairing of UAV and UAV-C needs to be authorized by USS successfully before the user plane connectivity for C2 communication (over Uu or over NR-PC5) is enabled. For C2 authorization procedure, the UE supporting UAS services provides to the network with CAA-level UAV ID. The USS authorization of UAV flight can also be performed during the C2 authorization procedure. The UE supporting UAS services provides the UAV flight authorization information to the network if provided by upper layers. NOTE 1: The C2 authorization payload in the service-level-AA payload can include one, some or all of the pairing information for C2 communication, an indication of the request for direct C2 communication, pairing information for direct C2 communication, and the UAV flight authorization information (see subclauses 6.4.1.2 and 6.4.2.2). The UE supporting UAS services can establish a PDU session for the C2 communication by providing the CAA-level UAV ID and the C2 authorization payload. The SMF upon reception of the UE's request for the PDU session establishment, determines that authorization is required based on the DNN and S-NSSAI combination of the PDU session is for aerial services according to user's subscription data and the CAA-level UAV ID included in the request. If a UE supporting UAS services uses a common PDU session for both USS communication and C2 communication, the C2 communication can be authorized using UUAA-SM procedure during the PDU session establishment procedure or during the PDU session modification procedure. If the pairing of UAV and UAV-C is revoked, the network shall disable C2 communication for the PDU session. The SMF upon reception of the UE's request for the PDU session establishment, determines that authorization is required based on the DNN and S-NSSAI combination of the PDU session is for aerial services according to user's subscription data and the CAA-level UAV ID included in the request. NOTE 2: The network can disable C2 communication for the PDU session e.g., by removing the QoS flow for C2 communication during PDU session modification procedure as decribed in subclauses 6.3.2.2. If a UE supporting UAS services uses separate PDU sessions for, respectively, USS communication and C2 communication, the C2 communication is authorized using UUAA-SM during the PDU session establishment procedure. If the pairing of UAV and UAV-C is revoked, the PDU session for C2 communication shall be released by the SMF. During the registration procedure for UAS services, direct C2 communication can be authorized as described in subclause 5.5.1.2. A UE supporting A2X over NR-PC5 can perform registration procedure for UAS services including a request for authorization of direct C2 communication by providing CAA-level UAV ID and C2 authorization payload.

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

4.4.1.1 Rf

The Rf reference point supports interaction between a CTF and a CDF. The following information may flow across this reference point in real-time: - Charging events for offline charging from the CTF to the CDF; - Acknowledgements for these events from the CDF to the CTF. The protocol(s) crossing this reference point shall support the following capabilities: - Real-time transactions; - Stateless mode ("event based charging") and statefull mode (“session based charging”) of operation; - Provide its own reliability mechanisms, e.g. retransmission of charging events, to run also on unreliable transport. In addition, the protocol should support changeover to a secondary destination (alternate CDF(s)) in case of the primary CDF not being reachable. This interface application is defined in TS 32.299[ Telecommunication management; Charging management; Diameter charging applications ] [50]. The information contained in the charging events and the relevant chargeable events are specific to the domain / subsystem / service and are detailed in the respective middle tier TSs.

3GPP TS 32.240

Telecommunication management; Charging management; Charging architecture and principles

SA WG5

3GPP Series : 32 , OAM&P and Charging

4.4.1.1

6.7.2 Requirements

The 5G system shall allow flexible mechanisms to establish and enforce priority policies among the different services (e.g. MPS, Emergency, medical, Public Safety) and users. NOTE 1: Priority between different services is subject to regional or national regulatory and operator policies. The 5G system shall be able to provide the required QoS (e.g. reliability, end-to-end latency, and bandwidth) for a service and support prioritization of resources when necessary for that service. The 5G system shall enable the network operator to define and statically configure a maximum resource assignment for a specific service that can be adjusted based on the network state (e.g. during congestion, disaster, emergency and DDoS events) subject to regional or national regulatory and operator policies. The 5G system shall allow decoupling of the priority of a particular communication from the associated QoS characteristics such as end-to-end latency and reliability. The 5G system shall be able to support a harmonised QoS and policy framework applicable to multiple accesses. The 5G system shall be able to support E2E (e.g. UE to UE) QoS for a service. NOTE 2: E2E QoS needs to consider QoS in the access networks, backhaul, core network, and network to network interconnect. The 5G system shall be able to support QoS for applications in a Service Hosting Environment. A 5G system with multiple access technologies shall be able to select the combination of access technologies to serve an UE on the basis of the targeted priority, pre-emption, QoS parameters and access technology availability. The 5G system shall support a mechanism to determine suitable QoS parameters for traffic over a satellite backhaul, based e.g. on the latency and bandwidth of the specific backhaul . NOTE 3: The case where a backhaul connection has dynamically changed latency and/or bandwidth needs to be considered.

3GPP TS 22.261

Service requirements for the 5G system

SA WG1

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

6.7.2

6.1.5 Coordination for interworking with ePDG connected to EPC

When the UE establishes a new PDN connection via an ePDG connected to EPC, to enable the transfer of the PDN connection to N1 mode in case of inter-system change, the UE allocates a PDU session identity and indicates its value in the PDU session ID field in the N1_MODE_CAPABILITY Notify payload of the IKE_AUTH request message (see 3GPP TS 24.302[ Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networks; Stage 3 ] [16]). The network provides the UE with an S-NSSAI in the N1_MODE_INFORMATION Notify payload of the IKE_AUTH response message (see 3GPP TS 24.302[ Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networks; Stage 3 ] [16]). Upon inter-system change to N1 mode , for PDN connection(s) established via an ePDG connected to EPC, if present, the UE may: a) keep some or all of these PDN connections still via ePDG connected to EPC, if supported; b) release some or all of these PDN connections explicitly by initiating the UE initiated tunnel disconnection procedure(s) as specified in 3GPP TS 24.302[ Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networks; Stage 3 ] [16]; or c) attempt to transfer some or all of these PDN connections to N1 mode using the parameters of the PDN connection for which the UE has allocated a PDU session identity by initiating the PDU session establishment procedure(s) with the PDU SESSION ESTABLISHMENT REQUEST message created. In that case, for each and every PDN connection to be transferred: 1) if the PDN connection is for emergency bearer services, the request type shall be set to "existing emergency PDU session". Otherwise the request type shall be set to "existing PDU session"; 2) if the previously allocated home address information for a PDN connection consists of an IPv4 address only for an ePDG connected to EPC according to 3GPP TS 24.302[ Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networks; Stage 3 ] [16], the PDU session type shall be set to "IPv4"; 3) if the previously allocated home address information for a PDN connection consists of an IPv6 prefix only for an ePDG connected to EPC according to 3GPP TS 24.302[ Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networks; Stage 3 ] [16], the PDU session type shall be set to "IPv6"; 4) if the previously allocated home address information for a PDN connection consists of both an IPv4 address and an IPv6 prefix for an ePDG connected to EPC according to 3GPP TS 24.302[ Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networks; Stage 3 ] [16], the PDU session type shall be set to "IPv4v6"; 5) the APN of the PDN connection shall be mapped to the DNN of the PDU session; 6) the PDU session ID shall be set to the PDU session identity in the N1_MODE_CAPABILITY Notify payload of the IKE_AUTH request message establishing IPsec tunnel of the PDN connection; and 7) if the PDN connection is not for emergency bearer services, the S-NSSAI of the PDU session shall be set to the S-NSSAI associated with the PDN connection as specified in 3GPP TS 24.302[ Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networks; Stage 3 ] [16]. The UE shall not request to perform handover of an existing PDN connection to N1 mode if the associated S-NSSAI is not included in the allowed NSSAI for 3GPP access. If an existing PDU session is transferred from 3GPP access to an ePDG connected to EPC connection and that existing PDU session is associated with one or more MBS sessions, the UE shall locally leave the associated multicast MBS sessions and the SMF shall consider the UE as removed from the associated multicast MBS sessions.

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

21.2.4 QoE Measurement Handling in RRC_IDLE and RRC_INACTIVE States

If the UE enters RRC_INACTIVE, the UE AS configuration for the QoE is stored in the UE Inactive AS context. If the UE enters RRC_IDLE state, the UE releases all application layer measurement configurations except the application layer configurations explicitly indicated by the gNB as applicable in RRC_IDLE and RRC_INACTIVE states. For application measurement configurations applicable in RRC_IDLE and RRC_INACTIVE states, the UE continues on-going QoE measurement collection when entering RRC_IDLE or RRC_INACTIVE state, and also when returning to RRC_CONNECTED state. The UE may also start QoE collection according to the stored QoE configuration while in RRC_IDLE or RRC_INACTIVE state. The UE keeps the application layer measurement configurations but does not start new QoE sessions when it is outside of the area scope for QoE configurations in RRC_IDLE and/or RRC_INACTIVE state. The UE stores the application layer measurement reports generated while in RRC_IDLE and/or RRC_INACTIVE state in the AS layer. The gNB can retrieve the application layer measurement reports/configurations and session status indication by configuring SRB4 or SRB5 after it receives application layer measurement reports/configurations availability indication. The UE can send idle/inactive application layer measurement reports to the gNB only when it has moved to RRC_CONNECTED state due to other reasons. Upon UE's transition from RRC_IDLE to RRC_CONNECTED, the gNB serving the UE should ensure that it does not release an already configured signalling-based QoE measurement configuration for the sake of configuring a new management-based QoE measurement configuration.

3GPP TS 38.300

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

RAN2

3GPP Series : 38 , Radio technology beyond LTE

21.2.4

4.7.4 Limited service state over non-3GPP access

There are a number of situations in which the UE is unable to obtain normal service from a PLMN over non-3GPP access and the UE enters the limited service state over non-3GPP access. These include: a) no USIM in the ME; b) an "illegal UE" or "illegal ME" is received when registration, network-initiated de-registration or service request is performed (any USIM in the ME is then considered "invalid"); c) a "5GS services not allowed" is received when a registration, network-initiated de-registration or service request is performed; d) a "PLMN not allowed" is received when registration, network-initiated de-registration or service request is performed; e) a "Tracking area not allowed" is received when a registration, network-initiated de-registration or service request is performed; f) a "Roaming not allowed in this tracking area" is received when a registration, network-initiated de-registration or service request is performed; g) void; or h) a "Serving network not authorized" is received when a registration or service request is performed. In limited service state with a valid USIM in the UE, the network selection is performed as defined in 3GPP TS 24.502[ Access to the 3GPP 5G Core Network (5GCN) via non-3GPP access networks ] [18]. With the exception of performing initial registration for emergency services, no registration requests are made until a valid USIM is present. For registration for emergency services, the PLMN of the current N3IWF or TNGF is considered as the selected PLMN for the duration the UE is registered for emergency services.

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

6.8A.1 EPDCCH formats

The enhanced physical downlink control channel (EPDCCH) carries scheduling assignments. An enhanced physical downlink control channel is transmitted using an aggregation of one or several consecutive enhanced control channel elements (ECCEs) where each ECCE consists of multiple enhanced resource element groups (EREGs), defined in clause 6.2.4A. The number of ECCEs used for one EPDCCH depends on the EPDCCH format as given by Table 6.8A.1-2 and the number of EREGs per ECCE is given by Table 6.8A.1-1. Both localized and distributed transmission is supported. An EPDCCH can use either localized or distributed transmission, differing in the mapping of ECCEs to EREGs and PRB pairs. A UE shall monitor multiple EPDCCHs as defined in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4]. One or two sets of physical resource-block pairs which a UE shall monitor for EPDCCH transmissions can be configured. All EPDCCH candidates in EPDCCH set use either only localized or only distributed transmission as configured by higher layers. Within EPDCCH set in subframe , the ECCEs available for transmission of EPDCCHs are numbered from 0 to and ECCE number corresponds to - EREGs numbered in PRB index for localized mapping, and - EREGs numbered in PRB indices for distributed mapping, where , is the number of EREGs per ECCE, and is the number of ECCEs per resource-block pair. The physical resource-block pairs constituting EPDCCH set are in this paragraph assumed to be numbered in ascending order from 0 to . Table 6.8A.1-1: Number of EREGs per ECCE, Table 6.8A.1-2: Supported EPDCCH formats Case A in Table 6.8A.1-2 is used when the conditions corresponding to case 1 in clause 9.1.4 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4] are satisfied, otherwise case B is used. The quantity for a particular UE and referenced in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4] is defined as the number of downlink resource elements available for EPDCCH transmission in a physical resource-block pair configured for possible EPDCCH transmission of EPDCCH set and fulfilling all of the following criteria: - they are part of any one of the 16 EREGs in the physical resource-block pair, and - they are assumed by the UE not to be used for cell-specific reference signals, where the positions of the cell-specific reference signals are given by clause 6.10.1.2 with the number of antenna ports for and the frequency shift of cell-specific reference signals derived as described in clause 6.10.1.2 unless other values for these parameters are provided by clause 9.1.4.3 in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4], and- - they are assumed by the UE not to be used for transmission of CSI reference signals, where the positions of the CSI reference signals are given by clause 6.10.5.2 with the configuration for zero power CSI reference signals obtained as described in clause 6.10.5.2 unless other values are provided by clause 9.1.4.3 in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4], and with the configuration for non-zero power CSI reference signals obtained as described in clause 6.10.5.2, and - for frame structure type 1 and 2, the index in the first slot in a subframe fulfils where is given by clause 9.1.4.1 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4], and - for frame structure type 3, - if the higher layer parameter subframeStartPosition indicates 's07' and if the downlink transmission starts in the second slot of a subframe - the index in the second slot in the subframe fulfils where is given by clause 9.1.4.1 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4], - otherwise - the index in the first slot in the subframe fulfils where is given by clause 9.1.4.1 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4].

3GPP TS 36.211

Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation

RAN1

3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology

6.8A.1

4.4.2.4 Change of security keys

When the MME initiates a re-authentication to create a new EPS security context, the messages exchanged during the authentication procedure are integrity protected and ciphered using the current EPS security context, if any. Both UE and MME shall continue to use the current EPS security context, until the MME initiates a security mode control procedure. The SECURITY MODE COMMAND message sent by the MME includes the eKSI of the new EPS security context to be used. The MME shall send the SECURITY MODE COMMAND message integrity protected with the new EPS security context, but unciphered. When the UE responds with a SECURITY MODE COMPLETE, it shall send the message integrity protected and ciphered with the new EPS security context. The MME can also modify the current EPS security context or take the non-current native EPS security context, if any, into use, by sending a SECURITY MODE COMMAND message including the eKSI of the EPS security context to be modified and including a new set of selected NAS security algorithms. In this case the MME shall send the SECURITY MODE COMMAND message integrity protected with the modified EPS security context, but unciphered. When the UE replies with a SECURITY MODE COMPLETE message, it shall send the message integrity protected and ciphered with the modified EPS security context.

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

A.24 Monitoring of SCell scheduling on PUCCH in Carrier Aggregation

In the deployment scenarios for carrier aggregation as depicted in 3GPP 36.300 [12], the number of possible SCell per PCell can be multiple and not fixed. So the PUCCH resource for the Scell scheduling needs to be properly allocated, because: - Over-dimensioned PUCCH causes high overhead and results in reduced UL throughput is (in general UL is not used efficiently); - Under-dimensioned PUCCH will result in reduced DL throughput (if no PUCCH format 1bCS or format 3 ACK/NACK resource is available, PDSCH cannot be allocated by the PDCCH for the SCell(s) and the UE cannot be allocated resources on its SCell(s)). Thus, the SCell scheduling success/blocking rate on PUCCH needs to be monitored for evaluation of control channel usage in CA. When needed OAM can also provide the guidance or take action to the eNB to optimize the PUCCH dimension for CA.

3GPP TS 32.425

Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN)

SA WG5

3GPP Series : 32 , OAM&P and Charging

A.24

8.2.1.3.1A Soft buffer management test

For CA, the requirements are specified in Table 8.2.1.3.1A-2, with the addition of the parameters in Table 8.2.1.3.1A-1 and the downlink physical channel setup according to Annex C.3.2. The purpose is to verify the UE performance with proper instantaneous buffer implementation. The test points are applied to UE category and bandwidth combination with maximum aggregated bandwidth as specified inTable 8.2.1.3.1A-3. Table 8.2.1.3.1A-1: Test Parameters for soft buffer management test (FRC) for CA Table 8.2.1.3.1A-2: Minimum performance soft buffer management test (FRC) for CA Table 8.2.1.3.1A-3: Test points for soft buffer management tests for CA

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

A.22 KTIPSec and KTNAP derivation function

When deriving a KTIPSec from KTNGF and when deriving a KTNAP from KTWIF or KTNGF the following parameters shall be used to form the input S to the KDF. - FC = 0x84 - P0 = Usage type distinguisher - L0 = length of Usage type distinguisher (i.e. 0x00 0x01) The values for the Usage type distinguisher are defined in table A.22-1. The values 0x00 and 0x03 to 0xf0 are reserved for future use, and the values 0xf1 to 0xff are reserved for private use. The Usage type distinguisher shall be set to the value for IPSec (0x01) when deriving KTIPSec. The Usage type distinguisher shall be set to the value for TNAP (0x02) when deriving KTNAP. The input key KEY shall be the 256-bit KTNGF or KTWIF. Table A.22-1: Usage type distinguishers

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

A.22

5.4.1.2.2 EAP-AKA' related procedures

5.4.1.2.2.1 General The UE shall support acting as EAP-AKA' peer as specified in IETF RFC 5448 [40]. The AUSF may support acting as EAP-AKA' server as specified in IETF RFC 5448 [40]. The AAA server of the Credentials Holder (CH) or the Default Credentials Server (DCS) may support acting as EAP-AKA' server as specified in IETF RFC 5448 [40]. The EAP-AKA' enables mutual authentication of the UE and the network. The UE can reject the EAP-request/AKA'-challenge message sent by the network. The UE shall proceed with an EAP-request/AKA'-challenge message only if a USIM is present. During a successful EAP based primary authentication and key agreement procedure, the CK and IK are computed by the USIM. CK and IK are then used by the ME as key material to generate an EMSK or MSK. 5.4.1.2.2.2 Initiation In order to initiate the EAP based primary authentication and key agreement procedure using EAP-AKA', the AUSF or the AAA server of the CH or the DCS shall send an EAP-request/AKA'-challenge message as specified in IETF RFC 5448 [40]. The AUSF or the AAA server of the CH or the DCS shall set the AT_KDF_INPUT attribute of the EAP-request/AKA'-challenge message to the SNN. The SNN is in format described in subclause 9.12.1. The AUSF or the AAA server of the CH or the DCS may include AT_RESULT_IND attribute in the EAP-request/AKA'-challenge message. 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. Upon receiving an EAP-request/AKA'-challenge message, the UE shall check whether the UE has a USIM, shall check the key derivation function indicated in AT_KDF attributes as specified in IETF RFC 5448 [40], and if the value of the Key derivation function field within the received AT_KDF attribute, is of value 1, shall check: a) whether the network name field of the AT_KDF_INPUT attribute is the SNN constructed according to subclause 9.12.1; and b) whether the network name field of the AT_KDF_INPUT attribute matches the PLMN identity or the SNPN identity of the selected SNPN saved in the UE. When not operating in SNPN access operation mode, the PLMN identity the UE uses for the above network name check is as follows: a) when the UE moves from 5GMM-IDLE mode to 5GMM-CONNECTED mode, until the first handover, the UE shall use the PLMN identity of the selected PLMN; and b) after handover or inter-system change to N1 mode in 5GMM-CONNECTED mode: 1) if the target cell is not a shared network cell, the UE shall use the PLMN identity received as part of the broadcast system information; 2) if the target cell is a shared network cell and the UE has a valid 5G-GUTI, the UE shall use the PLMN identity that is part of the 5G-GUTI; and 3) if the target cell is a shared network cell and the UE has a valid 4G-GUTI, but not a valid 5G-GUTI, the UE shall use the PLMN identity that is part of the 4G-GUTI. When operating in SNPN access operation mode, the SNPN identity the UE uses for the above network name check is the SNPN identity of the selected SNPN. 5.4.1.2.2.3 UE successfully authenticates network If a USIM is present and the SNN check is successful, the UE shall handle the EAP-request/AKA'-challenge message as specified in IETF RFC 5448 [40]. The USIM shall derive CK and IK and compute the authentication response (RES) using the 5G authentication challenge data received from the ME, and pass RES to the ME. The ME shall derive CK' and IK' from CK and IK, and if the UE operates in SNPN access operation mode and the credentials in the USIM contain an indication to use MSK for derivation of KAUSF after success of primary authentication and key agreement procedure then derive MSK from CK' and IK' otherwise derive EMSK from CK' and IK'. NOTE 1: When the UE is registering or registered for onboarding services in SNPN, credentials in the USIM do not contain an indication to use MSK for derivation of KAUSF after success of primary authentication and key agreement procedure. Furthermore, if the UE operates in SNPN access operation mode and the credentials in the USIM 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/AKA'-challenge 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/AKA'-challenge 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, and shall send an EAP-response/AKA'-challenge message as specified in IETF RFC 5448 [40]. NOTE 2: 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. If the EAP-request/AKA'-challenge message contains AT_RESULT_IND attribute, the UE may include AT_RESULT_IND attribute in the EAP-response/AKA'-challenge message as specified in IETF RFC 5448 [40]. 5.4.1.2.2.4 Errors when handling EAP-request/AKA'-challenge message If a USIM is present, the SNN check fails or the UE does not accept AUTN during handling of the EAP-request/AKA'-challenge message as specified in IETF RFC 5448 [40], the UE shall send an EAP-response/AKA'-authentication-reject message as specified in IETF RFC 5448 [40]. If a USIM is present, the SNN check is successful but the UE detects that the sequence number in AUTN is not correct during handling of the EAP-request/AKA'-challenge message as specified in IETF RFC 5448 [40], the UE shall send an EAP-response/AKA'-synchronization-failure message as specified in IETF RFC 5448 [40]. If a USIM is present, the SNN check is successful, the sequence number in AUTN is correct and the UE detects another error during handling of the EAP-request/AKA'-challenge message as specified in IETF RFC 5448 [40], the UE shall send an EAP-response/AKA'-client-error message as specified in IETF RFC 5448 [40]. If a USIM is not present, the UE shall send an EAP-response/AKA'-client-error message as specified in IETF RFC 5448 [40]. For any of the above, 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 timers T3510, T3517 or T3521 (if they were running). Upon receiving an AUTHENTICATION REQUEST message with the EAP message IE containing an EAP-request/AKA'-challenge from the network, the UE shall stop timer T3520, if running, and then process the EAP-request/AKA'-challenge information as normal. 5.4.1.2.2.5 Network successfully authenticates UE Upon reception of the EAP-response/AKA'-challenge message, if procedures for handling an EAP-response/AKA'-challenge message as specified in IETF RFC 5448 [40] are successful and: a) the AUSF acts as the EAP-AKA' server, the AUSF shall generate EMSK, 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]; or b) the AAA server of the CH or the DCS acts as the EAP-AKA' 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]; and: a) if the AUSF or the AAA server of the CH or the DCS included the AT_RESULT_IND attribute in the EAP-request/AKA'-challenge message and the AT_RESULT_IND attribute is included in the corresponding EAP-response/AKA'-challenge message, the AUSF or the AAA server of the CH or the DCS shall send an EAP-request/AKA'-notification message as specified in IETF RFC 5448 [40]; or b) if the AUSF or the AAA server of the CH or the DCS: 1) included the AT_RESULT_IND attribute in the EAP-request/AKA'-challenge message and the AT_RESULT_IND attribute is not included in the EAP-response/AKA'-challenge message; or 2) did not include the AT_RESULT_IND attribute in the EAP-request/AKA'-challenge message; then the AUSF or the AAA server of the CH or the DCS shall send an EAP-success message as specified in IETF RFC 5448 [40] and shall consider the procedure complete. NOTE 1: When the AAA server of the CH or the DCS acts as the EAP-AKA' server, 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 2: 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. 5.4.1.2.2.6 UE handling EAP-AKA' notification message Upon receiving an EAP-request/AKA'-notification message, the UE shall send an EAP-response/AKA'-notification message as specified in IETF RFC 5448 [40]. 5.4.1.2.2.6A EAP based Identification initiation by the network If the AUSF or the AAA server of the CH or the DCS decides to initiate the EAP based identification procedure, the AUSF or the AAA server of the CH or the DCS shall send an EAP-Request/Identity or EAP-Request/AKA'-Identity message as specified in IETF RFC 5448 [40]. The AMF shall encapsulate the EAP-Request/Identity or EAP-Request/AKA'-Identity message in the AUTHENTICATION REQUEST message and send it to the UE. 5.4.1.2.2.6B EAP based Identification response by the UE Upon receipt of the AUTHENTICATION REQUEST message with EAP-Request/Identity message the UE shall send an AUTHENTICATION RESPONSE message with EAP-Response/Identity to the network. In the EAP-Response/Identity message, the UE shall provide the requested identity according to 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24] annex F.2, in the UE identity in the EAP-Response/Identity message as specified in IETF RFC 5448 [40]. Upon receipt of the AUTHENTICATION REQUEST message with EAP-Request/AKA'-Identity message the UE shall send an AUTHENTICATION RESPONSE message with EAP-Response/AKA'-Identity to the network. Based on the attribute received in the EAP-Request/AKA'-Identity, the UE shall provide the requested identity according to 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24] annex F.2, in the EAP-Response/AKA'-Identity message, as specified in IETF RFC 5448 [40]. If the EAP-Request/AKA'-Identity carries the AT_PERMANENT_REQ, the UE shall respond with EAP-Response/AKA'-Client-Error with the error code "unable to process packet". 5.4.1.2.2.7 Network sending EAP-success message Upon reception of the EAP-response/AKA'-notification message, if earlier procedures for handling an EAP-request/AKA'-challenge message as specified in IETF RFC 5448 [40] were successful, the AUSF or the AAA server of the CH or the DCS shall send an EAP-success message as specified in IETF RFC 5448 [40] and shall consider the procedure complete. NOTE: The AUSF provides the KSEAF to the SEAF. Upon reception of the KSEAF, the SEAF generates the KAMF based on the ABBA and the KSEAF 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. 5.4.1.2.2.8 UE handling EAP-success message 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 as described in subclause 5.4.1.2.2.3: 1) if the UE operates in SNPN access operation mode and the credentials in the USIM 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; NOTE: When the UE is registering or registered for onboarding services in SNPN, credentials in the USIM do not contain an indication to use MSK for derivation of KAUSF after success of primary authentication and key agreement procedure. 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 new 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, and 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. 5.4.1.2.2.9 Network not successfully authenticates UE Upon reception of the EAP-response/AKA'-challenge message, if procedures for handling an EAP-response/AKA'-challenge message as specified in IETF RFC 5448 [40] are not successful, the AUSF or the AAA server of the CH or the DCS shall send an EAP-request/AKA'-notification message that implies failure as specified in IETF RFC 5448 [40]. 5.4.1.2.2.10 Network sending EAP-failure message Upon reception of the EAP-response/AKA'-notification message, if earlier procedures for handling an EAP-request/AKA'-challenge message as specified in IETF RFC 5448 [40] were not successful, the AUSF or the AAA server of the CH or the DCS shall send an EAP-failure message as specified in IETF RFC 5448 [40] and shall consider the procedure complete. If the authentication response (RES) returned by the UE in the AT_RES attribute of the EAP-response/AKA'-challenge message is not valid, 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 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. Depending on local requirements or operator preference for emergency services, if the UE initiates a registration procedure with 5GS registration type IE set to "emergency registration" and the AMF is configured to allow emergency registration without user identity, the AMF needs not follow the procedures specified for transporting the EAP-failure message in the AUTHENTICATION REJECT message of the EAP result message transport procedure in the present subclause. The AMF may include the EAP-failure message in a response of the current 5GMM specific procedure or in the AUTHENTICATION RESULT of the EAP result message transport procedure. 5.4.1.2.2.11 UE handling EAP-failure message 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 as described in subclause 5.4.1.2.2.3. The UE shall consider the procedure complete. If the EAP-failure message is received in an AUTHENTICATION REJECT message: 1) if the AUTHENTICATION REJECT message has been successfully integrity checked by the NAS: - 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 PLMN, the USIM shall be considered invalid until switching off the UE or the UICC containing the USIM is removed. 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. Additionally, the UE shall consider the USIM as invalid for the current SNPN until switching off or the UICC containing the USIM is removed. 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. Additionally, the UE shall consider the USIM as invalid for the entry until switching off or the UICC containing the USIM is removed. 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]; - if the UE is neither registered for onboarding services in SNPN nor performing initial registration for onboarding services in SNPN, the UE shall set: i) the counter for "SIM/USIM considered invalid for GPRS services" events, the counter for "USIM considered invalid for 5GS services over non-3GPP access" events, and the counter for "SIM/USIM considered invalid for non-GPRS services" events if maintained by the UE, in case of PLMN; or ii) 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 - if the UE is operating in single-registration mode, the UE shall handle EMM parameters, 4G-GUTI, last visited registered TAI, TAI list and eKSI as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] for the case when the authentication procedure is not accepted by the network. The USIM shall be considered as invalid also for non-EPS services until switching off or the UICC containing the USIM is removed; and 2) 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: a) if the AUTHENTICATION REJECT message is received over 3GPP access, and the counter for "SIM/USIM considered invalid for GPRS services" events in case of PLMN or the counter for "the entry for the current SNPN considered invalid for 3GPP access" events in case of SNPN has a value less than a UE implementation-specific maximum value, proceed as specified in subclause 5.3.20, list item 1)-a) of subclause 5.3.20.2 (if the UE is not operating in SNPN access operation mode) or list item a)-1) of subclause 5.3.20.3 (if the UE is operating in SNPN access operation mode) for the case that the 5GMM cause value received is #3; b) if the AUTHENTICATION REJECT message is received over non-3GPP access, and the counter for "USIM considered invalid for 5GS services over non-3GPP access" events in case of PLMN or the counter for "the entry for the current SNPN considered invalid for non-3GPP access" events in case of SNPN has a value less than a UE implementation-specific maximum value, proceed as specified in subclause 5.3.20, list item 1)-b) of subclause 5.3.20.2 (if the UE is not operating in SNPN access operation mode) or list item a)-2) of subclause 5.3.20.3 (if the UE is operating in SNPN access operation mode) for the case that the 5GMM cause value received is #3; c) 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 PLMN, the UE shall consider the USIM as invalid for 5GS services via 3GPP access and invalid for non-EPS service until switching off the UE or the UICC containing the USIM is removed. 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 UE shall consider the entry of the "list of subscriber data" with the SNPN identity of the current SNPN as invalid for 3GPP access until the UE is switched off or the entry is updated. Additionally, the UE shall consider the USIM as invalid for the current SNPN via 3GPP access until switching off or the UICC containing the USIM is removed. 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 for 3GPP access until the UE is switched off or the entry is updated. Additionally, the UE shall consider the USIM as invalid for the entry via 3GPP access until switching off or the UICC containing the USIM is removed. - The UE shall set: - the counter for "SIM/USIM considered invalid for GPRS services" events and the counter for "SIM/USIM considered invalid for non-GPRS services" events if maintained by the UE, in case of PLMN; or - the counter for "the entry for the current SNPN considered invalid for 3GPP access" events in case of SNPN; to UE implementation-specific maximum value. - If the UE is operating in single-registration mode, the UE shall handle 4G-GUTI, TAI list and eKSI as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] for the case when the authentication procedure is not accepted by the network. The USIM shall be considered as invalid also for non-EPS services until switching off or the UICC containing the USIM is removed; 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; - in case of PLMN, the UE shall consider the USIM as invalid for 5GS services via non-3GPP access until switching off the UE or the UICC containing the USIM is removed. In case of SNPN, the UE shall consider the entry of the "list of subscriber data" with the SNPN identity of the current SNPN as invalid for non-3GPP access until the UE is switched off or the entry is updated. Additionally, the UE shall consider the USIM as invalid for the current SNPN and for non-3GPP access until switching off or the UICC containing the USIM is removed; and - the UE shall set: - the counter for "USIM considered invalid for 5GS services over non-3GPP access" events to UE implementation-specific maximum value in case of PLMN; or - the counter for "the entry for the current SNPN considered invalid for non-3GPP access" events to UE implementation-specific maximum value in case of SNPN. If the UE is registered for onboarding services in SNPN or performing initial registration for onboarding services in SNPN, the UE shall: a) 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 b) 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. 5.4.1.2.2.12 Abnormal cases in the UE The following abnormal cases can be identified: a) EAP-request/AKA'-challenge message with the key derivation function indicated in AT_KDF attributes set to a value other than 1. The UE shall act as specified in IETF RFC 5448 [40] subclause 3.2 for the case when the AUTN had been incorrect.

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

6.8.1.4 R99+ ME

Release 99+ ME that has UTRAN radio capability shall support the USIM-ME interface as specified in TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [20]. Rel4- ME that has no UTRAN radio capabilities may support the USIM-ME interface as specified in TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [20]. Rel5+ ME that has no UTRAN radio capabilities shall support the USIM-ME interface as specified in TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [20]. A ME capable of UMTS AKA with a USIM active and attached to a UTRAN shall only participate in UMTS AKA and shall not participate in GSM AKA. A ME capable of UMTS AKA with a USIM active and attached to a GSM BSS shall participate in UMTS AKA and may participate in GSM AKA. Participation in GSM AKA is required to allow registration in a R98- VLR/SGSN. However, the use of GSM AKA in the MS shall be disabled on a particular visited network if instructed to do so by the USIM application. The mechanism is based on an EF ‘Disabled Authentications’ in the USIM application containing the unauthorized authentication methods per visited network. If the EF ‘Disabled Authentications’ is present and active, then the authentication methods marked as disabled shall not be used by the MS in the corresponding visited network. The disabled authentication method may be defined on a global, per country or per network basis. The relevant file in the USIM application is managed by the home operator based on information supplied to the home operator by the visited network. NOTE 1: It is possible for an attacker to spoof a PLMN id and therefore force the UE to use GSM AKA. This could be mitigated by the UE displaying the country name to the user. Displaying the country name is typically not done by today’s UEs and would have to be added as a new UE function. It should be further noted that the network name displayed to the user could be spoofed by an attacker as the displayed network name may not be based on MCC, MNC received via cell broadcast, but on additional signalling. NOTE 2: A similar mechanism to enforce the use of particular encryption algorithm(s) in a given network is described in clause 4.9 in TS 43.020[ Security related network functions ] . Editor's note: It is FFS whether disabling GSM AKA on a per network basis successfully achieves the intention of mitigating attacks by false basestations. A ME that not capable of UMTS AKA with a USIM active can only participate in GSM AKA. The execution of UMTS AKA results in the establishment of a UMTS security context; the UMTS cipher/integrity keys CK and IK and the key set identifier KSI are passed to the ME. If the USIM supports conversion function c3 and/or GSM AKA, the ME shall also receive a 64-bit GSM cipher key Kc derived at the USIM. If the ME supports 128-bit ciphering algorithms A5 and/or GEA for GSM, the ME shall also support the key derivation function for Kc128 as specified in annex B.5.The execution of GSM AKA results in the establishment of a GSM security context; the 64-bit GSM cipher key Kc and the cipher key sequence number CKSN are stored in the ME.

3GPP TS 33.102

3G security; Security architecture

SA WG3

3GPP Series : 33 , Security aspects

6.8.1.4

5.2.6.32.4 Nnef_MemberUESelectionAssistance_Notify service operation

Service operation name: Nnef_MemberUESelectionAssistance_Notify Description: NEF reports the Member UE selection assistance information to the consumer that has previously subscribed. Inputs, Required: Notification Correlation Information. Inputs, Conditional Required: At least one of the following inputs is required: - One or more list(s) of candidate UEs in the form of a list of GPSIs or a list of UE IP addresses. Inputs, Optional: Recommended time window for performing the application operation per list of candidate UEs as described in clause 4.15.13.1, specific values of the parameters that NEF gathered for the Member UE filtering criteria per candidate UE, a number for each filtering criterion that indicates the amount of UEs in the initial list which do not meet the criterion. NOTE: This number can be an indication for AF to revise the corresponding filtering criterion. Outputs, Required: Operation execution result indication.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

5.2.6.32.4

5.2.2.4 Substate when back to state 5GMM-DEREGISTERED from another 5GMM state

When returning to state 5GMM-DEREGISTERED, the UE shall select a cell as specified in 3GPP TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [28] or 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [25C]. The substate depends on the result of the cell selection procedure, the outcome of the previously performed 5GMM specific procedures, on the 5GS update status of the UE, on the tracking area data stored in the UE, on the presence of the USIM, on the UE configuration and on the reason for moving to 5GMM-DEREGISTERED: a) If no cell has been found, the substate is NO-CELL-AVAILABLE, until a cell is found; b) If no USIM is present or if the inserted USIM is considered invalid by the UE, the substate shall be NO-SUPI; c) If a suitable cell has been found and the PLMN or tracking area is not in one of the forbidden lists, the substate shall be NORMAL-SERVICE; d) If an initial registration shall be performed (e.g. network-requested re-registration), the substate shall be ATTEMPTING-REGISTRATION; e) If a PLMN reselection or SNPN reselection (according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]) is needed, the substate shall be PLMN-SEARCH; f) If the selected cell is known not to be able to provide normal service, the substate shall be LIMITED-SERVICE; and g) If the UE is configured for eCall only mode as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [22], T3444 and T3445 have expired or are not running, and substate PLMN-SEARCH is not required, the substate shall be eCALL-INACTIVE.

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

9.11.4.26 UE-DS-TT residence time

The purpose of the UE-DS-TT residence time information element is to signal the time taken within the UE and the DS-TT to forward a packet i.e. between the ingress of the UE and the DS-TT port in the DL direction, or between the DS-TT port and the egress of the UE in the UL direction. The UE- DS-TT residence time information element is coded as shown in figure 9.11.4.26.1 and table 9.11.4.26.1. The UE-DS-TT residence time is a type 4 information element with a length of 10 octets. Figure 9.11.4.26.1: UE-DS-TT residence time information element Table 9.11.4.26.1: UE-DS-TT residence time information element

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

9.11.4.26

13.3.6 Authentication and authorization between SCP and network functions

The SCP and network functions shall use one of the following methods described in clause 13.1 to mutually authenticate each other before service layer messages can be exchanged on that interface: - If the PLMN uses protection at the transport layer, authentication provided by the transport layer protection solution shall be used for mutual authentication of the SCP and the network functions. - If the PLMN does not use protection at the transport layer, mutual authentication of the SCP and network functions may be implicit by NDS/IP or physical security. Authentication between the SCP and the Network Function may be implicit by co-location. Authorization between the SCP and NFs is based on local authorization policy. Regarding the authorization of access token requests sent by an SCP on behalf of an NF Service Consumer, NOTE 3 in clause 13.3.1.2 applies.

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

13.3.6

6.1.3.13 Recommended bit rate MAC Control Element

The recommended bit rate MAC control element is identified by a MAC PDU subheader with LCID as specified in tables 6.2.1-1 and 6.2.1-2 for bit rate recommendation message from the eNB to the UE and bit rate recommendation query message from the UE to the eNB, respectively. It has a fixed size and consists of two octets defined as follows (figure 6.1.3.13-1): - LCID: This field indicates the identity of the logical channel (as described in Table 6.1.3.13-2) for which the recommended bit rate or the recommended bit rate query is applicable. The length of the field is 4 bits; - Uplink/Downlink (UL/DL): This field indicates whether the recommended bit rate or the recommended bit rate query applies to uplink or downlink. The length of the field is 1 bit. The UL/DL field set to "0" indicates downlink. The UL/DL field set to "1" indicates uplink; - Bit Rate: This field indicates an index to Table 6.1.3.13-1. The length of the field is 6 bits. For bit rate recommendation the value indicates the recommended bit rate. For bit rate recommendation query the value indicates the desired bit rate; - X: Bit rate multiplier. For UEs supporting recommended bit rate multiplier, when bitRateMultiplier is configured for the logical channel indicated by LCID field, X field set to "1" indicates the actual value of bit rate is the value corresponding to the index indicated by the Bit Rate field multiplied by bitRateMultiplier as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]; - R: reserved bit, set to "0". Figure 6.1.3.13-1: Recommended bit rate MAC control element Table 6.1.3.13-1: Values (kbit/s) for Bit Rate field Table 6.1.3.13-2: Values of identity of the logical channel for LCID field

3GPP TS 36.321

Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification

RAN2

3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology

6.1.3.13

4.11.6.2 Unsubscribing to N11otification of availability or expected level of support of a service API

Figure 4.11.6.2 1 represent the information flow unsubscribing to Continuous report type subscription of the availability or expected level of support of a service API. If the AF invokes Nnef_APISupportCapability_Subscribe service to SCEF+NEF node with the Duration of Reporting parameter for Continuous report type, the subscription on the SCEF+NEF and HSS+UDM are implicitly unsubscribed if the Duration of Reporting timer expires, i.e. the explicit unsubscribe service operation is not needed. If the explicit unsubscribe operation is needed, the information flow is as follows. Figure 4.11.6.2 1: Unsubscribing to notification of the availability or expected level of support of a service API 1. The AF unsubscribes to Nnef_APISupportCapability service for a UE or a group of UEs by sending APISupportCapability_Unsubscribe Request (UE ID or External Group ID) message. 2. If SCEF+NEF has subscribed to CN Type Change Event for the indicated UE or the indicated group of UEs, SCEF+NEF unsubscribes the CN Type Change Event by sending Ndum_EventExposure_Unsubscribe Request (CN Type Change, UE ID or External Group ID) message to HSS+UDM. 3. HSS+UDM deletes the CN Type Change Event subscription for the indicated UE or the indicated group of UEs, HSS+UDM responses to the SCEF+NEF by sending Ndum_EventExposure_Unsubscribe Response (Operation execution result indication) message. 4. If result indication indicates the operation is successful, the SCEF+NEF deletes the subscription to Nnef_APISupportCapability service. SCEF+NEF acknowledges the operation result by sending Nnef_APISupportCapability_Unsubscribe Response (Operation execution result indication) to AF.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.11.6.2

5.9.2.3 NEF security requirements

The Network Exposure Function (NEF) supports external exposure of capabilities of Network Functions to Application Functions, which interact with the relevant Network Functions via the NEF. The interface between the NEF and the Application Function shall fulfil the following requirements: - Integrity protection, replay protection and confidentiality protection for communication between the NEF and Application Function shall be supported. - Mutual authentication between the NEF and Application Function shall be supported. - Internal 5G Core information such as DNN, S-NSSAI etc., shall not be sent outside the 3GPP operator domain. - SUPI shall not be sent outside the 3GPP operator domain by NEF. The NEF shall be able to determine whether the Application Function is authorized to interact with the relevant Network Functions..

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

5.9.2.3

5.5.1.2.5 Attach not accepted by the network

If the attach request cannot be accepted by the network, the MME shall send an ATTACH REJECT message to the UE including an appropriate EMM cause value. If EMM-REGISTERED without PDN connection is not supported by the UE or the MME, the attach request included a PDN CONNECTIVITY REQUEST message, the attach procedure fails due to: - a default EPS bearer setup failure; - an ESM procedure failure; or - operator determined barring is applied on default EPS bearer context activation during attach procedure, the MME shall: - combine the ATTACH REJECT message with a PDN CONNECTIVITY REJECT message contained in the ESM message container information element. In this case the EMM cause value in the ATTACH REJECT message shall be set to #19 "ESM failure"; or - send the ATTACH REJECT message with the EMM cause set to #15 "No suitable cells in tracking area", if the PDN connectivity reject is due to ESM cause #29 subject to operator policies (see 3GPP TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [16D] for further details). In this case, the network may additionally include the Extended EMM cause IE with value "E-UTRAN not allowed". If the attach request is rejected due to NAS level mobility management congestion control, the network shall set the EMM cause value to #22 "congestion" and assign a value for back-off timer T3346. In NB-S1 mode, if the attach request is rejected due to operator determined barring (see 3GPP TS 29.272[ Evolved Packet System (EPS); Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol ] [16C]), the network shall set the EMM cause value to #22 "congestion" and assign a value for back-off timer T3346. If the attach request is rejected due to service gap control as specified in clause 5.3.17 i.e. the T3447 timer is running, the network shall set the EMM cause value to #22 "congestion" and may assign a back-off timer T3346 with the remaining time of the running T3447 timer. If the attach request is rejected due to incompatibility between the CIoT EPS optimizations supported by the UE and what the network supports and the network sets the EMM cause value to #15 "no suitable cells in tracking area", the network may additionally include the Extended EMM cause IE with value "requested EPS optimization not supported". NOTE 1: How the UE uses the Extended EMM cause IE with value "requested EPS optimization not supported" is implementation specific. The UE still behaves according to the EMM cause value #15. Based on operator policy, if the attach request is rejected due to core network redirection for CIoT optimizations, the network shall set the EMM cause value to #31 "Redirection to 5GCN required". NOTE 2: The network can take into account the UE's N1 mode capability, the 5GS CIoT network behaviour supported by the UE or the 5GS CIoT network behaviour supported by the 5GCN to determine the rejection with the EMM cause value #31 "Redirection to 5GCN required". In NB-S1 mode or WB-S1 mode via satellite E-UTRAN access, if the attach request is from a UE via a satellite E-UTRA cell and the network using the User Location Information provided by the eNodeB (see 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [23]), is able to determine that the UE is in a location where the network is not allowed to operate, the network shall set the EMM cause value in the ATTACH REJECT message to #78 "PLMN not allowed to operate at the present UE location". Upon receiving the ATTACH REJECT message, if the message is integrity protected or contains a reject cause other than EMM cause value #25, the UE shall stop timer T3410. If the ATTACH REJECT message with EMM cause #25 or #78 was received without integrity protection, then the UE shall discard the message. If the MME received multiple TAIs from the satellite E-UTRAN as described in 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10], and determines that, by UE subscription and operator's preferences, all of the received TAIs are forbidden for roaming or for regional provision of service, the MME shall include the TAI(s) in: a) the Forbidden TAI(s) for the list of "forbidden tracking areas for roaming" IE; b) the Forbidden TAI(s) for the list of "forbidden tracking areas for regional provision of service" IE; or c) both, in the ATTACH REJECT message. Regardless of the EMM cause value received in the ATTACH REJECT message, - if the UE receives the Forbidden TAI(s) for the list of "forbidden tracking areas for roaming" IE in the ATTACH REJECT message, the UE shall store the TAI(s) which are belonging to the serving PLMN or equivalent PLMN(s) included in the IE, if not already stored, into the list of "forbidden tracking areas for roaming" and ignore the TAI(s) which do not belong to the serving PLMN or equivalent PLMN(s); and - if the UE receives the Forbidden TAI(s) for the list of "forbidden tracking areas for regional provision of service" IE in the ATTACH REJECT message, the UE shall store the TAI(s) which are belonging to the serving PLMN or equivalent PLMN(s)included in the IE, if not already stored, into the list of "forbidden tracking areas for regional provision of service" and ignore the TAI(s) which do not belong to the serving PLMN or equivalent PLMN(s) Furthermore, the UE shall take the following actions depending on the EMM cause value received in the ATTACH REJECT message. #3 (Illegal UE); #6 (Illegal ME); or #8 (EPS services and non-EPS services not allowed); The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and eKSI. The UE shall consider the USIM as invalid for EPS services and non-EPS services until switching off or the UICC containing the USIM is removed or the timer T3245 expires as described in clause 5.3.7a. Additionally, the UE shall delete the list of equivalent PLMNs and enter state EMM-DEREGISTERED.NO-IMSI. If the message has been successfully integrity checked by the NAS and the UE maintains a counter for "SIM/USIM considered invalid for GPRS services", then the UE shall set this counter to UE implementation-specific maximum value. If the message has been successfully integrity checked by the NAS and the UE maintains a counter for "SIM/USIM considered invalid for non-GPRS services", then the UE shall set this counter to UE implementation-specific maximum value. If A/Gb mode or Iu mode is supported by the UE, the UE shall in addition handle the MM parameters update status, TMSI, LAI and ciphering key sequence number, and the GMM parameters GMM state, GPRS update status, P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the normal attach procedure is rejected with the GMM cause with the same value. For the EMM cause value #3 or #6, if the UE is operating in single-registration mode, the UE shall in addition handle the 5GMM parameters 5GMM state, 5GS update status, 5G-GUTI, last visited registered TAI, TAI list and ngKSI as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the initial registration procedure performed over 3GPP access is rejected with the 5GMM cause with the same value. For the EMM cause value #8, if the UE is operating in single-registration mode, the UE shall in addition set the 5GMM state to 5GMM-DEREGISTERED, 5GS update status to 5U3 ROAMING NOT ALLOWED, and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. NOTE 3: The possibility to configure a UE so that the radio transceiver for a specific RAT is not active, although it is implemented in the UE, is out of scope of the present specification. #7 (EPS services not allowed); The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and eKSI. The UE shall consider the USIM as invalid for EPS services until switching off or the UICC containing the USIM is removed or the timer T3245 expires as described in clause 5.3.7a. Additionally, the UE shall enter state EMM-DEREGISTERED. If the message has been successfully integrity checked by the NAS and the UE maintains a counter for "SIM/USIM considered invalid for GPRS services", then the UE shall set this counter to UE implementation-specific maximum value. If A/Gb mode or Iu mode is supported by the UE, the UE shall in addition handle the GMM parameters GMM state, GPRS update status, P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the normal attach procedure is rejected with the GMM cause with the same value. If the UE is operating in single-registration mode, the UE shall in addition handle the 5GMM parameters 5GMM state, 5GS update status, 5G-GUTI, last visited registered TAI, TAI list and ngKSI as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the initial registration procedure performed over 3GPP access is rejected with the 5GMM cause with the same value. #11 (PLMN not allowed); or #35 (Requested service option not authorized in this PLMN); The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and eKSI. Additionally, the UE shall delete the list of equivalent PLMNs and reset the attach attempt counter. In S1 mode, the UE shall store the PLMN identity in the "forbidden PLMN list" and enter state EMM-DEREGISTERED.PLMN-SEARCH and if the UE is configured to use timer T3245 (see 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]) then the UE shall start timer T3245 and proceed as described in clause 5.3.7a. The UE shall perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. If the message has been successfully integrity checked by the NAS and the UE maintains a PLMN-specific attempt counter for that PLMN, then the UE shall set this counter to the UE implementation-specific maximum value. In S101 mode, the UE shall store the PLMN identity provided with the indication from the lower layers to prepare for an S101 mode to S1 mode handover in the list of "forbidden PLMNs for attach in S101 mode" and enter the state EMM-DEREGISTERED.NO-CELL-AVAILABLE and if the UE is configured to use timer T3245 (see 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]) then the UE shall start timer T3245 and proceed as described in clause 5.3.7a. If A/Gb mode or Iu mode is supported by the UE, the UE shall in addition handle the MM parameters update status, TMSI, LAI, ciphering key sequence number and location update attempt counter, and the GMM parameters GMM state, GPRS update status, P-TMSI, P-TMSI signature, RAI, GPRS ciphering key sequence number and GPRS attach attempt counter as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the normal attach procedure is rejected with the GMM cause value #11and no RR connection exists. For the EMM cause value #11, if the UE is operating in single-registration mode, the UE shall in addition handle the 5GMM parameters 5GMM state, 5GS update status, 5G-GUTI, last visited registered TAI, TAI list, ngKSI and registration attempt counter as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the initial registration procedure performed over 3GPP access is rejected with the 5GMM cause with the same value. For the EMM cause value #35, if the UE is operating in single-registration mode, the UE shall in addition set the 5GMM state to 5GMM-DEREGISTERED, 5GS update status to 5U3 ROAMING NOT ALLOWED, and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. Additionally, the UE shall reset the registration attempt counter. #12 (Tracking area not allowed); The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and eKSI. Additionally, the UE shall reset the attach attempt counter. In S1 mode, the UE shall store the current TAI in the list of "forbidden tracking areas for regional provision of service" and enter the state EMM-DEREGISTERED.LIMITED-SERVICE. If the ATTACH REJECT message is not integrity protected, the UE shall memorize the current TAI was stored in the list of "forbidden tracking areas for regional provision of service" for non-integrity protected NAS reject message. In S101 mode, the UE shall store the PLMN identity provided with the indication from the lower layers to prepare for an S101 mode to S1 mode handover in the list of "forbidden PLMNs for attach in S101 mode" and enter the state EMM-DEREGISTERED.NO-CELL-AVAILABLE and if the UE is configured to use timer T3245 (see 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]) then the UE shall start timer T3245 and proceed as described in clause 5.3.7a. If A/Gb mode or Iu mode is supported by the UE, the UE shall in addition handle the GMM parameters GMM state, GPRS update status, P-TMSI, P-TMSI signature, RAI, GPRS ciphering key sequence number and GPRS attach attempt counter as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the normal attach procedure is rejected with the GMM cause with the same value. If the UE is operating in single-registration mode, the UE shall in addition handle the 5GMM parameters 5GMM state, 5GS update status, 5G-GUTI, last visited registered TAI, TAI list, ngKSI and registration attempt counter as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the initial registration procedure performed over 3GPP access is rejected with the 5GMM cause with the same value. #13 (Roaming not allowed in this tracking area); The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and eKSI. The UE shall delete the list of equivalent PLMNs and reset the attach attempt counter. In S1 mode, the UE shall store the current TAI in the list of "forbidden tracking areas for roaming". If the ATTACH REJECT message is not integrity protected, the UE shall memorize the current TAI was stored in the list of "forbidden tracking areas for roaming" for non-integrity protected NAS reject message. Additionally, the UE shall enter the state EMM-DEREGISTERED.LIMITED-SERVICE or optionally EMM-DEREGISTERED.PLMN-SEARCH. If the UE is registered in N1 mode and operating in dual-registration mode, the PLMN that the UE chooses to register in is specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] clause 4.8.3. Otherwise the UE shall perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. In S101 mode, the UE shall store the PLMN identity provided with the indication from the lower layers to prepare for an S101 mode to S1 mode handover in the list of "forbidden PLMNs for attach in S101 mode" and enter the state EMM-DEREGISTERED.NO-CELL-AVAILABLE and if the UE is configured to use timer T3245 (see 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]) then the UE shall start timer T3245 and proceed as described in clause 5.3.7a. If A/Gb mode or Iu mode is supported by the UE, the UE shall in addition handle the GMM parameters GMM state, GPRS update status, P-TMSI, P-TMSI signature, RAI, GPRS ciphering key sequence number and GPRS attach attempt counter as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the normal attach procedure is rejected with the GMM cause with the same value. If the UE is operating in single-registration mode, the UE shall in addition handle the 5GMM parameters 5GMM state, 5GS update status, 5G-GUTI, last visited registered TAI, TAI list, ngKSI and registration attempt counter as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the initial registration procedure performed over 3GPP access is rejected with the 5GMM cause with the same value. #14 (EPS services not allowed in this PLMN); The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and eKSI. Additionally, the UE shall delete the list of equivalent PLMNs and reset the attach attempt counter. In S1 mode, the UE shall store the PLMN identity in the "forbidden PLMNs for GPRS service" list. Additionally, the UE shall enter state EMM-DEREGISTERED.PLMN-SEARCH and if the UE is configured to use timer T3245 (see 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]) then the UE shall start timer T3245 and proceed as described in clause 5.3.7a. The UE shall perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. If the message has been successfully integrity checked by the NAS and the UE maintains a PLMN-specific PS-attempt counter for that PLMN, then the UE shall set this counter to the UE implementation-specific maximum value. In S101 mode, the UE shall store the PLMN identity provided with the indication from the lower layers to prepare for an S101 mode to S1 mode handover in the list of "forbidden PLMNs for attach in S101 mode" and enter the state EMM-DEREGISTERED.NO-CELL-AVAILABLE and if the UE is configured to use timer T3245 (see 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]) then the UE shall start timer T3245 and proceed as described in clause 5.3.7a. If A/Gb mode or Iu mode is supported by the UE, the UE shall in addition handle the GMM parameters GMM state, GPRS update status, P-TMSI, P-TMSI signature, RAI, GPRS ciphering key sequence number and GPRS attach attempt counter as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the normal attach procedure is rejected with the GMM cause with the same value. If the UE is operating in single-registration mode, the UE shall in addition set the 5GMM state to 5GMM-DEREGISTERED, 5GS update status to 5U3 ROAMING NOT ALLOWED, and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. Additionally, the UE shall reset the registration attempt counter. #15 (No suitable cells in tracking area); The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and eKSI. Additionally, the UE shall reset the attach attempt counter. The UE shall store the current TAI in the list of "forbidden tracking areas for roaming". If the ATTACH REJECT message is not integrity protected, the UE shall memorize the current TAI was stored in the list of "forbidden tracking areas for roaming" for non-integrity protected NAS reject message. Additionally, the UE shall enter the state EMM-DEREGISTERED.LIMITED-SERVICE and: - if the UE is in WB-S1 mode and the Extended EMM cause IE with value "E-UTRAN not allowed" is included in the ATTACH REJECT message, the UE supports "E-UTRA Disabling for EMM cause #15", and the "E-UTRA Disabling Allowed for EMM cause #15" parameter as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17] is present and set to enabled; then the UE shall disable the E-UTRA capability as specified in clause 4.5 and search for a suitable cell in GERAN, UTRAN or NG-RAN radio access technology; - if the UE is in NB-S1 mode and the Extended EMM cause IE with value "NB-IoT not allowed" is included in the ATTACH REJECT message, then the UE may disable the NB-IoT capability as specified in clause 4.9 and search for a suitable cell in E-UTRAN radio access technology; - otherwise, the UE shall search for a suitable cell in another tracking area or in another location area according to 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [21]. In S101 mode, the UE shall store the PLMN identity provided with the indication from the lower layers to prepare for an S101 mode to S1 mode handover in the list of "forbidden PLMNs for attach in S101 mode" and enter the state EMM-DEREGISTERED.NO-CELL-AVAILABLE and if the UE is configured to use timer T3245 (see 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]) then the UE shall start timer T3245 and proceed as described in clause 5.3.7a. If A/Gb mode or Iu mode is supported by the UE, the UE shall in addition handle the GMM parameters GMM state, GPRS update status, P-TMSI, P-TMSI signature, RAI, GPRS ciphering key sequence number and GPRS attach attempt counter as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the normal attach procedure is rejected with the GMM cause with the same value. If the UE is operating in single-registration mode, the UE shall in addition handle the 5GMM parameters 5GMM state, 5GS update status, 5G-GUTI, last visited registered TAI, TAI list, ngKSI and registration attempt counter as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the initial registration procedure performed over 3GPP access is rejected with the 5GMM cause with the same value. #22 (Congestion); If the T3346 value IE is present in the ATTACH REJECT message and the value indicates that this timer is neither zero nor deactivated, the UE shall proceed as described below; otherwise it shall be considered as an abnormal case and the behaviour of the UE for this case is specified in clause 5.5.1.2.6. The UE shall abort the attach procedure, reset the attach attempt counter, set the EPS update status to EU2 NOT UPDATED and enter state EMM-DEREGISTERED.ATTEMPTING-TO-ATTACH. The UE shall stop timer T3346 if it is running. If the ATTACH REJECT message is integrity protected, the UE shall start timer T3346 with the value provided in the T3346 value IE. If the ATTACH REJECT message is not integrity protected, the UE shall start timer T3346 with a random value from the default range specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13]. The UE stays in the current serving cell and applies the normal cell reselection process. The attach procedure is started if still needed when timer T3346 expires or is stopped. If A/Gb mode or Iu mode is supported by the UE, the UE shall in addition handle the GMM parameters GMM state, GPRS update status and GPRS attach attempt counter as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the normal attach procedure is rejected with the GMM cause with the same value. If the UE is operating in single-registration mode, the UE shall in addition handle the 5GMM parameters 5GMM state, 5GS update status and registration attempt counter as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the initial registration procedure performed over 3GPP access is rejected with the 5GMM cause with the same value. #25 (Not authorized for this CSG); EMM cause #25 is only applicable when received from a CSG cell. EMM cause #25 received from a non-CSG cell is considered as an abnormal case and the behaviour of the UE is specified in clause 5.5.1.2.6. The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and store it according to clause 5.1.3.3). Additionally, the UE shall reset the attach attempt counter and shall enter the state EMM-DEREGISTERED.LIMITED-SERVICE. If the CSG ID and associated PLMN identity of the cell where the UE has sent the ATTACH REQUEST message are contained in the Allowed CSG list, the UE shall remove the entry corresponding to this CSG ID and associated PLMN identity from the Allowed CSG list. If the CSG ID and associated PLMN identity of the cell where the UE has sent the ATTACH REQUEST message are contained in the Operator CSG list, the UE shall apply the procedures defined in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6] clause 3.1A. The UE shall search for a suitable cell according to 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [21]. If A/Gb mode or Iu mode is supported by the UE, the UE shall in addition handle the GMM parameters GMM state, GPRS update status and GPRS attach attempt counter as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the normal attach procedure is rejected with the GMM cause with the same value. If the UE is operating in single-registration mode, the UE shall in addition set the 5GMM state to 5GMM-DEREGISTERED and set the 5GS update status to 5U3 ROAMING NOT ALLOWED and reset the registration attempt counter. #31 (Redirection to 5GCN required); EMM cause #31 received by a UE that has not indicated support for CIoT optimizations or not indicated support for N1 mode is considered as an abnormal case and the behaviour of the UE is specified in clause 5.5.1.2.6. The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and eKSI. Additionally, the UE shall reset the attach attempt counter. The UE shall enable N1 mode capability for 3GPP access if it was disabled and disable the E-UTRA capability (see clause 4.5) and enter state EMM-DEREGISTERED.NO-CELL-AVAILABLE. If the UE is operating in single-registration mode, the UE shall in addition handle the 5GMM parameters 5GMM state, 5GS update status, 5G-GUTI, last visited registered TAI, TAI list, ngKSI and registration attempt counter as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the initial registration procedure performed over 3GPP access is rejected with the 5GMM cause with the same value. #36 (IAB-node operation not authorized); The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and eKSI. Additionally, the UE shall delete the list of equivalent PLMNs and reset the attach attempt counter. In S1 mode, the UE shall store the PLMN identity in the "forbidden PLMN list" and enter state EMM-DEREGISTERED.PLMN-SEARCH and if the UE is configured to use timer T3245 (see 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]) then the UE shall start timer T3245 and proceed as described in subclause 5.3.7a. The UE shall perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. If the message has been successfully integrity checked by the NAS and the UE maintains a PLMN-specific attempt counter for that PLMN, then the UE shall set this counter to the UE implementation-specific maximum value. In S101 mode, the UE shall store the PLMN identity provided with the indication from the lower layers to prepare for an S101 mode to S1 mode handover in the list of "forbidden PLMNs for attach in S101 mode" and enter the state EMM-DEREGISTERED.NO-CELL-AVAILABLE and if the UE is configured to use timer T3245 (see 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]) then the UE shall start timer T3245 and proceed as described in subclause 5.3.7a. If the UE is operating in single-registration mode, the UE shall in addition handle the 5GMM parameters 5GMM state, 5GS update status, 5G-GUTI, last visited registered TAI, TAI list and ngKSI as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the initial registration procedure performed over 3GPP access is rejected with the 5GMM cause with the same value. #42 (Severe network failure); The UE shall set the EPS update status to EU2 NOT UPDATED, and shall delete any GUTI, last visited registered TAI, TAI list, eKSI, and list of equivalent PLMNs, and set the attach attempt counter to 5. The UE shall start an implementation specific timer setting its value to 2 times the value of T as defined in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. While this timer is running, the UE shall not consider the PLMN + RAT combination that provided this reject cause a candidate for PLMN selection. The UE then enters state EMM-DEREGISTERED.PLMN-SEARCH in order to perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. If A/Gb mode or Iu mode is supported by the UE, the UE shall in addition set the GMM state to GMM-DEREGISTERED, GPRS update status to GU2 NOT UPDATED, and shall delete the P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number. If the UE is operating in single-registration mode, the UE shall in addition set the 5GMM state to 5GMM-DEREGISTERED, 5GS update status to 5U2 NOT UPDATED, and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. #78 (PLMN not allowed to operate at the present UE location). This cause value received from a non-satellite E-UTRA cell is considered as an abnormal case and the behaviour of the UE is specified in clause 5.5.1.2.6. The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and eKSI. Additionally, the UE shall reset the registration attempt counter. The UE shall store the PLMN identity and, if it is known, the current geographical location in the list of "PLMNs not allowed to operate at the present UE location", start a corresponding timer instance (see clause 4.11.2), enter state EMM-DEREGISTERED.PLMN-SEARCH and perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. If the UE is operating in single-registration mode, the UE shall in addition handle the 5GMM parameters 5GMM state, 5GS update status and registration attempt counter as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the initial registration procedure performed over 3GPP access is rejected with the 5GMM cause with the same value. Other values are considered as abnormal cases. The behaviour of the UE in those cases is specified in clause 5.5.1.2.6.

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

6.3.10 SMSF discovery and selection

The SMSF selection function is supported by the AMF and is used to allocate an SMSF instance that shall manage the SMS. If the "SMS supported" indication is included in the Registration Request by the UE, the AMF checks SMS subscription from the UDM for the UE on whether the SMS is allowed for the UE. If the SMS is allowed and the UE Context stored in AMF includes an SMSF address, the AMF uses the SMSF address included in UE Context (according to Table 5.2.2.2.2-1 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]). If the SMS is allowed and the UE Context stored in AMF does not include an SMSF address, the AMF discovers and selects an SMSF to serve the UE. The SMSF selection may be based on the following methods: - SMSF instance(s) address(es) preconfigured in the AMF (i.e. SMSF FQDN or IP addresses); or - SMSF information available in the serving PLMN if received from an old AMF or the UDM; or - The AMF invokes Nnrf_NFDiscovery service operation from NRF to discover SMSF instance as described in clause 5.2.7.3.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. For roaming scenario, the AMF discovers and selects an SMSF in VPLMN. If the NF consumer performs discovery and selection via NRF, the SMSF selection function in the NF consumer selects a SMSF instance based on the available SMSF instances obtained from the NRF. In the case of delegated discovery and selection in SCP, the NF consumer shall include all available factors in the request towards SCP.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

6.3.10

8.2.2.2.4 Enhanced Performance Requirement Type A – 2 Tx Antenna Ports with TM3 interference model

The requirements are specified in Table 8.2.2.2.4-2, with the addition of parameters in Table 8.2.2.2.4-1 and the downlink physical channel setup according to Annex C.3.2. The purpose is to verify the performance of transmit diversity (SFBC) with 2 transmit antennas when the PDSCH transmission in the serving cell is interfered by PDSCH of two dominant interfering cells applying transmission mode 3 interference model defined in clause B.5.2. In Table 8.2.2.2.4-1, Cell 1 is the serving cell, and Cell 2, 3 are interfering cells. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1, Cell 2 and Cell 3, respectively. Table 8.2.2.2.4-1: Test Parameters for Transmit diversity Performance (FRC) with TM3 interference model Table 8.2.2.2.4-2: Enhanced Performance Requirement Type A, Transmit Diversity (FRC) with TM3 interference model

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

– RRCResumeComplete

The RRCResumeComplete message is used to confirm the successful completion of an RRC connection resumption. Signalling radio bearer: SRB1 RLC-SAP: AM Logical channel: DCCH Direction: UE to Network RRCResumeComplete message -- ASN1START -- TAG-RRCRESUMECOMPLETE-START RRCResumeComplete ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { rrcResumeComplete RRCResumeComplete-IEs, criticalExtensionsFuture SEQUENCE {} } } RRCResumeComplete-IEs ::= SEQUENCE { dedicatedNAS-Message DedicatedNAS-Message OPTIONAL, selectedPLMN-Identity INTEGER (1..maxPLMN) OPTIONAL, uplinkTxDirectCurrentList UplinkTxDirectCurrentList OPTIONAL, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension RRCResumeComplete-v1610-IEs OPTIONAL } RRCResumeComplete-v1610-IEs ::= SEQUENCE { idleMeasAvailable-r16 ENUMERATED {true} OPTIONAL, measResultIdleEUTRA-r16 MeasResultIdleEUTRA-r16 OPTIONAL, measResultIdleNR-r16 MeasResultIdleNR-r16 OPTIONAL, scg-Response-r16 CHOICE { nr-SCG-Response OCTET STRING (CONTAINING RRCReconfigurationComplete), eutra-SCG-Response OCTET STRING } OPTIONAL, ue-MeasurementsAvailable-r16 UE-MeasurementsAvailable-r16 OPTIONAL, mobilityHistoryAvail-r16 ENUMERATED {true} OPTIONAL, mobilityState-r16 ENUMERATED {normal, medium, high, spare} OPTIONAL, needForGapsInfoNR-r16 NeedForGapsInfoNR-r16 OPTIONAL, nonCriticalExtension RRCResumeComplete-v1640-IEs OPTIONAL } RRCResumeComplete-v1640-IEs ::= SEQUENCE { uplinkTxDirectCurrentTwoCarrierList-r16 UplinkTxDirectCurrentTwoCarrierList-r16 OPTIONAL, nonCriticalExtension RRCResumeComplete-v1700-IEs OPTIONAL } RRCResumeComplete-v1700-IEs ::= SEQUENCE { needForGapNCSG-InfoNR-r17 NeedForGapNCSG-InfoNR-r17 OPTIONAL, needForGapNCSG-InfoEUTRA-r17 NeedForGapNCSG-InfoEUTRA-r17 OPTIONAL, nonCriticalExtension RRCResumeComplete-v1720-IEs OPTIONAL } RRCResumeComplete-v1720-IEs ::= SEQUENCE { uplinkTxDirectCurrentMoreCarrierList-r17 UplinkTxDirectCurrentMoreCarrierList-r17 OPTIONAL, nonCriticalExtension RRCResumeComplete-v1800-IEs OPTIONAL } RRCResumeComplete-v1800-IEs ::= SEQUENCE { needForInterruptionInfoNR-r18 NeedForInterruptionInfoNR-r18 OPTIONAL, musim-CapRestrictionInd-r18 ENUMERATED {true} OPTIONAL, flightPathInfoAvailable-r18 ENUMERATED {true} OPTIONAL, measConfigReportAppLayerAvailable-r18 ENUMERATED {true} OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } -- TAG-RRCRESUMECOMPLETE-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

7.5.1 Minimum requirements

The UE shall fulfil the minimum requirement specified in Table 7.5.1-1 for all values of an adjacent channel interferer up to –25 dBm. However it is not possible to directly measure the ACS, instead the lower and upper range of test parameters are chosen in Table 7.5.1-2 and Table 7.5.1-3 where the throughput shall be ≥ 95% of the maximum throughput of the reference measurement channels as specified in Annexes A.2.2, A.2.3 and A.3.2 (with one sided dynamic OCNG Pattern OP.1 FDD/TDD for the DL-signal as described in Annex A.5.1.1/A.5.2.1). For operating bands with an unpaired DL part (as noted in Table 5.5-1), the requirements only apply for carriers assigned in the paired part. Table 7.5.1-1: Adjacent channel selectivity Table 7.5.1-2: Test parameters for Adjacent channel selectivity, Case 1 Table 7.5.1-3: Test parameters for Adjacent channel selectivity, Case 2

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

7.5.1

9.7.1.1 FDD and half-duplex FDD

The following requirements apply to UE DL Category 0. For the parameters specified in Table 9.7.1.1-1, and using the downlink physical channels specified in tables C.3.2-1 and C.3.2-2, the reported CQI value according to RC.16 FDD in Table A.4-1 shall be in the range of ±1 of the reported median more than 90% of the time. If the PDSCH BLER using the transport format indicated by median CQI is less than or equal to 0.1, the BLER using the transport format indicated by the (median CQI + 1) shall be greater than 0.1. If the PDSCH BLER using the transport format indicated by the median CQI is greater than 0.1, the BLER using transport format indicated by (median CQI – 1) shall be less than or equal to 0.1. Table 9.7.1.1-1: PUCCH 1-0 static test (FDD and half-duplex 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.7.1.1

T.3 Security of EAS discovery procedure via EASDF in non-roaming Scenario

Annex P of the present document should be followed, with the following additions, to protect the discovery messages between the UE and the EASDF which is used as the DNS server for EAS discovery in the non-roaming case. If the core network is used to configure the security information, the SMF is preconfigured with the EASDF security information (credentials to authenticate the EASDF, supported security mechanisms, port number, etc.) and provides the security information to the UE as follows: The SMF provides the EASDF security information to the UE via PCO.

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

T.3

3.2 Numbering plan requirements

In principle, it should be possible for any subscriber of the ISDN or PSTN to call any MS in a PLMN. This implies that E.164 numbers for MSs should comply with the E.164 numbering plan in the home country of the MS. The E.164 numbers of MSs should be composed in such a way that standard ISDN/PSTN charging can be used for calls to MSs. It should be possible for each national numbering plan administrator to develop its own independent numbering/addressing plan for MSs. The numbering/addressing plan should not limit the possibility for MSs to roam among PLMNs. It should be possible to change the IMSI without changing the E.164 number assigned to an MS and vice versa. In principle, it should be possible for any subscriber of the CSPDN/PSPDN to call any MS in a PLMN. This implies that it may be necessary for an MS to have a X.121 number. In principle, it should be possible for any fixed or mobile terminal to communicate with a mobile terminal using an IP v4 address or IP v6 address.

3GPP TS 23.003

Numbering, addressing and identification

CT WG4

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

3.2

5.2.2.3.4 Namf_EventExposure_Notify service operation

Service operation name: Namf_EventExposure_Notify. Service operation description: Provides the previously subscribed event information to the NF Consumer which has subscribed to that event before. Input, Required: AMF ID (GUAMI), Notification Correlation Information, Event ID, corresponding UE(s) (SUPI(s) and if available GPSI(s)), time stamp. Input, Optional: Event specific parameter list, Idle Status Indication (time when UE returned to Idle, Active Time, Periodic Update Timer, eDRX cycle, suggested number of DL packets). Output, Required: None. Output, Optional: None. When the AMF detects a UE access and mobility event corresponding to a Subscription, it invokes Namf_EventExposure_Notify service operation to the NF consumer(s) which has subscribed to the UE mobility event before. The event is notified towards the consumers for which the Event filters (which may include "AN type(s)") match. The Notification Target Address (+ Notification Correlation ID) indicates to the Event Receiving NF the specific event notification subscription. The event specific parameter indicates the type of mobility event and related information, e.g. Registration Area Update/new Registration Area. For Subscription Correlation ID changes due to the AMF reallocation, the AMF can send a list of additional subscriptions to UDM in order to trigger an event resynchronization. The optional event specific parameter list provides the values that matched for generating the event notification. The parameter values to match are specified during the event subscription (see clause 5.2.2.3.2). For example, if the event type reported is "AN change", the event specific parameter list contains the value of the new AN.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

5.2.2.3.4

5.5.2.3.1 Network initiated detach procedure initiation

The network initiates the detach procedure by sending a DETACH REQUEST message to the UE (see example in figure 5.5.2.3.1). NOTE: If the MME performs a local detach, it will inform the UE with an EMM messages (e.g. SERVICE REJECT or TRACKING AREA UPDATE reject) with EMM cause #10 "implicitly detached" only when the UE initiates an EMM procedure. The network may include an EMM cause IE to specify the reason for the detach request. The network shall start timer T3422. If the Detach type IE indicates "re-attach required" or "re-attach not required" and the EMM cause value is not #2 "IMSI unknown in HSS", or if the MME performs a local detach, the MME shall either store the current EPS security context if it is a native EPS security context, or the MME shall delete the current EPS security context if it is a mapped EPS security context. If the detach type IE indicates "re-attach required" or "re-attach not required" and the EMM cause value is not #2 "IMSI unknown in HSS", the network shall deactivate the EPS bearer context(s), if any, for the UE locally and enter state EMM-DEREGISTERED-INITIATED. In NB-S1 mode or WB-S1 mode via satellite E-UTRAN access, if the network initiates the detach procedure because the network determines that the UE is in a location where the network is not allowed to operate (see 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10]), the network shall set the EMM cause value in the DETACH REQUEST message to #78 "PLMN not allowed to operate at the present UE location". If the network detach is triggered because the MME determines that, by UE subscription and operator's preferences, all of the TAIs received from the satellite E-UTRAN are forbidden for roaming or for regional provision of service, the MME shall include the TAI(s) in: a) the Forbidden TAI(s) for the list of "forbidden tracking areas for roaming" IE; b) the Forbidden TAI(s) for the list of "forbidden tracking areas for regional provision of service" IE; or c) both, in the DETACH REQUEST message. Figure 5.5.2.3.1: Network initiated detach procedure

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

4.22.8.3 UE or network requested MA PDU Session Modification (home-routed roaming)

The signalling flow for a MA PDU Session Modification when the UE is registered to the same VPLMN over 3GPP access and non-3GPP access and the PDU Session Anchor (PSA) is located in the HPLMN, is based on the signalling flow in Figure 4.3.3.3-1 with the following differences and clarifications: - In step 1b, the H-SMF may decide to update ATSSS rules and/or N4 rules based on updated PCC rules. - In step 1d, if the H-UPF determines that it cannot send GBR traffic over the current ongoing access e.g. based on the N4 rules and access availability and unavailability report from the UE, the H-UPF shall send Access Availability report to the H-SMF. When the H-SMF receives the Access Availability report, the H-SMF may decide to move the GBR QoS Flow to the other access as described in clause 5.32.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the H-SMF decides to move GBR QoS Flow, the H-SMF triggers this procedure and afterwards moves the GBR QoS flow to the target access. - In step 3, if the H-SMF decides to move the GBR QoS Flow to the other access, the H-SMF sends updated GBR QoS Flow information contains associated access type and ATSSS rule to the V-SMF. Based on the information the V-SMF establishes AN resources for the GBR QoS Flow to the target access. - In step 3, when the H-SMF provides GBR QoS Flow information, the H-SMF includes associated access type in Nsmf_PDUSession_Update. When the H-SMF provides non-GBR QoS Flow information, H-SMF provides the information for both accesses in Nsmf_PDUSession_Update. - In step 3, if the H-SMF wants to update ATSSS rules, the H-SMF triggers Nsmf_PDUSession_Update and includes an updated ATSSS rules. - In step 4, if the H-SMF decides to move the GBR QoS Flow to the other access, the PDU Session Modification Command message is sent to the UE to update ATSSS rule of the UE so that the UE sends uplink GBR traffic over the target access. The V-SMF releases AN resources of the GBR QoS Flow in the source access. - In step 4, when the V-SMF establishes user plane resources for a QoS flows, the V-SMF provides QoS profile to the AN as follows: - for Non-GBR QoS Flow, steps 4 to 9 are performed over each access for which the MA PDU Session is established. - for GBR QoS Flow allowed in a single access, steps 4 to 9 are performed in the allowed access. - for GBR QoS Flow allowed in both accesses, steps 4 to 9 are performed in the access according to the decision by the SMF (as described in clause 5.32.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]). - In step 4, if the H-SMF provides updated ATSSS rules, the V-SMF includes the updated ATSSS rules in the N1 SM container (PDU Session Modification Command). When the V-SMF provides N1 SM container and/or N2 SM information, the V-SMF includes access type in the Namf_Communication_N1N2MessageTransfer to provide routing information to the AMF. The description of signalling flow for a MA PDU Session Modification when the UE is registered to different PLMNs over 3GPP access and non-3GPP access and the PDU Session Anchor (PSA) is located in the HPLMN, is based on above procedure with the following differences and clarifications: - The description of (V-)SMF providing QoS profile to the AN is not applicable and instead the regular procedures for QoS profile provisioning from (V-)SMF to (R)AN applies.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.22.8.3

5.7.7.2 PDU Set Delay Budget

The PDU Set Delay Budget (PSDB) defines an upper bound for the delay that a PDU Set may experience for the transfer between the UE and the N6 termination point at the UPF, i.e. the duration between the reception time of the first PDU (at the N6 termination point for DL or the UE for UL) and the time when all PDUs of a PDU Set have been successfully received (at the UE for DL or N6 termination point for UL). PSDB applies to the DL PDU Set received by the PSA UPF over the N6 interface, and to the UL PDU Set sent by the UE. NOTE: To enable support for PSDB, it is required that a maximum inter arrival time between the first received PDU and the last received PDU of a PDU Set complies with SLA. This maximum inter arrival time does not exceed PSDB. NG-RAN behaviour when the SLA is not fulfilled is out of scope of this specification. A QoS Flow is associated with at most one PDU Set Delay Budget value per direction. PSDB is an optional parameter that may be provided by the PCF. The provided PSDB can be used by the NG-RAN to support the configuration of scheduling and link layer functions. When the PSDB is available, the PSDB supersedes the PDB for the given QoS Flow. The AN PSDB is derived at NG-RAN by subtracting CN PDB (as described in clause 5.7.3.4) from the PSDB.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.7.7.2

8.2.15.1 Message definition

This message is sent by the UE to the network - to initiate a CS fallback or 1xCS fallback call or respond to a mobile terminated CS fallback or 1xCS fallback request from the network; or - to request the establishment of a NAS signalling connection and of the radio and S1 bearers for packet services, if the UE needs to provide additional information that cannot be provided via a SERVICE REQUEST message. See table 8.2.15.1. Message type: EXTENDED SERVICE REQUEST Significance: dual Direction: UE to network Table 8.2.15.1: EXTENDED SERVICE REQUEST message content

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

8.2.15.1

– FeatureSetUplinkId

The IE FeatureSetUplinkId identifies an uplink feature set. The FeatureSetUplinkId of a FeatureSetUplink is the index position of the FeatureSetUplink in the featureSetsUplink list in the FeatureSets IE. The first element in the list is referred to by FeatureSetUplinkId = 1, and so on. The FeatureSetUplinkId =0 is not used by an actual FeatureSetUplink but means that the UE does not support a carrier in this band of a band combination. FeatureSetUplinkId information element -- ASN1START -- TAG-FEATURESETUPLINKID-START FeatureSetUplinkId ::= INTEGER (0..maxUplinkFeatureSets) -- TAG-FEATURESETUPLINKID-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

4.7.3.3 Uplink Scheduling Latency

The IAB-node can reduce UL scheduling latency through signalling of a Pre-emptive BSR to its parent node. The IAB-node can send the Pre-emptive BSR based on UL grants it has provided to child nodes and/or UEs, or based on BSRs it has received from child nodes or UEs (Figure 4.7.3.3-1). The Pre-emptive BSR conveys the data expected rather than the data buffered. Figure 4.7.3.3-1: Scheduling of BSR in IAB: a) regular BSR based on buffered data, b) Pre-emptive BSR based on UL grant, c) Pre-emptive BSR based on reception of regular BSR

3GPP TS 38.300

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

RAN2

3GPP Series : 38 , Radio technology beyond LTE

4.7.3.3

9.2.9 CM service request

This message is sent by the mobile station to the network to request a service for the connection management sublayer entities, e.g. circuit switched connection establishment, supplementary services activation, short message transfer, location services. See table 9.2.11/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Message type: CM SERVICE REQUEST Significance: dual Direction: mobile station to network Table 9.2.11/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : CM SERVICE REQUEST message content

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

5.35.1 IAB architecture and functional entities

Integrated access and backhaul (IAB) enables wireless in-band and out-of-band relaying of NR Uu access traffic via NR Uu backhaul links. In this Release of the specification, NR satellite access is not applicable. The serving PLMN may provide the mobility restriction for NR satellite access as specified in clause 5.3.4.1 The Uu backhaul links can exist between the IAB-node and: - a gNB referred to as IAB-donor; or - another IAB-node. The part of the IAB node that supports the Uu interface towards the IAB-donor or another parent IAB-node (and thus manages the backhaul connectivity with either PLMN or SNPN it is registered with) is referred to as an IAB-UE. In this Release of the specification, the IAB-UE function does not apply to the NR RedCap UE. At high level, IAB has the following characteristics: - IAB uses the CU/DU architecture defined in TS 38.401[ NG-RAN; Architecture description ] [42], and the IAB operation via F1 (between IAB-donor and IAB-node) is invisible to the 5GC; - IAB performs relaying at layer-2, and therefore does not require a local UPF; - IAB supports multi-hop backhauling; - IAB supports dynamic topology update, i.e. the IAB-node can change the parent node, e.g. another IAB-node, or the IAB-donor, during operation, for example in response to backhaul link failure or blockage. Figure 5.35.1-1 shows the IAB reference architecture with two backhaul hops, when connected to 5GC. Figure 5.35.1-1: IAB architecture for 5GS The gNB-DU in the IAB-node is responsible for providing NR Uu access to UEs and child IAB-nodes. The corresponding gNB-CU function resides on the IAB-donor gNB, which controls IAB-node gNB-DU via the F1 interface. IAB-node appears as a normal gNB to UEs and other IAB-nodes and allows them to connect to the 5GC. The IAB-UE function behaves as a UE, and reuses UE procedures to connect to: - the gNB-DU on a parent IAB-node or IAB-donor for access and backhauling; - the gNB-CU on the IAB-donor via RRC for control of the access and backhaul link; - 5GC, e.g. AMF, via NAS; - OAM system via a PDU session or PDN connection (based on implementation). NOTE: The 5GC, e.g. SMF, may detect that a PDU session for the IAB-UE is for the OAM system access, e.g. by checking the DNN and/or configuration. It is up to the operator configuration to choose whether to use 1 or multiple QoS Flows for OAM traffic and the appropriate QoS parameters, e.g. using 5QI=6 for software downloading, and 5QI=80 with signalled higher priority or a pre-configured 5QI for alarm or control traffic. The IAB-UE can connect to 5GC over NR (SA mode) or connect to EPC (EN-DC mode). The UE served by the IAB-node can operate in the same or different modes than the IAB-node as defined in TS 38.401[ NG-RAN; Architecture description ] [42]. The operation mode with both UE and IAB-node connected to EPC is covered in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [26]. Operation modes with UE and IAB-node connected to different core networks are described in clause 5.35.6.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.35.1

15.4.2.2 Inter-system energy saving

The solution builds upon the possibility for the NG-RAN node owning a capacity booster cell to autonomously decide to switch-off such cell to dormant state. The decision is typically based on cell load information, consistently with configured information. The switch-off decision may also be taken by O&M. The NG-RAN node indicates the switch-off action to the eNB over NG interface and S1 interface. The NG-RAN node could also indicate the switch-on action to the eNB over NG interface and S1 interface. The eNB providing basic coverage may request a NG-RAN node's cell re-activation based on its own cell load information or neighbour cell load information, the switch-on decision may also be taken by O&M. The eNB requests a NG-RAN node's cell re-activation and receives the NG-RAN node's cell re-activation reply from the NG-RAN node over the S1 interface and NG interface. Upon reception of the re-activation request, the NG-RAN node's cell should remain switched on at least until expiration of the minimum activation time. The minimum activation time may be configured by O&M or be left to the NG-RAN node's implementation.

3GPP TS 38.300

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

RAN2

3GPP Series : 38 , Radio technology beyond LTE

15.4.2.2

6.2.5.1.4.3 Creating a derived QoS rule by reflective QoS in the UE

If the UE receives a DL user data packet marked with a QFI and an RQI, the DL user data packet belongs to a PDU session of IPv4, IPv6, IPv4v6 or Ethernet PDU session type, and the UE does not have a derived QoS rule with the same packet filter for UL direction as the packet filter for UL direction derived from the DL user data packet as specified in subclause 6.2.5.1.4.2, then the UE shall create a new derived QoS rule as follows: a) the QFI of the derived QoS rule is set to the received QFI; b) the precedence value of the derived QoS rule is set to 80 (decimal); and c) the packet filter for UL direction of the derived QoS rule is set to the derived packet filter for UL direction; and the UE shall start the timer T3583 associated with the derived QoS rule with the RQ timer value last received during the UE-requested PDU session establishment procedure of the PDU session (see subclause 6.4.1) or the network-requested PDU session modification procedure of the PDU session (see subclause 6.4.2). If the RQ timer value was received neither in the UE-requested PDU session establishment procedure of the PDU session nor in any network-requested PDU session modification procedure of the PDU session, the default standardized RQ timer value is used.

3GPP TS 24.501

Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3

CT WG1

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

6.2.5.1.4.3

– VarMeasReportListSL

The UE variable VarMeasReportListSL includes information about the NR sidelink measurements for which the triggering conditions have been met. VarMeasReportListSL UE variable -- ASN1START -- TAG-VARMEASREPORTLISTSL-START VarMeasReportListSL-r16 ::= SEQUENCE (SIZE (1..maxNrofSL-MeasId-r16)) OF VarMeasReportSL-r16 VarMeasReportSL-r16 ::= SEQUENCE { -- List of NR sidelink measurement that have been triggered sl-MeasId-r16 SL-MeasId-r16, sl-FrequencyTriggeredList-r16 SEQUENCE (SIZE (1..maxNrofFreqSL-r16)) OF ARFCN-ValueNR OPTIONAL, sl-NumberOfReportsSent-r16 INTEGER } -- TAG-VARMEASREPORTLISTSL-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

4.8.1.1a Connection Inactive procedure with CN based MT communication handling

This procedure may be initiated by the serving NG-RAN node when CN based mobile terminating (MT) communication handling is requested for a UE that is configured with eDRX cycle value longer than 10.24 seconds for RRC_INACTIVE state and has at least one PDU session with active user plane as defined in clause 5.31.7 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. Figure 4.8.1.1a-1: NG-RAN initiated Connection Inactive procedure with CN based MT communication handling 0. The UE is registered in the network with negotiated eDRX parameters for CM-IDLE state and is in CM-CONNECTED with RRC_CONNECTED state. The AMF provides the eDRX values for CM-IDLE state to NG-RAN as part of the RRC Inactive Assistance Information as defined in clause 5.3.3.2.5 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 1. NG-RAN determines eDRX values for UE in RRC_INACTIVE state and decides to initiate Connection Inactive with CN based MT communication handling as specified in clause 5.31.7.2.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 1a. Optionally the NG-RAN may initiate state transition from RRC_CONNECTED to RRC_INACTIVE with RRC configuring eDRX value as specified in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [9]. The NG-RAN may send the request in step 2 towards CN immediately following step 1a or the NG-RAN may delay this request towards CN as specified in clause 5.31.7.2.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 2. Either immediately following step 1a or after having delayed the request for NG-RAN based on implementation, the NG-RAN sends N2 MT Communication Handling request message to AMF indicating the UE is transitioning to RRC_INACTIVE state. The CN takes the NG-RAN request into consideration and handles MT communication. The NG-RAN also provides the determined eDRX values for RRC_INACTIVE to AMF. If the NG-RAN receives DL NAS message and the UE is in RRC_INACTIVE with RRC configured eDRX and is considered not reachable, NG-RAN indicates to the AMF a NAS non-delivery and then initiates for the CN to handle mobile terminated (MT) communication. 3. For each of the PDU sessions with user plane resources have been activated, the AMF invokes Nsmf_PDUSession_UpdateSMContext Request (PDU Session ID, Cause, Operation type, User Location Information, Age of Location Information, N2 SM Information (Secondary RAT usage data), CN based MT handling indication) towards SMF. The Operation Type is set to a value that indicates to stop user plane DL data transmissions towards the UE and enable data buffering. The SMF starts data buffering for MT data if the data buffering is handled in SMF. 4. If data buffering is handled in the UPF, the SMF updates the UPF with proper rules for MT data handling. 5. The SMF sends the Nsmf_PDUSession_UpdateSMContext response. 6. The AMF sends N2 MT Communication Handling response message to NG-RAN acknowledging the NG-RAN request and indicating the AMF has taken the NG-RAN request into account. The AMF considers the UE is in CM-CONNECTED with RRC_INACTIVE state. 7. If the UE connection is not released as specified in step 1a, the NG-RAN initiates state transition from RRC_CONNECTED to RRC_INACTIVE with RRC configuring the eDRX values as specified in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [9].

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.8.1.1a

C.1.2 Support for the array mechanism

This subsection applies to all three schemes presented in subsection C.1.1. Each time an authentication vector is generated, the AuC shall retrieve INDHE from storage and allocate a new index value for that vector according to suitable rules and include it in the appropriate part of SQN. The index value may range from 0 to a -1 where a is the size of the array. An example value for the array size a is given in Annex C.3. The exact rules for index allocation are left unspecified. Guidelines are given in Annex C.3.4.

3GPP TS 33.102

3G security; Security architecture

SA WG3

3GPP Series : 33 , Security aspects

C.1.2

D.8 Handling of unknown, unforeseen, and erroneous UPDS data D.8.1 General

The procedures specified in the subclause apply to those messages which pass the checks described in this subclause. This subclause also specifies procedures for the handling of unknown, unforeseen, and erroneous UPDS data by the receiving entity. These procedures are called "error handling procedures", but in addition to providing recovery mechanisms for error situations they define a compatibility mechanism for future extensions of the UPDS. Subclauses D.8.1 to D.8.8 shall be applied in order of precedence. Detailed error handling procedures in the network are implementation dependent and may vary from PLMN to PLMN. However, when extensions of UPDS are developed, networks are assumed to have the error handling which is indicated in this subclause as mandatory ("shall") and that is indicated as strongly recommended ("should"). Also, the error handling of the network is only considered as mandatory or strongly recommended when certain thresholds for errors are not reached during a dedicated connection. For definition of semantical and syntactical errors see 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [11], subclause 11.4.2.

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

D.8

4.22.7 Adding / Re-activating / De-activating User-Plane Resources

If the UE has established a MA PDU Session but the user-plane resources over one access of the MA PDU Session have not been established, then: - If the UE wants to add user-plane resources over this access, the UE shall initiate the UE Requested PDU Session Establishment procedure over this access, as specified in clause 4.3.2.2. In the UL NAS Transport message, the UE sets Request Type as "MA PDU Request" and the same PDU Session ID of the established MA PDU Session. If only one N9 tunnel is established for the Home Routed roaming case as described in clause 4.22.2.2, additional N9 tunnel is established during this UE Requested PDU Session Establishment procedure. For the roaming with home-routed architecture as defined in TS 23.501[ System architecture for the 5G System (5GS) ] [2] figure 4.2.10-3, an N9 tunnel or an N3 tunnel is established during this PDU Session Establishment procedure, depending on the access for which the UE is requesting user-plane resources. - The PDU Session Establishment Accept message received by the UE may contain updated ATSSS rules for the MA PDU session. - If the SMF receives the PDU Session Establishment request message over an access and the SMF already has SM Contexts for the access, the SMF shall not release existing SM Contexts and shall re-activate user plane resources over the access while providing the PDU Session Establishment Accept message to the UE. If the UE has established a MA PDU Session and the user-plane resources over one access of the MA PDU Session have been established but are currently inactive (e.g. because the UE is CM-IDLE over this access), then: - If the UE wants to re-activate the user-plane resources over this access, then the UE shall initiate the Registration or UE Triggered Service Request procedure over this access, as specified in clause 4.22.9.2. - If the network wants to re-activate the user-plane resources over 3GPP access of the MA PDU Session, or over non-3GPP access of the MA PDU Session, the network shall initiate the Network Triggered Service Request procedure, as specified in clause 4.22.9.4. If the UE has established a MA PDU Session and the user plane resources are activated over either one access or both accesses, then: - If the network wants to de-activate the user-plane resources over single access, then the network shall initiate the CN-initiated deactivation of UP connection procedure over this access, as specified in clause 4.3.7. In all cases, if the UP security protection associated with this PDU session indicates that UP security is required, the SMF shall not establish resources over the 3GPP access unless the 3GPP Access Network can enforce the required UP security protection, even if resources were previously established over non-3GPP access.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.22.7

4.11.1.2.3 Handover Cancel

Instead of completing the handover procedure, the source RAN node (NG-RAN, E-UTRAN) may at any time, during the handover procedure, up to the time when a handover command message is sent to the UE, cancel the handover. The reason for cancelling may be e.g. due to a timer expiration or due to other events within the source RAN node and is initiated by sending a handover cancel message to the source CN node (AMF or MME). A handover cancel message shall also be sent by the source RAN node after a handover command message is sent to the UE for the case where the handover fails and the UE returns to the old cell or radio contact with the UE is lost. This is done in order to release the resources reserved for the handover in the target system. During EPS to 5GS handover when the initial AMF has invoked a target AMF (as described in step 8a in clause 4.11.1.2.2), - when the source MME has received a N26 Forward Relocation Response from the target AMF, the MME sends N26 Cancel Relocation Request directly to the target AMF and the initial AMF is not involved at all in the Cancel Relocation procedure. - When the source MME has not received a response from the target AMF, the MME sends N26 Cancel Relocation Request to the initial AMF: - if the initial AMF has already invoked the target AMF, the initial AMF indicates the Cancel Relocation to the target AMF and the target AMF becomes responsible of the Handover Cancellation (e.g. the target AMF initiates Nsmf_PDUSession_UpdateSMContext request indicating Handover Cancel towards the SMF+PGW-C(s) unless the target AMF has already indicated a Handover failure due to prior target NG RAN rejection of the Handover); - otherwise the initial AMF handles the relocation cancellation. Figure 4.11.1.2.3-1: Handover Cancel procedure 1. When the source RAN (NG-RAN, E-UTRAN) decides to cancel the handover to the target system, the source RAN initiates handover cancel message to the source CN node (AMF or MME). 2. After receiving the handover cancel message from the source RAN, if the source CN node or the target CN node is MME, it sends a Relocation Cancel Request message to the target CN node (MME or AMF). If both the source CN node and target CN node are AMF, the source AMF invokes (via initial AMF if AMF re-allocation is performed during preparation phase) the Namf_Communication_ReleaseUEContext Request (UE Context ID) toward the target AMF. During EPS to 5GS handover with AMF reallocation if the initial AMF has invoked a target AMF, the initial AMF invokes the Namf_Communication_CancelRelocateUEContext Request (UE Context ID) toward the target AMF. 3. The target CN node (MME or AMF) triggers release of resources towards target RAN node. The target RAN node releases the AN resources allocated for the handover. 4. If the target CN node is MME, the MME sends the Delete Session Request to the SGW/SGW-C (see clause 5.5.2.5.2 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13]). 4a. [Conditional] The SGW-C releases the corresponding resource in the SGW-U if allocated during the handover preparation. 4b. If the target CN node is AMF, the AMF invokes the Nsmf_PDUSession_UpdateSMContext request (Relocation Cancel Indication) toward the SMF in non-roaming and local breakout roaming scenarios. For home-routed roaming scenario, AMF invokes the Nsmf_PDUSession_UpdateSMContext request (Relocation Cancel Indication) toward the (target) V-SMF and the V-SMF invokes the Nsmf_PDUSession_Update Request (Relocation Cancel Indication) towards the H-SMF. Based on the Relocation Cancel Indication, the SMF(s) deletes the session resources established during handover preparation phase in SMF(s) and UPF(s). 4c. [Conditional] The (target) V-SMF releases the corresponding resource in the (target) V-UPF if allocated during the handover preparation. 4d. [Conditional] The (H-)SMF+PGW-C releases the corresponding resource in the (H-)UPF+PGW-U if allocated during the handover preparation. 5. The target CN node (MME or AMF) sends Relocation Cancel Response towards the source CN node (AMF or MME). 6. The source CN node (AMF or MME) responds with handover cancel ACK towards the source RAN. 7. [Conditional] If target CN node is AMF and the source CN is MME and indirect forwarding tunnel had been set up during handover preparation phase then cancellation of handover triggers the MME to release the temporary resources used for indirect forwarding. 7b. [Conditional] If the source CN is AMF and the target CN node is MME and if indirect forwarding tunnel had been setup during handover preparation phase, then cancellation of handover triggers the AMF to release the session resources established during handover preparation phase in SMF(s) and UPF(s). - The AMF invokes the Nsmf_PDUSession_UpdateSMContext request (Relocation Cancel Indication) toward the SMF in non-roaming and local breakout roaming scenarios. - For home-routed roaming scenario, the AMF invokes the Nsmf_PDUSession_UpdateSMContext request (Relocation Cancel Indication) toward the V-SMF and the V-SMF invokes the Nsmf_PDUSession_Update Request (Relocation Cancel Indication) towards the H-SMF. Based on the Relocation Cancel Indication, the SMF(s) deletes the session resources established during handover preparation phase in SMF(s) and UPF(s). 7c. [Conditional] In home routed roaming case, the V-SMF releases the corresponding resource in the target V-UPF if allocated during the handover preparation. 7d. [Conditional] In non-roaming or LBO case, the SMF+PGW-C releases the corresponding resource in the UPF+PGW-U if allocated during the handover preparation. 8. [Conditional] If target CN node is MME and indirect forwarding tunnel is setup during handover preparation phase then cancellation of handover triggers the target MME to release the temporary resources used for indirect forwarding. 8a. [Conditional] The SGW-C releases the resources for indirect forwarding in the SGW-U if allocated during the handover preparation.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.11.1.2.3

5.3.5.14 Sidelink dedicated configuration

Upon initiating the procedure, the UE shall: 1> if sl-FreqInfoToReleaseList is included in sl-ConfigDedicatedNR within RRCReconfiguration: 2> for each entry included in the received sl-FreqInfoToReleaseList that is part of the current UE configuration: 3> release the related configurations from the stored NR sidelink communication/discovery configurations; 1> if sl-FreqInfoToAddModList/sl-FreqInfoToAddModListExt is included in sl-ConfigDedicatedNR within RRCReconfiguration: 2> if configured to receive NR sidelink communication: 3> use the resource pool(s) indicated by sl-RxPool for NR sidelink communication reception, as specified in 5.8.7; 2> if configured to transmit NR sidelink communication: 3> use the resource pool(s) indicated by sl-TxPoolSelectedNormal, sl-TxPoolScheduling or sl-TxPoolExceptional for NR sidelink communication transmission, as specified in 5.8.8; 2> if configured to receive NR sidelink discovery: 3> use the resource pool(s) indicated by sl-DiscRxPool or sl-RxPool for NR sidelink discovery reception, as specified in 5.8.13.2; 2> if configured to transmit NR sidelink discovery: 3> use the resource pool(s) indicated by sl-DiscTxPoolSelected, sl-DiscTxPoolScheduling, sl-TxPoolSelectedNormal, sl-TxPoolScheduling or sl-TxPoolExceptional for NR sidelink discovery transmission, as specified in 5.8.13.3; 2> if configured to receive sidelink control information for SL-PRS measurement: 3> use the resource pool(s) indicated by sl-RxPool and/or sl-PRS-RxPool for SL-PRS reception, as specified in 5.8.18.2; 2> if configured to transmit SL-PRS: 3> use the resource pool(s) indicated by sl-PRS-TxPoolSelectedNormal, sl-PRS-TxPoolScheduling, sl-BWP-PRS-PoolConfig or sl-PRS-TxPoolExceptional for SL-PRS transmission, as specified in 5.8.18.3; 2> perform CBR measurement on the transmission resource pool(s) indicated by sl-TxPoolSelectedNormal, sl-TxPoolScheduling, sl-PRS-TxPoolSelectedNormal, sl-PRS-TxPoolScheduling, sl-DiscTxPoolSelected, sl-DiscTxPoolScheduling, sl-TxPoolExceptional or sl-PRS-TxPoolExceptional for NR sidelink communication/discovery/positioning transmission, as specified in 5.5.3; 2> use the synchronization configuration parameters for NR sidelink communication/discovery/positioning on frequencies included in sl-FreqInfoToAddModList/sl-FreqInfoToAddModListExt, as specified in 5.8.5; 1> if sl-RadioBearerToReleaseList or sl-RLC-BearerToReleaseList is included in sl-ConfigDedicatedNR within RRCReconfiguration: 2> perform sidelink DRB release as specified in 5.8.9.1a.1; 1> if sl-RLC-BearerToReleaseListSizeExt is included in sl-ConfigDedicatedNR within RRCReconfiguration: 2> perform additional sidelink RLC bearer release as specified in 5.8.9.1a.5; 1> if sl-RadioBearerToAddModList or sl-RLC-BearerToAddModList is included in sl-ConfigDedicatedNR within RRCReconfiguration: 2> perform sidelink DRB addition/modification as specified in 5.8.9.1a.2; 1> if sl-RLC-BearerToAddModListSizeExt is included in sl-ConfigDedicatedNR within RRCReconfiguration: 2> perform additional sidelink RLC bearer addition/modification as specified in 5.8.9.1a.6; 1> if sl-ScheduledConfig is included in sl-ConfigDedicatedNR within RRCReconfiguration: 2> configure the MAC entity parameters, which are to be used for NR sidelink communication/discovery, in accordance with the received sl-ScheduledConfig; 1> if sl-UE-SelectedConfig is included in sl-ConfigDedicatedNR within RRCReconfiguration: 2> configure the parameters, which are to be used for NR sidelink communication/discovery, in accordance with the received sl-UE-SelectedConfig; 1> if sl-MeasConfigInfoToReleaseList is included in sl-ConfigDedicatedNR within RRCReconfiguration: 2> for each SL-DestinationIndex included in the received sl-MeasConfigInfoToReleaseList that is part of the current UE configuration: 3> remove the entry with the matching SL-DestinationIndex from the stored NR sidelink measurement configuration information; 1> if sl-MeasConfigInfoToAddModList is included in sl-ConfigDedicatedNR within RRCReconfiguration: 2> for each sl-DestinationIndex included in the received sl-MeasConfigInfoToAddModList that is part of the current stored NR sidelink measurement configuration: 3> reconfigure the entry according to the value received for this sl-DestinationIndex from the stored NR sidelink measurement configuration information; 2> for each sl-DestinationIndex included in the received sl-MeasConfigInfoToAddModList that is not part of the current stored NR sidelink measurement configuration: 3> add a new entry for this sl-DestinationIndex to the stored NR sidelink measurement configuration. NOTE 1: The UE is expected to update the mapping between the Destination Layer-2 ID and the destination index for the stored NR sidelink measurement configuration after the UE updates the destination list and reports to the gNB. 1> if sl-DRX-ConfigUC-ToReleaseList is included in sl-ConfigDedicatedNR within RRCReconfiguration: 2> for each SL-DestinationIndex included in the received sl-DRX-ConfigUC-ToReleaseList that is part of the current UE configuration: 3> remove the entry with the matching SL-DestinationIndex from the stored NR sidelink DRX configuration information; 1> if sl-DRX-ConfigUC-ToAddModList is included in sl-ConfigDedicatedNR within RRCReconfiguration: 2> for each sl-DestinationIndex included in the received sl-DRX-ConfigUC-ToAddModList that is part of the current stored NR sidelink DRX configuration: 3> reconfigure the entry according to the value received for this sl-DestinationIndex from the stored NR sidelink DRX configuration information; 2> for each sl-DestinationIndex included in the received sl-DRX-ConfigUC-ToAddModList that is not part of the current stored NR sidelink DRX configuration: 3> add a new entry for this sl-DestinationIndex to the stored NR sidelink DRX configuration. NOTE 2: The UE is expected to update the mapping between the Destination Layer-2 ID and the destination index for the stored NR sidelink DRX configuration after the UE updates the destination list and reports to the gNB. 1> if sl-RLC-ChannelToReleaseList is included in sl-ConfigDedicatedNR within RRCReconfiguration: 2> perform PC5 Relay RLC channel release as specified in 5.8.9.7.1; 1> if sl-RLC-ChannelToAddModList is included in sl-ConfigDedicatedNR within RRCReconfiguration or RRCSetup: 2> perform PC5 Relay RLC channel addition/modification as specified in 5.8.9.7.2;

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

5.3.5.14

D.1 Factory automation – motion control D.1.0 General

Factory automation requires communications for closed-loop control applications. Examples for such applications are motion control of robots, machine tools, as well as packaging and printing machines. All other factory automation applications are addressed in Annex D.2. The corresponding industrial communication solutions are referred to as fieldbuses. The pertinent standard suite is IEC 61158. Note that clock synchronization is an integral part of fieldbuses that support motion control use cases. In motion control applications, a controller interacts with a large number of sensors and actuators (e.g. up to 100) that are integrated in a manufacturing unit. The resulting sensor/actuator density is often very high (up to 1 m-3). Many such manufacturing units have to be supported within close proximity within a factory (e.g. up to 100 in automobile assembly line production). In a closed-loop control application, the controller periodically submits instructions to a set of sensor/actuator devices, which return a response within a so-called cycle time. The messages, which are referred to as telegrams, are typically small (≤ 56 bytes). The cycle time can be as low as 2 ms, setting stringent end-to-end latency constraints on telegram forwarding (≤ 1 ms). Additional constraints on isochronous telegram delivery add tight constraints on the lateness (1 s), and the communication service has also to be highly available (99,9999%). Multi-robot cooperation is a case in closed-loop control, where a group of robots collaborate to conduct an action, for example, symmetrical welding of a car body to minimize deformation. This requires isochronous operation between all robots. For multi-robot cooperation, the lateness (1 µs) is to be interpreted as the lateness among the command messages of a control event to the group robots. To meet the stringent requirements of closed-loop factory automation, the following considerations have to be taken: - Limitation to short-range communications. - Use of direct device connection between the controller and actuators. - Allocation of licensed spectrum. Licensed spectrum can further be used as a complement to unlicensed spectrum, e.g. to enhance reliability. - Reservation of dedicated radio interface resources for each link. - Combination of multiple diversity techniques to approach the high reliability target within stringent end-to-end latency constraints (example: frequency, antenna and various forms of spatial diversity, e.g. via relaying) - Utilizing OTA time synchronization to satisfy latency-variation constraints for isochronous operation. A typical industrial closed-loop motion control application is based on individual control events. Each closed-loop control event consists of a downlink transaction followed by a synchronous uplink transaction, both of which are executed within a cycle time. Control events within a manufacturing unit might need to occur isochronously. Factory automation considers application layer transaction cycles between controller devices and sensor/actuator devices. Each transaction cycle consists of (1) a command sent by the controller to the sensor/actuator (downlink), (2) application-layer processing on the sensor/actuator device, and (3) a subsequent response by the sensor/actuator to the controller (uplink). Cycle time includes the entire transaction from the transmission of a command by the controller to the reception of a response by the controller. It includes all lower layer processes and latencies on the radio interface as well the application-layer processing time on the sensor/actuator. Figure D.1.0-1: Communication path for isochronous control cycles within factory units. Step 1 (red): controller requests sensor data (or an actuator to conduct actuation) from the sensor/actuator (S/A). Step 2 (blue): sensor sends measurement information (or acknowledges actuation) to controller. Figure D.1.0-1 depicts how communication can occur in factory automation. In this use case, communication is confined to local controller-to-sensor/actuator interaction within each manufacturing unit. Repeaters can provide spatial diversity to enhance reliability.

3GPP TS 22.261

Service requirements for the 5G system

SA WG1

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

D.1

4.3.1.5.4 Successful outgoing handovers non-DRX

This measurement provides the number of successful outgoing handovers, when DRX is not used (for DRX see [12]). CC. Receipt of a RRC message RRCConnectionReconfigurationComplete sent from the UE to the target (=source) eNB, indicating a successful outgoing intra-eNB handover when DRX is not used (see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]) when DRX is not used, or receipt at the source eNB of UE CONTEXT RELEASE [10] over the X2 from the target eNB following a successful handover when DRX is not used, or if handover is performed via S1, receipt of UE CONTEXT RELEASE COMMAND[9] at the source eNB following a successful handoverwhen DRX is not used. A single integer value. HO.NoDrxOutSucc EUtranCellFDD EUtranCellTDD Valid for packet switched traffic EPS

3GPP TS 32.425

Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN)

SA WG5

3GPP Series : 32 , OAM&P and Charging

4.3.1.5.4

6.6.2.3.1a Additional minimum requirement for E-UTRA (network signalled value “NS_29”)

When "NS_29" is indicated in the cell, the UE emission shall meet the additional requirements specified in Table 6.6.2.3.1a-1 for E-UTRA channels assigned within the frequency ranges 5150-5350 MHz and 5470-5725 MHz. The assigned E-UTRA channel power and alternative adjacent E-UTRA channel power are measured with rectangular filters with measurement bandwidths specified in Table 6.6.2.3.1a-1. If the measured alternative adjacent channel power is greater than –50dBm then the E-UTRAACLR2 shall be higher than the value specified in Table 6.6.2.3.1a-1. Table 6.6.2.3.1a-1: Additional E-UTRAACLR requirement

3GPP TS 36.101

Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception

RAN4

3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology

6.6.2.3.1a

4.21 Secondary RAT Usage Data Reporting Procedure

The procedure in Figure 4.21-1 may be used to report Secondary RAT Usage Data from NG-RAN node to the AMF. It is executed by the NG-RAN node to report the Secondary RAT Usage Data information towards AMF which is then reported towards SMF. The procedure in Figure 4.21-2 may be used to report the Secondary RAT Usage Data from AMF towards the SMF. Optionally, it is used to report the Secondary RAT Usage Data from V-SMF to the H-SMF when the reporting to H-SMF is activated. Figure 4.21-1: RAN Secondary RAT Usage Data Reporting procedure 1. The NG-RAN, if it supports Dual Connectivity with Secondary RAT (using NR radio, E-UTRA radio, or unlicensed spectrum using NR or E-UTRA radio) and it is configured to report Secondary RAT Usage Data for the UE, depending on certain conditions documented in this specification, it shall send a RAN Usage Data Report message to the AMF including the Secondary RAT Usage Data for the UE. The NG-RAN node will send only one RAN Usage Report for a UE when the UE is subject to handover by RAN. The RAN Usage Data Report includes a Handover Flag to indicate when the message is sent triggered by a handover. Figure 4.21-2: SMF Secondary RAT Usage Data Reporting procedure The NG-RAN, if it supports Dual Connectivity with Secondary RAT (using NR radio, E-UTRA radio, or unlicensed spectrum using NR or E-UTRA radio) and it is configured to report Secondary RAT usage data for the UE, it shall include the Secondary RAT usage data for the UE to the AMF in certain messages depending on certain conditions documented elsewhere in this TS. 1. The AMF forwards the N2 SM Information (Secondary RAT Usage Data) to the SMF in a Nsmf_PDUSession_UpdateSMContext Request. 2. The V-SMF sends the Nsmf_PDUSession_Update (Secondary RAT Usage Data) message to the H-SMF. 3. The H-SMF acknowledges receiving the Secondary RAT Usage data for the UE. 4. The V-SMF acknowledges receiving the Secondary RAT Usage data back to the AMF.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.21

5.5.3.10 Charging principles for 5G non-roaming Mobile Virtual Network Operators (MVNOs) charging

For scenarios in which subscribers have a subscription with an MVNO which allows usage of 5G data connectivity while in the home MNO, the MNO shall be able to collect charging information related to 5G data connectivity usage for each MVNO, for wholesale. The MVNO deploys their own billing and charging (CHF), but no other NFs. The charging mechanism in the MNO collects charging information related to the 5G data connectivity usage for each UE and conveys this charging information to the MVNO for each UE. The MVNO uses the charging information collected for retail charging (MVNO to subscriber). Charging for MVNO scenario is covered by the 5G data connectivity domain converged charging architecture specified in TS 32.255[ Telecommunication management; Charging management; 5G data connectivity domain charging; Stage 2 ] [15]. N47 reference point is also used when an additional actor (i.e. MVNO) performs retail charging for its own subscribers. In such a case N47 is the reference point between SMF in the MNO and CHF in the MVNO.

3GPP TS 32.240

Telecommunication management; Charging management; Charging architecture and principles

SA WG5

3GPP Series : 32 , OAM&P and Charging

5.5.3.10

D.2 Determination of UE presence in Area of Interest by NG-RAN

If the AMF has requested for the Area of Interest, NG-RAN determines the UE presence of Area Of Interest as follows: - IN: - if the UE is inside the Area Of Interest and the UE is in RRC_CONNECTED state; or - if the UE is inside an RNA which is completely contained within the Area Of Interest. - OUT: - if the UE is outside the Area Of Interest in RRC_CONNECTED state; or - if UE is inside an RNA which does not contain any part of Area Of Interest. - UNKNOWN: - if none of above conditions for IN or OUT is met.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

D.2

– RRCReestablishmentComplete

The RRCReestablishmentComplete message is used to confirm the successful completion of an RRC connection re-establishment. Signalling radio bearer: SRB1 RLC-SAP: AM Logical channel: DCCH Direction: UE to Network RRCReestablishmentComplete message -- ASN1START -- TAG-RRCREESTABLISHMENTCOMPLETE-START RRCReestablishmentComplete ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { rrcReestablishmentComplete RRCReestablishmentComplete-IEs, criticalExtensionsFuture SEQUENCE {} } } RRCReestablishmentComplete-IEs ::= SEQUENCE { lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension RRCReestablishmentComplete-v1610-IEs OPTIONAL } RRCReestablishmentComplete-v1610-IEs ::= SEQUENCE { ue-MeasurementsAvailable-r16 UE-MeasurementsAvailable-r16 OPTIONAL, nonCriticalExtension RRCReestablishmentComplete-v1800-IEs OPTIONAL } RRCReestablishmentComplete-v1800-IEs ::= SEQUENCE { flightPathInfoAvailable-r18 ENUMERATED {true} OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } -- TAG-RRCREESTABLISHMENTCOMPLETE-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

5.16.3.8.2 Access Selection for SMS over NAS

It should be possible to provision UEs with the HPLMN SMS over NAS operator preferences on access selection for delivering SMS over NAS signalling. Based on the SMS over NAS preference: - SMS is preferred to be invoked over 3GPP access for NAS transport: the UE attempts to deliver MO SMS over NAS via 3GPP access if the UE is both registered in 3GPP access and non-3GPP access. - SMS is preferred to be invoked over non-3GPP access for NAS transport: the UE attempts to deliver MO SMS over NAS via non-3GPP access if the UE is both registered in 3GPP access and non-3GPP access. If delivery of SMS over NAS via non-3GPP access is not available, the UE attempts to deliver SMS over NAS via 3GPP access.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.16.3.8.2

Annex F (normative): Dedicated bearer activation in combination with the default bearer activation at Attach and UE requested PDN connectivity procedures

For WB-E-UTRAN, it shall be possible for the PDN GW to initiate the activation of dedicated bearers (as specified in clause 5.4.1) as part of the attach procedure (as specified in clause 5.3.2.1) or as part of the UE requested PDN connectivity procedure (as specified in clause 5.10.2) over WB-E-UTRAN. However, the result of the dedicated bearer activation procedure shall be logically separate from the Attach procedure, meaning that the result of the Attach procedure is not dependent on whether the Dedicated bearer activation procedure succeeds or not. On the other hand, the dedicated bearer activation may only be regarded as successful if the Attach procedure completes successfully. The messages of the Dedicated bearer activation can be sent together with the messages of the Attach procedure or of the UE requested PDN connectivity procedure (i.e. Attach accept or PDN Connectivity Accept), as shown in the Figure and explanation below. On the S1 and Uu interfaces the messages for the default bearer activation at Attach and UE requested PDN connectivity procedures and for the Dedicated Bearer Activation procedure are combined into a single message. If the MME has sent an Attach Accept message towards the eNodeB, and then the MME receives a Create Bearer Request before the MME receives the Attach Complete message, the MME shall wait for the Attach procedure to complete before the MME continues with Dedicated Bearer Activation procedure. It shall be possible that multiple dedicated bearers can simultaneously be activated in the signalling flow shown below. Figure F.1: Dedicated bearer activation in combination with the default bearer activation at attach or UE requested PDN connectivity NOTE 1: Parameters related to dedicated bearer activation are written in italics. Figure F.1 describes the activation of dedicated bearer(s) in combination with the default bearer activation either as part of the Attach procedure (with specific steps 1a, 7a, 10a) or as part of the UE requested PDN connectivity procedure (with specific steps 1b, 7b, 10b). The following steps below require special attention: 5. (On the P-GW-S-GW interface) Create Session Response message of the Attach procedure or UE-requested PDN connectivity procedure is combined with Create Bearer Request message of the Dedicated Bearer Activation Procedure 6. (On the S-GW-MME interface) Create Session Response message of the Attach procedure or UE-requested PDN connectivity procedure is combined with the Create Bearer Request message of the Dedicated Bearer Activation Procedure 7a. For Attach procedure: If the MME receives a Create Session Response message combined with a Create Bearer Request message, the MME shall send the S1-AP Initial Context Setup Request message to the eNodeB, including the NAS parts for both the Attach Accept message of the Attach procedure and the Bearer Setup Request of the Dedicated Bearer Activation Procedure. NOTE 2: The MME shall not send a Bearer Setup Request message of a new Dedicated Bearer Activation procedure to the eNodeB before sending the Attach Accept message of the Attach procedure to the eNodeB. If the MME has already sent the Attach Accept message of the Attach procedure to the eNodeB, the MME shall wait for the Attach Complete message to arrive before sending a separate Bearer Setup Request of a Dedicated Bearer Activation procedure. 7b. For UE requested PDN connectivity procedure: If the MME receives a Create Session Response message combined with a Create Bearer Request message, the MME shall send the S1-AP Bearer Setup Request message to the eNodeB, including the NAS parts for both the PDN Connectivity Accept message and the Bearer Setup Request of the Dedicated Bearer Activation Procedure. 8-9. The radio bearer establishment of the default and dedicated bearer(s) is performed in the same RRC message. 10a. For Attach procedure: The eNodeB sends the S1-AP Initial Context Setup Response message to the MME. The MME shall be prepared to receive this message either before or after, some or all, of the Uplink NAS Uplink Transport messages sent in step 12. 10b. For UE requested PDN connectivity procedure: The eNodeB sends the S1-AP Bearer Setup Response message to the MME. The MME shall be prepared to receive this message either before or after, some or all, of the Uplink NAS Uplink Transport messages sent in step 12. 11. For the Attach procedure: The UE sends the eNodeB a Direct Transfer message containing the Attach Complete (Session Management Response for the Default Bearer) message as response of the attach procedure, and Direct Transfer messages containing the Session Management Responses of the dedicated bearer setup procedure. For the UE requested PDN connectivity procedure: The UE NAS layer builds a PDN Connectivity Complete (Session Management Response) for the Default Bearer Activation and Dedicated Bearer Activation Procedures. The UE then sends Direct Transfer (PDN Connectivity Complete) message to the eNodeB. The NAS messages to establish the EPS bearers shall be handled individually by the UE and be sent in separate RRC Direct Transfer messages. 12. The eNodeB sends an Uplink NAS Transport message to the MME, which contains the NAS messages from the RRC message in step 11. There may be multiple Uplink NAS Transport messages when the UE sends multiple RRC messages containing NAS messages in step 11. 13. Upon reception of the response messages in both step 10 and step 12, the Modify Bearer Request message of the Attach procedure or UE requested PDN connectivity procedure is combined with the Create Bearer Response message of the Dedicated Bearer Activation Procedure. After that, the Serving GW continues with sending a Create Bearer Response message to the PDN 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")

Annex

4.3.2 Services expected from physical layer

The physical layer provides the following services to MAC: - data transfer services; - signalling of HARQ feedback; - signalling of Scheduling Request; - measurements (e.g. Channel Quality Indication (CQI)). The access to the data transfer services is through the use of transport channels. The characteristics of a transport channel are defined by its transport format (or format set), specifying the physical layer processing to be applied to the transport channel in question, such as channel coding and interleaving, and any service-specific rate matching as needed.

3GPP TS 36.321

Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification

RAN2

3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology

4.3.2

4.4.6.2 IP Throughput in UL

This measurement provides IP throughput in uplink. For an eNodeB serving one or more RNs, packets transmitted between the E-UTRAN and RNs are excluded, i.e., only packets transmitted between the eNodeB (or RN) and UEs are counted. The measurement is also applicable to RN DER(N=1) This measurement is obtained according to the following formula based on the “ThpVolUl” and “ThpTimeUl” defined for the “Scheduled IP Throughput inUL” in 3GPP TS 36.314[ Evolved Universal Terrestrial Radio Access (E-UTRA); Layer 2 - Measurements ] [11] for each QCI. Each measurement is a real value representing the volume in kbit. The number of measurements is equal to the number of QCIs. The measurement name has the form DRB.IPThpUl.QCI where QCI identifies the E-RAB level quality of service class. EUtranCellFDD EUtranCellTDD Valid for packet switched traffic EPS This measurement is to support the Integrity KPI “E-UTRAN IP Throughput” 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.6.2

5.15.1.2.1 Sidelink HARQ Entity

There is one Sidelink HARQ Entity at the MAC entity for transmission on SL-DCH, which maintains one Sidelink process for each MAC PDU. For each subframe of the SL-DCH the Sidelink HARQ Entity shall: - if a grant and a MAC PDU has been delivered for this subframe to the Sidelink HARQ Entity: - deliver the MAC PDU and the grant to the Sidelink process; - instruct the Sidelink process to trigger a new transmission. - else, if this subframe corresponds to retransmission opportunity for the Sidelink process: - instruct the Sidelink process to trigger a retransmission.

3GPP TS 36.321

Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification

RAN2

3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology

5.15.1.2.1

5.7.2 Scenario

During initial authorisation operate procedures, MNO will identify whether this UAV is UAS-capable UE with certain 3GPP UAS communication capability, and interaction capability with UTM, or the UAV is attached external UE (e.g. a smart phone) with limited or no 3GPP UAS communication capability as well as interaction capability with UTM. If the UAV is authorized to be airborne, MNO may base on the type of the UE (UAS specific UE vs. regular UE) to schedule network resource accordingly, such as use different /optimized power control methods and mobility enhancement procedures, more specifically, mobility parameters for this UAV according to the type (e.g. the speed limit reflected by the type can affect the parameters used for handover). If the UAV is embedded with UAS-capable UE, which means the UAV can interact with UTM, so MNO may establish further communication between UAS and UTM. In addition, different charging rules will be used to the UAV by the serving MNO. Also an MNO may retrieve those capability/type of UAV according to subscription identifiers information, so MNO can determine whether or not to allow the UE to use certain Aerial UE function (defined in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] ) or enable certain RAN capability which can be used for mobility enhancement and interference mitigation. If this UAV is embedded with a UAS-capable UE but pretend to be a regular ground base UE. It may pass MNO’s authentication and become airborne. Later MNO may identify that this is a rogue UAV basing on its moving behaviours which is not matched with its subscription used for the authentication. The MNO will report this unauthorized UAV with related information to the UTM or law enforcement. MNO may also report an unauthorized UAV which only equips with ground based UE but fly into an area which only UAV with UAS-capable UE is allowed.

3GPP TS 22.825

Study on Remote Identification of Unmanned Aerial Systems (UAS)

SA WG1

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

5.7.2

F.2 5GS Bridge configuration

For 5GS integrating with fully-centralized model TSN network, the CNC provides TSN information to the AF. Figure F.2-1: 5GS Bridge information configuration 1. CNC provides per-stream filtering and policing parameters according to clause 8.6.5.2.1 of IEEE Std 802.1Q [66] to AF and the AF uses them to derive TSN QoS information and related flow information. The CNC provides the forwarding rule to AF according to clause 8.8.1 of IEEE Std 802.1Q [66]. The TSN AF uses this information to identify the DS-TT MAC address of corresponding PDU session. The AF determines if the stream is UE-UE TSC and divides the stream into UL and DL streams for PDU Sessions corresponding to ingress DS-TT Ethernet port and egress DS-TT port(s) as specified in clause 5.28.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] and separately triggers following procedures for the UL and DL streams. 2. The AF determines the MAC address of a PDU Session based on the previous stored associations, then triggers an AF request procedure. The AF request includes the DS-TT MAC address of the PDU session. Based on the information received from the CNC, 5GS bridge delay information and the UE-DS-TT residence time, the TSN AF determines the TSN QoS information and TSC Assistance Container for one or more TSN streams and sends them to the PCF. The TSN AF also provides Service Data Flow Filter containing Flow description also includes Ethernet Packet Filters. 3. When PCF receives the AF request, the PCF finds the correct SMF based on the DS-TT MAC address of the PDU session and notifies the SMF via Npcf_SMPolicyControl_UpdateNotify message. After mapping the received TSN QoS parameters for TSN streams to 5GS QoS, the PCF triggers Npcf_SMPolicyControl_UpdateNotify message to update the PCC rule to the SMF. The PCC rule includes the Ethernet Packet Filters, the 5GS QoS profile along with TSC Assistance Container. 4. SMF may trigger the PDU Session Modification procedure to establish/modify a QoS Flow to transfer the TSN streams. During this procedure, the SMF provides the information received in PCC rules to the UPF via N4 Session Modification procedure. Upon reception of the TSC Assistance Container, the SMF determine the TSCAI for QoS flow and sends the TSCAI along with the QoS profile to the NG RAN. 5. If needed, the CNC provides additional information (e.g. the gate control list as defined in clause 8.6.8.4 of IEEE Std 802.1Q [66]) to the TSN AF. 6. The AF determines the MAC address of a PDU Session for the configured port based on the previous stored associations, this is used to deliver the Port Management information to the correct SMF that manages the port via PCF. The AF triggers an AF request procedure. The AF request includes the DS-TT MAC address (i.e. the MAC address of the PDU Session), TSN QoS Parameters, Port Management information Container and the related port number as defined in clause 5.28.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The port number is used by SMF to decide whether the configured port is in DS-TT or NW-TT. NOTE: When TSN AF needs to convey 5GS Bridge- or NW-TT port-specific information to the NW-TT/UPF, the TSN AF chooses an arbitrary AF Session related to the corresponding 5GS bridge and sends the 5GS Bridge-specific information inside a User plane node Management Information Container (UMIC) or NW-TT Port Management Information Container (NW-TT PMIC) as specified in TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 7. The PCF determines the SMF based on the MAC address received in the AF request, the PCF maps the TSN QoS information provided by the AF to PCC rules as described in clause 5.28.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The PCF includes the TSC Assistance Container received from the AF with the PCC rules and forwards it to the SMF. The PCF transparently transports the received Port Management information Container and related port number to SMF via Npcf_SMPolicyControl_UpdateNotify message. 8a. If the SMF decides the port is on DS-TT based on the received port number, the SMF transports the received Port Management information Container to the UE/DS-TT in PDU Session Modification Request message. 8b. If the SMF decides the port is on NW-TT based on the received port number, the SMF transports the received Port Management information Container to the UPF/NW-TT in N4 Session Modification Request message. SMF provides the Ethernet Packet Filters as part of the N4 Packet Detection rule to the UPF/NW-TT. If the UPF sends a Clock Drift Report to the SMF as described in clause 5.27.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], the SMF adjusts the Burst Arrival Time, Periodicity and Survival Time (if present) from a TSN grandmaster clock to the 5G clock and sends the updated TSCAI to NG-RAN.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

F.2

5.4.7.2 Maintenance of PUR Uplink Time Alignment

MAC entity may be configured with timer pur-TimeAlignmentTimer by upper layers as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8], clause 5.3.8.3. The MAC entity shall: - when pur-TimeAlignmentTimer configuration is received from upper layers: - start or restart pur-TimeAlignmentTimer. - when pur-TimeAlignmentTimer is released by upper layers: - stop the pur-TimeAlignmentTimer, if running. - when a Timing Advance Command MAC control element is received or PDCCH indicates timing advance adjustment as specified in TS 36.212[ Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and channel coding ] [5] and if a NTA has been stored or maintained: - if the Timing Advance Command MAC control element or PDCCH indicating timing advance adjustment is addressed with a PUR-RNTI: - apply the Timing Advance Command or the timing advance adjustment; - start or restart the pur-TimeAlignmentTimer, if configured; - indicate to upper layers that the Timing Advance value has been adjusted. - upon considering a Random Access procedure successfully completed: - start or restart the pur-TimeAlignmentTimer, if configured; - indicate to upper layers that the Timing Advance value has been adjusted; - if a temporary NTA has been stored, delete the stored temporary NTA. - upon considering a Random Access procedure unsuccessfully completed, if a temporary NTA has been stored: - set the NTA to the stored temporary NTA; - delete the stored temporary NTA. Upon request from upper layers, MAC entity shall indicate whether pur-TimeAlignmentTimer is running.

3GPP TS 36.321

Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification

RAN2

3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology

5.4.7.2

5.21.3.3 Reliability of NF instances within the same NF Set

The NF producer instance is the NF instance which host the NF Service Producer. When the NF producer instance is not available, another NF producer instance within the same NF Set is selected. For Direct Communication mode, the NF Service consumer may subscribe to status change notifications of NF instance from the NRF. If the NF Service consumer is notified by the NRF or detects by itself (e.g. request is not responded) that the NF producer instance is not available anymore, another available NF producer instance within the same NF Set is selected by the NF Service consumer. For Indirect Communication mode, the SCP or NF Service consumer may subscribe to status change notifications of NF instance from the NRF and selects another NF producer instance within the same NF Set if the original NF producer instance serving the UE is not available anymore. NOTE: It is up to the implementation on how the SCP knows a NF producer instance is not available anymore.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.21.3.3

10.5.5.36 PLMN identity of the CN operator

The purpose of the PLMN identity of the CN operator information element is to indicate the PLMN identity of the CN operator that has accepted the GPRS attach request or routing area update request in a shared network or in a multi-operator core network (MOCN) with common GERAN. The PLMN identity of the CN operator is a type 4 information element with 5 octets length. The PLMN identity of the CN operator information element is coded as shown in figure 10.5.5.36-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.5.36-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.5.36-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] PLMN identity of the CN operator information element Table 10.5.5.36-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : PLMN identity of the CN operator 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.36

E.2.1 High level common architecture

The overall logical charging architecture is depicted below. The Rf and Ro reference points are applicable to GPRS, EPC or IMS NEs only, whereas the Nchf interface is applicable to 5GC NFs only. Figure E.2.1.1: High level overall charging architecture and information flows When the target charging system (i.e. 5G CCS or EPC OCS/OFCS) needs to support termination of a reference point or interface from the opposite type of core network (i.e. Ro/Rf or Nchf) implementations will need to include interworking between the HTTP used by SBI and the Diameter protocol.

3GPP TS 32.240

Telecommunication management; Charging management; Charging architecture and principles

SA WG5

3GPP Series : 32 , OAM&P and Charging

E.2.1

5.6.2 Channel Access Priority Classes

The Channel Access Priority Classes (CAPC) of radio bearers and MAC CEs are either fixed or configurable for operation in FR1: - Fixed to the lowest priority for the padding BSR and recommended bit rate MAC CEs; - Fixed to the highest priority for SRB0, SRB1, SRB3 and other MAC CEs; - Configured by the gNB for SRB2 and DRB. When choosing the CAPC of a DRB, the gNB takes into account the 5QIs of all the QoS flows multiplexed in that DRB while considering fairness between different traffic types and transmissions. Table 5.6.2-1 below shows which CAPC should be used for which standardized 5QIs i.e. which CAPC to use for a given QoS flow. NOTE: A QoS flow corresponding to a non-standardized 5QI (i.e. operator specific 5QI) should use the CAPC of the standardized 5QI which best matches the QoS characteristics of the non-standardized 5QI. Table 5.6.2-1: Mapping between Channel Access Priority Classes and 5QI When performing Type 1 LBT for the transmission of an uplink TB (see TS 37.213[ Physical layer procedures for shared spectrum channel access ] [37], clause 4.2.1.1) and when the CAPC is not indicated in the DCI, the UE shall select the CAPC as follows: - If only MAC CE(s) are included in the TB, the highest priority CAPC of those MAC CE(s) is used; or - If CCCH SDU(s) are included in the TB, the highest priority CAPC is used; or - If DCCH SDU(s) are included in the TB, the highest priority CAPC of the DCCH(s) is used; or - The lowest priority CAPC of the logical channel(s) with MAC SDU multiplexed in the TB is used otherwise.

3GPP TS 38.300

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

RAN2

3GPP Series : 38 , Radio technology beyond LTE

5.6.2

5.8.2.10 UP Tunnel Management

5GC shall support per PDU Session tunnelling on N3 between (R)AN and UPF and N9 between UPFs. If there exist more than one UPF involved for the PDU Session, any tunnel(s) between UPFs (e.g. in the case of two UPFs, between the UPF that is an N3 terminating point and the UPF for PDU Session Anchor) remains established when a UE enters CM-IDLE state. In the case of downlink data buffering by UPF, when mobile terminated (MT) traffic arrives at the PDU Session Anchor UPF, it is forwarded to the UPF which buffer the data packet via N9 tunnel. See clause 5.8.3 for more details on UPF buffering. In the case of Home Routed roaming, the SMF in HPLMN is not aware of the UP activation state of a PDU Session. When the UP connection of the PDU Session is deactivated, the SMF may release the UPF of N3 terminating point. In that case the UPF (e.g. the Branching Point/UL CL or PDU Session Anchor) connecting to the released UPF of N3 terminating point will buffer the DL packets. Otherwise, when the UPF with the N3 connection is not released, this UPF will buffer the DL packets. When the UP connection of the PDU Session is activated due to a down-link data arrived and a new UPF is allocated to terminate the N3 connection, a data forwarding tunnel between the UPF that has buffered packets and the newly allocated UPF is established, so that the buffered data packets are transferred from the old UPF that has buffered packets to the newly allocated UPF via the data forwarding tunnel. For a PDU Session whose the UP connection is deactivated and the SMF has subscribed the location change notification, when the SMF is notified of UE's new location from the AMF and detects that the UE has moved out of the service area of the existing intermediate UPF, the SMF may decide to maintain the intermediate UPF, remove the established tunnel between UPFs (in the case of removal of the intermediate UPF) or reallocate the tunnel between UPFs (in the case of reallocation of the intermediate UPF).

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.8.2.10

6.8.1.1.2.4 UE registration over a second access type to the same AMF

It is assumed in this clause that the UE is already registered over a first access type (say access A). Clauses 6.8.1.1.2.1 and 6.8.1.1.2.2 applies as well when the UE attempts to register over a new access type (access B) to the same AMF with the following addition/exception: Whenever the UE registers over a second access type (access B) to the same AMF, with the intention to transitioning from RM-DEREGISTERED to RM-REGISTERED state, then a full native 5G NAS security context is already available in the UE and the AMF. In this case, the UE shall directly take into use the available full 5G NAS security context and use it to protect the Registration Request over the second access using the distinct pair of NAS COUNTs for this second access type (access B). The AMF may decide to run a new primary authentication as part of the Registration procedure on this second access (access B). If a new primary authentication is run, then the new derived partial 5G NAS security context needs to be taken into use on this second access (access B) with a NAS SMC using the distinct pair of NAS COUNTs for this second access. As the UE is already registered on the first access (access A), then the AMF needs to run a NAS SMC procedure on the first access in order to take the partial 5G NAS security context into use as described in clause 6.4.2.2. If there is a need for the AMF to take a new partial 5G NAS security context into use, derived from primary authentication executed on the first access (access A), then the AMF needs to send a NAS SMC to the UE on the second access (access B) in order to take the new partial 5G NAS security context into use as described in clause 6.4.2.2.

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

6.8.1.1.2.4

5.3.15 Transmission failure abnormal case in the UE

The abnormal case 5GMM uplink message transmission failure indication by lower layers can be identified for 5GMM procedures: When it is specified in the relevant procedure that it is up to the UE implementation to re-run the ongoing procedure that triggered that procedure, the procedure can typically be re-initiated using a retransmission mechanism of the uplink message (i.e. the one that has previously failed to be transmitted) with new sequence number and message authentication code information thus avoiding to re-start the whole procedure. NOTE: The transmission failure can happen due to TAI change. The lower layer might take some time to read the system information and determine if the current TAI is changed. Therefore, the information of TAI change can be sent to the NAS layer a little after receiving the transmission failure indication from the lower layer. How to handle the retransmission procedure caused by the possible delayed TAI change information is up to UE implementation.

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

5.1 Charging data generation and quota supervision

The CTF embedded in all charging relevant network elements/network functions collects charging information within the NE/NF concerning the use of network resources by the mobile end users. These network resources may pertain to bearer (e.g. CS, PS), PDU session (e.g. 5GS), subsystem (e.g. IMS sessions) or service (e.g. MMS) usage / consumption. The various charging levels are further described in clause 5.3. The purpose of offline charging is to transform the charging information into CDRs that are post-processed within the BD, e.g. for the purpose of generating bills. While the collection of charging information used for the CDRs occurs during the network resource usage, there is no impact of offline charging on the use of the resources. All activities involved in the transformation of the charging information into end user bills, and the collection of the end user charges incurred in these bills, occur offline to, or after, the network resource usage. The purpose of online charging is to furnish charging information to the OCS/CCS in order to perform Credit-Control before the network resource usage is permitted. To this end, a prepaid subscriber account has to exist in the OCS/CCS, against which the resource usage can be billed. Hence all activities to assess the requested resource usage, to determine its value in monetary or other units, and to debit these units from the subscriber account, must occur prior to or at least, during the resource usage, i.e. online with respect to resource usage. Depending on the circumstances, a final evaluation must occur when resource usage ends. Hence, two cases must be distinguished: - Direct Debiting: the requested resource can be determined and billed in a one-off procedure. In that case, the resource usage is debited from the subscriber account immediately when processing the charging event, and the permission for the resource usage is returned to the network. An example of this may be the forwarding of a terminating short message from the MSC to the end user. In this scenario, it is generally required that the network can guarantee resource usage execution in order to avoid over-billing the user. - Unit Reservation: the OCS/CCS cannot a priori know the amount of resources that the end user may eventually consume, or it cannot be assumed a priori that the resource usage request can be (completely) fulfilled. In this case, a certain amount of (monetary or non-monetary) units is blocked, or reserved, on the subscriber’s account on the OCS/CCS, and permission to use an amount of resources that matches the unit reservation is returned to the network. When the granted units have been used or a new, not yet authorised chargeable event occurs, the network must send a new request for unit allocation to the OCS/CCS. When resource usage has been executed, the actual amount of resource usage (i.e. the used units) must be returned by the NE/NF to the OCS/CCS so that eventually over-reserved amounts can be re-credited to the subscriber account, assuring that the correct amount gets debited. Charging information is collected by the CTF based on chargeable events that describe the user(s) and their requested network resource usage. The chargeable events are specific to each domain / service / subsystem and specified in the respective middle tier TS. For each chargeable event, a matching charging event is formed and immediately sent to its destination, i.e. the CDF in offline charging,the OCF in online charging or CHF in the converged charging. Again, the event information is specific to the domain / service / subsystem and defined in the respective middle tier TS. While the accounting metrics (provided by the Accounting Metrics Collection part of the CTF) used in online, offline and converged charging are generally identical, the information comprising chargeable events (determined by the Accounting Data Forwarding part of the CTF) may be different between online,offline and converged charging. Note also that online and offline charging may occur simultaneously, i.e. for the same resource usage the CTF may send an offline charging event to the CDF and an online charging event to the OCF. In that particular case, Credit-Controloccurs for that resource usage but at the same time, CDRs are created in offline charging. Alternatively, if CDRs are required for online charged resource usage, this can be achieved by generating these CDRs in the OCS, as depicted in clause 4.3.2.3. The online,offline charging and converged charging can be categorised into two distinct classes, namely event based charging and session based charging. Event based charging implies that a chargeable event is defined as a single end-user-to-network transaction, e.g. the sending of a multimedia message. This chargeable event is then mapped to an appropriate charging event, resulting in a single CDR or in a single Credit-Control and resource usage authorisation procedure. In contrast, session based charging is characterised by the existence of a user session, such as a circuit call, an IP CAN bearer, an PDU session, or an IMS session. This user session is then matched by a charging session, resulting in the generation of multiple chargeable/charging events and the creation of one or more CDRs in offline charging/converged charging or the performance of a Credit-Control session in online charging/converged charging. The following paragraphs describe the event versus session based charging in more detail for both online, offline charging. converged charging. - Event based charging. The (chargeable) event is recognised in the NE /NF that handles it, based on e.g. signalling exchange between the user equipment and the NE/NF. The event is then mapped onto a single charging event as specified in the middle tier TS that applies to that NE/NF. - In online charging, the charging event is transferred to the EBCF via the Ro or CAP reference point, and the chargeable event is authorised after successfully performing Credit-Control on the subscriber account. The complete procedure must occur in real-time. If the chargeable event is not authorised by the OCS (e.g. when the subscriber account does not contain sufficient credit), the NE rejects the resource usage pertaining to that chargeable event. - The event charging procedure may occur with or without reservation of units from the subscriber’s account ("Event Charging with Unit Reservation" (ECUR),"Immediate Event Charging" (IEC) or "Post Event Charging" (PEC), respectively), as described above. Furthermore, if the procedure does include reservation, the OCS/CCS may choose to authorise one or more occurrences of the chargeable event (i.e. allot one or more "service"units). For example, multiple short messages may be authorised upon the first SMS request from the user. - In offline charging, the charging event is transferred to the CDF via the Rf reference point. The CDF produces a matching CDR, which is then sent to the CGF via the Ga reference point. The CDR will eventually be transferred to the BD in a CDR file, together with other CDRs of the same or different types, according to file transfer configuration by the operator. While there is no real-time requirement on any particular part of this procedure, the system should be capable of completing the process from the detection of the chargeable event up to, and including, CDR transfer to the CGF, in near real-time. - Session based charging. The start of the user session is recognised by the NE/NF that handles the session, based on e.g. signalling exchange between the user equipment and the NE/NF. This chargeable event is then mapped onto a charging event as specified in the middle tier TS that applies to that NE/NF. - In online charging, an "initial" charging event (session start) is transferred to the SBCF via the Ro or CAP reference point and the start of the user session is authorised after successfully performing Credit-Control on the subscriber account. The NE may delay the actual start of the user session until authorisation has been obtained (cf. 4.3.2.1). As there is no information available at this time concerning the overall evaluation of the session (e.g. complete duration or data volume of the session), session based charging always involves reservation of units from the subscriber’s account ("Session based Charging with Unit Reservation" (SCUR)): the OCS reserves credit from the subscriber account and returns the corresponding quota (e.g. units specifying the number of minutes or bytes allowed) to the NE. The NE, in turn, uses the provided quota to supervise the actual network resource consumption. In the case that another chargeable event occurs for the session, the network element issues an "interim" charging event in order to also authorise this new chargeable event. When the quota is used up, the network element either issues another interim charging event, requesting further units to be allotted, or terminates the session if previously instructed to do so by the OCS. Once the session is terminated in the network element, the consumed units are reported back to the OCS with a "final" charging event. The credit control session is then terminated, and the OCS returns the value of any unused quota (as reported by the NE) to the subscriber’s account. The complete procedure of receiving, processing and responding to an online charging event, must occur in real-time. Note that this procedure can occur in parallel for several concurrent services running on the same user session. For each charging event received during the session, the OCS/CCS decides whether to authorise the resource usage or whether to decline the request (e.g. when the subscriber account does not contain sufficient credit). If, at any time within the session, the OCS/CCS determines not to authorise the chargeable event, it rejects the request sent by the network element/network functions, causing the NE/NF to disallow the resource usage pertaining to that chargeable event. It must be noted that this does not necessarily terminate the user session. E.g. in the case of credit exhaustion, the session could be redirected to a credit recharging site. - In offline charging, the "initial" charging event is transferred to the CDF via the Rf reference point. Upon termination of the subscriber session, or when a new chargeable event occurs (as specified in the respective middle tier TS), further charging events ("final" or "interim" events, respectively) are sent for the session from the NE to the CDF. The CDF formats one or more of these events into CDRs according to CDR formats specified in the middle tier TSs, and in accordance with CDR generation triggers configured by the operator. Upon its completion, the CDR will be sent forward to the CGF via the Ga reference point, and a new CDR will be opened by the CDF for the same session. Finally, the CDRs will eventually be transferred to the BD in a CDR file, together with other CDRs of the same or different types, according to file transfer configuration by the operator. The system should be capable of completing the process of chargeable event detection and charging event forwarding, CDR generation / closure and CDR forwarding as closely as possible in real-time. However, a significant time may pass between the reception of the first charging event for a CDR and the time the CDR is closed, depending on the CDR generation triggers configured by the operator. For both event and session based charging, it has been specified above that the NE/NF shall disallow the requested resource usage when the associated chargeable event is not authorised by the OCS/CCS. The most typical case for the OCS/CCS to refuse authorisation is the expiry of the subscriber account. However, depending on operator policy, even in the case of account expiry the OCS/CCS may determine to allow the resource usage to occur / to continue. For example, if the interruption of the user session renders the complete session useless to the end user, it would be unfair to debit the user’s account for the portion of the session that was executed. While the decision making procedures and the special treatment of this situation are internal to the OCS/CCS, the important aspect to note is that the OCS/CCS must grant authorisation towards the network in order to allow the event to occur or the session to continue, effectively making the event or (remainder of the) session free of charge. Clause 5.2 provides a detailed analysis of the possible relationships between charging events, Credit-Control processes, CDRs and CDR files as well as their triggers. Both CDR and online charging data generation and contents should be flexible and unnecessary redundancy in data should be avoided. Clause 5.4 describes how the generation of charging data can be configured by the network operator in order to support the above requirement. Charging data are collected for successful and selected unsuccessful resource usage attempts. The resource usage attempt is seen as being successful in the network element/network function (where the chargeable event is detected) when the user event is successfully completed, or the user session has started. Further details, such as the indication of failure and failure reasons in charging events and CDRs, are specified in the middle tier TSs. NOTE: Some of the terminology used in this clause differs from IETF RFC 4006 [402] that forms the basis for the online charging application. For example, the DCCA uses "session" and "event" more in terms of the Credit-Control protocol rather than in terms of user activity, as the present document does. The mapping of the concepts and terminology used to describe the concepts, is described in TS 32.299[ Telecommunication management; Charging management; Diameter charging applications ] [50].

3GPP TS 32.240

Telecommunication management; Charging management; Charging architecture and principles

SA WG5

3GPP Series : 32 , OAM&P and Charging

5.1

8.4.1.2.4 Minimum Requirement 2 Tx Antenna Port (demodulation subframe overlaps with aggressor cell ABS and CRS assistance information are configured)

For the parameters for non-MBSFN ABS specified in Table 8.4.1-1 and Table 8.4.1.2.4-1, the average probability of a missed downlink scheduling grant (Pm-dsg) shall be below the specified value in Table 8.4.1.2.4-2. For the parameters for MBSFN ABS specified in Table 8.4.1-1 and Table 8.4.1.2.4-3, the average probability of a missed downlink scheduling grant (Pm-dsg) shall be below the specified value in Table 8.4.1.2.4-4. In Tables 8.4.1.2.4-1 and 8.4.1.2.4-3, Cell 1 is the serving cell, and Cell 2 and Cell3are 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] including Cell 2 and Cell 3 is provided. Table 8.4.1.2.4-1: Test Parameters for PDCCH/PCFICH – Non-MBSFN ABS Table 8.4.1.2.4-2: Minimum performance PDCCH/PCFICH – Non-MBSFN ABS Table 8.4.1.2.4-3: Test Parameters for PDCCH/PCFICH – MBSFN ABS Table 8.4.1.2.4-4: Minimum performance PDCCH/PCFICH – 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.4.1.2.4

5.34.7.2 SMF event exposure service

Consumers of SMF events do not need to be aware of the insertion / removal / change of an I-SMF as they always subscribe to the SMF of the PDU Session. Except for the events documented in the present clause, the I-SMF does not need to support the events defined in clause 5.2.8.3.1 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. For Events "First downlink packet per source of the downlink IP traffic (buffered / discarded / transmitted)", when an I-SMF is involved in the PDU Session, the SMF subscribes / unsubscribes onto I-SMF for the PDU Session ID on behalf of the event consumer (e.g. at I-SMF insertion or when a consumer subscribes or un subscribes while an I-SMF serves the PDU Session) and the I-SMF directly notifies the event consumer. At I-SMF change, the related SMF event subscriptions are not transferred from source I-SMF to the target I-SMF. The SMF may trigger new subscription event to the target I-SMF if the SMF wants to receive the corresponding SMF event. At I-SMF change or removal the corresponding subscription is removed in the source I-SMF when it removes the context associated with the PDU Session Id.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.34.7.2

4.9.2.4.2 The UE is roaming and the selected N3IWF is in the home PLMN

Figure 4.9.2.4.2-1: Handover of a PDU Session procedure from 3GPP access to untrusted non-3GPP access with N3IWF in the HPLMN (home routed roaming) 1. If the UE is not registered via untrusted non-3GPP access, the UE shall initiate Registration procedure as defined in clause 4.12.2. This includes the retrieval of the SMF-IDs corresponding to each of the PDU Sessions. 2. The UE performs PDU Session Establishment procedure with the PDU Session ID of the PDU Session to be moved as specified in clause 4.12.5. In the Nsmf_PDUSession_Create Response the H-SMF shall include all QoS information for the QoS Flow(s) applicable to the PDU Session for the target access so that when sending the PDU Session Establishment Accept, within the N1 SM container and in the N2 SM information, the V-SMF can include all QoS information (e.g. QoS Rule(s) in N1 SM container, QFI(s) and QoS Profile(s) in N2 SM information) for the QoS Flow(s) acceptable according to VPLMN policies. 3. The H-SMF executes the release of resources in source V-SMF, V-UPF, V-AMF and 3GPP AN by performing steps 3a, 5c to 16b specified in clause 4.3.4.3 with the following exceptions: - the H-SMF indicates in the Nsmf_PDUSession_Update Request that the UE shall not be notified. This shall result in the V-SMF not sending the N1 Container (PDU Session Release Command) to the UE; - Nsmf_PDUSession_StatusNotify service operation invoked by H-SMF to V-SMF indicates PDU Session is moved to different access; - Nsmf_PDUSession_SMContexStatusNotify service operation invoked by the V-SMF to the AMF indicates the PDU Session is moved to different access; - The Npcf_SMPolicyControl_Delete service operation to PCF shall not be performed. The steps 2 and 3 shall be repeated for all PDU Sessions to be moved from 3GPP access to untrusted non-3GPP access.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.9.2.4.2

6.12.2 Subscription concealed identifier

The SUbscription Concealed Identifier, called SUCI, is a privacy preserving identifier containing the concealed SUPI. The UE shall generate a SUCI using a protection scheme with the raw public key, i.e. the Home Network Public Key, that was securely provisioned in control of the home network. The protection schemes shall be the ones specified in Annex C of this document or the ones specified by the HPLMN. The UE shall construct a scheme-input from the subscription identifier part of the SUPI as follows: For SUPIs containing IMSI, the subscription identifier part of the SUPI includes the MSIN of the IMSI as defined in TS 23.003[ Numbering, addressing and identification ] [19]. For SUPIs taking the form of a NAI, the subscription identifier part of the SUPI includes the "username" portion of the NAI as defined in NAI RFC 7542 [57]. The UE shall execute the protection scheme with the constructed scheme-input as input and take the output as the Scheme Output. The UE shall not conceal the Home Network Identifier and the Routing Indicator. For SUPIs containing IMSI, the UE shall construct the SUCI with the following data fields: - The SUPI Type as defined in TS 23.003[ Numbering, addressing and identification ] [19] identifies the type of the SUPI concealed in the SUCI. - The Home Network Identifier is set to the MCC and MNC of the IMSI as specified in 23.003[ Numbering, addressing and identification ] [19]. - The Routing Indicator as specified in TS 23.003[ Numbering, addressing and identification ] [19]. - The Protection Scheme Identifier as specified in Annex C of this specification. - The Home Network Public Key Identifier as specified in this document and detailed in TS 23.003[ Numbering, addressing and identification ] [19]. - The Scheme Output as specified in this document and detailed in TS 23.003[ Numbering, addressing and identification ] [19]. For SUPIs containing Network Specific Identifier, the UE shall construct the SUCI in NAI format with the following data fields: - realm part of the SUCI is set to the realm part of the SUPI. - username part of the SUCI is formatted as specified in TS 23.003[ Numbering, addressing and identification ] [19] using the SUPI Type, Routing Indicator, the Protection Scheme Identifier, the Home Network Public Key Identifier and the Scheme Output. NOTE 1: The format of the SUPI protection scheme identifiers is defined in Annex C. NOTE 2: The identifier and the format of the Scheme Output are defined by the protection schemes in Annex C. In case of non-null-schemes, the freshness and randomness of the SUCI will be taken care of by the corresponding SUPI protection schemes. NOTE 2a: In case of null-scheme being used, the Home Network Public Key Identifier is set to a default value as described in TS 23.003[ Numbering, addressing and identification ] [19]. The UE shall include a SUCI only in the following 5G NAS messages: - if the UE is sending a Registration Request message of type "initial registration" to a PLMN for which the UE does not already have a 5G-GUTI, the UE shall include a SUCI to the Registration Request message, or - if the UE responds to an Identity Request message by which the network requests the UE to provide its permanent identifier, the UE includes a SUCI in the Identity Response message as specified in clause 6.12.4. - if the UE is sending a De-Registration Request message to a PLMN during an initial registration procedure for which the UE did not receive the registration accept message with 5G-GUTI, the UE shall include the SUCI used in the initial registration to the De-Registration Request message. NOTE 3: In response to the Identity Request message, the UE never sends the SUPI. The UE shall generate a SUCI using "null-scheme" only in the following cases: - if the UE is making an unauthenticated emergency session and it does not have a 5G-GUTI to the chosen PLMN, or - if the home network has configured "null-scheme" to be used, or - if the home network has not provisioned the public key needed to generate a SUCI. If the operator's decision, indicated by the USIM, is that the USIM shall calculate the SUCI, then the USIM shall not give the ME any parameter for the calculation of the SUCI including the Home Network Public Key Identifier, the Home Network Public Key, and the Protection Scheme Identifier. If the ME determines that the calculation of the SUCI, indicated by the USIM, shall be performed by the USIM, the ME shall delete any previously received or locally cached parameters for the calculation of the SUCI including the SUPI Type, the Routing Indicator, the Home Network Public Key Identifier, the Home Network Public Key and the Protection Scheme Identifier. The operator should use proprietary identifier for protection schemes if the operator chooses that the calculation of the SUCI shall be done in USIM. If the operator's decision is that ME shall calculate the SUCI, the home network operator shall provision in the USIM an ordered priority list of the protection scheme identifiers that the operator allows. The priority list of protection scheme identifiers in the USIM shall only contain protection scheme identifiers specified in Annex C, and the list may contain one or more protection schemes identifiers. The ME shall read the SUCI calculation information from the USIM, including the SUPI, the SUPI Type, the Routing Indicator, the Home Network Public Key Identifier, the Home Network Public Key and the list of protection scheme identifiers. The ME shall select the protection scheme from its supported schemes that has the highest priority in the list are obtained from the USIM. The ME shall calculate the SUCI using the null-scheme if the Home Network Public Key or the priority list are not provisioned in the USIM. NOTE 4: The above feature is introduced since additional protection schemes could be specified in the future for a release newer than the ME release. In this case, the protection scheme selected by older MEs may not be the protection scheme with the highest priority in the list of the USIM.

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

6.12.2

4.1.4.1 Mean RRC connection setup time

This measurement provides the mean time per establishment cause it takes to establish an RRC connection. DER (n=1). This measurement is obtained by accumulating the time intervals for every successful RRC connection establishment between the receipt of a RRCConnectionRequest and the corresponding RRCConnectionSetupComplete message by the eNodeB/RN over the granularity period. The end value of this time will then be divided by the number of successful RRC connections observed in the granularity period to give the arithmetic mean. The accumulator shall be reinitialised at the beginning of each granularity period. The measurement is split into subcounters per establishment cause, and the possible causes are included in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]. Each measurement is an integer value (in milliseconds). The measurement name has the form RRC.ConnEstabTimeMean.Cause where Cause identifies the establishment cause EUtranCellFDD EUtranCellTDD Valid for packet switching. 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.4.1