Datasets:

Exploration-Lab

/

MM-TelecoBench

like 0

Follow

Exploration Lab 61

9.6.1.4 TDD-FDD CA with TDD PCell

The following requirements apply to UE Category ≥5. For TDD-FDD CA with TDD PCell with 2 DL CC, for the parameters specified in Table 9.6.1.4-1 and Table 9.6.1.4-2, and using the downlink physical channels specified in tables C.3.2-1 and C.3.2-2 on each cell, the difference between the wideband CQI indices of PCell and SCell reported shall be such that wideband CQIPCell – wideband CQISCell ≥ 2 for more than 90% of the time. Table 9.6.1.4-1: Parameters for PUCCH 1-0 static test on multiple cells (TDD-FDD CA with TDD PCell, 2 DL CA) Table 9.6.1.4-2: PUCCH 1-0 static test (TDD-FDD CA with TDD PCell, 2 DL CA) The following requirements for 3DL CA apply to UE Category ≥5. For TDD-FDD CA with TDD PCell with 3 DL CC, for the parameters specified in Table 9.6.1.4-3 and Table 9.6.1.4-4, and using the downlink physical channels specified in tables C.3.2-1 and C.3.2-2 on each cell, the difference between the wideband CQI indices of PCell and SCell1 reported, and the difference between the wideband CQI indices of SCell1 and SCell2 reported shall be such that wideband CQIPCell – wideband CQISCell1 ≥ 2 wideband CQISCell1 – wideband CQISCell2 ≥ 2 for more than 90% of the time. The following requirements for 4DL CA apply to UE Cateogry ≥8. For TDD-FDD CA with TDD PCell with 4 DL CC, for the parameters specified in Table 9.6.1.4-3 and Table 9.6.1.4-5, and using the downlink physical channels specified in tables C.3.2-1 and C.3.2-2 on each cell, the difference between the wideband CQI indices of PCell and SCell1 reported, and the difference between the wideband CQI indices of SCell1 and SCell2, and SCell1 and SCell3 reported shall be such that wideband CQIPCell – wideband CQISCell1 ≥ 2 wideband CQISCell1 – wideband CQISCell2 ≥ 2 wideband CQISCell1 – wideband CQISCell3 ≥ 2 for more than 90% of the time. Table 9.6.1.4-3: PUCCH 1-0 static test on multiple cells (TDD-FDD CA with TDD PCell, 3 and 4 DL CA) Table 9.6.1.4-4: PUCCH 1-0 static test (TDD-FDD CA with TDD PCell, 3 DL CA) Table 9.6.1.4-5: PUCCH 1-0 static test (TDD-FDD CA with TDD PCell, 4 DL CA) The following requirements for 5DL CA apply to UE Category 8 and ≥11. For TDD-FDD CA with TDD PCell with 5 DL CC, for the parameters specified in Table 9.6.1.4-6 and Table 9.6.1.4-7, and using the downlink physical channels specified in tables C.3.2-1 and C.3.2-2 on each cell, the difference between the wideband CQI indices of PCell and SCell1 reported, and the difference between the wideband CQI indices of SCell1 and SCell2, SCell1 and SCell3 and SCell 1 and SCell 4 reported shall be such that wideband CQIPCell – wideband CQISCell1 ≥ 2 wideband CQISCell1 – wideband CQISCell2 ≥ 2 wideband CQISCell1 – wideband CQISCell3 ≥ 2 wideband CQISCell1 – wideband CQISCell4 ≥ 2 for more than 90% of the time. Table 9.6.1.4-6: PUCCH 1-0 static test on multiple cells (TDD-FDD CA with TDD PCell, 5 DL CA) Table 9.6.1.4-7: PUCCH 1-0 static test (TDD-FDD CA with TDD PCell, 5 DL CA) The following requirements for 6DL CA apply to UE Category 8 and ≥11. For TDD-FDD CA with TDD PCell with 6 DL CC, for the parameters specified in Table 9.6.1.4-8 and Table 9.6.1.4-9, and using the downlink physical channels specified in tables C.3.2-1 and C.3.2-2 on each cell, the difference between the wideband CQI indices of PCell and SCell1 reported, and the difference between the wideband CQI indices of SCell1 and SCell2, SCell1 and SCell3, SCell1 and SCell4, and SCell1 and SCell5 reported shall be such that wideband CQIPCell – wideband CQISCell1 ≥ 2 wideband CQISCell1 – wideband CQISCell2 ≥ 2 wideband CQISCell1 – wideband CQISCell3 ≥ 2 wideband CQISCell1 – wideband CQISCell4 ≥ 2 wideband CQISCell1 – wideband CQISCell5 ≥ 2 for more than 90% of the time. Table 9.6.1.4-8: PUCCH 1-0 static test on multiple cells (TDD-FDD CA with TDD PCell, 6 DL CA) Table 9.6.1.4-9: PUCCH 1-0 static test (TDD-FDD CA with TDD PCell, 6 DL CA) The following requirements for 7DL CA apply to UE Category 8 and ≥11. For TDD-FDD CA with TDD PCell with 7 DL CC, for the parameters specified in Table 9.6.1.4-10 and Table 9.6.1.4-11, and using the downlink physical channels specified in tables C.3.2-1 and C.3.2-2 on each cell, the difference between the wideband CQI indices of PCell and SCell1 reported, and the difference between the wideband CQI indices of SCell1 and SCell2, SCell1 and SCell3, SCell1 and SCell4, SCell1 and SCell5, and SCell1 and SCell6 reported shall be such that wideband CQIPCell – wideband CQISCell1 ≥ 2 wideband CQISCell1 – wideband CQISCell2 ≥ 2 wideband CQISCell1 – wideband CQISCell3 ≥ 2 wideband CQISCell1 – wideband CQISCell4 ≥ 2 wideband CQISCell1 – wideband CQISCell5 ≥ 2 wideband CQISCell1 – wideband CQISCell6 ≥ 2 for more than 90% of the time. Table 9.6.1.4-10: PUCCH 1-0 static test on multiple cells (TDD-FDD CA with TDD PCell, 7 DL CA) Table 9.6.1.4-11: PUCCH 1-0 static test (TDD-FDD CA with TDD PCell, 7 DL CA)

3GPP TS 36.101

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

RAN4

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

9.6.1.4

– UAV-Config

The IE UAV-Config provides configuration parameters for UAV UE. UAV-Config information element -- ASN1START -- TAG-UAV-CONFIG-START UAV-Config-r18 ::= SEQUENCE { flightPathUpdateThrConfig-r18 SEQUENCE { flightPathUpdateDistanceThr-r18 SetupRelease { FlightPathUpdateDistanceThr-r18 } OPTIONAL, -- Need M flightPathUpdateTimeThr-r18 SetupRelease { FlightPathUpdateTimeThr-r18 } OPTIONAL -- Need M } OPTIONAL, -- Need M ... } FlightPathUpdateDistanceThr-r18 ::= INTEGER (0..1023) FlightPathUpdateTimeThr-r18 ::= INTEGER (0..16383) -- TAG-UAV-CONFIG-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

9.1.2 Format of APN Operator Identifier

The APN Operator Identifier is composed of three labels. The last label (or domain) shall be "gprs". The first and second labels together shall uniquely identify the GPRS/EPS PLMN. For each operator, there is a default APN Operator Identifier (i.e. domain name). This default APN Operator Identifier is derived from the IMSI as follows: "mnc<MNC>.mcc<MCC>.gprs" where: "mnc" and "mcc" serve as invariable identifiers for the following digits. <MNC> and <MCC> are derived from the components of the IMSI defined in clause 2.2. This default APN Operator Identifier is used for home routed inter-PLMN roaming situations when attempting to translate an APN consisting only of a Network Identifier into the IP address of the GGSN/PGW in the HPLMN. The PLMN may provide DNS translations for other, more human-readable, APN Operator Identifiers in addition to the default Operator Identifier described above. Alternatively, in the roaming case if the GGSN/PGW from the VPLMN is to be selected, the APN Operator Identifier for the UE is constructed from the serving network PLMN ID. In this case, the APN-OI replacement field, if received, shall be ignored. In order to guarantee inter-PLMN DNS translation, the <MNC> and <MCC> coding used in the "mnc<MNC>.mcc<MCC>.gprs" format of the APN OI shall be: - <MNC> = 3 digits - <MCC> = 3 digits - If there are only 2 significant digits in the MNC, one "0" digit is inserted at the left side to fill the 3 digits coding of MNC in the APN OI. As an example, the APN OI for MCC 345 and MNC 12 will be coded in the DNS as "mnc012.mcc345.gprs". The APN-OI replacement is used for selecting the GGSN/PGWfor non-roaming and home routed scenarios. The format of the domain name used in the APN-OI replacement field (as defined in 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [3] and 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [72]) is the same as the default APN-OI as defined above except that it may be preceded by one or more labels each separated by a dot. It is up to the operators to determine what labels shall precede the "mnc<MNC>.mcc<MCC>.gprs" trailing labels (see clause 5.1.1.1 in TS 29.303[ Domain Name System Procedures; Stage 3 ] [73] and also clause 13.1 in TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [3]). EXAMPLE 1: province1.mnc012.mcc345.gprs EXAMPLE 2: ggsn-cluster-A.provinceB.mnc012.mcc345.gprs The APN constructed using the APN-OI replacement field is only used for DNS translation. The APN when being sent to other network entities over GTP interfaces shall follow the rules as specified in 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [3] and 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [72].

3GPP TS 23.003

Numbering, addressing and identification

CT WG4

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

9.1.2

4.8.2.4 Connection Resume in CM-IDLE with Suspend and MO EDT procedure

The Connection Resume with Early Data Transmission procedure is used by the UE to optimise sending user data in a single uplink packet and single uplink followed by single downlink packet cases for a UE in CM-IDLE with Suspend. Figure 4.8.2.4-1: Connection Resume in RRC_IDLE with Suspend with EDT 1. UE to NG-eNB: RRC message (Resume ID, AS RAI) with UL EDT. The UE initiates the transition from RRC_IDLE with Suspend state to RRC_CONNECTED state, see TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [46]. The UE may include AS Release Assistance information indicating: - No further Uplink and Downlink Data transmission, or - Only a single Downlink Data transmission subsequent to the Uplink transmission. 2. The NG-eNB deciphers the EDT UL data received from the UE and forwards it to the UPF using the N3 UL TEID in the AS context. 3. The NG-eNB sends N2 Resume Request to AMF including Resume cause and N2 SM. If the UE included AS Release Assistance information indicating No further Uplink and Downlink Data transmission in step 1, NG-eNB may request for immediate transition to RRC_IDLE with Suspend. If the NG-eNB requests for immediate transition to RRC_IDLE with Suspend, the NG-eNB should include Paging Assistance Data for CE capable UE in the N2 Resume Request message. If the NG-eNB supports WUS and requests for immediate transition to RRC_IDLE with Suspend, the NG-eNB should include Information on Recommended Cells and RAN Nodes for Paging in the N2 Resume Request message. The AMF stores this information in the UE context for subsequent Paging procedure. 4. [Conditional] The AMF interacts with SMF to establish the N3 tunnel, except for the case: - The AMF receives a request for immediate transition to RRC_IDLE with Suspend in step 3; and - the AMF is not aware of any downlink data or signalling pending. 5. The AMF sends an N2 Resume Response to NG-eNB. If the AMF received a request for immediate transition to RRC_IDLE with Suspend in step 3 and there is no downlink data or signalling pending, the AMF includes a Suspend indication, keeps the UE in CM-IDLE with Suspend and restarts the Periodic Registration Timer unless the Strictly Periodic Registration Timer Indication has been provided to the UE during the previous registration procedure. Otherwise the AMF sends an N2 Resume Response to NG-eNB after the N3 Connectivity has been established and moves the UE to CM-CONNECTED. If the AMF knows of mobile terminating data or signalling pending, the AMF may include the Extended Connected Time value to the RAN 6. [Conditional] RRC procedure: 6a. If the AMF included the Suspend indication, the NG-eNB releases the RRC Connection with Suspend. The procedure is complete and following steps are skipped. 6b. If the AMF did not include the Suspend indication and: - The UE did not include AS Release Assistance Indication; or - The AMF included the Extended Connected Time value. the NG-eNB sends an RRC Resume message to the UE and the UE moves to CM-CONNECTED and RRC_CONNECTED. The procedure is complete and the following steps are skipped. 6c. Otherwise, if the AMF did not include Extended Connected Time value and the UE included AS Release Assistance information with only a single Downlink Data transmission subsequent to the Uplink transmission, the NG-eNB waits for the DL data to arrive and proceeds to steps 7-10. 7-9. The NG-eNB releases the N3 connectivity by sending an N2 Suspend Request to AMF including Suspend cause and N2 SM. Steps 2-4 of Connection Suspend procedure in clause 4.8.1.2 is executed. 10. [Conditional] NG-eNB to UE: RRC message (with DL data). The NG-eNB ciphers received DL data. The NG-eNB releases the RRC Connection with Suspend including the DL EDT data.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.8.2.4

– ParentIE-WithEM

The IE ParentIE-WithEMis an example of a high level IE including the extension marker (EM). The root encoding of this IE includes two lower level IEs ChildIE1-WithoutEM and ChildIE2-WithoutEM which not include the extension marker. Consequently, non-critical extensions of the Child-IEs have to be included at the level of the Parent-IE. The example illustrates how the two extension IEs ChildIE1-WithoutEM-vNx0 and ChildIE2-WithoutEM-vNx0 (both in release N) are used to connect non-critical extensions with a default extension location in the lower level IEs to the actual extension location in this IE. ParentIE-WithEM information element -- /example/ ASN1START ParentIE-WithEM ::= SEQUENCE { -- Root encoding, including: childIE1-WithoutEM ChildIE1-WithoutEM OPTIONAL, -- Need N childIE2-WithoutEM ChildIE2-WithoutEM OPTIONAL, -- Need N ..., [[ childIE1-WithoutEM-vNx0 ChildIE1-WithoutEM-vNx0 OPTIONAL, -- Need N childIE2-WithoutEM-vNx0 ChildIE2-WithoutEM-vNx0 OPTIONAL -- Need N ]] } -- ASN1STOP Some remarks regarding the extensions shown in the above example: – The fields childIEx-WithoutEM-vNx0 may not really need to be optional (depends on what is defined at the next lower level). – In general, especially when there are several nesting levels, fields should be marked as optional only when there is a clear reason.

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

4.23.12.5 EPS to 5GS mobility registration procedure (Idle) using N26 interface with AMF reallocation and I-SMF insertion

For EPS to 5GS Mobility registration procedure using N26 with AMF reallocation and I-SMF insertion, the procedure "EPS to 5GS Mobility Registration Procedure (Idle) using N26 interface with AMF reallocation" defined in clause 4.11.1.3.4 are re-used, with the following change: - The V-SMF is replaced by I-SMF and H-SMF is replaced by SMF, V-UPF is replaced by I-UPF. - The V-SMF selection is replaced by the I-SMF selection. - The V-CN Tunnel Info is replaced by Tunnel Info at I-UPF, H-CN Tunnel Info is replaced by Tunnel Info at UPF(PSA).

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.23.12.5

8.10.1.2.1A Transmit diversity performance with Enhanced Performance Requirement Type A – 2 Tx Antenna Ports with TM3 interference model

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

3GPP TS 36.101

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

RAN4

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

8.10.1.2.1A

5.34.6 Interaction between I-SMF and SMF for the support of traffic offload by UPF controlled by the I-SMF 5.34.6.1 General

This clause applies only in the case of non-roaming or LBO roaming as control of UL CL/Branching Point in VPLMN is not supported in HR case. It applies for the architectures described in clauses 5.34.4 and 5.34.5 When the I-SMF is inserted into a PDU Session, e.g. during PDU Session establishment or due to UE mobility, the I-SMF may provide the DNAI list it supports to the SMF. Based on the DNAI list information received from I-SMF, the SMF may provide the DNAI(s) of interest for this PDU Session for local traffic steering to the I-SMF e.g. immediately or when a new or updated or removed PCC rule(s) is/are received. The DNAI(s) of interest is derived from PCC rules. The I-SMF is responsible for the insertion, modification and removal of UPF(s) to ensure local traffic steering. The SMF does not need to have access to local configuration or NRF output related with UPF(s) controlled by I-SMF. Based on the DNAI(s) of interest for this PDU Session for local traffic steering and UE location the I-SMF determines which DNAI(s) are to be selected, selects UPF(s) acting as UL CL/BP and/or PDU Session Anchor based on selected DNAI, and insert these UPF(s) into the data path of the PDU Session. When a UL CL/BP has been inserted, changed or removed, the I-SMF indicates to the SMF that traffic offload have been inserted, updated or removed for a DNAI, providing also the IPv6 prefix that has been allocated if a new IPv6 prefix has been allocated for the PDU Session. From now on the SMF and I-SMF interactions entail: - Notifying the SMF with the new Prefix (multi-Homing case): the SMF is responsible of issuing Router Advertisement message. The SMF constructs a link-local address as the source IP address. The Router Advertisement message includes the IPv6 multi-homed routing rules provided to the UE to select the source IPv6 prefix among the prefixes related with the PDU Session according to RFC 4191 [8]. The SMF sends the Router Advertisement message to the UE via the PSA UPF controlled by the SMF. - N4 interactions related with traffic offloading. The SMF provide N4 information to the I-SMF for how the traffic shall be detected, enforced, monitored in UPF(s) controlled by the I-SMF: the SMF issues requests to the I-SMF containing N4 information to be used for creating / updating /removing PDR, FAR, QER, URR, etc. The N4 information for local traffic offload provided by the SMF to the I-SMF are described in clause 5.34.6.2. - Receiving N4 notifications related with traffic usage reporting: the I-SMF forwards to the SMF N4 information corresponding to UPF notifications related with traffic usage reporting; the SMF aggregates and constructs usage reports towards PCF/CHF. NOTE: How the SMF decides what traffic steering and enforcement actions are enforced in UPF(s) controlled by I-SMF is left for implementation. The I-SMF is responsible of the N4 interface towards the local UPF(s) including: - the usage of AN Tunnel Info received from the 5G AN via the AMF in order to build PDR and FAR; - requesting the allocation of the CN Tunnel Info between local UPFs (if needed); - to control UPF actions when the UP of the PDU Session becomes INACTIVE. - provide Trace Requirements on the N4 interface towards the UPF(s) it is controlling, using Trace Requirements received from AMF.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.34.6

5.2.13.2.8 Nbsf_Management_Notify service operation

Service Operation name: Nbsf_Management_Notify Description: BSF can notify NEF, AF, TSCTSF or PCF for a UE of newly registered PCF for a PDU Session or of deregistered PCF for a PDU Session. Inputs, Required: Notification Correlation Information, One or more instance per (DNN, S-NSSAI) of (UE address(es) [Required, if PCF notification is for a PDU Session], PCF address(es), PCF instance ID [Conditional, if available] and PCF Set ID [Conditional, if available]), level of Binding [Conditional, if available] (see clause 6.3.1.0 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]) or notification of registration/deregistration per (DNN, S-NSSAI). Inputs, Optional: None. Outputs, Required: None. Outputs, Optional: None.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

5.2.13.2.8

5.8.10.3.2 Derivation of NR sidelink measurement results

The UE may be configured by the peer UE associated to derive NR sidelink RSRP measurement results per PC5-RRC connection associated to the NR sidelink measurement objects based on parameters configured in the sl-MeasObject and in the sl-ReportConfig. The UE shall: 1> for each NR sidelink measurement quantity to be derived based on NR sidelink DMRS: 2> derive the corresponding measurement of NR sidelink frequency indicated quantity based on PSSCH DMRS as described in TS 38.215[ NR; Physical layer measurements ] [9] in the concerned sl-MeasObject; 2> apply layer 3 filtering as described in 5.5.3.2;

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

5.8.10.3.2

D.1.2 Principles of PTI handling for UE policy delivery service procedures

When the PCF or the UE initiates a procedure, it shall include a valid PTI value in the message header of the command message or the request message. When the UE initiates a procedure, the UE shall use a PTI value in range between 01H and 77H. When the PCF initiates a procedure, the PCF shall use a PTI value in range between 80H and FEH. When the PCF initiates a transaction related procedure (i.e. a procedure consisting of more than one message and the messages are related), it shall include a valid PTI value in the message header of the command message. If a response message is sent as result of a received command or request message, the UE or the PCF shall include in the response message the PTI value received within the received command or request message (see examples in figure D.1.2.1, figure D.1.2.2 and figure D.1.2.3). If a command message is sent as result of a received request message, the PCF shall include in the command message the PTI value received with the request message (see examples in figure D.1.2.3). Figure D.1.2.1: Network-requested transaction related procedure Figure D.1.2.2: UE-requested transaction related procedure rejected by the network Figure D.1.2.3: UE-requested transaction related procedure triggering a network-requested transaction related procedure NOTE: In earlier versions of this protocol, the UE can include in the response message a PTI value which is not the same as the one received within the command message, and therefore the PCF could not associate the response message from the UE to the command message sent.

3GPP TS 24.501

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

CT WG1

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

D.1.2

4.7.1 Architecture

Integrated access and backhaul (IAB) enables wireless relaying in NG-RAN. The relaying node, referred to as IAB-node, supports access and backhauling via NR. The terminating node of NR backhauling on network side is referred to as the IAB-donor, which represents a gNB with additional functionality to support IAB. Backhauling can occur via a single or via multiple hops. The IAB architecture is shown in Figure 4.7.1-1. The IAB-node supports the gNB-DU functionality, as defined in TS 38.401[ NG-RAN; Architecture description ] [4], to terminate the NR access interface to UEs and next-hop IAB-nodes, and to terminate the F1 protocol to the gNB-CU functionality, as defined in TS 38.401[ NG-RAN; Architecture description ] [4], on the IAB-donor. The gNB-DU functionality on the IAB-node is also referred to as IAB-DU. In addition to the gNB-DU functionality, the IAB-node also supports a subset of the UE functionality referred to as IAB-MT, which includes, e.g., physical layer, layer-2, RRC and NAS functionality to connect to the gNB-DU of another IAB-node or the IAB-donor, to connect to the gNB-CU on the IAB-donor, and to the core network. The IAB-node can access the network using either SA mode or EN-DC. In EN-DC, the IAB-node connects via E-UTRA to a MeNB, and the IAB-donor terminates X2-C as SgNB (TS 37.340[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 ] [21]). Figure 4.7.1-1: IAB architecture; a) IAB-node using SA mode with 5GC; b) IAB-node using EN-DC All IAB-nodes that are connected to an IAB-donor via one or multiple backhaul hops and controlled by this IAB-donor via F1AP and/or RRC form an IAB topology with the IAB-donor as its root (Fig. 4.7.1-2). In this IAB topology, the neighbour node of the IAB-DU or the IAB-donor-DU is referred to as the child node and the neighbour node of the IAB-MT is referred to as the parent node. The direction toward the child node is referred to as downstream while the direction toward the parent node is referred to as upstream. The IAB-donor performs centralized resource, topology and route management for its IAB topology. Figure 4.7.1-2: Parent- and child-node relationship for IAB-node

3GPP TS 38.300

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

RAN2

3GPP Series : 38 , Radio technology beyond LTE

4.7.1

5.3.13 CSS subscription data management function procedure 5.3.13.1 General

The CSS subscription data management function allows the CSS to update the CSS subscription data stored in the MME. The CSS subscription data is stored and managed in the MME independently from the Subscription Data received from the HSS. Whenever the CSS subscription data is changed for a user in the CSS, and the changes affect the CSG subscription information stored in the MME, the MME shall be informed about these changes by the means of the following procedure: - Insert CSG Subscriber Data procedure, used to add or modify the CSS subscription data in the 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.3.13

4.1.3.2 GPRS update status

In addition to the GMM sublayer states described so far, a GPRS update status exists. The GPRS update status pertains to a specific subscriber embodied by a SIM/USIM. This status is defined even when the subscriber is not activated (SIM/USIM removed or connected to a switched off ME). It is stored in a non volatile memory in the SIM/USIM. The GPRS update status is changed only after execution of a GPRS attach, combined GPRS attach, network initiated GPRS detach, authentication, service request, paging for GPRS services using IMSI, routing area updating, combined routing area updating procedure or due to change in RAI while timer T3346 running. GU1: UPDATED The last GPRS attach or routing area updating attempt was successful (correct procedure outcome, and the answer was accepted by the network). The SIM/USIM contains the RAI of the routing area (RA) to which the subscriber was attached, and possibly a valid P-TMSI, GPRS GSM ciphering key, GPRS UMTS ciphering key, GPRS UMTS integrity key and GPRS ciphering key sequence number. Furthermore, if the ME supports any GEA ciphering algorithm that requires a 128-bit ciphering key and a USIM is in use, then the ME may contain a valid GPRS GSM Kc128. Furthermore, if the ME supports any GIA integrity algorithm that requires a 128-bit integrity key and a USIM is in use, then the ME may contain a valid GPRS GSM Kint. GU2: NOT UPDATED The last GPRS attach or routing area updating attempt failed procedurally, e.g. no response was received from the network. This includes the cases of failures or congestion inside the network. In this case, the SIM/USIM can contain the RAI of the routing area (RA) to which the subscriber was attached, and possibly also a valid P-TMSI, GPRS GSM ciphering key, GPRS UMTS ciphering key, GPRS UMTS integrity key and GPRS ciphering key sequence number. For compatibility reasons, all these fields shall be set to the "deleted" value if the RAI is deleted. However, the presence of other values shall not be considered an error by the MS. Furthermore, if the ME supports any GEA ciphering algorithm that requires a 128-bit ciphering key and a USIM is in use, then the ME shall delete the GPRS GSM Kc128 stored if the RAI is deleted. Furthermore, if the ME supports any GIA integrity algorithm that requires a 128-bit integrity key and a USIM is in use, then the ME shall delete the GPRS GSM Kint stored if the RAI is deleted. GU3: ROAMING NOT ALLOWED The last GPRS attach or routing area updating attempt was correctly performed, but the answer from the network was negative (because of roaming or subscription restrictions). In this case, the SIM/USIM can contain the RAI of the routing area (RA) to which the subscriber was attached, and possibly also a valid P-TMSI, GPRS GSM ciphering key, GPRS UMTS ciphering key, GPRS UMTS integrity key or GPRS ciphering key sequence number. For compatibility reasons, all these fields shall be set to the value "deleted" if the RAI is deleted. However, the presence of other values shall not be considered an error by the MS. Furthermore, if the ME supports any GEA ciphering algorithm that requires a 128-bit ciphering key and a USIM is in use, then the ME shall delete the GPRS GSM Kc128 stored if the RAI is deleted. Furthermore, if the ME supports any GIA integrity algorithm that requires a 128-bit integrity key and a USIM is in use, then the ME shall delete the GPRS GSM Kint stored if the RAI is deleted. If the MS is attached for emergency bearer services, the MS shall not store the GMM parameters described in this subclause on the SIM/USIM or in non-volatile memory. Instead the MS shall temporarily store these parameters locally in the ME and the MS shall delete these parameters when the MS is detached.

3GPP TS 24.008

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

CT WG1

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

4.1.3.2

10.5.5.15a Routing area identification 2

The purpose of the Routing area identification 2 information element is to provide an unambiguous identification of routing areas within the GPRS coverage area. The Routing area identification 2 is a type 4 information element with a length of 8 octets. The Routing area identification 2 information element is coded as shown in figure 10.5.130a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.148a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.130a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Routing area identification 2 information element Table 10.5.148a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Routing area identification 2 information element

3GPP TS 24.008

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

CT WG1

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

10.5.5.15a

5.37.3.2 Support of ECN marking for L4S in NG-RAN

ECN marking for L4S may be supported in NG-RAN as specified in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27]. To enable ECN marking for L4S in NG-RAN, dedicated QoS Flow(s) are used for carrying L4S enabled IP traffic. The SMF may be instructed, based on either dynamic or predefined PCC rule, to provide an indication for ECN marking for L4S to NG-RAN for a corresponding QoS Flow(s) in UL and/or DL directions. In the absence of such PCC rule, the use of ECN marking for L4S in NG-RAN on a QoS Flow is controlled by a coordinated configuration in NG-RAN and 5GC. The criteria based on which NG-RAN decides to mark ECN bits for L4S is NG-RAN implementation specific. In the case of inter NG-RAN UE mobility, if the ECN marking for L4S has been enabled on source NG-RAN, but the target NG-RAN does not support ECN marking for L4S, then the SMF may, if supported, enable ECN marking for L4S in PSA UPF as defined in clause 5.37.3.3.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.37.3.2

9.4.15.7 T3302 value

This IE may be included to indicate a value for the T3302 timer. In Iu mode, if the MS is not attached for emergency bearer services, the network shall not include this IE if this message is to be sent non-integrity protected. If the MS is attached for emergency bearer services, the network may include this IE if this message is to be sent non-integrity protected. In Iu mode, if this message is received without integrity protection the MS not attached for emergency bearer services shall ignore the contents of this IE and use the default value. If the MS is attached for emergency bearer services, the MS shall use the received contents of this IE if this message is received without integrity protection. If this IE is not included in the message in A/Gb mode or if in Iu mode this IE is not included in an integrity protected message, the MS shall use the default value.

3GPP TS 24.008

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

CT WG1

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

9.4.15.7

13.3 Private User Identity

The private user identity shall take the form of an NAI, and shall have the form username@realm as specified in clause 2.1 of IETF RFC 4282 [53]. NOTE 1: It is possible for a representation of the IMSI to be contained within the NAI for the private identity. For 3GPP systems, the private user identity used for the user shall be as specified in clause 4.2 of 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [81] and in 3GPP TS 23.228[ IP Multimedia Subsystem (IMS); Stage 2 ] [24] Annex E.3.1. If the private user identity is not known, the private user identity shall be derived from the IMSI. The following steps show how to build the private user identity out of the IMSI: 1. Use the whole string of digits as the username part of the private user identity; and 2. convert the leading digits of the IMSI, i.e. MNC and MCC, into a domain name, as described in clause 13.2. The result will be a private user identity of the form "<IMSI>@ims.mnc<MNC>.mcc<MCC>.3gppnetwork.org". For example: If the IMSI is 234150999999999 (MCC = 234, MNC = 15), the private user identity then takes the form "234150999999999@ims.mnc015.mcc234.3gppnetwork.org".. The private user identity for a Stand-alone Non-Public Network (SNPN) subscriber with an IMSI-based SUPI type, shall use the IMSI-based derivation described above, and append nid<NID> of the SNPN, between the "ims." and "mnc<MNC>" labels. NOTE 2: The UE takes the NID from "list of subscriber data" as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [139], from the entry selected by the UE. For an SNPN, if IMSI is as above, and for a NID of 000007ed9d5, the private user identity takes the form "234150999999999@ims.nid000007ed9d5.mnc015.mcc234.3gppnetwork.org". The Private User Identity for a Stand-alone Non-Public Network (SNPN) subscriber identified by a SUPI containing a network-specific identifier that takes the form of an NAI is obtained as follows: the username is the same as the username in the NAI, and the realm portion is identical with the Home domain defined in clause 13.2. For 3GPP2 systems, if there is no IMC present, the UE shall derive the private user identity as described in Annex C of 3GPP2 X.S0013-004 [67].

3GPP TS 23.003

Numbering, addressing and identification

CT WG4

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

13.3

19.3.9 IMSI-based Emergency NAI

This clause describes the format of the UE identification needed to access the 3GPP EPC from non-3GPP accesses, when UE is performing an emergency attach and IMSI is available. For more information, see clause 4.4.1 of 3GPP TS 24.302[ Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networks; Stage 3 ] [77]. The IMSI-based Emergency NAI shall take the form of an NAI and shall be encoded as the Root NAI as specified in clause 19.3.2, but with the realm name prepended by the "sos" label. The resulting realm part of the IMSI-based Emergency NAI will be in the form: "@sos.nai.epc.mnc<MNC>.mcc<MCC>.3gppnetwork.org" The resulting IMSI-based Emergency NAI will be in the form: "0<IMSI>@sos.nai.epc.mnc<MNC>.mcc<MCC>.3gppnetwork.org" when used for EAP AKA authentication "6<IMSI>@sos.nai.epc.mnc<MNC>.mcc<MCC>.3gppnetwork.org" when used for EAP AKA' authentication For example, if the IMSI is 234150999999999 (MCC = 234, MNC = 15), the IMSI-based Emergency NAI takes the form 0234150999999999@sos.nai.epc.mnc015.mcc234.3gppnetwork.org for EAP AKA authentication and it takes the form 6234150999999999@sos.nai.epc.mnc015.mcc234.3gppnetwork.org for EAP AKA' authentication.

3GPP TS 23.003

Numbering, addressing and identification

CT WG4

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

19.3.9

4.11.0a.2a.2 SMF initiated SM Policy Association Modification

4.11.0a.2a.2.1 SMF initiated SM Policy Association Modification due to UE requested bearer resource modification procedure When SMF+PGW-C receives the UE Policy Container in the UE requested bearer resource modification procedure, the SMF+PGW-C provides the UE Policy Container to the PCF. The SM Policy Association Modification procedure in clause 4.16.5.1 applies with the following enhancements is executed with the following differences, applicable between step 4 and step 5: If the PCF receives both the indication that the PCRT "UE Policy Container received" was met and the UE Policy Container, steps 4a to 4d below are executed. - Step 4a: The PCF determines that the SM Policy Association is used to provision URSP rules to the UE by checking the UE Policy Container received from SMF+PGW-C. - Step 4b: The PCF for the PDU Session discovers the PCF for the UE by querying the BSF, using Nbsf_Management_Discovery for the SUPI. If no result is obtained from the BSF the PCF for the PDU Session selects the PCF for the UE by querying NRF, using the URSP delivery in EPS capability of the PCF, as defined in clause 6.3.7.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. - Step 4c: The PCF for the PDU Session establishes a UE Policy Association towards the PCF for the UE as described in clause 4.11.0a.2a.5. - Step 4d: If the PCF for the UE provides any Policy Control Request Trigger parameters in the Npcf_UEPolicyControl Create Response the PCF for the PDU Session takes them into account for the generation of Policy Control Request Triggers to the SMF+PGW-C. 4.11.0a.2a.2.2 SMF initiated SM Policy Association Modification at mobility between 5GS and EPS During 5GS to EPS mobility procedure, the PCF for the PDU Session establishes a UE Policy Association towards the PCF for the UE if it exists otherwise, it performs PCF discovery and selection then establishes a UE Policy Association. During EPS to 5GS mobility procedure the PCF for the PDU Session terminates the UE Policy Association, if established during 5GS to EPS mobility. The following enhancements are applicable to clause 4.16.5.1 (SMF initiated SM Policy Association Modification procedure): In addition to step 4 in clause 4.16.5.1, the PCF determines that 5GS to EPS or EPS to 5GS mobility applies by checking a change in RAT and Access-Type. - If 5GS to EPS mobility applies, , in non-roaming and Home Routed roaming the (H-)PCF for the PDU Session determines whether the UE supports provisioning of URSP Rules in EPS by checking indication of support of URSP delivery in EPS in UDR and in LBO roaming the V-PCF for the PDU Session determine whether the UE supports provisioning of URSP rules in EPS based on local configuration, e.g. using the PEI, given that the V-PCF has no access to UDR at the HPLMN. The (H-)PCF or the V-PCF determines if the SMF+PGW-C supports delivery of URSP Rules in EPS as reported by the SMF+PGW-C. If the PCF determines that the UE and the SMF+PGW-C support provisioning of URSP Rules in EPS, the PCF for the PDU Session finds the PCF for the UE using Nbsf_Management_Discovery for the SUPI and then performs UE Policy Association Establishment procedure as specified in clause 4.11.0a.2a.5. If no result is obtained from the BSF, the PCF for the PDU Session selects the PCF for the UE by querying NRF, using the URSP delivery in EPS capability of the PCF, as defined in clause 6.3.7.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. - If EPS to 5GS mobility applies, the PCF for the PDU Session requests the termination of the UE Policy association as described in clause 4.11.0a.2a.8. 4.11.0a.2a.2.3 SMF initiated SM Policy Association Modification for UE reporting URSP update result When the UE reports the result of URSP rule update, the following enhancements are applicable to clause 4.16.5.1 (SM Policy Association Modification procedure): In addition to step 4 in clause 4.16.5.1 if the PCF for the PDU Session receives the "UE Policy" Policy Control Request Trigger and associated UE Policy Container, steps 4a to 4b below are executed: - Step 4a: The PCF for the PDU Session determines that a UE Policy association has been already established towards the PCF for the UE for the SM Policy Association as described in clause 4.11.0a.2a.7. - Step 4b: The PCF for the PDU Session forwards the UE Policy Container to the PCF for the UE in Npcf_UEPolicyControl_Update Request.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.11.0a.2a.2

– LogicalChannelConfig

The IE LogicalChannelConfig is used to configure the logical channel parameters. LogicalChannelConfig information element -- ASN1START -- TAG-LOGICALCHANNELCONFIG-START LogicalChannelConfig ::= SEQUENCE { ul-SpecificParameters SEQUENCE { priority INTEGER (1..16), prioritisedBitRate ENUMERATED {kBps0, kBps8, kBps16, kBps32, kBps64, kBps128, kBps256, kBps512, kBps1024, kBps2048, kBps4096, kBps8192, kBps16384, kBps32768, kBps65536, infinity}, bucketSizeDuration ENUMERATED {ms5, ms10, ms20, ms50, ms100, ms150, ms300, ms500, ms1000, spare7, spare6, spare5, spare4, spare3,spare2, spare1}, allowedServingCells SEQUENCE (SIZE (1..maxNrofServingCells-1)) OF ServCellIndex OPTIONAL, -- Cond PDCP-CADuplication allowedSCS-List SEQUENCE (SIZE (1..maxSCSs)) OF SubcarrierSpacing OPTIONAL, -- Need R maxPUSCH-Duration ENUMERATED {ms0p02, ms0p04, ms0p0625, ms0p125, ms0p25, ms0p5, ms0p01-v1700, spare1} OPTIONAL, -- Need R configuredGrantType1Allowed ENUMERATED {true} OPTIONAL, -- Need R logicalChannelGroup INTEGER (0..maxLCG-ID) OPTIONAL, -- Need R schedulingRequestID SchedulingRequestId OPTIONAL, -- Need R logicalChannelSR-Mask BOOLEAN, logicalChannelSR-DelayTimerApplied BOOLEAN, ..., bitRateQueryProhibitTimer ENUMERATED {s0, s0dot4, s0dot8, s1dot6, s3, s6, s12, s30} OPTIONAL, -- Need R [[ allowedCG-List-r16 SEQUENCE (SIZE (0.. maxNrofConfiguredGrantConfigMAC-1-r16)) OF ConfiguredGrantConfigIndexMAC-r16 OPTIONAL, -- Need S allowedPHY-PriorityIndex-r16 ENUMERATED {p0, p1} OPTIONAL -- Need S ]], [[ logicalChannelGroupIAB-Ext-r17 INTEGER (0..maxLCG-ID-IAB-r17) OPTIONAL, -- Need R allowedHARQ-mode-r17 ENUMERATED {harqModeA, harqModeB} OPTIONAL -- Need R ]] } OPTIONAL, -- Cond UL ..., [[ channelAccessPriority-r16 INTEGER (1..4) OPTIONAL, -- Need R bitRateMultiplier-r16 ENUMERATED {x40, x70, x100, x200} OPTIONAL -- Need R ]] } -- TAG-LOGICALCHANNELCONFIG-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

D.2.1.6 Abnormal cases in the UE

The following abnormal cases can be identified: a) Receipt of an instruction associated with a UPSI which has a PLMN ID part that is not equal to the PLMN ID of the UE's HPLMN and the instruction contains a UE policy part with a UE policy part type set to "URSP" for a UE not operating in SNPN access operation mode, or receipt of an instruction associated with a UPSI which has a PLMN ID part that is not equal to the PLMN ID part of the selected SNPN and the instruction contains a UE policy part with a UE policy part type set to "URSP" for a UE operating in SNPN access operation mode. The UE shall set the UE policy delivery service cause to #111 “Protocol error, unspecified” for the instruction in the UE policy section management result IE of the MANAGE UE POLICY COMMAND REJECT message. b) Receipt of an instruction associated with a UPSI which has a PLMN ID part that is not equal to the PLMN ID of the UE's HPLMN or the UE's RPLMN and the instruction contains a UE policy part with a UE policy part type set to "ANDSP" for a UE not operating in SNPN access operation mode or receipt of an instruction associated with a UPSI which has a PLMN ID part that is not equal to the PLMN ID part of the subscribed SNPN or the UE's RSNPN and the instruction contains a UE policy part with a UE policy part type set to "ANDSP" for a UE operating in SNPN access operation mode. The UE shall set the UE policy delivery service cause to #111 “Protocol error, unspecified” for the instruction in the UE policy section management result IE of the MANAGE UE POLICY COMMAND REJECT message. c) Transmission failure of the MANAGE UE POLICY COMPLETE message indication from lower layers. The UE shall not diagnose an error and consider the network-requested UE policy management procedure is complete. NOTE 1: Considering the network-requested UE policy management procedure is complete as the result of this abnormal case, does not cause the UE to revert the execution of the successfully executed instructions included in the MANAGE UE POLICY COMMAND message. d) Transmission failure of the MANAGE UE POLICY COMMAND REJECT message indication from lower layers. The UE shall not diagnose an error and consider the network-requested UE policy management procedure is complete. NOTE 2: Considering the network-requested UE policy management procedure is complete as the result of this abnormal case, does not cause the UE to revert the execution of the successfully executed instructions included in the MANAGE UE POLICY COMMAND message. e) Receipt of a MANAGE UE POLICY COMMAND message with a PTI set to the same value as the PTI of a previously received MANAGE UE POLICY COMMAND message. The UE shall discard the message and retransmit the MANAGE UE POLICY COMMAND COMPLETE or MANAGE UE POLICY COMMAND REJECT message transmitted in response to the previously received MANAGE UE POLICY COMMAND message. NOTE 3: The way to achieve this is UE implementation dependent. For example, the UE can assume that on the fifth expiry of timer T3501, the PCF will abort the procedure and that the PTI value assigned to the procedure will be released. f) Receipt of an instruction associated with a UPSI which has a PLMN ID part that is equal to the PLMN ID part of the selected SNPN, the instruction contains a UE policy part with a UE policy part type set to "URSP", UE's RSNPN is a non-subscribed SNPN and: 1) the UE has a stored non-subscribed SNPN signalled URSP handling indication for the selected entry of "list of subscriber data" or the selected PLMN subscription indicating that the UE is not allowed to accept URSP signalled by non-subscribed SNPNs; or 2) the UE does not have a stored non-subscribed SNPN signalled URSP handling indication for the selected entry of "list of subscriber data" or the selected PLMN subscription, and the non-subscribed SNPN signalled URSP handling indication preconfigured in the selected entry of "list of subscriber data" or the selected PLMN subscription indicates that the UE is not allowed to accept URSP signalled by non-subscribed SNPNs; for a UE operating in SNPN access operation mode. The UE shall set the UE policy delivery service cause to #111 “Protocol error, unspecified” for the instruction in the UE policy section management result IE of the MANAGE UE POLICY COMMAND REJECT message.

3GPP TS 24.501

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

CT WG1

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

D.2.1.6

A.1 Causes related to UE identification

Cause #3 – Illegal UE This 5GMM cause is sent to the UE when the network refuses service to the UE either because an identity of the UE is not acceptable to the network or because the UE does not pass the authentication check. Cause #6 – Illegal ME This 5GMM cause is sent to the UE if the ME used is not acceptable to the network, e.g. on the prohibited list. Cause #9 – UE identity cannot be derived by the network. This 5GMM cause is sent to the UE when the network cannot derive the UE's identity from the 5G-GUTI or 5G-S-TMSI because of e.g. no matching identity/context in the network, failure to validate the UE's identity due to integrity check failure of the received message. Cause #10 – Implicitly de-registered This 5GMM cause is sent to the UE either if the network has implicitly de-registered the UE, e.g. after the implicit de-registration timer has expired, or if the 5GMM context data related to the subscription does not exist in the AMF e.g. because of a AMF restart, or because of a registration request for mobility or registration update is routed to a new AMF.

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

A.1

5.2.6.23.6 Nnef_AMInfluence_Notify operation

Service operation name: Nnef_AMInfluence_Notify Description: Forward the notification of change of service coverage event report to the AF. Inputs, Required: AF Transaction Id, Event ID. The AF Transaction Id identifies the AF request for AM influence data that the event report is related to. The event that can be subscribed is the event for reporting change of coverage defined in clause 6.1.3.18 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20] Inputs, Optional: Event information (as defined in clause 6.1.3.18 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]). Outputs, Required: Operation execution result indication. Outputs, Optional: None.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

5.2.6.23.6

6.38.2.9 Creation and Management

The 5G system shall support a mechanism for the network operator to provision an eRG with: - policies on which transport (e.g. wireless, cable, etc.) is best suited for different negotiated QoS levels, - authentication credentials, - identification, - initial OA&M information, and - associated subscription The 5G system shall enable the network operator to configure a PRAS with: - radio settings pertaining to licensed spectrum, - authentication credentials, - identification, - initial OA&M information, and - associated subscription. Subject to operator policy, the 5G system shall enable the Authorised Administrator to provision a PRAS with UE access considerations (allowing all UEs, or allowing specific UEs only) The 5G system shall provide a mechanism for the Authorised Administrator to trigger initial provisioning of an eRG. The 5G system shall provide a mechanism for the Authorised Administrator to trigger initial provisioning of a PRAS. The 5G system shall support mechanisms for a network operator or authorized 3rd party (e.g., a PIN User) to create, remove and manage a PIN, including: - Authorizing/deauthorizing PIN Elements; - Authorizing/deauthorizing PIN Elements with Management Capability; - Authorizing/deauthorizing PIN Elements with Gateway Capability; - Establishing duration of the PIN; - Configure PIN Elements to enable service discovery of other PIN Elements; - Authorize/deauthorise if a PIN Element can use a PIN Element with Gateway Capability to communicate with the 5GS; - Authorize/deauthorise for a PIN Element(s): - which other PIN Element it can communicate with, - which applications/service or service in that PIN it can access, - which PIN Element it can use as a relay. - Authorize/deauthorise a UE to perform service discovery of PIN Elements over the 5G network; - Configure a PIN Element for external connectivity e.g.via 5G system; NOTE1: The authorization can include the consideration of the location and time validity of the PIN and its PIN elements. The 5G system shall support a mechanism to enable a UE that is not a PIN Element of the PIN or a non-3GPP device that is not a PIN element of the PIN to request to join the PIN. The 5G system shall support mechanisms for a network operator to configure the following policies in a PIN: - Configure the connectivity type (e.g. licensed, unlicensed PIN direct connection) a PIN Element can use. 5G system shall be able to support mechanism to provide life span information of the PIN to the authorized 3rd party or the PIN elements when the PIN is created for limited time span. The 5G system shall provide means to control which UEs can connect to a PRAS. The 5G system shall support mechanisms to provision a PIN Element to use either licensed (under control of a MNO) or unlicensed spectrum (may be under the control of the MNO, or not) (e.g., when it has no connectivity to the 5G system).

3GPP TS 22.261

Service requirements for the 5G system

SA WG1

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

6.38.2.9

5.16.4.4 Reachability Management

Over 3GPP access, an Emergency Registered UE when its Periodic Registration Update timer expires shall not initiate a Periodic Registration Update procedure but shall enter the RM-DEREGISTERED state. For such UEs, the AMF runs a mobile reachable timer with a similar value to the UE's Periodic Registration Update timer. After expiry of this timer the AMF may change the UE RM state for 3GPP Access in the AMF to RM-DEREGISTERED. The AMF assigns the Periodic Registration Update timer value to Emergency Registered UEs. This timer keeps the Emergency Registered UE registered for Emergency Services after change to CM-IDLE state to allow for a subsequent Emergency Service without a need for a new Emergency Registration. Over non-3GPP access, an Emergency Registered UE is only reachable in CM-CONNECTED state: since the UE may only use Emergency Services over Non-3GPP access when it is not possible over 3GPP access, 3GPP access is assumed to be unavailable for paging the UE.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.16.4.4

6.9.4 Key-change-on-the-fly 6.9.4.1 General

Key change on-the-fly consists of key refresh or key re-keying. Key refresh shall be possible for KgNB, KRRC-enc, KRRC-int, KUP-enc, and KUP-int (if available ) and shall be initiated by the gNB/ng-eNB when a PDCP COUNTs are about to be re-used with the same Radio Bearer identity and with the same KgNB. The procedure is described in clause 6.9.4.5. Key re-keying shall be possible for the KgNB, KRRC-enc, KRRC-int, KUP-enc, and KUP-int (if available). This re-keying shall be initiated by the AMF when a 5G AS security context different from the currently active one shall be activated. The procedures for doing this are described in clause 6.9.4.4. AS Key change on-the-fly is accomplished using a procedure based on intra-cell handover. The following AS key changes on-the-fly shall be possible: local KgNB refresh (performed when PDCP COUNTs are about to wrap around), KgNB re-keying performed after an AKA run, activation of a native context after handover from E-UTRAN. Key re-keying shall be possible for KNAS-enc and KNAS-int. Re-keying of KNAS-enc and KNAS-int shall be initiated by the AMF when a 5G NAS security context different from the currently active one shall be activated. The procedures for doing this are described in clause 6.9.4.2. Re-keying of the entire 5G key hierarchy including KAMF shall be achieved by first re-keying KAMF, then KNAS-enc and KNAS-int, followed by re-keying of the KgNB and derived keys. For NAS key change on-the-fly, activation of NAS keys is accomplished by a NAS SMC procedure.

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

6.9.4

16.15.4.2.2 Discard

When the PSIHI is set for a QoS flow, as soon as one PDU of a PDU set is known to be lost, the remaining PDUs of that PDU Set can be considered as no longer needed by the application and may be subject to discard operation at the transmitter to free up radio resources. NOTE 1: It cannot always be assumed that the remaining PDUs are not useful and can safely be discarded. Also, in case of Forward Error Correction (FEC), active discarding of PDUs when assuming that a large enough number of packets have already been transmitted for FEC to recover without the remaining PDUs is not recommended as it might trigger an increase of FEC packets. In uplink, the UE may be configured with PDU Set based discard operation for a specific DRB. When configured, the UE discards all packets in a PDU set when one PDU belonging to this PDU set is discarded due to discard timer expiry. The gNB may perform downlink PDU Set discarding based on implementation by taking at least PSDB, PSI, PSIHI parameters into account. In case of congestion, the gNB may use the PSI for PDU set discarding. For uplink, dedicated downlink signalling is used to request the UE to apply a shorter discard timer to low importance SDUs in PDCP. NOTE 2: How SDUs are identified as low importance is left up to UE implementation. When a PSI is available, it can be used to classify the PDCP SDUs of a PDU Set according to the guidelines specified in TS 26.522[ 5G Real-time Media Transport Protocol Configurations ] [58].

3GPP TS 38.300

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

RAN2

3GPP Series : 38 , Radio technology beyond LTE

16.15.4.2.2

5.2.6.16.5 Nnef_AnalyticsExposure_Fetch service operation

Service operation name: Nnef_AnalyticsExposure_Fetch Description: The NF consumer requests analytics information. Inputs Required: Analytics ID, Analytic Filter Information, Target of Analytic Reporting (UE (e.g. GPSI), External Group Identifier, any UEs), Analytic Reporting Information. These input parameters are detailed in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]. Inputs, Optional: Slice specific information, Geographical area. NOTE 1: When the Analytics ID is set to "User Data Congestion", the input parameters are defined in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]. NOTE 2: The Geographical area could be provided as e.g. shapes (e.g. polygons, circles, etc.) or civic addresses (e.g. streets, districts, etc.) as referenced by OMA Presence API. Outputs Required: Analytic information (defined on a per Analytics ID basis) specified in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]. Outputs, Optional: Timestamp of analytics generation, Probability assertion, specified in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50].

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

5.2.6.16.5

4.11.2 Interworking procedures without N26 interface 4.11.2.1 General

Clause 4.11.2 defines the procedures to support interworking between 5GS and EPS without any N26 interface between AMF and MME. During interworking from EPS to 5GS, as the SMF+PGW-C may have different IP addresses when being accessed over S5/S8 and N11/N16 respectively, the AMF shall discover the SMF instance by an NF/NF service discovery procedure using the FQDN for the S5/S8 interface received from the UDM as a query parameter. This is required for both non-roaming and roaming with local breakout, as well as for home routed roaming. NOTE: As the AMF is not aware of the S-NSSAI assigned for the PDN Connection, the NF/NF service discovery used to find the SMF instance can use PLMN level NRF.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.11.2

4.22.4 Access Network Performance Measurements

The PMF of UE side or/and UPF side should be able to correlate the measurement packets with the corresponding access type in order to get the accurate measurement result for each access. The PMF of UE side correlates the sent measurement request and received measurement response messages via the same access type and the PMF of UPF side correlates the sent measurement request and received measurement response messages via the same N3 or N9 Tunnel. The PMF of UPF side shall record the relationship between the RTT measurement result and the N3 or N9 Tunnel. NOTE: The frequency for RTT measurement for each access is decided by the PMF of the UE and the UPF respectively.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.22.4

– MTCH-SSB-MappingWindowList

The IE MTCH-SSB-MappingWindowList is used to configure MTCH PDCCH ocassions to SSB mapping window related periodic and offset parameters. MTCH-SSB-MappingWindowList information element -- ASN1START -- TAG-MTCH-SSB-MAPPINGWINDOWLIST-START MTCH-SSB-MappingWindowList-r17 ::= SEQUENCE (SIZE (1..maxNrofMTCH-SSB-MappingWindow-r17)) OF MTCH-SSB-MappingWindowCycleOffset-r17 MTCH-SSB-MappingWindowCycleOffset-r17 ::= CHOICE { ms10 INTEGER(0..9), ms20 INTEGER(0..19), ms32 INTEGER(0..31), ms64 INTEGER(0..63), ms128 INTEGER(0..127), ms256 INTEGER(0..255) } -- TAG-MTCH-SSB-MAPPINGWINDOWLIST-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

20.2 Paging Collision Avoidance

The purpose of paging collision avoidance is to address the overlap of paging occasions on both USIMs when a MUSIM device (e.g. dual USIM device) is in RRC_IDLE/RRC_INACTIVE state in both the networks (e.g. Network A and Network B) associated with respective USIMs. Network A is NR and Network B is E-UTRA or NR. A MUSIM device may determine potential paging collision on two networks and may trigger actions to prevent potential paging collision on NR network as specified in TS 23.501[ System architecture for the 5G System (5GS) ] [3]. NOTE: It is left to UE implementation as to how it selects one of the two RATs/networks for paging collision avoidance.

3GPP TS 38.300

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

RAN2

3GPP Series : 38 , Radio technology beyond LTE

20.2

5.2.2.3.4 Actions related to transmission of RRCSystemInfoRequest message

The UE shall set the contents of RRCSystemInfoRequest message as follows: 1> if the procedure is triggered to request the required SI message(s) other than positioning: 2> set the requested-SI-List to indicate the SI message(s) that the UE requires to operate within the cell, and for which si-BroadcastStatus is set to notBroadcasting; 1> else if the procedure is triggered to request the required SI message(s) for positioning: 2> set the requestedPosSI-List to indicate the SI message(s) that the UE upper layers require for positioning operations, and for which posSI-BroadcastStatus is set to notBroadcasting. The UE shall submit the RRCSystemInfoRequest message to lower layers for transmission.

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

5.2.2.3.4

6.4.7 Signalling procedure for periodic local authentication

The following procedure is used by the RNC to periodically perform a local authentication. At the same time, the amount of data sent during the RRC connection is periodically checked by the RNC and the UE. The RNC is monitoring the COUNT-C value associated to each radio bearer. The procedure is triggered whenever any of these values reaches a critical checking value. The granularity of these checking values and the values themselves are defined by the visited network. All messages in the procedure are integrity protected. Figure 15a: RNC periodic local authentication procedure 1. When a checking value is reached (e.g. the value in some fixed bit position in the hyperframe number is changed), a Counter Check message is sent by the RNC. The Counter Check message contains the most significant parts of the COUNT-C values (which reflect amount of data sent and received) from each active radio bearer. 2. The UE compares the COUNT-C values received in the Counter Check message with the values of its radio bearers. Different UE COUNT-C values are included within the Counter Check Response message. 3. If the RNC receives a counter check response message that does not contain any COUNT-C values, the procedure ends. If the RNC receives a counter check response that contains one or several COUNT-C values, the RNC may release the connection.

3GPP TS 33.102

3G security; Security architecture

SA WG3

3GPP Series : 33 , Security aspects

6.4.7

9.9.3.12 EPS mobile identity

The purpose of the EPS mobile identity information element is to provide either the IMSI, the GUTI or the IMEI. The EPS mobile identity information element is coded as shown in figures 9.9.3.12.1 and 9.9.3.12.2 and table 9.9.3.12.1. The EPS mobile identity is a type 4 information element with a minimum length of 3 octets and a maximum length of 13 octets. Figure 9.9.3.12.1: EPS mobile identity information element for type of identity "GUTI" Figure 9.9.3.12.2: EPS mobile identity information element for type of identity "IMSI" or "IMEI" Table 9.9.3.12.1: EPS mobile identity information element

3GPP TS 24.301

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

CT WG1

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

9.9.3.12

10.5.5.3 Ciphering algorithm

The purpose of the ciphering algorithm information element is to specify which ciphering algorithm shall be used. The ciphering algorithm is a type 1 information element. The ciphering algorithm information element is coded as shown in figure 10.5.119/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.136/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.119/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Ciphering algorithm information element Table 10.5.136/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Ciphering algorithm information element

3GPP TS 24.008

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

CT WG1

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

10.5.5.3

5.3.1 Uplink transmission scheme

Two transmission schemes are supported for PUSCH: codebook based transmission and non-codebook based transmission. For codebook based transmission, the gNB provides the UE with a transmit precoding matrix indication in the DCI. The UE uses the indication to select the PUSCH transmit precoder from the codebook. For non-codebook based transmission, the UE determines its PUSCH precoder based on wideband SRI field from the DCI. DMRS based spatial multiplexing is supported for PUSCH. Up to 8, 12, 16, and 24 orthogonal UL DMRS ports are supported for type 1, type 2, enhanced type 1, and enhanced type 2 DMRS respectively. For a given UE, up to 4 or up to 8 layer transmissions are supported. The number of code words is one for 1 to 4 layer transmission and two for 5 to 8 layer transmission. When transform precoding is used, only a single MIMO layer transmission is supported. Transmission durations from 1 to 14 symbols in a slot is supported. Aggregation of multiple slots with TB repetition is supported. Two types of frequency hopping are supported, intra-slot frequency hopping, and in case of slot aggregation, inter-slot frequency hopping. Intra-slot and inter-slot frequency hopping are not supported when PRB interlace uplink transmission waveform is used. PUSCH may be scheduled with DCI on PDCCH, or a semi-static configured grant may be provided over RRC, where two types of operation are supported: - The first PUSCH is triggered with a DCI, with subsequent PUSCH transmissions following the RRC configuration and scheduling received on the DCI, or - The PUSCH is triggered by data arrival to the UE's transmit buffer and the PUSCH transmissions follow the RRC configuration.

3GPP TS 38.300

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

RAN2

3GPP Series : 38 , Radio technology beyond LTE

5.3.1

4.7.6 P-TMSI reallocation procedure 4.7.6.0 General

A temporary mobile station identity for GPRS services, the Packet-TMSI (P-TMSI), is used for identification within the radio interface signalling procedures. The structure of the P-TMSI is specified in 3GPP TS 23.003[ Numbering, addressing and identification ] [10]. The P-TMSI has significance only within a routing area. Outside the routing area the P-TMSI has to be combined with the routing area identification (RAI) to provide for an unambiguous identity. The purpose of the P-TMSI reallocation procedure is to provide identity confidentiality, i.e. to protect a user against being identified and located by an intruder (see 3GPP TS 43.020[ Security related network functions ] [13], 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [74] and 3GPP TS 33.102[ 3G security; Security architecture ] [5a]). Usually, P-TMSI reallocation is performed at least at each change of a routing area (Such choices are left to the network operator). The reallocation of a P-TMSI is performed by the unique procedure defined in subclause 4.7.6. This procedure can only be initiated by the network in state GMM-REGISTERED. P-TMSI can also be implicitly reallocated in the attach or routing area updating procedures (see subclauses .1 and 4.7.5). The implicit reallocation of a P-TMSI is described in the corresponding subclauses. NOTE: Normally, the P-TMSI reallocation will take place in conjunction with another GMM procedure, e.g. at routing area updating (see 3GPP TS 29.002[ Mobile Application Part (MAP) specification ] [37]).

3GPP TS 24.008

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

CT WG1

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

4.7.6

10.5.2 MR-DC with 5GC

MN initiated SN Change The MN initiated SN change procedure is used to transfer a UE context from the source SN to a target SN and to change the SCG configuration in UE from one SN to another. The Secondary Node Change procedure always involves signalling over MCG SRB towards the UE. Figure 10.5.2-1: SN change procedure - MN initiated Figure 10.5.2-1 shows an example signalling flow for the SN Change initiated by the MN: 1/2. The MN initiates the SN change by requesting the target SN to allocate resources for the UE by means of the SN Addition procedure. The MN may include measurement results related to the target SN. If data forwarding is needed, the target SN provides data forwarding addresses to the MN. The target SN includes the indication of the full or delta RRC configuration. NOTE 1: The MN may trigger the MN-initiated SN Modification procedure (to the source SN) to retrieve the current SCG configuration and SN-associated QMC configuration information, and to allow provision of data forwarding related information before step 1. 2a. For SN terminated bearers using MCG resources, the MN provides Xn-U DL TNL address information in the Xn-U Address Indication message. 3. If the allocation of target SN resources was successful, the MN initiates the release of the source SN resources including a Cause indicating SCG mobility. The Source SN may reject the release. If data forwarding is needed the MN provides data forwarding addresses to the source SN. If direct data forwarding is used for SN terminated bearers, the MN provides data forwarding addresses as received from the target SN to source SN. Reception of the SN Release Request message triggers the source SN to stop providing user data to the UE. 4/5. The MN triggers the UE to apply the new configuration. The MN indicates the new configuration to the UE in the MN RRC reconfiguration message including the target SN RRC reconfiguration message. The UE applies the new configuration and sends the MN RRC reconfiguration complete message, including the SN RRC response message for the target SN, if needed. In case the UE is unable to comply with (part of) the configuration included in the MN RRC reconfiguration message, it performs the reconfiguration failure procedure. 6. If the RRC connection reconfiguration procedure was successful, the MN informs the target SN via SN Reconfiguration Complete message with the included SN RRC response message for the target SN, if received from the UE. 7. If configured with bearers requiring SCG radio resources the UE synchronizes to the target SN. 8. If PDCP termination point is changed for bearers using RLC AM, the source SN sends the SN Status Transfer message, which the MN sends then to the target SN, if needed. 9. If applicable, data forwarding from the source SN takes place. It may be initiated as early as the source SN receives the SN Release Request message from the MN. 10. The source SN sends the Secondary RAT Data Usage Report message to the MN and includes the data volumes delivered to and received from the UE as described in clause 10.11.2. NOTE 2: The order the SN sends the Secondary RAT Data Usage Report message and performs data forwarding with MN is not defined. The SN may send the report when the transmission of the related QoS flow is stopped. 11-15. If applicable, a PDU Session path update procedure is triggered by the MN. 16. Upon reception of the UE Context Release message, the source SN releases radio and C-plane related resources associated to the UE context. Any ongoing data forwarding may continue SN initiated SN Change The SN initiated SN change procedure is used to transfer a UE context from the source SN to a target SN and to change the SCG configuration in UE from one SN to another. Figure 10.5.2-2: SN change procedure - SN initiated Figure 10.5.2-2 shows an example signalling flow for the SN Change initiated by the SN: 1. The source SN initiates the SN change procedure by sending the SN Change Required message, which contains a candidate target node ID and may include the SCG configuration (to support delta configuration) and measurement results related to the target SN. For supporting QMC continuity during mobility, the SN Change Required message may contain the information about the QMC configurations at the source SN. 2/3. The MN requests the target SN to allocate resources for the UE by means of the SN Addition procedure, including the measurement results related to the target SN received from the source SN. If data forwarding is needed, the target SN provides data forwarding addresses to the MN. The target SN includes the indication of the full or delta RRC configuration. 3a. For SN terminated bearers using MCG resources, the MN provides Xn-U DL TNL address information in the Xn-U Address Indication message. 4/5. The MN triggers the UE to apply the new configuration. The MN indicates the new configuration to the UE in the MN RRC reconfiguration message including the SN RRC reconfiguration message generated by the target SN. The UE applies the new configuration and sends the MN RRC reconfiguration complete message, including the SN RRC response message for the target SN, if needed. In case the UE is unable to comply with (part of) the configuration included in the MN RRC reconfiguration message, it performs the reconfiguration failure procedure. 6. If the allocation of target SN resources was successful, the MN confirms the change of the source SN. If data forwarding is needed the MN provides data forwarding addresses to the source SN. If direct data forwarding is used for SN terminated bearers, the MN provides data forwarding addresses as received from the target SN to source SN. Reception of the SN Change Confirm message triggers the source SN to stop providing user data to the UE and, if applicable, to start data forwarding. 7. If the RRC connection reconfiguration procedure was successful, the MN informs the target SN via SN Reconfiguration Complete message with the included SN RRC response message for the target SN, if received from the UE. 8. The UE synchronizes to the target SN. 9. If PDCP termination point is changed for bearers using RLC AM, the source SN sends the SN Status Transfer message, which the MN sends then to the target SN, if needed. 10. If applicable, data forwarding from the source SN takes place. It may be initiated as early as the source SN receives the SN Change Confirm message from the MN. 11. The source SN sends the Secondary RAT Data Usage Report message to the MN and includes the data volumes delivered to and received from the UE as described in clause 10.11.2. NOTE 3: The order the SN sends the Secondary RAT Data Usage Report message and performs data forwarding with MN/target SN is not defined. The SN may send the report when the transmission of the related QoS flow is stopped. 12-16. If applicable, a PDU Session path update procedure is triggered by the MN. 17. Upon reception of the UE Context Release message, the source SN releases radio and C-plane related resources associated to the UE context. Any ongoing data forwarding may continue. MN initiated conditional SN Change The Conditional Secondary Node Change procedure is initiated by the MN for inter-SN CPC configuration and inter-SN CPC execution. Figure 10.5.2-3: Conditional SN change procedure - MN initiated Figure 10.5.2-3 shows an example signalling flow for the conditional SN Change initiated by the MN: 1/2. The MN initiates the conditional SN change by requesting the candidate SN(s) to allocate resources for the UE by means of the SN Addition procedure, indicating that the request is for CPAC. The MN also provides the candidate cells recommended by MN via the latest measurement results for the candidate SN(s) to choose and configure the SCG cell(s), provides the upper limit for the number of PSCells that can be prepared by the candidate SN. Within the list of cells as indicated within the measurement results indicated by the MN, the candidate SN decides the list of PSCell(s) to prepare (considering the maximum number indicated by the MN) and, for each prepared PSCell, the candidate SN decides other SCG SCells and provides the new corresponding SCG radio resource configuration to the MN in an NR RRCReconfiguration** message contained in the SN Addition Request Acknowledge message with the prepared PSCell ID(s). If data forwarding is needed, the candidate SN provides data forwarding addresses to the MN. The candidate SN includes the indication of the full or delta RRC configuration. The candidate SN can either accept or reject each of the candidate cells listed within the measurement results indicated by the MN, i.e. it cannot configure any alternative candidates. NOTE 4: The MN may trigger the MN-initiated SN Modification procedure (to the source SN) to retrieve the current SCG configuration and to allow provision of data forwarding related information before step 1. 2a. For SN terminated bearers using MCG resources, the MN provides Xn-U DL TNL address information in the Xn-U Address Indication message to the candidate SN(s). 3. The MN sends to the UE an RRCReconfiguration message including the CPC configuration, i.e. a list of RRCReconfiguration* messages and associated execution conditions, in which each RRCReconfiguration* message contains the SCG configuration in the RRCReconfiguration** message received from the candidate SN in step 2 and possibly an MCG configuration. Besides, the RRCReconfiguration message can also include an updated MCG configuration, e.g., to configure the required conditional measurements. 4. The UE applies the RRCReconfiguration message received in step 3, stores the CPC configuration and replies to the MN with an RRCReconfigurationComplete message. In case the UE is unable to comply with (part of) the configuration included in the RRCReconfiguration message, it performs the reconfiguration failure procedure. 4a. Upon receiving the MN RRCReconfigurationComplete message from the UE, the MN informs the source SN that the CPC has been configured via Xn-U Address Indication procedure, the source SN, if applicable, together with the Early Status Transfer procedure, starts early data forwarding. The PDCP SDU forwarding may take place during early data forwarding. NOTE 4a: Separate Xn-U Address Indication procedures may be invoked to provide different forwarding addresses of the prepared candidate target SNs. In this case, it is up to the MN and the source SN implementations to make sure that the EARLY STATUS TRANSFER message(s) from the source SN, if any, is forwarded to the right target destination. The Xn-U Address Indication procedure may further be invoked to indicate to the source SN to stop already initiated early data forwarding for some SN-terminated bearers if they are no longer subject to data forwarding due to the modification or cancellation of the prepared conditional SN change procedures. NOTE 4b: For the early transmission of MN terminated split/SCG bearers, the MN forwads the PDCP PDU to the candidate SN(s). 5. The UE starts evaluating the execution conditions. If the execution condition of one candidate PSCell is satisfied, the UE applies RRCReconfiguration* message corresponding to the selected candidate PSCell, and sends an MN RRCReconfigurationComplete* message, including an NR RRCReconfigurationComplete** message for the selected candidate PSCell, and information enabling the MN to identify the SN of the selected candidate PSCell. 6a-6c. The MN triggers the MN initiated SN Release procedure to inform the source SN to stop providing user data to the UE, and if applicable, triggers the Xn-U Address Indication procedure to inform the source SN the address of the SN of the selected candidate PSCell, to start late data forwarding. 7a-7c. If the RRC connection reconfiguration procedure was successful, the MN informs the SN of the selected candidate PSCell via SN Reconfiguration Complete message, including the SN RRCReconfigurationComplete** message. The MN sends the SN Release Request message(s) to cancel CPC in the other candidate SN(s), if configured. The other candidate SN(s) acknowledges the release request. 8. The UE synchronizes to the PSCell indicated in the RRCReconfiguration* message applied in step 5. 9a-9b. If PDCP termination point is changed for bearers using RLC AM, the source SN sends the message, which the MN sends then to the SN of the selected candidate PSCell, if needed. 10. If applicable, data forwarding from the source SN takes place. It may be initiated as early as the source SN receives the early data forwarding address in step 4a. 11. The source SN sends the Secondary RAT Data Usage Report message to the MN and includes the data volumes delivered to and received from the UE as described in clause 10.11.2. NOTE 5: The order the SN sends the Secondary RAT Data Usage Report message and performs data forwarding with MN is not defined. The SN may send the report when the transmission of the related QoS flow is stopped. 12-16. If applicable, a PDU Session path update procedure is triggered by the MN. 17. Upon reception of the UE Context Release message, the source SN releases radio and C-plane related resources associated to the UE context. Any ongoing data forwarding may continue. SN initiated conditional SN Change The SN initiated conditional SN change procedure is used for inter-SN CPC configuration and inter-SN CPC execution. The SN initiated conditional SN change procedure may also be initiated by the source SN, to modify the existing SN initiated inter-SN CPC configuration, or to trigger the release of the candidate SN by cancellation of all the prepared PSCells at the candidate SN and releasing the CPC related UE context at the candidate SN. NOTE 5a0: To modify or release an existing intra-SN CPC configuration, the source SN triggers an SN initiated Conditional SN Modification (with or without SRB3) without MN involvement, as specified in 10.3. Figure 10.5.2-4: Conditional SN change procedure - SN initiated Figure 10.5.2-4 shows an example signalling flow for the conditional SN Change initiated by the SN: 1. The source SN initiates the conditional SN change procedure by sending the SN Change Required message, which contains a CPC initiation indication. The message also contains candidate node ID(s) and may include the SCG configuration (to support delta configuration), and contains the measurements results which may include cells that are not CPC candidates. The message also includes a list of proposed PSCell candidates recommended by the source SN, including execution conditions, the upper limit for the number of PSCells that can be prepared by each candidate SN, and may also include the SCG measurement configurations for CPC (e.g. measurement ID(s) to be used for CPC). 2/3. The MN requests each candidate SN(s) to allocate resources for the UE by means of the SN Addition procedure(s), indicating the request is for CPAC, and the measurements results which may include cells that are not CPC candidates received from the source SN to the candidate SN, and indicating a list of proposed PSCell candidates received from the source SN, but not including execution conditions. Within the list of PSCells suggested by the source SN, the candidate SN decides the list of PSCell(s) to prepare (considering the maximum number indicated by the MN) and, for each prepared PSCell, the candidate SN decides SCG SCells and provides the new corresponding SCG radio resource configuration to the MN in an NR RRCReconfiguration** message contained in the SgNB Addition Request Acknowledge message. If data forwarding is needed, the candidate SN provides data forwarding addresses to the MN. The candidate SN includes the indication of full or delta RRC configuration, and the list of prepared PSCell IDs to the MN. The candidate SN can either accept or reject each of the candidate cells suggested by the source SN, i.e., it cannot configure any alternative candidates. 3a. For SN terminated bearers using MCG resources, the MN provides Xn-U DL TNL address information in the Xn-U Address Indication message to the candidate SN(s). 4/5. The MN may indicate the candidate PSCells accepted by each candidate SN to the source SN via SN Modification Request message before it configures the UE, e.g., when not all candidate PSCells were accepted by the candidate SN(s). If the MN does not send such indication, step 4 and 5 are skipped. If requested, the source SN sends an SN Modification Request Acknowledge message and if needed, provides an updated measurement configurations and/or the execution conditions to the MN. 6. The MN sends to the UE an RRCReconfiguration message including the CPC configuration, i.e. a list of RRCReconfiguration* messages and associated execution conditions, in which each RRCReconfiguration* message contains the SCG configuration in the RRCReconfiguration** message received from the candidate SN in step 3 and possibly an MCG configuration. Besides, the RRCReconfiguration message can also include an updated MCG configuration, as well as the NR RRCReconfiguration*** message generated by the source SN, e.g., to configure the required conditional measurements. 7. The UE applies the RRCReconfiguration message received in step 6, stores the CPC configuration and replies to the MN with an RRCReconfigurationComplete message, which can include an NR RRCReconfigurationComplete*** message. In case the UE is unable to comply with (part of) the configuration included in the RRCReconfiguration message, it performs the reconfiguration failure procedure. 8. If an SN RRC response message is included, the MN informs the source SN with the SN RRCReconfigurationComplete*** message via SN Change Confirm message. If step 4 and 5 are skipped, the MN will indicate the candidate PSCells accepted by each candidate SN to the source SN in the SN Change Confirm message. The MN sends the SN Change Confirm message towards the source SN to indicate that CPC is prepared, and in such case the source SN continues providing user data to the UE. If early data forwarding is applied, the MN informs the source SN the data forwarding addresses as received from the candidate SN(s), the source SN, if applicable, together with the Early Status Transfer procedure, starts early data forwarding. The PDCP SDU forwarding may take place during early data forwarding. In case multiple candidate SNs are prepared, the MN includes a list of Target SN ID and list of data forwarding addresses to the source SN. NOTE 5a: The Xn-U Address Indication procedure may further be invoked to indicate to the source SN to stop already initiated early data forwarding for some PDCP SDUs if they are no longer subject to data forwarding due to the modification or cancellation of the prepared conditional PSCell change. NOTE 5b: For the early transmission of MN terminated split/SCG bearers, the MN forwads the PDCP PDU to the candidate SN(s). 9a-9d. The source SN may send the SN Modification Required message to trigger an update of CPC execution condition and/or corresponding SCG measurement configuration for CPC. In such case in step 9b, the MN reconfigures the UE and in step 9c the UE responds with RRCReconfigurationComplete, similarly as in steps 6 and 7. 10. The UE starts evaluating the execution conditions. If the execution condition of one candidate PSCell is satisfied, the UE applies RRCReconfiguration* message corresponding to the selected candidate PSCell, and sends an RRCReconfigurationComplete* message, including an RRCReconfigurationComplete** message for the selected candidate PSCell, and information enabling the MN to identify the SN of the selected candidate PSCell. 11a-11c. The MN triggers the MN initiated SN Release procedure to inform the source SN to stop providing user data to the UE, and if applicable, triggers the Xn-U Address Indication procedure to inform the source SN the address of the SN of the selected candidate PSCell to start late data forwarding. 12a-12c. If the RRC connection reconfiguration procedure was successful, the MN informs the SN of the selected candidate PSCell via SN Reconfiguration Complete message, including the SN RRCReconfigurationComplete** message. The MN sends the SN Release Request message(s) to cancel CPC in the other candidate SN(s), if configured. The other candidate SN(s) acknowledges the release request. 13. The UE synchronizes to the PSCell indicated in the RRCReconfiguration* message applied in step 10. 14. If PDCP termination point is changed for bearers using RLC AM, the source SN sends the SN Status Transfer message, which the MN sends then to the SN of the selected candidate PSCell, if needed. 15. If applicable, data forwarding from the source SN takes place. It may be initiated as early as the source SN receives the data forwarding address related information from the MN. 16. The source SN sends the Secondary RAT Data Usage Report message to the MN and includes the data volumes delivered to and received from the UE as described in clause 10.11.2. NOTE 6: The order the SN sends the Secondary RAT Data Usage Report message and performs data forwarding with MN/target SN is not defined. The SN may send the report when the transmission of the related QoS flow is stopped. 17-21. If applicable, a PDU Session path update procedure is triggered by the MN. 22. Upon reception of the UE Context Release message, the source SN releases radio and C-plane related resources associated to the UE context. Any ongoing data forwarding may continue.

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

10.5.2

6.8.9.2 GSM security context

A GSM security context is only established for GSM subscribers. At the network side, two cases are distinguished: a) In case of a PS intra SGSN handover the SGSN derives UMTS cipher/integrity keys CK and IK from the 64-bit GSM cipher key Kc (using the conversion functions c4 and c5) agreed during the latest GSM AKA procedure and sends them to the target RNC or BSC. b) In case of a PS Inter SGSN handover the initial SGSN sends the 64-bit GSM cipher key Kc agreed during the latest GSM AKA procedure to the new SGSN controlling the target RNC or BSC. The new SGSN becomes the new anchor point for the service. The new SGSN stores the 64-bit GSM cipher key Kc and derives the UMTS cipher/integrity keys CK and IK which are then forwarded to the target RNC or BSC. At the user side, in all cases, the ME derives the UMTS cipher/integrity keys CK and IK from the 64-bit GSM cipher key Kc (using the conversion functions c4 and c5) received from the SIM during the latest GSM AKA procedure and applies them.

3GPP TS 33.102

3G security; Security architecture

SA WG3

3GPP Series : 33 , Security aspects

6.8.9.2

4.10 Interworking with ePDG connected to EPC

In order to interwork with ePDG connected to EPC, the UE shall operate as specified in either subclause 4.8.2.3 or subclause 4.8.3. Which subclause the UE follows is chosen by the UE irrespective of the interworking without N26 interface indicator. The UE shall not attempt to transfer PDU sessions with PDU session type "Ethernet" or "Unstructured" to an ePDG connected to EPC. NOTE 1: PDU sessions with PDU session type "Ethernet" or "Unstructured" cannot be transferred to an ePDG connected to EPC because PDN connections with PDN type "non-IP" or PDN type "Ethernet" are not supported over ePDG connected to EPC.

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

9.11.2.17 Service-level-AA pending indication

The purpose of the Service-level-AA pending indication information element is to provide an indication that the service level authentication and authorization procedure is to be performed. The Service-level-AA pending indication information element is coded as shown in figure 9.11.2.17.1 and table 9.11.2.17.1. The Service-level-AA pending indication information element is a type 1 information element. Figure 9.11.2.17.1: Service-level-AA pending indication Table 9.11.2.17.1: Service-level-AA pending indication

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

4.8.2 Single-registration mode 4.8.2.1 General

If the UE receives the indication that "interworking without N26 interface not supported" (see 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]), the UE operates as described in subclause 4.8.2.2. If the UE receives the indication that "interworking without N26 interface supported" and a) the UE does not support dual-registration mode; or b) the UE supporting dual-registration mode determines to operate in single-registration mode, the UE operates as described in subclause 4.8.2.3.

3GPP TS 24.501

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

CT WG1

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

4.8.2

5.2.2.4.9 Actions upon reception of SIB8

Upon receiving the SIB8 the UE shall: 1> if the SIB8 contains a complete warning message and the complete geographical area coordinates (if any): 2> forward the received warning message, messageIdentifier, serialNumber, dataCodingScheme and the geographical area coordinates (if any) to upper layers; 2> continue reception of SIB8; 1> else: 2> if the received values of messageIdentifier and serialNumber are the same (each value is the same) as a pair for which a warning message and the geographical area coordinates (if any) are currently being assembled: 3> store the received warningMessageSegment; 3> store the received warningAreaCoordinatesSegment (if any); 3> if all segments of a warning message and geographical area coordinates (if any) have been received: 4> assemble the warning message from the received warningMessageSegment; 4> assemble the geographical area coordinates from the received warningAreaCoordinatesSegment (if any); 4> forward the received warning message, messageIdentifier, serialNumber, dataCodingScheme and geographical area coordinates (if any) to upper layers; 4> stop assembling a warning message and geographical area coordinates (if any) for this messageIdentifier and serialNumber and delete all stored information held for it; 3> continue reception of SIB8; 2> else if the received values of messageIdentifier and/or serialNumber are not the same as any of the pairs for which a warning message is currently being assembled: 3> start assembling a warning message for this messageIdentifier and serialNumber pair; 3> start assembling the geographical area coordinates (if any) for this messageIdentifier and serialNumber pair; 3> store the received warningMessageSegment; 3> store the received warningAreaCoordinatesSegment (if any); 3> continue reception of SIB8; The UE should discard warningMessageSegment and warningAreaCoordinatesSegment (if any) and the associated values of messageIdentifier and serialNumber for SIB8 if the complete warning message and the geographical area coordinates (if any) have not been assembled within a period of 3 hours. NOTE: The number of warning messages that a UE can re-assemble simultaneously is a function of UE implementation.

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

5.2.2.4.9

5.8.2.2.4 IPv6 Prefix Delegation via DHCPv6

Optionally, a single network prefix shorter than the default /64 prefix may be assigned to a PDU Session. In this case, the /64 default prefix used for IPv6 stateless autoconfiguration will be allocated from this network prefix; the remaining address space from the network prefix can be delegated to the PDU Session using prefix delegation after the PDU Session establishment and IPv6 prefix allocation via IPv6 stateless address autoconfiguration as defined in clause 5.8.2.2.3. Depending on configuration, the SMF may obtain the prefix from a locally provisioned pool, from the PSA UPF or from the external DN. The address space provided is maintained as an IPv6 address space pool available to the PDU Session for DHCPv6 IPv6 prefix requests with the exclusion of the IPv6 prefix that is allocated to the PDU Session during PDU Session establishment as defined in clause 5.8.2.2.3. The total IPv6 address space available for the PDU Session (UE PDU Session prefix and UE PDU Session IPv6 address space pool) shall be possible to aggregate into one IPv6 prefix that will represent all IPv6 addresses that the UE may use. If the UE had indicated that it supports prefix exclusion and the prefix to be delegated to the UE includes the /64 prefix that was allocated to the PDU Session, the SMF shall utilise the prefix exclusion feature as specified for DHCPv6 Prefix Delegation in IETF RFC 6603 [162]. NOTE: Support of the IPv6 prefix delegation in the SMF is assumed to be ensured by the operator e.g. by configuring specific DNN/S-NSSAI for PDU Sessions that are used by UEs that utilize IPv6 prefix delegation. The UE uses DHCPv6 to request additional IPv6 prefixes (i.e. prefixes in addition to the default prefix) from the SMF after completing stateless IPv6 address autoconfiguration procedures. The UE acts as a "Requesting Router" as described in IETF RFC 8415 [163] and inserts one or more IA_PD option(s) into a DHCPv6 Solicit message sent from the UE to the SMF via the user plane and the UPF. The SMF acts as the DHCP server and fulfils the role of a "Delegating Router" according to IETF RFC 8415 [163]. The UE optionally includes the RAPID_COMMIT option in the DHCPv6 Solicit message to trigger two-message DHCPv6 procedure instead of the four-message DHCPv6 procedure. The UE shall include OPTION_PD_EXCLUDE option code in an OPTION_ORO option to indicate support for prefix exclusion. In response to the DHCPv6 Solicit message, the UE receives a DHCPv6 Reply message with one or more IA_PD prefix(es) for every IA_PD option that it sent in the DHCPv6 Solicit message. The SMF delegates a prefix excluding the default prefix with help of OPTION_PD_EXCLUDE. Prefix exclusion procedures shall follow IETF RFC 6603 [162]. For scenarios with RG connecting to 5GC, additional feature for IPv6 Prefix Delegation via DHCPv6 is defined in TS 23.316[ Wireless and wireline convergence access support for the 5G System (5GS) ] [84].

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.8.2.2.4

13.2.3.3 NF API data-type placement mapping

Each NF API data-type placement mapping shall contain the following: - Which IEs contain data of the type 'SUPI' or type 'NAI'. - Which IEs contain data of the type 'authentication vector’. - Which IEs contain data of the type 'location data'. - Which IEs contain data of the type 'cryptographic material'. - Which IEs contain data of the type 'authorization token'. The location of the IEs refers to the location of the IEs after the SEPP has rewritten the message for transmission over N32-f. An NF API data-type placement mapping shall furthermore contain data that identifies the NF API, namely - The name of the NF; - The API version; - An identifier for the NF API data-type placement mapping; - The NF’s 3GPP Release version. NOTE: Larger networks can contain multiple NFs with the same API, e.g. three AMFs. The NF API policy applies to all NFs with the same API. The NF API data-type placement mapping shall reside in the SEPP.

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

13.2.3.3

8.9.13 IP Address Allocation for IAB-nodes

NOTE: The general principles and procedures described in this clause does not apply to ng-eNB. An IAB-node may obtain IP address(es) either from the IAB-donor or from the OAM system. The IP address(es) is(are) used by the IAB-node for F1 and non-F1 traffic exchange via the backhaul. In case IPsec tunnel mode is used to protect this F1 and non-F1 traffic, the IP address(es) refer to the outer tunnel addresses. The allocation of the inner tunnel IP address(es) is outside of 3GPP scope. NOTE: The non-F1 traffic of an IAB-node includes all IP traffic that is not used for the management or transport of F1-C as specified in TS 38.472[ NG-RAN; F1 signalling transport ] [26] or F1-U as specified in TS 38.474[ NG-RAN; F1 data transport ] [7]. The non-F1 traffic may include, e.g., OAM traffic if it is transferred using the BH RLC channel. In case of IAB-donor-based IP address allocation, the IP address(es) is(are) allocated by the IAB-donor-CU or IAB-donor-DU. In both cases, the IAB-node requests the IP address(es) via RRC from the IAB-donor-CU. It includes a separate IP address request for each usage, where the usages defined are all traffic, F1-U, F1-C and non-F1. The IAB-donor-CU may initiate the IAB TNL Address Allocation procedure to obtain IP addresses from the IAB-donor-DU. The IAB-donor-CU sends the IP addresses allocated for each usage to the IAB-node via RRC. In case of IAB inter-CU topology management, the F1-terminating IAB-donor-CU may obtain the IP addresses for each usage in the non-F1-terminating IAB-donor-CU’s topology from the non-F1-terminating IAB-donor-CU for the boundary IAB-node and the descendant IAB-nodes of the boundary IAB-node. The IAB-node may be allocated one or multiple IPv6 addresses or one 64-bit IPv6 prefix for each usage and/or one or multiple IPv4 addresses for each usage. Each allocated IP address/IPv6 prefix is unique within the IAB network and routable from the wireline network. In case of OAM-based IP address allocation, the IAB-node informs the IAB-donor-CU via an UL RRC message about the IP address(es) it received for each purpose. This occurs before the IAB node uses the IP address(es) for UL and/or DL traffic. The IAB-donor-CU configures the IAB-donor-DU with mappings between IP header fields and L2 parameters (BAP Routing ID, BH RLC channels) used for DL traffic. Each mapping configuration may hold an IPv4 address, IPv6 address or a 64-bit IPv6 prefix. In case of two mapping entries matching the same IP header where one holds an IPv6 prefix and the other holds a full IPv6 address, the one with full IPv6 address takes precedence at the IAB-donor-DU. In case of IAB-donor-allocated IP addresses, the IAB-node’s IP address(es) can be updated using DL RRC signalling. For F1-C traffic transfer for NSA IAB, the LTE leg and NR leg should use separate IP address pairs {IAB-DU’s IP address, IAB-donor-CU’s IP address}. How the IAB-DU gets the remote IP end point(s) and its own IP address for LTE leg is not specified in this release.

3GPP TS 38.401

NG-RAN; Architecture description

RAN3

3GPP Series : 38 , Radio technology beyond LTE

8.9.13

6.4.2.6 Abnormal cases on the network side

The following abnormal cases can be identified: a) Expiry of timer T3485: On the first expiry of the timer T3485, the MME shall resend the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST and shall reset and restart timer T3485. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3485, the MME shall abort the procedure, release any resources allocated for this activation and enter the state BEARER CONTEXT INACTIVE. b) Collision of UE requested PDN disconnect procedure and dedicated EPS bearer context activation procedure: When the MME receives a PDN DISCONNECT REQUEST message during the dedicated EPS bearer context activation procedure, and the EPS bearer to be activated belongs to the PDN connection the UE wants to disconnect, the MME shall terminate the dedicated bearer context activation procedure locally, release any resources related to this procedure and proceed with the PDN disconnect procedure.

3GPP TS 24.301

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

CT WG1

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

6.4.2.6

8.102 MBMS Flags

MBMS Flags is coded as depicted in Figure 8.102-1. Figure 8.102-1: MBMS Flags The following bits within Octet 5 indicate: - Bit 1 – MSRI (MBMS Session Re-establishment Indication): if set to 1, this flag indicates that the MBMS Session Start Request message is used to re-establish an MBMS session (see 3GPP TS 23.007[ Restoration procedures ] [13]) - Bit 2 – LMRI (Local MBMS Bearer Context Release Indication): if set to 1, this flag indicates that the MBMS Session Stop Request message is used to release the MBMS Bearer Context locally in the MME/SGSN (see 3GPP TS 23.007[ Restoration procedures ] [13]); - Bit 3 to 8 – Spare, for future use and set to zero.

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

8.8.4.2 TDD

For the parameters specified in Table 8.8.4.2-1 the average probability of a missed downlink scheduling grant (Pm-dsg) shall be below the specified value in Table 8.8.4.2-2. The purpose of this test is to verify the localized EPDCCH performance, when the EPDCCH transmission in the serving cell is interfered by the CRS of the interfering cells, applying the CRS interference model defined in clause B.6.5. In Table 8.8.4.2-1, Cell 1 is the serving cell, and Cell 2 and Cell 3 are the aggressor cells. The downlink physical setup is in accordance with Annex C.3.2 for each of Cell 1, Cell 2 and Cell 3, respectively. The CRS assistance information [7] is provided and includes Cell 2 and Cell 3. Table 8.8.4.2-1: Test Parameters for EPDCCH Table 8.8.4.2-2: Minimum performance for EPDCCH for enhanced downlink control channel performance requirements Type A

3GPP TS 36.101

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

RAN4

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

8.8.4.2

6.9.1 Description

The UE (remote UE) can connect to the network directly (direct network connection), connect using another UE as a relay UE (indirect network connection), or connect using both direct and indirect connections. Relay UEs can be used in many different scenarios and verticals (inHome, SmartFarming, SmartFactories, Public Safety and others). In these cases, the use of relays UEs can be used to improve the energy efficiency and coverage of the system. Remote UEs can be anything from simple wearables, such as sensors embedded in clothing, to a more sophisticated wearable UE monitoring biometrics. They can also be non-wearable UEs that communicate in a Personal Area Network such as a set of home appliances (e.g. smart thermostat and entry key), or the electronic UEs in an office setting (e.g. smart printers), or a smart flower pot that can be remotely activated to water the plant. When a remote UE is attempting to establish an indirect network connection, there might be several relay UEs that are available in proximity and supporting selection procedures of an appropriate relay UE among the available relay UEs is needed. Indirect network connection covers the use of relay UEs for connecting a remote UE to the 3GPP network. There can be one or more relay UE(s) (more than one hop) between the network and the remote UE. A ProSe UE-to-UE Relay can also be used to connect two remote Public Safety UEs using direct device connection. There can be one or more ProSe UE-to-UE Relay(s) (more than one hop) between the two remote Public Safety UEs.

3GPP TS 22.261

Service requirements for the 5G system

SA WG1

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

6.9.1

10.5.6.16 Enhanced network service access point identifier

The purpose of the Enhanced network service access point identifier information element is to identify the service access point that is used at layer 3. The Enhanced network service access point identifier is a type 3 information element with a length of 2 octets. The value part of an Enhanced network service access point identifier information element is coded as shown in figure 10.5.157/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.171/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.157/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Enhanced network service access point identifier information element Table 10.5.171/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Enhanced network service access point identifier information element

3GPP TS 24.008

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

CT WG1

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

10.5.6.16

9.2.3.1 Overview

Network controlled mobility applies to UEs in RRC_CONNECTED and is categorized into two types of mobility: cell level mobility and beam level mobility. Beam level mobility includes intra-cell beam level mobility and inter-cell beam level mobility. Cell Level Mobility requires explicit RRC signalling to be triggered, i.e. handover. For inter-gNB handover, the signalling procedures consist of at least the following elemental components illustrated in Figure 9.2.3.1-1: Figure 9.2.3.1-1: Inter-gNB handover procedures 1. The source gNB initiates handover and issues a HANDOVER REQUEST over the Xn interface. 2. The target gNB performs admission control and provides the new RRC configuration as part of the HANDOVER REQUEST ACKNOWLEDGE. 3. The source gNB provides the RRC configuration to the UE by forwarding the RRCReconfiguration message received in the HANDOVER REQUEST ACKNOWLEDGE. The RRCReconfiguration message includes at least cell ID and all information required to access the target cell so that the UE can access the target cell without reading system information. For some cases, the information required for contention-based and contention-free random access can be included in the RRCReconfiguration message. The access information to the target cell may include beam specific information, if any. 4. The UE moves the RRC connection to the target gNB and replies with the RRCReconfigurationComplete. NOTE 1: User Data can also be sent in step 4 if the grant allows. In case of DAPS handover, the UE continues the downlink user data reception from the source gNB until releasing the source cell and continues the uplink user data transmission to the source gNB until successful random access procedure to the target gNB. Only source and target PCell are used during DAPS handover. CA, DC, SUL, multi-TRP, EHC, CHO, UDC, NR sidelink configurations and V2X sidelink configurations are released by the source gNB before the handover command is sent to the UE and are not configured by the target gNB until the DAPS handover has completed (i.e. at earliest in the same message that releases the source PCell). The handover mechanism triggered by RRC requires the UE at least to reset the MAC entity and re-establish RLC, except for DAPS handover, where upon reception of the handover command, the UE: - Creates a MAC entity for target; - Establishes the RLC entity and an associated DTCH logical channel for target for each DRB configured with DAPS; - For each DRB configured with DAPS, reconfigures the PDCP entity with separate security and ROHC functions for source and target and associates them with the RLC entities configured by source and target respectively; - Retains the rest of the source configurations until release of the source. The cell switch mechanism triggered by MAC, (i.e., LTM cell switch) requires the UE at least to reset the MAC entity. RLC handling depends on the network configuration. NOTE 2: Void. NOTE 3: Void. RRC managed handovers with and without PDCP entity re-establishment are both supported. For DRBs using RLC AM mode, PDCP can either be re-established together with a security key change or initiate a data recovery procedure without a key change. For DRBs using RLC UM mode, PDCP can either be re-established together with a security key change or remain as it is without a key change. For SRBs, PDCP can either remain as it is, discard its stored PDCP PDUs/SDUs without a key change or be re-established together with a security key change. Data forwarding, in-sequence delivery and duplication avoidance at handover can be guaranteed when the target gNB uses the same DRB configuration as the source gNB. Timer based handover failure procedure is supported in NR. RRC connection re-establishment procedure is used for recovering from handover failure except in certain CHO, DAPS handover or LTM cell switch scenarios: - When DAPS handover fails, the UE falls back to the source cell configuration, resumes the connection with the source cell, and reports DAPS handover failure via the source without triggering RRC connection re-establishment if the source link has not been released. - When initial CHO execution attempt fails or HO fails, the UE performs cell selection, and if the selected cell is a CHO candidate and if network configured the UE to try CHO after handover/CHO failure, then the UE attempts CHO execution once, otherwise re-establishment is performed. - When initial LTM execution attempt fails or HO fails, the UE performs cell selection and if the selected cell is an LTM candidate cell and if network configured the UE to try LTM after LTM execution failure, then the UE attempts LTM execution once, otherwise re-establishment is performed. DAPS handover for FR2 to FR2 case is not supported in this release of the specification. The handover of the IAB-MT in SA mode follows the same procedure as described for the UE. After the backhaul has been established, the handover of the IAB-MT is part of the intra-CU or inter-CU topology adaptation procedures defined in TS 38.401[ NG-RAN; Architecture description ] [4]. Modifications to the configuration of BAP sublayer and higher protocol layers above the BAP sublayer are described in TS 38.401[ NG-RAN; Architecture description ] [4]. The handover of the mobile IAB-MT follows the same procedure as described for the UE. After the backhaul has been established, the handover of the mobile IAB-MT is part of the mobile IAB-MT migration procedure defined in TS 38.401[ NG-RAN; Architecture description ] [4]. Beam Level Mobility does not require explicit RRC signalling to be triggered. Beam level mobility can be within a cell, or between cells, the latter is referred to as inter-cell beam management (ICBM). For ICBM, a UE can receive or transmit UE dedicated channels/signals via a TRP associated with a PCI different from the PCI of a serving cell, while non-UE-dedicated channels/signals can only be received via a TRP associated with a PCI of the serving cell. The gNB provides via RRC signalling the UE with measurement configuration containing configurations of SSB/CSI resources and resource sets, reports and trigger states for triggering channel and interference measurements and reports. In case of ICBM, a measurement configuration includes SSB resources associated with PCIs different from the PCI of a serving cell. Beam Level Mobility is then dealt with at lower layers by means of physical layer and MAC layer control signalling, and RRC is not required to know which beam is being used at a given point in time. SSB-based Beam Level Mobility is based on the CD-SSB associated to the initial DL BWP and can be configured for the initial DL BWPs, for DL BWPs containing the CD-SSB associated to the initial DL BWP, and if supported, for DL BWPs not containing the CD-SSB associated to the initial DL BWP. SSB-based Beam Level Mobility can be also performed based on an NCD-SSB, if configured for the active DL BWP. For other DL BWPs, Beam Level Mobility can only be performed based on CSI-RS, if configured for the active DL BWP.

3GPP TS 38.300

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

RAN2

3GPP Series : 38 , Radio technology beyond LTE

9.2.3.1

4.15.6.7.3 Service specific parameter provisioning by AF to VPLMN

Figure 4.15.6.7.3-1 shows procedure for service specific parameter provisioning by the AF to VPLMN. Figure 4.15.6.7.3-1: Service specific information provisioning by AF to VPLMN 0a. Same as in step 0a of Figure 4.15.6.7.2-1. 0b-0c. The V-PCF may request to V-UDR on changes in UE policy information and H-PCF may subscribe to H-UDR. 1-2. Steps 1-2 of Figure 4.15.6.7.2-1 apply with the following differences: - The AF and NEF belong to the VPLMN. The AF may belong to third party with agreement with VPLMN. - When the AF provides application guidance on URSP Rule determination to the VPLMN, it will target "PLMN ID(s) of inbound roamers". The NEF in the VPLMN rejects any request for a GPSI or an External-Group-ID of a different PLMN. 3-5. Steps 3-5 of Figure 4.15.6.7.2-1 apply with the following differences: - AF, NEF and UDR belong to VPLMN. The AF may belong to third party with agreement with VPLMN. - The UDR in the VPLMN notifies the V-PCF(s) that have subscribed to the reception of application guidance on URSP determination. - In step 5, the V-PCF receives updates on application guidance on URSP determination for the PLMN ID of a SUPI that has a UE Policy Association established. The PLMN ID of the SUPI is included in the target "PLMN ID(s) of inbound roamers" in step 2. In this case, the V-PCF checks whether application guidance on URSP determination applies for the SUPI as specified in clause 6.1.2.2.4 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. 5a. The V-PCF sends the Service Parameters including the mapped HPLMN S-NSSAI values to the H-PCF and subscribes to the result of the delivery of UE Policies if the delivery result was requested by the AF, using the event reporting on "Notification on outcome of UE Policies delivery" described in clause 6.1.3.18 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. NOTE: The AMF determines whether LBO is allowed and performs SMF selection to select the SMF in VPLMN for LBO case as described in clause 6.3.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The H-PCF requests V-PCF to notify the result of UE policy delivery to the UE. 6. The H-PCF generates new or updated URSP Rules considering the Service Parameters received from the V-PCF in step 5a as specified in clause 6.1.2.2.4 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. 7-8. Steps 7-8 of Figure 4.15.6.7.2-1 apply with the following differences: - Notification is sent from V-PCF to the AF belonging to the VPLMN or third party with agreement with VPLMN.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.15.6.7.3

4.8.1.1 Mean processor usage

a) This measurement provides the mean usage of each key processor during the granularity period. Each equipment may have more than one key processor, how to indentify key processor is vendor specific. b) SI. c) This measurement is obtained by sampling at a pre-defined interval the usage of the processor and then taking the arithmetic mean for each key processor. d) Each measurement is an integer value (Unit: %). e) EQPT.MeanProcessorUsage.ProcessorID where ProcessorID identifies the key processor of this equipment, the format of ProcessorID is vendor specific. f) ManagedElement. g) Valid for packet switched traffic. h) EPS.

3GPP TS 32.425

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

SA WG5

3GPP Series : 32 , OAM&P and Charging

4.8.1.1

10.5.7.3 GPRS Timer

The purpose of the GPRS timer information element is to specify GPRS specific timer values, e.g. for the READY timer. The GPRS timer is a type 3 information element with 2 octets length. The GPRS timer information element is coded as shown in figure 10.5.146/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.172/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.146/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : GPRS Timer information element Table 10.5.172/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : GPRS Timer 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.7.3

5.3.2.2 UTRAN/GERAN Initial Attach

When a UE attaches to UTRAN/GERAN, it executes the normal attach procedure as defined in TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7]. When the UE needs an IP address, it initiates PDP context activation procedure as defined in TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7]. This procedure along with PDP context activation is also used to establish the first PDN connection over UTRAN/GERAN when the UE already has active PDN connections over a non-3GPP access network and wants to establish simultaneous PDN connections to different APNs over multiple accesses.

3GPP TS 23.401

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

SA WG2

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

5.3.2.2

5.6A.1 Channel bandwidths per operating band for CA

The requirements for carrier aggregation in this specification are defined for carrier aggregation configurations with associated bandwidth combination sets. For inter-band carrier aggregation, a carrier aggregation configuration is a combination of operating bands, each supporting a carrier aggregation bandwidth class. For intra-band contiguous carrier aggregation, a carrier aggregation configuration is a single operating band supporting a carrier aggregation bandwidth class. For each carrier aggregation configuration, requirements are specified for all bandwidth combinations contained in a bandwidth combination set, which is indicated per supported band combination in the UE radio access capability. A UE can indicate support of several bandwidth combination sets per band combination. Requirements for intra-band contiguous carrier aggregation are defined for the carrier aggregation configurations and bandwidth combination sets specified in Table 5.6A.1-1. Requirements for inter-band carrier aggregation are defined for the carrier aggregation configurations and bandwidth combination sets specified in Table 5.6A.1-2, Table 5.6A.1-2a, Table 5.6A.1-2b and Table 5.6A.1-2c. Requirements for intra-band non-contiguous carrier aggregation are defined for the carrier aggregation configurations and bandwidth combination sets specified in Table 5.6A.1-3. The DL component carrier combinations for a given CA configuration shall be symmetrical in relation to channel centre unless stated otherwise in Table 5.6A.1-1, Table 5.6A.1-2, Table 5.6A.1-2a, Table 5.6A.1-2b and Table 5.6A.1-2c. Table 5.6A.1-1: E-UTRA CA configurations and bandwidth combination sets defined for intra-band contiguous CA Table 5.6A.1-2: E-UTRA CA configurations and bandwidth combination sets defined for inter-band CA (two bands) Table 5.6A.1-2a: E-UTRA CA configurations and bandwidth combination sets defined for inter-band CA (three bands) Table 5.6A.1-2b: E-UTRA CA configurations and bandwidth combination sets defined for inter-band CA (four bands) Table 5.6A.1-2c: E-UTRA CA configurations and bandwidth combination sets defined for inter-band CA (five bands) Table 5.6A.1-2d: E-UTRA CA configurations and bandwidth combination sets defined for inter-band CA (six bands) Table 5.6A.1-3: E-UTRA CA configurations and bandwidth combination sets defined for non-contiguous intra-band CA (with two sub-blocks) Table 5.6A.1-4: E-UTRA CA configurations and bandwidth combination sets defined for non-contiguous intra-band CA (with three sub-blocks) Table 5.6A.1-5: E-UTRA CA configurations and bandwidth combination sets defined for non-contiguous intra-band CA (with four sub-blocks)

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

5.6A.1

5.3.12 Handling of local emergency numbers

The additional requirements in subclause 5.3.12A apply to a UE supporting registration or attach procedures via 3GPP access and registration procedures via non-3GPP access. In case of PLMN, the network may send a local emergency numbers list or an extended local emergency numbers list or both, in the REGISTRATION ACCEPT message, by including the Emergency number list IE and the Extended emergency number list IE, respectively. The Local emergency numbers list can be updated as described in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15], subclause 5.3.7. In case of SNPN, the network may send an extended local emergency numbers list, in the REGISTRATION ACCEPT message, by including the Extended emergency number list IE. The network shall set the Extended Emergency Number List Validity (EENLV) field within the Extended emergency number list IE to "Extended Local Emergency Numbers List is valid only in the PLMN from which this IE is received". The UE shall consider the emergency number(s) received in the Extended emergency number list IE valid only in the SNPN from which this IE is received regardless of the received value of the EENLV field within the Extended emergency number list IE. The UE shall store the local emergency numbers list and the extended local emergency numbers list, as provided by the network. The local emergency numbers list stored in the UE shall be replaced on each receipt of the Emergency number list IE. The extended local emergency numbers list stored in the UE shall be replaced on each receipt of the Extended emergency number list IE. The received local emergency numbers list or the received extended local emergency numbers list or both shall be provided to the upper layers. The emergency number(s) received in the Emergency number list IE are valid only in PLMNs in the same country as the PLMN from which this IE is received. If no Emergency number list IE is contained in the REGISTRATION ACCEPT message, then the stored local emergency numbers list in the UE shall be kept, except if the UE has successfully registered to a PLMN in a country different from that of the PLMN that sent the list. The emergency number(s) received in the Extended emergency number list IE are valid only in: - PLMNs in the same country as the PLMN from which this IE is received, if the Extended Emergency Number List Validity (EENLV) field within the Extended emergency number list IE indicates "Extended Local Emergency Numbers List is valid in the country of the PLMN from which this IE is received"; and - the PLMN from which this IE is received, if 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"; and - the SNPN from which this IE is received, regardless of the value of the EENLV field within the Extended emergency number list IE. If no Extended Local Emergency Numbers List is contained in the REGISTRATION ACCEPT message, and the registered PLMN or the registered SNPN has not changed, then the stored Extended Local Emergency Numbers List in the UE shall be kept. If no Extended Local Emergency Numbers List is contained in the REGISTRATION ACCEPT message, but the registered PLMN or the registered SNPN has changed, then: - if the last received 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", the stored Extended Local Emergency Numbers List in the UE shall be deleted; and - if the last received indication in the EENLV field within the Extended emergency number list IE indicates "Extended Local Emergency Numbers List is valid in the country of the PLMN from which this IE is received" the list shall be kept except if the UE has successfully registered to a PLMN in a country different from that of the PLMN that sent the stored list. NOTE: To prevent the misrouting of emergency calls, all operators within a country need to follow the regulation or agree on the setting of the Extended emergency number list IE in accordance to national agreement – either to indicate validity within a country or to indicate validity only within the PLMN. The local emergency numbers list and the extended local emergency numbers list shall be deleted at switch off or removal of the USIM. The UE shall be able to store up to ten entries in the local emergency numbers list and up to twenty entries in the Extended local emergency numbers list, received from the network. For the use of the local emergency numbers list and the extended local emergency numbers list by the UE see 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15], subclause 5.3.7.

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

4.13.3.1 Registration procedures for SMS over NAS

Figure 4.13.3.1-1: Registration procedure supporting SMS over NAS 1. During Registration procedure in 5GS defined in Figure 4.2.2.2.2-1, to enable SMS over NAS transporting, the UE includes an "SMS supported" indication in Registration Request in step 1-3 indicating the UE's capability for SMS over NAS transport. The "SMS supported" indication indicates whether the UE supports SMS delivery over NAS. 2. Step 4 to step 14 of the Registration procedure in Figure 4.2.2.2.2-1 are performed. The AMF may retrieve the SMS Subscription data and UE Context in SMSF data using Nudm_SDM_Get. This requires that UDM may retrieve this information from UDR by Nudr_DM_Query. The UDM includes the SMSF information in the Nudm_SDM_Get response message if the stored SMSF belongs to the same PLMN of the AMF. After a successful response is received and if SMS service is allowed, the AMF subscribes to be notified using Nudm_SDM_Subscribe when the SMS Subscription data is modified and UDM may subscribe to UDR by Nudr_DM_Subscribe. The AMF can also receive UE context information containing SMSF Information from old AMF. When AMF re-allocation happens during the Registration procedure, the old AMF transfers SMSF Information to the new AMF as part of UE context in step 5 of Figure 4.2.2.2.2-1. NOTE 1: The AMF can, instead of the Nudm_SDM_Get service operation, use the Nudm_SDM_Subscribe service operation with an Immediate Report Indication that triggers the UDM to immediately return the subscribed data if the corresponding feature is supported by both the AMF and the UDM. 3. If the "SMS supported" indication is included in the Registration Request, the AMF checks in the SMS Subscription data that was received in step 2 whether the SMS service is allowed to the UE. If SMS service is allowed and the UE context received in step 2 includes an available SMSF of the serving PLMN, the AMF activates this SMSF Address and continues the registration procedure. If SMS service is allowed but an SMSF of the serving PLMN was not received in step 2, the AMF discovers and selects an SMSF to serve the UE as described in clause 6.3.10 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 4. Step 15 to step 20 of the Registration procedure in Figure 4.2.2.2.2-1 are performed. 5. The AMF invokes Nsmsf_SMService_Activate service operation from the SMSF. The invocation includes AMF address, Access Type, RAT Type, Trace Requirements, GPSI (if available) and SUPI. AMF uses the SMSF Information derived from step 3. Trace Requirements is provided if it has been received by AMF as part of subscription data. 6. The SMSF discovers a UDM as described in clause 6.3.8 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 7a. If the UE context for the current Access Type already exists in the SMSF, the SMSF shall replace the old AMF address with the new AMF address. Otherwise, the SMSF considers this a Registration request from a new Access Type and the SMSF registers with the UDM using Nudm_UECM_Registration with Access Type. As a result, the UDM stores the following information: SUPI, SMSF identity, SMSF address, Access Type(s) in UE Context in SMSF data. The UDM may further store SMSF Information in UDR by Nudr_DM_Update (SUPI, Subscription Data, UE Context in SMSF data). If the Nsmsf_SMService_Activate request contains two Access Types and one of them is already registered in the SMSF, the SMSF shall replace the old AMF address with the new AMF address for that Access Type. The SMSF shall then register the other Access Type with the UDM using Nudm_UECM_Registration request. 7b-7c SMSF retrieves SMS Management Subscription data (e.g. SMS teleservice, SMS barring list) using Nudm_SDM_Get and this requires that UDM may get this information from UDR by Nudr_DM_Query (SUPI, Subscription Data, SMS Management Subscription data). After a successful response is received, the SMSF subscribes to be notified using Nudm_SDM_Subscribe when the SMS Management Subscription data is modified and UDM may subscribe to notifications from UDR by Nudr_DM_Subscribe. SMSF also creates a UE context to store the SMS subscription information and the AMF address that is serving this UE. NOTE 2: The SMSF can, instead of the Nudm_SDM_Get service operation, use the Nudm_SDM_Subscribe service operation with an Immediate Report Indication that triggers the UDM to immediately return the subscribed data if the corresponding feature is supported by both the SMSF and the UDM. 8. The SMSF responds back to the AMF with Nsmsf_SMService_Activate service operation response message. The AMF stores the SMSF Information received as part of the UE context. 9. The AMF includes the "SMS allowed" indication to the UE in the Registration Accept message of step 21 of Figure 4.2.2.2.2-1 only after step 8 in which the AMF has received a positive indication from the selected SMSF. The "SMS allowed" indication in the Registration Accept message indicates to the UE whether the network allows the SMS message delivery over NAS.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.13.3.1

19.3.5 Pseudonym Identities

The pseudonym shall take the form of an NAI, as specified in clause 2.1 of IETF RFC 4282 [53]. The pseudonym shall be generated as specified in clause 6.4.1 of 3GPP TS 33.234[ 3G security; Wireless Local Area Network (WLAN) interworking security ] [55]. This part of the pseudonym shall follow the UTF-8 transformation format specified in IETF RFC 2279 [54] except for the following reserved hexadecimal octet value: FF When the pseudonym username is coded with FF, this reserved value is used to indicate the special case when no valid temporary identity exists in the UE (see 3GPP TS 24.234[ 3GPP system to Wireless Local Area Network (WLAN) interworking; WLAN User Equipment (WLAN UE) to network protocols; Stage 3 ] [48] for more information). The network shall not allocate a temporary identity with the whole username coded with the reserved hexadecimal value FF. The username portion of the pseudonym identity shall be prepended with the single digit "2" as specified in clause 4.1.1.7 of IETF RFC 4187 [50] for EAP-AKA. For EAP AKA', see IETF RFC 5448 [82], the pseudonym NAI shall comply with IETF RFC 4187 [50] except that the username part of the NAI shall be prepended with single digit "7". 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: For EAP AKA, if the pseudonym returned by the 3GPP AAA Server is 258405627015 and the IMSI is 234150999999999 (MCC = 234, MNC = 15), the pseudonym NAI for the case when NAI decoration is not used takes the form: 258405627015@nai.epc.mnc015.mcc234.3gppnetwork.org EXAMPLE 2: For EAP AKA', if the pseudonym returned by the 3GPP AAA Server is 758405627015 and the IMSI is 234150999999999 (MCC = 234, MNC = 15), the pseudonym NAI for the case when NAI decoration is not used takes the form: 758405627015@nai.epc.mnc015.mcc234.3gppnetwork.org EXAMPLE 3: For EAP AKA, if the pseudonym returned by the 3GPP AAA Server is 258405627015 and the IMSI is 234150999999999 (MCC = 234, MNC = 15), and the PLMN ID of the Selected PLMN is MCC = 610, MNC = 71, the pseudonym NAI takes the form: nai.epc.mnc015.mcc234.3gppnetwork.org! 258405627015@nai.epc.mnc071.mcc610.3gppnetwork.org EXAMPLE 4: For EAP AKA', if the pseudonym returned by the 3GPP AAA Server is 758405627015 and the IMSI is 234150999999999 (MCC = 234, MNC = 15), and the PLMN ID of the Selected PLMN is MCC = 610, MNC = 71, the pseudonym NAI takes the form: nai.epc.mnc015.mcc234.3gppnetwork.org! 758405627015@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.5

5.43.5 QoS monitoring when dynamic Satellite Backhaul is used

If dynamic satellite backhaul is used, QoS monitoring can be used to measure packet delay as specified in clause 5.45.2. If the Satellite backhaul category received from SMF indicates dynamic satellite backhaul is used, the PCF may, based on PCF local policy or configuration, request QoS monitoring for the packet delay between UE and PSA UPF as specified in clause 5.45.2. The AF can also trigger QoS monitoring by requesting QoS monitoring report from the PCF e.g. when the AF has received dynamic satellite backhaul indication. NOTE: PCF handling of satellite backhaul category indication and possible QoS monitoring is specified 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.43.5

5.5.1.3.7 Abnormal cases in the UE

The following abnormal cases can be identified: a) Timer T3346 is running. The UE shall not start the registration procedure for mobility and periodic registration update unless: 1) the UE is in 5GMM-CONNECTED mode; 2) the UE received a paging; 3) the UE receives a NOTIFICATION message over non-3GPP access when the UE is in 5GMM-CONNECTED mode over non-3GPP access and in 5GMM-IDLE mode over 3GPP access; 4) the UE is a UE configured for high priority access in selected PLMN or SNPN; 5) the UE has an emergency PDU session established or is establishing an emergency PDU session; 6) the UE receives a request from the upper layers to perform emergency services fallback; 7) the UE receives the CONFIGURATION UPDATE COMMAND message as specified in subclause 5.4.4.3; 8) the UE in NB-N1 mode is requested by the upper layer to transmit user data related to an exceptional event and: - the UE is allowed to use exception data reporting (see the ExceptionDataReportingAllowed leaf of the NAS configuration MO in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [17] or the USIM file EFNASCONFIG in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [22]); and - timer T3346 was not started when N1 NAS signalling connection was established with RRC establishment cause set to "mo-ExceptionData"; or 9) the MUSIM UE needs to request a new 5G-GUTI assignment as specified in subclause 5.5.1.3.2. The UE stays in the current serving cell and applies the normal cell reselection process. NOTE 1: It is considered an abnormal case if the UE needs to initiate a registration procedure for mobility and periodic registration update while timer T3346 is running independent on whether timer T3346 was started due to an abnormal case or a non-successful case. If the registration procedure for mobility and periodic registration update was initiated for an MO MMTEL voice call (i.e. access category 4), for an MO MMTEL video call (i.e. access category 5), for an MO IMS registration related signalling (i.e. access category 9) or for NAS signalling connection recovery during an ongoing MO MMTEL voice call (i.e. access category 4), or during an MO MMTEL video call (i.e. access category 5) or during an ongoing MO IMS registration related signalling (i.e. access category 9), then a notification that the procedure was not initiated due to network congestion shall be provided to upper layers. b) The lower layers indicate that the access attempt is barred. The UE shall not start the registration procedure for mobility and periodic registration update. The UE stays in the current serving cell and applies the normal cell reselection process. Receipt of the access barred indication shall not trigger the selection of a different core network type (EPC or 5GCN). The registration procedure for mobility and periodic registration update is started, if still needed, when the lower layers indicate that the barring is alleviated for the access category with which the access attempt was associated. ba) The lower layers indicate that: 1) access barring is applicable for all access categories except categories 0 and 2 and the access category with which the access attempt was associated is other than 0 and 2; or 2) access barring is applicable for all access categories except category 0 and the access category with which the access attempt was associated is other than 0. If the REGISTRATION REQUEST message has not been sent, the UE shall proceed as specified for case b. If the REGISTRATION REQUEST message has been sent, the UE shall proceed as specified for case e and, additionally, the registration procedure for mobility and periodic registration update is started, if still needed, when the lower layers indicate that the barring is alleviated for the access category with which the access attempt was associated. For additional UE requirements for both cases see subclause 4.5.5. c) T3510 timeout. The UE shall abort the registration update procedure and the N1 NAS signalling connection, if any, shall be released locally. If the UE has initiated the registration procedure in order to enable performing the service request procedure for emergency services fallback,the UE shall inform the upper layers of the failure of the emergency services fallback (see 3GP P TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [14]). Otherwise, the UE shall proceed as described below. d) REGISTRATION REJECT message, other 5GMM cause values than those treated in subclause 5.5.1.3.5, and cases of 5GMM cause values #11, #15, #22, #31, #72, #73, #74, #75, #76, #77 and #78, if considered as abnormal cases according to subclause 5.5.1.3.5. Upon reception of the 5GMM causes #95, #96, #97, #99 and #111 the UE should set the registration attempt counter to 5. The UE shall proceed as described below. e) Lower layer failure, release of the NAS signalling connection received from lower layers or the lower layers indicate that the RRC connection has been suspended without a cell change before the REGISTRATION ACCEPT or REGISTRATION REJECT message is received. The UE shall abort the registration procedure and proceed as described below. f) Change in the current TAI. If the current TAI is changed before the registration procedure for mobility and periodic registration update is completed, the registration procedure for mobility and periodic registration update shall be aborted and re-initiated immediately. The UE shall set the 5GS update status to 5U2 NOT UPDATED. g) Registration procedure for mobility and periodic registration update and de-registration procedure collision. If the UE receives a DEREGISTRATION REQUEST message without 5GMM cause value #11, #12, #13 or #15 before the registration procedure for mobility and periodic registration update has been completed, the registration procedure for mobility and periodic registration update shall be aborted and the de-registration procedure shall be progressed. If the UE receives a DEREGISTRATION REQUEST message with 5GMM cause value #11, #12, #13 or #15 before the registration procedure for mobility and periodic registration update has been completed, the registration procedure for mobility and periodic registration update shall be progressed and the de-registration procedure shall be aborted. NOTE 2: The registration procedure for mobility and periodic registration update shall be aborted only if the DEREGISTRATION REQUEST message indicates in the access type that the access in which the registration procedure for mobility and periodic registration update was attempted shall be de-registered. Otherwise both the procedures shall be progressed. h) Void i) Transmission failure of REGISTRATION REQUEST message indication from the lower layers or the lower layers indicate that the RRC connection has been suspended with a cell change. The registration procedure for mobility and periodic registration update shall be aborted and re-initiated immediately. The UE shall set the 5GS update status to 5U2 NOT UPDATED. j) Transmission failure of REGISTRATION COMPLETE message indication with change in the current TAI. If the current TAI is not in the TAI list, the registration procedure for mobility and periodic registration update shall be aborted and re-initiated immediately. The UE shall set the 5GS update status to 5U2 NOT UPDATED. If the current TAI is still part of the TAI list, it is up to the UE implementation how to re-run the ongoing procedure. k) Transmission failure of REGISTRATION COMPLETE message indication without change in the current TAI. It is up to the UE implementation how to re-run the ongoing procedure. l) UE-initiated de-registration required. De-registration due to removal of USIM or entry update in the "list of subscriber data" or due to switch off: The registration procedure for mobility and periodic registration update shall be aborted, and the UE initiated de-registration procedure shall be performed. De-registration not due to removal of USIM or entry update in the "list of subscriber data" and not due to switch off: the UE initiated de-registration procedure shall be initiated after successful completion of the registration procedure for mobility and periodic registration update. m) Timer T3447 is running The UE shall not start any mobility and periodic registration update procedure with Uplink data status IE or Follow-on request indicator set to "Follow-on request pending" unless: - the UE received a paging; - the UE is a UE configured for high priority access in selected PLMN; - the UE has an emergency PDU session established or is establishing an emergency PDU session; - the UE receives a request from the upper layers to perform emergency services fallback; or - the MUSIM UE needs to request a new 5G-GUTI assignment as specified in subclause 5.5.1.3.2. The UE stays in the current serving cell and applies the normal cell reselection process. The mobility and periodic registration update procedure is started, if still necessary, when timer T3447 expires or timer T3447 is stopped. n) Timer T3448 is running The UE in 5GMM-IDLE mode shall not start any mobility and periodic registration update procedure with Follow-on request indicator set to "Follow-on request pending" unless: 1) the UE is a UE configured for high priority access in selected PLMN; 2) the UE which is only using 5GS services with control plane CIoT 5GS optimization received a paging request; or 3) the UE in NB-N1 mode is requested by the upper layer to transmit user data related to an exceptional event and the UE is allowed to use exception data reporting (see the ExceptionDataReportingAllowed leaf of the NAS configuration MO in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [17] or the USIM file EFNASCONFIG in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [22]). The UE stays in the current serving cell and applies the normal cell reselection process. The mobility and periodic registration update procedure is started, if still necessary, when timer T3448 expires. o) UE is not registered to the access other than the access the REGISTRATION ACCEPT message is received and the 5GS registration result value in the 5GS registration result IE value in the REGISTRATION ACCEPT message is set to "3GPP access and non-3GPP access". The UE shall consider itself as being registered to only the access where the REGISTRATION ACCEPT message is received. p) Access for localized services in current SNPN is no longer allowed. If the mobility and periodic registration update is not for initiating an emergency PDU session, the registered SNPN is an SNPN selected for localized services in SNPN as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] and: - access for localized services in SNPN is disabled; or - the validity information for the selected SNPN is no longer met; the UE shall reset the registration attempt counter, stop T3510, abort the registration procedure for mobility and periodic registration update, locally release the NAS signalling connection, if any, and enter state 5GMM-REGISTERED.LIMITED-SERVICE or 5GMM-REGISTERED.PLMN-SEARCH in order to perform SNPN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]. For the cases c, d and e the UE shall proceed as follows: Timer T3510 shall be stopped if still running. If the registration procedure is not for initiating an emergency PDU session, the registration attempt counter shall be incremented, unless it was already set to 5. If the registration attempt counter is less than 5: - if the TAI of the current serving cell is not included in the TAI list or the 5GS update status is different to 5U1 UPDATED or if the registration procedure was triggered due to cases c, g, n, v in subclause 5.5.1.3.2, the UE shall start timer T3511, shall set the 5GS update status to 5U2 NOT UPDATED and change to state 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE. When timer T3511 expires, the registration update procedure is triggered again. - if the TAI of the current serving cell is included in the TAI list, the 5GS update status is equal to 5U1 UPDATED, and the UE is not performing the registration procedure after an inter-system change from S1 mode to N1 mode, the UE shall keep the 5GS update status to 5U1 UPDATED and enter state 5GMM-REGISTERED.NORMAL-SERVICE or 5GMM-REGISTERED.NON-ALLOWED-SERVICE (as described in subclause 5.3.5.2). The UE shall start timer T3511. If in addition the REGISTRATION REQUEST message did not include the MICO indication IE or the Extended DRX IE, and: - the REGISTRATION REQUEST message indicated "periodic registration updating"; - the registration procedure was initiated to recover the NAS signalling connection due to "RRC Connection failure" from the lower layers; or - the registration procedure was initiated by the UE in 5GMM-CONNECTED mode with RRC inactive indication entering a cell in the current registration area belonging to an equivalent PLMN of the registered PLMN and not belonging to the registered PLMN, and none of the other reasons for initiating the registration updating procedure listed in subclause 5.5.1.3.2 was applicable, the timer T3511 may be stopped when the UE enters 5GMM-CONNECTED mode. - if the TAI of the current serving cell is included in the TAI list, the 5GS update status is equal to 5U1 UPDATED and the UE is performing the registration procedure after an inter-system change from S1 mode to N1 mode, the UE shall change the 5GS update status to 5U2 NOT UPDATED and enter state 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE. The UE shall start timer T3511. - If the procedure is performed via 3GPP access and the UE is operating in single-registration mode, the UE shall in addition handle the EPS update status as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] for the abnormal cases when a normal or periodic tracking area updating procedure fails and the tracking area attempt counter is less than 5 and the EPS update status is different from EU1 UPDATED. If the registration attempt counter is equal to 5 - the UE shall start timer T3502 if the value of the timer as indicated by the network is not zero, shall set the 5GS update status to 5U2 NOT UPDATED. - the UE shall delete the list of equivalent PLMNs (if any) or the list of equivalent SNPNs (if any) if the UE is not registering or has not registered to the same PLMN over both 3GPP access and non-3GPP access, and shall change to state 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE or optionally to 5GMM-REGISTERED.PLMN-SEARCH in order to perform a PLMN selection, SNPN selection or SNPN selection for onboarding services according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]. - if the value of T3502 as indicated by the network is zero, the UE shall perform the actions defined for the expiry of the timer T3502. NOTE 3: For case e) if the lower layer failure is on a cell which was selected due to network slice-based cell reselection (see 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]), the UE can as an implementation option change the S-NSSAI(s) in the requested NSSAI to try and find a suitable NR cell. - if the procedure is performed via 3GPP access and the UE is operating in single-registration mode: - the UE shall in addition handle the EPS update status as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] for the abnormal cases when a normal or periodic tracking area updating procedure fails and the tracking area attempt counter is equal to 5; and - if the UE does not change to state 5GMM-REGISTERED.PLMN-SEARCH, the UE shall attempt to select E-UTRAN radio access technology. The UE may disable the N1 mode capability as specified in subclause 4.9.

3GPP TS 24.501

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

CT WG1

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

5.5.1.3.7

7.6.4.1 IEIs unknown in the Type 6 IE container information element

The UE shall ignore all IEs with an IEI unknown in a Type 6 IE container information element which are not encoded as "comprehension required" (see 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [11]). The network shall take the same approach. NOTE: The set of IEIs defined for a Type 6 IE container information element is independent of the set of IEIs defined for other parts of the message. Therefore, an IE can be unknown in a Type 6 IE container information element, even if an IE with the same IEI is known in other parts of the message, and vice versa.

3GPP TS 24.501

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

CT WG1

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

7.6.4.1

5.4.11.6 Support of Mobility Registration Update

A moving radio cell for NR satellite access may indicate support for one or more TACs for each PLMN. A UE that is registered with a PLMN may access a radio cell and does not need to perform a Mobility Registration Update procedure as long as at least one supported TAC for the RPLMN or equivalent to the RPLMN is part of the UE Registration Area. A UE shall perform a Mobility Registration Update procedure when accessing a radio cell where none of the supported TACs for the RPLMN or equivalent to the RPLMN are part of the UE Registration Area. When indicating a last visited TAI in a Registration Update, a UE may indicate any TAI supported in a radio cell for the RPLMN or equivalent to the RPLMN for the last UE access prior to the Registration Update that is part of the UE Registration Area.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.4.11.6

X.8.2.2 Policies configured as extended claims in access token

Figure X.8.2.2-1: Protection of analytics exchange when policies configured as extended claims in access token Pre-requisite: - The producer NRF has the NF profile of the NF Service Producer including the list of allowed Analytics ID(s) per PLMN. According to TS 29.510[ 5G System; Network function repository services; Stage 3 ] [68] clause 5.2.1, the NF profile can be configured in the NRF by other means such as O&M. Step 1: NWDAFc sends an access token request to the consumer NRF as specified in clause 13.4.1. The access token request may contain the Analytics ID. Step 2: vNRF forward the token request message to hNRF as specified in clause 13.4.1. Step 3: The home network hNRF shall verify the token get request as specified 13.4.1, then determine whether the requested analytics implied by the Analytics ID(s) can be obtained by the visited PLMN according to the allowed analytics ID(s) of the visited PLMN. Step 4: If the verification success, hNRF issue the token as specified in clause 13.4.1.The allowed Analytics ID(s) of the visited PLMN may be included in the token. Step 5: The vNRF forward the Token_Get Response to NWDAFc as specified in clause 13.4.1. Step 6: If the requested analytics is within the claim of token, the NWDAFc sends Nnwdaf_RoamingAnalytics_Subscribe/Request with the issued token to NWDAFp, Step 7: The roaming entry NWDAFp verifies the service request, including verifying token as specified in clause 13.4.1, and whether the requested analytics are consistent with the Analytics ID(s) in the token. Step 8: The roaming entry NWDAFp shall apply the security policies per consumer (PLMN) to the requested analytics and decide on their anonymization, restriction or desensitization based on operator’s policy. NOTE: The anonymization, restriction or desensitization mechanisms of data / analytics are left for implementation. Step 9: Roaming entry NWDAFp returns the requested and processed analytics to NWDAFc.

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

X.8.2.2

6.9.2.3 Permission and Authorization

The 5G system shall enable the network operator to authorize a UE to use indirect network connection. The authorization shall be able to be restricted to using only relay UEs belonging to the same network operator. The authorization shall be able to be restricted to only relay UEs belonging to the same application layer group. The 5G system shall enable the network operator to authorize a UE to relay traffic as relay UE. The authorization shall be able to allow relaying only for remote UEs belonging to the same network operator. The authorization shall be able to allow relaying only for remote UEs belonging to the same application layer group. The 5G system shall support a mechanism for an end user to provide/revoke permission to an authorized UE to act as a relay UE. The 5G system shall support a mechanism for an authorized third-party to provide/revoke permission to an authorized UE to act as a relay UE. The 5G system shall provide a suitable API by which an authorized third-party shall be able to authorize (multiple) UEs under control of the third-party to act as a relay UE or remote UE. The 5G system shall provide a suitable API by which an authorized third-party shall be able to enable/disable (multiple) UEs under control of the third-party to act as a relay UE or remote UE.

3GPP TS 22.261

Service requirements for the 5G system

SA WG1

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

6.9.2.3

4.7.6 Bearer Control Mode in EPC

The Bearer Control Mode (BCM) for E-UTRAN access is always UE/NW. Hence, explicit signalling between the UE and the network to determine BCM for E-UTRAN access does not occur. GERAN/UTRAN/E-UTRAN capable UEs negotiate the BCM of a PDN Connection applicable for GERAN/UTRAN access during E-UTRAN Initial Attach and during UE Requested PDN Connectivity procedure. Such UEs provide the Network Request Support UE (NRSU) parameter to the PDN GW in PCO. The PDN GW derives the BCM applicable to GERAN/UTRAN access based on the NRSU and operator policy. The selected BCM, valid for GERAN/UTRAN, is provided back to the UE in PCO IE in the E-UTRAN Attach Accept or PDN Connectivity Accept message. The selected BCM is also stored in the PDN GW and the UE, and applied by UE upon moving to GERAN or UTRAN access unless explicitly informed by PDN GW of a change in BCM (see TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7]) via PCO IE. NOTE 1: In Rel-8 it was not mandatory for GERAN/UTRAN/E-UTRAN capable UEs to provide NRSU to the PDN GW during E-UTRAN Initial Attach and UE Requested PDN Connectivity procedure. When a GERAN/UTRAN/E-UTRAN capable UE moves from UTRAN or GERAN access to E-UTRAN access, it stores the BCM used in UTRAN or GERAN access to be used again when the UE moves back to UTRAN or GERAN access unless explicitly informed by PDN GW of a change in BCM (see TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7]) via the PCO IE. If PCC is deployed, the PDN GW requests PCRF to perform BCM selection for the RAT the UE is accessing at IP-CAN session establishment and IP-CAN session modification. The PCRF, determines the applicable BCM, based on a number of factors (see TS 23.203[ Policy and charging control architecture ] [6]), and informs the PDN GW. If the BCM has changed, the PDN GW informs the UE of the new BCM via the PCO IE.

3GPP TS 23.401

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

SA WG2

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

4.7.6

6.4.2.5 Abnormal cases in the UE

The following abnormal cases can be identified: a) Dedicated EPS bearer context activation request for an already activated default EPS bearer context: If the UE receives an ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message with an EPS bearer identity identical to the EPS bearer identity of an already activated default EPS bearer context, the UE shall locally deactivate the existing default EPS bearer context and all the associated dedicated EPS bearer contexts, if any, and proceed with the requested dedicated EPS bearer context activation. b) Dedicated EPS bearer context activation request for an already activated dedicated EPS bearer context If the UE receives an ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message with an EPS bearer identity identical to the EPS bearer identity of an already activated dedicated EPS bearer context, the UE shall locally deactivate the existing dedicated EPS bearer context and proceed with the requested dedicated EPS bearer context activation. c) No default EPS bearer context with linked EPS bearer identity activated If the linked EPS bearer identity included in the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message does not match the EPS bearer identity of any activated default EPS bearer context, the UE shall reply with an ACTIVATE DEDICATED EPS BEARER CONTEXT REJECT message with ESM cause #43 "invalid EPS bearer identity". d) Dedicated EPS bearer context activation request when the PLMN's maximum number of EPS bearer contexts in S1 mode is reached at the UE: If the PLMN's maximum number of EPS bearer contexts in S1 mode is reached at the UE and the UE receives an ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message, the UE shall clear the determination representing the PLMN's maximum number of EPS bearer contexts in S1 mode and proceed with the dedicated EPS bearer context activation procedure.

3GPP TS 24.301

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

CT WG1

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

6.4.2.5

4.3.1.1.4 Attempted outgoing intra-DeNB handover executions from DeNB cell to RN per handover cause

This measurement provides the number of attempted outgoing intra-eNB handovers from DeNB cell to RN per handover cause; this measurement is only applicable to DeNB. CC. Transmission of the RRC ConnectionReconfiguration message to UE triggering the handover from the DeNB to the RN, indicatingthe attempt of an outgoing intra-eNB handover from DeNB cell to RN (see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]). Each RRCConnectionReconfiguration message transimtted is added to the relevant per handover cause measurement, the possible causes are included in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [9]. The sum of all supported per cause measurements shall equal the total number of attempted outgoing intra-eNB handovers from DeNB cell to RN. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first. Each measurement is an integer value. The number of measurements is equal to the number of causes supported plus a possible sum value identified by the .sum suffix. HO.IntraDenbOutToRnAtt.Cause where Cause identifies the cause for handover EUtranCellFDD EUtranCellTDD Valid for packet switched traffic EPS

3GPP TS 32.425

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

SA WG5

3GPP Series : 32 , OAM&P and Charging

4.3.1.1.4

5.1.5 Contention Resolution

Contention Resolution is based on either C-RNTI on PDCCH of the SpCell or UE Contention Resolution Identity on DL-SCH. Once Msg3 is transmitted, the MAC entity shall: - if the UE is an NB-IoT UE, a BL UE or a UE in enhanced coverage: - if Msg3 is transmitted on a non-terrestrial network: - if, for EDT, edt-SmallTBS-Enabled is set to TRUE for the corresponding PRACH resource: - start mac-ContentionResolutionTimer and restart mac-ContentionResolutionTimer at each HARQ retransmission of the bundle in the subframe corresponding to the last subframe of a PUSCH transmission corresponding to the largest TBS indicated by the UL grant plus UE-eNB RTT. - else: - start mac-ContentionResolutionTimer and restart mac-ContentionResolutionTimer at each HARQ retransmission of the bundle in the subframe containing the last repetition of the corresponding PUSCH transmission plus UE-eNB RTT. - else: - if, for EDT, edt-SmallTBS-Enabled is set to TRUE for the corresponding PRACH resource: - start mac-ContentionResolutionTimer and restart mac-ContentionResolutionTimer at each HARQ retransmission of the bundle in the subframe corresponding to the last subframe of a PUSCH transmission corresponding to the largest TBS indicated by the UL grant. - else: - start mac-ContentionResolutionTimer and restart mac-ContentionResolutionTimer at each HARQ retransmission of the bundle in the subframe containing the last repetition of the corresponding PUSCH transmission. - else: - start mac-ContentionResolutionTimer and restart mac-ContentionResolutionTimer at each HARQ retransmission. - regardless of the possible occurrence of a measurement gap or Sidelink Discovery Gap for Reception, monitor the PDCCH until mac-ContentionResolutionTimer expires or is stopped; - if notification of a reception of a PDCCH transmission is received from lower layers, the MAC entity shall: - if the C-RNTI MAC control element was included in Msg3: - if the Random Access procedure was initiated by the MAC sublayer itself or by the RRC sublayer and the PDCCH transmission is addressed to the C-RNTI and contains an UL grant for a new transmission; or - if the Random Access procedure was initiated by a PDCCH order and the PDCCH transmission is addressed to the C-RNTI: - consider this Contention Resolution successful; - stop mac-ContentionResolutionTimer; - discard the Temporary C-RNTI; - if the UE is an NB-IoT UE: - the UL grant or DL assignment contained in the PDCCH transmission is valid only for the configured carrier (i.e. UL/DL carrier used prior to this Random Access procedure). - consider this Random Access procedure successfully completed. - else if the CCCH SDU was included in Msg3 and the PDCCH transmission is addressed to its Temporary C-RNTI: - if the MAC PDU is successfully decoded: - stop mac-ContentionResolutionTimer; - if the MAC PDU contains a UE Contention Resolution Identity MAC control element; and - if the UE Contention Resolution Identity included in the MAC control element matches the 48 first bits of the CCCH SDU transmitted in Msg3: - consider this Contention Resolution successful and finish the disassembly and demultiplexing of the MAC PDU; - set the C-RNTI to the value of the Temporary C-RNTI; - discard the Temporary C-RNTI; - consider this Random Access procedure successfully completed. - else: - discard the Temporary C-RNTI; - consider this Contention Resolution not successful and discard the successfully decoded MAC PDU. - if mac-ContentionResolutionTimer expires: - for BL UEs or UEs in CE or NB-IoT UEs: - if notification of a reception of a PDCCH transmission has been received from lower layers before mac-ContentionResolutionTimer expired; and - if the MAC PDU received until the subframe that contains the last repetition of the corresponding PDSCH transmission is successfully decoded; and - if the MAC PDU contains a UE Contention Resolution Identity MAC control element; and - if the UE Contention Resolution Identity included in the MAC control element matches the 48 first bits of the CCCH SDU transmitted in Msg3: - consider this Contention Resolution successful and finish the disassembly and demultiplexing of the MAC PDU; - set the C-RNTI to the value of the Temporary C-RNTI; - discard the Temporary C-RNTI; - consider this Random Access procedure successfully completed. - else if Msg3 was transmitted on a non-terrestrial network: - if no notification of a reception of a PDCCH transmission addressed to the Temporary C-RNTI indicating an uplink grant for a Msg3 retransmission was received after the start of the mac-ContentionResolutionTimer: - discard the Temporary C-RNTI; - consider the Contention Resolution not successful. - else: - discard the Temporary C-RNTI; - consider this Contention Resolution not successful. - except for BL UEs or UEs in CE or NB-IoT UEs: - discard the Temporary C-RNTI; - consider the Contention Resolution not successful. - if the Contention Resolution is considered not successful the MAC entity shall: - flush the HARQ buffer used for transmission of the MAC PDU in the Msg3 buffer; - if the notification of power ramping suspension has not been received from lower layers: - increment PREAMBLE_TRANSMISSION_COUNTER by 1; - if the UE is an NB-IoT UE, a BL UE or a UE in enhanced coverage: - if PREAMBLE_TRANSMISSION_COUNTER = preambleTransMax-CE + 1: - indicate a Random Access problem to upper layers; - if NB-IoT: - consider the Random Access procedure unsuccessfully completed. - else: - if PREAMBLE_TRANSMISSION_COUNTER = preambleTransMax + 1: - indicate a Random Access problem to upper layers. - based on the backoff parameter, select a random backoff time according to a uniform distribution between 0 and the Backoff Parameter Value; - delay the subsequent Random Access transmission by the backoff time; - proceed to the selection of a Random Access Resource (see clause 5.1.2).

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

– PHR-Config

The IE PHR-Config is used to configure parameters for power headroom reporting. PHR-Config information element -- ASN1START -- TAG-PHR-CONFIG-START PHR-Config ::= SEQUENCE { phr-PeriodicTimer ENUMERATED {sf10, sf20, sf50, sf100, sf200,sf500, sf1000, infinity}, phr-ProhibitTimer ENUMERATED {sf0, sf10, sf20, sf50, sf100,sf200, sf500, sf1000}, phr-Tx-PowerFactorChange ENUMERATED {dB1, dB3, dB6, infinity}, multiplePHR BOOLEAN, dummy BOOLEAN, phr-Type2OtherCell BOOLEAN, phr-ModeOtherCG ENUMERATED {real, virtual}, ..., [[ mpe-Reporting-FR2-r16 SetupRelease { MPE-Config-FR2-r16 } OPTIONAL -- Need M ]], [[ mpe-Reporting-FR2-r17 SetupRelease { MPE-Config-FR2-r17 } OPTIONAL, -- Need M twoPHRMode-r17 ENUMERATED {enabled} OPTIONAL -- Need R ]], [[ phr-AssumedPUSCH-Reporting-r18 ENUMERATED {enabled} OPTIONAL, -- Need R dpc-Reporting-FR1-r18 ENUMERATED {enabled} OPTIONAL -- Need R ]] } MPE-Config-FR2-r16 ::= SEQUENCE { mpe-ProhibitTimer-r16 ENUMERATED {sf0, sf10, sf20, sf50, sf100, sf200, sf500, sf1000}, mpe-Threshold-r16 ENUMERATED {dB3, dB6, dB9, dB12} } MPE-Config-FR2-r17 ::= SEQUENCE { mpe-ProhibitTimer-r17 ENUMERATED {sf0, sf10, sf20, sf50, sf100, sf200, sf500, sf1000}, mpe-Threshold-r17 ENUMERATED {dB3, dB6, dB9, dB12}, numberOfN-r17 INTEGER(1..4), ... } -- TAG-PHR-CONFIG-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

4.7.7.2 Authentication and ciphering response by the MS

In A/Gb mode, an MS shall be ready to respond upon an AUTHENTICATION_AND_CIPHERING REQUEST message at any time. In UMTS, an MS shall be ready to respond upon an AUTHENTICATION_AND_CIPHERING REQUEST message at any time whilst a PS signalling connection exists. If a SIM is inserted in the MS, the MS shall ignore the Authentication Parameter AUTN IE if included in the AUTHENTICATION_AND_CIPHERING REQUEST message and perform the GSM authentication challenge. It shall not perform the authentication of the network described in subclause 4.7.7.5.1. In a GSM authentication challenge, if the AUTHENTICATION_AND_CIPHERING REQUEST message includes the authentication parameters RAND and GPRS CKSN, then upon receipt of the message, the MS processes the challenge information and sends an AUTHENTICATION_AND_CIPHERING RESPONSE message to the network. The value of the received A&C reference number information element shall be copied into the A&C reference number information element in the AUTHENTICATION_AND_CIPHERING RESPONSE message. A GSM authentication challenge will result in the SIM/USIM passing a SRES and a GPRS GSM ciphering key to the ME. The new GPRS GSM ciphering key calculated from the challenge information shall overwrite the previous one and any previously stored GPRS UMTS ciphering and GPRS UMTS integrity keys shall be deleted. The calculated GSM ciphering key shall be stored on the SIM/USIM together with the GPRS ciphering key sequence number before the AUTHENTICATION_AND_CIPHERING RESPONSE message is transmitted. In a UMTS authentication challenge, if the AUTHENTICATION_AND_CIPHERING REQUEST message includes the UMTS authentication parameters GPRS CKSN, RAND and AUTN, then upon receipt of the message, the MS verifies the AUTN parameter and if this is accepted, the MS processes the challenge information and sends an AUTHENTICATION_AND_CIPHERING RESPONSE message to the network. The value of the received A&C reference number information element shall be copied into the A&C reference number information element in the AUTHENTICATION_AND_CIPHERING RESPONSE message. A UMTS authentication challenge will result in the USIM passing a RES, a GPRS UMTS ciphering key, a GPRS UMTS integrity key and a GPRS GSM ciphering key to the ME. The new GPRS UMTS ciphering key, GPRS UMTS integrity key and GPRS GSM ciphering key calculated from the challenge information shall overwrite the previous ones. The new GPRS UMTS ciphering key, GPRS UMTS integrity key and GPRS GSM ciphering key shall be stored on the USIM together with the GPRS ciphering key sequence number before the AUTHENTICATION_AND_CIPHERING RESPONSE message is transmitted. Furthermore, in A/Gb mode if a GEA ciphering algorithm that requires a 128-bit ciphering key is taken into use, then a new GPRS GSM Kc128 shall also be calculated as described in the subclause 4.7.7.3a. In A/Gb mode, in a UMTS authentication challenge, if the MS supports integrity protection, then the MS shall ignore the GPRS GSM ciphering key received from the USIM and not store the GPRS GSM ciphering key in the ME or on the USIM. In addition, in A/Gb mode, in a UMTS authentication challenge, if the MS has indicated support of integrity protection in the MS network capability IE to the network, and if an authentication takes place in the authentication and ciphering procedure, then a new GPRS GSM Kint shall also be calculated by the MS from the new UMTS security context derived from AKA as described in the subclause 4.7.7.3b. The new GPRS GSM Kint shall be used by the MS to check and verify the message authentication code recived in the AUTHENTICATION AND CIPHERING REQUEST message as described in Annex H in 3GPP TS 43.020[ Security related network functions ] [13]. If the integrity is successfully verified in the MS, then the MS shall check if the replayed MS network capability IE and replayed MS Radio Access Capability IE received in the AUTHENTICATION AND CIPHERING REQUEST message has not been altered compared to the latest MS network capability IE and the latest MS Radio Access Capability IE that the MS sent to the network. If the replayed MS network capability IE and the replayed MS Radio Access Capability IE received in the AUTHENTICATION AND CIPHERING REQUEST message are not the same as the latest MS network capability IE and the MS Radio Access Capability IE that the MS sent to the network, then the MS shall ignore the authentication and ciphering procedure. The network may in addition indicate a GPRS GSM integrity algorithm and a new setting of the ciphering mode and GPRS GSM ciphering algorithm, to be taken into use by the MS. If the integrity of the AUTHENTICATION AND CIPHERING REQUEST message is not successfully verified in the GMM layer, then the MS shall ignore the AUTHENTICATION AND CIPHERING REQUEST message. In A/Gb mode, in a UMTS authentication challenge if the MS has no available UMTS security context and, if the MS has indicated support for integrity protection in MS network capability IE to the network, then if the network does not activate integrity protection by indicating a GPRS GSMintegrity algorithm or does not include a message authentication code to the MS in AUTHENTICATION AND CIPHERING REQUEST message, then the MS shall ignore the AUTHENTICATION AND CIPHERING REQUEST message. In A/Gb mode, in a UMTS authentication challenge, if the MS has indicated support for integrity protection to the network and if the integrity of the AUTHENTICATION AND CIPHERING REQUEST message is successfully verified in the MS and the MS decides to reply by sending an AUTHENTICATION AND CIPHERING RESPONSE message to the network, then the MS shall integrity protect the AUTHENTICATION AND CIPHERING RESPONSE message by calculating an message authentication code at the GMM layer using the new integrity key GPRS GSM Kint calculated by the MS from the new UMTS security context derived from AKA as described in the subclause 4.7.7.3b and as described in Annex H in 3GPP TS 43.020[ Security related network functions ] [13] and include the new message authentication code into the AUTHENTICATION AND CIPHERING RESPONSE message. When a successful authentication takes place on the USIM the GMM layer in the MS shall request the LLC layer to reset the IOV_updates counter to the value zero before sending the AUTHENTICATION AND CIPHERING RESPONSE message to the network. In Iu mode, an MS not capable of A/Gb mode shall ignore the Ciphering Algorithm IE in the AUTHENTICATION_AND_CIPHERING REQUEST message. An MS capable of both Iu mode and A/Gb mode shall store the received value in the Ciphering Algorithm IE in the AUTHENTICATION_AND_CIPHERING REQUEST message until entering state GMM-DEREGISTERED, in order to use it at an inter system change to A/Gb mode. In A/Gb mode, an MS supporting integrity protection shall store the received value in the Ciphering Algorithm IE when entering GMM-DEREGISTERED and at MS power off as described in subclause 4.7.7.3a. If the AUTHENTICATION_AND_CIPHERING REQUEST message does not include neither the GSM authentication parameters (RAND and GPRS CKSN) nor the UMTS authentication parameters (RAND, AUTN and GPRS CKSN), then upon receipt of the message, the MS replies by sending an AUTHENTICATION_AND_CIPHERING RESPONSE message to the network. In A/Gb mode, in the case of an established UMTS security context, if the MS has indicated support for integrity protection to the network, the network may only indicate a GPRS GSM integrity algorithm or a GPRS GSM ciphering algorithm or a change of ciphering mode setting in the AUTHENTICATION AND CIPHERING REQUEST message without re-authentication to the MS. The AUTHENTICATION AND CIPHERING REQUEST message shall include the new GPRS GSM integrity algorithm or the new GPRS GSM ciphering algorithm; or both, that shall be taken into use. When the MS receives this AUTHENTICATION AND CIPHERING REQUEST message without requiring a new authentication, then a new GPRS GSM Kint shall be calculated using the GPRS UMTS ciphering key and the GPRS UMTS integrity key from the already established UMTS security context stored in the ME as described in the subclause 4.7.7.3b and a new GPRS GSM Kc128 shall be calculated using the GPRS UMTS ciphering key and the GPRS UMTS integrity key from the already established UMTS security context stored in the ME as described in the subclause 4.7.7.3a and the MS replies by sending an AUTHENTICATION AND CIPHERING RESPONSE message to the network. NOTE: If only a change of GPRS GSM integrity algorithm or GPRS GSM encryption algorithm or a change of both algorithms is included in the AUTHENTICATION AND CIPHERING RESPONSE message without authentication, then the MS shall not integrity protect the AUTHENTICATION AND CIPHERING RESPONSE message at GMM layer. The MS does therefore not calculate and include a message authentication code into the AUTHENTICATION AND CIPHERING RESPONSE message at GMM layer. These GMM messages are instead integrity protected at the LLC layer with current UMTS security context. In A/Gb mode, the GMM layer shall notify the LLC layer if ciphering shall be used or not and if yes which GSM ciphering algorithm and GPRS GSM ciphering key that shall be used (see 3GPP TS 44.064[ Mobile Station - Serving GPRS Support Node (MS-SGSN); Logical Link Control (LLC) Layer Specification ] [78a]). In A/Gb mode, if an established UMTS security context context is available in the network, if the MS has indicated support of integrity protection to the network, then the GMM layer in the MS shall assign the GPRS GSM integrity algorithm and the GPRS GSM Kint integrity key to the LLC layer after it has sent off the AUTHENTICATION AND CIPHERING RESPONSE message to the network (see 3GPP TS 43.020[ Security related network functions ] [13] and 3GPP TS 44.064[ Mobile Station - Serving GPRS Support Node (MS-SGSN); Logical Link Control (LLC) Layer Specification ] [78a]). A ME supporting UMTS authentication challenge shall support the following procedure: In order to avoid a synchronisation failure, when the mobile station receives an AUTHENTICATION AND CIPHERING REQUEST message, the mobile station shall store the received RAND together with the RES returned from the USIM in the volatile memory and associate it with the PS domain. When the MS receives a subsequent AUTHENTICATION AND CIPHERING REQUEST message, if the stored RAND value for the PS domain is equal to the new received value in the AUTHENTICATION AND CIPHERING REQUEST message, then the mobile station shall not pass the RAND to the USIM, but shall immediately send the AUTHENTICATION AND CIPHERING RESPONSE message with the stored RES for the PS domain. If, for the PS domain, there is no valid stored RAND in the mobile station or the stored RAND is different from the new received value in the AUTHENTICATION AND CIPHERING REQUEST message, the mobile station shall pass the RAND to the USIM, shall override any previously stored RAND and RES with the new ones and start, or reset and restart timer T3316. The RAND and RES values stored in the mobile station shall be deleted and timer T3316, if running, shall be stopped: - upon receipt of a SECURITY MODE COMMAND (Iu mode only), SERVICE ACCEPT (Iu mode only), SERVICE REJECT (Iu mode only), ROUTING AREA UPDATE_ACCEPT or AUTHENTICATION AND CIPHERING REJECT message; - upon expiry of timer T3316; - if the mobile station enters the GMM states GMM-DEREGISTERED or GMM-NULL; or - if the mobile station enters PMM-IDLE mode (Iu mode 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

4.7.7.2

9.3.4 UE-selected subband CQI

The accuracy of UE-selected subband channel quality indicator (CQI) reporting under frequency-selective fading conditions is determined by the relative increase of the throughput obtained when transmitting on the UE-selected subbands with the corresponding transport format compared to the case for which a fixed format is transmitted on any subband in set S of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [6]. The purpose is to verify that correct subbands are accurately reported for frequency-selective scheduling. To account for sensitivity of the input SNR the subband CQI reporting under frequency-selective fading conditions is considered to be verified if the reporting accuracy is met for at least one of two SNR levels separated by an offset of 1 dB.

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

5.3.5.8.3 T304 expiry (Reconfiguration with sync Failure) or T420 expiry (Path switch failure)

The UE shall: 1> if T304 of the MCG expires; or 1> if T420 expires; or, 1> if the target L2 U2N Relay UE (i.e., the UE indicated by targetRelayUE-Identity in the received RRCReconfiguration message containing reconfigurationWithSync indicating path switch as specified in 5.3.5.5.2) changes its serving PCell before path switch: 2> release dedicated preambles provided in rach-ConfigDedicated if configured; 2> release dedicated msgA PUSCH resources provided in rach-ConfigDedicated if configured; 2> if any DAPS bearer is configured, and radio link failure is not detected in the source PCell, according to clause 5.3.10.3: 3> reset MAC for the target PCell and release the MAC configuration for the target PCell; 3> for each DAPS bearer: 4> release the RLC entity or entities as specified in TS 38.322[ NR; Radio Link Control (RLC) protocol specification ] [4], clause 5.1.3, and the associated logical channel for the target PCell; 4> reconfigure the PDCP entity to release DAPS as specified in TS 38.323[ NR; Packet Data Convergence Protocol (PDCP) specification ] [5]; 3> for each SRB: 4> if the masterKeyUpdate was not received: 5> configure the PDCP entity for the source PCell with state variables continuation as specified in TS 38.323[ NR; Packet Data Convergence Protocol (PDCP) specification ] [5]; 4> release the PDCP entity for the target PCell; 4> release the RLC entity as specified in TS 38.322[ NR; Radio Link Control (RLC) protocol specification ] [4], clause 5.1.3, and the associated logical channel for the target PCell; 4> trigger the PDCP entity for the source PCell to perform SDU discard as specified in TS 38.323[ NR; Packet Data Convergence Protocol (PDCP) specification ] [5]; 4> re-establish the RLC entity for the source PCell; 3> release the physical channel configuration for the target PCell; 3> discard the keys used in target PCell (the KgNB key, the KRRCenc key, the KRRCint key, the KUPint key and the KUPenc key), if any; 3> resume suspended SRBs in the source PCell; 3> for each non-DAPS bearer: 4> revert back to the UE configuration used for the DRB or multicast MRB in the source PCell, includes PDCP, RLC states variables, the security configuration and the data stored in transmission and reception buffers in PDCP and RLC entities ; 3> revert back to the UE measurement configuration used in the source PCell; 3> store the handover failure information in VarRLF-Report as described in the clause 5.3.10.5; 3> initiate the failure information procedure as specified in clause 5.7.5 to report DAPS handover failure. 2> else: 3> revert back to the UE configuration used in the source PCell; 3> if the associated T304 was not initiated upon cell selection performed while timer T311 was running, as defined in clause 5.3.7.3: 4> store the handover failure information in VarRLF-Report as described in the clause 5.3.10.5; 3> initiate the connection re-establishment procedure as specified in clause 5.3.7. NOTE 1: In the context above, "the UE configuration" includes state variables and parameters of each radio bearer. 1> else if T304 of a secondary cell group expires: 2> if MCG transmission is not suspended: 3> release dedicated preambles provided in rach-ConfigDedicated, if configured; 3> release dedicated msgA PUSCH resources provided in rach-ConfigDedicated, if configured; 3> initiate the SCG failure information procedure as specified in clause 5.7.3 to report SCG reconfiguration with sync failure, upon which the RRC reconfiguration procedure ends; 2> else: 3> if the UE is in NR-DC: 4> initiate the connection re-establishment procedure as specified in clause 5.3.7; 3> else (the UE is in (NG) EN-DC): 4> initiate the connection re-establishment procedure as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10], clause 5.3.7; 1> else if T304 expires when RRCReconfiguration is received via other RAT (HO to NR failure): 2> reset MAC; 2> perform the actions defined for this failure case as defined in the specifications applicable for the other RAT. NOTE 2: In this clause, the term 'handover failure' has been used to refer to 'reconfiguration with sync failure'.

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

5.3.5.8.3

13a.2.2.2 Establishment of a PDP Context/EPS Bearer for Signalling

The following applies for establishing a PDP context/EPS bearer for IMS signalling in the GGSN/P-GW as per 3GPP TS 23.228[ IP Multimedia Subsystem (IMS); Stage 2 ] [52]: I. The GGSN/P-GW shall allow IMS signalling on a "general-purpose PDP context"/default EPS bearer, in which case the IMS signalling shall be provided like any other transparent services provided by the packet domain. II. The GGSN/P-GW may (dependent on operator policy) also support PDP Contexts/EPS Bearers dedicated for IMS services. If the the bearer establishment selected for the APN is controlled by the MS/UE, the MS/UE may request a dedicated PDP context/EPS Bearer for IMS signalling (see 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [47]) by setting the IM CN Subsystem signalling flag in the PCO IE. Specifically, the GGSN/P-GW may receive the IM CN Subsystem signalling flag in the PCO IE in the PDP context activation or Secondary PDP context activation for GERAN and UTRAN accesses; in the Attach, UE-requested PDN connectivity request or UE-requested bearer resource modification procedures for E-UTRAN access. If the bearer establishment selected for the APN is controlled by the network, depending on the operator policy, the GGSN or P-GW may also activate a PDP context or dedicated EPS bearer for IMS signalling via network-initiated Secondary PDP context activation or network-initiated Dedicated Bearer activation procedures, respectively. If dedicated PDP contexts/EPS Bearers for IMS signalling are not supported, the GGSN/P-GW will reset the signalling flag in the response to the MS/UE. For P-GW, if the APN offers non-IMS services, the default bearer shall not be allowed to be set up as a dedicated IM CN signalling bearer. If the PDP context/EPS bearer can be established as a dedicated bearer for IMS signalling, the GGSN/P-GW can provide a set of UL filters for the PDP context/EPS bearer used for IMS. The UL filters provide the MS/UE with the rules and restrictions applied by the GGSN/P-GW for the dedicated PDP context/EPS bearer for IMS signalling. The GGSN/P-GW can in addition provide the IMS signalling flag to explicitly indicate to the MS/UE the intention of using the PDP context/EPS bearer for IMS related signalling. In both cases, I and II, - The GGSN may receive the Signalling Indication parameter in the QoS IE. This indicates a request for prioritised handling over the radio interface. The GGSN shall be able to downgrade the QoS (dependent on operator policy) by resetting the Signalling Indication according to the normal procedures for QoS negotiation, see 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [3]. - During the (default or dedicated) EPS bearer activation procedure, the P-GW may receive the request for appropriate QCI for IMS signalling traffic as specified in 3GPP TS 23.203[ Policy and charging control architecture ] [90] in EPS bearer QoS IE that indicates the prioritised handling of the EPS bearer over the radio interface. The P-GW may either accept or reject the request based on the operator policy configured at the P-GW. IM CN subsystem signalling flag and Signalling Indication or appropriate QCI for IMS signalling in the QoS IE may be used independently of each other. However, based on the operator policy, the network may honor the Signalling Indication or appropriate QCI for IMS signalling if the IM CN Subsystem signalling flag is present in PCO IE. The operator may provide other properties to the PDP contexts/EPS bearers dedicated for IMS signalling, e.g. special charging. It is out of the current scope of this TS to further specify these properties. For a PDP Context/EPS bearer marked as a dedicated for IMS signalling, the GGSN/P-GW shall apply the applicable PCC rules, as specified in 3GPP TS 29.212[ Policy and Charging Control (PCC); Reference points ] [75], and/or locally preconfigured packet filters, which shall only allow packets to be sent to and from a set of signalling servers, such as P-CSCF(s), DHCP server(s) and DNS server(s). The TFT filters on the dedicated signalling bearer shall have a precedence value so that they precede any other TFT filters. This will secure the use of the correct PDP context/EPS bearer for the signalling traffic, and that only authorized traffic uses the signalling PDP context. The locally preconfigured packet filters shall be defined in the GGSN/P-GW by the operator.

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

13a.2.2.2

A.5 Monitor of cell level QoS and radio resource utilisation

In an E-UTRAN cell the quality of service achieved is directly influenced by a number of factors, including: - Loading of users on the cell - Traffic loading and characteristics - UE locations and mobility - RRM policies - Scheduling - congestion control - admission control - layer 2 protocol configuration - Mapping of traffic to QCI - Setting of QoS parameters other than the QCI. It is very important to be able to monitor the QoS to determine whether the combined effect of these policies, algorithms and external factors is satisfactory. Unsatisfactory QoS may be rectified by adjusting policies and RRM settings, for instance.In case the rectification is not leading to desired QoS some other policies (ACB, rejected RRC connection setup) based on restricting the UEs for network access to the cell may be applied Cell bit-rate A fundamental measure of QoS is the throughput (data rate) of the cell. The total cell throughput measured across all radio bearers gives an indication of the loading and activity in the cell. Adding a per QCI counter allows the loading on the different QCIs to be measured. For example, if QCI 1 is used exclusively for VoIP then the loading of conversational speech can be directly determined. Finally, the maximum throughput can indicate to the operator whether there is enough capacity in the network; for example, is the backhaul sufficient. Separate counters should be configured on the downlink and uplink. Complexity may be reduced by performing the counters at layer 3, giving the ingress bit-rate to the eNB on the downlink and the egress bit-rate from the eNB on the uplink. Cell throughput includes both User Plane data and Control Plane data. To support the User Plane data, necessary Control Plane data also need to be transmitted. This Control Plane data although required, will not be perceived (felt) by the User. The total cell throughput helps to evaluate the usage of bandwidth and radio resource. Operators ideally want to see the Control Plane data as small as possible when compared to the User Plane data without compromising on the service. Hence it is important to monitor the total cell throughput as well as how much is occupied by Control Plane Data. Number of actives UEs It is also of interest to determine how many users are enjoying the throughput numbers determined for each QCI. Therefore, we may count the number of users that are active for each QCI – here active users have data queued pending transmission. A simple division of the throughput (data rate) of a QCI by the number of active users on the QCI indicates the throughput per user on the QCI. For example, taking QCI 1 this metric could indicate the typical codec rate being employed in the cell. Alternatively, for QCI 9 supporting low priority TCP-based traffic it can indicate the typical bandwidth pipe size for a user when he has data to send / receive. DL packet delay Latency is of prime concern for some services, particularly conversational services like speech and instant messaging. A counter is added to measure the mean delay for IP packets incurred within the eNodeB. Separate counters are provided per QCI which are particularly useful when the QCI is used by very few services and the packet sizes vary little. It is only practical to measure packet delays on the downlink. In case of the eNodeB serving one or more RN, the packet delay includes both the internal processing delay at eNB) and UE/RN as well as the packet transferring delay on the radio link. As RN UE’s packets need to be transferred via between E-UTRAN snfRN while packets for UEs directly connected to eNB need to pass through only Uu interface, packet delay optimization mechanism may be different for RN UEs and eNB UEs. Therefore it is beneficial to have measurements on packet delay separately for packets transmitted between the eNodeB and UEs and for packets transmitted between the E-UTRAN and RNs. DL packet drop rate When a cell is heavily loaded congestion can take place. When congestion is not severe. the impact is typically the incurrence of additional delay for non-GBR radio bearers. However, when congestion is severe the eNodeB may be forced to discard packets. It is important for the operator to have visibility of packet discard so that corrective action can be instigated (for example, by adjusting admission control settings in the network). It is only practical to measure packet discards on the downlink. Packet discards on handover should not be included in the count. PRB Usage The resource utilisation, measured in terms of physical resource blocks (PRBs), is a useful measure of whether a cell is lightly loaded or not. Loading is a key input to network capacity planning and load balancing. Furthermore, when resource utilisation per QCI is reported the distribution of resources between different services can be estimated. The PRB usage distribution could provide operators the load distribution information of the network during the collecting time period.According to the PRB usage distribution information, the scenarios where a cell may experience high load in certain short times (e.g. in a second) and recover to normal very quickly can be recognized.The PRB usage distribution is a useful measure for operator to be aware of whether a cell has ever experienced high load or not in the monitoring duration. This distribution information could also help in the root cause analysis in case when the application problems are caused by load bursts. The distribution information could show the median usage and the peak usage. The median usage is within the range of the bin that got the highest number of samples and the peak usage is within the range of the “highest” bin that got >0 samples. The distribution information is a key input to network capacity planning and load balancing. For a RN that requires subframe configuration, the RN can only be scheduled by the eNodeB within subframes configured for RN, while macro UE can be scheduled in any subframe. Therefore, in certain scenario it may be possible that the PRB usage is different for the subframe configured for the RN and for any other subframe. For example, in case there are many RNs in the network and only a few UEs connected directly to the eNodeB, it may happen that the PRB usage in the subframe configured for RN is quite high, while the subframes used for UEs is low. Therefore, it is beneficial to measure the PRB usage separately for RN and the total PRB usage. The total PRB usage includes the PRB usage for RN traffic and UE traffic, while the RN PRB usage includes only PRB usage for RN traffic. Resource Full Utilisation Resource congestion is a critical situation in the network that needs to be monitored closely in order to be assessed and addressed immediately (e.g. by expanding related resources). Measurements reflecting the time during which the resources are fully used are needed to properly assess the congestion. Congestion affects PRB so appropriate congestion measurements are needed. Transport Resource Usage Transport resource utilisation provides information on the overall traffic of an eNodeB with the rest of the network, together with information on the traffic of the individual cells it gives the ability to localise bottlenecks. On the other hand it is a key input for planning of timely expansion of transport (backhaul) resources in the network provides . Measurements enabling to track the transport resource utilisation are therefore useful. Hardware Resource Usage Hardware resource utilisation provides information on the overall load of an eNodeB, together with the information on the individual loads it gives the ability to localise bottlenecks. On the other hand it is a key input for planning of timely expansion of hardware resources in the network. Measurements enabling to track the hardware resource utilisation are therefore useful. Downlink Air interface packet loss rate The downlink air interface packet loss can be directly compared with the PELR value of a QCI to see if the packet loss (over the air interface) aspect of quality of service is being met within the cell (see [12] for more details on PELR). On the downlink this measurement can be added to the congestion losses (see DL packet drop rate) to determine the total packet loss rate at the eNodeB. Consequently, the downlink useful bit-rate can be estimated by scaling the measurement of the downlink PDCP ingress bit-rate by (1 – DL packet drop rate) (1 – air interface packet loss rate). In case or RN deployment the communicstion between the E-UTRAN and RN is going through the air interface. It is possible that the radio conditions are bad, which can lead also to high packet loss rate, which can contribute also whether the packet loss aspect of the quality of service is met or not. Therefore it is beneficial to have separate packet loss rate measurement for RN traffic and for the traffic connected directly to the eNodeB. Uplink packet loss rate The uplink air interface packet loss rate (per QCI) can be compared directly with the PELR defined for that QCI. An estimate of the uplink air interface packet loss may be provided by the “Uplink PDCP SDU loss rate”. This uplink measurement is based on PDCP sequence numbers and cannot precisely measure the air interface losses. Any packets discarded by the UE within the protocol stack (i.e. at layer 2) are also counted since they will have been given a PDCP sequence number. Discards at layer 3 are not counted. In case or RN deployment the communicstion between the E-UTRAN and RN is going through the air interface. It is possible that the radio conditions are bad, which can lead also to high packet loss rate, which can contribute also whether the packet loss aspect of the quality of service is met or not. Therefore it is beneficial to have separate packet loss rate measurement for RN traffic and for the traffic connected directly to the eNodeB. RACH Usage The RACH plays a vital role in the following procedures: - Initial access from RRC_IDLE; - Initial access after radio link failure; - Handover requiring random access procedure; - DL data arrival during RRC_CONNECTED requiring random access procedure; - UL data arrival during RRC_CONNECTED requiring random access procedure; Furthermore, the random access procedure takes two distinct forms: - Contention based using a randomly selected preamble (applicable to all five events); - Non-contention based using a dedicated preamble (applicable to only handover and DL data arrival). In the use-case of RACH configuration optimization, received Random Access Preambles and a contention indicator are signalled across an OAM interface. Monitoring of the preamble usage in a cell allows the operator to determine if the resources allocated to the RACH by the eNodeB are appropriate for the number of random access attempts. If the resources are underutilised then the operator may reconfigure the eNodeB (via CM) to allocate less resource to RACH thereby freeing up resource for other uplink transmissions. Alternatively, if the resources are heavily utilised then this is indicative of RACH congestion leading to increased latency for the procedures listed above. To this effect, measurements directly reflecting RACH congestion experienced by the eNodeB and by the UEs are useful. The eNodeB can partition the RACH resource between dedicated preambles, randomly selected preambles in group A and randomly selected preambles in group B. This partitioning can be evaluated when usage measurements are made on each set separately. To further monitor and analyze the latency of the procedures listed above created at the RACH level, the measurement of the number of RACH preambles sent per RACH attempt is useful. RACH optimisation function optimises RACH related configurations to achieve minimizing of access delays and random access collision probability for all the UEs. eNB may request the UEs to report the number of attempts to access the network (numberOfPreamblesSent in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]). Based on the attempting number of random access of all the UEs, the eNB can know the distribution of RACH preambles sent by UEs and calculate the access probability (AP) of a cell accurately. The eNB may also request the UEs to report contention detected while attempting to access the network (contentionDetected in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]). Based on the estimated time per random access and the estimated contention level in the network, the eNB can estimate the access delay probability (ADP) of a cell. Time period the requested quality of service cannot be achieved An overload situation in the cell can be related also to other conditions leading to insufficient QoS. That means UE is allowed for network access but later one due to some other reason either the session is dropped, or there is big PDCP SDU delay or low IP scheduled throughput, etc. leading to degradation of quality of provided services. Let’s consider a UE which is having an GBR service ongoing. The radio conditions in the cell are bad and thus despite there is no RLF detected for the UE because the QoS characteristics for the UE like throughput and delay cannot be achieved the UE is either abnormally released or quality of provided services has significantly degraded. Another example could be for the UE having an nonGBR service ongoing and RLF has been detected which leads to abnormal UE release or significant degradation of quality of provided services as well. In both cases despite the cell serving the UEs did its best from the point of view the most robust MCSs and thus maximum possible resources used, maximum UE transmit power and using other possible techniques (like HO, redirection….) it was not possible to keep the UEs active in the cell with guaranteed QoS simply because the cell did not have the needed capacity (features) to do so. For the operator it is therefore very important to have measurements to monitor duration the requested quality of service cannot be achieved.

3GPP TS 32.425

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

SA WG5

3GPP Series : 32 , OAM&P and Charging

A.5

14.1.2.1 Nausf_UEAuthentication_Authenticate service operation

Service operation name: Nausf_UEAuthentication_authenticate. Description: Authenticate the UE and provides related keying material. Input, Required: One of the options below. 1. In the initial authentication request: SUPI or SUCI, serving network name. 2. In the subsequent authentication requests depending on the authentication method: a. 5G AKA: Authentication confirmation message with RES* as described in clause 6.1.3.2 or Synchronization Failure indication and related information (i.e. RAND/AUTS). b. EAP-AKA’: EAP packet as described in RFC 4187 [21] and RFC 5448 [12], and Annex F. Input, Optional: Disaster Roaming service indication, NSWO indicator. NOTE: If NSWO indicator is present then the serving network name contains "5G:NSWO". Output, Required: One of the options below. 1. Depending on the authentication method: a. 5G AKA: authentication vector, as described in clause 6.1.3.2 or Authentication confirmation acknowledge message. b. EAP-AKA’: EAP packet as described in RFC 4187 [21] and RFC 5448 [12], and Annex F. 2. Authentication result and if success the master key which are used by AMF to derive NAS security keys and other security key(s). Output, Optional: SUPI if the authentication was initiated with SUCI, MSK if either NSWO indicator was received as input or MSK indicator was received from UDM.

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

14.1.2.1

5.2.3.2.4 Nudm_UECM_Get service operation

Service operation name: Nudm_UECM_Get. Description: The NF consumer requests the UDM to get the NF ID or SMS address of the NF serving the UE. Inputs, Required: UE ID, NF Type. Inputs, Optional: Access Type, Analytics ID(s) (if NF Type is NWDAF), indication to retrieve PDU Session ID information. - Access Type is included when the NF type indicates SMSF. Outputs, Required: NF ID or SMS address of the NF corresponding to the NF type requested by NF consumer. If the NF Type requested by NF consumer is AMF, the Access Type corresponding to the AMF is also included. Analytics ID(s), if NF Type is NWDAF. Outputs, Optional: SUPI or GPSI or both, PDU Session ID(s) already registered in the UDM for the UE. For more information on retrieving PDU Session information, refer to clause 4.11.0a.5.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

5.2.3.2.4

5.3.5.8.2 Inability to comply with RRCReconfiguration

NOTE 00: The UE behaviour specified in this clause does not apply to the following, and the UE ignores, i.e. does not take an action on and does not store, the fields that it does not support or does not comprehend: - The fields in ServingCellConfigCommon that are defined in Rel-16 and later. - The fields of searchSpaceMCCH and searchSpaceMTCH in PDCCH-ConfigCommon that are defined in Rel-17 and later. The UE shall: 1> if the UE is in (NG)EN-DC: 2> if the UE is unable to comply with (part of) the configuration included in the RRCReconfiguration message received over SRB3; 3> if the RRCReconfiguration message was received as part of ConditionalReconfiguration: 4> continue using the configuration used prior to when the inability to comply with the RRCReconfiguration message was detected; 3> else: 4> continue using the configuration used prior to the reception of RRCReconfiguration message; 3> if MCG transmission is not suspended: 4> initiate the SCG failure information procedure as specified in clause 5.7.3 to report SCG reconfiguration error, upon which the connection reconfiguration procedure ends; 3> else: 4> initiate the connection re-establishment procedure as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10], clause 5.3.7, upon which the connection reconfiguration procedure ends; 2> else, if the UE is unable to comply with (part of) the configuration included in the RRCReconfiguration message received over SRB1; 3> if the RRCReconfiguration message was received as part of ConditionalReconfiguration: 4> continue using the configuration used prior to when the inability to comply with the RRCReconfiguration message was detected; 3> else: 4> continue using the configuration used prior to the reception of RRCReconfiguration message; 3> initiate the connection re-establishment procedure as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10], clause 5.3.7, upon which the connection reconfiguration procedure ends. 1> else if RRCReconfiguration is received via NR (i.e., NR standalone, NE-DC, or NR-DC): 2> if the UE is unable to comply with (part of) the configuration included in the RRCReconfiguration message received over SRB3; NOTE 0: This case does not apply in NE-DC. 3> if the RRCReconfiguration message was received as part of ConditionalReconfiguration; or, 3> if the RRCReconfiguration message was received as part of ltm-Config: 4> continue using the configuration used prior to when the inability to comply with the RRCReconfiguration message was detected; 3> else: 4> continue using the configuration used prior to the reception of RRCReconfiguration message; 3> if MCG transmission is not suspended: 4> initiate the SCG failure information procedure as specified in clause 5.7.3 to report SCG reconfiguration error, upon which the connection reconfiguration procedure ends; 3> else: 4> initiate the connection re-establishment procedure as specified in clause 5.3.7, upon which the connection reconfiguration procedure ends; 2> else if the UE is unable to comply with (part of) the configuration included in the RRCReconfiguration message received over the SRB1 or if the upper layers indicate that the nas-Container is invalid: NOTE 0a: The compliance also covers the SCG configuration carried within octet strings e.g. field mrdc-SecondaryCellGroupConfig. I.e. the failure behaviour defined also applies in case the UE cannot comply with the embedded SCG configuration or with the combination of (parts of) the MCG and SCG configurations. NOTE 0b: The compliance also covers the V2X sidelink configuration carried within an octet string, e.g. field sl-ConfigDedicatedEUTRA. I.e. the failure behaviour defined also applies in case the UE cannot comply with the embedded V2X sidelink configuration. 3> if the RRCReconfiguration message was received as part of ConditionalReconfiguration; or, 3> if the RRCReconfiguration message was received as part of ltm-Config: 4> continue using the configuration used prior to when the inability to comply with the RRCReconfiguration message was detected; 3> else: 4> continue using the configuration used prior to the reception of RRCReconfiguration message; 3> if AS security has not been activated: 4> perform the actions upon going to RRC_IDLE as specified in 5.3.11, with release cause 'other' 3> else if AS security has been activated but SRB2 and at least one DRB or multicast MRB or, for IAB and NCR, SRB2, have not been setup: 4> perform the actions upon going to RRC_IDLE as specified in 5.3.11, with release cause 'RRC connection failure'; 3> else: 4> initiate the connection re-establishment procedure as specified in 5.3.7, upon which the reconfiguration procedure ends; 1> else if RRCReconfiguration is received via other RAT (Handover to NR failure): 2> if the UE is unable to comply with any part of the configuration included in the RRCReconfiguration message or if the upper layers indicate that the nas-Container is invalid: 3> perform the actions defined for this failure case as defined in the specifications applicable for the other RAT. NOTE 1: The UE may apply above failure handling also in case the RRCReconfiguration message causes a protocol error for which the generic error handling as defined in clause 10 specifies that the UE shall ignore the message. NOTE 2: If the UE is unable to comply with part of the configuration, it does not apply any part of the configuration, i.e. there is no partial success/failure. NOTE 3: It is up to UE implementation whether the compliance check for an RRCReconfiguration received as part of ConditionalReconfiguration is performed upon the reception of the message or upon CHO, CPA, CPC, and subsequent CPAC execution (when the message is required to be applied). NOTE 4: It is up to UE implementation whether the compliance check for an RRCReconfiguration message received as part of an LTM-Config IE is performed upon the reception of the message or during an LTM cell switch procedure (when the message is required to be applied).

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

5.3.5.8.2

4.3.7.4 MME control of overload 4.3.7.4.1 General

The MME shall contain mechanisms for avoiding and handling overload situations. These can include the use of NAS signalling to reject NAS requests from UEs. In addition, under unusual circumstances, the MME shall restrict the load that its eNodeBs are generating on it if it is configured to enable the overload restriction. This can be achieved by the MME invoking the S1 interface overload procedure (see TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5] and TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36]) to all or to a proportion of the eNodeB's with which the MME has S1 interface connections. To reflect the amount of load that the MME wishes to reduce, the MME can adjust the proportion of eNodeBs which are sent S1 interface OVERLOAD START message, and the content of the OVERLOAD START message. The MME should select the eNodeBs at random (so that if two MMEs within a pool area are overloaded, they do not both send OVERLOAD START messages to exactly the same set of eNodeBs). The MME may optionally include a Traffic Load Reduction Indication in the OVERLOAD START message. In this case the eNodeB shall, if supported, reduce the type of traffic indicated according the requested percentage (see TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36]). NOTE 1: The MME implementation may need to take into account the fact that eNodeBs compliant to Release 9 and earlier version of the specifications do not support the percentage overload indication. An MME supporting Control Plane CIoT EPS Optimisation may include an indication in the OVERLOAD START message indicating overload from data transfers via Control Plane CIoT EPS Optimisation. Using the OVERLOAD START message, the MME can request the eNodeB to: - reject RRC connection requests that are for non-emergency, non-exception reporting and non-high priority mobile originated services; or NOTE 2: This blocks PS service and service provided by MSC following an EPS/IMSI attach procedure. - reject new RRC connection requests for EPS Mobility Management signalling (e.g. for TA Updates) for that MME; - only permit RRC connection requests for emergency sessions and mobile terminated services for that MME. This blocks emergency session requests from UEs with USIMs provisioned with Access Classes 11 and 15 when they are in their HPLMN/EHPLMN and from UEs with USIMs provisioned with Access Classes 12, 13 and 14 when they are in their home country (defined as the MCC part of the IMSI, see TS 22.011[ Service accessibility ] [67]); or. NOTE 3: The MME can restrict the number of responses to paging by not sending paging messages for a proportion of the events that initiate paging. As part of this process, the MME can provide preference for paging UEs with Emergency Bearer Services and terminations associated with MPS ARP. - only permit RRC connection requests for high priority sessions, exception reporting and mobile terminated services for that MME; - reject new RRC connection requests from UEs that access the network with low access priority; - not accept RRC connection requests with RRC establishment cause "mo-data" or "delayTolerantAccess" from UEs that only support Control Plane CIoT EPS Optimisation. NOTE 4: The RRC connection requests listed in this clause also include the request for RRC Connection Resume. When rejecting an RRC connection request for overload reasons the eNodeB indicates to the UE an appropriate timer value that limits further RRC connection requests for a while. An eNodeB supports rejecting of RRC connection establishments for certain UEs as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [37]. Additionally, an eNodeB provides support for the barring of UEs configured for Extended Access Barring, as described in TS 22.011[ Service accessibility ] [67]. These mechanisms are further specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [37]. If the UE is camping on NB-IoT, Extended Access Barring does not apply. An eNodeB may initiate Extended Access Barring when: - all the MMEs connected to this eNodeB request to restrict the load for UEs that access the network with low access priority; or - requested by O&M. If an MME invokes the S1 interface overload procedure to restrict the load for UEs that access the network with low access priority, the MME should select all eNodeBs with which the MME has S1 interface connections. Alternatively, the selected eNodeBs may be limited to a subset of the eNodeBs with which the MME has S1 interface connection (e.g. particular location area or where devices of the targeted type are registered). During an overload situation the MME should attempt to maintain support for emergency bearer services (see clause 4.3.12) and for MPS (see clause 4.3.18). When the MME is recovering, the MME can either: - send OVERLOAD START messages with new percentage value that permit more traffic to be carried, or - the MME sends OVERLOAD STOP messages. to some, or all, of the eNodeB(s). In addition, to protect the network from overload the MME has the option of rejecting NAS request messages which include the low access priority indicator before rejecting NAS request messages without the low access priority indicator (see clause 4.3.7.4.2 for more information). NOTE 5: It cannot be guaranteed that voice services will be available for mobile terminated calls while the Mobility Management back-off timer is running. It is recommended, that UEs requiring voice services are not configured for low access priority. In addition, for UEs that don't support the Service Gap Control feature (see clause 4.3.17.9), the MME may use "General NAS level Mobility Management control" as defined in clause 4.3.7.4.2.1.

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

Suspend Acknowledge

The Suspend Acknowledge message shall be sent on the S11 interface by the SGW to the MME and on the S5/S8 interface by the PGW to the SGW as part of the 1xRTT CS fallback procedures in 3GPP TS 23.272[ Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2 ] [21]. The Suspend Acknowledge message shall be sent on the S3 interface by the MME to the SGSN, on the S11 interface by the SGW to the MME and on the S5/S8 interface by the PGW to SGW as part of the SRVCC procedures in 3GPP TS 23.216[ Single Radio Voice Call Continuity (SRVCC); Stage 2 ] [43] or the CS fallback from E-UTRAN access to UTRAN/GERAN CS domain access related procedures in 3GPP TS 23.272[ Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2 ] [21]. The Suspend Acknowledge message shall be sent on the S16 interface as per the inter-SGSN suspend procedures in 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [35]. The Suspend Acknowledge message shall be sent on the S16, the S4 and the S5/S8 interfaces as part of the SRVCC from UTRAN (HSPA) to GERAN without DTM support procedure in 3GPP TS 23.216[ Single Radio Voice Call Continuity (SRVCC); Stage 2 ] [43]. The Suspend Acknowledge message shall be sent on the S4 and the S5/S8 interfaces as part of the CS fallback from E-UTRAN to GERAN CS domain related procedures in 3GPP TS 23.272[ Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2 ] [21]. Possible Cause values are specified in Table 8.4-1. For backward compatibility, if the IMSI IE is missing in the Suspend Notification message that is received on the S11 interface, the cause value "Mandatory IE missing" shall be used. Table 7.4.2-1 specifies the presence requirements and conditions of the IEs in the message. Table -1: Information Element in Suspend Acknowledge

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

Suspend

12.3.6 Propagating the MME/S4-SGSN identity to the PGW

When the Overload Control feature is supported by the MME/S4-SGSN and the SGW, and it is also activated for the PLMN to which the PGW belongs (see clause 12.3.11), the following shall apply: - The MME/S4-SGSN shall include the MME/S4-SGSN identity towards the SGW during: - the PDN connection establishment, any mobility with an MME/S4-SGSN change or any SGW change procedures; - the dedicated bearer activation procedure, PGW initiated bearer modification procedure and PGW initiated bearer deactivation procedure as per the conditions specified in the corresponding messages. - The SGW shall forward the MME/S4-SGSN identifier to the PGW if it is received in the Create/Update/Delete Bearer Response messages. When it is received in other GTP-C messages, the SGW shall store the received MME/S4-SGSN identity and shall include the currently serving MME/S4-SGSN's identity in subsequent Modify Bearer Request messages which are sent over the S5/S8 interface, whenever there is signalling over the S5/S8 interface. NOTE: This allows updating of the PGW with the identity of the new MME/S4-SGSN during inter-MME/SGSN mobility scenarios as early as possible and without generating extra signalling over the S5/S8 interface. Inter-MME/inter-SGSN intra SGW mobility scenarios not requiring to send any S5/S8 signalling could result in the PGW not being updated with the currently serving MME/S4-SGSN's identity, for a given subscriber, until subsequent S5/S8 signalling takes place for the same PDN connection. However, considering these scenarios are not so frequent and considering that several features anyway require S5/S8 signalling during these scenarios (e.g. for user location reporting), the PGW will most often get the identity of the currently serving MME/S4-SGSN. Hence the risk that the PGW wrongly throttles PGW initiated signalling for that PDN connection, if the old MME/S4-SGSN is in overload, is low. - The PGW shall store the currently serving MME/S4-SGSN identity, received from the SGW, to be able to reduce the PGW initiated signalling messages for the PDN connections during an overload situation at the serving MME/S4-SGSN.

3GPP TS 29.274

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

CT WG4

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

12.3.6

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

If the SM cause value is different from #26 "insufficient resources", #50 "PDP type IPv4 only allowed", #51 "PDP type IPv6 only allowed", #57 "PDP type IPv4v6 only allowed", #58 "PDP type non IP only allowed", #65 "maximum number of PDP contexts reached", and #66 "requested APN not supported in current RAT and PLMN combination", and the Back-off timer value IE is included, the MS shall take different actions depending on the timer value received in the Back-off timer value IE (if the MS is an MS configured to use AC11 – 15 in selected PLMN, exceptions are specified in subclause 6.1.3.13): i) if the timer value indicates neither zero nor deactivated, the MS shall start the back-off timer with the value provided in the Back-off timer value IE for the PDP context activation procedure and PLMN and combination and: - shall not send another ACTIVATE PDP CONTEXT REQUEST message in the PLMN for the same APN that was sent by the MS, until the back-off timer expires, the MS is switched off or the SIM/USIM is removed; and - shall not send another ACTIVATE PDP CONTEXT REQUEST message in the PLMN without an APN if the APN was not included in the ACTIVATE PDP CONTEXT REQUEST message, until the back-off timer expires, the MS is switched off or the SIM/USIM is removed; ii) if the timer value indicates that this timer is deactivated, the MS: - shall not send another ACTIVATE PDP CONTEXT REQUEST message in the PLMN for the same APN that was sent by the MS, until the MS is switched off or the SIM/USIM is removed; and - shall not send another ACTIVATE PDP CONTEXT REQUEST message in the PLMN without an APN if the APN was not included in the ACTIVATE PDP CONTEXT REQUEST message, until the MS is switched off or the SIM/USIM is removed; and iii) if the timer value indicates that this timer is zero, the MS: - may send an ACTIVATE PDP CONTEXT REQUEST message in the PLMN for the same APN; and - may send an ACTIVATE PDP CONTEXT REQUEST message in the PLMN without an APN if the APN was not included in the ACTIVATE PDP CONTEXT REQUEST message. If the Back-off timer value IE is not included, then the MS shall ignore the Re-attempt indicator IE provided by the network, if any. i) Additionally, if the SM cause value is #8 "operator determined barring", #27 "missing or unknown APN", #32 "service option not supported", or #33 "requested service option not subscribed", the MS shall proceed as follows: - if the MS is registered in its HPLMN or in a PLMN that is within the EHPLMN list (if the EHPLMN list is present), the MS shall behave as described above in the present subclause, using the configured SM_RetryWaitTime value as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [135] or in USIM file NASCONFIG as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [112], if available, as back-off timer value; and - otherwise, if the MS is not registered in its HPLMN or in a PLMN that is within the EHPLMN list (if the EHPLMN list is present), or if the SM_RetryWaitTime value is not configured, the MS shall behave as described above in the present subclause using the default value of 12 minutes for the back-off timer. ii) For SM cause values different from #8 "operator determined barring", #27 "missing or unknown APN", #32 "service option not supported", or #33 "requested service option not subscribed", the MS behaviour regarding the start of a back-off timer is unspecified. The MS shall not stop any back-off timer upon a PLMN change or inter-system change. If the network indicates that a back-off timer for the PDP context activation procedure and PLMN and APN combination is deactivated, then it remains deactivated upon a PLMN change or inter-system change. NOTE 1: This means the back-off timer can still be running or be deactivated for the given SM procedure and PLMN and APN combination when the MS returns to the PLMN or when it performs inter-system change back from S1 mode to A/Gb or Iu mode. Thus the MS can still be prevented from sending another ACTIVATE PDP CONTEXT REQUEST message in the PLMN for the same APN. If the back-off timer is started upon receipt of an ACTIVATE PDP CONTEXT REJECT message (i.e. the timer value was provided by the network, a configured value is available or the default value is used as explained above) or the back-off timer is deactivated, the MS behaves as follows: i) after a PLMN change the MS may send an ACTIVATE PDP CONTEXT REQUEST message for the same in the new PLMN, if the back-off timer is not running and is not deactivated for the PDP context activation procedure and the combination of new PLMN and APN; Furthermore as an implementation option, for the SM cause values #8 "operator determined barring", #27 "missing or unknown APN", #32 "service option not supported" or #33 "requested service option not subscribed", if the network does not include a Re-attempt indicator IE, the MS may decide not to automatically send another ACTIVATE PDP CONTEXT REQUEST message for the same APN, if the MS registered to a new PLMN which is in the list of equivalent PLMNs. ii) if the network does not include the Re-attempt indicator IE to indicate whether re-attempt in S1 mode is allowed, or the MS ignores the Re-attempt indicator IE, e.g. because the Back-off timer value IE is not included, then: - if the MS is registered in its HPLMN or in a PLMN that is within the EHPLMN list (if the EHPLMN list is present), the MS shall apply the configured SM_RetryAtRATChange value as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [135] or in USIM file NASCONFIG as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [112], if available, to determine whether the MS may attempt a PDN connectivity procedure for the same PLMN and APN combination in S1 mode; and - if the MS is not registered in its HPLMN or in a PLMN that is within the EHPLMN list (if the EHPLMN list is present), or if the NAS configuration MO as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [135] is not available and the value for inter-system change is not configured in the USIM file NASCONFIG, then the MS behaviour regarding a PDN connectivity procedure for the same PLMN and APN combination in S1 mode is unspecified; and iii) if the network includes the Re-attempt indicator IE indicating that re-attempt in an equivalent PLMN is not allowed, then depending on the timer value received in the Back-off timer value IE, for each combination of a PLMN from the equivalent PLMN list and the APN the MS shall start a back-off timer for the PDP context activation procedure with the value provided by the network, or deactivate the respective back-off timer as follows: - If the Re-attempt indicator IE additionally indicates that re-attempt in S1 mode is allowed, the MS shall start or deactivate the back-off timer for A/Gb and Iu mode only; and - otherwise the MS shall start or deactivate the back-off timer for A/Gb, Iu, and S1 mode. If the back-off timer for a PLMN and APN combination was started or deactivated in S1 mode upon receipt of a PDN CONNECTIVITY REJECT message (see 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120]) and the network indicated that re-attempt in A/Gb or Iu mode is allowed, then this back-off timer does not prevent the MS from sending an ACTIVATE PDP CONTEXT REQUEST message in this PLMN for the same APN in A/Gb or Iu mode. If the network indicated that re-attempt in A/Gb or Iu mode is not allowed, the MS shall not send any ACTIVATE PDP CONTEXT REQUEST message in this PLMN for the same APN in A/Gb or Iu mode until the back-off timer expires, the MS is switched off or the USIM is removed. NOTE 2: The back-off timer is used to describe a logical model of the required MS behaviour. This model does not imply any specific implementation, e.g. as a timer or timestamp. NOTE 3: Reference to back-off timer in this section can either refer to use of timer T3396 or to use of a different packet system specific timer within the MS. Whether the MS uses T3396 as a back-off timer or it uses different packet system specific timers as back-off timers is left up to MS implementation. This back-off timer is stopped when the MS is switched off or the SIM/USIM is removed. The MS may initiate a PDP context activation procedure for emergency bearer services even if the back-off timer is running. If the SM cause value is #50 "PDP type IPv4 only allowed", #51 "PDP type IPv6 only allowed", #57 "PDP type IPv4v6 only allowed" or #58 "PDP type non IP only allowed", the MS shall ignore the Back-off timer value IE provided by the network, if any. The MS shall not automatically send another ACTIVATE PDP CONTEXT REQUEST message for the same APN that was sent by the MS using the same PDP type, until any of the following conditions is fulfilled: - the MS is registered to a new PLMN, and either the network did not include a Re-attempt indicator IE in the ACTIVATE PDP CONTEXT REJECT message or the Re-attempt indicator IE included in the message indicated that re-attempt in an equivalent PLMN is allowed; - the MS is registered to a new PLMN which was not in the list of equivalent PLMNs at the time when the ACTIVATE PDP CONTEXT REJECT message was received; - the PDP type which is used to access to the APN is changed; - the MS is switched off; or - the SIM/USIM is removed. For the SM cause values #50 "PDP type IPv4 only allowed", #51 "PDP type IPv6 only allowed", #57 "PDP type IPv4v6 only allowed" and #58 "PDP type non IP only allowed", the MS shall ignore the value of the RATC bit in the Re-attempt indicator IE provided by the network, if any. NOTE 4: For the SM cause values #50 "PDP type IPv4 only allowed", #51 "PDP type IPv6 only allowed", #57 "PDP type IPv4v6 only allowed" and #58 "PDP type non IP only allowed", re-attempt in S1 mode for the same APN (or no APN, if no APN was indicated by the MS) using the same PDP type is not allowed. Furthermore as an implementation option, for the SM cause values #50 "PDP type IPv4 only allowed", #51 "PDP type IPv6 only allowed", #57 "PDP type IPv4v6 only allowed" and #58 "PDP type non IP only allowed", if the network does not include a Re-attempt indicator IE the MS may decide not to automatically send another ACTIVATE PDP CONTEXT REQUEST message for the same APN that was sent by the MS using the same PDP type, if the MS registered to a new PLMN which is in the list of equivalent PLMNs. NOTE 5: Request to send another ACTIVATE PDP CONTEXT REQUEST message with a specific PDP type has to come from upper layers. If the SM cause value is #65 "maximum number of PDP contexts reached", the MS shall determine the PLMN's maximum number of PDP contexts in A/Gb or Iu mode (see subclause 6.1.3.0) as the number of active PDP contexts it has. The MS shall ignore the Back-off timer value IE and Re-attempt indicator IE provided by the network, if any. NOTE 6: In some situations, when attempting to establish multiple PDP contexts, the number of active PDP contexts that the MS has when SM cause #65 is received is not equal to the maximum number of PDP contexts reached in the network. NOTE 7: When the network supports emergency bearer services, it is not expected that SM cause #65 is returned by the network when the MS requests a PDP context for emergency bearer services. The PLMN's maximum number of PDP contexts in A/Gb or Iu mode applies to the PLMN in which the SM cause #65 "maximum number of PDP contexts reached" is received. When the MS is switched off or when the USIM is removed, the MS shall clear all previous determinations representing any PLMN's maximum number of PDP contexts in A/Gb or Iu mode (see subclause 6.1.3.0). Upon successful registration with a new PLMN, the MS may clear previous determinations representing any PLMN's maximum number of PDP contexts in A/Gb or Iu mode. If the SM cause value is #66 "requested APN not supported in current RAT and PLMN combination", the MS shall take different actions depending on the Back-off timer value IE and the Re-attempt indicator IE optionally included: i) If the Back-off timer value IE is not included, and either the Re-attempt indicator IE is not included or the Re-attempt indicator IE is included indicating that re-attempt in an equivalent PLMN is allowed, the MS shall not send an ACTIVATE PDP CONTEXT REQUEST message for the same APN in the current PLMN in A/Gb or Iu mode until the MS is switched off or the SIM/USIM is removed; ii) if the Back-off timer value IE is not included, and the Re-attempt indicator IE is included and indicates that re-attempt in an equivalent PLMN is not allowed, the MS shall not send an ACTIVATE PDP CONTEXT REQUEST message for the same APN in any PLMN in the list of equivalent PLMNs in A/Gb or Iu mode until the MS is switched off or the SIM/USIM is removed; and iii) if the Back-off timer value IE is included, the MS shall take different actions depending on the timer value received in the Back-off timer value IE: a) if the timer value indicates neither zero nor deactivated, the MS shall start the back-off timer with the value provided in the Back-off timer value IE for the PLMN and APN combination and shall not send another ACTIVATE PDP CONTEXT REQUEST for the same in the current PLMN in A/Gb or Iu mode until the back-off timer expires, the MS is switched off or the /USIM is removed; b) if the timer value indicates that this timer is deactivated, the MS shall not send another ACTIVATE PDP CONTEXT REQUEST message for the same APN in the current PLMN in A/Gb or Iu mode until the MS is switched off or the SIM/USIM is removed; and c) if the timer value indicates that this timer is zero, the MS may send an ACTIVATE PDP CONTEXT REQUEST message in the PLMN for the same APN. If the network includes the Re-attempt indicator IE indicating that re-attempt in an equivalent PLMN is not allowed, then - for case a) the MS shall additionally start a back-off timer with the value provided in the Back-off timer value IE for the PDP context activation procedure for each combination of a PLMN from the equivalent PLMN list and the APN; and - for case b) the MS shall deactivate the respective back-off timers for the PDP context activation procedure for each combination of a PLMN from the equivalent PLMN list and the APN. For the SM cause value #66 "requested APN not supported in current RAT and PLMN combination" the MS shall ignore the value of the RATC bit in the Re-attempt indicator IE provided by the network, if any. As an implementation option, for cases i), iii.a) and iii.b), if the Re-attempt indicator IE is not included, the MS may decide not to automatically send another ACTIVATE PDP CONTEXT REQUEST message for the same APN in a PLMN which is in the list of equivalent PLMNs.

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

6.15a.1 Description

Climate change and the rising consumption of energy motivate increased energy efficiency. Energy efficiency is a strategic priority for telecom operators around the world. Energy efficiency as a service criteria allows services to be delivered with diverse energy efficiency and energy consumption policies. Energy consumption and efficiency information and network energy states can be exposed to third parties and energy consumption can be constrained. Energy related information can include ratio of renewable energy and carbon emission information when available. Calculation of energy related information as described in the following requirements is done by means of averaging or applying a statistical model. The requirements do not imply that some form of 'real time' monitoring is required.

3GPP TS 22.261

Service requirements for the 5G system

SA WG1

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

6.15a.1

B.3 Other RANAP and S1-AP and NGAP IEs

When transparently copying a RANAP/S1AP/NGAP IE, other than the handover/relocation related generic transparent containers (see Annex B.1) into GTP IE, or GTP IE field the following applies: - a transparent copy of a RANAP/S1AP/NGAP IE, which is transported on the Iu/S1/NG-C interface within a "protocol-IE container", neither includes the Information Element Identity ("IE-ID") nor the "criticality" nor the open type field related length indication ("OT-LI"), but only the Information Element itself ("IE"). - "IE" refers to all parts of the encoded type of the Information Element, i.e. including also any related length indication (in case of types with variable length) and preamble (see ITU-T X.691 [49] for the definition of the term "preamble").

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

B.3

D.4.1 Example of possible implementation

This clause provides an example of a possible implementation of the enforcement of overload control between remote GTP-C entities, amongst other possible methods, considering the example network topology described in Figure D.4.1-1. Figure D.4.1-1: Example network topology The source GTP-C entity can apply message throttling according to the maximum of the overload reduction metric reported by the intermediate and target GTP-C entities, i.e. max (Intermediate_Overload-Metric, Target_Overload-Metric), for each of the path between the source and the target GTP-C entities. Each path is considered independently whilst performing the message throttling. Considering the following example overload condition for the topology above: Target_Overload-Metric = 30% IntermediateA_Overload-Metric = 10% IntermediateB_Overload-Metric = 20% IntermediateC_Overload-Metric = 40% Target_Terminated-Messages = 100 IntermediateA-Target_Messages = 20 IntermediateB-Target_Messages = 50 IntermediateC-Target_Messages = 30 the source GTP-C entity applies message throttling as follows: Source-IntermediateA_Messages = 14 (message throttling of 30% applied) Source-IntermediateB_Messages = 35 (message throttling of 30% applied) Source-IntermediateC_Messages = 18 (message throttling of 40% applied) Source-Target_Messages = 67 (the Target GTP-C entity receives 67 messages although it could have handled 70 messages in the overloaded condition).

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

D.4.1

13.12.2 Format of the Default WWSF URI

The Default WWSF URI is an HTTP URI that should have the following format: "http://wwsf.<domain>" in which "<domain>" identifies the domain hosting the WWSF. If a preconfigured or provisioned WWSF URI is available then the UE shall use it. When a preconfigured or provisioned WWSF URI does not exist then the UE shall create the Default WWSF URI as follows: - The first label shall be "wwsf". - The next label(s) shall identify the home network as follows: 1. When the UE has an ISIM, the domain name from the IMPI shall be used (see 3GPP TS 31.103[ Characteristics of the IP Multimedia Services Identity Module (ISIM) application ] [93]) as follows: a. if the last two labels of the domain name from the IMPI are "3gppnetwork.org": i. the next labels shall be all labels of the domain name from the IMPI apart from the last two labels; and ii. the last three labels shall be "pub.3gppnetwork.org"; b. if the last two labels of the domain name from the IMPI are other than the "3gppnetwork.org": i. the next labels shall be all labels of the domain name from the IMPI; 2. When the UE has a USIM and does not have an ISIM, the home network shall be "ims.mnc<MNC>.mcc<MCC>.pub.3gppnetwork.org" where <MNC> and <MCC> shall be derived from the components of the IMSI defined in clause 2.2. If there are only two significant digits in the MNC, one "0" digit shall be inserted at the left side to fill the 3 digits coding of MNC in the FQDN of WWSF URI. As an example for the case when the UE has the ISIM, where the IMPI is "user@operator.com", the Default WWSF URI used by the UE would be: EXAMPLE 1: "http://wwsf.operator.com". As an example for the case when the UE has the ISIM, where the IMPI is "234150999999999@ims.mnc015.mcc234.3gppnetwork.org", the Default WWSF URI used by the UE would be: EXAMPLE 2: "http://wwsf.ims.mnc015.mcc234.pub.3gppnetwork.org". As an example for the case when the UE has the USIM and does not have the ISIM, where the MCC is 345 and the MNC is 12, the Default WWSF URI created and used by the UE would be: EXAMPLE 3: "http://wwsf.ims.mnc012.mcc345.pub.3gppnetwork.org".

3GPP TS 23.003

Numbering, addressing and identification

CT WG4

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

13.12.2

– Uplink-PowerControl

The IE Uplink-PowerControl is used to configure UE specific power control parameter for PUSCH, PUCCH and SRS. Uplink-PowerControl information element -- ASN1START -- TAG-UPLINK-POWERCONTROL-START Uplink-powerControl-r17 ::= SEQUENCE { ul-powercontrolId-r17 Uplink-powerControlId-r17, p0AlphaSetforPUSCH-r17 P0AlphaSet-r17 OPTIONAL, -- Need R p0AlphaSetforPUCCH-r17 P0AlphaSet-r17 OPTIONAL, -- Need R p0AlphaSetforSRS-r17 P0AlphaSet-r17 OPTIONAL -- Need R } P0AlphaSet-r17 ::= SEQUENCE { p0-r17 INTEGER (-16..15) OPTIONAL, -- Need R alpha-r17 Alpha OPTIONAL, -- Need S closedLoopIndex-r17 ENUMERATED { i0, i1 } } Uplink-powerControlId-r17 ::= INTEGER(1.. maxUL-TCI-r17) -- TAG-UPLINK-POWERCONTROL-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

5.30.3 Public Network Integrated NPN 5.30.3.1 General

Public Network Integrated NPNs are NPNs made available via PLMNs e.g. by means of dedicated DNNs, or by one (or more) Network Slice instances allocated for the NPN. The existing network slicing functionalities apply as described in clause 5.15. When a PNI-NPN is made available via a PLMN, then the UE shall have a subscription for the PLMN in order to access PNI-NPN. NOTE 1: Annex D provides additional consideration to consider when supporting Non-Public Network as a Network Slice of a PLMN. As network slicing does not enable the possibility to prevent UEs from trying to access the network in areas where the UE is not allowed to use the Network Slice allocated for the NPN, Closed Access Groups may optionally be used to apply access control. A Closed Access Group identifies a group of subscribers who are permitted to access one or more CAG cells associated to the CAG. CAG is used for the PNI-NPNs to prevent UE(s), which are not allowed to access the NPN via the associated cell(s), from automatically selecting and accessing the associated CAG cell(s). NOTE 2: CAG is used for access control e.g. authorization at cell selection and configured in the subscription as part of the Mobility Restrictions i.e. independent from any S-NSSAI. CAG is not used as input to AMF selection nor Network Slice selection. If NPN isolation is desired, operator can better support NPN isolation by deploying network slicing for PNI-NPN, configuring dedicated S-NSSAI(s) for the given NPN as specified in Annex D, clause D.2 and restricting NPN's UE subscriptions to these dedicated S-NSSAI(s). The UE and PNI-NPN may support remote provisioning of credentials for NSSAA or credentials for secondary authentication/authorization to the UE, as specified in clause 5.39. NOTE 3: After successful provisioning of the credentials to the UE, specific service subscription data (e.g. to enable the use of PNI-NPN) can be activated in the UE Subscription data in the UDR/UDM. This can result in a change of the UE Subscription Data to include new S-NSSAI, DNN or CAG information, which can trigger update of the UE configurations, e.g. described in clause 5.15.5.2.2. NOTE 4: The UE always has subscription to the HPLMN providing the PNI-NPN and has a USIM that contains primary authentication credentials. Support for Proximity based Services (ProSe) as defined in TS 23.304[ Proximity based Services (ProSe) in the 5G System (5GS) ] [128] in conjunction with CAG is not specified in this Release of the specification.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.30.3

20.4.2 RE-Auth-Answer Command

The Re-Auth-Answer (RAA) command, defined in IETF RFC 6733 (DIAMETER BASE) [111], is indicated by the Command-Code set to 258 and the message flags’ ‘R’ bit clear, is sent in response to the RAR. The relevant AVPs that are of use for the SGmb interface are detailed in the ABNF description below. Other valid AVPs for this command are not used for SGmb purposes and should be ignored by the receiver or processed according to the relevant specifications. The bold marked AVPs in the message format indicate new optional AVPs for SGmb, or modified existing AVPs. Message Format: <RAA> ::= < Diameter Header: 258, PXY > < Session-Id > { Origin-Host } { Origin-Realm } [ Result-Code ] [ Experimental-Result ] [ MBMS-StartStop-Indication ] [ MBMS-GGSN-Address ] ; for unicast encapsulated user data [ MBMS-GGSN-Ipv6-Address ] ; for unicast encapsulated user data [ MBMS-User-Data-Mode-Indication ] [ MBMS-GW-UDP-Port] ; for unicast encapsulated user data [ Origin-State-Id ] [ Error-Message ] [ Error-Reporting-Host ] [ Failed-AVP ] * [ Redirected-Host ] [ Redirected-Host-Usage ] [ Redirected-Host-Cache-Time ] [ Proxy-Info ] * [ Supported-Features ] [ Restart-Counter ] For the MBMS Heartbeat procedure, RAA is sent by the BM-SC to the MBMS GW, or vice-versa. The RAA message shall contain the following AVPs: - the MBMS-StartStop-Indication AVP set to the value "heartbeat"; - the Restart-Counter AVP set to the local restart counter of the sender.

3GPP TS 29.061

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

CT WG3

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

20.4.2

20.3 UE notification on Network Switching

For MUSIM operation, a MUSIM device in RRC_CONNECTED state in Network A may have to switch from Network A to Network B. Network A is NR and Network B can either be E-UTRA or NR. Before switching from Network A, a MUSIM device should notify Network A to either leave RRC_CONNECTED state, or be kept in RRC_CONNECTED state in Network A while temporarily switching to Network B. When configured to do so, a MUSIM device can signal to the Network A a preference to leave RRC_CONNECTED state by using RRC (see TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12]) or NAS signalling (see TS 23.501[ System architecture for the 5G System (5GS) ] [3]). After sending a preference to leave RRC_CONNECTED state by using RRC signalling, if the MUSIM device does not receive an RRCRelease message from the Network A within a certain time period (configured by the Network A, see TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12]), the MUSIM device can enter RRC_IDLE state in Network A. When configured to do so, a MUSIM device can signal to the Network A a preference to be temporarily switching to Network B while remaining in RRC_CONNECTED state in Network. This is indicated by scheduling gaps preference. This preference can include information for setup or release of gap(s). The Network A can configure at most 4 gap patterns for MUSIM purpose: three periodic gaps and a single aperiodic gap. The Network A should always provide at least one of the requested gap pattern or no gaps. Network providing an alternative gap pattern instead of the one requested by the UE is not supported in this release. When configured to do so, a MUSIM device can include priority of periodic gap(s) in addition to scheduling gaps preference, and the priority preference should be indicated for all periodic gap(s). If the MUSIM device indicates gap priority preference, it can also indicate its preference on using keep solution (defined in TS 38.133[ NR; Requirements for support of radio resource management ] [13]).

3GPP TS 38.300

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

RAN2

3GPP Series : 38 , Radio technology beyond LTE

20.3

5.4.1.3 5G AKA based primary authentication and key agreement procedure 5.4.1.3.1 General

The purpose of the 5G AKA based primary authentication and key agreement procedure is to provide mutual authentication between the UE and the network and to agree on the keys KAUSF, KSEAF and KAMF (see 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]). The cases when the 5G AKA based primary authentication and key agreement procedure is used are defined in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. The network initiates the 5G AKA based primary authentication and key agreement procedure by sending an AUTHENTICATION REQUEST message to the UE without the EAP message IE. The network shall include the ngKSI and the ABBA in AUTHENTICATION REQUEST message. The 5G AKA based primary authentication and key agreement procedure is always initiated and controlled by the network. However, the UE can reject the 5G authentication challenge sent by the network. The UE shall proceed with a 5G authentication challenge only if a USIM is present. A partial native 5G NAS security context is established in the UE and the network when a 5G authentication is successfully performed. During a successful 5G AKA based primary authentication and key agreement procedure, the CK and IK are computed by the USIM. CK and IK are then used by the ME as key material to compute new keys KAUSF, KSEAF and KAMF. KAMF is stored in the 5G NAS security contexts (see 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]) of both the network and in the volatile memory of the ME while registered to the network, and is the root for the 5GS integrity protection and ciphering key hierarchy. NOTE 1: Generation of the new KAUSF and the new KSEAF does not result into deletion of the valid KAUSF and the valid KSEAF, if any. Upon successful completion of the 5G AKA based primary authentication, the AMF shall initiate a security mode control procedure (see subclause 5.4.2) to take the new partial native 5G NAS security context into use. NOTE 2: The AMF immediately initiates a security mode control procedure (see subclause 5.4.2) after 5G AKA primary authentication is successful to avoid KAUSF key mismatch between the UE and the network.

3GPP TS 24.501

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

CT WG1

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

5.4.1.3

4.7.13.4a Service request procedure for initiating a PDN connection for emergency bearer services not accepted by the network (UTRAN Iu mode only)

If the service request for initiating a PDN connection for emergency bearer services cannot be accepted by the network, the MS shall perform the procedures as described in subclause 4.7.13.4. Then if the MS is in the same selected PLMN where the last service request was attempted, the MS shall: a) inform the upper layers of the failure of the procedure; or NOTE 1: This can result in the upper layers requesting establishment of a CS emergency call (if not already attempted in the CS domain) or other implementation specific mechanisms, e.g. procedures specified in 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [95] that can result in the emergency call being attempted to another IP-CAN. b) detach locally, if not detached already, attempt GPRS attach for emergency bearer services. If the service request for initiating a PDN connection for emergency bearer services fails due to abnormal case a) in subclause 4.7.13.5, the MS shall perform the procedures as described in subclause 4.7.13.5 and inform the upper layers of the failure to access the network. NOTE 2: This can result in the upper layers establishment of a CS emergency call (if not already attempted in the CS domain) or other implementation specific mechanisms, e.g. procedures specified in 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [95] that can result in the emergency call being attempted to another IP-CAN. If the service request for initiating a PDN connection for emergency bearer services fails due to abnormal cases b), c) or d) in subclause 4.7.13.5, the MS shall perform the procedures as described in subclause 4.7.13.5. Then if the MS is in the same selected PLMN where the last service request was attempted, the MS shall: a) inform the upper layers of the failure of the procedure; or NOTE 3: This can result in the upper layers establishment of a CS emergency call (if not already attempted in the CS domain) or other implementation specific mechanisms, e.g. procedures specified in 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [95] that can result in the emergency call being attempted to another IP-CAN. b) detach locally, if not detached already, attempt GPRS attach for emergency bearer services.

3GPP TS 24.008

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

CT WG1

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

4.7.13.4a

10.4.2 MR-DC with 5GC

The SN Release procedure may be initiated either by the MN or by the SN and is used to initiate the release of the UE context and relevant resources at the SN. The recipient node of this request can reject it, e.g., if an SN change procedure is triggered by the SN. In case of CPA, inter-SN CPC or inter-SN subsequent CPAC, this procedure may be initiated either by the MN or the candidate SN, and it is used to cancel all the prepared PSCells at the candidate SN and initiate the release of related UE context at the candidate SN. MN initiated SN Release Figure 10.4.2-1: SN release procedure - MN initiated Figure 10.4.2-1 shows an example signalling flow for the MN initiated SN Release procedure. 1. The MN initiates the procedure by sending the SN Release Request message. 2. The SN confirms SN Release by sending the SN Release Request Acknowledge message. If appropriate, the SN may reject SN Release, e.g., if the SN change procedure is triggered by the SN. NOTE 00: If CPA or inter-SN CPC is configured, upon reception of the SN Release Request Acknowledge message the MN cancels all CPAC with the target candidate SN(s). NOTE 00a: If subsequent CPAC is configured, upon reception of the SN Release Acknowledge message from the source SN, the MN may retain the subsequent CPAC configuration or cancel the subsequent CPAC configuration. If the MN maintains the subsequent CPAC configuration, it should provide suitable execution conditions for the evaluation of the subsequent CPAC. 2a. When applicable, the MN provides forwarding address information to the SN. NOTE 0: The MN may send the Xn-U Address Indication message to provide forwarding address information before step 2. 3/4. If required, the MN indicates in the MN RRC reconfiguration message towards the UE that the UE shall release the entire SCG configuration. In case the UE is unable to comply with (part of) the configuration included in the MN RRC reconfiguration message, it performs the reconfiguration failure procedure. NOTE 1: If data forwarding is applied, timely coordination between steps 1 and 2 may minimize gaps in service provision, this is however regarded to be an implementation matter. 5. If PDCP termination point is changed to the MN for bearers using RLC AM, the SN sends the SN Status Transfer message. 6. Data forwarding from the SN to the MN may start. 7. The SN sends the Secondary RAT Data Usage Report message to the MN and includes the data volumes delivered to and received from the UE as described in clause 10.11.2. NOTE 1a: If data forwarding is applied, the order the SN sends the Secondary RAT Data Usage Report message and starts data forwarding with MN is not defined i.e., step 7 can take place before step 6. The SN does not need to wait for the end of data forwarding to send the Secondary RAT Data Usage Report message. 8. If applicable, the PDU Session path update procedure is initiated. 9. Upon reception of the UE Context Release message, the SN releases radio and C-plane related resources associated to the UE context. Any ongoing data forwarding may continue. SN initiated SN Release Figure 10.4.2-2: SN release procedure - SN initiated Figure 10.4.2-2 shows an example signalling flow for the SN initiated SN Release procedure. 1. The SN initiates the procedure by sending the SN Release Required message which may contain inter-node message to support delta configuration. 2. If data forwarding is requested, the MN provides data forwarding addresses to the SN in the SN Release Confirm message. The SN may start data forwarding and stop providing user data to the UE as early as it receives the SN Release Confirm message. NOTE 1b: If CPA or inter-SN CPC is configured, upon reception of the SN Release Required message the MN cancels all CPAC with the target candidate SN(s). NOTE 1c: If subsequent CPAC is configured, upon reception of the SN Release Required message from the source SN, the MN may retain the subsequent CPAC configuration or cancel the subsequent CPAC configuration. If the MN maintains the subsequent CPAC configuration, it should provide suitable execution conditions for the evaluation of the subsequent CPAC. 3/4. If required, the MN indicates in the MN RRC reconfiguration message towards the UE that the UE shall release the entire SCG configuration. In case the UE is unable to comply with (part of) the configuration included in the MN RRC reconfiguration message, it performs the reconfiguration failure procedure. NOTE 2: If data forwarding is applied, timely coordination between steps 2 and 3 may minimize gaps in service provision. This is however regarded to be an implementation matter. 5. If PDCP termination point is changed to the MN for bearers using RLC AM, the SN sends the SN Status Transfer message. 6. Data forwarding from the SN to the MN may start. 7. The SN sends the Secondary RAT Data Usage Report message to the MN and includes the data volumes delivered to and received from the UE as described in clause 10.11.2. NOTE 3: If data forwarding is applied, the order the SN sends the Secondary RAT Data Usage Report message and starts data forwarding with MN is not defined i.e., step 7 can take place before step 6. The SN does not need to wait for the end of data forwarding to send the Secondary RAT Data Usage Report message. 8. If applicable, the PDU Session path update procedure is initiated. 9. Upon reception of the UE Context Release message, the SN releases radio and C-plane related resources associated to the UE context. Any ongoing data forwarding may continue.

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

10.4.2

– AvailabilityIndicator

The IE AvailabilityIndicator is used to configure monitoring a PDCCH for Availability Indicators (AI). AvailabilityIndicator information element -- ASN1START -- TAG-AVAILABILITYINDICATOR-START AvailabilityIndicator-r16 ::= SEQUENCE { ai-RNTI-r16 AI-RNTI-r16, dci-PayloadSizeAI-r16 INTEGER (1..maxAI-DCI-PayloadSize-r16), availableCombToAddModList-r16 SEQUENCE (SIZE(1..maxNrofDUCells-r16)) OF AvailabilityCombinationsPerCell-r16 OPTIONAL, -- Need N availableCombToReleaseList-r16 SEQUENCE (SIZE(1..maxNrofDUCells-r16)) OF AvailabilityCombinationsPerCellIndex-r16 OPTIONAL, -- Need N ... } AI-RNTI-r16 ::= RNTI-Value -- TAG-AVAILABILITYINDICATOR-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

4.23.9.2 Removal of PDU Session Anchor and Branching Point or UL CL controlled by I-SMF

This clause describes a procedure to remove a PDU Session Anchor and Branching Point or UL CL controlled by I-SMF. Figure 4. 23.9.2-1: Removal of PDU Session Anchor and Branching Point or UL CL controlled by I-SMF 1. UE has an established PDU Session with a UPF including the PDU Session Anchor 1 (controlled by SMF) and the UL-CL/BP and the PDU Session Anchor 2 (controlled by I-SMF). Events described in item 1 and 2 of clause 4.23.9.0 have taken place. At some point the I-SMF decides to remove the PDU Session Anchor 2 and UL-CL/BP function, e.g. due to UE mobility. 2. The I-SMF may select a new UPF acting as new I-UPF and replace the existing I-UPF which was acting as UL-CL/BP before. If a new UPF acting as new I-UPF is selected, the I-SMF uses N4 establishment to provide the PSA1 CN Tunnel Info and (R)AN Tunnel Info to the new I-UPF. 3. The I-SMF invokes Nsmf_PDUSession_Update Request (Indication of Removal of traffic offload, Removal of IPv6 prefix @PSA2, DNAI associated with the PSA2, DL Tunnel Info of new I-UPF, if any) to SMF. Multiple local PSAs may be removed, in this case, the I-SMF provides for each local PSA to be removal, the associated DNAI and an IPv6 prefix in the case of multi-homing. The I-SMF informs the SMF that local traffic offload is removed. In the case of IPv6 multi-homing, the I-SMF also notifies the SMF with the removal of the IPv6 prefix @PSA2. The SMF issues a SM Policy Association Modification (clause 4.16.5) corresponding to the IP address allocation/release PCRT(Policy Control Request Trigger). The SMF may also send a notification to the AF, as described in clause 4.3.6.3. 4. If a new UPF that replaces existing I-UPF is selected in step 2, the SMF updates the PSA1 via N4. It provides the CN Tunnel Info of the new I-UPF for the downlink traffic. The SMF may update the packet handling rules in PSA1 as now all traffic is to be moved to PSA1. 5. In the case of IPv6 multi-homing, the SMF notifies the UE to stop using the IPv6 prefix corresponding to PSA2. Also the SMF sends IPv6 multi-homed routing rule along with the IPv6 prefix corresponding to PSA1 to the UE. Based on the information provided in the Router Advertisement, the UE starts using the IPv6 prefix (corresponding to PSA1) for corresponding traffic. 7. The SMF provides I-SMF with N4 information for the local UPF(s) with a SMF initiated Nsmf_PDUSession_Update Request; The N4 information indicates the removal of the traffic offload rules. 8. If a new UPF that replaces existing I-UPF is selected in step 2, the I-SMF releases the old I-UPF. Otherwise the I-SMF updates the existing I-UPF with new rules in order to remove the UL-CL/BP functionality from that I-UPF. If a new UPF that replaces existing I-UPF is selected in step 2, the SMF updates the (R)AN with the new I-UPF CN Tunnel Info. If the PSA2 is not collocated with UL-CL/BP function, the I-SMF releases it via N4. 9. The I-SMF answers to the SMF with a Nsmf_PDUSession_Update Response SMF that may include N4 information received from the local UPF(s).

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.23.9.2

4.14.2.8 Number of successful reconfigurations of LTE DRB to LWIP DRB

a) This measurement provides the number of attempted reconfigurations of LTE DRB to LWIP DRB. b) CC c) On receipt of RRCConnectionReconfigurationComplete message (see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]) corresponding to transmitted RRCConnectionReconfiguration message which triggered the measurement "Number of attempted reconfigurations of LTE DRB to LWIP DRB" (see section 4.x.z.7). d) An integer value e) LWI.LteToLwipDrbReconfSucc f) WLANMobilitySet g) Valid for packet switched traffic h) EPS

3GPP TS 32.425

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

SA WG5

3GPP Series : 32 , OAM&P and Charging

4.14.2.8

– SpatialRelationsSRS-Pos

The IE SpatialRelationsSRS-Pos is used to convey spatial relation for SRS for positioning related parameters. SpatialRelationsSRS-Pos information element -- ASN1START -- TAG-SPATIALRELATIONSSRS-POS-START SpatialRelationsSRS-Pos-r16 ::= SEQUENCE { spatialRelation-SRS-PosBasedOnSSB-Serving-r16 ENUMERATED {supported} OPTIONAL, spatialRelation-SRS-PosBasedOnCSI-RS-Serving-r16 ENUMERATED {supported} OPTIONAL, spatialRelation-SRS-PosBasedOnPRS-Serving-r16 ENUMERATED {supported} OPTIONAL, spatialRelation-SRS-PosBasedOnSRS-r16 ENUMERATED {supported} OPTIONAL, spatialRelation-SRS-PosBasedOnSSB-Neigh-r16 ENUMERATED {supported} OPTIONAL, spatialRelation-SRS-PosBasedOnPRS-Neigh-r16 ENUMERATED {supported} OPTIONAL } --TAG-SPATIALRELATIONSSRS-POS-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–