Datasets:

Exploration-Lab

/

MM-TelecoBench

like 1

Follow

Exploration Lab 62

G.2 Structure of HTTP Message

Following is a typical structure of the HTTP Message: Figure G.2-1 Typical structure of the HTTP message received by SEPP It consists of: - HTTP Message payload with JSON based IEs - HTTP Headers with or without sensitive elements - HTTP Request-URI with or without sensitive elements such as SUPI. In the outgoing direction, i.e. towards the N32 interface, the SEPP shall parse the HTTP message fully and apply protection on each part as required. In the incoming direction, i.e. towards the Network Function, the SEPP shall verify the message, and if successful reassemble the original message and send it to the destined Network Function.

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

G.2

6.16.4 Security handling in NAS based redirection from 5GS to EPS

When a UE initiates registration procedure with the AMF, the AMF may redirect the UE from 5GC to EPC by including a EMM cause indicating to the UE that it shall not use 5GC, as described in clause 5.31.3 in TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The following requirements apply to Registration Reject message with an EMM cause which indicates to the UE that the UE shall not use 5GC: - the AMF shall only send such a Registration Reject message once NAS security has been established between the AMF and the UE; and - the UE shall only act upon such Registration Reject message if received integrity protected and if UE has verified the integrity of the Registration Reject message successfully. NOTE: This solution does not apply to unauthenticated emergency calls.

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

6.16.4

5.3.2 Registration Management 5.3.2.1 General

A UE/user needs to register with the network to receive services that requires registration. Once registered and if applicable the UE updates its registration with the network (see TS 23.502[ Procedures for the 5G System (5GS) ] [3]): - periodically, in order to remain reachable (Periodic Registration Update); or - upon mobility (Mobility Registration Update); or - to update its capabilities or re-negotiate protocol parameters (Mobility Registration Update). The Initial Registration procedure involves execution of Network Access Control functions as defined in clause 5.2 (i.e. user authentication and access authorization based on subscription profiles in UDM). As result of the Registration procedure, the identifier of the serving AMF serving the UE in the access through which the UE has registered will be registered in UDM. The registration management procedures are applicable over both 3GPP access and Non-3GPP access. The 3GPP and Non-3GPP RM states are independent of each other, see clause 5.3.2.4.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.3.2

5.35A.4 MBSR authorization

For a MBSR, the subscription information stored in the HPLMN indicates whether it is authorized to operate as MBSR, and the corresponding location and time information as specified in TS 23.502[ Procedures for the 5G System (5GS) ] [3]. NOTE 1: For non-roaming MBSRs, the operator local policy can be taken into consideration for MBSR authorization, e.g. based on the network status, or a limit on the number of MBSRs operating in a certain area. When the MBSR (IAB-UE) performs initial registration with the serving PLMN, it indicates the request to operate as a MBSR as described in clause 5.35A.1. The AMF authorizes the MBSR based on the subscription information, and provides MBSR authorized indication to the MBSR node over NAS and NG-RAN over NGAP as described in the registration procedure in TS 23.502[ Procedures for the 5G System (5GS) ] [3]. The MBSR establishes the connection to OAM system using the configuration information for MBSR operation upon the reception of MBSR authorization indication (authorized). The MBSR provides the information about the authorization result (authorized) to its IAB-DU component. When the AMF formulates the registration area for an authorized MBSR, the TAs included in the registration area are authorized for MBSR operation homogenously, taking any MBSR Operation allowed information in subscription data and operator local policy into account. NOTE 2: The MBSR support can be deployed in certain Network Slices based on operator configuration and Network slicing functionalities (e.g. the function specified in clause 5.15.18) can be applied when suitable. When MBSR roaming is supported, a roaming agreement between VPLMN and HPLMN regarding MBSR operation is in place. The AMF can make use of the subscription data for authorization of the MBSR in the V-PLMN. MBSR (IAB-DU) can use IAB-node integration procedure or inter-IAB-donor gNB mobility procedure to integrate into the serving PLMN to provide service. NOTE 3: How the MBSR obtains the configuration information for MBSR operation is described in clause 5.35A.2. If the MBSR operation is not authorized (e.g. due to location or time limitation), the AMF of the MBSR can indicate to the MBSR IAB-UE that it is not allowed to act as an MBSR, i.e. the MBSR authorization indication (not authorized), as part of registration procedure. The AMF may provide the indication in a Registration Accept (if the PLMN allows the MBSR IAB-UE to be registered in the PLMN). In this case, the AMF includes the MBSR authorization indication (not authorized) to donor-gNB. The MBSR provides the information about the authorization result (not authorized) to its IAB-DU component. The AMF may reject the Registration (if the PLMN does not allow the MBSR IAB-UE to be registered in the PLMN). Editor's note: The details of the additional information and corresponding MBSR behaviour will be added. When the MBSR authorization state changes for a registered MBSR node (either authorized, or not authorized), the AMF updates the MBSR and the NG-RAN accordingly. Based on the operator configuration, the AMF may use either Deregistration (with re-registration required indication) or the UE Configuration Update procedure to inform the MBSR regarding the updated authorization status: - When Deregistration (with re-registration required indication) procedure is used, AMF provides the new authorization indication to MBSR (IAB-UE) as described above, when the MBSR performs initial Registration procedure after the deregistration. - When UE Configuration Update procedure is used, the AMF provides the new authorization indication and additional information to the MBSR in the UE Configuration Update Command. The MBSR provides the information about the new authorization status to its IAB-DU component. The AMF informs the NG-RAN of the new authorization status using UE Context Modification, Initial Context Setup procedure or the DOWNLINK NAS TRANSPORT message, with the following principles: - If the authorization state changes from authorized to not authorized and AMF uses the UE Configuration Updated procedure to update the MBSR, the AMF updates the NG-RAN with the new authorization indication (not authorized) by including this information in the DOWNLINK NAS TRANSPORT message. The NG-RAN completes handover of the UEs served by the MBSR before releasing the F1 connection to the MBSR IAB-DU. - If the authorization state changes from authorized to not authorized and the AMF uses the Deregistration procedure to update the MBSR, the AMF sends the UE Context Modification message to NG-RAN and after a certain period (e.g. based on the expiration of a timer configured on the AMF) the AMF executes the deregistration procedure with MBSR and releases the NAS signalling connection. If the Network-initiated Deregistration procedure is triggered for MBSR IAB-UE that is registered with authorization to act as MBSR, the AMF sends the UE Context Modification message to NG-RAN and updates the NG-RAN with the authorization indication as not authorized and after a certain period (e.g. based on the expiration of a timer configured on the AMF) the AMF executes the deregistration procedure with MBSR and releases the NAS signalling connection. NOTE 4: The AMF delays the MBSR de-registration to allow the IAB-donor gNB to move all connected UEs via MBSR to other cells as specified in clause 8.9.10 of TS 38.401[ NG-RAN; Architecture description ] [42]. If a PDU session is used to provide OAM access for MBSR when it is not authorized but remains registered, the AMF may notify the SMF serving the PDU session for O&M access to trigger the release of the PDU Session. NOTE 5: The mechanism applies to both roaming and non-roaming MBSR operations.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.35A.4

4.4.6.1 IP Throughput in DL

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

3GPP TS 32.425

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

SA WG5

3GPP Series : 32 , OAM&P and Charging

4.4.6.1

5.3.4.1 Mobility Restrictions 5.3.4.1.1 General

Mobility Restrictions restrict mobility handling or service access of a UE. The Mobility Restriction functionality is provided by the UE (only for mobility restriction categories provided to the UE), the radio access network and the core network. Unless otherwise stated, Mobility Restrictions only apply to 3GPP access and wireline access, they do not apply to other non-3GPP accesses. The UE and the network shall override Mobility restriction as specified in clause 5.16.4.3 when accessing the network for Emergency Services. For MPS and MCX, service area restriction does not apply, as specified in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]. For UE requesting Disaster Roaming service, the UE is only allowed to receive services in the area with Disaster Condition as specified in clause 5.40.4. The other areas within the PLMN shall be considered as forbidden area for the UE registered for Disaster Roaming service. Service Area restrictions and handling of Forbidden Areas for CM-IDLE state and, for CM-CONNECTED state when in RRC_INACTIVE state are executed by the UE based on information received from the core network. Mobility Restrictions for CM-CONNECTED state when in RRC_CONNECTED state are executed by the radio access network and the core network. In CM-CONNECTED state, the core network provides Mobility Restrictions to the radio access network within Mobility Restriction List. Mobility Restrictions consists of RAT restriction, Forbidden Area, Service Area Restrictions, Core Network type restriction and Closed Access Group information as follows: - RAT restriction: Defines the 3GPP and non-3GPP Radio Access Technology(ies), a UE is not allowed to access in a PLMN. In a restricted RAT a UE based on subscription is not permitted access to the network for this PLMN. For 3GPP access and CM-CONNECTED state, when radio access network determines target RAT and target PLMN during Handover procedure, it should take per PLMN RAT restriction into consideration. The RAT restriction is enforced in the network, and not provided to the UE. - Forbidden Area: In a Forbidden Area, the UE, based on subscription, is not permitted to initiate any communication with the network for this PLMN. The UE behaviour in terms of cell selection, RAT selection and PLMN selection depends on the network response that informs the UE of Forbidden Area. A Forbidden Area applies either to 3GPP access or to non-3GPP access. Further description on Forbidden Area when using wireline access is available in TS 23.316[ Wireless and wireline convergence access support for the 5G System (5GS) ] [84]. Support for Forbidden Area with NR satellite access is described in clause 5.4.11.8. Forbidden Areas should not be used for Untrusted or Trusted non-3GPP access. NOTE 1: If a UE receives that the UE is accessing from a forbidden tracking area when registering over untrusted non-3GPP access or trusted non-3GPP access, the UE cannot determine the corresponding TAI and thus needs to consider that access to untrusted non-3GPP access and to trusted non-3GPP access in this PLMN is forbidden until the forbidden area list is removed as described in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]. NOTE 2: The UE reactions to specific network responses are described in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]. - Service Area Restriction: Defines areas in which the UE may or may not initiate communication with the network as follows: - Allowed Area: In an Allowed Area, the UE is permitted to initiate communication with the network as allowed by the subscription. - Non-Allowed Area: In a Non-Allowed Area a UE is service area restricted based on subscription. The UE and the network are not allowed to initiate Service Request, or any connection requests for user plane data, control plane data, exception data reporting, or SM signalling (except for PS Data Off status change reporting) to obtain user services that are not related to mobility. The UE shall not use the entering of a Non-Allowed Area as a criterion for Cell Reselection, a trigger for PLMN Selection or Domain selection for UE originating sessions or calls. The RRC procedures while the UE is in CM-CONNECTED with RRC_INACTIVE state are unchanged compared to when the UE is in an Allowed Area. The RM procedures are unchanged compared to when the UE is in an Allowed Area. The UE in a Non-Allowed Area shall respond to core network paging or NAS Notification message from non-3GPP access with Service Request and RAN paging. The UE in a Non-Allowed Area may initiate MA PDU Session establishment or activation over a non-3GPP access other than wireline access, but the User Plane resources on the 3GPP access for the MA-PDU shall not be established or activated. The handling of Non-Allowed Area when using wireline access is described in TS 23.316[ Wireless and wireline convergence access support for the 5G System (5GS) ] [84]. NOTE 3: When the services are restricted in 5GS due to Service Area Restriction, then it is assumed that the services will be also restricted in all RATs/Systems at the same location(s) using appropriate mechanisms available in the other RATs/Systems. NOTE 4: Delivery of SOR transparent container, UE policy container, UE parameters update transparent container as defined in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47], or removal of any stored Paging Restriction Information from network via Registration Request (see clause 5.38), is part of the mobility related service and is allowed in an area with service restriction. NOTE 5: For a UE in CM-CONNECTED state then neither control plane data transmission nor, if user plane resources are already established, user plane data transmission are restricted by a non-allowed area. - Core Network type restriction: Defines whether UE is allowed to connect to 5GC only, EPC only, both 5GC and EPC for this PLMN. The Core Network type restriction when received applies in the PLMN either to both 3GPP and non-3GPP Access Types or to non-3GPP Access Type only. NOTE 6: The Core Network type restriction can be used e.g. in network deployments where the E-UTRAN connects to both EPC and 5GC as described in clause 5.17. When the Core Network type restriction applies to non-3GPP Access Type, the UE is restricted from using any connectivity to an N3IWF. - Closed Access Group information: As defined in clause 5.30.3. For a given UE, the core network determines the Mobility Restrictions based on UE subscription information, UE location and/or local policy (e.g. if the HPLMN has not deployed 5GC, HPLMN ID of the UE and the operator's policy are used in the VPLMN for determining the Core Network type restriction). The Mobility Restriction may change due to e.g. UE's subscription, location change and local policy. Optionally the Service Area Restrictions or the Non-Allowed Area may in addition be fine-tuned by the PCF e.g. based on UE location, PEI and network policies. Service Area Restrictions may be updated during a Registration procedure or UE Configuration Update procedure. NOTE 7: The subscription management ensures that for MPS service subscriber the Mobility Restrictions is not included. If the network sends Service Area Restrictions to the UE, the network sends only either an Allowed Area, or a Non-Allowed Area, but not both at the same time, to the UE. If the UE has received an Allowed Area from the network, any TA not part of the Allowed Area is considered by the UE as non-allowed. If the UE has received a Non-Allowed Area from the network, any TA not part of the Non-Allowed Area is considered by the UE as allowed. If the UE has not received any Service Area Restrictions, any TA in the PLMN is considered as allowed. If the UE has overlapping areas between Forbidden Areas, Service Area Restrictions, or any combination of them, the UE shall proceed in the following precedence order: - The evaluation of Forbidden Areas shall take precedence over the evaluation of Service Area Restrictions. The UDM shall provide to the AMF the information defined in TS 23.008[ Organization of subscriber data ] [119] about the subscriber's NR or E-UTRA access restriction set by the operator determined e.g. by subscription scenario and roaming scenario: - For NR: - NR not allowed as primary RAT. - NR not allowed as secondary RAT. - NR in unlicensed bands not allowed as primary RAT. - NR in unlicensed bands not allowed as secondary RAT. - NR(LEO) satellite access not allowed as primary RAT. - NR(MEO) satellite access not allowed as primary RAT. - NR(GEO) satellite access not allowed as primary RAT. - NR(OTHERSAT) satellite access not allowed as primary RAT. - NR RedCap not allowed as primary RAT. - For E-UTRA: - E-UTRA not allowed as primary RAT. - E-UTRA not allowed as secondary RAT. - E-UTRA in unlicensed bands not allowed as secondary RAT. - NB-IoT not allowed as primary RAT. - LTE-M not allowed as primary RAT. In order to enforce all primary RAT restrictions, the related RAT has to be deployed in different Tracking Area Codes and the subscriber shall not be allowed to access the network in TAs using the particular RAT. With all secondary RAT restrictions, the subscriber shall not be allowed to use this RAT as secondary RAT.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.3.4.1

9.3.3 Frequency-selective interference

The accuracy of sub-band channel quality indicator (CQI) reporting under frequency selective interference conditions is determined by a percentile of the reported differential CQI offset level +2 for a preferred sub-band, and the relative increase of the throughput obtained when transmitting on a randomly selected sub-band among the sub-bands with the highest reported differential CQI offset level the corresponding transport format compared to the case for which a fixed format is transmitted on any sub-band in set S of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [6]. The purpose is to verify that preferred sub-bands are used for frequently-selective scheduling under frequency-selective interference conditions.

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

13.2.4.2 Overall Message payload structure for message reformatting at SEPP

The SEPP reformats an HTTP message received from an internal Network Function into two temporary JSON objects that will be intput to JWE: a. The dataToIntegrityProtect, containing information that is only integrity protected. It consists of the following: - clearTextEncapsulationMessage: contains the complete original HTTP message, excluding attribute values which require encryption and, including the pseudo-header fields, HTTP headers and HTTP message body. - metadata: contains SEPP generated information i.e. authorizedIPX ID, N32-f message ID and N32-f context ID. b. The dataToIntegrityProtectAndCipher: contains attribute values of the original message that require both encryption and integrity protection. For the details of JSON representation of a reformatted HTTP message, refer to TS 29.573[ 5G System; Public Land Mobile Network (PLMN) Interconnection; Stage 3 ] [92].

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

13.2.4.2

5.4.4.3 Paging assistance information

The paging assistance information contains UE radio related information that assists the RAN for efficient paging. The Paging assistance information contains: a) UE radio capability for paging information: - The UE Radio Capability for Paging Information contains information derived by the NG-RAN node (e.g. band support information) from the UE Radio Capability information. The AMF stores this information without needing to understand its contents. As the AMF only infrequently (e.g. at Initial Registration) prompts the NG-RAN to retrieve and upload the UE radio capabilities i.e. UE Radio Capability information to the AMF, and the AMF may be connected to more than one NG-RAN RAT, it is the responsibility of the NG-RAN to ensure that UE Radio Capability for Paging Information (which is derived by the NG-RAN node) contains information on all NG-RAN RATs that the UE supports in that PLMN. To assist the NG-RAN in this task, as specified in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [34], the AMF provides its stored UE Radio Capability for Paging Information in every NG-AP INITIAL CONTEXT SETUP REQUEST message sent to the NG-RAN. - The UE Radio Capability for Paging Information is maintained in the core network, even during AMF reselection, and is stored in the UCMF alongside the UE Radio Capability information associated to a UE Radio Capability ID. b) Information On Recommended Cells And RAN nodes For Paging: - Information sent by the NG-RAN, and used by the AMF when paging the UE to help determining the NG RAN nodes to be paged as well as to provide the information on recommended cells to each of these RAN nodes, in order to optimize the probability of successful paging while minimizing the signalling load on the radio path. - The RAN provides this information during N2 release.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.4.4.3

8.15.2.1 Inter-gNB-CU Mobility between MBS Supporting nodes

Figure 8.15.2.1-1 shows the inter-gNB-CU multicast mobility procedure between MBS Supporting nodes during an active multicast session. Figure 8.15.2.1-1: Inter-gNB-CU Mobility for Multicast 1. The Source gNB-CU-CP sends MC BEARER CONTEXT MODIFICATION REQUEST message towards the Source gNB-CU-UP, to request the last delivered MRB Progress of an MBS Session related to a Multicast F1-U Context Reference E1. 2. The Source gNB-CU-UP responds to the gNB-CU-CP in the MC BEARER CONTEXT MODIFICATION RESPONSE message, providing the last delievered MRB Progress. 3. The source gNB-CU-CP sends the HANDOVER REQUEST message to the target gNB-CU-CP with the last delievered MRB progress for the Multicast sessions the UE has joined. 4. In case the Multicast session which the UE has joined was not established in the target cell, the target gNB-CU-CP triggers the Multicast MBS Session Context Establishment procedure as defined in section 8.15.1.2. 5. The target gNB-CU-CP triggers MC BEARER CONTET SETUP REQUEST message towards the target gNB-CU-UP. 6. The target gNB-CU-UP responds to the target gNB-CU-CP by sending the MC BEARER CONTET SETUP RESPONSE message. 7. The target gNB-CU-CP sends UE CONTEXT SETUP REQUEST towards the target gNB-DU. If the target gNB-CU-CP has decided to request a PTP Forwarding tunnel, the message contains the PTP Forwarding Tunnel Required indication and the last delivered MRB Progress for the MRBs requested to be configured. 8. The target gNB-DU sends UE CONTEXT SETUP RESPONSE towards the target gNB-CU-CP. 9. If a PTP Forwarding Tunnel was requested in step 7, the target gNB-DU shall, if supported, trigger the F1-U tunnel establishment via MULTICAST DISTRIBUTION SETUP REQUEST, including the F1-U DL UP TNL information and the last delievered MRB Progress for the each of the MRB. 10. The target gNB-CU-CP sends the MC BEARER CONTEXT MODIFICATION REQUEST towards the target gNB-CU-UP, including for each MRB a request for the oldest availiable MRB Progress information, the last delivered MRB Progress, and the F1-U DL UP TNL information. 11. Based on the information received in step 10, the target gNB-CU-UP determines whether the Xn-U data forwarding is needed or not, and in case it is needed, provide for each MRB the oldest available MRB Progress and the assigned XN-U DL Forwarding UP TNL Info to the target gNB-CU-CP in the MC BEARER CONTEXT MODIFICATION RESPONSE message. 12. In case step 9 was triggerred, the target gNB-CU-CP sends the MULTICAST DISTRIBUTION SETUP RESPONSE to the target gNB-DU. 13. The target gNB-CU-CP sends HANDOVER REQUEST ACKNOWLEDGE to the source gNB-CU-CP, including the XN-U DL Forwarding UP TNL Info and the oldest available MRB Progress for each MRB. 14. The source gNB-CU-CP forwards the XN-U DL Forwarding UP TNL Info and the oldest available MRB Progress for each MRB to the source gNB-CU-UP via MC BEARER CONTEXT MODIFICATION REQUEST message. 15. The source gNB-CU-UP sends the MC BEARER CONTEXT MODIFICATION RESPONSE message to the source gNB-CU-CP. 16. The source gNB-CU-UP starts to forward MBS data towards the target gNB-CU-UP. NOTE: step 16 may happen before or after or in parallel with step 15. 17. If a PTP Forwarding Tunnel was established, the target gNB-CU-UP sends the forwarding data to the target gNB-DU.

3GPP TS 38.401

NG-RAN; Architecture description

RAN3

3GPP Series : 38 , Radio technology beyond LTE

8.15.2.1

5.4.3.2 Paging Policy Differentiation

Paging policy differentiation is an optional feature that allows the AMF, based on operator configuration, to apply different paging strategies for different traffic or service types provided within the same PDU Session. In this Release of the specification this feature applies only to PDU Session of IP type. When the 5GS supports the Paging Policy Differentiation (PPD) feature, the DSCP value (TOS in IPv4 / TC in IPv6) is set by the application to indicate to the 5GS which Paging Policy should be applied for a certain IP packet. For example, as defined in TS 23.228[ IP Multimedia Subsystem (IMS); Stage 2 ] [15], the P-CSCF may support Paging Policy Differentiation by marking packet(s) to be sent towards the UE that relate to a specific IMS services (e.g. conversational voice as defined in IMS multimedia telephony service). NOTE 1: This PPD feature may be used to determine the Paging Cause Indication for Voice Service, as described in clause 5.38.3. It shall be possible for the operator to configure the SMF in such a way that the Paging Policy Differentiation feature only applies to certain HPLMNs, DNNs and 5QIs. In the case of HR roaming, this configuration is done in the SMF in the VPLMN. NOTE 2: Support of Paging Policy Differentiation in the case of HR roaming requires inter operator agreements including on the DSCP value associated with this feature. In the case of Network Triggered Service Request and UPF buffering downlink packets, the UPF shall include the DSCP in TOS (IPv4) / TC (IPv6) value from the IP header of the downlink packet and an indication of the corresponding QoS Flow in the Downlink Data Report sent to the SMF. When PPD applies, the SMF determines the Paging Policy Indicator (PPI) based on the DSCP received from the UPF. In the case of Network Triggered Service Request and SMF buffering downlink packets, when PPD applies, the SMF determines the PPI based on the DSCP in TOS (IPv4) / TC (IPv6) value from the IP header of the received downlink packet and identifies the corresponding QoS Flow from the QFI of the received downlink packet. The SMF includes the PPI, the ARP and the 5QI of the corresponding QoS Flow in the N11 message sent to the AMF. If the UE is in CM IDLE, the AMF uses this information to derive a paging strategy, and sends paging messages to NG-RAN over N2. NOTE 3: Network configuration needs to ensure that the information used as a trigger for Paging Policy Indication is not changed within the 5GS. NOTE 4: Network configuration needs to ensure that the specific DSCP in TOS (IPv4) / TC (IPv6) value, used as a trigger for Paging Policy Indication, is managed correctly in order to avoid the accidental use of certain paging policies. For a UE in RRC_INACTIVE state the NG-RAN may enforce specific paging policies in the case of NG-RAN paging, based on 5QI, ARP and PPI associated with an incoming DL PDU. To enable this, the SMF instructs the UPF to detect the DSCP in the TOS (IPv4) / TC (IPv6) value in the IP header of the DL PDU (by using a DL PDR with the DSCP for this traffic) and to transfer the corresponding PPI in the CN tunnel header (by using a QER with the PPI value). The NG-RAN can then utilize the PPI received in the CN tunnel header of an incoming DL PDU in order to apply the corresponding paging policy for the case the UE needs to be paged when in RRC_INACTIVE state. In the case of Home-Routed roaming, the V-SMF is responsible of controlling UPF setting of the PPI. In the case of PDU Session with I-SMF, the I-SMF is responsible of controlling UPF setting of the PPI.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.4.3.2

5.7.4.3 Actions related to transmission of UEAssistanceInformation message

The UE shall set the contents of the UEAssistanceInformation message as follows: 1> if transmission of the UEAssistanceInformation message is initiated to provide a delay budget report according to 5.7.4.2 or 5.3.5.3; 2> set delayBudgetReport to type1 according to a desired value; 1> if transmission of the UEAssistanceInformation message is initiated to provide overheating assistance information according to 5.7.4.2 or 5.3.5.3; 2> if the UE experiences internal overheating: 3> if the UE prefers to temporarily reduce the number of maximum secondary component carriers: 4> include reducedMaxCCs in the OverheatingAssistance IE; 4> set reducedCCsDL to the number of maximum SCells the UE prefers to be temporarily configured in downlink; 4> set reducedCCsUL to the number of maximum SCells the UE prefers to be temporarily configured in uplink; 3> if the UE prefers to temporarily reduce maximum aggregated bandwidth of FR1: 4> include reducedMaxBW-FR1 in the OverheatingAssistance IE; 4> set reducedBW-DL to the maximum aggregated bandwidth the UE prefers to be temporarily configured across all downlink carriers of FR1; 4> set reducedBW-UL to the maximum aggregated bandwidth the UE prefers to be temporarily configured across all uplink carriers of FR1; 3> if the UE prefers to temporarily reduce maximum aggregated bandwidth of FR2-1: 4> include reducedMaxBW-FR2 in the OverheatingAssistance IE; 4> set reducedBW-DL to the maximum aggregated bandwidth the UE prefers to be temporarily configured across all downlink carriers of FR2-1; 4> set reducedBW-UL to the maximum aggregated bandwidth the UE prefers to be temporarily configured across all uplink carriers of FR2-1; 3> if the UE prefers to temporarily reduce maximum aggregated bandwidth of FR2-2: 4> include reducedMaxBW-FR2-2 in the OverheatingAssistance IE; 4> set reducedBW-FR2-2-DL to the maximum aggregated bandwidth the UE prefers to be temporarily configured across all downlink carriers of FR2-2; 4> set reducedBW-FR2-2-UL to the maximum aggregated bandwidth the UE prefers to be temporarily configured across all uplink carriers of FR2-2; 3> if the UE prefers to temporarily reduce the number of maximum MIMO layers of each serving cell operating on FR1: 4> include reducedMaxMIMO-LayersFR1 in the OverheatingAssistance IE; 4> set reducedMIMO-LayersFR1-DL to the number of maximum MIMO layers of each serving cell operating on FR1 the UE prefers to be temporarily configured in downlink; 4> set reducedMIMO-LayersFR1-UL to the number of maximum MIMO layers of each serving cell operating on FR1 the UE prefers to be temporarily configured in uplink; 3> if the UE prefers to temporarily reduce the number of maximum MIMO layers of each serving cell operating on FR2-1: 4> include reducedMaxMIMO-LayersFR2 in the OverheatingAssistance IE; 4> set reducedMIMO-LayersFR2-DL to the number of maximum MIMO layers of each serving cell operating on FR2-1 the UE prefers to be temporarily configured in downlink; 4> set reducedMIMO-LayersFR2-UL to the number of maximum MIMO layers of each serving cell operating on FR2-1 the UE prefers to be temporarily configured in uplink; 3> if the UE prefers to temporarily reduce the number of maximum MIMO layers of each serving cell operating on FR2-2: 4> include reducedMaxMIMO-LayersFR2-2 in the OverheatingAssistance IE; 4> set reducedMIMO-LayersFR2-2-DL to the number of maximum MIMO layers of each serving cell operating on FR2 the UE prefers to be temporarily configured in downlink; 4> set reducedMIMO-LayersFR2-2-UL to the number of maximum MIMO layers of each serving cell operating on FR2 the UE prefers to be temporarily configured in uplink; 2> else (if the UE no longer experiences an overheating condition): 3> do not include reducedMaxCCs, reducedMaxBW-FR1, reducedMaxBW-FR2, reducedMaxBW-FR2-2, reducedMaxMIMO-LayersFR1, reducedMaxMIMO-LayersFR2 or reducedMaxMIMO-LayersFR2-2 in OverheatingAssistance IE; 1> if transmission of the UEAssistanceInformation message is initiated to provide IDC assistance information according to 5.7.4.2 or 5.3.5.3: 2> if there is at least one carrier frequency included in candidateServingFreqListNR, the UE is experiencing IDC problems that it cannot solve by itself: 3> include the field affectedCarrierFreqList with an entry for each affected carrier frequency included in candidateServingFreqListNR; 3> for each carrier frequency included in the field affectedCarrierFreqList, include interferenceDirection and set it accordingly; 2> if there is at least one supported UL CA or NR-DC combination comprising of carrier frequencies included in candidateServingFreqListNR, the UE is experiencing IDC problems that it cannot solve by itself: 3> include victimSystemType for each UL CA or NR-DC combination included in affectedCarrierFreqCombList; 3> if the UE sets victimSystemType to wlan or bluetooth: 4> include affectedCarrierFreqCombList with an entry for each supported UL CA combination comprising of carrier frequencies included in candidateServingFreqListNR, that is affected by IDC problems; 3> else: 4> optionally include affectedCarrierFreqCombList with an entry for each supported UL CA or NR-DC combination comprising of carrier frequencies included in candidateServingFreqListNR, that is affected by IDC problems; 2> if there is at least one affected frequency range overlapping with one candidate frequency range included in candidateServingFreqRangeListNR, and the center frequency of the affected frequency range is within the candidate frequency range included in candidateServingFreqRangeListNR, the UE is experiencing IDC problems that it cannot solve by itself: 3> include the field affectedCarrierFreqRangeList with an entry for each affected frequency range; 3> for each affected frequency range included in the field affectedCarrierFreqRangeList, include centerFreq and affectedBandwidth; 3> for each affected frequency range included in the field affectedCarrierFreqRangeList, include interferenceDirection and optionally victimSystemType, and set it accordingly; 2> if there is at least one supported UL CA or NR-DC combinations comprising of candidate frequency ranges included in candidateServingFreqRangeListNR, and each affected frequency range in the UL CA or NR-DC combination overlapping with one candidate frequency range included in candidateServingFreqRangeListNR, and the center frequency of the affected frequency range is within the candidate frequency range included in candidateServingFreqRangeListNR, the UE is experiencing IDC problems that it cannot solve by itself: 3> include the field affectedCarrierFreqRangeCombList with an entry for each supported UL CA or NR-DC combination comprising of frequency ranges that is affected by IDC problems; 3> for each affected frequency range included in the field affectedCarrierFreqRangeCombList, include centerFreq and affectedBandwidth; 3> for each UL CA or NR-DC combination included in the field affectedCarrierFreqRangeCombList, include interferenceDirection and optionally victimSystemType, and set it accordingly; 2> if there is at least one candidate carrier frequency included in candidateServingFreqListNR or candidate frequency range included in candidateServingFreqRangeListNR or one supported UL CA or NR-DC combination comprising of candidate carrier frequencies included in candidateServingFreqListNR or candidate frequency ranges included in candidateServingFreqRangeListNR, the UE is experiencing IDC problems that it cannot solve by itself, and affectedCarrierFreqList or affectedCarrierFreqCombList or affectedCarrierFreqRangeList or affectedCarrierFreqRangeCombList is included, and idc-TDM-AssistanceConfig is set to setup: 3> include Time Domain Multiplexing (TDM) based assistance information as indicated by idc-TDM-Assistance that could be used to resolve the IDC problems; NOTE 1: When sending an UEAssistanceInformation message to inform the IDC problems, the UE includes all IDC assistance information (rather than providing e.g. the changed part(s) of the IDC assistance information). NOTE 2: Upon not anymore experiencing a particular IDC problem that the UE previously reported, the UE provides an IDC indication with the modified contents of the UEAssistanceInformation message (e.g. by not including the IDC assistance information in the idc-Assistance, idc-FDM-Assistance and idc-TDM-Assistance fields). 1> if transmission of the UEAssistanceInformation message is initiated to provide drx-Preference of a cell group for power saving according to 5.7.4.2 or 5.3.5.3: 2> include drx-Preference in the UEAssistanceInformation message; 2> if the UE has a preference on DRX parameters for the cell group: 3> if the UE has a preference for the long DRX cycle: 4> include preferredDRX-LongCycle in the DRX-Preference IE and set it to the preferred value; 3> if the UE has a preference for the DRX inactivity timer: 4> include preferredDRX-InactivityTimer in the DRX-Preference IE and set it to the preferred value; 3> if the UE has a preference for the short DRX cycle: 4> include preferredDRX-ShortCycle in the DRX-Preference IE and set it to the preferred value; 3> if the UE has a preference for the short DRX timer: 4> include preferredDRX-ShortCycleTimer in the DRX-Preference IE and set it to the preferred value; 2> else (if the UE has no preference on DRX parameters for the cell group): 3> do not include preferredDRX-LongCycle, preferredDRX-InactivityTimer, preferredDRX-ShortCycle and preferredDRX-ShortCycleTimer in the DRX-Preference IE; 1> if transmission of the UEAssistanceInformation message is initiated to provide maxBW-Preference of a cell group for power saving according to 5.7.4.2 or 5.3.5.3: 2> include maxBW-Preference in the UEAssistanceInformation message; 2> if the UE has a preference on the maximum aggregated bandwidth for the cell group: 3> if the UE prefers to reduce the maximum aggregated bandwidth of FR1: 4> include reducedMaxBW-FR1 in the MaxBW-Preference IE; 4> set reducedBW-DL to the maximum aggregated bandwidth the UE desires to have configured across all downlink carriers of FR1 in the cell group; 4> set reducedBW-UL to the maximum aggregated bandwidth the UE desires to have configured across all uplink carriers of FR1 in the cell group; 3> if the UE prefers to reduce the maximum aggregated bandwidth of FR2-1: 4> include reducedMaxBW-FR2 in the MaxBW-Preference IE; 4> set reducedBW-DL to the maximum aggregated bandwidth the UE desires to have configured across all downlink carriers of FR2-1 in the cell group; 4> set reducedBW-UL to the maximum aggregated bandwidth the UE desires to have configured across all uplink carriers of FR2-1 in the cell group; 2> else (if the UE has no preference on the maximum aggregated bandwidth for the cell group): 3> do not include reducedMaxBW-FR1 and reducedMaxBW-FR2 in the MaxBW-Preference IE; 1> if transmission of the UEAssistanceInformation message is initiated to provide maxBW-PreferenceFR2-2 of a cell group for power saving according to 5.7.4.2 or 5.3.5.3: 2> include maxBW-PreferenceFR2-2 in the UEAssistanceInformation message; 3> if the UE prefers to reduce the maximum aggregated bandwidth of FR2-2: 4> include reducedMaxBW-FR2-2 in the MaxBW-PreferenceFR2-2 IE; 4> set reducedBW-FR2-2-DL to the maximum aggregated bandwidth the UE desires to have configured across all downlink carriers of FR2-2 in the cell group; 4> set reducedBW-FR2-2-UL to the maximum aggregated bandwidth the UE desires to have configured across all uplink carriers of FR2-2 in the cell group; 2> else (if the UE has no preference on the maximum aggregated bandwidth for the cell group): 3> do not include reducedMaxBW-FR2-2 in the MaxBW-PreferenceFR2-2 IE; 1> if transmission of the UEAssistanceInformation message is initiated to provide maxCC-Preference of a cell group for power saving according to 5.7.4.2 or 5.3.5.3: 2> include maxCC-Preference in the UEAssistanceInformation message; 2> if the UE has a preference on the maximum number of secondary component carriers for the cell group: 3> include reducedMaxCCs in the MaxCC-Preference IE; 3> set reducedCCsDL to the number of maximum SCells the UE desires to have configured in downlink in the cell group; 3> set reducedCCsUL to the number of maximum SCells the UE desires to have configured in uplink in the cell group; 2> else (if the UE has no preference on the maximum number of secondary component carriers for the cell group): 3> do not include reducedMaxCCs in the MaxCC-Preference IE; NOTE 3: The UE can implicitly indicate a preference for NR SCG release by reporting the maximum aggregated bandwidth preference for power saving of the cell group, if configured, as zero for both FR1 and FR2, and by reporting the maximum number of secondary component carriers for power saving of the cell group, if configured, as zero for both uplink and downlink. 1> if transmission of the UEAssistanceInformation message is initiated to provide maxMIMO-LayerPreference of a cell group for power saving according to 5.7.4.2 or 5.3.5.3: 2> include maxMIMO-LayerPreference in the UEAssistanceInformation message; 2> if the UE has a preference on the maximum number of MIMO layers for the cell group: 3> if the UE prefers to reduce the number of maximum MIMO layers of each serving cell operating on FR1: 4> include reducedMaxMIMO-LayersFR1 in the MaxMIMO-LayerPreference IE; 4> set reducedMIMO-LayersFR1-DL to the preferred maximum number of downlink MIMO layers of each BWP of each FR1 serving cell that the UE operates on in the cell group; 4> set reducedMIMO-LayersFR1-UL to the preferred maximum number of uplink MIMO layers of each FR1 serving cell that the UE operates on in the cell group; 3> if the UE prefers to reduce the number of maximum MIMO layers of each serving cell operating on FR2-1: 4> include reducedMaxMIMO-LayersFR2 in the MaxMIMO-LayerPreference IE; 4> set reducedMIMO-LayersFR2-DL to the preferred maximum number of downlink MIMO layers of each BWP of each FR2-1 serving cell that the UE operates on in the cell group; 4> set reducedMIMO-LayersFR2-UL to the preferred maximum number of uplink MIMO layers of each FR2-1 serving cell that the UE operates on in the cell group; 2> else (if the UE has no preference on the maximum number of MIMO layers for the cell group): 3> do not include reducedMaxMIMO-LayersFR1 and reducedMaxMIMO-LayersFR2 in the MaxMIMO-LayerPreference IE; 1> if transmission of the UEAssistanceInformation message is initiated to provide maxMIMO LayerPreferenceFR2 2 of a cell group for power saving according to 5.7.4.2 or 5.3.5.3: 2> include maxMIMO-LayerPreferenceFR2-2 in the UEAssistanceInformation message; 2> if the UE has a preference on the maximum number of MIMO layers for the cell group for FR2-2: 3> if the UE prefers to reduce the number of maximum MIMO layers of each serving cell operating on FR2 2: 4> include reducedMaxMIMO-LayersFR2-2 in the MaxMIMO-LayerPreferenceFR2 2 IE; 4> set reducedMIMO-LayersFR2-2-DL to the preferred maximum number of downlink MIMO layers of each BWP of each FR2-2 serving cell that the UE operates on in the cell group; 4> set reducedMIMO-LayersFR2-2-UL to the preferred maximum number of uplink MIMO layers of each FR2-2 serving cell that the UE operates on in the cell group; 2> else (if the UE has no preference on the maximum number of MIMO layers for the cell group): 3> do not include reducedMaxMIMO-LayersFR2-2 in the MaxMIMO-LayerPreferenceFR2-2 IE; 1> if transmission of the UEAssistanceInformation message is initiated to provide minSchedulingOffsetPreference of a cell group for power saving according to 5.7.4.2 or 5.3.5.3: 2> include minSchedulingOffsetPreference in the UEAssistanceInformation message; 2> if the UE has a preference on the minimum scheduling offset for cross-slot scheduling for the cell group: 3> if the UE has a preference for the value of K0 (TS 38.214[ NR; Physical layer procedures for data ] [19], clause 5.1.2.1) for cross-slot scheduling with 15 kHz SCS: 4> include preferredK0-SCS-15kHz in the MinSchedulingOffsetPreference IE and set it to the desired value of K0; 3> if the UE has a preference for the value of K0 for cross-slot scheduling with 30 kHz SCS: 4> include preferredK0-SCS-30kHz in the MinSchedulingOffsetPreference IE and set it to the desired value of K0; 3> if the UE has a preference for the value of K0 for cross-slot scheduling with 60 kHz SCS: 4> include preferredK0-SCS-60kHz in the MinSchedulingOffsetPreference IE and set it to the desired value of K0; 3> if the UE has a preference for the value of K0 for cross-slot scheduling with 120 kHz SCS: 4> include preferredK0-SCS-120kHz in the MinSchedulingOffsetPreference IE and set it to the desired value of K0; 3> if the UE has a preference for the value of K2 (TS 38.214[ NR; Physical layer procedures for data ] [19], clause 6.1.2.1) for cross-slot scheduling with 15 kHz SCS: 4> include preferredK2-SCS-15kHz in the MinSchedulingOffsetPreference IE and set it to the desired value of K2; 3> if the UE has a preference for the value of K2 for cross-slot scheduling with 30 kHz SCS: 4> include preferredK2-SCS-30kHz in the MinSchedulingOffsetPreference IE and set it to the desired value of K2; 3> if the UE has a preference for the value of K2 for cross-slot scheduling with 60 kHz SCS: 4> include preferredK2-SCS-60kHz in the MinSchedulingOffsetPreference IE and set it to the desired value of K2; 3> if the UE has a preference for the value of K2 for cross-slot scheduling with 120 kHz SCS: 4> include preferredK2-SCS-120kHz in the MinSchedulingOffsetPreference IE and set it to the desired value of K2; 2> else (if the UE has no preference on the minimum scheduling offset for cross-slot scheduling for the cell group): 3> do not include preferredK0 and preferredK2 in the MinSchedulingOffsetPreference IE; 1> if transmission of the UEAssistanceInformation message is initiated to provide minSchedulingOffsetPreferenceExt of a cell group for power saving according to 5.7.4.2 or 5.3.5.3: 2> include minSchedulingOffsetPreferenceExt in the UEAssistanceInformation message; 2> if the UE has a preference on the minimum scheduling offset for cross-slot scheduling for the cell group for FR2-2: 3> include minSchedulingOffsetPreferenceExt in the UEAssistanceInformation message; 4> if the UE has a preference for the value of K0 (TS 38.214[ NR; Physical layer procedures for data ] [19], clause 5.1.2.1) for cross-slot scheduling with 480 kHz SCS: 5> include preferredK0-SCS-480kHz in the minSchedulingOffsetPreferenceExt IE and set it to the desired value of K0; 4> if the UE has a preference for the value of K0 for cross-slot scheduling with 960 kHz SCS: 5> include preferredK0-SCS-960kHz in the minSchedulingOffsetPreferenceExt IE and set it to the desired value of K0; 4> if the UE has a preference for the value of K2 for cross-slot scheduling with 480 kHz SCS: 5> include preferredK2-SCS-480kHz in the minSchedulingOffsetPreferenceExt IE and set it to the desired value of K2; 4> if the UE has a preference for the value of K2 for cross-slot scheduling with 960 kHz SCS: 5> include preferredK2-SCS-960kHz in the minSchedulingOffsetPreferenceExt IE and set it to the desired value of K2; 3> else (if the UE has no preference on the minimum scheduling offset for cross-slot scheduling for the cell group): 4> do not include preferredK0 and preferredK2 in the minSchedulingOffsetPreferenceExt IE; 1> if transmission of the UEAssistanceInformation message is initiated to provide a release preference according to 5.7.4.2 or 5.3.5.3: 2> include releasePreference in the UEAssistanceInformation message; 2> set preferredRRC-State to the desired RRC state on transmission of the UEAssistanceInformation message; 1> if transmission of the UEAssistanceInformation message is initiated to provide an indication of preference in being provisioned with reference time information according to 5.7.4.2 or 5.3.5.3: 2> if the UE has a preference in being provisioned with reference time information: 3> set referenceTimeInfoPreference to true; 2> else: 3> set referenceTimeInfoPreference to false. 1> if transmission of the UEAssistanceInformation message is initiated to provide preference on FR2 UL gap according to 5.7.4.2 or 5.3.5.3: 2> if the UE has a preference for FR2 UL gap configuration: 3> set ul-GapFR2-PatternPreference to the preferred FR2 UL gap pattern; 2> else (if the UE has no preference for the FR2 UL gap configuration): 3> do not include ul-GapFR2-PatternPreference in the UL-GapFR2-Preference IE. 1> if transmission of the UEAssistanceInformation message is initiated to provide MUSIM assistance information according to 5.7.4.2 or 5.3.5.3: 2> if the UE has a preference for MUSIM periodic gap(s): 3> include musim-GapPreferenceList with an entry for each periodic gap the UE prefers to be configured; 4> set musim-GapLength and musim-GapRepetitionAndOffset in the musim-GapInfo IE to the values of the length and the repetition/offset of the gap(s), respectively, the UE prefers to be configured with; 2> if the UE has a preference for MUSIM aperiodic gap: 3> include the field musim-GapPreferenceList, with one entry for the aperiodic gap the UE prefers to be configured; 4> include musim-GapLength in the musim-GapInfo IE and set it to the values of the length of the gap the UE prefers to be configured with; 4> optionally include musim-Starting-SFN-AndSubframe in the musim-GapInfo IE and set it to the starting SFN/subframe of the gap the UE prefers to be configured with; 2> if the UE has no longer preference for the periodic/aperiodic gaps: 3> do not include musim-GapPreferenceList in the musim-Assistance IE; 2> if UE has a preference to leave RRC_CONNECTED state: 3> set musim-PreferredRRC-State to the preferred RRC state. 2> if UE has a preference for MUSIM gap priority: 3> include the musim-GapPriorityPreferenceList the UE prefers to be configured; 3> if the UE has preference to keep all collided MUSIM gaps for periodic MUSIM gap(s): 4> include the musim-GapKeep; 2> if UE has a preference for temporary capability restriction: 3> if UE has a preference for serving cell(s) and/or SCG to be released: 4> include the musim-Cell-SCG-ToRelease; 5> set musim-CellToRelease to include the serving cell(s) the UE prefers to be released; 5> set scg-ReleasePreference to scgReleasePreferred if the UE prefers the SCG to be released; 3> if UE has a preference to indicate the serving cells: 4> include the musim-CellToAffectList the UE prefers to be configured; 5> include the musim-ServCellIndex and the musim-MIMO-Layers-DL/ musim-MIMO-Layers-UL/ musim-SupportedBandwidth-DL/ musim-SupportedBandwidth-UL for the corresponding serving cell; 3> if UE has a preference to indicate the maximum number of CCs: 4> include the musim-capabilityRestricted for the corresponding musim-MaxCC the UE prefers to be configured; 5> include the the musim-MaxCC-DL/ musim-MaxCC-UL for the corresponding maximum number of CCs; 3> if UE has a preference to indicate band(s) and/or combination(s) of bands with capabilities restricted which comprise of the band(s) that is/are indicated in musim-CandidateBandList: 4> include the musim-AffectededBandCombList the UE prefer to be configured with capabilities restricted; 5> include the bandEntryIndex for each band for each band or each band of the combination(s) for which capabilities are restricted; 5> include the musim-CapabilityRestricted for the corresponding band(s) or bands of the combination(s); 3> if UE has a preference to indicate band(s) and/or combination(s) of bands to be avoided which comprise of band(s) that is indicated in musim-CandidateBandList: 4> include the musim-AvoidedBandsList the UE prefers not to be configured; 5> include the bandEntryIndex for each band or each band of the combination(s) to be avoided; 3> if UE has a preference for measurement gap requirement: 4> include the musim-NeedForGapsInfoNR to provide the measurement gap requirement information from the requestedTargetBandFilterNR-r16 of NeedForGapsConfigNR configuration in RRCResume message or RRCReconfiguration message of NR target bands the UE prefer to be configured; 2> if the UE has no longer preference for temporary capability restriction: 3> do not include the corresponding temporary capability restriction preference in the musim-CapRestriction in the musim-Assistance IE; 1> if transmission of the UEAssistanceInformation message is initiated to provide the relaxation state of RLM measurements of a cell group according to 5.7.4.2: 2> if the UE performs RLM measurement relaxation on the cell group according to TS 38.133[ NR; Requirements for support of radio resource management ] [14]: 3> set the rlm-MeasRelaxationState to true; 2> else: 3> set the rlm-MeasRelaxationState to false; 1> if transmission of the UEAssistanceInformation message is initiated to provide the relaxation state of BFD measurements of a cell group: 2> for each serving cell of the cell group: 3> if the UE performs BFD measurement relaxation on this serving cell according to TS 38.133[ NR; Requirements for support of radio resource management ] [14]: 4> set the n-th bit of bfd-MeasRelaxationState to '1', where n is equal to the servCellIndex value + 1 of the serving cell; 3> else: 4> set the n-th bit of bfd-MeasRelaxationState to '0', where n is equal to the servCellIndex value + 1 of the serving cell. 1> if transmission of the UEAssistanceInformation message is initiated to indicate availability of data mapped to radio bearers not configured for SDT according to 5.7.4.2: 2> include the nonSDT-DataIndication in the UEAssistanceInformation message; 2> include and set the resumeCause according to the information received from the upper layers, if provided. 1> if transmission of the UEAssistanceInformation message is initiated to provide an indication of preference for SCG deactivation according to 5.7.4.2: 2> include scg-DeactivationPreference in the UEAssistanceInformation message; 2> set the scg-DeactivationPreference to scgDeactivationPreferred if the UE prefers the SCG to be deactivated, otherwise set it to noPreference; 1> if transmission of the UEAssistanceInformation message is initiated to provide an indication that the UE has uplink data related to a deactivated SCG according to 5.7.4.2: 2> include uplinkData in the UEAssistanceInformation message. 1> if transmission of the UEAssistanceInformation message is initiated to provide an indication about whether the criterion for RRM relaxation for connected mode is fulfilled or not fulfilled: 2> if the criterion for RRM measurement relaxation for connected mode is fulfilled: 3> set the rrm-MeasRelaxationFulfilment to true; 2> else: 3> set the rrm-MeasRelaxationFulfilment to false. 1> if transmission of the UEAssistanceInformation message is initiated to provide the service link propagation delay difference between serving cell and neighbour cell(s) according to 5.7.4.2; 2> include the propagationDelayDifference for each neighbour cell in the neighCellInfoList; 1> if transmission of the UEAssistanceInformation message is initiated to provide preference on multi-Rx operation for FR2 according to 5.7.4.2: 2> if the UE has a preference for not operating on multi-Rx (i.e. not supporting simultaneous reception with different QCL-typeD) for FR2: 3> set multiRx-PreferenceFR2 to the preferred multi-Rx operation for FR2; 2> else (if the UE has the preference for operating on multi-Rx for FR2): 3> not include multiRx-PreferenceFR2. 1> if transmission of the UEAssistanceInformation message is initiated to indicate the availability of flight path information according to 5.7.4.2 or 5.3.5.3; 2> include the flightPathInfoAvailable; 1> if transmission of the UEAssistanceInformation message is initiated to provide UL traffic information according to 5.7.4.2: 2> for each PDU session for which the UE intends to provide UL traffic information in this UEAssistanceInformation message: 3> set pdu-SessionID to the value of the concerned PDU session ID; 3> for each QoS flow of this PDU session for which timer T346x is not running and for which the UE intends to provide UL traffic information in this UEAssistanceInformation message: 4> start timer T346x associated to this QoS flow with the timer value set to the value of ul-TrafficInfoProhibitTimer; 4> set qfi to the value of the concerned QFI; 4> if the jitter range measurement is available; and 4> if the UE did not provide jitter range since it was configured to provide UL traffic information, or if the measured jitter range has changed since the last transmission of the UEAssistanceInformation message containing jitterRange: 5> set jitterRange to the latest measured value of the jitter range; 4> if the burst arrival time measurement is available; and 4> if the UE did not provide burst arrival time since it was configured to provide UL traffic information, or if the measured burst arrival time has changed since the last transmission of the UEAssistanceInformation message containing burstArrivalTime: 5> set burstArrivalTime to the latest measured value of the burst arrival time; 4> if the traffic periodicity measurement is available; and 4> if the UE did not provide traffic periodicity since it was configured to provide UL traffic information, or if the measured traffic periodicity has changed since the last transmission of the UEAssistanceInformation message containing trafficPeriodicity: 5> set trafficPeriodicity to the latest measured value of the traffic periodicity; 4> if the UE did not provide pduSetIdentification since it was configured to provide UL traffic information, or if the information previously provided in pduSetIdentification has changed since the last transmission of the UEAssistanceInformation message containing pduSetIdentification: 5> if the UE is able to identify PDU Set related information for the QoS flow: 6> set pduSetIdentification to true; 5> else: 6> set pduSetIdentification to false. 1> if transmission of the UEAssistanceInformation message is initiated to report relay UE information with non-3GPP connection(s) according to 5.7.4.2: 2> include n3c-relayUE-InfoList in the UEAssistanceInformation message; The UE shall set the contents of the UEAssistanceInformation message for configured grant assistance information for NR sidelink communication or NR sidelink positioning: 1> if configured to provide configured grant assistance information for NR sidelink communication or NR sidelink positioning: 2> include the sl-UE-AssistanceInformationNR; NOTE 4: It is up to UE implementation when and how to trigger configured grant assistance information for NR sidelink communication. The UE shall: 1> if the procedure was triggered to provide configured grant assistance information for NR sidelink communication by an NR RRCReconfiguration message that was embedded within an E-UTRA RRCConnectionReconfiguration: 2> submit the UEAssistanceInformation to lower layers via SRB1, embedded in E-UTRA RRC message ULInformationTransferIRAT as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10], clause 5.6.28; 1> else if the procedure was triggered to provide UE preference for SCG deactivation or to indicate that the UE with a deactivate SCG has uplink data to send on a DRB for which there is no MCG RLC bearer: 2> submit the UEAssistanceInformation via SRB1 to lower layers for transmission; 1> else if the UE is in (NG)EN-DC: 2> if SRB3 is configured and the SCG is not deactivated: 3> submit the UEAssistanceInformation message via SRB3 to lower layers for transmission; 2> else: 3> submit the UEAssistanceInformation message via the E-UTRA MCG embedded in E-UTRA RRC message ULInformationTransferMRDC as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10]. 1> else if the UE is in NR-DC: 2> if the UE assistance configuration that triggered this UE assistance information is associated with the SCG: 3> if SRB3 is configured and the SCG is not deactivated: 4> submit the UEAssistanceInformation message via SRB3 to lower layers for transmission; 3> else: 4> submit the UEAssistanceInformation message via the NR MCG embedded in NR RRC message ULInformationTransferMRDC as specified in 5.7.2a.3; 2> else: 3> submit the UEAssistanceInformation message via SRB1 to lower layers for transmission; 1> else: 2> submit the UEAssistanceInformation message to lower layers for transmission. 1> if the procedure was triggered to provide configured grant assistance information for NR sidelink positioning: 2> submit the UEAssistanceInformation to lower layers via SRB1.

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

5.7.4.3

6.10.5.2 Mapping to resource elements

In subframes configured for CSI reference signal transmission, the reference signal sequence shall be mapped to complex-valued modulation symbols used as reference symbols on antenna port . The mapping depends on the higher-layer parameter CDMType. For the case of CDMType is not configured or is configured to CDM2: where For the case of CDMType equal to CDM4: where and where is given by Table 6.10.5.2-0. Table 6.10.5.2-0: The sequence for CDM4. If neither of the higher-layer parameters NZP-FrequencyDensity and NZP-TransmissionComb are configured, . If the UE is configured with one or more of the parameters NZP-FrequencyDensity and NZP-TransmissionComb, - if either NZP-FrequencyDensity equals 1, - if NZP-FrequencyDensity equals 1/2 and NZP-TransmissionComb equals 0, - if NZP-FrequencyDensity equals 1/2 and NZP-TransmissionComb equals 1, - if NZP-FrequencyDensity equals 1/3 and NZP-TransmissionComb equals 0, - if NZP-FrequencyDensity equals 1/3 and NZP-TransmissionComb equals 1, - if NZP-FrequencyDensity equals 1/3 and NZP-TransmissionComb equals 2, The quantity and the necessary conditions on are given by Tables 6.10.5.2-1 and 6.10.5.2-2 for normal and extended cyclic prefix, respectively. The relation between the antenna port number and the quantity depends on the number of CSI-RS antenna ports: - for CSI reference signals using up to eight antenna ports, - for CSI reference signals using more than eight antenna ports when the higher-layer parameter CDMType equals CDM2 where is the CSI-RS resource number. - for CSI reference signals using more than eight antenna ports when the higher-layer parameter CDMType equals CDM4, antenna port number where for CSI-RS resource number . For the case of CDMType equal to CDM8 and the number of CSI-RS antenna ports equal to 32: where The resource elements for the CDM8 pattern, where , are determined by aggregating pairs of resource elements satisfying from the aggregated CSI-RS configurations, where at most one pair of resource elements is drawn from each of the aggregated CSI-RS configurations. For the case of CDMType equal to CDM8 and the number of CSI-RS antenna ports equal to 32, the aggregated CSI-RS configurations from Table 6.10.5.2-1 for normal cyclic prefix and from Table 6.10.5.2-2 for extended cyclic prefix are restricted to one of , , or . Antenna port number where for CSI-RS resource number . The sequence is given by Table 6.10.5.2-0A, where . Table 6.10.5.2-0A: The sequence for CDM8 with 32 CSI-RS antenna ports. For the case of CDMType equal to CDM8 and the number of CSI-RS antenna ports equal to 24: where For the case of CDMType equal to CDM8 and the number of CSI-RS antenna ports equal to 24, the aggregated CSI-RS configurations from Table 6.10.5.2-1 for normal cyclic prefix are restricted to in that order. Resource elements for CDM8 patterns are determined as follows: - Aggregating resource element quadruplet satisfying from CSI-RS configuration 1 with resource element quadruplet satisfying from CSI-RS configuration 2 - Aggregating resource element quadruplet satisfying from CSI-RS configuration 3 with resource element quadruplet satisfying from CSI-RS configuration 1 - Aggregating resource element quadruplet satisfying from CSI-RS configuration 2 with resource element quadruplet satisfying from CSI-RS configuration 3 Antenna port number where for CSI-RS resource number . The sequence is given by Table 6.10.5.2-0B. The sequence index is determined as follows: - For resource element quadruplet satisfying from CSI-RS configuration 1, resource element quadruplet satisfying from CSI-RS configuration 2, or resource element quadruplet satisfying from CSI-RS configuration 3, . - For resource element quadruplet satisfying from CSI-RS configuration 1, resource element quadruplet satisfying from CSI-RS configuration 2, or resource element quadruplet satisfying from CSI-RS configuration 3, . Table 6.10.5.2-0B: The sequence for CDM8 with 24 CSI-RS antenna ports. Multiple CSI reference signal configurations can be used in a given cell. A UE can be configured with multiple sets of CSI reference signals, - one or more configurations for CSI reporting for which the UE shall assume non-zero transmission power for the CSI-RS, and - zero or more configurations for which the UE shall assume zero transmission power, and - zero or more configurations valid across the system downlink bandwidth as part of the discovery signals for which the UE shall assume non-zero transmission power for the CSI-RS. The CSI-RS configurations for which the UE shall assume non-zero transmission power are provided by higher layers. The CSI-RS configurations for which the UE shall assume zero transmission power in a subframe are given by a bitmap derived according to clause 7.2.7 in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4]. For each bit set to one in the 16-bit bitmap, the UE shall assume zero transmission power for the resource elements corresponding to the four CSI reference signal column in Tables 6.10.5.2-1 and 6.10.5.2-2 for normal and extended cyclic prefix, respectively, except for resource elements that overlap with those for which the UE shall assume non-zero transmission power CSI-RS as configured by higher layers. The most significant bit corresponds to the lowest CSI reference signal configuration index and subsequent bits in the bitmap correspond to configurations with indices in increasing order. CSI reference signals not corresponding to higher layer configured parameters csi-RS-ConfigNZP-ApList or csi-RS-ConfigZP-ApList can only occur in - downlink slots where fulfils the condition in Tables 6.10.5.2-1 and 6.10.5.2-2 for normal and extended cyclic prefix, respectively, and - where the subframe number fulfils the conditions in clause 6.10.5.3. CSI reference signals corresponding to either higher layer configured parameter csi-RS-ConfigNZP-ApList or csi-RS-ConfigZP-ApList can only occur in - downlink slots where fulfils the condition in Tables 6.10.5.2-1 and 6.10.5.2-2 for normal and extended cyclic prefix, respectively. The UE shall assume that CSI reference signals are not transmitted - in the DwPTS for special subframe configuration 0, 5, 9 and 10 for normal cyclic prefix and special subframe configuration 0, 4 and 7 for extended cyclic prefix, in case of frame structure type 2, - in the DwPTS for normal CP for the case of CDMType equal to CDM8 and the number of CSI-RS antenna ports equal to 24, - in subframes where PDSCH/EPDCCH transmission starts in the second slot of a subframe for frame structure type 3, - in subframes where PDSCH/EPDCCH transmission ends prior to the end of a subframe for frame structure type 3, - in an empty subframe where there is no PDSCH or discovery signal transmission for frame structure type 3, - in subframes where transmission of a CSI-RS would collide with SystemInformationBlockType1 messages, - in the primary cell in subframes configured for transmission of paging messages in the primary cell for any UE with the cell-specific paging configuration. For special subframe configuration {1, 2, 6, or 7}, a UE does not expect to be configured with one of CSI-RS configurations {1, 2, 3, 4, 6, 7, 8, 9, 12, 13, 14, 15, 16, 17} in DwPTS for normal CP. The UE shall assume that none of the CSI reference signals corresponding to a CSI reference signal configuration are transmitted in subframes where transmission of any of those CSI reference signals would collide with transmission of synchronization signals or the core part of PBCH. Resource elements used for transmission of CSI reference signals on any of the antenna ports in the set , where , , , , , , , , , , , , , , , or shall not be used for transmission of PDSCH on any antenna port in the same slot if higher layer parameter CDMType is not configured, or is configured to CDM2. Resource elements used for transmission of CSI reference signals on any of the antenna ports in the set , where - , or for CSI reference signals on 12 ports, or - , , or for CSI reference signals on 16 ports, or - , , , or for CSI reference signals on 20 ports, or - , , , , or for CSI reference signals on 24 ports, or - , , , ,, or for CSI reference signals on 28 ports, or - , , , , , , or for CSI reference signals on 32 ports shall not be used for transmission of PDSCH on any antenna port in the same slot if higher layer parameter CDMType is configured to CDM4. Resource elements used for transmission of CSI reference signals on any of the antenna ports in the set , where - , or for CSI reference signals on 24 ports, or - , , or for CSI reference signals on 32 ports shall not be used for transmission of PDSCH on any antenna port in the same slot if higher layer parameter CDMType is configured to CDM8. The mapping for CSI reference signal configuration 0 is illustrated in Figures 6.10.5.2-1 and 6.10.5.2-2. Table 6.10.5.2-1: Mapping from CSI reference signal configuration to for normal cyclic prefix Note: . Configurations 0 – 19 for normal subframes are available for frame structure types 1, 2 and 3. Configurations 20 – 31 and configurations for special subframes are available for frame structure type 2 only. Table 6.10.5.2-2: Mapping from CSI reference signal configuration to for extended cyclic prefix. Note: . Configurations 0 – 15 for normal subframes are available for both frame structure type 1 and type 2. Configurations 16 – 27 and configurations for special subframes are available for frame structure type 2 only. Figure 6.10.5.2-1: Mapping of CSI reference signals (CSI configuration 0, normal cyclic prefix) Figure 6.10.5.2-2: Mapping of CSI reference signals (CSI configuration 0, extended cyclic prefix)

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

9.11.4.12 QoS flow descriptions

The purpose of the QoS flow descriptions information element is to indicate a set of QoS flow descriptions to be used by the UE, where each QoS flow description is a set of parameters as described in subclause 6.2.5.1.1.4. The QoS flow descriptions information element is a type 6 information element with a minimum length of 6 octets. The maximum length for the information element is 65538 octets. The QoS flow descriptions information element is coded as shown in figure 9.11.4.12.1, figure 9.11.4.12.2, figure 9.11.4.12.3, figure 9.11.4.12.4, and table 9.11.4.12.1. Figure 9.11.4.12.1: QoS flow descriptions information element Figure 9.11.4.12.2: QoS flow description Figure 9.11.4.12.3: Parameters list Figure 9.11.4.12.4: Parameter Table 9.11.4.12.1: QoS flow descriptions information element

3GPP TS 24.501

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

CT WG1

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

9.11.4.12

5.4.5.2 UE-initiated NAS transport procedure 5.4.5.2.1 General

The purpose of the UE-initiated NAS transport procedure is to provide a transport of: a) a single 5GSM message as defined in subclause 8.3; b) SMS (see 3GPP TS 24.011[ Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface ] [13]); c) an LPP message; c1) an SLPP message; d) an SOR transparent container; e) a UE policy container; f) a UE parameters update transparent container; g) a location services message; h) a CIoT user data container; i) a Service-level-AA container; j) a UPP-CMI container; or k) multiple of the above types. and: - for a) to e), g) and h), optional associated payload routing information from the UE to the AMF in a 5GMM message; and - for k), the Payload container IE consists a list of payload container entries, where each of the payload container entry contains the payload and optional associated payload routing information (e.g. PDU session information for 5GSM message payload).

3GPP TS 24.501

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

CT WG1

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

5.4.5.2

4.4.3.5 N4 PFD management Procedure

This N4 procedure is used by the SMF to provision or remove all PFD(s) belonging to an Application Identifier in the UPF. PFD sets belonging to different Application Identifiers can be managed with the same PFD management request message. The N4 PFD management procedure is a node level procedure, i.e. independent of any PDU Session. Figure 4.4.3.5-1: PFD management in the UPF 1. The SMF is triggered to provision or remove the PFD set belonging to an Application Identifier in the following cases: When the caching timer expires and there's no active PCC rule that refers to the corresponding application identifier, the SMF informs the UPF to remove the PFD(s) identified by the Application Identifier. When a PCC rule is provided for an Application Identifier corresponding to the PFD(s) that are not already provided to the UPF, the SMF shall provide the PFD(s) to the UPF (if there are no PFD(s) cached, the SMF retrieves them from the NEF (PFDF), as described in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]). When any update of the PFD(s) is received from NEF (PFDF) and there are still active PCC rules in UPF for the Application Identifier. 2. The SMF sends a PFD management request to the UPF to provision/remove the PFD(s) corresponding to the Application Identifier(s). 3. The UPF updates the PFD(s) according to the request and acknowledges by responding with a PFD management response message.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.4.3.5

10.5.5.24 Inter RAT information container

The purpose of the Inter RAT information container information element is to supply the network with Iu mode related information that needs to be transferred at PS inter-system handover to Iu mode (see 3GPP TS 43.129[ None ] [113]). The Inter RAT information container information element is coded as shown in figure 10.5.150/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The Inter RAT information container information element is a type 4 information element with a minimum length of 3 octets and a maximum length of 250 octets. The Inter RAT information container contains: - predefined configuration status information; - mobile station security information to be used after handover to Iu mode, which includes the START-PS value that is stored by the MS at handover from Iu mode to A/Gb mode (see 3GPP TS 33.102[ 3G security; Security architecture ] [5a]); and/or - the specific Iu mode radio capabilities of the mobile station, i.e. UE RAC (see 3GPP TS 25.331[ None ] [23c]). Figure 10.5.150/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Inter RAT information container information element The value part of the Inter RAT information container information element is the INTER RAT HANDOVER INFO as defined in 3GPP TS 25.331[ None ] [23c]. If this field includes padding bits, they are defined in 3GPP TS 25.331[ None ] [23c].

3GPP TS 24.008

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

CT WG1

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

10.5.5.24

– DLInformationTransferMRDC

The DLInformationTransferMRDC message is used for the downlink transfer of RRC messages during fast MCG link recovery. Signalling radio bearer: SRB3 RLC-SAP: AM Logical channel: DCCH Direction: Network to UE DLInformationTransferMRDC message -- ASN1START -- TAG-DLINFORMATIONTRANSFERMRDC-START DLInformationTransferMRDC-r16 ::= SEQUENCE { criticalExtensions CHOICE { c1 CHOICE { dlInformationTransferMRDC-r16 DLInformationTransferMRDC-r16-IEs, spare3 NULL, spare2 NULL, spare1 NULL }, criticalExtensionsFuture SEQUENCE {} } } DLInformationTransferMRDC-r16-IEs::= SEQUENCE { dl-DCCH-MessageNR-r16 OCTET STRING OPTIONAL, -- Need N dl-DCCH-MessageEUTRA-r16 OCTET STRING OPTIONAL, -- Need N lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } -- TAG-DLINFORMATIONTRANSFERMRDC-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

4.8.2.3 Connection Resume in CM-IDLE with Suspend procedure

For the UE supporting User Plane CIoT 5GS Optimisation, the Connection Resume procedure is used by the UE to perform RRC_IDLE with Suspend to RRC_CONNECTED state transition. Triggers for the UE to initiate this procedure are defined in clause 5.31.18 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. Figure 4.8.2.3-1: Connection Resume in CM-IDLE with Suspend 1. UE to NG-RAN: RRC message (Resume ID). The UE initiates the transition from CM-IDLE and RRC_IDLE state with Suspend to CM-CONNECTED and RRC_CONNECTED state, see TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [46]. The UE provides its Resume ID needed by the NG-RAN to access the UE's stored Context. 2. [Conditional] NG-RAN performs UE Context Retrieval. UE Context Retrieval may be performed when the UE Context associated with the UE attempting to resume its connection is not locally available at the accessed NG-RAN. The UE Context Retrieval procedure via NG-RAN is specified in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [9]. 3. NG-RAN and UE continues the resume procedure and access stratum configuration synchronization is performed between the UE and the network. UE enters CM-CONNECTED and RRC_CONNECTED. 4. NG-RAN to AMF: a) If the NG-RAN is the same as the NG-RAN when UE is suspended, the NG-RAN sends N2 Resume Request to AMF including Resume cause and N2 SM information which indicates the PDU sessions successfully resumed and PDU sessions failed or partially failed to resume the user plane resource. b) If the NG-RAN is different from the NG-RAN when UE is suspended and the new NG-RAN is able to retrieve the UE Context from the old NG-RAN, the new NG-RAN node initiates N2 Path Switch Request towards AMF, i.e. Steps 1b of clause 4.9.1.2.2. 5. AMF to SMF: For each of the PDU Sessions indicated in step 4, the AMF invokes Nsmf_PDUSession_UpdateSMContext Request (PDU Session ID, Cause, Operation type, User Location Information, Age of Location Information, N2 SM Information). The Operation Type is set to "UP Resume" to indicate resume of user plane resources for the PDU Session. For PDU Session(s) to be switched to the new NG-RAN, upon receipt of the Nsmf_PDUSession_UpdateSMContext request, the SMF determines whether the existing UPF can continue to serve the UE. If the existing UPF cannot continue to serve the UE, steps 3 to 7 of clause 4.9.1.2.3 or clause 4.9.1.2.4 are performed depending on whether the existing UPF is a PDU Session Anchor and flow continues in step 7. Otherwise, step 6 is performed if the existing UPF can continue to serve the PDU Session. If the RRC connection is resumed and the UE is accessing via the NB-IoT RAT with the RRC resume cause set to "MO exception data" the AMF updates all (H-)SMFs. If AMF indicates "MO exception data" then it includes the MO Exception Data Counter. The AMF maintains the MO Exception Data Counter for Small Data Rate Control purposes as described in clause 5.31.14.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. Each (H-)SMF should be updated for every RRC Connection which is triggered for "MO exception data". In the home-routed roaming case, if Small Data Rate Control applies, the V-SMF waits for H-SMF response before proceeding with the N3 establishment. 6. SMF to UPF: N4 Session Modification Request (AN Tunnel Info to be resumed, Buffering on/off). The SMF initiates an N4 Session Modification procedure indicating the resume of AN tunnel. Buffering on/off indicates whether the UPF shall buffer incoming DL PDU or not. If step 4a) is performed, the AN tunnel info is the one maintained by the SMF during Connection Suspend procedure, step 3 of clause 4.8.1.2. If step 4b) is performed, the AN tunnel info is part of the N2 SM information received by SMF in step 5. The UPF sends N4 Session Modification Response to acknowledge the SMF request. 7. SMF to AMF: The SMF sends Nsmf_PDUSession_UpdateSMContext response to the AMF. If new CN tunnel information is allocated for the PDU session, i.e. in the case of new AN tunnel is received in step 6, the SMF includes the new CN tunnel information as part of the N2 SM information. If the resume for PDU session is unsuccessful, the SMF shall include the resume failure as part of the N2 SM information. 8. AMF to NG-RAN: After response for each PDU session in step 7, the AMF sends N2 Resume Response to NG-RAN and indicates success, including N2 SM information for PDU session received in step 7, if at least one PDU session is resumed successfully. If none of the PDU sessions is resumed successfully, AMF indicates failure to NG-RAN. The AMF sends N2 Path Switch Acknowledge with PDU session resume information, if Path Switch Request is received in step 4. The AMF may provide Extended Connected Time value to the NG-RAN. If the NG-RAN receives the Extended Connected Time value, the NG-RAN may take this information into account when determining user inactivity. 9. [Conditional] NG-RAN to UE: RRC message. The NG-RAN may reconfigure the RRC connection based on resume result received from AMF. 10. If the AMF has paged the UE to trigger the Connection Resume procedure, the AMF shall initiate the UE configuration update procedure as defined in clause 4.2.4.2 to assign a new 5G-GUTI.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.8.2.3

9.9.2.6 NAS security parameters from E-UTRA

The purpose of the NAS security parameters from E-UTRA information element is to provide the UE with information that enables the UE to create a mapped UMTS security context. The NAS security parameters from E-UTRA information element is coded as shown in figure 9.9.2.6.1 and table 9.9.2.6.1. The NAS security parameters from E-UTRA is a type 3 information element with a length of 2 octets. The value part of the NAS security parameters from E-UTRA information element is included in specific information elements within some RRC messages sent to the UE; see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]. For these cases the coding of the information element identifier and length information is defined in 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]. Figure 9.9.2.6.1: NAS security parameters from E-UTRA information element Table 9.9.2.6.1: NAS security parameters from E-UTRA information element

3GPP TS 24.301

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

CT WG1

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

9.9.2.6

6.11.1.2 Mapping to resource elements

The mapping of the sequence to resource elements depends on the frame structure. The UE shall not assume that the primary synchronization signal is transmitted on the same antenna port as any of the downlink reference signals. The UE shall not assume that any transmission instance of the primary synchronization signal is transmitted on the same antenna port, or ports, used for any other transmission instance of the primary synchronization signal. The sequence shall be mapped to the resource elements according to For frame structure type 1, the primary synchronization signal shall be mapped to the last OFDM symbol in slots 0 and 10. For frame structure type 2, the primary synchronization signal shall be mapped to the third OFDM symbol in subframes 1 and 6. Resource elements in the OFDM symbols used for transmission of the primary synchronization signal where are reserved and not used for transmission of the primary synchronization signal. For frame structure type 3, the primary synchronization signal shall be mapped according to frame structure type 1 with the following exceptions: - the primary synchronization signal shall be transmitted only if the corresponding subframe is non-empty and at least 12 OFDM symbols are transmitted, - a primary synchronization signal being part of a discovery signal shall be transmitted in the last OFDM symbol of the first slot of a discovery signal occasion. For an MBMS-dedicated cell, the primary synchronization signal shall be mapped according to frame structure type 1 with following exception: - the primary synchronization signal shall be transmitted in slot 0 in subframes fulfilling only,

3GPP TS 36.211

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

RAN1

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

6.11.1.2

J.6 Handling of special situations

Situations may occur that cause unsynchronized state information in the UE, MME and SGSN. Such situations are: - Modification of any EPS bearer context or PDP context which was activated before the ISR is activated in the UE; - At the time when the UE moves from E-UTRAN to GERAN/UTRAN or moves from GERAN/UTRAN to E-UTRAN, if any EPS bearer context or PDP context activated after the ISR was activated in the UE exists; - Missing periodic TA or RA updates, e.g. because the coverage of a RAT is lost or the RAT is no more selected by the UE (this may result also in implicit detach by SGSN or MME); - CN node change resulting in context transfer between the same type of CN nodes (SGSN to SGSN or MME to MME); - Serving GW change (both with and without UE mobility); - Change of the UE specific DRX parameters; - Change of the UE Core Network Capabilities; - E-UTRAN selection by a UTRAN-connected UE (e.g. when in URA_PCH to release Iu on UTRAN side); E-UTRAN selection from GERAN READY state; - GERAN selection by an E-UTRAN-connected UE via Cell Change Order that is not for CS fallback. There are no ISR specific procedures to handle such situations to avoid additional complexity and error cases. All special situations that cause context in the UE, MME and SGSN to become asynchronous are handled by ISR deactivation. The normal RAU/TAU procedures synchronize contexts in MME and SGSN and activate ISR again when wanted by the network. Some specific handling is defined to enable combined MME/SGSN. For this the UE signals at UTRAN RRC level always an Intra Domain NAS Node Selector (IDNNS) derived from the ID signalled as P-TMSI (also when mapped from GUTI). At E-UTRAN RRC level the UE indicates the GUMMEI derived from the GUTI that is signalled in the TAU Request message (also when derived from P-TMSI). This handling is performed by the UE independent from the network configuration. It is not visible to the UE whether MME and SGSN are combined. Given the IP-based architecture of EPS and the IP-based applications such establishment and deactivation of the EPS bearer or PDP context can happen frequently before the UE changes the RAT e.g. a UE asking for delivery of an SMS (over IP) or starting a VoIP over IMS, an entirely new EPS bearer or PDP context may be established for that purpose. Then, after the application/service is finished, the newly established EPS bearer or PDP context gets deactivated. In such particular situation the deactivation of the ISR at the UE and hence performing a RAU or TAU update when the UE changes the RAT is not needed. Preventing the UE from deactivating the ISR in this case ensures an efficient usage of the UE's battery power and reduces the unnecessary signalling load that is seen as the key objective to be achieved by introducing the ISR feature. Thus, UE only locally deactivates ISR when bearer existed at the time of ISR is activated, or when UE changes RAT with bearers which are created after ISR is activated.

3GPP TS 23.401

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

SA WG2

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

J.6

19.4.2.9.5 Replacement field used in DNS-based Discovery of regulatory requirements

If 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 NAPTR record(s) associated to the Visited Country FQDN shall be provisioned with the replacement field containing the identity of the PLMN(s) in the visited country which may be used for ePDG selection. The replacement field shall take the form of an Operator Identifier based ePDG FQDN as specified in clause 19.4.2.9.2. For countries with multiple MCC, the NAPTR records returned by the DNS may contain a different MCC than the MCC indicated in the Visited Country FQDN. As an example, the NAPTR records associated to the Visited Country FQDN for MCC 345, and for MNC 012, 013 and 014, are provisioned in the DNS as: epdg.epc.mcc345.visited-country.pub.3gppnetwork.org ; IN NAPTR order pref. flag service regexp replacement IN NAPTR 100 999 "" "" epdg.epc.mnc012.mcc345.pub.3gppnetwork.org IN NAPTR 100 999 "" "" epdg.epc.mnc013.mcc345.pub.3gppnetwork.org IN NAPTR 100 999 "" "" epdg.epc.mnc014.mcc345.pub.3gppnetwork.org

3GPP TS 23.003

Numbering, addressing and identification

CT WG4

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

19.4.2.9.5

5.6 Channel bandwidth

Requirements in present document are specified for the channel bandwidths listed in Table 5.6-1. Table 5.6-1: Transmission bandwidth configuration NRB in E-UTRA channel bandwidths Figure 5.6-1 shows the relation between the Channel bandwidth (BWChannel) and the Transmission bandwidth configuration (NRB). The channel edges are defined as the lowest and highest frequencies of the carrier separated by the channel bandwidth, i.e. at FC +/- BWChannel /2. Figure 5.6-1: Definition of channel bandwidth and transmission bandwidth configuration for one E-UTRA carrier

3GPP TS 36.101

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

RAN4

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

5.6

4.15.3.2.9 Information flow for Availability after DDN Failure with UPF buffering

The procedure is used if the SMF requests the UPF to buffer packets. The procedure describes a mechanism for the Application Function to subscribe to notifications about availability after DDN failure. Cancelling is done by sending Nnef_EventExposure_Unsubscribe request identifying the subscription to cancel with Subscription Correlation ID. Steps 2 to 7 are not applicable in the cancellation case. Figure 4.15.3.2.9-1: Information flow for availability after DDN Failure event with UPF buffering 1. AF interacts with NEF to subscribe availability after DDN failure event in AMF/SMF as described in steps 0-8 of clause 4.15.3.2.7. In case of subscription cancelling from AMF and SMF having interacted with the PCF during event subscription, the SMF reports to the PCF for the unsubscribe of DDN failure event. The PCF updates or removes the PCC rule and this triggers the SMF to update or remove the corresponding PDR and FAR in the UPF. In the case of PDU Session with I-SMF or home-routed PDU Session, the AMF unsubscribes the DDN failure event towards I/V-SMF. In case of home-routed PDU Session, the V-SMF updates the N4 information (deactivating the notifications) in the V-UPF. In case of PDU Session with I-SMF, the I-SMF may request N4 information (deactivating the notifications) from the SMF and provides the Traffic Descriptor to the SMF. The SMF provides updated N4 information (deactivating the notifications) to the I-SMF which in turn updates the I-UPF. 2. The SMF checks whether an installed PDR for the Traffic Descriptor exists and if so, requests the UPF to report when the first downlink packet is received and when it is discarded in the UPF. If PCC is not used and there is no installed PDR with the exact same traffic descriptor, the SMF copies the installed PDR that would have previously matched the incoming traffic described by the traffic descriptor, but provides that traffic descriptor, a higher priority and requests the UPF to report when the first downlink packet is received and when it is discarded in the UPF. If PCC is used and if the "DDN Failure event subscription with Traffic Descriptor" PCRT is set as defined in clause 6.1.3.5 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20], the SMF interacts with the PCF and forwards the traffic descriptor before contacting the UPF; the PCF then updates an existing PCC rule or provides a new PCC rule taking into consideration the traffic descriptor for the subscribed DDN failure event. NOTE 1: If a new PCC rule is provided by the PCF for the DDN failure event detection, the PCF populates the PCC rules as defined in clause 6.1.3.5 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. In the case of PDU Session with I-SMF or home-routed PDU Session, the AMF subscribes the DDN failure event towards the I/V-SMF. In the case of home-routed PDU Session, the V-SMF generates the N4 information (activating the notifications) for the V-UPF based on local configuration. In the case of PDU Session with I-SMF, the I-SMF may request N4 information (activating the notifications) from the SMF based on local configuration and provides the Traffic Descriptor to the SMF. The SMF provides updated N4 information (activating the notifications) to the I-SMF which in turn updates the I-UPF. For home-routed PDU Session or PDU Session with I-SMF, steps 3-4 below are performed by V-SMF/V-UPF or I-SMF/I-UPF. 3-4. When the first downlink packet matching the traffic descriptor is received in the UPF, if in step 2 the SMF indicated drop notification to the UPF, the UPF notifies the SMF and the SMF reports the DDN Failure status with NEF Correlation ID, by means of Nsmf_PDUSession_SMContextStatusNotify message, to the AMF indicated as notification endpoint. When the first downlink packet matching the traffic descriptor is received in the UPF, if in step 2 the SMF indicated buffer notification to the UPF, the UPF notifies the SMF and the SMF may initiate Network Triggered Service Request as specified in clause 4.2.3.3. If the AMF responds Namf_Communication_N1N2MessageTransfer response with failure (e.g. due to UE not reachable, or paging no response), in addition to what is specified in clause 4.2.3.3, the SMF reports DDN Failure status with NEF Correlation ID, by means of Nsmf_PDUSession_SMContextStatusNotify message, to the AMF indicated as notification endpoint. When the AMF receives DDN Failure status from the SMF, the AMF shall set a Notify-on-available-after-DDN-failure flag corresponding to the Notification Correlation Id and the identifier of the UE if available. 5-6. [Conditional] The AMF detects the UE is reachable and sends the event report(s) based on the Notify-on-available-after-DDN-failure flag, by means of Namf_EventExposure_Notify message(s), only to the NEF(s) indicated as notification endpoint(s) identified via the corresponding subscription in step 1. In this way, only the AF(s) for which DL traffic transmission failed are notified. If the AMF received Idle Status Indication request in step 1 and the AMF supports Idle Status Indication, the AMF includes also the Idle Status Indication in Namf_EventExposure_Notify message. 7. The NEF sends Nnef_EventExposure_Notify message with the "Availability after DDN Failure" event to AF.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.15.3.2.9

A.29 Monitor of user data transmission over Xw interface for non-collocated LWA

In the non-collocated LWA scenario, the Xw user plane interface (Xw-U) is defined between eNB and WT. The Xw-U interface supports flow control based on feedback from WT. The Xw-U interface is used to deliver LWA PDUs (user data) between eNB and WT for a UE. The user data For LWA, the S1-U terminates in the eNB and, if Xw-U user data bearers are associated with E-RABs for which the LWA bearer option is configured, the user plane data is transferred from eNB to WT using the Xw-U interface. The E-UTRAN capacity needs to be determined with the user data transmitted over Xw interface into account, including the volume of the user data transmitted or received over Xw interface for non-collocated LWA, the number of UEs associated with WLAN and the number of UEs actually with user data transferred over Xw interface.

3GPP TS 32.425

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

SA WG5

3GPP Series : 32 , OAM&P and Charging

A.29

5.14.2.3 Relaying

The MME performs relaying between GTPv2 messages as described in TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [43]. The MME performs relaying between S1 and S10 messages as described in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36], TS 23.501[ System architecture for the 5G System (5GS) ] [83] and TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [43]. The Target eNodeB performs relaying between S1 and X2 message as described in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36] and TS 36.423[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 Application Protocol (X2AP) ] [76].

3GPP TS 23.401

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

SA WG2

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

5.14.2.3

5.7.12.3 Actions related to transmission of IABOtherInformation message

The IAB-MT shall set the contents of IABOtherInformation message as follows: 1> if the procedure is used to request IP addresses: 2> if IPv4 addresses are requested: 3> set the iab-IPv4-AddressNumReq to the number of IPv4 addresses requested per specific usage; 2> if IPv6 addresses or IPv6 address prefixes are requested: 3> if IPv6 addresses are requested: 4> set the iab-IPv6-AddressNumReq to the number of IPv6 addresses requested per specific usage; 3> else if IPv6 address prefixes are requested: 4> set the iab-IPv6-AddressPrefixReq to true per specific usage; 1> if the procedure is used to report IP addresses: 2> if IPv4 addresses are reported: 3> include iPv4-Address in iab-IPv4-AddressReport, and for each IP address included: 4> if IPv4 addresses are used for F1-C traffic: 5> include these addresses in f1-C-Traffic-IP-Address. 4> if IPv4 addresses are used for F1-U traffic: 5> include these addresses in f1-U-Traffic-IP-Address. 4> if IPv4 address are used for non-F1 traffic: 5> include these addresses in non-f1-Traffic-IP-Address. 4> if IPv4 addresses are used for all traffic: 5> include these addresses in all-Traffic-IAB-IP-Address. 2> if IPv6 addresses or IPv6 address prefixes are reported: 3> if IPv6 addresses are reported: 4> include iPv6-Address in iab-IPv6-AddressReport, and for each IP address included; 5> if IPv6 addresses are used for F1-C traffic: 6> include these addresses in f1-C-Traffic-IP-Address. 5> if IPv6 addresses are used for F1-U traffic: 6> include these addresses in f1-U-Traffic-IP-Address. 5> if IPv6 addresses are used for non-F1 traffic: 6> include these addresses in non-f1-Traffic-IP-Address. 5> if IPv6 addresses are used for all traffic: 6> include these addresses in all-Traffic-IAB-IP-Address. 3> else if IPv6 address prefixes are reported: 4> include these iPv6-Prefix in iab-IPv6-PrefixReport, and for each IP address prefix included; 5> if this IPv6 address prefix is used for F1-C traffic: 6> include this prefix in f1-C-Traffic-IP-Address. 5> if this IPv6 address prefix is used for F1-U traffic: 6> include this prefix in f1-U-Traffic-IP-Address. 5> if this IPv6 address prefix is used for non-F1 traffic: 6> include this prefix in non-f1-Traffic-IP-Address. 5> if this IPv6 address prefix is used for all traffic: 6> include this prefix in all-Traffic-IAB-IP-Address. 1> if the IAB-MT is in (NG)EN-DC, or 1> if the IAB-MT is in NR-DC and the IAB Other Information procedure is towards the IAB-donor-CU in the SN: 2> if SRB3 is configured: 3> submit the IABOtherInformation message via SRB3 to lower layers for transmission; 2> else if the IAB-MT is in (NG)EN-DC: 3> submit the IABOtherInformation message via the E-UTRA MCG embedded in E-UTRA RRC message ULInformationTransferMRDC as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10]; 2> else: 3> submit the IABOtherInformation message via the NR MCG embedded in NR RRC message ULInformationTransferMRDC as specified in clause 5.7.2a.3; 1> else: 2> submit the IABOtherInformation message to lower layers for transmission.

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

5.7.12.3

5.2.1.1 Call initiation

The "call initiated" state is supervised by timer T303.For normal MO calls, this timer will have already been started after entering the "MM connection pending" state. For network-initiated MO calls this timer will be started in the recall present state as defined in subclause 5.2.3.4 When the call control entity of the mobile station is in the "call initiated" state and if it receives: i) a CALL PROCEEDING message, it shall proceed as described in subclause 5.2.1.3; ii) an ALERTING message, it shall proceed as described in subclause 5.2.1.5; iii) a CONNECT message, it shall proceed as described in subclause 5.2.1.6; iv) a RELEASE COMPLETE message it shall proceed as described in subclause 5.2.1.2. Abnormal case: - If timer T303 elapses in the "call initiated" state before any of the CALL PROCEEDING, ALERTING, CONNECT or RELEASE COMPLETE messages has been received, the clearing procedure described in subclause 5.4 is performed.

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

9.11.4.15 SM PDU DN request container

The purpose of the SM PDU DN request container information element is to carry a DN-specific identity of the UE in the network access identifier (NAI) format. The SM PDU DN request container information element is coded as shown in figure 9.11.4.15.1 and table 9.11.4.15.1. The SM PDU DN request container is a type 4 information element with minimal length of 3 octets and maximum length of 255 octets. Figure 9.11.4.15.1: SM PDU DN request container information element Table 9.11.4.15.1: SM PDU DN request container information element

3GPP TS 24.501

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

CT WG1

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

9.11.4.15

6.2.6 NRF 6.2.6.1 General

The Network Repository Function (NRF) supports the following functionality: - Supports service discovery of NRF services and their endpoint addresses by the NRF bootstrapping service. - Supports service discovery function. Receive NF Discovery Request from NF instance or SCP, and provides the information of the discovered NF instances (be discovered) to the NF instance or SCP. - Supports P-CSCF discovery (specialized case of AF discovery by SMF). - Maintains the NF profile of available NF instances and their supported services. - Maintains SCP profile of available SCP instances. - Supports SCP discovery by SCP instances. - Notifies about newly registered/updated/ deregistered NF and SCP instances along with its potential NF services to the subscribed NF service consumer or SCP. - Maintains the health status of NFs and SCP. In the context of Network Slicing, based on network implementation, multiple NRFs can be deployed at different levels (see clause 5.15.5): - PLMN level (the NRF is configured with information for the whole PLMN), - shared-slice level (the NRF is configured with information belonging to a set of Network Slices), - slice-specific level (the NRF is configured with information belonging to an S-NSSAI). In the context of roaming, multiple NRFs may be deployed in the different networks (see clause 4.2.4): - the NRF(s) in the Visited PLMN (known as the vNRF) configured with information for the visited PLMN. - the NRF(s) in the Home PLMN (known as the hNRF) configured with information for the home PLMN, referenced by the vNRF via the N27 interface.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

6.2.6

8.1.2.9 Applicability of SDR requirements for CA and LAA

For UE supporting both CA and LAA, UE selects the corresponding SDR tests between CA and LAA as per the following applicab1ility rules: - 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 LAA and non-LAA CA configurations with the same largest aggregated bandwidth, select non-LAA CA configuration.

3GPP TS 36.101

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

RAN4

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

8.1.2.9

7.2 Measurements

If the measurement is configured to the UE in preparation for the Secondary Node Addition procedure described in clause 10.2, the Master node should configure the measurement to the UE. In case of the intra-secondary node mobility described in clause 10.3, the SN should configure the measurement to the UE in coordination with the MN, if required. The Secondary Node Change procedure described in clause 10.5 can be triggered by both the MN (only for inter-frequency secondary node change) and the SN. For secondary node changes triggered by the SN, the RRM measurement configuration is maintained by the SN which also processes the measurement reporting, without providing the measurement results to the MN. Measurements can be configured independently by the MN and by the SN (intra-RAT measurements on serving and non-serving frequencies). The MN indicates the maximum number of frequency layers and measurement identities of intra-frequency and inter-frequency measurement that can be used in the SN to ensure that UE capabilities are not exceeded. In MR-DC, to assist MN to identify the measurement type, the SN indicates to the MN the list of SCG serving frequencies. In NR-DC, to assist SN to identify the measurement type, the MN indicates also to SN the list of MCG serving frequencies. The SN can also request the MN for new maximum values of the number of measurement identities that it can configure, and it is up to the MN whether to accommodate the SN request, based on the capability coordination principles as described in 7.3. If the SN receives from the MN a new value for the maximum number of measurement identities, is SN responsibility to ensure that its configured measurement identities to comply with the new limit. If MN and SN both configure measurements on the same carrier frequency then the configurations need to be consistent (if the network wants to ensure these are considered as a single measurement layer). Each node (MN and SN) can configure independently a threshold for the SpCell quality. In (NG)EN-DC scenario, when the PCell quality is above the threshold configured by the MN, the UE is still required to perform inter-RAT measurements configured by the MN on the SN RAT (while it's not required to perform intra-RAT measurements); when the PSCell quality is above the threshold configured by the SN, the UE is not required to perform measurements configured by the SN. In NR-DC or NE-DC scenario, when the PCell quality is above the threshold configured by the MN, the UE is not required to perform measurements configured by the MN; when the PSCell quality is above the threshold configured by the SN, the UE is not required to perform measurements configured by the SN. NOTE: The SN cannot renegotiate the number of frequency layers allocated by the MN in this version of the protocol. In MR-DC, both the MN and the SN can configure CGI reporting. The MN can configure CGI reporting for intra-RAT and inter-RAT cells but the SN can only configure CGI reporting of intra-RAT cells. At any point in time, the UE can be configured with at most one CGI reporting configuration. For CGI reporting coordination, the SN sends the CGI measurement request and the embedded CGI reporting configuration to the MN. Optionally, the SN sends the unknown cell information to the MN. If there is no ongoing CGI reporting measurement on UE side, the MN forwards the SN CGI measurement configuration to UE. Otherwise the MN rejects the request by sending X2/Xn reject message. In case the SN indicates the unknown cell information, and the CGI information of the requested cell is already available in the MN, the MN can also reject the request, and sends the CGI information of the requested cell to the SN. The SN cannot configure the CGI measurement using the SRB3. Both MN-configured and SN-configured RRM measurements are supported while the SCG is deactivated. The PSCell measurement cycle when in deactivated SCG state is configured by RRC. When SRB3 is not configured or the SCG is deactivated, reports for measurements configured by the SN are sent on SRB1. When SRB3 is configured and SCG transmission of radio bearers is not suspended and the SCG is not deactivated, reports for measurements configured by the SN are sent on SRB3. Measurement results related to the target SN can be provided by MN to target SN at MN initiated SN change procedure. Measurement results of target SN can be forwarded from source SN to target SN via MN at SN initiated SN change procedure. Measurement results related to the target SN can be provided by source MN to target MN at Inter-MN handover with/without SN change procedure. Measurement results according to measurement configuration from the MN are encoded according to SN RRC when they are provided by MN to SN in SgNB Addition Request message / SN Addition Request message. During SN initiated SN change procedure, measurement results according to measurement configuration from SN are encoded according to SN RRC when they are provided by MN to SN in SgNB Addition Request message / SN Addition Request message. Per-UE or per-FR measurement gaps can be configured, depending on UE capability to support independent FR measurement and network preference. Per-UE gap applies to both FR1 (E-UTRA, UTRA-FDD and NR) and FR2 (NR) frequencies. For per-FR gap, two independent gap patterns (i.e. FR1 gap and FR2 gap) are configured for FR1 and FR2 respectively. The UE may also be configured with a per-UE gap sharing configuration (applying to per-UE gap) or with two separate gap sharing configurations (applying to FR1 and FR2 measurement gaps respectively) [8]. A measurement gap configuration is always provided: - In EN-DC, NGEN-DC and NE-DC, for UEs configured with E-UTRA inter-frequency measurements as described in table 9.1.2-2 in TS 38.133[ NR; Requirements for support of radio resource management ] [8]; - In EN-DC and NGEN-DC, for UEs configured with UTRAN and GERAN measurements as described in table 9.1.2-2 in TS 38.133[ NR; Requirements for support of radio resource management ] [8]; - In NR-DC, for UEs configured with E-UTRAN measurements as described in table 9.1.2-3 in TS 38.133[ NR; Requirements for support of radio resource management ] [8]; - In NR-DC, NE-DC, for UEs configured with UTRAN measurements as described in table 9.4.6.3-1 and 9.4.6.3-2 in TS 38.133[ NR; Requirements for support of radio resource management ] [8]; - In MR-DC, for UEs that support either per-UE or per-FR gaps, when the conditions to measure SSB based inter-frequency measurement or SSB based intra-frequency measurement as described in clause 9.2.4 in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [3] are met; If per-UE gap is used, the MN decides the gap pattern and the related gap sharing configuration. If per-FR gap is used, in EN-DC and NGEN-DC, the MN decides the FR1 gap pattern and the related gap sharing configuration for FR1, while the SN decides the FR2 gap pattern and the related gap sharing configuration for FR2; in NE-DC and NR-DC, the MN decides both the FR1 and FR2 gap patterns and the related gap sharing configurations. In EN-DC and NGEN-DC, the measurement gap configuration from the MN to the UE indicates if the configuration from the MN is a per-UE gap or an FR1 gap configuration. The MN also indicates the configured per-UE or FR1 measurement gap pattern and the gap purpose (per-UE or per-FR1) to the SN. Measurement gap configuration assistance information can be exchanged between the MN and the SN. For the case of per-UE gap, the SN indicates to the MN the list of SN configured frequencies in FR1 and FR2 measured by the UE. For the per-FR gap case, the SN indicates to the MN the list of SN configured frequencies in FR1 measured by the UE and the MN indicates to the SN the list of MN configured frequencies in FR2 measured by the UE. In NE-DC, the MN indicates the configured per-UE or FR1 measurement gap pattern to the SN. The SN can provide a gap request to the MN, without indicating any list of frequencies. In NR-DC, the MN indicates the configured per-UE, FR1 or FR2 measurement gap pattern and the gap purpose to the SN. The SN can indicate to the MN the list of SN configured frequencies in FR1 and FR2 measured by the UE. In (NG)EN-DC and NR-DC, SMTC can be used for PSCell addition/PSCell change to assist the UE in finding the SSB in the target PSCell. In case the SMTC of the target PSCell is provided by both MN and SN it is up to UE implementation which one to use. CLI measurements can be configured for NR cells in all MR-DC options. In EN-DC and NGEN-DC, only the SN can configure CLI measurements. In NE-DC, only the MN can configure CLI measurements. In NR-DC, both the MN and the SN can configure CLI measurements, and the MN informs the SN about the maximum number of CLI measurement resources that can be configured by the SN to ensure that the total number of CLI measurement resources does not exceed the UE capabilities. For MUSIM operation, when the UE is configured to operate in NR-DC in Network A (as described in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [3]), the MN indicates the per-UE MUSIM gap configuration to the SN.

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

7.2

8.2.7.5 Allowed NSSAI

This IE shall be included: a) if: 1) one or more S-NSSAIs in the requested NSSAI of the REGISTRATION REQUEST message are allowed by the AMF for a network not supporting NSSAA; 2) one or more S-NSSAIs in the requested NSSAI of the REGISTRATION REQUEST message are not subject to network slice-specific authentication and authorization and are allowed by the AMF; or 3) the network slice-specific authentication and authorization has been successfully performed for one or more S-NSSAIs in the requested NSSAI of the REGISTRATION REQUEST message; or b) if the initial registration request is not for onboarding services in SNPN or the UE is not registered for onboarding services in SNPN, the requested NSSAI was not included in the REGISTRATION REQUEST message or none of the requested NSSAI are allowed; and 1) the network does not support NSSAA; or 2) the network has one or more default S-NSSAIs which are not subject to network slice-specific 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

8.2.7.5

5.35A.7 Control of UE access to MBSR

CAG Identifier is used to control the access of UE via MBSR (i.e. mobile IAB-node) and existing CAG mechanism defined in clause 5.30.3 can be used for managing UE's access to MBSR, with the following additional considerations: - When the MBSR is allowed to operate as an IAB node for a PLMN, the MBSR is configured, either during the communication with the serving PLMN OAM or (pre-)configuration mechanism, with a CAG identifier which is unique within the scope of this PLMN. If the MBSR is (pre-)configured with the PLMN list in which the MBSR is allowed to operate as MBSR, the corresponding CAG Identifier per PLMN is also configured in the MBSR. NOTE 1: The CAG for MBSR is supported as part of the PNI-NPN concept described in clause 5.30.3. - NG-RAN and 5GC support the UE access control based on the CAG identifier associated with the MBSR cell and the allowed CAG identifiers for the UE that supports CAG functionality. - For the UE that does not support CAG functionality, NG-RAN and 5GC are allowed to use not only CAG mechanism but also the other existing mechanism e.g. forbidden Tracking Area, to manage its access to MBSR. - Time duration restriction may be provided together with the CAG Identifier(s) for the MBSR(s) that the UE can access. The enhanced Allowed CAG list will be provided to UE and AMF for enforcement, to make sure that UE not accessing the MBSR cell outside of the time duration. For example, if the time when a certain CAG is allowed for a UE is up, the CAG for the UE is revoked from the network. NOTE 2: Control of the MBSR access to the serving network is based on normal mobility restriction management based on subscription data form MBSR (i.e. IAB-UE).

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.35A.7

6.3 PDCP Sublayer

In EN-DC, CA duplication (see [3]) can be applied in the MN and in the SN, but MCG bearer CA duplication can be configured only in combination with E-UTRAN PDCP and MCG bearer CA duplication can be configured only if DC duplication is not configured for any split bearer. In NGEN-DC, CA duplication can only be configured for SCG bearer. In NE-DC, CA duplication can only be configured for MCG bearer. In NR-DC, CA duplication can be configured for both MCG and SCG bearers, and can be configured together with DC duplication. In MR-DC, RoHC and EHC (as described in TS 36.323[ Evolved Universal Terrestrial Radio Access (E-UTRA); Packet Data Convergence Protocol (PDCP) specification ] [15] and TS 38.323[ NR; Packet Data Convergence Protocol (PDCP) specification ] [16]) can be configured for all the bearer types. In MR-DC with 5GC, UDC (as described in TS 38.323[ NR; Packet Data Convergence Protocol (PDCP) specification ] [16]) can be configured for all the bearer types.

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

6.3

5.2.6.30.2 Nnef_PDTQPolicyNegotiation_Create service operation

Service operation name: Nnef_PDTQPolicyNegotiation_Create Description: The consumer requests to create a PDTQ policy. Inputs, Required: ASP Identifier, Number of UEs, list of Desired time windows, QoS reference or individual QoS parameters as described in clause 6.1.3.22 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. Inputs, Optional: Network Area Information, Request for notification, Alternative Service Requirements. Outputs, Required: PDTQ Reference ID, one or more PDTQ policies. Output, Optional: None.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

5.2.6.30.2

8.3.1.3.5 Minimum requirements with different Cell ID and non-colliding CRS (with multiple NZP CSI-RS resources and CRS assistance information is configured)

The requirements are specified in Table 8.3.1.3.5-3, with the additional parameters in Tables 8.3.1.3.5-1 and 8.3.1.3.5-2. The purpose of this test is to verify the UE capability of supporting non quasi-colocated antenna ports when the UE receives DCI format 2D in a scenario where three transmission points have different Cell ID and non-colliding CRS. In particular the test verifies that the UE, configured with quasi co-location type B, performs correct tracking and compensation of the frequency difference and timing difference between two transmission points, channel parameters estimation and rate matching according to the ‘PDSCH RE Mapping and Quasi-Co-Location Indicator’ (PQI) signalling defined in [6]. Further, the test verifies that the UE, configured with the CRS assistance information [7], can mitigate interference from CRS for demodulation. The CRS assistance information [7] includes TP 3. In Tables 8.3.1.3.5-1 and 8.3.1.3.5-2, transmission point 1 (TP 1) is the serving cell transmitting PDCCH, synchronization signals and PBCH, Transmission point 2 (TP 2) has different Cell ID as TP 1, and Transmission point 3 (TP 3) is the aggressor transmission point. Multiple NZP CSI-RS resources and ZP CSI-RS resources are configured. In each sub-frame, DL PDSCH transmission is dynamically switched between TP 1 and TP 2 with multiple PDSCH RE Mapping and Quasi-Co-Location Indicator configuration (PQI). Configurations of PDSCH RE Mapping and Quasi-Co-Location Indicator and downlink transmission hypothesis are defined in Table 8.3.1.3.5-2. The downlink physical channel setup for TP 1 is according to Table C.3.4-1, for TP 2 is according to Table C.3.4-2, and for TP 3 is according to Annex C.3.2. Table 8.3.1.3.5-1: Test Parameters DPS transmission with CRS assistance information Table 8.3.1.3.5-2: Configurations of PQI and DL transmission hypothesis for each PQI set Table 8.3.1.3.5-3: Performance Requirements DPS transmission with CRS assistance information

3GPP TS 36.101

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

RAN4

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

8.3.1.3.5

5.7.10.3 Reception of the UEInformationRequest message

Upon receiving the UEInformationRequest message, the UE shall, only after successful security activation: 1> if the idleModeMeasurementReq is included in the UEInformationRequest and the UE has stored VarMeasIdleReport that contains measurement information concerning cells other than the PCell: 2> set the measResultIdleEUTRA in the UEInformationResponse message to the value of measReportIdleEUTRA in the VarMeasIdleReport, if available; 2> set the measResultIdleNR in the UEInformationResponse message to the value of measReportIdleNR in the VarMeasIdleReport, if available; 2> discard the VarMeasIdleReport upon successful delivery of the UEInformationResponse message confirmed by lower layers; 1> if the logMeasReportReq is present and if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReport, or if the current registered SNPN is included in snpn-ConfigIDList stored in VarLogMeasReport: 2> if VarLogMeasReport includes one or more logged measurement entries, set the contents of the logMeasReport in the UEInformationResponse message as follows: 3> include the absoluteTimeStamp and set it to the value of absoluteTimeInfo in the VarLogMeasReport; 3> include the traceReference and set it to the value of traceReference in the VarLogMeasReport; 3> include the traceRecordingSessionRef and set it to the value of traceRecordingSessionRef in the VarLogMeasReport; 3> include the tce-Id and set it to the value of tce-Id in the VarLogMeasReport; 3> include the logMeasInfoList and set it to include one or more entries from the VarLogMeasReport starting from the entries logged first, and for each entry of the logMeasInfoList that is included, include all information stored in the corresponding logMeasInfoList entry in VarLogMeasReport; 3> if the VarLogMeasReport includes one or more additional logged measurement entries that are not included in the logMeasInfoList within the UEInformationResponse message: 4> include the logMeasAvailable; 4> if bt-LocationInfo is included in locationInfo of one or more of the additional logged measurement entries in VarLogMeasReport that are not included in the logMeasInfoList within the UEInformationResponse message: 5> include the logMeasAvailableBT; 4> if wlan-LocationInfo is included in locationInfo of one or more of the additional logged measurement entries in VarLogMeasReport that are not included in the logMeasInfoList within the UEInformationResponse message: 5> include the logMeasAvailableWLAN; 1> if ra-ReportReq is set to true and the UE has random access related information available in VarRA-Report and if the RPLMN is included in plmn-IdentityList stored in VarRA-Report; or 1> if ra-ReportReq is set to true and the UE has random access related information available in VarRA-Report and if the registered SNPN is included in snpn-IdentityList stored in VarRA-Report: 2> set the ra-ReportList in the UEInformationResponse message to the value of ra-ReportList in VarRA-Report; 2> discard the ra-ReportList from VarRA-Report upon successful delivery of the UEInformationResponse message confirmed by lower layers; 1> if rlf-ReportReq is set to true: 2> if the UE has radio link failure information or handover failure information available in VarRLF-Report and if the RPLMN is included in plmn-IdentityList stored in VarRLF-Report; or 2> if the UE has radio link failure information or handover failure information available in VarRLF-Report and if the current registered SNPN is included in snpn-IdentityList stored in VarRLF-Report: 3> set timeSinceFailure in VarRLF-Report to the time that elapsed since the last radio link failure or handover failure in NR; 3> set the rlf-Report in the UEInformationResponse message to the value of rlf-Report in VarRLF-Report; 3> discard the rlf-Report from VarRLF-Report upon successful delivery of the UEInformationResponse message confirmed by lower layers; 2> else if the UE is capable of cross-RAT RLF reporting as defined in TS 38.306[ NR; User Equipment (UE) radio access capabilities ] [26] and has radio link failure information or handover failure information available in VarRLF-Report of TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10] and if the RPLMN is included in plmn-IdentityList stored in VarRLF-Report of TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10]: 3> set timeSinceFailure in VarRLF-Report of TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10] to the time that elapsed since the last radio link failure or handover failure in EUTRA; 3> set failedPCellId-EUTRA in the rlf-Report in the UEInformationResponse message to indicate the PCell in which RLF was detected or the source PCell of the failed handover in the VarRLF-Report of TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10]; 3> set the measResult-RLF-Report-EUTRA in the rlf-Report in the UEInformationResponse message to the value of rlf-Report in VarRLF-Report of TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10]; 3> discard the rlf-Report from VarRLF-Report of TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10] upon successful delivery of the UEInformationResponse message confirmed by lower layers; 1> if connEstFailReportReq is set to true and the UE has connection establishment failure or connection resume failure information in VarConnEstFailReport or VarConnEstFailReportList and if the RPLMN is equal to plmn-Identity stored in VarConnEstFailReport or in at least one of the entries of VarConnEstFailReportList: 1> if connEstFailReportReq is set to true and if the UE has connection establishment failure information or connection resume failure information available in VarConnEstFailReport or VarConnEstFailReportList and if the registered SNPN identity is equal to snpn-identity stored in VarConnEstFailReport or any entry of VarConnEstFailReportList: 2> set timeSinceFailure in VarConnEstFailReport to the time that elapsed since the last connection establishment failure or connection resume failure in NR; 2> set the connEstFailReport in the UEInformationResponse message to the value of connEstFailReport in VarConnEstFailReport; 2> if the UE supports multiple CEF report: 3> for each connEstFailReport in the connEstFailReportList in VarConnEstFailReportList: 4> set timeSinceFailure to the time that elapsed since the associated connection establishment failure or connection resume failure in NR; 2> for each connEstFailReport in the connEstFailReportList in the UEInformationResponse message, set the value to the value of connEstFailReport in VarConnEstFailReport in VarConnEstFailReportList; 2> discard the connEstFailReport from VarConnEstFailReport and VarConnEstFailReportList upon successful delivery of the UEInformationResponse message confirmed by lower layers; 1> if the mobilityHistoryReportReq is set to true: 2> include the mobilityHistoryReport and set it to include visitedCellInfoList from VarMobilityHistoryReport; 2> include in the mobilityHistoryReport an entry for the current PCell, possibly after removing the oldest entry if required, and set its fields as follows: 3> set visitedCellId to the global cell identity or the physical cell identity and carrier frequency of the current PCell: 3> set field timeSpent to the time spent in the current PCell; 3> if the UE supports PSCell mobility history information and if visitedPSCellInfoList is present in VarMobilityHistoryReport: 4> for the newest entry of the PCell in the mobilityHistoryReport, include visitedPSCellInfoList from VarMobilityHistoryReport; 4> if the UE is configured with a PSCell: 5> for the newest entry of the PCell in the mobilityHistoryReport, include the current PSCell information in the visitedPSCellInfoListReport, possibly after removing the oldest PSCell entry of a PCell in the mobilityHistoryReport, if required, and set its fields as follows: 6> set visitedCellId to the global cell identity or the physical cell identity and carrier frequency of the current PSCell: 6> set field timeSpent to the time spent in the current PSCell while being connected to the current PCell; 4> else: 5> for the newest entry of the PCell in the mobilityHistoryReport, include a new entry in the visitedPSCellInfoListReport, possibly after removing the oldest PSCell entry of a PCell in the mobilityHistoryReport, if required, and set its fields as follows: 6> set field timeSpent to the time spent without PSCell in the current PCell since last PSCell release since connected to the current PCell in RRC_CONNECTED; 3> else if the UE supports PSCell mobility history information: 4> if the UE is configured with a PSCell: 5> for the newest entry of the PCell in the mobilityHistoryReport, include the current PSCell information in the visitedPSCellInfoListReport, possibly after removing the oldest PSCell entry of a PCell in the mobilityHistoryReport, if required, and set its fields as follows: 6> set visitedCellId to the global cell identity or the physical cell identity and carrier frequency of the current PSCell: 6> set field timeSpent to the time spent in the current PSCell while being connected to the current PCell; 4> else: 5> for the newest entry of the PCell in the mobilityHistoryReport, include a new entry in the visitedPSCellInfoListReport, possibly after removing the oldest PSCell entry of a PCell in the mobilityHistoryReport, if required, and set its fields as follows: 6> set field timeSpent to the time spent without PSCell in the current PCell since connected to the current PCell in RRC_CONNECTED; 1> if the successHO-ReportReq is set to true and if the UE has successful handover related information available in VarSuccessHO-Report and if the RPLMN is included in the plmn-IdentityList stored in VarSuccessHO-Report; or 1> if the successHO-ReportReq is set to true and if the UE has successful handover related information available in VarSuccessHO-Report and if the current registered SNPN is included in snpn-IdentityList if stored in the VarSuccessHO-Report: 2> if the successHO-Report in the VarSuccessHO-Report concerns a DAPS handover and if a PDCP PDU has been received from the source cell of the concerned HO and a non-duplicated PDCP PDU has been received from the target cell of the concerned HO: 3> set upInterruptionTimeAtHO in VarSuccessHO-Report to include the time elapsed between the time of arrival of the last PDCP PDU received from the source cell of the concerned handover and the time of arrival of the first non-duplicate PDCP PDU received from the target cell of the concerned handover, as measured at the time of arrival of the first non-duplicate PDCP PDU received from the target cell; 2> if the successHO-Report in the VarSuccessHO-Report concerns a mobilityFromNRCommand: 3> set timeSinceSHR in VarSuccessHO-Report to the time that elapsed since the execution of the associated mobilityFromNRCommand; 2> set the successHO-Report in the UEInformationResponse message to the value of successHO-Report in the VarSuccessHO-Report, if available; 2> discard the VarSuccessHO-Report upon successful delivery of the UEInformationResponse message confirmed by lower layers; 1> if the successPSCell-ReportReq is set to true and if the UE has successful PSCell change or addition information available in VarSuccessPSCell-Report and if the RPLMN is included in plmn-IdentityList stored in VarSuccessPSCell-Report; or 1> if the successPSCell-ReportReq is set to true and if the UE has successful PSCell change or addition information available in VarSuccessPSCell-Report and if the current registered SNPN is included in snpn-IdentityList if stored in the VarSuccessPSCell-Report: 2> set the successPSCell-Report in the UEInformationResponse message to the value of successPSCell-Report in the VarSuccessPSCell-Report; 2> discard the VarSuccessPSCell-Report upon successful delivery of the UEInformationResponse message confirmed by lower layers; 1> if the coarseLocationRequest is set to true: 2> include coarseLocationInfo, if available; 1> if the flightPathInfoReq is included in the UEInformationRequest and the UE has flight path information available, set the flightPathInfoReport in the UEInformationResponse message as follows: 2> include the list of up to maxWayPointNumber waypoints along the flight path; 2> if the includeTimeStamp is set to true, for each included waypoint: 3> if available, set the field timestamp to the time when UE intends to arrive at the waypoint; 1> if the logMeasReport is included in the UEInformationResponse: 2> submit the UEInformationResponse message to lower layers for transmission via SRB2; 2> discard the logged measurement entries included in the logMeasInfoList from VarLogMeasReport upon successful delivery of the UEInformationResponse message confirmed by lower layers; 1> else: 2> submit the UEInformationResponse message to lower layers for transmission via SRB1.

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

5.7.10.3

6.4.3 UE-requested PDU session release procedure 6.4.3.1 General

The purpose of the UE-requested PDU session release procedure is to enable by the UE to request a release of a PDU session. The UE is allowed to initiate the PDU session release procedure even if the timer T3396 is running. The UE is allowed to initiate the PDU session release procedure even if the timer T3584 is running. The UE is allowed to initiate the PDU session release procedure even if the timer T3585 is running. The UE is allowed to initiate the PDU session release procedure even if the UE is outside the LADN service area.

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

5.2.5.3.5 Npcf_PolicyAuthorization_Notify service operation

Service operation name: Npcf_PolicyAuthorization_Notify Description: provided by the PCF to notify NF consumers of the subscribed events. Inputs, Required: Event ID. The events that can be subscribed are defined in clause 6.1.3.18 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. Inputs, Optional: Event information (defined on a per Event ID basis) are defined in clause 6.1.3.18 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20], Notification Correlation Information (information to identify the application session), DNN, S-NSSAI. Notification Correlation Information is mandatory except in the case of the new 5GS Bridge/Router information detected event if no AF session exists between the PCF and the AF. DNN and S-NSSAI are required in the case of private IPv4 address being used for the IP type PDU Session that are potentially impacted by time sensitive communication and time synchronization service. Outputs, Required: Operation execution result indication. Outputs, Optional: None.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

5.2.5.3.5

– FeatureCombinationPreambles

The IE FeatureCombinationPreambles associates a set of preambles with a feature combination. For parameters which can be provided in this IE, the UE applies this field value when performing Random Access using a preamble in this featureCombinationPreambles, otherwise the UE applies the corresponding value as determined by applicable Need Code, e.g. Need S. On a specific BWP, there can be at most one set of preambles associated with a given feature combination per RA Type (i.e. 4-step RACH or 2-step RACH) per MSG1 repetition number. FeatureCombinationPreambles information element -- ASN1START -- TAG-FEATURECOMBINATIONPREAMBLES-START FeatureCombinationPreambles-r17 ::= SEQUENCE { featureCombination-r17 FeatureCombination-r17, startPreambleForThisPartition-r17 INTEGER (0..63), numberOfPreamblesPerSSB-ForThisPartition-r17 INTEGER (1..64), ssb-SharedRO-MaskIndex-r17 INTEGER (1..15) OPTIONAL, -- Need S groupBconfigured-r17 SEQUENCE { ra-SizeGroupA-r17 ENUMERATED {b56, b144, b208, b256, b282, b480, b640, b800, b1000, b72, spare6, spare5,spare4, spare3, spare2, spare1}, messagePowerOffsetGroupB-r17 ENUMERATED { minusinfinity, dB0, dB5, dB8, dB10, dB12, dB15, dB18}, numberOfRA-PreamblesGroupA-r17 INTEGER (1..64) } OPTIONAL, -- Need R separateMsgA-PUSCH-Config-r17 MsgA-PUSCH-Config-r16 OPTIONAL, -- Cond MsgAConfigCommon msgA-RSRP-Threshold-r17 RSRP-Range OPTIONAL, -- Need R rsrp-ThresholdSSB-r17 RSRP-Range OPTIONAL, -- Need R deltaPreamble-r17 INTEGER (-1..6) OPTIONAL, -- Need R ..., [[ msg1-RepetitionNum-r18 ENUMERATED {n2, n4, n8} OPTIONAL, -- Cond Msg1Rep2 msg1-RepetitionTimeOffsetROGroup-r18 ENUMERATED {n4, n8, n16, n32} OPTIONAL -- Cond Msg1Rep3 ]] } -- TAG-FEATURECOMBINATIONPREAMBLES-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

Annex A (Informative): Backward Compatibility Guidelines for Information Elements

In order to preserve backward compatibility, the following rules should apply when adding or modifying information elements for existing messages. - No new mandatory (M) information elements should be added. - No new conditional (C) information elements should be added. - Any new IEs should be either: optional (O), having no conditions on their presence, or conditional-optional (CO), having conditions that should apply only to the sender and not to the receiver. Such conditions should be worded generally as follows: "This IE shall be sent over the xxx interface <condition>. The receiving entity need not check the IE's presence." - If any new conditions are added to a previously specified conditional (C) information element, these new conditions should apply only to the sender and not to the receiver. Such additional conditions should be worded generally as follows: "This IE shall be sent over the xxx interface <condition>. For this optional condition, the receiving entity need not check the IE's presence." Existing conditions for such conditional (C) IEs should be treated as before, and the presence of the IEs should remain conditional (C).

3GPP TS 29.274

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

CT WG4

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

Annex

5.9.2 Location Change Reporting Procedure 5.9.2.1 General

The PDN GW may request for each PDN connection independently whether the MME shall report changes of ECGI/eNodeB ID/TAI (by using the "MS Info Change Reporting Action" parameter) and/or the UE entering/leaving a Presence Reporting Area (by using the "Presence Reporting Area Action" parameter) and/or whether the MME shall report changes of user CSG information (by using "CSG Information Reporting Action" parameter) to the PDN GW. This reporting (any combination of "MS Info Change Reporting Action" and/or "Presence Reporting Area Action" and/or "CSG Information Reporting Action") may be controlled by the PDN GW at the following procedures: - Attach, - Tracking Area Update (when inducing a Modify Bearer procedure to the PDN GW), - Inter-RAT Mobility to E-UTRAN (when inducing a Modify Bearer procedure to the PDN GW), - Dedicated bearer activation, - PDN GW initiated bearer modification with bearer QoS update, - PDN GW initiated bearer modification without bearer QoS update, - UE requested PDN connectivity, - UE requested bearer resource modification. The "Presence Reporting Area Action" and "Presence Reporting Area Information" parameters apply to all procedures listed above but, within this specification, their usage has only been described in the message flows related with the Attach and the UE requested PDN connectivity procedures. The reporting of UE entering/leaving a Presence Reporting Area is further described in clause 5.9.2.2. The PDN GW may also request the MME to stop any of the above mentioned types of reporting. The MME shall obey the last explicit instruction received from the PDN GW or source MME. During both mobility management and session management procedures, the MME shall indicate to the PDN GW the support of reporting location changes (using the MS Info Change Reporting support indication): - If ECGI/eNodeB ID/TAI information is permitted to be sent to the PDN GW according to MME operator's policy, - If CSG information is permitted to be sent to the PDN GW according to MME operator's policy. The MME may be configured to report ECGI/eNodeB ID/TAI changes only when one or more E-RAB(s) are established. Otherwise the MME shall report ECGI/eNodeB ID/TAI changes as soon as detected. If the level of support changes during a mobility management procedure then the MME shall indicate the current level of support to the S-GW and shall in addition provide ECGI/eNodeB ID/TAI even if the PDN GW has not requested this information. This could for example happen during MME change when the level of support indicated by the old MME is not the same as in the new MME. NOTE 1: The inclusion of ECGI/eNodeB ID/TAI will trigger a Modify Bearer Request message from S-GW to the PDN GW and therefore this will make sure that the new level of support reaches the PDN GW. At change of Serving Node (MME/S4-SGSN), the old Serving Node provides the new serving node with "MS Info Change Reporting Action" as previously requested by the PDN GW. The new Serving Node takes the "MS Info Change Reporting Action" immediately into account with the exception that, at mobility between a S4-SGSN and a MME, the new MME (respectively S4-SGSN) does not take into account the "MS Info Change Reporting Action" received from the S4-SGSN (respectively MME) but assumes that no location information change reporting is requested for the target RAT. At a change of RAT type between EUTRAN and UTRAN or between EUTRAN and GERAN, if location information change reporting is required in the target RAT, the PDN GW shall request "MS Info Change Reporting Action" from the new Serving Node (MME or S4-SGSN). Upon inter-RAT mobility, if the target MME/S4-SGSN supports location information change reporting, the target MME/S4-SGSN shall include the User Location Information in the Create Session Request / Modify Bearer Request, regardless of whether location Information change reporting had been requested in the previous RAT by the PDN GW. The PDN GWPDN GW shall not request the MME to report location changes if it has not received the indication for corresponding support from the MME. NOTE 2: For E-UTRAN access, homogeneous support of reporting changes of UE presence in a Presence Reporting Area in a network is assumed: When the PCRF configuration indicates that reporting changes of UE presence in a Presence Reporting Area is supported for E-UTRAN, this means it is supported by all the PDN GWPDN GW, all MME and all the SGW including the MME and SGW working in network sharing mode. If change of UE presence in Presence Reporting Area reporting is not supported, the PCRF may instead activate location information change reporting at cell, eNodeB or tracking area level. The following procedure shall be used for location change reports to the PDN GWPDN GW where the report is not combined with other mobility management or session management signalling. The procedure shall only apply when the MME has been explicitly requested to report location changes. The following procedure can be used for MO Exception Data Counter reporting where the report is not combined with other mobility management or session management signalling. The MME only includes the MO Exception data counter if the RRC establishment cause is set to "MO exception data" and the UE is accessing via the NB-IoT RAT. The MME maintains the MO Exception Data Counter for Serving PLMN Rate Control purposes (see clause 4.7.7.2). The MME may immediately send the MO Exception Data Counter to the Serving GW. Alternatively, in order to reduce signalling, the MME may send the MO Exception Data Counter to the Serving GW as described in TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [43]. The SGW and PDN GWPDN GW indicate each use of this RRC establishment cause by the related counter on its CDR. NOTE 3: Due to the increased signalling load, it is recommended that ECGI/eNodeB ID/TAI or CSG reporting is only applied for a limited number of subscribers. Figure 5.9.2.1-1 represents the ECGI change triggering a report of change in ECGI, and/or the User CSG information change triggering a report of change in user CSG information. The figure also shows the reporting of a TAI change and/or when a UE enters or leaves a Presence Reporting Area. Figure 5.9.2.1-1: Notification of the ECGI, TAI and/or user CSG information changes 1a. the MME has received an ECGI information Update from the eNodeB. 1b. The MME detects that the user CSG information has changed by comparing with the MME stored user CSG information, or 1c. The MME detects that the TAI of the UE has changed, or 1d. The MME detects that the UE has entered or left a Presence Reporting Area defined for this UE. NOTE 4: It is possible that these changes are triggered at same time. 2. If the MME has been requested to report location changes to the PDN GWPDN GW for the UE (under the conditions specified in clause 5.9.2), the MME shall send the Change Notification message to the SGW indicating the new ECGI, TAI and/or user CSG information. The MME stores the notified user CSG information. If the MME has been requested to report a change of UE presence in Presence Reporting Area (under the conditions specified in clause 5.9.2), the MME shall send the Change Notification message including the Presence Reporting Area Information comprising the area identifier(s) and indication(s) on whether the UE is inside or outside the area(s). If MME decides to reactivate one or more of the inactive Presence Reporting Area(s), the Presence Reporting Area Information in this message also comprises the reactivated PRA identifier(s), and indication(s) on whether the UE is inside or outside the reactivated area(s). 3. The SGW forwards the Change Notification message to the PDN GWPDN GW. If dynamic PCC is deployed, and location changes need to be conveyed to the PCRF, then the PDN GWPDN GW shall send this information to the PCRF as defined in TS 23.203[ Policy and charging control architecture ] [6]. If Presence Reporting Area Information has been received, the PDN GWPDN GW shall forward the Presence Reporting Area Information to the PCRF, to the OCS or to both as defined in TS 23.203[ Policy and charging control architecture ] [6]. 4. The PDN GW sends the Change Notification Ack to the SGW. 5. The SGW forwards the Change Notification Ack to the MME.

3GPP TS 23.401

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

SA WG2

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

5.9.2

– UERadioAccessCapabilityInformation

This message is used to transfer UE radio access capability information, covering both upload to and download from the 5GC. Direction: ng-eNB or gNB to/ from 5GC UERadioAccessCapabilityInformation message -- ASN1START -- TAG-UE-RADIO-ACCESS-CAPABILITY-INFORMATION-START UERadioAccessCapabilityInformation ::= SEQUENCE { criticalExtensions CHOICE { c1 CHOICE{ ueRadioAccessCapabilityInformation UERadioAccessCapabilityInformation-IEs, spare7 NULL, spare6 NULL, spare5 NULL, spare4 NULL, spare3 NULL, spare2 NULL, spare1 NULL }, criticalExtensionsFuture SEQUENCE {} } } UERadioAccessCapabilityInformation-IEs ::= SEQUENCE { ue-RadioAccessCapabilityInfo OCTET STRING (CONTAINING UE-CapabilityRAT-ContainerList), nonCriticalExtension SEQUENCE {} OPTIONAL } -- TAG-UE-RADIO-ACCESS-CAPABILITY-INFORMATION-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

– DownlinkConfigCommonSIB

The IE DownlinkConfigCommonSIB provides common downlink parameters of a cell. DownlinkConfigCommonSIB information element -- ASN1START -- TAG-DOWNLINKCONFIGCOMMONSIB-START DownlinkConfigCommonSIB ::= SEQUENCE { frequencyInfoDL FrequencyInfoDL-SIB, initialDownlinkBWP BWP-DownlinkCommon, bcch-Config BCCH-Config, pcch-Config PCCH-Config, ..., [[ pei-Config-r17 PEI-Config-r17 OPTIONAL, -- Need R initialDownlinkBWP-RedCap-r17 BWP-DownlinkCommon OPTIONAL -- Need R ]], [[ frequencyInfoDL-v1800 FrequencyInfoDL-SIB-v1800 OPTIONAL -- Need R ]] } DownlinkConfigCommonSIB-v1760 ::= SEQUENCE { frequencyInfoDL-v1760 FrequencyInfoDL-SIB-v1760 } BCCH-Config ::= SEQUENCE { modificationPeriodCoeff ENUMERATED {n2, n4, n8, n16}, ... } PCCH-Config ::= SEQUENCE { defaultPagingCycle PagingCycle, nAndPagingFrameOffset CHOICE { oneT NULL, halfT INTEGER (0..1), quarterT INTEGER (0..3), oneEighthT INTEGER (0..7), oneSixteenthT INTEGER (0..15) }, ns ENUMERATED {four, two, one}, firstPDCCH-MonitoringOccasionOfPO CHOICE { sCS15KHZoneT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..139), sCS30KHZoneT-SCS15KHZhalfT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..279), sCS60KHZoneT-SCS30KHZhalfT-SCS15KHZquarterT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..559), sCS120KHZoneT-SCS60KHZhalfT-SCS30KHZquarterT-SCS15KHZoneEighthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..1119), sCS120KHZhalfT-SCS60KHZquarterT-SCS30KHZoneEighthT-SCS15KHZoneSixteenthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..2239), sCS480KHZoneT-SCS120KHZquarterT-SCS60KHZoneEighthT-SCS30KHZoneSixteenthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..4479), sCS480KHZhalfT-SCS120KHZoneEighthT-SCS60KHZoneSixteenthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..8959), sCS480KHZquarterT-SCS120KHZoneSixteenthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..17919) } OPTIONAL, -- Need R ..., [[ nrofPDCCH-MonitoringOccasionPerSSB-InPO-r16 INTEGER (2..4) OPTIONAL -- Cond SharedSpectrum2 ]], [[ ranPagingInIdlePO-r17 ENUMERATED {true} OPTIONAL, -- Need R firstPDCCH-MonitoringOccasionOfPO-v1710 CHOICE { sCS480KHZoneEighthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..35839), sCS480KHZoneSixteenthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..71679) } OPTIONAL -- Need R ]] } PEI-Config-r17 ::= SEQUENCE { po-NumPerPEI-r17 ENUMERATED {po1, po2, po4, po8}, payloadSizeDCI-2-7-r17 INTEGER (1..maxDCI-2-7-Size-r17), pei-FrameOffset-r17 INTEGER (0..16), subgroupConfig-r17 SubgroupConfig-r17, lastUsedCellOnly-r17 ENUMERATED {true} OPTIONAL, -- Need R ... } SubgroupConfig-r17 ::= SEQUENCE { subgroupsNumPerPO-r17 INTEGER (1.. maxNrofPagingSubgroups-r17), subgroupsNumForUEID-r17 INTEGER (1.. maxNrofPagingSubgroups-r17) OPTIONAL, -- Need S ... } -- TAG-DOWNLINKCONFIGCOMMONSIB-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

4.3.4.3 UE or network requested PDU Session Release for Home-routed Roaming

This procedure is used in the case of home-routed roaming scenarios. Figure 4.3.4.3-1: UE or network requested PDU Session Release for home-routed roaming 1. The procedure is triggered by one of the following events: 1a. (UE initiated release) As in step 1a of clause 4.3.4.2 with the addition that: - the V-SMF initiates N4 Session Modification to instruct the V-UPF to stop forwarding uplink traffic; and - the V-SMF invokes the Nsmf_PDUSession_Update Request (SM Context ID, information from the SM message from the UE e.g. PCO, "Trigger PDU Session Release" indication, Timezone, User Location Information) service operation to request the H-SMF to release the PDU Session. The H-SMF responds to the request immediately. 1b. (Serving network initiated release) The serving network initiates the PDU Session Release during UE or serving network initiated Deregistration procedure as specified in clause 4.2.2.3. There is no NAS SM message between the UE and the V-SMF in this case. This step is the same as step 1c in clause 4.3.4.2, with the addition that: - the V-SMF initiates N4 Session Modification to instruct the V-UPF to stop forwarding uplink traffic; and - the V-SMF initiates the release of the PDU Session at the H-SMF by invoking the Nsmf_PDUSession_Release request. The serving network also initiates the PDU Session Release where neither N1 nor N2 SM signalling is needed before releasing the SM context as in step 1c in clause 4.3.4.2 if e.g. due to the set of network slices for a UE changes where a network slice instance is no longer available (e.g. as described in clause 5.15.5.2.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], or the AAA Server triggered Network Slice-Specific Re-authentication and Re-authorization procedure fails as specified in clause 4.2.9.2 or the AAA Server triggered Slice-Specific Authorization Revocation takes place as specified in clause 4.2.9.4). 1c. (HPLMN initiated release) This step is the same as step 1b in clause 4.3.4.2, with the addition that: - the H-SMF initiates N4 Session Modification to instruct the H-UPF to stop forwarding downlink traffic. 1d. This step is the same as step 1d in clause 4.3.4.2, with the addition that: - the V-SMF initiates N4 Session Modification to instruct the V-UPF to stop forwarding uplink traffic; and - the V-SMF invokes the Nsmf_PDUSession_Update Request towards H-SMF. 1e. (HPLMN initiated release) This step is the same as step 1e in clause 4.3.4.2, with the addition that: - if the H-SMF is notified by the V-SMF that the HPLMN S-NSSAI of the PDU Session with SSC mode 1 or SSC mode 2 is to be replaced with Alternative HPLMN S-NSSAI and if the H-SMF determines that a new PDU Session is to be established on the Alternative HPLMN S-NSSAI, the H-SMF initiates release of the PDU Session, as described in clause 5.15.19 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]; - the H-SMF initiates N4 Session Modification to instruct the H-UPF to stop forwarding downlink traffic. 1f. This step is the same as step 1f in clause 4.3.4.2, with the addition that: - the V-SMF initiates N4 Session Modification to instruct the V-UPF to stop forwarding uplink traffic; and - the V-SMF invokes the Nsmf_PDUSession_Update Request towards H-SMF. If the SMF receives one of the triggers in step 1a, 1c, 1e or 1f, the H-SMF starts PDU Session Release procedure. When a SMF above initiates N4 Session Modification to instruct the UPF to stop forwarding traffic this means also to stop taking into account the traffic for usage monitoring. 2a-2b. (UE-, (R)AN- or Serving network initiated) This step is performed in case the PDU Session Release is triggered by a message from V-SMF. These steps are the same as steps 2a-2b in clause 4.3.4.2. The SMF is the SMF in HPLMN. NOTE 1: This step 2a-2b can correspond to steps 1a, 1b, 1d, 1f. 3a. (UE or HPLMN initiated release) The H-SMF prepares the SM Release PDU Session Command message and initiates the PDU Session Release towards the UE by invoking the Nsmf_PDUSession_Update Request service operation towards the V-SMF. The Nsmf_PDUSession_Update Request contains necessary information to build the SM Release PDU Session Command by the V-SMF towards the UE (for example a Release Cause or PCO). For network slice replacement as in step 1e, the H-SMF includes Alternative HPLMN S-NSSAI and a cause value indicating that a new PDU Session re-establishment on the Alternative HPLMN S-NSSAI is required. 3b. (Serving network initiated release) The H-SMF responds to the PDU release request from the V-SMF with a Nsmf_PDUSession_Release response. If the UPF included Small Data Rate Control Status in step 2 then the SMF includes Small Data Rate Control Status in the request to the AMF. If the Control Plane CIoT 5GS Optimisation is enabled for this PDU Session, the steps 4a and 4b are skipped. 4a-4b. The V-SMF releases the corresponding User Plane resources. This includes the same procedure in step 2 but controlled from the SMF in VPLMN. 5-13. These steps are the same as steps 3-10 in clause 4.3.4.2, with the addition that: - In step 5c, for network slice replacement, based on information from H-SMF, the PDU Session Release Command message may include Alternative HPLMN S-NSSAI and/or Alternative VPLMN S-NSSAI and a cause value indicating that a PDU Session re-establishment on the Alternative HPLMN S-NSSAI and/or Alternative VPLMN S-NSSAI is required. 14. (UE or HPLMN initiated release) The V-SMF responds to the Nsmf_PDUSession_Update Request invoked at step 3a and confirms the PDU Session Release. The Nsmf_PDUSession_Update response may carry information such as PCO received from the UE in SM PDU Session Release Accept. as well as User Location Information, Time Zone and Secondary RAT Usage Data. 15a. (UE or HPLMN or Serving network initiated release) The H-SMF releases the SM policy control association with the PCF by invoking the SM Policy Association Termination procedure defined in clause 4.16.6. For serving network initiated PDU Session Release case, this step happens between step 1b and step 3b. 15b-15c. (HPLMN initiated release) In case the PDU Session Release is HPLMN-initiated (i.e. triggers in 1c, 1e), the H-SMF releases the corresponding User Plane resources. This includes the same procedure as in step 2. 15d. As in step 15 of clause 4.3.4.2, the SMF invokes the Nudm_UECM_Deregistration service operation. NOTE 2: Step 15d does not necessarily take place after step 15c. 16. (UE or HPLMN initiated release) The H-SMF shall remove all contexts associated with the PDU Session: 16a. The H-SMF requests the V-SMF to release all contexts associated with the PDU Session by invoking the Nsmf_PDUSession_StatusNotify (Release) operation. 16b. The V-SMF requests the AMF to release all contexts associated with the PDU Session by invoking the Nsmf_PDUSession_SMContexStatusNotify (Release). The AMF releases the association between the SMF ID and the PDU Session ID.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.3.4.3

8.3.8.2 Back-off timer value

The network may include this IE if the 5GSM cause is not #26 "insufficient resources", #37 "5GS QoS not accepted", #44 "Semantic errors in packet filter(s)", #45 "Syntactical error in packet filter(s)", #46 "out of LADN service area", #59 "unsupported 5QI value", #67 "insufficient resources for specific slice and DNN", #69 "insufficient resources for specific slice", #83 "Semantic error in the QoS operation", or #84 "Syntactical error in the QoS operation" to request a minimum time interval before procedure retry is allowed.

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

8.3.8.2

5.2.6.12 Nnef_APISupportCapability service 5.2.6.12.1 General

In order to support interworking with EPC, the NEF is integrated with SCEF as a combined SCEF+NEF node for network exposure as defined in clause 5.17.5 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The common services provided by SCEF+NEF may become unavailable because the UE is now being served by a node (e.g. MME) or NF (e.g. AMF) that does not support that service. If the availability or expected level of support of a service API associated with a UE changes, for example due to a mobility between 5GC and EPC, the AF can be made aware of the change via this service. This service consists of Subscribe, Unsubscribe, Notify service operations. It supports informing AF of the availability or expected level of support of a given service via a response to the One-time report type subscribe request of the AF or via a notification to the Continuous report type subscription of the AF.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

5.2.6.12

– NZP-CSI-RS-ResourceSet

The IE NZP-CSI-RS-ResourceSet is a set of Non-Zero-Power (NZP) CSI-RS resources (their IDs) and set-specific parameters. NZP-CSI-RS-ResourceSet information element -- ASN1START -- TAG-NZP-CSI-RS-RESOURCESET-START NZP-CSI-RS-ResourceSet ::= SEQUENCE { nzp-CSI-ResourceSetId NZP-CSI-RS-ResourceSetId, nzp-CSI-RS-Resources SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourcesPerSet)) OF NZP-CSI-RS-ResourceId, repetition ENUMERATED { on, off } OPTIONAL, -- Need S aperiodicTriggeringOffset INTEGER(0..6) OPTIONAL, -- Need S trs-Info ENUMERATED {true} OPTIONAL, -- Need R ..., [[ aperiodicTriggeringOffset-r16 INTEGER(0..31) OPTIONAL -- Need S ]], [[ pdc-Info-r17 ENUMERATED {true} OPTIONAL, -- Need R cmrGroupingAndPairing-r17 CMRGroupingAndPairing-r17 OPTIONAL, -- Need R aperiodicTriggeringOffset-r17 INTEGER (0..124) OPTIONAL, -- Need S aperiodicTriggeringOffsetL2-r17 INTEGER(0..31) OPTIONAL -- Need R ]], [[ resourceType-r18 ENUMERATED {periodic} OPTIONAL -- Cond LTM ]] } CMRGroupingAndPairing-r17 ::= SEQUENCE { nrofResourcesGroup1-r17 INTEGER (1..7), pair1OfNZP-CSI-RS-r17 NZP-CSI-RS-Pairing-r17 OPTIONAL, -- Need R pair2OfNZP-CSI-RS-r17 NZP-CSI-RS-Pairing-r17 OPTIONAL -- Need R } NZP-CSI-RS-Pairing-r17 ::= SEQUENCE { nzp-CSI-RS-ResourceId1-r17 INTEGER (1..7), nzp-CSI-RS-ResourceId2-r17 INTEGER (1..7) } -- TAG-NZP-CSI-RS-RESOURCESET-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

6.14 Steering of roaming security mechanism 6.14.1 General

This clause describes the security functions necessary to support steering of the UE in the VPLMN during registration procedure and also after registration as described in TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [53] Annex C. The security functions are described in the context of the functions supporting the control plane solution for steering of roaming in 5GS. If the control plane solution for Steering of Roaming is supported by the HPLMN, the AUSF shall store the latest KAUSF after the completion of the latest primary authentication. The content of the Steering List as well as the conditions for sending it to the UE are described in TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [53] Annex C. The Steering List includes either a list of preferred PLMN/access technology combinations, a secured packet or the HPLMN indication that 'no change of the "Operator Controlled PLMN Selector with Access Technology" list stored in the UE is needed and thus no list of preferred PLMN/access technology combinations is provided'. NOTE1: If a SOR-AF is involved in providing the content of the Steering List as described in TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [53] Annex C, the SOR-AF belongs to the HPLMN. NOTE 2: The Steering of Roaming Information is defined in clause 1.2 of TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [53]. It contains thus the ACK indication, the Steering List and the integrity protection information.

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

6.14

4.11.4.3.3a Initial Attach for emergency session (GTP on S2b)

The procedure in clause 7.2.5 of TS 23.402[ Architecture enhancements for non-3GPP accesses ] [26] applies with the following modification: - Step 3 (Create Session Request): ePDG determines if interworking with 5GC is supported based on UE's 5G NAS capability and local configuration. In SMF+PGW-C, only one S-NSSAI is configured for the emergency APN. An emergency SMF+PGW-C identity should be configured as part of the Emergency Configuration Data specified in clause 13.5 of TS 23.402[ Architecture enhancements for non-3GPP accesses ] [26]. - Step 6 (Create Session Response), compared to step D.1 of clause 4.11.4.3.3, SMF+PGW-C does not include S-NSSAI in PCO for emergency PDN connection.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.11.4.3.3a

5.4.13.4 Paging

In the case of NR satellite access that provides discontinuous network coverage, AMF may utilize sub-area paging as described in clause 4.2.3.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] (e.g. first page in the last known cell-id or TA and retransmission in all registered TAs). The AMF may utilize the location information as received at or before the AN release due to the discontinuous coverage for paging optimisation. The AMF may e.g. receive UE location from NG-RAN during the Registration procedure e.g. triggered for Mobility Management and Power Saving Optimization for discontinuous network coverage as described in clause 5.4.13.1, or the AMF may request NG-RAN location reporting when the UE is in CM-CONNECTED state as described in clause 5.4.7.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.4.13.4

5.2.6.2.4 Nnef_EventExposure_Notify service operation

Service operation name: Nnef_EventExposure_Notify Description: NEF reports the event to the consumer that has previously subscribed. Inputs, Required: Event ID, Notification Correlation Information, time stamp. Inputs, Optional: Event information (defined on a per Event ID basis), Event Removal Indication, list of group member UE(s) whose subscription to event notification(s) are removed from a group-based event notification subscription, UE(s) added/removed to/from the group. Outputs, Required: Operation execution result indication.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

5.2.6.2.4

6.1.3.10 Data Volume and Power Headroom Report MAC Control Element

The Data Volume and Power Headroom Report (DPR) MAC control element is identified by the MAC PDU subheader used for the CCCH MAC SDU, as specified in table 6.2.1-2. It does not add any additional subheader and is always placed before the CCCH MAC SDU. DPR MAC control element is not included in the calculation of the L field in the MAC PDU subheader for the CCCH MAC SDU. It has a fixed size and consists of a single octet defined as follows (figures 6.1.3.10-1 and 6.1.3.10-1a): - Data Volume (DV): The Data Volume field identifies the total amount of data available across all logical channels and of data not yet associated with a logical channel after all MAC PDUs for the TTI have been built. The amount of data is indicated in number of bytes. It shall include all data that is available for transmission in the RLC layer, in the PDCP layer, and in the RRC layer; the definition of what data shall be considered as available for transmission is specified in TS 36.322[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Link Control (RLC) protocol specification ] [3], TS 36.323[ Evolved Universal Terrestrial Radio Access (E-UTRA); Packet Data Convergence Protocol (PDCP) specification ] [4] and TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8] respectively. The size of the RLC and MAC headers are not considered in the buffer size computation. The length of this field is 4 bits. The values taken by the Data Volume field are shown in Table 6.1.3.10-1; - Power Headroom (PH): This field indicates the power headroom level. The length of the field is 2 bits or 4 bits. The reported PH and the corresponding power headroom and extended power headroom levels are shown in Table 6.1.3.10-2 and Table 6.1.3.10-2a, respectively, below (the corresponding measured values in dB can be found in TS 36.133[ Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for support of radio resource management ] [9]); - R: reserved bit, set to "0". Figure 6.1.3.10-1: Data Volume and Power Headroom Report MAC control element Figure 6.1.3.10-1a: Data Volume and Power Headroom Report MAC control element for Extended Power Headroom level reporting Table 6.1.3.10-1: Data Volume levels for DV Table 6.1.3.10-2: Power Headroom levels for PH Table 6.1.3.10-2a: Extended Power Headroom levels for PH

3GPP TS 36.321

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

RAN2

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

6.1.3.10

9.2.8 Beam failure detection and recovery

For beam failure detection, the gNB configures the UE with beam failure detection reference signals (SSB or CSI-RS) and the UE declares beam failure when the number of beam failure instance indications from the physical layer reaches a configured threshold before a configured timer expires. For beam failure detection in multi-TRP operation, the gNB configures the UE with two sets of beam failure detection reference signals, and the UE declares beam failure for a TRP / BFD-RS set when the number of beam failure instance indications associated with the corresponding set of beam failure detection reference signals from the physical layer reaches a configured threshold before a configured timer expires. SSB-based Beam Failure Detection is based on the CD-SSB associated to the initial DL BWP and can be configured for the initial DL BWPs, for DL BWPs containing the CD-SSB associated to the initial DL BWP, and, if supported, for DL BWPs not containing the CD-SSB associated to the initial DL BWP. Besides, SSB-based Beam Failure Detection can be also performed based on the non-cell defining SSB, if configured for the active DL BWP. For other DL BWPs, Beam Failure Detection can only be performed based on CSI-RS, if configured for the active DL BWP. After beam failure is detected on PCell, the UE: - triggers beam failure recovery by initiating a Random Access procedure on the PCell; - selects a suitable beam to perform beam failure recovery (if the gNB has provided dedicated Random Access resources for certain beams, those will be prioritized by the UE). - includes an indication of a beam failure on PCell in a BFR MAC CE if the Random Access procedure involves contention-based random access. Upon completion of the Random Access procedure, beam failure recovery for PCell is considered complete. After beam failure is detected on an SCell, the UE: - triggers beam failure recovery by initiating a transmission of a BFR MAC CE for this SCell; - selects a suitable beam for this SCell (if available) and indicates it along with the information about the beam failure in the BFR MAC CE. Upon reception of a PDCCH indicating an uplink grant for a new transmission for the HARQ process used for the transmission of the BFR MAC CE, beam failure recovery for this SCell is considered complete. After beam failure is detected for a BFD-RS set of a Serving Cell, the UE: - triggers beam failure recovery by initiating a transmission of a BFR MAC CE for this BFD-RS set; - selects a suitable beam for this BFD-RS set (if available) and indicates whether the suitable (new) beam is found or not along with the information about the beam failure in the BFR MAC CE for this BFD-RS set. Upon reception of a PDCCH indicating an uplink grant for a new transmission for the HARQ process used for the transmission of the BFR MAC CE for this BFD-RS set, beam failure recovery for this BFD-RS set is considered complete. After beam failure is detected for both BFD-RS sets of PCell concurrently, the UE: - triggers beam failure recovery by initiating a Random Access procedure on the PCell; - selects a suitable beam for each failed BFD-RS set (if available) and indicates whether the suitable (new) beam is found or not along with the information about the beam failure in the BFR MAC CE for each failed BFD-RS set; - upon completion of the Random Access procedure, beam failure recovery for both BFD-RS sets of PCell is considered complete.

3GPP TS 38.300

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

RAN2

3GPP Series : 38 , Radio technology beyond LTE

9.2.8

5.3.8 Requirements for secure environment of the gNB

The secure environment is logically defined within the gNB. It ensures protection and secrecy of all sensitive information and operations from any unauthorized access or exposure. The following list defines the requirements of the secure environment: - The secure environment shall support secure storage of sensitive data, e.g. long-term cryptographic secrets and vital configuration data. - The secure environment shall support the execution of sensitive functions, e.g. en-/decryption of user data and the basic steps within protocols which use long term secrets (e.g. in authentication protocols). - The secure environment shall support the execution of sensitive parts of the boot process. - The secure environment's integrity shall be assured. - Only authorised access shall be granted to the secure environment, i.e. to data stored and used within it, and to functions executed within it.

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

5.3.8

8.2.2.1.1 Minimum Requirement

For single carrier, the requirements are specified in Table 8.2.2.1.1-2, with the addition of the parameters in Table 8.2.2.1.1-1 and the downlink physical channel setup according to Annex C.3.2. For CA with 2 DL CCs, the requirements are specified in Table 8.2.2.1.1-4, with the addition of the parameters in Table 8.2.2.1.1-3 and the downlink physical channel setup according to Annex C.3.2. For CA with 3 DL CCs, the requirements are specified in Table 8.2.2.1.1-7, based on single carrier requirement specified in Table 8.2.2.1.1-5, with the addition of the parameters in Table 8.2.2.1.1-3 and the downlink physical channel setup according to Annex C.3.2. For CA with 4 DL CCs, the requirements are specified in Table 8.2.2.1.1-8, based on single carrier requirement specified in Table 8.2.2.1.1-5, with the addition of the parameters in Table 8.2.2.1.1-3 and the downlink physical channel setup according to Annex C.3.2. For CA with 5 DL CCs, the requirements are speicifed in Table 8.2.1.1.1-9, based on single carrier requirement speicified in Table 8.2.2.1.1-5, with the addition of the parameters in Table 8.2.2.1.1-3 and the downlink physical channel setup according to Annex C.3.2. For CA with 6 DL CCs, the requirements are speicifed in Table 8.2.1.1.1-10, based on single carrier requirement speicified in Table 8.2.2.1.1-5, with the addition of the parameters in Table 8.2.2.1.1-3 and the downlink physical channel setup according to Annex C.3.2. For CA with 7 DL CCs, the requirements are speicifed in Table 8.2.1.1.1-11, based on single carrier requirement speicified in Table 8.2.2.1.1-5, with the addition of the parameters in Table 8.2.2.1.1-3 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.2.2.1.1-1: Test Parameters Table 8.2.2.1.1-2: Minimum performance (FRC) Table 8.2.2.1.1-3: Test Parameters for CA Table 8.2.2.1.1-4: Minimum performance (FRC) for CA with 2DL CCs Table 8.2.2.1.1-5: Single carrier performance for multiple CA configurations Table 8.2.2.1.1-6: Void Table 8.2.2.1.1-7: Minimum performance (FRC) based on single carrier performance for CA with 3 DL CCs Table 8.2.2.1.1-8: Minimum performance (FRC) based on single carrier performance for CA with 4 DL CCs Table 8.2.2.1.1-9: Minimum performance (FRC) based on single carrier performance for CA with 5 DL CCs Table 8.2.2.1.1-10: Minimum performance (FRC) based on single carrier performance for CA with 6 DL CCs Table 8.2.2.1.1-11: Minimum performance (FRC) based on single carrier performance for CA with 7 DL CCs

3GPP TS 36.101

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

RAN4

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

8.2.2.1.1

5.2.5 Guard period for narrowband and wideband retuning

For BL/CE UEs, a guard period of at most SC-FDMA symbols is created for Tx-to-Tx frequency retuning between two consecutive subframes. - If the higher layer parameter ce-RetuningSymbols is set, then equals ce-RetuningSymbols, otherwise . - If the higher layer parameter ce-pusch-maxBandwidth-config is set to 5 MHz, then the rules for guard period creation defined in the remainder of this clause do not apply for retuning between narrowbands but for retuning between widebands and for transmissions involving multiple widebands. - If a UE is configured with higher layer parameter ce-PUSCH-FlexibleStartPRB-AllocConfig and the allocation resources are not fully within one narrowband, the rules for guard period creation defined in the remainder of this clause apply for retuning between tuning narrowbands, where - In case of CEModeA, the tuning narrowband is defined as the 6 consecutive PRBs starting from defined in 8.1.1 of [4] with the center frequency set in the middle. - In case of CEModeB, the tuning narrowband is defined as the 6 consecutive PRBs with the center frequency set in the middle of allocated two PRBs. - If the UE retunes from a first narrowband carrying PUSCH to a second narrowband carrying PUSCH, or if the UE retunes from a first narrowband carrying PUCCH to a second narrowband carrying PUCCH, - if , a guard period is created by the UE not transmitting the last SC-FDMA symbol in the first subframe; - if , a guard period is created by the UE not transmitting the last SC-FDMA symbol in the first subframe and the first SC-FDMA symbol in the second subframe. - If the UE retunes from a first narrowband carrying PUCCH to a second narrowband carrying PUSCH, - if the PUCCH uses a shortened PUCCH format and , a guard period is created by the UE not transmitting the last SC-FDMA symbol in the first subframe; - if the PUCCH uses a shortened PUCCH format and , a guard period is created by the UE not transmitting the last SC-FDMA symbol in the first subframe and the first SC-FDMA symbol in the second subframe; - if the PUCCH uses a normal PUCCH format, a guard period is created by the UE not transmitting the first SC-FDMA symbols in the second subframe. - If the UE retunes from a first narrowband carrying PUSCH to a second narrowband carrying PUCCH, - a guard period is created by the UE not transmitting the last SC-FDMA symbols in the first subframe. - For CEModeA, if the PUSCH is associated with C-RNTI or SPS C-RNTI and the higher layer parameter ce-pusch-maxBandwidth-config is set to 5 MHz, - If the PUSCH resource allocation is within a 5 MHz wideband, the center frequency of the transmission bandwidth is the center frequency of the wideband; - If the PUSCH resource allocation spans two 5 MHz widebands, the center frequency of transmission bandwidth is in the center of PUSCH resource allocation. Furthermore, for BL/CE UEs configured with the higher layer parameter srs-UpPtsAdd, a guard period of at most SC-FDMA symbols is created for Tx-to-Tx frequency retuning between a first special subframe and a second uplink subframe for frame structure type 2 according to: - If the UE retunes from a first narrowband carrying SRS in the last UpPTS symbol to a second narrowband carrying PUSCH, - a guard period is created by the UE not transmitting the first SC-FDMA symbols in the second subframe. - If the UE retunes from a first narrowband carrying SRS in the last but one UpPTS symbol, but not in the last UpPTS symbol, to a second narrowband carrying PUSCH, - if , a guard period is created by the UE not transmitting the last UpPTS symbol in the first subframe; - if , a guard period is created by the UE not transmitting the last UpPTS symbol in the first subframe and the first SC-FDMA symbol in the second subframe. - If the UE retunes from a first narrowband carrying SRS to a second narrowband carrying PUCCH, - if , a guard period is created by the UE not transmitting the last UpPTS symbol in the first subframe; - if , a guard period is created by the UE not transmitting the last UpPTS symbol in the first subframe and the first SC-FDMA symbol in the second subframe. For , and for SRS transmission in a special subframe, a BL/CE UE is not expected to be configured with a first SRS transmission in symbol l and a second SRS transmission in any of symbols if the first SRS transmission and the second SRS transmission use different narrowbands.

3GPP TS 36.211

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

RAN1

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

5.2.5

– SI-RequestConfigRepetition

The IE SI-RequestConfigRepetition contains configuration for Msg1 based SI request with Msg1 repetition. SI-RequestConfigRepetition information element -- ASN1START -- TAG-SI-REQUESTCONFIGREPETITION-START SI-RequestConfigRepetition-r18 ::= SEQUENCE { rach-OccasionsSI-r18 SEQUENCE { rach-ConfigSI-r18 RACH-ConfigGeneric, ssb-perRACH-Occasion-r18 ENUMERATED {oneEighth, oneFourth, oneHalf, one, two, four, eight, sixteen} } OPTIONAL, -- Need R si-RequestResourcesRepetitionNum2-r18 SEQUENCE (SIZE (1..maxSI-Message)) OF SI-RequestResourcesRepetition-r18 OPTIONAL, -- Need R si-RequestResourcesRepetitionNum4-r18 SEQUENCE (SIZE (1..maxSI-Message)) OF SI-RequestResourcesRepetition-r18 OPTIONAL, -- Need R si-RequestResourcesRepetitionNum8-r18 SEQUENCE (SIZE (1..maxSI-Message)) OF SI-RequestResourcesRepetition-r18 OPTIONAL, -- Need R ... } SI-RequestResourcesRepetition-r18 ::= SEQUENCE { ra-PreambleStartIndex-r18 INTEGER (0..63), ra-ssb-OccasionMaskIndex-r18 INTEGER (0..15) OPTIONAL -- Need R } -- TAG-SI-REQUESTCONFIGREPETITION-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

5.3.5.5.7 SpCell Configuration

The UE shall: 1> if the UE is acting as L2 U2N Remote UE and is not configured with MP: 2> if the SpCellConfig contains the rlf-TimersAndConstants which is set to setup: 3> use value for timers T311 as received in rlf-TimersAndConstants; 2> else if rlf-TimersAndConstants is not configured for this cell group or SpCellConfig contains the rlf-TimersAndConstants which is set to release: 3> use value for timers T311, as included in ue-TimersAndConstants received in SIB1; 1> else 2> if the SpCellConfig contains the rlf-TimersAndConstants: 3> configure the RLF timers and constants for this cell group as specified in 5.3.5.5.6; 2> else if rlf-TimersAndConstants is not configured for this cell group: 3> if any DAPS bearer is configured: 4> use values for timers T301, T310, T311 and constants N310, N311 for the target cell group, as included in ue-TimersAndConstants received in SIB1; 3> else 4> use values for timers T301, T310, T311 and constants N310, N311, as included in ue-TimersAndConstants received in SIB1; 2> if the SpCellConfig contains spCellConfigDedicated: 3> configure the SpCell in accordance with the spCellConfigDedicated; 3> consider the bandwidth part indicated in firstActiveUplinkBWP-Id, if included in the spCellConfigDedicated, to be the active uplink bandwidth part; 3> if the firstActiveDownlinkBWP-Id is included in the spCellConfigDedicated: 4> if the SpCellConfig is included in an RRCReconfiguration message contained in an NR or E-UTRA RRC message indicating that the SCG is deactivated: 5> consider the bandwidth part indicated in firstActiveDownlinkBWP-Id to be the bandwidth part for Radio Link Monitoring, Beam Failure Detection and measurements; 4> else: 5> consider the bandwith part indicated in firstActiveDownlinkBWP-Id to be the active downlink bandwidth part; 3> if any of the reference signal(s) that are used for radio link monitoring are reconfigured by the received spCellConfigDedicated: 4> stop timer T310 for the corresponding SpCell, if running; 4> stop timer T312 for the corresponding SpCell, if running; 4> reset the counters N310 and N311. 1> if the SpCellConfig contains the lowMobilityEvaluationConnected: 2> the UE may perform the evaluation of the low mobility criterion for this cell group as specified in 5.7.13.1; 1> if the SpCellConfig contains the goodServingCellEvaluationRLM: 2> the UE may perform the evaluation of the good serving cell quality criterion for this SpCell as specified in 5.7.13.2; 1> if the SpCellConfig contains the goodServingCellEvaluationBFD: 2> the UE may perform the evaluation of the good serving cell quality criterion for this serving cell as specified in 5.7.13.2;

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

5.3.5.5.7

8.10.1.1.10 Closed loop spatial multiplexing performance - Single-Layer Spatial Multiplexing 2 Tx Antenna Port with CRS assistance information (Cell-Specific Reference Symbols)

The requirements are specified in Table 8.10.1.1.10-2, with the addition of parameters in Table 8.10.1.1.10-1. In Table 8.10.1.1.10-1, Cell 1 is the serving cell, and Cell 2 and Cell 3 are the aggressor cells. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1, Cell 2 and Cell 3, respectively. The CRS assistance information [7] is provided to the UE and includes information on Cell 2 and Cell 3. The purpose of the test is to verify the closed loop single layer TM4 performance under assumption that UE applies CRS interference mitigation in the scenario with 2 CRS antenna ports in the serving and aggressor cells. Table 8.10.1.1.10-1: Test Parameters Table 8.10.1.1.10-2: Minimum Performance for PDSCH

3GPP TS 36.101

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

RAN4

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

8.10.1.1.10

– PUCCH-Config

The IE PUCCH-Config is used to configure UE specific PUCCH parameters (per BWP). PUCCH-Config information element -- ASN1START -- TAG-PUCCH-CONFIG-START PUCCH-Config ::= SEQUENCE { resourceSetToAddModList SEQUENCE (SIZE (1..maxNrofPUCCH-ResourceSets)) OF PUCCH-ResourceSet OPTIONAL, -- Need N resourceSetToReleaseList SEQUENCE (SIZE (1..maxNrofPUCCH-ResourceSets)) OF PUCCH-ResourceSetId OPTIONAL, -- Need N resourceToAddModList SEQUENCE (SIZE (1..maxNrofPUCCH-Resources)) OF PUCCH-Resource OPTIONAL, -- Need N resourceToReleaseList SEQUENCE (SIZE (1..maxNrofPUCCH-Resources)) OF PUCCH-ResourceId OPTIONAL, -- Need N format1 SetupRelease { PUCCH-FormatConfig } OPTIONAL, -- Need M format2 SetupRelease { PUCCH-FormatConfig } OPTIONAL, -- Need M format3 SetupRelease { PUCCH-FormatConfig } OPTIONAL, -- Need M format4 SetupRelease { PUCCH-FormatConfig } OPTIONAL, -- Need M schedulingRequestResourceToAddModList SEQUENCE (SIZE (1..maxNrofSR-Resources)) OF SchedulingRequestResourceConfig OPTIONAL, -- Need N schedulingRequestResourceToReleaseList SEQUENCE (SIZE (1..maxNrofSR-Resources)) OF SchedulingRequestResourceId OPTIONAL, -- Need N multi-CSI-PUCCH-ResourceList SEQUENCE (SIZE (1..2)) OF PUCCH-ResourceId OPTIONAL, -- Need M dl-DataToUL-ACK SEQUENCE (SIZE (1..8)) OF INTEGER (0..15) OPTIONAL, -- Need M spatialRelationInfoToAddModList SEQUENCE (SIZE (1..maxNrofSpatialRelationInfos)) OF PUCCH-SpatialRelationInfo OPTIONAL, -- Need N spatialRelationInfoToReleaseList SEQUENCE (SIZE (1..maxNrofSpatialRelationInfos)) OF PUCCH-SpatialRelationInfoId OPTIONAL, -- Need N pucch-PowerControl PUCCH-PowerControl OPTIONAL, -- Need M ..., [[ resourceToAddModListExt-v1610 SEQUENCE (SIZE (1..maxNrofPUCCH-Resources)) OF PUCCH-ResourceExt-v1610 OPTIONAL, -- Need N dl-DataToUL-ACK-r16 SetupRelease { DL-DataToUL-ACK-r16 } OPTIONAL, -- Need M ul-AccessConfigListDCI-1-1-r16 SetupRelease { UL-AccessConfigListDCI-1-1-r16 } OPTIONAL, -- Need M subslotLengthForPUCCH-r16 CHOICE { normalCP-r16 ENUMERATED {n2,n7}, extendedCP-r16 ENUMERATED {n2,n6} } OPTIONAL, -- Need R dl-DataToUL-ACK-DCI-1-2-r16 SetupRelease { DL-DataToUL-ACK-DCI-1-2-r16} OPTIONAL, -- Need M numberOfBitsForPUCCH-ResourceIndicatorDCI-1-2-r16 INTEGER (0..3) OPTIONAL, -- Need R dmrs-UplinkTransformPrecodingPUCCH-r16 ENUMERATED {enabled} OPTIONAL, -- Cond PI2-BPSK spatialRelationInfoToAddModListSizeExt-v1610 SEQUENCE (SIZE (1..maxNrofSpatialRelationInfosDiff-r16)) OF PUCCH-SpatialRelationInfo OPTIONAL, -- Need N spatialRelationInfoToReleaseListSizeExt-v1610 SEQUENCE (SIZE (1..maxNrofSpatialRelationInfosDiff-r16)) OF PUCCH-SpatialRelationInfoId OPTIONAL, -- Need N spatialRelationInfoToAddModListExt-v1610 SEQUENCE (SIZE (1..maxNrofSpatialRelationInfos-r16)) OF PUCCH-SpatialRelationInfoExt-r16 OPTIONAL, -- Need N spatialRelationInfoToReleaseListExt-v1610 SEQUENCE (SIZE (1..maxNrofSpatialRelationInfos-r16)) OF PUCCH-SpatialRelationInfoId-r16 OPTIONAL, -- Need N resourceGroupToAddModList-r16 SEQUENCE (SIZE (1..maxNrofPUCCH-ResourceGroups-r16)) OF PUCCH-ResourceGroup-r16 OPTIONAL, -- Need N resourceGroupToReleaseList-r16 SEQUENCE (SIZE (1..maxNrofPUCCH-ResourceGroups-r16)) OF PUCCH-ResourceGroupId-r16 OPTIONAL, -- Need N sps-PUCCH-AN-List-r16 SetupRelease { SPS-PUCCH-AN-List-r16 } OPTIONAL, -- Need M schedulingRequestResourceToAddModListExt-v1610 SEQUENCE (SIZE (1..maxNrofSR-Resources)) OF SchedulingRequestResourceConfigExt-v1610 OPTIONAL -- Need N ]], [[ format0-r17 SetupRelease { PUCCH-FormatConfig } OPTIONAL, -- Need M format2Ext-r17 SetupRelease { PUCCH-FormatConfigExt-r17 } OPTIONAL, -- Need M format3Ext-r17 SetupRelease { PUCCH-FormatConfigExt-r17 } OPTIONAL, -- Need M format4Ext-r17 SetupRelease { PUCCH-FormatConfigExt-r17 } OPTIONAL, -- Need M ul-AccessConfigListDCI-1-2-r17 SetupRelease { UL-AccessConfigListDCI-1-2-r17 } OPTIONAL, -- Need M mappingPattern-r17 ENUMERATED {cyclicMapping, sequentialMapping} OPTIONAL, -- Need R powerControlSetInfoToAddModList-r17 SEQUENCE (SIZE (1..maxNrofPowerControlSetInfos-r17)) OF PUCCH-PowerControlSetInfo-r17 OPTIONAL, -- Need N powerControlSetInfoToReleaseList-r17 SEQUENCE (SIZE (1..maxNrofPowerControlSetInfos-r17)) OF PUCCH-PowerControlSetInfoId-r17 OPTIONAL, -- Need N secondTPCFieldDCI-1-1-r17 ENUMERATED {enabled} OPTIONAL, -- Need R secondTPCFieldDCI-1-2-r17 ENUMERATED {enabled} OPTIONAL, -- Need R dl-DataToUL-ACK-r17 SetupRelease { DL-DataToUL-ACK-r17 } OPTIONAL, -- Need M dl-DataToUL-ACK-DCI-1-2-r17 SetupRelease { DL-DataToUL-ACK-DCI-1-2-r17} OPTIONAL, -- Need M ul-AccessConfigListDCI-1-1-r17 SetupRelease { UL-AccessConfigListDCI-1-1-r17 } OPTIONAL, -- Need M schedulingRequestResourceToAddModListExt-v1700 SEQUENCE (SIZE (1..maxNrofSR-Resources)) OF SchedulingRequestResourceConfigExt-v1700 OPTIONAL, -- Need N dmrs-BundlingPUCCH-Config-r17 SetupRelease { DMRS-BundlingPUCCH-Config-r17 } OPTIONAL, -- Need M dl-DataToUL-ACK-v1700 SetupRelease { DL-DataToUL-ACK-v1700 } OPTIONAL, -- Need M dl-DataToUL-ACK-MulticastDCI-Format4-1-r17 SetupRelease { DL-DataToUL-ACK-MulticastDCI-Format4-1-r17 } OPTIONAL, -- Need M sps-PUCCH-AN-ListMulticast-r17 SetupRelease { SPS-PUCCH-AN-List-r16 } OPTIONAL -- Need M ]] } PUCCH-FormatConfig ::= SEQUENCE { interslotFrequencyHopping ENUMERATED {enabled} OPTIONAL, -- Need R additionalDMRS ENUMERATED {true} OPTIONAL, -- Need R maxCodeRate PUCCH-MaxCodeRate OPTIONAL, -- Need R nrofSlots ENUMERATED {n2,n4,n8} OPTIONAL, -- Need S pi2BPSK ENUMERATED {enabled} OPTIONAL, -- Need R simultaneousHARQ-ACK-CSI ENUMERATED {true} OPTIONAL -- Need R } PUCCH-FormatConfigExt-r17 ::= SEQUENCE { maxCodeRateLP-r17 PUCCH-MaxCodeRate OPTIONAL, -- Need R ... } PUCCH-MaxCodeRate ::= ENUMERATED {zeroDot08, zeroDot15, zeroDot25, zeroDot35, zeroDot45, zeroDot60, zeroDot80} -- A set with one or more PUCCH resources PUCCH-ResourceSet ::= SEQUENCE { pucch-ResourceSetId PUCCH-ResourceSetId, resourceList SEQUENCE (SIZE (1..maxNrofPUCCH-ResourcesPerSet)) OF PUCCH-ResourceId, maxPayloadSize INTEGER (4..256) OPTIONAL -- Need R } PUCCH-ResourceSetId ::= INTEGER (0..maxNrofPUCCH-ResourceSets-1) PUCCH-Resource ::= SEQUENCE { pucch-ResourceId PUCCH-ResourceId, startingPRB PRB-Id, intraSlotFrequencyHopping ENUMERATED { enabled } OPTIONAL, -- Need R secondHopPRB PRB-Id OPTIONAL, -- Need R format CHOICE { format0 PUCCH-format0, format1 PUCCH-format1, format2 PUCCH-format2, format3 PUCCH-format3, format4 PUCCH-format4 } } PUCCH-ResourceExt-v1610 ::= SEQUENCE { interlaceAllocation-r16 SEQUENCE { rb-SetIndex-r16 INTEGER (0..4), interlace0-r16 CHOICE { scs15 INTEGER (0..9), scs30 INTEGER (0..4) } } OPTIONAL, --Need R format-v1610 CHOICE { interlace1-v1610 INTEGER (0..9), occ-v1610 SEQUENCE { occ-Length-v1610 ENUMERATED {n2,n4} OPTIONAL, -- Need M occ-Index-v1610 ENUMERATED {n0,n1,n2,n3} OPTIONAL -- Need M } } OPTIONAL, -- Need R ..., [[ format-v1700 SEQUENCE { nrofPRBs-r17 INTEGER (1..16) } OPTIONAL, -- Need R pucch-RepetitionNrofSlots-r17 ENUMERATED { n1,n2,n4,n8 } OPTIONAL -- Need R ]], [[ applyIndicatedTCI-State-r18 ENUMERATED {first, second, both} OPTIONAL, -- Need R multipanelSFN-Scheme-r18 ENUMERATED {enabled} OPTIONAL -- Need R ]] } PUCCH-ResourceId ::= INTEGER (0..maxNrofPUCCH-Resources-1) PUCCH-format0 ::= SEQUENCE { initialCyclicShift INTEGER(0..11), nrofSymbols INTEGER (1..2), startingSymbolIndex INTEGER(0..13) } PUCCH-format1 ::= SEQUENCE { initialCyclicShift INTEGER(0..11), nrofSymbols INTEGER (4..14), startingSymbolIndex INTEGER(0..10), timeDomainOCC INTEGER(0..6) } PUCCH-format2 ::= SEQUENCE { nrofPRBs INTEGER (1..16), nrofSymbols INTEGER (1..2), startingSymbolIndex INTEGER(0..13) } PUCCH-format3 ::= SEQUENCE { nrofPRBs INTEGER (1..16), nrofSymbols INTEGER (4..14), startingSymbolIndex INTEGER(0..10) } PUCCH-format4 ::= SEQUENCE { nrofSymbols INTEGER (4..14), occ-Length ENUMERATED {n2,n4}, occ-Index ENUMERATED {n0,n1,n2,n3}, startingSymbolIndex INTEGER(0..10) } PUCCH-ResourceGroup-r16 ::= SEQUENCE { pucch-ResourceGroupId-r16 PUCCH-ResourceGroupId-r16, resourcePerGroupList-r16 SEQUENCE (SIZE (1..maxNrofPUCCH-ResourcesPerGroup-r16)) OF PUCCH-ResourceId } PUCCH-ResourceGroupId-r16 ::= INTEGER (0..maxNrofPUCCH-ResourceGroups-1-r16) DL-DataToUL-ACK-r16 ::= SEQUENCE (SIZE (1..8)) OF INTEGER (-1..15) DL-DataToUL-ACK-r17 ::= SEQUENCE (SIZE (1..8)) OF INTEGER (-1..127) DL-DataToUL-ACK-v1700 ::= SEQUENCE (SIZE (1..8)) OF INTEGER (16..31) DL-DataToUL-ACK-DCI-1-2-r16 ::= SEQUENCE (SIZE (1..8)) OF INTEGER (0..15) DL-DataToUL-ACK-DCI-1-2-r17 ::= SEQUENCE (SIZE (1..8)) OF INTEGER (0..127) UL-AccessConfigListDCI-1-1-r16 ::= SEQUENCE (SIZE (1..16)) OF INTEGER (0..15) UL-AccessConfigListDCI-1-2-r17 ::= SEQUENCE (SIZE (1..16)) OF INTEGER (0..15) UL-AccessConfigListDCI-1-1-r17 ::= SEQUENCE (SIZE (1..3)) OF INTEGER (0..2) DL-DataToUL-ACK-MulticastDCI-Format4-1-r17 ::= SEQUENCE (SIZE (1..8)) OF INTEGER (0..15) -- TAG-PUCCH-CONFIG-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

4.23.7.3.2 Preparation phase

Figure 4.23.7.3.2-1: Inter NG-RAN node N2 based handover, preparation phase, with I-SMF insertion/change/removal 1. Steps 1-3 in clause 4.9.1.3.2 are performed. 2. For PDU sessions in the UE context, the Target AMF determines whether a (new) Target I-SMF needs to be selected based on Target UE location and service area of the SMF or of the old I-SMF. If Target I-SMF needs to be selected, the AMF selects a Target I-SMF as described in clause 5.34.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the UE moves from the service area of the I-SMF to the service area of the SMF, the I-SMF will be removed. The rest of steps are performed for PDU sessions requested to be handed over, i.e. the PDU Sessions with active UP connections. Case: I-SMF insertion, or I-SMF change, step 3~8 are skipped for I-SMF removal case. 3. T-AMF to Target I-SMF: Nsmf_PDUSession_CreateSMContext (PDU Session ID, Target ID, T-AMF ID, SM Context ID). The SM Context ID points to the source I-SMF in the case of I-SMF change or to SMF in the case of I-SMF insertion. Case: I-SMF change, steps 4 are skipped for I-SMF insertion case. 4a. (I-SMF change case) Target I-SMF to Source I-SMF: Target I-SMF retrieves SM Context from the source I-SMF by invoking Nsmf_PDUSession_Context Request (SM context type, SM Context ID). The Target I-SMF uses SM Context ID received from T-AMF for this service operation. SM context type indicates that the requested information is all SM context, i.e. PDN Connection Context and 5G SM context. The SM Context ID is used by the recipient of Nsmf_PDUSession_Context Request in order to determine the targeted PDU Session. 4b. Source I-SMF to Target I-SMF: Nsmf_PDUSession_Context Response. The source I-SMF responds with the requested SM context. Case: I-SMF insertion, steps 5 are skipped for I-SMF change case. 5a. Target I-SMF to SMF: Target I-SMF retrieves SM Context from the SMF by invoking Nsmf_PDUSession_Context Request (SM context type, SM Context ID). The Target I-SMF uses SM Context ID received from T-AMF for this service operation. SM context type indicates that the requested information is all SM context, i.e. PDN Connection Context and 5G SM context. The SM Context ID is used by the recipient of Nsmf_PDUSession_Context Request in order to determine the targeted PDU Session. 5b. Void. 5c. Void. 5d. SMF to Target I-SMF: Nsmf_PDUSession_Context Response.The SMF responds with the requested SM context. 6. The Target I-SMF selects a Target I-UPF: Based on the received SM context, e.g. S-NSSAI and UE location information, the Target I-SMF selects a Target I-UPF as described in clause 6.3.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 7a. The Target I-SMF to Target I-UPF: N4 Session Establishment Request. An N4 Session Establishment Request message is sent to the Target I-UPF, providing Packet detection, enforcement and reporting rules to be installed on the Target I-UPF. The UL CN Tunnel Info (on N9) of UPF (PSA) for this PDU Session, which is used to setup N9 tunnel, is also provided to the Target I-UPF. 7b. Target I-UPF to Target I-SMF or SMF: N4 Session Establishment Response. The Target I-UPF sends an N4 Session Establishment Response message to the Target I-SMF with DL CN Tunnel Info (i.e. N9 tunnel info) and UL CN Tunnel Info (i.e. N3 tunnel info). Case: I-SMF insertion, step 7c~7f are skipped for I-SMF change case. 7c. Target I-SMF to SMF: Nsmf_PDUSession_Create Request (PDU Session ID, HO Preparation Indication). 7d. [Conditional] SMF to UPF (PSA): N4 Session Modification Request. If different CN Tunnel Info need be used by PSA UPF, i.e. the CN Tunnel Info for N3 and N9 are different, the SMF request CN tunnel information from UPF. 7e. [Conditional] UPF(PSA) to SMF: N4 Session Modification Response. The UPF (PSA) sends an N4 Session Modification Response message to the SMF with CN Tunnel Info (on N9). 7f. SMF to Target I-SMF: Nsmf_PDUSession_Create Response (PDU Session ID, CN Tunnel Info of UPF(PSA) for N9). The Target I-SMF provides the CN Tunnel Info of UPF(PSA) for N9 to Target I-UPF via N4 Session Modification. 8. The Target I-SMF to T-AMF: Nsmf_PDUSession_CreateSMContext Response (PDU Session ID, N2 SM Information, Reason for non-acceptance). If N2 handover for the PDU Session is accepted, the Target I-SMF includes in the Nsmf_PDUSession_CreateSMContext Response the N2 SM Information containing the N3 UP address and the UL CN Tunnel ID of the UPF and the QoS parameters. Case: I-SMF removal, step 9~13 are skipped for I-SMF insertion, or I-SMF change case. 9. T-AMF to SMF: Nsmf_PDUSession_CreateSMContext (PDU Session ID, Target ID, T-AMF ID, SM Context ID). The SM Context ID points to the source I-SMF. 10. The SMF selects a Target I-UPF if the UE is not in the service area of the PDU Session Anchor UPF. The SMF selects a Target I-UPF as described in clause 6.3.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 11a. [Conditional] SMF to UPF(PSA): N4 Session Modification Request. If the Target I-UPF was not selected (i.e. the service area of PSA covers UE location) and different CN Tunnel Info (on N3) need to be used by PSA, the SMF sends N4 Session Modification Request to UPF(PSA). 11b. [Conditional] UPF(PSA) to SMF: N4 Session Modification Response. The PSA UPF sends UL CN Tunnel Info (i.e. N3 tunnel info) to SMF. 12a: [Conditional] SMF to Target I-UPF: N4 Session Establishment Request. If a Target I-UPF is selected by SMF in step 10, the SMF sends N4 Session Establishment Request to Target I-UPF. An N4 Session Establishment Request message is sent to the Target I-UPF, providing Packet detection, enforcement and reporting rules to be installed on the Target I-UPF. The UL CN Tunnel Info (on N9) of UPF (PSA) for this PDU Session, which is used to setup N9 tunnel, is also provided to the Target I-UPF. 12b. [Conditional]Target I-UPF to SMF: N4 Session Establishment Response. The Target I-UPF sends an N4 Session Establishment Response message to the SMF with DL CN Tunnel Info (i.e. N9 tunnel info) and UL CN Tunnel Info (i.e. N3 tunnel info). 13. SMF to T-AMF: Nsmf_PDUSession_CreateSMContext Response (PDU Session ID, N2 SM Information, Reason for non-acceptance). If N2 handover for the PDU Session is accepted, the Target I-SMF includes in the Nsmf_PDUSession_CreateSMContext Response the N2 SM Information containing the N3 UP address and the UL CN Tunnel ID of the UPF and the QoS parameters. 14. Same as step 8-10 clause 4.9.1.3.2 are performed. Case: I-SMF insertion, or I-SMF change, step 15~23 are skipped for I-SMF removal case. 15. T-AMF to Target I-SMF: Nsmf_PDUSession_UpdateSMContext Request (PDU Session ID, N2 SM response received from T-RAN). The Target I-SMF stores the N3 tunnel info of T-RAN from the N2 SM response if N2 handover is accepted by T-RAN. 16a. [Conditional]Target I-SMF to Target I-UPF: N4 Session modification request (T-RAN SM N3 forwarding Information list, indication to allocate DL forwarding tunnel(s) for indirect forwarding). Indirect forwarding may be performed via a UPF which is different from the Target I-UPF, in which case the Target I-SMF selects another UPF for indirect forwarding. 16b. [Conditional]Target I-UPF to Target I-SMF: N4 Session Modification Response (Target I-UPF N9 forwarding Information list). The Target I-UPF allocates Tunnel Info and returns an N4 Session Modification Response message to the Target I-SMF. The Target I-UPF SM N9 forwarding info list includes Target I-UPF N9 address, Target I-UPF N9 Tunnel identifiers for forwarding data. Case: I-SMF change, step 17~19 are skipped for I-SMF insertion case. 17. [Conditional]Target I-SMF to Source I-SMF: Nsmf_PDUSession_UpdateSMContext Request. Target I-SMF invokes Nsmf_PDUSession_UpdateSMContext Request (Target I-UPF SM N9 forwarding Information list, Operation type) to the source I-SMF in order to establish the indirect forwarding tunnel. The Target I-SMF uses the SM Context ID received from Target AMF for this service operation. The Operation type indicates the establishment of forwarding tunnel(s) for indirect forwarding. 18a. [Conditional]The source I-SMF initiates a N4 session modification request (Target I-UPF SM N9 forwarding Information list, indication to allocate DL forwarding tunnel(s) for indirect forwarding) to the source I-UPF to establish indirect forwarding tunnel. Indirect forwarding may be performed via a UPF which is different from the Source I-UPF. 18b. [Conditional]The source I-UPF to source I-SMF: N4 Session Modification Response (source I-UPF SM N3 forwarding Information list). 19. [Conditional]Source I-SMF to Target I-SMF: Nsmf_PDUSession_UpdateSMContext response (Source I-UPF SM N3 forwarding Information list). Case: I-SMF insertion, step 20~22 are skipped for I-SMF change case. 20. [Conditional]Target I-SMF to SMF: Nsmf_PDU Session_UpdateSMContext. The Target I-SMF invokes Nsmf_PDUSession_UpdateSMContext Request (Target I-UPF SM N9 forwarding Information list, Operation type) to the SMF in order to establish the indirect forwarding tunnel. The Target I-SMF uses the SM Context ID received from Target AMF for this service operation. The Operation type indicates the establishment of forwarding tunnel(s) for indirect forwarding. 21a. [Conditional]The SMF initiates a N4 session modification request (UPF SM N9 forwarding Information list, indication to allocate DL forwarding tunnel(s) for indirect forwarding) to the UPF(PSA) to establish indirect forwarding tunnel. Indirect forwarding may be performed via a UPF which is different from the UPF(PSA). 21b [Conditional] The UPF(PSA) to SMF: N4 Session Modification Response (UPF SM N3 forwarding Information list). 22. [Conditional] The SMF to Target I-SMF: Nsmf_PDUSession_UpdateSMContext response (UPF SM N3 forwarding Information list). 23. Target I-SMF to T-AMF: Nsmf_PDUSession_UpdateSMContext Response (N2 SM Information). Target I-SMF creates an N2 SM information containing the DL forwarding Tunnel Info to be sent to the S-RAN by Source AMF via the Target AMF. Target I-SMF includes this information in the Nsmf_PDUSession_UpdateSMContext response. The DL forwarding Tunnel Info can be one of the following information: - If direct forwarding applies, then Target I-SMF includes the T-RAN N3 forwarding information received in step 15. - If the indirect forwarding tunnel is setup, then the SMF includes Source I-UPF forwarding information containing the N3 UP address and the Tunnel ID of the Source I-UPF. Case: I-SMF removal, step 24~30 are skipped for I-SMF insertion, or I-SMF change case. 24. T-AMF to SMF: Nsmf_PDUSession_UpdateSMContext Request (PDU Session ID, N2 SM response received from T-RAN). The SMF stores the N3 tunnel info of T-RAN from the N2 SM response if N2 handover is accepted by T-RAN. 25a. [Conditional] SMF to UPF (PSA): N4 Session modification Request. If the Target I-UPF is not selected (i.e. the service area of PSA covers UE location), the SMF sends N4 Session modification request to UPF(PSA) to allocate DL forwarding tunnel(s). Indirect forwarding may be performed via a UPF which is different from the UPF(PSA), in which case the SMF selects another UPF for indirect forwarding. 25b. [Conditional] UPF (PSA) to SMF: N4 Session Modification Response (UPF N9 forwarding Information list). 26a. [Conditional] SMF to Target I-UPF: If the Target I-UPF is selected, the SMF sends N4 Session modification request to Target I-UPF to allocate DL forwarding tunnel(s) for indirect forwarding; Indirect forwarding may be performed via a UPF which is different from the Target I-UPF, in which case the SMF selects another UPF for indirect forwarding. 26b. [Conditional] Target I-UPF to SMF: N4 Session Modification Response (Target I-UPF N9 forwarding Information list). 27. [Conditional] SMF to Source I-SMF: Nsmf_PDUSession_UpdateSMContext. The SMF invokes Nsmf_PDUSession_UpdateSMContext Request (SM N9 forwarding Information list, Operation type) to the source I-SMF in order to establish the indirect forwarding tunnel. The SMF uses the SM Context ID received from T-AMF for this service operation. The Operation type indicates the establishment of forwarding tunnel(s) for indirect forwarding. 28a. [Conditional] Source I-SMF to Source I-UPF: N4 Session Modification Request. The source I-SMF initiates a N4 session modification request (Target I-UPF SM N9 forwarding Information list, indication to allocate DL forwarding tunnel(s) for indirect forwarding) to the source I-UPF to establish indirect forwarding tunnel. Indirect forwarding may be performed via a UPF which is different from the Source I-UPF. 28b. [Conditional]The source I-UPF to source I-SMF: N4 Session Modification Response (source I-UPF SM N3 forwarding Information list). 29. [Conditional]The source I-SMF to SMF: Nsmf_PDUSession_UpdateSMContext response (Source I-UPF SM N3 forwarding Information list). 30. SMF to T-AMF: Nsmf_PDUSession_UpdateSMContext Response (N2 SM Information). The SMF creates an N2 SM information containing the DL forwarding Tunnel Info to be sent to the S-RAN by the Source AMF via the Target AMF. The DL forwarding Tunnel Info can be one of the following information: - If direct forwarding applies, then the SMF includes the T-RAN N3 forwarding information the SMF received in step 24. - If the indirect forwarding tunnel is setup, then the SMF includes Source I-UPF forwarding information containing the N3 UP address and the Tunnel ID of the Source I-UPF. 31. Same as step 12 in clause 4.9.1.3.2 is performed.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.23.7.3.2

6.6.1.3 Exchange of protocol configuration options in other messages

The UE may include a Protocol configuration options IE or Extended protocol configuration options IE on EPS bearer context activation, EPS bearer context deactivation, EPS bearer context modification, PDN connectivity request, PDN disconnect request, bearer resource allocation request and bearer resource modification request if the UE wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the PDN GW or the SCEF. In particular, the UE may use this procedure on EPS bearer context activation to perform the MSISDN notification procedure as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13], clause 6.4. The PDN GW or the SCEF may include a Protocol configuration options IE or Extended protocol configuration options IE on EPS bearer context activation, EPS bearer context deactivation, EPS bearer context modification, PDN connectivity reject, PDN disconnect reject, bearer resource allocation reject and bearer resource modification reject if the PDN GW or the SCEF wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the UE. In particular, the PDN GW may use this procedure on EPS bearer context activation to perform the MSISDN notification procedure as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13], clause 6.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.6.1.3

4.2.1.1 Initial Messages

The UDP Destination Port number for GTPv2 Initial messages shall be 2123. It is the registered port number for GTP-C. The UDP Source Port for a GTPv2 Initial message is a locally allocated port number at the sending GTP entity. If GTPv2 and GTP' v2 modules are using the same IP address for sending messages, the implementation shall ensure that while some source port number is used by GTPv2 messages, the same source port number shall not be used by GTP' v2 messages. Otherwise, the IP interface may have difficulty to delivering a response message to the right protocol entity.

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

4.2.1.1

3.2 Symbols

For the purposes of the present document, the following symbols apply: BWChannel Channel bandwidth BWChannel,block Sub-block bandwidth, expressed in MHz. BWChannel,block= Fedge,block,high- Fedge,block,low. BWChannel_CA Aggregated channel bandwidth, expressed in MHz. BWGB Virtual guard band to facilitate transmitter (receiver) filtering above / below edge CCs. Transmitted energy per RE for reference symbols during the useful part of the symbol, i.e. excluding the cyclic prefix, (average power normalized to the subcarrier spacing) at the eNode B transmit antenna connector The averaged received energy per RE of the wanted signal during the useful part of the symbol, i.e. excluding the cyclic prefix, at the UE antenna connector; average power is computed within a set of REs used for the transmission of physical channels (including user specific RSs when present), divided by the number of REs within the set, and normalized to the subcarrier spacing F Frequency Fagg_alloc_low Aggregated Transmission Bandwidth Configuration. The lowest frequency of the simultaneously transmitted resource blocks. Fagg_alloc_high Aggregated Transmission Bandwidth Configuration. The highest frequency of the simultaneously transmitted resource blocks. FInterferer (offset) Frequency offset of the interferer (between the center frequency of the interferer and the carrier frequency of the carrier measured) FInterferer Frequency of the interferer FIoffset Frequency offset of the interferer (between the center frequency of the interferer and the closest edge of the carrier measured) FC Frequency of the carrier centre frequency FC_agg Aggregated Transmission Bandwidth Configuration. Center frequency of the aggregated carriers. FC,block, high Center frequency of the highest transmitted/received carrier in a sub-block. FC,block, low Center frequency of the lowest transmitted/received carrier in a sub-block. FC_low The centre frequency of the lowest carrier, expressed in MHz. FC_high The centre frequency of the highest carrier, expressed in MHz. FDL_low The lowest frequency of the downlink operating band FDL_high The highest frequency of the downlink operating band FUL_low The lowest frequency of the uplink operating band FUL_high The highest frequency of the uplink operating band Fedge,block,low The lower sub-block edge, where Fedge,block,low = FC,block,low - Foffset. Fedge,block,high The upper sub-block edge, where Fedge,block,high = FC,block,high + Foffset. Fedge_low The lower edge of aggregated channel bandwidth, expressed in MHz. Fedge_high The higher edge of aggregated channel bandwidth, expressed in MHz. Foffset Frequency offset from FC_high to the higher edge or FC_low to the lower edge. Foffset,block,low Separation between lower edge of a sub-block and the center of the lowest component carrier within the sub-block Foffset,block,high Separation between higher edge of a sub-block and the center of the highest component carrier within the sub-block Foffset_NS_23 Frequency offset in MHz needed if NS_23 is used FOOB The boundary between the E-UTRA out of band emission and spurious emission domains. The power spectral density of the total input signal (power averaged over the useful part of the symbols within the transmission bandwidth configuration, divided by the total number of RE for this configuration and normalised to the subcarrier spacing) at the UE antenna connector, including the own-cell downlink signal The total transmitted power spectral density of the own-cell downlink signal (power averaged over the useful part of the symbols within the transmission bandwidth configuration, divided by the total number of RE for this configuration and normalised to the subcarrier spacing) at the eNode B transmit antenna connector The total received power spectral density of the own-cell downlink signal (power averaged over the useful part of the symbols within the transmission bandwidth configuration, divided by the total number of RE for this configuration and normalised to the subcarrier spacing) at the UE antenna connector The received power spectral density of the total noise and interference for a certain RE (average power obtained within the RE and normalized to the subcarrier spacing) as measured at the UE antenna connector LCRB Transmission bandwidth which represents the length of a contiguous resource block allocation expressed in units of resources blocks LCtone Transmission bandwidth which represents the length of a contiguous sub-carrier allocation expressed in units of tones Ncp Cyclic prefix length NDL Downlink EARFCN The power spectral density of a white noise source (average power per RE normalised to the subcarrier spacing), simulating interference from cells that are not defined in a test procedure, as measured at the UE antenna connector The power spectral density of a white noise source (average power per RE normalized to the subcarrier spacing), simulating interference in non-CRS symbols in ABS subframe from cells that are not defined in a test procedure, as measured at the UE antenna connector. The power spectral density of a white noise source (average power per RE normalized to the subcarrier spacing), simulating interference in CRS symbols in ABS subframe from all cells that are not defined in a test procedure, as measured at the UE antenna connector. The power spectral density of a white noise source (average power per RE normalised to the subcarrier spacing), simulating interference in non-ABS subframe from cells that are not defined in a test procedure, as measured at the UE antenna connector The power spectral density (average power per RE normalised to the subcarrier spacing) of the summation of the received power spectral densities of the strongest interfering cells explicitly defined in a test procedure plus , as measured at the UE antenna connector. The respective power spectral density of each interfering cell relative to is defined by its associated DIP value, or the respective power spectral density of each interfering cell relative to is defined by its associated Es/Noc value. NOffs-DL Offset used for calculating downlink EARFCN NOffs-UL Offset used for calculating uplink EARFCN The power spectral density of a white noise source (average power per RE normalised to the subcarrier spacing) simulating eNode B transmitter impairments as measured at the eNode B transmit antenna connector NRB Transmission bandwidth configuration, expressed in units of resource blocks NRB_agg The number of the aggregated RBs within the fully allocated Aggregated Channel bandwidth. NRB_alloc Total number of simultaneously transmitted resource blocks in Channel bandwidth or Aggregated Channel Bandwidth. NRB,c The transmission bandwidth configuration of component carrier c, expressed in units of resource blocks NRB,largest BW The largest transmission bandwidth configuration of the component carriers in the bandwidth combination, expressed in units of resource blocks NRX Number of receiver antennas Ntone Transmission bandwidth configuration for category NB1 and NB2, expressed in units of tones. Ntone 3.75kHz Transmission bandwidth configuration for category NB1 and NB2 with 3.75 kHz sub-carrier spacing, expressed in units of tones. Ntone 15kHz Transmission bandwidth configuration for category NB1 and NB2 with 15 kHz sub-carrier spacing, expressed in units of tones. NUL Uplink EARFCN. Rav Minimum average throughput per RB. PCMAX The configured maximum UE output power. PCMAX, c The configured maximum UE output power for serving cell c. PEMAX Maximum allowed UE output power signalled by higher layers. Same as IE P-Max, defined in [7]. PEMAX, c Maximum allowed UE output power signalled by higher layers for serving cell c. Same as IE P-Max, defined in [7]. PInterferer Modulated mean power of the interferer PPowerClass PPowerClass is the nominal UE power (i.e., no tolerance). PPowerClass_Default PPowerClass_Default is the default nominal UE power (i.e., no tolerance) for the band. PUMAX The measured configured maximum UE output power. Puw Power of an unwanted DL signal Pw Power of a wanted DL signal RBstart Indicates the lowest RB index of transmitted resource blocks. RBend Indicates the highest RB index of transmitted resource blocks. Tno_hopping Transmission period within a TTI duration when consecutive symbols are transmitted without applying any frequency hopping ΔfOOB Δ Frequency of Out Of Band emission. ΔPPowerClass Adjustment to maximum output power for a given power class. ΔRIB,c Allowed reference sensitivity relaxation due to support for inter-band CA operation, for serving cell c. ΔRIB,4R Reference sensitivity adjustment due to support for 4 antenna ports. ΔRIB,8R Reference sensitivity adjustment due to support for 8 antenna ports. ΔTIB,c Allowed maximum configured output power relaxation due to support for inter-band CA operation, for serving cell c. TC Allowed operating band edge transmission power relaxation. TC,c Allowed operating band edge transmission power relaxation for serving cell c. TProSe Allowed operating band transmission power relaxation due to support of E-UTRA ProSe on an operating band. According to Clause 5.2 in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [6] According to Clause 5.2 in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [6] Test specific auxiliary variable used for the purpose of downlink power allocation, defined in Annex C.3.2. Wgap Sub-block gap size Wgap_L Sub-block gap size between lowest two CCs in frequency domain on CA_X-X-X Wgap_H Sub-block gap size between highest two CCs in frequency domain on CA_X-X-X

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

3.2

5.14.2.2 Routing

The following description applies to all the Configuration Transfer messages used for the exchange of the E-UTRAN transparent container. The source RAN node sends a message to its MME including the source and destination addresses. The MME uses the destination address to route the message encapsulated in a GTPv2 message to the correct MME via the S10 interface (see TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [43]). The MME connected to the target eNodeB decides which RAN node to send the message to, based on the destination address. For Dual Connectivity with E-UTRAN as Master RAN node and NR as Secondary RAN node as defined in TS 37.340[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 ] [85], target eNodeB decides which candidate en-gNB to send the message to, based on the destination address.

3GPP TS 23.401

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

SA WG2

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

5.14.2.2

5.6.15 Triggers for network analytics

Triggers for the SMF to request for or subscribe to the analytics information from the NWDAF are internal logic may include for example: - UE PDU Session related event subscription by other NFs (e.g. AMF, NEF); - UE access and mobility event reports from the AMF; - locally detected events; - analytics information received. The trigger conditions may depend on operator and implementation policy in the SMF. When a trigger condition happens, the SMF may decide if any analytics information is needed and if so, request for or subscription to the analytics information from the NWDAF. The SMF may, upon detection of certain local events, e.g. number of PDU sessions establishment or released reaches a threshold in a specific area, request for or subscribe to network analytics related to "Abnormal behaviour" as described in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [86] to detect whether there are any exceptional UE behaviours in this area.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.6.15

5.27.4 Hold and Forward Buffering mechanism

DS-TT ports and NW-TT ports support a hold and forward mechanism to schedule traffic as defined in IEEE Std 802.1Q [98] if 5GS is to participate transparently as a bridge in a TSN network. That is, the hold and forward buffering mechanism in this release of the specification provides externally observable behaviour identical to scheduled traffic with up to eight queues (clause 8.6.8.4 in IEEE Std 802.1Q [98]) and with protected windows (Annex Q.2 in IEEE Std 802.1Q [98]). Frames are only transmitted from a given buffer according to the open time interval of the corresponding transmission gate; otherwise, frames are hold back (which corresponds to a closed transmission gate). The protected windows scheme implies that only a single transmission gate is open at any single time. Thus, the Hold and Forward buffering mechanism allows PDB based 5GS QoS to be used for TSC traffic. For Ethernet frames that contain a VLAN tag, DS-TT and NW-TT determine the priority based on the PCP value contained in the VLAN tag. For Ethernet frames that do not contain a VLAN tag, DS-TT and NW-TT apply a priority value of 0. To achieve externally observable behaviour according to the protected windows scheme, 5GS provides AdminControlList, AdminBaseTime, AdminCycleTime and TickGranularity as defined in IEEE Std 802.1Q [98] on a per Ethernet port basis to DS-TT and NW-TT for the hold and forward buffering mechanism as described in clause 5.28.3. NOTE: The details of how Hold and Forward buffering mechanism is provided by the DS-TT and NW-TT is up to implementation.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.27.4

9.3.9.1 Facility (network to mobile station direction)

This message is sent by the network to the mobile station to request or acknowledge a supplementary service. The supplementary service to be invoked and its associated parameters are specified in the facility information element. See table 9.62a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Message type: FACILITY Significance: local (NOTE 1) Direction: network to mobile station Table 9.62a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : FACILITY message content (network to mobile station direction) NOTE 1: This message has local significance; however, it may carry information of global significance. NOTE 2: The facility information element has no upper length limit except that given by the maximum number of octets in a L3 message, see 3GPP TS 44.006[ None ] [19].

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

– SL-FreqSelectionConfig

The IE SL-FreqSelectionConfig specifies the configuration information for carrier selection for NR sidelink transmission using UE autonomous resource selection. SL-FreqSelectionConfig information element -- ASN1START -- TAG-SL-FREQSELECTIONCONFIG-START SL-FreqSelectionConfig-r18 ::= SEQUENCE { sl-priorityList-r18 SEQUENCE (SIZE (1..8)) OF INTEGER (1..8), sl-threshCBR-FreqReselection-r18 SL-CBR-r16 OPTIONAL, -- Need R sl-threshCBR-FreqKeeping-r18 SL-CBR-r16 OPTIONAL -- Need R } -- TAG-SL-FREQSELECTIONCONFIG-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

16a.4.2 AAA Command

The AAA command, defined in Diameter NASREQ (IETF RFC 7155 [120]), is indicated by the Command-Code field set to 265 and the ‘R’ bit cleared in the Command Flags field., It is sent by the Diameter server to the GGSN/P-GW in response to the AAR command. The relevant AVPs that are of use for the Gi/Sgi interface are detailed in the ABNF description below. Other valid AVPs for this command are not used for Gi/Sgi purposes and should be ignored by the receiver or processed according to the relevant specifications. The "Tunneling" AVP may include the "Tunnel-Type" with value 3 to represent L2TP tunnel type, "Tunnel-Medium-Type" and "Tunnel-Server-Endpoint" AVPs. If more than one set of these "Tunneling" AVPs are provided, the optional "Tunnel-Preference" AVP may be provided in each set to identify the relative preference. The Tunnel-Password AVP may be used to authenticate to a remote server. NOTE: The other optional AVPs within the "Tunneling" AVPs not listed in the above description, can be referred to the IETF RFC 7155 [120] with implementation specific. The bold marked AVPs in the message format indicate optional AVPs for Gi/Sgi, or modified existing AVPs. Message Format: <AA-Answer> ::= < Diameter Header: 265, PXY > < Session-Id > { Auth-Application-Id } { Auth-Request-Type } { Result-Code } { Origin-Host } { Origin-Realm } [ User-Name ] [ Service-Type ] * [ Class ] [ Acct-Interim-Interval ] [ Error-Message ] [ Error-Reporting-Host ] [ Failed-AVP ] [ Idle-Timeout ] [ Authorization-Lifetime ] [ Auth-Grace-Period ] [ Auth-Session-State ] [ Re-Auth-Request-Type ] [ Multi-Round-Time-Out ] [ Session-Timeout ] * [ Reply-Message ] [ Origin-State-Id ] * [ Filter-Id ] [ Port-Limit ] [ Prompt ] [ Callback-Id ] [ Callback-Number ] * [ Framed-Compression ] [ Framed-Interface-Id ] [ Framed-IP-Address ] * [ Framed-IPv6-Prefix ] [ Framed-IPv6-Pool ] * [ Framed-IPv6-Route ] * [ Delegated-IPv6-Prefix ] [ Framed-IP-Netmask ] * [ Framed-Route ] [ Framed-Pool ] [ Framed-IPX-Network ] [ Framed-MTU ] [ Framed-Protocol ] [ Framed-Routing ] * [ Login-IP-Host ] * [ Login-IPv6-Host ] [ Login-LAT-Group ] [ Login-LAT-Node ] [ Login-LAT-Port ] [ Login-LAT-Service ] [ Login-Service ] [ Login-TCP-Port ] * [ NAS-Filter-Rule ] * [ QoS-Filter-Rule ] * [ Tunneling ] * [ Redirect-Host ] [ Redirect-Host-Usage ] [ Redirect-Max-Cache-Time ] * [ Proxy-Info ] [ 3GPP-IPv6-DNS-Servers ] * [ External-Identifier] * [ 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.4.2

5.8.2.14 Inter PLMN User Plane Security functionality

Operators can deploy UPF(s) supporting the Inter PLMN User Plane Security (IPUPS) functionality at the border of their network to protect their networks from invalid inter PLMN N9 traffic. The IPUPS functionality forwards GTP-U packets (received via the N9 interface) only if they belong to an active PDU Session and are not malformed, as described in TS 33.501[ Security architecture and procedures for 5G System ] [29]. The SMF can activate the IPUPS functionality together with other UP functionality in the same UPF, or insert a separate UPF in the UP path for the IPUPS functionality. In both cases the UPF with IPUPS functionality is controlled by the SMF via the N4 interface.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.8.2.14

– Alpha

The IE Alpha defines possible values of a the pathloss compensation coefficient for uplink power control. Value alpha0 corresponds to the value 0, Value alpha04 corresponds to the value 0.4, Value alpha05 corresponds to the value 0.5 and so on. Value alpha1 corresponds to value 1. See also clause 7.1 of TS 38.213[ NR; Physical layer procedures for control ] [13]. -- ASN1START -- TAG-ALPHA-START Alpha ::= ENUMERATED {alpha0, alpha04, alpha05, alpha06, alpha07, alpha08, alpha09, alpha1} -- TAG-ALPHA-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

6.2.1 Key hierarchy

Requirements on 5GC and NG-RAN related to keys are described in clause 5.1.3. The following describes the keys of the key hierarchy generation in a 5GS in detail.: Figure 6.2.1-1: Key hierarchy generation in 5GS The keys related to authentication (see Figure 6.2.1-1) include the following keys: K, CK/IK. In case of EAP-AKA', the keys CK', IK' are derived from CK, IK as specified in clause 6.1.3.1. The key hierarchy (see Figure 6.2.1-1) includes the following keys: KAUSF, KSEAF, KAMF, KNASint, KNASenc, KN3IWF, KgNB, KRRCint, KRRCenc, KUPint and KUPenc. Keys for AUSF in home network: - KAUSF is a key derived - by ME and AUSF from CK', IK' in case of EAP-AKA', CK' and IK' is received by AUSF as a part of transformed AV from ARPF; or, - by ME and ARPF from CK, IK in case of 5G AKA, KAUSF is received by AUSF as a part of the 5G HE AV from ARPF. - KSEAF is an anchor key derived by ME and AUSF from KAUSF. KSEAF is provided by AUSF to the SEAF in the serving network. Key for AMF in serving network: - KAMF is a key derived by ME and SEAF from KSEAF. KAMF is further derived by ME and source AMF when performing horizontal key derivation. Keys for NAS signalling: - KNASint is a key derived by ME and AMF from KAMF, which shall only be used for the protection of NAS signalling with a particular integrity algorithm. - KNASenc is a key derived by ME and AMF from KAMF, which shall only be used for the protection of NAS signalling with a particular encryption algorithm. Key for NG-RAN: - KgNB is a key derived by ME and AMF from KAMF. KgNB is further derived by ME and source gNB when performing horizontal or vertical key derivation. The KgNB is used as KeNB between ME and ng-eNB. Keys for UP traffic: - KUPenc is a key derived by ME and gNB from KgNB, which shall only be used for the protection of UP traffic with a particular encryption algorithm. - KUPint is a key derived by ME and gNB from KgNB, which shall only be used for the protection of UP traffic between ME and gNB with a particular integrity algorithm. Keys for RRC signalling: - KRRCint is a key derived by ME and gNB from KgNB, which shall only be used for the protection of RRC signalling with a particular integrity algorithm. - KRRCenc is a key derived by ME and gNB from KgNB, which shall only be used for the protection of RRC signalling with a particular encryption algorithm. Intermediate keys: - NH is a key derived by ME and AMF to provide forward security as described in Clause A.10. - KNG-RAN * is a key derived by ME and NG-RAN (i.e., gNB or ng-eNB) when performing a horizontal or vertical key derivation as specified in Clause 6.9. 2.1.1 using a KDF as specified in Clause A.11/A.12. - KAMF' is a key that can be derived by ME and AMF when the UE moves from one AMF to another during inter-AMF mobility as specified in Clause 6.9.3 using a KDF as specified in Annex A.13. Key for the non-3GPP access: - KN3IWF is a key derived by ME and AMF from KAMF for the non-3GPP access. KN3IWF is not forwarded between N3IWFs. NOTE 1: The key hierarchy for standalone non-public networks when an authentication method other than 5G AKA or EAP-AKA' is used is given in Annex I.2.3.

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

6.2.1

8.100 TWAN Identifier

The TWAN Identifier is used for reporting UE location in a Trusted WLAN Access Network (TWAN). See 3GPP TS 23.402[ Architecture enhancements for non-3GPP accesses ] [45]. TWAN Identifier shall be coded as depicted in Figure 8.100-1. Figure 8.100-1: TWAN Identifier The BSSID and SSID shall be encoded as described in IEEE Std 802.11-2012 [52]. The TWAN identifier shall contain the SSID and, unless otherwise determined by the TWAN operator's policies, it shall contain at least the BSSID, the civic address of the access point to which the UE is attached or the Circuit-ID with the identity of the Relay (e.g. TWAG) which has allocated it (see clause 16.1.7 of 3GPP TS 23.402[ Architecture enhancements for non-3GPP accesses ] [45]). It may also contain the identifier of the TWAN operator, i.e. either the TWAN PLMN-ID if the TWAN is operated by a mobile operator or the TWAN Operator Name otherwise. The SSID Length in octet '6' indicates the length of the SSID field. The SSID is an Octet String which shall have a maximum length of 32 octets (see IEEE Std 802.11-2012 [52]). The BSSIDI flag in octet 5 indicates whether the BSSID in octets 'k+1' to 'k+6' shall be present. If BSSIDI is set to '1', then the BSSID shall be present. If BSSIDI is set to '0', then the BSSID shall not be present. The BSSID is an Octet String which shall be 6 octets long (see IEEE Std 802.11-2012 [52]). The CIVAI flag in octet 5 indicates whether the Civic Address Length and Civic Address Information in octets 'q' and 'q+1' to 'q+r' shall be present. The Civic Address Length and Information shall be present if and only if the CIVAI flag is set to 1. When present, the Civic Address Information shall contain the civic address of the Access Point to which the UE is attached and it shall be encoded as defined in clause 3.1 of IETF RFC 4776 [59] excluding the first 3 octets. The PLMNI flag in octet 5 indicates whether the TWAN PLMN-ID in octets 's' to 's+2' shall be present. The TWAN PLMN-ID shall be present if and only if the PLMNI flag is set to 1. The TWAN PLMN-ID shall be encoded as octets 5 to 7 of the Serving Network IE in clause 8.18. When present, the TWAN PLMN-ID shall indicate the PLMN-ID of the TWAN operator. NOTE: the PLMN ID contained in the TWAN PLMN-ID can differ from the PLMN ID in the Serving Network IE. The OPNAI flag in octet 5 indicates whether the TWAN Operator Name Length and TWAN Operator Name in octets 't' and 't+1' to 't+u' shall be present. The TWAN Operator Name Length and TWAN Operator Name shall be present if and only if the OPNAI flag is set to 1. The TWAN Operator Name shall be encoded as specified in clause 19. 8 of 3GPP TS 23.003[ Numbering, addressing and identification ] [2]. When present, the TWAN Operator Name shall indicate the identifier of the TWAN operator. The LAII flag in octet 5 indicates whether the Logical Access ID information is present in the TWAN Identifier IE. The Logical Access ID is encoded by the Relay Identity information in octets 'v' to 'v+w' and the Circuit-ID information in octets 'x' to 'x+y'. The Relay Identity information and the Circuit-ID information shall be present if the LAII flag is set to '1'. The Relay indicates a DHCP relay agent as defined in IETF RFC 3046 [60]. The Relay Identity Type indicates the type of the Relay Identity as described in Table 8.100-1. The Relay Identity Length indicates the length of the Relay Identity. In case the Relay Identity Type indicates an IP address, the length indicates if it is IPv4 or IPv6 address of the Relay. The length is 4 octets for IPv4 and 16 octets for IPv6. If the Relay Identity type is set to 1 (i.e. an FQDN), it is encoded as described in clause 3.1 of IETF RFC 1035 [31] but excluding the trailing zero byte. The Circuit-ID length indicates the length of the Circuit-ID. The Circuit-ID is as defined in IETF RFC 3046 [60], it is encoded as an Octetstring and provided by the Relay. Table 8.100-1: Relay Identity Type

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

19.4.2.9A ePDG FQDN for emergency bearer services 19.4.2.9A.1 General

The ePDG FQDN used for the selection of an ePDG supporting emergency bearer services shall be constructed using one of the following formats, as specified in clause 4.5.4a of 3GPP TS 23.402[ Architecture enhancements for non-3GPP accesses ] [68] and 3GPP TS 24.302[ Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networks; Stage 3 ] [77]: - an Operator Identifier based Emergency ePDG FQDN; - a Tracking/Location Area Identity based Emergency ePDG FQDN; - an Emergency ePDG FQDN configured in the UE by the HPLMN, which may have a different format than the one specified in the following clause. The Visited Country Emergency FQDN is used by a roaming UE, in the context of an emergency session, to determine whether the visited country mandates the selection of an ePDG in this country. The Visited Country Emergency FQDN shall be constructed as specified in clause 19.4.2.9A.4. The Replacement field used in DNS-based Discovery of regulatory requirements shall be constructed as specified in clause 19.4.2.9A.5. The Visited Country Emergency Numbers FQDN is used by a roaming UE to determine the list of emergency numbers and related emergency service types in the the visited country.

3GPP TS 23.003

Numbering, addressing and identification

CT WG4

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

19.4.2.9A

6.4.8 Initialisation of synchronisation for ciphering and integrity protection

The ciphering and integrity protection algorithms are driven by counters (COUNT-C and COUNT-I) that at connection establishment need to be initialised. For that purpose the ME and the USIM have the ability to store a START value. The ME and the USIM store a STARTCS value for the CS cipher/integrity keys and a STARTPS value for the PS cipher/integrity keys. The length of START is 20 bits. The ME only contains (valid) START values when it is powered-on and a USIM is inserted. When the ME is powered-off or the USIM is removed, the ME deletes its START values and the Kc128 if one was derived. After power-on or insertion of a USIM, the USIM sends its START values to the ME, and the ME stores them. At radio connection establishment for a particular serving network domain (CS or PS) the ME sends the STARTCS and the STARTPS value to the RNC in the RRC connection setup complete message. The ME and the RNC initialise the 20 most significant bits of the RRC HFN (for integrity protection), the RLC HFN (for ciphering) and the MAC-d HFN (for ciphering) to the START value of the corresponding service domain; the remaining bits are initialised to 0. Also the RRC SN (for integrity protection) and the RLC SN (for ciphering) are initialised to 0. During an ongoing radio connection, the STARTCS value in the ME and in the SRNC is defined as the 20 most significant bits of the maximum of all current COUNT-C and COUNT-I values for all signalling radio bearers and CS user data radio bearers protected using CKCS and/or IKCS, incremented by2, i.e.: STARTCS' = MSB20 ( MAX {COUNT-C, COUNT-I | all radio bearers (including signalling) protected with CKCS and IKCS}) +2. - If current STARTCS < STARTCS' then STARTCS = STARTCS', otherwise STARTCS is unchanged. Likewise, during an ongoing radio connection, the STARTPS value in the ME and in the SRNC is defined as the 20 most significant bits of the maximum of all current COUNT-C and COUNT-I values for all signalling radio bearers and PS user data radio bearers protected using CKPS and/or IKPS, incremented by2, i.e.: STARTPS' = MSB20 ( MAX {COUNT-C, COUNT-I | all radio bearers (including signalling) protected with CKPS and IKPS}) +2. - If current STARTPS < STARTPS' then STARTPS = STARTPS', otherwise STARTPS is unchanged. If any of the COUNT-C or COUNT-I assigned to the radio bearers of the same CN domain reaches its maximum value, the ME and SRNC shall set START of the corresponding CN domain to its maximum value. The handling of the START values for new keys obtained from an authentication and key agreement run is described in clause 4.1.1.8 of TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [35] and clause 8.1.12.3.1 of TS 25.331[ None ] [17].

3GPP TS 33.102

3G security; Security architecture

SA WG3

3GPP Series : 33 , Security aspects

6.4.8

5.39 Remote provisioning of credentials for NSSAA or secondary authentication/authorization 5.39.1 General

The UE's subscribed network (i.e. HPLMN, or subscribed SNPN) may provide functionalities to provision or update the credentials used for NSSAA or credentials used for secondary authentication/authorization to the UE. The provisioning procedure is supported via User Plane. For User Plane Remote Provisioning, the UE establishes a PDU Session that is used for remote provisioning, e.g. by using DNN(s)/S-NSSAI(s) which can access the PVS. The AMF selects an SMF used for remote provisioning using the SMF discovery and selection functionality as described in clause 6.3.2. If the SMF is configured with the PVS address(es) and/or PVS FQDN(s), the SMF shall send the PVS address(es) and/or PVS FQDN(s) per DNN/S-NSSAI to the UE via PCO during PDU Session Establishment procedure, based on the UE's subscribed DNN(s)/S-NSSAI(s) and the UE's request of PVS information from the network. Alternatively, the UE may be configured with an address of a PVS or the PVS may subscribe for UE Reachability Notification and may use the Application Triggering procedure as specified in TS 23.502[ Procedures for the 5G System (5GS) ] [3] to trigger the UE to initiate the setup of a connection for remote provisioning.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.39

9.9.4.20 Remote UE context list

The purpose of the Remote UE context list information element is to provide identity and optionally IP address of a remote UE connected to, or disconnected from, a UE acting as a ProSe UE-to-network relay. The Remote UE context list information element is coded as shown in figure 9.9.4.20.1 and table 9.9.4.20.1. The Remote UE context list is a type 6 information element with a minimum length of 5 octets and a maximum length of 65538 octets. Figure 9.9.4.20.1: Remote UE context list Table 9.9.4.20.1: Remote UE context list Figure 9.9.4.20.2: Remote UE context Table 9.9.4.20.2: Remote UE context list information element

3GPP TS 24.301

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

CT WG1

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

9.9.4.20

6.2.9.2 URSP

The URSP requires interaction between upper layers and the 5GSM entities in the UE (see 3GPP TS 24.526[ User Equipment (UE) policies for 5G System (5GS); Stage 3 ] [19] for further details). Each of the 5GSM entities in the UE shall indicate attributes (e.g. PDU session identity, SSC mode, S-NSSAI, DNN, PDU session type, access type, PDU address) of a newly established PDU session to the upper layers. If a PDU session is released, the 5GSM entity handling the PDU session shall inform the PDU session identity of the released PDU session to the upper layers. The upper layers may request a 5GSM entity: a) to establish a PDU session indicating one or more PDU session attributes; b) to release an existing PDU session; or c) to establish a PDU session indicating one or more PDU session attributes, and to release an existing PDU session.

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

4.1.1.2 Successful RRC connection establishments

1) This measurement provides the number of successful RRC establishments for each establishment cause. 2) CC 3) Receipt by the eNodeB/RN of an RRCConnectionSetupComplete message following a RRC connection establishment request. Each RRCConnectionSetupComplete message received is added to the relevant per establishment cause measurement. The possible causes are included in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]. The sum of all supported per cause measurements shall equal the total number of successful RRC Connection Establishments. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first. 4) Each measurement is an integer value. The number of measurements is equal to the number of causes plus a possible sum value identified by the .sum suffix. 5) The measurement name has the form RRC.ConnEstabSucc.Cause where Cause identifies the establishment cause. 6) EUtranCellFDD EUtranCellTDD 7) Valid for packet switched traffic 8) EPS

3GPP TS 32.425

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

SA WG5

3GPP Series : 32 , OAM&P and Charging

4.1.1.2

5.3.14.4 T302, T390 expiry or stop (Barring alleviation)

The UE shall: 1> if timer T302 expires or is stopped: 2> for each Access Category for which T390 is not running: 3> consider the barring for this Access Category to be alleviated: 1> else if timer T390 corresponding to an Access Category other than '2' expires or is stopped, and if timer T302 is not running: 2> consider the barring for this Access Category to be alleviated; 1> else if timer T390 corresponding to the Access Category '2' expires or is stopped: 2> consider the barring for this Access Category to be alleviated; 1> when barring for an Access Category is considered being alleviated: 2> if the Access Category was informed to upper layers as barred: 3> inform upper layers about barring alleviation for the Access Category. 2> else if the Access Category is Access Category '0': 3> perform actions specified in 5.3.13.1d; 2> if barring is alleviated for Access Category '8'; or 2> if barring is alleviated for Access Category '2': 3> perform actions specified in 5.3.13.8;

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

5.3.14.4

4.3.5.9 Voice domain preference and UE's usage setting

If the UE supports CS fallback, or the UE is configured to support IMS voice, or both, the UE shall include the information element "Voice domain preference and UE's usage setting" in Attach Request, Tracking Area Update Request and Routing Area Update Request messages. The purpose of this information element is to signal to the network the UE's usage setting and voice domain preference for E-UTRAN. The UE's usage setting indicates whether the UE behaves in a voice centric or data centric way (as defined in TS 23.221[ Architectural requirements ] [27]). The voice domain preference for E-UTRAN indicates whether the UE is configured as CS Voice only, CS Voice preferred and IMS PS Voice as secondary, IMS PS Voice preferred and CS Voice as secondary, or IMS PS Voice only (as defined in TS 23.221[ Architectural requirements ] [27]). In this Release of the specifications, inter-RAT mobility to/from the NB-IoT RAT is not supported, and GBR bearers are not supported in the NB-IoT RAT. Hence the UE should not include the "Voice domain preference and UE's usage setting" IE when sending an Attach Request or Tracking Area Update Request on the NB-IoT RAT. NOTE: Depending on operator's configuration, the UE's usage setting and voice domain preference for E-UTRAN can be used by the network to choose the RFSP Index in use (see clause 4.3.6). As an example, this enables the enforcement of selective idle mode camping over GERAN/UTRAN for voice centric UEs relying on CS Fallback for voice support in E-UTRAN.

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

– ChildIE2-WithoutEM

The IE ChildIE2-WithoutEM is an example of a lower level IE, typically used to control certain radio configurations. The example illustrates how the new field chIE1-NewField is added in release N to the configuration of the configurable feature. ChildIE2-WithoutEM information element -- /example/ ASN1START ChildIE2-WithoutEM ::= CHOICE { release NULL, setup SEQUENCE { -- Root encoding } } ChildIE2-WithoutEM-vNx0 ::= SEQUENCE { chIE2-NewField-rN INTEGER (0..31) OPTIONAL -- Cond ConfigF } -- ASN1STOP A.4.3.6 Non-critical extensions of lists with ToAddMod/ToRelease When the size of a list using the ToAddMod/ToRelease construction is extended and/or fields are added to the list element structure, the list should be non-critically extended in accordance with the following general principles: – When only the size of the list is extended, this extension is reflected in a non-critical extension of the list, with a "SizeExt" suffix added to the end of the field name (before the -vNxy suffix). The differential size of the extended list uses the suffix "Diff". A new ToRelease list is needed, and its range should include only the increase in list size. In many cases, extending the list size will also require an extended list element ID type to account for the increased size of the list; in these cases the element type will need to be extended to include the extended element ID, resulting in a more complex extension (see example 3 for further discussion of this case). The field description table should indicate that the UE considers the original list and the extension list as a single list; thus entries added with the original list can be modified by the extension list (or removed by the extension of the ToRelease list), or vice versa. The result is as shown in the following example: -- /example 1/ ASN1START ContainingStructure ::= SEQUENCE { listElementToAddModList SEQUENCE (SIZE (1..maxNrofListElements)) OF ListElement OPTIONAL, -- Need N listElementToReleaseList SEQUENCE (SIZE (1..maxNrofListElements)) OF ListElementId OPTIONAL, -- Need N ..., [[ -- Non-critical extension lists listElementToAddModListSizeExt-vNxy SEQUENCE (SIZE (1..maxNrofListElementsDiff-rN)) OF ListElement OPTIONAL, -- Need N listElementToReleaseListSizeExt-vNxy SEQUENCE (SIZE (1..maxNrofListElementsDiff-rN)) OF ListElementId OPTIONAL -- Need N ]] } -- ASN1STOP – When fields are added to the list element structure, an extension marker should normally be used if available. If no extension marker is available or if overhead or other considerations prevent using the extension marker, an extension structure should be created for the new fields, with the suffix "Ext" added to the end of the field name and the element structure type name (before the -vNxy suffix), and a parallel ToAddMod list introduced to hold the new structures, also with the "Ext" suffix. The field description table should indicate that the parallel list contains the same number of entries, and in the same order, as the original list. No new ToRelease list is typically needed (unless the list element ID type changes). It should typically be ensured that the contained fields in the "Ext" elements are releasable without release and add of the entire list element; this can, for instance, be ensured by having the new fields be OPTIONAL Need R. If multiple extensions of the same list are needed, the version suffix should distinguish the lists (e.g. listElementToAddModListExt-vNwz added after listElementToAddModListExt-vNxy). The result is as shown in the following example: -- /example 2/ ASN1START ContainingStructure ::= SEQUENCE { listElementToAddModList SEQUENCE (SIZE (1..maxNrofListElements)) OF ListElement OPTIONAL, -- Need N listElementToReleaseList SEQUENCE (SIZE (1..maxNrofListElements)) OF ListElementId OPTIONAL, -- Need N ..., [[ -- Parallel list listElementToAddModListExt-vNxy SEQUENCE (SIZE (1..maxNrofListElements)) OF ListElementExt-vNxy OPTIONAL -- Need N ]], [[ -- Second parallel list from a later spec version listElementToAddModListExt-vNwz SEQUENCE (SIZE (1..maxNrofListElements)) OF ListElementExt-vNwz OPTIONAL -- Need N ]] } ListElement ::= SEQUENCE { elementId ListElementId, field1 INTEGER (0..3), field2 ENUMERATED { value1, value2, value3 } } ListElementExt-vNxy ::= SEQUENCE { field3-rN BIT STRING (SIZE (8)) OPTIONAL -- Need R } ListElementExt-vNwz ::= SEQUENCE { field4-rN INTEGER (0..255) OPTIONAL -- Need R } -- ASN1STOP – When the size of a list is extended and fields are added to the list element structure, an extension marker should normally be used for the added fields if available, and the list extended with the non-critical mechanism as described in example 1 above. Note that if the list element ID type changes in this case, the new ID can be added after the extension marker, and the entries of the size-extended ToRelease list should have the type of the new ID (e.g. ListElementId-vNxy). If no extension marker is available or if overhead or other considerations prevent using the extension marker, an extension structure should be created for the new fields and a parallel list with ToAddMod introduced to hold the extension structures, as in the second example above, for entries of the original list and for entries of the extension list holding new entries. The field description table should indicate that the parallel list contains the same number of entries, and in the same order, as the concatenation of the original list and the extension list. An extended ToRelease list is needed, but no additional parallel ToRelease list is needed (i.e. there is no listElementToReleaseListExt-vNxy in the example below), as the original and extended ToRelease lists suffice to release any element of the combined list. The extended element ID type should be captured as a non-critical extension of the original element ID type, with the field description indicating that if the extended ID is present, the original ID is ignored. The result is as shown in the following example: -- /example 3/ ASN1START ContainingStructure ::= SEQUENCE { listElementToAddModList SEQUENCE (SIZE (1..maxNrofListElements)) OF ListElement OPTIONAL, -- Need N listElementToReleaseList SEQUENCE (SIZE (1..maxNrofListElements)) OF ListElementId OPTIONAL, -- Need N ..., [[ -- Non-critical extension lists listElementToAddModListSizeExt-vNxy SEQUENCE (SIZE (1..maxNrofListElementsDiff-rN)) OF ListElement OPTIONAL, -- Need N listElementToReleaseListSizeExt-vNxy SEQUENCE (SIZE (1..maxNrofListElementsDiff-rN)) OF ListElementId-vNxy OPTIONAL, -- Need N -- Parallel list with maxNrofListElements-rN = maxNrofListElements + maxNrofListElementsDiff-rN listElementToAddModListExt-vNxy SEQUENCE (SIZE (1..maxNrofListElements-rN)) OF ListElementExt-vNxy OPTIONAL -- Need N ]] } ListElement ::= SEQUENCE { elementId ListElementId, field1 INTEGER (0..3), field2 ENUMERATED { value1, value2, value3 } } ListElementExt-vNxy ::= SEQUENCE { -- Field description should indicate that if the elementId-vNxy is present, the elementId (without suffix) is ignored elementId-vNxy ListElementId-vNxy OPTIONAL, -- Need S field3-rN BIT STRING (SIZE (8)) OPTIONAL -- Need R } ListElementId ::= INTEGER (0..maxNrofListElements-1) ListElementId-vNxy ::= INTEGER (maxNrofListElements..maxNrofListElements-1-rN) -- ASN1STOP – When different extensions are made to a list in separate releases, the extension mechanisms described above may interact. In case fields are added in Rel-M (listElementToAddModListExt-vMxy) and later the list size is extended in Rel-N (listElementToAddModListSizeExt-vNwz), the size-extended list in Rel-N should be a single list extending the combination of listElementToAddModList and listElementToAddModListExt-vMxy. This requires creating a new type (ListElement-rN) to contain the combined fields of ListElement and ListElementExt-vMxy. A corresponding ToRelease list is needed. The result is as shown in the following example: -- /example 4/ ASN1START ContainingStructure ::= SEQUENCE { listElementToAddModList SEQUENCE (SIZE (1..maxNrofListElements)) OF ListElement OPTIONAL, -- Need N listElementToReleaseList SEQUENCE (SIZE (1..maxNrofListElements)) OF ListElementId OPTIONAL, -- Need N ..., [[ -- Parallel list (Rel-M) listElementToAddModListExt-vMxy SEQUENCE (SIZE (1..maxNrofListElements)) OF ListElementExt-vMxy OPTIONAL -- Need N ]], [[ -- Size-extended list (Rel-N) with maxNrofListElements-rN = maxNrofListElements + maxNrofListElementsDiff-rN listElementToAddModListSizeExt-vNwz SEQUENCE (SIZE (1..maxNrofListElementsDiff-rN)) OF ListElement-rN OPTIONAL, -- Need N listElementToReleaseListSizeExt-vNwz SEQUENCE (SIZE (1..maxNrofListElementsDiff-rN)) OF ListElementId-vNwz OPTIONAL -- Need N ]] } ListElement ::= SEQUENCE { elementId ListElementId, field1 INTEGER (0..3), field2 ENUMERATED { value1, value2, value3 } } ListElementExt-vMxy ::= SEQUENCE { field3-rM BIT STRING (SIZE (8)) OPTIONAL -- Need R } ListElement-rN ::= SEQUENCE { elementId-vNwz ListElementId-vNwz, field1 INTEGER (0..3), field2 ENUMERATED { value1, value2, value3 }, field3-rN BIT STRING (SIZE (8)) OPTIONAL -- Need R } ListElementId ::= INTEGER (0..maxNrofListElements-1) ListElementId-vNwz ::= INTEGER (maxNrofListElements..maxNrofListElementsDiff-1-rN) -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

6.46.6 Efficient user plane

For a 5G system with satellite access, the following requirements apply: A 5G system with satellite access shall be able to select the communication link providing the UE with the connectivity that most closely fulfils the agreed QoS. A 5G system with satellite access shall be capable of supporting simultaneous use of 5G satellite access network and 5G terrestrial access networks. - A 5G system with satellite access shall be able to support both UEs supporting only satellite access and UEs supporting simultaneous connectivity to 5G satellite access network and 5G terrestrial access network. - Subject to regulatory requirements and operator’s policies, a 5G system with satellite access shall be able to support an efficient communication path and resource utilization for a UE using only satellites access, e.g. to minimize the latencies introduced by satellite links involved.

3GPP TS 22.261

Service requirements for the 5G system

SA WG1

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

6.46.6

5.8.2.5.3 Support of Ethernet PDU Session type

When configuring an UPF acting as PSA for an Ethernet PDU Session Type, the SMF may instruct the UPF to route the traffic based on detected MAC addresses as follows. - The UPF learns the MAC address(es) connected via N6 based on the source MAC addresses of the DL traffic received on a N6 Network Instance. - The UPF learns the MAC address(es) of UE(s) and devices connected behind, if any, based on the source MAC address contained within the UL traffic received on a PDU Session (N3/N9 interface). - The UPF forwards DL unicast traffic (with a known destination address) on a PDU Session determined based on the source MAC address(es) used by the UE for the UL traffic. - The UPF forwards UL unicast traffic (with a known destination address) on a port (PDU Session or N6 interface) determined based on the source MAC address(es) learned beforehand. - In the case of multicast and broadcast traffic (if the destination MAC address is a broadcast or multicast address): - for DL traffic received by UPF on a N6 Network Instance the UPF should forward the traffic to every DL PDU Session (corresponding to any N4 Session) associated with this Network Instance - for uplink traffic received by UPF over a PDU session on a N3/N9 interface, the UPF should forward the traffic to the N6 interface and downlink to every PDU session (except toward the one of the incoming traffic) associated with the same N6 Network Instance - for uplink and downlink unicast traffic received by UPF, if the destination MAC has not been learnt, the UPF should forward the traffic to every PDU session associated with the same N6 Network Instance and towards the N6 interface. In any case the traffic is not replicated on the PDU Session or the N6 interface of the incoming traffic. NOTE 1: The UPF can consider a PDU Session or a N6 interface to be active or inactive in order to avoid forwarding loops. User data traffic is not sent on inactive PDU sessions or inactive N6 interface. This release of the specification does not further specify how the UPF determines whether a PDU Session or N6 interface is considered active or inactive. NOTE 2: This release of the specification supports only a single N6 interface in a UPF associated with the N6 Network Instance. - if the traffic is received with a VLAN ID, the above criteria apply only towards the N6 interface or PDU session matching the same VLAN ID, unless the UPF is instructed to remove the VLAN ID in the incoming traffic. NOTE 3: This release of the specification supports Independent VLAN Learning (IVL) and does not support Shared VLAN Learning (SVL), as described in IEEE Std 802.1Q [98]. - if the destination MAC address of traffic refers to the same N6 interface or PDU session on which the traffic has been received, the frame shall be dropped. In order to handle scenarios where a device behind a UE is moved from a source UE to a target UE, a MAC address is considered as no longer associated with a UPF interface (source UE's PDU session) when the MAC address has not been detected as Source MAC address in UL traffic for a pre-defined period of time or the MAC address has been detected under a different interface (target UE's PDU Session or N6). NOTE 4: The UPF/NW-TT may also be provided with static filtering entries as described in clause 5.28.3. How the UPF uses the static filtering entry to achieve forwarding of Ethernet frames to one or more egress ports is up to UPF implementation. The externally observable behaviour of 5GS Bridge needs to comply with IEEE Std 802.1Q [98]. For ARP/IPv6 Neighbour Solicitation traffic, a SMF's request to respond to ARP/IPv6 Neighbour Solicitation based on local cache information or to redirect such traffic from the UPF to the SMF overrules the traffic forwarding rules described above. NOTE 5: Local policies in UPF associated with the Network Instance can prevent local traffic switching in the UPF between PDU Sessions either for unicast traffic only or for any traffic. In the case where UPF policies prevent local traffic switching for any traffic (thus for broadcast/multicast traffic) some mechanism such as responding to ARP/ND based on local cache information or local multicast group handling is needed to ensure that upper layer protocol can run on the Ethernet PDU sessions. The SMF may ask to get notified with the source MAC addresses used by the UE, e.g. if the PCF has subscribed to UE MAC address change notifications, as described in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. In order to request the UPF to act as defined above, the SMF may, for each PDU Session corresponding to a Network Instance, set an Ethernet PDU Session Information in a DL PDR that identifies all (DL) Ethernet packets matching the PDU session. Alternatively, for unicast traffic the SMF may provide UPF with dedicated forwarding rules related with MAC addresses notified by the UPF.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.8.2.5.3

6.4.3.6 Abnormal cases on the network side

The following abnormal cases can be identified: a) Expiry of timer T3486: On the first expiry of the timer T3486, the MME shall resend the MODIFY EPS BEARER CONTEXT REQUEST and shall reset and restart timer T3486. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3486, the MME shall abort the procedure and enter the state BEARER CONTEXT ACTIVE. The MME may continue to use the previous configuration of the EPS bearer context or initiate an EPS bearer context deactivation procedure. b) Collision of UE requested PDN disconnect procedure and EPS bearer context modification: When the MME receives a PDN DISCONNECT REQUEST message during an EPS bearer context modification procedure, and the EPS bearer to be modified belongs to the PDN connection the UE wants to disconnect, the MME shall terminate the EPS bearer context modification procedure locally, release any resources related to this procedure and proceed with the PDN disconnect procedure. c) Collision of UE requested bearer resource modification procedure and EPS bearer context modification procedure: If the MME receives a BEARER RESOURCE MODIFICATION REQUEST message during the EPS bearer context modification procedure and the EPS bearer indicated in the BEARER RESOURCE MODIFICATION REQUEST message is the EPS bearer that the network had requested to modify, the network shall ignore the BEARER RESOURCE MODIFICATION REQUEST message received in the state BEATER CONTEXT MODIFY PENDING. The network shall proceed with the EPS bearer modification procedure as if no BEARER RESOURCE MODIFICATION REQUEST message was received from the UE.

3GPP TS 24.301

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

CT WG1

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

6.4.3.6

4.6.2.10 Mobility management aspects of handling network slices with NS-AoS not matching deployed tracking areas

An operator can choose to let the NS-AoS of an S-NSSAI not match the existing tracking area boundaries (see subclause 5.15.18 of 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]). In order to support this deployment option, the operator has to ensure that an AMF covering the NS-AoS operates as described below. The support for S-NSSAI location validity information by the UE and the network, respectively, is optional. If a UE supports S-NSSAI location validity information, the UE indicates that it supports S-NSSAI location validity information during the registration procedure (see subclause 5.5.1). The AMF can provide a UE which has indicated that it supports S-NSSAI location validity information with S-NSSAI location validity information (see subclauses 5.4.4 and 5.5.1). The S-NSSAI location validity information consists of, for each of the applicable S-NSSAI(s) in the configured NSSAI: a) an S-NSSAI; and b) a list of cell identities of TA(s) belonging to the registration area where the related S-NSSAI(s) is available in some cells but not all cells of one or more TAs, which represents the NS-AoS of the S-NSSAI. The UE shall consider itself to be inside the NS-AoS if the cell identity of the current serving cell matches any of the identities in the S-NSSAI location validity information. Otherwise, the UE shall consider itself to be outside the NS-AoS. NOTE 1: The cell identity of the current serving cell is received from the lower layers. For an S-NSSAI in the S-NSSAI location validity information, even if the S-NSSAI is included in the rejected NSSAI with a rejection cause value set to "S-NSSAI not available in the current registration area" or is included in the partially rejected NSSAI, the UE is allowed to request the S-NSSAI if the UE determines that it is inside the NS-AoS of the S-NSSAI. For an S-NSSAI limited by NS-AoS, if the UE in 5GMM-CONNECTED mode does not support S-NSSAI location validity information and the AMF determines that: a) the UE is not in the NS-AoS, then the AMF may: 1) provide the UE with an allowed NSSAI or a partially allowed NSSAI excluding the S-NSSAI, and optionally a configured NSSAI excluding the S-NSSAI; or NOTE 2: If excluding the S-NSSAI limited by NS-AoS results in an empty allowed NSSAI or partially allowed NSSAI, the AMF includes one or more default S-NSSAIs in the provided allowed NSSAI or partially allowed NSSAI. 2) indicate to the SMF to release all PDU sessions associated with the S-NSSAI; or b) the UE is in the NS-AoS, then the AMF may update the configured NSSAI to include the S-NSSAI in the configured NSSAI. If the UE that does not support S-NSSAI location validity information requests a PDU session establishment for an S-NSSAI limited by NS-AoS and the AMF determines that the UE is not in the NS-AoS, the AMF may perform S-NSSAI based congestion control for the S-NSSAI as specified in subclauses 5.3.11 and 5.4.5. The S-NSSAI location validity information is only applicable to 3GPP access.

3GPP TS 24.501

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

CT WG1

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

4.6.2.10

5.5.3.3.4.2 Combined tracking area updating successful

The description for normal tracking area update as specified in clause 5.5.3.2.4 shall be followed. In addition, the following description for location area updating applies. The TMSI reallocation may be part of the combined tracking area updating procedure. The TMSI allocated is then included in the TRACKING AREA UPDATE ACCEPT message together with the location area identification (LAI). In this case the MME shall change to state EMM-COMMON-PROCEDURE-INITIATED and shall start the timer T3450 as described in clause 5.4.1. The LAI may be included in the TRACKING AREA UPDATE ACCEPT message without TMSI. If the MME does not indicate "SMS only" in the TRACKING AREA UPDATE ACCEPT message, subject to operator policies the MME should allocate a TAI list that does not span more than one location area. For a shared network in CS domain, the MME indicates the selected PLMN for CS domain in the LAI to the UE as specified in 3GPP TS 23.272[ Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2 ] [9]. The UE, receiving a TRACKING AREA UPDATE ACCEPT message, stores the received location area identification, resets the location update attempt counter, sets the update status to U1 UPDATED and enters MM state MM IDLE. If the UE maintains a counter for "SIM/USIM considered invalid for non-GPRS services" events (see clause 5.3.7b), then the UE shall reset this counter. If the LAI contained in the TRACKING AREA UPDATE ACCEPT message is a member of the list of "forbidden location areas for regional provision of service" or the list of "forbidden location areas for roaming" then such entry shall be deleted. If the PLMN identity for the CS domain which is provided as part of the LAI contained in the TRACKING AREA UPDATE ACCEPT message differs from the PLMN identity provided as part of the GUTI, the MME shall include the PLMN identity for the CS domain in the list of equivalent PLMNs in the TRACKING AREA UPDATE ACCEPT message. If the UE requested "SMS only" in the Additional update type IE, or if the UE requested a combined tracking area updating for EPS and non-EPS services, but the network decides to accept the tracking area update request for EPS services and "SMS only", the network shall indicate "SMS only" in the Additional update result IE. In addition, if the SMS services are provided via SMS in MME, the network shall, in the TRACKING AREA UPDATE ACCEPT message, provide a non-broadcast LAI and may indicate in the EPS update result IE that ISR is activated. If a TMSI has to be allocated, then the network shall also provide a TMSI which cannot cause any ambiguity with assigned TMSI values. If the TRACKING AREA UPDATE ACCEPT message includes the Additional update result IE with value "SMS only", a UE operating in CS/PS mode 2 and a UE operating in CS/PS mode 1 with "IMS voice available" shall not attempt to use CS fallback for mobile originating services. As an implementation option, if the TRACKING AREA UPDATE ACCEPT message does not include the Additional update result IE with value "SMS only" and the UE is not configured for NAS signalling low priority then the UE may stop timer T3246 if running. If the TRACKING AREA UPDATE ACCEPT message includes the Additional update result IE with value "CS Fallback not preferred", this indicates to a UE operating in CS/PS mode 2 and a UE operating in CS/PS mode 1 with "IMS voice available" that it is attached for EPS and non-EPS services and that it can use CS fallback. How to handle the old TMSI stored in the UE depends on the mobile identity included in the TRACKING AREA UPDATE ACCEPT message. - If the TRACKING AREA UPDATE ACCEPT message contains an IMSI, the UE is not allocated any TMSI, and shall delete any old TMSI accordingly. - If the TRACKING AREA UPDATE ACCEPT message contains a TMSI, the UE shall use this TMSI as new temporary identity. The UE shall delete its old TMSI and shall store the new TMSI. In this case, a TRACKING AREA UPDATE COMPLETE message is returned to the network to confirm the received TMSI. - If neither a TMSI nor an IMSI has been included by the network in the TRACKING AREA UPDATE ACCEPT message, the old TMSI, if any is available, shall be kept. NOTE 1: It is possible for UEs compliant with earlier versions of this specification to send a TRACKING AREA UPDATE COMPLETE message even if TMSI reallocation is not part of the combined tracking area updating procedure. If the TRACKING AREA UPDATE ACCEPT message includes the Additional update result IE with value "SMS only" or "CS Fallback not preferred", a UE operating in CS/PS mode 1 with "IMS voice not available" shall attempt to select GERAN or UTRAN radio access technology and disable the E-UTRA capability (see clause 4.5). The network receiving a TRACKING AREA UPDATE COMPLETE message stops timer T3450, changes to state EMM-REGISTERED. NOTE 2: Upon receiving a TRACKING AREA UPDATE COMPLETE message, if a new TMSI was included in the TRACKING AREA UPDATE ACCEPT message, the MME sends an SGsAP-TMSI-REALLOCATION-COMPLETE message as specified in 3GPP TS 29.118[ Mobility Management Entity (MME) - Visitor Location Register (VLR) SGs interface specification ] [16A]. Unless the MME supporting N26 is in a deployment where it, after intersystem change from N1 mode to S1 mode, has an IMEI or an IMEISV for the UE, then after the UE performs intersystem change from N1 mode to S1 mode, if: - the network supports SRVCC for IMS emergency sessions (see 3GPP TS 23.216[ Single Radio Voice Call Continuity (SRVCC); Stage 2 ] [8]); - the UE has an emergency PDN connection; - the UE has set the SRVCC to GERAN/UTRAN capability bit in the MS network capability IE to "SRVCC from UTRAN HSPA or E-UTRAN to GERAN/UTRAN supported; and - the MME has neither an IMEI nor an IMEISV for the UE; NOTE 3: The AMF can receive an IMEI from the UE and pass it to the MME during the intersystem change if the UE is emergency registered and the UE doesn't have a valid USIM or the UE's IMSI remains unauthenticated. then the MME shall initiate the identification procedure (see clause 5.4.4) or the security mode control procedure (see clause 5.4.3) with the UE.

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

5.4.2A PUCCH format 3

The block of bits shall be scrambled with a UE-specific scrambling sequence, resulting in a block of scrambled bits according to where the scrambling sequence is given by clause 7.2. The scrambling sequence generator shall be initialised with at the start of each subframe where is the C-RNTI. The block of scrambled bits shall be QPSK modulated as described in Clause 7.1, resulting in a block of complex-valued modulation symbols where . The complex-valued symbols shall be block-wise spread with the orthogonal sequences and resulting in sets of values each according to where for both slots in a subframe using normal PUCCH format 3 and , holds for the first and second slot, respectively, in a subframe using shortened PUCCH format 3. The orthogonal sequences and are given by Table 5.4.2A-1. Resources used for transmission of PUCCH format 3 are identified by a resource index from which the quantities and are derived according to Each set of complex-valued symbols shall be cyclically shifted according to where is given by Clause 5.4, is the slot number within a radio frame and is the SC-FDMA symbol number within a slot. The shifted sets of complex-valued symbols shall be transform precoded according to where is the number of antenna ports used for PUCCH transmission, resulting in a block of complex-valued symbols . Table 5.4.2A-1: The orthogonal sequence

3GPP TS 36.211

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

RAN1

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

5.4.2A

4.15.1 Number of WLAN connection status reports

a) This measurement provides the number of WLAN connection status reports. This measurement is split into subcounters per reported WLAN status. b) CC c) On receipt of WLANConnectionStatusReport message (see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [18]) by the eNB. Each received message increments the relevant subcounter per WLAN status by 1. d) Each measurement is an integer. e) LWI.WlanConnectionReport.succAsso LWI.WlanConnectionReport.failRL LWI.WlanConnectionReport.failUnavail LWI.WlanConnectionReport.failTimeout LWI.WlanConnectionReport.suspended LWI.WlanConnectionReport.resumed Where LWI.WlanConnectionReport.succ indicates the WLAN status reported in the WLANConnectionStatusReport message is “successfulAssociation”; LWI.WlanConnectionReport.failRL indicates the WLAN status reported in the WLANConnectionStatusReport message is “failureWlanRadioLink”; LWI.WlanConnectionReport.failUnavail indicates the WLAN status reported in the WLANConnectionStatusReport message is “failureWlanUnavailable”; LWI.WlanConnectionReport.failTimeout indicates the WLAN status reported in the WLANConnectionStatusReport message is “failureTimeout”; LWI.WlanConnectionReport.suspended indicates the WLAN status reported in the WLANConnectionStatusReport message is “suspended”; LWI.WlanConnectionReport.resumed indicates the WLAN status reported in the WLANConnectionStatusReport message is “resumed”. 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.15.1

– AppLayerMeasConfig

The IE AppLayerMeasConfig indicates configuration of application layer measurements. AppLayerMeasConfig information element -- ASN1START -- TAG-APPLAYERMEASCONFIG-START AppLayerMeasConfig-r17 ::= SEQUENCE { measConfigAppLayerToAddModList-r17 SEQUENCE (SIZE (1..maxNrofAppLayerMeas-r17)) OF MeasConfigAppLayer-r17 OPTIONAL, -- Need N measConfigAppLayerToReleaseList-r17 SEQUENCE (SIZE (1..maxNrofAppLayerMeas-r17)) OF MeasConfigAppLayerId-r17 OPTIONAL, -- Need N rrc-SegAllowedSRB4-r17 ENUMERATED {enabled} OPTIONAL, -- Need R ..., [[ rrc-SegAllowedSRB5-r18 ENUMERATED {enabled} OPTIONAL, -- Need R idleInactiveReportAllowed-r18 ENUMERATED {enabled} OPTIONAL -- Need R ]] } MeasConfigAppLayer-r17 ::= SEQUENCE { measConfigAppLayerId-r17 MeasConfigAppLayerId-r17, measConfigAppLayerContainer-r17 OCTET STRING (SIZE (1..8000)) OPTIONAL, -- Need N serviceType-r17 ENUMERATED {streaming, mtsi, vr, spare5, spare4, spare3, spare2, spare1} OPTIONAL, -- Need M pauseReporting-r17 BOOLEAN OPTIONAL, -- Need M transmissionOfSessionStartStop-r17 BOOLEAN OPTIONAL, -- Need M ran-VisibleParameters-r17 SetupRelease {RAN-VisibleParameters-r17} OPTIONAL, -- Cond ServiceType ..., [[ reportingSRB-r18 ENUMERATED {srb4, srb5, spare2, spare1} OPTIONAL, -- Need M appLayerMeasPriority-r18 INTEGER (1..16) OPTIONAL, -- Need M appLayerIdleInactiveConfig-r18 AppLayerIdleInactiveConfig-r18 OPTIONAL -- Need M ]] } RAN-VisibleParameters-r17 ::= SEQUENCE { ran-VisiblePeriodicity-r17 ENUMERATED {ms120, ms240, ms480, ms640, ms1024} OPTIONAL, -- Need S numberOfBufferLevelEntries-r17 INTEGER (1..8) OPTIONAL, -- Need R reportPlayoutDelayForMediaStartup-r17 BOOLEAN OPTIONAL, -- Need M ..., [[ ran-VisibleReportingSRB-r18 ENUMERATED {srb4, srb5, spare2, spare1} OPTIONAL -- Need M ]] } -- TAG-APPLAYERMEASCONFIG-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

4.7.1.7b Intersystem change from S1 mode to A/Gb mode or S1 mode to Iu mode for eCall only MS capable of eCall over IMS

If an eCall only MS (as determined by information configured in USIM) capable of eCall over IMS returns from S1 mode to A/Gb or Iu mode, the MS shall: a) if timer T3444 is running, start timer T3242 with the time left on timer T3444, and stop timer T3444; b) if timer T3445 is running, start timer T3243 with the time left on timer T3445, and stop timer T3445; c) if the MS is attached for GPRS services only and timer T3444 or timer T3445 is running: - perform a combined routing area updating procedure with IMSI attach if the network operates in network operation mode I; and - perform a routing area updating procedure and a location area updating procedure if the network operates in network operation mode II; and d) if the MS is attached for both GPRS services and non-GPRS services and timer T3444 or timer T3445 is running: - perform a combined routing area updating procedure if the network operates in network operation mode I; and - perform a routing area updating procedure and a location are updating procedure if the network operates in network operation mode II. NOTE: Timers T3444 and T3445 are specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120].

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

10.2.5.5 Mapping to resource elements

The block of complex-valued symbols shall be mapped in sequence starting with to resource elements on the associated antenna port which meet all of the following criteria: - they are part of the NCCE(s) assigned for the NPDCCH transmission, and - they are not used for transmission of NPBCH, NPSS, or NSSS, and - except in a special subframe when NPDCCH is transmitted in more than one subframe, they are assumed by the UE not to be used for NRS, and - they are not overlapping with resource elements used for CRS as defined in clause 6 (if any), and - the index in the first slot in a subframe fulfils where is given by clause 16.6.1 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4], - in addition, for frame structure Type 2, - in a special subframe where the NPDCCH is transmitted in one subframe, they are in DwPTS - in a special subframe where the NPDCCH is transmitted in more than one subframe, they are not NRS locations when the subframe is not a special subframe. The mapping to resource elements on antenna port meeting the criteria above shall be in increasing order of first the index and then the index, starting with the first slot and ending with the second slot in a subframe. Denote as the complex-valued symbols that are mapped to resource elements meeting the criteria above in subframe , with the insertion of <NIL> elements in the locations of resource elements which are not part of the NCCE(s) assigned for the NPDCCH transmission. If the NPDCCH is transmitted in more than one subframe, the resource elements in a special subframe that are not part of DwPTS are counted but not used in the mapping. When , the resource elements in a special subframe assumed by the UE for NRSs are counted but not used in the mapping if the NPDCCH is transmitted in more than one subframe. For frame structure type 1, - for NPDCCH associated with RA-RNTI, TC-RNTI or - for P-RNTI and transmitted in an NB-IoT carrier configured by SystemInformationBlockType22-NB, or - for NPDCCH associated with C-RNTI in an NB-IoT carrier configured by SystemInformationBlockType22-NB when RadioResourceConfigDedicted-NB is not configured by higher layer, or - for NPDCCH associated with PUR-RNTI/G-RNTI/ SC-RNTI, or - for NPDCCH associated with C-RNTI or SPS C-RNTI when interferenceRandomisationConfig is used according to [9], or for frame structure type 2, each complex-valued symbol , shall be multiplied with ,where where the scrambling sequence is given by clause 7.2 and shall be initialized at the start of each subframe with . The NPDCCH transmission can be configured by higher layers with transmissions gaps where the NPDCCH transmission is postponed. The configuration is the same as described for NPDSCH in clause 10.2.3.4. The UE shall not expect NPDCCH in subframe if it is not a NB-IoT downlink subframe. In case of NPDCCH transmissions, in subframes that are not NB-IoT downlink subframes, the NPDCCH transmission is postponed until the next NB-IoT downlink subframe. If higher layer parameter resourceReservationConfigDL is configured, then in case of NPDCCH transmission associated with C-RNTI or SPS C-RNTI using UE-specific NPDCCH search space, - In a subframe that is fully reserved as defined in clause 16.4 in [4], the NPDCCH transmission is postponed until the next NB-IoT downlink subframe that is not fully reserved. - In a subframe that is partially reserved, the reserved OFDM symbols shall be counted in the NPDCCH mapping but not used for transmission of the NPDCCH.

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

4.2.11.5.1 Network Slice Admission Control Support for Roaming by VPLMN

This clause describes the case of VPLMN NSAC admission mode. For NSAC for roaming UEs, a maximum number of allowed UEs per mapped S-NSSAI in HPLMN and/or a maximum number of allowed PDU Sessions in LBO mode per mapped S-NSSAI in HPLMN is allocated to the VPLMN for each S-NSSAI in HPLMN and stored in one NSCAF in the VPLMN responsible for NSAC for the S-NSSAI in the HPLMN, subject to NSAC. Enforcement for the maximum number of UEs registered with a network slice is done in the VPLMN by the NSACF in the VPLMN as per the description in Figure 4.2.11.2-1 with the following differences: - Step 2, in the Nnsacf_NSAC_NumOfUEsUpdate_Request service operation where the AMF provides both the S-NSSAI in VPLMN and the corresponding mapped S-NSSAI in HPLMN to the NSACF in the VPLMN. - Step 3, the NSACF in the VPLMN performs NSAC for both the S-NSSAI in VPLMN and the corresponding mapped S-NSSAI in HPLMN based on the SLA between VPLMN and HPLMN. For LBO PDU sessions, enforcement for the maximum number of PDU Sessions established for an S-NSSAI is performed in the VPLMN by the NSACF in the VPLMN as per the description in Figure 4.2.11.4-1 with the following differences: - Step 2, in the Nnsacf_NSAC_NumOfPDUsUpdate_Request service operation where the V-SMF provides both the S-NSSAI in VPLMN and the corresponding mapped S-NSSAI in HPLMN to the NSACF in the VPLMN. - Step 3, the NSACF in the VPLMN performs NSAC for both the S-NSSAI in VPLMN and the corresponding mapped S-NSSAI in HPLMN based on the SLA between VPLMN and HPLMN. An NSACF at VPLMN can optionally fetch the maximum number of registered UEs to be enforced and the maximum number of LBO PDU sessions to be enforced rather than have them pre-configured. In this case, the following is performed: - For a centralized NSAC architecture in the VPLMN, the NSACF, being a centralized NSACF, issues the Nnsacf_NSAC_QuotaUpdate Request to fetch from the HPLMN centralized NSACF or primary NSACF the maximum number of registered UEs and the maximum number of LBO PDU sessions to be enforced. - For a hierarchical NSAC architecture in the VPLMN, the NSACF issues the Nnsacf_NSAC_NumOfUEsUpdate_Request or Nnsacf_NSAC_NumOfPDUsUpdate_Request to the VPLMN primary NSACF for NSAC for the maximum number of registered UEs, or NSAC for the maximum number of LBO PDU sessions. The VPLMN primary NSACF in turn issues the Nnsacf_NSAC_QuotaUpdate Request, to fetch from the HPLMN centralized NSACF or primary NSACF the maximum number of registered UEs, or the maximum number of LBO PDU sessions to be admitted; this information in turn may be distributed to the VPLMN NSACF. The NSACF in VPLMN discovers the primary or central NSACF in HPLMN as defined in clause 6.3.22 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], or optionally be configured with the needed information.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.2.11.5.1

5.3.9 Handling of NAS level mobility management congestion control

The network may detect EMM signalling congestion and perform NAS level mobility management congestion control. NAS level mobility management congestion control consists of general NAS level mobility management congestion control and subscribed APN based congestion control. Under general overload conditions the network may reject mobility management signalling requests from UEs as specified in 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10]. The network should not reject the following requests: - requests for emergency bearer services; - DETACH REQUEST message; - service request or tracking area update request triggered by paging; - requests from UEs that were received via NAS signalling connections established with RRC establishment cause "High priority access AC 11 – 15"; - requests for attach, normal tracking area updating or periodic tracking area updating, when emergency is indicated by lower layers; - requests for CS fallback emergency call or 1xCS fallback emergency call; and - requests for tracking area update when the UE is reporting unavailability information due to enhanced discontinuous coverage. When subscribed APN based mobility management congestion control is active for a particular APN, the network may reject attach requests from UEs with a subscription to this APN. In mobility management the network may detect NAS signalling congestion and start or stop performing the subscribed APN based congestion control based on mobility management level criteria such as: - rate of mobility management NAS messages from a group of UEs with a subscription to a particular APN exceeds or falls below certain thresholds; and/or - setting in network management. When the NAS level mobility management congestion control is active, the network may include a value for the mobility management back-off timer T3346 in the reject messages. The UE starts the timer T3346 with the value received in the mobility management reject messages. To avoid that large numbers of UEs simultaneously initiate deferred requests, the network should select the value for the timer T3346 for the rejected UEs so that timeouts are not synchronised. For subscribed APN based congestion control the value of timer T3346 for a particular APN may be APN dependent. If the timer T3346 is running when the UE enters state EMM-DEREGISTERED, the UE remains switched on, and the USIM in the UE remains the same, then timer T3346 is kept running until it expires or it is stopped. If the UE is switched off when the timer T3346 is running, the UE shall behave as follows when the UE is switched on and the USIM in the UE remains the same: - let t1 be the time remaining for T3346 timeout at switch off and let t be the time elapsed between switch off and switch on. If t1 is greater than t, then the timer shall be restarted with the value t1 – t. If t1 is equal to or less than t, then the timer need not be restarted. If the UE is not capable of determining t, then the UE shall restart the timer with the value t1; and - if prior to switch off, timer T3346 was started due to a NAS request message (ATTACH REQUEST, TRACKING AREA UPDATE REQUEST, CONTROL PLANE SERVICE REQUEST or EXTENDED SERVICE REQUEST) which contained the low priority indicator set to "MS is configured for NAS signalling low priority", then if timer T3346 is restarted at switch on, the UE configured for dual priority shall handle mobility management requests as indicated in clauses 5.5.1.2.6, 5.5.3.2.6 and 5.6.1.6. If the UE enters a new PLMN while timer T3346 is running, and the new PLMN is not equivalent to the PLMN where the UE started timer T3346, the UE shall stop timer T3346 when initiating mobility management procedures in the new PLMN. After change in TAI which is not part of TAI list, if the timer T3346 is running and EMM update status is EU1 UPDATED then UE shall set the EMM update status to EU2 NOT UPDATED and enter state EMM-REGISTERED.ATTEMPTING-TO-UPDATE.

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

5.30.2.2 Broadcast system information

NG-RAN nodes or Trusted non-3GPP access networks which provide access to SNPNs broadcast the following information: - One or multiple PLMN IDs; - List of NIDs per PLMN ID identifying the non-public networks NG-RAN provides access to; and NOTE 1: It is assumed that an NG-RAN node supports broadcasting a total of twelve NIDs. Further details are defined in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [28]. NOTE°2: The presence of a list of NIDs for a PLMN ID indicates that the related PLMN ID and NIDs identify SNPNs. - Optionally: - A human-readable network name per SNPN; NOTE 3: The human-readable network name per SNPN is only used for manual SNPN selection. If the SNPN supports Localized Service, the human-readable network name of the SNPN can be information related to the Localized Service. The mechanism how human-readable network name is provided (i.e. whether it is broadcasted or unicasted) to the UE is specified in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [28]. - Information, as described in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27], TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [28] and in TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [50], to prevent UEs not supporting SNPNs from accessing the cell, e.g. if the cell only provides access to non-public networks; - An indication per SNPN of whether access using credentials from a Credentials Holder is supported; - List of supported Group IDs for Network Selection (GINs) per SNPN; and - An indication per SNPN of whether the SNPN allows registration attempts from UEs that are not explicitly configured to select the SNPN, i.e. UEs that do not have any PLMN ID and NID nor GIN broadcast by the SNPN in the Credentials Holder controlled prioritized lists of preferred SNPNs/GINs. NOTE 4: Further details (including number of supported GINs per SNPN) are defined in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [28].

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.30.2.2

4.3.2.8 Handling of keys at intersystem change from A/Gb mode to Iu mode

At inter-system change from A/Gb mode to Iu mode, ciphering and integrity may be started (see 3GPP TS 25.331[ None ] [23c]) without any new authentication procedure. Deduction of the appropriate security keys for ciphering and integrity check in Iu mode, depends on the current GSM/UMTS security context stored in the MS and the network. The ME shall handle the UMTS ciphering key and the UMTS integrity key according to table 4.3.2.8.1. Table 4.3.2.8.1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Inter-system change from A/Gb mode to Iu mode NOTE: A USIM with UMTS security context, passes the UMTS ciphering key, the UMTS integrity key and the derived GSM ciphering key to the ME independent on the current radio access being UTRAN or GERAN.

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