Datasets:

Exploration-Lab

/

MM-TelecoBench

like 1

Follow

Exploration Lab 62

4.3.2.2.3 SMF selection

4.3.2.2.3.1 General The SMF selection function, as described in clause 6.3.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], is supported by the AMF and is used to allocate an SMF that manages the PDU Session. The SMF selection function described in this clause does not apply to the selection of an SMF for Emergency services. For SMF selection for Emergency services is described in clause 5.16.4.5 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. Two main branches of deployment scenarios to consider: - Non-roaming and roaming with local breakout, see clause 4.3.2.2.3.2 - Home routed roaming, see clause 4.3.2.2.3.3 In the case of non-roaming and local breakout, there are two operational scenarios dependent on the configuration of AMF and the deployment option of NSSF in the serving PLMN. In the case of home-routed, there are two main options dependent on the operators' choices in terms of involvement of NRF, NSSF and configuration of AMF. The decision of which option to use is part of the roaming agreements. NOTE: The use of NSI ID and the use of multiple NRFs in the network are optional and depend on the deployment choices of the operator. 4.3.2.2.3.2 Non-roaming and roaming with local breakout Figure 4.3.2.2.3.2-1: SMF selection for non-roaming and roaming with local breakout scenarios This procedure may be skipped altogether if SMF information is available in the AMF by other means (e.g. locally configured); otherwise: - when the serving AMF is aware of the appropriate NRF to be used to select NFs/services within the corresponding Network Slice instance based on configuration or based on the Network Slice selection information received during Registration, only steps 3 and 4 in the following procedure are executed as described in Figure 4.3.2.2.3.2-1; - when the serving AMF is not aware of the appropriate NRF to be used to select NFs/services within the corresponding Network Slice instance, all steps in the following procedure are executed as described in Figure 4.3.2.2.3.2-1. 1. The AMF invokes the Nnssf_NSSelection_Get service operation from the NSSF in serving PLMN with the S-NSSAI of the Serving PLMN from the Allowed NSSAI or Partially Allowed NSSAI requested by the UE, PLMN ID of the SUPI, TAI of the UE and the indication that the request is within a procedure of PDU Session establishment in either the non-roaming or roaming with local breakout scenario. 2. The NSSF in serving PLMN selects the Network Slice instance, determines and returns the appropriate NRF to be used to select NFs/services within the selected Network Slice instance and optionally may return a NSI ID corresponding to the Network Slice instance. 3. AMF queries the appropriate NRF in serving PLMN by issuing the Nnrf_NFDiscovery_Request including at least the S-NSSAI of the Serving PLMN for this PDU Session from the Allowed NSSAI or Partially Allowed NSSAI, PLMN ID of the SUPI, DNN and possibly NSI ID if the AMF has stored an NSI ID for the S-NSSAI of the Serving PLMN for this PDU Session from the Allowed NSSAI or Partially Allowed NSSAI. NOTE: The list of parameters for SMF selection is defined in clause 6.3.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. See also clause 5.34.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] for I-SMF selection. 4. The NRF in serving PLMN provides to the AMF, e.g. FQDN or IP address, of a set of the discovered SMF instance(s) or Endpoint Address(es) of SMF service instance(s) in Nnrf_NFDiscovery_Request response message and possibly an NSI ID for the selected Network Slice instance corresponding to the S-NSSAI for subsequent NRF queries. 4.3.2.2.3.3 Home routed roaming The selection of the SMF in VPLMN is performed in the same way as for non-roaming and roaming with local breakout (see clause 4.3.2.2.3.2). The selection of the SMF in HPLMN is performed by means of one of two main options. Which of these two options to use is decided based on Service Level Agreements between the operators. NOTE 1: The procedures described in this clause are not limited to SMF selection but can be used to discover and select any NF/NF service in the HPLMN part of a Network Slice instance. In the first option, requiring the use of NSSF in both the VPLMN and the HPLMN, the selection of the SMF in HPLMN is performed by means of the procedure depicted in Figure 4.3.2.2.3.3-1. Figure 4.3.2.2.3.3-1: Option 1 for SMF selection for home-routed roaming scenarios 1. Based on the operator's configuration, if the AMF is not aware of the appropriate NRF to be used to select NFs/services in the HPLMN, the AMF invokes the Nnssf_NSSelection_Get service operation from the NSSF in VPLMN with the VPLMN S-NSSAI from the Allowed NSSAI or Partially Allowed NSSAI requested by the UE for this PDU Session, the HPLMN S-NSSAI that maps to the VPLMN S-NSSAI, PLMN ID of the SUPI, the TAI of the UE and the indication that the request is within a procedure of PDU Session establishment in the home-routed roaming scenario. 2. If slicing configuration information for the S-NSSAI in the HPLMN is not available (e.g. the NSSF has no cached information), the NSSF of the VPLMN invokes the Nnssf_NSSelection_Get service operation from NSSF of the HPLMN according to the PLMN ID of SUPI by including the HPLMN S-NSSAI. 3. The NSSF in HPLMN may include the NSI ID, if needed, for the Network Slice instance in HPLMN selected for the corresponding S-NSSAI of the HPLMN in the Nnssf_NSSelection_Get response. The NSSF in HPLMN also includes the appropriate hNRF to be used to select NFs/services within HPLMN in the Nnssf_NSSelection_Get response. 4. The serving NSSF includes in the Nnssf_NSSelection_Get response all the information that has been received from the NSSF in HPLMN when responding to the AMF. 5. The AMF queries the target vNRF using the Nnrf_NFDiscovery_Request by including PLMN ID of the SUPI, DNN, HPLMN S-NSSAI, the hNRF and possibly an HPLMN NSI ID for the selected Network Slice instance corresponding to the HPLMN S-NSSAI if available in the AMF (obtained from the HPLMN NSSF in steps 3 and 4 or cached from a previous H-NSSF query). 6. The NRF in serving PLMN identifies NRF in HPLMN (hNRF) based on the information provided by the NSSF in the serving PLMN and it invokes the Nnrf_NFDiscovery_Request service from hNRF according the procedure in Figure 4.17.4-1 to get the expected SMF instance(s) deployed in the HPLMN. As the vNRF in VPLMN triggers the "NF Discovery" on behalf of the AMF, the NRF in the VPLMN shall not replace the information of the NF, i.e. AMF ID, in the Nnrf_NFDiscovery_Request message it sends to the hNRF. 7-8. The hNRF provides to the AMF, via vNRF, the information e.g. FQDN or IP address, of a set of the SMF instance(s) in Nnrf_NFDiscovery_Request response message and possibly an NSI ID for the selected Network Slice instance corresponding to the S-NSSAI of the HPLMN for subsequent NRF queries. When the NSSF is not deployed in HPLMN then the AMF in VPLMN relies on either the configuration to obtain the NRF in HPLMN or on the option below. The second option for the selection of the SMF in HPLMN is performed by means of the procedure depicted in Figure 4.3.2.2.3.3-2. Figure 4.3.2.2.3.3-2: Option 2 for SMF selection for home-routed roaming scenarios 1. Based on the operator's configuration, the AMF queries the vNRF with PLMN ID of the SUPI, PLMN ID of the serving PLMN, DNN, the HPLMN S-NSSAI that maps to the S-NSSAI from the Allowed NSSAI or Partially Allowed NSSAI of the Serving PLMN the UE has requested, the hNRF and if applicable and available, an HPLMN NSI ID (if the AMF has stored an hNRF and if applicable and available, an HPLMN NSI ID for the selected Network Slice instance corresponding to the S-NSSAI of the HPLMN) and DNN. 2. The vNRF queries, on behalf of the AMF in VPLMN, the hNRF identified by means of the PLMN ID of the SUPI (if no hNRF is received from the AMF, the hNRF is locally determined in the vNRF based on information received in step 1). The NRF in VPLMN requests "NF Discovery" service from hNRF according the procedure in Figure 4.17.4-1 to get the expected SMF instance(s) deployed in the HPLMN. As the NRF in the serving PLMN triggers the "NF Discovery" on behalf of the AMF, the NRF in the VPLMN shall not replace the information of the NF, i.e. AMF ID, in the Nnrf_NFDiscovery_Request message it sends to the hNRF. Depending on the available information and based on configuration, the hNRF may either execute steps in 3(A) or in 3(B). 3(A) The hNRF provides to the AMF, via vNRF, the information e.g. FQDN or IP address, of a set of the discovered SMF instance(s) and possibly an NSI ID for the selected HPLMN part of the Network Slice instance corresponding to the S-NSSAI of the HPLMN for subsequent NRF queries in Nnrf_NFDiscovery_Request response message(steps 3a and 3b). 3(B) The hNRF queries, on behalf of the AMF, an appropriate local NRF in HPLMN (e.g. a slice level NRF); this local NRF provides the IP address or the FQDN of expected SMF instance(s) and possibly an NSI ID for the selected HPLMN part of the Network Slice instance corresponding to the S-NSSAI of the HPLMN for subsequent NRF queries (steps 3a and 3b) that the hNRF returns, via vNRF, to the AMF (steps 3c and 3d).

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.3.2.2.3

14.7 W-APN

The W-APN is composed of two parts as follows: - The W-APN Network Identifier; this defines to which external network the PDG is connected. - The W-APN Operator Identifier; this defines in which PLMN the PDG serving the W-APN is located. The W-APN Operator Identifier is placed after the W-APN Network Identifier. The W-APN consisting of both the Network Identifier and Operator Identifier corresponds to a FQDN of a PDG; the W-APN has, after encoding as defined in the paragraph below, a maximum length of 100 octets. The encoding of the W-APN shall follow the Name Syntax defined in IETF RFC 2181 [18], IETF RFC 1035 [19] and IETF RFC 1123 [20]. The W-APN consists of one or more labels. Each label is coded as a one octet length field followed by that number of octets coded as 8 bit ASCII characters. Following IETF RFC 1035 [19] the labels shall consist only of the alphabetic characters (A-Z and a-z), digits (0-9) and the hyphen (-). Following IETF RFC 1123 [20], the label shall begin and end with either an alphabetic character or a digit. The case of alphabetic characters is not significant. The W-APN is not terminated by a length byte of zero. For the purpose of presentation, a W-APN is usually displayed as a string in which the labels are separated by dots (e.g. "Label1.Label2.Label3"). The W-APN for the support of IMS Emergency calls shall take the form of a common, reserved Network Identifier described in clause 14.7.1 together with the usual W-APN Operator Identifier as described in clause 14.7.2.

3GPP TS 23.003

Numbering, addressing and identification

CT WG4

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

14.7

4.2.2.3 Service State, LIMITED SERVICE

When in state MM IDLE and service state LIMITED SERVICE the mobile station shall: - not perform periodic updating; - not perform IMSI detach; - reject any requests from CM entities for MM connections except for emergency calls; - perform normal location updating when a cell is entered which may provide normal service (e.g. location area not in one of the forbidden LAI lists.); and - for an eCall only mobile station (as determined by information configured in USIM), perform the eCall inactivity procedure at expiry of timer T3242 or timer T3243. When in state MM IDLE and service state LIMITED SERVICE the mobile station may: - respond to paging (with IMSI); In addition, mobile stations supporting VGCS listening or VBS listening shall: - indicate notifications to the GCC or BCC sublayer for which a channel description has been received in the notification by the RR sublayer; - reject requests of the GCC or BCC sublayer to respond to notifications for which no channel description has been received in the notification by the RR sublayer; - request the RR sublayer to receive a voice group or broadcast call if the GCC or BCC sublayer requests the reception of a voice group or broadcast call for which a channel description has been received in the notification by the RR sublayer and then go to the service state RECEIVING GROUP CALL (LIMITED SERVICE).

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

16.2.1.2 MMTEL voice quality/coverage enhancements

The air interface delay budget can be relaxed to increase the robustness of the transmission for coverage enhancement. Such relaxation may be achieved when a UE in good coverage indicates a preference to the gNB to reduce the local air interface delay by sending a DelayBudgetReport message to decrease the DRX cycle length, so that the E2E delay and jitter can be reduced. When the UE detects changes such as end-to-end MMTEL voice quality or local radio quality, the UE may inform the gNB its new preference by sending DelayBudgetReport messages with updated contents.

3GPP TS 38.300

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

RAN2

3GPP Series : 38 , Radio technology beyond LTE

16.2.1.2

A.19 UPU-MAC-IAUSF generation function

When deriving a UPU-MAC-IAUSF from KAUSF, the following parameters shall be used to form the input S to the KDF. - FC = 0x7B, - P0 = UE Parameters Update Data, i.e. UE parameters update list as given in clause 9.11.3.53A of TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [35] (starting from octet 23), - L0 = length of UE Parameters Update Data - P1 = CounterUPU - L1 = length of CounterUPU The input key Key shall be KAUSF. The UPU-MAC-IAUSF is identified with the 128 least significant bits of the output of the KDF.

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

A.19

8.76 CSG Information Reporting Action

CSG Information Reporting Action is coded as depicted in Figure 8.76-1. Figure 8.76-1: CSG Reporting Action The following bits within Octet 5 shall indicate: - Bit 1 – UCICSG: When set to "1", shall indicate to start reporting User CSG Info when the UE enters/leaves/access through the CSG Cell. - Bit 2 – UCISHC: When set to "1", shall indicate to start reporting User CSG Info when the UE enters/leaves/access through Subscribed Hybrid Cell. - Bit 3 – UCIUHC: When set to "1", shall indicate to start Reporting User CSG Info when the UE enters/leaves/access through Unsubscribed Hybrid Cell. All the bits 1 to 3 shall be set to 0 to stop reporting User CSG Info.

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

6.6.3.1A Minimum requirements for CA

This clause specifies the spurious emission requirements for carrier aggregation. NOTE: For measurement conditions at the edge of each frequency range, the lowest frequency of the measurement position in each frequency range should be set at the lowest boundary of the frequency range plus MBW/2. The highest frequency of the measurement position in each frequency range should be set at the highest boundary of the frequency range minus MBW/2. MBW denotes the measurement bandwidth defined for the protected band. For inter-band carrier aggregation with one component carrier per operating band and the uplink active in two E-UTRA bands, the spurious emission requirement Table 6.6.3.1-2 apply for the frequency ranges that are more than FOOB as defined in Table 6.6.3.1-1 away from edges of the assigned channel bandwidth on a component carrier. If for some frequency a spurious emission requirement of individual component carrier overlaps with the spectrum emission mask or channel bandwidth of another component carrier then it does not apply. NOTE: For inter-band carrier aggregation with uplink assigned to two E-UTRA bands the requirements in Table 6.6.3.1-2 could be verified by measuring spurious emissions at the specific frequencies where second and third order intermodulation products generated by the two transmitted carriers can occur; in that case, the requirements for remaining applicable frequencies in Table 6.6.3.1-2 would be considered to be verified by the measurements verifying the one uplink inter-band CA spurious emission requirement. For intra-band contiguous carrier aggregation the spurious emission limits apply for the frequency ranges that are more than FOOB (MHz) in Table 6.6.3.1A-1 from the edge of the aggregated channel bandwidth (Table 5.6A-1). For frequencies ΔfOOB greater than FOOB as specified in Table 6.6.3.1A-1the spurious emission requirements in Table 6.6.3.1-2 are applicable. Table 6.6.3.1A-1: Boundary between E-UTRA out of band and spurious emission domain for intra-band contiguous carrier aggregation For intra-band non-contiguous carrier aggregation transmission the spurious emission requirement is defined as a composite spurious emission requirement. Composite spurious emission requirement applies to frequency ranges that are more than FOOB away from the edges of the sub-blocks. Composite spurious emission requirement is defined as follows a) Composite spurious emission requirement is a combination of individual sub-block spurious emission requirements b) In case the sub-block consist of one component carrier the sub-lock spurious emission requirement and FOOB are defined in subclause 6.6.3.1 c) If for some frequency an individual sub-block spurious emission requirement overlaps with the general spectrum emission mask or the sub-block bandwidth of another sub-block then it does not apply For combinations of intra-band and inter-band carrier aggregation with three uplink component carriers (up to two contiguously aggregated carriers per band), the spurious emission requirememnt is defined as follows. For the E-UTRA band supporting one component carrier the requirements in Table 6.6.3.1-2 apply for frequency ranges that are more than FOOB (MHz) from the edges of assigned channel bandwidth as defined in Table 6.6.3.1-1. For the E-UTRA band supporting two contiguous component carriers the requirements in Table 6.6.3.1-2 apply for frequency ranges that are more than FOOB (MHz) from the edges of assigned aggregated channel bandwidth as defined in Table 6.6.3.1A-1. If for some frequency a spurious emission requirement of a single component carrier or two contiguous component carriers overlap with the spurious emission requirement or channel bandwidth of another component carrier or two contiguously aggregated carriers then it does not apply.

3GPP TS 36.101

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

RAN4

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

6.6.3.1A

6.9.5.1 Rules related to AS and NAS security context synchronization

Concurrent runs of security procedures may, in certain situations, lead to mismatches between security contexts in the network and the UE. In order to avoid such mismatches, the following rules shall be adhered to: 1. AMF shall not initiate any of the N2 procedures including a new key towards a UE if a NAS Security Mode Command procedure is ongoing with the UE. 2. The AMF shall not initiate a NAS Security Mode Command towards a UE if one of the N2 procedures including a new key is ongoing with the UE. 3. When the AMF has sent a NAS Security Mode Command to a UE in order to take a new KAMF into use and receives a request for an inter-AMF handover or an inter-RAT handover from the serving gNB/ng-eNB, the AMF shall wait for the completion of the NAS SMC procedure (i.e. receiving NAS Security Mode Complete) before initiating an inter-AMF handover or initiating an inter-RAT handover. 4. When the AMF has initiated a NGAP UE Context Modification procedure in order to take a new KgNB into use, and receives a request for an inter-AMF handover from the serving gNB/ng-eNB, and decides not to change the KAMF for the inter-AMF handover, the AMF shall wait for the (successful or unsuccessful) completion of the UE Context Modification procedure before initiating an inter-AMF handover. 5. Once the source AMF has initiated inter-AMF handover to the target AMF, or inter-system handover to the target MME, the source AMF shall not send any downlink NAS messages to the UE until it is aware that the handover has either failed or has been cancelled.

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

6.9.5.1

19.4.2.9.4 Visited Country FQDN

The Visited Country FQDN, used by a roaming UE to determine whether the visited country mandates the selection of an ePDG in this country, shall be constructed as described below. The Visited Country FQDN shall contain a MCC that uniquely identifies the country in which the UE is located. The Visited Country FQDN is composed of seven labels. The last three labels shall be "pub.3gppnetwork.org". The fourth label shall be "visited-country". The third label shall uniquely identify the MCC of the visited country. The first and second labels shall be "epdg.epc". The Visited Country FQDN shall be constructed as follows: "epdg.epc.mcc<MCC>.visited-country.pub.3gppnetwork.org" The <MCC> coding used in this FQDN shall be: - <MCC> = 3 digits As an example, the Visited Country FQDN for MCC 345 is coded in the DNS as: "epdg.epc. mcc345.visited-country.pub.3gppnetwork.org".

3GPP TS 23.003

Numbering, addressing and identification

CT WG4

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

19.4.2.9.4

5.14.1.2.2 Sidelink process

The Sidelink process is associated with a HARQ buffer. The sequence of redundancy versions is 0, 2, 3, 1. The variable CURRENT_IRV is an index into the sequence of redundancy versions. This variable is updated modulo 4. New transmissions and retransmissions either for a given SC period in sidelink communication or in V2X sidelink communication are performed on the resource indicated in the sidelink grant as specified in clause 5.14.1.1 and with the MCS selected as specified in clause 5.14.1.1. If the sidelink process is configured to perform transmissions of multiple MAC PDUs for V2X sidelink communication the process maintains a counter SL_RESOURCE_RESELECTION_COUNTER. For other configurations of the sidelink process, this counter is not available. If the Sidelink HARQ Entity requests a new transmission, the Sidelink process shall: - set CURRENT_IRV to 0; - store the MAC PDU in the associated HARQ buffer; - store the sidelink grant received from the Sidelink HARQ Entity; - generate a transmission as described below. If the Sidelink HARQ Entity requests a retransmission, the Sidelink process shall: - generate a transmission as described below. To generate a transmission, the Sidelink process shall: - if there is no uplink transmission; or if the MAC entity is able to perform uplink transmissions and transmissions on SL-SCH simultaneously at the time of the transmission; or if there is a MAC PDU to be transmitted in this TTI in uplink, except a MAC PDU obtained from the Msg3 buffer, and transmission of V2X sidelink communication is prioritized over uplink transmission; and - if there is no Sidelink Discovery Gap for Transmission or no transmission on PSDCH at the time of the transmission; or, in case of transmissions of V2X sidelink communication, if the MAC entity is able to perform transmissions on SL-SCH and transmissions on PSDCH simultaneously at the time of the transmission: - instruct the physical layer to generate a transmission according to the stored sidelink grant with the redundancy version corresponding to the CURRENT_IRV value. - increment CURRENT_IRV by 1; - if this transmission corresponds to the last transmission of the MAC PDU: - decrement SL_RESOURCE_RESELECTION_COUNTER by 1, if available. The transmission of the MAC PDU for V2X sidelink communication is prioritized over uplink transmissions if the following conditions are met: - if the MAC entity is not able to perform all uplink transmissions and all transmissions of V2X sidelink communication simultaneously at the time of the transmission; and - if uplink transmission is not prioritized by upper layer according to TS 24.386[ User Equipment (UE) to V2X control function; protocol aspects; Stage 3 ] [15]; and - if thresSL-TxPrioritization is configured and the value of the highest priority of the sidelink logical channel(s) in the MAC PDU is lower than thresSL-TxPrioritization.

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

4.2.10 Architecture Reference Model for ATSSS Support

In order to support the ATSSS feature, the 5G System Architecture is extended as shown in Figure 4.2.10-1, Figure 4.2.10-2 and Figure 4.2.10-3. The additional functionality that is supported by the UE and the network functions shown in these figures is specified in clause 5.32 below. In summary: - The UE supports one or more of the steering functionalities specified in clause 5.32.6, i.e. the MPTCP functionality, the MPQUIC functionality and the ATSSS-LL functionality. Each steering functionality in the UE enables traffic steering, switching and splitting across 3GPP access and non-3GPP access, in accordance with the ATSSS rules provided by the network. The ATSSS-LL functionality is mandatory in the UE for MA PDU Session of type Ethernet. - The UPF may support the MPTCP Proxy functionality, which communicates with the MPTCP functionality in the UE by using the MPTCP protocol (IETF RFC 8684 [81]), as defined in clause 5.32.6.2.1. - The UPF may support the MPQUIC Proxy functionality, which communicates with the MPQUIC functionality in the UE by using the QUIC protocol (RFC 9000 [166], RFC 9001 [167], RFC 9002 [168]) and its multipath extensions (draft-ietf-quic-multipath [174]), as defined in clause 5.32.6.2.2. - The UPF may support ATSSS-LL functionality, which is similar to the ATSSS-LL functionality defined for the UE. There is no user plane protocol defined between the ATSSS-LL functionality in the UE and the ATSSS-LL functionality in the UPF. NOTE 1: ATSSS-LL functionality is needed in the 5GC for MA PDU Session of type Ethernet. - In addition, the UPF supports Performance Measurement Functionality (PMF), which may be used by the UE to obtain access performance measurements (see clause 5.32.5) over the user-plane of 3GPP access and/or over the user-plane of non-3GPP access. - The AMF, SMF and PCF are extended with new functionality that is further discussed in clause 5.32. Figure 4.2.10-1: Non-roaming and Roaming with Local Breakout architecture for ATSSS support NOTE 2: The interactions between the UE and PCF that may be required for ATSSS control are specified in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. NOTE 3: The UPF shown in Figure 4.2.10-1 can be connected via an N9 reference point, instead of the N3 reference point. Figure 4.2.10-2 shows the 5G System Architecture for ATSSS support in a roaming case with home-routed traffic and when the UE is registered to the same VPLMN over 3GPP and non-3GPP accesses. In this case, the MPTCP Proxy functionality, the MPQUIC Proxy functionality, the ATSSS-LL functionality and the PMF are located in the H-UPF. Figure 4.2.10-2: Roaming with Home-routed architecture for ATSSS support (UE registered to the same VPLMN) Figure 4.2.10-3 shows the 5G System Architecture for ATSSS support in a roaming case with home-routed traffic and when the UE is registered to a VPLMN over 3GPP access and to HPLMN over non-3GPP access (i.e. the UE is registered to different PLMNs). In this case, the MPTCP Proxy functionality, the MPQUIC functionality, the ATSSS-LL functionality and the PMF are located in the H-UPF. Figure 4.2.10-3: Roaming with Home-routed architecture for ATSSS support (UE registered to different PLMNs)

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

4.2.10

16.14.3.2.3 Satellite switch with re-sync

Upon both hard and soft satellite switch over in the quasi-Earth fixed scenario with the same SSB frequency and the same gNB, the satellite switch with re-sync procedure is supported. The satellite switch with re-sync avoids a L3 mobility for UEs in the cell by maintaining the same PCI on the geographical area covered by quasi-Earth fixed beam. CHO can be configured simultaneously with the satellite switch with re-sync procedure. For soft satellite switch over, the UE can start synchronizing with the target satellite before the source satellite ends to serve the cell. It is not required for the UE to be connected to source satellite when the UE switches to target satellite.

3GPP TS 38.300

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

RAN2

3GPP Series : 38 , Radio technology beyond LTE

16.14.3.2.3

5.5.3.3.5 Combined tracking area updating procedure not accepted by the network

If the combined tracking area updating cannot be accepted by the network, the MME shall send a TRACKING AREA UPDATE REJECT message to the UE including an appropriate EMM cause value. If the MME locally deactivates EPS bearer contexts for the UE (see clause 5.5.3.2.4) and no active EPS bearer contexts remain for the UE, the MME shall send the TRACKING AREA UPDATE REJECT message including the EMM cause value #10 "implicitly detached". If the tracking area update request is rejected due to general NAS level mobility management congestion control, the network shall set the EMM cause value to #22 "congestion" and assign a back-off timer T3346. If the UE initiated the tracking area updating procedure due to inter-system change from N1 mode to S1 mode, and the MME does not support N26 interface, the MME shall send a TRACKING AREA UPDATE REJECT message with EMM cause value #9 "UE identity cannot be derived by the network". When the UE performs inter-system change from N1 mode to S1 mode, if the MME is informed that verification of the integrity protection of the TRACKING AREA UPDATE REQUEST message has failed in the AMF, then: a) If the MME can retrieve the current EPS security context as indicated by the eKSI and GUTI sent by the UE, the MME shall proceed as specified in clause 5.5.3.2.4; b) if the MME cannot retrieve the current EPS security context as indicated by the eKSI and GUTI sent by the UE, or the eKSI or GUTI was not sent by the UE, the MME may initiate the identification procedure by sending the IDENTITY REQUEST message with the "Type of identity" of the Identity type IE set to "IMSI" before taking actions as specified in clause 4.4.4.3; or c) If the MME needs to reject the tracking area updating procedure, the MME shall send a TRACKING AREA UPDATE REJECT message with EMM cause value #9 "UE identity cannot be derived by the network". If the tracking area request is rejected due to service gap control as specified in clause 5.3.17 i.e. the T3447 timer is running, the network shall set the EMM cause value to #22 "congestion" and may assign a back-off timer T3346 with the remaining time of the running T3447 timer. Based on operator policy, if the tracking area update request is rejected due to core network redirection for CIoT optimizations, the network shall set the EMM cause value to #31 "Redirection to 5GCN required". NOTE 1: The network can take into account the UE's N1 mode capability, the 5GS CIoT network behaviour supported by the UE or the 5GS CIoT network behaviour supported by the 5GCN to determine the rejection with the EMM cause value #31 "Redirection to 5GCN required". Upon receiving the TRACKING AREA UPDATE REJECT message, if the message is integrity protected or contains a reject cause other than EMM cause value #25, the UE shall stop timer T3430, stop any transmission of user data and enter state MM IDLE. If the TRACKING AREA UPDATE REJECT message with EMM cause #25 or #78 was received without integrity protection, then the UE shall discard the message. The UE shall take the following actions depending on the EMM cause value received in the TRACKING AREA UPDATE REJECT message. #3 (Illegal UE); #6 (Illegal ME); or #8 (EPS services and non-EPS services not allowed); The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI List and eKSI. The UE shall consider the USIM as invalid for EPS and non-EPS services until switching off or the UICC containing the USIM is removed or the timer T3245 expires as described in clause 5.3.7a. Additionally, the UE shall delete the list of equivalent PLMNs and shall enter the state EMM-DEREGISTERED.NO-IMSI. If the message has been successfully integrity checked by the NAS and the UE maintains a counter for "SIM/USIM considered invalid for GPRS services", then the UE shall set this counter to UE implementation-specific maximum value. If the message has been successfully integrity checked by the NAS and the UE maintains a counter for "SIM/USIM considered invalid for non-GPRS services", then the UE shall set this counter to UE implementation-specific maximum value. If A/Gb mode or Iu mode is supported by the UE, the UE shall handle the MM parameters update status, TMSI, LAI and ciphering key sequence number, and the GMM parameters GMM state, GPRS update status, P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the combined routing area updating procedure is rejected with the GMM cause with the same value. For the EMM cause value #3 or #6, if the UE is operating in single-registration mode, the UE shall in addition handle the 5GMM parameters 5GMM state, 5GS update status, 5G-GUTI, last visited registered TAI, TAI list and ngKSI as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the registration procedure for mobility and periodic registration update performed over 3GPP access and indicating "mobility registration updating" in the 5GS registration type IE of the REGISTRATION REQUEST message is rejected with the 5GMM cause with the same value. For the EMM cause value #8, if the UE is operating in single-registration mode, the UE shall in addition set the 5GMM state to 5GMM-DEREGISTERED, 5GS update status to 5U3 ROAMING NOT ALLOWED, and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI.#7 (EPS services not allowed); The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI List and eKSI. The UE shall consider then USIM as invalid for EPS services until switching off or the UICC containing the USIM is removed or the timer T3245 expires as described in clause 5.3.7a. The UE shall enter the state EMM-DEREGISTERED. If the message has been successfully integrity checked by the NAS and the UE maintains a counter for "SIM/USIM considered invalid for GPRS services", then the UE shall set this counter to UE implementation-specific maximum value. A UE in CS/PS mode 1 or CS/PS mode 2 of operation which is already IMSI attached for non-EPS services is still IMSI attached for non-EPS services. A UE in CS/PS mode 1 or CS/PS mode 2 of operation shall set the update status to U2 NOT UPDATED, shall attempt to select GERAN or UTRAN radio access technology and proceed with appropriate MM specific procedure according to the MM service state. The UE shall not reselect E-UTRAN radio access technology until switching off or the UICC containing the USIM is removed. If A/Gb mode or Iu mode is supported by the UE, the UE shall in addition handle the GMM parameters GMM state, GPRS update status, P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the combined routing area updating procedure is rejected with the GMM cause with the same value. If the UE is operating in single-registration mode, the UE shall in addition handle the 5GMM parameters 5GMM state, 5GS update status, 5G-GUTI, last visited registered TAI, TAI list and ngKSI as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the registration procedure performed over 3GPP access and for mobility and periodic registration update indicating "mobility registration updating" in the 5GS registration type IE of the REGISTRATION REQUEST message is rejected with the 5GMM cause with the same value. #9 (UE identity cannot be derived by the network); The UE shall set the EPS update status to EU2 NOT UPDATED (and shall store it according to clause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI List and eKSI. The UE shall enter the state EMM-DEREGISTERED.NORMAL-SERVICE. If there is a CS fallback emergency call pending or CS fallback call pending, or a paging for CS fallback, the UE shall attempt to select GERAN or UTRAN radio access technology. If the UE finds a suitable GERAN or UTRAN cell, it then proceeds with the appropriate MM and CC specific procedures; otherwise, if there is a CS fallback emergency call or CS fallback call pending, the EMM sublayer shall indicate the abort of the EMM procedure to the MM sublayer. If there is a 1xCS fallback emergency call pending or 1xCS fallback call pending, or a paging for 1xCS fallback, the UE shall select cdma2000® 1x radio access technology. The UE then proceeds with appropriate cdma2000® 1x CS procedures. If there is a 1xCS fallback emergency call pending or 1xCS fallback call pending, or a paging for 1xCS fallback, and the UE has dual Rx/Tx configuration and supports enhanced 1xCS fallback, the UE shall perform a new attach procedure. If there is no CS fallback emergency call pending, CS fallback call pending, 1xCS fallback emergency call pending, 1xCS fallback call pending, paging for CS fallback, or paging for 1xCS fallback and the rejected request was not for initiating a PDN connection for emergency bearer services, the UE shall subsequently, automatically initiate the attach procedure. NOTE 2: User interaction is necessary in some cases when the UE cannot re-activate the EPS bearer(s) automatically. If A/Gb mode or Iu mode is supported by the UE, the UE shall in addition handle the GMM parameters GMM state, GPRS update status, P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the combined routing area updating procedure is rejected with the GMM cause with the same value. A UE in CS/PS mode 1 or CS/PS mode 2 of operation which is already IMSI attached for non-EPS services is still IMSI attached for non-EPS services. A UE in CS/PS mode 1 or CS/PS mode 2 of operation shall set the update status to U2 NOT UPDATED. If the UE is operating in the single-registration mode, the UE shall handle the 5GMM parameters 5GMM state, 5GS update status, 5G-GUTI, last visited registered TAI, TAI list and ngKSI as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the registration procedure for mobility and periodic registration update performed over 3GPP access and indicating "mobility registration updating" in the 5GS registration type IE of the REGISTRATION REQUEST message is rejected with the 5GMM cause with the same value. #10 (Implicitly detached); A UE in CS/PS mode 1 or CS/PS mode 2 of operation is IMSI detached for both EPS services and non-EPS services. The UE shall enter the state EMM-DEREGISTERED.NORMAL-SERVICE. The UE shall delete any mapped EPS security context or partial native EPS security context. If there is a CS fallback emergency call pending or CS fallback call pending, or a paging for CS fallback, the UE shall attempt to select GERAN or UTRAN radio access technology. If the UE finds a suitable GERAN or UTRAN cell, it then proceeds with the appropriate MM and CC specific procedures; otherwise, if there is a CS fallback emergency call or CS fallback call pending, the EMM sublayer shall indicate the abort of the EMM procedure to the MM sublayer. If there is a 1xCS fallback emergency call pending or 1xCS fallback call pending, or a paging for 1xCS fallback, the UE shall select cdma2000® 1x radio access technology. The UE then proceeds with appropriate cdma2000® 1x CS procedures. If there is a 1xCS fallback emergency call pending or 1xCS fallback call pending, or a paging for 1xCS fallback, and the UE has dual Rx/Tx configuration and supports enhanced 1xCS fallback, the UE shall perform a new attach procedure. If there is no CS fallback emergency call pending, CS fallback call pending, 1xCS fallback emergency call pending, 1xCS fallback call pending, paging for CS fallback, or paging for 1xCS fallback and the rejected request was not for initiating a PDN connection for emergency bearer services, the UE shall then perform a new attach procedure. NOTE 3: User interaction is necessary in some cases when the UE cannot re-activate the EPS bearer(s) automatically. If A/Gb mode or Iu mode is supported by the UE, the UE shall in addition handle the GMM state as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the combined routing area updating procedure is rejected with the GMM cause with the same value. A UE in CS/PS mode 1 or CS/PS mode 2 of operation shall set the update status to U2 NOT UPDATED. If the UE is operating in single-registration mode, the UE shall in addition handle the 5GMM state as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the registration procedure for mobility and periodic registration update performed over 3GPP access and indicating "mobility registration updating" in the 5GS registration type IE of the REGISTRATION REQUEST message is rejected with the 5GMM cause with the same value. #11 (PLMN not allowed); or #35 (Requested service option not authorized in this PLMN); The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI List and eKSI, and reset the tracking area updating attempt counter. The UE shall delete the list of equivalent PLMNs and enter the state EMM-DEREGISTERED.PLMN-SEARCH. The UE shall store the PLMN identity in the "forbidden PLMN list" and if the UE is configured to use timer T3245 (see 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]) then the UE shall start timer T3245 and proceed as described in clause 5.3.7a. If the message has been successfully integrity checked by the NAS and the UE maintains a PLMN-specific attempt counter for that PLMN, then the UE shall set this counter to the UE implementation-specific maximum value. The UE shall then perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. If A/Gb mode or Iu mode is supported by the UE, the UE shall handle and the MM parameters update status, TMSI, LAI, ciphering key sequence number and the location update attempt counter, and the GMM parameters GMM state, GPRS update status, P-TMSI, P-TMSI signature, RAI, GPRS ciphering key sequence number and routing area updating attempt counter as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the combined routing area updating procedure is rejected with the GMM cause value #11 and no RR connection exists. For the EMM cause value #11, if the UE is operating in single-registration mode, the UE shall in addition handle the 5GMM parameters 5GMM state, 5GS update status, 5G-GUTI, last visited registered TAI, TAI list, ngKSI and registration attempt counter as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the registration procedure for mobility and periodic registration update performed over 3GPP access and indicating "mobility registration updating" in the 5GS registration type IE of the REGISTRATION REQUEST message is rejected with the 5GMM cause with the same value. For the EMM cause value #35, if the UE is operating in single-registration mode, the UE shall in addition set the 5GMM state to 5GMM-DEREGISTERED, 5GS update status to 5U3 ROAMING NOT ALLOWED, and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. In addition, the UE shall reset the registration attempt counter. #12 (Tracking area not allowed); The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI List and eKSI. The UE shall reset the tracking area updating attempt counter and shall enter the state EMM-DEREGISTERED.LIMITED-SERVICE. The UE shall store the current TAI in the list of "forbidden tracking areas for regional provision of service". If the TRACKING AREA UPDATE REJECT message is not integrity protected, the UE shall memorize the current TAI was stored in the list of "forbidden tracking areas for regional provision of service" for non-integrity protected NAS reject message. If A/Gb mode or Iu mode is supported by the UE, the UE shall handle the MM parameters update status, TMSI, LAI, ciphering key sequence number and the location update attempt counter, and the GMM parameters GMM state, GPRS update status, P-TMSI, P-TMSI signature, RAI, GPRS ciphering key sequence number and routing area updating attempt counter as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the combined routing area updating procedure is rejected with the GMM cause with the same value. If the UE is operating in single-registration mode, the UE shall in addition handle the 5GMM parameters 5GMM state, 5GS update status, 5G-GUTI, last visited registered TAI, TAI list, ngKSI and registration attempt counter as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the registration procedure for mobility and periodic registration update performed over 3GPP access and indicating "mobility registration updating" in the 5GS registration type IE of the REGISTRATION REQUEST message is rejected with the 5GMM cause with the same value. #13 (Roaming not allowed in this tracking area); The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.3) and shall delete the list of equivalent PLMNs. The UE shall reset the tracking area updating attempt counter and shall change to state EMM-REGISTERED.PLMN-SEARCH. The UE shall store the current TAI in the list of "forbidden tracking areas for roaming" and shall remove the current TAI from the stored TAI list if present. If the TRACKING AREA UPDATE REJECT message is not integrity protected, the UE shall memorize the current TAI was stored in the list of "forbidden tracking areas for roaming" for non-integrity protected NAS reject message. If the UE is registered in N1 mode and operating in dual-registration mode, the PLMN that the UE chooses to register in is specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] clause 4.8.3. Otherwise the UE shall perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. The UE shall indicate the Update type IE "combined TA/LA updating with IMSI attach" when performing the tracking area updating procedure following the PLMN selection. If A/Gb mode or Iu mode is supported by the UE, the UE shall handle the MM parameters update status and the location update attempt counter, and the GMM parameters GMM state, GPRS update status and routing area updating attempt counter as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the combined routing area updating procedure is rejected with the GMM cause with the same value. If the UE is operating in single-registration mode, the UE shall in addition handle the 5GMM parameters 5GMM state, 5GS update status, and registration attempt counter as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the registration procedure for mobility and periodic registration update performed over 3GPP access and indicating "mobility registration updating" in the 5GS registration type IE of the REGISTRATION REQUEST message is rejected with the 5GMM cause with the same value. #14 (EPS services not allowed in this PLMN); The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.3). Furthermore, the UE shall delete any GUTI, last visited registered TAI, TAI List and eKSI. The UE shall reset the tracking area updating attempt counter and shall enter the state EMM-DEREGISTERED.PLMN-SEARCH. The UE shall store the PLMN identity in the "forbidden PLMNs for GPRS service" list and if the UE is configured to use timer T3245 (see 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]) then the UE shall start timer T3245 and proceed as described in clause 5.3.7a. If the message has been successfully integrity checked by the NAS and the UE maintains a PLMN-specific PS-attempt counter for that PLMN, then the UE shall set this counter to the UE implementation-specific maximum value. The UE operating in CS/PS mode 1 or CS/PS mode 2 of operation which is already IMSI attached for non-EPS services is still IMSI attached for non-EPS services. The UE operating in CS/PS mode 1 or CS/PS mode 2 of operation shall set the update status to U2 NOT UPDATED. A UE operating in CS/PS mode 1 of operation and supporting A/Gb mode or Iu mode may select GERAN or UTRAN radio access technology and proceed with the appropriate MM specific procedure according to the MM service state. In this case, the UE shall disable the E-UTRA capability (see clause 4.5). A UE operating in CS/PS mode 1 of operation and supporting A/Gb mode or Iu mode may perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. A UE operating in CS/PS mode 1 of operation and supporting S1 mode only, or operating in CS/PS mode 2 of operation shall delete the list of equivalent PLMNs and shall perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. If A/Gb mode or Iu mode is supported by the UE, the UE shall handle the GMM parameters GMM state, GPRS update status, P-TMSI, P-TMSI signature, RAI, GPRS ciphering key sequence number and routing area updating attempt counter as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the combined routing area updating procedure is rejected with the GMM cause with the same value. If the UE is operating in single-registration mode, the UE shall in addition set the 5GMM state to 5GMM-DEREGISTERED, 5GS update status to 5U3 ROAMING NOT ALLOWED, and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. In addition, the UE shall reset the registration attempt counter. #15 (No suitable cells in tracking area); The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.3). The UE shall reset the tracking area updating attempt counter and shall enter the state EMM-REGISTERED.LIMITED-SERVICE. The UE shall store the current TAI in the list of "forbidden tracking areas for roaming". If the TRACKING AREA UPDATE REJECT message is not integrity protected, the UE shall memorize the current TAI was stored in the list of "forbidden tracking areas for roaming" for non-integrity protected NAS reject message. Additionally, the UE shall remove the current TAI from the stored TAI list if present and: - if the UE is in WB-S1 mode and the Extended EMM cause IE with value "E-UTRAN not allowed" is included in the TRACKING AREA UPDATE REJECT message, the UE supports "E-UTRA Disabling for EMM cause #15", and the "E-UTRA Disabling Allowed for EMM cause #15" parameter as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17] is present and set to enabled; then the UE shall disable the E-UTRA capability as specified in clause 4.5 and search for a suitable cell in another location area or 5GS tracking area; - if the UE is in NB-S1 mode and the Extended EMM cause IE with value "NB-IoT not allowed" is included in the TRACKING AREA UPDATE REJECT message, then the UE may disable the NB-IoT capability as specified in clause 4.9 and search for a suitable cell in E-UTRAN radio access technology; - otherwise, the UE shall search for a suitable cell in another tracking area or in another location area according to 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [21]. The UE shall indicate the Update type IE "combined TA/LA updating with IMSI attach" when performing the tracking area updating procedure. If A/Gb mode or Iu mode is supported by the UE, the UE shall handle the MM parameters update status and the location update attempt counter, and the GMM parameters GMM state, GPRS update status and routing area updating attempt counter as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the combined routing area updating procedure is rejected with the GMM cause with the same value. If the UE is operating in single-registration mode, the UE shall in addition handle the 5GMM parameters 5GMM state, 5GS update status, and registration attempt counter as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the registration procedure for mobility and periodic registration update performed over 3GPP access and indicating "mobility registration updating" in the 5GS registration type IE of the REGISTRATION REQUEST message is rejected with the 5GMM cause with the same value. #22 (Congestion); If the T3346 value IE is present in the TRACKING AREA UPDATE REJECT message and the value indicates that this timer is neither zero nor deactivated, the UE shall proceed as described below, otherwise it shall be considered as an abnormal case and the behaviour of the UE for this case is specified in clause 5.5.3.3.6. The UE shall abort the tracking area updating procedure, reset the tracking area updating attempt counter and set the EPS update status to EU2 NOT UPDATED. If the rejected request was not for initiating a PDN connection for emergency bearer services, the UE shall change to state EMM-REGISTERED.ATTEMPTING-TO-UPDATE. The UE shall stop timer T3346 if it is running. If the TRACKING AREA UPDATE REJECT message is integrity protected, the UE shall start timer with the value provided in the T3346 value IE. If the TRACKING AREA UPDATE REJECT message is not integrity protected, the UE shall start timer T3346 with a random value from the default range specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13]. The UE stays in the current serving cell and applies the normal cell reselection process. The tracking area updating procedure is started, if still necessary, when timer T3346 expires or is stopped. If A/Gb mode or Iu mode is supported by the UE, the UE shall handle the GMM parameters GMM state, GPRS update status and routing area updating attempt counter as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the combined routing area updating procedure is rejected with the GMM cause with the same value. If the tracking area updating procedure was initiated for an MO MMTEL voice call or an MO MMTEL video call is started, then a notification that the request was not accepted due to network congestion shall be provided to upper layers. NOTE 4: This can result in the upper layers requesting establishment of the originating voice call on an alternative manner e.g. requesting establishment of a CS voice call (see 3GPP TS 24.173[ IMS Multimedia telephony communication service and supplementary services; Stage 3 ] [13E]). If the UE is operating in single-registration mode, the UE shall in addition handle the 5GMM parameters 5GMM state, 5GS update status and registration attempt counter as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the registration procedure for mobility and periodic registration update performed over 3GPP access and indicating "mobility registration updating" in the 5GS registration type IE of the REGISTRATION REQUEST message is rejected with the 5GMM cause with the same value. #25 (Not authorized for this CSG); EMM cause #25 is only applicable when received from a CSG cell. EMM cause #25 received from a non-CSG cell is considered as an abnormal case and the behaviour of the UE is specified in clause 5.5.3.3.6. The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and store it according to clause 5.1.3.3). The UE shall reset the tracking area updating attempt counter and shall enter the state EMM-REGISTERED.LIMITED-SERVICE. If the CSG ID and associated PLMN identity of the cell where the UE has sent the TRACKING AREA UPDATE REQUEST message are contained in the Allowed CSG list, the UE shall remove the entry corresponding to this CSG ID and associated PLMN identity from the Allowed CSG list. If the CSG ID and associated PLMN identity of the cell where the UE has sent the TRACKING AREA UPDATE REQUEST message are contained in the Operator CSG list, the UE shall apply the procedures defined in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6] clause 3.1A. The UE shall search for a suitable cell according to 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [21]. The UE shall indicate the Update type IE "combined TA/LA updating with IMSI attach" when performing the tracking area updating procedure. If A/Gb mode or Iu mode is supported by the UE, the UE shall handle the MM parameters update status and the location update attempt counter, and the GMM parameters GMM state, GPRS update status and routing area updating attempt counter as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the combined routing area updating procedure is rejected with the GMM cause with the same value. If the UE is operating in single-registration mode, the UE shall in addition set the 5GMM state to 5GMM-REGISTERED and set the 5GS update status to 5U3 ROAMING NOT ALLOWED and reset the registration attempt counter. #31 (Redirection to 5GCN required); EMM cause #31 received by a UE that has not indicated support for CIoT optimizations or not indicated support for N1 mode is considered as an abnormal case and the behaviour of the UE is specified in clause 5.5.3.3.6. The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.3). The UE shall reset the tracking area updating attempt counter and shall enter the state EMM-REGISTERED.LIMITED-SERVICE. The UE shall enable N1 mode capability for 3GPP access if it was disabled and disable the E-UTRA capability (see clause 4.5). If the UE is operating in single-registration mode, the UE shall in addition handle the 5GMM parameters 5GMM state, 5GS update status, and registration attempt counter as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the registration procedure for mobility and periodic registration update performed over 3GPP access and indicating "mobility registration updating" in the 5GS registration type IE of the REGISTRATION REQUEST message is rejected with the 5GMM cause with the same value. #36 (IAB-node operation not authorized); The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI List and eKSI, and reset the tracking area updating attempt counter. The UE shall delete the list of equivalent PLMNs and enter the state EMM-DEREGISTERED.PLMN-SEARCH. The UE shall store the PLMN identity in the "forbidden PLMN list" and if the UE is configured to use timer T3245 (see 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]) then the UE shall start timer T3245 and proceed as described in subclause 5.3.7a. If the message has been successfully integrity checked by the NAS and the UE maintains a PLMN-specific attempt counter for that PLMN, then the UE shall set this counter to the UE implementation-specific maximum value. The UE shall then perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. If the UE is operating in single-registration mode, the UE shall in addition handle the 5GMM parameters 5GMM state, 5GS update status, 5G-GUTI, last visited registered TAI, TAI list and ngKSI as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the registration procedure for mobility and periodic registration update performed over 3GPP access and indicating "mobility registration updating" in the 5GS registration type IE of the REGISTRATION REQUEST message is rejected with the 5GMM cause with the same value. #40 (No EPS bearer context activated); The UE shall deactivate all the EPS bearer contexts locally, if any, and shall enter the state EMM-DEREGISTERED.NORMAL-SERVICE. If there is a CS fallback emergency call pending or CS fallback call pending, or a paging for CS fallback, the UE shall attempt to select GERAN or UTRAN radio access technology. If the UE finds a suitable GERAN or UTRAN cell, it then proceeds with the appropriate MM and CC specific procedures; otherwise, if there is a CS fallback emergency call or CS fallback call pending, the EMM sublayer shall indicate the abort of the EMM procedure to the MM sublayer. If there is a 1xCS fallback emergency call pending or 1xCS fallback call pending, or a paging for 1xCS fallback, the UE shall select cdma2000® 1x radio access technology. The UE then proceeds with appropriate cdma2000® 1x CS procedures. If there is a 1xCS fallback emergency call pending or 1xCS fallback call pending, or a paging for 1xCS fallback, and the UE has dual Rx/Tx configuration and supports enhanced 1xCS fallback, the UE shall perform a new attach procedure. If there is no CS fallback emergency call pending, CS fallback call pending, 1xCS fallback emergency call pending, 1xCS fallback call pending, paging for CS fallback, or paging for 1xCS fallback and the rejected fallback request was not for initiating a PDN connection for emergency bearer services, the UE shall perform a new attach procedure. NOTE 5: User interaction is necessary in some cases when the UE cannot re-activate the EPS bearer(s) automatically. If A/Gb mode or Iu mode is supported by the UE, the UE shall in addition handle the GMM state as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the combined routing area updating procedure is rejected with the GMM cause value #10 "Implicitly detached". A UE in CS/PS mode 1 or CS/PS mode 2 of operation which is already IMSI attached for non-EPS services is still IMSI attached for non-EPS services. A UE in CS/PS mode 1 or CS/PS mode 2 of operation shall set the update status to U2 NOT UPDATED. If the UE is operating in single-registration mode, the UE shall in addition set the 5GMM state to 5GMM-DEREGISTERED. #42 (Severe network failure); The UE shall set the EPS update status to EU2 NOT UPDATED, and shall delete any GUTI, last visited registered TAI, TAI list, eKSI, and list of equivalent PLMNs, and set the tracking area updating attempt counter to 5. The UE shall start an implementation specific timer, setting its value to 2 times the value of T as defined in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. While this timer is running, the UE shall not consider the PLMN + RAT combination that provided this reject cause as a candidate for PLMN selection. The UE then enters state EMM-DEREGISTERED.PLMN-SEARCH in order to perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. If A/Gb mode or Iu mode is supported by the UE, the UE shall in addition set the GMM state to GMM-DEREGISTERED, GPRS update status to GU2 NOT UPDATED, MM update status to U2 NOT UPDATED, and shall delete the P-TMSI, P-TMSI signature, RAI, GPRS ciphering key sequence number, LAI, TMSI and ciphering key sequence number. If the UE is operating in single-registration mode, the UE shall in addition set the 5GMM state to 5GMM-DEREGISTERED, 5GS update status to 5U2 NOT UPDATED, and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. Other values are considered as abnormal cases. The behaviour of the UE in those cases is specified in clause 5.5.3.3.6.

3GPP TS 24.301

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

CT WG1

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

5.5.3.3.5

– ULInformationTransfer

The ULInformationTransfer message is used for the uplink transfer of NAS or non-3GPP dedicated information, or IAB-DU specific F1-C related information. Signalling radio bearer: SRB2 or SRB1 (only if SRB2 not established yet). If SRB2 is suspended, the UE does not send this message until SRB2 is resumed. If only dedicatedInfoF1c is included, SRB2 is used. RLC-SAP: AM Logical channel: DCCH Direction: UE to network ULInformationTransfer message -- ASN1START -- TAG-ULINFORMATIONTRANSFER-START ULInformationTransfer ::= SEQUENCE { criticalExtensions CHOICE { ulInformationTransfer ULInformationTransfer-IEs, criticalExtensionsFuture SEQUENCE {} } } ULInformationTransfer-IEs ::= SEQUENCE { dedicatedNAS-Message DedicatedNAS-Message OPTIONAL, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension ULInformationTransfer-v1700-IEs OPTIONAL } ULInformationTransfer-v1700-IEs ::= SEQUENCE { dedicatedInfoF1c-r17 DedicatedInfoF1c-r17 OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } -- TAG-ULINFORMATIONTRANSFER-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

N.6 Configuration of Credentials Holder for determining SNPN selection information

To enable the HPLMN or the subscribed SNPN acting as Credentials Holder to generate and provision UEs with SNPN selection information for discovery and selection of SNPNs providing Localized Services, based on Localized Service agreements between the Localized Service Provider or the SNPN providing Localized Services and the HPLMN or the subscribed SNPN acting as Credentials Holder, the Localized Service Provider or the SNPN providing access to Localized Services can provide configuration information for SNPN selection to the HPLMN or the subscribed SNPN acting as Credentials Holder. The configuration information for SNPN selection may contain at least one of the following parameters: a. SNPN ID or GIN of the SNPN providing access to one or more Localized Services; b. Identification of each Localized Service; c. validity information for each Localized Service, e.g. the validity time information or/and location assistance information; and/or d. List of UE IDs (e.g. GPSIs or External Group ID) identifying the UEs subscribed with a Localized Service. NOTE: How HPLMN or subscribed SNPN obtains the information above as part of the Localized Service agreements is out of 3GPP scope. The operator of the HPLMN or the subscribed SNPN acting as Credentials Holder then may use the information received from the SNPN providing Localized Services and/or Localized Service Provider to create or update the Credentials Holder controlled prioritized lists of preferred SNPNs/GINs for accessing Localized Services and provision the UEs using the Steering of Roaming procedure as defined in TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [17].

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

N.6

16.2 BSF address

The Bootstrapping Server Function (BSF) address is in the form of a Fully Qualified Domain Name as defined in IETF RFC 1035 [19] and IETF RFC 1123 [20]. The BSF address consists of one or more labels. Each label shall consist of the alphabetic characters (A-Z and a-z), digits (0-9) and the hyphen (-) in accordance with IETF RFC 1035 [19]. Each label shall begin and end with either an alphabetic character or a digit in accordance with IETF RFC 1123 [20]. The case of alphabetic characters is not significant. For 3GPP systems, the UE shall discover the BSF address from the identity information related to the UICC application that is used during the bootstrapping procedure i.e. IMSI for USIM, or IMPI for ISIM, in the following way: - In the case where the USIM is used in bootstrapping, the BSF address shall be derived as follows: 1. take the first 5 or 6 digits, depending on whether a 2 or 3 digit MNC is used (see 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [27]) and separate them into MCC and MNC; if the MNC is 2 digits then a zero shall be added at the beginning; 2. use the MCC and MNC derived in step 1 to create the "mnc<MNC>.mcc<MCC>.pub.3gppnetwork.org" domain name; 3. add the label "bsf." to the beginning of the domain. Example 1: If IMSI in use is "234150999999999", where MCC=234, MNC=15, and MSIN=0999999999, the BSF address would be "bsf.mnc015.mcc234.pub.3gppnetwork.org". - In the case where ISIM is used in bootstrapping, the BSF address shall be derived as follows: 1. extract the domain name from the IMPI; 2. if the last two labels of the domain name extracted from the IMPI are "3gppnetwork.org": a. the first label is "bsf"; b. the next labels are all labels of the domain name extracted from the IMPI apart from the last two labels; and c. the last three labels are "pub.3gppnetwork.org"; Example 2: If the IMPI in use is "234150999999999@ims.mnc015.mcc234.3gppnetwork.org", the BSF address would be "bsf.ims.mnc015.mcc234.pub.3gppnetwork.org". 3. if the last two labels of the domain name extracted from the IMPI are other than the "3gppnetwork.org": a. add the label "bsf." to the beginning of the domain. Example 3: If the IMPI in use is "user@operator.com", the BSF address would be "bsf.operator.com ".

3GPP TS 23.003

Numbering, addressing and identification

CT WG4

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

16.2

10.5.4.30 Cause of No CLI

Cause of No CLI information element provides the mobile station the detailed reason why Calling party BCD number is not notified (see 3GPP TS 24.081[ Line Identification supplementary services; Stage 3 ] [25]). The Cause of No CLI information element is coded as shown in figure 10.5.118a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.135a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The Cause of No CLI is a type 4 information element with the length of 3 octets. Figure 10.5.118a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Cause of No CLI information element Table 10.5.135a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Cause of No CLI 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.4.30

– SL-FreqConfigCommon

The IE SL-FreqConfigCommon specifies the cell-specific configuration information on one particular carrier frequency for NR sidelink communication. SL-FreqConfigCommon information element -- ASN1START -- TAG-SL-FREQCONFIGCOMMON-START SL-FreqConfigCommon-r16 ::= SEQUENCE { sl-SCS-SpecificCarrierList-r16 SEQUENCE (SIZE (1..maxSCSs)) OF SCS-SpecificCarrier, sl-AbsoluteFrequencyPointA-r16 ARFCN-ValueNR, sl-AbsoluteFrequencySSB-r16 ARFCN-ValueNR OPTIONAL, -- Need R frequencyShift7p5khzSL-r16 ENUMERATED {true} OPTIONAL, -- Cond V2X-SL-Shared valueN-r16 INTEGER (-1..1), sl-BWP-List-r16 SEQUENCE (SIZE (1..maxNrofSL-BWPs-r16)) OF SL-BWP-ConfigCommon-r16 OPTIONAL, -- Need R sl-SyncPriority-r16 ENUMERATED {gnss, gnbEnb} OPTIONAL, -- Need R sl-NbAsSync-r16 BOOLEAN OPTIONAL, -- Need R sl-SyncConfigList-r16 SL-SyncConfigList-r16 OPTIONAL, -- Need R ..., [[ absenceOfAnyOtherTechnology-r18 ENUMERATED {true} OPTIONAL, -- Need R sl-FreqSelectionConfig-r18 SL-FreqSelectionConfig-r18 OPTIONAL, -- Need R sl-SyncTxDisabled-r18 ENUMERATED {true} OPTIONAL, -- Need R sl-EnergyDetectionConfig-r18 CHOICE { sl-MaxEnergyDetectionThreshold-r18 INTEGER (-85..-52), sl-EnergyDetectionThresholdOffset-r18 INTEGER (-13..20) } OPTIONAL, -- Need R ue-toUE-COT-SharingED-Threshold-r18 INTEGER (-85..-52) OPTIONAL, -- Need R harq-ACKFeedbackRatioforContentionWindowAdjustmentGC-Option2-r18 INTEGER (10..100) OPTIONAL -- Need R ]] } -- TAG-SL-FREQCONFIGCOMMON-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

9.9.3.4 Authentication response parameter

The purpose of the Authentication response parameter information element is to provide the network with the authentication response calculated in the USIM. The Authentication response parameter information element is coded as shown in figure 9.9.3.4.1 and table 9.9.3.4.1. The Authentication response parameter is a type 4 information element with a minimum length of 6 octets and a maximum length of 18 octets. In an EPS authentication challenge, the response calculated in the USIM (RES) is minimum 4 octets and may be up to 16 octets in length. In a 5G AKA authentication challenge, the response calculated in the ME (RES*) is 16 octets in length. Figure 9.9.3.4.1: Authentication response parameter information element Table 9.9.3.4.1: Authentication response parameter 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.4

6.3.4.4 Precoding for spatial multiplexing using antenna ports with UE-specific reference signals

Precoding for spatial multiplexing using antenna ports with UE-specific reference signals is only used in combination with layer mapping for spatial multiplexing as described in clause 6.3.3.2. Spatial multiplexing using antenna ports with UE-specific reference signals supports up to eight antenna ports. If the higher-layer parameter dmrs-tableAlt is set to TRUE and the set of antenna ports is used for two layers transmission, the precoding operation for transmission on the two antenna ports is defined by where , . If the higher-layer parameter semiOpenLoop is set to TRUE for subframe PDSCH or the higher-layer parameter semiOpenLoop-STTI is set to TRUE for slot/subslot PDSCH and the set of antenna ports is used for rank=2 transmission, the precoding operation for transmission on the two antenna ports is defined by where and . If the number of codewords is two and the DCI associated with the scheduled PDSCH is of Format 2D and the 'PDSCH RE Mapping and Quasi-Co-Location indicator' field in the DCI indicates a higher-layer configured PDSCH-RE-MappingQCL containing two sets of parameters, the precoding operation for transmission on antenna ports is defined by where , and set of antenna ports used is given by Table 6.3.4.4-1. Table 6.3.4.4-1: Layer-to-port mapping for two-codeword transmission when PDSCH-RE-MappingQCL contains two sets of parameters Otherwise, the set of antenna ports used is and the precoding operation for transmission on antenna ports is defined by where , .

3GPP TS 36.211

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

RAN1

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

6.3.4.4

6.5.2.3 In-band emissions

The in-band emission is defined as the average across 12 sub-carrier and as a function of the RB offset from the edge of the allocated UL transmission bandwidth. The in-band emission is measured as the ratio of the UE output power in a non–allocated RB to the UE output power in an allocated RB. The basic in-band emissions measurement interval is defined over one slot in the time domain. When the PUSCH or PUCCH transmission slot is shortened due to multiplexing with SRS, the in-band emissions measurement interval is reduced by one SC-FDMA symbol, accordingly. Likewise, when the PUSCH starting position is modified or when the second last symbol is the ending symbol of the PUSCH sub-frame for Frame Structure Type 3, the in-band emissions measurement interval is reduced accordingly.

3GPP TS 36.101

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

RAN4

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

6.5.2.3

5.2.6.22 Nnef_AMPolicyAuthorization Service 5.2.6.22.1 General

Service description: This service is to authorise an AF request and trigger a respective Npcf_AMPolicyAuthorization request. This service allows the NF consumer to subscribe/unsubscribe the notification of events for reporting change of service 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]. The description of the Throughput requirements, service coverage requirements and policy duration are defined in clause 6.1.2.6.1 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20].

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

5.2.6.22

D.5.4.1 Message definition

The UE STATE INDICATION message is sent by the UE to the PCF: a) to deliver the UPSI(s) of the UE policy section(s) stored in the UE; b) to indicate whether the UE supports ANDSP; c) to indicate whether the UE supports URSP provisioning in EPS in the UE policy classmark IE; c1) to indicate whether the UE supports VPS URSP; c2) to indicate whether the UE supports reporting URSP rule enforcement; and d) to deliver the UE's one or more OS IDs; see table D.5.4.1.1. Message type: UE STATE INDICATION Significance: dual Direction: UE to network Table D.5.4.1.1: UE STATE INDICATION message content

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

6.3.3 Abnormal cases in the UE

The following abnormal case can be identified: a) ESM uplink message transmission failure indication by lower layers Unless the procedure descriptions in clause 6.6 specify a different behaviour, the following applies: - If lower layers indicate a TAI change, but the current TAI is not in the TAI list, the ESM procedure shall be aborted and re-initiated after successfully performing a tracking area updating procedure. - If lower layers indicate a TAI change, but the current TAI is still part of the TAI list, it is up to the UE implementation how the ESM procedure is re-initiated. - If lower layers indicate the TAI has not changed, it is up to the UE implementation how the ESM procedure is re-initiated. NOTE 1: The ESM procedure can typically be re-initiated using a retransmission mechanism of the uplink message (the one that has previously failed to be transmitted) with new sequence number and message authentication code information thus avoiding to restart the whole procedure. The case a) above does not apply to the ESM INFORMATION RESPONSE message. NOTE 2: The ESM INFORMATION RESPONSE message cannot be subjected to a transmission failure by lower layers due to handover as no handover message can be accepted by the UE prior to reception of the ATTACH ACCEPT message (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]). b) Transmission failure of the ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message indication from EMM sublayer when the UE received any ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST messages during the attach procedure It is up to the UE implementation how the dedicated EPS bearer context activation procedure is re-initiated. NOTE 3: The ESM procedure can typically be re-initiated using a retransmission mechanism of the ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message or ACTIVATE DEDICATED EPS BEARER CONTEXT REJECT message with new sequence number and message authentication code information thus avoiding to restart the whole 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.3.3

– CG-CandidateList

This message is used to transfer the SCG radio configuration for one or more candidate cells for Conditional PSCell Addition (CPA) or Conditional PSCell Change (CPC) as generated by the candidate target SgNB. Direction: Secondary gNB to master gNB or eNB. CG-CandidateList message -- ASN1START -- TAG-CG-CANDIDATELIST-START CG-CandidateList ::= SEQUENCE { criticalExtensions CHOICE { c1 CHOICE{ cg-CandidateList-r17 CG-CandidateList-r17-IEs, spare3 NULL, spare2 NULL, spare1 NULL }, criticalExtensionsFuture SEQUENCE {} } } CG-CandidateList-r17-IEs ::= SEQUENCE { cg-CandidateToAddModList-r17 SEQUENCE (SIZE (1..maxNrofCondCells-r16)) OF CG-CandidateInfo-r17 OPTIONAL, cg-CandidateToReleaseList-r17 SEQUENCE (SIZE (1..maxNrofCondCells-r16)) OF CG-CandidateInfoId-r17 OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } CG-CandidateInfo-r17 ::= SEQUENCE { cg-CandidateInfoId-r17 CG-CandidateInfoId-r17, candidateCG-Config-r17 OCTET STRING (CONTAINING CG-Config) } CG-CandidateInfoId-r17::= SEQUENCE { ssbFrequency-r17 ARFCN-ValueNR, physCellId-r17 PhysCellId } -- TAG-CG-CANDIDATELIST-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

9.2.7 Radio Link Failure

In RRC_CONNECTED, the UE performs Radio Link Monitoring (RLM) in the active BWP based on reference signals (SSB/CSI-RS) and signal quality thresholds configured by the network. SSB-based RLM is based on the CD-SSB associated to the initial DL BWP and can be configured for the initial DL BWP, 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. Besides, SSB-based RLM can be also performed based on a non-cell defining SSB, if configured for the active DL BWP. For other DL BWPs, RLM can only be performed based on CSI-RS, if configured for the active DL BWP. In case of DAPS handover, the UE continues the detection of radio link failure at the source cell until the successful completion of the random access procedure to the target cell. The UE declares Radio Link Failure (RLF) when one of the following criteria are met: - Expiry of a radio problem timer started after indication of radio problems from the physical layer (if radio problems are recovered before the timer is expired, the UE stops the timer); or - Expiry of a timer started upon triggering a measurement report for a measurement identity for which the timer has been configured while another radio problem timer is running; or - Random access procedure failure; or - RLC failure; or - Detection of consistent uplink LBT failures for operation with shared spectrum channel access as described in 5.6.1; or - For IAB-MT, the reception of a BH RLF indication received from its parent node. After RLF is declared, the UE: - stays in RRC_CONNECTED; - in case of DAPS handover, for RLF in the source cell: - stops any data transmission or reception via the source link and releases the source link, but maintains the source RRC configuration; - if handover failure is then declared at the target cell, the UE: - selects a suitable cell and then initiates RRC re-establishment; - enters RRC_IDLE if a suitable cell was not found within a certain time after handover failure was declared. - in case of CHO, for RLF in the source cell: - selects a suitable cell and if the selected cell is a CHO candidate and if network configured the UE to try CHO after RLF then the UE attempts CHO execution once, otherwise re-establishment is performed; - enters RRC_IDLE if a suitable cell was not found within a certain time after RLF was declared. - in case of MCG LTM, for RLF in the source cell: - selects a suitable cell and if the selected cell is an LTM candidate cell and if network configured the UE to try LTM after RLF then the UE attempts LTM execution once, otherwise re-establishment is performed; - enters RRC_IDLE if a suitable cell was not found within a certain time after RLF was declared. - otherwise, for RLF in the serving cell or in case of DAPS handover, for RLF in the target cell before releasing the source cell: - selects a suitable cell and then initiates RRC re-establishment; - enters RRC_IDLE if a suitable cell was not found within a certain time after RLF was declared. When RLF occurs at the IAB BH link, the same mechanisms and procedures are applied as for the access link. This includes BH RLF detection and RLF recovery. The IAB-DU can transmit a BH RLF detection indication to its child nodes in the following cases: - The collocated IAB-MT initiates RRC re-establishment; - The collocated IAB-MT is dual-connected, detects BH RLF on a BH link, and cannot perform UL re-routing for any traffic. This includes the scenario of an IAB-node operating in EN-DC or NR-DC, which uses only one link for backhauling and has BH RLF on this BH link; - The collocated IAB-MT has received a BH RLF detection indication from a parent node, and there is no remaining backhaul link that is unaffected by the BH RLF condition indicated. Upon reception of the BH RLF detection indication, the child node may perform local rerouting for upstream traffic, if possible, over an available BH link. If the IAB-DU has transmitted a BH RLF detection indication to a child node due to an RLF condition on the collocated IAB-MT's parent link, and the collocated IAB-MT's subsequent RLF recovery is successful, the IAB-DU may transmit a BH RLF recovery indication to this child node. If the IAB-DU has transmitted a BH RLF detection indication to a child node due to the reception of a BH RLF detection indication by the collocated IAB-MT, and the collocated IAB-MT receives a BH RLF recovery indication, the IAB-DU may also transmit a BH RLF recovery indication to this child node. Upon reception of the BH RLF recovery indication, the child node reverts the actions triggered by the reception of the previous BH RLF detection indication. In case the RRC re-establishment procedure fails, the IAB-node may transmit a BH RLF indication to its child nodes. The BH RLF detection indication, BH RLF recovery indication and BH RLF indication are transmitted as BAP Control PDUs.

3GPP TS 38.300

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

RAN2

3GPP Series : 38 , Radio technology beyond LTE

9.2.7

– VarMeasConfigSL

The UE variable VarMeasConfigSL includes the accumulated configuration of the NR sidelink measurements to be performed by the UE of unicast destination. VarMeasConfigSL UE variable -- ASN1START -- TAG-VARMEASCONFIGSL-START VarMeasConfigSL-r16 ::= SEQUENCE { -- NR sidelink measurement identities sl-MeasIdList-r16 SL-MeasIdList-r16 OPTIONAL, -- NR sidelink measurement objects sl-MeasObjectList-r16 SL-MeasObjectList-r16 OPTIONAL, -- NR sidelink reporting configurations sl-ReportConfigList-r16 SL-ReportConfigList-r16 OPTIONAL, -- Other parameters sl-QuantityConfig-r16 SL-QuantityConfig-r16 OPTIONAL } -- TAG-VARMEASCONFIGSL-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

– PosSI-SchedulingInfo

-- ASN1START -- TAG-POSSI-SCHEDULINGINFO-START PosSI-SchedulingInfo-r16 ::= SEQUENCE { posSchedulingInfoList-r16 SEQUENCE (SIZE (1..maxSI-Message)) OF PosSchedulingInfo-r16, posSI-RequestConfig-r16 SI-RequestConfig OPTIONAL, -- Cond MSG-1 posSI-RequestConfigSUL-r16 SI-RequestConfig OPTIONAL, -- Cond SUL-MSG-1 ..., [[ posSI-RequestConfigRedCap-r17 SI-RequestConfig OPTIONAL -- Cond REDCAP-MSG-1 ]], [[ posSI-RequestConfigMSG1-Repetition-r18 SI-RequestConfigRepetition-r18 OPTIONAL, -- Cond MSG-1 posSI-RequestConfigSUL-MSG1-Repetition-r18 SI-RequestConfigRepetition-r18 OPTIONAL, -- Cond SUL-MSG-1 posSI-RequestConfigRedCap-MSG1-Repetition-r18 SI-RequestConfigRepetition-r18 OPTIONAL -- Cond REDCAP-MSG-1 ]] } PosSchedulingInfo-r16 ::= SEQUENCE { offsetToSI-Used-r16 ENUMERATED {true} OPTIONAL, -- Need R posSI-Periodicity-r16 ENUMERATED {rf8, rf16, rf32, rf64, rf128, rf256, rf512}, posSI-BroadcastStatus-r16 ENUMERATED {broadcasting, notBroadcasting}, posSIB-MappingInfo-r16 PosSIB-MappingInfo-r16, ... } PosSIB-MappingInfo-r16 ::= SEQUENCE (SIZE (1..maxSIB)) OF PosSIB-Type-r16 PosSIB-Type-r16 ::= SEQUENCE { encrypted-r16 ENUMERATED { true } OPTIONAL, -- Need R gnss-id-r16 GNSS-ID-r16 OPTIONAL, -- Need R sbas-id-r16 SBAS-ID-r16 OPTIONAL, -- Cond GNSS-ID-SBAS posSibType-r16 ENUMERATED { posSibType1-1, posSibType1-2, posSibType1-3, posSibType1-4, posSibType1-5, posSibType1-6, posSibType1-7, posSibType1-8, posSibType2-1, posSibType2-2, posSibType2-3, posSibType2-4, posSibType2-5, posSibType2-6, posSibType2-7, posSibType2-8, posSibType2-9, posSibType2-10, posSibType2-11, posSibType2-12, posSibType2-13, posSibType2-14, posSibType2-15, posSibType2-16, posSibType2-17, posSibType2-18, posSibType2-19, posSibType2-20, posSibType2-21, posSibType2-22, posSibType2-23, posSibType3-1, posSibType4-1, posSibType5-1,posSibType6-1, posSibType6-2, posSibType6-3,... }, areaScope-r16 ENUMERATED {true} OPTIONAL -- Need S } GNSS-ID-r16 ::= SEQUENCE { gnss-id-r16 ENUMERATED{gps, sbas, qzss, galileo, glonass, bds, ..., navic-v1760}, ... } SBAS-ID-r16 ::= SEQUENCE { sbas-id-r16 ENUMERATED { waas, egnos, msas, gagan, ...}, ... } -- TAG-POSSI-SCHEDULINGINFO-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

6.4.1.7 Abnormal cases on the network side

The following abnormal cases can be identified: a) If the received request type is "initial emergency request" and there is an existing emergency PDU session for the UE, regardless whether the PDU session ID in the PDU SESSION ESTABLISHMENT REQUEST message is identical to the PDU session ID of the existing PDU session, the SMF shall locally release the existing emergency PDU session and proceed the new PDU SESSION ESTABLISHMENT REQUEST message b) The information for the PDU session authentication and authorization by the external DN in PDU DN request container is not compliant with local policy and user's subscription data If the PDU session being established is a non-emergency PDU session, the request type is not set to "existing PDU session", the PDU session authentication and authorization by the external DN is required due to local policy and user's subscription data and the information for the PDU session authentication and authorization by the external DN in the SM PDU DN request container IE is not compliant with the local policy and user's subscription data, the SMF shall reject the PDU session establishment request including the 5GSM cause #29 "user authentication or authorization failed", in the PDU SESSION ESTABLISHMENT REJECT message. c) UE-requested PDU session establishment with request type set to "initial request" for an existing PDU session: If the SMF receives a PDU SESSION ESTABLISHMENT REQUEST message with a PDU session ID identical to the PDU session ID of an existing PDU session and with request type set to "initial request", the SMF shall locally release the existing PDU session and proceed with the PDU session establishment procedure. d) UE-requested PDU session establishment with request type "existing PDU session" or "existing emergency PDU session" for a PDU session that does not exist: If the SMF receives a PDU SESSION ESTABLISHMENT REQUEST message with request type set to "existing PDU session" or "existing emergency PDU session", and the SMF does not have any information about that PDU session, then the SMF shall reject the PDU session establishment procedure with the 5GSM cause set to #54 "PDU session does not exist" in the PDU SESSION ESTABLISHMENT REJECT message. e) 5G access network cannot forward the message: If the SMF determines based on content of the n2SmInfo attribute specified in 3GPP TS 29.502[ 5G System; Session Management Services; Stage 3 ] [20A] that the DL NAS TRANSPORT message carrying the PDU SESSION ESTABLISHMENT ACCEPT was not forwarded to the UE by the 5G access network, then the SMF shall reject the PDU session establishment procedure with the 5GSM cause set to #26 "insufficient resources" in the PDU SESSION ESTABLISHMENT 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

6.4.1.7

4.17.10 Delegated service discovery when NF service consumer and NF service producer are in different PLMNs

Figure 4.17.10-1: Delegated NF service discovery when NF service consumer and NF service producer are in different PLMNs 1. The NF service consumer intends to communicate with an NF service producer. The NF service consumer sends the request to an SCP. The request includes at least the source PLMN ID and the target PLMN ID in the discovery and selection parameters necessary for the SCP to discover and select a NF service producer instance. The discovery and selection parameters are included in the request by the NF service consumer in a way that the SCP does not need to parse the request body. 2. The SCP recognises that the request is for a NF service producer in another PLMN. SCP interacts with NRF using the Nnrf_NFDiscovery service. 3. NRF in PLMN-1 and NRF in PLMN 2 interact using the Nnrf_NFDiscovery service. See step 2 in clause 4.17.5. 4. SCP gets Nnrf_NFDiscovery service response with NF profile(s). 5. SCP selects a NF service producer instance in PLMN-2. 6. SCP forwards the request to the selected NF service producer instance in PLMN-2. Alternatively, SCP may send the discovery request directly to the NRF in PLMN-2, if it has the relevant NRF address and is authorized by the NRF in PLMN-2. Thus step 2 goes from SCP to NRF in PLMN-2 and step 4 goes from NRF in PLMN-2 to SCP and step 3 is omitted.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.17.10

8.11.4 Support of shared signalling transport

This clause specifies for F1-C, Xn-C and, in case of EN-DC, for X2-C, how an interface instance is identified in case of network sharing with multiple cell ID broadcast with shared signalling transport. For UE associated signalling, the interface instance is identified by assigning on F1-C appropriate UE F1AP IDs, on Xn-C appropriate UE XnAP IDs and on X2-C appropriate UE X2AP IDs. For non-UE associated signalling, the interface instance is identified on F1-C by the assigning an appropriate value to the Transaction ID, on Xn-C and X2-C by including the Interface Instance Indication in the respective message and assigning an appropriate value to it.

3GPP TS 38.401

NG-RAN; Architecture description

RAN3

3GPP Series : 38 , Radio technology beyond LTE

8.11.4

6.2.14 NSSF

The Network Slice Selection Function (NSSF) supports the following functionality: - Selecting the set of Network Slice instances serving the UE; - Determining the Allowed NSSAI and, if needed, the mapping to the Subscribed S-NSSAIs; - Determining the Configured NSSAI and, if needed, the mapping to the Subscribed S-NSSAIs; - Determining the AMF Set to be used to serve the UE, or, based on configuration, a list of candidate AMF(s), possibly by querying the NRF; - The NSSF may provide support for Network Slice restriction and Network Slice instance restriction based on NWDAF analytics. - Determining whether an S-NSSAI has to be replaced and providing to the AMF the indication that the S-NSSAI is unavailable and a corresponding Alternative S-NSSAI, e.g. based on received NWDAF analytics (e.g. for Service Experience for a Network Slice or Slice load level), or local trigger from the OAM system.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

6.2.14

A.4.3.2 Further guidelines

Further to the general principles defined in the previous clause, the following additional guidelines apply regarding the use of extension markers: - Extension markers within SEQUENCE: - Extension markers are primarily, but not exclusively, introduced at the higher nesting levels. - Extension markers are introduced for a SEQUENCE comprising several fields as well as for information elements whose extension would result in complex structures without it (e.g. re-introducing another list). - Extension markers are introduced to make it possible to maintain important information structures e.g. parameters relevant for one particular RAT. - Extension markers are also used for size critical messages (i.e. messages on BCCH, BR-BCCH, PCCH and CCCH), although introduced somewhat more carefully. - The extension fields introduced (or frozen) in a specific version of the specification are grouped together using double brackets. - Extension markers within ENUMERATED: - Spare values may be used until the number of values reaches the next power of 2, while the extension marker caters for extension beyond that limit, given that the use of spare values in a later Release is possible without any error cases. - A suffix of the form "vXYZ" is used for the identifier of each new value, e.g. "value-vXYZ". - Extension markers within CHOICE: - Extension markers are introduced when extension is foreseen and when comprehension is not required by the receiver i.e. behaviour is defined for the case where the receiver cannot comprehend the extended value (e.g. ignoring an optional CHOICE field). It should be noted that defining the behaviour of a receiver upon receiving a not comprehended choice value is not required if the sender is aware whether or not the receiver supports the extended value. - A suffix of the form "vXYZ" is used for the identifier of each new choice value, e.g. "choice-vXYZ". Non-critical extensions at the end of a message/ of a field contained in an OCTET or BIT STRING: - When a nonCriticalExtension is actually used, a "Need" code should not be provided for the field, which always is a group including at least one extension and a field facilitating further possible extensions. For simplicity, it is recommended not to provide a "Need" code when the field is not actually used either. Further, more general, guidelines: - In case a need code is not provided for a group, a "Need" code is provided for all individual extension fields within the group i.e. including for fields that are not marked as OPTIONAL. The latter is to clarify the action upon absence of the whole group.

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

A.4.3.2

6.13.1 Description

The proliferation of video services, ad-hoc multicast/broadcast streams, software delivery over wireless, group communications and broadcast/multicast IoT applications have created a need for a flexible and dynamic allocation of radio resources between unicast and multicast services within the network as well as support for a stand-alone deployment of multicast/broadcast network. Moreover, enabling such a service over a network for a wide range of inter-site distances between the radio base stations will enable a more efficient and effective delivery system for real-time and streaming multicast/broadcast content over wide geographic areas as well as in specific geographic areas spanning a limited number of base stations. A flexible multicast/broadcast service will allow the 5G system to efficiently deliver such services.

3GPP TS 22.261

Service requirements for the 5G system

SA WG1

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

6.13.1

8.3.1.4 Performance Requirements for semiOpenLoop transmission

The requirements are specified in Table 8.3.1.4-2, with the addition of the parameters in Table 8.3.1.4-1 and the downlink physical channel setup according to Annex C.3.2. The purpose of these tests is to verify rank one and rank two performances for full RB allocation upon antenna ports 7 and 8 with higher layer parameter semiOpenLoop is configured. Table 8.3.1.4-1: Test Parameters for Testing CDM-multiplexed DM RS (dual layer) when high layer parameter semiOpenLoop is configured Table 8.3.1.4-2: Minimum Performance Requirements for CDM-multiplexed DM RS (FRC) when high layer parameter semiOpenLoop is configured

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

5.15.5.3 Establishing a PDU Session in a Network Slice

The PDU Session Establishment in a Network Slice instance to a DN allows data transmission in a Network Slice instance. A PDU Session is associated to an S-NSSAI and a DNN. A UE that is registered in a PLMN over an Access Type and has obtained a corresponding Allowed NSSAI, shall indicate in the PDU Session Establishment procedure the S-NSSAI according to the NSSP in the URSP rules or according to the UE Local Configuration as defined in clause 6.1.2.2.1 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45], and, if available, the DNN the PDU Session is related to. The UE includes the appropriate S-NSSAI from this Allowed NSSAI and, if mapping of the Allowed NSSAI to HPLMN S-NSSAIs was provided, an S-NSSAI with the corresponding value from this mapping. If the UE cannot determine any S-NSSAI after performing the association of the application to a PDU Session according to clause 6.1.2.2.1 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45], the UE shall not indicate any S-NSSAI in the PDU Session Establishment procedure. The network (HPLMN) may provision the UE with Network Slice selection policy (NSSP) as part of the URSP rules, see clause 6.6.2 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. When the Subscription Information contains more than one S-NSSAI and the network wants to control/modify the UE usage of those S-NSSAIs, then the network provisions/updates the UE with NSSP as part of the URSP rules. When the Subscription Information contains only one S-NSSAI, the network needs not provision the UE with NSSP as part of the URSP rules. The NSSP rules associate an application with one or more HPLMN S-NSSAIs. A default rule which matches all applications to a HPLMN S-NSSAI may also be included. The UE shall store and use the URSP rules, including the NSSP, as described in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. When a UE application associated with a specific S-NSSAI requests data transmission: - if the UE has one or more PDU Sessions established corresponding to the specific S-NSSAI, the UE routes the user data of this application in one of these PDU Sessions, unless other conditions in the UE prohibit the use of these PDU Sessions. If the application provides a DNN, then the UE considers also this DNN to determine which PDU Session to use. This is further described in clause 6.6.2 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. - If the UE does not have a PDU Session established with this specific S-NSSAI, the UE requests a new PDU Session corresponding to this S-NSSAI and with the DNN that may be provided by the application. In order for the RAN to select a proper resource for supporting network slicing in the RAN, RAN needs to be aware of the Network Slices used by the UE. This is further described in clause 6.6.2 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. If the AMF is not able to determine the appropriate NRF to query for the S-NSSAI provided by the UE, the AMF may query the NSSF with this specific S-NSSAI, location information, PLMN ID of the SUPI. The NSSF determines and returns the appropriate NRF to be used to select NFs/services within the selected Network Slice instance. The NSSF may also return an NSI ID to be used to select NFs within the selected Network Slice instance to use for this S-NSSAI. The AMF or NSSF may select an S-NSSAI (if the UE does not provide an S-NSSAI for the PDU session establishment) and a Network Slice instance, based on load level and/or Observe Service Experience and/or Dispersion analytics from NWDAF, as described in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [86]. The IP address or FQDN of the NSSF is locally configured in the AMF. SMF discovery and selection within the selected Network Slice instance is initiated by the AMF when a SM message to establish a PDU Session is received from the UE. The appropriate NRF is used to assist the discovery and selection tasks of the required network functions for the selected Network Slice instance. The AMF queries the appropriate NRF to select an SMF in a Network Slice instance based on S-NSSAI, DNN, NSI-ID (if available) and other information e.g. UE subscription and local operator policies, when the UE triggers PDU Session Establishment. The AMF may select the SMF among the set of the SMF instance(s) returned by the NRF or locally configured in the AMF, based on network data analytics (NF load, etc.) from the NWDAF as described in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [86]. The selected SMF establishes a PDU Session based on S-NSSAI and DNN. When the AMF belongs to multiple Network Slice instances, based on configuration, the AMF may use an NRF at the appropriate level for the SMF selection. For further details on the SMF selection, refer to clause 4.3.2.2.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. When a PDU Session for a given S-NSSAI is established using a specific Network Slice instance, the CN provides to the (R)AN the S-NSSAI corresponding to this Network Slice instance to enable the RAN to perform access specific functions. The UE shall not perform PDU Session handover from one Access Type to another if the S-NSSAI of the PDU Session is not included in the Allowed NSSAI of the target Access Type.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.15.5.3

– SL-DRX-ConfigGC-BC

The IE SL-DRX-ConfigGC-BC is used to configure DRX related parameters for NR sidelink groupcast and broadcast communication, unicast/broadcast based communication of Direct Link Establishment Request (TS 24.587[ Vehicle-to-Everything (V2X) services in 5G System (5GS); Stage 3 ] [57]), and discovery message (TS 24.554[ Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3 ] [72]). SL-DRX-ConfigGC-BC information element -- ASN1START -- TAG-SL-DRX-CONFIGGC-BC-START SL-DRX-ConfigGC-BC-r17 ::= SEQUENCE { sl-DRX-GC-BC-PerQoS-List-r17 SEQUENCE (SIZE (1..maxSL-GC-BC-DRX-QoS-r17)) OF SL-DRX-GC-BC-QoS-r17 OPTIONAL, -- Need M sl-DRX-GC-generic-r17 SL-DRX-GC-Generic-r17 OPTIONAL, -- Need M sl-DefaultDRX-GC-BC-r17 SL-DRX-GC-BC-QoS-r17 OPTIONAL, -- Need M ... } SL-DRX-GC-BC-QoS-r17 ::= SEQUENCE { sl-DRX-GC-BC-MappedQoS-FlowList-r17 SEQUENCE (SIZE (1..maxNrofSL-QFIs-r16)) OF SL-QoS-Profile-r16 OPTIONAL, -- Need M sl-DRX-GC-BC-OnDurationTimer-r17 CHOICE { subMilliSeconds INTEGER (1..31), milliSeconds ENUMERATED { ms1, ms2, ms3, ms4, ms5,ms6, ms8, ms10, ms20, ms30, ms40, ms50, ms60, ms80, ms100, ms200, ms300, ms400, ms500, ms600, ms800, ms1000, ms1200, ms1600, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1} }, sl-DRX-GC-InactivityTimer-r17 ENUMERATED { ms0, ms1, ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30, ms40, ms50, ms60, ms80, ms100, ms200, ms300, ms500, ms750, ms1280, ms1920, ms2560, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1}, sl-DRX-GC-BC-Cycle-r17 ENUMERATED { ms10, ms20, ms32, ms40, ms60, ms64, ms70, ms80, ms128, ms160, ms256, ms320, ms512, ms640, ms1024, ms1280, ms2048, ms2560, ms5120, ms10240, spare12, spare11, spare10, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1}, ... } SL-DRX-GC-Generic-r17 ::= SEQUENCE { sl-DRX-GC-HARQ-RTT-Timer1-r17 ENUMERATED {sl0, sl1, sl2, sl4, spare4, spare3, spare2, spare1} OPTIONAL, -- Need M sl-DRX-GC-HARQ-RTT-Timer2-r17 ENUMERATED {sl0, sl1, sl2, sl4, spare4, spare3, spare2, spare1} OPTIONAL, -- Need M sl-DRX-GC-RetransmissionTimer-r17 ENUMERATED { sl0, sl1, sl2, sl4, sl6, sl8, sl16, sl24, sl33, sl40, sl64, sl80, sl96, sl112, sl128, sl160, sl320, spare15, spare14, spare13, spare12, spare11, spare10, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1} } -- TAG-SL-DRX-CONFIGGC-BC-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

9.2.1.2 Cell Reselection

A UE in RRC_IDLE performs cell reselection. The principles of the procedure are the following: - Cell reselection is always based on CD-SSBs located on the synchronization raster (see clause 5.2.4). - The UE makes measurements of attributes of the serving and neighbour cells to enable the reselection process: - For the search and measurement of inter-frequency neighbouring cells, only the carrier frequencies need to be indicated. - Cell reselection identifies the cell that the UE should camp on. It is based on cell reselection criteria which involves measurements of the serving and neighbour cells: - Intra-frequency reselection is based on ranking of cells; - Inter-frequency reselection is based on absolute priorities where a UE tries to camp on the highest priority frequency available; - A Neighbour Cell List (NCL) can be provided by the serving cell to handle specific cases for intra- and inter-frequency neighbouring cells; - Exclude-lists can be provided to prevent the UE from reselecting to specific intra- and inter-frequency neighbouring cells; - Allow-lists can be provided to request the UE to reselect to only specific intra- and inter-frequency neighbouring cells; - Cell reselection can be speed dependent; - Service specific prioritisation; - Slice-based cell reselection information can be provided to facilitate the UE to reselect a cell that supports specific slices. In multi-beam operations, the cell quality is derived amongst the beams corresponding to the same cell (see clause 9.2.4).

3GPP TS 38.300

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

RAN2

3GPP Series : 38 , Radio technology beyond LTE

9.2.1.2

5.11.5 UE Radio Capability for Category M Differentiation

This functionality is used by the Core Network to be able to identify traffic to/from Category M UEs for charging differentiation. The eNodeB determines whether a UE is of Category M from the UE's radio capability if UE signals one or more of the specific Category M. The eNodeB then indicates to the MME whether the UE is Category M using the "LTE-M Indication" information in S1-AP message(s) used to upload the UE Radio Capabilities to the MME. Typically this is at the same time as the eNodeB uploads the UE Radio Capability information. When the UE is of Category M, the MME receives one "LTE-M Indication" from eNB irrespective of whether the UE supports terrestrial WB-E-UTRAN or satellite WB-E-UTRAN or both and irrespective of whether the UE Radio Capability information of the UE is retrieved from terrestrial or satellite access eNB. The MME stores the "LTE-M Indication" in the MME context. If the UE context in MME contains the "LTE-M Indication" the MME indicates to the S-GW that the RAT type of the UE is one of the LTE-M RAT types in every Create Session Request message and every Modify Bearer Request message, so this is handled for charging and PCC purposes. The MME additionally takes into account whether the UE is accessing over terrestrial WB-E-UTRAN or satellite WB-E-UTRAN when determine the LTE-M RAT type. If the MME requests the SGW to pass LTE-M RAT type to the PDN GW, based on operator policy (e.g. based on roaming agreements or based on the need to pass the LTE-M RAT type information to PGW also), the MME informs the Serving GW that it is requested to relay the LTE-M RAT type to the PGW also. Otherwise, the Serving GW indicates WB-E-UTRAN RAT type to the PDN GW. In order to handle the situations of inter-MME change, the "LTE-M Indication" is sent from the source MME to the target MME as part of the MM Context information. The UE Radio Capability for Category M Differentiation is only applicable for MMEs, i.e. it is not applicable for SGSNs. Therefore, it will not be included during context transfers from and towards SGSNs.

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

4.15.6.13 Multi-member AF session with required QoS 4.15.6.13.1 General Descriptions

This clause describes the procedure to request QoS and to perform QoS monitoring for the traffic flows for the communication between an AF and a set of UEs, identified by the list of UE address(es). For every UE in the set, this list contains the IP address and the port number that are used by the UE for the communication with the AF. The NEF receives the request for a Multi-member AF session with required QoS for a set of UEs identified by their addresses. The NEF then maps the request for Multi-member AF session with required QoS to individual requests for AF session with required QoS (i.e., one request for individual AF session with required QoS per UE address) and interacts with each of the UE's serving PCFs on a per AF session basis. The interaction follows the AF session with required QoS procedure as described in clauses 4.15.6.6 and 4.15.6.6a, except that the involvement of the TSCTSF and the provisioning of TSCTSF related information are not supported. The NEF receives the outcome of the individual requests for AF session with required QoS corresponding to each UE's IP address and consolidates them into a single response before forwarding it to the AF based on a locally configured timer (which could be set to zero). NOTE 1: The consolidation of the outcome of the individual requests and the locally configured timer allow the optimization of the NEF to AF signalling according to the specific Multi-member AF session with required QoS. Multiple responses could be sent by an NEF (as RAN nodes may responds late or signalling messages may get lost) and the details of the NEF behaviour (e.g. handling of UE addresses for which no response has been received within the locally configured timer) are to be defined by stage 3. The AF can subscribe to QoS Monitoring (as described in clause 5.45 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]) for the Multi-member AF session with required QoS. If so, QoS monitoring will be activated by the NEF for the whole set of UEs by interacting with each of the UE's serving PCFs on a per AF session basis. If the AF request contains QoS monitoring information without an indication of direct event notification, the NEF shall include that indication in the request to ensure that QoS Monitoring reports shall be sent by the UPF directly to the NEF. The NEF forwards the QoS Monitoring reports to the AF together with the respective UE address individually or, optionally, in an aggregated manner based on a locally configured timer. When the AF subscribes to QoS Monitoring of UL and/or DL data rate (as described in clause 5.45 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]) for the set of UEs, the AF may provide a Consolidated Data Rate threshold that is to be stored in the NEF. The Consolidated Data Rate threshold defines the upper bound of the aggregated data rate across all traffic flows corresponding to the list of UE addresses of the Multi-member AF session with required QoS. The AF may provide in addition a specific list of UE addresses subject to Consolidated Data Rate monitoring (which has to be the subset of the list of UE addresses for the Multi-member AF session), if only a part of the UEs participate in the current communication with the AF and the NEF maintains this list as well. The NEF aggregates the QoS Monitoring reports for data rate for those UEs identified by the specific list of UE addresses subject to Consolidated Data Rate monitoring (if available) or otherwise by the list of UE addresses for the Multi-member AF session with required QoS. The QoS Monitoring reports for data rate will then be sent to the AF by NEF, only if the aggregated data rate exceeds the Consolidated Data Rate threshold. The following Table 4.15.6.13.1-1 describes the 4 types of requests for the Multi-member AF session with required QoS by the NEF and the corresponding requests to/from PCF using Npcf_PolicyAuthorization service. There may be different PCFs serving the PDU Sessions associated with the UE addresses in the Nnef_AFSessionWithQoS Request. Table 4.15.6.13.1-1: Mapping of requests for Multi-member AF session with required QoS service to the corresponding Npcf_PolicyAuthorization service operations NOTE 2: It is expected that the AF requests QoS and QoS monitoring for a specific traffic flow (used for the communication between a UE address and the AF) with either the procedure for Multi-member AF session with required QoS (described in this clause) or the procedure for AF session with required QoS as described in clause 4.15.6.6 and 4.15.6.6a.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.15.6.13

6.4.1.4.2 Handling of network rejection due to congestion control

If: - the 5GSM cause value #26 "insufficient resources" and the Back-off timer value IE are included in the PDU SESSION ESTABLISHMENT REJECT message; or - an indication that the 5GSM message was not forwarded due to DNN based congestion control is received along a Back-off timer value and a PDU SESSION ESTABLISHMENT REQUEST message with the PDU session ID IE set to the PDU session ID of the PDU session; the UE shall ignore the 5GSM congestion re-attempt indicator or the Re-attempt indicator IE provided by the network, if any, and the UE shall take different actions depending on the timer value received for timer T3396 in the Back-off timer value IE or depending on the Back-off timer value received from the 5GMM sublayer (if the UE is a UE configured for high priority access in selected PLMN or SNPN, exceptions are specified in subclause 6.2.7): a) If the timer value indicates neither zero nor deactivated and a DNN was provided during the PDU session establishment, the UE shall stop timer T3396 associated with the corresponding DNN, if it is running. If the timer value indicates neither zero nor deactivated and no DNN was provided during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session", the UE shall stop timer T3396 associated with no DNN if it is running. In an SNPN, the timer T3396 to be stopped includes: 1) the timer T3396 applied for all the equivalent SNPNs, and associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and 2) the timer T3396 applied for the registered SNPN, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running. The UE shall then start timer T3396 with the value provided in the Back-off timer value IE or with the Back-off timer value received from the 5GMM sublayer and: 1) shall not send another PDU SESSION ESTABLISHMENT REQUEST message or PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for the same DNN that was sent by the UE, until timer T3396 expires or timer T3396 is stopped; and 2) shall not send another PDU SESSION ESTABLISHMENT REQUEST message without a DNN and with request type different from "initial emergency request" and different from "existing emergency PDU session", or another PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for a non-emergency PDU session established without a DNN provided by the UE, if no DNN was provided during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session", until timer T3396 expires or timer T3396 is stopped. The UE shall not stop timer T3396 upon a PLMN change, SNPN change, or inter-system change; b) if the timer value indicates that this timer is deactivated and a DNN was provided during the PDU session establishment, the UE shall stop timer T3396 associated with the corresponding DNN, if it is running. If the timer value indicates that this timer is deactivated and no DNN was provided during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session", the UE shall stop timer T3396 associated with no DNN if it is running. In an SNPN, the timer T3396 to be stopped includes: 1) the timer T3396 applied for all the equivalent SNPNs, and associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and 2) the timer T3396 applied for the registered SNPN, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running. The UE: 1) shall not send another PDU SESSION ESTABLISHMENT REQUEST message or PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for the same DNN until the UE is switched off, the USIM is removed, the entry in the "list of subscriber data" for the current SNPN is updated if the UE does not support access to an SNPN using credentials from a credentials holder, or the selected entry of the "list of subscriber data" is updated if the UE supports access to an SNPN using credentials from a credentials holder, or the UE receives a PDU SESSION MODIFICATION COMMAND message for the same DNN from the network, or a PDU SESSION AUTHENTICATION COMMAND message for the same DNN from the network, or a PDU SESSION RELEASE COMMAND message without the Back-off timer value IE for the same DNN from the network; and 2) shall not send another PDU SESSION ESTABLISHMENT REQUEST message without a DNN and with request type different from "initial emergency request" and different from "existing emergency PDU session", or another PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for a non-emergency PDU session established without a DNN provided by the UE, if no DNN was provided during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session", until the UE is switched off, the USIM is removed, the entry in the "list of subscriber data" for the current SNPN is updated if the UE does not support access to an SNPN using credentials from a credentials holder, or the selected entry of the "list of subscriber data" is updated if the UE supports access to an SNPN using credentials from a credentials holder, or the UE receives a PDU SESSION MODIFICATION COMMAND message for a non-emergency PDU session established without a DNN provided by the UE, or a PDU SESSION AUTHENTICATION COMMAND message for a non-emergency PDU session established without a DNN provided by the UE, or a PDU SESSION RELEASE COMMAND message without the Back-off timer value IE for a non-emergency PDU session established without a DNN provided by the UE. The timer T3396 remains deactivated upon a PLMN change, SNPN change, or inter-system change; and c) if the timer value indicates zero, the UE: 1) shall stop timer T3396 associated with the corresponding DNN, if running. In an SNPN, the timer T3396 to be stopped includes: i) the timer T3396 applied for all the equivalent SNPNs, and associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and ii) the timer T3396 applied for the registered SNPN, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running. The UE may send another PDU SESSION ESTABLISHMENT REQUEST message or PDU SESSION MODIFICATION REQUEST message for the same DNN; and 2) if no DNN was provided during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session", the UE shall stop timer T3396 associated with no DNN, if running. In an SNPN, the timer T3396 to be stopped includes: i) the timer T3396 applied for all the equivalent SNPNs, and associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and ii) the timer T3396 applied for the registered SNPN, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running. The UE may send another PDU SESSION ESTABLISHMENT REQUEST message without a DNN, or another PDU SESSION MODIFICATION REQUEST message without a DNN provided by the UE. In an SNPN, if the UE supports equivalent SNPNs, then the UE shall apply the timer T3396 for all the equivalent SNPNs. Otherwise, the UE shall apply the timer T3396 for the registered SNPN. If the Back-off timer value IE is not included or no Back-off timer value is received from the 5GMM sublayer, then the UE may send another PDU SESSION ESTABLISHMENT REQUEST message or PDU SESSION MODIFICATION REQUEST message for the same DNN or without a DNN. When the timer T3396 is running or the timer is deactivated, the UE is allowed to initiate a PDU session establishment procedure for emergency services. If the timer T3396 is running when the UE enters state 5GMM-DEREGISTERED, the UE remains switched on, and the USIM in the UE (if any) remains the same and the entry in the "list of subscriber data" to which timer T3396 is associated (if any) is not updated, then timer T3396 is kept running until it expires or it is stopped. If the UE is switched off when the timer T3396 is running, and if the USIM in the UE (if any) remains the same and the entry in the "list of subscriber data" to which timer T3396 is associated (if any) is not updated when the UE is switched on, the UE shall behave as follows: - let t1 be the time remaining for T3396 timeout at switch off and let t be the time elapsed between switch off and switch on. If t1 is greater than t, then the timer shall be restarted with the value t1 – t. If t1 is equal to or less than t, then the timer need not be restarted. If the UE is not capable of determining t, then the UE shall restart the timer with the value t1. If: - the 5GSM cause value #67 "insufficient resources for specific slice and DNN" and the Back-off timer value IE are included in the PDU SESSION ESTABLISHMENT REJECT message; or - an indication that the 5GSM message was not forwarded due to S-NSSAI and DNN based congestion control is received along a Back-off timer value and a PDU SESSION ESTABLISHMENT REQUEST message with the PDU session ID IE set to the PDU session ID of the PDU session; the UE shall ignore the Re-attempt indicator IE provided by the network, if any, and take different actions depending on the timer value received for timer T3584 in the Back-off timer value IE or depending on the Back-off timer value received from the 5GMM sublayer (if the UE is a UE configured for high priority access in selected PLMN or SNPN, exceptions are specified in subclause 6.2.8): a) If the timer value indicates neither zero nor deactivated, the UE shall stop timer T3584 associated with the same [S-NSSAI, DNN] combination as that the UE provided during the PDU session establishment, if it is running. If the timer value indicates neither zero nor deactivated and no DNN was provided during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session", the UE shall stop timer T3584 associated with [S-NSSAI, no DNN] combination as that the UE provided during the PDU session establishment, if it is running. If the timer value indicates neither zero nor deactivated and no S-NSSAI was provided during the PDU session establishment, the UE shall stop timer T3584 associated with [no S-NSSAI, DNN] combination as that the UE provided during the PDU session establishment, if it is running. If the timer value indicates neither zero nor deactivated and neither S-NSSAI nor DNN was provided during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session", the UE shall stop timer T3584 associated with [no S-NSSAI, no DNN] combination as that the UE provided during the PDU session establishment, if it is running. The timer T3584 to be stopped includes: 1) in a PLMN: i) the timer T3584 applied for all the PLMNs, if running; and ii) the timer T3584 applied for the registered PLMN, if running; or 2) in an SNPN: i) the timer T3584 applied for all the equivalent SNPNs, and associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and ii) the timer T3584 applied for the registered SNPN, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running. The UE shall then start timer T3584 with the value provided in the Back-off timer value IE or with the Back-off timer value received from the 5GMM sublayer and: 1) shall not send another PDU SESSION ESTABLISHMENT REQUEST message, or PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for the same [S-NSSAI, DNN] combination that was sent by the UE, until timer T3584 expires or timer T3584 is stopped; 2) shall not send another PDU SESSION ESTABLISHMENT REQUEST message with request type different from "initial emergency request" and different from "existing emergency PDU session", or another PDU SESSION MODIFICATION REQUEST with exception of those identified in subclause 6.4.2.1, message for the same [S-NSSAI, no DNN] combination that was sent by the UE, if no DNN was provided during the PDU session establishment, until timer T3584 expires or timer T3584 is stopped; 3) shall not send another PDU SESSION ESTABLISHMENT REQUEST message, or another PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for the same [no S-NSSAI, DNN] combination that was sent by the UE, if no S-NSSAI was provided during the PDU session establishment, until timer T3584 expires or timer T3584 is stopped; and 4) shall not send another PDU SESSION ESTABLISHMENT REQUEST message with request type different from "initial emergency request" and different from "existing emergency PDU session", or another PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for the same [no S-NSSAI, no DNN] combination that was sent by the UE, if neither S-NSSAI nor DNN was provided during the PDU session establishment, until timer T3584 expires or timer T3584 is stopped. The UE shall not stop timer T3584 upon a PLMN change, SNPN change, or inter-system change; b) if the timer value indicates that this timer is deactivated, the UE: 1) shall stop timer T3584 associated with the same [S-NSSAI, DNN] combination as that the UE provided during the PDU session establishment, if running. The timer T3584 to be stopped includes: i) in a PLMN: A) the timer T3584 applied for all the PLMNs, if running; and B) the timer T3584 applied for the registered PLMN, if running; or ii) in an SNPN: A) the timer T3584 applied for all the equivalent SNPNs, and associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and B) the timer T3584 applied for the registered SNPN, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running. The UE shall not send another PDU SESSION ESTABLISHMENT REQUEST message, or PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for the same [S-NSSAI, DNN] combination that was sent by the UE, until the UE is switched off, the USIM is removed, the entry in the "list of subscriber data" for the current SNPN is updated if the UE does not support access to an SNPN using credentials from a credentials holder, or the selected entry of the "list of subscriber data" is updated if the UE supports access to an SNPN using credentials from a credentials holder, or the UE receives a PDU SESSION MODIFICATION COMMAND message for the same [S-NSSAI, DNN] combination from the network, or a PDU SESSION AUTHENTICATION COMMAND message for the same [S-NSSAI, DNN] combination from the network, or a PDU SESSION RELEASE COMMAND message without the Back-off timer value IE for the same [S-NSSAI, DNN] combination from the network; 2) shall stop timer T3584 associated with the same [S-NSSAI, no DNN] combination as that the UE provided during the PDU session establishment, if running. The timer T3584 to be stopped includes: i) in a PLMN: A) the timer T3584 applied for all the PLMNs, if running; and B) the timer T3584 applied for the registered PLMN, if running; or ii) in an SNPN: A) the timer T3584 applied for all the equivalent SNPNs, and associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and B) the timer T3584 applied for the registered SNPN, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running. The UE shall not send a PDU SESSION ESTABLISHMENT REQUEST message with request type different from "initial emergency request" and different from "existing emergency PDU session", or a PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for the same [S-NSSAI, no DNN] combination that was sent by the UE, if no DNN was provided during the PDU session establishment, until the UE is switched off, the USIM is removed, the entry in the "list of subscriber data" for the current SNPN is updated if the UE does not support access to an SNPN using credentials from a credentials holder, or the selected entry of the "list of subscriber data" if the UE supports access to an SNPN using credentials from a credentials holder, or the UE receives an PDU SESSION MODIFICATION COMMAND message for a non-emergency PDU session established for the same [S-NSSAI, no DNN] combination from the network, or a PDU SESSION AUTHENTICATION COMMAND message for a non-emergency PDU session established for the same [S-NSSAI, DNN] combination from the network, or a PDU SESSION RELEASE COMMAND message without the Back-off timer value IE for a non-emergency PDU session established for the same [S-NSSAI, no DNN] combination from the network; 3) shall stop timer T3584 associated with the same [no S-NSSAI, DNN] combination as that the UE provided during the PDU session establishment, if running. The timer T3584 to be stopped includes: i) in a PLMN: A) the timer T3584 applied for all the PLMNs, if running; and B) the timer T3584 applied for the registered PLMN, if running; or ii) in an SNPN: A) the timer T3584 applied for all the equivalent SNPNs, and associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and B) the timer T3584 applied for the registered SNPN, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running. The UE shall not send a PDU SESSION ESTABLISHMENT REQUEST message, or a PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for the same [no S-NSSAI, DNN] combination that was sent by the UE, if no S-NSSAI was provided during the PDU session establishment, until the UE is switched off, the USIM is removed, the entry in the "list of subscriber data" for the current SNPN is updated, or the UE receives a PDU SESSION MODIFICATION COMMAND message for the same [no S-NSSAI, DNN] combination from the network, or a PDU SESSION AUTHENTICATION COMMAND message for a non-emergency PDU session established for the same [no S-NSSAI, no DNN] combination from the network, or a PDU SESSION RELEASE COMMAND message without the Back-off timer value IE for the same [no S-NSSAI, DNN] combination from the network; and 4) shall stop timer T3584 associated with the same [no S-NSSAI, no DNN] combination as that the UE provided during the PDU session establishment , if running. The timer T3584 to be stopped includes: i) in a PLMN: A) the timer T3584 applied for all the PLMNs, if running; and B) the timer T3584 applied for the registered PLMN, if running; or ii) in an SNPN: A) the timer T3584 applied for all the equivalent SNPNs, and associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and B) the timer T3584 applied for the registered SNPN, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running. The UE shall not send a PDU SESSION ESTABLISHMENT REQUEST message with request type different from "initial emergency request" and different from "existing emergency PDU session", or a PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for the same [no S-NSSAI, no DNN] combination that was sent by the UE, if neither S-NSSAI nor DNN was provided during the PDU session establishment, until the UE is switched off, the USIM is removed, the entry in the "list of subscriber data" for the current SNPN is updated if the UE does not support access to an SNPN using credentials from a credentials holder, or the selected entry of the "list of subscriber data" is updated if the UE supports access to an SNPN using credentials from a credentials holder, or the UE receives an PDU SESSION MODIFICATION COMMAND message for a non-emergency PDU session established for the same [no S-NSSAI, no DNN] combination from the network or a PDU SESSION RELEASE COMMAND message without the Back-off timer value IE for a non-emergency PDU session established for the same [no S-NSSAI, no DNN] combination from the network. The timer T3584 remains deactivated upon a PLMN change, SNPN change, or inter-system change; and c) if the timer value indicates zero, the UE: 1) shall stop timer T3584 associated with the same [S-NSSAI, DNN] combination as that the UE provided during the PDU session establishment, if running. The timer T3584 to be stopped includes: i) in a PLMN: A) the timer T3584 applied for all the PLMNs, if running; and B) the timer T3584 applied for the registered PLMN, if running; or ii) in an SNPN: A) the timer T3584 applied for all the equivalent SNPNs, and associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and B) the timer T3584 applied for the registered SNPN, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running. The UE may send another PDU SESSION ESTABLISHMENT REQUEST message or PDU SESSION MODIFICATION REQUEST message for the same [S-NSSAI, DNN] combination; 2) shall stop timer T3584 associated with the same [S-NSSAI, no DNN] combination as that the UE provided during the PDU session establishment, if running. The timer T3584 to be stopped includes: i) in a PLMN: A) the timer T3584 applied for all the PLMNs, if running; and B) the timer T3584 applied for the registered PLMN, if running; or ii) in an SNPN: A) the timer T3584 applied for all the equivalent SNPNs, and associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and B) the timer T3584 applied for the registered SNPN, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running. The UE may send another PDU SESSION ESTABLISHMENT REQUEST message or PDU SESSION MODIFICATION REQUEST message for the same [S-NSSAI, no DNN] combination if no DNN was provided during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session"; 3) shall stop timer T3584 associated with the same [no S-NSSAI, DNN] combination as that the UE provided during the PDU session establishment, if running. The timer T3584 to be stopped includes: i) in a PLMN: A) the timer T3584 applied for all the PLMNs, if running; and B) the timer T3584 applied for the registered PLMN, if running; or ii) in an SNPN: A) the timer T3584 applied for all the equivalent SNPNs, and associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and B) the timer T3584 applied for the registered SNPN, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running. The UE may send another PDU SESSION ESTABLISHMENT REQUEST message, or PDU SESSION MODIFICATION REQUEST message for the same [no S-NSSAI, DNN] combination if no NSSAI was provided during the PDU session establishment; and 4) shall stop timer T3584 associated with the same [no S-NSSAI, no DNN] combination as that the UE provided during the PDU session establishment, if running. The timer T3584 to be stopped includes: i) in a PLMN: A) the timer T3584 applied for all the PLMNs, if running; and B) the timer T3584 applied for the registered PLMN, if running; or ii) in an SNPN: A) the timer T3584 applied for all the equivalent SNPNs, and associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and B) the timer T3584 applied for the registered SNPN, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running. The UE may send another PDU SESSION ESTABLISHMENT REQUEST message, or PDU SESSION MODIFICATION REQUEST message for the same [no S-NSSAI, no DNN] combination if neither S-NSSAI nor DNN was provided during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session". If the 5GSM congestion re-attempt indicator IE with the ABO bit set to "The back-off timer is applied in all PLMNs or all equivalent SNPNs " is included in the PDU SESSION ESTABLISHMENT REJECT message with the 5GSM cause value #67 "insufficient resources for specific slice and DNN", then the UE shall apply the timer T3584 for all the PLMNs or all the equivalent SNPNs. Otherwise, the UE shall apply the timer T3584 for the registered PLMN. If the Back-off timer value IE is not included or no Back-off timer value is received from the 5GMM sublayer, then the UE may send another PDU SESSION ESTABLISHMENT REQUEST message or PDU SESSION MODIFICATION REQUEST message for the same [S-NSSAI, DNN] combination, or for the same [S-NSSAI, no DNN] combination, or for the same [no S-NSSAI, DNN] combination, or for the same [no S-NSSAI, no DNN] combination. When the timer T3584 is running or the timer is deactivated, the UE is allowed to initiate a PDU session establishment procedure for emergency services. If the timer T3584 is running when the UE enters state 5GMM-DEREGISTERED, the UE remains switched on, and the USIM in the UE (if any) remains the same and the entry in the "list of subscriber data" to which timer T3584 is associated (if any) is not updated, then timer T3584 is kept running until it expires or it is stopped. If the UE is switched off when the timer T3584 is running, and if the USIM in the UE (if any) remains the same and the entry in the "list of subscriber data" to which timer T3584 is associated (if any) is not updated when the UE is switched on, the UE shall behave as follows: - let t1 be the time remaining for T3584 timeout at switch off and let t be the time elapsed between switch off and switch on. If t1 is greater than t, then the timer shall be restarted with the value t1 – t. If t1 is equal to or less than t, then the timer need not be restarted. If the UE is not capable of determining t, then the UE shall restart the timer with the value t1. If: - the 5GSM cause value #69 "insufficient resources for specific slice" and the Back-off timer value IE are included in the PDU SESSION ESTABLISHMENT REJECT message; or - an indication that the 5GSM message was not forwarded due to S-NSSAI only based congestion control is received along a Back-off timer value and a PDU SESSION ESTABLISHMENT REQUEST message with the PDU session ID IE set to the PDU session ID of the PDU session; the UE shall ignore the Re-attempt indicator IE provided by the network, if any, and take different actions depending on the timer value received for timer T3585 in the Back-off timer value IE or depending on the Back-off timer value received from the 5GMM sublayer (if the UE is a UE configured for high priority access in selected PLMN or SNPN, exceptions are specified in subclause 6.2.8): a) If the timer value indicates neither zero nor deactivated and an S-NSSAI was provided during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session", the UE shall stop timer T3585 associated with the corresponding S-NSSAI, if it is running. If the timer value indicates neither zero nor deactivated and no S-NSSAI was provided during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session", the UE shall stop timer T3585 associated with no S-NSSAI if it is running. The timer T3585 to be stopped includes: 1) in a PLMN: i)- the timer T3585 applied for all the PLMNs and for the access over which the PDU SESSION ESTABLISHMENT REJECT is received, if running; ii) the timer T3585 applied for all the PLMNs and for both 3GPP access type and non-3GPP access type, if running; iii) the timer T3585 applied for the registered PLMN and for the access over which the PDU SESSION ESTABLISHMENT REJECT is received, if running; and iv) the timer T3585 applied for the registered PLMN and for both 3GPP access type and non-3GPP access type, if running; or 2) in an SNPN: i) the timer T3585 applied for all the equivalent SNPNs and for the access over which the PDU SESSION AUTHENTICATION COMMAND message is received, associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; ii) the timer T3585 applied for all the equivalent SNPNs and for both 3GPP access type and non-3GPP access type, associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; iii) the timer T3585 applied for the registered SNPN and for the access over which the PDU SESSION AUTHENTICATION COMMAND message is received, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and iv) the timer T3585 applied for the registered PLMN and for both 3GPP access type and non-3GPP access type, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running. The UE shall then start timer T3585 with the value provided in the Back-off timer value IE or with the Back-off timer value received from the 5GMM sublayer and: 1) shall not send another PDU SESSION ESTABLISHMENT REQUEST message with request type different from "initial emergency request" and different from "existing emergency PDU session", or another PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for a non-emergency PDU session for the same S-NSSAI that was sent by the UE, until timer T3585 expires or timer T3585 is stopped; and 2) shall not send another PDU SESSION ESTABLISHMENT REQUEST message without an S-NSSAI and with request type different from "initial emergency request" and different from "existing emergency PDU session", or another PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for a non-emergency PDU session established without an S-NSSAI provided by the UE, if no S-NSSAI was provided during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session", until timer T3585 expires or timer T3585 is stopped. The UE shall not stop timer T3585 upon a PLMN change, SNPN change, or inter-system change; b) if the timer value indicates that this timer is deactivated and an S-NSSAI was provided during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session", the UE shall stop timer T3585 associated with the corresponding S-NSSAI, if it is running. If the timer value indicates that this timer is deactivated and no S-NSSAI was provided during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session", the UE shall stop timer T3585 associated with no S-NSSAI if it is running. The timer T3585 to be stopped includes: 1) in a PLMN: i) the timer T3585 applied for all the PLMNs and for the access over which the PDU SESSION ESTABLISHMENT REJECT is received, if running; ii) the timer T3585 applied for all the PLMNs and for both 3GPP access type and non-3GPP access type, if running; iii) the timer T3585 applied for the registered PLMN and for the access over which the PDU SESSION ESTABLISHMENT REJECT is received, if running; and iv) the timer T3585 applied for the registered PLMN and for both 3GPP access type and non-3GPP access type, if running; or 2) in an SNPN: i) the timer T3585 applied for all the equivalent SNPNs and for the access over which the PDU SESSION AUTHENTICATION COMMAND message is received, associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; ii) the timer T3585 applied for all the equivalent SNPNs and for both 3GPP access type and non-3GPP access type, associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; iii) the timer T3585 applied for the registered SNPN and for the access over which the PDU SESSION AUTHENTICATION COMMAND message is received, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and iv) the timer T3585 applied for the registered PLMN and for both 3GPP access type and non-3GPP access type, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running. The UE: 1) shall not send another PDU SESSION ESTABLISHMENT REQUEST message with request type different from "initial emergency request" and different from "existing emergency PDU session", or another PDU SESSION MODIFICATION REQUEST with exception of those identified in subclause 6.4.2.1, for a non-emergency PDU session for the same S-NSSAI until the UE is switched off, the USIM is removed, the entry in the "list of subscriber data" for the current SNPN is updated if the UE does not support access to an SNPN using credentials from a credentials holder, or the selected entry of the "list of subscriber data" is updated if the UE supports access to an SNPN using credentials from a credentials holder, or the UE receives a PDU SESSION MODIFICATION COMMAND message for a non-emergency PDU session for the same S-NSSAI from the network, or a PDU SESSION AUTHENTICATION COMMAND message for a non-emergency PDU session for the same S-NSSAI from the network, or a PDU SESSION RELEASE COMMAND message without the Back-off timer value IE for the same S-NSSAI from the network; and 2) shall not send another PDU SESSION ESTABLISHMENT REQUEST message without an S-NSSAI and with request type different from "initial emergency request" and different from "existing emergency PDU session", or another PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for a non-emergency PDU session established without an S-NSSAI provided by the UE, if no S-NSSAI was provided during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session", until the UE is switched off, the USIM is removed, the entry in the "list of subscriber data" for the current SNPN is updated if the UE does not support access to an SNPN using credentials from a credentials holder, or the selected entry of the "list of subscriber data" is updated if the UE supports access to an SNPN using credentials from a credentials holder, or the UE receives a PDU SESSION MODIFICATION COMMAND message for a non-emergency PDU session established without an S-NSSAI provided by the UE, or a PDU SESSION AUTHENTICATION COMMAND message for a non-emergency PDU session established without an S-NSSAI provided by the UE, or a PDU SESSION RELEASE COMMAND message without the Back-off timer value IE for a non-emergency PDU session established without an S-NSSAI provided by the UE. The timer T3585 remains deactivated upon a PLMN change, SNPN change, or inter-system change; and c) if the timer value indicates zero, the UE: 1) shall stop timer T3585 associated with the corresponding S-NSSAI, if running. The timer T3585 to be stopped includes: i) in a PLMN: A) the timer T3585 applied for all the PLMNs and for the access over which the PDU SESSION RELEASE COMMAND is received, if running; B) the timer T3585 applied for all the PLMNs and for the access over which the PDU SESSION RELEASE COMMAND is received, if running; C) the timer T3585 applied for the registered PLMN and for current access type or both 3GPP access type and non-3GPP access type, if running; and D) the timer T3585 applied for the registered PLMN and for both 3GPP access type and non-3GPP access type, if running; or ii) in an SNPN: A) the timer T3585 applied for all the equivalent SNPNs and for the access over which the PDU SESSION AUTHENTICATION COMMAND message is received, associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; B) the timer T3585 applied for all the equivalent SNPNs and for both 3GPP access type and non-3GPP access type, associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; C) the timer T3585 applied for the registered SNPN and for the access over which the PDU SESSION AUTHENTICATION COMMAND message is received, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and D) the timer T3585 applied for the registered PLMN and for both 3GPP access type and non-3GPP access type, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running. The UE may send another PDU SESSION ESTABLISHMENT REQUEST message or PDU SESSION MODIFICATION REQUEST message for the same S-NSSAI; and 2) if no S-NSSAI was provided during the PDU session establishment and the request type was different from "initial emergency request " and different from "existing emergency PDU session", the UE shall stop timer T3585 associated with no S-NSSAI, if running. The timer T3585 to be stopped includes: i) in a PLMN: A) the timer T3585 applied for all the PLMNs and for the access over which the PDU SESSION RELEASE COMMAND is received, if running; B) the timer T3585 applied for all the PLMNs and for the access over which the PDU SESSION RELEASE COMMAND is received, if running; C) the timer T3585 applied for the registered PLMN and for current access type or both 3GPP access type and non-3GPP access type, if running; and D) the timer T3585 applied for the registered PLMN and for both 3GPP access type and non-3GPP access type, if running; or ii) in an SNPN: A) the timer T3585 applied for all the equivalent SNPNs and for the access over which the PDU SESSION AUTHENTICATION COMMAND message is received, associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; B) the timer T3585 applied for all the equivalent SNPNs and for both 3GPP access type and non-3GPP access type, associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; C) the timer T3585 applied for the registered SNPN and for the access over which the PDU SESSION AUTHENTICATION COMMAND message is received, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and D) the timer T3585 applied for the registered PLMN and for both 3GPP access type and non-3GPP access type, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running. The UE may send another PDU SESSION ESTABLISHMENT REQUEST message without an S-NSSAI, or another PDU SESSION MODIFICATION REQUEST message without an S-NSSAI provided by the UE. If the 5GSM congestion re-attempt indicator IE with the ABO bit set to "The back-off timer is applied in all PLMNs or equivalent SNPNs " is included in the PDU SESSION ESTABLISHMENT REJECT message with the 5GSM cause value #69 "insufficient resources for specific slice", then the UE shall apply the timer T3585 for all the PLMNs or all the equivalent SNPNs. Otherwise, the UE shall apply the timer T3585 for the registered PLMN or the registered SNPN. Additionally, if the 5GSM congestion re-attempt indicator IE with the CATBO bit set to "The back-off timer is applied in the current access type" is included in the PDU SESSION ESTABLISHMENT REJECT message with the 5GSM cause value #69 "insufficient resources for specific slice", then the UE shall apply the timer T3585 for the current access type. Otherwise, the UE shall apply the timer T3585 for both 3GPP access type and non-3GPP access type and the UE shall stop any running timer T3585 for the applied PLMN or SNPN and for the access different from the access from which the PDU SESSION ESTABLISHMENT REJECT message is received. If the Back-off timer value IE is not included or no Back-off timer value is received from the 5GMM sublayer, then the UE may send another PDU SESSION ESTABLISHMENT REQUEST message or PDU SESSION MODIFICATION REQUEST message for the same S-NSSAI or without an S-NSSAI. When the timer T3585 is running or the timer is deactivated, the UE is allowed to initiate a PDU session establishment procedure for emergency services. If the timer T3585 is running when the UE enters state 5GMM-DEREGISTERED, the UE remains switched on, and the USIM in the UE (if any) remains the same and the entry in the "list of subscriber data" to which timer T3585 is associated (if any) is not updated, then timer T3585 is kept running until it expires or it is stopped. If the UE is switched off when the timer T3585 is running, and if the USIM in the UE (if any) remains the same and the entry in the "list of subscriber data" to which timer T3585 is associated (if any) is not updated when the UE is switched on, the UE shall behave as follows: let t1 be the time remaining for T3585 timeout at switch off and let t be the time elapsed between switch off and switch on. If t1 is greater than t, then the timer shall be restarted with the value t1 – t. If t1 is equal to or less than t, then the timer need not be restarted. If the UE is not capable of determining t, then the UE shall restart the timer with the value t1. NOTE: As described in this subclause, upon PLMN change, SNPN change or inter-system change, the UE does not stop the timer T3584 or T3585. This means the timer T3584 or T3585 can still be running or be deactivated for the given 5GSM procedure, the PLMN or SNPN, the S-NSSAI and optionally the DNN combination when the UE returns to the PLMN or SNPN or when it performs inter-system change back from S1 mode to N1 mode. Thus the UE can still be prevented from sending another PDU SESSION ESTABLISHMENT REQUEST or PDU SESSION MODIFICATION REQUEST message in the PLMN or SNPN for the same S-NSSAI and optionally the same DNN. Upon PLMN change or SNPN change, if T3584 applied for the registered PLMN or the registered SNPN is running or is deactivated for an S-NSSAI, a DNN, and old PLMN or old SNPN, but T3584 is not running and is not deactivated for the S-NSSAI, the DNN, and new PLMN or new SNPN, then the UE is allowed to send a PDU SESSION ESTABLISHMENT REQUEST message for the same S-NSSAI and the same DNN in the new PLMN or new SNPN. Upon PLMN change or SNPN change, if T3585 applied for the registered PLMN or the registered SNPN is running or is deactivated for an S-NSSAI and old PLMN or old SNPN, but T3585 is not running and is not deactivated for the S-NSSAI and new PLMN or new SNPN, then the UE is allowed to send a PDU SESSION ESTABLISHMENT REQUEST message for the same S-NSSAI in the new PLMN or new SNPN. Upon SNPN change, if T3585 applied for all the equivalent SNPNs is running or is deactivated for an S-NSSAI and old SNPN, but T3585 is not running and is not deactivated for the S-NSSAI and new non-equivalent SNPN, then the UE is allowed to send a PDU SESSION ESTABLISHMENT REQUEST message for the same S-NSSAI in the new SNPN.

3GPP TS 24.501

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

CT WG1

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

6.4.1.4.2

4.11.4 Support for enhanced discontinuous coverage

If the UE and network support enhanced discontinuous coverage, the UE may provide unavailability information to the network in the tracking area updating procedure if the UE is registered over satellite E-UTRAN access (see 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10]). The unavailability information includes the unavailability period duration if known, and the start of the unavailability period if known. The support for the enhanced discontinuous coverage is negotiated in the attach procedure or the tracking area updating procedure. The MME may consider the unavailability period duration if provided by the UE to determine the unavailability period duration of the UE. The MME may provide the unavailability period duration to the UE in the TRACKING AREA UPDATE ACCEPT message. The MME may consider the unavailability period duration if provided by the UE to determine the unavailability period duration of the UE. If the UE provided unavailability information in the last tracking area updating procedure, the MME considers the UE unreachable until the UE registers for normal service without providing unavailability information. If the UE did not include a start of the unavailability period, the MME shall consider the start of the unavailability period to be the time at which MME received the TRACKING AREA UPDATE REQUEST message to the UE. The MME may determine the value of the periodic tracking area update timer (T3412) provided to the UE based on the unavailability period duration and the start of the unavailability period, if available. The MME releases the NAS signalling connection after the completion of the attach procedure or the tracking area updating procedure in which the UE provided unavailability information. If for discontinuous coverage the UE has stored a discontinuous coverage maximum time offset, upon returning in coverage after being out of coverage due to discontinuous coverage, the UE sets the discontinuous coverage maximum time offset value to a random value up to and including the stored discontinuous coverage maximum time offset for this PLMN and satellite E-UTRAN access and starts this timer. The UE shall not initiate any NAS signalling on that satellite E-UTRAN access and PLMN combination while the discontinuous coverage maximum time offset timer is running. The UE shall stop the discontinuous coverage maximum time offset timer and initiate NAS signalling if the UE receives a paging message, has pending emergency services, is establishing an emergency PDN connection, is performing emergency services fallback procedure or when the UE enters a new tracking area. When the unavailability period is activated, all NAS timers are stopped and associated procedures aborted except for timers T3412, T3346, T3447, T3396, any back-off timers, T3247, and the timer T controlling the periodic search for HPLMN or EHPLMN or higher prioritized PLMNs (see 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]). When the UE provides unavailability information using the tracking area updating procedure without providing the start of the unavailability period, then after successful completion of the procedure the UE may deactivate the access stratum and enter the state EMM-REGISTERED.NO-CELL-AVAILABLE. Otherwise, if the UE provided the start of unavailability period, the UE may deactivate the access stratum and enter the state EMM-REGISTERED.NO-CELL-AVAILABLE only after the start of the unavailability period.

3GPP TS 24.301

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

CT WG1

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

4.11.4

5.19.7 NAS level congestion control 5.19.7.1 General

NAS level congestion control may be applied in general (i.e. for all NAS messages), per DNN, per S-NSSAI, per DNN and S-NSSAI, or for a specific group of UEs. NAS level congestion control is achieved by providing the UE a back-off time. To avoid that large amounts of UEs initiate deferred requests (almost) simultaneously, the 5GC should select each back-off time value so that the deferred requests are not synchronized. When the UE receives a back-off time, the UE shall not initiate any NAS signalling with regards to the applied congestion control until the back-off timer expires or the UE receives a mobile terminated request from the network, or the UE initiates signalling for emergency services or high priority access. AMFs and SMFs may apply NAS level congestion control, but should not apply NAS level congestion control for procedures not subject to congestion control.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.19.7

9.2 CQI reporting definition under AWGN conditions

The reporting accuracy of the channel quality indicator (CQI) under frequency non-selective conditions is determined by the reporting variance and the BLER performance using the transport format indicated by the reported CQI median. The purpose is to verify that the reported CQI values are in accordance with the CQI definition given in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [6]. To account for sensitivity of the input SNR the reporting definition 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.2

5.5.1.2.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 initial registration unless: 1) the UE is a UE configured for high priority access in selected PLMN or SNPN; 2) the UE needs to perform the registration procedure for initial registration for emergency services; 3) the UE receives a DEREGISTRATION REQUEST message with the "re-registration required" indication; 4) 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 5) the UE needs to perform the registration procedure with 5GS registration type IE set to "initial registration" for initiating of an emergency PDU session, upon request of the upper layers to establish the emergency PDU session. 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 initial registration while timer T3346 is running independent on whether timer T3346 was started due to an abnormal case or a non-successful case. b) The lower layers indicate that the access attempt is barred. The UE shall not start the initial registration procedure. 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 initial registration procedure 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 initial registration 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. c) T3510 timeout. The UE shall abort the registration procedure for initial registration and the NAS signalling connection, if any, shall be released locally if the initial registration request is neither for emergency services nor for initiating a PDU session for emergency services with request type set to "existing emergency PDU session". The UE shall proceed as described below. d) REGISTRATION REJECT message, other 5GMM cause values than those treated in subclause 5.5.1.2.5, and cases of 5GMM cause values #10, #11, #15, #22, #31, #72, #73, #74, #75, #76, #77 and #78, if considered as abnormal cases according to subclause 5.5.1.2.5. If the registration request is neither an initial registration request for emergency services nor an initial registration request for initiating a PDU session for emergency services with request type set to "existing emergency PDU session", 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 or release of the NAS signalling connection received from lower layers before the REGISTRATION ACCEPT or REGISTRATION REJECT message is received. The UE shall abort the registration procedure for initial registration and proceed as described below. f) UE initiated de-registration required. The registration procedure for initial registration shall be aborted, and the UE initiated de-registration procedure shall be performed. g) De-registration procedure collision. If the UE receives a DEREGISTRATION REQUEST message from the network in state 5GMM-REGISTERED-INITIATED the de-registration procedure shall be aborted and the initial registration procedure shall be progressed. NOTE 2: The above collision case is valid if the DEREGISTRATION REQUEST message indicates the access type over which the initial registration procedure is attempted otherwise both the procedures are progressed. h) Change in the current TAI. If the current TAI is changed before the registration procedure for initial registration is completed, the registration procedure for initial registration shall be aborted and re-initiated immediately. If the REGISTRATION COMPLETE message needs to be sent and a tracking area border is crossed when the REGISTRATION ACCEPT message has been received but before a REGISTRATION COMPLETE message is sent and: 1) if the current TAI is in the TAI list, the UE sends the REGISTRATION COMPLETE message to the network; and 2) otherwise, the registration procedure for initial registration shall be aborted and the registration procedure for mobility registration update shall be initiated. If a 5G-GUTI was allocated during the registration procedure, this 5G-GUTI shall be used in the registration procedure. i) Transmission failure of REGISTRATION COMPLETE message indication with change in the current TAI. 1) If the current TAI is still part of the TAI list, the UE resends the REGISTRATION COMPLETE message to the network; and 2) otherwise, the registration procedure for initial registration shall be aborted and the registration procedure for mobility registration update shall be initiated. j) Transmission failure of REGISTRATION COMPLETE message indication without change in the current TAI from lower layers. It is up to the UE implementation how to re-run the ongoing procedure. k) Transmission failure of REGISTRATION REQUEST message indication from the lower layers. The registration procedure for initial registration shall be aborted and re-initiated immediately. l) Timer T3447 is running. The UE shall not start the registration procedure for initial registration 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; or 2) the UE needs to perform the registration procedure for initial registration for emergency services. The UE stays in the current serving cell and applies the normal cell reselection process. The registration procedure for initial registration is started, if still necessary, when timer T3447 expires or timer T3447 is stopped. m) 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. n) Access for localized services in current SNPN is no longer allowed. If the initial registration request is neither for emergency services nor for initiating a PDU session for emergency services with request type set to "existing emergency PDU session", the selected 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: 1) access for localized services in SNPN is disabled; or 2) 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 initial registration, locally release the NAS signalling connection, if any, and enter state 5GMM-DEREGISTERED.LIMITED-SERVICE or 5GMM-DEREGISTERED.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 neither an initial registration for emergency services nor for establishing an emergency PDU session with registration type not set to "emergency registration", 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 initial registration request is not for emergency services, timer T3511 is started and the state is changed to 5GMM-DEREGISTERED.ATTEMPTING-REGISTRATION. When timer T3511 expires the registration procedure for initial registration shall be restarted, if still required. If the registration attempt counter is equal to 5 - the UE shall delete TAI list and last visited registered TAI, start timer T3502 if the value of the timer as indicated by the network is not zero and shall set the 5GS update status to 5U2 NOT UPDATED. If the UE is not registering or has not registered to the same PLMN over both 3GPP access and non-3GPP access, the UE shall additionally delete 5G-GUTI, ngKSI and list of equivalent PLMNs (if any) or list of equivalent SNPNs (if any). The state is changed to 5GMM-DEREGISTERED.ATTEMPTING-REGISTRATION or optionally to 5GMM-DEREGISTERED.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. - if the procedure is performed via 3GPP access and the UE is operating in single-registration mode: - the UE shall in addition handle the EMM parameters EPS update status, EMM state, 4G-GUTI, TAI list, last visited registered TAI, list of equivalent PLMNs and eKSI 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 an EPS attach procedure fails and the attach attempt counter is equal to 5; and - the UE shall attempt to select E-UTRAN radio access technology and proceed with appropriate EMM specific procedures. Additionally, 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.2.7

4.3.1 Non-roaming architecture

Figure 4.3.1-1 represents the non-roaming architecture for interworking between 5GS and EPC/E-UTRAN. Figure 4.3.1-1: Non-roaming architecture for interworking between 5GS and EPC/E-UTRAN NOTE 1: N26 interface is an inter-CN interface between the MME and 5GS AMF in order to enable interworking between EPC and the NG core. Support of N26 interface in the network is optional for interworking. N26 supports subset of the functionalities (essential for interworking) that are supported over S10. NOTE 2: PGW-C + SMF and UPF + PGW-U are dedicated for interworking between 5GS and EPC, which are optional and are based on UE MM Core Network Capability and UE subscription. UEs that are not subject to 5GS and EPC interworking may be served by entities not dedicated for interworking, i.e. by either by PGW or SMF/UPF. NOTE 3: There can be another UPF (not shown in the figure above) between the NG-RAN and the UPF + PGW-U, i.e. the UPF + PGW-U can support N9 towards an additional UPF, if needed. NOTE 4: Figures and procedures in this specification that depict an SGW make no assumption whether the SGW is deployed as a monolithic SGW or as an SGW split into its control-plane and user-plane functionality as described in TS 23.214[ Architecture enhancements for control and user plane separation of EPC nodes ] [32].

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

4.3.1

9.2.4.1 FDD

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

3GPP TS 36.101

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

RAN4

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

9.2.4.1

– PosSystemInformation-r16-IEs

-- ASN1START -- TAG-POSSYSTEMINFORMATION-R16-IES-START PosSystemInformation-r16-IEs ::= SEQUENCE { posSIB-TypeAndInfo-r16 SEQUENCE (SIZE (1..maxSIB)) OF CHOICE { posSib1-1-r16 SIBpos-r16, posSib1-2-r16 SIBpos-r16, posSib1-3-r16 SIBpos-r16, posSib1-4-r16 SIBpos-r16, posSib1-5-r16 SIBpos-r16, posSib1-6-r16 SIBpos-r16, posSib1-7-r16 SIBpos-r16, posSib1-8-r16 SIBpos-r16, posSib2-1-r16 SIBpos-r16, posSib2-2-r16 SIBpos-r16, posSib2-3-r16 SIBpos-r16, posSib2-4-r16 SIBpos-r16, posSib2-5-r16 SIBpos-r16, posSib2-6-r16 SIBpos-r16, posSib2-7-r16 SIBpos-r16, posSib2-8-r16 SIBpos-r16, posSib2-9-r16 SIBpos-r16, posSib2-10-r16 SIBpos-r16, posSib2-11-r16 SIBpos-r16, posSib2-12-r16 SIBpos-r16, posSib2-13-r16 SIBpos-r16, posSib2-14-r16 SIBpos-r16, posSib2-15-r16 SIBpos-r16, posSib2-16-r16 SIBpos-r16, posSib2-17-r16 SIBpos-r16, posSib2-18-r16 SIBpos-r16, posSib2-19-r16 SIBpos-r16, posSib2-20-r16 SIBpos-r16, posSib2-21-r16 SIBpos-r16, posSib2-22-r16 SIBpos-r16, posSib2-23-r16 SIBpos-r16, posSib3-1-r16 SIBpos-r16, posSib4-1-r16 SIBpos-r16, posSib5-1-r16 SIBpos-r16, posSib6-1-r16 SIBpos-r16, posSib6-2-r16 SIBpos-r16, posSib6-3-r16 SIBpos-r16, ... , posSib1-9-v1700 SIBpos-r16, posSib1-10-v1700 SIBpos-r16, posSib2-24-v1700 SIBpos-r16, posSib2-25-v1700 SIBpos-r16, posSib6-4-v1700 SIBpos-r16, posSib6-5-v1700 SIBpos-r16, posSib6-6-v1700 SIBpos-r16, posSib2-17a-v1770 SIBpos-r16, posSib2-18a-v1770 SIBpos-r16, posSib2-20a-v1770 SIBpos-r16, posSib1-11-v1800 SIBpos-r16, posSib1-12-v1800 SIBpos-r16, posSib2-26-v1800 SIBpos-r16, posSib2-27-v1800 SIBpos-r16 }, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } -- TAG-POSSYSTEMINFORMATION-R16-IES-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

5.30.2.1 Identifiers

The combination of a PLMN ID and a Network identifier (NID) identifies an SNPN. NOTE 1: The PLMN ID used for SNPNs is not required to be unique. PLMN IDs reserved for use by private networks can be used for non-public networks, e.g. based on mobile country code (MCC) 999 as assigned by ITU [78]). Alternatively, a PLMN operator can use its own PLMN IDs for SNPN(s) along with NID(s), but registration in a PLMN and mobility between a PLMN and an SNPN are not supported using an SNPN subscription given that the SNPNs are not relying on network functions provided by the PLMN. The NID shall support two assignment models: - Self-assignment: NIDs are chosen individually by SNPNs at deployment time (and may therefore not be unique) but use a different numbering space than the coordinated assignment NIDs as defined in TS 23.003[ Numbering, addressing and identification ] [19]. - Coordinated assignment: NIDs are assigned using one of the following two options: 1. The NID is assigned such that it is globally unique independent of the PLMN ID used; or 2. The NID is assigned such that the combination of the NID and the PLMN ID is globally unique. NOTE 2: Which legal entities manage the number space is beyond the scope of this specification. NOTE 3: The use of SNPN with self-assignment model NID such that the combination of PLMN ID and NID is not globally unique is not assumed for the architecture described in Figure 5.30.2.9.3-1, Figure 5.30.2.9.2-1 and for SNPN - SNPN Mobility as described in clause 5.30.2.11. The GIN shall support two assignment models: - Self-assignment: GINs are chosen individually and may therefore not be unique. It is defined as in TS 23.003[ Numbering, addressing and identification ] [19]; or - Coordinated assignment: GIN uses a combination of PLMN ID and NID and is assigned using one of the following two options as defined in TS 23.003[ Numbering, addressing and identification ] [19]: 1. The GIN is assigned such that the NID is globally unique (e.g. using IANA Private Enterprise Numbers) independent of the PLMN ID used; or 2. The GIN is assigned such that the combination of the NID and the PLMN ID is globally unique. NOTE 4: Which legal entities manage the number space for GIN is beyond the scope of this specification. An optional human-readable network name helps to identify an SNPN during manual SNPN selection. The human-readable network name and how it is used for SNPN manual selection is specified in TS 22.261[ Service requirements for the 5G system ] [2] and TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [17].

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.30.2.1

8.3.1 User Plane Protocol Stack for a PDU Session

This clause illustrates the protocol stack for the User plane transport related with a PDU Session. Legend: - PDU layer: This layer corresponds to the PDU carried between the UE and the DN over the PDU Session. When the PDU Session Type is IPv4 or IPv6 or IPv4v6, it corresponds to IPv4 packets or IPv6 packets or both of them; When the PDU Session Type is Ethernet, it corresponds to Ethernet frames; etc. - GPRS Tunnelling Protocol for the user plane (GTP-U): This protocol supports tunnelling user data over N3 (i.e. between the 5G-AN node and the UPF) and N9 (i.e. between different UPFs of the 5GC) in the backbone network, details see TS 29.281[ General Packet Radio System (GPRS) Tunnelling Protocol User Plane (GTPv1-U) ] [75]. GTP shall encapsulate all end user PDUs. It provides encapsulation on a per PDU Session level. This layer carries also the marking associated with a QoS Flow defined in clause 5.7. This protocol is also used on N4 interface as defined in TS 29.244[ Interface between the Control Plane and the User Plane nodes ] [65]. Figure 8.3.1-1: User Plane Protocol Stack - 5G-AN protocol stack: This set of protocols/layers depends on the AN: - When the 5G-AN is a 3GPP NG-RAN, these protocols/layers are defined in TS 38.401[ NG-RAN; Architecture description ] [42]. The radio protocol between the UE and the 5G-AN node (eNodeB or gNodeB) is specified in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [30] and TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27]. - When the AN is an Untrusted non 3GPP access to 5GC the 5G-AN interfaces with the 5GC at a N3IWF defined in clause 4.3.2 and the 5G-AN protocol stack is defined in clause 8.3.2. - UDP/IP: These are the backbone network protocols. NOTE 1: The number of UPF in the data path is not constrained by 3GPP specifications: there may be in the data path of a PDU Session 0, 1 or multiple UPF that do not support a PDU Session Anchor functionality for this PDU Session. NOTE 2: The "non PDU Session Anchor" UPF depicted in the Figure 8.3.1-1 is optional. NOTE 3: The N9 interface may be intra-PLMN or inter PLMN (in the case of Home Routed deployment). If there is an UL CL (Uplink Classifier) or a Branching Point (both defined in clause 5.6.4) in the data path of a PDU Session, the UL CL or Branching Point acts as the non PDU Session Anchor UPF of Figure 8.3.1-1. In that case there are multiple N9 interfaces branching out of the UL CL / Branching Point each leading to different PDU Session anchors. NOTE 4: Co-location of the UL CL or Branching Point with a PDU Session Anchor is a deployment option.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

8.3.1

10.5.6.17 Request type

The purpose of the Request type information element is to indicate whether the MS requests to establish a new connectivity to a PDN or keep the connection(s) to which it has connected via non-3GPP access, or to keep the PDU session to which it has connected via 3GPP access or non-3GPP access. The Request type information element is also used to indicate that the MS is requesting connectivity to a PDN that provides emergency bearer services, or DN that provides emergency services or keep the connection that provides emergency services to which it has connected via non-3GPP access, or to keep the PDU session to which it has connected via 3GPP access or non-3GPP access. The Request type information element is coded as shown in figure 10.5.158/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.173/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The Request type is a type 1 information element. Figure 10.5.158/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Request type information element Table 10.5.173/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Request type 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.17

4.16.1.13 Number of Successful SN terminated bearers Path Update at Secondary Node Additions

a) This measurement provides the number of Successful SN terminated bearers Path Update at Secondary Node Additions. b) CC c) On receipt of an E-RAB modification confirmation message by the MN from MME (after MN sends SgNB reconfiguration complete message) when path switch is needed. SGNB Addition Trigger Indication (TS 36.423[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 Application Protocol (X2AP) ] [10]) excludes SN change, inter-eNB HO, intra-eNB HO. d) Each measurement is an integer value. e) The measurement name has the form ERAB.PathUpdateSucctAtSNAddition. f) EUtranCellFDD EUtranCellTDD g) Valid for packet switched traffic h) EPS

3GPP TS 32.425

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

SA WG5

3GPP Series : 32 , OAM&P and Charging

4.16.1.13

4.7.9.1.2 Paging for GPRS services using IMSI

Paging for GPRS services using IMSI is an abnormal procedure used for error recovery in the network. The network may initiate paging using IMSI if the P-TMSI is not available due to a network failure. In Iu mode, to initiate the procedure the GMM entity in the network requests the lower layer to start paging (see 3GPP TS 25.331[ None ] [23c] and 3GPP TS 25.413[ UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling ] [19c]). In A/Gb mode, to initiate the procedure the GMM entity in the network requests the RR sublayer to start paging (see 3GPP TS 44.018[ None ] [84], 3GPP TS 44.060[ None ] [76]). Upon reception of a paging indication for GPRS services using IMSI, the MS shall stop the timer T3346, if it is running, locally deactivate any active PDP context(s), MBMS context(s) and locally detach from GPRS. The local detach includes deleting any RAI, P-TMSI, P-TMSI signature and GPRS ciphering key sequence number stored, setting the GPRS update status to GU2 NOT UPDATED and changing state to GMM-DEREGISTERED. The MS shall stop all timers T3396 that are running. If S1 mode is supported by the MS, the MS shall in addition handle the EMM parameters EMM state, EPS update status, last visited registered TAI, TAI list, GUTI and KSIASME as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when a paging for EPS services using IMSI is received. In Iu mode, when an MS receives a paging request for GPRS services using the IMSI from the network before an MS initiated GMM specific procedure has been completed, then the MS shall abort the GMM specific procedure, and the MS shall proceed according to the description in this clause. After performing the local detach, the MS shall then perform a GPRS attach or combined GPRS attach procedure. After performing the attach, the MS should activate PDP context(s) to replace any previously active PDP context(s). The MS should also perform the procedures needed in order to activate any previously active multicast service(s). NOTE 1: In some cases, user interaction may be required and then the MS cannot activate the PDP and MBMS context(s) automatically. NOTE 2: The MS does not respond to the paging except with the Attach Request. Hence timers T3313 and T3315 in the network are not used when paging with IMSI. NOTE 3: Paging without DRX parameters may require a considerable extension of the paging duration. NOTE 4: Paging without using eDRX parameters may result in the paging with IMSI not to be received by the MS for which eDRX has been negotiated or may require a considerable extension of the paging duration.

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

8.10 Mobile Equipment Identity (MEI)

Mobile Equipment Identity (MEI) is coded as depicted in Figure 8.10-1. MEI is defined in clause 6.2 of 3GPP TS 23.003[ Numbering, addressing and identification ] [2]. Figure 8.10-1: Mobile Equipment (ME) Identity (MEI) The ME Identity field contains either the IMEI or the IMEISV as defined in clause 6.2 of 3GPP TS 23.003[ Numbering, addressing and identification ] [2]. It is encoded as specified in clause 7.7.53 of 3GPP TS 29.060[ General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface ] [4], beginning with octet 4 of Figure 7.7.53.1. The IMEI(SV) digits are encoded using BCD coding where IMEI is 15 BCD digits and IMEISV is 16 BCD digits. For IMEI, bits 5 to 8 of the last octet shall be filled with an end mark coded as '1111'.

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

8.6.1.2.3 Minimum Requirement 2 Tx Antenna Port under Time Domain Measurement Resource Restriction with CRS Assistance Information

For the parameters specified in Table 8.6.1.2.3-1 and Table 8.6.1.2.3-2, the averaged probability of a miss-detected PBCH (Pm-bch) shall be below the specified value in Table 8.6.1.2.3-2. Cell 1 is the serving cell, and Cell 2 and Cell 3 are the aggressor cells. The downlink physical channel setup for Cell 1 is according to Annex C.3.2 and for Cell 2 and Cell 3 is according to Annex C.3.3, repectively. The CRS assistance information [7] including Cell 2 and Cell 3 is provided. Table 8.6.1.2.3-1: Test Parameters for PBCH Table 8.6.1.2.3-2: Minimum performance PBCH

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

10.5.3.11 LSA Identifier

This element uniquely identifies a LSA. The LSA Identifier information element is coded as shown in figure 10.68c/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The LSA Identifier is a type 4 information element with a length of 2 or 5 octets. Figure 10.68c/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] LSA Identifier information element If the Length = 0, then no LSA ID is included. This is used to indicate that the MS has moved to an area where there is no LSA available for that MS. Octets 3-5 are coded as specified in 3GPP TS 23.003[ Numbering, addressing and identification ] [10], 'Identification of Localised Service Area'. Bit 8 of octet 3 is the most significant bit.

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

5.5.4.26 Event A4H2 (Neighbour becomes better than threshold1 and the Aerial UE altitude becomes lower than a threshold2)

The UE shall: 1> consider the entering condition for this event to be satisfied when both condition A4H2-1 and condition A4H2-2, as specified below, are fulfilled; 1> consider the leaving condition for this event to be satisfied when condition A4H2-3 or condition A4H2-4, i.e. at least one of the two, as specified below, is fulfilled. Inequality A4H2-1 (Entering condition 1) Mn + Ofn + Ocn – Hys1 > Thresh1 Inequality A4H2-2 (Entering condition 2) Ms + Hys2 < Thresh2 Inequality A4H2-3 (Leaving condition 1) Mn + Ofn + Ocn + Hys1 < Thresh1 Inequality A4H2-4 (Leaving condition 2) Ms – Hys2 > Thresh2 The variables in the formula are defined as follows: Mn is the measurement result of the neighbouring cell, not taking into account any offsets. Ofn is the measurement object specific offset of the neighbour cell (i.e. offsetMO as defined within measObjectNR corresponding to the neighbour cell). Ocn is the measurement object specific offset of the neighbour cell (i.e. cellIndividualOffset as defined within measObjectNR corresponding to the neighbour cell), and set to zero if not configured for the neighbour cell. Hys1 is the hysteresis parameter for this event (i.e. a4-Hysteresis as defined within reportConfigNR for this event). Thresh1 is the threshold parameter for this event (i.e. a4-Threshold as defined within reportConfigNR for this event). Ms is the Aerial UE altitude relative to the sea level. Hys2 is the hysteresis parameter for this event (i.e. h2-Hysteresis as defined within reportConfigNR for this event). Thresh2 is the threshold parameter for this event (i.e. h2-Threshold as defined within reportConfigNR for this event). Mn is expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR. Ofn, Ocn, Hys are expressed in dB. Thresh1 is expressed in the same unit as Mn. Ms, Hys2, Thresh2 are expressed in meters.

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

5.5.4.26

– UplinkConfigCommonSIB

The IE UplinkConfigCommonSIB provides common uplink parameters of a cell. UplinkConfigCommonSIB information element -- ASN1START -- TAG-UPLINKCONFIGCOMMONSIB-START UplinkConfigCommonSIB ::= SEQUENCE { frequencyInfoUL FrequencyInfoUL-SIB, initialUplinkBWP BWP-UplinkCommon, timeAlignmentTimerCommon TimeAlignmentTimer } UplinkConfigCommonSIB-v1700 ::= SEQUENCE { initialUplinkBWP-RedCap-r17 BWP-UplinkCommon OPTIONAL -- Need R } UplinkConfigCommonSIB-v1760 ::= SEQUENCE { frequencyInfoUL-v1760 FrequencyInfoUL-SIB-v1760 } -- TAG-UPLINKCONFIGCOMMONSIB-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

I.10.4.1 Support for N5CW devices in SNPN without CH

Procedures for authentication for devices that do not support 5GC NAS over WLAN access are described in clause 7A.2.4. For SNPN the procedures are modified as follows: Steps 0-1 are performed as described in clause 7A.2.4. In step 2 of clause 7A.2.4 the SUCI can be of type anonymous SUCI if the construction of SUCI as described in clause 6.12 cannot be used and if the employed EAP method supports SUPI privacy. Step 3-6 is performed as described in clause 7A.2.4. In step 7 of clause 7A.2.4, the authentication method is selected. 5G AKA, EAP-AKA’, or any other key-generating EAP authentication method apply for UE authentication in SNPN. In case UDM receives an anonymous SUCI, the UDM chooses the authentication method as described in step 4 of Annex I.2.2.2.2. Editor's Note: How the authentication method is selected is ffs. In step 8 of clause 7A.2.4, in case the AUSF received an anonymous SUCI in step 7, the AUSF shall perform steps 11-13 of Annex I.2.2.2 after a successful authentication to inform the UDM of the actual SUPI. Steps 9-14 are performed as described in clause 7A.2.4.

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

I.10.4.1

4.4.4.8 Release of RR connection after location updating

When the Location updating procedure is finished (see subclauses 4.4.4.6 and 4.4.4.7) the mobile station shall (except in the case where the mobile has a follow-on CM application request pending and has received the follow-on proceed indication, see subclause 4.4.4.6) set timer T3240 and enter the state WAIT FOR NETWORK COMMAND, expecting the release of the RR connection. The network may decide to keep the RR connection for network initiated establishment of a MM connection, or to allow for mobile initiated MM connection establishment. Any release of the RR connection shall be initiated by the network according to subclause 3.5 in 3GPP TS 44.018[ None ] [84], and 3GPP TS 25.331[ None ] [23c]. If the RR connection is not released within a given time controlled by the timer T3240, the mobile station shall abort the RR connection. In both cases, either after a RR connection release triggered from the network side or after a RR connection abort requested by the MS-side, the MS shall return to state MM IDLE. At transition to state MM IDLE, substates NORMAL SERVICE or RECEIVING GROUP CALL (NORMAL SERVICE) or ATTEMPTING TO UPDATE either timer T3212 or timer T3211 is started as described in subclause 4.4.4.9, or, timer T3246 is started as described in subclauses 4.4.4.7, 4.4.4.9 and 4.5.1.1. If the MS receives the "Extended wait time" for CS domain from the lower layers when no location updating or CM service request procedure is ongoing, the MS shall ignore the "Extended wait time".

3GPP TS 24.008

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

CT WG1

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

4.4.4.8

5.2.3 Physical downlink control channels

The Physical Downlink Control Channel (PDCCH) can be used to schedule DL transmissions on PDSCH and UL transmissions on PUSCH, where the Downlink Control Information (DCI) on PDCCH includes: - Downlink assignments containing at least modulation and coding format, resource allocation, and hybrid-ARQ information related to DL-SCH; - Uplink scheduling grants containing at least modulation and coding format, resource allocation, and hybrid-ARQ information related to UL-SCH. In addition to scheduling, PDCCH can be used to for: - Activation and deactivation of configured PUSCH transmission with configured grant; - Activation and deactivation of PDSCH semi-persistent transmission; - Notifying one or more UEs of the slot format; - Notifying one or more UEs of the PRB(s) and OFDM symbol(s) where the UE may assume no transmission is intended for the UE; - Transmission of TPC commands for PUCCH and PUSCH; - Transmission of one or more TPC commands for SRS transmissions by one or more UEs; - Switching a UE's active bandwidth part; - Initiating a random access procedure; - Indicating the UE(s) to monitor the PDCCH during the next occurrence of the DRX on-duration; - In IAB context, indicating the availability for soft symbols of an IAB-DU; - Triggering one shot HARQ-ACK codebook feedback; - For operation with shared spectrum channel access: - Triggering search space set group switching; - Indicating one or more UEs about the available RB sets and channel occupancy time duration; - Indicating downlink feedback information for configured grant PUSCH (CG-DFI). A UE monitors a set of PDCCH candidates in the configured monitoring occasions in one or more configured COntrol REsource SETs (CORESETs) according to the corresponding search space configurations. A CORESET consists of a set of PRBs with a time duration of 1 to 3 OFDM symbols. The resource units Resource Element Groups (REGs) and Control Channel Elements (CCEs) are defined within a CORESET with each CCE consisting a set of REGs. Control channels are formed by aggregation of CCE. Different code rates for the control channels are realized by aggregating different number of CCE. Interleaved and non-interleaved CCE-to-REG mapping are supported in a CORESET. The PDCCH repetition is operated by using two search spaces which are explicitly linked by configuration provided by the RRC layer, and are associated with corresponding CORESETs. For PDCCH repetition, two linked search spaces are configured with the same number of candidates, and two PDCCH candidates in two search spaces are linked with the same candidate index. When PDCCH repetition is scheduled to a UE, an intra-slot repetition is allowed and each repetition has the same number of CCEs and coded bits, and corresponds to the same DCI payload. Polar coding is used for PDCCH. Each resource element group carrying PDCCH carries its own DMRS. QPSK modulation is used for PDCCH.

3GPP TS 38.300

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

RAN2

3GPP Series : 38 , Radio technology beyond LTE

5.2.3

5.2.2.3.5 Acquisition of SIB(s) or posSIB(s) in RRC_CONNECTED

The UE shall: 1> if the UE is in RRC_CONNECTED with an active BWP not configured with common search space with the field searchSpaceOtherSystemInformation and the UE has not stored a valid version of a SIB or posSIB, in accordance with clause 5.2.2.2.1, of one or several required SIB(s) or posSIB(s) in accordance with clause 5.2.2.1, or 1> if the UE is in RRC_CONNECTED and acting as a L2 U2N Remote UE and the UE has not stored a valid version of a SIB, in accordance with clause 5.2.2.2.1, of one or several required SIB(s) in accordance with clause 5.2.2.1: 2> for the SI message(s) that, according to the si-SchedulingInfo or posSI-SchedulingInfo in the stored SIB1, contain at least one required SIB or requested posSIB: 3> if onDemandSIB-Request is configured and timer T350 is not running: 4> initiate transmission of the DedicatedSIBRequest message in accordance with 5.2.2.3.6; 4> start timer T350 with the timer value set to the onDemandSIB-RequestProhibitTimer; 1> else if the UE is in RRC_CONNECTED with an active BWP configured with common search space with the field searchSpaceOtherSystemInformation and the UE has not stored a valid version of a SIB or posSIB, in accordance with clause 5.2.2.2.1, of one or several required SIB(s) or posSIB(s) in accordance with clause 5.2.2.1: 2> for the SI message(s) that, according to the si-SchedulingInfo in the stored SIB1, contain at least one required SIB and for which si-BroadcastStatus is set to broadcasting: 3> acquire the SI message(s) as defined in clause 5.2.2.3.2; 2> for the SI message(s) that, according to the si-SchedulingInfo in the stored SIB1, contain at least one required SIB and for which si-BroadcastStatus is set to notBroadcasting: 3> if onDemandSIB-Request is configured and timer T350 is not running: 4> initiate transmission of the DedicatedSIBRequest message in accordance with 5.2.2.3.6; 4> start timer T350 with the timer value set to the onDemandSIB-RequestProhibitTimer; 4> acquire the requested SI message(s) corresponding to the requested SIB(s) as defined in clause 5.2.2.3.2. 2> for the SI message(s) that, according to the posSI-SchedulingInfo in the stored SIB1, contain at least one requested posSIB and for which posSI-BroadcastStatus is set to broadcasting: 3> acquire the SI message(s) as defined in clause 5.2.2.3.2; 2> for the SI message(s) that, according to the posSI-SchedulingInfo in the stored SIB1, contain at least one requested posSIB and for which posSI-BroadcastStatus is set to notBroadcasting: 3> if onDemandSIB-Request is configured and timer T350 is not running: 4> initiate transmission of the DedicatedSIBRequest message in accordance with 5.2.2.3.6; 4> start timer T350 with the timer value set to the onDemandSIB-RequestProhibitTimer; 4> acquire the requested SI message(s) corresponding to the requested posSIB(s) as defined in clause 5.2.2.3.2. NOTE: UE may include on demand request for SIB and/or posSIB(s) in the same DedicatedSIBRequest message.

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

5.2.2.3.5

4.22.6.2.1 5GS to EPS handover using N26 interface

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

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.22.6.2.1

16.9.4.2 Control of connected UEs

The UE in RRC_CONNECTED performs NR sidelink communication and/or V2X sidelink communication, as configured by the upper layers. The UE sends Sidelink UE Information to NG-RAN in order to request or release sidelink resources and report QoS information for each destination. NG-RAN provides RRCReconfiguration to the UE in order to provide the UE with dedicated sidelink configuration. The RRCReconfiguration may include SL DRB configuration(s) for NR sidelink communication as well as mode 1 resource configuration and/or mode 2 resource configuration. If UE has received SL DRB configuration via system information, UE should continue using the configuration to perform sidelink data transmissions and receptions until a new configuration is received via the RRCReconfiguration. NG-RAN may also configure measurement and reporting of CBR for NR sidelink communication and V2X sidelink communication, and reporting of location information for V2X sidelink communication to the UE via RRCReconfiguration. During handover, the UE performs sidelink transmission and reception based on configuration of the exceptional transmission resource pool or configured sidelink grant Type 1 and reception resource pool of the target cell as provided in the handover command.

3GPP TS 38.300

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

RAN2

3GPP Series : 38 , Radio technology beyond LTE

16.9.4.2

13.2.4.4.1 N32-f key hierarchy

The N32-f key hierarchy is based on the N32-f master key generated during the N32-c initial handshake by TLS key export. The N32-f key hierarchy consists of two pairs of session keys and two pairs of IV salts, which are used in two different HTTP/2 sessions. In one Session the N32-c initiator acts as the HTTP client and in the second the N32-c responder acts as the client. If the exported master secret is reused to set up multiple HTTP sessions or to set up new HTTP sessions on stream ID exhaustion, a new, unique, N32-f Context ID shall be generated to avoid key and IV re-use. The master key shall be obtained from the TLS exporter. The export function takes 3 arguments: Label, Context, Length (in octets) of the desired output. For the N32 Master key derivation, the Label shall be the IANA registered label "EXPORTER_3GPP_N32_MASTER" [89], the Context shall be "" (the empty string) and the Length shall be 64. The N32 key derivation function N32-KDF shall be based on HKDF [62] and shall use only the HKDF-Expand function as the initial key material has been generated securely: N32-KDF (label, L) = HKDF-Expand (N32-f master key, "N32" || N32-Context-ID || label, L), where - label is a string used for key separation, - L is the length of output keying material in octets. Each run of N32-KDF (label, L) produces either one session key or one IV salt. There are two pairs of session keys and IV salts to be derived. NOTE: In AES-GCM re-use of one IV may reveal the integrity key (Joux’s Forbidden attack). The binding of session keys and IV salts to N32-f context IDs and labels is essential to protect against inadvertent use of the same key with a repeated IV. The labels for the JWE keys are: - "parallel_request_key" - "parallel_response_key" - "reverse_request_key", and - "reverse_response_key". The keys derived with labels starting parallel shall be used for request/responses in an HTTP session with the N32-c initiating SEPP acting as the client (i.e. in parallel to the N32-c connection). The keys derived with the labels starting reverse shall be used for an HTTP session with the N32-c responding SEPP acting as the client. To generate the IV salts, the length is 8 and the labels are: - "parallel_request_iv_salt", - "parallel_response_iv_salt", - "reverse_request_iv_salt", and - "reverse_response_iv_salt". The 96-bit nonce for AES_GCM shall be constructed as the concatenation of the IV salt (8 octets, 64-bits) and the sequence counter, SEQ, following section 8.2.1 of NIST Special Publication 800-38D [63]: Nonce = IV salt || SEQ. The sequence counter shall be a 32-bit unsigned integer that starts at zero and is incremented for each invocation of the encryption. A different sequence counter shall be maintained for each IV salt.

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

13.2.4.4.1

6.1.3.9 MBMS context deactivation

The purpose of this procedure is to deactivate an existing MBMS context in the MS and the network. The MS shall only initiate the MBMS context deactivation when requested by the network, however the trigger for the deactivation request by the network may be initiated by the MS at application layer or by the network, see 3GPP TS 23.246[ Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description ] [106]. After a successful MBMS context deactivation, the associated MBMS NSAPI and TI values shall be released in both the MS and the network and can be reassigned to another MBMS context. The MBMS context deactivation procedure makes use of the messaging and signalling of the PDP context deactivation procedure as described in the subclauses 6.1.3.9.1 and 6.1.3.9.2.

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

6.2.5.1.4.4 Updating a derived QoS rule by reflective QoS in the UE

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

3GPP TS 24.501

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

CT WG1

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

6.2.5.1.4.4

4.1 Charging mechanisms 4.1.0 General

3GPP networks provide functions that implement offline and/or online charging mechanisms on the domain (e.g. EPC), subsystem (e.g. IMS) and service (e.g. MMS) levels. In order to support these charging mechanisms, the network performs real-time monitoring of resource usage on the above three levels in order to detect the relevant chargeable events. The charging levels are further described in clause 5.3. In offline charging, the resource usage is reported from the network to the BD after the resource usage has occurred. In online charging, a subscriber account, located in an OCS or CCS, is queried prior to granting permission to use the requested network resource(s). Typical examples of network resource usage are a voice call of certain duration, the transport of a certain volume of data, or the submission of a MM of a certain size. The network resource usage requests may be initiated by the UE (MO case) or by the network (MT case). Offline and online charging may be performed simultaneously and independently for the same chargeable event. Clause 5.5 provides further insight into potential utilisation of the charging information produced by the offline and online charging mechanisms.

3GPP TS 32.240

Telecommunication management; Charging management; Charging architecture and principles

SA WG5

3GPP Series : 32 , OAM&P and Charging

4.1

5.5.3.2.4A Tracking area updating successful for EPS services and not accepted for SMS services

Apart from the actions on the tracking area updating attempt counter, the description for tracking area update for EPS services as specified in clause 5.5.3.2.4 shall be followed. In addition, the following description for tracking area updating for SMS services applies. In NB-S1 mode, if the UE requested "SMS only" in the Additional update type IE and supports NB-S1 mode only, the MME decides to accept the tracking area update request for EPS services only and: - the location update for non-EPS services is not accepted by the VLR as specified in 3GPP TS 29.118[ Mobility Management Entity (MME) - Visitor Location Register (VLR) SGs interface specification ] [16A]; or - the MME decides to not accept the tracking area update request for "SMS only", the MME shall set the EPS update result IE to "EPS only", shall not indicate "SMS only" in the Additional update result IE in the TRACKING AREA UPDATE ACCEPT message and shall include an appropriate SMS services status value. The UE receiving the TRACKING AREA UPDATE ACCEPT message takes one of the following actions depending on the value included in the SMS services status IE: "SMS services not available" The UE shall stop timer T3430 if still running, shall reset the tracking area updating attempt counter, shall set the EPS update status to EU1 UPDATED and shall enter state EMM-REGISTERED.NORMAL-SERVICE. The USIM shall be considered as invalid for SMS services until switching off or the UICC containing the USIM is removed or the timer T3245 expires as described in clause 5.3.7a. "SMS services not available in this PLMN" The UE shall stop timer T3430 if still running, shall reset the tracking area updating attempt counter, shall set the EPS update status to EU1 UPDATED and shall enter state EMM-REGISTERED.NORMAL-SERVICE. The UE may provide a notification to the user or the upper layers that the SMS services are not available. The UE shall not attempt normal attach or tracking area updating procedures indicating "SMS only" with current PLMN until switching off the UE or the UICC containing the USIM is removed. Additionally, the UE may perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. "Network failure" The UE shall stop timer T3430 if still running. The tracking area updating attempt counter shall be incremented, unless it was already set to 5. If the tracking area updating attempt counter is less than 5: - the UE shall start timer T3411, shall set the EPS update status to EU1 UPDATED and shall enter state EMM-REGISTERED.NORMAL-SERVICE. When timer T3411 expires the normal tracking area updating procedure for EPS services and "SMS only" or the combined tracking area updating procedure for EPS services and "SMS only" is triggered. If the tracking area updating attempt counter is equal to 5: - the UE shall start timer T3402, shall set the EPS update status to EU1 UPDATED and shall enter state EMM-REGISTERED.NORMAL-SERVICE. When timer T3402 expires the normal tracking area updating procedure for EPS services and "SMS only" or the combined tracking area updating procedure for EPS services and "SMS only" is triggered. "Congestion" The UE shall stop the timer T3430 if still running. The tracking area updating attempt counter shall be set to 5. The UE shall start the timer T3402, shall set the EPS update status to EU1 UPDATED, and shall enter state EMM-REGISTERED.NORMAL-SERVICE. When timer T3402 expires the normal tracking area updating procedure for EPS services and "SMS only" or the combined tracking area updating procedure for EPS services and "SMS only" is triggered. Other values are considered as abnormal cases. The tracking area updating procedure shall be considered as failed for SMS services. The behaviour of the UE in those cases is specified in clause 5.5.3.2.6A.

3GPP TS 24.301

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

CT WG1

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

5.5.3.2.4A

6.37.1 Description

Ranging-based services are the applications utilizing the distance between two UEs and/or the direction of one UE from the other one. In 3D case, direction includes horizontal direction and elevation direction. Ranging-based services can apply to a variety of verticals, such as consumer, smart home, smart city, smart transportation, smart retail, and industry 4.0. Some ranging-based services can only require the distance measurement, some can only require direction measurement, others can require both distance and direction measurement. Ranging can be supported with or without 5G coverage and figure 6.37.1-1 is an illustration of ranging between UEs that are in coverage, out of coverage, or with partial coverage. Both licensed and unlicensed spectrum can be used for ranging. If licensed spectrum is used, it shall be fully under operator control. Figure 6.37.1-1: Illustration of ranging between UEs with or without 5G coverage

3GPP TS 22.261

Service requirements for the 5G system

SA WG1

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

6.37.1

6.40.2.1 Requirements for direct network connection

Based on operator policy, the 5G system shall be able to provide means to allow an authorized third-party to monitor the resource utilisation of the network service that is associated with the third-party. NOTE 1: Resource utilization in the preceding requirement refers to measurements relevant to the UE’s performance such as the data throughput provided to the UE. Based on operator policy, the 5G system shall be able to provide an indication about a planned change of bitrate, latency, or reliability for a QoS flow to an authorized 3rd party so that the 3rd party AI/ML application is able to adjust the application layer behaviour if time allows. The indication shall provide the anticipated time and location of the change, as well as the target QoS parameters. Based on operator policy, 5G system shall be able to provide means to predict and expose predicted network condition changes (i.e. bitrate, latency, reliability) per UE, to an authorized third party. Subject to user consent, operator policy and regulatory constraints, the 5G system shall be able to support a mechanism to expose monitoring and status information of an AI-ML session to a 3rd party AI/ML application. NOTE 2: Such mechanism is needed for AI/ML application to determine an in-time transfer of AI/ML model. 5G system shall be able to provide event alerting to an authorized 3rd party, together with a predicted time of the event (e.g., alerting about traffic congestion or UE moving into/out of a different geographical area). NOTE 3: A 3rd party AI/ML application may use the prediction information to minimize disturbance in the transfer of learning data and AI/ML model data. The 5G system shall be able to expose aggregated QoS parameter values for a group of UEs to an authorized service provider. The 5G system shall be able to support an authorised 3rd party to change aggregated QoS parameter values associated with a group of UEs, e.g. UEs of a FL group. Subject to user consent, operator policy and regulatory requirements, the 5G system shall be able to expose information (e.g. candidate UEs) to an authorized 3rd party to assist the 3rd party to determine member(s) of a group of UEs (e.g. UEs of a FL group).

3GPP TS 22.261

Service requirements for the 5G system

SA WG1

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

6.40.2.1

6.9.2.1.1 Access stratum

The general principle of key handling for KNG-RAN*/NH at handovers is depicted in Figure 6.9.2.1.1-1. Figure 6.9.2.1.1-1: Model for the handover key chaining The following is an outline of the key handling model to clarify the intended structure of the key derivations. The detailed specification is provided in sub-clauses 6.9.2.2 and 6.9.2.3. Whenever an initial AS security context needs to be established between UE and gNB/ng-eNB, AMF and the UE shall derive a KgNB and a Next Hop parameter (NH). The KgNB and the NH are derived from the KAMF. A NH Chaining Counter (NCC) is associated with each KgNB and NH parameter. Every KgNB is associated with the NCC corresponding to the NH value from which it was derived. At initial setup, the KgNB is derived directly from KAMF, and is then considered to be associated with a virtual NH parameter with NCC value equal to zero. At initial setup, the derived NH value is associated with the NCC value one. NOTE 1: At the UE, the NH derivation associated with NCC=1 could be delayed until the first handover performing vertical key derivation. NOTE 1a: In N2 handover, when the KgNB is updated either due to KAMF change or synchronising the AS security context with the NAS security context, the KgNB is derived as specified in clauses 6.9.2.3.3 and 6.9.2.3.4 of the present document. In inter-RAT handover, the KgNB is derived as specified in clause 8.4 of the present document. In UE context modification, the KgNB is derived as specified in clause 6.9.2.2. Whether the AMF sends the KgNB key or the {NH, NCC} pair to the serving gNB/ng-eNB is described in detail in sub-clauses 6.9.2.2 and 6.9.2.3. The AMF shall not send the NH value to gNB/ng-eNB at the initial connection setup. The gNB/ng-eNB shall initialize the NCC value to zero after receiving NGAP Initial Context Setup Request message. NOTE 2: Since the AMF does not send the NH value to gNB/ng-eNB at the initial connection setup, the NH value associated with the NCC value one cannot be used in the next Xn handover or the next intra-gNB/intra-ng-eNB-CU handover, for the next Xn handover or the next intra-gNB-CU/intra-ng-eNB handover the horizontal key derivation (see Figure 6.9.2.1.1-1) will apply. NOTE 3: One of the rules specified for the AMF in sub-clause 6.9.2.3.3 of the present document states that the AMF always computes a fresh {NH, NCC} pair that is given to the target gNB/ng-eNB. An implication of this is that the first {NH, NCC} pair will never be used to derive a KgNB. It only serves as an initial value for the NH chain. The UE and the gNB/ng-eNB use the KgNB to secure the communication between each other. On handovers and at transitions from RRC_INACTIVE to RRC_CONNECTED states (defined in clause 6.8.2.1), the basis for the KgNB that will be used between the UE and the target gNB/ng-eNB, called KNG-RAN*, is derived from either the currently active KgNB or from the NH parameter. If KNG-RAN* is derived from the currently active KgNB this is referred to as a horizontal key derivation (see Figure 6.9.2.1.1-1) and if the KNG-RAN* is derived from the NH parameter the derivation is referred to as a vertical key derivation (see Figure 6.9.2.1.1-1). As NH parameters are only computable by the UE and the AMF, it is arranged so that NH parameters are provided to gNB/ng-eNBs from the AMF in such a way that forward security can be achieved. On handovers with vertical key derivation the NH is further bound to the target PCI and its frequency ARFCN-DL before it is taken into use as the KgNB in the target gNB/ng-eNB. On handovers with horizontal key derivation the currently active KgNB is further bound to the target PCI and its frequency ARFCN-DL before it is taken into use as the KgNB in the target gNB/ng-eNB.

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

6.9.2.1.1

8.15.1.3 Multicast MRB type re-configuration with F1-U ptp-retransmission tunnel establishment

Figure 8.15.1.3-1: Multicast MRB type re-configuration with F1-U ptp retransmission tunnel establishment 1. The gNB-DU decides to change the MRB type configuration for a UE and provides the new configuration to the gNB-CU-CP along with a per-MRB MRB type reconfiguration indication and the MRB Reconfigured RLC mode. 2. The gNB-CU-CP confirms the modification request and indicates this to the gNB-DU. The gNB-CU-CP may request the gNB-DU to establish F1-U ptp retransmission resources in order for the UE to perform PDCP Status Report and receive retransmitted PDCP PDUs for the reconfigured MRBs. 4. - 7. If necessary, the gNB-DU requests the establishment of F1-U resources for ptp retransmission by means of triggering the F1AP Multicast Distribution Setup procedure, which in turn triggers the E1AP MC Bearer Context Modification procedure to exchange F1-U tunnel end-point addresses. NOTE: Depending on MRB bearer type reconfiguration the gNB-DU may also request to release some F1-U resources. 8./9. The RRC Reconfiguration procedure is performed 10. PDCP Status Report and PDCP PDU retransmission can take place via the established F1-U ptp retransmission resources.

3GPP TS 38.401

NG-RAN; Architecture description

RAN3

3GPP Series : 38 , Radio technology beyond LTE

8.15.1.3

7B.7.3 Authentication for AUN3 devices supporting 5G key hierarchy

This clause specifies the how an AUN3 device supporting 5G key hierarchy behind 5G-RG shall be registered to the 5GC by the 5G-RG and shall be authenticated by 5GC using EAP-AKA’. Figure 7B.7.3-1 Authentication Procedure for AUN3 devices supporting 5G key hierarchy using EAP-AKA’ Steps 1-7 are the same as steps 1-7 in clause 7B.7.2. 8. The UDM shall send to the AUSF a Nudm_UEAuthentication_Get Response message, including the EAP-AKA’ authentication vector (RAND, AUTN, XRES, CK´ and IK´), the SUPI. Steps 9-15 are the same as steps 9-15 in clause 7B.7.2. 16. The AUSF shall verify the AKA’-Challenge message as described in RFC 5448[12]. If successful, the AUSF shall generate the KAUSF as defined in section 6.1.3.1. 17. The AUSF shall send to the AMF/SEAF an Nausf_UEAuthentication_Authenticate Response message including the EAP-Success, the Anchor key, and the SUPI. 18. In the final authentication message from the home network, if the AUSF has sent the anchor key KSEAF, the SEAF shall derive the KAMF from KSEAF and send it to the AMF. 19. The AMF shall derive KWAGF key. NOTE: Whether the key KWAGF is used by the 5G-RG and W-AGF is out of the scope of 3GPP. 20. Step 20 is the same as step 19 in clause 7B.7.2. 21a-21b. If the layer 2 connection is over WLAN (IEEE 802.11), the AUN3 device and the 5G-RG use KWAGF as the PMK, from which the WLAN keys are derived. 22. Step 22 is the same as step 21 in clause 7B.7.2.

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

7B.7.3

5.2.6.9 Nnef_AFsessionWithQoS service 5.2.6.9.1 General

See clauses 4.15.6.6, 4.15.6.13, 4.15.6.14. This service is also used to support subscription and notification of QoS Monitoring for the QoS parameter(s) to be measured defined in clause 5.45 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. This service is also used to support subscription and notification of BAT offset for the AF that supports adjusting burst sending time based on RAN feedback, as described in clause 5.27.2.5 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. This service is also used to support the QoS resource allocation for a list of UEs. This service is also used to support subscription and notification of QoS Monitoring event for Data Rate Monitoring for a list of QoS flows, as described in clause 5.2.26.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

5.2.6.9

5.2.6.17.4 Nnef_UCMFProvisioning_Update operation

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

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

5.2.6.17.4

4.7.3.2 Flow and Congestion Control

Flow and congestion control can be supported in both upstream and downstream directions in order to avoid congestion-related packet drops on IAB-nodes and IAB-donor-DU: - In upstream direction, UL scheduling on MAC layer can support flow control on each hop; - In downstream direction, the NR user plane protocol (TS 38.425[ NG-RAN; NR user plane protocol ] [33]) supports flow and congestion control between the IAB-node and the IAB-donor-CU for UE bearers that terminate at this IAB-node. Further, flow control is supported on BAP sublayer, where the IAB-node can send feedback information on the available buffer size for an ingress BH RLC channel or BAP routing ID to its parent node. The feedback can be sent proactively, e.g., when the buffer load exceeds a certain threshold, or based on polling by the parent node.

3GPP TS 38.300

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

RAN2

3GPP Series : 38 , Radio technology beyond LTE

4.7.3.2

6.5.4.2 UE requested bearer resource modification procedure initiation

In order to request the modification of bearer resources for one traffic flow aggregate, the UE shall send a BEARER RESOURCE MODIFICATION REQUEST message to the MME, start timer T3481 and enter the state PROCEDURE TRANSACTION PENDING (see example in figure 6.5.4.2.1). The UE shall include the EPS bearer identity of the EPS bearer associated with the traffic flow aggregate in the EPS bearer identity for packet filter IE. To request a change of the GBR without changing the packet filter(s), the UE shall set the TFT operation code in the Traffic flow aggregate IE to "no TFT operation" and include the packet filter identifier(s) to which the change of the GBR applies in the Packet filter identifier parameter in the parameters list. The UE shall indicate the new GBR requested for the EPS bearer context in the Required traffic flow QoS IE. To request a modification of a traffic flow aggregate, the UE shall set the TFT operation code in the Traffic flow aggregate IE to "Replace packet filters in existing TFT" or "Add packet filters to existing TFT". If the TFT operation code is set to "Add packet filters to existing TFT", the UE shall include in the parameter list one existing packet filter identifier to which the newly added packet filter(s) is linked. If the EPS bearer is a GBR bearer and the UE also wishes to request a change of GBR, the UE shall indicate the new GBR requested for the EPS bearer context in the Required traffic flow QoS IE. To request a release of bearer resources, the UE shall set the TFT operation code in the Traffic flow aggregate IE to "Delete packet filters from existing TFT". If the EPS bearer is a GBR bearer and the UE does not request the release of all bearer resources, the UE shall indicate the new GBR requested for the EPS bearer context in the Required traffic flow QoS IE. To request re-negotiation of header compression configuration associated to an EPS bearer context, the UE shall include the Header compression configuration IE in the BEARER RESOURCE MODIFICATION REQUEST message if the network indicated "Control plane CIoT EPS optimization supported" and "Header compression for control plane CIoT EPS optimization supported" in the EPS network feature support IE. After an inter-system change from N1 mode to S1 mode, if: a) the UE is operating in single-registration mode and has received the interworking without N26 interface indicator set to "interworking without N26 interface not supported" from the network; b) the PDN type value of the PDN type IE is set to "IPv4", "IPv6" or "IPv4v6"; c) the UE indicates "Control plane CIoT EPS optimization supported" and "Header compression for control plane CIoT EPS optimization supported" in the UE network capability IE of the TRACKING AREA UPDATE REQUEST message; and d) the network indicates "Control plane CIoT EPS optimization supported" and "Header compression for control plane CIoT EPS optimization supported" in the EPS network feature support IE of the TRACKING AREA UPDATE ACCEPT message; the UE shall send a BEARER RESOURCE MODIFICATION REQUEST message to the MME and include the Header compression configuration IE to negotiate the header compression configuration. To indicate a change of 3GPP PS data off UE status associated to a PDN connection, the UE shall include the Protocol configuration options IE in the BEARER RESOURCE MODIFICATION REQUEST message and set the 3GPP PS data off UE status only if: - the network included the 3GPP PS data off support indication in the Protocol configuration options IE in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message when the PDN connection was established; or - the PDU session was established when in N1 mode. To indicate a change of 3GPP PS data off UE status, the UE shall include the EPS bearer identity of the default EPS bearer context of the PDN connection, for which the UE wishes a change of the 3GPP PS data off UE status, in the EPS bearer identity for packet filter IE. The UE behaves as described in clause 6.3.10. If the UE requests the modification of a traffic flow aggregate, which is assigned to a dedicated EPS bearer context, it shall ensure that at least one packet filter applicable for the uplink direction remains among the packet filters created on request from the UE in that TFT, or no own packet filters. NOTE 1: If the UE requests the release of all bearer resources of a GBR bearer and includes a Required traffic flow QoS IE in the BEARER RESOURCE MODIFICATION REQUEST message, the network ignores the Required traffic flow QoS IE. If the UE includes the Required traffic flow QoS IE, the UE shall set the QCI to the current QCI value of the EPS bearer context. If the UE requests the release of bearer resources, the ESM cause value typically indicates one of the following: #36: regular deactivation. To perform authorization for the C2 communication when a PDN connection is already established for the USS communication, the UE shall include the Extended protocol configuration options IE in the BEARER RESOURCE MODIFICATION REQUEST message containing the service-level-AA container with the length of two octets. In the service-level-AA container with the length of two octets, the UE shall include: a) the service-level device ID, with the value set to CAA-level UAV ID; b) if provided by the upper layers, the service-level-AA payload type parameter with the value set to "C2 authorization payload"; and c) the service-level-AA payload parameter, with the value set to C2 authorization payload. NOTE 2: The C2 authorization payload can contain one, some or all of the pairing information for C2 communication, an indication of the request for direct C2 communication, pairing information for direct C2 communication and flight authorization information. To provide a UE policy container with the length of two octets containing the UE STATE INDICATION message (see 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] annex D), the UE shall include the Extended protocol configuration options IE in the BEARER RESOURCE MODIFICATION REQUEST message, and include the UE policy container with the length of two octets in the Extended protocol configuration options IE. Figure 6.5.4.2.1: UE requested bearer resource modification procedure For the NBIFOM procedures as defined in 3GPP TS 24.161[ Network-Based IP Flow Mobility (NBIFOM); Stage 3 ] [36], the UE may send a BEARER RESOURCE MODIFICATION REQUEST message to the MME. It is possible that the traffic flow aggregate IE is not needed in the following procedures: - re-negotiation of header compression configuration associated to an EPS bearer context; - indicating a change of 3GPP PS data off UE status associated to a PDN connection; or - NBIFOM procedures. If the traffic flow aggregate IE is not needed, the UE shall set: - the length indicator of the Traffic flow aggregate IE to the value 1; - the TFT operation code to "000"; - the E bit to zero; and - the number of packet filters to zero.

3GPP TS 24.301

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

CT WG1

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

6.5.4.2

5.3.2.2.2 RM-DEREGISTERED state

In the RM-DEREGISTERED state, the UE is not registered with the network. The UE context in AMF holds no valid location or routing information for the UE so the UE is not reachable by the AMF. However, some parts of UE context may still be stored in the UE and the AMF e.g. to avoid running an authentication procedure during every Registration procedure. In the RM-DEREGISTERED state, the UE shall: - attempt to register with the selected PLMN using the Initial Registration procedure if it needs to receive service that requires registration (see clause 4.2.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]). - remain in RM-DEREGISTERED state if receiving a Registration Reject upon Initial Registration (see clause 4.2.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]). - enter RM-REGISTERED state upon receiving a Registration Accept (see clause 4.2.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]). When the UE RM state in the AMF is RM-DEREGISTERED, the AMF shall: - when applicable, accept the Initial Registration of a UE by sending a Registration Accept to this UE and enter RM-REGISTERED state for the UE (see clause 4.2.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]); or - when applicable, reject the Initial Registration of a UE by sending a Registration Reject to this UE (see clause 4.2.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]).

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.3.2.2.2

4.12.5 UE Requested PDU Session Establishment via Untrusted non-3GPP Access

Clause 4.12.5 specifies how a UE can establish a PDU Session via an untrusted non-3GPP Access Network as well as to hand over an existing PDU Session between 3GPP access and non-3GPP access. The procedure applies in non-roaming, roaming with LBO as well as in home-routed roaming scenarios. For non-roaming and LBO scenarios, if the UE is simultaneously registered to a 3GPP access in a PLMN different from the PLMN of the N3IWF, the functional entities in the following procedures are located in the PLMN of the N3IWF. For home-routed roaming scenarios, the AMF, V-SMF and associated UPF in VPLMN in the following procedure is located in the PLMN of the N3IWF. The procedure below is based on the PDU Session Establishment procedure specified in clause 4.3.2.2.1 (for non-roaming and roaming with LBO) and the PDU Session Establishment procedure specified in clause 4.3.2.2.2 (for home-routed roaming). Figure 4.12.5-1: PDU Session establishment via untrusted non-3GPP access 1. The UE shall send a PDU Session Establishment Request message to AMF as specified in step 1 of clause 4.3.2.2.1. This message shall be sent to N3IWF via the IPsec SA for NAS signalling (established as specified in clause 4.12.2) and the N3IWF shall transparently forward it to AMF in the 5GC. 2a. In the case of non-roaming or roaming with Local Breakout, steps 2-11 specified in clause 4.3.2.2.1are executed according to the PDU Session Establishment procedure over 3GPP access. In the case of home-routed roaming, steps 2-14 specified in clause 4.3.2.2.2 are executed according to the PDU Session Establishment procedure over 3GPP access. 2b. As described in step 12 of clause 4.3.2.2.1, the AMF shall send a N2 PDU Session Request message to N3IWF to establish the access resources for this PDU Session. 3. Based on its own policies and configuration and based on the QoS profiles received in the previous step, the N3IWF shall determine the number of IPsec Child SAs to establish and the QoS profiles associated with each IPsec Child SA. For example, the N3IWF may decide to establish one IPsec Child SA and associate all QoS profiles with this IPsec Child SA. In this case, all QoS Flows of the PDU Session would be transferred over one IPsec Child SA. 4a. The N3IWF shall send to UE an IKE Create_Child_SA request according to the IKEv2 specification in RFC 7296 [3] to establish the first IPsec Child SA for the PDU Session. The IKE Create_Child_SA request indicates that the requested IPsec Child SA shall operate in tunnel mode. This request shall include a 3GPP-specific Notify payload which contains (a) the QFI(s) associated with the Child SA, (b) the identity of the PDU Session associated with this Child SA, (c) optionally, a DSCP value associated with the Child SA, (d) optionally a Default Child SA indication and (e) optionally, the Additional QoS Information specified in clause 4.12a.5 The IKE Create_Child_SA request shall also include another 3GPP-specific Notify payload, which contains the UP_IP_ADDRESS that is specified in step 8 below. If a DSCP value is included, then the UE and the N3IWF shall mark all IP packets sent over this Child SA with this DSCP value. There shall be one and only one Default Child SA per PDU session. The UE shall send all QoS Flows to this Child SA for which there is no mapping information to a specific Child SA. The IKE Create_Child_SA request also contains other information (according to RFC 7296 [3]) such as the SA payload, the Traffic Selectors (TS) for the N3IWF and the UE, etc. After receiving the IKE Create_Child_SA request, if the Additional QoS Information is received, the UE may reserve non-3GPP Access Network resources according to the Additional QoS Information. 4b. If the UE accepts the new IPsec Child SA, the UE shall send an IKE Create_Child_SA response according to the IKEv2 specification in RFC 7296 [3]. During the IPsec Child SA establishment the UE shall not be assigned an IP address. 4c-4d. If in step 3 the N3IWF determined to establish multiple IPsec Child SAs for the PDU Session, then additional IPsec Child SAs shall be established, each one associated with one or more QFI(s), optionally with a DSCP value, with a UP_IP_ADDRESS and optionally with the Additional QoS Information specified in clause 4.12a.5. For each IPsec Child SA, if the Additional QoS Information is received, the UE may reserve non-3GPP Access Network resources according to the Additional QoS Information for the IPsec Child SA. 5. After all IPsec Child SAs are established, the N3IWF shall forward to UE via the signalling IPsec SA (see clause 4.12.2.2) the PDU Session Establishment Accept message received in step 2b. 6. The N3IWF shall send to AMF an N2 PDU Session Response. 7. In the case of non-roaming or roaming with Local Breakout, all steps specified in clause 4.3.2.2.1 after step 14 are executed according to the PDU Session Establishment procedure over 3GPP access. In the case of home-routed roaming, all steps specified in clause 4.3.2.2.2 after step 18 are executed according to the PDU Session Establishment procedure over 3GPP access. 8. On the user-plane: - When the UE has to transmit an UL PDU, the UE shall determine the QFI associated with the UL PDU (by using the QoS rules of the PDU Session), it shall encapsulate the UL PDU inside a GRE packet and shall forward the GRE packet to N3IWF via the IPsec Child SA associated with this QFI. The header of the GRE packet carries the QFI associated with the UL PDU. The UE shall encapsulate the GRE packet into an IP packet with source address the "inner" IP address of the UE and destination address the UP_IP_ADDRESS associated with the Child SA. - When the N3IWF receives a DL PDU via N3, the N3IWF uses the QFI and the identity of the PDU Session in order to determine the IPsec Child SA to use for sending the DL PDU over NWu. The N3IWK encapsulates the DL PDU inside a GRE packet and copies the QFI in the header of the GRE packet. The N3IWF may include also in the GRE header a Reflective QoS Indicator (RQI), which shall be used by the UE to enable reflective QoS. The N3IWF shall encapsulate the GRE packet into an IP packet with source address the UP_IP_ADDRESS associated with the Child SA and destination address the "inner" IP address of the UE.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.12.5

9.11.3.24 EPS NAS message container

The purpose of the EPS NAS message container information element is to transport an EPS NAS message as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]. The EPS NAS message container information element is coded as shown in figure 9.11.3.24.1 and table 9.11.3.24.1. The EPS NAS message container is a type 6 information element. Figure 9.11.3.24.1: EPS NAS message container information element Table 9.11.3.24.1: EPS NAS message container information element

3GPP TS 24.501

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

CT WG1

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

9.11.3.24

4.1.2.1.1 Main states

0 NULL The mobile station is inactive (e.g. power down). Important parameters are stored. Only manual action by the user may transfer the MM sublayer to another state. 3 LOCATION UPDATING INITIATED A location updating procedure has been started and the MM awaits a response from the network. The timer T3210 is running. 5 WAIT FOR OUTGOING MM CONNECTION The MM connection establishment has been started, and the MM awaits a response from the network. The timer T3230 is running. 6 MM CONNECTION ACTIVE The MM sublayer has a RR connection to its peer entity on the network side. One or more MM connections are active. 7 IMSI DETACH INITIATED The IMSI detach procedure has been started. The timer T3220 is running. 8 PROCESS CM SERVICE PROMPT The MM sublayer has a RR connection to its peer entity on the network side. The Mobile Station has received a CM SERVICE PROMPT message but has not yet responded $(CCBS)$. 9 WAIT FOR NETWORK COMMAND The MM sublayer has a RR connection to its peer entity in the network, but no MM connection is established. The mobile station is passive, awaiting further commands from the network. The timer T3240 may be running. 10 LOCATION UPDATE REJECTED A location updating procedure has been rejected and RR connection release is awaited. The timer T3240 is running. Figure 4.1a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Overview mobility management protocol/MS Side Additions to Figure 4.1a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] 13. WAIT FOR RR CONNECTION (LOCATION UPDATING) The MM sublayer has requested RR connection establishment for starting the location updating procedure. 14. WAIT FOR RR CONNECTION (MM CONNECTION) The MM sublayer has requested RR connection establishment for dedicated mode for starting the MM connection establishment. 15. WAIT FOR RR CONNECTION (IMSI DETACH) The MM sublayer has requested RR connection establishment for starting the IMSI detach procedure. 17. WAIT FOR REESTABLISH A lower layer failure has occurred and re-establishment may be performed from the disturbed CM layer entities. 18. WAIT FOR RR ACTIVE The MM sublayer has requested activation of the RR sublayer. 19. MM IDLE There is no MM procedure running and no RR connection exists except that a local MM context may exist when the RR sublayer is in Group Receive mode. This is a compound state, and the actual behaviour of the mobile station to Connection Management requests is determined by the actual substate as described hereafter. 20. WAIT FOR ADDITIONAL OUTGOING MM CONNECTION. The MM connection establishment for an additional MM connection has been started, and the MM awaits response from the network. 21. MM CONNECTION ACTIVE (GROUP TRANSMIT MODE) (Only applicable for mobile stations supporting VGCS talking:) The MM sublayer has a RR connection on the VGCS channel to its peer entity on the network side. Only one MM connection is active. 22. WAIT FOR RR CONNECTION (GROUP TRANSMIT MODE) (Only applicable for mobile stations supporting VGCS talking:) The MM sublayer has requested to perform an uplink access on the VGCS channel. 23. LOCATION UPDATING PENDING (Only applicable for GPRS MS operation modes A and B; not shown in figure 4.1a) A location updating has been started using the combined GPRS attach procedure or the combined GPRS routing area updating procedure. 24. IMSI DETACH PENDING (Only applicable for GPRS MS operation modes A and B; not shown in figure 4.1a) An IMSI detach for non-GPRS services has been started using the combined GPRS detach procedure at not switching off. 25. RR CONNECTION RELEASE NOT ALLOWED (Only applicable for mobile stations supporting RRLP procedures (see 3GPP TS 44.031[ None ] [23b]) or LCS procedures over RRC (see 3GPP TS 25.331[ None ] [23c])). All MM connections are released by their CM entities, but the RR connection is maintained by the network due to an ongoing RRLP procedure or LCS procedure over RRC.

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

– MBS-SessionInfoList

The IE MBS-SessionInfoList provides the list of ongoing MBS broadcast sessions transmitted via broadcast MRB and, for each MBS broadcast session, the associated G-RNTI and scheduling information. MBS-SessionInfoList information element -- ASN1START -- TAG-MBS-SESSIONINFOLIST-START MBS-SessionInfoList-r17 ::= SEQUENCE (SIZE (1..maxNrofMBS-Session-r17)) OF MBS-SessionInfo-r17 MBS-SessionInfo-r17 ::= SEQUENCE { mbs-SessionId-r17 TMGI-r17, g-RNTI-r17 RNTI-Value, mrb-ListBroadcast-r17 MRB-ListBroadcast-r17, mtch-SchedulingInfo-r17 DRX-ConfigPTM-Index-r17 OPTIONAL, -- Need S mtch-NeighbourCell-r17 BIT STRING (SIZE(maxNeighCellMBS-r17)) OPTIONAL, -- Need S pdsch-ConfigIndex-r17 PDSCH-ConfigIndex-r17 OPTIONAL, -- Need S mtch-SSB-MappingWindowIndex-r17 MTCH-SSB-MappingWindowIndex-r17 OPTIONAL -- Cond MTCH-Mapping } DRX-ConfigPTM-Index-r17 ::= INTEGER (0..maxNrofDRX-ConfigPTM-1-r17) PDSCH-ConfigIndex-r17 ::= INTEGER (0..maxNrofPDSCH-ConfigPTM-1-r17) MTCH-SSB-MappingWindowIndex-r17 ::= INTEGER (0..maxNrofMTCH-SSB-MappingWindow-1-r17) MRB-ListBroadcast-r17 ::= SEQUENCE (SIZE (1..maxNrofMRB-Broadcast-r17)) OF MRB-InfoBroadcast-r17 MRB-InfoBroadcast-r17 ::= SEQUENCE { pdcp-Config-r17 MRB-PDCP-ConfigBroadcast-r17, rlc-Config-r17 MRB-RLC-ConfigBroadcast-r17, ... } MRB-PDCP-ConfigBroadcast-r17 ::= SEQUENCE { pdcp-SN-SizeDL-r17 ENUMERATED {len12bits} OPTIONAL, -- Need S headerCompression-r17 CHOICE { notUsed NULL, rohc SEQUENCE { maxCID-r17 INTEGER (1..16) DEFAULT 15, profiles-r17 SEQUENCE { profile0x0000-r17 BOOLEAN, profile0x0001-r17 BOOLEAN, profile0x0002-r17 BOOLEAN } } }, t-Reordering-r17 ENUMERATED {ms1, ms10, ms40, ms160, ms500, ms1000, ms1250, ms2750} OPTIONAL -- Need S } MRB-RLC-ConfigBroadcast-r17 ::= SEQUENCE { logicalChannelIdentity-r17 LogicalChannelIdentity, sn-FieldLength-r17 ENUMERATED {size6} OPTIONAL, -- Need S t-Reassembly-r17 T-Reassembly OPTIONAL -- Need S } -- TAG-MBS-SESSIONINFOLIST-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

– FrequencyInfoUL-SIB

The IE FrequencyInfoUL-SIB provides basic parameters of an uplink carrier and transmission thereon. FrequencyInfoUL-SIB information element -- ASN1START -- TAG-FREQUENCYINFOUL-SIB-START FrequencyInfoUL-SIB ::= SEQUENCE { frequencyBandList MultiFrequencyBandListNR-SIB OPTIONAL, -- Cond FDD-OrSUL absoluteFrequencyPointA ARFCN-ValueNR OPTIONAL, -- Cond FDD-OrSUL scs-SpecificCarrierList SEQUENCE (SIZE (1..maxSCSs)) OF SCS-SpecificCarrier, p-Max P-Max OPTIONAL, -- Need S frequencyShift7p5khz ENUMERATED {true} OPTIONAL, -- Cond FDD-TDD-OrSUL-Optional ..., [[ frequencyBandListAerial-r18 MultiFrequencyBandListNR-Aerial-SIB-r18 OPTIONAL -- Need S ]] } FrequencyInfoUL-SIB-v1760 ::= SEQUENCE { frequencyBandList-v1760 MultiFrequencyBandListNR-SIB-v1760 } -- TAG-FREQUENCYINFOUL-SIB-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

5.2.14.2.3 Nudsf_UnstructuredDataManagement_Create service operation

Service operation name: Nudsf_UnstructuredDataManagement_Create. Description: NF service consumer intends to insert a new user data record into the UDSF, e.g. AMF stores the context for registered UE(s) in the UDSF. Inputs, Required: Data Identifier, Data. Data Identifier uniquely identifies the data, which is created in the UDSF. Inputs, Optional: Validity time, Notification Endpoint. Validity time tells for how long the created data is valid. When validity time has expired, NF service consumer is notified and data is removed. Outputs, Required: Result. Outputs, Optional: None.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

5.2.14.2.3

10.1 FDD (Fixed Reference Channel)

The parameters specified in Table 10.1-1 are valid for all FDD tests unless otherwise stated. For the requirements defined in this section, the difference between CRS EPRE and the MBSFN RS EPRE should be set to 0 dB as the UE demodulation performance might be different when this condition is not met (e.g. in scenarios where power offsets are present, such as scenarios when reserved cells are present). Table 10.1-1: Common Test Parameters (FDD) All tests specified in 10.1 and 10.3 the applicability rules are defined as the following. The requirements in clause 10.3 are applicable to UEs that support FeMBMS. The test case applicability is in according to Table 10.1-2 depending on set of supported UE capabilities. Table 10.1-2: FeMBMS PMCH tests applicability For FeMBMS capable UEs, if corresponding tests listed in clause 10.1 or 10.3.1 or 10.3.2 are tested, the test coverage can be considered fulfilled without executing the corresponding tests listed in clause 10.3.3.

3GPP TS 36.101

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

RAN4

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

10.1

5.3.14 Unified Access Control 5.3.14.1 General

The purpose of this procedure is to perform access barring check for an access attempt associated with a given Access Category and one or more Access Identities upon request from upper layers according to TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [23] or the RRC layer. This procedure does not apply to IAB-MT and NCR-MT. This procedure does not apply to L2 U2N Relay UE initiating RRC connection establishment or RRC connection resume upon reception of any message from a L2 U2N remote UE via SL-RLC0 or SL-RLC1 in accordance to 5.3.3.1a or 5.3.13.1a. After a PCell change in RRC_CONNECTED the UE shall defer access barring checks until it has obtained SIB1 (as specified in 5.2.2.2) from the target cell.

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

5.3.14

6.3 Transport addresses

The transport layer address parameter is transported in the radio network application signalling procedures that result in establishment of transport bearer connections. The transport layer address parameter shall not be interpreted in the radio network application protocols and reveal the addressing format used in the transport layer. The formats of the transport layer addresses are further described in TS 38.414[ NG-RAN; NG data transport ] [5], TS 38.424[ NG-RAN; Xn data transport ] [6] and TS 38.474[ NG-RAN; F1 data transport ] [7].

3GPP TS 38.401

NG-RAN; Architecture description

RAN3

3GPP Series : 38 , Radio technology beyond LTE

6.3

– SCGFailureInformationEUTRA

The SCGFailureInformationEUTRA message is used to provide information regarding E-UTRA SCG failures detected by the UE. Signalling radio bearer: SRB1 RLC-SAP: AM Logical channel: DCCH Direction: UE to Network SCGFailureInformationEUTRA message -- ASN1START -- TAG-SCGFAILUREINFORMATIONEUTRA-START SCGFailureInformationEUTRA ::= SEQUENCE { criticalExtensions CHOICE { scgFailureInformationEUTRA SCGFailureInformationEUTRA-IEs, criticalExtensionsFuture SEQUENCE {} } } SCGFailureInformationEUTRA-IEs ::= SEQUENCE { failureReportSCG-EUTRA FailureReportSCG-EUTRA OPTIONAL, nonCriticalExtension SCGFailureInformationEUTRA-v1590-IEs OPTIONAL } SCGFailureInformationEUTRA-v1590-IEs ::= SEQUENCE { lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } FailureReportSCG-EUTRA ::= SEQUENCE { failureType ENUMERATED { t313-Expiry, randomAccessProblem,rlc-MaxNumRetx, scg-ChangeFailure, spare4, spare3, spare2, spare1}, measResultFreqListMRDC MeasResultFreqListFailMRDC OPTIONAL, measResultSCG-FailureMRDC OCTET STRING OPTIONAL, ..., [[ locationInfo-r16 LocationInfo-r16 OPTIONAL ]] } MeasResultFreqListFailMRDC ::= SEQUENCE (SIZE (1.. maxFreq)) OF MeasResult2EUTRA -- TAG-SCGFAILUREINFORMATIONEUTRA-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

9.5.5 Minimum requirement (with CSI process)

Each CSI process is associated with a CSI-RS resource and a CSI-IM resource as shown in Table 9.5.5-1. For UE supports one CSI process, CSI process 0 is configured for Test 1 and Test 2, but CSI process 1 is not configured for Test 2. The corresponding  requirements for Test 1 and Test 2 shall be fulfilled. The requirement on reported RI for CSI process 1 in Test 2 is not applicable. For UE supports multiple CSI processes, CSI process 0 is configured for Test 1 and CSI processes 0 and 1 are configured for Test 2. The corresponding  requirements for Test 1 and Test 2 shall be fulfilled, and also the requirement on reported RI for CSI process 1 in Test 2. Table 9.5.5-1: Configuration of CSI processes

3GPP TS 36.101

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

RAN4

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

9.5.5

5.7.3.3 Priority Level

The Priority Level associated with 5G QoS characteristics indicates a priority in scheduling resources among QoS Flows. The lowest Priority Level value corresponds to the highest priority. The Priority Level shall be used to differentiate between QoS Flows of the same UE, and it shall also be used to differentiate between QoS Flows from different UEs. In the case of congestion, when all QoS requirements cannot be fulfilled for one or more QoS Flows, the Priority Level shall be used to select for which QoS Flows the QoS requirements are prioritised such that a QoS Flow with Priority Level value N is priorized over QoS Flows with higher Priority Level values (i.e. N+1, N+2, etc).In the case of no congestion, the Priority Level should be used to define the resource distribution between QoS Flows. In addition, the scheduler may prioritize QoS Flows based on other parameters (e.g. resource type, radio condition) in order to optimize application performance and network capacity. Every standardized 5QI is associated with a default value for the Priority Level -specified in QoS characteristics Table 5.7.4.1). Priority Level may also be signalled together with a standardized 5QI to the -R)AN, and if it is received, it shall be used instead of the default value. Priority Level may also be signalled together with a pre-configured 5QI to the (R)AN, and if it is received, it shall be used instead of the pre-configured value.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.7.3.3

5.5.4.6 Abnormal cases in the UE

The following abnormal cases in the UE can be identified: a) Transmission failure of RELAY KEY REQUEST message or RELAY KEY AUTHENTICATION RESPONSE message indication from lower layers. The UE shall abort the authentication and key agreement procedure for 5G ProSe UE-to-network relay and perform the PC5 signalling protocol procedure as specified in subclause 7.2.2.5 of 3GPP 24.554 [19E]. b) Expiry of timer T3527. The UE shall, on the first expiry of the timer T3527, retransmit the RELAY KEY REQUEST message or the RELAY KEY AUTHENTICATION RESPONSE message and shall reset and start timer T3527. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3527, the procedure shall be aborted. c) Collision between the authentication and key agreement procedure for 5G ProSe UE-to-network relay or 5G ProSe UE-to-UE relay and de-registration procedure. The UE shall abort the authentication and key agreement procedure for 5G ProSe UE-to-network relay or 5G ProSe UE-to-UE relay, proceed with the network initiated de-registration procedure, and perform the PC5 signalling protocol procedure as specified in subclause 7.2.2.5 of 3GPP 24.554 [19E].

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

15.5.1.4 Adapting handover and/or reselection configuration

This function enables requesting of a change of handover and/or reselection parameters at target cell. The source cell that initialized the load balancing estimates if it is needed to change mobility configuration in the source and/or target cell. If the amendment is needed, the source cell initializes mobility negotiation procedure toward the target cell. The source cell informs the target cell about the new mobility setting and provides cause for the change (e.g. load balancing related request). The proposed change is expressed by the means of the difference (delta) between the current and the new values of the handover trigger. The handover trigger is the cell specific offset that corresponds to the threshold at which a cell initialises the handover preparation procedure. Cell reselection configuration may be amended to reflect changes in the HO setting. The target cell responds to the information from the source cell. The allowed delta range for HO trigger parameter may be carried in the failure response message. The source cell should consider the responses before executing the planned change of its mobility setting. All automatic changes on the HO and/or reselection parameters must be within the range allowed by OAM.

3GPP TS 38.300

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

RAN2

3GPP Series : 38 , Radio technology beyond LTE

15.5.1.4

5.8.10.3 Performing NR sidelink measurements 5.8.10.3.1 General

A UE shall derive NR sidelink measurement results by measuring one or multiple DMRS associated per PC5-RRC connection as configured by the peer UE associated, as described in 5.8.10.3.2. For all NR sidelink measurement results the UE applies the layer 3 filtering as specified in clause 5.5.3.2, before using the measured results for evaluation of reporting criteria and measurement reporting. In this release, only NR sidelink RSRP can be configured as trigger quantity and reporting quantity. The UE shall: 1> for each sl-MeasId included in the sl-MeasIdList within VarMeasConfigSL: 2> if the sl-MeasObject is associated to NR sidelink and the sl-RS-Type is set to dmrs: 3> derive the layer 3 filtered NR sidelink measurement result based on PSSCH DMRS for the trigger quantity and each measurement quantity indicated in sl-ReportQuantity using parameters from the associated sl-MeasObject, as described in 5.8.10.3.2. 2> perform the evaluation of reporting criteria as specified in 5.8.10.4.

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

5.8.10.3

5.6.1.5B Service request procedure for UE attached for access to RLOS not accepted by the network

If the service request for UE attached for access to RLOS cannot be accepted by the network, the UE shall perform the procedures as described in clause 5.6.1.5. Then if: a) the UE is in the same selected PLMN where the last service request was attempted and rejected; b) the service request procedure was rejected with an EMM cause value other than #9, #10 and #40; and c) timer T3346 is not running, the UE shall: a) detach locally, if not detached already, and perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6] to attempt EPS attach for access to RLOS via another PLMN. If the service request for UE attached for access to RLOS fails due to abnormal cases a), b), c) or e) in clause 5.6.1.6, the UE shall perform the procedures as described in clause 5.6.1.6. Then if the UE is in the same selected PLMN where the last service request was attempted, the UE shall: a) detach locally, if not detached already, and perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6] to attempt EPS attach for access to RLOS via another PLMN.

3GPP TS 24.301

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

CT WG1

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

5.6.1.5B

4.3.5.1 Non-roaming architecture

Figure 4.3.5.1-1 shows the non-roaming architecture for Service Exposure for EPC-5GC Interworking. If the UE is capable of mobility between EPS and 5GS, the network is expected to associate the UE with an SCEF+NEF node for Service Capability Exposure. Figure 4.3.5.1 1: Non-roaming Service Exposure Architecture for EPC-5GC Interworking NOTE 1: In Figure 4.3.5.1-1, Trust domain for SCEF+NEF is same as Trust domain for SCEF as defined in TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [36]. NOTE 2: In Figure 4.3.5.1-1, EPC Interface represents southbound interfaces between SCEF and EPC nodes e.g. the S6t interface between SCEF and HSS, the T6a interface between SCEF and MME, etc. All southbound interfaces from SCEF are defined in TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [36] and are not shown for the sake of simplicity. NOTE 3: In Figure 4.3.5.1-1, 5GC Interface represents southbound interfaces between NEF and 5GC Network Functions e.g. N29 interface between NEF and SMF, N30 interface between NEF and PCF, etc. All southbound interfaces from NEF are not shown for the sake of simplicity. NOTE 4: Interaction between the SCEF and NEF within the combined SCEF+NEF is required. For example, when the SCEF+NEF supports monitoring APIs, the SCEF and NEF need to share context and state information on a UE's configured monitoring events if the UE moves between from EPC and 5GC. NOTE 5: The north-bound APIs which can be supported by an EPC or 5GC network are discovered by the SCEF+NEF node via the CAPIF function and/or via local configuration of the SCEF+NEF node. Different sets of APIs can be supported by the two network types.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

4.3.5.1

5.3.1 Scrambling

For each codeword , the block of bits , where is the number of bits transmitted in codeword on the physical uplink shared channel in subframe(s)/slot/subslot, shall be scrambled with a UE-specific scrambling sequence prior to modulation, resulting in a block of scrambled bits according to the following pseudo code Set i = 0 while if // ACK/NACK or Rank Indication placeholder bits else if // ACK/NACK or Rank Indication repetition placeholder bits else // Data or channel quality coded bits, Rank Indication coded bits or ACK/NACK coded bits end if end if i = i + 1 end while where x and y are tags defined in TS 36.212[ Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and channel coding ] [3] clause 5.2.2.6 and where the scrambling sequence is given by clause 7.2. The scrambling sequence generator shall be initialised with at the start of each subframe where corresponds to the RNTI associated with the PUSCH transmission as described in clause 8 in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4]. For AUL PUSCH, For BL/CE UEs, - if the PUSCH transmission is using sub-PRB allocations, the scrambling sequence generator shall be initialised with at the first valid uplink subframe of every subframes comprising the allocated UL resource unit(s), where, and N is the number of BL/CE UL subframes for the PUSCH transmission as determined in clause 8.0 in [4]. - otherwise, the same scrambling sequence is applied per subframe to PUSCH for a given block of subframes. The subframe number of the first subframe in each block of consecutive subframes, denoted as , satisfies . For the block of subframes, the scrambling sequence generator shall be initialised with where and is the absolute subframe number of the first uplink subframe intended for PUSCH. The PUSCH transmission spans consecutive subframes including subframes that are not BL/CE UL subframes where the UE postpones the PUSCH transmission. For a BL/CE UE configured in CEModeA, . For a BL/CE UE configured with CEModeB, for frame structure type 1 and for frame structure type 2. For PUSCH with a subframe duration, up to two codewords can be transmitted in one subframe, i.e., . In the case of single-codeword transmission, .

3GPP TS 36.211

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

RAN1

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

5.3.1

9.9.4.21 PKMF address

The purpose of the PKMF address information element is to provide IP address of a ProSe Key Management Function associated with remote UEs connected to or disconnected from a UE acting as a ProSe UE-to-network relay. The PKMF address information element is coded as shown in figure 9.9.4.21.1 and table 9.9.4.21.1. The PKMF address is a type 4 information element with a minimum length of 3 octets and a maximum length of 19 octets. Figure 9.9.4.21.1: PKMF Address Table 9.9.4.21.1: PKMF Address information element If Address type indicates IPv4, the Address information in octet 4 to octet 7 contains the IPv4 address. Bit 8 of octet 4 represents the most significant bit of the IP address and bit 1 of octet 7 the least significant bit. If Address type indicates IPv6, the Address information in octet 4 to octet 19 contains the IPv6 address. Bit 8 of octet 4 represents the most significant bit of the IP address and bit 1 of octet 19 the least significant bit.

3GPP TS 24.301

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

CT WG1

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

9.9.4.21

9.11.4.36 N3QAI

The purpose of the N3QAI information element is to indicate a set of QoS parameters to be used by the UE for non-3GPP access network resource management behind the UE. The N3QAI information element is a type 6 information element with a minimum length of 9 octets. The maximum length for the information element is 65538 octets. The N3QAI information element is coded as shown in figure 9.11.4.36.1, figure 9.11.4.36.2, figure 9.11.4.36.3, figure 9.11.4.36.4, and table 9.11.4.36.1. Figure 9.11.4.36.1: N3QAI information element Figure 9.11.4.36.2: N3QAI Figure 9.11.4.36.3: N3QAI parameters list Figure 9.11.4.36.4: N3QAI parameter Table 9.11.4.36.1: N3QAI information element

3GPP TS 24.501

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

CT WG1

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

9.11.4.36

– UAC-BarringInfoSetIndex

The IE UAC-BarringInfoSetIndex provides the index of the entry in uac-BarringInfoSetList. Value 1 corresponds to the first entry in uac-BarringInfoSetList, value 2 corresponds to the second entry in this list and so on. An index value referring to an entry not included in uac-BarringInfoSetList indicates no barring. UAC-BarringInfoSetIndex information element -- ASN1START -- TAG-UAC-BARRINGINFOSETINDEX-START UAC-BarringInfoSetIndex ::= INTEGER (1..maxBarringInfoSet) -- TAG-UAC-BARRINGINFOSETINDEX-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–