Datasets:

Exploration-Lab

/

MM-TelecoBench

like 1

Follow

Exploration Lab 62

W.4.1.2 Control-plane procedure

The multicast session security context consists of the MBS session ID, MBS keys and the corresponding key ID. The MBS keys include MBS Service Key (MSK) and MBS Traffic Key (MTK). MBS traffic is protected with the MTK. The MSK is used to protect the MTK when the MTK is delivered to the UE. The identification for every MSK and MTK are determined as specified in Clause 6.3.2.1 and clause 6.3.3.1 of TS 33.246[ 3G Security; Security of Multimedia Broadcast/Multicast Service (MBMS) ] [102]. The MBSF determines whether security protection to be applied or not for the MBS session based on locally configured policy or based on the information provided by the AF. If security protection to be applied, then the MBSF shall create the multicast session security context by generating the MSK and its key ID for a MBS session. Afterwards, the MBSF distributes the MSK with MBS session ID and its key ID to the MB-SMF and MBSTF. The MBSF shall also distribute them to MB-SMF either upon request by the MB-SMF (i.e., pull) or when a new MSK is generated (i.e., push). The MBSF may also include the MSK lifetime when it distributes the MSK to MBSTF. Upon receiving the MSK from the MBSF, the MBSTF generates the MTK and its key ID for the MBS traffic protection. A new MTK may be generated based on the MBS session security policy. When the MBSTF generates a new MTK, the MBSTF shall multicast the MTK and its key ID after protecting it using the MSK as specified in TS 33.246[ 3G Security; Security of Multimedia Broadcast/Multicast Service (MBMS) ] [102]. The MBSTF shall also provide the new MTK and its key ID to the MBSF. During the MBS session creation for multicast communication as specified in clause 7.1.1 of TS 23.247[ Architectural enhancements for 5G multicast-broadcast services ] [103], after receiving the description for an MBS session from the AF of content provider, the MBSF shall create the multicast session security context by generating an MSK and acquiring an MTK from the MBSTF. Afterwards, the MBSF distributes the muticast session security context to the MB-SMF via the Nmbsmf_MBSSession_Create Request message. In the multicast session join and session establishment procedure, the SMF interacts with the MB-SMF to obtain the multicast session security context with Nmbsmf_MBSSession_ContextStatusSubscribe service. Absence of the multicast security context indicates that security protection is not applied for the MBS session. The SMF shall provide the multicast session security context in the N1 SM container (PDU Session Modification Command) to the UE if received from the MB-SMF and the UE is authorized to use the required multicast service. The UE shall use the MTK in the received multicast session security context, to process the protected MBS traffic until it receives a new MTK update over the user-plane. The MSK update may be triggered by MB-SMF based on the request from AS or based on the local policy (e.g., key lifetime expiration). When the MSK is updated, the MBSF shall send the new MSK with MBS session ID and its key ID to the MB-SMF and then the MB-SMF shall trigger the session update as specified in clause 7.2.6 in TS 23.247[ Architectural enhancements for 5G multicast-broadcast services ] [103]. The MSK with MBS session ID and the corresponding key ID are delivered to the UEs that has joined the multicast session. The MBSF shall also send the new MSK with MBS session ID and its key ID to the MBSTF. The MBSTF may request a MSK to the MBSF when it does not have a valid MSK (e.g., due to the current MSK expiration). NOTE 1: For an inactive MBS session, MBSTF defers MSK distribution until the MBS session is re-activated. The MTK may be updated based on the change of the authorization information or based on the local policy (e.g. key lifetime expiration). In such cases, the MBSF or MB-SMF may trigger the MTK update to the MBSTF. The key update request message shall include the MBS session ID. If the MBSTF has generated a new MTK, the MBSTF shall provide the new MTK to the MBSF. To improve the efficiency of MTK update, the updated MTK is delivered from MBSTF to the UE using MIKEY over UDP as specified in clause 6.3.3.2 in TS 33.246[ 3G Security; Security of Multimedia Broadcast/Multicast Service (MBMS) ] [102]. The MSK is used to protect the updated MTK. The UE shall not send an error message to the MBSTF as a result of receiving an MTK message. NOTE 2: For an inactive MBS session, MBSTF defers the MTK distribution until the session in re-activated.

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

W.4.1.2

6.6.2.1A Spectrum emission mask for CA

For inter-band carrier aggregation with one component carrier per operating band and the uplink active in two E-UTRA bands, the spectrum emission mask of the UE is defined per component carrier while both component carriers are active and the requirements are specified in subclauses 6.6.2.1 and 6.6.2.2. If for some frequency spectrum emission masks of component carriers overlap then spectrum emission mask allowing higher power spectral density applies for that frequency. If for some frequency a component carrier spectrum emission mask overlaps with the channel bandwidth of another component carrier, then the emission mask does not apply for that frequency. For intra-band contiguous carrier aggregation the spectrum emission mask of the UE applies to frequencies (ΔfOOB) starting from the edge of the aggregated channel bandwidth (Table 5.6A-1) For intra-band contiguous carrier aggregation the bandwidth class B, C and D, the power of any UE emission shall not exceed the levels specified in Table 6.6.2.1A-0, Table 6.6.2.1A-1 and Table 6.6.2.1A-2 for the specified channel bandwidth. Table 6.6.2.1A-0: General E-UTRA CA spectrum emission mask for Bandwidth Class B Table 6.6.2.1A-1: General E-UTRA CA spectrum emission mask for Bandwidth Class C Table 6.6.2.1A-2: General E-UTRA CA spectrum emission mask for Bandwidth Class D For intra-band non-contiguous carrier aggregation transmission the spectrum emission mask requirement is defined as a composite spectrum emissions mask. Composite spectrum emission mask applies to frequencies up to ΔfOOB starting from the edges of the sub-blocks. Composite spectrum emission mask is defined as follows a) Composite spectrum emission mask is a combination of individual sub-block spectrum emissions masks b) In case the sub-block consist of one component carrier the sub-lock general spectrum emission mask is defined in subclause 6.6.2.1.1 c) If for some frequency sub-block spectrum emission masks overlap then spectrum emission mask allowing higher power spectral density applies for that frequency d) If for some frequency a sub-block spectrum emission mask overlaps with the sub-block bandwidth of another sub-block, then the emission mask does not apply for that frequency. For combinations of intra-band and inter-band carrier aggregation with three uplink component carriers (up to two contiguously aggregated carriers per band), the spectrum emission mask of the UE is defined per E-UTRA band while all component carriers are active. For the E-UTRA band supporting one component carrier the requirements in subclauses 6.6.2.1 and 6.6.2.2 apply. For the E-UTRA band supporting two contiguous component carriers the requirements specified in subclause 6.6.2.1A apply. If for some frequency spectrum emission masks of single component carrier and two contiguous component carriers overlap then spectrum emission mask allowing higher power spectral density applies for that frequency. If for some frequency spectrum emission masks of single component carrier or two contiguous component carriers overlap then the emission mask does not apply for that frequency.

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

12.3.11 Discovery of the support of the feature by the peer node

A GTP-C entity shall determine whether to use the overload control feature: - within the PLMN, based on operator's policy (local PLMN-wide configuration); - across the PLMN boundaries, based on operator's policy (local configuration per PLMN). NOTE: The feature can be activated when all or some of the nodes in the PLMN support the feature. The GTP-C entity assumes that all the peer nodes support this feature when the feature is activated, i.e. it does not need to determine which peers support the feature. The above operator policy/local configuration may allow the use of overload control at node level and APN level, or none.

3GPP TS 29.274

3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3

CT WG4

3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network

12.3.11

9.2.4 Minimum requirement PUCCH 1-1 (With Single CSI Process)

The minimum requirements for dual codeword transmission are defined in terms of a reporting spread of the wideband CQI value for codeword #1, and their BLER performance using the transport format indicated by the reported CQI median of codeword #0 and codeword #1. The precoding used at the transmitter is a fixed precoding matrix specified by the bitmap parameter codebookSubsetRestriction. The propagation condition assumed for the minimum performance requirement is defined in subclause B.1. If UE supporting interferenceMeasRestriction, test cases specified in 9.2.4.1A and 9.2.4.2A are applicable for such UE otherwise test cases specified in 9.2.4.1 and 9.2.4.2 are applied.

3GPP TS 36.101

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

RAN4

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

9.2.4

6.15a.2.1 Description

Energy consumption can be monitored and considered through O&M as part of network operations [47], as well as a service criteria. For best-effort traffic, that is, without QoS criteria, policies can be defined to limit energy use for services. This is not in conflict with the principle that performance policies will not be traded off for energy efficiency, since best-effort service has no performance guarantees. Specifically, best-effort traffic can be subject to a policy that limits the maximum energy consumption over time, or further constrained by location (so that the energy consumption limit only applies when used in a specified service area.) Additionally, policies can be defined with a maximum energy credit limit, e.g. for best-effort services to limit the total amount of energy consumption according to an energy charging rate. These policies expand the options of subscription policies to control energy consumption in the 5G system.

3GPP TS 22.261

Service requirements for the 5G system

SA WG1

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

6.15a.2.1

5.1.3.2.1.4.8 5GMM-REGISTERED.UPDATE-NEEDED

This state can be entered if the UE has to perform a registration procedure for mobility and periodic registration update but: a) the access is barred due to unified access control when in 3GPP access; b) the network rejects the N1 NAS signalling connection establishment when in 3GPP access or in non-3GPP access; or c) the UE in 5GMM-CONNECTED mode with RRC inactive indication receives an indication from the lower layers that the resumption of the RRC connection has failed and for access is barred for all categories except categories '0' and '2' as specified in subclause 5.3.1.4. No 5GMM procedure except: a) registration procedure for mobility and periodic registration update; b) service request procedure as a response to paging or notification; and c) de-registration procedure shall be initiated by the UE in this substate. NOTE: This substate is entered irrespective whether: - the UE is camped on a cell which is in the registered PLMN, a PLMN from the list of equivalent PLMNs, or the registered SNPN, and the current TAI is not in the list of "allowed tracking areas"; or - the current TAI is in the list of "non-allowed tracking areas".

3GPP TS 24.501

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

CT WG1

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

5.1.3.2.1.4.8

6.11.3.2 Mapping to resource elements

If only one CRS port is configured in a cell, the UE may assume that the same antenna port is used for all subframes in an RSS transmission in the cell. Otherwise, the UE may assume that the same antenna port is used for RSS transmission in absolute subframes and and . An RSS is transmitted in consecutive BL/CE DL subframes, starting in the first BL/CE DL subframe in a radio frame satisfying where the RSS periodicity and the RSS time offset are configured by higher layers. In frequency domain, the RSS frequency location is assigned to the 24 subcarriers in the physical resource blocks numbers and , as configured by higher layers. In each subframe used for RSS transmission, the RSS sequence shall be mapped to resource elements in sequence, starting with in increasing order of first the index , over the 24 assigned subcarriers and then the index . A resource element overlapping with resource elements where cell-specific reference signals according to clause 6.10 are transmitted shall not be used for RSS transmission but is counted in the mapping process. Additionally, an RSS subframe is dropped if any RSS PRB pair overlaps with any PRB pair carrying PSS, SSS, PBCH or PDSCH associated with SI-RNTI. In frame structure type 2, those special subframes, indicated as BL/CE DL subframes by higher layer fdd-DownlinkOrTddSubframeBitmapBR, are not counted in RSS mapping and are not used for transmission of RSS.

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

4.3.29 3GPP PS Data Off 4.3.29.1 General

This feature, when activated by the user, prevents transport via 3GPP access of all IP packets, Ethernet data and non-IP data except for those related to 3GPP PS Data Off Exempt Services. The 3GPP PS Data Off Exempt Services are a set of operator services, defined in TS 23.221[ Architectural requirements ] [27], that are the only allowed services when the 3GPP PS Data Off feature has been activated by the user. UEs may be configured with up to two lists of 3GPP PS Data Off Exempt Services and the list(s) are provided to the UEs by HPLMN via Device Management or UICC provisioning. When the UE is configured with two lists, one list is valid for the UEs camping in the home PLMN and the other list is valid for any VPLMN the UE is roaming in. When the UE is configured with a single list, without an indication to which PLMNs the list is applicable, then this list is valid for the home PLMN and any PLMN the UE is roaming in. NOTE 1: The operator needs to ensure coordinated lists of 3GPP Data Off Exempt Services provisioned in the UE and configured in the network. The UE discovers whether a PDN GW supports 3GPP PS Data Off feature at initial attach and during the establishment of a PDN connection via the presence of the 3GPP PS Data Off Support Indication in the Create Session response message. NOTE 2: When the UE detects that the PDN GW does not support 3GPP PS Data Off feature, how the UE reacts to non-exempt services MT requests from the network is implementation dependent. The UE shall report its 3GPP PS Data Off status in PCO (Protocol Configuration Option) to PDN GW during Initial Attach procedure as described in clause 5.3.2.1 and UE requested PDN connectivity procedure as described in clause 5.10.2. NOTE 3: This also covers scenarios when the user activates/deactivates 3GPP PS Data Off while connected via WLAN access only, and then a handover to 3GPP access occurs. If 3GPP PS Data Off is activated, the UE prevents the sending of uplink IP packets, Ethernet data and non-IP data except for those related to 3GPP PS Data Off Exempt Services, based on the pre-configured list of Data Off Exempt Services. For those PDN GWs that indicated support for the 3GPP PS Data Off feature during PDN connection setup and at Initial Attach, the UE shall report immediately a change of its 3GPP PS Data Off status in PCO by using Bearer Resource Modification procedure as described in clause 5.4.5, this also applies to the scenario of inter-RAT mobility procedure to E-UTRAN and also to scenarios where the 3GPP PS Data Off status is changed when the session management back-off timer is running as specified in clause 4.3.7.4.2. If the UE has not received any 3GPP PS Data Off Support Indication during the establishment of the PDN connection, it shall not report any change of its 3GPP PS Data Off Status for this PDN connection. The additional behaviour of the PDN GW for 3GPP PS Data Off is controlled by local configuration or policy from the PCRF as defined in TS 23.203[ Policy and charging control architecture ] [6]. NOTE 4: For the PDN connection used for IMS services, the 3GPP Data Off Exempt Services are enforced in the IMS domain as specified TS 23.228[ IP Multimedia Subsystem (IMS); Stage 2 ] [52]. Policies configured in the PDN GW/PCRF need to ensure those services are always allowed when the 3GPP Data Off status of the UE is set to "activated".

3GPP TS 23.401

General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access

SA WG2

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

4.3.29

5.15.4.2 Update of UE Network Slice configuration

At any time, the AMF may provide the UE with a new Configured NSSAI for the Serving PLMN, associated with mapping of the Configured NSSAI to HPLMN S-NSSAIs as specified in clause 5.15.4.1. The Configured NSSAI for the Serving PLMN and the mapping information is either determined in the AMF (if based on configuration, the AMF is allowed to determine the Network Slice configuration for the whole PLMN) or by the NSSF. The AMF provides an updated Configured NSSAI as specified in clause 4.2.4 of TS 23.502[ Procedures for the 5G System (5GS) ] [3], UE Configuration Update procedure. If an S-NSSAI is to be stopped to be used, e.g. due to the network slice is to be deleted as described in TS 28.541[ Management and orchestration; 5G Network Resource Model (NRM); Stage 2 and stage 3 ] [149], the AMFs may reject UE requests for the S-NSSAI based on the OAM state before the network slice becomes unavailable. The AMF may based on operator policies (e.g. when there is no timing information related to the termination or the AMF or UE does not support the timing information as described in in clause 5.15.16), release PDU Sessions associated with the S-NSSAI, and remove the S-NSSAI from e.g. the Allowed NSSAI and the Configured NSSAI before the Network Slice becomes unavailable. The AMF may use the timing information as described in clause 5.15.16 if it supports this feature and set validity time of the S-NSSAI accordingly. The AMF shall provide the UE with NSSRG information alongside the Configured NSSAI if NSSRG information is included in the subscription information received from the UDM and if the UE has indicated support for the feature as part of the registration request, see clause 5.15.12. The AMF may provide the UE with the mapping of old S-NSSAI to the Alternative S-NSSAI if the UE has indicated support for the feature as part of the registration request, see clause 5.15.19. If the HPLMN performs the configuration update of a UE registered in the HPLMN (e.g. due to a change in the Subscribed S-NSSAI(s) or due to a change of NSSRG information), this results in updates to the Configured NSSAI for the HPLMN and, if applicable, NSSRG information for each S-NSSAI of the Configured NSSAI. Updates to the Allowed NSSAI and/or, if present, to the associated mapping of the Allowed NSSAI to HPLMN S-NSSAIs are also possible if the configuration update affects S-NSSAI(s) in the current Allowed NSSAI. If the VPLMN performs the configuration update of a UE registered in the VPLMN (e.g. due to a change in the Subscribed S-NSSAI(s), the associated mapping is updated, or due to a change of NSSRG information), this results in updates to the Configured NSSAI for the Serving PLMN and/or to the associated mapping of the Configured NSSAI for the Serving PLMN to HPLMN S-NSSAIs and, if applicable, NSSRG information for each S-NSSAI of the Configured NSSAI. Updates to the Allowed NSSAI and/or to the associated mapping of the Allowed NSSAI to HPLMN S-NSSAIs are also possible if the configuration update affects S-NSSAI(s) in the current Allowed NSSAI. A UE for which the Configured NSSAI for the Serving PLMN has been updated as described in clause 5.15.4.1 and has been requested to perform a Registration procedure, shall initiate a Registration procedure to receive a new valid Allowed NSSAI (see clause 5.15.5.2.2). When the subscribed S-NSSAIs change, a UDR flag is set in the HPLMN to make sure the current PLMN (or, if the UE was not reachable, the next serving PLMN) is informed by the UDM that the subscription data for network slicing has changed. The AMF, when it receives the indication from the UDM subscription has changed, indicates the UE that subscription has changed and uses any updated subscription information from the UDM to update the UE. Once the AMF updates the UE and obtains an acknowledgment from the UE, the AMF informs the UDM that the configuration update was successful and the UDM clears the flag in the UDR. If the UE is in a CM-IDLE state, the AMF may trigger Network Triggered Service Request or wait until the UE is in a CM-CONNECTED state as described in clause 4.2.4.2, TS 23.502[ Procedures for the 5G System (5GS) ] [3]. If the UE receives indication from the AMF that Network Slicing subscription has changed, the UE locally deletes the network slicing information it has for all PLMNs, except the Default Configured NSSAI (if present). It also updates the current PLMN network slicing configuration information with any received values from the AMF. The update of URSP rules (which include the NSSP), if necessary at any time, is described in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45].

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.15.4.2

4.22.3.2 Non-roaming or roaming with local breakout

In the case of non-roaming or roaming with local breakout, the procedure for establishing a MA PDU Session when the UE requests a single-access PDU Session is the same with the procedure specified in clause 4.22.2.1.1, with the following clarifications and modifications: - In step 1, the UE sets Request Type to initial request and it may include the "MA PDU Network-Upgrade Allowed" indication in UL NAS Transport message and its ATSSS Capabilities in PDU Session Establishment Request message, if the 5GC is ATSSS capable and no policy in the UE (e.g. no URSP rule) and no local restrictions mandate a single access for the requested PDU Session. The "MA PDU Network-Upgrade Allowed" indication indicates that the requested single-access PDU Session may be converted to a MA PDU Session, if the 5GC network wants to. - In step 2, if the AMF receives the "MA PDU Network-Upgrade Allowed" indication, the AMF may select a SMF that supports MA PDU sessions. The AMF does not send the "MA PDU Request" indication to SMF, but it sends the "MA PDU Network-Upgrade Allowed" indication, if received from the UE. If the AMF determines that the requested S-NSSAI is not allowed on both accesses, the AMF shall not forward "MA PDU Network-Upgrade Allowed" indication to the SMF. If the AMF sends the "MA PDU Network-Upgrade Allowed" indication to SMF, it shall also indicate to SMF whether the UE is registered over both accesses. If the PDU Session Establishment request is for a LADN, the AMF shall not forward "MA PDU Network-Upgrade Allowed" indication to the SMF. - After step 6, if SMF receives the "MA PDU Network-Upgrade Allowed" indication, the SMF may decide, if dynamic PCC is not to be used, to convert the single-access PDU Session requested by the UE into a MA PDU Session. The SMF may take this decision based on local operator policy, subscription data indicating whether the MA PDU session is allowed or not and/or other conditions, which are not specified in the present document. If the SMF receives ATSSS Capabilities from the UE but does not receive "MA PDU Network-Upgrade Allowed" indication from the AMF, the SMF shall not convert the single-access PDU Session requested by the UE into a MA PDU Session. If the SMF receives a UP Security Policy for the PDU Session with Integrity Protection set to "Required" and the MA PDU session is being established over non-3GPP access, the SMF does not verify whether the access can satisfy the UP Security Policy. - In step 7, if dynamic PCC is to be used for the PDU Session, the SMF indicates to PCF that the SM policy control information is requested for a MA PDU Session via "MA PDU Network-Upgrade Allowed" indication if the MA PDU session is allowed based on the subscription data. The SMF provides the currently used Access Type(s) and RAT Type(s) for the MA-PDU session to the H-PCF. The SMF also provides the ATSSS Capabilities of the MA PDU session. - In step 10, the N4 rules derived by SMF for the MA-PDU session are sent to UPF and two N3 UL CN tunnels info are allocated by the UPF. - In step 11, for the MA PDU Session, the SMF sends an "MA PDU session Accepted" indication in the Namf_Communication_N1N2MessageTransfer message to the AMF. The AMF marks this PDU session as MA PDU session based on the received "MA PDU session Accepted" indication. - The PDU Session Establishment Accept message includes ATSSS rules which indicate to UE that the requested PDU Session was converted by the network to a MA PDU Session. - The SMF triggers the establishment of user-plane resources in both accesses, if it was informed in step 2 that the UE is registered over both accesses.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.22.3.2

6.3.13.2 Authentication and authorization of UAV

The UE supporting UAS services may request a PDN connection for USS communication during attach and UE-requested PDN connectivity procedures (see clause 5.5.1 and 6.5.1). In the request of the PDN connection for USS communication, the UE provides CAA-level UAV ID to the network via the protocol configuration options and the network may decide to perform UUAA-SM procedure. If provided by the upper layers, a UE supporting UAS services may provide to the network the USS address via the protocol configuration options during attach and UE-requested PDN connectivity procedures so that the network may use the information to discover the USS. After successful UUAA-SM procedure, the network may initiate the re-authentication or re-authorization procedure for the UE supporting UAS services as a part of network-initiated EPS bearer context modification procedure. If UUAA-SM fails during the re-authentication or a re-authorization procedure, or if the revocation of UUAA is initiated by the network, then the associated PDN connection for USS communication is released.

3GPP TS 24.301

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

CT WG1

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

6.3.13.2

4.23.9.5 Simultaneous change of Branching Points or UL CLs controlled by different I-SMFs

This clause describes simultaneous change of UL-CL/BP function and additional PSA, e.g. addition of a new UL CL/BP and PDU Session Anchor (i.e. PSA2) and release of the existing UL CL/BP and PDU Session Anchor (i.e. PSA0), with target UPF(s) and source UPF(s) are all controlled by different I-SMF(s). This procedure may be triggered after N2 handover or Xn based handover procedure. Figure 4.23.9.5-1: Simultaneous change of Branching Point or UL CL and additional PSA controlled by different I-SMFs 1. UE has established PDU Session with Source Branching Point or UL CL and Source UPF (PSA0) controlled by source I-SMF and Remote PSA. The UE has mobility with I-SMF change, e.g. handed over from a source RAN to a target RAN. After mobility, the path between Target I-UPF and Remote PSA (PSA1) has been established. 2. This step is the same as steps 2 in clause 4.23.9.3. 3. Same as in step 3 of Figure 4.23.9.4-1. 4. Same as in step 4 of Figure 4.23.9.4-1. 5. Same as in step 5 of Figure 4.23.9.4-1.. 6-8. These steps are the same as steps 4-6 in clause 4.23.9.3 with the following enhancement: In step 7, to support EAS session continuity upon UL CL relocation the SMF provides the target I-SMF with an indication that a N9 forwarding tunnel to support the EAS session continuity is required, UL traffic filter for N9 forwarding by the target UL CL and the value of the timer to detect the end of activity on the N9 forwarding tunnel to support the EAS session continuity. Based on the received information, the target I-SMF installs corresponding N4 rules in the target UL CL for forwarding of uplink traffics via the N9 forwarding tunnel. The time interval for User Plane inactivity report is also provisioned to UL CL per the timer value received from SMF. 9. Same as in step 9 of Figure 4.23.9.4-1. 10. This step is the same as step 9 in clause 4.23.9.3. The SMF triggers the procedure from step 11 onwards to support EAS session continuity upon UL CL relocation. 11. If N9 forwarding tunnel to support the EAS session continuity is required based on indication received from SMF in step 7, the target I-SMF request target UL CL to allocate N9 forwarding tunnel info via N4 session modification procedure. 12. The target I-SMF invokes Nsmf_PDUSession_UpdateSMContext Request (N9 forwarding tunnel required, target UL CL N9 forwarding tunnel info, value of the timer to detect the end of activity on the N9 forwarding tunnel to support the EAS session continuity) toward the source I-SMF. 13. The source I-SMF triggers N4 modification procedure to request the source UL CL to establish the N9 forwarding tunnel to support the EAS session continuity. The source I-SMF provides the target UL CL N9 forwarding tunnel info to the source UL CL and receives the source UL CL N9 forwarding tunnel info from the source UL CL. The source I-SMF configures the source UL CL to forward traffic received from source L-PSA related to that PDU session toward the target UL CL via the N9 forwarding tunnel. The source I-SMF configures a time interval for the source ULCL for the detection of no active traffic over the N9 forwarding tunnel, which is based on the value of the timer to detect the end of activity on the N9 forwarding tunnel to support the EAS session continuity as received from target I-SMF. After this step, the downlink data can be forwarded via N9 forwarding tunnel from the source L-PSA (PSA0). 14. The source I-SMF sends Nsmf_PDUSession_UpdateSMContext Response (source UL CL N9 forwarding to support the EAS session continuity tunnel info). 15. Based on the traffic filter information received from SMF at step 7 and source UL CL N9 forwarding tunnel to support the EAS session continuity info, the target I-SMF request the target UL CL to forward related UL traffic via N9 forwarding tunnel to support the EAS session continuity. The target I-SMF configures a time interval for the target ULCL for the detection of no active traffic over the N9 forwarding tunnel, which is based on the value of the timer to detect the end of activity on the N9 forwarding tunnel to support the EAS session continuity received from SMF. After this step, the uplink data can be forwarded via N9 forwarding tunnel toward the source L-PSA (PSA0). 16-17. Upon detection of no active traffic over the N9 forwarding tunnel to support the EAS session continuity, the source I-SMF releases via N4 the source UL-CL/BP The Source I-SMF also releases via N4 the PSA0 if PSA0 is not collocated with source UL CL/BP. 17a. The source I-SMF invokes Nsmf_PDUSession_Update Request to inform the SMF of the release of the resource in the UL CL/BP and the PSA0 for this PDU Session. 18. Upon detection of no active traffic over the N9 forwarding tunnel to support the EAS session continuity, the Target I-SMF releases the N9 forwarding tunnel in Target UL CL and remove the related filter.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.23.9.5

4.22.6.2.2 5GS to EPS idle mode mobility using N26 interface

Based on the signalling flow in Figure 4.11.1.3.2-1, the procedure is performed with the following differences and modifications: - Step 5a is also performed with all the SMF+PGW-Cs corresponding to the MA PDU Sessions with allocated EBI(s). - In step 12, if the MA PDU Session is established in both 3GPP and non-3GPP accesses and the MA PDU Session is moved to EPS and if the UE or the network does not support MA PDU Session with 3GPP access connected to EPC, the SMF triggers the MA PDU Session Release procedure over non-3GPP access. If UE and the network support MA PDU Session with 3GPP access connected to EPC, the SMF should keep the user-plane resources over non-3GPP access in 5GC and use the PDN Connection as the 3GPP access leg of the MA PDU Session. If the MA PDU Session is established using one 3GPP access path via 5GC and one non-3GPP access path via ePDG/EPC and the MA PDU Session is moved to EPS and if the UE and network supports MA PDU Session with non-3GPP access connected to EPC, the SMF may keep the MA PDU Session. - In step 15a, the AMF also requests the release of the MA PDU Session which has resources established for 3GPP access, but not expected to be transferred to EPS, i.e. no EBI(s) allocated to the MA PDU Session by triggering Nsmf_PDUSession_UpdateSMContext service operation. NOTE: When the SMF received the release request from the AMF, the SMF decides whether the MA PDU Session is completely released or released over a single access based on its local policy.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.22.6.2.2

5.43.2 Edge Computing via UPF deployed on satellite

This clause only applies to the case where Edge Computing is deployed with UPF and Edge Computing services on-board the satellite. The UPF deployed on satellite can act as UL CL/BP/local PSA UPF or act as PSA UPF. NOTE 1: In this Release, Edge Computing via UPF deployed on satellite only applies to GEO satellite backhaul. To select the UPF deployed on satellite as PSA, the following enhancements apply: - If the UE is accessing gNB with satellite backhaul, and AMF is aware of the satellite backhaul category, the AMF sends the satellite backhaul category to the PCF. If GEO satellite backhaul category is indicated, the PCF may take it into account to generate or update the URSP rule as defined in clause 6.1.2.2 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45] to including an appropriate Route Selection Descriptor for services deployed on GEO satellite, which further enable PDU Session Establishment with PSA UPF on the satellite. Based on GEO satellite ID provided by the AMF, the SMF performs PSA UPF selection or UL CL/BP/local PSA selection and insertion during the PDU Session Establishment procedure as described in clause 4.3.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] or PDU Session Modification procedure as described in clause 4.3.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] to select the UPF deployed on the GEO satellite if available, which includes: - Based on configuration, the AMF may determine the GEO Satellite ID serving the UE and send it to the SMF. If GEO satellite ID changes, e.g. due to UE handover to an gNB using different GEO satellite as part of backhaul, the AMF may update the latest GEO Satellite ID to the SMF. NOTE 2: It is assumed that AMF determines the GEO Satellite ID based on local configuration, e.g. based on Global RAN Node IDs associated with satellite backhaul. - The SMF determines DNAI based on local configuration, DNN or S-NSSAI or both and the GEO Satellite ID received from AMF. NOTE 3: It is assumed that one or more DNAI values are assigned for each GEO Satellite ID by the operator. SMF is locally configured with mapping relationship between DNAI and GEO Satellite ID. - If the UE is allowed to access the service(s) according to the EAS Deployment Information as described in clause 6.2.3.4 of TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [130], the SMF selects the PSA UPF or UL CL/BP/local PSA based on the DNAI corresponding to the GEO Satellite ID and other factors as described in clause 6.2.3.2 of TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [130]. NOTE 4: EASDF may be deployed on satellite based on local configuration.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.43.2

19.3.4 Fast Re-authentication NAI

The Fast Re-authentication NAI shall take the form of a NAI as specified in clause 2.1 of IETF RFC 4282 [53]. If the 3GPP AAA server does not return a complete NAI, the Fast Re-authentication NAI shall consist of the username part of the fast re-authentication identity as returned from the 3GPP AAA server and the same realm as used in the permanent user identity. If the 3GPP AAA server returns a complete NAI as the re-authentication identity, then this NAI shall be used. The username part of the fast re-authentication identity shall be decorated as described in 19.3.3 if the Selected PLMN is different from the HPLMN. For EAP-AKA authentication, the username portion of the fast re-authentication identity shall be prepended with the single digit "4" as specified in clause 4.1.1.7 of IETF RFC 4187 [50]. For EAP AKA', see IETF RFC 5448 [82], the Fast Re-authentication NAI shall comply with IETF RFC 4187 [50] except that the username part of the NAI shall be prepended with single digit "8". NOTE: The permanent user identity is either the Root NAI or Decorated NAI as defined in clauses 19.3.2 and 19.3.3, respectively. EXAMPLE 1: If the fast re-authentication identity returned by the 3GPP AAA Server is 358405627015, the IMSI is 234150999999999 (MCC = 234, MNC = 15) and EAP-AKA is used, the Fast Re-authentication NAI for the case when NAI decoration is not used takes the form: 4358405627015@nai.epc.mnc015.mcc234.3gppnetwork.org EXAMPLE 2: If the fast re-authentication identity returned by the 3GPP AAA Server is "358405627015@aaa1.nai.epc.mnc015.mcc234.3gppnetwork.org" , the IMSI is 234150999999999 (MCC = 234, MNC = 15) and EAP-AKA' is used, the Fast Re-authentication NAI for the case when NAI decoration is not used takes the form: 8358405627015@aaa1.nai.epc.mnc015.mcc234.3gppnetwork.org EXAMPLE 3: If the fast re-authentication identity returned by the 3GPP AAA Server is 358405627015, the IMSI is 234150999999999 (MCC = 234, MNC = 15), the PLMN ID of the Selected PLMN is MCC = 610, MNC = 71 and EAP-AKA is used, the Fast Re-authentication NAI takes the form: nai.epc.mnc015.mcc234.3gppnetwork.org !4358405627015@nai.epc.mnc071.mcc610.3gppnetwork.org.

3GPP TS 23.003

Numbering, addressing and identification

CT WG4

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

19.3.4

– SIB1

SIB1 contains information relevant when evaluating if a UE is allowed to access a cell and defines the scheduling of other system information. It also contains radio resource configuration information that is common for all UEs and barring information applied to the unified access control. Signalling radio bearer: N/A RLC-SAP: TM Logical channels: BCCH Direction: Network to UE SIB1 message -- ASN1START -- TAG-SIB1-START SIB1 ::= SEQUENCE { cellSelectionInfo SEQUENCE { q-RxLevMin Q-RxLevMin, q-RxLevMinOffset INTEGER (1..8) OPTIONAL, -- Need S q-RxLevMinSUL Q-RxLevMin OPTIONAL, -- Need R q-QualMin Q-QualMin OPTIONAL, -- Need S q-QualMinOffset INTEGER (1..8) OPTIONAL -- Need S } OPTIONAL, -- Cond Standalone cellAccessRelatedInfo CellAccessRelatedInfo, connEstFailureControl ConnEstFailureControl OPTIONAL, -- Need R si-SchedulingInfo SI-SchedulingInfo OPTIONAL, -- Need R servingCellConfigCommon ServingCellConfigCommonSIB OPTIONAL, -- Need R ims-EmergencySupport ENUMERATED {true} OPTIONAL, -- Need R eCallOverIMS-Support ENUMERATED {true} OPTIONAL, -- Need R ue-TimersAndConstants UE-TimersAndConstants OPTIONAL, -- Need R uac-BarringInfo SEQUENCE { uac-BarringForCommon UAC-BarringPerCatList OPTIONAL, -- Need S uac-BarringPerPLMN-List UAC-BarringPerPLMN-List OPTIONAL, -- Need S uac-BarringInfoSetList UAC-BarringInfoSetList, uac-AccessCategory1-SelectionAssistanceInfo CHOICE { plmnCommon UAC-AccessCategory1-SelectionAssistanceInfo, individualPLMNList SEQUENCE (SIZE (2..maxPLMN)) OF UAC-AccessCategory1-SelectionAssistanceInfo } OPTIONAL -- Need S } OPTIONAL, -- Need R useFullResumeID ENUMERATED {true} OPTIONAL, -- Need R lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SIB1-v1610-IEs OPTIONAL } SIB1-v1610-IEs ::= SEQUENCE { idleModeMeasurementsEUTRA-r16 ENUMERATED{true} OPTIONAL, -- Need R idleModeMeasurementsNR-r16 ENUMERATED{true} OPTIONAL, -- Need R posSI-SchedulingInfo-r16 PosSI-SchedulingInfo-r16 OPTIONAL, -- Need R nonCriticalExtension SIB1-v1630-IEs OPTIONAL } SIB1-v1630-IEs ::= SEQUENCE { uac-BarringInfo-v1630 SEQUENCE { uac-AC1-SelectAssistInfo-r16 SEQUENCE (SIZE (2..maxPLMN)) OF UAC-AC1-SelectAssistInfo-r16 } OPTIONAL, -- Need R nonCriticalExtension SIB1-v1700-IEs OPTIONAL } SIB1-v1700-IEs ::= SEQUENCE { hsdn-Cell-r17 ENUMERATED {true} OPTIONAL, -- Need R uac-BarringInfo-v1700 SEQUENCE { uac-BarringInfoSetList-v1700 UAC-BarringInfoSetList-v1700 } OPTIONAL, -- Cond MINT sdt-ConfigCommon-r17 SDT-ConfigCommonSIB-r17 OPTIONAL, -- Need R redCap-ConfigCommon-r17 RedCap-ConfigCommonSIB-r17 OPTIONAL, -- Need R featurePriorities-r17 SEQUENCE { redCapPriority-r17 FeaturePriority-r17 OPTIONAL, -- Need R slicingPriority-r17 FeaturePriority-r17 OPTIONAL, -- Need R msg3-Repetitions-Priority-r17 FeaturePriority-r17 OPTIONAL, -- Need R sdt-Priority-r17 FeaturePriority-r17 OPTIONAL -- Need R } OPTIONAL, -- Need R si-SchedulingInfo-v1700 SI-SchedulingInfo-v1700 OPTIONAL, -- Need R hyperSFN-r17 BIT STRING (SIZE (10)) OPTIONAL, -- Need R eDRX-AllowedIdle-r17 ENUMERATED {true} OPTIONAL, -- Need R eDRX-AllowedInactive-r17 ENUMERATED {true} OPTIONAL, -- Cond EDRX-RC intraFreqReselectionRedCap-r17 ENUMERATED {allowed, notAllowed} OPTIONAL, -- Need S cellBarredNTN-r17 ENUMERATED {barred, notBarred} OPTIONAL, -- Need S nonCriticalExtension SIB1-v1740-IEs OPTIONAL } SIB1-v1740-IEs ::= SEQUENCE { si-SchedulingInfo-v1740 SI-SchedulingInfo-v1740 OPTIONAL, -- Need R nonCriticalExtension SIB1-v1800-IEs OPTIONAL } SIB1-v1800-IEs ::= SEQUENCE { ncr-Support-r18 ENUMERATED {true} OPTIONAL, -- Need S mt-SDT-ConfigCommonSIB-r18 MT-SDT-ConfigCommonSIB-r18 OPTIONAL, -- Need R musim-CapRestrictionAllowed-r18 ENUMERATED {true} OPTIONAL, -- Need R featurePriorities-v1800 SEQUENCE { msg1-Repetitions-Priority-r18 FeaturePriority-r17 OPTIONAL, -- Need R eRedCapPriority-r18 FeaturePriority-r17 OPTIONAL -- Need R } OPTIONAL, -- Need R si-SchedulingInfo-v1800 SI-SchedulingInfo-v1800 OPTIONAL, -- Need R cellBarredATG-r18 ENUMERATED {barred, notBarred} OPTIONAL, -- Need S cellBarredNES-r18 ENUMERATED {notBarred} OPTIONAL, -- Need R mobileIAB-Cell-r18 ENUMERATED {true} OPTIONAL, -- Need R eDRX-AllowedInactive-r18 ENUMERATED {true} OPTIONAL, -- Cond EDRX-RC intraFreqReselection-eRedCap-r18 ENUMERATED {allowed, notAllowed} OPTIONAL, -- Need S nonServingCellMII-r18 ENUMERATED {true} OPTIONAL, -- Need R nonCriticalExtension SEQUENCE {} OPTIONAL } UAC-AccessCategory1-SelectionAssistanceInfo ::= ENUMERATED {a, b, c} UAC-AC1-SelectAssistInfo-r16 ::= ENUMERATED {a, b, c, notConfigured} SDT-ConfigCommonSIB-r17 ::= SEQUENCE { sdt-RSRP-Threshold-r17 RSRP-Range OPTIONAL, -- Need R sdt-LogicalChannelSR-DelayTimer-r17 ENUMERATED { sf20, sf40, sf64, sf128, sf512, sf1024, sf2560, spare1} OPTIONAL, -- Need R sdt-DataVolumeThreshold-r17 ENUMERATED {byte32, byte100, byte200, byte400, byte600, byte800, byte1000, byte2000, byte4000, byte8000, byte9000, byte10000, byte12000, byte24000, byte48000, byte96000}, t319a-r17 ENUMERATED { ms100, ms200, ms300, ms400, ms600, ms1000, ms2000, ms3000, ms4000, spare7, spare6, spare5, spare4, spare3, spare2, spare1} } RedCap-ConfigCommonSIB-r17 ::= SEQUENCE { halfDuplexRedCapAllowed-r17 ENUMERATED {true} OPTIONAL, -- Need R cellBarredRedCap-r17 SEQUENCE { cellBarredRedCap1Rx-r17 ENUMERATED {barred, notBarred}, cellBarredRedCap2Rx-r17 ENUMERATED {barred, notBarred} } OPTIONAL, -- Need R ..., [[ cellBarredRedCap-r18 SEQUENCE { cellBarred-eRedCap1Rx-r18 ENUMERATED {barred, notBarred}, cellBarred-eRedCap2Rx-r18 ENUMERATED {barred, notBarred} } OPTIONAL -- Need R ]] } FeaturePriority-r17 ::= INTEGER (0..7) MT-SDT-ConfigCommonSIB-r18 ::= SEQUENCE { sdt-RSRP-ThresholdMT-r18 RSRP-Range OPTIONAL, -- Need S sdt-LogicalChannelSR-DelayTimer-r18 ENUMERATED { sf20, sf40, sf64, sf128, sf512, sf1024, sf2560, spare1} OPTIONAL, -- Cond MT-SDT1 t319a-r18 ENUMERATED { ms100, ms200, ms300, ms400, ms600, ms1000, ms2000, ms3000, ms4000, spare7, spare6, spare5, spare4, spare3, spare2, spare1} OPTIONAL -- Cond MT-SDT2 } -- TAG-SIB1-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

16.19.3.2.2 Conditional Handover

The same principle as described in 9.2.3.4 applies to ATG unless hereunder specified. ATG supports the following additional trigger conditions upon which UE may execute CHO to a candidate cell, as defined in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12]: - The RRM measurement-based event A4; - A location-based trigger condition. A location-based trigger condition is always configured together with one of the measurement-based trigger conditions (CHO events A3/A4/A5) as defined in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12].

3GPP TS 38.300

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

RAN2

3GPP Series : 38 , Radio technology beyond LTE

16.19.3.2.2

5.3.5.13a SCG activation

Upon initiating the procedure, the UE shall: 1> if the UE is configured with an SCG after receiving the message for which this procedure is initiated: 2> if the UE was configured with a deactivated SCG before receiving the message for which this procedure is initiated: 3> consider the SCG to be activated; 3> resume performing radio link monitoring on the SCG, if previously stopped; 3> indicate to lower layers to resume beam failure detection on the PSCell, if previously stopped; 3> indicate to lower layers that the SCG is activated.

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

5.3.5.13a

4.15.3 Time synchronization

Two types of synchronization processes are supported by the 5GS: 5GS synchronization and (g)PTP domain synchronization (see 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]). For 5GS synchronization, the lower layers provide the 5G internal system clock signalled via the NG-RAN (see 3GPP TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [30]) and the UE forwards the 5G internal system clock to the DS-TT(s). For (g)PTP domain synchronization, the UE supports forwarding (g)PTP messages (see 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8], 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9], and 3GPP TS 24.535[ 5G System (5GS); Device-Side Time Sensitive Networking (TSN) Translator (DS-TT) to Network-Side TSN Translator (NW-TT) protocol aspects; Stage 3 ] [19A]). For all (g)PTP domains associated with a PDU session: a) if the UE receives (g)PTP message via the PDU session, the UE forwards the (g)PTP messages to the DS-TT associated with the PDU session; or b) if the UE receives (g)PTP messages from the DS-TT associated with the PDU session, the UE forwards the (g)PTP messages via the PDU session. Depending on the 5G access stratum-based time distribution or (g)PTP-based time distribution, the network timing synchronization status of the nodes involved in the operation (e.g., NG-RAN nodes, NW-TTs) may change. Using the 5GMM protocol, the network can request a supporting UE to reconnect to the network upon receiving an indication of a change in the RAN timing synchronization status.

3GPP TS 24.501

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

CT WG1

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

4.15.3

5.22.2 Subscription-related Priority Mechanisms

Subscription-related mechanisms which are always applied: - (R)AN: During initial Access Network Connection Establishment, the Establishment Cause is set to indicate that special treatment is to be applied by the (R)AN in the radio resource allocation as specified in clause 5.2 for 3GPP access. - UDM: As defined in clause 5.2.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3], the UE subscription data in the UDM contains an MPS subscription indication (i.e. MPS priority) and an MCX subscription indication (i.e. MCX priority) for the UE that has subscription to MPS and MCX, respectively. The MPS priority and the MCX priority, if available, are provided to the AMF via the Registration or the UE Configuration Update procedure as defined in clause 4.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. - AMF: Following Access Network Connection Establishment, the receipt of the designated Establishment Cause (i.e. high priority access) by the AMF will result in priority handling of the "Initial UE Message" received as part of the Registration procedures of clause 4.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. If the AMF did not receive a designated Establishment Cause (i.e. high priority access), but when the AMF determines that there is a MPS priority (or MCX priority) in the UDM for that UE, the AMF shall provide priority handling for that UE at that time and shall provide the MPS priority (or MCX priority) to the UE via the Registration or the UE Configuration Update procedure, as defined in clause 4.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. In addition, certain exemptions to Control Plane Congestion and Overload Control are provided as specified in clause 5.19. Subscription-related mechanisms which are conditionally applied: - UE: When barring control parameters are broadcast by the RAN, access barring based on Access Identity(es) configured in the USIM and/or an Access Category is applied prior to an initial upstream transmission for the UE which provides a mechanism to limit transmissions from UEs categorized as non-prioritized, while allowing transmissions from UEs categorized as prioritized (such as MPS subscribed UEs), during the RRC Connection Establishment procedure as specified in clause 5.2. - UDM: One or more ARP priority levels are assigned for prioritized or critical services. The ARP of the prioritized QoS Flows for each DN is set to an appropriate ARP priority level. The 5QI is from the standard value range as specified in clause 5.7.2.7. In addition, Priority Level may be configured for the standardized 5QIs, and if configured, it overwrites the default value specified in the QoS characteristics Table 5.7.4-1. - PCF: The "IMS Signalling Priority" information is set for the subscriber in the UDM, and the PCF modifies the ARP of the QoS Flow used for IMS signalling, for each DN which supports prioritized services leveraging on IMS signalling, to an appropriate ARP priority level assigned for that service.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.22.2

5.27.1.2.1 Distribution of 5G internal system clock

The 5G internal system clock shall be made available to all user plane nodes in the 5G system. The UPF and NW-TT may get the 5G internal system clock via the underlying PTP compatible transport network with mechanisms outside the scope of 3GPP. The 5G internal system clock shall be made available to UE with signalling of time information related to absolute timing of radio frames as described in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [28]. The 5G internal system clock shall be made available to DS-TT by the UE.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.27.1.2.1

Annex E (informative): NG-RAN Architecture for Radio Access Network Sharing with multiple cell ID broadcast

Each NG-RAN node serving a cell identified by a Cell Identity associated with either a subset of PLMNs, or a subset of SNPNs, or a subset of PNI-NPNs is connected to another NG-RAN node via a single Xn-C interface instance. Each Xn-C interface instance is setup and removed individually. Xn-C interface instances terminating at NG-RAN nodes which share the same physical radio resources may share the same signalling transport resources. If this option is applied: - Non-UE associated signalling is associated to an Xn-C interface instance by including an Interface Instance Indication in the XnAP message; - Node related, non-UE associated Xn-C interface signalling may provide information destined for multiple logical nodes in a single XnAP procedure instance once the Xn-C interface instance is setup; NOTE 1: If the Interface Instance Indication corresponds to more than one interface instance, the respective XnAP message carries information destined for multiple logical nodes. - A UE associated signalling connection is associated to an Xn-C interface instance by allocating values for the corresponding NG-RAN node UE XnAP IDs so that they can be mapped to that Xn-C interface instance. NOTE 2: One possible implementation is to partition the value ranges of the NG-RAN node UE XnAP IDs and associate each value range with an Xn-C interface instance.

3GPP TS 38.300

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

RAN2

3GPP Series : 38 , Radio technology beyond LTE

Annex

6.4 UE associations in NG-RAN Node

There are several types of UE associations needed in the NG-RAN node: the "NG-RAN node UE context" used to store all information needed for a UE and the associations between the UE and the logical NG and Xn connections used for NG/XnAP UE associated messages. An "NG-RAN node UE context" exists for a UE in CM_CONNECTED. Definitions: NG-RAN node UE context: An NG-RAN node UE context is a block of information in an NG-RAN node associated to one UE. The block of information contains the necessary information required to maintain the NG-RAN services towards the active UE. An NG-RAN node UE context is established when the transition to RRC CONNECTED for a UE is completed or in the target NG-RAN node after completion of handover resource allocation during handover preparation, in which case at least UE state information, security information, UE capability information and the identities of the UE-associated logical NG-connection shall be included in the NG-RAN node UE context. For Dual Connectivity an NG-RAN node UE context is also established in the S-NG-RAN node after completion of S-NG-RAN node Addition Preparation procedure. If radio bearers are requested to be setup during a UE Context setup or modification procedure, the UE capabilities are signalled to the receiving node as part of the UE context setup or modification procedures. Bearer context: A bearer context is a block of information in a gNB-CU-UP node associated to one UE that is used for the sake of communication over the E1 interface. It may include the information about data radio bearers, PDU sessions and QoS-flows associated to the UE. The block of information contains the necessary information required to maintain user-plane services toward the UE. UE-associated logical NG/Xn/F1/E1-connection: NGAP, XnAP, F1AP and E1AP provide means to exchange control plane messages associated with the UE over the respectively NG-C, Xn-C, F1-C or E1 interface. A UE-associated logical connection is established during the first NGAP/XnAP/F1AP message exchange between the NG/Xn/F1 peer nodes. The connection is maintained as long as UE associated NG/XnAP/F1AP messages need to be exchanged over the NG/Xn/F1 interface. The UE-associated logical NG-connection uses the identities AMF UE NGAP ID and RAN UE NGAP ID. The UE-associated logical Xn-connection uses the identities Old NG-RAN node UE XnAP ID and New NG-RAN node UE XnAP ID, or M-NG-RAN node UE XnAP ID and S-NG-RAN node UE XnAP ID. The UE-associated logical F1-connection uses the identities gNB-CU UE F1AP ID and gNB-DU UE F1AP ID. The UE-associated logical E1-connection uses the identities gNB-CU-CP UE E1AP ID and gNB-CU-UP UE E1AP ID. When a node (AMF or gNB) receives a UE associated NGAP/XnAP/F1AP/E1AP message the node retrieves the associated UE based on the NGAP/XnAP/F1AP/E1AP ID. UE-associated signalling: UE-associated signalling is an exchange of NGAP/XnAP/F1AP/E1AP messages associated with one UE over the UE-associated logical NG/Xn/F1/E1-connection. NOTE1: The UE-associated logical NG-connection may exist before the NG-RAN node UE context is setup in the NG-RAN node. NOTE2: The UE-associated logical F1-connection may exist before the UE context is setup in the gNB-DU. NOTE3: The general principle described in this clause also applies to ng-eNB and W1/E1 interface, if not explicitly specified otherwise.

3GPP TS 38.401

NG-RAN; Architecture description

RAN3

3GPP Series : 38 , Radio technology beyond LTE

6.4

15.4.2.3 Cell DTX/DRX

To facilitate reducing gNB downlink transmission/uplink reception active time, UE can be configured with a periodic cell DTX/DRX pattern (i.e. active and non-active periods). The pattern configuration for cell DTX/DRX is common for the UEs configured with this feature in the cell. The cell DTX and cell DRX patterns can be configured and activated separately. A maximum of two cell DTX/DRX patterns can be configured per MAC entity for different serving cells. When cell DTX is configured and activated for the concerned cell, the UE may not monitor PDCCH in selected cases or does not monitor SPS occasions during cell DTX non-active duration. When cell DRX is configured and activated for the concerned cell, the UE does not transmit on CG resources or does not transmit a SR during cell DRX non-active duration. This feature is only applicable to UEs in RRC_CONNECTED state and it does not impact Random Access procedure, SSB transmission, paging, and system information broadcasting. Cell DTX/DRX can be activated/deactivated by RRC signalling or L1 group common signalling. Cell DTX/DRX is characterized by the following: - active duration: duration that the UE waits for to receive PDCCHs or SPS occasions, and transmit SR or CG. In this duration, the gNB transmission/reception of PDCCH, SPS, SR, CG, periodic and semi-persistent CSI report are not impacted for the purpose of network energy saving; - cycle: specifies the periodic repetition of the active-duration followed by a period of non-active duration. Active duration and cycle parameters are common between cell DTX and cell DRX, when both are configured; Once the gNB recognizes there is an emergency call or public safety related service (e.g. MPS or MCS), the network should ensure that there is no impact to that service (e.g. it may release or deactivate cell DTX/DRX configuration). The network should also ensure that there is at least partial overlapping between UE's connected mode DRX on-duration and cell DTX/DRX active duration, i.e. the UE's connected mode DRX periodicity is a multiple of cell DTX/DRX periodicity or vice versa.

3GPP TS 38.300

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

RAN2

3GPP Series : 38 , Radio technology beyond LTE

15.4.2.3

17.3.3 Provisioning GANC identifier

The Provisioning GANC identifier shall take the form of a fully qualified domain name (FQDN) as specified in IETF RFC 1035 [19] and IETF RFC 1123 [20]. The Provisioning GANC identifier consists of one or more labels. Each label shall consist of the alphabetic characters (A-Z and a-z), digits (0-9) and the hyphen (-) in accordance with IETF RFC 1035 [19]. Each label shall begin and end with either an alphabetic character or a digit in accordance with IETF RFC 1123 [20]. The case of alphabetic characters is not significant. If the (U)SIM is not provisioned with the FQDN or IP address of the Provisioning GANC, the UE derives an FQDN from the IMSI to identify the Provisioning GANC. The UE shall derive such an FQDN as follows: 1. create a domain name as specified in 17.3.1; 2. add the label "pganc." to the beginning of the domain name. An example of an FQDN for a Provisioning GANC is: IMSI in use: 234150999999999; Where: MCC = 234; MNC = 15; MSIN = 0999999999, Which gives the FQDN: pganc.gan.mnc015.mcc234.pub.3gppnetwork.org. NOTE: If it is not possible for the UE to identify whether a 2 or 3 digit MNC is used (e.g. SIM is inserted and the length of MNC in the IMSI is not available in the "Administrative data" data file), it is implementation dependent how the UE determines the length of the MNC (2 or 3 digits).

3GPP TS 23.003

Numbering, addressing and identification

CT WG4

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

17.3.3

1.6.1 List of procedures

The following procedures are specified in the present document: a) Clause 4 specifies elementary procedures for Mobility Management: - mobility management common procedures (subclause 4.3): - TMSI reallocation procedure (subclause 4.3.1); - authentication procedure (subclause 4.3.2); - identification procedure (subclause 4.3.3); - IMSI detach procedure (subclause 4.3.4); - abort procedure (subclause 4.3.5); - MM information procedure (subclause 4.3.6). - mobility management specific procedures (subclause 4.4): - location updating procedure (subclause 4.4.1); - periodic updating (subclause 4.4.2); - IMSI attach procedure (subclause 4.4.3); - generic location updating procedure (subclause 4.4). - connection management sublayer service provision: - mobility management connection establishment (subclause 4.5.1); - mobility management connection information transfer phase (subclause 4.5.2); - mobility management connection release (subclause 4.5.3). - GPRS specific mobility management procedures (subclause 4.7): - GPRS attach procedure (subclause 4.7.3); - GPRS detach procedure (subclause 4.7.4); - GPRS routing area updating procedure (subclause 4.7.5). - GPRS common mobility management procedures (subclause 4.7): - GPRS P-TMSI reallocation procedure (subclause 4.7.6); - GPRS authentication and ciphering procedure (subclause 4.7.7); - GPRS identification procedure (subclause 4.7.8); - GPRS information procedure (subclause 4.7.12). b) Clause 5 specifies elementary procedures for circuit switched Call Control comprising the following elementary procedures: - mobile originating call establishment (subclause 5.2.1); - mobile terminating call establishment (subclause 5.2.2); - signalling procedures during the active state (subclause 5.3): - user notification procedure (subclause 5.3.1); - call rearrangements (subclause 5.3.2); - DTMF protocol control procedure (subclause 5.5.7); - in-call modification (subclause 5.3.4). - call clearing initiated by the mobile station (subclause 5.4.3); - call clearing initiated by the network (subclause 5.4.4); - miscellaneous procedures: - in-band tones and announcements (subclause 5.5.1); - status enquiry procedure (subclause 5.5.3); - call re-establishment procedure (subclause 5.5.4). d) Clause 6 specifies elementary procedures for session management: - GPRS session management procedures (subclause 6.1): - PDP context activation (subclauses 6.1.3.1 and 6.1.3.2); - PDP context modification (subclause 6.1.3.3); - PDP context deactivation (subclause 6.1.3.4). - MBMS context activation (subclause 6.1.3.8); - MBMS context deactivation (subclause 6.1.3.9). The elementary procedures can be combined to form structured procedures. Examples of such structured procedures are given in clause 7. This part of the present document is only provided for guidance to assist implementations. Clause 8 specifies actions to be taken on various error conditions and also provides rules to ensure compatibility with future enhancements of the protocol.

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

1.6.1

6.2.5.1.1.4 QoS flow descriptions

The network can also provide the UE with one or more QoS flow descriptions associated with a PDU session at the PDU session establishment or at the PDU session modification. Each QoS flow description contains: a) a QoS flow identifier (QFI); b) if the flow is a GBR QoS flow: 1) Guaranteed flow bit rate (GFBR) for UL; 2) Guaranteed flow bit rate (GFBR) for DL; 3) Maximum flow bit rate (MFBR) for UL; 4) Maximum flow bit rate (MFBR) for DL; and 5) optionally averaging window, applicable for both UL and DL; c) 5QI, if the QFI is not the same as the 5QI of the QoS flow identified by the QFI; and d) optionally, an EPS bearer identity (EBI) if the QoS flow can be mapped to an EPS bearer as specified in subclause 4.11.1 of 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9]. If the averaging window is not included in a QoS flow description for a GBR QoS flow with a 5QI indicated in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8] table 5.7.4-1, the averaging window associated with the 5QI in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8] table 5.7.4-1 applies for the averaging window. If the averaging window is not included in a QoS flow description for a GBR QoS flow with a 5QI not indicated in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8] table 5.7.4-1, the standardized value of two seconds is used as the averaging window.

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

4.3.2.1 Common MR-DC principles

There are different U-plane connectivity options of the MN and SN involved in MR-DC for a certain UE, as shown in Figure 4.3.2.1-1. The U-plane connectivity depends on the bearer option configured: - For MN terminated bearers, the user plane connection to the CN entity is terminated in the MN; - For SN terminated bearers, the user plane connection to the CN entity is terminated in the SN; - The transport of user plane data over the Uu either involves MCG or SCG radio resources or both: - For MCG bearers, only MCG radio resources are involved; - For SCG bearers, only SCG radio resources are involved; - For split bearers, both MCG and SCG radio resources are involved. - For split bearers, MN terminated SCG bearers and SN terminated MCG bearers, PDCP data is transferred between the MN and the SN via the MN-SN user plane interface. Figure 4.3.2.1-1: U-Plane connectivity for EN-DC (left) and MR-DC with 5GC (right).

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

4.3.2.1

17.7.18 MBMS-User-Data-Mode-Indication AVP

The MBMS-User-Data-Mode-Indication AVP (AVP code 915) is of type Enumerated. The meaning of the message containing this AVP depends on the sending entity. The absence of this AVP indicates unicast mode of operation. The following values are supported: Unicast (0) When BM-SC sends this value, that indicates to GGSN that BM-SC supports only unicast mode (IP multicast packets encapsulated over UDP by IP unicast header). When GGSN sends this value, that indicates to BM-SC that BM-SC shall send user plane data with unicast mode (IP multicast packets encapsulated over UDP by IP unicast header). Multicast and Unicast (1) When BM-SC sends this value, that indicates to GGSN that BM-SC supports both modes of operation. When GGSN sends this value, that indicates to BM-SC that BM-SC shall send user plane data with multicast mode.

3GPP TS 29.061

Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN)

CT WG3

3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network

17.7.18

X.8 Protection of data and analytics exchange in roaming case X.8.1 General

The protection of data and analytics exchange in roaming case including authorization and anonymization of data/analytics: - Authorization at data and analytics level is enforced by the roaming entry NWDAF producer. The parameters used by NWDAF service consumer to request/subscribe to the services provided by NWDAF producer are defined in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [105], clause 6.1.5. Accordingly, the operator authorization policies can be configured locally in the NWDAF producer. Also, when the NWDAF in one PLMN requests an access token from the NRF in the peer PLMN, the access token request and the access token claims may contain the Analytics ID. - The roaming entry NWDAF producer is responsible to control the amount of exposed data/analytics and to abstract or hide internal network aspects in the exposed data/analytics. The corresponding mechanisms used to restrict the data/analytics and/or anonymization are subject to the implementation.

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

X.8

– CSI-RS-ResourceMapping

The IE CSI-RS-ResourceMapping is used to configure the resource element mapping of a CSI-RS resource in time- and frequency domain. CSI-RS-ResourceMapping information element -- ASN1START -- TAG-CSI-RS-RESOURCEMAPPING-START CSI-RS-ResourceMapping ::= SEQUENCE { frequencyDomainAllocation CHOICE { row1 BIT STRING (SIZE (4)), row2 BIT STRING (SIZE (12)), row4 BIT STRING (SIZE (3)), other BIT STRING (SIZE (6)) }, nrofPorts ENUMERATED {p1,p2,p4,p8,p12,p16,p24,p32}, firstOFDMSymbolInTimeDomain INTEGER (0..13), firstOFDMSymbolInTimeDomain2 INTEGER (2..12) OPTIONAL, -- Need R cdm-Type ENUMERATED {noCDM, fd-CDM2, cdm4-FD2-TD2, cdm8-FD2-TD4}, density CHOICE { dot5 ENUMERATED {evenPRBs, oddPRBs}, one NULL, three NULL, spare NULL }, freqBand CSI-FrequencyOccupation, ... } -- TAG-CSI-RS-RESOURCEMAPPING-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

4.3.5.8 Ethernet PDU Session Anchor Relocation

This procedure allows for Ethernet PDU Sessions to change the PDU Session Anchor (PSA) while the session remains set up. Originally the Ethernet PDU Session goes via the Source UPF acting as the PSA. The Ethernet context which contains all Ethernet specific information including the MAC address of the UE and possibly its VLAN tag(s) is reported from the Source PSA UPF to the SMF. It is possible to report multiple MAC addresses (with their VLAN tag(s)) if these are reachable via the UE. The SMF determines whether and when a serving PDU Session anchor for an Ethernet PDU Session needs to be changed and selects the Target PSA UPF, establishes the N4 session at the Target PSA UPF. The information within the Ethernet context is sent to the Target UPF. Based on the information in the Ethernet context, the Target PSA UPF may take action to update the Ethernet forwarding in the data network. Figure 4.3.5.8-1: Ethernet PDU Session Anchor Relocation Initially, the Ethernet PDU Session is established with the user data going via the Source UPF. The Source UPF acts as the PSA. 1. The Source UPF reports the Ethernet context which contains all Ethernet specific information including the MAC address of the UE and possibly its VLAN tag(s) that the UPF has learned from the UE side to the SMF. In the case of any changes in the Ethernet context, the change is updated to the SMF so that the SMF maintains an up-to-date state of the Ethernet context. This signalling is realized based on N4 reporting. 2. The UPF's report is acknowledged. 3-5. In the case of handover, the RAN handover preparation and execution is followed by path switch signalling to the AMF and corresponding signalling to SMF, as defined in clause 4.9.1.2. 6. The SMF decides that the PSA is to be changed for the Ethernet PDU Session and selects the Target UPF that will act as the new PSA. The decision may be triggered by a mobility event, such as receiving the message in step 5. 7. The Target UPF N4 session is established. The SMF provides the N3 tunnel endpoint used by RAN. 8. The establishment of the new N4 session is acknowledged from the Target UPF to the SMF. The UPF provides its N3 tunnel endpoint. 9-10. In the case of handover, the SMF signals to the RAN via the AMF to provide the Path Switch Request Ack, which includes the update of the uplink N3 tunnel endpoint to the target UPF. This signalling is defined in clause 4.9.1.2. In steps 9-10, an indication is sent from the SMF via the AMF to the RAN node indicating that the RAN node should not expect to receive an end marker packet. The RAN node may skip trying to reorder the downlink packets. 11-12. If there is no handover and the UE is in connected mode, the SMF sends PDU Session Modify Request message to the RAN via the AMF, which includes the update of the uplink N3 tunnel endpoint to the target UPF. The RAN acknowledges the message. The RAN node does not need to to reorder the downlink packets. NOTE 1: Due to the change in the end to end path, packet re-ordering can occur both for the handover and no handover cases. If necessary, upper layer protocols can ensure in sequence delivery. After steps 9-10 or 11-12, uplink Ethernet frames pass via the target UPF. Downlink Ethernet frames may continue to be delivered from the source UPF to the RAN node. In the case of handover, the Ethernet frames are forwarded from the source RAN node to the target RAN node. 13-14. The SMF sends an N4 Session Modification Request to the Target UPF which includes the information in Ethernet context (i.e. MAC address and VLAN tag(s)) and a trigger for updating the Ethernet forwarding (next step). The Target UPF acknowledges by an N4 Session Modification Response. 15. The Target UPF may assist in the update of Ethernet forwarding tables of Ethernet switches in the DN via a variety of mechanisms, the use of which are specific to the DN and the specification of which are out-of-scope for 3GPP. NOTE 2: The UPF acting as a switch in the DN, can for example issue a Gratuitous ARP (GARP) containing the MAC address(es) of the UE that has switched to the new anchor, or the UPF can send an unsolicited Neighbor Discovery Protocol (NDP) Neighbor Advertisement message indicating the UE MAC addresses, or the UPF can generate a uplink Ethernet frame with the UE's MAC addresses as source MAC addresses (and possibly its VLAN tag(s)) and configurable payload which will be dropped by endhosts, or the UPF can send another message or Ethernet frame compatible with DN protocols. In the case of a central controller in the Ethernet network which sets the forwarding tables, the central controller can be instructed that the given MAC address is reachable at the new location. When multiple MAC addresses are present in the Ethernet context, the update of the Ethernet forwarding is performed for each MAC address. 16. The N4 session is released at the Source UPF. The source UPF may wait for a configurable period before it stops delivering downlink Ethernet frames for the given PDU Session. 17. The N4 session release is acknowledged from the Source UPF to the SMF.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.3.5.8

5.28a.3 Topology Information for TSN TN

NG-RAN and UPF may support u-plane LLDP functionality to provide topology information to the TN. When LLDP is supported, AN-TL and CN-TL shall perform the LLDP functionality at the u-plane without the need to interact with the c-plane. Further there is no need for 5GS interaction with TN CNC directly. This is achieved with following measures: - AN-TL and CN-TL implement the Transmit Only operation mode as defined in clause 9.1 of IEEE Std 802.1AB [97]. - The TSN End Station is pre-configured with parameter set for Transmit Only operating mode as defined in clause 9.2 of IEEE Std 802.1AB [97]. - The System Capabilities TLV may also be set to Station Only as defined in clause 8.5.8 of IEEE Std 802.1AB [97].

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.28a.3

6.8.2.4 R99+ ME

R99+ ME with a SIM inserted, shall participate only in GSM AKA. GSM AKA results in the establishment of a GSM security context; the GSM cipher key Kc and the cipher key sequence number CKSN are stored in the ME. When the user is attached to a UTRAN, R99+ ME shall derive the UMTS cipher/integrity keys CK and IK from the GSM cipher key Kc using the conversion functions c4 and c5. The ME shall handle the STARTCS and STARTPS as described in section 6.4.8 with the exception that the START values shall be stored in non-volatile memory on the ME rather than on the GSM SIM. If a different SIM is inserted then the ME shall delete the GSM cipher keys for the PS and CS domain (Kc), the derived UMTS cipher/integrity keys (CK and IK) for the PS and CS domain, and reset the START values to zero. The ME shall then trigger a new authentication and key agreement at the next connection establishment by indicating to the network that no valid keys are available for use using the procedure described in section 6.4.4. When the user is attached to a UTRAN, a R99+ ME with a SIM inserted shall use a default value of all ones for maximum value of STARTCS or STARTPS. The ME shall handle the maximum value of STARTCS or STARTPS as described in section 6.4.3 with the exception that the maximum value of STARTCS or STARTPS is stored on the ME rather than on the GSM SIM.

3GPP TS 33.102

3G security; Security architecture

SA WG3

3GPP Series : 33 , Security aspects

6.8.2.4

6.6.2D Out of band emission for ProSe

When UE is configured for E-UTRA ProSe sidelink transmissions non-concurrent with E-UTRA uplink transmissions for E-UTRA ProSe operating bands specified in Table 5.5D-1, the requirements in subclause 6.6.2 apply. When UE is configured for simultaneous E-UTRA ProSe sidelink and E-UTRA uplink transmissions for inter-band E-UTRA ProSe / E-UTRA bands specified in Table 5.5D-2, the requirements in subclause 6.6.2 apply per E-UTRA ProSe sidelink and E-UTRA uplink transmission as specified for the corresponding inter-band aggregation with uplink assigned to two bands.

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

9.3.8.3.1 FDD

For the parameters specified in Table 9.3.8.3.1-1, and using the downlink physical channels specified in Annex C, the minimum requirements are specified in Table 9.3.8.3.1-2 and by the following a) the ratio of the throughput obtained for the Type B receiver with NAICS assistance information when transmitting the transport format indicated by each reported wideband CQI index subject to interference sources with specified and that obtained for the Type B receiver without NAICS assistance information when transmitting the transport format indicated by each reported wideband CQI index subject to interference sources with the same specified shall be ≥ ; Table 9.3.8.3.1-1 Fading test for single antenna (FDD) Table 9.3.8.3.1-2 Minimum requirement (FDD)

3GPP TS 36.101

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

RAN4

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

9.3.8.3.1

14.2.2 Nudm_UEAuthentication_Get service operation

Service operation name: Nudm_UEAuthentication_Get Description: Requester NF gets the authentication data from UDM. For AKA based authentication, this operation can be also used to recover from synchronization failure situations. If SUCI is included, this service operation returns the SUPI. Inputs, Required: SUPI or SUCI, serving network name. Inputs, Optional: Synchronization Failure indication and related information (i.e. RAND/AUTS) , Disaster Roaming service indication, NSWO indicator. NOTE: If NSWO indicator is present then the serving network name contains "5G:NSWO". Outputs, Required: Authentication method Editor's note: How the UDM indicates to the AUSF to run primary authentication with an external Credentials holder is FFS. Outputs, Optional: SUPI if SUCI was used as input. Depending on the authentication method, authentication data (e.g. AKA authentication vector) for the SUPI. AKMA Indication and Routing indicator, if the subscriber has an AKMA subscription (see TS 33.535[ Authentication and Key Management for Applications (AKMA) based on 3GPP credentials in the 5G System (5GS) ] [91]). MSK indicator.

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

14.2.2

6.1.3.7 Protocol configuration options

The MS and the GGSN may communicate parameters by means of the protocol configuration options information element or extended protocol configuration options information element when activating, modifying or deactivating a PDP context. Such parameters can e.g. be used to convey information from external protocols between the MS and the GGSN. An overview of how the protocol configuration options information element is used is specified in 3GPP TS 27.060[ Packet domain; Mobile Station (MS) supporting Packet Switched services ] [36a]. The protocol configuration options information element and the extended protocol configuration options information element is transparent to the SGSN. NOTE 1: The MS and the network negotiate support of the extended protocol configuration options IE end-to-end for each PDN connection, as the information element can only be used if it is supported also by the GGSN/PDN GW. If supported by the network and the MS end-to-end for a PDN connection, protocol configuration options shall be exchanged via the extended protocol configuration options IE. Otherwise the protocol configuration options IE is used. For the MS, the extended protocol configuration options is supported by the network and the MS end-to-end for a PDN connection if the network has indicated support of the extended protocol configuration options IE in the last ATTACH ACCEPT or ROUTING AREA UPDATING ACCEPT message, and - the PDP Type requested for the default PDP context is non-IP; or - the network has included the extended protocol configuration options IE in at least one session management message received by the MS for this PDN connection. For the SGSN, the extended protocol configuration options is supported by the network and the MS end-to-end for a PDN connection if the MS has indicated support of the extended protocol configuration options IE in the last ATTACH REQUEST or ROUTING AREA UPDATING REQUEST message, and - the PDP Type requested for the default PDP context is non-IP; or - the SGSN has received the extended protocol configuration options IE in at least one message sent by the GGSN or PDN GW towards the MS for this PDN connection (for details 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]). NOTE 2: For the GGSN or PDN GW, the extended protocol configuration options is supported by the network and the MS end-to-end for a PDN connection if: - the GGSN initiates a network requested PDP context activation with offered PDP Type non-IP; or - the last support indication received from the SGSN or S-GW indicates that extended protocol configuration options is supported for this PDN connection (for details 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]).

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

8.129 Serving PLMN Rate Control

Serving PLMN Rate Control may be configured in the Serving PLMN network, to protect serving network, e.g. the MME and the Signalling Radio Bearers in the E-UTRAN, from the load generated by NAS Data PDUs. It defines the maximum number of the NAS Data PDUs which can be transferred by the Serving Network per 6 minute interval. The maximum number of the NAS Data PDUs which can be transferred for both downlink and uplink shall be configured to a value greater than 10. When the value is set to 0, it shall indicate Serving PLMN Rate Control is not applicable to the PDN Connection for the given direction. The Serving PLMN Rate Control shall only apply to the PDN Connection(s) which is set to Control Plane Only. Serving PLMN Rate Control Information is coded as depicted in Figure 8.129-1. Figure 8.129-1: Serving PLMN Rate Control

3GPP TS 29.274

3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3

CT WG4

3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network

8.129

9.2.1.3 State Transitions

The following figure describes the UE triggered transition from RRC_IDLE to RRC_CONNECTED (for the NAS part, see TS 23.502[ Procedures for the 5G System (5GS) ] [22]): Figure 9.2.1.3-1: UE triggered transition from RRC_IDLE to RRC_CONNECTED 1. The UE requests to setup a new connection from RRC_IDLE. 2/2a. The gNB completes the RRC setup procedure. NOTE: The scenario where the gNB rejects the request is described below. 3. The first NAS message from the UE, piggybacked in RRCSetupComplete, is sent to AMF. 4/4a/5/5a. Additional NAS messages may be exchanged between UE and AMF, see TS 23.502[ Procedures for the 5G System (5GS) ] [22]. 6. The AMF prepares the UE context data (including PDU session context, the Security Key, UE Radio Capability and UE Security Capabilities, etc.) and sends it to the gNB. 7/7a. The gNB activates the AS security with the UE. 8/8a. The gNB performs the reconfiguration to setup SRB2 and DRBs for UE, or SRB2 and optionally DRBs for IAB-MT. 9. The gNB informs the AMF that the setup procedure is completed. NOTE 1: RRC messages in step 1 and 2 use SRB0, all the subsequent messages use SRB1. Messages in steps 7/7a are integrity protected. From step 8 on, all the messages are integrity protected and ciphered. NOTE 2: For signalling only connection, step 8 is skipped since SRB2 and DRBs are not setup. The following figure describes the rejection from the network when the UE attempts to setup a connection from RRC_IDLE: Figure 9.2.1.3-2: Rejection of UE triggered transition from RRC_IDLE 1. UE attempts to setup a new connection from RRC_IDLE. 2. The gNB is not able to handle the procedure, for instance due to congestion. 3. The gNB sends RRCReject (with a wait time) to keep the UE in RRC_IDLE.

3GPP TS 38.300

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

RAN2

3GPP Series : 38 , Radio technology beyond LTE

9.2.1.3

5.7.8.4 Cell re-selection or cell selection while T331 is running

The UE shall: 1> if intra-RAT cell selection or reselection occurs while T331 is running: 2> if validityAreaList is configured in VarMeasIdleConfig: 3> if the serving frequency does not match with the carrierFreq of an entry in the validityAreaList; or 3> if the serving frequency matches with the carrierFreq of an entry in the validityAreaList, the validityCellList is included in that entry, and the physical cell identity of the serving cell does not match with any entry in validityCellList: 4> stop timer T331; 4> perform the actions as specified in 5.7.8.3, upon which the procedure ends. 1> else if inter-RAT cell selection or reselection occurs while T331 is running: 2> stop timer T331; 2> perform the actions as specified in 5.7.8.3;

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

5.7.8.4

6.1.4.2 Coordination between 5GSM and ESM without N26 interface

When the network does not support N26 interface, the SMF does not provide the UE with the mapped EPS bearer context for a PDU session. NOTE 1: Since the SMF does not provide the UE with the mapped EPS bearer context for a PDU session, the UE does not know whether interworking with EPS is supported for a PDU session before attempting to transfer the PDU session from N1 mode to S1 mode. NOTE 2: It is up to UE implementation to decide which PDU session(s) to be attempted to transfer from N1 mode to S1 mode, e.g. based on UE policy or UE local configuration. Upon inter-system change from N1 mode to S1 mode in EMM-IDLE mode, the UE shall not transfer a PDU session for LADN to EPS. Upon inter-system change from N1 mode to S1 mode in EMM-IDLE mode, the UE shall not transfer a multi-homed IPv6 PDU session to EPS. Upon inter-system change from N1 mode to S1 mode in EMM-IDLE mode, the UE shall use the parameters from each PDU session which the UE intends to transfer to EPS to create the contents of a PDN CONNECTIVITY REQUEST message as follows: a) if the PDU session is an emergency PDU session, the request type shall be set to "handover of emergency bearer services". Otherwise the request type shall be set to "handover"; b) the PDU session type of the PDU session shall be mapped to the PDN type of the default EPS bearer context as follows: 1) the PDN type shall be set to "non-IP" if the PDU session type is "Unstructured"; 2) the PDN type shall be set to "IPv4" if the PDU session type is "IPv4"; 3) the PDN type shall be set to "IPv6" if the PDU session type is "IPv6"; 4) the PDN type shall be set to "IPv4v6" if the PDU session type is "IPv4v6"; 5) the PDN type shall be set to "non-IP" if the PDU session type is "Ethernet" and the UE, the network or both of them do not support Ethernet PDN type in S1 mode; and 6) the PDN type shall be set to "Ethernet" if the PDU session type is "Ethernet" and the UE and the network support Ethernet PDN type in S1 mode; c) the DNN of the PDU session shall be mapped to the APN of the default EPS bearer context, unless the PDU session is an emergency PDU session; d) the PDU session ID parameter in the Protocol configuration options IE or Extended protocol configuration options IE shall be set to the PDU session identity of the PDU session; and e) if the PDU session is an MA PDU session established over 3GPP access, the ATSSS request parameter shall be included in the Protocol configuration options IE or Extended protocol configuration options IE. After inter-system change from N1 mode to S1 mode, the UE shall associate the PDU session identity with the default EPS bearer context. If the PDU session being transferred is a non-emergency PDU session, the UE shall in addition associate the S-NSSAI and the PLMN ID of the current PLMN with the default EPS bearer context. Upon successful completion of an EPS attach procedure after inter-system change from N1 mode to S1 mode (see 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]), the UE shall delete any UE derived QoS rules except when the PDU session is an MA PDU session established over 3GPP access and non-3GPP access both connected to the 5GCN. The UE shall perform a local release of the PDU session(s) and QoS flow(s) associated with the 3GPP access which have not been transferred to EPS. The UE shall also perform a local release of any QoS flow description not associated with any QoS rule. For PDU session(s) associated with non-3GPP access in 5GS, if present, the UE may: a) keep some or all of these PDU sessions still associated with non-3GPP access in 5GS, if supported; b) release some or all of these PDU sessions explicitly by initiating the UE requested PDU session release procedure(s); or c) attempt to transfer some or all of these PDU sessions from N1 mode to S1 mode by initiating the UE requested PDN connectivity procedure(s) with the PDN CONNECTIVITY REQUEST message created as above. When the network does not support N26 interface, the MME does not provide the UE with the mapped PDU session for a PDN connection but provides the UE with an S-NSSAI if the PDN connection is not for emergency bearer services. When establishing a new PDN connection in S1 mode, to enable the UE to attempt to transfer the PDN connection from S1 mode to N1 mode in case of inter-system change, the UE shall allocate a PDU session identity, indicate the allocated PDU session identity in the PDU session ID parameter in the Protocol configuration options IE of the PDN CONNECTIVITY REQUEST message and associate the allocated PDU session identity with the default EPS bearer context of the PDN connection. If an N5CW device supporting 3GPP access establishes a new PDN connection in S1 mode, the N5CW device supporting 3GPP access shall refrain from allocating "PDU session identity value 15". The network provides the UE with an S-NSSAI and the related PLMN ID in the Protocol configuration options IE or Extended protocol configuration options IE of the ACTIVATE DEFAULT EPS BEARER REQUEST message, the UE shall delete the stored S-NSSAI and the related PLMN ID, if any, and shall store the S-NSSAI and the related PLMN ID provided in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message. NOTE 3: Since the MME does not provide the UE with the mapped PDU session for a PDN connection, the UE does not know whether interworking to 5GS is supported for a PDN connection for which the UE assigned a PDU Session identity before attempting to transfer the PDN connection from S1 mode to N1 mode. NOTE 4: It is up to UE implementation to decide which PDN connection(s) to be attempted to transfer from S1 mode to N1 mode, e.g. based on UE policy or UE local configuration. NOTE 5: If the PDN connection has been transferred from a PDN connection established via non-3GPP access to EPC, it is possible that the network provided the S-NSSAI already during the establishment via non-3GPP access (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 from S1 mode to N1 mode in 5GMM-IDLE mode, the UE uses the parameters from the default EPS bearer context of each PDN connection which the UE intends to transfer to 5GS and for which the UE has allocated a PDU session identity to create a PDU SESSION ESTABLISHMENT REQUEST message as follows: a) 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: 1) "MA PDU request", if the PDN connection to be transferred is a user-plane resource of an MA PDU session; or 2) "existing PDU session"; b) the PDN type of the default EPS bearer context shall be mapped to the PDU session type of the PDU session as follows: 1) if the PDN type is "non-IP": - the PDU session type is set to the locally available information associated with the PDN connection (either "Ethernet" or "Unstructured"), if available; or - otherwise, the PDU session type is set to "Unstructured"; 2) if the PDN type is "IPv4" the PDU session type is set to "IPv4"; 3) if the PDN type is "IPv6", the PDU session type is set to "IPv6"; 4) if the PDN type is "IPv4v6", the PDU session type is set to "IPv4v6"; and 5) if the PDN type is "Ethernet", the PDU session type is set to "Ethernet"; and c) the APN of the default EPS bearer context shall be mapped to the DNN of the PDU session, unless the PDN connection is an emergency PDN connection; d) the PDU session ID shall be set to the PDU session identity included by the UE in the Protocol configuration options IE or Extended protocol configuration options IE in the PDN CONNECTIVITY REQUEST message, or to the PDU session ID associated with the default EPS bearer context; and e) if the PDU session is not an emergency PDU session, the S-NSSAI of the PDU session shall be set to the S-NSSAI included by the network in the Protocol configuration options IE or Extended protocol configuration options IE in the ACTIVATE DEFAULT EPS BEARER REQUEST message, if provided by the network, or the S-NSSAI associated with the default EPS bearer context, if available. NOTE 6: If T3584 is running or deactivated for the S-NSSAI and optionally the DNN combination, the UE is allowed to initiate ESM procedures in EPS with or without APN corresponding to that DNN, and if the APN is congested in EPS, the MME can send a back-off timer for the APN to the UE as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]. The UE shall locally release the PDN connection(s) and EPS bearer(s) associated with the 3GPP access which have not been transferred to 5GS. Upon inter-system change from N1 mode to S1 mode, if the UE has any PDU sessions associated with one or more MBS multicast sessions, the UE shall locally leave the associated multicast MBS sessions and the network 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.4.2

V.4 User consent revocation

Any NF that is deemed an enforcement point for user consent shall support subscription to the user consent parameter change notification provided by the UDM. Consumer NFs (processing the data pertaining to user consent) shall subscribe to UDM for user consent parameter change notification, except if the consent enforcement NF that is deemed an enforcement point is tracking of those NFs and is actively informing those consumer NFs in case of user consent revocation. NOTE: When authorization consumer NFs for data processing subject to user consent, care needs to be taken to not authorize requests by those consumers that do not support the necessary services or related parameters for revocation. This is important because the user consent may change in the future. Upon notification of user consent revocation, any NF that is deemed an enforcement point for user consent shall no longer accept any service request for data processing subject to a revoked user consent. Upon notification of user consent revocation, any NF that is deemed an enforcement point for user consent may notify other NFs to halt the processing of the data subject to the revoked user consent. Upon notification of user consent revocation, NFs (processing the data pertaining to the revoked consent) shall halt processing and collection of the data. Upon notification of user consent revocation, NFs may delete, quarantine, or temporarily retain the data pertaining to the revoked user consent based on local policies and legal constraints.

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

V.4

6.4.2.5 Abnormal cases in the UE

The following abnormal cases can be identified: a) Expiry of timer T3581. The UE shall, on the first expiry of the timer T3581, retransmit the PDU SESSION MODIFICATION REQUEST message and the PDU session information which was transported together with the initial transmission of the PDU SESSION MODIFICATION REQUEST message and shall reset and start timer T3581. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3581, the UE shall abort the procedure and shall release the allocated PTI. b) Invalid PDU session identity. Upon receipt of the PDU SESSION MODIFICATION REJECT message including 5GSM cause #43 "invalid PDU session identity", the UE shall perform a local release of the existing PDU session and shall stop the timer T3581. c) Collision of network-requested PDU session release procedure and UE-requested PDU session modification procedure. If the UE receives a PDU SESSION RELEASE COMMAND message during the UE-requested PDU session modification procedure, and the PDU session indicated in the PDU SESSION RELEASE COMMAND message is the PDU session that the UE had requested to modify, the UE shall abort the PDU session modification procedure and proceed with the network-requested PDU session release procedure. d) Handling DL user data packets marked with RQI when UE has already revoked the usage of reflective QoS If the UE receives a DL user data packet marked with a RQI and the DL user data packet belongs to a PDU session of IPv4, IPv6, IPv4v6 or Ethernet PDU session type for which the UE has already revoked the usage of reflective QoS, then the UE shall ignore the RQI and shall handle the received DL user data packet. e) Collision of network-requested PDU session modification procedure and UE-requested PDU session modification procedure. The handling of the same abnormal case as described in subclause 6.3.2.6 applies. f) Upon receiving an indication that the 5GSM message was not forwarded due to service area restrictions along with a PDU SESSION MODIFICATION REQUEST message with the PDU session ID IE set to the same value as the PDU session ID that was sent by the UE, the UE shall abort the procedure and shall stop the timer T3581. g) Upon receiving an indication that the 5GSM message was not forwarded due to routing failure along with a PDU SESSION MODIFICATION REQUEST message with the PDU session ID IE set to the same value as the PDU session ID that was sent by the UE, the UE shall stop timer T3581 and shall abort the procedure. ga) Upon receiving an indication that the 5GSM message was not forwarded because the UE accessing via a satellite NG-RAN cell is informed that the PLMN is not allowed to operate at the present UE location along with a PDU SESSION MODIFICATION REQUEST message with the PDU session ID IE set to the same value as the PDU session ID that was sent by the UE, the UE shall stop timer T3581 and shall abort the procedure. h) Collision of UE-requested PDU session modification procedure and N1 NAS signalling connection release The UE may immediately retransmit the PDU SESSION MODIFICATION REQUEST message and stop, reset and restart timer T3581, if the following conditions apply: 1) The original UE-requested PDU session modification procedure was initiated over an existing N1 NAS signalling connection; and 2) the previous transmission of the PDU SESSION MODIFICATION REQUEST message was not initiated due to timer T3581 expiry. i) Rejection of a UE-requested PDU session modification procedure when the UE has initiated the procedure to delete one or more non-default QoS rules for the PDU session: Upon receipt of a PDU SESSION MODIFICATION REJECT message with 5GSM cause value #31 "request rejected, unspecified", if the UE had initiated deletion of one or more non-default QoS rules for the PDU session, as an implementation option, 1) it may perform a local release of the PDU session and shall stop the timer T3581. In order to synchronize the PDU session context with the AMF, the UE shall perform the registration procedure for mobility and periodic registration update with a REGISTRATION REQUEST message including the PDU session status IE; or 2) it shall stop the timer T3581 and initiate the UE-requested PDU session release 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

6.4.2.5

4.2.11.3 Configuration for Early Admission Control (EAC) update procedure

The configuration for Early Admission Control (EAC) update procedure indicates to the AMF the activation or the deactivation of the EAC mode for the S-NSSAI subject to NSAC. EAC mode means that the AMF is required to perform the number of UEs per network slice availability check and update procedure before the S-NSSAI subject to NSAC is included in the Allowed NSSAI or Partially Allowed NSSAI and sent to the UE. EAC mode is only applicable in the AMF when the update flag is set to increase. The AMF implicitly subscribes to the EAC notification for the S-NSSAI when it performs the first network slice availability check and update procedure for the S-NSSAI with the NSACF. The NSACF sends the EAC mode notification towards all notification endpoints associated with the S-NSSAI. Figure 4.2.11.3-1: Early Admission Control (EAC) update procedure 1. The number of UEs registered with a network slice subject to NSAC crosses a certain operator defined threshold. The NSACF determines whether to activate or deactivate the EAC mode. 2. The NSACF triggers Nnsacf_NSAC_EACNotify operation including the S-NSSAI(s) for which the EAC mode is to be activated or deactivated and a EAC flag(s) set to activated if the number of UEs registered with the network slice is above certain threshold or set to deactivated if the number of the UEs registered with the network slice is below certain threshold which may be same or different with respect to the activation threshold. NOTE 1: When the operator set the EAC inactive threshold, the Denial-of-Service issue due to a potential burst of registration request needs to be taken into account. 3. The AMF uses the EAC flag to decide when to trigger the number of UEs per network slice availability check and update procedure so that delays to the registration procedure and impact to the already allowed network slices are avoided. If the EAC flag indicates EAC mode activated, the AMF triggers the number of UEs per network slice availability check and update procedure before the Registration Accept step of the registration procedure or before the UE Configuration Update message. If the EAC flag indicates EAC mode deactivated, the AMF triggers the number of UEs per network slice availability check and update procedure after Registration Accept step of the registration procedure or after the UE Configuration Update. NOTE 2: When the S-NSSAI subject to NSAC and NSSAA, with EAC mode activated or deactivated, the AMF performs them as described in clause 4.2.11.2.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.2.11.3

5.3.3A.2 Precoding for spatial multiplexing

Precoding for spatial multiplexing is only used in combination with layer mapping for spatial multiplexing as described in clause 5.3.2A.2. Spatial multiplexing supports or antenna ports where the set of antenna ports used for spatial multiplexing is and , respectively. Precoding for spatial multiplexing is defined by where , . The precoding matrix of size is given by one of the entries in Table 5.3.3A.2-1 for and by Tables 5.3.3A.2-2 through 5.3.3A.2-5 for where the entries in each row are ordered from left to right in increasing order of codebook indices. Table 5.3.3A.2-1: Codebook for transmission on antenna ports Table 5.3.3A.2-2: Codebook for transmission on antenna ports with Table 5.3.3A.2-3: Codebook for transmission on antenna ports with Table 5.3.3A.2-4: Codebook for transmission on antenna ports with Table 5.3.3A.2-5: Codebook for transmission on antenna ports with

3GPP TS 36.211

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

RAN1

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

5.3.3A.2

4.4.7 Protection of NAS IEs

The network can provide the SOR transparent container IE during the registration procedure to the UE in the REGISTRATION ACCEPT message. The SOR transparent container IE is integrity protected by the HPLMN or subscribed SNPN as specified in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. The UE can provide the SOR transparent container IE during the registration procedure to the network in the REGISTRATION COMPLETE message. The SoR-MAC-IUE in the SOR transparent container IE is generated by the UE as specified in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. The network can provide the Payload container IE during the Network-initiated NAS transport procedure to the UE in DL NAS TRANSPORT message. If the Payload container type IE is set to "SOR transparent container" or "UE parameters update transparent container", the Payload container IE is integrity protected by the HPLMN or subscribed SNPN as specified in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. If the Payload container type IE is set to "Multiple payloads" and the payload container type field of the payload container entry is set to "SOR transparent container" or "UE parameters update transparent container", the payload container entry contents field of the payload container entry is integrity protected correspondingly. The UE can provide the Payload container IE during the UE-initiated NAS transport procedure to the network in UL NAS TRANSPORT message. If the Payload container type IE is set to "SOR transparent container" or "UE parameters update transparent container", the SoR-MAC-IUE or UPU-MAC-IUE in the Payload container IE is generated by the UE as specified in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. If the Payload container type IE is set to "Multiple payloads" and the payload container type field of the payload container entry is set to "SOR transparent container" or "UE parameters update transparent container", the SoR-MAC-IUE or UPU-MAC-IUE in the payload container entry contents field of the payload container entry is generated by the UE correspondingly.

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

10.5.1.13 PLMN list

The purpose of the PLMN List information element is to provide a list of PLMN codes to the mobile station. The PLMN List information element is coded as shown in figure 10.5.13/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.13/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The PLMN List is a type 4 information element with a minimum length of 5 octets and a maximum length of 47 octets. Figure 10.5.13/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] PLMN List information element Table 10.5.13/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : PLMN List information element

3GPP TS 24.008

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

CT WG1

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

10.5.1.13

P.5 Inter-system change between Iu mode and S1 mode

An MS is required to perform routing area updating for IMS voice termination at inter-system change from S1 mode to Iu mode and tracking area updating for IMS voice termination at inter-system change from Iu mode to S1 mode if: 1) conditions 1 and 2 of annex P.3 are fulfilled; and 2) any of the following conditions a, b and c is fulfilled: a) the IMS voice over PS session indicators received for Iu mode and S1 mode have the values - "IMS voice over PS session supported in Iu mode, but not supported in A/Gb mode" and - "IMS voice over PS session in S1 mode not supported", and the voice domain preference for UTRAN as defined in 3GPP TS 24.167[ 3GPP IMS Management Object (MO); Stage 3 ] [134] is not "CS voice only"; b) the IMS voice over PS session indicators received for Iu mode and S1 mode have the values - "IMS voice over PS session in Iu mode and A/G mode not supported" and - "IMS voice over PS session in S1 mode supported", and the voice domain preference for E-UTRAN as defined in 3GPP TS 24.167[ 3GPP IMS Management Object (MO); Stage 3 ] [134] is not "CS voice only"; or c) the IMS voice over PS session indicators received for Iu mode and S1 mode have the values - "IMS voice over PS session supported in Iu mode, but not supported in A/Gb mode" and - "IMS voice over PS session in S1 mode supported", and exactly one of the voice domain preferences for UTRAN and E-UTRAN as defined in 3GPP TS 24.167[ 3GPP IMS Management Object (MO); Stage 3 ] [134] is "CS voice only".

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

P.5

12.1.1.3 Applicability and test rules for different CA configurations and bandwidth combination sets

The performance requirement for CA UE demodulation tests with active Sidelink in Clause 12 are defined independent of CA configurations and bandwidth combination sets specified in Clause 5.6A.1. For UEs supporting different CA configurations and bandwidth combination sets, the applicability and test rules are defined in Table 12.1.1.3-1. For simplicity, CA configuration below refers to combination of CA configuration and bandwidth combination set. Table 12.1.1.3-1: Applicability and test rules for CA UE demodulation tests with active Sidelink

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

12.1.1.3

4.6.2.6 Provision of NSAG information to lower layers

The support for NSAG information by the UE and the network, respectively, is optional. The NSAG information provided by the network and stored in the UE includes a list of NSAGs each of which contains: a) an NSAG ID; b) a list of S-NSSAI(s), which are associated with the NSAG and shall be part of the configured NSSAI; NOTE 0: An alternative S-NSSAI is added to the configured NSSAI if not included yet. c) a priority value that is associated with the NSAG; and NOTE 1: The AMF can take local configuration, UE 5GMM capabilities, subscribed S-NSSAIs, the mapping information between the S-NSSAI to be replaced and the alternative S-NSSAI, HPLMN, etc. to determine the NSAG priority information for the associated NSAG to a UE. d) optionally a list of TAIs in which the NSAG is valid. If it is not provided by the network, the NSAG is valid in the PLMN or SNPN which has sent the NSAG information and its equivalent PLMN(s). NOTE 2: If the NSAG for the PLMN and its equivalent PLMN(s) have different associations with S-NSSAIs, then the AMF includes a list of TAIs in the NSAG information. The UE NAS layer shall provide the lower layers with: a) the most recent NSAG information stored in the UE (see subclause 4.6.2.2); b) the allowed NSSAI and the partially allowed NSSAI (if any) or the requested NSSAI for the purpose of network slice-based cell reselection (see 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]); and c) zero or more S-NSSAIs related to an access attempt for the purpose of network slice-based random access, when the access attempt is made by the UE in 5GMM-IDLE mode or 5GMM-CONNECTED mode with RRC inactive indication, determined as follows: i) requested NSSAI (if any), if an access attempt occurred due to the REGISTRATION REQUEST message; ii) NSSAI(s) associated with all the PDU sessions included in the Uplink data status IE (if any), PDU session status IE (if any), or Allowed PDU session status IE (if any), if an access attempt occurred due to the SERVICE REQUEST message or CONTROL PLANE SERVICE REQUEST message; iii) the S-NSSAI associated with the PDU session, if an access attempt occurred due to: - an uplink user data packet to be sent for a PDU session with suspended user-plane resources; - an UL NAS TRANSPORT which carries a 5GSM message for a PDU session associated with an S-NSSAI (if any); or - CIoT user data to be sent in a CONTROL PLANE SERVICE REQUEST message or an UL NAS TRANSPORT message; iv) no S-NSSAI, if an access attempt occurred due to: - the deregistration procedure; - the UE-initiated NAS transport procedure for sending SMS, LPP message, UPP-CMI container, SLPP message, SOR transparent container, UE policy container, UE parameters update transparent container, or a location services message; or - emergency services; or v) the allowed NSSAI (if any) and the partially allowed NSSAI (if any), if an access attempt occurred for other reason than those specified in bullets i) - iv).

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

5.16.3.5 Domain selection for UE originating sessions / calls

For UE originating calls, the 5GC capable UE performs access domain selection. The UE shall be able to take following factors into account for access domain selection decision: - The state of the UE in the IMS. The state information shall include: Registered, Unregistered. - The "IMS voice over PS session supported indication" as defined in clause 5.16.3.2. - Whether the UE is expected to behave in a "voice centric" or "data centric" way for 5GS. - UE capability of supporting IMS PS voice. - UE capability for operating in dual-registration mode with selective PDU Session transfer as defined in clause 5.17.2.3.3. - Whether 3GPP PS Data Off is active or not and whether IMS voice is included in 3GPP PS Data Off Exempt Services or not as defined in clause 5.24. NOTE 1: In this release of the specification, the exact logic of which PDU sessions are kept in which system for Dual Registration UE with selective transfer of certain PDU Sessions as defined in clause 5.17.2.3.3, is left up to UE implementation. The voice centric UE will keep the PDU Session used for IMS services to a system that supports voice over IMS. The voice centric UE can re-register with the IMS (if needed) when the IMS PDU session is transferred between 5GS and EPS. To allow for appropriate domain selection for originating voice calls, the UE shall attempt Initial Registration in 5GC. If the UE fails to use IMS for voice, e.g. due to "IMS voice over PS session supported indication" indicates voice is not supported in 5G System, the UE behaves as described below for "voice centric" for 5GS or "data centric" for 5GS: - A UE set to "voice centric" for 5GS shall always try to ensure that Voice service is possible. A voice centric 5GC capable and EPC capable UE unable to obtain voice service in 5GS shall not select a cell connected only to 5GC. By disabling capabilities to access 5GS, the UE re-selects to E-UTRAN connected to EPC first (if available). When the UE selects E-UTRAN connected to EPC, the UE performs Voice Domain Selection procedures as defined in TS 23.221[ Architectural requirements ] [23]. - A UE set to "data centric" for 5GS does not need to perform any reselection if voice services cannot be obtained. NOTE 2: The related radio capabilities in order for the voice centric UE to not reselect to NR or E-UTRA cell connected to 5GC (i.e. avoid ping pong) will be defined by RAN WGs.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.16.3.5

4.15.13.7 Member UE selection assistance information unsubscribe procedure

This clause describes the procedure that an AF decides to unsubscribe the previous subscription for Member UE selection assistance information in NEF. Figure 4.15.13.7-1: Member UE selection assistance information unsubscribe procedure 1. AF deletes the previous subscription for Member UE selection assistance information by sending Nnef_MemberUESelectionAssistance_unsubscribe request including the Subscription Correlation ID. 2. NEF interacts with different 5GC network functions to delete the required information subscription for each UE in the list of target UE(s). The set of interactions between NEF and among 5GC NFs are dependent on the Member UE filtering criteria that AF subscribed in clause 4.15.13.1. 3. NEF sends a Nnef_MemberUESelectionAssistance_unsubscribe response to the AF with the operation execution result indication.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.15.13.7

9.11.2.12 Service-level-AA server address

The purpose of the Service-level-AA server address information element is to carry the address of the service level authentication and authorization server. The Service-level-AA server address information element is coded as shown in figure 9.11.2.12.1 and table 9.11.2.12.1. The Service-level-AA server address information element is a type 4 information element with minimum length of 4 octets and maximum length of 258 octets. Figure 9.11.2.12.1: Service-level-AA server address information element Table 9.11.2.12.1: Service-level-AA server address 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.2.12

4.13.3.3 MO SMS over NAS in CM-IDLE (baseline)

Figure 4.13.3.3-1: MO SMS over NAS 1. The UE performs domain selection for UE originating SMS as defined in clause 5.16.3.8 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] if SMS delivery via non 3GPP access is allowed and possible. If an UE under CM-IDLE state is going to send uplink SMS message, then UE and network perform the UE Triggered Service Request procedure firstly as defined in clause 4.2.3.2 to establish a NAS signalling connection to AMF. 2a. The UE builds the SMS message to be sent as defined in TS 23.040[ Technical realization of the Short Message Service (SMS) ] [7] (i.e. the SMS message consists of CP-DATA/RP-DATA/TPDU/SMS-SUBMIT parts). The SMS message is encapsulated in an NAS message with an indication indicating that the NAS message is for SMS transporting. The UE send the NAS message to the AMF. 2b. The AMF forwards the SMS message and SUPI to the SMSF serving the UE over N20 message by invoking Nsmsf_SMService_UplinkSMS service operation. In order to permit the SMSF to create an accurate charging record, the AMF adds the IMEISV, the current UE Location Information (ULI) of the UE as defined in clause 5.6.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] and if the UE has sent the SMS via 3GPP access, the local time zone. 2c. The SMSF invokes Namf_Communication_N1N2MessageTransfer service operation to forward SMS ack message to AMF. 2d. The AMF forwards the SMS ack message from the SMSF to the UE using downlink unit data message. 3-5. The SMSF checks the SMS management subscription data. If SMS delivery is allowed, the procedure defined in TS 23.040[ Technical realization of the Short Message Service (SMS) ] [7] or TS 23.540[ 5G System: Technical realization of Service Based Short Message Service; Stage 2 ] [84] applies. 6a-6b. The SMSF forwards the submit report to AMF by invoking Namf_Communication_N1N2MessageTransfer service operation which is forwarded to UE via Downlink NAS transport. If the SMSF knows the submit report is the last message to be transferred for UE, the SMSF shall include a last message indication in the Namf_Communication_N1N2MessageTransfer service operation so that the AMF knows no more SMS data is to be forwarded to UE. NOTE: The behaviour of AMF based on the "last message indication" is implementation specific. If the UE has more than one SMS message to send, the AMF and SMSF forwards SMS /SMS ack/submit report the same way as described in step 2a-6b. 6c-6d. When no more SMS is to be sent, UE returns a CP-ack as defined in TS 23.040[ Technical realization of the Short Message Service (SMS) ] [7] to SMSF. The AMF forwards the SMS ack message by invoking Nsmsf_SMService_UplinkSMS service operation to SMSF.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.13.3.3

7.2.1 Overview

Several scenarios require the support of very low latency and very high communications service availability. Note that this implies a very high reliability. The overall service latency depends on the delay on the radio interface, transmission within the 5G system, transmission to a server which can be outside the 5G system, and data processing. Some of these factors depend directly on the 5G system itself, whereas for others the impact can be reduced by suitable interconnections between the 5G system and services or servers outside of the 5G system, for example, to allow local hosting of the services.

3GPP TS 22.261

Service requirements for the 5G system

SA WG1

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

7.2.1

5.3.12A.2 Receiving a REGISTRATION ACCEPT message via non-3GPP access

If the UE can determine the current country and after switch on or after removal of the USIM, has not been registered or has not been attached via 3GPP access in the current country, then the UE shall store the local emergency numbers list or the extended local emergency numbers list or both, as provided by the network with an MCC matching the current country via non-3GPP access. NOTE: The UE determines, as the current country, the country in which it is located in accordance with 3GPP TS 24.502[ Access to the 3GPP 5G Core Network (5GCN) via non-3GPP access networks ] [18]. The UE shall replace a previously stored local emergency numbers list or a previously stored extended local emergency numbers list or both with a local emergency numbers list or an extended local emergency numbers list or both received in a REGISTRATION ACCEPT message via non-3GPP access, if the previously stored local emergency numbers list was also received via non-3GPP access or the previously stored extended local emergency numbers list was also received via non-3GPP access. The UE shall replace a previously stored extended local emergency numbers list with an extended local emergency numbers list received in a REGISTRATION ACCEPT message via non-3GPP access, if: - the UE is neither registered nor attached over 3GPP access; - the REGISTRATION ACCEPT message is received from a PLMN different from which the stored list was received; and - the stored indication in the EENLV field within the Extended emergency number list IE indicates "Extended Local Emergency Numbers List is valid only in the PLMN from which this IE is received". If no extended local emergency numbers list is contained in a REGISTRATION ACCEPT message received via non-3GPP access and the UE is neither registered nor attached over 3GPP access, the stored extended local emergency numbers list in the UE shall be discarded if: - the UE can determine the current country and the UE has successfully registered to a PLMN in the country and that country is different from that of the PLMN that sent the stored list; or - the REGISTRATION ACCEPT message is received from a PLMN different from which the stored list was received, and the stored indication in the EENLV field within the Extended emergency number list IE indicates "Extended Local Emergency Numbers List is valid only in the PLMN from which this IE is received".

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

5.6.3.4 Abnormal cases in the UE

The following abnormal case can be identified: a) Timer T3346 is running The UE shall not send an UPLINK NAS TRANSPORT message unless: - the UE is a UE configured to use AC11 – 15 in selected PLMN; - the UE has a PDN connection for emergency bearer services established; or - the UE is configured for dual priority and has a PDN connection established without low access priority but the timer T3346 was started in response to NAS signalling request with low access priority. The UPLINK NAS TRANSPORT message can be sent, if still necessary, when timer T3346 expires or is stopped. b) Timer T3447 is running The UE shall not send an UPLINK NAS TRANSPORT message when the UE is in EMM-CONNECTED mode after the UE attached without PDN connection, unless: - the UE is a UE configured to use AC11 – 15 in the selected PLMN; or - a network initiated signalling message has been received. The UPLINK NAS TRANSPORT message can be sent, if still necessary, when timer T3447 expires.

3GPP TS 24.301

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

CT WG1

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

5.6.3.4

– PDCP-Config

The IE PDCP-Config is used to set the configurable PDCP parameters for signalling, MBS multicast and data radio bearers. PDCP-Config information element -- ASN1START -- TAG-PDCP-CONFIG-START PDCP-Config ::= SEQUENCE { drb SEQUENCE { discardTimer ENUMERATED {ms10, ms20, ms30, ms40, ms50, ms60, ms75, ms100, ms150, ms200, ms250, ms300, ms500, ms750, ms1500, infinity} OPTIONAL, -- Cond Setup pdcp-SN-SizeUL ENUMERATED {len12bits, len18bits} OPTIONAL, -- Cond Setup1 pdcp-SN-SizeDL ENUMERATED {len12bits, len18bits} OPTIONAL, -- Cond Setup2 headerCompression CHOICE { notUsed NULL, rohc SEQUENCE { maxCID INTEGER (1..16383) DEFAULT 15, profiles SEQUENCE { profile0x0001 BOOLEAN, profile0x0002 BOOLEAN, profile0x0003 BOOLEAN, profile0x0004 BOOLEAN, profile0x0006 BOOLEAN, profile0x0101 BOOLEAN, profile0x0102 BOOLEAN, profile0x0103 BOOLEAN, profile0x0104 BOOLEAN }, drb-ContinueROHC ENUMERATED { true } OPTIONAL -- Need N }, uplinkOnlyROHC SEQUENCE { maxCID INTEGER (1..16383) DEFAULT 15, profiles SEQUENCE { profile0x0006 BOOLEAN }, drb-ContinueROHC ENUMERATED { true } OPTIONAL -- Need N }, ... }, integrityProtection ENUMERATED { enabled } OPTIONAL, -- Cond ConnectedTo5GC1 statusReportRequired ENUMERATED { true } OPTIONAL, -- Cond Rlc-AM-UM outOfOrderDelivery ENUMERATED { true } OPTIONAL -- Need R } OPTIONAL, -- Cond DRB moreThanOneRLC SEQUENCE { primaryPath SEQUENCE { cellGroup CellGroupId OPTIONAL, -- Need R logicalChannel LogicalChannelIdentity OPTIONAL -- Need R }, ul-DataSplitThreshold UL-DataSplitThreshold OPTIONAL, -- Cond SplitBearer pdcp-Duplication BOOLEAN OPTIONAL -- Need R } OPTIONAL, -- Cond MoreThanOneRLC t-Reordering ENUMERATED { ms0, ms1, ms2, ms4, ms5, ms8, ms10, ms15, ms20, ms30, ms40, ms50, ms60, ms80, ms100, ms120, ms140, ms160, ms180, ms200, ms220, ms240, ms260, ms280, ms300, ms500, ms750, ms1000, ms1250, ms1500, ms1750, ms2000, ms2250, ms2500, ms2750, ms3000, spare28, spare27, spare26, spare25, spare24, spare23, spare22, spare21, spare20, spare19, spare18, spare17, spare16, spare15, spare14, spare13, spare12, spare11, spare10, spare09, spare08, spare07, spare06, spare05, spare04, spare03, spare02, spare01 } OPTIONAL, -- Need S ..., [[ cipheringDisabled ENUMERATED {true} OPTIONAL -- Cond ConnectedTo5GC ]], [[ discardTimerExt-r16 SetupRelease { DiscardTimerExt-r16 } OPTIONAL, -- Cond DRB2 moreThanTwoRLC-DRB-r16 SEQUENCE { splitSecondaryPath-r16 LogicalChannelIdentity OPTIONAL, -- Cond SplitBearer2 duplicationState-r16 SEQUENCE (SIZE (3)) OF BOOLEAN OPTIONAL -- Need S } OPTIONAL, -- Cond MoreThanTwoRLC-DRB ethernetHeaderCompression-r16 SetupRelease { EthernetHeaderCompression-r16 } OPTIONAL -- Need M ]], [[ survivalTimeStateSupport-r17 ENUMERATED {true} OPTIONAL, -- Cond Drb-Duplication uplinkDataCompression-r17 SetupRelease { UplinkDataCompression-r17 } OPTIONAL, -- Cond Rlc-AM discardTimerExt2-r17 SetupRelease { DiscardTimerExt2-r17 } OPTIONAL, -- Need M initialRX-DELIV-r17 BIT STRING (SIZE (32)) OPTIONAL -- Cond MRB-Initialization ]], [[ pdu-SetDiscard-r18 ENUMERATED {true} OPTIONAL, -- Need R discardTimerForLowImportance-r18 SetupRelease { DiscardTimerForLowImportance-r18 } OPTIONAL, -- Cond DRB2 primaryPathOnIndirectPath-r18 ENUMERATED {true} OPTIONAL -- Cond SplitBearerMP ]] } EthernetHeaderCompression-r16 ::= SEQUENCE { ehc-Common-r16 SEQUENCE { ehc-CID-Length-r16 ENUMERATED { bits7, bits15 }, ... }, ehc-Downlink-r16 SEQUENCE { drb-ContinueEHC-DL-r16 ENUMERATED { true } OPTIONAL, -- Need N ... } OPTIONAL, -- Need M ehc-Uplink-r16 SEQUENCE { maxCID-EHC-UL-r16 INTEGER (1..32767), drb-ContinueEHC-UL-r16 ENUMERATED { true } OPTIONAL, -- Need N ... } OPTIONAL -- Need M } UL-DataSplitThreshold ::= ENUMERATED { b0, b100, b200, b400, b800, b1600, b3200, b6400, b12800, b25600, b51200, b102400, b204800, b409600, b819200, b1228800, b1638400, b2457600, b3276800, b4096000, b4915200, b5734400, b6553600, infinity, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1} DiscardTimerExt-r16 ::= ENUMERATED {ms0dot5, ms1, ms2, ms4, ms6, ms8, spare2, spare1} DiscardTimerExt2-r17 ::= ENUMERATED {ms2000, spare3, spare2, spare1} UplinkDataCompression-r17 ::= CHOICE { newSetup SEQUENCE { bufferSize-r17 ENUMERATED {kbyte2, kbyte4, kbyte8, spare1}, dictionary-r17 ENUMERATED {sip-SDP, operator} OPTIONAL -- Need N }, drb-ContinueUDC NULL } DiscardTimerForLowImportance-r18 ::= ENUMERATED {ms0, ms2, ms4, ms6, ms8, ms10, ms12, ms14, ms18, ms22, ms26, ms30, ms40, ms50, ms75, ms100} -- TAG-PDCP-CONFIG-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

5.2.6.25.4 Nnef_TimeSynchronization_ConfigDelete operation

Service operation name: Nnef_TimeSynchronization_ConfigDelete Description: The consumer requests to delete the time synchronization configuration and deactivate the corresponding time synchronization service, for which the NEF authorizes the request and invokes the corresponding service operation with TSCTSF (clause 5.2.27.2.4). Inputs, Required: As specified in clause 5.2.27.2.4. Inputs, Optional: As specified in clause 5.2.27.2.4. Outputs, Required: Operation execution result indication and in the case of successful operation, any outputs as specified in clause 5.2.27.2.4. Outputs, Optional: As specified in clause 5.2.27.2.4.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

5.2.6.25.4

4.11.2.4.2 Session Management

4.11.2.4.2.1 PDN Connection Request Same procedure as specified in clause 4.11.1.5.4.1 is used with the following clarification: Step 6. The relevant steps of the procedure as specified in the figure above are executed with the following modification: - Additional condition to trigger Notify Request to HSS in step 15 of Figure 5.10.2-1 in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13] is that the network supports the procedures for 5GC interworking without N26 and that the UE is allowed to use 5GS in the subscription data. If the Request Type of the UE requested connectivity procedure indicates "Emergency", MME triggers Notify Request to HSS if the network supports the procedures for 5GC interworking without N26 and operator policy allows handover of emergency session to 5GS. For an unauthenticated or roaming UE, if the Request Type of the UE requested connectivity procedure indicates "Emergency", the MME shall not send any Notify Request to an HSS.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.11.2.4.2

8.4 Unknown or unforeseen message type

If a mobile station receives an RR, MM or CC message with message type not defined for the PD or not implemented by the receiver in unacknowledged mode, it shall ignore the message. If a mobile station receives an RR, MM or CC message with message type not defined for the PD or not implemented by the receiver in acknowledged mode, it shall return a status message (STATUS, MM STATUS depending on the protocol discriminator) with cause # 97 "message type non-existent or not implemented". If a mobile station receives a GMM message or SM message with message type not defined for the PD or not implemented by the receiver, it shall return a status message (GMM STATUS or SM STATUS depending on the protocol discriminator) with cause # 97 "message type non-existent or not implemented". If the network receives an MM message with message type not defined for the PD or not implemented by the receiver in a protocol state where reception of an unsolicited message with the given PD from the mobile station is not foreseen in the protocol, the network actions are implementation dependent. Otherwise, if the network receives a message with message type not defined for the PD or not implemented by the receiver, it shall ignore the message except that it should return a status message (STATUS, MM STATUS, GMM STATUS or SM STATUS depending on the protocol discriminator) with cause #97 "message type non-existent or not implemented". NOTE: A message type not defined for the PD in the given direction is regarded by the receiver as a message type not defined for the PD, see 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [20]. If the mobile station receives a message not compatible with the protocol state, the mobile station shall ignore the message except for the fact that, if an RR connection exists, it returns a status message (STATUS, MM STATUS depending on the protocol discriminator) with cause #98 "Message type not compatible with protocol state". When the message was a GMM message the GMM-STATUS message with cause #98 "Message type not compatible with protocol state" shall be returned. When the message was a SM message the SM-STATUS message with cause #98 "Message type not compatible with protocol state" shall be returned. If the network receives a message not compatible with the protocol state, the network actions are implementation dependent. NOTE: The use by GMM and SM of unacknowledged LLC may lead to messages "not compatible with the protocol state".

3GPP TS 24.008

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

CT WG1

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

8.4

8.10.1.2.6B Dual-Layer Spatial Multiplexing with altCQI-Table-1024QAM configured (User-Specific Reference Symbols)

The requirements are specified in Table 8.10.1.2.6B-2, with the addition of the parameters in Table 8.10.1.2.6B-1 and the downlink physical channel setup according to Annex C.3.2. The purpose of these tests is to verify the rank-two performance for full RB allocation upon antenna ports 7 and 8. Table 8.10.1.2.6B-1: Test Parameters for Testing CDM-multiplexed DM RS (dual layer) with multiple CSI-RS configurations Table 8.10.1.2.6B-2: Minimum performance Dual-Layer Spatial Multiplexing with altCQI-Table-1024QAM

3GPP TS 36.101

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

RAN4

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

8.10.1.2.6B

4.5 Unified access control 4.5.1 General

When the UE needs to access the 5GS, the UE not operating as an IAB-node (see 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]), not acting as a 5G ProSe layer-2 UE-to-network relay UE (see 3GPP TS 23.304[ Proximity based Services (ProSe) in the 5G System (5GS) ] [6E]) whose access attempt is triggered by a 5G ProSe layer-2 remote UE, and not acting as an NCR-MT node (see 3GPP TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27]), first performs access control checks to determine if the access is allowed. Access control checks shall be performed for the access attempts defined by the following list of events: NOTE 1: Although the UE operating as an IAB-node or as an NCR-MT node skips the access control checks, the UE operating as an IAB-node or as an NCR-MT node determines an access category and one or more access identities for each access attempt in order to derive an RRC establishment cause. In this case the NAS provides the RRC establishment cause but does not provide the access category and the one or more access identities to the lower layers. NOTE 1A: Although the UE acting as a 5G ProSe layer-2 UE-to-network relay UE skips the access control checks, the UE determines an access category and one or more access identities for each access attempt in order to derive an RRC establishment cause. a) the UE is in 5GMM-IDLE mode or 5GMM-IDLE mode with suspend indication over 3GPP access and an event that requires a transition to 5GMM-CONNECTED mode occurs; and b) the UE is in 5GMM-CONNECTED mode over 3GPP access or 5GMM-CONNECTED mode with RRC inactive indication and one of the following events occurs: 1) 5GMM receives an MO-IMS-registration-related-signalling-started indication, an MO-MMTEL-voice-call-started indication, an MO-MMTEL-video-call-started indication or an MO-SMSoIP-attempt-started indication from upper layers; 2) 5GMM receives a request from upper layers to send a mobile originated SMS over NAS unless the request triggered a service request procedure to transition the UE from 5GMM-IDLE mode or 5GMM-IDLE mode with suspend indication to 5GMM-CONNECTED mode; 3) 5GMM receives a request from upper layers to send an UL NAS TRANSPORT message for the purpose of PDU session establishment unless the request triggered a service request procedure to transition the UE from 5GMM-IDLE mode or 5GMM-IDLE mode with suspend indication to 5GMM-CONNECTED mode; 4) 5GMM receives a request from upper layers to send an UL NAS TRANSPORT message for the purpose of PDU session modification unless the request triggered a service request procedure to transition the UE from 5GMM-IDLE mode or 5GMM-IDLE mode with suspend indication to 5GMM-CONNECTED mode; 5) 5GMM receives a request to re-establish the user-plane resources for an existing PDU session; 6) 5GMM is notified that an uplink user data packet is to be sent for a PDU session with suspended user-plane resources; 7) 5GMM receives a request from upper layers to send a mobile originated location request unless the request triggered a service request procedure to transition the UE from 5GMM-IDLE mode or 5GMM-IDLE mode with suspend indication to 5GMM-CONNECTED mode; 8) 5GMM receives a request from upper layers to send a mobile originated signalling transaction towards the PCF by sending an UL NAS TRANSPORT message including a UE policy container (see 3GPP TS 24.587[ Vehicle-to-Everything (V2X) services in 5G System (5GS); Stage 3 ] [19B] and 3GPP TS 24.554[ Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3 ] [19E]) unless the request triggered a service request procedure to transition the UE from 5GMM-IDLE mode to 5GMM-CONNECTED mode; and 9) 5GMM receives an indication from lower layers of the RAN timing synchronization status change, and decides to transition the UE from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-CONNECTED mode as specified in subclause 5.3.1.4. NOTE 2: 5GMM specific procedures initiated by NAS in 5GMM-CONNECTED mode or 5GMM-CONNECTED mode with RRC inactive indication are not subject to access control, e.g. a registration procedure after PS handover will not be prevented by access control (see subclause 5.5). NOTE 3: LPP messages, SLPP messages, or location event report messages transported in the UL NAS TRANSPORT message sent in response to a mobile terminating or network induced location request, and the corresponding access attempts are handled as MT access. NOTE 4: Initiating a mobile originated signalling transaction towards the UDM by sending an UL NAS TRANSPORT message including an SOR transparent container is not supported. Therefore, access control for these cases has not been specified. When the NAS detects one of the above events, the NAS needs to perform the mapping of the kind of request to one or more access identities and one access category and lower layers will perform access barring checks for that request based on the determined access identities and access category. NOTE 5: The NAS is aware of the above events through indications provided by upper layers or through determining the need to start 5GMM procedures through normal NAS behaviour, or both. To determine the access identities and the access category for a request, the NAS checks the reason for access, types of service requested and profile of the UE including UE configurations, against a set of access identities and access categories defined in 3GPP TS 22.261[ Service requirements for the 5G system ] [3], namely: a) a set of standardized access identities; b) a set of standardized access categories; and c) a set of operator-defined access categories, if available. For the purpose of determining the applicable access identities from the set of standardized access identities defined in 3GPP TS 22.261[ Service requirements for the 5G system ] [3], the NAS shall follow the requirements set out in: a) subclause 4.5.2 and the rules and actions defined in table 4.5.2.1, if the UE is not operating in SNPN access operation mode over 3GPP access; or b) subclause 4.5.2A and the rules and actions defined in table 4.5.2A.1, if the UE is operating in SNPN access operation mode over 3GPP access. In order to enable access barring checks for access attempts identified by lower layers in 5GMM-CONNECTED mode with RRC inactive indication, the UE provides the applicable access identities to lower layers. NOTE 6: When and how the NAS provides the applicable access identities to lower layers is UE implementation specific. NOTE 7: Although the UE operating as an IAB-node or as an NCR-MT node skips the access control checks, the UE provides the applicable access identities to lower layers for access attempts identified by lower layers in 5GMM-CONNECTED mode with RRC inactive indication. For the purpose of determining the applicable access category from the set of standardized access categories and operator-defined access categories defined in 3GPP TS 22.261[ Service requirements for the 5G system ] [3], the NAS shall follow the requirements set out in: a) subclause 4.5.2 and the rules and actions defined in table 4.5.2.2, if the UE is not operating in SNPN access operation mode over 3GPP access; or b) subclause 4.5.2A and the rules and actions defined in table 4.5.2A.2, if the UE is operating in SNPN access operation mode over 3GPP access.

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

6.31.2 Requirements 6.31.2.1 General

Subject to regulatory requirements or operator's policy, 3GPP system shall be able to enable a UE of a given PLMN to obtain connectivity service (e.g. voice call, mobile data service) from another PLMN for the area where a Disaster Condition applies. Subject to regulatory requirements, operator's policy or UE capabilities, the 3GPP system shall be able to support a UE, with 5G-only national roaming access to a VPLMN, to obtain 4G connectivity service (e.g. voice call, mobile data service) from that VPLMN in the area where a Disaster Condition applies. Subject to regulatory requirements or operator's policy, in case of shared RAN between participating PLMNs, the 3GPP system shall be able to support a UE of a given PLMN to obtain connectivity service (e.g. voice call, mobile data service) from another participating network when a Disaster Condition applies to the UE’s PLMN.

3GPP TS 22.261

Service requirements for the 5G system

SA WG1

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

6.31.2

O.1 A PDU Session with multiple QoS Flows for different groups

In case the UE Application sends individual copies of data to different receivers, 5GS allows UE to simultaneously send data to different groups with different QoS policy via the following: - If different groups (IP or Ethernet multicast groups) are associated to the same DNN and S-NSSAI combination used for a 5G VN group, then different QoS Flows of a single PDU Session may be used to transfer the data copy sent to different groups. Figure O.1-1 shows a PDU Session with multiple QoS Flows for different groups as an example. - Group1 (G1): a group of multicast address 1 with members UE1 and UE2 is associated with 5GVN.A group. The QoS for multicast address 1 is set to QoS1. For G1, its members, multicast address 1 and corresponding QoS1 are provisioned as part of the AF requested QoS information as described in clause 6.1.3.28 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. - Group2 (G2): a group of multicast address 2 with members UE1 and UE3 is associated with 5GVN.A group. The QoS for multicast address 2 is set to QoS2. For G2, its members, multicast address 2 and corresponding QoS2 are provisioned as part of the AF requested QoS information as described in clause 6.1.3.28 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. - During establishment or modification procedure for PDU Sessions targeting to DNN and S-NSSAI for 5GVN.A group, or upon detection of the UE joining a multicast address, the SMF and PCF can jointly use the AF requested QoS information for 5GVN.A group to set up the QoS flow in respective member's PDU Session. As a result: - There will have two QoS flows in UE1's PDU Session targeting to DNN and S-NSSAI for 5GVN.A group, one QoS flow (QoS Flow 1.1) is used to carry data destined to multicast address 1 with QoS1, the other one (QoS Flow 1.2) is used to carry data destined to multicast address 2 with QoS2. - There will have one QoS flow (QoS Flow 2) in UE2's PDU Session targeting to DNN and S-NSSAI for 5GVN.A group, this QoS flow is used to carry data destined to multicast address 1 with QoS1. - There will have one QoS flow (QoS Flow 3) in UE3's PDU Session targeting to DNN and S-NSSAI for 5GVN.A group, this QoS flow is used to carry data destined to multicast address 2 with QoS2. - UE1 sends data with multicast address 1 (MA.1) to a UPF via QoS Flow 1.1 of UE1's PDU session for 5GVN.A group. The UPF forwards the packet to UE2 as it is a member of multicast group represented by multicast address 1 via QoS Flow 2 of UE2's PDU Session for 5GVN.A group. - UE1 also sends the same data with multicast address 2 (MA.2) to the UPF via QoS Flow 1.2 of the same PDU Session for 5GVN.A group. The UPF forwards the packet to UE3 as it is a member of multicast group represented by multicast address 2 via QoS Flow 3 of UE3'sPDU Session for 5GVN.A group. Figure O.1-1: A PDU Session with multiple QoS Flows for different groups

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

O.1

12.7.1 Network Identifier (NID)

A Stand-Alone Non-Public Network (SNPN) is identified by a combination of PLMN-Identifier (see clause 12.1) and Network Identifier (NID) (see 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [119] clause 5.30.2). The NID shall consist of 11 hexadecimal digits, one digit for representing an assignment mode and 10 digits for a NID value, as shown in figure 12.7.1-1. Figure 12.7.1-1: Network Identifier (NID) The NID can be assigned using the following assignment models: a) Self-assignment: NIDs are chosen individually by SNPNs at deployment time; this assignment model is encoded by setting the assignment mode to value 1. b) Coordinated assignment: NIDs are assigned using one of the following two options: - option 1: the NID assigned such that it is globally unique independent of the PLMN ID used. Option 1 of this assignment model is encoded by setting the assignment mode to value 0. - option 2: the NID assigned such that the combination of the NID and the PLMN ID is globally unique. Option 2 of this assignment model is encoded by setting the assignment mode to value 2. The self-assignment NID model should not be used, if UE accesses SNPN using e.g. credentials from Credentials Holder via AAA Server, as specified in clause 5.30.2.1 in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [119]. Other Assignment mode values are spare, for future use.

3GPP TS 23.003

Numbering, addressing and identification

CT WG4

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

12.7.1

8.5.1.2.3 Minimum Requirement 2 Tx Antenna Port (demodulation subframe overlaps with aggressor cell ABS)

For the parameters specified in Table 8.5.1-1 and Table 8.5.1.2.3-1, the average probability of a miss-detecting ACK for NACK (Pm-an) shall be below the specified value in Table 8.5.1.2.3-2. The downlink physical setup is in accordance with Annex C.3.2 and Annex C.3.3. In Table 8.5.1.2.3-1, Cell 1 is the serving cell, and Cell 2 is the aggressor cell. The downlink physical channel setup for Cell 1 is according to Annex C.3.2 and for Cell 2 is according to Annex C.3.3, respectively. Table 8.5.1.2.3-1: Test Parameters for PHICH Table 8.5.1.2.3-2: Minimum performance PHICH

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

6.41.1 Description

Providing access to local services refers to the capability to provide access to a hosting network and a set of services offered by the hosting network provider, and 3rd party service providers including other network operators and 3rd party application providers. The services can be localized (i.e. provided at specific/limited area) and can be bounded in time. The user can become aware of the available access to local services, and the process to gain and terminate access to the hosting network and local services. This process should be efficient, and convenient from a user experience standpoint. Providing access to local services creates new opportunities for users and service providers. For example, access can be provided in areas where there is no coverage provided by other networks (for example, on a fairground established far from other infrastructure), or the access and local services can be established as needed (on a short-term basis), without the need for long term business relationships, permanently installed equipment, etc. The type of local services and access for localized services via a hosting network can be promoted and arranged through different channels. Principally the service providers (e.g., brick and mortar businesses, entertainment venues, construction contractors, first responder agencies, etc.) will provide information and proper incentive or instructions to potential users so that they will seek to access the local services via hosting networks.

3GPP TS 22.261

Service requirements for the 5G system

SA WG1

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

6.41.1

10.1 Overview

Within the Layer 3 protocols defined in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] , every message is a standard L3 message as defined in 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [20]. This means that the message consists of the following parts: a) protocol discriminator; b) transaction identifier; c) message type; d) other information elements, as required. This organization is illustrated in the example shown in figure 10.1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] General message organization example Unless specified otherwise in the message descriptions of clause 9, a particular information element shall not be present more than once in a given message. The term "default" implies that the value defined shall be used in the absence of any assignment, or that this value allows negotiation of alternative values in between the two peer entities. When a field extends over more than one octet, the order of bit values progressively decreases as the octet number increases. The least significant bit of the field is represented by the lowest numbered bit of the highest numbered octet of the field.

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

8.1.2.2A Definition of dual connectivity capability

The definition with respect to dual connectivity capabilities for configurations with 2CCs is given as in Table 8.1.2.2A-1. The definition with respect to dual connectivity capabilities for configurations with 3CCs is given as in Table 8.1.2.2A-3. Table 8.1.2.2A-1: Definition of dual connectivity capability with 2DL CCs The supported testable dual connectivity bandwidth combinations for 2CCs for each dual connectivity capability are listed in Table 8.1.2.2A-2. Table 8.1.2.2A-2: Supported testable dual connectivity bandwidth combinations for different dual connectivitys capability with 2DL CCs Table 8.1.2.2A-3: Definition of dual connectivity capability with 3DL CCs The supported testable dual connectivity bandwidth combinations for 3CCs for each dual connectivity capability are listed in Table 8.1.2.2A-4. Table 8.1.2.2A-4: Supported testable dual connectivity bandwidth combinations for different dual connectivitys capability with 3DL 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.1.2.2A

6.3.3.2 SMF Provisioning of available UPF(s)

SMF may be locally configured with the information about the available UPFs, e.g. by OA&M system when UPF is instantiated or removed. NOTE 1: UPF information can be updated e.g. by OA&M system any time after the initial provisioning, or UPF itself updates its information to the SMF any time after the node level interaction is established. The UPF selection functionality in the SMF may optionally utilize the NRF to discover UPF instance(s). In this case, the SMF issues a request to the NRF that may include following parameters: DNN, S-NSSAI, SMF Area Identity, the requested functionalities and capabilities (e.g. ATSSS steering capabilities, functionality associated with high data rate low latency service etc.). In its answer, the NRF provides the NF profile(s) that include(s) the IP address(es) or the FQDN of the N4 interface of corresponding UPF instance(s) to the SMF. UPFs may be associated with an SMF Area Identity in the NRF. This allows limiting the SMF provisioning of UPF(s) using NRF to those UPF(s) associated with a certain SMF Area Identity. This can e.g. be used in the case that an SMF is only allowed to control UPF(s) configured in NRF as belonging to a certain SMF Area Identity. The NRF may be configured by OAM with information on the available UPF(s) or the UPF instance(s) may register its/their NF profile(s) in the NRF. This is further defined in clause 4.17 of TS 23.502[ Procedures for the 5G System (5GS) ] [3].

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

6.3.3.2

5.3.4.3 Radio Resource Management functions 5.3.4.3.1 General

To support radio resource management in NG-RAN the AMF provides the parameter 'Index to RAT/Frequency Selection Priority' (RFSP Index) to NG-RAN across N2. The RFSP Index is mapped by the RAN to locally defined configuration in order to apply specific RRM strategies, taking into account any available information in RAN. The RFSP Index is UE specific and applies to all the Radio Bearers. Examples of how this parameter may be used by the RAN: - to derive UE specific cell reselection priorities to control idle mode camping. - to decide on redirecting active mode UEs to different frequency layers or RATs (e.g. see clause 5.3.4.3.2). The HPLMN may set the RFSP Index taking into account the Subscribed S-NSSAIs. The AMF receives the subscribed RFSP Index from the UDM (e.g. during the Registration procedure). For non-roaming subscribers, the AMF chooses the RFSP Index in use according to one of the following procedures, depending on operator's configuration: - the RFSP Index in use is identical to the subscribed RFSP Index, or - the AMF chooses the RFSP Index in use based on the subscribed RFSP Index, the locally configured operator's policies, the Allowed NSSAI and any Partially Allowed NSSAI, S-NSSAI(s) rejected partially in the RA, Rejected S-NSSAI(s) for the RA, Pending NSSAI and the UE related context information available at the AMF, including UE's usage setting, if received during Registration procedures (see clause TS 23.502[ Procedures for the 5G System (5GS) ] [3]). NOTE 1: One example of how the AMF can use the "UE's usage setting," is to select an RFSP value that enforces idle mode camping on E-UTRA for a UE acting in a "Voice centric" way, in the case voice over NR is not supported in the specific Registration Area and it contains NR cells. The AMF may report to the PCF the subscribed RFSP Index received from the UDM for further evaluation as described in clause 6.1.2.1 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. When receiving the authorized RFSP Index from the PCF, the AMF shall apply the authorized RFSP Index instead of the subscribed RFSP Index for choosing the RFSP index in use (as described above). For roaming subscribers, the AMF may choose the RFSP Index in use based on the visited network policy, but can take input from the HPLMN into account (e.g. an RFSP Index value pre-configured per HPLMN, or a single RFSP Index value to be used for all roamers independent of the HPLMN). If the AMF receives authorized RFSP Index value from the V-PCF, the AMF chooses the RFSP index in use based on the authorized RFSP Index value. NOTE 2: The PCF can provide validity time together with the authorized RFSP Index indicating a change in priority from 5G access to E-UTRAN access as specified in clause 5.17.2.2. The RFSP Index in use is also forwarded from source to target NG-RAN node when Xn or N2 is used for intra-NG-RAN handover. The AMF stores the subscribed RFSP Index value received and the RFSP Index value in use. During the Registration procedure, the AMF may update the RFSP Index value in use (e.g. the AMF may need to update the RFSP Index value in use if the UE related context information in the AMF has changed). When the RFSP Index value in use is changed, the AMF immediately provides the updated RFSP Index value in use to NG-RAN node by modifying an existing UE context or by establishing a new UE context in RAN or by being configured to include the updated RFSP Index value in use in the NGAP DOWNLINK NAS TRANSPORT message if the user plane establishment is not needed. During inter-AMF mobility procedures, the source AMF forwards both RFSP Index values to the target AMF. The target AMF may replace the received RFSP Index value in use with a new RFSP Index value in use that is based on the operator's policies and the UE related context information available at the target AMF. In order to enable UE idle mode mobility control and priority-based reselection mechanism considering availability of Network Slices at the network and the Network Slices allowed for a UE, an RFSP is derived as described in clause 5.3.4.3, considering also the Allowed NSSAI and any Partially Allowed NSSAI for the UE. A UE supporting NSAG (see clause 5.15.14) may be configured, for some of the S-NSSAIs in the configured NSSAI, with NSAGs it can use as described in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27], TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [50], TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [28], TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [143], TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47] and as described in clause 5.3.4.3.4.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.3.4.3

5.4.10 Support for identification and restriction of using NR satellite access

Support for NR satellite access is specified in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27]. Editor's note: TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27] not yet updated by RAN groups. The AMF determines the RAT Type for NR satellite access, i.e. NR(LEO), NR(MEO), NR(GEO) and NR(OTHERSAT). When the UE is accessing NR using satellite access, an indication is provided in N2 interface indicating the type of NR satellite access, as defined in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [34]. Editor's note: Further details on what type of satellite platforms OTHERSAT includes is FFS and to be aligned with RAN WG3. The serving PLMN can enforce mobility restrictions for NR satellite access as specified in clause 5.3.4.1. In order to enable efficient enforcement of Mobility Restrictions, cells of each NR satellite RAT Type (NR(LEO), NR(MEO), NR(GEO) or NR(OTHERSAT)) need to be deployed in TAs different from TAs for other NR satellite RAT Types as well as different from TAs supporting terrestrial access RAT Types. The AMF may initiate deregistration of the UE when an N2 UE Context Release Request is received with cause value indicating that the UE is not in PLMN serving area, as specified in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [34].

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.4.10

9.9.1.3.1 FDD

The following requirements apply to UE Category ≥5. For the parameters specified in table 9.9.1.3.1-1, and using the downlink physical channels specified in tables C.3.2-1 and C.3.2-2, the reported offset level of the wideband spatial differential CQI for codeword #1 (Table 7.2-2 in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [6]) shall be used to determine the wideband CQI index for codeword #1 as wideband CQI1 = wideband CQI0 – Codeword 1 offset level The wideband CQI1 shall be within the set {median CQI1 -1, median CQI1, median CQI1 +1} for more than 90% of the time, where the resulting wideband values CQI1 shall be used to determine the median CQI values for codeword #1. For both codewords #0 and #1, the PDSCH BLER using the transport format indicated by the respective median CQI0 – 1 and median CQI1 – 1 shall be less than or equal to 0.1. Furthermore, for both codewords #0 and #1, the PDSCH BLER using the transport format indicated by the respective median CQI0 + 1 and median CQI1 + 1 shall be greater than or equal to 0.1. Table 9.9.1.3.1-1: PUCCH 1-1 static test (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.9.1.3.1

19.4.2.3 Tracking Area Identity (TAI)

The Tracking Area Identity (TAI) consists of a Mobile Country Code (MCC), Mobile Network Code (MNC), and Tracking Area Code (TAC). It is composed as shown in figure 19.4.2.3.1. Figure 19.4.2.3.1: Structure of the Tracking Area Identity (TAI) The TAI is composed of the following elements: - Mobile Country Code (MCC) identifies the country in which the PLMN is located. The value of the MCC is the same as the three digit MCC contained in the IMSI; - Mobile Network Code (MNC) is a code identifying the PLMN in that country. The value of the MNC is the same as the two or three digit MNC contained in the IMSI; - Tracking Area Code (TAC) is a fixed length code (of 2 octets) identifying a Tracking Area within a PLMN. This part of the tracking area identification shall be coded using a full hexadecimal representation. The following are reserved hexadecimal values of the TAC: - 0000, and - FFFE. NOTE: The above reserved values are used in some special cases when no valid TAI exists in the MS (see 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [90] for more information). A subdomain name can be derived from the TAI. This shall be done by adding the label "tac" to the beginning of the Home Network Realm/Domain (see clause 19.2) and encoding the TAC as a sub-domain. This is called the TAI FQDN.. The TAI FQDN shall be constructed as follows: tac-lb<TAC-low-byte>.tac-hb<TAC-high-byte>.tac.epc.mnc<MNC>.mcc<MCC>.3gppnetwork.org The TAC is a 16-bit integer. The <TAC-high-byte> is the hexadecimal string of the most significant byte in the TAC and the <TAC-low-byte > is the hexadecimal string of the least significant byte. If there are less than 2 significant digits in <TAC-high-byte> or <TAC-low-byte >, "0" digit(s) shall be inserted at the left side to fill the 2 digit coding.

3GPP TS 23.003

Numbering, addressing and identification

CT WG4

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

19.4.2.3

28.12 NF Set Identifier (NF Set ID)

A NF Set Identifier is a globally unique identifier of a set of equivalent and interchangeable CP NFs from a given network that provide distribution, redundancy and scalability (see clause 5.21.3 of 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [119]). An NF Set Identifier shall be constructed from the MCC, MNC, NID (for SNPN), NF type and a Set ID. A NF Set Identifier shall be formatted as the following string: set<Set ID>.<nftype>set.5gc.mnc<MNC>.mcc<MCC> for a NF Set in a PLMN, or set<Set ID>.<nftype>set.5gc.nid<NID>.mnc<MNC>.mcc<MCC> for a NF Set in a SNPN. where: - the <MCC> and <MNC> shall identify the PLMN of the NF Set and shall be encoded as follows: - <MCC> = 3 digits - <MNC> = 3 digits If there are only 2 significant digits in the MNC, one "0" digit shall be inserted at the left side to fill the 3 digits coding of MNC. - the Network Identifier (NID) shall be encoded as hexadecimal digits as specified in clause 12.7. - the <NFType> shall identify the NF type of the NFs within the NF set and shall be encoded as a value of Table 6.1.6.3.3-1 of 3GPP TS 29.510[ 5G System; Network function repository services; Stage 3 ] [130] but with lower case characters; - the Set ID shall be a NF type specific Set ID within the PLMN, chosen by the operator, that shall consist of alphabetic characters (A-Z and a-z), digits (0-9) and/or the hyphen (-) and that shall end with either an alphabetic character or a digit; - the case of alphabetic characters is not significant (i.e. two NF Set IDs with the same characters but using different lower and upper cases identify the same NF Set). For an AMF set, the Set ID shall be set to "<AMF Set ID>-region<AMF Region ID>", with the AMF Region ID and AMF Set ID encoded as defined in 3GPP TS 29.571[ 5G System; Common Data Types for Service Based Interfaces; Stage 3 ] [129]. EXAMPLE 1: setxyz.smfset.5gc.mnc012.mcc345 EXAMPLE 2: set12.pcfset.5gc.mnc012.mcc345 EXAMPLE 3: set001-region48.amfset.5gc.mnc012.mcc345 (for AMF Region 48 (hexadecimal) and AMF Set 1) EXAMPLE 4: setxyz.smfset.5gc.nid000007ed9d5.mnc012.mcc345 for a SNPN with the NID 000007ed9d5 (hexadecimal). NOTE 1: If needed, an FQDN can be derived from a given NF Set ID by appending the ".3gppnetwork.org" domain to the NF Set ID, see e.g. SMF Set FQDN in clause 28.3.2.9. For NFs whose NF type contains an underscore and for which an FQDN needs to be derived, the underscore is replaced by an hyphen in the corresponding label of the FQDN. As an exception, the AMF Set FQDN defined in clause 28.3.2.7 is not derived by merely appending the ".3gppnetwork.org" domain to the NF Set ID of an AMF set defined in this clause. NF Instances of an NF Set are equivalent and share the same MCC, MNC, NID (for SNPN), NF type and NF Set ID. In earlier versions of this specification, the Set ID of an AMF Set was defined to be set to the string "<AMF Set ID>.region<AMF Region ID>". For backward compatibility with AMF implementations complying with these earlier versions of the specifications, AMF peers' implementations shall: - support receiving such a former encoding of an AMF Set ID in 3GPP custom HTTP headers (e.g. 3gpp-Sbi-Binding header or 3gpp-Sbi-Producer header) and shall interpret it the same as if they receive these headers with the AMF Set format defined in the current version of the specification; and - use the amf-region-id and the amf-set-id query parameters when they need to discover the AMF profiles of the AMF set registered at the NRF, when receiving a binding header with such a former encoding of the AMF Set ID. NOTE 2: The NF Set ID format for an AMF set defined in earlier versions of the specification cannot be encoded in JSON attributes defined with the NfSetId data type of 3GPP TS 29.571[ 5G System; Common Data Types for Service Based Interfaces; Stage 3 ] [129] which does not allow to encode a period ".". Accordingly, any such attribute encodes the Set ID of an AMF set as defined above (i.e. <AMF Set ID>-region<AMF Region ID>").

3GPP TS 23.003

Numbering, addressing and identification

CT WG4

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

28.12

Annex E (Normative): TWAN mapping table between GTPv2 S2a Cause and non-3GPP access Cause values

The TWAN initiates session establishment requests or mobility management requests towards the PGW. If this operation is not successful, there are several possible cause codes, which need to be mapped to the appropriate cause codes over non-3GPP access to the UE. The TWAN should map these cause codes as defined in Table E.1, Table E.2, Table E.3 and Table E.4. Table E.1: Mapping from GTPv2 S2a to non-3GPP access Cause values – Rejection indication from PGW Table E.2: Mapping from GTPv2 S2a to non-3GPP access Cause values – Acceptance indication from PGW Table E.3: Mapping from GTPv2 S2a to WLCP Cause values – Indication in request from PGW Table E.4: Mapping from WLCP to GTP Cause values – Rejection indication from TWAN

3GPP TS 29.274

3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3

CT WG4

3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network

Annex

A.3 New QoS Flow with Explicit RRC Signalling

The following figure shows an example message flow when explicit RRC signalling is used for a new QoS flow. In this example, the gNB receives from UPF a first downlink packet associated with a QFI, for which the QoS parameters are already known from the PDU session establishment, but for which there is no association to any DRB yet in AS. Figure A.3-1: DL data with new QFI sent over existing DRB 0. PDU session and DRB(s) have been already established. 1. gNB receives a downlink packet with a new QFI from UPF. 2. gNB decides to send the new QoS flow over an existing DRB using explicit RRC signalling for updating the AS mapping rules. 3. gNB sends an RRCReconfiguration message to UE with the new QFI to DRB mapping rule. gNB may also decide to update the DRB configuration if required to meet the QoS requirements for the new QoS Flow. 4. UE updates the QFI to DRB mapping rules and configuration (if received). 5. UE sends an RRCReconfigurationComplete message to gNB. 6. User Plane Data for the new QoS flow can then be exchanged between UE and gNB over the DRB according to the updated mapping rules and between UPF and gNB over the tunnel for the PDU session.

3GPP TS 38.300

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

RAN2

3GPP Series : 38 , Radio technology beyond LTE

A.3

16a.3a.3 Server-Initiated Bearer termination

Diameter is used as the protocol between the P-GW and a Diameter server or proxy for applications (e.g. MMS) to deliver information related to the user session. However some IP applications could need to interwork with the P-GW to release the corresponding resource (e.g. terminate a particular bearer or Resource Allocation Deactivation procedures as defined in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [78]). For this purpose, the Diameter server or proxy may send a Diameter ASR along with the EPS bearer ID, if available, to identify the particular bearer to be terminated to the P-GW. The P-GW should react by deleting the corresponding bearer. If the P-GW deletes the corresponding bearer, it need not wait for the response from the S-GW or trusted non-3GPP IP access or ePDG before sending the ASA to the server. The absence of the EPS bearer ID in the Diameter ASR message indicates to the P-GW that all bearers/resources for this particular user and sharing the same user session shall be deleted. The bearer(s)/resources belonging to the same IP-CAN session are identified by the Diameter Session-Id. If a user has the same user IP address(es) for different sets of bearers towards different networks, only the bearers linked to the one identified by the Diameter Session-Id shall be deleted. The message flow in figure 25d.3 provides an example for Server-initiated Bearer Termination procedure on Sgi interface, which is applicable for GTP based S5/S8: Figure 25d.3: Server-initiated Bearer Termination with Diameter

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

16a.3a.3

21.1 Overview

The QoE Measurement Collection function enables collection of application layer measurements from the UE. The supported service types are: - QoE Measurement Collection for DASH streaming services; - QoE Measurement Collection for MTSI services; - QoE Measurement Collection for VR services. For DASH, MTSI, VR, the QoE measurement collection is supported in RRC_CONNECTED state only, unless the application data is delivered via MBS broadcast communication service. The QoE Measurement Collection function supports collection of QoE measurements for MBS communication service. The measurement collection is supported for the following two communication service types: - MBS broadcast; - MBS multicast. QoE measurement collection for application sessions delivered via MBS broadcast is supported in RRC_CONNECTED, RRC_INACTIVE, and RRC_IDLE states. QoE measurement collection for the application sessions delivered via MBS multicast is supported in RRC_CONNECTED state only. Both signalling based and management based QoE measurement collection are supported in NR SA and NR-DC. Further details of NR-DC operation can be found in TS 37.340[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 ] [21] and clause 21.7. NOTE: The naming QoE Measurement is used in NG, Xn, and interfaces between the OAM and the gNB. In the Uu interface, the naming application layer measurement is used and it is equal to QoE Measurement.

3GPP TS 38.300

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

RAN2

3GPP Series : 38 , Radio technology beyond LTE

21.1

– EphemerisInfo

The IE EphemerisInfo provides satellite ephemeris. Ephemeris may be expressed either in format of position and velocity state vector in ECEF or in format of orbital parameters in ECI. Note: The ECI and ECEF coincide at epochTime, i.e., x,y,z axis in ECEF are aligned with x,y,z axis in ECI at epochTime. EphemerisInfo information element -- ASN1START -- TAG-EPHEMERISINFO-START EphemerisInfo-r17 ::= CHOICE { positionVelocity-r17 PositionVelocity-r17, orbital-r17 Orbital-r17 } PositionVelocity-r17 ::= SEQUENCE { positionX-r17 PositionStateVector-r17, positionY-r17 PositionStateVector-r17, positionZ-r17 PositionStateVector-r17, velocityVX-r17 VelocityStateVector-r17, velocityVY-r17 VelocityStateVector-r17, velocityVZ-r17 VelocityStateVector-r17 } Orbital-r17 ::= SEQUENCE { semiMajorAxis-r17 INTEGER (0..8589934591), eccentricity-r17 INTEGER (0..1048575), periapsis-r17 INTEGER (0..268435455), longitude-r17 INTEGER (0..268435455), inclination-r17 INTEGER (-67108864..67108863), meanAnomaly-r17 INTEGER (0..268435455) } PositionStateVector-r17 ::= INTEGER (-33554432..33554431) VelocityStateVector-r17 ::= INTEGER (-131072..131071) -- TAG-EPHEMERISINFO-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

5.2.3.2.7 ATTEMPTING-TO-UPDATE-MM

The UE: - shall perform cell selection/reselection according to 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [21]; - shall be able to receive and transmit user data and signalling information; - shall initiate combined tracking area updating procedure indicating "combined TA/LA updating with IMSI attach" on the expiry of timers T3411 or T3402 or when the UE enters a tracking area not in the list of registered tracking areas and not in one of the lists of forbidden tracking areas; - shall respond to paging with IMSI or S-TMSI for the PS domain; NOTE: 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. - shall use requests for non-EPS services from CM layers to attempt to select GERAN or UTRAN radio access technology and proceed with the appropriate MM and CC specific procedures, unless T3402 is running due to receipt of an ATTACH ACCEPT or TRACKING AREA UPDATING ACCEPT message with EMM cause #22 "congestion"; - shall use requests for non-EPS services due to emergency call from CM layers to attempt to select GERAN or UTRAN radio access technology and proceed with the appropriate MM and CC specific procedures, even if T3402 is running due to receipt of an ATTACH ACCEPT or TRACKING AREA UPDATING ACCEPT message with EMM cause #22 "congestion"; and - if configured for eCall only mode as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17], shall perform the eCall inactivity procedure at expiry of timer T3444 or T3445 (see clause 5.5.4).

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

6.3.6.1 Authentication re-attempt

The serving network sets the Authentication re-attempt to "true" if the second authentication described in the following cases results in an authentication failure report: - authentication with (P-)TMSI failed in MS (reject cause 'MAC failure') and new authentication procedure (re-attempt) is taken because an IMSI obtained by the followed IDENTITY REQUEST procedure does not match to the original IMSI that linked with (P-)TMSI. - authentication failed in MS (reject cause 'GSM authentication unacceptable') and new authentication procedure (re-attempt) is taken after MSC obtains UMTS authentication vectors from HLR. - authentication failed in MS (reject cause 'synch failure') and new authentication procedure (re-attempt) is taken after MSC obtains new authentication vectors from HLR for re-synchronisation. - SRES mismatches with (P-)TMSI in VLR/SGSN and new authentication procedure (re-attempt) is taken because an IMSI obtained by the followed IDENTITY REQUEST procedure does not match to the original IMSI that linked with (P-)TMSI. Otherwise Authentication re-attempt is set to "False".

3GPP TS 33.102

3G security; Security architecture

SA WG3

3GPP Series : 33 , Security aspects

6.3.6.1

5.1.3 Random Access Preamble transmission

The random-access procedure shall be performed as follows: - set PREAMBLE_RECEIVED_TARGET_POWER to preambleInitialReceivedTargetPower + DELTA_PREAMBLE + (PREAMBLE_TRANSMISSION_COUNTER – 1) * powerRampingStep; - if the UE is a BL UE or a UE in enhanced coverage: - the PREAMBLE_RECEIVED_TARGET_POWER is set to: PREAMBLE_RECEIVED_TARGET_POWER - 10 * log10(numRepetitionPerPreambleAttempt); - if the UE is an NB-IoT UE: - for enhanced coverage level 0, the PREAMBLE_RECEIVED_TARGET_POWER is set to: PREAMBLE_RECEIVED_TARGET_POWER - 10 * log10(numRepetitionPerPreambleAttempt) - for FDD if the UE supports enhanced random access power control and PowerRampingParameters-NB-v1450 is configured by upper layers, or for TDD: - the MSG3_RECEIVED_TARGET_POWER is set to preambleInitialReceivedTargetPower + (PREAMBLE_TRANSMISSION_COUNTER_CE – 1) * powerRampingStep; - for other enhanced coverage levels: - for FDD if the UE supports enhanced random access power control and PowerRampingParameters-NB-v1450 is configured by upper layers, or for TDD; and - if the starting enhanced coverage level was enhanced coverage level 0 or enhanced coverage level 1: - if the MAC entity considers itself to be in enhanced coverage level 1 and if powerRampingStepCE1 and preambleInitialReceivedTargetPowerCE1 have been configured by upper layers: - the PREAMBLE_RECEIVED_TARGET_POWER is set to preambleInitialReceivedTargetPowerCE1 + DELTA_PREAMBLE + (PREAMBLE_TRANSMISSION_COUNTER_CE – 1) * powerRampingStepCE1 - 10 * log10(numRepetitionPerPreambleAttempt); - the MSG3_RECEIVED_TARGET_POWER is set to preambleInitialReceivedTargetPowerCE1 + (PREAMBLE_TRANSMISSION_COUNTER_CE – 1) * powerRampingStepCE1; - else: - the PREAMBLE_RECEIVED_TARGET_POWER is set to preambleInitialReceivedTargetPower + DELTA_PREAMBLE + (PREAMBLE_TRANSMISSION_COUNTER_CE – 1) * powerRampingStep - 10 * log10(numRepetitionPerPreambleAttempt); - the MSG3_RECEIVED_TARGET_POWER is set to preambleInitialReceivedTargetPower + (PREAMBLE_TRANSMISSION_COUNTER_CE – 1) * powerRampingStep; - else: - the PREAMBLE_RECEIVED_TARGET_POWER is set corresponding to the max UE output power; - if the UE is an NB-IoT UE, a BL UE or a UE in enhanced coverage: - instruct the physical layer to transmit a preamble with the number of repetitions required for preamble transmission corresponding to the selected preamble group (i.e., numRepetitionPerPreambleAttempt) using the selected PRACH corresponding to the selected enhanced coverage level, corresponding RA-RNTI, preamble index or for NB-IoT subcarrier index, and PREAMBLE_RECEIVED_TARGET_POWER. - else: - instruct the physical layer to transmit a preamble using the selected PRACH, corresponding RA-RNTI, preamble index and PREAMBLE_RECEIVED_TARGET_POWER.

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

– UE-TimersAndConstantsRemoteUE

The IE UE-TimersAndConstantsRemoteUE contains timers and constants used by the L2 U2N Remote UE in RRC_CONNECTED, RRC_INACTIVE and RRC_IDLE. UE-TimersAndConstantsRemoteUE information element -- ASN1START -- TAG-UE-TIMERSANDCONSTANTSREMOTEUE-START UE-TimersAndConstantsRemoteUE-r17 ::= SEQUENCE { t300-RemoteUE-r17 ENUMERATED {ms100, ms200, ms300, ms400, ms600, ms1000, ms1500, ms2000} OPTIONAL, -- Need S t301-RemoteUE-r17 ENUMERATED {ms100, ms200, ms300, ms400, ms600, ms1000, ms1500, ms2000} OPTIONAL, -- Need S t319-RemoteUE-r17 ENUMERATED {ms100, ms200, ms300, ms400, ms600, ms1000, ms1500, ms2000} OPTIONAL, -- Need S ... } -- TAG-UE-TIMERSANDCONSTANTSREMOTEUE-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

5.1.1.2 eNodeB - MME

Legend: - S1 Application Protocol (S1-AP): Application Layer Protocol between the eNodeB and the MME. - Stream Control Transmission Protocol (SCTP): This protocol guarantees delivery of signalling messages between MME and eNodeB (S1). SCTP is defined in RFC 4960 [35]. Figure 5.1.1.2-1: Control Plane for S1-MME Interface NOTE: Refer to TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5] for the corresponding control plane for the HeNB Subsystem - MME.

3GPP TS 23.401

General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access

SA WG2

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

5.1.1.2

G.1 Asset Tracking

Every organisation owns assets (e.g. machines, medical devices, containers, pallets, trolleys). These assets are often not stationary: they are transported all over the world by different kinds of vehicles; and the assets are also moved inside various kinds of buildings. The ownership of assets can change many times during the life-cycle of the asset as different stakeholders take possession of the assets and pass them on to other stakeholders along the supply chain and value chain. So, many stakeholders want to track their assets anytime and anywhere (indoor & outdoor) in a global and multi-modal context (e.g. sea, air, road, rail). The asset tracking topic implies more than just knowing the location of an asset. Asset tracking includes real time and/or time-stamped monitoring of several asset-related properties depending on the asset and its content (e.g. condition of the asset and changes, environmental factors – temperature, mechanical shock). The 5G system provides the capability to better support asset tracking in all its aspects in particular in term of coverage (need to support full coverage: e.g. indoor / urban / rural / harsh environments / metallic obstructions on land, sea) with the support of terrestrial and non- terrestrial network as well as use of relays when necessary and in term of energy efficiency (15 to 20 years’ lifetime of an asset tracking device without changing the battery or the UE).

3GPP TS 22.261

Service requirements for the 5G system

SA WG1

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

G.1

– IndirectPathFailureInformation

The IndirectPathFailureInformation message is used to provide information regarding indirect path failure detected by the MP remote UE. Signalling radio bearer: SRB1 RLC-SAP: AM Logical channel: DCCH Direction: UE to Network IndirectPathFailureInformation message -- ASN1START -- TAG-INDIRECTPATHFAILUREINFORMATION-START IndirectPathFailureInformation-r18 ::= SEQUENCE { criticalExtensions CHOICE { indirectPathFailureInformation-r18 IndirectPathFailureInformation-r18-IEs, criticalExtensionsFuture SEQUENCE {} } } IndirectPathFailureInformation-r18-IEs ::= SEQUENCE { failureReportIndirectPath-r18 FailureReportIndirectPath-r18 OPTIONAL, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } FailureReportIndirectPath-r18 ::= SEQUENCE { failureTypeIndirectPath-r18 ENUMERATED {t421-Expiry,sl-Failure,n3c-Failure, relayUE-Uu-RLF, ffsrelayUE-HO, relayUE-CellReselection, relayUE-Uu-RRC-Failure, indirectPathAddChangeFailure} OPTIONAL, sl-MeasResultServingRelay-r18 OCTET STRING OPTIONAL, -- Contains PC5 SL-MeasResultRelay-r17 sl-MeasResultsCandRelay-r18 OCTET STRING OPTIONAL, n3c-RelayUE-InfoList-r18 N3C-RelayUE-InfoList-r18 OPTIONAL, ... } -- TAG-INDIRECTPATHFAILUREINFORMATION-STOP -- ASN1STOP Editor's Note: FFS whether the detailed report types other than indirectPathAddChangeFailure, path failure, Uu-RLF, Uu failure, PC5-RLF can be included.

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

5.3.5.4 HARQ

Asynchronous Incremental Redundancy Hybrid ARQ is supported. The gNB schedules each uplink transmission and retransmission using the uplink grant on DCI. For operation with shared spectrum channel access, UE can also retransmit on configured grants if configured. The UE may be configured to transmit code block group based transmissions where retransmissions may be scheduled to carry a sub-set of all the code blocks of a transport block. Up to two HARQ-ACK codebooks corresponding to a priority (high/low) can be constructed simultaneously. For each HARQ-ACK codebook, more than one PUCCH for HARQ-ACK transmission within a slot is supported. Each PUCCH is limited within one sub-slot, and the sub-slot pattern is configured per HARQ-ACK codebook.

3GPP TS 38.300

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

RAN2

3GPP Series : 38 , Radio technology beyond LTE

5.3.5.4

5.2.21.2.4 Nnsacf_NSAC_NumOfPDUsUpdate service operation

Service Operation name: Nnsacf_NSAC_NumOfPDUsUpdate Description: Updates the number of PDU Sessions established on a network slice (e.g. increase or decrease). Also, if the number of PDU Sessions on the network slice is to be increased, the NSACF first checks whether the number of the PDU Sessions on that network slice has reached the maximum number of PDU Sessions per network slice. If the maximum number of PDU Sessions on the network slice has already been reached, the PDU Session Establishment procedure is rejected. Inputs, Required: S-NSSAI, UE ID, PDU Session ID, Access Type, update flag. The S-NSSAI parameter is the network slice for which the number of PDU Sessions established on a network slice is to be updated. In the LBO roaming case, the corresponding mapped S-NSSAI of the HPLMN is also included. The UE ID parameter is used by the NSACF to maintain a list of UE IDs that has established PDU sessions with the network slice. PDU Session ID parameter is used by the NSACF to maintain for each UE ID, the PDU Session ID(s) for established PDU Sessions. The Access Type parameter indicates over which access network type the PDU Session is established. In the case of MA PDU Session, one or multiple Access Types may be included for a PDU Session ID. The update flag input parameter indicates 'increase', 'decrease' or 'update' as specified in clause 4.2.11.4. Inputs, Optional: NSAC admission mode, PLMN ID. NSAC admission mode applies to inbound roamers. It is included by NF consumer to indicate applicable NSAC admission mode in VPLMN. Its values can be VPLMN NSAC admission mode, or VPLMN with HPLMN assistance NSAC admission mode. The PLMN ID is the serving PLMN of the UE. Inputs, Conditional: The SMF NSAC service area is included in a centralized NSAC architecture, if applicable. Outputs, Required: Result indication, Access Type. The Result indication parameter contains the outcome of the update and check operation in the NSACF and may indicate one of the values 'maximum number of PDU Sessions for the S-NSSAI not reached' or 'maximum number of PDU Sessions for the S-NSSAI reached'. The Access Type parameter is associated with the Result indication parameter. Outputs, Optional: Updated local maximum number of PDUs. This parameter is returned only by a primary NSACF.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

5.2.21.2.4

5.8.2.17 Data exposure via Service Based interface

The UPF may expose information by means of UPF Event Exposure service as described in TS 23.502[ Procedures for the 5G System (5GS) ] [3] clause 5.2.26.2, via a service-based interface directly. The NF consumers, which may receive UPF event notifications, are AF/NEF, TSNAF/TSCTSF and NWDAF/DCCF/MFAF. When the UPF supports the data exposure via the service based interface, it may register its NF profile to the NRF including the UPF Event Exposure services and the related Event ID(s). For data collection from UPF (see clause 4.15.4.5 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]), NF consumers do the subscription to the UPF directly or indirectly via SMF. A n NF consumer may subscribe to the UPF Event Exposure service directly only for data collected for "any UE" e.g. to collect user data usage information for NWDAF NF Load analytic (see clause 6.5 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [86]) and if the subscription is not including any of the following parameters: AoI, traffic filtering, BSSID/SSID and Application ID. To alleviate the load of UPF due to frequent event notification, the event subscription may include Reporting suggestion information. The Reporting suggestion information includes Report urgency and Reporting window information. Reporting urgency information represents whether this event report can be delay tolerant, i.e. the event report can be delayed. If the Reporting urgency information indicates "delay tolerant", the Reporting window is also provided, which defines the last valid reporting time, and UPF shall report the detected event before the last valid time. Per Reporting suggestion information UPF can concatenate several notification messages to the same notification endpoint in one notification message. The UPF may also expose UE information by means of the Nupf_GetUEPrivateIPaddrAndIdentifiers service as described in TS 23.502[ Procedures for the 5G System (5GS) ] [3] clause 5.2.26.3. An UPF which is deployed with NAPT (Network Address Port Translation) functionality may support to provide the 5GC UE IP address to NEF based on NEF request containing public IP address and port number using the Nupf_GetUEPrivateIPaddrAndIdentifiers service as described in clause 4.15.10 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] for AF specific UE ID retrieval.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.8.2.17

– SL-PRS-ResourcePool

The IE SL-PRS-ResourcePool specifies the configuration information for NR sidelink PRS dedicated resource pool. SL-PRS-ResourcePool information element -- ASN1START -- TAG-SL-PRS-RESOURCEPOOL-START SL-PRS-ResourcePool-r18 ::= SEQUENCE { sl-PRS-PSCCH-Config-r18 SetupRelease { SL-PSCCH-ConfigDedicatedSL-PRS-RP-r18} OPTIONAL, -- Need M sl-StartRB-SubchannelDedicatedSL-PRS-RP-r18 INTEGER (0..265) OPTIONAL, -- Need M sl-RB-Number-r18 INTEGER (10..275) OPTIONAL, -- Need M sl-TimeResource-r18 BIT STRING (SIZE (10..160)) OPTIONAL, -- Need M sl-PosAllowedResourceSelectionConfig-r18 ENUMERATED {c1, c2, c3} OPTIONAL, -- Need M sl-PRS-ResourceReservePeriodList-r18 SEQUENCE (SIZE (1..16)) OF SL-ReservationPeriodAllowedDedicatedSL-PRS-RP-r18 OPTIONAL, sl-PRS-ResourcesDedicatedSL-PRS-RP-r18 SEQUENCE (SIZE (1..12)) OF SL-PRS-ResourceDedicatedSL-PRS-RP-r18 OPTIONAL, -- Need M sl-PRS-PowerControl-r18 SL-PRS-PowerControl-r18 OPTIONAL, -- Need M sl-SensingWindowDedicatedSL-PRS-RP-r18 ENUMERATED {ms100, ms1100} OPTIONAL, -- Need M sl-TxPercentageDedicatedSL-PRS-RP-List-r18 SEQUENCE (SIZE (8)) OF SL-TxPercentageDedicatedSL-PRS-RP-Config-r18 OPTIONAL, -- Need M sl-SCI-basedSL-PRS-TxTriggerSCI1-B-r18 BOOLEAN OPTIONAL, -- Need M sl-NumSubchannelDedicatedSL-PRS-RP-r18 INTEGER (1..27) OPTIONAL, -- Need M sl-SubchannelSizeDedicatedSL-PRS-RP-r18 ENUMERATED {n10, n12, n15, n20, n25, n50, n75, n100} OPTIONAL, -- Need M sl-MaxNumPerReserveDedicatedSL-PRS-RP-r18 ENUMERATED {n2, n3} OPTIONAL, -- Need M sl-NumReservedBitsSCI1B-DedicatedSL-PRS-RP-r18 INTEGER (0..20) OPTIONAL, -- Need M sl-SRC-ID-LenDedicatedSL-PRS-RP-r18 ENUMERATED {n12, n24} OPTIONAL, -- Need M sl-CBR-PriorityTxConfigDedicatedSL-PRS-RP-List-r18 SEQUENCE (SIZE (1..8)) OF SL-PriorityTxConfigIndexDedicatedSL-PRS-RP-r18 OPTIONAL, -- Need M sl-TimeWindowSizeCBR-DedicatedSL-PRS-RP-r18 ENUMERATED {ms100, slot100} OPTIONAL, -- Need M sl-TimeWindowSizeCR-DedicatedSL-PRS-RP-r18 ENUMERATED {ms1000, slot1000} OPTIONAL, -- Need M sl-CBR-CommonTxDedicatedSL-PRS-RP-List-r18 SL-CBR-CommonTxDedicatedSL-PRS-RP-List-r18 OPTIONAL, -- Need M sl-PriorityThreshold-UL-URLLC-r18 INTEGER (1..9) OPTIONAL, -- Need M sl-PriorityThreshold-r18 INTEGER (1..9) OPTIONAL -- Need M } SL-PSCCH-ConfigDedicatedSL-PRS-RP-r18 ::= SEQUENCE { timeResourcePSCCH-DedicatedSL-PRS-RP-r18 ENUMERATED {n2, n3} OPTIONAL, -- Need M freqResourcePSCCH-DedicatedSL-PRS-RP-r18 ENUMERATED {n10,n12, n15, n20, n25} OPTIONAL, -- Need M ... } SL-ReservationPeriodAllowedDedicatedSL-PRS-RP-r18 ::= CHOICE { sl-ResourceReservePeriod1-r18 ENUMERATED {ms0, ms100, ms200, ms300, ms400, ms500, ms600, ms700, ms800, ms900, ms1000}, sl-ResourceReservePeriod2-r18 INTEGER (1..99) } SL-PRS-ResourceDedicatedSL-PRS-RP-r18::= SEQUENCE { sl-PRS-ResourceID-r18 INTEGER (0..11) OPTIONAL, -- Need M sl-NumberOfSymbols-r18 INTEGER (1..9) OPTIONAL, -- Need M sl-CombSize-r18 ENUMERATED{n2,n4,n6} OPTIONAL, sl-PRS-starting-symbol-r18 INTEGER (4..12) OPTIONAL, -- Need M sl-PRS-comb-offset-r18 INTEGER(1..5) OPTIONAL -- Need M } SL-PRS-PowerControl-r18::= SEQUENCE { dl-P0-SL-PRS-r18 INTEGER(-202..24) OPTIONAL, -- Need M dl-Alpha-SL-PRS-r18 ENUMERATED {alpha0, alpha04, alpha05, alpha06, alpha07, alpha08, alpha09, alpha1} OPTIONAL, -- Need S sl-P0-SL-PRS-r18 INTEGER(-202..24) OPTIONAL, -- Need S sl-Alpha-SL-PRS-r18 ENUMERATED {alpha0, alpha04, alpha05, alpha06, alpha07, alpha08, alpha09, alpha1} OPTIONAL -- Need S } SL-TxPercentageDedicatedSL-PRS-RP-Config-r18::= SEQUENCE { sl-TxPercentageDedicatedSL-PRS-RP-r18 INTEGER (1..8) OPTIONAL, -- Need M sl-Priority-DedicatedSL-PRS-RP ENUMERATED {p20, p35, p50} OPTIONAL -- Need M } SL-PriorityTxConfigIndexDedicatedSL-PRS-RP-r18 ::= SEQUENCE { sl-PriorityThresholdDedicatedSL-PRS-RP-r18 INTEGER (1..8) OPTIONAL, -- Need M sl-DefaultTxConfigIndexDedicatedSL-PRS-RP-r18 INTEGER (0..maxCBR-LevelDedSL-PRS-1-r18) OPTIONAL, -- Need M sl-CBR-ConfigIndexDedicatedSL-PRS-RP-r18 INTEGER (0..maxCBR-ConfigDedSL-PRS-1-r18) OPTIONAL, -- Need M sl-PRS-TxConfigIndexList-r18 SEQUENCE (SIZE (1.. maxCBR-LevelDedSL-PRS-1-r18)) OF SL-PRS-TxConfigIndex-r18 OPTIONAL -- Need M } SL-PRS-TxConfigIndex-r18 ::= INTEGER (0.. maxNrofSL-PRS-TxConfig-r18) -- TAG-SL-PRS-RESOURCEPOOL-STOP -- ASN1STOP – SL-PSBCH-Config The IE SL-PSBCH-Config indicates PSBCH transmission parameters on each sidelink bandwidth part. SL-PSBCH-Config information element -- ASN1START -- TAG-SL-PSBCH-CONFIG-START SL-PSBCH-Config-r16 ::= SEQUENCE { dl-P0-PSBCH-r16 INTEGER (-16..15) OPTIONAL, -- Need M dl-Alpha-PSBCH-r16 ENUMERATED {alpha0, alpha04, alpha05, alpha06, alpha07, alpha08, alpha09, alpha1} OPTIONAL, -- Need M ..., [[ dl-P0-PSBCH-r17 INTEGER (-202..24) OPTIONAL -- Need M ]] } -- TAG-SL-PSBCH-CONFIG-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

– SL-PDCP-Config

The IE SL-PDCP-Config is used to set the configurable PDCP parameters for a sidelink radio bearer. SL-PDCP-Config information element -- ASN1START -- TAG-SL-PDCP-CONFIG-START SL-PDCP-Config-r16 ::= SEQUENCE { sl-DiscardTimer-r16 ENUMERATED {ms3, ms10, ms20, ms25, ms30, ms40, ms50, ms60, ms75, ms100, ms150, ms200, ms250, ms300, ms500, ms750, ms1500, infinity} OPTIONAL, -- Cond Setup sl-PDCP-SN-Size-r16 ENUMERATED {len12bits, len18bits} OPTIONAL, -- Cond Setup2 sl-OutOfOrderDelivery ENUMERATED { true } OPTIONAL, -- Need R ... } -- TAG-SL-PDCP-CONFIG-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

9.5.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 PSDCH. 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. Resource elements in the last SC-FDMA symbol within a subframe shall be counted in the mapping process but not transmitted. The set of physical resource blocks that shall be used are given by [4, clause 14.3.1].

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

– SL-CBR-CommonTxConfigList

The IE SL-CBR-CommonTxConfigList indicates the list of PSSCH transmission parameters (such as MCS, sub-channel number, retransmission number, CR limit) in sl-CBR-PSSCH-TxConfigList, and the list of CBR ranges in sl-CBR-RangeConfigList, to configure congestion control to the UE for sidelink communication. SL-CBR-CommonTxConfigList information element -- ASN1START -- TAG-SL-CBR-COMMONTXCONFIGLIST-START SL-CBR-CommonTxConfigList-r16 ::= SEQUENCE { sl-CBR-RangeConfigList-r16 SEQUENCE (SIZE (1..maxCBR-Config-r16)) OF SL-CBR-LevelsConfig-r16 OPTIONAL, -- Need M sl-CBR-PSSCH-TxConfigList-r16 SEQUENCE (SIZE (1.. maxTxConfig-r16)) OF SL-CBR-PSSCH-TxConfig-r16 OPTIONAL -- Need M } SL-CBR-LevelsConfig-r16 ::= SEQUENCE (SIZE (1..maxCBR-Level-r16)) OF SL-CBR-r16 SL-CBR-PSSCH-TxConfig-r16 ::= SEQUENCE { sl-CR-Limit-r16 INTEGER(0..10000) OPTIONAL, -- Need M sl-TxParameters-r16 SL-PSSCH-TxParameters-r16 OPTIONAL -- Need M } SL-CBR-r16 ::= INTEGER (0..100) -- TAG-SL-CBR-COMMONTXCONFIGLIST-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

7.10.1G Minimum requirements for V2X Communication

Receiver image rejection is a measure of a receiver's ability to receive the E-UTRA V2X signal on one component carrier while it is also configured to receive another aggregated carrier. Receiver image rejection ratio is the ratio of the wanted received power on a sub-carrier being measured to the unwanted image power received on the same sub-carrier when both sub-carriers are received with equal power at the UE antenna connector. For intra-band contiguous multi-carrier operation, the UE shall fulfil the minimum requirement specified in Table 7.10.1G-1 for all values of aggregated input signal. Table 7.10.1G-1: Receiver image rejection

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.10.1G

5.3.10.4.2 NAS Security Mode Command procedure

The MME uses the NAS Security Mode Command (SMC) procedure to establish a NAS security association between the UE and MME, in order to protect the further NAS signalling messages. This procedure is also used to make changes in the security association, e.g. to change the security algorithm. Figure 5.3.10.4.2-1: NAS Security Mode Command Procedure 1. The MME sends NAS Security Mode Command (Selected NAS algorithms, eKSI, ME Identity request, UE Security Capability) message to the UE. ME identity request may be included when NAS SMC is combined with ME Identity retrieval (see clause 5.3.10.5). 2. The UE responds NAS with Security Mode Complete (NAS-MAC, ME Identity) message. The UE includes the ME Identity if it was requested in step 1. NOTE: The NAS Security Mode Command procedure is typically executed as part of the Attach procedure (see clause 5.3.2.1) in advance of, or in combination with, executing the ME Identity Check procedure (see clause 5.3.10.5) and in the TAU procedure (see clauses 5.3.3.1 and 5.3.3.2). More details of the procedure are described in TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [41].

3GPP TS 23.401

General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access

SA WG2

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

5.3.10.4.2

6.8.1.1.1 Transition from RM-REGISTERED to RM-DEREGISTERED

There are different reasons for transition to the RM-DEREGISTERED state. If a NAS messages leads to state transition to RM-DEREGISTERED, it shall be security protected by the current 5G NAS security context (mapped or native), if such exists in the UE or the AMF. NOTE: The present document only considers the states RM-DEREGISTERED and RM REGISTERED and transitions between these two states. Other documents define additional RM states (see, e.g. 5GMM states in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [35]). On transitioning to RM-DEREGISTERED, the UE and AMF shall do the following: 1. If they have a full non-current native 5G NAS security context and a current mapped 5G NAS security context, then they shall make the non-current native 5G NAS security context the current one. 2. They shall delete any mapped or partial 5G NAS security contexts they hold. Handling of the remaining security parameters for each of these cases are given below: 1. Registration reject: All remaining security parameters shall be removed from the UE and AMF 2. Deregistration: a. UE-initiated i. If the reason is switch off then all the remaining security parameters shall be removed from the UE and AMF with the exception of the current native 5G NAS security context (as in clause 6.1.1), which should remain stored in the AMF and UE. ii. If the reason is not switch off then AMF and UE shall keep all the remaining security parameters. b. AMF-initiated i. Explicit: all the remaining security parameters shall be kept in the UE and AMF if the de-registration type is "re-registration required". ii. Implicit: all the remaining security parameters shall be kept in the UE and AMF. c. UDM/ARPF-initiated: If the message is "subscription withdrawn" then all the remaining security parameters shall be removed from the UE and AMF. 3. Registration reject: There are various reasons for Registration reject. The action to be taken shall be as given in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [35]. Storage of the full native 5G NAS security context including the pair(s) of distinct NAS COUNT values associated with each access together with respective NAS connection identifier, excluding the UE security capabilities and the keys KNASint and KNASenc, in the UE when the UE transitions to RM-DEREGISTERED state is done as follows: a) If the ME does not have a full native 5G NAS security context in volatile memory, any existing native 5G NAS security context stored on the USIM or in non-volatile memory of the ME shall be marked as invalid. b) If the USIM supports RM parameters storage, then the ME shall store the full native 5G NAS security context parameters on the USIM (except for KNASint and KNASenc), mark the native 5G NAS security context on the USIM as valid, and not keep any native 5G NAS security context in non-volatile ME memory. c) If the USIM does not support RM parameters storage, then the ME shall store the full native 5G NAS security context (except for KNASint and KNASenc) in a non-volatile part of its memory and mark the native 5G NAS security context in its non-volatile memory as valid. d) For the case that the AMF or the UE enter RM-DEREGISTERED state without using any of the above procedures, the handling of the remaining security parameters shall be as specified in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [35].

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

6.8.1.1.1

4.4.3.3 Integrity protection and verification

The sender shall use its locally stored NAS COUNT as input to the integrity protection algorithm. The receiver shall use the NAS sequence number included in the received message and an estimate for the NAS overflow counter as defined in subclause 4.4.3.1 to form the NAS COUNT input to the integrity verification algorithm. The algorithm to calculate the integrity protection information is specified in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24], and in case of the: a) SECURITY PROTECTED 5GS NAS MESSAGE message, the integrity protection shall include octet 7 to n, i.e. the Sequence number IE and the NAS message IE. b) Intra N1 mode NAS transparent container IE and S1 mode to N1 mode NAS transparent container IE, the integrity protection shall include all octets of the value part of the IE starting from octet 7. NOTE: To ensure backward compatibility, the UE uses all octets starting from octet 7 in the received NAS transparent container for the purpose of integrity check of the NAS transparent container irrespective of the release/version it supports. After a successful integrity check, the UE can ignore the octets which are not specified in the release/version which the UE supports. In addition to the data that is to be integrity protected, the BEARER ID, DIRECTION bit, NAS COUNT and 5G NAS integrity key are input to the integrity protection algorithm. These parameters are described in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. After successful integrity protection validation, the receiver shall update its corresponding locally stored NAS COUNT with the value of the estimated NAS COUNT for this NAS message. Integrity verification is not applicable when 5G-IA0 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

4.4.3.3