Datasets:

Exploration-Lab

/

MM-TelecoBench

like 0

Follow

Exploration Lab 61

– MeasResultCellListSFTD-EUTRA

The IE MeasResultCellListSFTD-EUTRA consists of SFN and radio frame boundary difference between the PCell and an E-UTRA PSCell. MeasResultCellListSFTD-EUTRA information element -- ASN1START -- TAG-MEASRESULTCELLLISTSFTD-EUTRA-START MeasResultCellListSFTD-EUTRA ::= SEQUENCE (SIZE (1..maxCellSFTD)) OF MeasResultSFTD-EUTRA MeasResultSFTD-EUTRA ::= SEQUENCE { eutra-PhysCellId EUTRA-PhysCellId, sfn-OffsetResult INTEGER (0..1023), frameBoundaryOffsetResult INTEGER (-30720..30719), rsrp-Result RSRP-Range OPTIONAL } -- TAG-MEASRESULTCELLLISTSFTD-EUTRA-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

5.5.4.3 Event A2 (Serving becomes worse than threshold)

The UE shall: 1> consider the entering condition for this event to be satisfied when condition A2-1, as specified below, is fulfilled; 1> consider the leaving condition for this event to be satisfied when condition A2-2, as specified below, is fulfilled; 1> for this measurement, consider the serving cell indicated by the measObjectNR associated to this event. NOTE: If the serving cell indicated by the measObjectNR associated to this event is not detectable, then the UE should consider for the value of Ms the lowest value of the value range of the measurement quantity as the serving cell measurement. Inequality A2-1 (Entering condition) Ms + Hys < Thresh Inequality A2-2 (Leaving condition) Ms – Hys > Thresh The variables in the formula are defined as follows: Ms is the measurement result of the serving cell, not taking into account any offsets. Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigNR for this event). Thresh is the threshold parameter for this event (i.e. a2-Threshold as defined within reportConfigNR for this event). Ms is expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR. Hys is expressed in dB. Thresh is expressed in the same unit as Ms.

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

5.5.4.3

13.3 State Transitions and Mobility

As a general principle, on RRC_IDLE to RRC_CONNECTED transitions, RRC protection keys and UP protection keys are generated while keys for NAS protection as well as higher layer keys are assumed to be already available. These higher layer keys may have been established as a result of an AKA run, or as a result of a transfer from another AMF during handover or idle mode mobility see TS 23.502[ Procedures for the 5G System (5GS) ] [22]). On RRC_CONNECTED to RRC_IDLE transitions, the gNBs deletes the keys it stores for that UE such that state information for idle mode UEs only has to be maintained in AMF. It is also assumed that gNB does no longer store state information about the corresponding UE and deletes the current keys from its memory. In particular, on connected to idle transitions: - The gNB and UE delete NH, KgNB, KRRCint, KRRCenc, KUPint and KUPenc and related NCC; - AMF and UE keeps KAMF, KNASint and KNASenc stored. On mobility 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. On mobility 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 (see clause 13.1). In both cases, ARFCN-DL is the absolute frequency of SSB of the target PCell. It is not required to change the AS security algorithms during intra-gNB-CU handover. If the UE does not receive an indication of new AS security algorithms during an intra-gNB-CU handover, the UE shall continue to use the same algorithms as before the handover (see TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12]).

3GPP TS 38.300

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

RAN2

3GPP Series : 38 , Radio technology beyond LTE

13.3

5.8.9.1a.6.2 Additional Sidelink RLC Bearer addition/modification operation

For the additional Sidelink RLC bearer, whose addition conditions are met as in clause 5.8.9.1a.6.1, the UE capable of NR sidelink communication that is configured by upper layers to perform NR sidelink communication shall: 1> for groupcast and broadcast; or 1> for unicast, if the additional Sidelink RLC bearer addition was triggered due to the reception of the RRCReconfigurationSidelink message; or 1> for unicast, for DRB, after receiving the RRCReconfigurationCompleteSidelink message, if the additional Sidelink RLC bearer addition was triggered due to the configuration received within the sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR or indicated by upper layers; or 1> for unicast, for SRB, after receiving the RRCReconfigurationCompleteSidelink message, if the additional Sidelink RLC bearer addition was decided by UE: 2> establish an additional RLC entity for NR sidelink communication and configure it in accordance with each sl-RLC-ConfigPC5 received in the RRCReconfigurationSidelink or sl-RLC-Config received in sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR for SL DRB, and as specified in clause 9.1.1.4 for SL SRB; 2> if this procedure was for Sidelink DRB: 3> if this procedure was due to the reception of a RRCReconfigurationSidelink message: 4> configure the MAC entity with a logical channel in accordance with the sl-MAC-LogicalChannelConfigPC5 received in the RRCReconfigurationSidelink associated with the sidelink RLC entity; 3> else if this procedure was due to the reception of a RRCReconfigurationCompleteSidelink message: 4> configure the MAC entity with a logical channel associated with the sidelink RLC entity, in accordance with the sl-MAC-LogicalChannelConfig received in the sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR; 3> else (i.e. for groupcast/broadcast): 4> configure the MAC entity with a logical channel associated with the sidelink RLC entity, in accordance with the sl-MAC-LogicalChannelConfig received in the sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR and assign a new LCID to this logical channel. 3> if the UE is in RRC_CONNECTED: 4> indicate the allowed carriers for the two RLC bearers of the DRB, as indicated in sl-AllowedCarriers, to lower layer; 3> else: 4> indicate the allowed carriers for the two RLC bearers of the DRB, decided by UE implementation, to lower layer, where the carrier indicated in sl-FreqInfoList is used for the RLC bearer if the SL-TxProfile of at least one associated QoS flow for the sl-ServedRadioBearer indicates backwardsCompatible; 2> else (i.e., if this procedure was for Sidelink SRB): 3> configure the MAC entity with a logical channel associated with the sidelink RLC entity, as specified in clause 9.1.1.4. 3> if the UE is in RRC_CONNECTED: 4> indicate the allowed carriers for the two RLC bearers of the SRB, as indicated in allowedCarrierFreqSet1/allowedCarrierFreqSet2, to lower layer; 3> else: 4> indicate the allowed carriers for the two RLC bearers of the SRB, decided by UE implementation, to lower layer, where the carrier indicated in sl-FreqInfoList is used for the RLC bearer if the SL-TxProfile of at least one associated QoS flow for the sl-ServedRadioBearer indicates backwardsCompatible; For the additional Sidelink RLC bearer, whose modification conditions are met as in clause 5.8.9.1a.6.1, the UE capable of NR sidelink communication that is configured by upper layers to perform NR sidelink communication shall: 1> for groupcast and broadcast; or 1> for unicast, if the additional Sidelink RLC bearer modification was triggered due to the reception of the RRCReconfigurationSidelink message; or 1> for unicast, after receiving the RRCReconfigurationCompleteSidelink message, if the additional Sidelink RLC bearer modification was triggered due to the configuration received within the sl-ConfigDedicatedNR, SIB12 or SidelinkPreconfigNR: 2> reconfigure the RLC entity of the sidelink DRB, in accordance with the sl-RLC-ConfigPC5 received in the RRCReconfigurationSidelink or sl-RLC-Config received in sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR, if included; 2> reconfigure the logical channel of the sidelink DRB, in accordance with the sl-MAC-LogicalChannelConfigPC5 received in the RRCReconfigurationSidelink or sl-MAC-LogicalChannelConfig received in sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR, if included.

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

5.8.9.1a.6.2

5.8.9.7.1 PC5 Relay RLC channel release

The UE shall: 1> if the PC5 Relay RLC channel release was triggered after the reception of the RRCReconfigurationSidelink message; or 1> after receiving the RRCReconfigurationCompleteSidelink message, if the PC5 Relay RLC channel release was triggered due to the configuration received within the sl-ConfigDedicatedNR; or 1> for unicast in L2 U2U relay operation, if there is no end-to-end sidelink DRB(s) associated with this RLC channel: 2> for each SL-RLC-ChannelID in sl-RLC-ChannelToReleaseList received in sl-ConfigDedicatedNR within RRCReconfiguration, or for each SL-RLC-ChannelID included in the received sl-RLC-ChannelToReleaseListPC5 that is part of the current UE sidelink configuration, or for the RLC channel to be released: 3> release the RLC entity and the corresponding logical channel associated with the SL-RLC-ChannelID; 1> if the PC5 Relay RLC channel release was triggered for a specific destination by upper layers as specified in 5.8.9.5, or for a specific destination corresponding to the received sl-DestinationIdentityRemoteUE by upper layers as specified in 5.8.9.10.4, or due to sidelink RLF as specified in 5.8.9.3: 2> release the RLC entity and the corresponding logical channel associated with the SL-RLC-ChannelID of the specific destination;

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

5.8.9.7.1

4.15.2 External Exposure of Network Capabilities

The Network Exposure Function (NEF) supports external exposure of capabilities of network functions. External exposure can be categorized as Monitoring capability, Provisioning capability, Policy/Charging capability, network status reporting capability, Analytics reporting capability and Member UE selection assistance capability. The Monitoring capability is for monitoring of specific event for UE in 5GS and making such monitoring events information available for external exposure via the NEF. The Provisioning capability is for allowing external party to provision of information which can be used for the UE in 5GS. The Policy/Charging capability is for handling QoS and charging policy for the UE based on the request from external party. The Analytics capability is for allowing external party to acquire analytics information generated by 5G System. The Member UE selection assistance capability enables the NEF to consolidate information collected from other 5GC NFs, which fulfil the Member UE filtering criteria requested by the AF, to derive one or more lists of UE(s) and possibly additional information that assists AF for the selection of candidate members to participate in the application layer operation e.g. federated learning operation in the application layer. The details for the External Exposure of Analytics capabilities as well as interactions between NEF, external party and NWDAF are described in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50].

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.15.2

– CGI-InfoEUTRA

The IE CGI-InfoEUTRA indicates EUTRA cell access related information, which is reported by the UE as part of E-UTRA report CGI procedure. CGI-InfoEUTRA information element -- ASN1START -- TAG-CGI-INFOEUTRA-START CGI-InfoEUTRA ::= SEQUENCE { cgi-info-EPC SEQUENCE { cgi-info-EPC-legacy CellAccessRelatedInfo-EUTRA-EPC, cgi-info-EPC-list SEQUENCE (SIZE (1..maxPLMN)) OF CellAccessRelatedInfo-EUTRA-EPC OPTIONAL } OPTIONAL, cgi-info-5GC SEQUENCE (SIZE (1..maxPLMN)) OF CellAccessRelatedInfo-EUTRA-5GC OPTIONAL, freqBandIndicator FreqBandIndicatorEUTRA, multiBandInfoList MultiBandInfoListEUTRA OPTIONAL, freqBandIndicatorPriority ENUMERATED {true} OPTIONAL } -- TAG-CGI-INFOEUTRA-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

6.6.1 Scrambling

The block of bits, where , the number of bits transmitted on the physical broadcast channel, equals 1920 for normal cyclic prefix and 1728 for extended cyclic prefix, shall be scrambled with a cell-specific sequence prior to modulation, resulting in a block of scrambled bits according to where the scrambling sequence is given by clause 7.2. The scrambling sequence shall be initialised with in each radio frame fulfilling . For an MBMS-dedicated cell, the scrambling sequence shall be initialised with in each radio frame fulfilling .

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

8.7.12.1 FDD CA in licensed bands

The parameters specified in Table 8.7.12.1-1 are valid for all LAA CA SDR tests unless otherwise stated. Table 8.7.12.1-1: Common Test Parameters For UE not supporting 256QAM, the TB success rate shall be higher than 85% when PDSCH are scheduled with FRC in Table 8.7.12.1-2 with the downlink physical channel setup according to Annex C.3.2. For UE supporting 256QAM, the TB success rate shall be higher than 85% when PDSCH are scheduled with FRC in Table 8.7.12.1-3 with the downlink physical channel setup according to Annex C.3.2. For UE supporting 256QAM, the requirement with 64QAM is not applicable. For LAA SCell, per-CC separate FRCs are defined for different UE capability for endingDwPTS and secondSlotStartingPosition. The TB success rate is defined as 100%*NDL_correct_rx/ (NDL_newtx + NDL_retx), where NDL_newtx is the number of newly transmitted DL transport blocks, NDL_retx is the number of retransmitted DL transport blocks, and NDL_correct_rx is the number of correctly received DL transport blocks. The TB success rate shall be sustained during at least 300 frames. Table 8.7.12.1-2: Per-CC FRC for SDR test (64QAM) Table 8.7.12.1-3: Per-CC FRC for SDR test (256QAM) CA configuration, bandwidth combination and MIMO layer on each CC is determined by following procedure. - Select one CA bandwidth combination among all supported CA configurations with bandwidth combination and MIMO layer on each CC following the equation that leads to largest equivalent aggregated bandwidth among all CA bandwidth combinations supported by UE. Equivalent aggregated bandwidth is defined as where is number of CCs, and is MIMO layer and bandwidth of CC . - When there are multiple sets of {CA configuration, bandwidth combination, MIMO layer} with same largest aggregated bandwidth, select one among sets with largest number of 4 layer CCs.

3GPP TS 36.101

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

RAN4

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

8.7.12.1

5.30.2.15 Access to SNPN services for N5CW devices

Devices that do not support 5GC NAS signalling over WLAN access (referred to as "Non-5G-Capable over WLAN" devices, or N5CW devices for short), may access 5GC in an SNPN via a trusted WLAN access network that supports a TWIF function. To access SNPN services the N5CW device performs the following procedure: - A WLAN access network may advertise (e.g. with ANQP), not only the PLMNs with which "5G connectivity-without-NAS" is supported (as specified in clause 6.3.12a.1), but also the SNPNs with which "5G connectivity-without-NAS" is supported, as well as the related parameters and indications defined in clause 5.30.2.2 (i.e. human-readable network name(s), GIN(s), indication whether access using credentials from a Credentials Holder is supported, indication whether SNPN allows registration attempts from UEs that are not explicitly configured to select the SNPN). - The N5CW device initiates the access network selection procedure by sending an ANQP query to each discovered WLAN access network and constructs a list of available SNPNs with which "5G connectivity-without-NAS" is supported. This list contains the SNPNs with which "5G connectivity-without-NAS" is supported as advertised by all the discovered WLAN access networks. - The N5CW device selects an SNPN that is included in the list of available SNPNs with which "5G connectivity-without-NAS" is supported following the procedure in clause 5.30.2.4. - The N5CW device selects a WLAN access network (e.g. an SSID) that supports "5G connectivity-without-NAS" to the selected SNPN and initiates the "Initial Registration and PDU Session Establishment" procedure specified in clause 4.12b.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. If there are multiple WLAN access networks that support "5G connectivity-without-NAS" to the selected SNPN, then the N5CW device selects the highest priority WLAN access network from this list. To determine the priority of a WLAN access network, the N5CW device shall apply the WLANSP rules (if provided), and the procedure specified in clause 6.6.1.3 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45], "UE procedure for selecting a WLAN access based on WLANSP rules". If the N5CW device is not provided with WLANSP rules, the N5CW device determines the priority of a WLAN access network by using implementation means. NOTE: How the N5CW device selects credentials to use for SNPN access is implementation specific.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.30.2.15

5.5.3.3.4.3 Combined tracking area updating successful for EPS services only

Apart from the actions on the tracking area updating attempt counter, the description for tracking area for EPS services as specified in clause 5.5.3.2.4 shall be followed. In addition, the following description for location updating for non-EPS services applies. If, due to emergency services fallback (see 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [59], clause 4.13.4), there is a request for emergency services pending and the emergency bearer services indicator in the EPS network feature support IE indicates "emergency bearer services in S1 mode not supported", then the UE shall skip the requirements defined below in the present clause for the receipt of a TRACKING AREA UPDATE ACCEPT message including an EMM cause value, attempt to select GERAN or UTRAN radio access technology, select a setup message as defined in clause 5.3.7, proceed with appropriate MM specific procedures, and send the setup message. The UE receiving the TRACKING AREA UPDATE ACCEPT message takes one of the following actions depending on the EMM cause value: #2 (IMSI unknown in HSS) The UE shall stop T3430 if still running and shall reset the tracking area updating attempt counter. The UE shall set the update status to U3 ROAMING NOT ALLOWED and shall delete any TMSI, LAI and ciphering key sequence number. The UE shall enter state EMM-REGISTERED.NORMAL-SERVICE. The new MM state is MM IDLE. The USIM shall be considered as invalid for non-EPS services until switching off or the UICC containing the USIM is removed or the timer T3245 expires as described clause 5.3.7a. If 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, due to emergency services fallback (see 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [59]), there is a request for CS fallback call pending (see clause 5.3.7), the UE shall attempt to select GERAN or UTRAN radio access technology and attempt emergency call setup. A UE operating in CS/PS mode 1 of operation with "IMS voice not available" and without a persistent EPS bearer context shall disable the E-UTRA capability (see clause 4.5). A UE operating in CS/PS mode 1 of operation with "IMS voice not available" and with a persistent EPS bearer context shall, after the radio bearer associated with the persistent EPS bearer context has been released, disable the E-UTRA capability (see clause 4.5). #16 (MSC temporarily not reachable); or #17 (Network failure) The UE shall stop timer T3430 if still running, and shall enter state MM IDLE. 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.ATTEMPTING-TO-UPDATE-MM. When timer T3411 expires the combined tracking area updating procedure indicating "combined TA/LA updating with IMSI attach" is triggered again. If the tracking area updating attempt counter is equal to 5: - a UE operating in CS/PS mode 2 of operation and a UE operating in CS/PS mode 1 of operation with "IMS voice available" shall start timer T3402, shall set the EPS update status to EU1 UPDATED and shall enter state EMM-REGISTERED.ATTEMPTING-TO-UPDATE-MM. When timer T3402 expires the combined tracking area updating procedure indicating "combined TA/LA updating with IMSI attach" is triggered again; - a UE operating in CS/PS mode 1 of operation with "IMS voice not available" without a persistent EPS bearer context shall attempt to select GERAN or UTRAN radio access technology and proceed with appropriate MM or GMM specific procedures and disable the E-UTRA capability (see clause 4.5); - a UE operating in CS/PS mode 1 of operation with "IMS voice not available" and with a persistent EPS bearer context shall start timer T3402, shall set the EPS update status to EU1 UPDATED and shall enter state EMM-REGISTERED.ATTEMPTING-TO-UPDATE-MM. When timer T3402 expires the combined tracking area updating procedure indicating "combined TA/LA updating with IMSI attach" is triggered again. When the radio bearer associated with the persistent EPS bearer context has been released and the UE is registered for EPS services only, operating in CS/PS mode 1 of operation with "IMS voice not available", then the UE shall stop timer T3402, if already running, attempt to select GERAN or UTRAN radio access technology and proceed with appropriate MM or GMM specific procedures and disable the E-UTRA capability (see clause 4.5). #18 (CS domain 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 UE shall enter state MM IDLE and shall set the update status to U2 NOT UPDATED. A UE in CS/PS mode 1 of operation with "IMS voice not available" without a persistent EPS bearer context shall attempt to select GERAN or UTRAN radio access technology rather than E-UTRAN for the registered PLMN or equivalent PLMN and disable the E-UTRA capability (see clause 4.5). A UE in CS/PS mode 1 of operation with "IMS voice not available" and with a persistent EPS bearer context shall, after the radio bearer associated with the persistent EPS bearer context has been released, attempt to select GERAN or UTRAN radio access technology rather than E-UTRAN for the registered PLMN or equivalent PLMN and disable the E-UTRA capability (see clause 4.5). A UE in CS/PS mode 2 of operation and a UE operating in CS/PS mode 1 of operation with "IMS voice available" may provide a notification to the user or the upper layers that the CS domain is not available. The UE shall not attempt combined attach or combined tracking area updating procedure with current PLMN until switching off the UE or the UICC containing the USIM is removed. #22 (Congestion) The UE shall stop timer T3430 if still running. The tracking area updating attempt counter shall be set to 5. The UE shall start timer T3402, shall set the EPS update status to EU1 UPDATED, shall enter state EMM-REGISTERED.ATTEMPTING-TO-UPDATE-MM, shall enter state MM IDLE. Other EMM cause values and the case that no EMM cause IE was received are considered as abnormal cases. The combined tracking area updating procedure shall be considered as failed for non-EPS services. 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.4.3

6.5.3.3 UE requested bearer resource allocation procedure accepted by the network

Upon receipt of the BEARER RESOURCE ALLOCATION REQUEST message, the MME checks whether the resources requested by the UE can be established by verifying the EPS bearer identity given in the Linked EPS bearer identity IE to be any of the active default EPS bearer context(s). If the bearer resource allocation requested is accepted by the network, the MME shall initiate either a dedicated EPS bearer context activation procedure or an EPS bearer context modification procedure. Upon receipt of an ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST or MODIFY EPS BEARER CONTEXT REQUEST message with a PTI which matches the value used for the BEARER RESOURCE ALLOCATION REQUEST message, the UE shall stop timer T3480 and enter the state PROCEDURE TRANSACTION INACTIVE. The UE should ensure that the procedure transaction identity (PTI) assigned to this procedure is not released immediately. The way to achieve this is implementation dependent. While the PTI value is not released, the UE regards any received ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST or MODIFY EPS BEARER CONTEXT REQUEST message with the same PTI value as a network retransmission (see clause 7.3.1). If the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message is received, the UE shall verify that the EPS bearer identity given in the EPS bearer identity IE is not already used by any EPS bearer context. The UE shall then proceed as described in clause 6.4.2.3 or clause 6.4.2.4. If the MODIFY EPS BEARER CONTEXT REQUEST message is received, the UE verifies that the EPS bearer identity given in the EPS bearer identity IE is any of the active EPS bearer contexts. The UE shall then proceed as described in clause 6.4.3.3 or clause 6.4.3.4.

3GPP TS 24.301

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

CT WG1

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

6.5.3.3

4.2.4 Common architecture - management domain

Figure 4.2.4.1 provides an overview of the logical ubiquitous charging architecture for the management domain with MDAS. Figure 4.2.4.2 provides an overview of the logical ubiquitous charging architecture for the management (MDAS) and control domain (NWDAF). Figure 4.2.4.3 provides an overview of the logical ubiquitous charging architecture for the management with other management. Figure 4.2.4.1: Logical ubiquitous charging architecture for management domain Figure 4.2.4.2: Logical ubiquitous charging architecture for management domain (MDAS) and control domain (NWDAF) Figure 4.2.4.3: Logical ubiquitous charging architecture for other management layers This common charging architecture provides only a common logical view. The above figures illustrate three options on how CEF can consume those described. The CEF can either consume management services or services exposed by Network functions (e.g. NWDAF), and is also a consumer of Nchf, this is illustrated in figure 4.2.4.1 which can be adapted to requirements of the Service Provider, an additional scenario (depicted in 4.2.4.3) would allow the consumption of other management services (e.g. provisioning service, notification service) The Network Data Analytics Function (NWDAF) is specified in TS 23.501[ System architecture for the 5G System (5GS) ] [215]. The MnS producer, MnS consumer and MDAS are defined in TS 28.533[ Management and orchestration; Architecture framework ] [216]. The Charging Enablement Function (CEF) is defined in clause 4.3.3.3

3GPP TS 32.240

Telecommunication management; Charging management; Charging architecture and principles

SA WG5

3GPP Series : 32 , OAM&P and Charging

4.2.4

5.2 Requirements on the UE 5.2.1 General

The support and usage of ciphering and integrity protection between the UE and the ng-eNB is identical to the support and usage of ciphering and integrity protection between the UE and the eNB as specified in TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [10] with the following additional requirement(s): - The UE shall support the use of integrity protection with the ng-eNB over the Uu interface if it supports E-UTRA connected to 5GC. - The UE shall indicate its support of integrity protection with the ng-eNB if it supports E-UTRA connected to 5GC. The PEI shall be securely stored in the UE to ensure the integrity of the PEI.

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

5.2

8.13.3.5.1 Minimum Requirement for FDD PCell

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

3GPP TS 36.101

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

RAN4

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

8.13.3.5.1

6.10.3A.2 Mapping to resource elements

For the antenna port in a physical resource block assigned for the associated EPDCCH/MPDCCH, a part of the reference signal sequence shall be mapped to complex-valued modulation symbols in a subframe according to Normal cyclic prefix: where The sequence is given by Table 6.10.3A.2-1. Table 6.10.3A.2-1: The sequence for normal cyclic prefix Extended cyclic prefix: where The sequence is given by Table 6.10.3A.2-2. Table 6.10.3A.2-2: The sequence for extended cyclic prefix For extended cyclic prefix, demodulation reference signals are not supported on antenna ports 109 to 110. For the antenna port in a physical resource block assigned for the SPDCCH, a part of the reference signal sequence shall be mapped to complex-valued modulation symbols in a subframe according to the procedure used for UE-specific reference signals associated with subslot-PDSCH on antenna port described in clause 6.10.3.2 with the following amendments: - for slot-SPDCCH, , - for slot-SPDCCH in MBSFN subframes, the procedure used for the baseline pattern of UE-specific reference signals associated with subslot-PDSCH is applied - for slot-SPDCCH in normal subframes, the procedure used for the shifted pattern of UE-specific reference signals associated with subslot-PDSCH depending on the cell-specific frequency shift is applied. Resource elements used for transmission of demodulation reference signals to one UE on any of the antenna ports in the set , where or shall - not be used for transmission of EPDCCH/MPDCCH on any antenna port in the same slot, and - not be used for demodulation reference signals to the same UE on any antenna port other than those in in the same slot. Replacing antenna port numbers 7 – 10 by 107 – 110 in Figure 6.10.3.2-3 provides an illustration of the resource elements used for demodulation reference signals associated with EPDCCH/MPDCCH for normal cyclic prefix. Replacing antenna port numbers 7 – 8 by 107 – 108 in Figure 6.10.3.2-4 provides an illustration of the resource elements used for demodulation reference signals associated with EPDCCH/MPDCCH for extended cyclic prefix. For frame structure type 3, for EPDCCH in a subframe with the same duration as the DwPTS duration of a special subframe configuration, the mapping of the demodulation reference signals to the resource elements is the same as that for the corresponding special subframe configuration. For BL/CE UEs, if downlink resource reservation is enabled for the UE as specified in [9], then in case of MPDCCH transmission associated with C-RNTI or SPS C-RNTI using UE-specific MPDCCH search space, - If all OFDM symbols in a PRB are reserved, the demodulation reference signal transmission in that PRB is dropped.

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

6.3.5F.2 Relative power tolerance

Category NB1 and NB2 UE relative power control requirement is defined for NPRACH power step values of 0, 2, 4 and 6 dB. For NPRACH transmission, the relative tolerance is the ability of the UE transmitter to set its output power relatively to the power of the most recently transmitted preamble. The measurement period for the NPRACH preamble is specified in Table 6.3.4F.2-1. The requirements specified in Table 6.3.5F.2-1 apply when the power of the target and reference sub-frames are within the power range bounded by the Minimum output power as defined in subclause 6.3.2F and the maximum output power as defined in subclause 6.2.2F. Table 6.3.5F.2-1: Relative power tolerance for category NB1 and NB2 NPRACH transmission (normal conditions) The power step (ΔP) is defined as the difference in the calculated setting of the UE transmit power between the target and reference sub-frames. The error is the difference between ΔP and the power change measured at the UE antenna port with the power of the cell-specific reference signals kept constant. The error shall be less than the relative power tolerance specified in Table 6.3.5F.2-1.

3GPP TS 36.101

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

RAN4

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

6.3.5F.2

9.9.1.1.2 TDD

The following requirements apply to UE Category ≥1. For the parameters specified in Table 9.9.1.1.2-1, using the downlink physical channels specified in tables C.3.2-1 and C.3.2-2, the reported CQI value according to RC.1/RC.4 TDD in Table A.4-1 shall be in the range of ±1 of the reported median more than 90% of the time. If the PDSCH BLER using the transport format indicated by median CQI is less than or equal to 0.1, the BLER using the transport format indicated by the (median CQI + 1) shall be greater than 0.1. If the PDSCH BLER using the transport format indicated by the median CQI is greater than 0.1, the BLER using transport format indicated by (median CQI – 1) shall be less than or equal to 0.1. Table 9.9.1.1.2-1: PUCCH 1-0 static test (TDD)

3GPP TS 36.101

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

RAN4

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

9.9.1.1.2

– SidelinkUEInformationNR

The SidelinkUEinformationNR message is used for the indication of NR sidelink UE information to the network. Signalling radio bearer: SRB1 RLC-SAP: AM Logical channel: DCCH Direction: UE to Network SidelinkUEInformationNR message -- ASN1START -- TAG-SIDELINKUEINFORMATIONNR-START SidelinkUEInformationNR-r16::= SEQUENCE { criticalExtensions CHOICE { sidelinkUEInformationNR-r16 SidelinkUEInformationNR-r16-IEs, criticalExtensionsFuture SEQUENCE {} } } SidelinkUEInformationNR-r16-IEs ::= SEQUENCE { sl-RxInterestedFreqList-r16 SL-InterestedFreqList-r16 OPTIONAL, sl-TxResourceReqList-r16 SL-TxResourceReqList-r16 OPTIONAL, sl-FailureList-r16 SL-FailureList-r16 OPTIONAL, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SidelinkUEInformationNR-v1700-IEs OPTIONAL } SidelinkUEInformationNR-v1700-IEs ::= SEQUENCE { sl-TxResourceReqList-v1700 SL-TxResourceReqList-v1700 OPTIONAL, sl-RxDRX-ReportList-v1700 SL-RxDRX-ReportList-v1700 OPTIONAL, sl-RxInterestedGC-BC-DestList-r17 SL-RxInterestedGC-BC-DestList-r17 OPTIONAL, sl-RxInterestedFreqListDisc-r17 SL-InterestedFreqList-r16 OPTIONAL, sl-TxResourceReqListDisc-r17 SL-TxResourceReqListDisc-r17 OPTIONAL, sl-TxResourceReqListCommRelay-r17 SL-TxResourceReqListCommRelay-r17 OPTIONAL, ue-Type-r17 ENUMERATED {relayUE, remoteUE} OPTIONAL, sl-SourceIdentityRemoteUE-r17 SL-SourceIdentity-r17 OPTIONAL, nonCriticalExtension SidelinkUEInformationNR-v1800-IEs OPTIONAL } SidelinkUEInformationNR-v1800-IEs ::= SEQUENCE { sl-CarrierFailureList-r18 SL-CarrierFailureList-r18 OPTIONAL, sl-TxResourceReqL2-U2U-r18 SL-TxResourceReqL2-U2U-r18 OPTIONAL, sl-PosRxInterestedFreqList-r18 SL-InterestedFreqList-r16 OPTIONAL, sl-PosTxResourceReqList-r18 SL-TxResourceReqList-r16 OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } SL-InterestedFreqList-r16 ::= SEQUENCE (SIZE (1..maxNrofFreqSL-r16)) OF INTEGER (1..maxNrofFreqSL-r16) SL-TxResourceReqList-r16 ::= SEQUENCE (SIZE (1..maxNrofSL-Dest-r16)) OF SL-TxResourceReq-r16 SL-TxResourceReq-r16 ::= SEQUENCE { sl-DestinationIdentity-r16 SL-DestinationIdentity-r16, sl-CastType-r16 ENUMERATED {broadcast, groupcast, unicast, spare1}, sl-RLC-ModeIndicationList-r16 SEQUENCE (SIZE (1.. maxNrofSLRB-r16)) OF SL-RLC-ModeIndication-r16 OPTIONAL, sl-QoS-InfoList-r16 SEQUENCE (SIZE (1..maxNrofSL-QFIsPerDest-r16)) OF SL-QoS-Info-r16 OPTIONAL, sl-TypeTxSyncList-r16 SEQUENCE (SIZE (1..maxNrofFreqSL-r16)) OF SL-TypeTxSync-r16 OPTIONAL, sl-TxInterestedFreqList-r16 SL-TxInterestedFreqList-r16 OPTIONAL, sl-CapabilityInformationSidelink-r16 OCTET STRING OPTIONAL } SL-TxResourceReqList-v1700 ::= SEQUENCE (SIZE (1..maxNrofSL-Dest-r16)) OF SL-TxResourceReq-v1700 SL-RxDRX-ReportList-v1700 ::= SEQUENCE (SIZE (1..maxNrofSL-Dest-r16)) OF SL-RxDRX-Report-v1700 SL-TxResourceReq-v1700 ::= SEQUENCE { sl-DRX-InfoFromRxList-r17 SEQUENCE (SIZE (1..maxNrofSL-RxInfoSet-r17)) OF SL-DRX-ConfigUC-SemiStatic-r17 OPTIONAL, sl-DRX-Indication-r17 ENUMERATED {on, off} OPTIONAL, ..., [[ sl-QoS-InfoList-v1800 SEQUENCE (SIZE (1..maxNrofSL-QFIsPerDest-r16)) OF SL-QoS-Info-v1800 OPTIONAL ]] } SL-RxDRX-Report-v1700 ::= SEQUENCE { sl-DRX-ConfigFromTx-r17 SL-DRX-ConfigUC-SemiStatic-r17, ...} SL-RxInterestedGC-BC-DestList-r17 ::= SEQUENCE (SIZE (1..maxNrofSL-Dest-r16)) OF SL-RxInterestedGC-BC-Dest-r17 SL-RxInterestedGC-BC-Dest-r17 ::= SEQUENCE { sl-RxInterestedQoS-InfoList-r17 SEQUENCE (SIZE (1..maxNrofSL-QFIsPerDest-r16)) OF SL-QoS-Info-r16, sl-DestinationIdentity-r16 SL-DestinationIdentity-r16 } SL-TxResourceReqListDisc-r17 ::= SEQUENCE (SIZE (1..maxNrofSL-Dest-r16)) OF SL-TxResourceReqDisc-r17 SL-TxResourceReqDisc-r17 ::= SEQUENCE { sl-DestinationIdentityDisc-r17 SL-DestinationIdentity-r16, sl-SourceIdentityRelayUE-r17 SL-SourceIdentity-r17 OPTIONAL, sl-CastTypeDisc-r17 ENUMERATED {broadcast, groupcast, unicast, spare1}, sl-TxInterestedFreqListDisc-r17 SL-TxInterestedFreqList-r16, sl-TypeTxSyncListDisc-r17 SEQUENCE (SIZE (1..maxNrofFreqSL-r16)) OF SL-TypeTxSync-r16, sl-DiscoveryType-r17 ENUMERATED {relay, non-Relay}, ... } SL-TxResourceReqListCommRelay-r17 ::= SEQUENCE (SIZE (1..maxNrofSL-Dest-r16)) OF SL-TxResourceReqCommRelayInfo-r17 SL-TxResourceReqCommRelayInfo-r17 ::= SEQUENCE { sl-RelayDRXConfig-r17 SL-TxResourceReq-v1700 OPTIONAL, sl-TxResourceReqCommRelay-r17 SL-TxResourceReqCommRelay-r17 } SL-TxResourceReqCommRelay-r17 ::= CHOICE { sl-TxResourceReqL2U2N-Relay-r17 SL-TxResourceReqL2U2N-Relay-r17, sl-TxResourceReqL3U2N-Relay-r17 SL-TxResourceReq-r16 } SL-TxResourceReqL2U2N-Relay-r17 ::= SEQUENCE { sl-DestinationIdentityL2U2N-r17 SL-DestinationIdentity-r16 OPTIONAL, sl-TxInterestedFreqListL2U2N-r17 SL-TxInterestedFreqList-r16, sl-TypeTxSyncListL2U2N-r17 SEQUENCE (SIZE (1..maxNrofFreqSL-r16)) OF SL-TypeTxSync-r16, sl-LocalID-Request-r17 ENUMERATED {true} OPTIONAL, sl-PagingIdentityRemoteUE-r17 SL-PagingIdentityRemoteUE-r17 OPTIONAL, sl-CapabilityInformationSidelink-r17 OCTET STRING OPTIONAL, ... } SL-TxResourceReqL2-U2U-r18 ::= SEQUENCE { sl-DestinationIdentityL2-U2U-r18 SL-DestinationIdentity-r16 OPTIONAL, sl-TxInterestedFreqListL2-U2U-r18 SL-TxInterestedFreqList-r16, sl-TypeTxSyncListL2-U2U-r18 SEQUENCE (SIZE (1..maxNrofFreqSL-r16)) OF SL-TypeTxSync-r16, sl-CapabilityInformationSidelink-r18 OCTET STRING OPTIONAL, sl-U2U-InfoList-r18 SEQUENCE (SIZE (1.. maxNrofRemoteUE-r17)) OF SL-U2U-Info-r18 OPTIONAL, ... } SL-U2U-Info-r18 ::= SEQUENCE { sl-U2U-Identity-r18 CHOICE { sl-TargetUE-Identity-r18 SL-DestinationIdentity-r16, sl-SourceUE-Identity-r18 SL-SourceIdentity-r17 }, sl-E2E-QoS-InfoList-r18 SEQUENCE (SIZE (1.. maxNrofSL-QFIsPerDest-r16)) OF SL-QoS-Info-r16 OPTIONAL, sl-PerHop-QoS-InfoList-r18 SEQUENCE (SIZE (1.. maxNrofSL-QFIsPerDest-r16)) OF SL-SplitQoS-Info-r18 OPTIONAL, sl-PerSLRB-QoS-InfoList-r18 SEQUENCE (SIZE (1.. maxNrofSLRB-r16)) OF SL-PerSLRB-QoS-Info-r18 OPTIONAL } SL-TxInterestedFreqList-r16 ::= SEQUENCE (SIZE (1..maxNrofFreqSL-r16)) OF INTEGER (1..maxNrofFreqSL-r16) SL-QoS-Info-r16 ::= SEQUENCE { sl-QoS-FlowIdentity-r16 SL-QoS-FlowIdentity-r16, sl-QoS-Profile-r16 SL-QoS-Profile-r16 OPTIONAL } SL-QoS-Info-v1800 ::= SEQUENCE { sl-QoS-FlowIdentity-r18 SL-QoS-FlowIdentity-r16, sl-TxInterestedFreqList-v1800 SL-TxInterestedFreqList-r16 OPTIONAL, sl-TxProfile-v1800 ENUMERATED {backwardsCompatible, backwardsIncompatible} OPTIONAL, ... } SL-RLC-ModeIndication-r16 ::= SEQUENCE { sl-Mode-r16 CHOICE { sl-AM-Mode-r16 NULL, sl-UM-Mode-r16 NULL }, sl-QoS-InfoList-r16 SEQUENCE (SIZE (1..maxNrofSL-QFIsPerDest-r16)) OF SL-QoS-Info-r16 } SL-FailureList-r16 ::= SEQUENCE (SIZE (1..maxNrofSL-Dest-r16)) OF SL-Failure-r16 SL-Failure-r16 ::= SEQUENCE { sl-DestinationIdentity-r16 SL-DestinationIdentity-r16, sl-Failure-r16 ENUMERATED {rlf,configFailure, drxReject-v1710, spare5, spare4, spare3, spare2, spare1} } SL-CarrierFailureList-r18 ::= SEQUENCE (SIZE (1..maxNrofSL-Dest-r16)) OF SL-CarrierFailure-r18 SL-CarrierFailure-r18 ::= SEQUENCE { sl-DestinationIdentity-r18 SL-DestinationIdentity-r16, sl-CarrierFailure-r18 SEQUENCE (SIZE (1..maxNrofFreqSL-r16)) OF INTEGER (1..maxNrofFreqSL-r16) } SL-SplitQoS-Info-r18 ::= SEQUENCE { sl-QoS-FlowIdentity-r18 SL-QoS-FlowIdentity-r16, sl-SplitPacketDelayBudget-r18 INTEGER (0..1023) OPTIONAL, ... } SL-PerSLRB-QoS-Info-r18 ::= SEQUENCE { sl-RemoteUE-SLRB-Identity-r18 SLRB-Uu-ConfigIndex-r16, sl-QoS-ProfilePerSLRB-r18 SL-QoS-Profile-r16 OPTIONAL } -- TAG-SIDELINKUEINFORMATIONNR-STOP -- ASN1STOP Editor's Note: Whether the per-SLRB QoS is reported in a list of E2E connections or all in one big list can be further checked in maintenance. Editor's Note: Whether to differentiate U2U discovery and U2N discovery can be checked in maintenance. Editor's note: The carrier mapping for sl-RxInterestedFreqList is pending R2 discussion. Editor's note: The carrier mapping for sl-TxInterestedFreqList is pending R2 discussion.

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

8.11 Demodulation (UE supporting coverage enhancement)

The requirements for UE DL Category M1 in this sub-clause are defined based on the simulation results with UE DL Category M1 unless otherwise stated. The requirements for UE DL Category M2 in this sub-clause are defined based on the simulation results with UE DL Category M2 unless otherwise stated. The requirements of UE DL Category M1 in this sub-clause are applicable for UE DL Category M2, UE DL Category 1bis and Category 0, as specified in the applicability rule in the sub-clause 8.1.2.8A. The requirements of UE DL Category M2 in this sub-clause are applicable for UE DL Category 1bis and Category 0, as specified in the applicability rule in the sub-clause 8.1.2.8A.

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

4.3.17.8a Support of PDN type Ethernet

The support of Ethernet PDN type relies upon the selection of a P-GW that supports combined PGW+SMF functionality specified in TS 23.501[ System architecture for the 5G System (5GS) ] [83], TS 23.502[ Procedures for the 5G System (5GS) ] [84] and TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [88]. This functionality may be supported by a PLMN even if it has no NG-RAN coverage, however, it does require that the subscriber has a subscription record in the 5GS UDM. This feature is described in clause 5.6.10.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [83]. For PDN connection with Ethernet PDN type, IP address allocation is not needed. In contrast to the Non-IP PDN type, EPS Dedicated Bearers are supported for the Ethernet PDN type (including the TFT as described in clause 4.7.2.1). The details about the TFT packet filter(s) are described in clause 5.7.6.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [83]. For PDN connection of Ethernet type, dynamic PCC is applied as described in clause 4.7.5 with the following differences: - Dynamic PCC specified in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [88] is applied, i.e. the PCEF interacts with the PCF using N7 interface as described in TS 23.501[ System architecture for the 5G System (5GS) ] [83], and the PCEF does not interact with the PCRF using Gx interface as specified in TS 23.203[ Policy and charging control architecture ] [6]. - The SDF template included in the PCC rule(s) uses Ethernet packet filter as specified in TS 23.501[ System architecture for the 5G System (5GS) ] [83]. - The description related to IP address configuration is not applicable. Dedicated Core Network functionality (see clause 4.3.25) can be used to avoid the need for all MMEs in the PLMN to be upgraded to support Ethernet PDN Type. If the UE's attempt to use the Ethernet PDN Type is rejected by the network, the UE may attempt to gain service by requesting the Non-IP PDN type. Ethernet PDN Type is not supported in GERAN/UTRAN. If the UE only has an Ethernet PDN connection established, mobility to GERAN/UTRAN should be prevented. To do this, the MME shall indicate to the eNodeB in Handover Restriction List that GERAN/UTRAN is restricted. For PDN connection with Ethernet PDN type, mobility to Non 3GPP access to EPC is not supported.

3GPP TS 23.401

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

SA WG2

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

4.3.17.8a

4.3.2 Base Station Identify Code (BSIC)

The base station identity code is a local colour code that allows an MS to distinguish between different neighbouring base stations. BSIC is a 6 bit code which is structured as shown in Figure 6. Exceptions apply to networks supporting EC-GSM-IoT or PEO and for mobile stations in EC or PEO operation (see 3GPP TS 43.064[ None ] [112]) where the BSIC is a 9 bit code which is structured as shown in Figure 6a. Figure 6: Structure of 6 bit BSIC Figure 6a: Structure of 9 bit BSIC In the definition of the NCC, care should be taken to ensure that the same NCC is not used in adjacent PLMNs which may use the same BCCH carrier frequencies in neighbouring areas. Therefore, to prevent potential deadlocks, a definition of the NCC appears in annex A. This annex will be reviewed in a co-ordinated manner when a PLMN is created. In addition to the above, the GERAN networks should be configured so that: - in a cell shared between different PLMNs as per GERAN network sharing (see 3GPP TS 44.018[ None ] [99] and 3GPP TS 44.060[ None ] [100]), the NCC used in this cell is different from the NCC used in the neighbouring non-shared cells of these PLMNs; and that - these PLMNs use different NCCs in non-shared cells neighbouring this shared cell. Furthermore, GERAN networks supporting the 9 bit BSIC shall also support the 6 bit BSIC field and when supporting both the 6 bit BSIC and 9 bit BSIC the network shall ensure that the NCC and BCC parts are identical between the 6 bit and 9 bit BSIC fields.

3GPP TS 23.003

Numbering, addressing and identification

CT WG4

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

4.3.2

12.3.9.3.1 Description

When performing message throttling: - GTP requests related to priority traffic (i.e. eMPS as described in 3GPP TS 22.153[ Multimedia priority service ] [62]) and emergency have the highest priority. Depending on regional/national requirements and network operator policy, these GTP requests shall be the last to be throttled, when applying traffic reduction, and the priority traffic shall be exempted from throttling due to GTP overload control up to the point where the requested traffic reduction cannot be achieved without throttling the priority traffic; NOTE 1: For non-3GPP access, eMPS traffic is determined based on the MPS subscription from the UE USIM as specified in 3GPP TS 24.302[ Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networks; Stage 3 ] [63] clause 7.2.2.1 and clause 7.4.1.1 or the MPS subscription for the UE from the HSS as specified in 3GPP TS 29.273[ Evolved Packet System (EPS); 3GPP EPS AAA interfaces ] [68] clause 5.1.2.1.2 and clause 7.1.2.1.2. - for other types of sessions, messages throttling should consider the relative priority of the messages so that the messages which are considered as low priority are considered for throttling before the other messages. The relative priority of the messages may be derived from the relative priority of the procedure for which the message is being sent (as specified in clause 12.3.9.3.2) or may be derived from the session parameters (as specified in clause 12.3.9.3.3). NOTE 2: A random throttling mechanism, i.e. discarding the messages without any special consideration, could result in an overall poor congestion mitigation mechanism and bad user experience. An overloaded node may also apply these message prioritization schemes when handling incoming initial messages during an overloaded condition, as part of the self-protection mechanism (see clause 12.3.10.2.3).

3GPP TS 29.274

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

CT WG4

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

12.3.9.3.1

15.3.3 Automatic Neighbour Cell Relation Function 15.3.3.1 General

The purpose of ANR function is to relieve the operator from the burden of manually managing NCRs. Figure 15.3.3.1-1 shows ANR and its environment: Figure 15.3.3.1-1: Interaction between gNB and OAM due to ANR The ANR function resides in the gNB and manages the Neighbour Cell Relation Table (NCRT). Located within ANR, the Neighbour Detection Function finds new neighbours and adds them to the NCRT. ANR also contains the Neighbour Removal Function which removes outdated NCRs. The Neighbour Detection Function and the Neighbour Removal Function are implementation specific. An existing NCR from a source cell to a target cell means that gNB controlling the source cell: a) Knows the global and physical IDs (e.g. NR CGI/NR PCI, ECGI/PCI) of the target cell; and b) Has an entry in the NCRT for the source cell identifying the target cell; and c) Has the attributes in this NCRT entry defined, either by OAM or set to default values. NCRs are cell-to-cell relations, while an Xn link is set up between two gNBs. Neighbour Cell Relations are unidirectional, while an Xn link is bidirectional. NOTE: The neighbour information exchange, which occurs during the Xn Setup procedure or in the gNB Configuration Update procedure, may be used for ANR purpose. The ANR function also allows OAM to manage the NCRT. OAM can add and delete NCRs. It can also change the attributes of the NCRT. The OAM system is informed about changes in the NCRT.

3GPP TS 38.300

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

RAN2

3GPP Series : 38 , Radio technology beyond LTE

15.3.3

9.3.18.2 Release (mobile station to network direction)

This message is sent from the mobile station to the network to indicate that the mobile station intends to release the transaction identifier, and that the receiving equipment shall release the transaction identifier after sending RELEASE COMPLETE. See table 9.68a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Message type: RELEASE Significance: local (note) Direction: mobile station to network direction Table 9.68a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : RELEASE message content (mobile station to network direction) NOTE: This message has local significance; however, it may carry information of global significance when used as the first call clearing message.

3GPP TS 24.008

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

CT WG1

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

9.3.18.2

9.9.2.2.1 FDD

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

3GPP TS 36.101

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

RAN4

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

9.9.2.2.1

5.36 RIM Information Transfer

The purpose of RIM Information Transfer is to enable the transfer of RIM information between two RAN nodes via 5GC. The RIM Information Transfer is specified in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [34]. When the source AMF receives RIM information from source NG-RAN towards target NG-RAN, the source AMF forwards the RIM information to the target AMF, as described in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [34] and TS 29.518[ 5G System; Access and Mobility Management Services; Stage 3 ] [71]. The AMF does not interpret the transferred RIM information.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.36

16a.3.1 IP PDP type

Figure 25a represents the Diameter message flows between a GGSN and a Diameter server. NOTE 1: If some external applications require Diameter Accounting request (Start) information before they can process user packets, then the selected APN (GGSN) may be configured in such a way that the GGSN drops user data until the Accounting Answer (START) is received from the Diameter server. The GGSN may wait for the Accounting Answer (START) before sending the CreatePDPContextResponse. The GGSN may reject the PDP context if the Accounting Answer (START) is not received. NOTE 2: Separate accounting and authentication servers may be used. NOTE 3: The AA-Request message shall be used for primary PDP context only. NOTE 4: The Accounting-Request (Start) message may be sent at a later stage, e.g. after IPv4 address has been assigned and PDP Context updated, in case of IP address allocation via DHCPv4 after successful PDP context activation signalling. Figure 25a: Diameter message flow for PDP type IP (successful user authentication case) When a GGSN receives a Create PDP Context Request message for a given APN, the GGSN may (depending on the configuration for this APN) send a Diameter AA-Request to a Diameter server. The Diameter server authenticates and authorizes the user. If Diameter is also responsible for IPv4 address and/or IPv6 prefix allocation the Diameter server shall return the allocated IPv4 address and/or IPv6 prefix in the AA-Answer message. The AA-Request and AA-Answer messages are only used for the primary PDP context. When PDP type is IPv4v6 and deferred IPv4 addressing via IPv4 address pool in the AAA server is used, the GGSN may intiate Diameter re-authorization procedures after successful initial attach for the purpose of IPv4 address allocation or to renew the lease for a previously allocated IPv4 address. In this case, the GGSN shall set the Session-Id to the value used in the initial access request, the Auth-Request-Type AVP to "AUTHORIZE_ONLY" and the 3GPP-Allocate-IP-Type AVP to the type of IP address to be allocated in the AA-Request message sent to the AAA server. See subclause 16.4.7.2 for the conditions to use 3GPP-Allocate-IP-Type AVP in AA-Request messages. If the GGSN is using DHCPv4 signalling towards the MS and the Diameter server includes the Session-Timeout attribute in the Access-Accept, the GGSN may use the Session-Timeout value as the DHCP lease time. The GGSN shall not set the DHCPv4 lease time value higher than the Session-Timeout value. The GGSN may renew the DHCP lease to the MS without re-authorization towards the AAA server providing that the new lease expiry is no later than the Session-Timeout timer expiry. If the GGSN wishes to extend the lease time beyond the current Session-Timeout expiry, it shall initiate a new AAA re-authorization. Even if the GGSN was not involved in user authentication (e.g. transparent network access mode), it may send a Diameter Accounting-Request (START) message to a Diameter server. If no Diameter session is already open for the user a Diameter session needs to be activated, otherwise the existing Diameter session is used to send the Accounting-Request (START). The NSAPI will identify the particular PDP context this accounting refers to. The Accounting-Request message also indicates to the Diameter server that the user session has started. This message contains parameters, e.g. the tuple which includes the user-id, IPv4 address and/or IPv6 prefix, and the MSISDN to be used by application servers (e.g. WAP gateway) in order to identify the user. If some external applications require Diameter Accounting request (Start) information before they can process user packets, then the selected APN (GGSN) may be configured in such a way that the GGSN drops user data until the Accounting Answer (START) is received from the Diameter server. The GGSN may wait for the Accounting Answer (START) before sending the CreatePDPContextResponse. The GGSN may reject the PDP context if the Accounting Answer (START) is not received. The authentication and accounting servers may be separately configured for each APN. For PDP type IPv4, at IPv4 address allocation via DHCP4 signalling between the TE and the PDN, no IPv4 address is available at PDP context activation. In that case the GGSN may wait to send the Accounting-Request (START) message until the TE receives its IP address in a DHCPACK. For PDP type IPv4v6 and deferred IPv4 addressing, when the IPv4 address is allocated or re-allocated, the accounting session that was established for the IPv6 prefix allocation shall be used to inform the accounting server about the allocated IPv4 address by sending Diameter Accounting-Request Interim-Update with the Framed-IP-Address AVP and its value field containing the allocated IPv4 address. When the GGSN receives a Delete PDP Context Request message and providing a Diameter Accounting-Request (START) message was sent previously, the GGSN shall send a Diameter Accounting-Request (STOP) message to the Diameter server, which indicates the termination of this particular user accounting session. The NSAPI will identify the particular PDP context this accounting refers to. The GGSN shall immediately send a Delete PDP context response, without waiting for an Accounting-Answer (STOP) message from the Diameter server. If this was the last PDP context for that PDP address, the GGSN shall additionally send an STR message to the Diameter server. The Diameter server shall reply with an STA and shall deallocate the IP address or IPv6 prefix (if any) initially allocated to the subscriber. For PDP type IPv4v6 and deferred IPv4 addressing, when the GGSN receives a message from the MS or the network indicating the release of the IPv4 address (e.g. receiving DHCPRELEASE) or decides to release the IPv4 address on its own (e.g. due to DHCP lease timer expiry for GGSN assigned IPv4 address), the GGSN shall inform the accounting server about the deallocation of the IPv4 address by sending Diameter Accounting-Request Interim-Update without the Framed-IP-Address AVP.

3GPP TS 29.061

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

CT WG3

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

16a.3.1

4.15.13.3 Specific procedure for QoS Member UE filtering criteria 4.15.13.3.1 General

An AF may invoke Nnef_MemberUESelectionAssistance_Subscribe service operation with one QoS filtering criterion for receiving a list of UEs that match or exceed such criteria. In addition to the mandatory parameters, the AF also includes in the request: - QoS filtering criteria. - Optionally, an Area of Interest: location area of the candidate UEs. The QoS filtering criteria includes: - a traffic descriptor (e.g. Application ID). - Optionally, DNN. - Optionally, S-NSSAI. And one or more of the QoS parameters subject to QoS monitoring (see list in clause 5.45 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]). The determination of the list of UEs that match or exceed the QoS filtering criteria and are optionally located in the AoI in real time, for the duration of the subscription, is further described in clause 4.15.13.3.3.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.15.13.3

4.6.3 Session management aspects 4.6.3.0 General

In order to enable PDU transmission in a network slice, the UE may request establishment of a PDU session in a network slice towards a data network (DN) which is associated with an S-NSSAI and a data network name (DNN) if there is no established PDU session adequate for the PDU transmission. The S-NSSAI included is part of allowed NSSAI of the serving PLMN or SNPN, which is an S-NSSAI value valid in the serving PLMN or SNPN, and in roaming scenarios the mapped S-NSSAI is also included for the PDU session if available. See subclause 6.4.1 for further details. The UE determines whether to establish a new PDU session or use one of the established PDU session(s) based on the URSP rules which include S-NSSAIs, if any (see subclause 6.2.9), or based on UE local configuration, as described in subclause 4.2.2 of 3GPP TS 24.526[ User Equipment (UE) policies for 5G System (5GS); Stage 3 ] [19].

3GPP TS 24.501

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

CT WG1

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

4.6.3

– SL-DRX-ConfigUC-SemiStatic

The IE SL-DRX-ConfigUC-SemiStatic is used to indicate the semi-static sidelink DRX related parameters for unicast communication. SL-DRX-ConfigUC-SemiStatic information element -- ASN1START -- TAG-DRX-CONFIGUCSEMISTATIC-START SL-DRX-ConfigUC-SemiStatic-r17 ::= SEQUENCE { sl-drx-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-CycleStartOffset-r17 CHOICE { ms10 INTEGER(0..9), ms20 INTEGER(0..19), ms32 INTEGER(0..31), ms40 INTEGER(0..39), ms60 INTEGER(0..59), ms64 INTEGER(0..63), ms70 INTEGER(0..69), ms80 INTEGER(0..79), ms128 INTEGER(0..127), ms160 INTEGER(0..159), ms256 INTEGER(0..255), ms320 INTEGER(0..319), ms512 INTEGER(0..511), ms640 INTEGER(0..639), ms1024 INTEGER(0..1023), ms1280 INTEGER(0..1279), ms2048 INTEGER(0..2047), ms2560 INTEGER(0..2559), ms5120 INTEGER(0..5119), ms10240 INTEGER(0..10239) }, sl-drx-SlotOffset-r17 INTEGER (0..31) } -- TAG-SL-DRX-CONFIGUCSEMISTATIC-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

.7 MCH Scheduling Information MAC Control Element

The MCH Scheduling Information MAC Control Element illustrated in Figure 6.1.3.7-1 is identified by a MAC PDU subheader with LCID as specified in Table 6.2.1-4. This control element has a variable size. For each MTCH the fields below are included: - LCID: this field indicates the Logical Channel ID of the MTCH. The length of the field is 5 bits; - Stop MTCH: this field indicates the ordinal number of the subframe within the MCH scheduling period, counting only the subframes allocated to the MCH, where the corresponding MTCH stops. Value 0 corresponds to the first subframe. The length of the field is 11 bits. The special Stop MTCH value 2047 indicates that the corresponding MTCH is not scheduled. The value range 2043 to 2046 is reserved. Figure 6.1.3.7-1: MCH Scheduling Information MAC control element

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

.7

8.32 Bearer Flags

Bearer Flags is coded as depicted in Figure 8.32-1. Figure 8.32-1: Bearer Flags The following bits within Octet 5 indicate: - Bit 1 – PPC (Prohibit Payload Compression): This flag is used to determine whether an SGSN should attempt to compress the payload of user data when the users asks for it to be compressed (PPC = 0), or not (PPC = 1). - Bit 2 – VB (Voice Bearer): This flag is used to indicate a voice bearer when doing PS-to-CS (v)SRVCC handover. - Bit 3 – Vind (vSRVCC indicator): This flag is used to indicate that this bearer is an IMS video bearer and is candidate for PS-to-CS vSRVCC handover. - Bit 4 - ASI (Activity Status Indicator): When set to 1, this flag indicates that the bearer context is preserved in the CN without corresponding Radio Access Bearer established. The target S4-SGSN shall keep the bearer context associated with this indicator preserved. When the target S4-SGSN sends Relocation Request message towards the target RNC, the target S4-SGSN may not request to setup the RABs for those bearer contexts associated with this indicator.

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

I.10.3.1 Trusted non-3GPP access support in SNPN without CH

Procedures for trusted non-3GPP access authentication are described in clause 7A.2.1. For SNPN the procedures are re-used with the following modifications: Steps 0-4 are performed as described in clause 7A.2.1. In step 5, the SUCI can be an onboarding SUCI. Further in step 5, the SUCI carried in AN parameter and NAS-PDU 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. If anonymous SUCI is used, the UE shall send a 64-bit random number as a key identifier in the AN parameters. The random number generation should follow the recommendations given in SP 800-90A [110] or equivalent. If the UE provides a key identifier already allocated in the TNGF, the UE will be rejected. Editor's Note: Whether also the anonymous SUCI is sent in the AN parameter is ffs. Step 6-7 is performed as described in clause 7A.2.1. In step 8 of clause 7A.2.1, in case the AUSF receives an onboarding indication, the AUSF shall perform steps 6-10 and 14-17 as described in Annex I.2.2.2. In the selection of UE authentication method in step 8 of clause 7A.2.1, 5G AKA, EAP-AKA’, or any other key-generating EAP authentication method apply. When the "username" part of the SUPI is "anonymous" or omitted, the UDM may select an authentication method based on the "realm" part of the SUPI or on the UDM local policy. In case the AUSF received an anonymous SUCI in step 7 (but no onboarding indication was received) 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. In case anonymous SUCI and onboarding indication was received in step 7, steps 11-13 of Annex I.2.2.2 can be skipped. Steps 9-12 are performed as described in clause 7A.2.1. In step 13, in case anonymous SUCI was used in step 5, the key identifier sent in the AN parameters is used in the IDi payload. If the key identifier is not the same as the one sent in step 5, the IPsec setup will fail and the UE will be rejected. Steps 14-19 are performed as described in clause 7A.2.1.

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

I.10.3.1

16.9.2.2 MAC

The MAC sublayer provides the following services and functions over the PC5 interface in addition to the services and functions specified in clause 6.2.1: - Radio resource selection; - Packet filtering; - Priority handling between uplink and sidelink transmissions for a given UE; - Sidelink CSI reporting. With LCP restrictions in MAC, only sidelink logical channels belonging to the same destination can be multiplexed into a MAC PDU for every unicast, groupcast and broadcast transmission which is associated to the destination. NG-RAN can also control whether a sidelink logical channel can utilise the resources allocated to a configured sidelink grant Type 1 (see clause 16.9.3.2). For transmissions to RX UE(s) using SL DRX operation, LCP ensures that a TX UE transmits data in the active time of the RX UE(s). For packet filtering, a SL-SCH MAC header including portions of both Source Layer-2 ID and a Destination Layer-2 ID is added to each MAC PDU as specified in clause 8.4. LCID included within a MAC subheader uniquely identifies a logical channel within the scope of the Source Layer-2 ID and Destination Layer-2 ID combination. The following logical channels are used in sidelink: - Sidelink Control Channel (SCCH): a sidelink channel for transmitting control information (i.e. PC5-RRC and PC5-S messages) and NR sidelink discovery messages from one UE to other UE(s); - Sidelink Traffic Channel (STCH): a sidelink channel for transmitting user information from one UE to other UE(s); - Sidelink Broadcast Control Channel (SBCCH): a sidelink channel for broadcasting sidelink system information from one UE to other UE(s). The following connections between logical channels and transport channels exist: - SCCH can be mapped to SL-SCH; - STCH can be mapped to SL-SCH; - SBCCH can be mapped to SL-BCH.

3GPP TS 38.300

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

RAN2

3GPP Series : 38 , Radio technology beyond LTE

16.9.2.2

6.2.15 Handling of Reliable Data Service

If the UE supports Reliable Data Service (see 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8] and 3GPP TS 24.250[ Protocol for Reliable Data Service; Stage 3 ] [14A]), the UE may request data transfer using Reliable Data Service for a PDU session in the Extended protocol configuration options IE during UE-requested PDU session establishment procedure (see subclause 6.4.1). The Reliable Data Service may only be used with PDU sessions for which the "Control Plane CIoT 5GS Optimisation" indicator is set or with PDU sessions using the control plane CIoT 5GS optimization when the AMF does not move such PDU sessions to the user plane. The network shall inform the UE about the acceptance of UE's request for Reliable Data Service usage during the PDU session establishment procedure (see subclause 6.4.1) in the Extended protocol configuration options IE. If the network accepts the use of Reliable Data Service to transfer data for the specified PDU session, the UE shall use this PDU session exclusively for data transfer using Reliable Data Service; otherwise the UE shall not use this PDU session for data transfer using Reliable Data Service.

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

– EUTRA-NS-PmaxList

The IE EUTRA-NS-PmaxList concerns a list of additionalPmax and additionalSpectrumEmission, as defined in TS 36.101[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception ] [22], table 6.2.4-1 for UEs neither in CE nor BL UEs, TS 36.101[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception ] [22], table 6.2.4E-1 for UEs in CE or BL UEs, and TS 36.101[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception ] [22], table TBD for Aerial UEs,for a given frequency band. EUTRA-NS-PmaxList information element -- ASN1START -- TAG-EUTRA-NS-PMAXLIST-START EUTRA-NS-PmaxList ::= SEQUENCE (SIZE (1..maxEUTRA-NS-Pmax)) OF EUTRA-NS-PmaxValue EUTRA-NS-PmaxValue ::= SEQUENCE { additionalPmax INTEGER (-30..33) OPTIONAL, -- Need R additionalSpectrumEmission INTEGER (1..288) OPTIONAL -- Need R } -- TAG-EUTRA-NS-PMAXLIST-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

4.3.24.3 RAN user plane congestion mitigation in the CN

RAN user plane congestion mitigation in the CN uses RAN OAM information, collected by the RAN Congestion Awareness Function (RCAF), to detect congestion. The RAN Congestion Awareness Function is further described in clause 4.4.12. This functionality is applicable only in the case of UTRAN/E-UTRAN accesses. NOTE 1: The criteria used for detection of RAN user plane congestion (including detection of congestion abatement) are outside the scope of 3GPP specifications. NOTE 2: The interface to the RAN's OAM system is not standardized. The RCAF can transfer RAN user plane congestion information (RUCI) to the PCRF over the Np reference point in order to mitigate the congestion by measures selected by the PCRF, as specified in TS 23.203[ Policy and charging control architecture ] [6]. Decisions to apply congestion mitigation measures may take into account operator policies and subscriber information and all additional available IP-CAN session information. Different mechanisms and mitigation actions applicable as described in TS 23.203[ Policy and charging control architecture ] [6] in order to mitigate RAN User Plane Congestion. Those mechanisms include e.g. service/application gating, service/application bandwidth limitation, deferring of services. NOTE 3: Co-existence between congestion mitigation in RAN and CN can be assured by appropriate network configuration of applicable policies for congestion mitigation, as well as related RAN parameter alignment/tuning, such as tuning of parameters for e.g., load balancing, carrier aggregation, co-ordinated multipoint, dual connectivity. This parameter alignment/tuning is not further specified. NOTE 4: A condition leading to interoperability issues which may lead to suboptimal situation is that the time scales for actions of congestion mitigation in RAN and in CN are of comparable duration. Therefore, congestion mitigation in RAN and CN cannot have comparable time scales, otherwise interoperability is affected.

3GPP TS 23.401

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

SA WG2

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

4.3.24.3

6.1.3.1.3.2 Handling of network rejection due to SM cause #26

If the SM cause value is #26 "insufficient resources" and the Back-off timer value IE is included, the MS 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 T3396 in the Back-off timer value IE (if the MS is configured for dual priority, exceptions are specified in subclause 6.1.3.12; if the MS is an MS configured to use AC11 – 15 in selected PLMN, exceptions are specified in subclause 6.1.3.11): i) if the timer value indicates neither zero nor deactivated and an APN was included in the ACTIVATE PDP CONTEXT REQUEST message, the MS shall stop timer T3396 associated with the corresponding APN, if it is running. If the timer value indicates neither zero nor deactivated, the request type was different from "emergency", and no APN was included in the ACTIVATE PDP CONTEXT REQUEST message, the MS shall stop timer T3396 associated with no APN if it is running. The MS shall then start timer T3396 with the value provided in the Back-off timer value IE and: - shall not send another ACTIVATE PDP CONTEXT REQUEST, ACTIVATE SECONDARY PDP CONTEXT REQUEST or MODIFY PDP CONTEXT REQUEST message with exception of those identified in subclause 6.1.3.3, for the same APN that was sent by the MS, until timer T3396 expires or timer T3396 is stopped; and - shall not send another ACTIVATE PDP CONTEXT REQUEST message without an APN and with request type different from "emergency", or another ACTIVATE SECONDARY PDP CONTEXT REQUEST or MODIFY PDP CONTEXT REQUEST message with exception of those identified in subclause 6.1.3.3, for a non-emergency PDN connection established without an APN sent by the MS, if the APN was not included in the ACTIVATE PDP CONTEXT REQUEST message and the request type was different from "emergency", until timer T3396 expires or timer T3396 is stopped. The MS shall not stop timer T3396 upon a PLMN change or inter-system change; ii) if the timer value indicates that this timer is deactivated, the MS: - shall not send another ACTIVATE PDP CONTEXT REQUEST, ACTIVATE SECONDARY PDP CONTEXT REQUEST or MODIFY PDP CONTEXT REQUEST message with exception of those identified in subclause 6.1.3.3, for the same APN that was sent by the MS, until the MS is switched off or the SIM/USIM is removed or the MS receives a REQUEST PDP CONTEXT ACTIVATION, REQUEST SECONDARY PDP CONTEXT ACTIVATION or MODIFY PDP CONTEXT REQUEST message with the same APN from the network or a DEACTIVATE PDP CONTEXT REQUEST message including SM cause #39 "reactivation requested" for a PDP context which was activated by the MS for the same APN from the network; and - shall not send another ACTIVATE PDP CONTEXT REQUEST message without an APN and with request type different from "emergency", or another ACTIVATE SECONDARY PDP CONTEXT REQUEST or MODIFY PDP CONTEXT REQUEST message with exception of those identified in subclause 6.1.3.3, for a non-emergency PDN connection established without an APN sent by the MS, if the APN was not included in the ACTIVATE PDP CONTEXT REQUEST message and the request type was different from "emergency", until the MS is switched off or the SIM/USIM is removed or the MS receives for a non-emergency PDP context which was activated by the MS any of the following messages: a REQUEST PDP CONTEXT ACTIVATION without an APN, a REQUEST SECONDARY PDP CONTEXT ACTIVATION or MODIFY PDP CONTEXT REQUEST message for a non-emergency PDN connection established without an APN sent by the MS, or a DEACTIVATE PDP CONTEXT REQUEST message including SM cause #39 "reactivation requested" for a non-emergency PDN connection which was established without an APN sent by the MS. The timer T3396 remains deactivated upon a PLMN change or inter-system change; and iii) if the timer value indicates that this timer is zero, the MS: - shall stop timer T3396 associated with the corresponding APN, if running, and may send an ACTIVATE PDP CONTEXT REQUEST, ACTIVATE SECONDARY PDP CONTEXT REQUEST or MODIFY PDP CONTEXT REQUEST message for the same APN; and - if the APN was not included in the ACTIVATE PDP CONTEXT REQUEST message and the request type was different from "emergency", the MS shall stop timer T3396 associated with no APN, if running, and may send an ACTIVATE PDP CONTEXT REQUEST message without an APN, or another ACTIVATE SECONDARY PDP CONTEXT REQUEST or MODIFY PDP CONTEXT REQUEST message for a non-emergency PDN connection established without an APN sent by the MS. If the Back-off timer value IE is not included, then the MS may send another ACTIVATE PDP CONTEXT REQUEST, ACTIVATE SECONDARY PDP CONTEXT REQUEST or MODIFY PDP CONTEXT REQUEST message for the same APN. The MS may initiate a PDP context activation procedure for emergency bearer services even if the timer T3396 is running. If the timer T3396 is running when the MS enters state GMM-DEREGISTERED, the MS remains switched on, and the SIM/USIM in the MS remains the same, then timer T3396 is kept running until it expires or it is stopped. If the MS is switched off when the timer T3396 is running, and if the SIM/USIM in the MS remains the same when the MS is switched on, the MS 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 MS is not capable of determining t, then the MS shall restart the timer with the value t1; and - if prior to switch off, timer T3396 was running because an ACTIVATE PDP CONTEXT REQUEST, ACTIVATE SECONDARY PDP CONTEXT REQUEST, MODIFY PDP CONTEXT REQUEST or ACTIVATE MBMS CONTEXT REQUEST message containing the low priority indicator set to "MS is configured for NAS signalling low priority" was rejected with a timer value for timer T3396, and if timer T3396 is restarted at switch on, then the MS configured for dual priority shall handle session management requests as indicated in subclause 6.1.3.12.

3GPP TS 24.008

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

CT WG1

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

6.1.3.1.3.2

D.2.1.4 Network-requested UE policy management procedure not accepted by the UE

If the UE could not execute all instructions included in the UE policy section management list IE successfully, the UE shall: a) set the PTI IE to the PTI value received within the MANAGE UE POLICY COMMAND message and encode the results by including: 1) the UPSI associated with the instructions which could not be executed successfully; 2) the failed instruction order set to order of the instruction in the UE policy section management sublist of the received UE policy section management list IE which could not be executed successfully; and 3) the cause of the failure, in the UE policy section management result IE as specified in subclause D.5.3 and include it in a MANAGE UE POLICY COMMAND REJECT message, and b) transport the MANAGE UE POLICY COMMAND REJECT message using the NAS transport procedure as specified in subclause 5.4.5. Upon receipt of the MANAGE UE POLICY COMMAND REJECT message, the PCF shall stop timer T3501. Any instruction that was included in the UE policy section management list IE but not indicatedin the UE policy section management result IE of the received MANAGE UE POLICY COMMAND REJECT message, shall be considered as successfully executed. The PCF should ensure that the PTI value assigned to this procedure is not released immediately. NOTE: The way to achieve this is implementation dependent. For example, the PCF can ensure that the PTI value assigned to this procedure is not released during the time equal to or greater than the default value of timer T3501. Upon receipt of the notification from the AMF that the UE is not reachable, the PCF shall stop the T3501.

3GPP TS 24.501

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

CT WG1

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

D.2.1.4

5.40.6 Prevention of signalling overload related to Disaster Condition and Disaster Roaming service

The load control, congestion and overload control mechanism specified in clause 5.19 and access control and barring specified in clause 5.2.5 can be used to mitigate the load caused by UE requesting the Disaster Roaming service in the PLMN providing Disaster Roaming service and returning of UE to allowable PLMN when Disaster Condition is no longer applicable. To prevent signalling overload in PLMN providing Disaster Roaming, the HPLMN or registered PLMN: - may provide the UE in a prioritized manner with the list of PLMNs described in clause 5.40.2 for Disaster Roaming; - may provide disaster roaming wait range information to control when the UE can initiate the registration for Disaster Roaming service upon arriving in the PLMN providing Disaster Roaming service as specified in TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [17] and TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]; and - applies Access Identity 3 for Disaster Roaming service request as specified in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]. NOTE: The mechanisms available at the AMF and the SMF for mitigation of overload and congestion are used for 5GSM congestion mitigation during the Disaster Roaming. To prevent signalling overload by returning UEs in PLMN previously with Disaster Condition which is no long applicable, the HPLMN or registered PLMN: - may provide disaster return wait range information to control when the UE can initiate the registration upon returning to the PLMN previously with Disaster Condition as specified in TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [17] and TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47].

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.40.6

10.5.2 Uplink

The UE has an uplink rate control function which manages the sharing of uplink resources between logical channels. RRC controls the uplink rate control function by giving each logical channel a priority, a prioritised bit rate (PBR), and a buffer size duration (BSD). The values signalled need not be related to the ones signalled via NG to the gNB. In addition, mapping restrictions can be configured (see clause 16.1.2). The uplink rate control function ensures that the UE serves the logical channel(s) in the following sequence: 1. All relevant logical channels in decreasing priority order up to their PBR; 2. All relevant logical channels in decreasing priority order for the remaining resources assigned by the grant. NOTE 1: In case the PBRs are all set to zero, the first step is skipped and the logical channels are served in strict priority order: the UE maximises the transmission of higher priority data. NOTE 2: The mapping restrictions tell the UE which logical channels are relevant for the grant received. If no mapping restrictions are configured, all logical channels are considered. NOTE 3: Through radio protocol configuration and scheduling, the gNB can guarantee the GFBR(s) and ensure that any of the MFBR(s), the UE-AMBR and, when supported and feasible, the UE-Slice-MBR is not exceeded in uplink (see clause 12). NOTE 4: The mapping restrictions allows the gNB to fulfil the MDBV requirements through scheduling at least for the case where logical channels are mapped to separate serving cells. If more than one logical channel have the same priority, the UE shall serve them equally.

3GPP TS 38.300

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

RAN2

3GPP Series : 38 , Radio technology beyond LTE

10.5.2

8.17.1 IAB Inter-donor-DU Re-routing

When an IAB-donor-DU is configured to support inter-donor-DU re-routing, the IAB-donor-DU may identify a re-routed UL IP packet based on the source IP address field of the UL packet, and forwards UL IP packets, whose source IP addresses are anchored at a peer IAB-donor-DU, to this peer IAB-donor-DU via a tunnel. The IAB-donor-DU and the peer IAB-donor-DU may be controlled by the same IAB-donor-CU or by two different IAB-donor-CUs. The inter-donor-DU tunnel may be a GTP-U tunnel. The configuration of the tunnel is up to implementation. At the IAB-donor-DU forwarding the UL IP packets, inter-donor-DU tunnelling may be restricted to only a subset of the IP addresses anchored at the peer IAB-donor-DU. For this purpose, the IAB-donor-CU configures the IAB-donor-DU for forwarding the UL IP packets with a list of TNL addresses and/or prefixes for which tunnelling should be permitted and TNL address filtering should be exempted. NOTE: Tunnel types other than GTP-U may be used for the inter-donor-DU tunnel, by implementation.

3GPP TS 38.401

NG-RAN; Architecture description

RAN3

3GPP Series : 38 , Radio technology beyond LTE

8.17.1

4.16.11 UE Policy Association Establishment 4.16.11.1 General

The UE Policy Association Establishment procedure, which may be performed for a UE registered in the same AMF or different AMFs for 3GPP access and non-3GPP access, concerns the following scenarios: 1. UE initial registration with the network. 2. The AMF relocation with PCF change in handover procedure and registration procedure. 3. UE registration with 5GS when the UE moves from EPS to 5GS and there is no existing UE Policy Association between AMF and PCF for this UE. In Non-roaming case, the H-PCF may interact with the CHF in HPLMN to make a decision about UE Policies based on spending limits. Figure 4.16.11-1: UE Policy Association Establishment This procedure concerns both roaming and non-roaming scenarios. In the non-roaming case the V-PCF is not involved and the role of the H-PCF is performed by the PCF. For the roaming scenarios, the V-PCF interacts with the AMF and the H-PCF interacts with the V-PCF: 1. The AMF establishes UE Policy Association with the (V-)PCF when a UE Policy Container is received from the UE. If a UE Policy Container is not received from the UE, the AMF may establish UE Policy Association with the (V-)PCF based on AMF local configuration. NOTE 1: In roaming scenario, the AMF local configuration can indicate whether UE Policy delivery is needed based on the roaming agreement with home PLMN of the UE. 2. The AMF sends a Npcf_UEPolicyControl Create Request with the following information: SUPI, may include Access Type and RAT, PEI, ULI, UE time zone, Serving Network (PLMN ID, or PLMN ID and NID, see clause 5.34 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]), the Internal-Group-ID-list and UE Policy Container (the list of stored PSIs, operating system identifier, Indication of UE support for ANDSP, indication of UE capability of reporting URSP rule enforcement to network). In roaming scenario, based on operator policies, the AMF may provide to the V-PCF the PCF ID of the selected H-PCF. The V-PCF contacts the H-PCF. In roaming case, steps 3 and 4 are executed, otherwise step 5 follows. If the AMF, based on configuration, is aware that the UE is accessing over a gNB using satellite backhaul, the AMF includes the Satellite Backhaul Category as described in clause 5.43 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 3. The V-PCF forwards the information received from AMF in step 2 to the H-PCF. When a UE Policy Container is received at initial registration, the H-PCF may store the PEI, the OSId, indication of UE capability of reporting URSP rule enforcement to network or the indication of UE support for ANDSP in the UDR using Nudr_DM_Create including DataSet "Policy Data" and Data Subset "UE context policy control data". The V-PCF may retrieve the Application guidance on URSP Rule for inbound roamers of the PLMN of the SUPI, if not available, using Nudr_DM_Query or Nudr_DM_Subscribe including the Data Set "Application Data" and Data Subset "Service Specific Information" and DataKey set to "PLMN ID(s) of inbound roamers". The V-PCF may retrieve the Application guidance on URSP Rule for inbound roamers of the PLMN of the SUPI, if not available, using Nudr_DM_Query or Nudr_DM_Subscribe including the Data Set "Application. 4. The H-PCF sends a Npcf_UEPolicyControl Create Response to the V-PCF. The H-PCF may provide the Policy Control Request Trigger parameters in the Npcf_UEPolicyControl Create Response. Before sending the response, the H-PCF may determine that the decision about UE policy control depends on the status of the policy counters available at the CHF and if such reporting is not established for the subscriber, the H-PCF initiates an Initial Spending Limit Report Retrieval as defined in clause 4.16.8.2. If policy counter status reporting is already established for the subscriber and the H-PCF determines that the status of additional policy counters are required, the H-PCF initiates an Intermediate Spending Limit Report Retrieval as defined in clause 4.16.8.3. The (H-)PCF in roaming and the PCF in non-roaming may register to the BSF as the PCF serving this UE, if not already registered at the AM Policy Association establishment. This is performed by using the Nbsf_Management_Register operation, providing as inputs the UE SUPI/GPSI and the PCF identity. 5. The (V-) PCF sends a Npcf_UEPolicyControl Create Response to the AMF. The (V-)PCF relays the Policy Control Request Trigger parameters in the Npcf_UEPolicyControl Create Response. The (V-)PCF also subscribes to notification of N1 message delivery of policy information to the UE using Namf_Communication_N1N2MessageSubscribe service which is not shown in this figure. 6. The (H-)PCF gets policy subscription related information and the latest list of PSIs from the UDR using Nudr_DM_Query service operation (SUPI, Policy Data, UE context policy control data, Policy Set Entry) if either or both are not available and makes a policy decision. The (H-)PCF may get the PEI, the OSId, indication of UE capability of reporting URSP rule enforcement to network or the indication of UE support for ANDSP in the UDR using Nudr_DM_Query including DataSet "Policy Data" and Data Subset "UE context policy control data" if the AMF relocates and the PCF changes. In the roaming scenario, the H-PCF may provide the indication of UE support for ANDSP to the V-PCF, if the indication was not present in the Npcf_UEPolicyControl Create request from V-PCF and the H-PCF gets this information from the H-UDR. The (H-)PCF may get the 5G VN group data and 5G VN group membership for each Internal-Group-ID received from the AMF using Nudr_DM_Query (Internal-Group-Id, Subscription Data, 5G VN Group Configuration). The (H-)PCF may store the 5G VN group data and 5G VN group membership for later use for other SUPIs that belong to the same Internal-Group-ID. The (H-)PCF may request notifications from the UDR on changes in the subscription information by invoking Nudr_DM_Subscribe (Policy Data, SUPI, DNN, S-NSSAI, Notification Target Address (+ Notification Correlation Id), Event Reporting Information (continuous reporting), UE context policy control data) service. The (H-)PCF may request notifications from the UDR on changes in the 5G VN group data or 5G VN group membership associated to each of the Internal-Group-Id provided to the PCF by invoking Nudr_DM_Subscribe (Subscription Data, 5G VN Group Configuration, Internal Group ID, Notification Target Address (+ Notification Correlation Id), Event Reporting Information (continuous reporting)) service. The (H-)PCF creates the UE policy container including UE policy information as defined in clause 6.6 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20] and in the case of roaming H-PCF provides the UE policy container in the Npcf_UEPolicyControl UpdateNotify Request. In the non-roaming case, the PCF may subscribe to Analytics from NWDAF as defined in clause 6.1.1.3 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. 7. The V-PCF sends a response to H-PCF using Npcf_UEPolicyControl UpdateNotify Response. NOTE 2: Step 6 (and step 7) can be omitted. Then the (H-)PCF creates the UE policy container including UE polices in step 2 (in the case of non-roaming) or step 3 (in the case of roaming). This means that the potential interactions with UDR as in step 6 will have to be executed in step 2 (non-roaming) or step 3 (roaming). 8. The (V-)PCF triggers UE Configuration Update Procedure in clause 4.2.4.3 to sends the UE policy container including UE policy information to the UE. The (V-)PCF checks the size limit as described in clause 6.1.2.2.2 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. 9. If the V-PCF received notification of the reception of the UE Policy container then the V-PCF forwards the notification response of the UE to the H-PCF using Npcf_UEPolicyControl_Update Request. If the V-PCF is notified by the V-UDR about the Service Specific Information applicable to inbound roamers from the HPLMN of the UE as specified in clause 4.15.6.10, the V-PCF provides the Service Parameters to the H-PCF. 10. The H-PCF sends a response to the V-PCF. If the V-PCF received a UE Policy Container step 8 will follow.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.16.11

6.2.3E UE maximum output power for modulation / channel bandwidth for category M1 and M2

For category M1 UE Power Class 3, 5 and 6, the allowed Maximum Power Reduction (MPR) for the maximum output power specified in Table 6.2.2E-1 due to higher order modulation and transmit bandwidth configuration (resource blocks) is specified in Tables 6.2.3E-1, 6.2.3E-2 and 6.2.3E-5 respectively. For category M2 UE Power Class 3, 5 and 6, the allowed Maximum Power Reduction (MPR) for the maximum output power specified in Table 6.2.2E-1 due to higher order modulation and transmit bandwidth configuration (resource blocks) is specified in Table 6.2.3E-3, Table 6.2.3E-4 and Table 6.2.3E-6 respectively. For subPRB allocation of category M1 UE of Power Class 3, there is no MPR applies. For subPRB allocation of category M2 UE of Power Class 3, the allowed MPR due to higher order modulation and transmit bandwidth configuration (subcarrier) is specified in in Table 6.2.3E-7. Table 6.2.3E-1: Maximum Power Reduction (MPR) for category M1 UE for Power Class 2 and 3 Table 6.2.3E-2: Maximum Power Reduction (MPR) for category M1 for Power Class 5 Table 6.2.3E-3: Maximum Power Reduction (MPR) for category M2 UE for Power Class 2 and 3 Table 6.2.3E-4: Maximum Power Reduction (MPR) for category M2 UE for Power Class 5 Table 6.2.3E-5: Maximum Power Reduction (MPR) for category M1 for Power Class 6 Table 6.2.3E-6: Maximum Power Reduction (MPR) for category M2 UE for Power Class 6 Table 6.2.3E-7: Maximum Power Reduction (MPR) for category M2 UE for Power Class 3 for subPRB allocation For PRACH, PUCCH and SRS transmissions, the allowed MPR is according to that specified for PUSCH QPSK modulation for the corresponding transmission bandwidth. For each subframe, the MPR is evaluated per slot and given by the maximum value taken over the transmission(s) within the slot; the maximum MPR over the two slots is then applied for the entire subframe. For the UE maximum output power modified by MPR, the power limits specified in subclause 6.2.5 apply. No other MPR requirement than those specified in tables 6.2.3E-1 and Table 6.2.3E-2 and Table 6.2.3E-5 applies to category M1 and those specified in tables 6.2.3E-3 and Table 6.2.3E-4 and Table 6.2.3E-6 applies to category M2 UE.

3GPP TS 36.101

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

RAN4

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

6.2.3E

8.2.1.4.4 Minimum Requirement Multi-Layer Spatial Multiplexing 2 Tx Antenna Port (Superposed transmission)

The requirements are specified in Table 8.2.1.4.4-2, with the addition of the parameters in Table 8.2.1.4.4-1 and the downlink physical channel setup according to Annex C.3.2. The purpose is to verify the minimun performance of closed-loop spatial multiplexing with 2 transmitter antennas superposed with simultaneous PDSCH interference. Table 8.2.1.4.4-1: Test Parameters for Minimum Requirement Multi-Layer Spatial Multiplexing 2 Tx Antenna Port - Superposed transmission (FRC) Table 8.2.1.4.4-2: Minimum Performance for Minimum Requirement Multi-Layer Spatial Multiplexing 2 Tx Antenna Port - Superposed transmission (FRC)

3GPP TS 36.101

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

RAN4

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

8.2.1.4.4

9.3.1.2.6 TDD (when csi-SubframeSet –r12 is configured with one CSI process)

The following requirements apply to UE Category ≥1 which supports Rel-12 CSI subframe sets and TM10. For the parameters specified in Table 9.3.1.2.6-1, and using the downlink physical channels specified in Annex C.3.2, the minimum requirements are specified in Table 9.3.1.2.6-2 and by the following a) a sub-band differential CQI offset level of 0 shall be reported at least  % of the time but less than % for each sub-band for each CSI subframe set; b) the ratio of the throughput obtained when transmitting on a randomly selected sub-band among the sub-bands with the highest differential CQI offset level the corresponding TBS and that obtained when transmitting the TBS indicated by the reported wideband CQI median on a randomly selected sub-band in set S shall be ≥ for each CSI subframe set; c) when transmitting on a randomly selected sub-band among the sub-bands with the highest differential CQI offset level the corresponding TBS, the average BLER for the indicated transport formats shall be greater or equal to 0.01 for each CSI subframe set. d) The difference of the wide-band median CQI obtained by reports in CSI subframe sets CCSI,0 and the wide-band median CQI obtained by reports in CSI subframe sets CCSI,1 shall be larger than or equal to 3. The requirements only apply for sub-bands of full size and the random scheduling across the sub-bands is done by selecting a new sub-band in each available downlink transmission instance. Sub-bands of a size smaller than full size are excluded from the test. Table 9.3.1.2.6-1: Sub-band test for TDD Table 9.3.1.2.6-2: Minimum requirement (TDD)

3GPP TS 36.101

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

RAN4

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

9.3.1.2.6

6.4.1.5 Handling the maximum number of established PDU sessions

The maximum number of PDU sessions which a UE can establish in a PLMN or SNPN is limited by whichever is the lowest of: the maximum number of PDU session IDs allowed by the protocol (as specified in 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [11] subclause 11.2.3.1b), the PLMN's or SNPN's maximum number of PDU sessions and the UE's implementation-specific maximum number of PDU sessions. If during a UE-requested PDU session establishment procedure the 5GSM sublayer in the UE receives an indication that the 5GSM message was not forwarded because: a) the PLMN's maximum number of PDU sessions has been reached, then the UE determines the PLMN's maximum number of PDU sessions as the number of active PDU sessions it has; or b) the SNPN's maximum number of PDU sessions has been reached, then the UE determines the SNPN's maximum number of PDU sessions as the number of active PDU sessions it has and associates the determined maximum number of PDU sessions with: 1) the entry in the "list of subscriber data" for the current SNPN if the UE does not support access to an SNPN using credentials from a credentials holder and equivalent SNPNs; or 2) the selected entry of the "list of subscriber data" or the selected PLMN subscription if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both. NOTE 1: In some situations, when attempting to establish multiple PDU sessions, the number of active PDU sessions that the UE has when 5GMM cause #65 is received is not equal to the maximum number of PDU sessions reached in the network. NOTE 2: When the network supports emergency services, it is not expected that 5GMM cause #65 is returned by the network when the UE requests an emergency PDU session. NOTE 3: The network maintains only one maximum number of PDU sessions for a PLMN regardless of which access the PDU session exists in. NOTE 3a: When the UE is registered on the same PLMN for both 3GPP access and non-3GPP access, the UE maintains single maximum number of PDU sessions for respective PLMN. When the UE is registered on two different PLMNs over 3GPP access and non-3GPP access, the UE maintains maximum number of PDU sessions for a PLMN separately for each PLMN. NOTE 4: An MA PDU session which (only) has a PDN connection established as a user-plane resource is counted as an active PDU session when determining the PLMN's maximum number of PDU sessions. The PLMN's maximum number of PDU sessions applies to the PLMN in which the 5GMM cause #65 "maximum number of PDU sessions reached" is received. When the UE is switched off or when the USIM is removed, the UE shall clear all previous determinations representing PLMN's maximum number of PDU sessions. The SNPN's maximum number of PDU sessions applies to the SNPN in which the 5GMM cause #65 "maximum number of PDU sessions reached" is received. When the UE is switched off, the UE shall clear all previous determinations representing SNPN's maximum number of PDU sessions. In addition: a) if the UE does not support access to an SNPN using credentials from a credentials holder and equivalent SNPNs, and the entry in the "list of subscriber data" for the current SNPN is updated, then the UE shall clear all previous determinations representing SNPN's maximum number of PDU sessions associated with the entry in the "list of subscriber data" for the current SNPN; and b) if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, and: 1) the selected entry of the "list of subscriber data" is updated, then UE shall clear all previous determinations representing SNPN's maximum number of PDU sessions associated with the selected entry in the "list of subscriber data"; or 2) the USIM associated with the selected PLMN subscription is removed, then UE shall clear all previous determinations representing SNPN's maximum number of PDU sessions associated with the selected PLMN subscription. Upon successful registration with a new PLMN or SNPN, the UE may clear previous determinations representing any PLMN's or SNPN's maximum number(s) of PDU sessions, if the previous PLMN or SNPN is not registered over both 3GPP access and non-3GPP access. If the maximum number of established PDU sessions is reached at the UE and the upper layers of the UE request connectivity to a DNN the UE shall not send a PDU SESSION ESTABLISHMENT REQUEST message unless an established PDU session is released. If the UE needs to release an established PDU session, choosing which PDU session to release is implementation specific, however the UE shall not release the emergency PDU session. If the UE needs to release a PDU session in order to request an emergency PDU session, it shall either perform a local release of a PDU session or release a PDU session via explicit signalling. If the UE performs a local release, the UE shall: a) if the PDU session is an MA PDU session: 1) perform a registration procedure for mobility and periodic registration update to indicate PDU session status to the network over each access that user plane resources have been established; and 2) perform a normal and periodic tracking area updating to indicate EPS bearer context status to the network as specified in subclause 5.5.3.2.2 of 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] when a PDN connection has been established as a user plance resource; or b) if the PDU session is a single access PDU session, perform a registration procedure for mobility and periodic registration update to indicate PDU session status to the network over the access the PDU session is associated with.

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

4.7.5.2.3 Combined routing area updating procedure accepted by the network

Depending on the value of the update result IE received in the ROUTING AREA UPDATE ACCEPT message, two different cases can be distinguished: Case 1) The update result IE value indicates "combined RA/LA": Routing and location area updating is successful; Case 2) The update result IE value indicates "RA only": Routing area updating is successful, but location area updating is not successful. A ROUTING AREA UPDATE COMPLETE message shall be returned to the network if the ROUTING AREA UPDATE ACCEPT message containsany of: - a P-TMSI and/or a TMSI; - Receive N-PDU Numbers (see 3GPP TS 44.065[ Mobile Station (MS) - Serving GPRS Support Node (SGSN); Subnetwork Dependent Convergence Protocol (SNDCP) ] [78] and 3GPP TS 25.322[ None ] [19b]); or - a request for the provision of Inter RAT handover information. If Receive N-PDU Numbers were included, the Receive N-PDU Numbers that are valid in the MS shall be included in the ROUTING AREA UPDATE COMPLETE message. If the network has requested the provision of Inter RAT handover information the MS shall return a ROUTING AREA UPDATE COMPLETE message including the Inter RAT handover information IE, as applicable, to the network. In Iu mode, if the network wishes to prolong the PS signalling connection (for example, if the mobile station has indicated "follow-on request pending" in ROUTING AREA UPDATE REQUEST message) the network shall indicate the "follow-on proceed" in the ROUTING AREA UPDATE ACCEPT message. If the network wishes to release the PS signalling connection, the network shall indicate "no follow-on proceed" in the ROUTING AREA UPDATE ACCEPT message. After that in Iu mode, the mobile station shall act according to the follow-on proceed flag included in the Update result information element in the ROUTING AREA UPDATE ACCEPT message (see subclause 4.7.13). If the network supports CS Fallback, and the mobile station has indicated support of EMM combined procedures in MS network capability, the network shall indicate in the Update result IE in the ROUTING AREA UPDATE ACCEPT message that ISR is not activated. 4.7.5.2.3.1 Combined routing area updating successful The description for normal routing area update as specified in subclause 4.7.5.1.3 shall be followed. In addition, the following description for location area updating applies. The handling at the receipt of the ROUTING AREA UPDATE ACCEPT depends on the value received in the update result IE as specified below. The TMSI reallocation may be part of the combined routing area updating procedure. The TMSI allocated is then included in the ROUTING AREA UPDATE ACCEPT message together with the location area identification (LAI). The network shall, in this case, change to state GMM-COMMON-PROCEDURE-INITIATED and shall start the timer T3350 as described in subclause 4.7.6. The MS, receiving a ROUTING AREA UPDATE ACCEPT message, stores the received location area identification, stops timer T3330, enters state MM IDLE, reset the location update attempt counter and sets the update status to U1 UPDATED. If the ROUTING AREA UPDATE ACCEPT message contains an IMSI, the mobile station is not allocated any TMSI, and shall delete any TMSI accordingly. If the ROUTING AREA UPDATE ACCEPT message contains a TMSI, the MS shall use this TMSI as new temporary identity. The MS shall delete its old TMSI and shall store the new TMSI. In this case, an ROUTING AREA UPDATE COMPLETE message is returned to the network. If neither a TMSI nor an IMSI has been included by the network in the ROUTING AREA UPDATE ACCEPT message, the old TMSI, if any is available, shall be kept. If the MS maintains a counter for "SIM/USIM considered invalid for non-GPRS services" events (see subclause 4.1.1.6A), then the MS shall reset this counter. If the MS is not configured for NAS signalling low priority, and any of the following conditions is fulfilled: - the MS initiated the combined routing area updating procedure due to a change of the registered location area; - the value of the Update type IE in the ROUTING AREA UPDATE REQUEST message indicated "combined RA/LA updating with IMSI attach"; or - the MS indicated support of EMM combined procedures in the MS network capability; then the MS may stop timer T3246 if running. Any timer used for triggering the location updating procedure (e.g. T3211, T3212) shall be stopped if running. The network receiving a ROUTING AREA UPDATE COMPLETE message stops timer T3350, changes to GMM-REGISTERED state NOTE: Upon receiving a ROUTING AREA UPDATE COMPLETE message, the SGSN sends a BSSAP+-TMSI-REALLOCATION-COMPLETE message as specified in 3GPP TS 29.018[ General Packet Radio Service (GPRS); Serving GPRS Support Node (SGSN) - Visitors Location Register (VLR); Gs interface layer 3 specification ] [149]. 4.7.5.2.3.2 Combined routing area updating successful for GPRS services only Apart from the actions on the routing area updating attempt counter, the description for normal routing area update as specified in subclause 4.7.5.1.3 shall be followed. In addition, the following description for location area updating applies. The SGSN shall use GMM cause #28 "SMS provided via GPRS in this routing area" in the ROUTING AREA UPDATE ACCEPT message only if the MS requested "SMS-only service" by including the Additional update type IE in the ROUTING AREA UPDATE REQUEST message. The SGSN may indicate in the Update result IE in the ROUTING AREA UPDATE ACCEPT message that ISR is activated. The MS receiving the ROUTING AREA UPDATE ACCEPT message takes one of the following actions depending on the GMM cause: #2 (IMSI unknown in HLR); The MS shall stop timer T3330 if still running and shall reset the routing area updating attempt counter. The MS shall set the update status to U3 ROAMING NOT ALLOWED and shall delete any TMSI, LAI and ciphering key sequence number. The MS shall enter state GMM-REGISTERED.NORMAL-SERVICE. The new MM state is MM IDLE. The SIM/USIM shall be considered as invalid for non-GPRS services until switching off or the SIM/USIM is removed. If the message has been successfully integrity checked by the lower layers and the MS maintains a counter for "SIM/USIM considered invalid for non-GPRS services", then the MS shall set this counter to MS implementation-specific maximum value. #16 (MSC temporarily not reachable); or #17 (Network failure) The MS shall stop timer T3330 if still running, and shall enter state MM-IDLE. The routing area updating attempt counter shall be incremented. If the routing area updating attempt counter is less than 5, and the stored RAI is equal to the RAI of the current serving cell and the GMM update status is equal to GU1 UPDATED: - the MS shall keep the GMM update status GU1 UPDATED and changes state to GMM-REGISTERED.ATTEMPTING-TO-UPDATE-MM. The MS shall start timer T3311. When timer T3311 expires the combined routing area update procedure indicating "combined RA/LA updating with IMSI attach" is triggered again. If the routing area updating attempt counter is greater than or equal to 5: - the MS shall start timer T3302 and shall change to state GMM-REGISTERED.ATTEMPTING-TO-UPDATE-MM; - a GPRS MS operating in MS operation mode A shall then proceed with appropriate MM specific procedure; a GPRS MS operating in MS operation mode B may then proceed with appropriate MM specific procedures. The MM sublayer shall act as in network operation mode II as long as the combined GMM procedures are not successful and no new RA is entered. # 22 (Congestion); The MS shall change to state GMM-REGISTERED.ATTEMPTING-TO-UPDATE-MM, shall stop timer T3330 if still running, and shall enter state MM-IDLE. The MS shall set the routing area updating attempt counter to 5 and shall start timer T3302. # 28 (SMS provided via GPRS in this routing area); The MS shall stop timer T3330 if still running and shall reset the routing area updating attempt counter. The MS shall set the update status to U3 ROAMING NOT ALLOWED and shall delete any TMSI, LAI and ciphering key sequence number. The MS shall enter state GMM-REGISTERED.NORMAL-SERVICE. The new MM state is MM IDLE. The MS stays in the current serving cell and applies the normal cell reselection process. Other GMM causevalues and the case that no GMM cause IE was received are considered as abnormal cases. The combined routing area updating shall be considered as failed for non-GPRS services. The specification of the MS behaviour in those cases is specified in subclause 4.7.5.2.5.

3GPP TS 24.008

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

CT WG1

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

4.7.5.2.3

19.4.2.9 ePDG FQDN and Visited Country FQDN for non-emergency bearer services 19.4.2.9.1 General

The ePDG Fully Qualified Domain Name (ePDG FQDN), for non-emergency bearers services, shall be constructed using one of the following formats, as specified in clause 4.5.4 of 3GPP TS 23.402[ Architecture enhancements for non-3GPP accesses ] [68]: - Operator Identifier based ePDG FQDN; - Tracking/Location Area Identity based ePDG FQDN; - the ePDG FQDN configured in the UE by the HPLMN. NOTE: The ePDG FQDN configured in the UE can have a different format than those specified in the following clauses. The Visited Country FQDN is used by a roaming UE to determine whether the visited country mandates the selection of an ePDG in this country (see clause 4.5.4.5 of 3GPP TS 23.402[ Architecture enhancements for non-3GPP accesses ] [68]). The Visited Country FQDN shall be constructed as specified in clause 19.4.2.9.4. The Replacement field used in DNS-based Discovery of regulatory requirements shall be constructed as specified in clause 19.4.2.9.5.

3GPP TS 23.003

Numbering, addressing and identification

CT WG4

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

19.4.2.9

4.2.1 Control Plane

In MR-DC, the UE has a single RRC state, based on the MN RRC and a single C-plane connection towards the Core Network. Figure 4.2.1-1 illustrates the Control plane architecture for MR-DC. Each radio node has its own RRC entity (E-UTRA version if the node is an eNB or NR version if the node is a gNB) which can generate RRC PDUs to be sent to the UE. RRC PDUs generated by the SN can be transported via the MN to the UE. The MN always sends the initial SN RRC configuration via MCG SRB (SRB1), but subsequent reconfigurations may be transported via MN or SN. When transporting RRC PDU from the SN, the MN does not modify the UE configuration provided by the SN. In E-UTRA connected to EPC, at initial connection establishment SRB1 uses E-UTRA PDCP. If the UE supports EN-DC, regardless whether EN-DC is configured or not, after initial connection establishment, MCG SRBs (SRB1 and SRB2) can be configured by the network to use either E-UTRA PDCP or NR PDCP (either SRB1 and SRB2 are both configured with E-UTRA PDCP, or they are both configured with NR PDCP). Change from E-UTRA PDCP to NR PDCP (or vice-versa) is supported via a handover procedure (reconfiguration with mobility) or, for the initial change of SRB1 from E-UTRA PDCP to NR PDCP, with a reconfiguration without mobility before the initial security activation. If the SN is a gNB (i.e. for EN-DC, NGEN-DC and NR-DC), the UE can be configured to establish a SRB with the SN (SRB3) to enable RRC PDUs for the SN to be sent directly between the UE and the SN. RRC PDUs for the SN can only be transported directly to the UE for SN RRC reconfiguration not requiring any coordination with the MN. Measurement reporting for mobility within the SN can be done directly from the UE to the SN if SRB3 is configured. In NR-DC, the UE can be configured to establish a SRB with the SN (SRB5) to enable RRC messages which include application layer measurement report information to be sent directly between the UE and the SN. The application measurement report can be sent directly from the UE to the SN if SRB5 is configured and indicated by the network for the application measurement reporting. Split SRB is supported for all MR-DC options, allowing duplication of RRC PDUs generated by the MN, via the direct path and via the SN. Split SRB uses NR PDCP. This version of the specification does not support the duplication of RRC PDUs generated by the SN via the MN and SN paths. In EN-DC, the SCG configuration is kept in the UE during suspension. During connection resumption, if the UE supports resuming with EN-DC, the UE can be configured to release, restore, or reconfigure the SCG configuration. Otherwise, the UE releases the SCG configuration (but not the radio bearer configuration) during resumption initiation. In MR-DC with 5GC, the UE stores the PDCP/SDAP configuration and the SCG configuration when moving to RRC Inactive. During connection resumption, if the UE supports resuming with MR-DC, the UE can be configured to release, restore, or reconfigure the SCG configuration. Otherwise, it releases the SCG configuration. Figure 4.2.1-1: Control plane architecture for EN-DC (left) and MR-DC with 5GC (right).

3GPP TS 37.340

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

RAN2

3GPP Series : 37 , Multiple radio access technology aspects

4.2.1

5.2.6.23 Nnef_AMInfluence service 5.2.6.23.1 General

Service description: This service is to authorize the request and store in the UDR application data that can be retrieved by relevant PCFs in order to influence access and mobility management policies of one or multiple UEs. This service allows the NF consumer to subscribe/unsubscribe the notification of events about 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.23

– FreqBandList

The IE FreqBandList is used by the network to request NR CA, NR non-CA and/or MR-DC band combinations for specific NR and/or E-UTRA frequency bands and/or up to a specific number of carriers and/or up to specific aggregated bandwidth. This is also used to request feature sets (for NR) and feature set combinations (for NR and MR-DC). For NR sidelink communication, this is used by the initiating UE to request sidelink UE radio access capabilities from the peer UE. This is also used to request lower MSD capability for specific NR frequency bands for the UE supporting lower MSD. FreqBandList information element -- ASN1START -- TAG-FREQBANDLIST-START FreqBandList ::= SEQUENCE (SIZE (1..maxBandsMRDC)) OF FreqBandInformation FreqBandInformation ::= CHOICE { bandInformationEUTRA FreqBandInformationEUTRA, bandInformationNR FreqBandInformationNR } FreqBandInformationEUTRA ::= SEQUENCE { bandEUTRA FreqBandIndicatorEUTRA, ca-BandwidthClassDL-EUTRA CA-BandwidthClassEUTRA OPTIONAL, -- Need N ca-BandwidthClassUL-EUTRA CA-BandwidthClassEUTRA OPTIONAL -- Need N } FreqBandInformationNR ::= SEQUENCE { bandNR FreqBandIndicatorNR, maxBandwidthRequestedDL AggregatedBandwidth OPTIONAL, -- Need N maxBandwidthRequestedUL AggregatedBandwidth OPTIONAL, -- Need N maxCarriersRequestedDL INTEGER (1..maxNrofServingCells) OPTIONAL, -- Need N maxCarriersRequestedUL INTEGER (1..maxNrofServingCells) OPTIONAL -- Need N } AggregatedBandwidth ::= ENUMERATED {mhz50, mhz100, mhz150, mhz200, mhz250, mhz300, mhz350, mhz400, mhz450, mhz500, mhz550, mhz600, mhz650, mhz700, mhz750, mhz800} -- TAG-FREQBANDLIST-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

5.8.2.13.3 Support for user plane traffic replication in a 5G VN

5.8.2.13.3.1 User plane traffic replication based on UPF internal functionality For Ethernet PDU Sessions, the SMF may instruct the UPF to route traffic to be replicated as described in clause 5.8.2.5. For IP PDU Session types, the SMF may instruct the UPF to manage IP multicast traffic as described in clauses 4.6.6 and 7.7.1 of TS 23.316[ Wireless and wireline convergence access support for the 5G System (5GS) ] [84]. The UPF replicates the IP multicast traffic received from PDU Sessions or N6 interface and sends the packets over other PDU Sessions and other N6 interface subscribed to the IP Multicast groups. Mechanisms described in clauses 4.6.6 and 7.7.1 of TS 23.316[ Wireless and wireline convergence access support for the 5G System (5GS) ] [84] apply to support 5G VN group communication with following clarifications: - These mechanisms are not limited to Wireline access and can apply on any access, - IP Multicast traffic allowed for a PDU Session is not meant for IPTV services reachable over N6, - IGMP /MLD signalling does not relate with STB or 5G-RG: Clauses 4.6.6 and 7.7.1 of TS 23.316[ Wireless and wireline convergence access support for the 5G System (5GS) ] [84], apply to UE members of a 5G VN group instead of 5G-RG, and - Clauses 7.7.1.1.2 and 7.7.1.1.4 of TS 23.316[ Wireless and wireline convergence access support for the 5G System (5GS) ] [84] are not applicable to 5G VN groups: members of the 5G VN groups may receive any multicast traffic associated with the (DNN, S-NSSAI) of the 5G VN group. - UPF exchange of signalling such as PIM (Protocol-Independent Multicast) may apply as defined in TS 23.316[ Wireless and wireline convergence access support for the 5G System (5GS) ] , with following clarification: - PIM signalling is generally exchanged over N6 but may be sent towards the PDU Session supporting the source address of multicast traffic identified by IGMP / MLD signalling for Source Specific Multicast. In the case of IGMP / MLD signalling not related with Source Specific Multicast no PIM signalling is sent towards any PDU Session 5.8.2.13.3.2 User plane traffic replication based on PDRs with replication instructions Alternatively, for IP or Ethernet type data communication, the SMF instructs the UPF via PDRs and FARs how to replicate user plane traffic. The mechanism is supported in the following conditions: - When N19 is used, there is a full mesh of N19 tunnels between UPFs controlled by each SMF Set serving the 5G VN group; - There is no support for forwarding a broadcast/multicast packet with source address not known to SMF/UPF. - Each UPF supports one N6 interface instance towards the data network, or only supports N19-based forwarding without N6; - Multicast group formation of selected members of a 5G VN for Ethernet type data communication is not described in this release of the specification. In this case, when the UPF receives a broadcast packet of a 5G VN group from N19 or N6, it shall distribute it to all 5G VN group members connected to this UPF. When the UPF receives a broadcast packet from a UE (source UE) via PDU Session associated with a 5G VN group, it shall distribute it to: - All 5G VN group members (except the source UE) connected to this UPF via local switch; and - All 5G VN group members connected to other UPFs via N19-based forwarding or N6-based forwarding; and - The devices on the DN via N6-based forwarding. To enable broadcast traffic forwarding of a 5G VN group in a UPF, the following applies: - The SMF provides group-level N4 Session and each 5G VN group member' N4 Session with the PDR that detect the broadcast packet sent via "internal interface". When UPF receives the broadcast packets sent via "internal interface", it matches the broadcast packet against all PDRs installed at the "internal interface". A successful matching with a PDR that detect the broadcast packet instructs the UPF to continue the lookup of the other PDRs. A matching PDR that detects the broadcast packet shall instruct the UPF to duplicate the broadcast packet and perform processing (using associated FAR, URR, QER) on the copy instead of the original packet if the broadcast packet does not satisfy the packet replication skip information, otherwise the PDR instructs the UPF to skip the processing of the broadcast packet. - The broadcast packets received from N19 or N6 are forwarded to the UPF internal interface together with a N19 or N6 indication. - The SMF provides for each 5G VN group member' N4 Session (i.e. N4 session corresponding to PDU Session) the following N4 rules that enable the processing of broadcast packets towards this UE. - in order to detect the traffic, a PDR containing Source Interface set to "5G VN internal", Destination Address set to the broadcast address, the Packet replication skip information set to the IP/MAC address (es) of this 5G VN group member, and the indication to carry on matching; and - in order to forward the traffic, a FAR containing Outer Header Creation indicating the PDU Session tunnel information, and Destination Interface set "access side". - The SMF configures the group-level N4 Session for processing packets received from a N19 tunnel with the following N4 rules for each N19 tunnel. - in order to detect the traffic, a PDR containing Source Interface set to "core side", Destination Address set to the broadcast address, and CN Tunnel Information set to N19 tunnel header (i.e. N19 GTP-U TEID); and - in order to forward the traffic, a FAR containing Destination Interface set to "5G VN internal", Outer Header Creation with the N19 indication. - The SMF provides for the group-level N4 Session the following N4 rules that enable the processing of broadcast packets towards the other UPFs. - in order to detect the traffic, a PDR containing Source Interface set to "5G VN internal", Destination Address set to the broadcast address, the Packet replication skip information set to the N19 indication, and the indication to carry on matching; and - in order to forward the traffic to each involved UPF via the corresponding N19 tunnel, a FAR containing "Duplication" instruction, Outer Header Creation indicating the N19 tunnel information, Destination Interface set to "core side". - The SMF configures the group-level N4 Session for processing packets received from N6 with the following N4 rules. - in order to detect the traffic, a PDR containing Source Interface set to "core side", and Destination Address set to the broadcast address; and - in order to forward the traffic, a FAR containing Destination Interface set to "5G VN internal", Outer Header Creation with the N6 indication. - The SMF provides for the group-level N4 Session the following N4 rules that enable the processing of broadcast packets towards N6. - in order to detect the traffic, a PDR containing Source Interface set to "5G VN internal" and Destination Address set to the broadcast address and the Packet replication skip information set to the N6 indication; and - in order to forward the traffic to N6, a FAR containing Destination Interface set to "core side". In this case, to enable multicast traffic forwarding of a 5G VN group in a UPF, broadcast traffic forwarding of a 5G VN applies to multicast traffic forwarding of a 5G VN with the following modifications: - The SMF installs PDRs for the multicast address instead of the broadcast address. - The PDRs and FARs are installed for PDU Sessions corresponding to the members of the multicast group. - In addition, the SMF installs the PDR identifying IGMP/MLD signalling for each 5G VN group member' N4 Session and a URR with a Reporting Trigger set to "IGMP reporting" for IGMP or set to "MLD reporting" for MLD. Based on the IP Multicast address in "IP multicast join" or "IP multicast leave" reports received from UPF, the SMF manipulates (delete or add) the PDR identifying the multicast traffic for the reported IP Multicast address at the corresponding 5G VN group member' N4 Session, and if required at the group-level N4 Session at the UPF(s) of the 5G VN group.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.8.2.13.3

20.7 Use of the Supported-Features AVP on the SGmb reference point

The Supported-Features AVP is used during session establishment to inform the destination host about the required and optional features that the origin host supports. The client shall, in the first request in a Diameter session indicate the set of supported features. The server shall, in the first answer within the Diameter session indicate the set of features that it has in common with the client and that the server shall support within the same Diameter session. Any further command messages shall always be compliant with the list of supported features indicated in the Supported-Features AVPs during session establishment. Features that are not advertised as supported shall not be used to construct the command messages for that Diameter session. Unless otherwise stated, the use of the Supported-Features AVP on the SGmb reference point shall be compliant with the requirements for dynamic discovery of supported features and associated error handling on the Cx reference point as defined in clause 7.2.1 of 3GPP TS 29.229[ Cx and Dx interfaces based on the Diameter protocol; Protocol details ] [105]. The base functionality for the SGmb reference point is the 3GPP Rel-11 standard and a feature is an extension to that functionality. If the origin host does not support any features beyond the base functionality, the Supported-Features AVP may be absent from the SGmb commands. As defined in clause 7.1.1 of 3GPP TS 29.229[ Cx and Dx interfaces based on the Diameter protocol; Protocol details ] [105], when extending the application by adding new AVPs for a feature, the new AVPs shall have the M bit cleared and the AVP shall not be defined mandatory in the command ABNF. As defined in 3GPP TS 29.229[ Cx and Dx interfaces based on the Diameter protocol; Protocol details ] [105], the Supported-Features AVP is of type grouped and contains the Vendor-Id, Feature-List-ID and Feature-List AVPs. On the SGmb reference point, the Supported-Features AVP is used to identify features that have been defined by 3GPP and hence, for features defined in this document, the Vendor-Id AVP shall contain the vendor ID of 3GPP (10415). If there are multiple feature lists defined for the SGmb reference point, the Feature-List-ID AVP shall differentiate those lists from one another. On receiving an initial request application message, the destination host shall act as defined in clause 7.2.1 of 3GPP TS 29.229[ Cx and Dx interfaces based on the Diameter protocol; Protocol details ] [105]. The following exceptions apply to the initial RAR/RAA command pair: - If the BM-SC supporting post-Rel-11 SGmb functionality is able to interoperate with a MBMS GW supporting Rel-11, the RAR shall include the features supported by the BM-SC within Supported-Features AVP(s) with the ‘M’ bit cleared. Otherwise, the RAR shall include the supported features within the Supported-Features AVP(s) with the M-bit set. NOTE 1: One instance of Supported-Features AVP is needed per Feature-List-ID. - If the RAR command does not contain any Supported-Features AVP(s) and the MBMS GW supports Rel-11 SGmb functionality, the RAA command shall not include the Supported-Features AVP. In this case, both BM-SC and MBMS GW shall behave as specified in the Rel-11 version of this document. - If the RAR command contains the Supported-Features AVP, the MBMS GW shall include the Supported-Features AVP in the RAA command, with the ‘M’ bit cleared, indicating only the features that both the BM-SC and MBMS GW support. NOTE 2: The client will always declare all features that are supported according to table 20.7.1. When more than one feature identifying a release is supported by both BM-SC and MBMS GW, the BM-SC will work according to the latest common supported release. Once the BM-SC and MBMS GW have negotiated the set of supported features during session establishment, the set of common features shall be used during the lifetime of the Diameter session. The table below defines the features applicable to the SGmb interface for the feature list with a Feature-List-ID of 1. Table 20.7.1: Features of Feature-List-ID 1 used in SGmb

3GPP TS 29.061

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

CT WG3

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

20.7

5.2 Call establishment procedures

Establishment of a call is initiated by request of upper layer in either the mobile station or the network; it consists of: - the establishment of a CC connection between the mobile station and the network; - the activation of the codec or interworking function. Whenever it is specified in the present document clause 5 that the mobile station shall attach the user connection, this means that the mobile station shall activate the codec or interworking function as soon as an appropriate channel is available. The mobile station shall de-activate the codec or interworking function whenever an appropriate channel is no longer available. As soon as an appropriate channel is (again) available, the codec or interworking function shall be re-activated. If a new order to attach the user connection is received, the new order shall supersede the previous one. A channel shall be considered as appropriate if it is consistent with the possibly negotiated bearer capability applicable for the actual phase of the call. The mobile station shall not consider a channel as not appropriate because the type of the channel (full rate/half rate) is not the preferred one. If: - the user connection has to be attached but no appropriate channel is available for a contiguous time of 30 seconds; or if - the codec or interworking function is de-activated for a contiguous time of 30 seconds; then the mobile station may initiate call clearing. Upon request of upper layers to establish a call, restricting conditions for the establishment of the call are examined. These restricting conditions concern the states of parallel CC entities and are defined elsewhere. If these restricting conditions are fulfilled, the call establishment is rejected. Otherwise a CC entity in state U0, "null", is selected to establish the call. It initiates the establishment by requesting the MM sublayer to establish an MM connection. In Iu mode, if the lower layers indicate the release of a radio access bearer, whereas the corresponding call is still active, the MS shall not automatically initiate the release of that call.

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

5.2

4.11.4.3.4 Interaction with PCC

When interworking with 5GS is supported and a SMF+PGW-C is selected by the ePDG, policy interactions between PDN GW and PCRF specified in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [26] are replaced by equivalent interactions between SMF+PGW-C and PCF as captured in clause 4.11.0a.2. If SMF+PGW-C is selected and interaction with PCF is required for a UE that does not support 5GC NAS, the SMF+PGW-C determines the PDU Session ID and S-NSSAI in the same way as for PDN connection via MME as specified in clause 4.11.0a.5.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.11.4.3.4

10.3 Timers of 5GS session management

Timers of 5GS session management are shown in table 10.3.1 and table 10.3.2. NOTE: Timer T3396 is defined in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [12]. Table 10.3.1: Timers of 5GS session management – UE side NOTE 1: The back-off timer is used to describe a logical model of the required UE behaviour. This model does not imply any specific implementation, e.g. as a timer of timestamp. NOTE 2: Reference to back-off timer in this section can either refer to use of timer T3396 or to use of a different packet system specific timer within the UE. Whether the UE uses T3396 as a back-off timer or it uses different packet system specific timers as back-off timers is left up to UE implementation. Table 10.3.2: Timers of 5GS session management – SMF side

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

10.3

5.8.9.1a.3 Sidelink SRB release

The UE shall: 1> if a PC5-RRC connection release for a specific destination is requested by upper layers or AS layer; or 1> if the sidelink radio link failure is detected for a specific destination: 2> release the PDCP entity, RLC entity and the logical channel of the sidelink SRB for PC5-RRC message of the specific destination; 2> consider the PC5-RRC connection is released for the destination. 1> if PC5-S transmission for a specific destination is terminated in upper layers: 2> release the PDCP entity, RLC entity and the logical channel of the sidelink SRB(s) for PC5-S message of the specific destination; 1> if discovery transmission for a specific destination is terminated in upper layers: 2> release the PDCP entity, RLC entity and the logical channel of the sidelink SRB4 for discovery message of the specific destination; Editor's Note: FFS on how to release SL SRB on E2E and hop configuration for U2U relay.

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

5.8.9.1a.3

10.2.7.1.2 Mapping to resource elements

The same antenna port shall be used for all symbols of the narrowband primary synchronization signal within a subframe. UE shall not assume that the narrowband primary synchronization signal is transmitted on the same antenna port as any of the downlink reference signals. The UE shall not assume that the transmissions of the narrowband primary synchronization signal in a given subframe use the same antenna port, or ports, as the narrowband primary synchronization signal in any other subframe. The sequences shall be mapped to resource elements in increasing order of first the index and then the index in subframe 5 in every radio frame. For resource elements overlapping with resource elements where cell-specific reference signals according to clause 6.10 are transmitted, the corresponding sequence element is not used for the NPSS but counted in the mapping process.

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

10.2.7.1.2

4.3.20.2.2 Attach for RN preconfiguration

The RN attaches to the E-UTRAN/EPC as a UE at power-up (i.e. the RN shall not include the RN indication in the RRC Connection establishment signalling). The eNodeB treats the RN as a normal UE when performing MME selection. Because the eNodeB does not indicate that this is a RN in the S1 interface Initial UE message, the MME does not perform any further RN specific actions (e.g. it ignores any indication from the HSS that "this subscription includes a permission to operate as a RN"). The authentication of the "RN acting as an UE" is performed by the MME during this attach procedure, using the information obtained from the HSS. The MME performs the S-GW and P-GW selection as for a normal UE. NOTE: It is the responsibility of the HSS operator to ensure that the RN subscription includes an APN configuration that ensures that the RN subscription cannot be used for other purposes, e.g. only a single APN is configured for the use of RNs in phase I, and, that this APN is reserved for RNs only. The RN retrieves initial RN configuration parameters as user plane traffic, across the SGi reference point, from RN OAM (e.g. list of DeNB cells and selected PLMN). After this operation is complete, the RN detaches from the network using the normal UE initiated detach procedure, see clause 5.3.8.2.1 and the RN triggers Phase II.

3GPP TS 23.401

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

SA WG2

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

4.3.20.2.2

5.2.5.5.2 Npcf_BDTPolicyControl_Create service operation

Service operation name: Npcf_BDTPolicyControl_Create Description: This service is to create the background data transfer policy. Inputs, Required: ASP identifier, Volume per UE, Number of UEs, Desired time window. Inputs, Optional: S-NSSAI, DNN, Internal Group Identifier, Network Area Information, Request for notification, MAC address or IP 3-tuple of Application server. Outputs, Required: one or more background data transfer policies, Background Data Transfer Reference ID. Outputs, Optional: None.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

5.2.5.5.2

4.11.0a.7 Interactions with DN-AAA Server

EAP-based secondary authentication and authorization at PDU Session establishment is supported as defined in clause 4.3.2.3. EAP-based secondary authentication and authorization at PDN connection establishment is supported as defined in Annex H. This clause 4.11.0a.7 defines the support of secondary authorization over EPS without EAP-based authentication when one of the UE, the 5GC and the DN does not support (or is configured not to use) the mechanisms defined in Annex H. NOTE 1: This implies that when data connectivity to the DN is initiated as a PDU Session over 5GC it can be subject to EAP based secondary authentication mechanism (see TS 33.501[ Security architecture and procedures for 5G System ] [15]) whereas, when data connectivity to the same DN is initiated as a PDN connection over EPC it cannot be subject to EAP based secondary authentication mechanism. This discrepancy occurs regardless of whether the data connection is later on moved between EPC and 5GC. NOTE 2: Secondary authorization without authentication means no signalling exchange with the UE. If secondary authentication and authorization has been performed for the PDU Session while the UE was in 5GS and the UE has moved to EPS, the following applies: - DN-AAA re-authorization (without re-authentication signalling) can be performed even when the UE is in EPS, e.g. to provide new parameters from the DN-AAA Server to SMF+PGW-C. - Re-authentication cannot be performed while the UE is in EPS because there is no support of the related signalling in EPS. In case the SMF+PGW-C receives a re-authentication request from the DN-AAA, the SMF+PGW-C informs the DN-AAA Server that the UE is not available for re-authentication at the moment. The SMF+PGW-C should not initiate PDN connection release at this point: the DN-AAA decides the actions to take, based on the reply from SMF+PGW-C and local policy which may also trigger a DN-AAA Server request to release the PDU Session/PDN connection of the UE.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.11.0a.7

7.6 Transport of NAS Messages

NR provides reliable in-sequence delivery of NAS messages over SRBs in RRC, except at handover where losses or duplication can occur when PDCP is re-established. In RRC, NAS messages are sent in transparent containers. Piggybacking of NAS messages can occur in the following scenarios: - At bearer establishment/modification/release in the DL; - For transferring the initial NAS message during connection setup and connection resume in the UL. NOTE: In addition to the integrity protection and ciphering performed by NAS, NAS messages can also be integrity protected and ciphered by PDCP. Multiple NAS messages can be sent in a single downlink RRC message during PDU Session Resource establishment or modification. In this case, the order of the NAS messages contained in the RRC message shall be in the same order as that in the corresponding NG-AP message in order to ensure the in-sequence delivery of NAS messages. NG-RAN node may trigger the NAS Non Delivery Indication procedure to report the non-delivery of the non PDU Session related NAS PDU received from the AMF as specified in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [26].

3GPP TS 38.300

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

RAN2

3GPP Series : 38 , Radio technology beyond LTE

7.6

28.15.3 User Location Information for RG accessing the 5GC via W-5GCAN (HFC Node ID)

The User Location information for a 5G-CRG/FN-CRG accessing the 5GC via a Wireline 5G Cable Access network (W-5GCAN) shall take the form of an HFC Node ID. The HFC Node ID consists of a string of up to six characters as specified in CableLabs WR-TR-5WWC-ARCH [134]. The User Location information shall include the GCI and HFC Node ID for a AUN3 device connected behind the 5G-CRG (see clause 7.2.8.1 of 3GPP TS 23.316[ Wireless and wireline convergence access support for the 5G System (5GS) ] [131]).

3GPP TS 23.003

Numbering, addressing and identification

CT WG4

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

28.15.3

D.4.1.0 Overview

An energy-automation domain that now has standards based support by mobile-network technology is the backhaul electricity grid, i.e. the part of the distribution grid between primary substations (high voltage medium voltage) and secondary substations (medium voltage low voltage), and other smart grid services. In figure D.4.1.0-1 we depict a medium-voltage ring together with energy-automation use cases that either are already deployed or are anticipated within the near future. Figure D.4.1.0-1: Functional, topological sketch of a medium-voltage ring. AMI: advanced metering infrastructure; CB: circuit breaker; DMS: distribution management system; FISR: fault isolation and system restoration; HEM: home energy manager; PQ: power quality; RMU: ring main unit. The primary substation and the secondary substations are supervised and controlled by a distribution-management system (DMS). If energy-automation devices in the medium-voltage power line ring need to communicate with each other and /or the DMS, a wireless backhaul network needs to be present (orange "cloud" in figure D.4.1.0-1). A majority of applications in electricity distribution adhere to the communication standard IEC 60870-5-104. However, its modern "cousin" IEC 61850 experiences rapidly increasing popularity. The communication requirements for IEC 61850 applications can be found in EC 61850-90-4. Communication in wide-area networks is described in IEC 61850-90-12. Usually, power line ring structures have to be open in order to avoid a power-imbalance in the ring (green dot in figure D.4.1.0 1). Examples for energy-automation that already is implemented in medium-voltage grids (albeit in low numbers) are power-quality measurements and the measurement of secondary-substation parameters (temperature, power load, etc.) [13]. Other use cases are demand response and the control of distributed, renewable energy resources (e.g. photovoltaics). A use case that could also be realised in the future is fault isolation and system restoration (FISR). FISR automates the management of faults in the distribution grid. It supports the localization of the fault, the isolation of the fault, and the restoration of the power delivery. For this kind of automation, the pertinent sensors and actuators broadcast telegrams about their states (e.g., "emergency closer idle") and about actions (e.g., "activating closer") into the backhaul network. This information is used by the ring main units (RMUs) as input for their decision algorithms. We illustrate this use of automation telegrams for an automated FISR event in figure D.4.1.0-1. Let us assume the distribution lines are cut at the location indicated by the bolt of lightning in the figure. In that case, the RMUs between the bolt and the green load switch (open) will be without power. The RMUs next to the "bolt" automatically open their load switches after having sensed the loss of electric connectivity between them. They both broadcast these actions into the backhaul network. Typically, these telegrams are repeated many times while the time between adjacent telegrams increases exponentially. This communication patterns leads to sudden, distributed surges in the consumed communication bandwidth. After the RMUs next to the "bolt" have opened their switch, the RMU that so far has kept the power line ring open (green dot in figure D.4.1.0-1) closes the load switch. This event too is broadcasted into the backhaul network. The typical maximum end-to-end latency for this kind of broadcast is 25 ms with a peak experienced data rate of 10 Mbit/s. Note that the distribution system typically subscribes to telegrams from all RMUs in order to keep abreast with the happenings in the distribution grid. Automatic fault handling in the distribution grid shortens outage time and offloads the operators in the distribution control centre for more complicated situations. Therefore, automated FISR can help to improve performance indexes like System Average Interruption Duration Index and System Average Interruption Frequency Index. Automation telegrams are typically distributed via domain multicast. As explained above, the related communication pattern can be "bursty", i.e. only few automation telegrams are sent when the distribution network operates nominally (~ 1 kbit/s), but, for instance, a disruption in the power line triggers a short-lived avalanche of telegrams from related applications in the ring (≥ 1 Mbit/s).

3GPP TS 22.261

Service requirements for the 5G system

SA WG1

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

D.4.1.0

4.7.13 Service Request procedure (Iu mode only)

The purpose of this procedure is to transfer the PMM mode from PMM-IDLE to PMM-CONNECTED mode, and/or to assign radio access bearer in case of PDP contexts are activated without radio access bearer assigned. In latter case, the PMM mode may be PMM-IDLE mode or may alternatively be the PMM-CONNECTED mode if the MS requires radio access bearer re-establishment. This procedure is used for; - the initiation of CM layer service (e.g. SM or SMS) procedure from the MS in PMM-IDLE mode, - the network to transfer down link signalling, - uplink (in PMM-IDLE or PMM CONNECTED) and downlink (only in PMM-IDLE) user data, - counting the number of mobile stations in a cell which are interested in a specific MBMS service. - requesting the establishment of a point-to-point Radio Bearer for receiving a MBMS service. For downlink transfer of signalling or user data in PMM-IDLE mode, the trigger is given from the network by the paging request procedure, which is out of scope of the present document. For pending downlink user data in PMM-CONNECTED mode, the re-establishment of radio access bearers for all active PDP contexts is done without paging. For counting the number of mobile stations in PMM-IDLE mode interested in a specific MBMS service, the trigger is given from the network by the MBMS notification procedure (see 3GPP TS 25.331[ None ] [23c]). For establishing a point-to-point radio bearer to allow MBMS service, the trigger is given from the RRC determining this need from the MBMS control parameters broadcasted by the network (see 3GPP TS 25.331[ None ] [23c]). Service type can take either of the following values; "signalling", "data", "paging response", "MBMS multicast service reception" or "MBMS broadcast service reception". Each of the values shall be selected according to the criteria to initiate the Service request procedure. If the MS is triggered to send a Service Request message for both MBMS multicast service and MBMS broadcast service simultaneously, the MS shall include a Service Type indicating "MBMS multicast service reception". The criteria to invoke the Service request procedure are when: a) the MS has any signalling messages except GMM messages (e.g. for SM or SMS) to be sent to the network in PMM-IDLE mode (i.e., no secure PS signalling connection has been established). In this case, the service type shall be set to "signalling". b) the MS, either in PMM-IDLE or PMM-CONNECTED mode, has pending user data to be sent, no radio access bearer is established for the corresponding PDP context, and timer T3319 (see subclause 4.7.13.3) is not running or, optionally, if timer T3319 is running and the flag in the Uplink data status IE for this PDP context has not been set in the last Service Request. The procedure is initiated by an indication from the lower layers (see 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [20]). In this case, the service type shall be set to "data". c) the MS receives a paging request using P-TMSI for PS domain from the network in PMM-IDLE mode. In this case, the service type shall be set to "paging response". d) the MS is in PMM-IDLE mode or PMM-CONNECTED, receives an MBMS notification for an MBMS multicast service for which the MS has activated an MBMS context or for an MBMS broadcast service which has been selected for reception locally by upper layers in the MS, and is prompted by the contents of the notification to establish a PS signalling connection (see 3GPP TS 25.346[ None ] [110]). In this case, the service type shall be set to "MBMS multicast service reception" or "MBMS broadcast service reception", respectively. e) the MS in PMM-IDLE mode or PMM-CONNECTED, determines from the broadcast MBMS control parameters that there is a need to establish a point-to-point Radio Bearer to enable MBMS reception (see 3GPP TS 25.346[ None ] [110]). In this case, the service type shall be set to "MBMS multicast service reception" or "MBMS broadcast service reception", respectively. If one of the above criteria to invoke the Service request procedure is fulfilled, then the Service request procedure may only be initiated by the MS when the following conditions are fulfilled: - its GPRS update status is GU1 UPDATED and the stored RAI is equal to the RAI of the current serving cell; and - no GMM specific procedure is ongoing (see subclause 4.1.1.1). If a GMM specific procedure is ongoing at the time a request from CM sublayer, the RRC or the RABM (see 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [20]) is received and the ATTACH REQUEST or ROUTING AREA UPDATE REQUEST message has been sent, then, depending on implementation, the MS shall abort the received request or delay it until the GMM specific procedure is completed. If the ATTACH REQUEST or ROUTING AREA UPDATE REQUEST message has not been sent, the MS may indicate "follow-on request pending" in the message (i.e. the MS wishes to prolong the established PS signalling connection after the GMM specific procedure). Then, the MS shall delay the Service request procedure until the GMM specific procedure is completed. If the network indicates "follow-on proceed" in the ATTACH ACCEPT or ROUTING AREA UPDATE ACCEPT message and the MS has a service request pending, the MS shall react depending on the service type. If the service type is: - "signalling": the MS shall abort the Service request procedure and send the pending signalling messages immediately; - "data": the MS shall immediately perform the pending Service request procedure using the current PS signalling connection; - "paging response": the MS shall abort the Service request procedure. No further specific action is required from the MS. If the network indicates "follow-on proceed" and the MS has no service request pending, then no specific action is required from the MS. As an implementation option, the MS may start timer T3340 as described in subclause 4.7.1.9 if no user plane radio access bearers are set up. If the network indicates "no follow-on proceed" in the ATTACH ACCEPT or ROUTING AREA UPDATE ACCEPT message, the MS shall not initiate the pending Service request procedure until the current PS signalling connection is released. NOTE: The "follow-on proceed" indication was not defined in earlier versions of the protocol. A network that is compliant with the earlier versions of the protocol will always encode the respective bit as zero, i.e. as "follow-on proceed", even if it does not prolong the PS signalling connection. After completion of a Service request procedure but before re-establishment of radio access bearer, if the PDP and MBMS context status information elements are included, then the network shall deactivate all those PDP and MBMS contexts locally (without peer to peer signalling between the MS and the network), which are not in SM state PDP-INACTIVE on network side but are indicated by the MS as being in state PDP-INACTIVE. After completion of a Service request procedure, the pending service is resumed and uses then the connection established by the procedure. If the service type is indicating "data", then the radio access bearers for all activated PDP contexts are re-established by the network, except for those activated PDP contexts having maximum bit rate value set to 0 kbit/s for both uplink and downlink and as an option those which have no pending user data. The re-establishment of radio access bearers for those PDP contexts is specified in subclause 6.1.3.3. A service request attempt counter is used to limit the number of service request attempts and no response from the network. The service request attempt counter shall be incremented as specified in subclause 4.7.13.5. The service request attempt counter shall be reset when: - an attach or combined attach procedure is successfully completed; - a normal or periodic routing area updating or a combined routing area updating procedure is successfully completed; - a service request procedure is successfully completed ; or - the UE moves to GMM-DEREGISTERED state.

3GPP TS 24.008

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

CT WG1

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

4.7.13

5.2.6.12.2 Nnef_APISupportCapability_Subscribe service operation

Service operation name: Nnef_APISupportCapability_Subscribe Description: The AF subscribes to receive notification about the availability or expected level of support of a service API for a UE or a group of UEs. Inputs, Required: UE ID or External Group ID, Report Type (One-time report or Continuous report). Inputs, Optional: Duration of Reporting, callback URI. Outputs, Required: Operation execution result indication. When the subscription is accepted: Subscription Correlation ID, API indication.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

5.2.6.12.2

4.4.3.2 N4 Association Update Procedure

The N4 Association Update procedure shall be used to modify an existing N4 association between the SMF and the UPF. It may be initiated by the UPF or by the SMF to update the supported features or available resources of the UP function. N4 Association Update procedure can be used by the SMF to update the provisioning of External Clock Drift Report as specified in clause 4.4.3.1. Figure 4.4.3.2-1: SMF initiated N4 association update procedure Figure 4.4.3.2-2: UPF initiated N4 association update procedure

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.4.3.2

5.37 Support for high data rate low latency services, eXtended Reality (XR) and interactive media services 5.37.1 General

This clause provides an overview of 5GS functionalities for support of XR services (AR/VR applications) and interactive media services that require high data rate and low latency communication, e.g. cloud gaming and tactile/multi-modal communication services according to service requirements documented in TS 22.261[ Service requirements for the 5G system ] [2]. The standardized 5QI characteristics for such interactive services are provided in Table 5.7.4-1 and TSCAI is used to describe the related traffic characteristics as defined in clause 5.27.2. Further enhancements for these interactive media services are as follows: - The 5GS may support QoS policy control for multi-modal traffic, see clause 5.37.2. - The 5GS may support network information exposure which can be based on ECN markings for L4S, see clause 5.37.3 or 5GS exposure API, see clause 5.37.4. - The 5GS may support PDU Set based QoS handling including PDU Set identification and marking, see clause 5.37.5. - The 5GS may ensure that the UL and DL packets together meet the requested round trip delay and also update the delay for UL and DL considering QoS monitoring results, see clause 5.37.6. - The 5GS may perform per-flow Packet Delay Variation (PDV) monitoring and policy control according to AF provided requirements, see clause 5.37.7. - The 5GC may provide traffic assistance information to the NG-RAN to enable Connected mode DRX power saving, see clause 5.37.8.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.37

4.13.2.6 Number of successful additions of LWA DRB

a) This measurement provides the number of successful additions of LWA DRB. b) CC c) On receipt of RRCConnectionReconfigurationComplete message (see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [18]) by the eNB, corresponding to the transmitted RRCConnectionReconfiguration message which triggered the measurement "Number of attempted additions of LWA DRB" (see clause 4.13.2.5). d) An integer value e) LWI.LwaDrbAddSucc f) WLANMobilitySet g) Valid for packet switched traffic h) EPS

3GPP TS 32.425

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

SA WG5

3GPP Series : 32 , OAM&P and Charging

4.13.2.6

O.2 Baseline for using non-5G capable devices with 5GC

N5GC devices lack some key 5G capabilities, including NAS and the derivation of 5G key hierarchy. Those devices exist in wireline networks and need to be able to access the converged 5G core. The authentication of N5GC devices can be based on additional EAP methods other than EAP-AKA’. The procedure in O.3 uses EAP-TLS as in Annex B as an example, but it differs from the Annex B in the following: a) the W-AGF creates the registration request on behalf of the N5GC device, b) 5G related parameters (including ngKSI and ABBA) are not sent to the N5GC device. When received from the AMF, these parameters are ignored by the W-AGF, and c) Neither the N5GC device nor the AUSF derives any 5G related keys after EAP authentication.

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

O.2

– PUCCH-PathlossReferenceRS-Id

The IE PUCCH-PathlossReferenceRS-Id is an ID for a reference signal (RS) configured as PUCCH pathloss reference (see TS 38.213[ NR; Physical layer procedures for control ] [13], clause 7.2). PUCCH-PathlossReferenceRS-Id information element -- ASN1START -- TAG-PUCCH-PATHLOSSREFERENCERS-ID-START PUCCH-PathlossReferenceRS-Id ::= INTEGER (0..maxNrofPUCCH-PathlossReferenceRSs-1) PUCCH-PathlossReferenceRS-Id-v1610 ::= INTEGER (maxNrofPUCCH-PathlossReferenceRSs..maxNrofPUCCH-PathlossReferenceRSs-1-r16) PUCCH-PathlossReferenceRS-Id-r17 ::= INTEGER (0..maxNrofPUCCH-PathlossReferenceRSs-1-r17) -- TAG-PUCCH-PATHLOSSREFERENCERS-ID-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

5.31.19 QoS model for NB-IoT

5GC QoS model described in clause 5.7 applies to NB-IoT with the following requirements: - The default QoS rule shall be the only QoS rule of a PDU Session for a UE connected to 5GC via NB-IoT. There is only one QoS Flow (corresponding to the default QoS rule) per PDU session. - Reflective QoS is not supported over NB-IoT. - For NB-IoT, there is a 1:1 mapping between the QoS Flow corresponding to the default QoS of a PDU session and a Data Radio Bearer when user plane resources are active for that PDU session. - A maximum of two Data Radio Bearers are supported over NB-IoT. Therefore, at most two PDU sessions can have active user plane resources at the same time. - The capability of multiple UP resource support for NB-IoT UEs is indicated in the UE 5GMM Core Network Capability (see TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]). During PDU Session Establishment or UP resource activation, the AMF checks if the UE can support the establishment of user plane resources (See clause 4.2.3.2 and clause 4.3.2.2.1 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.31.19

5.16.4.10 Support of eCall Only Mode

For service requirements for eCall only mode, refer to TS 22.101[ Service aspects; Service principles ] [33]. A UE configured for eCall Only Mode shall remain in RM-DEREGISTERED state, shall camp on a network cell when available but shall refrain from any Registration Management, Connection Management or other signalling with the network. The UE may instigate Registration Management and Connection Management procedures in order to establish, maintain and release an eCall Over IMS session or a session to any non-emergency MSISDN(s) or URI(s) configured in the USIM for test and/or terminal reconfiguration services. Following the release of either session and after the UE has left RRC_CONNECTED state, the UE starts a timer whose value depends on the type of session (i.e. whether eCall or a session to a non-emergency MSISDN or URI for test/reconfiguration). While the timer is running, the UE shall perform normal RM/CM procedures and is permitted to respond to paging to accept and establish an incoming session (e.g. from an emergency centre, PSAP or HPLMN operator). When the timer expires, once the UE is not in RRC_CONNECTED state, the UE shall perform a UE-initiated Deregistration procedure if still registered and enter RM-DEREGISTERED state. NOTE 1: An HPLMN operator can change the eCall Only Mode configuration state of a UE in the USIM. An HPLMN operator can also instead add, modify or remove a non-emergency MSISDN or URI in the USIM for test and/or terminal reconfiguration services. This can occur following a UE call to a non-emergency MSISDN or URI configured for reconfiguration. When the eCall Only Mode configuration is removed, the UE operates as a normal UE that can support eCall over IMS. NOTE 2: A test call and a reconfiguration call can be seen as normal (non-emergency) call by a serving PLMN and normal charging rules can apply depending on operator policy. NOTE 3: An MSISDN configured in the USIM for test and/or terminal reconfiguration services for eCall Over IMS can differ from an MSISDN configured in the USIM for test services for eCall over the CS domain.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.16.4.10

5.3.5.13.2 Conditional reconfiguration removal

The UE shall: 1> for each condReconfigId value included in the condReconfigToRemoveList that is part of the current UE conditional reconfiguration in VarConditionalReconfig: 2> remove the entry with the matching condReconfigId from the VarConditionalReconfig; NOTE 1: The UE does not consider the message as erroneous if the condReconfigToRemoveList includes any condReconfigId value that is not part of the current UE configuration. NOTE 2: The UE does not consider the message as erroneous if the condExecutionCondToReleaseList includes any condReconfigId value that is not part of the current UE configuration.

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

5.3.5.13.2

8.144 SGi PtP Tunnel Address

SGi PtP Tunnel Address is coded as depicted in Figure 8.144-1. Figure 8.144-1: SGi PtP Tunnel Address The following flags are coded within Octet 5: - Bit 1 – V4: If this bit is set to "1", then the IPv4 address field shall be present, otherwise it shall be absent. Bit 2 shall be set to "0" when Bit 1 is set to "1". - Bit 2 – V6: If this bit is set to "1", then the IPv6 address field shall be present, otherwise it shall be absent. Bit 1 shall be set to "0" when Bit 2 is set to "1". - Bit 3 – Port: If this bit is set to "1", then the Port Number field shall be present, otherwise it shall be absent. When the IPv4 address field is present, octets m to (m+3) shall contains an IPv4 address. Bit 8 of Octet m represents the most significant bit of the IPv4 address and bit 1 of octet (m+3) the least significant bit. When the IPv6 address field is present, octets p to (p+15) shall contain the IPv6 Prefix and Interface Identifier. Bit 8 of octet p represents the most significant bit of the IPv6 Prefix and Interface Identifier and bit 1 of octet (p+15) the least significant bit. When the UDP port field is present, octets q to (q+1) shall contain a UDP port number. Bit 8 of Octet q represents the most significant bit of the port number and bit 1 of octet (q+1) the least significant bit.

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

8.73 MBMS IP Multicast Distribution

The MBMS IP Multicast Distribution IE is sent by the MBMS GW to the MME/SGSN in the MBMS Session Start Request. Source Specific Multicasting is used according to IETF RFC 4607 [40]. The IP Multicast Distribution Address and the IP Multicast Source Address fields contain the IPv4 or IPv6 address. The Address Type and Address Length fields shall be included in each field: - The Address Type, which is a fixed length code (of 2 bits) identifying the type of address that is used in the Address field. - The Address Length, which is a fixed length code (of 6 bits) identifying the length of the Address field. - The Address, which is a variable length field shall contain either an IPv4 address or an IPv6 address. Address Type 0 and Address Length 4 shall be used when Address is an IPv4 address. Address Type 1 and Address Length 16 shall be used when Address is an IPv6 address. Other combinations of values are not valid. MBMS HC Indicator represents an indication if header compression should be used for MBMS user plane data, as specified in 3GPP TS 25.413[ UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling ] [33]. MBMS HC Indicator field is encoded as a one octet long enumeration. NOTE: Currently, 3GPP TS 25.413[ UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling ] [33] specifies two enumeration values: 0 (indicates "uncompressed-header") and 1 (indicates "compressed-header"). Common Tunnel Endpoint Identifier is allocated at the source Tunnel Endpoint and signalled to the destination Tunnel Endpoint. There is one Common Tunnel Endpoint Identifier allocated per MBMS bearer service. The recommendations on how to set the value of C-TEID are provided in 3GPP TS 23.246[ Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description ] [37]. Figure 8.73-1: MBMS IP Multicast Distribution

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

8.13.2.6 User consent propagation in MR-DC with 5GC

As specified in TS 32.422[ Telecommunication management; Subscriber and equipment trace; Trace control and configuration management ] [20] in Management based MDT getting user consent is required before activating the MDT functionality because of privacy and legal obligations. User consent is communicated to the MN at the UE context setup procedure using the INITIAL CONTEXT SETUP REQUEST message, or in HANDOVER REQUEST and PATH SWITCH REQUEST ACKNOWLEDGE messages. Modified user consent information may be received in the UE CONTEXT MODIFICATION REQUEST message. The MN stores the received information in the UE context and uses it to allow subsequent selection of the UE for management based MDT as specified in TS 32.422[ Telecommunication management; Subscriber and equipment trace; Trace control and configuration management ] [20]. The MN will forward the MDT user consent to the SN at MR-DC setup, i.e., if available in the UE context, the MN will include the Management Based MDT PLMN List IE in the S-NODE ADDITION REQUEST message or in the S-NODE MODIFICATION REQUEST message sent to the SN. Furthermore, in NR-DC and NGEN-DC, the user consent will be forwarded to the relevant SgNB-CU-UP at the bearer context setup or to the SgNB-DU by including the Management Based MDT PLMN List information in the BEARER CONTEXT SETUP REQUEST or UE CONTEXT SETUP REQUEST. Furthermore, in NR-DC and NGEN-DC, the user consent may be updated to the relevant SgNB-CU-UP at the bearer context modification or to the SgNB-DU by including the Management Based MDT PLMN List information in the BEARER CONTEXT MODIFICATION REQUEST or UE CONTEXT MODIFICATION REQUEST. The signalling flow for User consent propagation in NR-DC and NGEN-DC is shown in Figure 8.13.2.6-1. Figure 8.13.2.6-1 User consent propagation in NR-DC and NGEN-DC 0. User Context information are made available at the AMF. 1. The AMF sends INITIAL CONTEXT SETUP REQUEST message to the MN, including the Management based MDT PLMN List IE to communicate user consent to the MN. 2. The MN sends S-NODE ADDITION REQUEST to the SgNB-CU-CP at NR-DC setup. This request includes the Management based MDT PLMN List IE. 3a. The user consent is communicated to the SgNB-DU at the UE context setup by including the Management based MDT PLMN List IE in the UE CONTEXT SETUP REQUEST. 3b. The user consent is communicated to the SgNB-CU-UP at the bearer context setup by including the Management based MDT PLMN List IE in the BEARER CONTEXT SETUP REQUEST.

3GPP TS 38.401

NG-RAN; Architecture description

RAN3

3GPP Series : 38 , Radio technology beyond LTE

8.13.2.6

5.3.23 Forbidden wireline access area

The AMF shall send a REGISTRATION REJECT, SERVICE REJECT or DEREGISTRATION REQUEST message over a wireline access network with the 5GMM cause #77 "wireline access area not allowed", if conditions specified in 3GPP TS 23.316[ Wireless and wireline convergence access support for the 5G System (5GS) ] [6D] for AMF's enforcement of forbidden area are fulfilled. If a REGISTRATION REJECT, SERVICE REJECT or DEREGISTRATION REQUEST message is received over a wireline access network with the 5GMM cause #77 "wireline access area not allowed": a) the 5G-RG shall not access 5GCN over the wireline access network until the 5G-RG is switched off, the UICC containing the USIM is removed, or the 5G-RG starts using another wireline access network; NOTE: When the 5G-RG acting on behalf of the AUN3 device receives a REGISTRATION REJECT, SERVICE REJECT or DEREGISTRATION REQUEST message over a wireline access network with the 5GMM cause #77 "wireline access area not allowed", the 5G-RG acting on behalf of the AUN3 device can prevent reattempt of the same procedure until the AUN3 device is switched off or the UICC containing the USIM of the AUN3 device is removed. b) the W-AGF acting on behalf of the FN-CRG shall not access 5GCN until the W-AGF acting on behalf of the FN-CRG determines that the FN-CRG is switched off; and c) the W-AGF acting on behalf of the N5GC device shall not access 5GCN until the W-AGF acting on behalf of the FN-CRG determines that the FN-CRG serving the N5GC device is switched off.

3GPP TS 24.501

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

CT WG1

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

5.3.23

4.7.5.1.6 Abnormal cases on the network side

The following abnormal cases can be identified: a) If a lower layer failure occurs before the message ROUTING AREA UPDATE COMPLETE has been received from the MS and a P-TMSI and/or PTMSI signature has been assigned, the network shall abort the procedure and shall consider both, the old and new P-TMSI and the corresponding P-TMSI signatures as valid until the old P-TMSI can be considered as invalid by the network (see subclause 4.7.1.5). During this period the network may use the identification procedure followed by a P-TMSI reallocation procedure if the old P-TMSI is used by the MS in a subsequent message. NOTE 1: Optionally, paging with IMSI may be used if paging with old and new P-TMSI fails. Paging with IMSI causes the MS to re-attach as described in subclause 4.7.9.1. b) Protocol error If the ROUTING AREA UPDATE REQUEST message has been received with a protocol error, the network shall return a ROUTING AREA UPDATE REJECT message with one of the following reject causes: #96: Mandatory information element error; #99: Information element non-existent or not implemented; #100: Conditional IE error; #111: Protocol error, unspecified. c) T3350 time-out On the first expiry of the timer, the network shall retransmit the ROUTING AREA UPDATE ACCEPT message and shall reset and restart timer T3350. The retransmission is performed four times, i.e. on the fifth expiry of timer T3350, the routing area updating procedure is aborted. Both, the old and the new P-TMSI and the corresponding P-TMSI signatures shall be considered as valid until the old P-TMSI can be considered as invalid by the network(see subclause 4.7.1.5). During this period the network acts as described for case a above. Figure 4.7.5/1 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Routing and combined routing area updating procedure d.1) ROUTING AREA UPDATE REQUEST received after the ROUTING AREA UPDATE ACCEPT message has been sent and before the ROUTING AREA UPDATE COMPLETE message is received - If one or more of the information elements in the ROUTING AREA UPDATE REQUEST message differ from the ones received within the previous ROUTING AREA UPDATE REQUEST message, the previously initiated routing area updating procedure shall be aborted if the ROUTING AREA UPDATE COMPLETE message has not been received and the new routing area updating procedure shall be progressed, or - If the information elements do not differ, then the ROUTING AREA UPDATE ACCEPT message shall be resent and the timer T3350 shall be restarted if an ROUTING AREA UPDATE COMPLETE message is expected. In that case, the retransmission counter related to T3350 is not incremented. d.2) More than one ROUTING AREA UPDATE REQUEST received and no ROUTING AREA UPDATE ACCEPT or ROUTING AREA UPDATE REJECT message has been sent - If one or more of the information elements in the ROUTING AREA UPDATE REQUEST message differs from the ones received within the previous ROUTING AREA UPDATE REQUEST message, the previously initiated routing area updating procedure shall be aborted and the new routing area updating procedure shall be progressed; - If the information elements do not differ, then the network shall continue with the previous routing area updating procedure and shall not treat any further this ROUTING AREA UPDATE REQUEST message. e) DETACH REQUEST message received before the ROUTING AREA UPDATE ACCEPT message is sent or before the ROUTING AREA UPDATE COMPLETE message (in case of P-TMSI and/or TMSI was allocated) is received. GPRS detach containing cause "power off": The network shall abort the signalling for the routing area updating procedure towards the MS and shall progress the detach procedure as described in subclause 4.7.4.1. NOTE 2: Internally in the network, before processing the detach request, the SGSN can perform the necessary signalling procedures for the routing area updating procedure before progressing the detach procedure. GPRS detach containing other causes than "power off": The network shall proceed with the routing area updating procedure and shall progress the detach procedure after successful completion of the routing area updating procedure. f) ROUTING AREA UPDATE REQUEST message with update type IE indicating "periodic updating" is received by the network, the network does not have the GMM context data related to the subscription, and the network operates in network operation mode I. The network may send the ROUTING AREA UPDATE REJECT message with GMM cause value #10 "Implicitly detached".

3GPP TS 24.008

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

CT WG1

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

4.7.5.1.6

D.4 Support for UE capable of simultaneously connecting to an SNPN and a PLMN

When a UE capable of simultaneously connecting to an SNPN and a PLMN and the UE is not set to operate in SNPN access mode for any of the Uu/Yt/NWu interfaces, the UE only performs PLMN selection procedures using the corresponding interface for connection to the PLMN. A UE supporting simultaneous connectivity to an SNPN and a PLMN applies the network selection as applicable for the access and network for SNPN and PLMN respectively. Whether the UE uses SNPN or PLMN for its services is implementation dependent. A UE supporting simultaneous connectivity to an SNPN and a PLMN applies the cell (re-)selection as applicable for the access and network for SNPN and PLMN respectively. Whether the UE uses SNPN or PLMN for its services is implementation dependent.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

D.4

18.4 MT-SDT with/without UE context relocation

The overall procedure for MT-SDT procedure with/without UE context relocation is illustrated in the figure 18.4-1. Figure 18.4-1: MT-SDT with/without UE context relocation 1. DL user data and/or DL NAS signalling are received at the Last Serving gNB for the UE in RRC_INACTIVE state. 2. The Last Serving gNB may send MT-SDT information to the neighbour gNBs within the RNA, via XnAP RAN PAGING message. 3. The gNB that receives MT-SDT information within the RNA, takes into account the MT-SDT information received in the XnAP RAN PAGING message to decide whether to trigger MT-SDT Paging. The gNB which ultimately reaches the UE via the Uu Paging becomes the Receiving gNB. NOTE 1: In case that the Receiving gNB decides not to trigger MT-SDT paging, the above step 3 and subsequent steps are the same as Figure 9.2.2.4.2 from step 3. 4/5. The UE may decide to initiate MT-SDT procedure and in this case sends an RRCResumeRequest message with an MT-SDT resume cause to the Receiving gNB. 6. The following steps are the same as Figure 18.2-1/18.3-1 from step 2, except that the first SDT user data and/or NAS signalling is DL SDT data and/or DL SDT NAS signalling. NOTE 2: In case DL non-SDT data or DL non-SDT signalling has arrived between step 2 and step 6, the Last Serving gNB should relocate the UE context to the Receiving gNB and forward the received data to the Receiving gNB.

3GPP TS 38.300

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

RAN2

3GPP Series : 38 , Radio technology beyond LTE

18.4

5.17.5.2.1 Interworking with N26 interface

In addition to the interworking principles documented in clause 5.17.2.2, the following applies for interworking with N26: - When UE moves from EPS to 5GS, when the AMF registers in UDM, if no event subscription via UDM is available, the AMF indicates the situation to the UDM, and in this case the UDM can decide if the event subscriptions should be provisioned, otherwise if the AMF has event subscription information, after the registration procedure is completed, the AMF may inform the UDM of the currently subscribed events, and UDM will do synchronization if needed. - When UE moves from 5GS to EPS, the MME gets monitoring event configuration from HSS during as part of mobility procedure as specified in clause 4.11.1.3.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.17.5.2.1

– SL-RadioBearerConfig

The IE SL-RadioBearerConfig specifies the sidelink DRB configuration information for NR sidelink communication. SL-RadioBearerConfig information element -- ASN1START -- TAG-SL-RADIOBEARERCONFIG-START SL-RadioBearerConfig-r16 ::= SEQUENCE { slrb-Uu-ConfigIndex-r16 SLRB-Uu-ConfigIndex-r16, sl-SDAP-Config-r16 SL-SDAP-Config-r16 OPTIONAL, -- Cond SLRBSetup sl-PDCP-Config-r16 SL-PDCP-Config-r16 OPTIONAL, -- Cond SLRBSetup sl-TransRange-r16 ENUMERATED {m20, m50, m80, m100, m120, m150, m180, m200, m220, m250, m270, m300, m350, m370, m400, m420, m450, m480, m500, m550, m600, m700, m1000, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1} OPTIONAL, -- Need R ... } -- TAG-SL-RADIOBEARERCONFIG-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

5.6.10.1 Support of IP PDU Session type

The IP address allocation is defined in clause 5.8.1 The UE may acquire following configuration information from the SMF, during the lifetime of a PDU Session: - Address(es) of P-CSCF(s); - Address(es) of DNS server(s). - If the UE indicates support of DNS with security as defined in TS 33.501[ Security architecture and procedures for 5G System ] [29] to the network in PCO and the network wants to enforce the use of DNS with security, the configuration information sent by the SMF via PCO may also include the corresponding DNS server security information as specified in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47] and TS 33.501[ Security architecture and procedures for 5G System ] [29]. - the GPSI of the UE. The UE may acquire from the SMF, at PDU Session Establishment, the MTU that the UE shall consider, see clause 5.6.10.4. The UE may provide following information to the SMF during the lifetime of a PDU Session: - an indication of the support of P-CSCF re-selection based on procedures specified in TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [62] (clauses B.2.2.1C and L.2.2.1C). - PS data off status of the UE. NOTE 2: An operator can deploy NAT functionality in the network; the support of NAT is not specified in this release of the specification, though UPF can expose mapping between public and private IP addresses.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.6.10.1

4.3.2.2.2 Home-routed Roaming

This procedure is used in the case of home-routed roaming scenarios. Figure 4.3.2.2.2-1: UE-requested PDU Session Establishment for home-routed roaming scenarios 1. This step is the same as step 1 in clause 4.3.2.2.1. 2. For NR satellite access, the AMF may decide to verify the UE location as described in clause 5.4.11.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. As in step 2 of clause 4.3.2.2.1 except that, if the UE does not include an S-NSSAI in the PDU Session request, both a Serving PLMN S-NSSAI (in the Allowed NSSAI or Partially Allowed NSSAI) and its corresponding HPLMN S-NSSAI values are selected by the AMF. Also, the AMF in the serving PLMN selects both an SMF in the Serving PLMN using the S-NSSAI of the Serving PLMN mapping to the S-NSSAIs of the HPLMN used for the PDU Session and additionally, an SMF in the HPLMN using the S-NSSAI of the HPLMN used for the PDU Session, as described in clause 4.3.2.2.3. The AMF may also receive alternative H-SMFs from the NRF. If Control Plane CIoT 5GS Optimisation is enabled for the PDU Session, the AMF selects V-SMF and H-SMF that supports the Control Plane CIoT 5GS Optimisation (see clause 6.3.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]). The AMF stores the association of the S-NSSAI(s), the DNN, the PDU Session ID, the SMF ID in VPLMN as well as Access Type of the PDU Session. Whether to perform DNN replacement is based on operator agreement. In step 3 of clause 4.3.2.2.1, in local breakout roaming case, if V-SMF responds to AMF indicating that V-SMF is not able to process some part of the N1 SM information, the AMF proceeds with home routed case from this step and may select an SMF in the VPLMN different from the V-SMF selected earlier. 3a. As in step 3 of clause 4.3.2.2.1 with the addition that: - the AMF also provides the identity of the H-SMF it has selected in step 2 and both the VPLMN S-NSSAI from the Allowed NSSAI or Partially Allowed NSSAI and the corresponding S-NSSAI of the HPLMN, which is in the mapping the VPLMN S-NSSAI from the Allowed NSSAI or Partially Allowed NSSAI. The H-SMF is provided when the PDU Session is home-routed. The AMF may also provide the identity of alternative H-SMFs, if it has received in step 2. If the AMF determines to replace the HPLMN S-NSSAI received from the UE with the HPLMN Alternative S-NSSAI or the AMF receives the HPLMN Alternative S-NSSAI and the HPLMN S-NSSAI provided by the UE, the AMF selects the H-SMF based on the HPLMN Alternative S-NSSAI. - The V-SMF does not use DNN Selection Mode received from the AMF but relays this information to the H-SMF. If the AMF is reusing an already established association with a V-SMF for the PDU Session ID provided by the UE (e.g. when Request Type indicates "existing PDU Session"), the AMF invokes the Nsmf_PDUSession_UpdateSMContext Request. The AMF may include the H-PCF ID in this step and V-SMF will pass it to the H-SMF in step 6. This will enable the H-SMF to select the same H-PCF in step 9a. If Control Plane CIoT 5GS Optimisation is used for the PDU Session and the "Invoke NEF indication" in the subscription data is set for the S-NSSAI / DNN combination, the AMF includes an "Invoke NEF" flag in Nsmf_PDUSession_CreateSMContext Request. If Disaster Roaming service indication is received, the V-SMF stores the indication in PDU session context and includes the indication in charging data. V-SMF may also apply policy and charging control based on the indication according to roaming agreement. 3b: This step is the same as step 5 of clause 4.3.2.2.1. If the PDU Session Type is Unstructured and the V-SMF received an "Invoke NEF" flag in step 3a, then it skips steps 4 and 5. 4. The V-SMF selects a UPF in VPLMN as described in clause 6.3.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 5. The V-SMF initiates an N4 Session Establishment procedure with the selected V-UPF: 5a. The V-SMF sends an N4 Session Establishment Request to the V-UPF. The V-SMF provides Trace Requirements to the V-UPF if the V-SMF has received Trace Requirements from AMF. 5b. The V-UPF acknowledges by sending an N4 Session Establishment Response. The CN Tunnel Info is provided to V-SMF in this step. 6. V-SMF to H-SMF: Nsmf_PDUSession_Create Request (SUPI, GPSI (if available), V-SMF SM Context ID, DNN, S-NSSAI with the value defined by the HPLMN, [HPLMN Alternative S-NSSAI], PDU Session ID, V-SMF ID, V-CN-Tunnel-Info, PDU Session Type, PCO, Number Of Packet Filters, User location information, Access Type, RAT Type, PCF ID, [Small Data Rate Control Status], SM PDU DN Request Container, DNN Selection Mode, Control Plane CIoT 5GS Optimisation Indication, [Always-on PDU Session Requested], AMF ID, Serving Network, [ECS Address Configuration Information asscociated with PLMN ID of visited network], the QoS constraints from the VPLMN, Satellite backhaul category, Disaster Roaming service indication) or Nsmf_PDUSession_Update Request (V-CN-Tunnel-Info, PCO, User location information, Access Type, RAT Type, SM PDU DN Request Container, Control Plane CIoT 5GS Optimisation Indication, [Always-on PDU Session Requested], Serving Network, Satellite backhaul category). Protocol Configuration Options may contain information that H-SMF may needs to properly establish the PDU Session (e.g. SSC mode or SM PDU DN Request Container to be used to authenticate the UE by the DN-AAA as defined in clause 4.3.2.3). The H-SMF may use DNN Selection Mode when deciding whether to accept or reject the UE request. If the V-SMF does not receive any response from the H-SMF due to communication failure on the N16 interface, depending on operator policy the V-SMF may create the PDU Session to one of the alternative H-SMF(s) if additional H-SMF information is provided in step 3a, as specified in detail in TS 29.502[ 5G System; Session Management Services; Stage 3 ] [36]. The Small Data Rate Control Status is included if received from the AMF. The Control Plane CIoT 5GS Optimisation Indication is set by the V-SMF, if the PDU Session is intended for Control Plane CIoT 5GS Optimisation. The QoS constraints from the VPLMN are specified in clause 5.7.1.11 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The Disaster Roaming service indication is included if the indication is received from AMF in step 3a above. NOTE 1: The QoS constraints from the VPLMN are provided by the VPLMN to avoid the risk that V-SMF rejects the PDU Session in step 13 when controlling SLA with the HPLMN. V-SMF SM Context ID contains the addressing information it has allocated for service operations related with this PDU Session. The H-SMF stores an association of the PDU Session and V-SMF Context ID for this PDU Session for this UE. If the H-SMF needs to use V-SMF services for this PDU Session (invoking Nsmf_PDUSession_Update Request) before step 13, at the first invocation of Nsmf_PDUSession_Update Request the H-SMF provides the V-SMF with the H-SMF SM Context ID it has allocated for service operations related with this PDU Session. If the RAT type was included in the message, then the H-SMF stores the RAT type in SM Context. ECS Address Configuration Information associated with PLMN ID of visited network is an optional information that may only be provided when HR-SBO is supported for roamers of HPLMN. If the V-SMF has an association with the H-SMF for the indicated PDU Session ID, the V-SMF invokes Nsmf_PDUSession_Update Request. Otherwise the V-SMF invokes Nsmf_PDUSession_Create Request. If the V-SMF receives the HPLMN Alternative S-NSSAI and the HPLMN S-NSSAI from the AMF, the V-SMF sends both the HPLMN Alternative S-NSSAI and the HPLMN S-NSSAI to the H-SMF. 7-12b. These steps are the same as steps 4-10 in clause 4.3.2.2.1 with the following differences: - These steps are executed in Home PLMN; - If the S-NSSAI of this PDU Session is subject to network slice usage control, the H-SMF configures the PDU Session inactivity timer in the H-UPF as described in clause 5.15.15 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. Otherwise, the H-SMF does not provides the inactivity timer to the H-UPF as described in step 10a in clause 4.3.2.2.1. - If the QoS constraints from the VPLMN is provided in step 6 and PCF is deployed, the H-SMF provides the QoS constraints from the VPLMN to PCF. The PCF takes this into account when making policy decisions. In case dynamic PCC is not deployed, the SMF takes this into account when generating the default QoS rule. - Step 5 of clause 4.3.2.2.1 is not executed. - If Disaster Roaming service indication is received, the SMF stores the indication in PDU session context and includes the indication in charging data. H-SMF may also apply policy and charging control based on the indication according to roaming agreement. When PCF is deployed, the SMF shall further report the PS Data Off status to PCF if the PS Data Off event trigger is provisioned, the additional behaviour of SMF and PCF for 3GPP PS Data Off is defined in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. 12c. This step is the same as step 16c in clause 4.3.2.2.1 with the following difference: - The H-SMF registers for the PDU Session with the UDM using Nudm_UECM_Registration (SUPI, DNN, S-NSSAI with the value defined by the HPLMN, PDU Session ID). 13. H-SMF to V-SMF: Nsmf_PDUSession_Create Response (QoS Rule(s), QoS Flow level QoS parameters if needed for the QoS Flow(s) associated with the QoS rule(s), PCO including session level information that the V-SMF is not expected to understand, selected PDU Session Type and SSC mode, Reliable Data Service Support, H-CN Tunnel Info, QFI(s), QoS profile(s), Session-AMBR, Reflective QoS Timer (if available), information needed by V-SMF in the case of EPS interworking such as the PDN Connection Type, User Plane Policy Enforcement, [ECS Address Configuration Information for the serving PLMN]). If the PDU Session being established was requested to be an always-on PDU Session, the H-SMF shall indicate to the V-SMF whether the request is accepted or not via the Always-on PDU Session Granted indication in the response message to V-SMF. If the PDU Session being established was not requested to be an always-on PDU Session but the H-SMF determines that the PDU Session needs to be established as an always-on PDU Session, the H-SMF shall indicate it to the V-SMF by including Always-on PDU Session Granted indication that the PDU Session is an always-on PDU Session. The information that the H-SMF may provide is the same than defined for step 11 of Figure 4.3.2.2.1-1. The H-CN Tunnel Info contains the tunnel information for uplink traffic towards H-UPF. Multiple QoS Rules and QoS Flow level QoS parameters for the QoS Flow(s) associated with the QoS rule(s) may be included in the Nsmf_PDUSession_Create Response. The V-SMF may apply VPLMN policies related with the SLA negotiated with the HPLMN or with QoS values supported by the VPLMN to evaluate the QoS parameters received from H-SMF; such policies may result in that V-SMF does not accept the PDU Session or does not accept some of the QoS Flows requested by the H-SMF. If the V-SMF does not accept the PDU Session, the V-SMF triggers the V-SMF initiated PDU Session Release procedure from step 1b-3b as defined in clause 4.3.4.3. When the V-SMF accepts at least one QoS flow, it transfers (via the AMF) the corresponding N2 (and NAS) request towards the 5G AN (and the UE) but does not issue requests for the QoS Flow(s) it has rejected due these policies. The V-SMF notifies the H-SMF about the rejected QoS Flows in step 23 below. NOTE 2: QoS enforcement in V-UPF is not expected on the QoS parameters received from H-SMF. If Control Plane CIoT 5GS Optimisation is enabled for the PDU Session, certain information, e.g. H-CN tunnel info, is not provided in the response to V-SMF. V-SMF stores the indication of Small Data Rate Control applicability on this PDU Session, if it is received in Nsmf_PDUSession_Create Response. 13a-13b. The V-SMF initiates an N4 Session Modification procedure with the V-UPF. The V-SMF may provide N4 rules to the V-UPF for this PDU Session, including rules to forward UL traffic to the H-UPF. 14-18. These steps are the same as steps 11-15 in clause 4.3.2.2.1 with the following differences: - These steps are executed in Visited PLMN; - The V-SMF stores an association of the PDU Session and H-SMF ID for this PDU Session for this UE; - If the H-SMF indicates the PDU Session can be established as an always-on PDU Session, the V-SMF shall further check whether the PDU Session can be established as an always-on PDU Session based on local policies. The V-SMF notifies the UE whether the PDU Session is an always-on PDU Session or not via the Always-on PDU Session Granted indication in the PDU Session Establishment Accept message. - If the N2 SM information indicates failure of user plane resource setup and the V-SMF rejected the PDU session establishment as described in step 15 in clause 4.3.2.2.1, step 19 is skipped and instead the V-SMF releases the N4 Session with V-UPF. - If an alternative H-SMF is selected for the PDU Session and the corresponding selected alternative H-SMF ID has not been previously provided to the AMF, the V-SMF provides the selected alternative H-SMF ID to the AMF. NOTE 3: The selected alternative H-SMF ID can be provided to AMF earlier, e.g. in step 8 if PDU Session Authentication/Authorization is performed. - If Control Plane CIoT 5GS Optimisation is enabled for the PDU Session, steps 19, 20 and 23 below are omitted. 19a. The V-SMF initiates an N4 Session Modification procedure with the V-UPF. The V-SMF may provide N4 rules to the V-UPF for this PDU Session, including rules to forward DL traffic to the AN. 19b. The V-UPF provides a N4 Session Modification Response to the V-SMF. After this step, the V-UPF delivers any down-link packets to the UE that may have been buffered for this PDU Session. 20. This step is the same as step 17 in clause 4.3.2.2.1 with the following differences: - The SMF is a V-SMF. The H-SMF and V-SMF subscribe to UE reachability event from AMF. 21. This step is same as step 18 in clause 4.3.2.2.1. In addition, if during the procedure, after step 14, the PDU Session establishment is not successful as specified in step 15 of clause 4.3.2.2.1, the V-SMF triggers the V-SMF initiated PDU Session Release procedure from step 1b-3b as defined in clause 4.3.4.3. 22. H-SMF to UE, via H-UPF and V-UPF in VPLMN: In the case of PDU Session Type IPv6 or IPv4v6, the H-SMF generates an IPv6 Router Advertisement and sends it to the UE via N4 and the H-UPF and V-UPF. If the Control Plane CIoT 5GS Optimisation is enabled for this PDU session the V-UPF forwards the IPv6 Router Advertisement to the V-SMF for transmission to the UE using the Mobile Terminated Data Transport in Control Plane CIoT 5GS Optimisation procedures (see clause 4.24.2). 23. If the V-SMF received in step18 an indication that the (R)AN has rejected some QFI(s) or if the V-SMF has rejected some QFI(s) in step 13, the V-SMF notifies the H-SMF via a Nsmf_PDUSession_Update Request. The H-SMF is responsible of updating accordingly the QoS rules and QoS Flow level QoS parameters if needed for the QoS Flow(s) associated with the QoS rule(s) in the UE. 24. This step is the same as step 20 in clause 4.3.2.2.1 with the following differences: - this step is executed in the Home PLMN; - the SMF also deregisters for the given PDU Session using Nudm_UECM_Deregistration (SUPI, DNN, PDU Session ID). The UDM may update corresponding UE context by Nudr_DM_Update (SUPI, Subscription Data, UE context in SMF data). NOTE 4: The SMF in HPLMN can initiate H-SMF initiated PDU Session Release procedure as defined in clause 4.3.4.3, already after step 13.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.3.2.2.2

6.3.2.2 Network-requested PDU session modification procedure initiation

In order to initiate the network-requested PDU session modification procedure, the SMF shall create a PDU SESSION MODIFICATION COMMAND message. If the authorized QoS rules of the PDU session is modified or is marked as to be synchronised with the UE, the SMF shall set the Authorized QoS rules IE of the PDU SESSION MODIFICATION COMMAND message to the authorized QoS rules of the PDU session. The SMF shall ensure that the number of the packet filters used in the authorized QoS rules of the PDU Session does not exceed the maximum number of packet filters supported by the UE for the PDU session. The SMF may bind service data flows for which the UE has requested traffic segregation to a dedicated QoS flow for the PDU session, if possible. Otherwise the SMF may bind the service data flows to an existing QoS flow. The SMF shall use only one dedicated QoS flow for traffic segregation. If the UE has requested traffic segregation for multiple service data flows with different QoS handling, the SMF shall bind all these service data flows to a single QoS flow. If the SMF allows traffic segregation for service data flows in a QoS rule, then the SMF shall create a new authorized QoS rule for these service data flows and shall delete packet filters corresponding to these service data flows from the other authorized QoS rules. If the authorized QoS flow descriptions of the PDU session is modified or is marked as to be synchronised with the UE, the SMF shall set the Authorized QoS flow descriptions IE of the PDU SESSION MODIFICATION COMMAND message to the authorized QoS flow descriptions of the PDU session. If SMF creates a new authorized QoS rule for a new QoS flow, then SMF shall include the authorized QoS flow description for that QoS flow in the Authorized QoS flow descriptions IE of the PDU SESSION MODIFICATION COMMAND message, if: a) the newly created authorized QoS rules is for a new GBR QoS flow; b) the QFI of the new QoS flow is not the same as the 5QI of the QoS flow identified by the QFI; c) the new QoS flow can be mapped to an EPS bearer as specified in subclause 4.11.1 of 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9]; or d) the new QoS flow is established for the PDU session used for relaying, as specified in subclause 5.6.2.1 of 3GPP TS 23.304[ Proximity based Services (ProSe) in the 5G System (5GS) ] [6E]. NOTE 0: In cases other than above listed cases, it is up to the SMF implementation to include the authorized QoS flow description of the new QoS flow for the new authorized QoS rule in the Authorized QoS flow descriptions IE of the PDU SESSION MODIFICATION COMMAND message. If the session-AMBR of the PDU session is modified, the SMF shall set the selected Session-AMBR IE of the PDU SESSION MODIFICATION COMMAND message to the session-AMBR of the PDU session. If interworking with EPS is supported for the PDU session and if the mapped EPS bearer contexts of the PDU session is modified, the SMF shall set the Mapped EPS bearer contexts IE of the PDU SESSION MODIFICATION COMMAND message to the mapped EPS bearer contexts of the PDU session. If the association between a QoS flow and the mapped EPS bearer context is changed, the SMF shall set the EPS bearer identity parameter in Authorized QoS flow descriptions IE of the PDU SESSION MODIFICATION COMMAND message to the new EPS bearer identity associated with the QoS flow. NOTE 0A: The SMF can include multiple mapped EPS bearer context fields with the same EPS bearer identity in the Mapped EPS bearer contexts IE of the PDU SESSION MODIFICATION COMMAND message in cases, e.g. the packet filters need to be modified and the modification requires more than one TFT operation codes or the mapped traffic flow template needs to be modified and the modification exceeds the maximum size of the TFT IE. If the network-requested PDU session modification procedure is triggered by a UE-requested PDU session modification procedure and the PDU SESSION MODIFICATION REQUEST message includes a 5GSM capability IE, the SMF shall: a) if the RQoS bit is set to: 1) "Reflective QoS supported", consider that the UE supports reflective QoS for this PDU session; or 2) "Reflective QoS not supported", consider that the UE does not support reflective QoS for this PDU session; and; b) if the MH6-PDU bit is set to: 1) "Multi-homed IPv6 PDU session supported", consider that this PDU session is supported to use multiple IPv6 prefixes; or 2) "Multi-homed IPv6 PDU session not supported", consider that this PDU session is not supported to use multiple IPv6 prefixes. If the SMF considers that reflective QoS is supported for QoS flows belonging to this PDU session, the SMF may include the RQ timer IE set to an RQ timer value in the PDU SESSION MODIFICATION COMMAND message. If a port management information container needs to be delivered (see 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8] and 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9]) and the UE has set the TPMIC bit to "Transport of port management information container supported" in the 5GSM capability IE, the SMF shall include a Port management information container IE in the PDU SESSION MODIFICATION COMMAND message. For a PDN connection established when in S1 mode, upon aninter-system change from S1 mode to N1 mode, if the network-requested PDU session modification procedure is triggered by a UE-requested PDU session modification procedure and a UE-requested PDU session modification procedure has not been successfully performed yet, the PDU session type is "IPv4", "IPv6", "IPv4v6" or "Ethernet" and the PDU SESSION MODIFICATION REQUEST message includes a Maximum number of supported packet filters IE, the SMF shall consider this number as the maximum number of packet filters that can be supported by the UE for this PDU session. Otherwise the SMF considers that the UE supports 16 packet filters for this PDU session. For a PDN connection established when in S1 mode, upon an inter-system change from S1 mode to N1 mode, if the network-requested PDU session modification procedure is triggered by a UE-requested PDU session modification procedure and a UE-requested PDU session modification procedure has not been successfully performed yet, the SMF shall consider that the maximum data rate per UE for user-plane integrity protection supported by the UE for uplink and the maximum data rate per UE for user-plane integrity protection supported by the UE for downlink are valid for the lifetime of the PDU session. For a PDN connection established when in S1 mode, upon aninter-system change from S1 mode to N1 mode, if the network-requested PDU session modification procedure is triggered by a UE-requested PDU session modification procedure and a UE-requested PDU session modification procedure has not been successfully performed yet, and the SMF determines, based on local policies or configurations in the SMF and the Always-on PDU session requested IE in the PDU SESSION MODIFICATION REQUEST message (if available), that either: a) the requested PDU session needs to be an always-on PDU session, the SMF shall include the Always-on PDU session indication IE in the PDU SESSION MODIFICATION COMMAND message and shall set the value to "Always-on PDU session required"; or b) the requested PDU session shall not be an always-on PDU session and: 1) if the UE included the Always-on PDU session requested IE, the SMF shall include the Always-on PDU session indication IE in the PDU SESSION MODIFICATION COMMAND message and shall set the value to "Always-on PDU session not allowed"; or 2) if the UE did not include the Always-on PDU session requested IE, the SMF shall not include the Always-on PDU session indication IE in the PDU SESSION MODIFICATION COMMAND message. For a PDN connection established when in S1 mode, upon aninter-system change from S1 mode to N1 mode, if the network-requested PDU session modification procedure is triggered by a UE-requested PDU session modification procedure, a UE-requested PDU session modification procedure has not been successfully performed yet, the UE supports EDC and the network allows the use of EDC, then the SMF shall include the Extended protocol configuration options IE in the PDU SESSION MODIFICATION COMMAND message with the EDC usage allowed indicator. For a PDN connection established when in S1 mode, upon an inter-system change from S1 mode to N1 mode, if the network-requested PDU session modification procedure is triggered by a UE-requested PDU session modification procedure, a UE-requested PDU session modification procedure has not been successfully performed yet, the UE supports EDC and the network requires the use of EDC, then the SMF shall include the Extended protocol configuration options IE in the PDU SESSION MODIFICATION COMMAND message with the EDC usage required indicator. If a QoS flow for URLLC is created in a PDU session and the SMF has not provided the Always-on PDU session indication IE with the value set to "Always-on PDU session required" in the UE-requested PDU session establishment procedure or a network-requested PDU session modification procedure for the PDU session, the SMF shall include the Always-on PDU session indication IE in the PDU SESSION MODIFICATION COMMAND message and shall set the value to "Always-on PDU session required". If the value of the RQ timer is set to "deactivated" or has a value of zero, the UE considers that RQoS is not applied for this PDU session and remove the derived QoS rule(s) associated with the PDU session, if any. If the network-requested PDU session modification procedure is triggered by a UE-requested PDU session modification procedure, the SMF shall set the PTI IE of the PDU SESSION MODIFICATION COMMAND message to the PTI of the PDU SESSION MODIFICATION REQUEST message received as part of the UE-requested PDU session modification procedure. If the network-requested PDU session modification procedure is triggered by a UE-requested PDU session modification procedure and the UE has included the Requested MBS container IE in the PDU SESSION MODIFICATION REQUEST message with the MBS operation set to "Join multicast MBS session", the SMF: a) shall include the TMGI for the multicast MBS session IDs that the UE is allowed to join, if any, in the Received MBS container IE, shall set the MBS decision to "MBS join is accepted" for each of those Received MBS information, may include the MBS start time to indicate the time when the multicast MBS session starts, and shall include the MBS security container in each of those Received MBS information if security protection is applied for that multicast MBS session and the control plane security procedure is used as specified in annex W.4.1.2 in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24], and shall use separate QoS flows dedicated for multicast by including the Authorized QoS flow descriptions IE if no separate QoS flows dedicated for multicast exist or if the SMF wants to establish new QoS flows dedicated for multicast; NOTE 1: The network determines whether security protection applies or not for the multicast MBS session as specified in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. b) shall include the TMGI for multicast MBS session IDs that the UE is rejected to join, if any, in the Received MBS container IE, shall set the MBS decision to "MBS join is rejected" for each of those Received MBS information, shall set the Rejection cause for each of those Received MBS information with the reason of rejection and, if the Rejection cause is set to "multicast MBS session has not started or will not start soon", may include an MBS back-off timer value; and c) may include in the Received MBS container IE the MBS service area for each multicast MBS session and include in it the MBS TAI list, the NR CGI list or both, that identify the service area(s) for the local MBS service; NOTE 2: For an multicast MBS session that has multiple MBS service areas, the MBS service areas are indicated to the UE using MBS service announcement as described in 3GPP TS 23.247[ Architectural enhancements for 5G multicast-broadcast services ] [53], which is out of scope of this specification. in the PDU SESSION MODIFICATION COMMAND message. If the UE has set the Type of multicast MBS session ID to "Source specific IP multicast address" in the Requested MBS container IE for certain multicast MBS session(s) in the PDU SESSION MODIFICATION REQUEST message, the SMF shall include the Source IP address information and Destination IP address information in the Received MBS information together with the TMGI for each of those multicast MBS sessions. NOTE 3: Including the Source IP address information and Destination IP address information in the Received MBS information in that case is to allow the UE to perform the mapping between the requested multicast MBS session ID and the provided TMGI. NOTE 4: In SNPN, TMGI is used together with NID to identify an MBS Session. If: a) the SMF wants to remove joined UE from one or more multicast MBS sessions; or b) the network-requested PDU session modification procedure is triggered by a UE-requested PDU session modification procedure and the UE has included the Requested MBS container IE in the PDU SESSION MODIFICATION REQUEST message with the MBS operation set to "Leave multicast MBS session", the SMF shall include the multicast MBS session IDs that the UE is removed from, if any, in the Received MBS container IE in the PDU SESSION MODIFICATION COMMAND message and shall set the MBS decision to "Remove UE from multicast MBS session" for each of those Received MBS information. The SMF may include the updated MBS service area in each of the Received MBS information, if any. The SMF may delete the QoS flows associated for the multicast by including the Authorized QoS flow descriptions IE in the PDU SESSION MODIFICATION COMMAND message. If the UE is removed from multicast MBS session due to the MBS session release, the SMF shall set the Rejection cause to "multicast MBS session is released". The SMF shall include the Rejection cause for each of the Received MBS information, if any, and set its value with the reason of removing the UE from the corresponding multicast MBS session. NOTE 5: based on operator's policy, e.g. after a locally configured time period, the SMF is allowed to trigger the removal of joined UE from an multicast MBS session when the UE moves outside all the MBS service area(s) of that multicast MBS session. If the SMF wants to update the MBS security information of an multicast MBS session that the UE has joined, the SMF shall include the corresponding multicast MBS session ID and the MBS security container in the Received MBS container IE in the PDU SESSION MODIFICATION COMMAND message, and shall set the MBS Decision to "MBS security information update" in the Received MBS information. If the SMF wants to update the MBS service area of an multicast MBS session that the UE has joined, the SMF shall include the corresponding multicast MBS session ID and the updated MBS service area in the Received MBS container IE in the PDU SESSION MODIFICATION COMMAND message, and shall set the MBS decision to "MBS service area update" in the Received MBS information. NOTE 6: The MBS service area of an multicast MBS session is also allowed to be updated to the UE using the MBS service announcement as described in 3GPP TS 23.247[ Architectural enhancements for 5G multicast-broadcast services ] [53], which is out of scope of this specification. If the network needs to update ATSSS parameters (see subclause 5.2.4 of 3GPP TS 24.193[ 5G System;Access Traffic Steering, Switching and Splitting (ATSSS); Stage 3 ] [13B]), the SMF shall include the ATSSS container IE with the updates of ATSSS parameters in the PDU SESSION MODIFICATION COMMAND message. If the network-requested PDU session modification procedure is not triggered by a UE-requested PDU session modification procedure, the SMF shall set the PTI IE of the PDU SESSION MODIFICATION COMMAND message to "No procedure transaction identity assigned". If the selected SSC mode of the PDU session is "SSC mode 3" and the SMF requests the relocation of SSC mode 3 PDU session anchor with multiple PDU sessions as specified in 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9], the SMF shall include 5GSM cause #39 "reactivation requested", in the PDU SESSION MODIFICATION COMMAND message, and may include the PDU session address lifetime in a PDU session address lifetime parameter in the Extended protocol configuration options IE of the PDU SESSION MODIFICATION COMMAND message. If the selected SSC mode of the PDU session is "SSC mode 3", the S-NSSAI or the mapped S-NSSAI associated with the PDU session needs to be replaced and the SMF determines that the PDU session needs to be re-established on the alternative S-NSSAI, the SMF shall include the Alternative S-NSSAI IE and 5GSM cause #39 "reactivation requested" in the PDU SESSION MODIFICATION COMMAND message. NOTE 7: The relocation of SSC mode 3 PDU session anchor with multiple PDU sessions can also be initiated by the SMF in case of the SMF is requested by the AMF to release the PDU session due to the network slice instance of the PDU session is changed as specified in subclause 5.15.5.3 of 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]. The SMF shall send the PDU SESSION MODIFICATION COMMAND message, and the SMF shall start timer T3591 (see example in figure 6.3.2.2.1). NOTE 8: If the SMF requests the relocation of SSC mode 3 PDU session anchor with multiple PDU sessions as specified in 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9], the reallocation requested indication indicating whether the SMF is to be reallocated or the SMF is to be reused is provided to the AMF. If the control plane CIoT 5GS optimization is enabled for a PDU session and the IP header compression configuration IE was included in the PDU SESSION ESTABLISHMENT REQUEST message or the PDU SESSION MODIFICATION REQUEST message, and the SMF supports control plane CIoT 5GS optimization and IP header compression for control plane CIoT 5GS optimization, the SMF may include the IP header compression configuration IE in the PDU SESSION MODIFICATION COMMAND message to re-negotiate IP header compression configuration associated to the PDU session. If the control plane CIoT 5GS optimization is enabled for a PDU session and the Ethernet header compression configuration IE was included in the PDU SESSION ESTABLISHMENT REQUEST message or the PDU SESSION MODIFICATION REQUEST message, and the SMF supports control plane CIoT 5GS optimization and Ethernet header compression for control plane CIoT 5GS optimization, the SMF may include the Ethernet header compression configuration IE in the PDU SESSION MODIFICATION COMMAND message to re-configure Ethernet header compression configuration associated with the PDU session. If the network-requested PDU session modification procedure is associated with C2 authorization procedure, the SMF shall send the PDU SESSION MODIFICATION COMMAND message by including the Service-level-AA container IE containing: a) the service-level-AA response with the value of C2AR field set to the "C2 authorization was successful"; b) if a payload is provided from the UAS-NF, the service-level-AA payload with the value set to the payload; and c) if a payload type associated with the payload is provided from the UAS-NF, the service-level-AA payload type with the value set to the payload type; and d) if the CAA-level UAV ID is provided from the UAS-NF, the service-level device ID set to the CAA-level UAV ID. NOTE 9: The C2 authorization payload in the service-level-AA payload can include one, some or all of the pairing information for C2 communication, and the pairing information for direct C2 communication, NOTE 9A: The C2 authorization payload in the service-level-AA payload can include the security information for C2 session as specified in TS 33.256[ Security aspects of Uncrewed Aerial Systems (UAS) ] [24B]. If the service-level-AA procedure is triggered for the established PDU session for UAS services with re-authentication purpose, and the SMF is provided by the UAS-NF with the successful UUAA-SM result, the SMF shall transmit a PDU SESSION MODIFICATION COMMAND message to the UE, where the PDU SESSION MODIFICATION COMMAND message shall include the Service-level-AA container IE containing: a) the service-level-AA response with the value of SLAR field set to "Service level authentication and authorization was successful"; b) if received the CAA-level UAV ID from the UAS-NF, the service-level device ID with the value set to the CAA-level UAV ID; c) if received a payload from the UAS-NF, the service-level-AA payload with the value set to the payload; and d) if received a payload type associated with the payload, the service-level-AA payload type with the value set to the payload type. If the SMF needs to provide new ECS configuration information to the UE and the UE has indicated support for ECS configuration information provisioning in the PDU SESSION ESTABLISHMENT REQUEST message or while in S1 mode, then the SMF may include the Extended protocol configuration options IE in the PDU SESSION MODIFICATION COMMAND message with: - at least one of ECS IPv4 Address(es), ECS IPv6 Address(es), ECS FQDN(s); - at least one associated ECSP identifier;and - optionally, spatial validity conditions associated with the ECS address; NOTE 10: The IP address(es), FQDN(s), or both are associated with the ECSP identifier and replace previously provided ECS configuration information associated with the same ECSP identifier, if any. If the SMF needs to provide DNS server address(es) to the UE and the UE has provided the DNS server IPv4 address request, the DNS server IPv6 address request or both of them, in the PDU SESSION ESTABLISHMENT REQUEST message or a PDU SESSION MODIFICATION REQUEST message, then the SMF shall include the Extended protocol configuration options IE in the PDU SESSION MODIFICATION COMMAND message with one or more DNS server IPv4 address(es), one or more DNS server IPv6 address(es) or both of them. If the SMF needs to trigger EAS rediscovery and the UE has indicated support of the EAS rediscovery in the PDU SESSION ESTABLISHMENT REQUEST message or the PDU SESSION MODIFICATION REQUEST message, then the SMF shall include the Extended protocol configuration options IE in the PDU SESSION MODIFICATION COMMAND message: a) with the EAS rediscovery indication without indicated impact; or b) with the following: 1) one or more EAS rediscovery indication(s) with impacted EAS IPv4 address range, if the UE supports EAS rediscovery indication(s) with impacted EAS IPv4 address range; 2) one or more EAS rediscovery indication(s) with impacted EAS IPv6 address range, if the UE supports EAS rediscovery indication(s) with impacted EAS IPv6 address range; 3) one or more EAS rediscovery indication(s) with impacted EAS FQDN, if the UE supports EAS rediscovery indication(s) with impacted EAS FQDN; or 4) any combination of the above. When UE has requested P-CSCF IPv6 address or P-CSCF IPv4 address and the SMF has provided P-CSCF address(es) during the PDU session establishment procedure, if the network-requested PDU session modification procedure is triggered for P-CSCF restoration, the SMF shall include the P-CSCF IP address(es) in the Extended protocol configuration options IE in the PDU SESSION MODIFICATION COMMAND message as specified in subclause 5.8.2.2 of 3GPP TS 23.380[ IMS Restoration Procedures ] [54]. If the S-NSSAI or the mapped S-NSSAI of the PDU session needs to be replaced and the SMF determines that the PDU session needs to be retained, the SMF shall include the Alternative S-NSSAI IE in the PDU SESSION MODIFICATION COMMAND message. If the SMF includes the authorized QoS flow descriptions and the SMF determines to provide the N3QAI to the UE, the SMF shall include the N3QAI in the PDU SESSION MODIFICATION COMMAND message. Figure 6.3.2.2.1: Network-requested PDU session modification procedure

3GPP TS 24.501

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

CT WG1

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

6.3.2.2

4.3.21.1 CN Assistance Information

Core Network assisted eNodeB parameters tuning aids the eNodeB to minimize the UE state transitions and achieve optimum network behaviour. How the eNodeB uses the Core Network assistance information is not in scope of this specification and is implementation specific. Core Network assistance information may be derived by the MME per UE in the MME based on collection of UE behaviour statistics or other available information about the expected UE behaviour (such as subscribed APN, IMSI ranges or other subscription information). If the HSS provides the Communication Pattern (CP) parameters (see TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [74]) within the subscription profile information, then the MME may use the CP parameters for selecting the CN assisted eNodeB parameters. The CP parameters received from the HSS are used by the MME as input to derive the CN assisted eNodeB parameter values. For the case of statistics-based Core Network assistance information collection, this may be enabled based on local configuration (e.g. subscribed APN, IMSI ranges or other subscription information). This information provides the eNodeB with a way to understand the UE behaviour for these aspects: - "Expected UE activity behaviour", i.e. the expected pattern of the UE's changes between ECM-CONNECTED and ECM-IDLE states. This may be derived e.g. from statistical information or from subscription information. - "Expected HO interval", i.e. the expected time interval between inter-eNodeB handovers. This may be derived e.g. from statistical information or from subscription information. The "Expected HO interval" parameter is not based on subscription information. Highly mobile UEs may have the ECM-CONNECTED state reduced to reduce handover signalling, unless the activity data do not justify that, as reduced handover signalling would be outweighed by more Service Request signalling). - "UE Differentiation Information" including the Communication Pattern parameters (see TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [74]) to support Uu operation optimisation for NB-IoT UE differentiation. The respective signalling to support this feature is specified in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36]. The cases where the Traffic Profile (see see TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [74]) is not used are described in clauses 5.3.4B.2 and 5.3.4B.3. The MME decides when to send this information to the eNodeB as "Expected UE behaviour" carried in S1-AP signalling over the S1-MME interface as per procedure documented in clause 4.3.21.3. NOTE 1: The calculation of the Core Network assistance information, i.e. the algorithms used and related criteria, and the decision when it is considered suitable and stable to send to the eNodeB are vendor specific. Unreliable information should not be provided to the eNodeB as it may drive undesirable system effects. NOTE 2: It is recommended the MME or, depending on where this assessment is performed, the eNodeB, can consider the average times in the ECM-CONNECTED and ECM-IDLE states an accurate representation of the traffic patterns if the average time in ECM-CONNECTED mode is short enough to assume the UE is generally actively transmitting and/or receiving data while in ECM-CONNECTED state. NOTE 3: When there are multiple overlapping CP parameter sets received from the HSS for one UE, then the MME considers a merge per CP parameter when deriving the CN assisted eNodeB parameters, e.g. based on the Scheduled communication time and/or Communication duration time parameters. A conflict on the Stationary Indication parameter can be resolved by considering the UE as "mobile".

3GPP TS 23.401

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

SA WG2

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

4.3.21.1

6.6.2.3.3A Minimum requirements for CA E-UTRA

For intra-band contiguous carrier aggregation the carrier aggregation E-UTRA Adjacent Channel Leakage power Ratio (CA E-UTRAACLR) is the ratio of the filtered mean power centred on the aggregated channel bandwidth to the filtered mean power centred on an adjacent aggregated channel bandwidth at nominal channel spacing. The assigned aggregated channel bandwidth power and adjacent aggregated channel bandwidth power are measured with rectangular filters with measurement bandwidths specified in Table 6.6.2.3.3A-1. If the measured adjacent channel power is greater than –50dBm then the E-UTRAACLR shall be higher than the value specified in Table 6.6.2.3.3A-1 and Table 6.6.2.3.3A-1a. Table 6.6.2.3.3A-1: General requirements for CA E-UTRAACLR Table 6.6.2.3.3A-1a: Additional requirements for CA E-UTRAACLR for UL CA_41C Power Class 2 For inter-band carrier aggregation with one component carrier per operating band and the uplink active in two E-UTRA bands, E-UTRA Adjacent Channel Leakage power Ratio (E-UTRAACLR) is the ratio of the filtered mean power centred on the assigned channel bandwidth on a component carrier to the filtered mean power centred on an adjacent channel frequency. The E-UTRA Adjacent Channel Leakage power Ratio is defined per carrier and the requirement is specified in subclause 6.6.2.3.1. For intra-band non-contiguous carrier aggregation when all sub-blocks consist of one component carrier the E-UTRA Adjacent Channel Leakage power Ratio (E-UTRAACLR) is the ratio of the sum of the filtered mean powers centred on the assigned sub-block frequencies to the filtered mean power centred on an adjacent channel frequency at nominal channel spacing. In case the sub-block gap bandwidth Wgap is smaller than of the sub-block bandwidth then for that sub-block no E-UTRAACLR requirement is set for the gap. In case the sub-block gab bandwidth Wgap is smaller than either of the sub-block bandwidths then no E- UTRAACLR requirement is set for the gap.The assigned E-UTRA sub-block power and adjacent E-UTRA channel power are measured with rectangular filters with measurement bandwidths specified in Table 6.6.2.3.3A-2. If the measured adjacent channel power is greater than –50dBm then the E-UTRAACLR shall be higher than the value specified in Table 6.6.2.3.3A-2. Table 6.6.2.3.3A-2: General requirements for non-contiguous intraband CA E-UTRAACLR For combinations of intra-band and inter-band carrier aggregation with three uplink component carriers (up to two contiguously aggregated carriers per band), the E-UTRA Adjacent Channel Leakage power Ratio (E-UTRAACLR) is defined as follows. For the E-UTRA band supporting one component carrier, the E-UTRA Adjacent Channel Leakage power Ratio (UTRAACLR) is the ratio of the filtered mean power centred on the assigned channel bandwidth of the component carrier to the filtered mean power centred on an adjacent channel frequency and the requirements in subclause 6.6.2.3.1 apply. For the E-UTRA band supporting two contiguous component carriers the E-UTRA Adjacent Channel Leakage power Ratio (E-UTRAACLR) is the ratio of the filtered mean power centred on the aggregated channel bandwidth to the filtered mean power centred on an adjacent(s) aggregated channel bandwidth at nominal channel spacing and the requirements of CA E-UTRAACLR specified in subclause 6.6.2.3.3A 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.2.3.3A

5.2.1.3 Receipt of a CALL PROCEEDING message

Having entered the "call initiated" state, when the call control entity of the mobile station receives a CALL PROCEEDING message, it shall stop timer T303; start timer T310 unless - the CALL PROCEEDING message contains a progress indicator IE specifying progress description #1, #2, or #64; or - it has received a PROGRESS message containing a progress indicator IE specifying progress description #1, #2, or #64 prior to the CALL PROCEEDING message and enter the "mobile originating call proceeding" state. Abnormal case: If timer T310 elapses before any of the ALERTING, CONNECT or DISCONNECT messages has been received, the mobile station shall perform the clearing procedure described in subclause 5.4. Figure 5.3/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Call proceeding sequence at mobile originating call establishment

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

5.2.1.3

4.14.2.7 Number of attempted reconfigurations of LTE DRB to LWIP DRB

a) This measurement provides the number of attempted reconfigurations of LTE DRB to LWIP DRB. b) CC c) On transmission of RRCConnectionReconfiguration message which includes the drb-ToAddModList in the radioResourceConfigDedicated information element, and the drb-ToAddModList contains at least one drb-Identity that it an LTE DRB of the current UE configuration and the drb-TypeLWIP of this DRB is included and not set to "eutran" (see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]). d) An integer value e) LWI.LteToLwipDrbReconfAtt f) WLANMobilitySet g) Valid for packet switched traffic h) EPS

3GPP TS 32.425

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

SA WG5

3GPP Series : 32 , OAM&P and Charging

4.14.2.7

10.5.4.11a CLIR suppression

The CLIR suppression information element may be sent by the mobile station to the network in the SETUP message. The use is defined in 3GPP TS 24.081[ Line Identification supplementary services; Stage 3 ] [25]. The CLIR suppression information element is coded as shown in figure 10.5.96/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The CLIR suppression is a type 2 information element. Figure 10.5.96/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] CLIR suppression 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.11a

– FeatureSetUplinkPerCC

The IE FeatureSetUplinkPerCC indicates a set of features that the UE supports on the corresponding carrier of one band entry of a band combination. FeatureSetUplinkPerCC information element -- ASN1START -- TAG-FEATURESETUPLINKPERCC-START FeatureSetUplinkPerCC ::= SEQUENCE { supportedSubcarrierSpacingUL SubcarrierSpacing, supportedBandwidthUL SupportedBandwidth, channelBW-90mhz ENUMERATED {supported} OPTIONAL, mimo-CB-PUSCH SEQUENCE { maxNumberMIMO-LayersCB-PUSCH MIMO-LayersUL OPTIONAL, maxNumberSRS-ResourcePerSet INTEGER (1..2) } OPTIONAL, maxNumberMIMO-LayersNonCB-PUSCH MIMO-LayersUL OPTIONAL, supportedModulationOrderUL ModulationOrder OPTIONAL } FeatureSetUplinkPerCC-v1540 ::= SEQUENCE { mimo-NonCB-PUSCH SEQUENCE { maxNumberSRS-ResourcePerSet INTEGER (1..4), maxNumberSimultaneousSRS-ResourceTx INTEGER (1..4) } OPTIONAL } FeatureSetUplinkPerCC-v1700 ::= SEQUENCE { supportedMinBandwidthUL-r17 SupportedBandwidth-v1700 OPTIONAL, -- R1 23-3-1-3 FeMIMO: Multi-TRP PUSCH repetition (type B) - non-codebook based mTRP-PUSCH-RepetitionTypeB-r17 ENUMERATED {n1,n2,n3,n4} OPTIONAL, -- R1 23-3-1-1 -codebook based Multi-TRP PUSCH repetition (type B) mTRP-PUSCH-TypeB-CB-r17 ENUMERATED {n1,n2,n4} OPTIONAL, supportedBandwidthUL-v1710 SupportedBandwidth-v1700 OPTIONAL } FeatureSetUplinkPerCC-v1800 ::= SEQUENCE { -- R1 40-6-1: Single-DCI based STx2P SDM scheme for PUSCH—codebook pusch-CB-SingleDCI-STx2P-SDM-r18 SEQUENCE { maxNumberSRS-ResourcePerSet-r18 ENUMERATED {n1,n2,n4}, maxNumberLayerPerPanel-r18 INTEGER (1..2), maxNumberNZP-PUSCH-PortsPerSet-r18 ENUMERATED {n1,n2,n4}, maxNumberSRS-AntennaPortsPerSet-r18 ENUMERATED {n1,n2,n4} } OPTIONAL, -- R1 40-6-1a: Single-DCI based STx2P SDM scheme for PUSCH—noncodebook pusch-NonCB-SingleDCI-STx2P-SDM-r18 SEQUENCE { maxNumberSRS-ResourcePerSet-r18 INTEGER (1..4), maxNumberLayerPerPanel-r18 INTEGER (1..2), maxNumberSimulSRS-ResourcePerSet-r18 INTEGER (1..4) } OPTIONAL, -- R1 40-6-2: Single-DCI based STx2P SFN scheme for PUSCH—codebook pusch-CB-SingleDCI-STx2P-SFN-r18 SEQUENCE { maxNumberSRS-ResourcePerSet-r18 ENUMERATED {n1,n2,n4}, maxNumberLayerPerSet-r18 INTEGER (1..2), maxNumberSRS-AntennaPortsPerSet-r18 ENUMERATED {n1,n2,n4}, maxNumberNZP-PUSCH-PortsPerSet-r18 ENUMERATED {n1,n2,n4} } OPTIONAL, -- R1 40-6-2a: Single-DCI based STx2P SFN scheme for PUSCH—noncodebook pusch-NonCB-SingleDCI-STx2P-SFN-r18 SEQUENCE { maxNumberSRS-ResourcePerSet-r18 INTEGER (1..4), maxNumberLayerPerSet-r18 INTEGER (1..2), maxNumberSimulSRS-ResourcePerSet-r18 INTEGER (1..4) } OPTIONAL, -- R1 40-6-3a: codebook multi-DCI based STx2P PUSCH+PUSCH for DG+DG twoPUSCH-CB-MultiDCI-STx2P-DG-DG-r18 SEQUENCE { maxNumberSRS-ResourcePerSet-r18 ENUMERATED {n1, n2, n4}, maxNumberLayerOverlapping-r18 INTEGER (1..2), maxNumberNZP-PUSCH-Overlapping-r18 ENUMERATED {n1, n2, n4}, maxNumberPUSCH-PerCORESET-PerSlot-r18 SEQUENCE { scs-60kHz-r18 ENUMERATED {n1,n2,n3,n4,n7} OPTIONAL, scs-120kHz-r18 ENUMERATED {n1,n2,n3,n4,n7} OPTIONAL } OPTIONAL, maxNumberTotalLayerOverlapping-r18 INTEGER (2..4), maxNumberSRS-AntennaPortsPerSet-r18 ENUMERATED {n1,n2,n4} } OPTIONAL, -- R1 40-6-3b: Noncodebook multi-DCI based STx2P PUSCH+PUSCH for DG+DG twoPUSCH-NonCB-MultiDCI-STx2P-DG-DG-r18 SEQUENCE { maxNumberSRS-ResourcePerSet-r18 INTEGER (1..4), maxNumberLayerOverlapping-r18 INTEGER (1..2), maxNumberSimulSRS-ResourcePerSet-r18 INTEGER (1..4), maxNumberPUSCH-PerCORESET-PerSlot-r18 SEQUENCE { scs-60kHz-r18 ENUMERATED {n1,n2,n3,n4,n7} OPTIONAL, scs-120kHz-r18 ENUMERATED {n1,n2,n3,n4,n7} OPTIONAL } OPTIONAL, maxNumberTotalLayerOverlapping-r18 INTEGER (2..4) } OPTIONAL, -- R1 40-6-6: Out-of-order operation for multi-DCI based STx2P PUSCH+PUSCH twoPUSCH-MultiDCI-STx2P-OutOfOrder-r18 ENUMERATED {supported} OPTIONAL, -- R1 40-7-1a: Codebook-based 8Tx PUSCH—codebook1 codebook1-8TxPUSCH-r18 ENUMERATED {n4-1,n2-2,both} OPTIONAL, -- R1 40-7-1b: Codebook-based 8Tx PUSCH—codebook2 codebook2-8TxPUSCH-r18 ENUMERATED {supported} OPTIONAL, -- R1 40-7-1c: Codebook-based 8Tx PUSCH—codebook3 codebook3-8TxPUSCH-r18 ENUMERATED {supported} OPTIONAL, -- R1 40-7-1d: Codebook-based 8Tx PUSCH—codebook4 codebook4-8TxPUSCH-r18 ENUMERATED {supported} OPTIONAL } -- TAG-FEATURESETUPLINKPERCC-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

4.13.2.1 Number of attempted WLAN additions to the LWA WLAN mobility set

a) This measurement provides the number of attempted WLAN additions to the LWA WLAN mobility set. b) CC c) On transmission of RRCConnectionReconfiguration message which includes the wlan-ToAddList in the lwa-MobilityConfig of lwa-Configuration information element (see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [18]) by the eNB. d) An integer value e) LWI.LwaWlanAddAtt f) WLANMobilitySet g) Valid for packet switched traffic h) EPS

3GPP TS 32.425

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

SA WG5

3GPP Series : 32 , OAM&P and Charging

4.13.2.1

5.37.7 5GS Packet Delay Variation monitoring and reporting 5.37.7.1 General

The 5GS Packet Delay Variation is the variation of packet delay measured between UE and PSA UPF. The AF may send the requirement for Packet Delay Variation monitoring to 5GS together with the requirement for packet delay measurement, as described in clause 6.1.3.21 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. Upon AF request for Packet Delay Variation monitoring together with packet delay monitoring, the PCF triggers the QoS monitoring procedure, and gets the UL, DL or RT QoS Monitoring result from the SMF. The PCF derives the 5GS Packet Delay Variation based on the QoS Monitoring result and then reports to the AF/NEF both packet delay measurements and Packet Delay Variation. NOTE: The derivation of 5GS Packet Delay Variation by PCF, based on QoS Monitoring, is implementation dependent. The Packet Delay Variation calculation method needs to be the same within the PLMN, based on operator policy. QoS Monitoring is used to obtain measurement of QoS parameters of individual QoS Flows. PCF determines the measurements required based on input from AF and enables the measurements by generating an authorized QoS Monitoring Policy for the PCC Rule as specified in clause 6.1.3.21 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45].

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.37.7

F.3 BMCA procedure

Figure F.3-1: BMCA procedure 1. PDU Session Establishment is performed as shown in F.1-1 step 1 and 2 for an Ethernet or IP type PDU Session to carry the UMIC or PMIC. 2. The TSN AF or TSCTSF may subscribe to notifications for the PTP port state changes from UPF/NW-TT. 3. The UPF/NW-TT receives the Announce message via User -plane from DS-TT connectivity established using PDU session, or via NW-TT port over N6. As Announce message is a periodic message, after step 3, the UPF/NW-TT will receive Announce messages regularly. 4. The NW-TT runs the BMCA algorithm in order to determine the PTP port state for the DS-TT port(s) and NW-TT port(s). BMCA will be triggered after receiving the Announce message. 5. If the BMCA procedure in NW-TT determines to use Announce message from the external grandmaster PTP instance, the UPF/NW-TT regenerates the Announce message based on the received Announce message for each Leader PTP port on the NW-TT and DS-TT(s) port for this PTP domain. The NW-TT/UPF forwards the regenerated Announce messages to the PDU session(s) related to the Leader PTP ports on the DS-TT(s). NOTE: Leader and Follower terms in this specification are aligned with NOTE 2 in clause 5.27.1.2.2.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2].. 6. If the TSN AF or TSCTSF has subscribed for notifications for the PTP port state changes, the UPF/NW-TT reports any changes to the PTP port states to the TSN AF or TSCTSF via UMIC (for DS-TT ports) or PMIC (for NW-TT ports). 7. Based on the notification for the PTP port state changes, the TSN AF or TSCTSF may request appropriate QoS treatment and PDU Session modification may then be triggered to modify the QoS Flow carrying the gPTP messages over user plane in order to be compliant with the IEEE Std 802.1AS [75] delay recommendation for carrying gPTP messages as in clause 5.27.1.6 of TS 23.501[ System architecture for the 5G System (5GS) ] [2].

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

F.3

10.5.6.19 Connectivity type

The purpose of the Connectivity type information element is to specify the type of connectivity selected by the network for the PDN connection. The Connectivity type information element is coded as shown in figure 10.5.6.19-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.6.19-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The Connectivity type is a type 1 information element. Figure 10.5.6.19-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Connectivity type information element Table 10.5.6.19-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Connectivity 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.19

10.5.3.5 Location updating type

The purpose of the Location Updating Type information element is to indicate whether a normal updating, a periodic updating or an IMSI attach is wanted. It may also indicate that a follow-on request has been received from the mobile station CM layer. The Location Updating Type information element is coded as shown in figure 10.5.79/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.93/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The Location Updating Type is a type 1 information element. Figure 10.5.79/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Location Updating Type information element Table 10.5.93/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Location Updating 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.3.5

4.20 5GS session management in WB-N1 mode for IoT

In WB-N1 mode, a UE operating in category CE can operate in either CE mode A or CE mode B (see 3GPP TS 36.306[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio access capabilities ] [25D]). If a UE that supports CE mode B and operates in WB-N1 mode and the UE's usage setting is not set to "voice centric" (see 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]), and: a) the use of enhanced coverage is not restricted by the network; or b) CE mode B is not restricted by the network (see 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]); the UE shall apply the value of the applicable NAS timer indicated in table 10.3.1 for WB-N1/CE mode. A UE that supports CE mode B and operates in WB-N1 mode shall not apply the value of the applicable NAS timer indicated in table 10.3.1 for WB-N1/CE mode before receiving an indication from the network that the use of enhanced coverage is not restricted, or CE mode B is not restricted, as described in this subclause. The NAS timer value obtained is used as described in the appropriate procedure subclause of this specification. The NAS timer value shall be calculated at start of a NAS procedure, and shall not be re-calculated until the NAS procedure is completed, restarted or aborted. If the use of extended NAS timer is indicated by the AMF (see 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8] and 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9]), the SMF shall calculate the value of the applicable NAS timer indicated in table 10.3.2 for WB-N1/CE mode. The NAS timer value obtained is used as described in the appropriate procedure subclause of this specification. The NAS timer value shall be calculated at start of a NAS procedure and shall not be re-calculated until the NAS procedure is completed, restarted or aborted. 4.21 Authentication and Key Management for Applications (AKMA) The UE may support AKMA. The purpose of AKMA is to provide authentication and key management to applications based on 3GPP credentials used for 5GS access as specified in 3GPP TS 33.535[ Authentication and Key Management for Applications (AKMA) based on 3GPP credentials in the 5G System (5GS) ] [24A], which allows the UE to securely exchange data with an AKMA application function. Upon receiving a request from the upper layers to obtain AKMA Anchor Key (KAKMA) and AKMA Key Identifier (A-KID), the UE supporting AKMA shall derive the KAKMA and the AKMA Temporary Identifier (A-TID) from the valid KAUSF if available as specified in 3GPP TS 33.535[ Authentication and Key Management for Applications (AKMA) based on 3GPP credentials in the 5G System (5GS) ] [24A], shall further derive the A-KID from the A-TID as specified in 3GPP TS 33.535[ Authentication and Key Management for Applications (AKMA) based on 3GPP credentials in the 5G System (5GS) ] [24A] and shall provide KAKMA and A-KID to the upper layers. The UE supporting AKMA shall notify the upper layers whenever there is a change of the KAUSF upon reception of an EAP-success message in subclauses 5.4.1.2.2.8, 5.4.1.2.3.1 and 5.4.1.2.3A.1 or upon reception of SECURITY MODE COMMAND message in subclauses 5.4.2.3. During an ongoing primary authentication and key agreement procedure (see subclause 5.4.1), if the UE receives a request from upper layers to obtain KAKMA and A-KID, the UE shall derive the KAKMA and A-TID after the completion of the ongoing primary authentication and key agreement procedure, shall further derive the A-KID from the A-TID as specified in 3GPP TS 33.535[ Authentication and Key Management for Applications (AKMA) based on 3GPP credentials in the 5G System (5GS) ] [24A] and shall provide KAKMA and A-KID to the upper layers. NOTE 1: The upper layers derive the AKMA Application Key (KAF) from KAKMA as specified in 3GPP TS 33.535[ Authentication and Key Management for Applications (AKMA) based on 3GPP credentials in the 5G System (5GS) ] [24A]. NOTE 2: The knowledge of whether a certain application needs to use AKMA or not is application specific and is out of the scope of 3GPP. NOTE 3: The exact method of securing the data exchange at the upper layers using KAF is application specific and is out of the scope of 3GPP. NOTE 4: The upper layers request the UE NAS layer to provide KAKMA and A-KID before the upper layers initiate communication with an AKMA application function. NOTE 5: Upon receiving a request from the upper layers to obtain KAKMA and A-KID, if there is no KAUSF available, the UE NAS layer cannot derive the KAKMA and A-KID and provides an indication to the upper layers that KAKMA and A-KID cannot be generated. 4.22 Uncrewed aerial vehicle identification, authentication, and authorization

3GPP TS 24.501

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

CT WG1

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

4.20