Datasets:

Exploration-Lab

/

MM-TelecoBench

like 1

Follow

Exploration Lab 62

B.1 Voice Control

To enable charging of ARP subscribers for voice calls, an online charging interface between the DSP and ARP is established. The concept of voice call shall be interpreted as any Circuit-switched call, whatever the teleservice used (speech, 3.1 kHz audio, Fax, or CS data) except circuit-switched Video Telephony calls (BS 37, 64 kbit/s unrestricted digital info mode). The voice control architecture is shown in figure B.1.1. Figure B.1.1: Voice Control Architecture and Associated Functions The signaling between the Visited Network and the DSP utilizes CAP for the online CS domain charging as specified in TS 32.250[ Telecommunication management; Charging management; Circuit Switched (CS) domain charging ] [10]. For the CAMEL option of IF#1, the signaling between the DSP and ARP also utilizes CAP for the online CS domain charging as specified in TS 32.250[ Telecommunication management; Charging management; Circuit Switched (CS) domain charging ] [10]. For the Diameter option of IF#1, the signaling between the DSP and ARP utilizes Diameter Ro for the Voice Call Service online charging as specified in TS 32.276[ Telecommunication management; Charging management; Voice Call Service (VCS) charging ] [36] and utilizes the Proxy Function for mapping between CAMEL and Diameter as specified in TS 32.293[ Telecommunication management; Charging management; Proxy function ] [56].

3GPP TS 32.240

Telecommunication management; Charging management; Charging architecture and principles

SA WG5

3GPP Series : 32 , OAM&P and Charging

B.1

6.2.12 Handling of network rejection not due to congestion control

The network may include a back-off timer value in a 5GS session management reject message to regulate the time interval at which the UE may retry the same procedure for 5GSM cause values other than #26 "insufficient resources", #28 "unknown PDU session type", #39 "reactivation requested", #46 "out of LADN service area", #50 "PDU session type IPv4 only allowed", #51 "PDU session type IPv6 only allowed", #54 "PDU session does not exist", #57 "PDU session type IPv4v6 only allowed", #58 "PDU session type Unstructured only allowed", #61 "PDU session type Ethernet only allowed", #67 "insufficient resources for specific slice and DNN", #68 "not supported SSC mode" and #69 "insufficient resources for specific slice". For 5GSM cause values other than #26 "insufficient resources", #28 "unknown PDU session type", #39 "reactivation requested", #46 "out of LADN service area", #54 "PDU session does not exist", #67 "insufficient resources for specific slice and DNN", #68 "not supported SSC mode", and #69 "insufficient resources for specific slice", and #86 "UAS services not allowed", the network may also include the re-attempt indicator to indicate whether the UE is allowed to re-attempt the corresponding session management procedure for the same DNN in S1 mode after inter-system change. NOTE 1: In a PLMN, if the network includes this back-off timer value for 5GSM cause values other than #27 "missing or unknown DNN", then the UE is blocked from sending another 5GSM request for the same procedure for the same [PLMN, DNN, S-NSSAI], [PLMN, DNN, no S-NSSAI], [PLMN, no DNN, S-NSSAI], or [PLMN, no DNN, no S-NSSAI] combination for the specified duration. If the network includes this back-off timer value for 5GSM cause value #27 "missing or unknown DNN", then the UE is blocked from sending another 5GSM request for the same procedure for the same [PLMN, DNN], or [PLMN, no DNN] combination for the specified duration. In an SNPN, if the network includes this back-off timer value for 5GSM cause values other than #27 "missing or unknown DNN", then the UE is blocked from sending another 5GSM request for the same procedure for the same [SNPN, selected entry of the "list of subscriber data" or selected PLMN subscription, DNN, S-NSSAI], [SNPN, selected entry of the "list of subscriber data" or selected PLMN subscription, DNN, no S-NSSAI], [SNPN, selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, S-NSSAI], or [SNPN, selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, no S-NSSAI] combination for the specified duration. If the network includes this back-off timer value for 5GSM cause value #27 "missing or unknown DNN", then the UE is blocked from sending another 5GSM request for the same procedure for the same [SNPN, selected entry of the "list of subscriber data" or selected PLMN subscription, DNN], or [SNPN, selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN] combination for the specified duration. Therefore, the operator needs to exercise caution in determining the use of this timer value. NOTE 2: If the re-attempt indicator is not provided by the network, a UE registered in its HPLMN or in an EHPLMN can use the configured SM_RetryAtRATChange value specified in the NAS configuration MO or in the USIM NASCONFIG file to derive the re-attempt indicator as specified in subclauses 6.4.1.4.3 and 6.4.2.4.3. If re-attempt in S1 mode is allowed for 5GSM cause values other than #27 "missing or unknown DNN", the UE shall consider the back-off timer to be applicable only to the 5GS session management in N1 mode for the rejected 5GS session management procedure and the given [PLMN, DNN, S-NSSAI], [PLMN, DNN, no S-NSSAI], [PLMN, no DNN, S-NSSAI], or [PLMN, no DNN, no S-NSSAI] combination. If re-attempt in S1 mode is allowed for 5GSM cause value #27 "missing or unknown DNN", the UE shall consider the back-off timer to be applicable only to the 5GS session management in N1 mode for the rejected 5GS session management procedure and the given [PLMN, DNN], or [PLMN, no DNN] combination.If re-attempt in S1 mode is not allowed, the UE shall consider the back-off timer to be applicable to both NAS protocols, i.e. applicable to the 5GS session management in N1 mode for the rejected 5GS session management procedure and to the EPS session management in S1 mode for the corresponding session management procedure and the given [PLMN, DNN] or [PLMN, no DNN] combination. NOTE 3: In the present subclause the terms DNN and APN are referring to the same parameter. In a PLMN, if the back-off timer was provided during the PDU session establishment procedure, the UE behaves as follows: for 5GSM cause values other than #27 "missing or unknown DNN", when the UE is registered in a HPLMN, the DNN and the S-NSSAI of the [PLMN, DNN, S-NSSAI] combination associated with the back-off timer is the DNN and the S-NSSAI provided by the UE when the PDU session is established. When the UE is registered in a VPLMN, the DNN and the S-NSSAI of the [PLMN, DNN, S-NSSAI] combination associated with the back-off timer is the DNN and the mapped S-NSSAI provided by the UE when the PDU session is established. For 5GSM cause value #27 "missing or unknown DNN", the DNN of the [PLMN, DNN] combination associated with the back-off timer is the DNN provided by the UE when the PDU session is established. If no DNN or no S-NSSAI was provided to the network during the PDU session establishment, then the back-off timer is associated with the [PLMN, DNN, no S-NSSAI], [PLMN, no DNN, S-NSSAI], or [PLMN, no DNN, no S-NSSAI] combination, dependent on which parameters were provided for 5GSM cause values other than #27 "missing or unknown DNN". If no DNN was provided to the network during the PDU session establishment, then the back-off timer is associated with the [PLMN, no DNN] combination for 5GSM cause value #27 "missing or unknown DNN". For this purpose, the UE shall memorize the DNN and the S-NSSAI provided to the network during the PDU session establishment. In a PLMN, if the back-off timer was provided during the PDU session modification procedure, the UE behaves as follows: the DNN associated with the back-off timer is the DNN, including no DNN, provided by the UE when the PDU session is established. If an S-NSSAI was provided by the UE during the PDU session establishment, when the UE is registered in a HPLMN, then the S-NSSAI associated with the back-off timer is the S-NSSAI of the PDU session. If an S-NSSAI was provided by the UE during the PDU session establishment, when the UE is registered in a VPLMN, then the S-NSSAI associated with the back-off timer is the mapped S-NSSAI of the PDU session. If no S-NSSAI was provided by the UE during the PDU session establishment, then the back-off timer is associated with no S-NSSAI. For this purpose, the UE shall memorize the DNN and the S-NSSAI provided to the network during the PDU session establishment. In a PLMN, the back-off timer associated with the [PLMN, no DNN, no S-NSSAI], or [PLMN, no DNN] combination will never be started due to any 5GSM procedure related to an emergency PDU session. If the back-off timer associated with the [PLMN, no DNN, no S-NSSAI], or [PLMN, no DNN] combination is running, it does not affect the ability of the UE to request an emergency PDU session. In an SNPN, the back-off timer associated with the [SNPN, selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, no S-NSSAI], or [SNPN, selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN] combination will never be started due to any 5GSM procedure related to an emergency PDU session. If the back-off timer associated with the back-off timer associated with the [SNPN, selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, no S-NSSAI], or [SNPN, selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN] combination, it does not affect the ability of the UE to request an emergency PDU session. In a PLMN, the network may additionally indicate in the re-attempt indicator that a command to back-off is applicable not only for the PLMN in which the UE received the 5GS session management reject message, but for each PLMN included in the equivalent PLMN list at the time when the 5GS session management reject message was received. In an SNPN, the network may additionally indicate in the re-attempt indicator that a command to back-off is applicable not only for the SNPN in which the UE received the 5GS session management reject message, but for each SNPN included in the equivalent SNPN list at the time when the 5GS session management reject message was received. In a PLMN, if the back-off timer is running or is deactivated for a given [PLMN, DNN, S-NSSAI], [PLMN, DNN, no S-NSSAI], [PLMN, no DNN, S-NSSAI], [PLMN, no DNN, no S-NSSAI], [PLMN, DNN], or [PLMN, no DNN] combination, and the UE is a UE configured for high priority access in selected PLMN, then the UE is allowed to initiate 5GSM procedures for the [PLMN, DNN, S-NSSAI], [PLMN, DNN, no S-NSSAI], [PLMN, no DNN, S-NSSAI], [PLMN, no DNN, no S-NSSAI], [PLMN, DNN], or [PLMN, no DNN] combination. In an SNPN, if the back-off timer is running or is deactivated for a given [SNPN, selected entry of the "list of subscriber data" or selected PLMN subscription, DNN, S-NSSAI], [SNPN, selected entry of the "list of subscriber data" or selected PLMN subscription, DNN, no S-NSSAI], [SNPN, selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, S-NSSAI], [SNPN, selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, no S-NSSAI], [SNPN, selected entry of the "list of subscriber data" or selected PLMN subscription, DNN], or [SNPN, selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN] combination if the UE is a UE configured for high priority access in selected SNPN, then the UE is allowed to initiate 5GSM procedures for the [SNPN, selected entry of the "list of subscriber data" or selected PLMN subscription, DNN, S-NSSAI], [SNPN, selected entry of the "list of subscriber data" or selected PLMN subscription, DNN, no S-NSSAI], [SNPN, selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, S-NSSAI], [SNPN, selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, no S-NSSAI], [SNPN, selected entry of the "list of subscriber data" or selected PLMN subscription, DNN], or [SNPN, selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN] combination. The RATC bit in the re-attempt indicator IE and its derivation shall not be applicable in an SNPN.

3GPP TS 24.501

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

CT WG1

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

6.2.12

4.3.18.4 CS fallback

CS Fallback allows users to fallback to GERAN/UTRAN/1x RTT while in E-UTRAN access thus allowing the network to transfer the call towards GERAN/UTRAN CS domain. In order to ensure that a priority CSFB call to/from a service user is given proper priority treatment in the EPS, MPS subscription indicates the user's CS priority status, i.e. MPS CS Priority, which is provided to MME with user's subscription information. When the eNodeB receives mobile initiated signalling with establishment cause set to highPriorityAccess, the eNodeB handles the RRC connection request with priority. When the MME receives and verifies mobile initiated signalling with establishment cause set to highPriorityAccess, the MME establishes the S1 bearer with priority. Details on the priority treatment of CSFB, see TS 23.272[ Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2 ] [58].

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

4.2.9 Network Slice-Specific Authentication and Authorization procedure 4.2.9.1 General

The Network Slice-Specific Authentication and Authorization procedure is triggered for an S-NSSAI requiring Network Slice-Specific Authentication and Authorization with an AAA Server (AAA-S) which may be hosted by the H-PLMN operator or by a third party which has a business relationship with the H-PLMN, using the EAP framework as described in TS 33.501[ Security architecture and procedures for 5G System ] [15]. An AAA Proxy (AAA-P) in the HPLMN may be involved e.g. if the AAA Server belongs to a third party. This procedure is triggered by the AMF during a Registration procedure when some Network Slices require Slice-Specific Authentication and Authorization, when AMF determines that Network Slice-Specific Authentication and Authorization is requires for an S-NSSAI in the current Allowed NSSAI or Partially Allowed NSSAI (e.g. subscription change), or when the AAA Server that authenticated the Network Slice triggers a re-authentication. NOTE 1: The S-NSSAI in the procedure can be part of Allowed NSSAI, Mapping Of Allowed NSSAI, Partially Allowed NSSAI or Mapping Of Partially Allowed NSSAI. The AMF performs the role of the EAP Authenticator and communicates with the AAA-S via the Network Slice specific and SNPN Authentication and Authorization Function (NSSAAF). The NSSAAF undertakes any AAA protocol interworking with the AAA protocol supported by the AAA-S. The Network Slice-Specific Authentication and Authorization procedure requires the use of a GPSI. In other words, a subscription that contains S-NSSAIs subject to Network Slice-Specific Authentication and Authorization shall include at least one GPSI. After a successful or unsuccessful UE Network Slice-Specific Authentication and Authorization, the AMF store the NSSAA result status for the related S-NSSAI in the UE context. NOTE 2: If an S-NSSAI subject to the NSSAA is rejected due to Network Slice Admission Control (e.g. the maximum number of UEs per network slice has been reached), the NSSAA result status stored in the UE context is not impacted.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.2.9

4.8.3 N2 Notification procedure

This procedure is used by an AMF to request the NG-RAN to report RRC state information, when the target UE is in CM-CONNECTED state. When AMF has requested reporting of subsequent state changes, the need for the NG-RAN to continue reporting ceases when the UE transitions to CM-IDLE or the AMF sends a cancel indication. This procedure may be used for services that require RRC state information (e.g. 5GC MT control and paging assistance, O&M and collection of statistics), or for subscription to the service by other NFs. See TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [10] for details of the procedure. Reporting of RRC state transitions can be requested per UE by AMF. Continuous reporting of all RRC state transitions can be enabled by operator local configuration. Figure 4.8.3-1: RRC state transition notification 1. The AMF sends a UE State Transition Notification Request to the NG-RAN as described in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [10]. The UE State Transition Notification Request message shall identify the UE for which notification(s) are requested and may contain a reporting type. The reporting type either indicates subsequent state transitions shall be notified at every RRC state transition (i.e. from RRC_CONNECTED state to RRC_INACTIVE state, or from RRC_INACTIVE to RRC_CONNECTED state), or it indicates Single RRC_CONNECTED state notification. 2. The NG-RAN sends the UE Notification message to report the current RRC state for the UE (i.e. RRC_INACTIVE state or RRC_CONNECTED state). The current UE location information (i.e. TAI + Cell Identity) is always included when RRC state information is reported. 2b. When the AMF has requested reporting about subsequent state transitions, the NG-RAN sends subsequent UE Notification messages to the AMF at every RRC state transition until the UE transitions to CM-IDLE or NG-RAN receives a Cancel UE State Notification message from the AMF. When the AMF has requested reporting for Single RRC_CONNECTED state notification and UE is in RRC_CONNECTED state, the NG-RAN sends one UE Notification message but no subsequent messages. If UE is in RRC_INACTIVE state, the NG-RAN sends one UE Notification message plus one subsequent UE Notification message when RRC state transits to RRC_CONNECTED. 3. The AMF can send a Cancel UE State Notification message to inform the NG-RAN that it should terminate notifications for a given UE. This message should only be used when notification(s) about subsequent state transitions was requested at every RRC state transition.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.8.3

6.46.10 Positioning aspects for satellite access

For a 5G system with satellite access, the following requirements apply: - Subject to regulatory requirements and operator’s policy, a 5G system with satellite access shall be able to support 3GPP positioning methods for UEs using only satellite access. - A 5G system with satellite access shall be able to provide positioning service to a UE using only satellite access and the information on positioning services (e.g. supported positioning performance). NOTE: UE can be with or without GNSS capabilities - A 5G system with satellite access shall be able to support negotiation of positioning methods, between UE and network, according e.g. to 3GPP RAT and UE positioning capability, the availability of non-3GPP positioning technologies (e.g. GNSS).

3GPP TS 22.261

Service requirements for the 5G system

SA WG1

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

6.46.10

8.3.2 Session Management

The mobile station and network shall ignore a session management message with TI EXT bit = 0. Otherwise, the following procedures shall apply: a) Whenever any session management message except ACTIVATE PDP CONTEXT REQUEST, ACTIVATE SECONDARY PDP CONTEXT REQUEST, or SM-STATUS is received by the network specifying a transaction identifier which is not recognized as relating to an active PDP context or MBMS context,or to a PDP context or MBMS context that is in the process of activation or deactivation, the network shall send a SM-STATUS message with cause #81 "invalid transaction identifier value" using the received transaction identifier value including the extension octet and remain in the PDP-INACTIVE state. b) Whenever any session management message except REQUEST PDP CONTEXT ACTIVATION, REQUEST SECONDARY PDP CONTEXT ACTIVATION, REQUEST MBMS CONTEXT ACTIVATION, or SM-STATUS is received by the MS specifying a transaction identifier which is not recognized as relating to an active context or to a context that is in the process of activation or deactivation, the MS shall send a SM-STATUS message with cause #81 "invalid transaction identifier value" using the received transaction identifier value including the extension octet and remain in the PDP-INACTIVE state. c) When a REQUEST PDP CONTEXT ACTIVATION message, REQUEST SECONDARY PDP CONTEXT ACTIVATION message or REQUEST MBMS CONTEXT ACTIVATION message is received by the MS with a transaction identifier flag set to "1", this message shall be ignored. d) When an ACTIVATE PDP CONTEXT REQUEST message is received by the network specifying a transaction identifier which is not recognized as relating to a PDP context that is in the process of activation, and with a transaction identifier flag set to "1", this message shall be ignored. e) Whenever an ACTIVATE PDP CONTEXT REQUEST or ACTIVATE SECONDARY PDP CONTEXT REQUEST message is received by the network specifying a transaction identifier relating to a PDP context or MBMS context not in state PDP-INACTIVE, the network shall deactivate the old PDP context or MBMS context relating to the received transaction identifier without notifying the MS. Furthermore, the network shall continue with the activation procedure of a new PDP context as indicated in the received message. Whenever an ACTIVATE MBMS CONTEXT REQUEST message is received by the network specifying a transaction identifier relating to an MBMS context not in state PDP-INACTIVE, the network shall deactivate the old MBMS context relating to the received transaction identifier without notifying the MS. Furthermore, the network shall continue with the activation procedure of a new MBMS context as indicated in the received message. f) Whenever a REQUEST PDP CONTEXT ACTIVATION message or REQUEST SECONDARY PDP CONTEXT ACTIVATION message is received by the MS specifying a transaction identifier relating to a PDP context or MBMS context not in state PDP-INACTIVE, the MS shall locally deactivate the old PDP context or MBMS context relating to the received transaction identifier. Furthermore, the MS shall continue with the activation procedure of a new PDP context as indicated in the received message. Whenever a REQUEST MBMS CONTEXT ACTIVATION message is received by the MS specifying a transaction identifier relating to a PDP context or MBMS context not in state PDP-INACTIVE, the MS shall locally deactivate the old PDP context or MBMS context relating to the received transaction identifier. Furthermore, the MS shall continue with the activation procedure of a new MBMS context as indicated in the received message. g) When an ACTIVATE SECONDARY PDP CONTEXT REQUEST message is received by the network specifying a transaction identifier which is not recognized as relating to a PDP context that is in the process of activation and with a transaction identifier flag set to "1", this message shall be ignored.

3GPP TS 24.008

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

CT WG1

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

8.3.2

5.2.3.3.6 Nudm_SDM_Info service operation

Service Operation name: Nudm_SDM_Info Description: Consumer NF provides UDM with information about the status of the subscription data management procedures. This service operation is used for: - providing acknowledgement from the UE to UDM about successful delivery of Steering of Roaming information via the AMF as defined in TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [22]. - providing acknowledgement from the UE to UDM about successful Network Slicing Configuration subsequent to delivery of the Network Slicing Subscription Change Indication via the AMF. - providing acknowledgement from the UE to UDM about successful delivery of UDM Update Data via the AMF as defined in clause 4.20. - providing acknowledgement from the AMF to UDM that the delivery of the UDM Update Data has failed as defined in clause 4.20. Inputs, Required: SUPI, Info (e.g. UE acknowledgment of SoR information from UDM via AMF, UE acknowledgement of successful Network Slicing Configuration subsequent to delivery of the Network Slicing Subscription Change Indication via the AMF, UE acknowledgment of UDM Update Data from UDM via AMF, failed transmission of UDM Update Data from UDM via AMF, failed transmission of SoR information from UDM via AMF). Inputs, Optional: None. Outputs, Required: None. Outputs, Optional: None.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

5.2.3.3.6

4.1.1 Offline charging

Offline charging is a process where charging information for network resource usage is collected concurrently with that resource usage. The charging information is then passed through a chain of logical charging functions that are further explained in clause 4.3.1 and clause 4.3.3. At the end of this process, CDR files are generated by the network, which are then transferred to the network operator's BD for the purpose of subscriber billing and/or inter-operator accounting (or additional functions, e.g. statistics, at the operator’s discretion). The BD typically comprises post-processing systems such as the operator's billing system or billing mediation device. In conclusion, offline charging is a mechanism where charging information does not affect, in real-time, the service rendered.

3GPP TS 32.240

Telecommunication management; Charging management; Charging architecture and principles

SA WG5

3GPP Series : 32 , OAM&P and Charging

4.1.1

8.3.6.15 Extended protocol configuration options

This IE is included in the message when the network wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the UE and the extended protocol configuration options is supported by both the UE and the network end-to-end for the PDN connection (see clause 6.6.1.1). This IE shall be included if the network supports Local IP address in the traffic flow aggregate description and TFT filter, the PDN Type is different from Non-IP and Ethernet, and the extended protocol configuration options is supported by both the UE and the network end-to-end for the PDN connection (see clause 6.6.1.1).

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

8.3.6.15

6.26.2.5 Traffic types

A 5G system shall support all media types (e.g. voice, data, multimedia) for 5G LAN-type service. The 5G system shall support traffic scenarios typically found in a home setting (from sensors to video streaming, relatively low amount of UEs per group, many devices are used only occasionally) for 5G LAN-type service. The 5G system shall support traffic scenarios typically found in an office setting (from sensors to very high data rates e.g. for conferencing, medium amount of UEs per group) for 5G LAN-type service. The 5G system shall support traffic scenarios typically found in an industrial setting (from sensors to remote control, large amount of UEs per group) for 5G LAN-type service.

3GPP TS 22.261

Service requirements for the 5G system

SA WG1

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

6.26.2.5

4.22.9.1 Registration procedures

Support for using the Registration procedures for non-3GPP access path switching is described in clause 4.22.9.5. The signalling flow for a Registration is based on the signalling flow in Figure 4.2.2.2.2-1 with the following differences and clarifications: - In step 1, if the UE wants to re-activate the user plane of the MA PDU Session(s) over the access the Registration message is sent to, the UE indicates PDU Session ID(s) of the MA PDU Session(s) in the List Of PDU Sessions To Be Activated. If the UE locally releases the MA PDU Session(s) in both accesses, the UE indicates it in the PDU Session Status. If the AMF receives the PDU Session Status and finds mismatch, regardless of roaming mode of the MA PDU Session(s) (i.e. non-roaming, local breakout roaming, home routed roaming in the same PLMN or home routed roaming in different PLMNs), the AMF invokes Nsmf_PDUSession_ReleaseSMContext service towards the SMF(s) in order to release any network resources related to the MA PDU Session(s). - In step 4, the old AMF determines whether the new AMF support ATSSS or not based on the supported features provided by the new AMF. - In step 5, if the old AMF determined in step 4 that the new AMF does not support ATSSS, the old AMF does not include the PDU Session context of the MA PDU Session(s) in the UE context transferred to the new AMF. - If the old AMF has not included MA PDU Session(s) in the UE context in step 5, the old AMF informs the corresponding SMF(s) to release the MA PDU Session(s) by invoking the Nsmf_PDUSession_ReleaseSMContext service operation as described in clause 4.22.10. - In step 21, the AMF provides an MA PDU Session Support indicator in Registration Accept message to inform the UE whether ATSSS is supported or not. The UE uses this indicator to determine whether an MA PDU session related procedure can be initiated or not, as described in clause 4.22.1. In step 17, if the UE indicated to re-activate MA PDU Session(s) in the List Of PDU Sessions To Be Activated the AMF includes access type which the Registration Request message is received on when the AMF triggers Nsmf_PDUSession_UpdateSMContext service operation. The SMF only re-activates user plane resources of the access type the Registration Request message is received on. - In step 21, the AMF indicates to the UE whether it supports non-3GPP access path switching. - In step 22, if the AMF indicates that the PDU Session(s) has been released in the PDU Session Status to the UE in Registration Accept message, the UE removes locally any internal resources related to the MA PDU Session(s) that are not marked as established.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.22.9.1

10.5.4.22b SETUP Container $(CCBS)$

This information element contains the contents of a SETUP message (Mobile Station to Network). This means that the Call Control protocol discriminator IE, the Transaction Identifier IE and the Setup message type IE are not included. The SETUP Container information element is coded as shown in figure 10.5.111/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The SETUP Container is a type 4 information. No upper length limit is specified except for that given by the maximum number of octets in a L3 message (see 3GPP TS 44.006[ None ] [19]). Figure 10.5.111/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Octet j (j = 3, 4 ... n) is the unchanged octet j of the SETUP message.

3GPP TS 24.008

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

CT WG1

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

10.5.4.22b

Annex F (informative): Distributed deployment models F.1 General

This annex provides information that the charging functions can be deployed in multiple physical locations. This annex provides an overview of two deployment models: Centralized Model and Local/Edge Deployment Model. It’ll focus on possibiliby of deploying different CHF instances, and respective charging functions in different physical locations. Nevertheless, its considered only 1(one) Converged Charging System as defined in TS 32.240[ Telecommunication management; Charging management; Charging architecture and principles ] . This annex can be used to support the design of Charging Architecture in 5GS.

3GPP TS 32.240

Telecommunication management; Charging management; Charging architecture and principles

SA WG5

3GPP Series : 32 , OAM&P and Charging

Annex

9.9.2.1.1 FDD

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

3GPP TS 36.101

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

RAN4

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

9.9.2.1.1

6.50 Traffic steering and switching over two 3GPP access networks 6.50.2.1 General

Subject to HPLMN policy and network control, the 5G system shall be able to support mechanisms to enable traffic steering and/or switching of a DualSteer device’s user data (for different services) across two 3GPP access networks belonging to the same PLMN (either HPLMN or VPLMN), assuming data anchoring in the HPLMN and non-simultaneous transmission over the two networks. Subject to HPLMN policy and network control, the 5G system may be able to support mechanisms to enable traffic steering and/or switching with simultaneous transmission of a DualSteer device’s user data (for different services) across two 3GPP access networks belonging to the same PLMN (either HPLMN or VPLMN), assuming data anchoring in the HPLMN. Subject to HPLMN policy and network control, the 5G system shall be able to support mechanisms to enable traffic steering and/or switching of a DualSteer device’s user data (for different services) across two 3GPP access networks belonging to two PLMNs, assuming a business/roaming agreement between PLMN operators (if different), data anchoring in the HPLMN and non-simultaneous transmission over the two networks. Subject to HPLMN policy and network control, the 5G system may be able to support mechanisms to enable traffic steering and/or switching with simultaneous transmission of a DualSteer device’s user data (for different services) across two 3GPP access networks belonging to two PLMNs, assuming a business/roaming agreement between PLMN operators (if different) and HPLMN data anchoring. NOTE 1: Inter-PLMN requirements can apply also to PLMN-NPN scenarios assuming a PLMN-integrated NPN (NPN hosted by a PLMN or offered as a slice of a PLMN). For traffic steering and/or switching of user data across two 3GPP access networks, the 5G system shall be able to allow a HPLMN to provide policies and criteria for a DualSteer device to connect to an additional PLMN/NPN, or an additional RAT within the same PLMN. NOTE 2: The above requirements assume configuration of traffic policies, under HPLMN control or negotiated between the HPLMN and other network operators, considering e.g., user subscription, application/traffic type, service preference, QoS requirements, location, time, UE capabilities, mobility, connectivity conditions. For any particular service, at any given time, the DualSteer device shall transmit all traffic of that service using only a single 3GPP access network.

3GPP TS 22.261

Service requirements for the 5G system

SA WG1

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

6.50

15.5.3 Support for RACH Optimization

RACH optimization is supported by UE reported information made available at the NG RAN node as specified in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12] and by PRACH parameters exchange between NG RAN nodes. The contents of the RA Report comprise of the following: - Contention detection indication per RACH attempt; - Indexes of the SSBs and number of RACH preambles sent on each tried SSB listed in chronological order of attempts; - Indication whether the selected SSB is above or below the configured RSRP threshold per RACH attempt; - 2-step RACH information as specified in clause 5.7.10.4 of TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12]. SN RA Reports The UE operating in NR-DC, may also support collection of RA Reports by the SN. The RA report retrieval and forwarding in case of NGEN-DC is specified in TS 37.340[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 ] [21].

3GPP TS 38.300

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

RAN2

3GPP Series : 38 , Radio technology beyond LTE

15.5.3

5.3.5.10 MR-DC release

The UE shall: 1> as a result of MR-DC release triggered by E-UTRA or NR: 2> release SRB3, if established, as specified in 5.3.5.6.2; 2> release SRB5, if established, as specified in 5.3.5.6.2; 2> release measConfig associated with SCG; 2> if the UE is configured with NR SCG: 3> release the SCG configuration as specified in clause 5.3.5.4; 3> release otherConfig associated with the SCG, if configured; 3> release successPSCell-Config configured by the PCell in the otherConfig, if configured; 3> stop timers T346a, T346b, T346c, T346d, T346e, T346j and T346k associated with the SCG, if running; 3> release bap-Config associated with the SCG, if configured; 3> release the BAP entity as specified in TS 38.340[ NR; Backhaul Adaptation Protocol (BAP) specification ] [47], if there is no configured bap-Config; 3> release iab-IP-AddressConfigurationList associated with the SCG, if configured; 2> else if the UE is configured with E-UTRA SCG: 3> release the SCG configuration as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10], clause 5.3.10.19 to release the E-UTRA SCG;

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

5.3.5.10

10.5.6.20 WLAN offload acceptability

The purpose of the WLAN offload acceptability information element is to indicate whether traffic can be offloaded using a PDN connection via a WLAN, or not. The values "offloading the traffic of the PDN connection via a WLAN when in S1 mode is acceptable" and "offloading the traffic of the PDN connection via a WLAN when in Iu mode is acceptable" map to "indication that the PDP context is offloadable" as defined in 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [74] and 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [122]. The value "offloading the traffic of the PDN connection via a WLAN when in S1 mode is not acceptable" and "offloading the traffic of the PDN connection via a WLAN when in Iu mode is not acceptable" map to "indication that the PDP context is not offloadable" as defined in 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [74] and 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [122]. The procedures in 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [74] when the MS receives the UTRAN offload acceptability value in A/Gb mode or Iu mode apply. The procedures in 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [122] when the MS receives the E-UTRAN offload acceptability value in S1 mode apply. The WLAN offload acceptability information element is coded as shown in figure 10.5.6.20-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.6.20-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The WLAN offload acceptability is a type 1 information element. Figure 10.5.6.20-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : WLAN offload acceptability information element Table 10.5.6.20-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : WLAN offload acceptability information element

3GPP TS 24.008

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

CT WG1

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

10.5.6.20

16.12.6 Service Continuity for L2 U2N relay 16.12.6.0 General

The service continuity procedure is applicable only for the mobility cases of path switch from indirect to direct path, and from direct to indirect path when the L2 U2N Remote UE and L2 U2N Relay UE belong to the same gNB or different gNB. This procedure is also applicable for the mobility cases of path switch from indirect to indirect path when the two L2 U2N Relay UEs belong to the same gNB or different gNBs. For inter-gNB path switching, the source gNB decides to trigger path switching and the path switch type, i.e. direct or indirect path.

3GPP TS 38.300

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

RAN2

3GPP Series : 38 , Radio technology beyond LTE

16.12.6

5.2.2 UE behaviour in state 5GMM-DEREGISTERED 5.2.2.1 General

The state 5GMM-DEREGISTERED is entered in the UE, when: a) the de-registration is performed either by the UE or by the network (see subclause 5.5.2); b) the registration request is rejected by the AMF (see subclause 5.5.1.2.5 and 5.5.1.3.5); c) the service request is rejected by the AMF (see subclause 5.6.1); d) the UE is switched on; or e) the UE registered for emergency services is in 5GMM-IDLE mode and its periodic registration update timer expires (see subclause 5.3.7). In state 5GMM-DEREGISTERED, the UE shall behave according to the substate as explained in subclause 5.2.2.3.

3GPP TS 24.501

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

CT WG1

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

5.2.2

K.4 Call control information elements.

For the call control information elements listed below, the default coding of the information element identifiers is defined in table K.4/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Table K.4/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Default information element identifier coding for call control information elements NOTE: These values were allocated but never used in earlier phases of the protocol.

3GPP TS 24.008

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

CT WG1

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

K.4

4.2.2.3.2 UE-initiated Deregistration

The UE uses this procedure to deregister from the registered PLMN as shown in Figure 4.2.2.3.2-1. Figure 4.2.2.3.2-1: UE-initiated Deregistration 1. The UE sends NAS message Deregistration Request (5G-GUTI, Deregistration type (e.g. Switch off), Access Type, [Unavailability Period Duration], [NAS message container]) to the AMF. Access type indicates whether the Deregistration procedure applies to the 3GPP access, to the non-3GPP access, or to both if the 3GPP access and non-3GPP access of the UE are served by the same AMF (refer to TS 23.501[ System architecture for the 5G System (5GS) ] [2]). The AMF shall invoke the Deregistration procedure for the target access indicated by the UE. If the UE and network support Unavailability Period and an event is triggered in the UE that would make the UE unavailable for a period of time, the UE includes Unavailability Period Duration as described in clause 5.4.1.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The NAS message container shall be included if the UE is sending a Deregistration Request message as an Initial NAS message and the UE has a valid 5G NAS security context and the UE needs to send non-cleartext IEs, see clause 4.4.6 of TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [25]. If the UE does not need to send non-cleartext IEs, the UE shall send a Deregistration Request message without including the NAS message container. 1a. [Conditional] If the Deregistration Request message was not sent integrity protected or integrity protection verification failed, the NAS security initiation is performed as described in TS 33.501[ Security architecture and procedures for 5G System ] [15], the UE includes the full Deregistration Request message as defined in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [25]. 2. [Conditional] AMF to SMF (or V-SMF): Nsmf_PDUSession_ReleaseSMContext (SM Context ID). If the UE has no established PDU Session over the target access indicated in step 1, then steps 2 to 5 are not executed. All PDU Sessions over the target access(es), which belong to the UE are released by the AMF sending Nsmf_PDUSession_ReleaseSMContext Request (SM Context ID) message to the SMF (or V-SMF) for each PDU Session. If the AMF determines that the secondary RAT usage reporting is required for the PDU Session, the AMF shall execute step 7 and 8 and then wait for the completion of step 8 to receive the secondary RAT usage data from the NG-RAN. After that, steps 2 to 6 in this procedure are performed to e.g. release the PDU Session(s). For home routed roaming case, the V-SMF initiates the release of the PDU Session at the H-SMF by invoking the Nsmf_PDUSession_Release request. 3. [Conditional] The SMF (or H-SMF) releases all resources e.g. the IP address / Prefix(es) that were allocated to the PDU Session and releases the corresponding User Plane resources: 3a. [Conditional] The SMF (or H-SMF) sends N4 Session Release Request (N4 Session ID) message to the UPF(s) of the PDU Session. The UPF(s) shall drop any remaining packets of the PDU Session and release all tunnel resource and contexts associated with the N4 Session. 3b. [Conditional] The UPF(s) acknowledges the N4 Session Release Request by the transmission of an N4 Session Release Response (N4 Session ID) message to the SMF. 4. [Conditional] The SMF (or V-SMF) responds with Nsmf_PDUSession_ReleaseSMContext Response message. For home routed roaming case, the H-SMF responds to the V-SMF with a Nsmf_PDUSession_Release response. The V-SMF releases the corresponding User Plane resources. The V-SMF responds to AMF with Nsmf_PDUSession_ReleaseSMContext Response message. 5a. [Conditional] If dynamic PCC applied to this session the SMF performs an SM Policy Association Termination procedure as defined in clause 4.16.6. 5b-c. [Conditional] If it is the last PDU Session the SMF is handling for the UE for the associated (DNN, S-NSSAI), the SMF unsubscribes from Session Management Subscription data changes notification with the UDM by means of the Nudm_SDM_Unsubscribe service operation. The SMF invokes the Nudm_UECM_Deregistration service operation so that the UDM removes the association it had stored between the SMF identity and the associated DNN and PDU Session Id. 6. [Conditional] If there is any association with the PCF for this UE and the UE is no more registered over any access, the AMF performs a AMF-initiated AM Policy Association Termination procedure as defined in clause 4.16.3.2 delete the association with the PCF. 6a. [Conditional] If there is any association with the PCF for this UE and the UE is no more registered over any access, the AMF performs a AMF-initiated UE Policy Association Termination procedure as defined in clause 4.16.13.1 delete the association with the PCF. 7. [Conditional] The AMF sends NAS message Deregistration Accept to UE depending on the Deregistration type i.e. if Deregistration type is switch-off, AMF does not send Deregistration Accept message. 7a [Conditional] If Unavailability Period Duration is received from the UE and there is "Loss of Connectivity" monitoring event subscription for the UE, the AMF triggers "Loss of Connectivity" monitoring event report and includes the remaining value of the Unavailability Period Duration. 8. [Conditional] AMF to AN: N2 UE Context Release Request (Cause) If the target access for Deregistration procedure is 3GPP access or both 3GPP access and non-3GPP access and there is N2 signalling connection to NG-RAN, the AMF sends N2 UE Release command to NG-RAN with Cause set to Deregistration to release N2 signalling connection. The details of this step are covered by steps 2 to 4 in the AN Release procedure, as described in clause 4.2.6. If the target access for Deregistration procedure is non-3GPP access or both 3GPP access and non-3GPP access and there is N2 signalling connection to the N3IWF/TNGF/W-AGF, the AMF sends N2 UE Release command to N3IWF/TNGF/W-AGF with Cause set to Deregistration to release N2 signalling connection. The details of this step are covered by steps 2 to 5 in the "Deregistration procedure for (un)trusted non-3gpp access", as described in clauses 4.12.3 / 4.12a.3 and in clause 7.2.1 of TS 23.316[ Wireless and wireline convergence access support for the 5G System (5GS) ] [53] for W-5GAN access.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.2.2.3.2

6.1.3.1a Sidelink BSR MAC Control Elements

Sidelink BSR and Truncated Sidelink BSR MAC control elements consist of one Destination Index field, one LCG ID field and one corresponding Buffer Size field per reported target group. The Sidelink BSR MAC control elements are identified by MAC PDU subheaders with LCIDs as specified in table 6.2.1-2. They have variable sizes. For each included group, the fields are defined as follows (figures 6.1.3.1a-1 and 6.1.3.1a-2): - Destination Index: The Destination Index field identifies the ProSe Destination or the destination for V2X sidelink communication. The length of this field is 4 bits. The value is set to the index of the destination reported in destinationInfoList for sidelink communication or is set to one index among index(es) associated to same destination reported in v2x-DestinationInfoList for V2X sidelink communication. If multiple such lists are reported, the value is indexed sequentially across all the lists in the same order as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]; - LCG ID: The Logical Channel Group ID field identifies the group of logical channel(s) which buffer status is being reported. The length of the field is 2 bits; - Buffer Size: The Buffer Size field identifies the total amount of data available across all logical channels of a LCG of a ProSe Destination 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 and in the PDCP 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] and TS 36.323[ Evolved Universal Terrestrial Radio Access (E-UTRA); Packet Data Convergence Protocol (PDCP) specification ] [4] respectively. The size of the RLC and MAC headers are not considered in the buffer size computation. The length of this field is 6 bits. The values taken by the Buffer Size field are shown in Table 6.1.3.1-1; - R: Reserved bit, set to "0". Buffer Sizes of LCGs are included in decreasing order of the highest priority of the sidelink logical channel belonging to the LCG irrespective of the value of the Destination Index field. Figure 6.1.3.1a-1: Sidelink BSR and Truncated Sidelink BSR MAC control element for even N Figure 6.1.3.1a-2: Sidelink BSR and Truncated Sidelink BSR MAC control element for odd N

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

6.6.3 UP confidentiality mechanisms

The PDCP protocol, as specified in TS 38.323[ NR; Packet Data Convergence Protocol (PDCP) specification ] [23] between the UE and the NG-RAN, shall be responsible for user plane data confidentiality protection. The use and mode of operation of the 128-bit NEA algorithms are specified in Annex D. The input parameters to the 128-bit NEA algorithms as described in Annex D are the message packet, an 128-bit cipher key KUPenc as KEY, a 5-bit bearer identity BEARER which value is assigned as specified by TS 38.323[ NR; Packet Data Convergence Protocol (PDCP) specification ] [23], the 1-bit direction of transmission DIRECTION, the length of the keystream required LENGTH and a bearer specific, and direction dependent 32-bit input COUNT which corresponds to the 32-bit PDCP COUNT.

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

6.6.3

5.2.26.2.3 Nupf_EventExposure_Subscribe service operation

Service operation name: Nupf_EventExposure_Subscribe Description: This service operation is used by an NF to subscribe or modify a subscription to UPF event exposure notifications e.g. for the purpose of UPF data collection on a specified PDU Session or for all PDU Sessions of one UE or any UE. Input, Required: NF ID, Target of Event Reporting, (set of) Event ID(s) defined in clause 5.2.26.2.1, Notification Target Address (+ Notification Correlation ID), Event Reporting Information defined in Table 4.15.1-1. Input, Optional: Subscription Correlation ID (in the case of modification of the event subscription), Expiry time, DNN, S-NSSAI, Application ID(s), traffic filtering information, Type of measurement, granularity of measurement, Reporting suggestion information. Output, Required: When the subscription is accepted: Subscription Correlation ID (required for management of this subscription), Expiry time (required if the subscription can be expired based on the operator's policy). Output, Optional: First corresponding event report is included, if available (see clause 4.15.1). Notification Target Address (+ Notification Correlation ID) is used to correlate Notifications sent by UPF with this subscription.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

5.2.26.2.3

5.11 UE Capability Handling 5.11.1 General

The UE Capability information is made up of the UE Radio Capability information and the UE Core Network Capability information. The UE Radio Capability for Paging Information is separate from both the UE Radio Capability information and the UE Core Network Capability information. While some of the UE Radio Capability for Paging Information may be used to enhance the paging in the E-UTRAN, other E-UTRAN features are critically dependent upon it (see TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]).

3GPP TS 23.401

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

SA WG2

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

5.11

5.3.14 List of equivalent PLMNs

The UE shall store a list of equivalent PLMNs. These PLMNs shall be regarded by the UE as equivalent to each other for PLMN selection and cell selection/re-selection. The same list is used by 5GMM, EMM, GMM and MM (see 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] and 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [12]) except for the case when the UE operates in dual-registration mode (see subclause 4.8.3). The UE shall update or delete this list at the end of each registration procedure. The stored list consists of a list of equivalent PLMNs as downloaded by the network plus the PLMN code of the registered PLMN that downloaded the list. When the UE is switched off, the UE shall keep the stored list so that it can be used for PLMN selection after switch on. The UE shall delete the stored list if the USIM is removed or when the UE registered for emergency services enters the state 5GMM-DEREGISTERED. The maximum number of possible entries in the stored list is 16. If the UE registers to different PLMNs over 3GPP and non-3GPP accesses, the UE shall store an additional list of equivalent PLMNs associated with non-3GPP access. The UE manages the two lists of equivalent PLMNs per access type independently.

3GPP TS 24.501

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

CT WG1

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

5.3.14

13.2.3.4 Modification policy

The SEPP shall contain an operator-controlled policy that specifies which IEs can be modified by the IPX provider directly related to this particular SEPP. These IEs refer to the IEs after the sending SEPP has rewritten the message. Each PLMN-operator shall agree the modification policy with the IPX provider it has a business relationship with prior to establishment of an N32 connection. Each modification policy applies to one individual relation between PLMN-operator and IPX provider. To cover the whole N32 connection, both involved roaming partners shall exchange their modification policies. NOTE 1: In order to validate modifications for messages received on the N32-f interface, the operator’s roaming partners will have to know the overall modification policy. NOTE 2: Modification includes removal and addition of new IE. IEs therefore may not be present in the rewritten message. The IEs that the IPX is allowed to modify shall be specified in a list giving an enumeration of JSON paths within the JSON object created by the SEPP. Wildcards may be used to specify paths. This policy shall be specific per roaming partner and per IPX provider that is used for the specific roaming partner. The modification policy shall reside in the SEPP. For each roaming parter, the SEPP shall be able to store a policy for receiving. The following basic validation rules shall always be applied irrespective of the policy exchanged between two roaming partners: - IEs requiring encryption shall not be inserted at a different location in the JSON object.

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

13.2.3.4

9.2.1 Authentication reject

This message is sent by the network to the mobile station to indicate that authentication has failed (and that the receiving mobile station shall abort all activities). See table 9.2.2/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Message type: AUTHENTICATION REJECT Significance: dual Direction: network to mobile station Table 9.2.2/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : AUTHENTICATION REJECT message content

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

7.3.1 Overview

System Information (SI) consists of a MIB and a number of SIBs, which are divided into Minimum SI and Other SI: - Minimum SI comprises basic information required for initial access and information for acquiring any other SI. Minimum SI consists of: - MIB contains cell barred status information and essential physical layer information of the cell required to receive further system information, e.g. CORESET#0 configuration. MIB is periodically broadcast on BCH. - SIB1 defines the scheduling of other system information blocks and contains information required for initial access. SIB1 is also referred to as Remaining Minimum SI (RMSI) and is periodically broadcast on DL-SCH or sent in a dedicated manner on DL-SCH to UEs in RRC_CONNECTED. - Other SI encompasses all SIBs not broadcast in the Minimum SI. Those SIBs can either be periodically broadcast on DL-SCH, broadcast on-demand on DL-SCH (i.e. upon request from UEs in RRC_IDLE, RRC_INACTIVE, or RRC_CONNECTED), or sent in a dedicated manner on DL-SCH to UEs in RRC_CONNECTED (i.e., upon request, if configured by the network, from UEs in RRC_CONNECTED or when the UE has an active BWP with no common search space configured or when the UE configured with inter cell beam management is receiving DL-SCH from a TRP with PCI different from serving cell's PCI). Other SI consists of: - SIB2 contains cell re-selection information, mainly related to the serving cell; - SIB3 contains information about the serving frequency and intra-frequency neighbouring cells relevant for cell re-selection (including cell re-selection parameters common for a frequency as well as cell specific re-selection parameters); - SIB4 contains information about other NR frequencies and inter-frequency neighbouring cells relevant for cell re-selection (including cell re-selection parameters common for a frequency as well as cell specific re-selection parameters), which can also be used for NR idle/inactive measurements; - SIB5 contains information about E-UTRA frequencies and E-UTRA neighbouring cells relevant for cell re-selection (including cell re-selection parameters common for a frequency as well as cell specific re-selection parameters); - SIB6 contains an ETWS primary notification; - SIB7 contains an ETWS secondary notification; - SIB8 contains a CMAS warning notification; - SIB9 contains information related to GPS time and Coordinated Universal Time (UTC); - SIB10 contains the Human-Readable Network Names (HRNN) of the NPNs listed in SIB1; - SIB11 contains information related to idle/inactive measurements; - SIB15 contains information related to disaster roaming; - SIB16 contains slice-based cell reselection information; - SIB17 contains information related to TRS configuration for UEs in RRC_IDLE/RRC_INACTIVE; - SIBpos contains positioning assistance data as defined in TS 37.355[ LTE Positioning Protocol (LPP) ] [43] and TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12]; - SIB18 contains information related to the Group IDs for Network selection (GINs) associated with SNPNs listed in SIB1. - SIB19 in TN contains NTN-specific parameters for NTN neighbour cells as defined in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12]. For sidelink, Other SI also includes: - SIB12 contains information related to NR sidelink communication; - SIB13 contains information related to SystemInformationBlockType21 for V2X sidelink communication as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] clause 5.2.2.28 [29]; - SIB14 contains information related to SystemInformationBlockType26 for V2X sidelink communication as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] clause 5.2.2.33 [29]; - SIB23 contains information related to ranging and sidelink positioning. For non-terrestrial network, Other SI also includes: - SIB19 contains NTN-specific parameters for serving cell and optionally NTN-specific parameters for neighbour cells as defined in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12]. - SIB25 contains TN coverage are information as defined in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12]. For MBS broadcast, Other SI also includes: - SIB20 contains MCCH configuration; - SIB21 contains information related to service continuity for MBS broadcast reception. For ATG network, Other SI also includes: - SIB22 contains ATG-specific parameters for serving cell and optionally ATG-specific parameters for neighbour cells as defined in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12]. Figure 7.3.1-1 below summarises System Information provisioning. Figure 7.3.1-1: System Information Provisioning For a cell/frequency that is considered for camping by the UE, the UE is not required to acquire the contents of the minimum SI of that cell/frequency from another cell/frequency layer. This does not preclude the case that the UE applies stored SI from previously visited cell(s). If the UE cannot determine the full contents of the minimum SI of a cell by receiving from that cell, the UE shall consider that cell as barred. In case of BA, the UE only acquires SI on the active BWP. If the UE is configured with inter cell beam management: - the UE is not required to acquire the SI from the serving cell while it is receiving DL-SCH from a TRP with PCI different from serving cell's PCI.

3GPP TS 38.300

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

RAN2

3GPP Series : 38 , Radio technology beyond LTE

7.3.1

20.3 Network based solution 20.3.1 General

In this solution the MSC Server enhanced for ICS performs a special IMS registration on behalf of the UE. Thus, the MSC Server enhanced for ICS shall use a Private User Identity and Temporary Public User Identity that are different to those defined in clause 13 (see 3GPP TS 23.292[ IP Multimedia Subsystem (IMS) centralized services; Stage 2 ] [70], clause 4.6.2 for more information). Furthermore, the MSC Server enhanced for ICS derives a Conference Factory URI that is known to the home IMS. These are defined in the following clauses.

3GPP TS 23.003

Numbering, addressing and identification

CT WG4

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

20.3

6.15a.5.2 Requirements

Subject to operator’s policy and agreement with 3rd party, the 5G system shall be able to expose information on energy consumption for serving this 3rd party. NOTE 1: Energy consumption information can include ratio of renewable energy and carbon emission information when available. The reporting period could be set, e.g., on monthly or yearly basis and can vary based on location. NOTE 2: The energy consumption information can be related to the network resources of network slice, NPNs, etc. Subject to operator’s policy,agreement with 3rd party and consent by the customer, the 5G system shall be able to expose the network performance statistic information (e.g. the data rate, packet delay and packet loss) together with energy consumption information resulting from service provided to the customer, to the authorized third party, related to the same time interval e.g. hourly or daily. Subject to operator’s policy, the 5G system shall support a means to expose energy consumption to authorized third parties for services, including energy consumption information related to the condition of energy credit limit (e.g. when the energy consumption is reaching the energy credit limit). Subject to operator policy, the 5G system shall provide means for the trusted 3rd party, to configure which network performance statistic information (e.g. the data rate, packet delay and packet loss) for the communication service provided to the 3rd party, needs to be exposed along with the information on energy consumption for serving this 3rd party. Based on operator’s policy and agreement with 3rd party, the 5G system shall be able to expose energy consumption information and prediction on energy consumption of the 5G network per application service to the 3rd party. Subject to operator’s policy and agreement with 3rd party, the 5G system shall support a mechanism for the 3rd party to provide current or predicted energy consumption information over a specific period of time.

3GPP TS 22.261

Service requirements for the 5G system

SA WG1

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

6.15a.5.2

6.6.2 Requirements

The 5G system shall enable efficient delivery of content from a content caching application under the control of the operator (e.g. a cache located close to the UE). The 5G system shall support a content caching application in a UE under the control of the operator. The 5G system shall support configurations of content caching applications in the network (e.g. access network, core network), that provide content close to the UE. Based on operator policy, the 5G system shall support an efficient mechanism for selection of a content caching application (e.g. minimize utilization of radio, backhaul resources and/or application resource) for delivery of the cached content to the UE. The 5G system shall support a mechanism for the operator to manage content distribution across content caching applications. The 5G system shall support delivery of cached content from a content caching application via the broadcast/multicast service. For a 5G system with satellite access, the following requirement applies. - A 5G system with satellite access shall be able to optimise the delivery of content from a content caching application by taking advantage of satellites in supporting ubiquitous service, as well as broadcasting/multicasting on very large to global coverages.

3GPP TS 22.261

Service requirements for the 5G system

SA WG1

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

6.6.2

7.1.5 Network Function and Network Function Service registration and de-registration

For the NRF to properly maintain the information of available NF instances and their supported services, each NF instance informs the NRF of the list of NF services that it supports. NOTE: The NF informs the appropriate NRF based on configuration. The NF instance may make this information available to NRF when the NF instance becomes operative for the first time (registration operation) or upon individual NF service instance activation/de-activation within the NF instance (update operation) e.g. triggered after a scaling operation. The NF instance while registering the list of NF services it supports, for each NF service, may provide a notification endpoint information for each type of notification service that the NF service is prepared to consume, to the NRF during the NF instance registration. The NF instance may also update or delete the NF service related parameters (e.g. to delete the notification endpoint information). Alternatively, another authorised entity (such as an OA&M function) may inform the NRF on behalf of an NF instance triggered by an NF service instance lifecycle event (register or de-registration operation depending on instance instantiation, termination, activation, or de-activation). Registration with the NRF includes capacity and configuration information at time of instantiation. The NF instance may also de-registers from the NRF when it is about to gracefully shut down or disconnect from the network in a controlled way. If an NF instance become unavailable or unreachable due to unplanned errors (e.g. NF crashes or there are network issues), an authorised entity shall de-register the NF instance with the NRF.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

7.1.5

5.3.4B.3 Mobile Terminated Data Transport in Control Plane CIoT EPS Optimisation with P-GW connectivity

Figure 5.3.4B.3-1: MT Data transport in NAS PDUs 0. The UE is EPS attached and in ECM-Idle mode. 1. When the S-GW receives a downlink data packet/control signalling for a UE, if the S- GW context data indicates no downlink user plane TEID towards the MME), it buffers the downlink data packet and identifies which MME is serving that UE. If that MME has requested the Serving GW to throttle downlink low priority traffic and if the downlink data packet is received on a low priority bearer to be throttled (see clause 4.3.7.4.1a), the S-GW drops the downlink data. The steps below are not executed. If that MME has requested the S-GW to delay sending the Downlink Data Notification (see clause 5.3.4.2 on "Handling of abnormal conditions in UE triggered Service Request"), the Serving GW buffers the downlink data and waits until the timer expires before continuing with step 2. If the DL-TEID and MME address for that UE is received before the expiry of the timer, the timer shall be cancelled and the Mobile Terminated Data transport procedure is progressed from step 11 as Downlink data are sent to the UE. If the Serving GW receives additional downlink data packets/control signalling for this UE before the expiry of the timer, the Serving GW does not restart this timer. 2. If the Serving GW is buffering data in step 1, the Serving GW sends a Downlink Data Notification message (ARP, EPS Bearer ID) to the MME for which it has control plane connectivity for the given UE. The ARP and EPS Bearer ID are always set in Downlink Data Notification. The MME responds to the S-GW with a Downlink Data Notification Ack message. An MME detects that the UE is in a power saving state (e.g. Power Saving Mode) and cannot be reached by paging at the time of receiving Downlink data notification, shall invoke extended buffering depending on operator configuration, except for cases described in next paragraphs. The MME derives the expected time before radio bearers can be established to the UE. The MME then indicates Downlink Buffering Requested to the Serving GW in the Downlink Data Notification Ack message and includes a Downlink Buffering Duration time and optionally a Downlink Buffering Suggested Packet Count. The MME stores a new value for the Downlink Data Buffer Expiration Time in the MM context for the UE based on the Downlink Buffering Duration time and skips the remaining steps of this procedure. The Downlink Data Buffer Expiration Time is used for UEs using power saving state and indicates that there are buffered data in the Serving GW and that the user plane setup procedure is needed when the UE makes signalling with the network. When the Downlink Data Buffer Expiration Time has expired, the MME considers no Downlink data to be buffered and no indications of Buffered Downlink Data Waiting are sent during context transfers at TAU procedures. If there is an "Availability after DDN Failure" monitoring event configured for the UE in the MME, the MME does not invoke extended buffering. Instead, the MME sets the Notify-on-available-after-DDN-failure flag to remember to send an "Availability after DDN Failure" notification when the UE becomes available. If there is a "UE Reachability" monitoring event configured for the UE in the MME, the MME does not invoke extended buffering. NOTE 1: When "Availability after DDN failure" and "UE reachability" monitoring events are used for a UE, the application server is assumed to send data only when the UE is reachable, hence no extended buffering is needed. If there are multiple application servers, the event notifications and extended buffering may be needed simultaneously. It is assumed this is handled through additional information based on SLA as described in the next paragraph. The MME may use additional information based on a SLA with the MTC user for when to invoke extended buffering, e.g. only invoke it for a certain APN, do not invoke it for certain subscribers, invoke extended buffering in conjunction with "Availability after DDN failure" and "UE reachability" monitoring events, etc. A Serving GW that receives a Downlink Buffering Requested indication in a Downlink Data Notification Ack message stores a new value for the Downlink Data Buffer Expiration Time based on the Downlink Buffering Duration time and does not send any additional Downlink Data Notification if subsequent downlink data packets are received in the Serving GW before the buffer time Downlink Data Buffer Expiration Time has expired for the UE. If the Serving GW, while waiting for the user plane to be established, is triggered to send a second Downlink Data Notification for a bearer with higher priority (i.e. ARP priority level) than that of the bearer for which the first Downlink Data Notification was sent, the S-GW sends a new Downlink Data Notification message indicating the higher priority to the MME. If the Serving GW receives additional downlink data packets for a bearer with same or lower priority than the first Downlink Data Notification was sent for or if the Serving GW has sent the second Downlink Data Notification message indicating the higher priority and receives additional downlink data packets for this UE, the Serving GW buffers these downlink data packets and does not send a new Downlink Data Notification. If the Serving GW, while waiting for the user plane to be established, receives a Modify Bearer Request message from an MME other than the one it sent a Downlink Data Notification message to, the Serving GW re-sends the Downlink Data Notification message but only to the new MME from which it received the Modify Bearer Request message. If the MME holds stored Paging Restriction Information (see clause 4.3.33.6) for the UE that restricts the Downlink Data from causing paging, the MME sends Downlink Data Notification Ack message with an indication that the Downlink Data Notification message has been temporarily rejected. Upon reception of a Downlink Data Notification Ack message with an indication that the Downlink Data Notification message has been temporarily rejected and if the Downlink Data Notification is triggered by the arrival of downlink data packets at the Serving GW, the Serving GW may start a locally configured guard timer and buffers all downlink user packets received to the given UE and waits for a Modify Bearer Request message to come. Upon reception of a Modify Bearer Request message, the Serving GW re-sends the Downlink Data Notification message but only to the new MME from which it received the Modify Bearer Request message. Otherwise the Serving GW releases buffered downlink user packets upon expiry of the guard timer or upon receiving the Delete Session Request message from MME. If the S11-U is already established (buffering is in the MME), step 2 is not executed and step 11 is immediately executed. Steps 7,8,9,10 are executed only if conditions are met when the NAS control plane service request is received at step 6, as outlined below in the respective clauses. An MME detecting that the UE is in a power saving state (e.g. Power Saving Mode) and cannot be reached by paging at the time of receiving Downlink data, shall start extended buffering depending on operator configuration, except for cases described in next paragraphs. The MME derives the expected time before radio bearers can be established to the UE, stores a new value for the Downlink Data Buffer Expiration Time in the MM context for the UE and skips the remaining steps of this procedure. When the Downlink Data Buffer Expiration Time has expired, the MME considers no Downlink data to be buffered. Also for the case of buffering in the MME the "Availability after DDN Failure" monitoring event can be configured for the UE, even though the actual DDN is not received and the Downlink data is received. The "UE Reachability" monitoring event can also be configured. The extended buffering can also be configured as per what is described above in this step of the procedure for the case of buffering in S-GW. 3. If the UE is registered in the MME and considered reachable, the MME sends Paging message(s) as specified in step 3a of clause 5.3.4.3. 4. If eNodeBs receive paging messages from the MME, the UE is paged by the eNodeBs as specified in step 4a of clause 5.3.4.3. 5. As the UE is in the ECM-IDLE state, upon reception of paging indication, the UE sends Control Plane Service Request NAS message (as defined in TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [46]) over RRC Connection request and S1-AP initial message. The Control Plane Service Request NAS message, when Control Plane CIoT EPS Optimisation applies, does not trigger Data radio bearer establishment by the MME and the MME can immediately send Downlink Data it receives using a NAS PDU to the eNodeB. The MME supervises the paging procedure with a timer. If the MME receives no response from the UE to the Paging Request message, it may repeat the paging according to any applicable paging strategy described in step 3. If the Multi-USIM UE in ECM-IDLE state, upon reception of paging indication in E-UTRAN access and if the UE decides not to accept the paging, the UE attempts to send a Reject Paging Indication in the Control Plane Service Request NAS message (as defined in TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [46]) over RRC Connection request and S1-AP initial message. If the Control Plane Service Request NAS message includes a Reject Paging Indication, then: - If the Service Request message includes Paging Restriction Information, the MME may accept or reject the Paging Restriction Information requested by the UE based on operator policy. If the MME rejects the Paging Restriction Information, the MME removes any stored Paging Restriction Information from the UE context and discards the UE requested Paging Restriction Information. If the MME accepts the Paging Restriction Information from the UE, the MME stores the Paging Restriction Information from the UE in the UE context. The MME informs the UE about the acceptance/rejection of the requested Paging Restriction Information in the Service Accept message. If no Paging Restriction Information is provided, no paging restrictions apply; - no Downlink or Uplink Data is sent (steps 7-20 are skipped); - the MME triggers the S1 release procedure in step 21. 5b. In the NB-IoT case, the eNodeB, based on configuration, may retrieve the EPS negotiated QoS profile from the MME, if not previously retrieved. The MME Code within the S-TMSI in the RRCConnectionRequest message is used to identify the MME. In the case of network sharing, the MME Codes shall be unique within the area of overlapping MME pools of the participating operators. The eNodeB may apply prioritisation between requests from different UEs before triggering step 6 and throughout the RRC connection. The eNodeB may retrieve additional parameters (e.g., UE Radio Capabilities - see TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36]). 6. If the MME receives no response from the UE after this paging repetition procedure, it shall use the Downlink Data Notification Reject message to notify the Serving GW about the paging failure (or, equivalently, if the buffering is in the MME, the MME simply discards data for the UE locally), unless the MME is aware of an ongoing MM procedure that prevents the UE from responding, i.e. the MME received a Context Request message indicating that the UE performs TAU with another MME. When a Downlink Data Notification Reject message is received, the Serving GW deletes the buffered packet(s). The Serving GW may invoke the procedure PDN GW Pause of Charging (clause 5.3.6A) if UE is in ECM IDLE and the PDN GW has enabled "PDN charging pause" feature. If buffering is in the MME, Pause Charging is triggered by the MME via a Release Access Bearer Request to the S-GW(not shown in Figure 5.3.4B.3-1) including a "Abnormal Release of Radio Link" cause, which releases the S11-U. NOTE 2: The Serving GW (or MME, in the case of buffering in the MME) may initiate the procedure P-GW Pause of Charging at any time before step 5 if the UE is in ECM IDLE and the P-GW has indicated that the feature is enabled for this PDN. See clause 5.3.6A.0. To assist Location Services, the eNodeB indicates the UE's Coverage Level to the MME. The MME performs (and the UE responds to) any EMM or ESM procedures if necessary, e.g. the security related procedures. Steps 7 to 11 can continue in parallel to this, however, steps 12 and 13 shall await completion of all the EMM and ESM procedures. 7. If the S11-U is not established, the MME sends a Modify Bearer Request message (MME address, MME TEID DL, Delay Downlink Packet Notification Request, RAT Type, LTE-M RAT type reporting to PGW flag) for each PDN connection to the Serving GW. The Serving GW is now able to transmit downlink data towards the UE. The usage of the Delay Downlink Packet Notification Request Information Element is specified in clause 5.3.4.2 with reference to the UE initiated service request procedure, but it equally applies in this case. The MME shall indicate S11-U tunnelling of NAS user data and send its own S11-U IP address and MME DL TEID for DL data forwarding by the SGW. Also, regardless of whether the S11-U was already established: - If the P-GW requested UE's location and/or User CSG information and the UE's location and/or User CSG information has changed, the MME shall send the Modify Bearer Request message and also includes the User Location Information IE and/or User CSG Information IE in this message. - If the Serving Network IE has changed compared to the last reported Serving Network IE then the MME shall send the Modify Bearer Request message and also includes the Serving Network IE in this message. - If the UE Time Zone has changed compared to the last reported UE Time Zone then the MME shall send the Modify Bearer Request message and include the UE Time Zone IE in this message. If the RAT type currently used is NB-IOT this shall be reported as different from other -E-UTRA flavours. If the UE is using the LTE-M RAT type and the PDN GW expects the LTE-M RAT type reporting as specified in clause 5.11.5, the MME also includes the LTE-M RAT type reporting to PGW flag to indicate to the Serving GW to forward the LTE-M RAT type to the PDN GW. 8. If the RAT Type has changed compared to the last reported RAT Type or if the UE's Location and/or Info IEs and/or UE Time Zone and Serving Network id are present in step 7, the Serving GW shall send the Modify Bearer Request message (RAT Type) to the P-GW. User Location Information IE and/or User CSG Information IE and/or Serving Network IE and/or UE Time Zone are also included if they are present in step 7. If LTE-M RAT type and the LTE-M RAT type reporting to PGW flag were received at step 7, the Serving GW shall include the LTE-M RAT type in the Modify Bearer Request message to the PGW. Otherwise the Serving GW includes RAT type WB-E-UTRAN. If the Modify Bearer Request message is not sent because of above reasons and the PDN GW charging is paused, then the S-GW shall send a Modify Bearer Request message with PDN Charging Pause Stop Indication to inform the PDN GW that the charging is no longer paused. Other IEs are not included in this message. 9. The PDN GW sends the Modify Bearer Response to the Serving GW. 10. If a Modify Bearer Request message was sent at step 7, the Serving GW shall return a Modify Bearer Response (Serving GW address and TEID for uplink traffic) to the MME as a response to a Modify Bearer Request message. The Serving GW address for S11-U User Plane and Serving GW TEID are used by the MME to forward UL data to the SGW. 11. Buffered (if S11-U was not established) Downlink data is sent by the S-GW to the MME. 12-13. The MME encrypts and integrity protects Downlink data and sends it to the eNodeB using a NAS PDU carried by a Downlink S1-AP message. If the configuration in the MME indicates that the eNodeB supports acknowledgements of downlink NAS data PDUs and if acknowledgements of downlink NAS data PDUs are enabled in the subscription information for the UE, the MME indicates in the Downlink S1-AP message that acknowledgment is requested from the eNodeB. For IP PDN type PDN connections configured to support Header Compression, the MME shall apply header compression before encapsulating data into the NAS message. Alternatively and if the MME decides that S1-U bearers need to be established in the case that the UE and MME accept User Plane EPS Optimisation or S1-U data transfer, steps 4-12 from clause 5.3.4.1 are followed. If the UE is accessing via an NB-IoT cell, or if it is accessing via an WB-E-UTRAN cell and is capable of CE mode B, to determine the NAS PDU retransmission strategy the MME should take into account the transmission delay of the NAS PDU and the CE mode B Restricted parameter stored in the MME's MM context and, if applicable, the CE mode, i.e. set the NAS timers long enough according to the worst transmission delay (see TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [46]). 14. The NAS PDU with data is delivered to the UE via a Downlink RRC message. This is taken by the UE as implicit acknowledgment of the Service Request message sent in step 5. If header compression was applied, to the PDN, the UE shall perform header decompression to rebuild the IP header. 15. The eNodeB sends a NAS Delivery indication to the MME if requested. If the eNodeB reports an unsuccessful delivery with an S1-AP NAS Non Delivery Indication, the MME should wait for some time until the UE has potentially changed cell and re-established contact with the MME, by which MME should resend the Downlink S1-AP message to the eNodeB, otherwise the MME reports an unsuccessful delivery to the SCEF in the case of T6a procedure (see TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [74], clause 5.13.3). If the eNodeB reports a successful delivery with an S1-AP NAS Delivery Indication and if the Downlink data was received over the T6a interface, the MME should respond to the SCEF (see TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [74], clause 5.13.3). If the eNodeB does not support S1-AP NAS delivery indications, the MME indicates a cause code 'Success Unacknowledged Delivery' to the SCEF otherwise 'Success Acknowledged Delivery', for the SCEF to know if reliable delivery was possible or not. 16. While the RRC connection is still up, further Uplink and Downlink data can be transferred using NAS PDUs. In step 17 an Uplink data transfer is shown using an Uplink RRC message encapsulating a NAS PDU with data. At any time the UE has no user plane bearers established, the UE may provide a Release Assistance Information with Uplink data in the NAS PDU. For IP PDN type PDN connections configured to support Header Compression, the UE shall apply header compression before encapsulating it into the NAS message. 17. The NAS PDU with data is send to the MME in a Uplink S1-AP message. To assist Location Services, the eNodeB may indicate, if changed, the UE's Coverage Level to the MME. If the Release Assistance Information is received from the UE it overrides the Traffic Profile (see TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [74]) and the MME does not send the Traffic Profile to the eNodeB. 18. The data is checked for integrity and decrypted. If header compression was applied to the PDN, the MME shall perform header decompression to rebuild the IP header. 19. The MME sends Uplink data to the PDN GW via the S-GW and executes any action related to the presence of Release Assistance Information as follows: - for the case where the Release Assistance Information indicates there is no downlink data to follow the uplink data then unless the MME is aware of pending MT traffic, and unless S1-U bearers exist, the MME immediately releases the connection and therefore step 21 is executed. - for the case where the Release Assistance Information indicates that downlink data will follow the uplink transmission then unless the MME is aware of additional pending MT traffic and unless S1-U bearers exist, the MME sends a S1 UE Context Release Command to the eNodeB immediately after the S1-AP message including the Downlink data encapsulated in NAS PDU. 20. If no NAS activity exists for a while the eNodeB detects inactivity and executes step 21. 21. The eNodeB starts an eNodeB initiated S1 release procedure according to clause 5.3.5 or Connection Suspend Procedure defined in clause 5.3.4A. The UE and the MME shall store the ROHC configuration and context for the uplink/downlink data transmission when entering ECM_CONNECTED state next time.

3GPP TS 23.401

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

SA WG2

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

5.3.4B.3

6 Network Functions 6.1 General

Clause 6 provides the functional description of the Network Functions and network entities and the principles for Network Function and Network Function Service discovery and selection. NG-RAN functions and entities are described in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27] and TS 38.401[ NG-RAN; Architecture description ] [42]. Security functions and entities are described in TS 33.501[ Security architecture and procedures for 5G System ] [29] and TS 33.535[ Authentication and Key Management for Applications (AKMA) based on 3GPP credentials in the 5G System (5GS) ] [124]. 5G Media streaming functions are described in TS 26.501[ 5G Media Streaming (5GMS); General description and architecture ] [135].

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

6

– PDCP-Parameters

The IE PDCP-Parameters is used to convey capabilities related to PDCP. PDCP-Parameters information element -- ASN1START -- TAG-PDCP-PARAMETERS-START PDCP-Parameters ::= SEQUENCE { supportedROHC-Profiles SEQUENCE { profile0x0000 BOOLEAN, profile0x0001 BOOLEAN, profile0x0002 BOOLEAN, profile0x0003 BOOLEAN, profile0x0004 BOOLEAN, profile0x0006 BOOLEAN, profile0x0101 BOOLEAN, profile0x0102 BOOLEAN, profile0x0103 BOOLEAN, profile0x0104 BOOLEAN }, maxNumberROHC-ContextSessions ENUMERATED {cs2, cs4, cs8, cs12, cs16, cs24, cs32, cs48, cs64, cs128, cs256, cs512, cs1024, cs16384, spare2, spare1}, uplinkOnlyROHC-Profiles ENUMERATED {supported} OPTIONAL, continueROHC-Context ENUMERATED {supported} OPTIONAL, outOfOrderDelivery ENUMERATED {supported} OPTIONAL, shortSN ENUMERATED {supported} OPTIONAL, pdcp-DuplicationSRB ENUMERATED {supported} OPTIONAL, pdcp-DuplicationMCG-OrSCG-DRB ENUMERATED {supported} OPTIONAL, ..., [[ drb-IAB-r16 ENUMERATED {supported} OPTIONAL, non-DRB-IAB-r16 ENUMERATED {supported} OPTIONAL, extendedDiscardTimer-r16 ENUMERATED {supported} OPTIONAL, continueEHC-Context-r16 ENUMERATED {supported} OPTIONAL, ehc-r16 ENUMERATED {supported} OPTIONAL, maxNumberEHC-Contexts-r16 ENUMERATED {cs2, cs4, cs8, cs16, cs32, cs64, cs128, cs256, cs512, cs1024, cs2048, cs4096, cs8192, cs16384, cs32768, cs65536} OPTIONAL, jointEHC-ROHC-Config-r16 ENUMERATED {supported} OPTIONAL, pdcp-DuplicationMoreThanTwoRLC-r16 ENUMERATED {supported} OPTIONAL ]], [[ longSN-RedCap-r17 ENUMERATED {supported} OPTIONAL, udc-r17 SEQUENCE { standardDictionary-r17 ENUMERATED {supported} OPTIONAL, operatorDictionary-r17 SEQUENCE { versionOfDictionary-r17 INTEGER (0..15), associatedPLMN-ID-r17 PLMN-Identity } OPTIONAL, continueUDC-r17 ENUMERATED {supported} OPTIONAL, supportOfBufferSize-r17 ENUMERATED {kbyte4, kbyte8} OPTIONAL } OPTIONAL ]], [[ longSN-NCR-r18 ENUMERATED {supported} OPTIONAL ]] } -- TAG-PDCP-PARAMETERS-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

4.4.5 Application Triggering Services

See clause 5.2.6.1 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. Application trigger message contains information that allows the network to route the message to the appropriate UE and the UE to route the message to the appropriate application. The information destined to the application, excluding the information to route it, is referred to as the Trigger payload. The Trigger payload is implementation specific. NOTE: The application in the UE may perform actions indicated by the Trigger payload when the Triggered payload is received at the UE. For example initiation of immediate or later communication with the application server based on the information contained in the Trigger payload, which includes the PDU Session Establishment procedure if the related PDU Session is not already established.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

4.4.5

– CellAccessRelatedInfo-EUTRA-EPC

The IE CellAccessRelatedInfo-EUTRA-EPC indicates cell access related information for an LTE cell connected to EPC. CellAccessRelatedInfo-EUTRA-EPC information element -- ASN1START -- TAG-CELLACCESSRELATEDINFOEUTRA-EPC-START CellAccessRelatedInfo-EUTRA-EPC ::= SEQUENCE { plmn-IdentityList-eutra-epc PLMN-IdentityList-EUTRA-EPC, trackingAreaCode-eutra-epc BIT STRING (SIZE (16)), cellIdentity-eutra-epc BIT STRING (SIZE (28)) } PLMN-IdentityList-EUTRA-EPC::= SEQUENCE (SIZE (1..maxPLMN)) OF PLMN-Identity -- TAG-CELLACCESSRELATEDINFOEUTRA-EPC-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

5.21 Architectural support for virtualized deployments 5.21.0 General

5GC supports different virtualized deployment scenarios, including but not limited to the options below: - A Network Function instance can be deployed as distributed, redundant, stateless, and scalable NF instance that provides the services from several locations and several execution instances in each location. - This type of deployments would typically not require support for addition or removal of NF instances for redundancy and scalability. In the case of an AMF this deployment option may use enablers like, addition of TNLA, removal of TNLA, TNLA release and rebinding of NGAP UE association to a new TNLA to the same AMF. - A Network Function instance can also be deployed such that several network function instances are present within a NF set provide distributed, redundant, stateless and scalability together as a set of NF instances. - This type of deployments may support for addition or removal of NF instances for redundancy and scalability. In the case of an AMF this deployment option may use enablers like, addition of AMFs and TNLAs, removal of AMFs and TNLAs, TNLA release and rebinding of NGAP UE associations to a new TNLA to different AMFs in the same AMF set. - The SEPP, although not a Network Function instance, can also be deployed distributed, redundant, stateless, and scalable. - The SCP, although not a Network Function instance, can also be deployed distributed, redundant, and scalable. Also, deployments taking advantage of only some or any combination of concepts from each of the above options is possible.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.21

5.15.2 Identification and selection of a Network Slice: the S-NSSAI and the NSSAI 5.15.2.1 General

An S-NSSAI identifies a Network Slice. An S-NSSAI is comprised of: - A Slice/Service type (SST), which refers to the expected Network Slice behaviour in terms of features and services; - A Slice Differentiator (SD), which is optional information that complements the Slice/Service type(s) to differentiate amongst multiple Network Slices of the same Slice/Service type. An S-NSSAI can have standard values (i.e. such S-NSSAI is only comprised of an SST with a standardised SST value, see clause 5.15.2.2, and no SD) or non-standard values (i.e. such S-NSSAI is comprised of either both an SST and an SD or only an SST without a standardised SST value and no SD). An S-NSSAI with a non-standard value identifies a single Network Slice within the PLMN with which it is associated. An S-NSSAI with a non-standard value shall not be used by the UE in access stratum procedures in any PLMN other than the one to which the S-NSSAI is associated. The S-NSSAIs in the NSSP of the URSP rules (see clause 6.6.2 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]) and in the Subscribed S-NSSAIs (see clause 5.15.3) contain only HPLMN S-NSSAI values. The S-NSSAIs in the Configured NSSAI, the Allowed NSSAI (see clause 5.15.4.1), the Requested NSSAI (see clause 5.15.5.2.1), the Rejected S-NSSAIs contain only values from the Serving PLMN. The Serving PLMN can be the HPLMN or a VPLMN. The S-NSSAI(s) in the PDU Session Establishment contain one Serving PLMN S-NSSAI value and in addition may contain a corresponding HPLMN S-NSSAI value to which this first value is mapped (see clause 5.15.5.3). Further information for slice replacement is described in clause 5.15.19. The optional mapping of Serving PLMN S-NSSAIs to HPLMN S-NSSAIs contains Serving PLMN S-NSSAI values and corresponding mapped HPLMN S-NSSAI values. The NSSAI is a collection of S-NSSAIs. An NSSAI may be a Configured NSSAI, a Requested NSSAI, Allowed NSSAI or a Partially Allowed NSSAI. There can be at most eight S-NSSAIs in Allowed NSSAI and Requested NSSAI sent in signalling messages between the UE and the Network. There can be at most seven S-NSSAIs in the Partially Allowed NSSAI and at most seven S-NSSAIs rejected partially in the RA, and the sum of S-NSSAIs in the Allowed NSSAI, and the Partially Allowed NSSAI shall be at most eight. The Requested NSSAI signalled by the UE to the network allows the network to select the Serving AMF, Network Slice(s) and Network Slice instance(s) for this UE, as specified in clause 5.15.5. NOTE 1: There can be at most a maximum of seven S-NSSAIs in the Partially Allowed NSSAI since there will always be an Allowed NSSAI allocated. Based on the operator's operational or deployment needs, a Network Slice instance can be associated with one or more S-NSSAIs, and an S-NSSAI can be associated with one or more Network Slice instances. Multiple Network Slice instances associated with the same S-NSSAI may be deployed in the same or in different Tracking Areas. When multiple Network Slice instances associated with the same S-NSSAI are deployed in the same Tracking Areas, the AMF instance serving the UE may logically belong to (i.e. be common to) more than one Network Slice instance associated with this S-NSSAI. In a PLMN, when an S-NSSAI is associated with more than one Network Slice instance, one of these Network Slice instances, as a result of the Network Slice instance selection procedure defined in clause 5.15.5, serves a UE that is allowed to use this S-NSSAI. For any S-NSSAI, the network may at any one time serve the UE with only one Network Slice instance associated with this S-NSSAI until cases occur where e.g. this Network Slice instance is no longer valid in a given Registration Area, or a change in UE's Allowed NSSAI occurs, etc. In such cases, procedures mentioned in clause 5.15.5.2.2 or clause 5.15.5.2.3 apply. Based on the Requested NSSAI (if any) and the Subscription Information, the 5GC is responsible for selection of a Network Slice instance(s) to serve a UE including the 5GC Control Plane and User Plane Network Functions corresponding to this Network Slice instance(s). The Subscription Information may contain restrictions to the simultaneous registration of network slices. This is provided to the serving AMF as part of the UE subscription, in the form of Network Slice Simultaneous Registration Group (NSSRG) information (see clause 5.15.12). The (R)AN may use Requested NSSAI in access stratum signalling to handle the UE Control Plane connection before the 5GC informs the (R)AN of the Allowed NSSAI. The Requested NSSAI is used by the RAN for AMF selection, as described in clause 6.3.5. The UE shall not include the Requested NSSAI in the RRC Resume when the UE asks to resume the RRC connection and is CM-CONNECTED with RRC_INACTIVE state. When a UE is successfully registered over an Access Type, the CN informs the (R)AN by providing the Allowed NSSAI for the corresponding Access Type. NOTE 2: The details of how the RAN uses NSSAI information are described in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27].

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.15.2

9.2.1.2 TDD

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

3GPP TS 36.101

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

RAN4

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

9.2.1.2

17.5.9 Trace Session Deactivation procedure

The Trace Session Deactivation procedure occurs when the GGSN indicates to the BM-SC that a Trace Session, previously activated, needs to be deactivated. Figure 34: Trace Session Deactivation procedure 1. When the GGSN has received a Trace Deactivation message from the SGSN, in a Create MBMS Context Request/Update MBMS Context Request, that requires the deactivation of a Trace Session in the BM-SC, the GGSN sends a STR message (containing the Additional MBMS Trace Info AVP) to deactivate a trace session in the BM-SC and to tear down the corresponding Diameter Session previously established to activate the Trace Session. 2. Upon reception of an STR from a GGSN to deactivate a Trace Session, the BM-SC responds with an STA message.

3GPP TS 29.061

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

CT WG3

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

17.5.9

6.1.1 Authentication framework 6.1.1.1 General

The purpose of the primary authentication and key agreement procedures is to enable mutual authentication between the UE and the network and provide keying material that can be used between the UE and the serving network in subsequent security procedures. The keying material generated by the primary authentication and key agreement procedure results in an anchor key called the KSEAF provided by the AUSF of the home network to the SEAF of the serving network. Keys for more than one security context can be derived from the KSEAF without the need of a new authentication run. A concrete example of this is that an authentication run over a 3GPP access network can also provide keys to establish security between the UE and a N3IWF used in untrusted non-3GPP access. The anchor key KSEAF is derived from an intermediate key called the KAUSF. The KAUSF is established between the UE and HN resulting from the primary authentication procedure. The KAUSF may be securely stored in the AUSF based on the home operator's policy on using such key e.g. if the control plane solution for Steering of Roaming (see clause 6.14) or UE Parameter Update procedures (see clause 6.15) or AKMA are supported by the HPLMN. NOTE A: For standalone non-public networks when an authentication method other than 5G AKA or EAP-AKA' is used, Annex I.2 applies. NOTE 1: This feature is an optimization that might be useful, for example, when a UE registers to different serving networks for 3GPP-defined access and untrusted non-3GPP access (this is possible according to TS 23.501[ System architecture for the 5G System (5GS) ] [2]). The details of this feature are operator-specific and not in scope of this document. NOTE 2: A subsequent authentication based on the KAUSF stored in the AUSF gives somewhat weaker guarantees than an authentication directly involving the ARPF and the USIM. It is rather comparable to fast re-authentication in EAP-AKA'. NOTE 2a: Void. UE and serving network shall support EAP-AKA' and 5G AKA authentication methods. NOTE 2b: It is the home operator's decision which authentication method is selected. The USIM shall reside on a UICC. The UICC may be removable or non-removable. NOTE 3: For non-3GPP access networks USIM applies in case of terminal with 3GPP access capabilities. If the terminal supports 3GPP access capabilities, the credentials used with EAP-AKA' and 5G AKA for non-3GPP access networks shall reside on the UICC. NOTE 4: EAP-AKA' and 5G AKA are the only authentication methods that are supported in UE and serving network, hence only they are described in sub-clause 6.1.3 of the present document. For a private network using the 5G system as specified in [7] an example of how additional authentication methods can be used with the EAP framework is given in the informative Annex B. NOTE 5: For non-public network (NPN) security the Annex I of the present document provides details. Upon successful completion of the 5G AKA primary authentication, the AMF shall initiate NAS security mode command procedure (see clause 6.7.2) with the UE. NOTE 6: The reason to mandatory run the NAS SMC procedure after primary authentication is because the UE does not store the new derived KAUSF until receiving the NAS SMC message. The new partial native NAS security context is taken into use. It is specified in clause 6.9.4.4 whether AS key re-keying is performed.

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

6.1.1

5.10.1 Security visibility

Although in general the security features should be transparent to the user or application, for certain events and according to the user's or application's concern, greater visibility of the operation of following security feature shall be provided: - AS confidentiality: (AS confidentiality, Confidentiality algorithm, bearer information) - AS integrity: (AS integrity, Integrity algorithm, bearer information) - NAS confidentiality: (NAS confidentiality, Confidentiality algorithm) - NAS integrity: (NAS integrity, Integrity algorithm) The UE shall provide above security information to the applications in the UE (e.g. via APIs), on a per PDU session granularity. The serving network identifier shall be available for applications in the UE.

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

5.10.1

28.7.12 NAI used for 5G NSWO

When the UE decides to use 5G NSWO to connect to the WLAN access network using its 5GS credentials but without registration to 5GS, the NAI format for 5G NSWO in non-roaming scenarios is used. See clause 28.7.9.2 for the NAI format for 5G NSWO in roaming scenarios. NOTE: In this case the NAI realm is different than the realm defined for usage during 5G registration via of Trusted non-3GPP access to the 5GCN (see clause 28.7.6) or when N5CW devices access 5GCN via Trusted non-3GPP access to the 5GCN (see clause 28.7.7). See clause 5.42 in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [119]. In the 5G NSWO use case, the UE shall use a NAI in the following format: - For PLMNs: "<username>@5gc-nswo.mnc<MNC>.mcc<MCC>.3gppnetwork.org" - For SNPNs: "<username>@5gc-nswo.nid<NID>.mnc<MNC>.mcc<MCC>.3gppnetwork.org" In the above use cases: a) The entire NAI is constructed by the definition of the username part in clause 28.7.3, along with the realm mentioned in this section. b) the label '5gc-nswo' in the realm part indicates that the NAI is used for 5G NSWO. For PLMNs, <MNC> and <MCC> identify the PLMN, and for SNPNs, <NID>, <MNC> and <MCC> identify the SNPN, to which the UE attempts to connect via the 5G NSWO as described in clause 4.2.15 of 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [119]. For an anonymous SUCI in the 5G NSWO use case, assuming that, a MCC=234, MNC=15 and the Routing Indicator 678, the UE shall use the NAI in the following format: [email protected]<NID>.mnc015.mcc234.3gppnetwork.org (with username corresponding to "anonymous"), or [email protected]<NID>.mnc015.mcc234.3gppnetwork.org (with username corresponding to an empty string)

3GPP TS 23.003

Numbering, addressing and identification

CT WG4

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

28.7.12

5.7.3 Baseband signal generation

The time-continuous random access signal is defined by where, is an amplitude scaling factor in order to conform to the transmit power specified in clause 6.1 in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4], and . The location in the frequency domain is controlled by the parameter is derived from clause 5.7.1. The factor accounts for the difference in subcarrier spacing between the random access preamble and uplink data transmission. The variable, the subcarrier spacing for the random access preamble, and the variable, a fixed offset determining the frequency-domain location of the random access preamble within the physical resource blocks, are both given by Table 5.7.3-1. Table 5.7.3-1: Random access baseband parameters

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

5.3.14.2 Initiation

Upon initiation of the procedure, the UE shall: 1> if timer T390 is running for the Access Category: 2> consider the access attempt as barred; 1> else if timer T302 is running and the Access Category is neither '2' nor '0': 2> consider the access attempt as barred; 1> else: 2> if the Access Category is '0': 3> consider the access attempt as allowed; 2> else: 3> if SIB1 includes uac-BarringPerPLMN-List that contains a UAC-BarringPerPLMN for the selected PLMN or SNPN: 4> if the procedure in 5.2.2.4.2 for a selected PLMN resulted in use of information in npn-IdentityInfoList and UAC-BarringPerPLMN has an entry with the plmn-IdentityIndex corresponding to used information in this list: 5> select the UAC-BarringPerPLMN entry with the plmn-IdentityIndex corresponding to used information in the npn-IdentityInfoList; 4> else: 5> select the UAC-BarringPerPLMN entry with the plmn-IdentityIndex corresponding to the selected PLMN and the PLMN-IdentityInfo, if any, or the selected SNPN and the npn-IdentityInfoList; 3> if any UAC-BarringPerPLMN entry is selected: 4> in the remainder of this procedure, use the selected UAC-BarringPerPLMN entry (i.e. presence or absence of access barring parameters in this entry) irrespective of the uac-BarringForCommon included in SIB1; 3> else if SIB1 includes uac-BarringForCommon: 4> in the remainder of this procedure use the uac-BarringForCommon (i.e. presence or absence of these parameters) included in SIB1; 3> else: 4> consider the access attempt as allowed; 3> if uac-BarringForCommon is applicable or the uac-ACBarringListType indicates that uac-ExplicitACBarringList is used: 4> if the corresponding UAC-BarringPerCatList contains a UAC-BarringPerCat entry corresponding to the Access Category: 5> select the UAC-BarringPerCat entry; 5> if the uac-BarringInfoSetList contains a UAC-BarringInfoSet entry corresponding to the selected uac-barringInfoSetIndex in the UAC-BarringPerCat: 6> select the UAC-BarringInfoSet entry; 6> perform access barring check for the Access Category as specified in 5.3.14.5, using the selected UAC-BarringInfoSet as "UAC barring parameter"; 5> else: 6> consider the access attempt as allowed; 4> else: 5> consider the access attempt as allowed; 3> else if the uac-ACBarringListType indicates that uac-ImplicitACBarringList is used: 4> select the uac-BarringInfoSetIndex corresponding to the Access Category in the uac-ImplicitACBarringList; 4> if the uac-BarringInfoSetList contains the UAC-BarringInfoSet entry corresponding to the selected uac-BarringInfoSetIndex: 5> select the UAC-BarringInfoSet entry; 5> perform access barring check for the Access Category as specified in 5.3.14.5, using the selected UAC-BarringInfoSet as "UAC barring parameter"; 4> else: 5> consider the access attempt as allowed; 3> else: 4> consider the access attempt as allowed; 1> if the access barring check was requested by upper layers: 2> if the access attempt is considered as barred: 3> if timer T302 is running: 4> if timer T390 is running for Access Category '2': 5> inform the upper layer that access barring is applicable for all access categories except categories '0', upon which the procedure ends; 4> else 5> inform the upper layer that access barring is applicable for all access categories except categories '0' and '2', upon which the procedure ends; 3> else: 4> inform upper layers that the access attempt for the Access Category is barred, upon which the procedure ends; 2> else: 3> inform upper layers that the access attempt for the Access Category is allowed, upon which the procedure ends; 1> else: 2> the procedure ends.

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

5.3.14.2

4.3.2.3 Secondary authorization/authentication by an DN-AAA Server during the PDU Session establishment

The PDU Session establishment authentication/authorization is optionally triggered by the SMF during a PDU Session establishment and performed transparently via a UPF or directly with the DN-AAA Server without involving the UPF if the DN-AAA Server is located in the 5GC and reachable directly, as described in clause 5.6.6 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. In the case of Home Routed Roaming, unless specified otherwise, the SMF in the information flow defined in this clause is the H-SMF. Figure 4.3.2.3-1: PDU Session Establishment authentication/authorization by a DN-AAA Server NOTE 1: Steps 2, 3a, 3f and 4 are not defined in this specification. Steps 3 can be repeated depending on the mechanism used. NOTE 2: When the SMF directly communicates with the DN-AAA Server without involving the UPF, Step 1 is skipped and Step 2, 3a, 3f, 4 and 6 are executed without involving the UPF. 0. The SMF determines that it needs to contact the DN-AAA Server. The SMF identifies the DN-AAA Server based on local configuration or using the DN-specific identity (TS 33.501[ Security architecture and procedures for 5G System ] [15]) provided by the UE inside the SM PDU DN Request Container provided by the UE in the PDU Session Establishment request or inside the EAP message in the PDU Session Authentication Complete message (TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [25]). NOTE 3: The content of the SM PDU DN Request Container is defined in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [25]. NOTE 4: When secondary authentication, using Default UE credentials for secondary authentication, is used in the context of the UE onboarding architecture in Figure 5.30.2.10.2.2-3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], the DCS can act as the DN-AAA server. 1. If there is no existing N4 session that can be used to carry DN-related messages between the SMF and the DN, the SMF selects a UPF and triggers N4 session establishment. 2. The SMF initiates the authentication procedure with the DN-AAA via the UPF to authenticate the DN-specific identity provided by the UE as specified in TS 29.561[ 5G System; Interworking between 5G Network and external Data Networks; Stage 3 ] [63]. When available, the SMF provides the GPSI in the signalling exchanged with the DN-AAA. The UPF transparently relays the message received from the SMF to the DN-AAA Server. 3a. The DN-AAA Server sends an Authentication/Authorization message towards the SMF. The message is carried via the UPF. 3b. Transfer of DN Request Container information received from DN-AAA towards the UE. In non-roaming and LBO cases, the SMF invokes the Namf_Communication_N1N2MessageTransfer service operation on the AMF to transfer the DN Request Container information within N1 SM information sent towards the UE. In the case of Home Routed roaming, the H-SMF initiates a Nsmf_PDUSession_Update service operation to request the V-SMF to transfer DN Request Container to the UE and the V-SMF invokes the Namf_Communication_N1N2MessageTransfer service operation on the AMF to transfer the DN Request Container information within N1 SM information sent towards the UE. In Nsmf_PDUSession_Update Request, the H-SMF additionally includes the H-SMF SM Context ID. 3c: The AMF sends the N1 NAS message to the UE 3d-3e. Transfer of DN Request Container information received from UE towards the DN-AAA. When the UE responds with a N1 NAS message containing DN Request Container information, the AMF informs the SMF by invoking the Nsmf_PDUSession_UpdateSMContext service operation. The SMF issues an Nsmf_PDUSession_UpdateSMContext response. In the case of Home Routed roaming, the V-SMF relays the N1 SM information to the H-SMF using the information of PDU Session received in step 3b via a Nsmf_PDUSession_Update service operation. 3f: The SMF (In HR case it is the H-SMF) sends the content of the DN Request Container information (authentication message) to the DN-AAA Server via the UPF. Step 3 may be repeated until the DN-AAA Server confirms the successful authentication/authorization of the PDU Session. 4. The DN-AAA Server confirms the successful authentication/authorization of the PDU Session. The DN-AAA Server may provide: - an SM PDU DN Response Container to the SMF to indicate successful authentication/authorization; - DN Authorization Data as defined in clause 5.6.6 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]; - a request to get notified with the IP address(es) allocated to the PDU Session and/or with N6 traffic routing information or MAC address(es) used by the UE for the PDU Session; and - an IP address (or IPV6 Prefix) for the PDU Session. The N6 traffic routing information is defined in clause 5.6.7 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. After the successful DN authentication/authorization, a session is kept between the SMF and the DN-AAA. If the SMF receives a DN Authorization Data, the SMF uses the DN Authorization Profile Index to apply the policy and charging control (see clause 5.6.6 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]). 5. The PDU Session establishment continues and completes. In the step 7b of the Figure 4.3.2.2.1-1, if the SMF receives the DN Authorization Profile Index in DN Authorization Data from the DN-AAA, it sends the DN Authorization Profile Index to retrieve the PDU Session related policy information (described in clause 6.4 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]) and the PCC rule(s) (described in clause 6.3 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]) from the PCF. If the SMF receives the DN authorized Session AMBR in DN Authorization Data from the DN-AAA, it sends the DN authorized Session AMBR within the Session AMBR to the PCF to retrieve the authorized Session AMBR (described in clause 6.4 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]). For PDU Session of Ethernet type, the SMF may instruct the UPF to handle VLAN information of the Ethernet frames related with the PDU Session received and sent on N6 or N19 or internal interface, as described in clause 5.6.10.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 6. If requested so in step 4 or if configured so by local policies, the SMF notifies the DN-AAA with the IP/MAC address(es) and/or with N6 traffic routing information allocated to the PDU Session together with the GPSI. Later on the SMF notifies the DN-AAA if the DN-AAA had requested to get notifications about: - allocation or release of an IPV6 Prefix for the PDU Session of IP type or addition or removal of source MAC addresses for the PDU Session of Ethernet type (e.g. using IPV6 multi-homing as defined in clause 5.6.4.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]); - Change of N6 traffic routing information. When later on the PDU Session gets released as described in clause 4.3.4, the SMF notifies the DN-AAA. The DN-AAA Server may revoke the authorization for a PDU Session or update DN authorization data for a PDU Session. According to the request from DN-AAA Server, the SMF may release or update the PDU Session. At any time after the PDU Session establishment, the DN-AAA Server or SMF may initiate Secondary Re-authentication procedure for the PDU Session as specified in clause 11.1.3 of TS 33.501[ Security architecture and procedures for 5G System ] [15]. Step 3a to step 3f are performed to transfer the Secondary Re-authentication message between the UE and the DN-AAA Server. The Secondary Re-authentication procedure may start from step 3a (DN-AAA initiated Secondary Re-authentication procedure) or step 3b (SMF initiated Secondary Re-authentication procedure). For the DN-AAA Server initiated Secondary Re-authentication, the message in step 3a shall include GPSI, if available and the IP/MAC address(es) of the PDU session, for SMF to identify the corresponding UE and PDU session. If the Re-authentication result is unsuccessful then SMF may release the PDU session and notify the DN-AAA Server. During Secondary Re-authentication, if the SMF receives an indication from the AMF that the UE is unreachable then it informs the DN-AAA Server that UE is not reachable for re-authentication. Based on this indication from SMF, the DN-AAA Server may decide to keep the PDU Session or request to release the PDU session. DN-AAA may initiate DN-AAA Re-authorization without performing re-authentication based on local policy. DN-AAA Re-authorization procedure may start from step 4. During Secondary Re-authentication/Re-authorization, if the SMF receives DN Authorization Profile Index and/or DN authorized Session AMBR, the SMF reports the received value(s) to the PCF (as described in TS 23.501[ System architecture for the 5G System (5GS) ] [2]) by triggering the Policy Control Request Trigger as described in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20].

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.3.2.3

5.11.1.1 Ciphering algorithm identifier values

All identifiers and names specified in this sub-clause are for 5G NAS and New Radio. In relation to AS capabilities, the identifiers and names for E-UTRAN connected to 5GC are specified in TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [10]. Each encryption algorithm will be assigned a 4-bit identifier. The following values for ciphering algorithms are defined: "00002" NEA0 Null ciphering algorithm; "00012" 128-NEA1 128-bit SNOW 3G based algorithm; "00102" 128-NEA2 128-bit AES based algorithm; and "00112" 128-NEA3 128-bit ZUC based algorithm. 128-NEA1 is based on SNOW 3G (see TS 35.215[ Specification of the 3GPP Confidentiality and Integrity Algorithms UEA2 & UIA2; Document 1: UEA2 and UIA2 specifications ] [14]). 128-NEA2 is based on 128-bit AES [15] in CTR mode [16]. 128-NEA3 is based on 128-bit ZUC (see TS 35.221[ Specification of the 3GPP Confidentiality and Integrity Algorithms EEA3 & EIA3; Document 1: EEA3 and EIA3 specifications ] [18]). Full details of the algorithms are specified in Annex D.

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

5.11.1.1

5.32.5.1a Address of PMF messages

As described in clause 5.32.5.2, 5.32.5.2a and 5.32.5.3, a UE and UPF may exchange PMF messages to measure access performance and report access availability/unavailability. When the UE and UPF exchanges PMF message, source and destination address of the PMF messages shall be assigned as follows: 1. In the case of a MA PDU Session of IP type: - If access performance measurements are performed only over the QoS Flow associated with the default QoS rule, the PMF in the UE sends PMF messages to the PMF in the UPF over UDP/IP. The destination IP address is the IP address contained in the Measurement Assistance Information and the destination UDP port is one of the two UDP ports contained in the Measurement Assistance Information. One UDP port is used for sending PMF messages to UPF over 3GPP access and the other UDP port is used for sending PMF messages to UPF over non-3GPP access. The source IP address is the IP address assigned to UE for the MA PDU Session and the source UDP port is a UDP port that is dynamically allocated by the UE for PMF communication. This source UDP port in the UE remains the same for the entire lifetime of the MA PDU Session. If access performance measurements per QoS Flow is performed, the Measurement Assistance Information contains UDP ports, one for each QoS Flow and access combination. When the UE sends PMF message over a QoS Flow of an access, the UE shall set the destination UDP port as the UDP port for the QoS Flow and the access in Measurement Assistance information. - If access performance measurements are performed only over the QoS Flow associated with the default QoS rule, the PMF in the UPF sends PMF messages to the PMF in the UE over UDP/IP. The source IP address is the same IP address as the one provided in the Measurement Assistance Information and the source UDP port is one of the two UDP ports as provided in the Measurement Assistance Information. One UDP port is used for sending PMF messages to UE over 3GPP access and the other UDP port is used for sending PMF messages to UE over the non-3GPP access. The destination IPv4 address is the IPv4 address assigned to UE for the MA PDU Session (if any) and the destination IPv6 address is an IPv6 address selected by the UE from the IPv6 prefix assigned for the MA PDU Session (if any). The destination UDP port is the dynamically allocated UDP port in the UE, which is contained in all PMF messages received from the UE. If access performance measurements per QoS Flow is performed, when the UPF sends PMF message over a QoS Flow of an access, the UPF shall set the source UDP port with the UDP port for the QoS Flow and the access as the one for the QoS Flow and the access provided in Measurement Assistance information. - If the UE receives Measurement Assistance Information, the UE shall inform the network via the user plane about the UE's dynamically allocated UDP port, and the IPv6 address if IPv6 is used for PMF messages, so that it is possible for the UPF to know the UE's IPv6 address (if applicable) and dynamically allocated UDP port as soon as the MA PDU Session has been established. NOTE 1: Regardless of whether access performance measurements per QoS Flow is applied or not, the UE only allocates a single UDP port for PMF messages. 2. In the case of a MA PDU Session of Ethernet type: - The PMF in the UE sends PMF messages to the PMF in the UPF over Ethernet. The Ethertype is the Ethertype contained in the Measurement Assistance Information. If access performance measurements are performed only over the QoS Flow associated with the default QoS rule, the destination MAC address is one of the two MAC addresses contained in the Measurement Assistance Information. One MAC address is used for sending PMF messages to UPF over 3GPP access and the other MAC address is used for sending PMF messages to UPF over non-3GPP access. The source MAC address is a MAC address of the UE, which remains the same for the entire lifetime of the MA PDU Session. If access performance measurements per QoS Flow is performed, Measurement Assistance Information contains MAC addresses for each QoS Flow and each access. When the UE sends PMF message over a QoS Flow of an access, the UE shall set the destination MAC address as the MAC address for the QoS Flow and the access in Measurement Assistance information. - The PMF in the UPF sends PMF messages to the PMF in the UE over Ethernet. The Ethertype is the same Ethertype as the one provided in the Measurement Assistance Information. If access performance measurements are performed only over the QoS Flow associated with the default QoS rule, the source MAC address is one of the two MAC addresses as provided in the Measurement Assistance Information. One MAC address is used for sending PMF messages to UE over 3GPP access and the other MAC address is used for sending PMF messages to UE over non-3GPP access. The destination MAC address is the MAC address of the UE, which is contained in all PMF messages received from the UE. If access performance measurements per QoS Flow is performed, when the UPF sends PMF message over a QoS Flow of an access, the UPF shall set the source MAC address with the MAC address for the QoS Flow and the access as the one for the QoS Flow and the access provided in Measurement Assistance information. - If the UE receives Measurement Assistance Information, the UE shall inform the network via the user plane about the UE's MAC address so that it is possible for the UPF to know the UE's MAC address as soon as the MA PDU Session has been established. NOTE 2: Regardless of whether access performance measurements per QoS Flow is applied or not, the UE only use a single MAC address.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.32.5.1a

5.2.2 User data and signalling data confidentiality

The UE shall support ciphering of user data between the UE and the gNB. The UE shall activate ciphering of user data based on the indication sent by the gNB. The UE shall support ciphering of RRC and NAS-signalling. The UE shall implement the following ciphering algorithms: NEA0, 128-NEA1, 128-NEA2 as defined in Annex D of the present document. The UE may implement the following ciphering algorithm: 128-NEA3 as defined in Annex D of the present document. The UE shall implement the ciphering algorithms as specified in TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [10] if it supports E-UTRA connected to 5GC. Confidentiality protection of the user data between the UE and the gNB is optional to use. Confidentiality protection of the RRC-signalling, and NAS-signalling is optional to use. Confidentiality protection should be used whenever regulations permit.

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

5.2.2

9.11.2.18 Service-level-AA service status indication

The purpose of the Service-level-AA service status indication information element is to provide an indication of the service availability to the UE. The Service-level-AA service status indication information element is coded as shown in figure 9.11.2.18.1 and table 9.11.2.18.1. The Service-level-AA service status indication information element is a type 4 information element with a length of 3 octets. Figure 9.11.2.18.1: Service-level-AA-service-status indication information element Table 9.11.2.18.1: Service-level-AA-service-status indication information element

3GPP TS 24.501

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

CT WG1

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

9.11.2.18

4.13.2.9 Number of attempted reconfigurations of LWA DRB

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

3GPP TS 32.425

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

SA WG5

3GPP Series : 32 , OAM&P and Charging

4.13.2.9

10.5.4.11 Cause

The purpose of the cause information element is to describe the reason for generating certain messages, to provide diagnostic information in the event of procedural errors and to indicate the location of the cause originator. The cause information element is coded as shown in figure 10.5.95/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and tables 10.5.122 and 10.5.123/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The cause is a type 4 information element with a minimum length of 4 octets and a maximum length of 32 octets. The cause information element may be repeated in a message. Figure 10.5.95/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Cause information element If the default value applies for the recommendation field, octet 3a shall be omitted. Table 10.5.122/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Cause information element Table 10.5.122/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Cause information element (continued) Table 10.5.123/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Cause information element values Table 10.5.123/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] (concluded): Cause information element values All other values in the range 0 to 31 shall be treated as cause 31. All other values in the range 32 to 47 shall be treated as cause 47. All other values in the range 48 to 63 shall be treated as cause 63. All other values in the range 64 to 79 shall be treated as cause 79. All other values in the range 80 to 95 shall be treated as cause 95. All other values in the range 96 to 111 shall be treated as cause 111. All other values in the range 112 to 127 shall be treated as cause 127. NOTE 1: Diagnostics for supplementary services are handled as follows: octet 5, bit 8: This is an extension bit as defined in the preliminary part of subclause 10.5. In this version of this protocol, this bit shall be set to 1. If it is set to zero, the contents of the following octets shall be ignored. octet 5, bit 7-1: 0000001 - Outgoing calls barred within CUG 0000010 - No CUG selected 0000011 - Unknown CUG index 0000100 - CUG index incompatible with requested basic service 0000101 - CUG call failure, unspecified 0000110 - CLIR not subscribed 0000111 - CCBS possible 0001000 - CCBS not possible All other values shall be ignored. NOTE 2: The incompatible parameter is composed of the incompatible information element identifier. NOTE 3: The format of the diagnostic field for cause numbers 57, 58 and 65 is as shown in figure 10.5.88/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and tables 10.5.102/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] to 10.5.115/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . NOTE 4: The user supplied diagnostics field is encoded according to the user specification, subject to the maximum length of the cause information element. The coding of user supplied diagnostics should be made in such a way that it does not conflict with the coding described in note 9 below. NOTE 5: The new destination is formatted as the called party BCD number information element, including information element identifier. NOTE 6: Locking and non-locking shift procedures described in subclause 10.5.4.2 and clause 3 are applied. In principle, information element identifiers are ordered in the same order as the information elements in the received message. NOTE 7: When only the locking shift information element is included and no information element identifier follows, it means that the codeset in the locking shift itself is not implemented. NOTE 8: The timer number is coded in IA5 characters, e.g., T308 is coded as "3" "0" "8". The following coding is used in each octet: bit 8: spare "0" bits 7-1: IA5 character Octet 5 carries "3", octet 5a carries "0", etc. NOTE 9: The following coding is used for octet 5: bit 8 : 1 bits 7-3: 00000 bits 2-1: condition as follows: 00 - unknown 01 - permanent 10 - transient

3GPP TS 24.008

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

CT WG1

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

10.5.4.11

6.8.5 Mapping to resource elements

The mapping to resource elements is defined by operations on quadruplets of complex-valued symbols. Let denote symbol quadruplet for antenna port. The block of quadruplets , where , shall be permuted resulting in . The permutation shall be according to the sub-block interleaver in clause 5.1.4.2.1 of TS 36.212[ Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and channel coding ] [3] with the following exceptions: - the input and output to the interleaver is defined by symbol quadruplets instead of bits - interleaving is performed on symbol quadruplets instead of bits by substituting the terms "bit", "bits" and "bit sequence" in clause 5.1.4.2.1 of TS 36.212[ Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and channel coding ] [3] by "symbol quadruplet", "symbol quadruplets" and "symbol-quadruplet sequence", respectively <NULL> elements at the output of the interleaver in TS 36.212[ Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and channel coding ] [3] shall be removed when forming . Note that the removal of <NULL> elements does not affect any <NIL> elements inserted in clause 6.8.2. The block of quadruplets shall be cyclically shifted, resulting in where. Mapping of the block of quadruplets is defined in terms of resource-element groups, specified in clause 6.2.4, according to steps 1–10 below: 1) Initialize (resource-element group number) 2) Initialize 3) Initialize 4) If the resource element represents a resource-element group and the resource-element group is not assigned to PCFICH or PHICH then perform step 5 and 6, else go to step 7 5) Map symbol-quadruplet to the resource-element group represented by for each antenna port 6) Increase by 1 7) Increase by 1 8) Repeat from step 4 if , where corresponds to the number of OFDM symbols used for PDCCH transmission. The quantity is obtained from - the sequence transmitted on the PCFICH, or - the higher-layer parameter cfi-SubframeMBSFN-r15 for DCI formats other than DCI format 7 in a MBSFN subframe, or - the higher-layer parameter cfi-SlotSubslotMBSFN-r15 for DCI format 7 in a MBSFN subframe, or - the higher-layer parameter cfi-SubframeNonMBSFN-r15 for DCI formats other than DCI format 7 in a non-MBSFN subframe, or - the higher-layer parameter cfi-SlotSubslotNonMBSFN-r15 for DCI format 7 in a non-MBSFN subframe, or - the higher-layer parameter cfi-PatternSubframe-r15 for DCI formats other than DCI format 7 in one subframe for frame structure 2, or - the higher-layer parameter cfi-PatternSlotSubslot-r15 for DCI formats 7 in one subframe for frame structure 2. 9) Increase by 1 10) Repeat from step 3 if PDCCHs shall not be transmitted in MBSFN subframes with zero-size non-MBSFN region.

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

5.3.3.3.3 NAS signalling connection Release

The procedure of releasing a NAS signalling connection is initiated by the AN node (either 5G (R)AN node or N3IWF) or the AMF. The NG-RAN node may include the list of recommended cells/ TAs / NG-RAN node identifiers for paging, during the AN Release Procedure in the AN (see clause 4.2.6 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]). The AMF stores this information, if provided by the NG-RAN. The UE considers the NAS signalling connection is released if it detects the AN signalling connection is released. The AMF considers the NAS signalling connection is released if it detects the N2 context is released.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.3.3.3.3

5.8.9.11.2 Actions related to transmission of the UEInformationRequestSidelink by the UE

For initial information transfer (e.g. for QoS split) or upon change in any of the information in the UEInformationRequestSidelink, the UE shall set the contents of UEInformationRequestSidelink message as follows: 1> if the UE is acting as L2 U2U Remote UE: 2> set sl-E2E-QoS-ConnectionListPC5 to include the end-to-end QoS profile(s) of the sidelink QoS flow(s) of peer L2 U2U Remote UE if configured by the upper layer, and for each entry: 3> set sl-DestinationIdentityRemoteUE to include the associated destination identity for peer L2 U2U Remote UE if configured by the upper layer; 2> submit the UEInformationRequestSidelink 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.8.9.11.2

– RRCResumeRequest

The RRCResumeRequest message is used to request the resumption of a suspended RRC connection or perform an RNA update. Signalling radio bearer: SRB0 RLC-SAP: TM Logical channel: CCCH Direction: UE to Network RRCResumeRequest message -- ASN1START -- TAG-RRCRESUMEREQUEST-START RRCResumeRequest ::= SEQUENCE { rrcResumeRequest RRCResumeRequest-IEs } RRCResumeRequest-IEs ::= SEQUENCE { resumeIdentity ShortI-RNTI-Value, resumeMAC-I BIT STRING (SIZE (16)), resumeCause ResumeCause, spare BIT STRING (SIZE (1)) } -- TAG-RRCRESUMEREQUEST-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

5.5.1.2.7 Abnormal cases on the network side

The following abnormal cases can be identified: a) Lower layer failure If a lower layer failure occurs before the message ATTACH COMPLETE has been received from the UE, the network shall locally abort the attach procedure, enter state EMM-DEREGISTERED and shall not resend the message ATTACH ACCEPT. If a new GUTI was assigned to the UE in the attach procedure, the MME shall consider both the old and the new GUTI as valid until the old GUTI can be considered as invalid by the network or the EMM context which has been marked as detached in the network is released. If the old GUTI was allocated by an MME other than the current MME, the current MME does not need to retain the old GUTI. If the old GUTI is used by the UE in a subsequent attach message, the network may use the identification procedure to request the UE's IMSI. b) Protocol error If the ATTACH REQUEST message is received with a protocol error, the network shall return an ATTACH REJECT message with one of the following EMM cause values: #96: invalid mandatory information; #99: information element non-existent or not implemented; #100: conditional IE error; or #111: protocol error, unspecified. c) T3450 time-out On the first expiry of the timer, the network shall retransmit the ATTACH ACCEPT message and shall reset and restart timer T3450. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3450, the attach procedure shall be aborted and the MME enters state EMM-DEREGISTERED. If a new GUTI was allocated in the ATTACH ACCEPT message, the network shall consider both the old and the new GUTI as valid until the old GUTI can be considered as invalid by the network or the EMM context which has been marked as detached in the network is released. If the old GUTI was allocated by an MME other than the current MME, the current MME does not need to retain the old GUTI. If the old GUTI is used by the UE in a subsequent attach message, the network acts as specified for case a above. d) ATTACH REQUEST received after the ATTACH ACCEPT message has been sent and before the ATTACH COMPLETE message is received - If one or more of the information elements in the ATTACH REQUEST message differ from the ones received within the previous ATTACH REQUEST message, the previously initiated attach procedure shall be aborted if the ATTACH COMPLETE message has not been received and the new attach procedure shall be progressed; or - if the information elements do not differ, then the ATTACH ACCEPT message shall be resent and the timer T3450 shall be restarted if an ATTACH COMPLETE message is expected. In that case, the retransmission counter related to T3450 is not incremented. e) More than one ATTACH REQUEST received and no ATTACH ACCEPT or ATTACH REJECT message has been sent - If one or more of the information elements in the ATTACH REQUEST message differs from the ones received within the previous ATTACH REQUEST message, the previously initiated attach procedure shall be aborted and the new attach procedure shall be executed; - if the information elements do not differ, then the network shall continue with the previous attach procedure and shall ignore the second ATTACH REQUEST message. f) ATTACH REQUEST received in state EMM-REGISTERED If an ATTACH REQUEST message is received in state EMM-REGISTERED the network may initiate the EMM common procedures; if it turned out that the ATTACH REQUEST message was sent by a genuine UE that has already been attached, the EMM context, EPS bearer contexts, if any, are deleted and the new ATTACH REQUEST is progressed, otherwise if network considers ATTACH REQUEST message was not sent by a genuine UE based on authentication procedure the network shall maintain the EMM-context, if any, unchanged. NOTE 1: The network can determine that the UE is genuine by executing the authentication procedure as described in clause 5.4.2. g) TRACKING AREA UPDATE REQUEST message received before ATTACH COMPLETE message. Timer T3450 shall be stopped. The allocated GUTI in the attach procedure shall be considered as valid and the tracking area updating procedure shall be rejected with the EMM cause #10 "implicitly detached" as described in clause 5.5.3.2.5. h) DETACH REQUEST message received before ATTACH COMPLETE message. The network shall abort the attach procedure and shall progress the detach procedure as described in clause 5.5.2.2. i) If EMM-REGISTERED without PDN connection is supported by the UE and the MME, the MME receives an ATTACH REQUEST message with an ESM message included in the ESM message container information element, and the ESM sublayer in the MME detects a message error according to clause 7, the MME may decide to proceed with the attach procedure or to reject it. When sending the ATTACH ACCEPT or ATTACH REJECT message to the UE, the MME shall include the ESM message provide by the ESM layer in the ESM message container information element. j) UE security capabilities invalid or unacceptable If the ATTACH REQUEST message is received with invalid or unacceptable UE security capabilities (e.g. no EPS encryption algorithms (all bits zero), no EPS integrity algorithms (all bits zero), mandatory EPS encryption algorithms not supported or mandatory EPS integrity algorithms not supported, etc.), the MME shall return an ATTACH REJECT message. NOTE 2: EMM cause value to be used in ATTACH REJECT message is up to the network implementation.

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

4.25.9 NEF Anchored Group NIDD via NEF anchored unicast MT data

Figure 4.25.9-1 illustrates the procedure by which the AF can send a Group NIDD addressed to External Group Identifier. It is a pre-requisite assumption that the NEF has already resolved the mapping of External Group Identifier to individual SUPIs with the help of UDM during NIDD Configuration procedure as specified in clause 4.25.3. Standalone MT NIDD procedure specified in clause 4.25.5 is re-used by NEF to unicast the MT data to each UE. Figure 4.25.9-1: NEF Anchored Group NIDD via NEF anchored unicast data 1. If AF has already used the NIDD Configuration procedure of clause 4.25.3 to activate the NIDD service for a group of UEs and has unstructured data to send to the group identified by an External Group Identifier, the AF sends a Nnef_NIDD_Delivery Request (External Group Identifier, TLTRI, unstructured data, Reliable Data Service Configuration) message to the NEF. Reliable Data Service Configuration is an optional parameter that is used to configure the Reliable Data Service. When unstructured data is sent to an External Group Identifier, the AF shall not request acknowledgement in the Reliable Data Service Configuration. 2. Based on the existing NIDD configuration of the UE Group (see clause 4.25.3), the NEF sends a single Nnef_NIDD_Delivery Response to AF to acknowledge the acceptance of the Group NIDD delivery request in step 1. 3. The NEF uses the NEF anchored Mobile Terminated Data Transport procedure that is specified in steps 2-16 in clause 4.25.5 to send the same MT NIDD to each UE in the group. 4. After executing step 3 for all UEs in the group, the NEF sends aggregated response in Nnef_NIDD_GroupDeliveryNotify message. If some target UEs were not reachable due to UE power saving, then the NEF does not buffer the MT NIDD, but it may include indication on the expected reachability of those UEs in its response to AF in this step. If the delivery towards certain UE failed, the NEF may include the cause value.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.25.9

– SL-CBR-PriorityTxConfigList

The IE SL-CBR-PriorityTxConfigList indicates the mapping between PSSCH transmission parameter (such as MCS, PRB number, retransmission number, CR limit) sets by using the indexes of the configurations provided in sl-CBR-PSSCH-TxConfigList, CBR ranges by an index to the entry of the CBR range configuration in sl-CBR-RangeConfigList, and priority ranges. It also indicates the default PSSCH transmission parameters to be used when CBR measurement results are not available, and MCS range for the MCS tables used in the resource pool. SL-CBR-PriorityTxConfigList information element -- ASN1START -- TAG-SL-CBR-PRIORITYTXCONFIGLIST-START SL-CBR-PriorityTxConfigList-r16 ::= SEQUENCE (SIZE (1..8)) OF SL-PriorityTxConfigIndex-r16 SL-CBR-PriorityTxConfigList-v1650 ::= SEQUENCE (SIZE (1..8)) OF SL-PriorityTxConfigIndex-v1650 SL-PriorityTxConfigIndex-r16 ::= SEQUENCE { sl-PriorityThreshold-r16 INTEGER (1..8) OPTIONAL, -- Need M sl-DefaultTxConfigIndex-r16 INTEGER (0..maxCBR-Level-1-r16) OPTIONAL, -- Need M sl-CBR-ConfigIndex-r16 INTEGER (0..maxCBR-Config-1-r16) OPTIONAL, -- Need M sl-Tx-ConfigIndexList-r16 SEQUENCE (SIZE (1.. maxCBR-Level-r16)) OF SL-TxConfigIndex-r16 OPTIONAL -- Need M } SL-PriorityTxConfigIndex-v1650 ::= SEQUENCE { sl-MCS-RangeList-r16 SEQUENCE (SIZE (1..maxCBR-Level-r16)) OF SL-MinMaxMCS-List-r16 OPTIONAL -- Need M } SL-TxConfigIndex-r16 ::= INTEGER (0..maxTxConfig-1-r16) -- TAG-SL-CBR-PRIORITYTXCONFIGLIST-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

5.7.3c.3 Failure type determination

The L2 U2N Remote UE configured with SL indirect path shall set the indirect path failure type as follows: 1> if the UE initiates transmission of the IndirectPathFailureInformation message due to T421 expiry in accordance with clause 5.3.5.16.1.3: 2> set the failureTypeIndirectPath as t421-Expiry; 1> else if the UE initiates transmission of the IndirectPathFailureInformation message due to reception of the NotificationMessageSidelink including indicationType, in accordance with clause 5.8.9.10.4: 2> set the failureTypeIndirectPath as the value in indicationType received from NotificationMessageSidelink; 1> else if the UE initiates transmission of the IndirectPathFailureInformation message due to sidelink radio link failure in accordance with clause 5.8.9.3: 2> set the failureTypeIndirectPath as sl-Failure; 1> if the target L2 U2N Relay UE (i.e., the UE indicated by sl-IndirectPathRelayUE-Identity in the received sl-IndirectPathAddChange) changes its serving PCell to a different cell from the target cell (i.e. the cell indicated by sl-IndirectPathCellIdentity in the received sl-IndirectPathAddChange) before path addition or change: 2> set the failureTypeIndirectPath as indirectPathAddChangeFailure; The N3C remote UE shall set the indirect path failure type as follows: 1> if the UE initiates transmission of the IndirectPathFailureInformation message due to N3C connection failure: 2> set the failureTypeIndirectPath as n3c-Failure; 1> else if the UE initiates transmission of the IndirectPathFailureInformation message due to Uu radio link failure on N3C indirect path: 2> set the failureTypeIndirectPath as relayUE-Uu-RLF; NOTE: it is out of 3GPP scope how the remote UE detects N3C connection failure, or how the relay UE indicates Uu RLF to the remote UE on the N3C connection.

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

5.7.3c.3

5.5.2.2.4 UTRAN Iu mode to E-UTRAN Inter RAT handover reject

The Target eNodeB may reject the use of the Handover procedure if none of the requested EPS bearers in the Handover Request message could be established. In this case no UE context is established in the target MME/eNodeB and no resources are allocated. The UE remains in the Source RNC/SGSN. Figure 5.5.2.2.4-1: UTRAN Iu mode to E-UTRAN Inter RAT HO reject 1. Steps 1 to 5 in the flow are identical to the ones in clause 5.5.2.2.2. 6. If the Target eNodeB fails to allocate any resources for any of the requested EPS Bearers it sends a Handover Failure (Cause) message to the Target MME. When the Target MME receives the Handover Failure message from Target eNodeB the Target MME clears any reserved resources for this UE. 7. This step is only performed for Serving GW relocation, i.e. if Steps 4/4a have been performed. The Target MME deletes the EPS bearer resources by sending Delete Session Request (Cause) messages to the Target Serving GW. The Target Serving GW acknowledges with Delete Session Response (Cause) messages. 8. The Target MME sends the Forward Relocation Response (Cause) message to the Source SGSN. 9. When the Source SGSN receives the Forward Relocation Response message it send a Relocation Preparation Failure (Cause) message to the Source RNC.

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

4.15.4.2 Exposure of Mobility Events from AMF

The AMF invokes the Namf_EventExposure_Notify to provide mobility related events to NF consumers that have subscribed for the events by invoking Namf_EventExposure_Subscribe, in the following scenarios listed below and after Namf_EventExposure_Subscribe service operation. - During Registration procedure, Inter NG-RAN node N2 based handover procedure, when there is a change of AMF (within the same AMF Set or across the AMF Set), the new AMF receives all event subscriptions from old AMF or UDSF. For each event subscription: if the event subscription only applies to the UE, the new AMF allocates a new Subscription Correlation ID and notify the NF consumer of the new Subscription Correlation ID associated with the change of Subscription Correlation ID event. if the event subscription applies to a group of UE(s) and there is no corresponding subscription for this group (identified by the internal group Id and notification endpoint) at the new AMF, the new AMF shall create corresponding event subscription, allocate a new Subscription Correlation Id and send it to the received notification endpoint, i.e. Notification Target Address (+Notification Correlation Id), associated with the addition of Subscription Correlation ID event. The new AMF does not need to allocate another Subscription Correlation ID for any subsequent registrations of the members of the same group. The initial Maximum number of reports and the remaining number of reports within the Maximum number of reports quota for the UE is transferred from the old AMF. NOTE: For group monitoring, even if the remaining number of reports is zero, indicating that reporting for the group event has been completed by the old AMF for this UE, the new AMF uses the received information related to initial event subscription to create the corresponding group event subscription. - During Registration procedure, when there is a change of AMF, the new AMF notifies each NF that has subscribed for UE reachability event about the UE reachability status. - During Registration, Handover, UE Triggered Service Request procedure in CM-IDLE state, Location Reporting, N2 Notification and AN Release procedures, the AMF determines the UE presence in Area Of Interest (i.e. IN, OUT or UNKNOWN status ) as described in Annex D.1 and notifies the NF Consumers of the UE presence in an Area Of Interest if the NF consumers (e.g. SMF) had subscribed for this Area Of Interest and if the UE presence in Area Of Interest is different from the one reported earlier. - During Registration and Handover procedure or during Service Area Restriction update by UDM or PCF, if the UE is moving from an Allowed Area to a Non-Allowed Area, then the AMF informs all the NF consumers (e.g. SMF), that have subscribed for UE reachability event, that the UE is reachable only for regulatory prioritized service. The SMF shall explicitly subscribe UE reachability unless the established PDU Session is related to regulatory prioritized service. - If the AMF had notified an SMF of the UE being reachable only for regulatory prioritized service earlier, the AMF informs the NF consumers (e.g. SMF), that have subscribed for UE reachability event, that the UE is reachable if the UE enters into Allowed Area. - During Registration procedure and Service Request procedure, if the AMF had notified an SMF earlier of the UE being unreachable and that SMF need not invoke Namf_Communication_N1N2MessageTransfer to the AMF due to DL data notifications, the AMF informs the SMF when the UE becomes reachable. - During Registration procedure and Service Request procedure, if the AMF had notified an SMF earlier that the UE is unreachable together with an Estimated Maximum Wait time, then the AMF informs the SMF when the UE becomes reachable. When the SMF learns that the UE is reachable and: - if the SMF performs Extended Buffering for a PDU session, the SMF sends the buffered data to the UPF and invokes the Namf_Communication_N1N2MessageTransfer service operation to the AMF to establish the User Plane(s) for the PDU Sessions, or the buffered data is delivered to the UE as per the procedure in clause 4.24.2 starting from step 2g for a PDU session using Control Plane CIoT 5GS Optimisation; - if the UPF performs Extended Buffering for a PDU session, the SMF invokes the Namf_Communication_N1N2MessageTransfer service operation to the AMF to establish the User Plane(s) for the PDU Sessions, or the buffered data is delivered to the UE as per the procedure in clause 4.24.2 starting from step 8a for a PDU session using Control Plane CIoT 5GS Optimisation. - If NEF had subscribed for UE reachability event notification for Extend Buffering, then the AMF informs the NEF when the UE becomes reachable. When the NEF learns that the UE is reachable, it invokes the Nsmf_NIDD_Delivery service operation of the corresponding SMF to deliver the buffered data to the UE as per the procedure in clause 4.25.5 starting from step 2 for a PDU session using Control Plane CIoT 5GS Optimisation. - During Registration procedure, Handover without Registration procedure and Service Request procedure, if the NF consumers had subscribed for UE reachability status, the AMF notifies the UE reachability status changes. - If the Mobile Reachable Timer expires the AMF notifies the NF consumers that have subscribed for the corresponding events that the UE is not reachable. - If the UDM had subscribed for UE reachability event notification either to be reported to the UDM or to an NF consumer directly, then the AMF notifies the UE reachability event to the UDM or to the NF consumer as specified in clause 4.2.5.2. - If UE's TAC is already known by the AMF, then, the AMF notifies UE TAC to the NF consumers (e.g. to NWDAF). If UE TAC is unknown, then the AMF notifies the UE TAC when it obtained the UE TAC from the UE. During Connection, Registration and Mobility Management procedures, the AMF may store and update the UE access behaviour trends specified in Table 4.15.4.2-1 and the UE location trends specified in Table 4.15.4.2-2. Each metrics is updated incrementally, e.g. using exponential moving average. This information is exposed to consumer NFs (e.g. NWDAF) that subscribe for the event ID "UE access behaviour trends" and/or "UE location trends", respectively, by invoking Namf_EventExposure_Subscribe. Table 4.15.4.2-1: UE access behaviour trends exposed by AMF Table 4.15.4.2-2: UE location trends

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.15.4.2

Resume Acknowledge

The Resume Acknowledge message should be sent on the S11 interface by the SGW to the MME and on the S5/S8 by the PGW to the SGW as part of the resume procedure returning back to E-UTRAN in the case of CS fallback or SRVCC. The Resume Acknowledge message should also be sent on the S4 interface by the SGW to the SGSN and on the S5/S8 interface by the PGW to the SGW as part of the resume procedure returning from SRVCC to HSPA if there is no Modify Bearer Request message sent to the SGW and PGW as specified in 3GPP TS 23.216[ Single Radio Voice Call Continuity (SRVCC); Stage 2 ] [43]. The PGW shall also send a Resume Acknowledge message to the SGW on the S5/S8 interface as a response to a Resume Notification message sent by the SGW upon receipt from the MME/S4-SGSN of a (non-empty) Modify Bearer Request used as an implicit resume of the suspended bearers in the SGW and in the PGW (see 3GPP TS 23.216[ Single Radio Voice Call Continuity (SRVCC); Stage 2 ] [43] clauses 6.2.2.1 and 6.3.2.1, 3GPP TS 23.272[ Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2 ] [21] clauses 6.3, 6.5 and 7.4) if the conditions of presence of the IEs in the Modify Bearer Request specified in table 7.2.7-1 do not require any IE to be sent to the PGW. Possible Cause values are specified in Table 8.4-1. Table 7.4.4-1 specifies the presence requirements and conditions of the IEs in the message. Table -1: Information Element in Resume Acknowledge

3GPP TS 29.274

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

CT WG4

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

Resume

– UE-BasedPerfMeas-Parameters

The IE UE-BasedPerfMeas-Parameters contains UE-based performance measurement parameters. UE-BasedPerfMeas-Parameters information element -- ASN1START -- TAG-UE-BASEDPERFMEAS-PARAMETERS-START UE-BasedPerfMeas-Parameters-r16 ::= SEQUENCE { barometerMeasReport-r16 ENUMERATED {supported} OPTIONAL, immMeasBT-r16 ENUMERATED {supported} OPTIONAL, immMeasWLAN-r16 ENUMERATED {supported} OPTIONAL, loggedMeasBT-r16 ENUMERATED {supported} OPTIONAL, loggedMeasurements-r16 ENUMERATED {supported} OPTIONAL, loggedMeasWLAN-r16 ENUMERATED {supported} OPTIONAL, orientationMeasReport-r16 ENUMERATED {supported} OPTIONAL, speedMeasReport-r16 ENUMERATED {supported} OPTIONAL, gnss-Location-r16 ENUMERATED {supported} OPTIONAL, ulPDCP-Delay-r16 ENUMERATED {supported} OPTIONAL, ..., [[ sigBasedLogMDT-OverrideProtect-r17 ENUMERATED {supported} OPTIONAL, multipleCEF-Report-r17 ENUMERATED {supported} OPTIONAL, excessPacketDelay-r17 ENUMERATED {supported} OPTIONAL, earlyMeasLog-r17 ENUMERATED {supported} OPTIONAL ]], [[ loggedMDT-PNI-NPN-r18 ENUMERATED {supported} OPTIONAL, loggedMDT-SNPN-r18 ENUMERATED {supported} OPTIONAL ]] } -- TAG-UE-BASEDPERFMEAS-PARAMETERS-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

8.148 PSCell ID

PSCell ID shall be encoded as depicted in Figure 8.148-1. PSCell ID contains an NR Cell Identity. Figure 8.148-1: PSCell ID The "MNC digit 3" field shall be coded as "1111" if the MNC contains only two digits. The NR CGI field shall consist of 36 bits. The NR CGI field shall start with Bit 4 of octet 8, which is the most significant bit. Bit 1 of Octet 12 is the least significant bit. The coding of the NR CGI is the responsibility of each administration. Coding using full hexadecimal representation (binary, not ASCII encoding) shall be used.

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

5.7.2.4 Notification control 5.7.2.4.1 General

The QoS Parameter Notification control indicates whether notifications are requested from the NG-RAN when the "GFBR can no longer (or can again) be guaranteed" for a QoS Flow during the lifetime of the QoS Flow. Notification control may be used for a GBR QoS Flow if the application traffic is able to adapt to the change in the QoS (e.g. if the AF is capable to trigger rate adaptation). The SMF shall only enable Notification control when the QoS Notification Control parameter is set in the PCC rule (received from the PCF) that is bound to the QoS Flow. The Notification control parameter is signalled to the NG-RAN as part of the QoS profile.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.7.2.4

5.10.2 UE requested PDN connectivity

The UE requested PDN connectivity procedure for an E-UTRAN is depicted in figure 5.10.2-1. The procedure allows the UE to request for connectivity to an additional PDN over E-UTRAN including allocation of a default bearer, if the UE already has active PDN connections over E-UTRAN. This procedure may also be used when a UE has set "Attach without PDN Connectivity is supported" in the Preferred Network behaviour at attach time and the network has acknowledged its support to the UE. If so, the UE may remain attached without a Default PDN connection and, at any time, request a PDN connection to be established. This procedure is also used to request for connectivity to an additional PDN over E-UTRAN, if the UE is simultaneously connected to E-UTRAN and a non-3GPP access and the UE already has active PDN connections over both accesses. The PDN connectivity procedure may trigger one or multiple Dedicated Bearer Establishment procedures to establish dedicated EPS bearer(s) for that UE. An emergency attached or RLOS attached UE shall not initiate any PDN Connectivity Request procedure. A normal attached UE shall request a PDN connection for emergency services when Emergency Service is required and an emergency PDN connection is not already active. The UE supporting 15 EPS bearers as defined in clause 4.12 shall not initiate a UE requested PDN connectivity procedure if it has already 8 EPS bearers established and the UE has not received an Indication for support of 15 EPS bearers per UE or has received cause #65 "maximum number of EPS bearers reached". Figure 5.10.2-1: UE requested PDN connectivity NOTE 1: For a PMIP-based S5/S8, procedure steps (A) are defined in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [2]. Steps 3, 4, 5 and 13a/b concern GTP based S5/S8. NOTE 2: The UE also uses this procedure to request re-establishment of existing PDN connectivity upon handover from non-3GPP accesses. NOTE 3: The steps in (B) are executed only upon handover from non-3GPP access or if Presence Reporting Area Information is received from the MME. NOTE 4: When using the Control Plane CIoT EPS Optimisation, steps 7 and 8 are modified and 9 and 10 are skipped. 1. The UE initiates the UE Requested PDN procedure by the transmission of a PDN Connectivity Request (APN, PDN Type, Protocol Configuration Options, Request Type, Header Compression Configuration) message. If the UE was in ECM-IDLE mode, this NAS message is preceded by the Service Request procedure if any of the exiting PDN connections were using the User Plane without CIoT EPS Optimisation, or, if the user plane was used just with User Plane CIoT EPS Optimisations, a Connection Resume Procedure is executed instead. PDN type indicates the requested IP version (IPv4, IPv4v6, IPv6, Non-IP, Ethernet). The MME verifies that the APN provided by UE is allowed by subscription. If the APN provided by the UE is not allowed by subscription, based on operator policy, the MME may reject the request from the UE with an appropriate cause, or accept the request by replacing the UE requested APN with a network supported APN. The MME uses that network supported APN for the remainder of this procedure, except that the MME provides to the UE the same APN that the UE requested. If the UE did not provide an APN, the MME shall use the APN from the default PDN subscription context, and, use this APN for the remainder of this procedure. Protocol Configuration Options (PCO) are used to transfer parameters between the UE and the Network and are sent transparently through the MME and the Serving GW. The Protocol Configuration Options may include the Address Allocation Preference, which indicates that the UE prefers to obtain an IPv4 address only after the default bearer activation by means of DHCPv4. If the UE has UTRAN or GERAN capabilities, it shall send the NRSU in the PCO to indicate the support of the network requested bearer control in UTRAN/GERAN. The UE sends the ETFTU in the PCO to indicate the support of the extended TFT filter format. The Request Type indicates "initial request" if the UE requests new additional PDN connectivity over the 3GPP access network for multiple PDN connections, the Request Type indicates "handover" when the UE is performing a handover from non-3GPP access and the UE has already established connectivity with the PDN over the non-3GPP access. The UE shall indicate Request Type "Emergency" when it requests a PDN connection for emergency services. If the message is being sent via a HeNB which has a collocated L-GW, it includes the L-GW address in the Uplink NAS transport message to the MME. If a UE indicated Control Plane CIoT EPS Optimisation supported in Preferred Network Behaviour and supports header compression, it shall include the Header Compression Configuration, unless "Non-IP" or "Ethernet" PDN type is indicated. The Header Compression Configuration includes the information necessary for the ROHC channel setup. Optionally, the Header Compression Configuration may also include additional header compression context setup parameters, if the UE already has the application traffic information, e.g. the target server IP address. The UE shall include in the PCO the 3GPP PS Data Off UE Status, which indicates whether the user has activated or deactivated 3GPP PS Data Off. In the case of satellite access for Cellular IoT, the MME may verify the UE location as described in clause 4.13.4. 2. If the MME receives a PDN Connectivity Request from an emergency attached or RLOS attached UE or the PDN Connectivity Request is for normal services and the mobility or access restrictions do not allow the UE to access normal services the MME shall reject this request. If the Request Type indicates "Emergency" and the MME is not configured to support PDN connections for emergency services the MME shall reject the PDN Connectivity Request with an appropriate reject cause. If the Request Type is not set to "Emergency", and the UE has indicated support for Attach without PDN Connectivity, and the network supports Attach without PDN Connectivity, and the PDN Connection Restriction is set in the subscriber data, then the MME should reject the PDN Connectivity Request with an appropriate cause value. If the Request Type indicates "Emergency", the MME derives a PDN GW from the MME Emergency Configuration Data or the MME selects a PDN GW as described in clause 4.3.12.4 on PDN GW Selection Function (3GPP accesses) according to the Emergency APN in the MME Emergency Configuration Data. This selection shall provide a PDN GW from visited PLMN only. If the Request Type indicates "Emergency" and the MME is configured to support PDN connections for emergency services, it uses the MME Emergency Configuration Data for the bearer establishment in this step and ignores any subscription data limitation. If the Request Type indicates "Handover", the MME uses the PDN GW stored in the Subscription Data retrieved by the MME during the Update Location performed at attach. If the Request Type indicates "initial request" the MME selects a PDN GW as described in clause 4.3.8.1 on PDN GW Selection Function (3GPP accesses). If the UE provided APN is authorized for LIPA according to the user subscription, the MME shall use the CSG Subscription Data to authorize the connection. If the subscription context does not indicate that the APN is for a PDN connection to an SCEF the MME allocates a Bearer Id, and sends a Create Session Request (IMSI, MSISDN, MME TEID for control plane, RAT type, LTE-M RAT type reporting to PGW flag, PDN GW address, PDN Address, Default EPS Bearer QoS, PDN Type, subscribed APN-AMBR, APN, EPS Bearer Id, Protocol Configuration Options, Handover Indication, ME Identity, User Location Information (ECGI and TAI), UE Time Zone, User CSG Information, MS Info Change Reporting support indication, Selection Mode, Charging Characteristics, Trace Reference, Trace Type, Trigger Id, OMC Identity, Maximum APN Restriction, Dual Address Bearer Flag) message to the Serving GW. If Control Plane CIoT EPS Optimisation applies, then the MME shall also indicate S11-U tunnelling of NAS user data and send its own S11-U IP address and MME DL TEID for DL data forwarding by the SGW. If the MME determines the PDN connection shall only use the Control Plane CIoT EPS Optimisation, the MME shall include a Control Plane Only PDN Connection Indicator in Create Session Request. For PDN type "non-IP", if the APN subscription data indicate a SCEF connection needs to be used, then the MME allocates an EPS Bearer Identity for the Default Bearer associated with the UE and established connection to the SCEF address indicated in subscription data according to TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [74] and the steps 2,3,4,5,6 are not executed. The rest of the interactions with the UE apply as specified below. The RAT type is provided in this message for the later PCC decision. The RAT type shall enable NB-IoT, LTE-M and WB-E-UTRAN to be differentiated by the PDN-GW The MSISDN is included if the MME has it stored for that UE. Handover Indication is included if the Request Type indicates "handover". Selection Mode indicates whether a subscribed APN was selected, or a non-subscribed APN sent by the UE was selected. The P-GW may use Selection Mode when deciding whether to accept or reject the default bearer activation. For example, if an APN requires subscription, the P-GW is configured to accept only the default bearer activation that requests a subscribed APN as indicated by Selection Mode. Charging Characteristics indicates which kind of charging the bearer context is liable for. The charging characteristics for the PS subscription and individually subscribed APNs as well as the way of handling Charging Characteristics and whether to send them or not to the P-GW is defined in TS 32.251[ Telecommunication management;Charging management;Packet Switched (PS) domain charging ] [44]. The MME shall include Trace Reference, Trace Type, Trigger Id, and OMC Identity if S-GW and/or P-GW trace is activated. The MME shall copy Trace Reference, Trace Type, and OMC Identity from the trace information received from the HLR or OMC. The Maximum APN Restriction denotes the most stringent restriction as required by any already active bearer context. If there are no already active bearer contexts, this value is set to the least restrictive type (see clause 15.4 of TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7]). If the P-GW receives the Maximum APN Restriction, then the P-GW shall check if the Maximum APN Restriction value does not conflict with the APN Restriction value associated with this bearer context request. If there is no conflict the request shall be allowed, otherwise the request shall be rejected with sending an appropriate error cause to the UE. If the PDN subscription context contains a subscribed IPv4 address and/or IPv6 prefix, the MME indicates it in the PDN address. The MME may change the requested PDN type according to the subscription data for this APN as described in clause 5.3.1.1. The MME shall set the Dual Address Bearer Flag when the PDN type is set to IPv4v6 and all SGSNs which the UE may be handed over to are Release 8 or above supporting dual addressing, which is determined based on node pre-configuration by the operator. If there is an APN Rate Control Status in the MME MM Context for the UE, the MME forwards it to the SGW. Based on UE and Serving GW capability of supporting MT-EDT, Communication Pattern parameters or local policy, the MME may indicate to Serving GW that MT-EDT is applicable for the PDN Connection. 3. The Serving GW creates a new entry in its EPS Bearer table and sends a Create Session Request (IMSI, MSISDN, Serving GW Address for the user plane, Serving GW TEID of the user plane, Serving GW TEID of the control plane, RAT type, Default EPS Bearer QoS, PDN Type, PDN Address, subscribed APN-AMBR, APN, Bearer Id, Protocol Configuration Options, Handover Indication, ME Identity, User Location Information (ECGI), UE Time Zone, User CSG Information, MS Info Change Reporting support indication, PDN Charging Pause Support indication, Selection Mode, Charging Characteristics, Trace Reference, Trace Type, Trigger Id, OMC Identity, Maximum APN Restriction, Dual Address Bearer Flag, APN Rate Control Status) message to the PDN GW indicated in the PDN GW address received in the previous step. After this step, the Serving GW buffers any downlink packets it may receive from the PDN GW until receives the message in step 13 below. The MSISDN is included if received from the MME. If the Handover Indication is included, the Serving GW includes it in the Create Session Request message. If the Serving GW has received the Control Plane Only PDN Connection Indicator in step 2, the Serving GW informs the PDN GW this information in Create Session Request. The Serving GW and PDN GW shall indicate the use of CP only on their CDRs. P-GWs shall not perform any checks of Maximum APN Restriction if Create Default Bearer Request includes emergency APN. If the PDN GW detects that the 3GPP PS Data Off UE Status has changed, the PDN GW shall indicate this event to the charging system for offline and online charging. 4. If dynamic PCC is deployed and the Handover Indication is not present, the PDN GW may employ an IP-CAN Session Establishment procedure as defined in TS 23.203[ Policy and charging control architecture ] [6] with the PCRF to get the default PCC rules for the UE. This may lead to the establishment of a number of dedicated bearers following the procedures defined in clause 5.4.1 in association with the establishment of the default bearer which is described in Annex F. The RAT type is provided to the PCRF by the PDN GW if received by the previous message. If the PDN GW/PCEF is configured to activate predefined PCC rules for the default bearer, the interaction with the PCRF is not required (e.g. operator may configure to do this) at the moment. The ETFTU is provided to the PCRF by the PDN GW, if received in the PCO from the UE and the PDN GW supports the extended TFT filter format. If the PCRF decides that the PDN connection may use extended TFT filters, it shall return the ETFTN indicator to the PDN GW for inclusion in the protocol Configuration Options returned to the UE. The PCRF may modify the APN-AMBR and the QoS parameters (QCI and ARP) associated with the default bearer in the response to the PDN GW as defined in TS 23.203[ Policy and charging control architecture ] [6]. If the PCC is configured to support emergency services and dynamic PCC is deployed, the PCRF, based on the Emergency APN, sets the ARP of the PCC rules to a value that is reserved for emergency services and the authorization of dynamic PCC rules as described in TS 23.203[ Policy and charging control architecture ] [6]. If dynamic PCC is not deployed, the PDN GW is configured to set the ARP to a value that is reserved for emergency services. If dynamic PCC is deployed and the Handover Indication is present, the PDN GW executes a PCEF-Initiated IP-CAN Session Modification procedure with the PCRF as specified in TS 23.203[ Policy and charging control architecture ] [6] to report the new IP-CAN type. Depending on the active PCC rules, the establishment of dedicated bearer for the UE may be required. The establishment of those bearers shall take place in combination with the default bearer activation as described in Annex F. This procedure can continue without waiting for a PCRF response. If changes to the active PCC rules are required, the PCRF may provide them after the handover procedure is finished. In both cases (Handover Indication is present or not), if dynamic PCC is not deployed, the PDN GW may apply local QoS policy. This may lead to the establishment of a number of dedicated bearers for the UE following the procedures defined in clause 5.4.1 in combination with the establishment of the default bearer, which is described in Annex F. If the CSG information reporting triggers are received from the PCRF, the PDN GW should set the CSG Information Reporting Action IE accordingly. If 3GPP PS Data Off status is received in the PCO from the UE and PDN GW supports 3GPP PS Data Off, the PDN GW shall provide the 3GPP PS Data Off status to the PCRF. If the PCRF supports 3GPP PS Data Off, it shall return 3GPP PS Data Off support to the PDN GW for inclusion in the PCO returned to the UE. If the 3GPP PS Data Off UE Status indicates that 3GPP PS Data Off is activated for the UE, the PDN GW shall enforce the PCC rules for downlink traffic to be used when 3GPP PS Data Off is activated. If received, the PDN GW may take the APN Rate Control Status into account when encoding the APN Rate Control parameters in Protocol Configuration Options and when enforcing the APN Rate Control as described in clause 4.7.7.3. 5. The P-GW creates a new entry in its EPS bearer context table and generates a Charging Id for the Default Bearer. The new entry allows the P-GW to route user plane PDUs between the S-GW and the packet data network, and to start charging. The way the P-GW handles Charging Characteristics that it may have received is defined in TS 32.251[ Telecommunication management;Charging management;Packet Switched (PS) domain charging ] [44]. The PDN GW returns a Create Session Response (PDN GW Address for the user plane, PDN GW TEID of the user plane, PDN GW TEID of the control plane, PDN Type, PDN Address, EPS Bearer Id, EPS Bearer QoS, Protocol Configuration Options, Charging Id, Prohibit Payload Compression, APN Restriction, Cause, MS Info Change Reporting Action (Start) (if the PDN GW decides to receive UE's location information during the session), CSG Information Reporting Action (Start) (if the PDN GW decides to receive UE's User CSG information during the session), Presence Reporting Area Action (if the PDN GW decides to receive notifications about a change of UE presence in Presence Reporting Area), PDN Charging Pause Enabled indication (if PDN GW has chosen to enable the function), APN-AMBR, Delay Tolerant Connection) message to the Serving GW. The PDN GW takes into account the received PDN type, the Dual Address Bearer Flag and the policies of operator when the PDN GW selects the PDN type to be used as follows. If the received PDN type is IPv4v6 and both IPv4 and IPv6 addressing are possible in the PDN but the Dual Address Bearer Flag is not set, or only single IP version addressing for this APN is possible in the PDN, the PDN GW selects a single IP version (either IPv4 or IPv6). If the received PDN type is IPv4 or IPv6, the PDN GW uses the PDN type if it is supported in the PDN, otherwise an appropriate error cause will be returned. The PDN GW allocates a PDN Address according to the selected PDN Type If the PDN GW has selected a PDN type different from the received PDN Type, the PDN GW indicates together with the PDN type IE a reason cause to the UE why the PDN type has been modified, as described in clause 5.3.1.1. PDN Address may contain an IPv4 address for IPv4 and/or an IPv6 prefix and an Interface Identifier. If the PDN has been configured by the operator so that the PDN addresses for the requested APN shall be allocated by usage of DHCPv4 only, or if the PDN GW allows the UE to use DHCPv4 for address allocation according to the Address Allocation Preference received from the UE, the PDN Address shall be set to 0.0.0.0, indicating that the IPv4 address shall be negotiated by the UE with after completion of the Default Bearer Activation procedure. For external PDN addressing for IPv6, the PDN GW obtains the IPv6 prefix from the external PDN using either RADIUS or Diameter client function. In the PDN Address field of the Create Session Response, the PDN GW includes the Interface Identifier and IPv6 prefix. The PDN GW sends Router Advertisement to the UE after default bearer establishment with the IPv6 prefix information for all cases. If the PDN address is contained in the Create Session Request, the PDN GW shall allocate the IPv4 address and/or IP6 prefix contained in the PDN address to the UE. If Handover Indication indicates "Handover", the PDN Address Information shall contain the same IP address the UE obtained during PDN connectivity establishment over the non-3GPP access. The PDN GW derives the BCM based on the NRSU and operator policy. The PDN GW derives whether the extended TFT filter format is to be used based on the ETFTU, ETFTN received from the PCRF and operator policy. Protocol Configuration Options contains the BCM, ETFTN as well as optional PDN parameters that the P-GW may transfer to the UE. These optional PDN parameters may be requested by the UE, or may be sent unsolicited by the P-GW. Protocol Configuration Options are sent transparently through the MME. If the PDN type is Non-IP or Ethernet, the PDN-GW uses the APN and IMSI to determine what local actions to perform before answering the Serving GW. The PDN GW includes a Delay Tolerant Connection indication if the PDN GW supports receiving a rejection cause from the SGW indicating that the UE is temporarily not reachable due to power saving, and holding mobile terminated procedures until the PDN GW receives a message indicating that the UE is available for end to end signalling. When the Handover Indication is present, the PDN GW does not yet send downlink packets to the S-GW; the downlink path is to be switched at step 13a. If the PDN GW is an L-GW, it does not forward downlink packets to the S-GW. The packets will only be forwarded to the HeNB at step 10 via the direct user plane path for Local IP Access. If the 3GPP PS Data Off UE Status was present in the Create Session Request PCO, and if the network supports 3GPP PS Data Off, the PDN GW shall include the 3GPP PS Data Off Support Indication in the Create Session Response PCO. 6. The Serving GW returns a Create Session Response (PDN Type, PDN Address, Serving GW address for User Plane, Serving GW TEID for User Plane, Serving GW TEID for control plane, EPS Bearer Id, EPS Bearer QoS, PDN GW address and TEID (GTP-based S5/S8) or GRE key (PMIP-based S5/S8) at the PDN GW for uplink traffic, Protocol Configuration Options, Prohibit Payload Compression, APN Restriction, Cause, MS Info Change Reporting Action (Start), CSG Information Reporting Action (Start), Presence Reporting Area Action, APN-AMBR, DTC) message to the MME. The DL TFT for PMIP-based S5/S8 is obtained from interaction between the Serving GW and the PCRF as described in clause 5.6.1 of TS 23.402[ Architecture enhancements for non-3GPP accesses ] [2], when PCC is deployed; otherwise, the DL TFT IE is wildcarded, matching any downlink traffic. If the UE indicates the Request Type as "Handover", this message also serves as an indication to the MME that the S5/S8 bearer setup and update has been successful. At this step the GTP tunnel(s) over S5/S8 are established If Control Plane CIoT EPS Optimisation applies, and if MME doesn't include Control Plane Only PDN Connection Indicator in the Create Session Request: - If separation of S11-U from S1-U is required, the Serving GW shall include the Serving GW IP address and TEID for S11-U and additionally the Serving GW IP address and TEID for S1-U in the Create Session Response. - Otherwise if separation of S11-U from S1-U is not required, the Serving GW includes the Serving GW IP address and TEID for S11-U in Create Session Response. 7. If an APN Restriction is received, then the MME shall store this value for the Bearer Context and the MME shall check this received value with the stored value for the Maximum APN Restriction to ensure there are no conflicts between values. If the consequence of this check results in the PDN connectivity being rejected, the MME shall initiate a Bearer Deactivation and return an appropriate error cause. If the PDN Connectivity Request is accepted, the MME shall determine a (new) value for the Maximum APN Restriction. If there is no previously stored value for Maximum APN Restriction, then the Maximum APN Restriction shall be set to the value of the received APN Restriction. The P-GW shall ignore Maximum APN restriction if the request includes the Emergency APN. For emergency service MME shall not deactivate bearer(s), if present, to maintain valid APN restriction combination. If the MS Info Change Reporting Action (Start) and/or the CSG Information Reporting Action (Start) are received for this bearer context, then the MME shall store this for the bearer context and the MME shall report to that P-GW via the S-GW whenever a UE's Location Information and/or User CSG Information change occurs that meets the P-GW request, as described in clause 15.1.1a of TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7]. If Presence Reporting Area Action is received for this bearer context, the MME shall store this information for the bearer context and shall report to that P-GW via the S-GW whenever a change of UE presence in a Presence Reporting Area is detected, as described in clause 5.9.2.2. The MME may need to modify the UE AMBR, which has been assigned to the eNodeB, based on the subscribed UE-AMBR and the updated set of APN-AMBRs in use. The principles to determine the UE-AMBR are described in clause 4.7.3. The MME sends PDN Connectivity Accept Session Management Request (APN, PDN Type, PDN Address, EPS Bearer Id, Protocol Configuration Options, Header Compression Configuration, Control Plane Only Indicator) message to the UE. If the PDN connection uses the user plane over the radio, this message is contained in an S1_MME control message Bearer Setup Request (EPS Bearer QoS, UE-AMBR, PDN Connectivity Accept, S1-TEID) to the eNodeB. However, if Control Plane CIoT EPS Optimisation applies to the PDN connection, an S1-AP Downlink NAS transport message is used. The S1-AP Initial Context Setup Request message includes the TEID at the Serving GW used for user plane and the address of the Serving GW for user plane. If the PDN type is set to "Non-IP" the MME includes it in the S1-AP Initial Context Setup Request so that the eNodeB disables header compression. If the PDN type is set to "Ethernet" the MME includes it in the S1-AP Initial Context Setup Request so that any eNodeB header compression functionality can act appropriately. In addition, if the PDN connection is established for Local IP Access, the corresponding S1 Initial Context Setup Request message includes a Correlation ID for enabling the direct user plane path between the HeNB and the L-GW. If the PDN connection is established for SIPTO at the Local Network with L-GW function collocated with the (H)eNB, the corresponding S1-AP Initial Context Setup Request includes a SIPTO Correlation ID for enabling the direct user plane path between the (H)eNB and the L-GW. LIPA and SIPTO do not apply to Control Plane CIoT EPS Optimisation. NOTE 5: In this release of the 3GPP specification the Correlation ID and SIPTO Correlation ID is set equal to the user plane PDN GW TEID (GTP-based S5) or GRE key (PMIP-based S5) that the MME has received in step 6. In the PDN Connectivity Accept message, the MME does not include the IPv6 prefix within the PDN Address. The MME includes the APN-AMBR and the EPS Bearer QoS parameter QCI into the Session Management Request. Furthermore, if the UE has UTRAN or GERAN capabilities and the network supports mobility to UTRAN or GERAN, the MME uses the EPS bearer QoS parameters to derive the corresponding PDP context parameters QoS Negotiated (R99 QoS profile), Radio Priority, Packet Flow Id and TI and includes them in the Session Management Request. If the UE indicated in the UE Network Capability that it does not support BSS packet flow procedures, then the MME shall not include the Packet Flow Id. MME will not send the S1 Bearer Setup Request message until any outstanding S1 Bearer Setup Response message for the same UE has been received or timed out. If the APN-AMBR has changed the MME may update the UE-AMBR if appropriate. The MME may include an indication whether the traffic of this PDN Connection is allowed to be offloaded to WLAN, as described in clause 4.3.23. If the UE has indicated PDN type "Non-IP" or "Ethernet", the MME and PDN GW shall not change PDN type. If the MME or PDN GW has changed the PDN Type, an appropriate reason cause shall be returned to the UE as described in clause 5.3.1.1. If Control Plane CIoT EPS Optimisation applies for an IP PDN connection, and the UE has sent in the PDN Connectivity Request the Header Compression Configuration, the MME shall include the Header Compression Configuration in the PDN Connectivity Accept message. The MME also binds the uplink and downlink ROHC channels to support header compression feedback signalling. If the UE has included ROHC context setup parameters in Header Compression Configuration in the PDN Connectivity Request, the MME may acknowledge ROHC context setup parameters. If the ROHC context is not established during the PDN connection establishment procedure, before using the compressed format for sending the data, the UE and the MME need to establish the ROHC context with ROHC IR packet based on Header Compression Configuration. If the MME based on local policy determines the PDN connection shall only use the Control Plane CIoT EPS Optimisation, the MME shall include a Control Plane Only Indicator in the Session Management Request. For PDN connections with an SCEF, the MME shall always include the Control Plane Only Indicator. If there is an existing SGi PDN connection for this UE for which the MME included a Control Plane Only Indicator, the MME shall include it also for the additional SGi PDN connection. If the MME did not include a Control Plane Only Indicator for any of the existing SGi PDN connections of this UE, the MME shall not include it for the additional SGi PDN connection. A UE receiving the Control Plane Only Indicator, for a PDN connection shall only use the Control Plane CIoT EPS Optimisation for this PDN connection. NOTE 6: The MME decision whether to include a Control Plane Only Indicator to an SGi PDN connection for a UE that previously had no SGi connections will impact other potential subsequent SGi PDN connections for that UE. 8. If the eNodeB received an S1-AP Initial Context Setup Request, the eNodeB sends RRC Connection Reconfiguration to the UE including the PDN Connectivity Accept message. If the eNodeB received an S1-AP Downlink NAS Transport message containing the NAS PDN Connectivity Accept message, the eNode B sends a RRC Direct Transfer message to the UE and the steps 9 and 10 are not executed. The UE shall store the QoS Negotiated, Radio Priority, Packet Flow Id and TI, which it received in the Session Management Request IE, for use when accessing via GERAN or UTRAN. The UE may provide EPS Bearer QoS parameters to the application handling the traffic flow. The application usage of the EPS Bearer QoS is implementation dependent. The UE shall not reject the RRC Connection Reconfiguration on the basis of the EPS Bearer QoS parameters contained in the Session Management Request. If the UE receives an IPv4 address set to 0.0.0.0, it may negotiate the IPv4 address with DHCPv4 as specified in TS 29.061[ Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) ] [38], If the UE receives an IPv6 interface identifier, it may wait for the Router Advertisement from the network with the IPv6 prefix information or it may send a Router Solicitation if necessary. NOTE 7: The IP address allocation details are described in clause 5.3.1 on "IP Address Allocation". 9. The UE sends the RRC Connection Reconfiguration Complete to the eNodeB. 10. The eNodeB send an S1-AP Bearer Setup Response to the MME. The S1-AP message includes the TEID of the eNodeB and the address of the eNodeB used for downlink traffic on the S1_U reference point. If the Correlation ID or SIPTO Correlation ID is included in the Bearer Setup Request, the eNodeB shall use the included information to establish a direct user plane path to the L-GW and forward uplink data for Local IP Access or SIPTO at the Local Network with L-GW function collocated with the (H)eNB accordingly. 11. The UE NAS layer builds a PDN Connectivity Complete message including EPS Bearer Identity. The UE then sends a Direct Transfer (PDN Connectivity Complete) message to the eNodeB. 12. The eNodeB sends an Uplink NAS Transport (PDN Connectivity Complete) message to the MME. After the PDN Connectivity Accept message and once the UE (if applicable to the PDN type) has obtained a PDN Address Information, the UE can then send uplink packets towards the eNodeB which may then be tunnelled by the MME to the Serving GW and PDN GW, or transferred by the MME to an SCEF (see TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [74]), as per subscription information related to APN discussed above in step 2. If the UE requested for a dual address PDN type (IPv4v6) to a given APN and was granted a single address PDN type (IPv4 or IPv6) by the network with a reason cause indicating that only single IP version per PDN connection is allowed, the UE should request for the activation of a parallel PDN connection to the same APN with a single address PDN type (IPv4 or IPv6) other than the one already activated. If the UE receives no reason cause in step 8 in response to a IPv4v6 PDN type and it receives an IPv6 Interface Identifier apart from the IPv4 address or 0.0.0.0 in the PDN Address field, it considers that the request for a dual address PDN was successful. It can wait for the Router Advertisement from the network with the IPv6 prefix information or it may send Router Solicitation if necessary. 13. Upon reception of the Bearer Setup Response message in step 10 and the PDN Connectivity Complete message in step 12, the MME sends a Modify Bearer Request (EPS Bearer Identity, eNodeB address, eNodeB TEID, Handover Indication, Presence Reporting Area Information) message to the Serving GW. If the Control Plane CIoT EPS Optimisation applies and the PDN connection is not served via a SCEF type of connectivity, steps 13 and 14 are executed only if the MME needs to report a change of UE presence in Presence Reporting Area, otherwise, if the PDN connection is served by SCEF, steps 13,14, 15, and 16 are not executed. If Request Type indicates "handover", the Handover Indication is also included. If the MME has been requested to report a change of UE presence in Presence Reporting Area, the MME includes in this message the Presence Reporting Area Information comprising the PRA identifier(s) and indication(s) on whether the UE is inside or outside the area(s). When receiving the request for reporting change of UE presence in Presence Reporting Area, and the MME decides not to activate reporting UE presence in one or more of the received Presence Reporting Area(s), the MME reports also the inactive Presence Reporting Area(s) in this message. 13a. If the Handover Indication is included in step 13, the Serving GW sends a Modify Bearer Request (Handover Indication) message to the PDN GW to prompt the PDN GW to tunnel packets from non 3GPP IP access to 3GPP access system and immediately start routing packets to the Serving GW for the default and any dedicated EPS bearers established. If Presence Reporting Area Information is included in step 13, the Serving GW sends a Modify Bearer Request (Presence Reporting Area Information) message to the PDN GW. NOTE 8: The PDN GW forwards 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]. 13b. The PDN GW acknowledges by sending Modify Bearer Response to the Serving GW. 14. The Serving GW acknowledges by sending Modify Bearer Response (EPS Bearer Identity) to the MME. The Serving GW can then send its buffered downlink packets. 15. After the MME receives Modify Bearer Response in step 14, if Request type does not indicate handover and an EPS bearer was established and if the subscription data indicates that the user is allowed to perform handover to non-3GPP accesses and if this is the first PDN connection associated with this APN and if the MME selected a PDN GW that is different from the PDN GW identity which was previously indicated by the HSS in the PDN subscription context, the MME shall send a Notify Request including the PDN GW address and the APN to the HSS for mobility with non-3GPP accesses. The message shall include information that identifies the PLMN in which the PDN GW is located. For an unauthenticated or roaming UE, if the Request Type of the UE requested connectivity procedure indicates "Emergency", the MME shall not send any Notify Request to the HSS. For a non-roaming authenticated UE, based on operator configuration (e.g. on whether Voice over WLAN is supported or not by the operator), if the Request Type indicates "Emergency", the MME may send a Notify Request to the HSS including the "PDN GW currently in use for emergency services", which comprises the PDN GW address and an indication that the PDN connection is for emergency services. The HSS shall store it as part of the UE context for emergency services. 16. In the case of non-emergency services, the HSS stores the PDN GW identity and the associated APN. In the case of emergency services, the HSS stores the "PDN GW currently in use for emergency services". Then the HSS sends a Notify Response to the MME. NOTE 9: For handover from non-3GPP access, the PDN GW initiates resource allocation deactivation procedure in the trusted/untrusted non-3GPP IP access as specified in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [2].

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

5.5.1.1.3 X2-based handover with Serving GW relocation

This procedure is used to hand over a UE from a source eNodeB to a target eNodeB using X2 when the MME is unchanged and the MME decides that the Serving GW is to be relocated. The presence of IP connectivity between the source Serving GW and the source eNodeB, between the source Serving GW and the target eNodeB, and between the target Serving GW and target eNodeB is assumed. (If there is no IP connectivity between target eNodeB and source Serving GW, it is assumed that the S1-based handover procedure in clause 5.5.1.2 shall be used instead.) Figure 5.5.1.1.3-1: X2-based handover with Serving GW relocation NOTE 1: For a PMIP-based S5/S8, procedure steps (A) and (B) are defined in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [2]. 1a. If the PLMN has configured Secondary RAT usage data reporting and the source eNodeB has Secondary RAT usage data to report, the eNodeB sends a RAN usage data Report (Secondary RAT usage data, handover flag) message to the MME. The eNodeB shall provide this only when it is to perform a Path Switch (i.e. the Target eNodeB has confirmed it is ready over X2 interface (see TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5] and the source eNodeB has sent a HO command to the UE). The handover flag indicates to the MME that it should buffer the report before forwarding the Secondary RAT usage charging data. 1b. The target eNodeB sends a Path Switch Request message to MME to inform that the UE has changed cell, including the ECGI of the target cell and the list of EPS bearers to be switched. If Dual Connectivity is activated for the UE, the PSCell ID shall be included in the Path Switch Request message. If the target cell is a CSG cell, the target eNodeB includes the CSG ID of the target cell in Path Switch Request message. If the target cell is in hybrid mode, it includes the CSG ID of the target cell and CSG Access Mode set to "hybrid" in the Path Switch Request message. Moreover, the Path Switch Request message contains the CSG Membership Status IE if the hybrid cell accessed by the UE has a different CSG from the source cell or the source cell does not have a CSG ID. The MME determines the CSG membership based on the CSG ID and the target PLMN id received from the target eNodeB. The MME updates the User CSG information based on the CSG ID and CSG Access Mode received from the target eNodeB and CSG membership if one of the parameters has changed. For SIPTO at the Local Network with stand-alone GW architecture, the target eNodeB shall include the Local Home Network ID of the target cell in the Path Switch Request message. The MME determines that the Serving GW is relocated and selects a new Serving GW according to clause 4.3.8.2 on "Serving GW Selection Function". NOTE 2: The MME knows the S-GW Service Area with a TA granularity. 2. The MME sends a Create Session Request (bearer context(s) with PDN GW addresses and TEIDs (for GTP-based S5/S8) or GRE keys (for PMIP-based S5/S8) at the PDN GW(s) for uplink traffic, eNodeB address(es) and TEIDs for downlink user plane for the accepted EPS bearers, the Protocol Type over S5/S8, Serving Network, UE Time Zone, Secondary RAT usage data, User Location Information, PSCell ID) message per PDN connection to the target Serving GW for each PDN connection where the default bearer has been accepted by the target eNodeB. The target Serving GW allocates the S-GW addresses and TEIDs for the uplink traffic on S1_U reference point (one TEID per bearer). The Protocol Type over S5/S8 is provided to Serving GW which protocol should be used over S5/S8 interface. If the PDN GW requested location information change reporting, the MME also includes the User Location Information IE in this message if it is different compared to the previously sent information. If the PDN GW requested UE's User CSG information (determined from the UE context), the MME includes the User CSG Information IE in this message if the User CSG Information has changed. The MME uses the list of EPS bearers to be switched, received in step 1, to determine whether any dedicated EPS bearers in the UE context have not been accepted by the target eNodeB. The MME releases the non-accepted dedicated bearers by triggering the bearer release procedure as specified in clause 5.4.4.2 via target Serving GW. If the Serving GW receives a DL packet for a non-accepted bearer, the Serving GW drops the DL packet and does not send a Downlink Data Notification to the MME. If the default bearer of a PDN connection has not been accepted by the target eNodeB and there are multiple PDN connections active, the MME shall consider all bearers of that PDN connection as failed and release that PDN connection by triggering the MME requested PDN disconnection procedure specified in clause 5.10.3 via source Serving GW. If none of the default EPS bearers have been accepted by the target eNodeB or there is a LIPA PDN connection that has not been released, the MME shall act as specified in step 5. If the MME received it from the source eNodeB in step 1a and PDN GW Secondary RAT reporting is active, the MME includes the Secondary RAT usage data with a flag stating that the target SGW shall not process the information and only forward it to the PDN GW. If MME received PSCell ID in step 1b, the MME shall include it in Create Session Request. 3. The target Serving GW assigns addresses and TEIDs (one per bearer) for downlink traffic from the PDN GW. The Serving GW allocates DL TEIDs on S5/S8 even for non-accepted bearers. It sends a Modify Bearer Request (Serving GW addresses for user plane and TEID(s), Serving Network, PDN Charging Pause Support Indication, Secondary RAT usage data) message per PDN connection to the PDN GW(s). The S-GW also includes User Location Information IE and/or UE Time Zone IE and/or User CSG Information IE if it is present in step 2. The PDN GW updates its context field and returns a Modify Bearer Response (Charging Id, MSISDN, PDN Charging Pause Enabled Indication (if PDN GW has chosen to enable the function), etc.) message to the Serving GW. The MSISDN is included if the PDN GW has it stored in its UE context. The PDN GW starts sending downlink packets to the target GW using the newly received address and TEIDs. These downlink packets will use the new downlink path via the target Serving GW to the target eNodeB. The Serving GW shall allocate TEIDs for the failed bearers and inform to the MME. The Serving GW forwards the Secondary RAT usage data to the PDN GW, if the Serving GW received it in step 2 and if PGW secondary RAT usage data reporting is active. If the Serving GW is relocated, the PDN GW shall send one or more "end marker" packets on the old path immediately after switching the path in order to assist the reordering function in the target eNodeB. The source Serving GW shall forward the "end marker" packets to the source eNodeB. 4. The target Serving GW sends a Create Session Response (Serving GW addresses and uplink TEID(s) for user plane) message back to the target MME. The MME starts a timer, to be used in step 7. 5. The MME confirms the Path Switch Request message with the Path Switch Request Ack (Serving GW addresses and uplink TEID(s) for user plane) message. If the UE-AMBR is changed, e.g. all the EPS bearers which are associated to the same APN are rejected in the target eNodeB, the MME shall provide the updated value of UE-AMBR to the target eNodeB in the Path Switch Request Ack message. The target eNodeB starts using the new Serving GW address(es) and TEID(s) for forwarding subsequent uplink packets. If the CSG membership status was included in the Path Switch Request message, the MME shall include its verified CSG membership status in the Path Switch Request Ack message. If some EPS bearers have not been switched successfully in the core network, the MME shall indicate in the Path Switch Request Ack message which bearers failed to be established (see more detail in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36]) and for dedicated bearers initiate the bearer release procedure as specified in clause 5.4.4.2 to release the core network resources of the failed dedicated EPS bearers. The target eNodeB shall delete the corresponding bearer contexts when it is informed that bearers have not been established in the core network. If none of the default EPS bearers have been switched successfully in the core network or if they have not been accepted by the target eNodeB or the LIPA PDN connection has not been released, the MME shall send a Path Switch Request Failure message (see more detail in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36]) to the target eNodeB. The MME performs explicit detach of the UE as described in the MME initiated detach procedure of clause 5.3.8.3. If the MME supports RACS as defined in clause 5.11.3a and has UE Radio Capability ID stored in the UE's context it includes it in the Path Switch Request Ack message. 6. By sending Release Resource the target eNodeB informs success of the handover to source eNodeB and triggers the release of resources. This step is specified in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]. 7. When the timer has expired after step 4, the source MME releases the bearer(s) in the source Serving GW by sending a Delete Session Request message (Cause, Operation Indication, Secondary RAT usage data, User Location Information, PSCell ID). The operation Indication flag is not set, that indicates to the Source Serving GW that the Source Serving GW shall not initiate a delete procedure towards the PDN GW. If PSCell ID was received in step 1a, the MME includes it in Delete Session Request message. The Source Serving GW acknowledges with Delete Session Response messages. If ISR has been activated before this procedure, the cause indicates to the Source S-GW that the Source S-GW shall delete the bearer resources on the other old CN node by sending Delete Bearer Request message(s) to that CN node. The MME includes the Secondary RAT usage data in this message if it received it in step 1a. 8. The UE initiates a Tracking Area Update procedure when one of the conditions listed in clause "Triggers for tracking area update" applies. NOTE 3: It is only a subset of the TA update procedure that is performed by the MME, since the UE is in ECM-CONNECTED state. The UE is informed about the ISR status in the Tracking Area Update procedure.

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

.4 Failed RRC connection establishment per failure cause

a) This measurement provides the number of failed RRC establishment per failure cause. This measurement is to support LBO target setting and evaluation, see [15] b) CC c) Transmission of an RRCConnectionReject message by the eNodeB to the UE. Each transmitted RRCConnectionReject message caused by “congestion” is added to the measurement cause ‘Congestion’, when eNB receives an RRCConnectionRequest message and the RRC connection is not established because the eNB is going to Energy Saving mode is added to the measurement cause ‘EnergySaving’ and each transmitted RRCConnectionReject message caused by the other reasons is added to measurement cause ‘Unspecified’. d) Each measurement is an integer value. e) RRC.ConnEstabFaileNBCause.Congestion RRC.ConnEstabFaileNBCause.Unspecified RRC.ConnEstabFaileNBCause.EnergySaving f) EUtranCellFDD EUtranCellTDD g) Valid for packet switched traffic h) EPS i) The measurement is use to count ‘Failed RRC connection establishment related to load’ for LBO target setting and evaluation, see [15].

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

10.5.4.5a Call Control Capabilities

The purpose of the Call Control Capabilities information element is to identify the call control capabilities of the mobile station. The Call Control Capabilities information element is coded as shown in figure 10.5.89/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.116/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The Call Control Capabilities is a type 4 information element with a length of 4 octets. Figure 10.5.89/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Call Control Capabilities information element Table 10.5.116/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Call Control Capabilities

3GPP TS 24.008

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

CT WG1

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

10.5.4.5a

– NotificationMessageSidelink

The NotificationMessageSidelink message is used to send notification message from U2N Relay UE to the connected U2N Remote UE or from U2U Relay UE to the connected U2U Remote UE. Signalling radio bearer: SL-SRB3 RLC-SAP: AM Logical channel: SCCH Direction: U2N Relay UE to U2N Remote UE or U2U Relay UE to U2U Remote UE NotificationMessageSidelink message -- ASN1START -- TAG-NOTIFICATIONMESSAGESIDELINK-START NotificationMessageSidelink-r17 ::= SEQUENCE { criticalExtensions CHOICE { notificationMessageSidelink-r17 NotificationMessageSidelink-r17-IEs, criticalExtensionsFuture SEQUENCE {} } } NotificationMessageSidelink-r17-IEs ::= SEQUENCE { indicationType-r17 ENUMERATED { relayUE-Uu-RLF, relayUE-HO, relayUE-CellReselection, relayUE-Uu-RRC-Failure } OPTIONAL, -- Need N lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension NotificationMessageSidelink-v1800-IEs OPTIONAL } NotificationMessageSidelink-v1800-IEs ::= SEQUENCE { sl-IndicationType-r18 ENUMERATED {relayUE-PC5-RLF, spare1} OPTIONAL, -- Need N sl-DestinationIdentityRemoteUE-r18 SL-DestinationIdentity-r16 OPTIONAL, -- Need N nonCriticalExtension SEQUENCE {} OPTIONAL } -- TAG-NOTIFICATIONMESSAGESIDELINK -STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

A.1 PDU Session Establishment

The following figure shows an example message flow for a PDU session establishment. NAS procedures details between gNB and 5GC can be found in TS 23.501[ System architecture for the 5G System (5GS) ] [3], TS 23.502[ Procedures for the 5G System (5GS) ] [22] and TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [26]. Figure A.1-1: PDU session establishment 1. UE requests a PDU session establishment to AMF. 2. AMF sends a PDU SESSION RESOURCE SETUP REQUEST message to gNB, which includes the NAS message to be sent to the UE with NAS QoS related information. 3. gNB sends an RRCReconfiguration message to UE including the configuration of at least one DRB and the NAS message received at Step 2. 4. UE establishes the DRB(s) for the new PDU session and creates the QFI to DRB mapping rules. 5. UE sends an RRCReconfiguration Complete message to gNB. 6. gNB sends a PDU SESSION RESOURCE SETUP RESPONSE message to AMF. 7. User Plane Data can then be exchanged between UE and gNB over DRB(s) according to the mapping rules and between UPF and gNB over the tunnel for the PDU session. QFI marking over Uu is optional (see clause 12) while QFI marking over NG-U is always present.

3GPP TS 38.300

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

RAN2

3GPP Series : 38 , Radio technology beyond LTE

A.1

5.3.10.4 User Data and Signalling Confidentiality 5.3.10.4.0 General

There are two different levels of the security associations between the UE and the network. i) RRC and UP security association is between the UE and E-UTRAN. The RRC security associations protect the RRC signalling between the UE and E-UTRAN (integrity protection and ciphering). The UP security association is between the UE and E-UTRAN and can provide user plane encryption and integrity protection. ii) NAS security association is between the UE and the MME. It provides integrity protection and encryption of NAS signalling and, when the Control Plane CIoT EPS Optimisation is used, user data. Some earlier releases of the EPS specifications do not support User Plane Integrity Protection in EPS (EPS-UPIP). Hence UEs that support EPS-UPIP indicate this capability in the security algorithm octets of the UE Network Capability IE as defined in TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [46] and use it as described in TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [41]; and the MME copies this capability into S1-AP signalling sent to the E-UTRAN. The E-UTRAN can be locally configured with a policy (to be used when no explicit EPS UPIP policy is received from the MME), e.g. that the use of EPS-UPIP is "Preferred" for UE(s) that support User Plane Integrity Protection in EPS. For EPC networks with no 5GC interworking, E-UTRAN can have a preconfigured policy for "preferred" User Plane Integrity Protection that can be used if MME does not provide a security policy for the bearers of an UE and if the E-UTRAN has received an indication that the UE supports User Plane Integrity Protection. This preconfigured policy applies to any bearer of any UE unless the MME provides a User Plane Integrity Protection security policy to the E-UTRAN, in which case the MME policy overwrites the preconfigured E-UTRAN policy. Differentiated User plane integrity protection beyond preconfigured policy is only supported for PDN connections served by a SMF+PGW-C: to support PDN connections that "Require" the use of EPS-UPIP, the MME shall select a SMF+PGW-C. NOTE 1: See TS 23.502[ Procedures for the 5G System (5GS) ] [84] for additional features for EPS-UPIP in case of interworking with 5GC. NOTE 2: In this Release of the specifications, EPS UPIP can only be supported by UEs that support NR-PDCP.

3GPP TS 23.401

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

SA WG2

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

5.3.10.4

4.3.20.3 DeNB E-RAB activation/modification

This procedure is used by the DeNB to change the EPS bearer allocation for the RN. The procedure is the same as the normal network-initiated bearer activation/modification procedure with the exception that the S-GW/P-GW functionality (steps 1 and 6) is performed by the DeNB. Figure 4.3.20.3-1: DeNB-initiated bearer activation/modification procedure NOTE: It is up to implementation if and when the DeNB sets up and modifies EPS bearers for the RN, in addition to the initial bearer set up procedures at Attach.

3GPP TS 23.401

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

SA WG2

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

4.3.20.3

4.4.1.2 N4 Session Establishment procedure

The N4 Session Establishment procedure is used to create the initial N4 session context for a PDU Session at the UPF. The SMF assigns a new N4 Session ID and provides it to the UPF. The N4 Session ID is stored by both entities and used to identify the N4 session context during their interaction. The SMF also stores the relation between the N4 Session ID and PDU Session for a UE. Figure 4.4.1.2-1 N4 Session Establishment procedure 1. SMF receives the trigger to establish a new PDU Session or change the UPF for an established PDU Session. 2. The SMF sends an N4 session establishment request message to the UPF that contains the structured control information which defines how the UPF needs to behave. 3. The UPF responds with an N4 session establishment response message containing any information that the UPF has to provide to the SMF in response to the control information received. If the UPF (by configuration or other means) utilizes an NWDAF, UPF adds the NWDAF serving the UE identified by the NWDAF instance ID. Per NWDAF service instance the Analytics ID(s) are also included. NOTE: The SMF can use this NWDAF related information and can forward it to the PCF using the SMF initiated SM Policy Modification procedure, as a result of a Policy Control Request Trigger. 4. The SMF interacts with the network function which triggered this procedure (e.g. AMF or PCF).

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.4.1.2

5.8.9.6.3 Actions related to reception of UEAssistanceInformationSidelink message

For sidelink unicast, when a UE is in RRC_CONNECTED and is performing sidelink operation with resource allocation mode 1, it may report the sidelink DRX assistance information received within the UEAssistanceInformationSidelink from its peer UE to the network as specified in 5.8.3. For sidelink unicast, when a UE is in RRC_CONNECTED and is performing sidelink operation with resource allocation mode 2 or is in RRC_IDLE or RRC_INACTIVE or out of coverage, regardless of whether the UE has obtained the sidelink DRX assistance information from the UEAssistanceInformationSidelink transmitted from its peer UE or not, it may determine the sidelink DRX configuration SL-DRX-ConfigUC for its peer UE. NOTE: When UE determines the sidelink DRX configuration for its peer UE, it may take the sidelink DRX assistance information received from its peer UE into account.

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

5.8.9.6.3

4.4.2.1 Ro

The Ro reference point supports interaction between a CTF and an OCF. The following information may flow across this reference point: - Charging events for online charging from the CTF to the OCF. - Receive Acknowledgements for these charging events from the OCF to the CTF. The acknowledgement grants or rejects the network resource usage requested in the charging event, according to the decision taken by the OCS. The protocol(s) crossing this reference point shall support the following capabilities: - Real-time transactions; - Stateless mode ("event based charging") and statefull mode ("session based charging") of operation; NOTE: For "event based charging", the protocol may be stateless, however Internal implementation of the CTF and OCF may be stateful across the different charging events. - Provide its own reliability mechanisms, e.g. retransmission of charging events, to run also on unreliable transport. In addition, the protocol should support changeover to a secondary destination (alternate OCF(s)) in case of the primary OCF not being reachable. This interface application is defined in TS 32.299[ Telecommunication management; Charging management; Diameter charging applications ] [50]. The information contained in the charging events and the relevant chargeable events are specific to the domain / subsystem / service and are detailed in the respective middle tier TSs.

3GPP TS 32.240

Telecommunication management; Charging management; Charging architecture and principles

SA WG5

3GPP Series : 32 , OAM&P and Charging

4.4.2.1

7.10 Segmentation of RRC messages

An RRC message may be segmented in case the size of the encoded RRC message PDU exceeds the maximum PDCP SDU size. Segmentation is performed in the RRC layer using a separate RRC PDU to carry each segment. The receiver reassembles the segments to form the complete RRC message. All segments of an RRC message are transmitted before sending another RRC message. Segmentation is supported in both uplink and downlink as specified in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12].

3GPP TS 38.300

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

RAN2

3GPP Series : 38 , Radio technology beyond LTE

7.10

5 General architecture 5.1 General

The protocols over Uu and NG interfaces are divided into two structures: - User plane protocols These are the protocols implementing the actual PDU Session service, i.e. carrying user data through the access stratum. - Control plane protocols These are the protocols for controlling the PDU Sessions and the connection between the UE and the network from different aspects (including requesting the service, controlling different transmission resources, handover etc.). Also a mechanism for transparent transfer of NAS messages is included.

3GPP TS 38.401

NG-RAN; Architecture description

RAN3

3GPP Series : 38 , Radio technology beyond LTE

5

G.3.3 B2B charging data generation and quota supervision

Both B-CHF and C-CHF can generate CDRs, with information for both individual subscriber identification and the related business subscriber identifications if any. - The B- CHF generate CDRs for the business subscriber. - The C-CHF generate CDRs for the individual subscriber. In the business CHF only interaction, the quota is requested and granted between CTF and CHF. - The CTF request and consume quota from B-CHF. - B-CHF grant quota to the CTF. In the business CHF via consumer CHF interaction, the quota is requested and granted between CTF and B-CHF via C-CHF. - The CTF request and consume quota from B-CHF via C-CHF. - B-CHF grant quota to the CTF. - C-CHF forward and re-allocate quota. The Nchf services for interaction between C-CHF and B-CHF are specified in TS 32.290[ Telecommunication management; Charging management; 5G system; Services, operations and procedures of charging using Service Based Interface (SBI) ] [57].

3GPP TS 32.240

Telecommunication management; Charging management; Charging architecture and principles

SA WG5

3GPP Series : 32 , OAM&P and Charging

G.3.3

4.7.6.2 P-TMSI reallocation completion by the MS

Upon receipt of the P-TMSI REALLOCATION COMMAND message, the MS shall store the routing area identifier (RAI) and the P-TMSI. Furthermore, the MS shall send a P-TMSI REALLOCATION COMPLETE message to the network. If a P-TMSI signature is present in the P-TMSI REALLOCATION COMMAND message, the MS shall store the new P-TMSI signature and shall if available delete the old P-TMSI signature. If no P-TMSI signature is present in the P-TMSI REALLOCATION COMMAND message, the old P-TMSI signature, if available, shall be kept. If the P-TMSI REALLOCATION COMMAND message contains the DCN-ID IE, then the MS shall store the included DCN-ID value together with the PLMN code of the registered PLMN in a DCN-ID list in a non-volatile memory in the ME as described in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120], annex C.

3GPP TS 24.008

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

CT WG1

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

4.7.6.2

5.5.1.3.5 Combined attach not accepted by the network

If the attach request can neither be accepted by the network for EPS nor for non-EPS services, the MME shall send an ATTACH REJECT message to the UE including an appropriate EMM cause value. If EMM-REGISTERED without PDN connection is not supported by the UE or the MME, the attach request included a PDN CONNECTIVITY REQUEST message, and the attach procedure fails due to a default EPS bearer setup failure, an ESM procedure failure or operator determined barring, the MME shall: - combine the ATTACH REJECT message with a PDN CONNECTIVITY REJECT message contained in the ESM message container information element. In this case the EMM cause value in the ATTACH REJECT message shall be set to #19, "ESM failure"; or - send the ATTACH REJECT message with the EMM cause set to #15 "No suitable cells in tracking area", if the PDN connectivity reject is due to ESM cause #29 subject to operator policies (see 3GPP TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [16D] for further details). In this case, the network may additionally include the Extended EMM cause IE with value "E-UTRAN not allowed". If the attach request is rejected due to NAS level mobility management congestion control, the network shall set the EMM cause value to #22 "congestion" and assign a back-off timer T3346. If the attach request is rejected due to service gap control as specified in clause 5.3.17 i.e. the T3447 timer is running, the network shall set the EMM cause value to #22 "congestion" and may assign a back-off timer T3346 with the remaining time of the running T3447 timer. Based on operator policy, if the attach request is rejected due to core network redirection for CIoT optimizations, the network shall set the EMM cause value to #31 "Redirection to 5GCN required". NOTE: The network can take into account the UE's N1 mode capability, the 5GS CIoT network behaviour supported by the UE or the 5GS CIoT network behaviour supported by the 5GCN to determine the rejection with the EMM cause value #31 "Redirection to 5GCN required". Upon receiving the ATTACH REJECT message, if the message is integrity protected or contains a reject cause other than EMM cause value #25, the UE shall stop timer T3410 and enter MM state MM IDLE. If the ATTACH REJECT message with EMM cause #25 or #78 was received without integrity protection, then the UE shall discard the message. The UE shall take the following actions depending on the EMM cause value received in the ATTACH REJECT message. #3 (Illegal UE); #6 (Illegal ME); or #8 (EPS services and non-EPS services not allowed); The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to clause5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and eKSI. The UE shall consider the USIM as invalid for EPS and non-EPS services until switching off or the UICC containing the USIM is removed or the timer T3245 expires as described in clause 5.3.7a. Additionally, the UE shall delete the list of equivalent PLMNs and shall enter the state EMM-DEREGISTERED.NO-IMSI. If the message has been successfully integrity checked by the NAS and the UE maintains a counter for "SIM/USIM considered invalid for GPRS services", then the UE shall set this counter to UE implementation-specific maximum value. If the message has been successfully integrity checked by the NAS and the UE maintains a counter for "SIM/USIM considered invalid for non-GPRS services", then the UE shall set this counter to UE implementation-specific maximum value. If A/Gb mode or Iu mode is supported by the UE, the UE shall in addition handle the MM parameters update status, TMSI, LAI and ciphering key sequence number, and the GMM parameters GMM state, GPRS update status, P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the combined attach procedure is rejected with the GMM cause with the same value. For the EMM cause value #3 or #6, if the UE is operating in single-registration mode, the UE shall in addition handle the 5GMM parameters 5GMM state, 5GS update status, 5G-GUTI, last visited registered TAI, TAI list and ngKSI as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the initial registration procedure performed over 3GPP access is rejected with the 5GMM cause with the same value. For the EMM cause value #8, if the UE is operating in single-registration mode, the UE shall in addition set the 5GMM state to 5GMM-DEREGISTERED, 5GS update status to 5U3 ROAMING NOT ALLOWED, and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. #7 (EPS services not allowed); The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and eKSI. The UE shall consider the USIM as invalid for EPS services until switching off or the UICC containing the USIM is removed or the timer T3245 expires as described in clause 5.3.7a. Additionally, the UE shall enter the state EMM-DEREGISTERED. If the message has been successfully integrity checked by the NAS and the UE maintains a counter for "SIM/USIM considered invalid for GPRS services", then the UE shall set this counter to UE implementation-specific maximum value. A UE which is already IMSI attached for non-EPS services is still IMSI attached for non-EPS services and shall set the update status to U2 NOT UPDATED. The UE shall attempt to select GERAN or UTRAN radio access technology and shall proceed with the appropriate MM specific procedure according to the MM service state. The UE shall not reselect E-UTRAN radio access technology until switching off or the UICC containing the USIM is removed. If A/Gb mode or Iu mode is supported by the UE, the UE shall in addition handle the GMM parameters GMM state, GPRS update status, P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the combined attach procedure is rejected with the GMM cause with the same value. If the UE is operating in single-registration mode, the UE shall in addition handle the 5GMM parameters 5GMM state, 5GS update status, 5G-GUTI, last visited registered TAI, TAI list and ngKSI as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the initial registration procedure performed over 3GPP access is rejected with the 5GMM cause with the same value. #11 (PLMN not allowed); or #35 (Requested service option not authorized in this PLMN); The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and eKSI, and reset the attach attempt counter. The UE shall delete the list of equivalent PLMNs and enter the state EMM-DEREGISTERED.PLMN-SEARCH. The UE shall store the PLMN identity in the "forbidden PLMN list" and if the UE is configured to use timer T3245 (see 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]) then the UE shall start timer T3245 and proceed as described in clause 5.3.7a. If the message has been successfully integrity checked by the NAS and the UE maintains a PLMN-specific attempt counter for that PLMN, then the UE shall set this counter to the UE implementation-specific maximum value. The UE shall perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. If A/Gb mode or Iu mode is supported by the UE, the UE shall in addition handle the MM parameters update status, TMSI, LAI, ciphering key sequence number and location update attempt counter, and the GMM parameters GMM state, GPRS update status, P-TMSI, P-TMSI signature, RAI, GPRS ciphering key sequence number and GPRS attach attempt counter as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the combined attach procedure is rejected with the GMM cause value #11 and no RR connection exists. For the EMM cause value #11, if the UE is operating in single-registration mode, the UE shall in addition handle the 5GMM parameters 5GMM state, 5GS update status, 5G-GUTI, last visited registered TAI, TAI list, ngKSI and registration attempt counter as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the initial registration procedure performed over 3GPP access is rejected with the 5GMM cause with the same value. For the EMM cause value #35, if the UE is operating in single-registration mode, the UE shall in addition set the 5GMM state to 5GMM-DEREGISTERED, 5GS update status to 5U3 ROAMING NOT ALLOWED, and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. Additionally, the UE shall reset the registration attempt counter. #12 (Tracking area not allowed); The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and eKSI. The UE shall reset the attach attempt counter and enter the state EMM-DEREGISTERED.LIMITED-SERVICE. The UE shall store the current TAI in the list of "forbidden tracking areas for regional provision of service". If the ATTACH REJECT message is not integrity protected, the UE shall memorize the current TAI was stored in the list of "forbidden tracking areas for regional provision of service" for non-integrity protected NAS reject message. If A/Gb mode or Iu mode is supported by the UE, the UE shall in addition handle the MM parameters update status, TMSI, LAI, ciphering key sequence number and location update attempt counter, and the GMM parameters GMM state, GPRS update status, P-TMSI, P-TMSI signature, RAI, GPRS ciphering key sequence number and GPRS attach attempt counter as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the combined attach procedure is rejected with the GMM cause with the same value. If the UE is operating in single-registration mode, the UE shall in addition handle the 5GMM parameters 5GMM state, 5GS update status, 5G-GUTI, last visited registered TAI, TAI list, ngKSI and registration attempt counter as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the initial registration procedure performed over 3GPP access is rejected with the 5GMM cause with the same value. #13 (Roaming not allowed in this tracking area); The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and eKSI. The UE shall delete the list of equivalent PLMNs and reset the attach attempt counter. Additionally the UE enter the state EMM-DEREGISTERED.LIMITED-SERVICE or optionally EMM-DEREGISTERED.PLMN-SEARCH. The UE shall store the current TAI in the list of "forbidden tracking areas for roaming". If the ATTACH REJECT message is not integrity protected, the UE shall memorize the current TAI was stored in the list of "forbidden tracking areas for roaming" for non-integrity protected NAS reject message. If the UE is registered in N1 mode and operating in dual-registration mode, the PLMN that the UE chooses to register in is specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] clause 4.8.3. Otherwise the UE shall perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. If A/Gb mode or Iu mode is supported by the UE, the UE shall in addition handle the MM parameters update status, TMSI, LAI, ciphering key sequence number and location update attempt counter, and the GMM parameters GMM state, GPRS update status, P-TMSI, P-TMSI signature, RAI, GPRS ciphering key sequence number and GPRS attach attempt counter as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the combined attach procedure is rejected with the GMM cause with the same value. If the UE is operating in single-registration mode, the UE shall in addition handle the 5GMM parameters 5GMM state, 5GS update status, 5G-GUTI, last visited registered TAI, TAI list, ngKSI and registration attempt counter as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the initial registration procedure performed over 3GPP access is rejected with the 5GMM cause with the same value. #14 (EPS services not allowed in this PLMN); The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and eKSI. Additionally the UE shall reset the attach attempt counter and enter the state EMM-DEREGISTERED.PLMN-SEARCH. The UE shall store the PLMN identity in the "forbidden PLMNs for GPRS service" list and if the UE is configured to use timer T3245 (see 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]) then the UE shall start timer T3245 and proceed as described in clause 5.3.7a. If the message has been successfully integrity checked by the NAS and the UE maintains a PLMN-specific PS-attempt counter for that PLMN, then the UE shall set this counter to the UE implementation-specific maximum value. A UE operating in CS/PS mode 1 or CS/PS mode 2 of operation which is already IMSI attached for non-EPS services is still IMSI attached for non-EPS services and shall set the update status to U2 NOT UPDATED. A UE operating in CS/PS mode 1 of operation and supporting A/Gb or Iu mode may select GERAN or UTRAN radio access technology and proceed with the appropriate MM specific procedure according to the MM service state. In this case, the UE shall disable the E-UTRA capability (see clause 4.5). A UE operating in CS/PS mode 1 of operation and supporting A/Gb or Iu mode may perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. A UE operating in CS/PS mode 1 of operation and supporting S1 mode only, or operating in CS/PS mode 2 of operation shall delete the list of equivalent PLMNs and shall perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. If A/Gb mode or Iu mode is supported by the UE, the UE shall in addition handle the GMM parameters GMM state, GPRS update status, P-TMSI, P-TMSI signature, RAI, GPRS ciphering key sequence number and GPRS attach attempt counter as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the combined attach procedure is rejected with the GMM cause with the same value. If the UE is operating in single-registration mode, the UE shall in addition set the 5GMM state to 5GMM-DEREGISTERED, 5GS update status to 5U3 ROAMING NOT ALLOWED, and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. Additionally, the UE shall reset the registration attempt counter. #15 (No suitable cells in tracking area); The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and eKSI. Additionally the UE shall reset the attach attempt counter and enter the state EMM-DEREGISTERED.LIMITED-SERVICE. The UE shall store the current TAI in the list of "forbidden tracking areas for roaming". If the ATTACH REJECT message is not integrity protected, the UE shall memorize the current TAI was stored in the list of "forbidden tracking areas for roaming" for non-integrity protected NAS reject message. Additionally, the UE shall proceed as follows: - if the UE is in WB-S1 mode and the Extended EMM cause IE with value "E-UTRAN not allowed" is included in the ATTACH REJECT message, the UE supports "E-UTRA Disabling for EMM cause #15", and the "E-UTRA Disabling Allowed for EMM cause #15" parameter as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17] is present and set to enabled, then the UE shall disable the E-UTRA capability as specified in clause 4.5 and search for a suitable cell in another location area or 5GS tracking area; - if the UE is in NB-S1 mode and the Extended EMM cause IE with value "NB-IoT not allowed" is included in the ATTACH REJECT message, then the UE may disable the NB-IoT capability as specified in clause 4.9 and search for a suitable cell in E-UTRAN radio access technology; - otherwise, the UE shall search for a suitable cell in another tracking area or in another location area according to 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [21]. If A/Gb mode or Iu mode is supported by the UE, the UE shall in addition handle the MM parameters update status, TMSI, LAI, ciphering key sequence number and location update attempt counter, and the GMM parameters GMM state, GPRS update status, P-TMSI, P-TMSI signature, RAI, GPRS ciphering key sequence number and GPRS attach attempt counter as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the combined attach procedure is rejected with the GMM cause with the same value. If the UE is operating in single-registration mode, the UE shall in addition handle the 5GMM parameters 5GMM state, 5GS update status, 5G-GUTI, last visited registered TAI, TAI list, ngKSI and registration attempt counter as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the initial registration procedure performed over 3GPP access is rejected with the 5GMM cause with the same value. #22 (Congestion); If the T3346 value IE is present in the ATTACH REJECT message and the value indicates that this timer is neither zero nor deactivated, the UE shall proceed as described below; otherwise it shall be considered as an abnormal case and the behaviour of the UE for this case is specified in clause 5.5.1.3.6. The UE shall abort the attach procedure, reset the attach attempt counter, set the EPS update status to EU2 NOT UPDATED and enter state EMM-DEREGISTERED.ATTEMPTING-TO-ATTACH. The UE shall stop timer T3346 if it is running. If the ATTACH REJECT message is integrity protected, the UE shall start timer T3346 with the value provided in the T3346 value IE. If the ATTACH REJECT message is not integrity protected, the UE shall start timer T3346 with a random value from the default range specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13]. The UE stays in the current serving cell and applies the normal cell reselection process. The attach procedure is started if still needed when timer T3346 expires or is stopped. If A/Gb mode or Iu mode is supported by the UE, the UE shall in addition handle the GMM parameters GMM state, GPRS update status and GPRS attach attempt counter as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the combined attach procedure is rejected with the GMM cause with the same value. If the UE is operating in single-registration mode, the UE shall in addition handle the 5GMM parameters 5GMM state, 5GS update status and registration attempt counter as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the initial registration procedure performed over 3GPP access is rejected with the 5GMM cause with the same value. #25 (Not authorized for this CSG); EMM cause #25 is only applicable when received from a CSG cell. EMM cause #25 received from a non-CSG cell is considered as an abnormal case and the behaviour of the UE is specified in clause 5.5.1.3.6. The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and store it according to clause 5.1.3.3). Additionally, the UE shall reset the attach attempt counter and shall enter the state EMM-DEREGISTERED.LIMITED-SERVICE. If the CSG ID and associated PLMN identity of the cell where the UE has sent the ATTACH REQUEST message are contained in the Allowed CSG list, the UE shall remove the entry corresponding to this CSG ID and associated PLMN identity from the Allowed CSG list. If the CSG ID and associated PLMN identity of the cell where the UE has sent the ATTACH REQUEST message are contained in the Operator CSG list, the UE shall apply the procedures defined in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6] clause 3.1A. The UE shall search for a suitable cell according to 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [21]. If A/Gb mode or Iu mode is supported by the UE, the UE shall in addition handle the MM parameters update status and location update attempt counter, and GMM parameters GMM state, GPRS update status and GPRS attach attempt counter as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the combined attach procedure is rejected with the GMM cause with the same value. If the UE is operating in single-registration mode, the UE shall in addition set the 5GMM state to 5GMM-DEREGISTERED and set the 5GS update status to 5U3 ROAMING NOT ALLOWED and reset the registration attempt counter. #31 (Redirection to 5GCN required); EMM cause #31 received by a UE that has not indicated support for CIoT optimizations or not indicated support for N1 mode is considered as an abnormal case and the behaviour of the UE is specified in clause 5.5.1.3.6. The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and eKSI. Additionally, the UE shall reset the attach attempt counter. The UE shall enable N1 mode capability for 3GPP access if it was disabled and disable the E-UTRA capability (see clause 4.5) and enter state EMM-DEREGISTERED.NO-CELL-AVAILABLE. If the UE is operating in single-registration mode, the UE shall in addition handle the 5GMM parameters 5GMM state, 5GS update status, 5G-GUTI, last visited registered TAI, TAI list, ngKSI and registration attempt counter as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the initial registration procedure performed over 3GPP access is rejected with the 5GMM cause with the same value. #36 (IAB-node operation not authorized); The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and eKSI, and reset the attach attempt counter. The UE shall delete the list of equivalent PLMNs and enter the state EMM-DEREGISTERED.PLMN-SEARCH. The UE shall store the PLMN identity in the "forbidden PLMN list" and if the UE is configured to use timer T3245 (see 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]) then the UE shall start timer T3245 and proceed as described in subclause 5.3.7a. If the message has been successfully integrity checked by the NAS and the UE maintains a PLMN-specific attempt counter for that PLMN, then the UE shall set this counter to the UE implementation-specific maximum value. The UE shall perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. If the UE is operating in single-registration mode, the UE shall in addition handle the 5GMM parameters 5GMM state, 5GS update status, 5G-GUTI, last visited registered TAI, TAI list and ngKSI as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the initial registration procedure performed over 3GPP access is rejected with the 5GMM cause with the same value. #42 (Severe network failure); The UE shall set the EPS update status to EU2 NOT UPDATED, and shall delete any GUTI, last visited registered TAI, TAI list, eKSI, and list of equivalent PLMNs, and set the attach attempt counter to 5. The UE shall start an implementation specific timer, setting its value to 2 times the value of T as defined in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. While this timer is running, the UE shall not consider the PLMN + RAT combination that provided this reject cause as a candidate for PLMN selection. The UE then enters state EMM-DEREGISTERED.PLMN-SEARCH in order to perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. If A/Gb mode or Iu mode is supported by the UE, the UE shall in addition set the GMM state to GMM-DEREGISTERED, GPRS update status to GU2 NOT UPDATED signature, RAI and GPRS ciphering key sequence number TMSI and ciphering key sequence number. If the UE is operating in single-registration mode, the UE shall in addition set the 5GMM state to 5GMM-DEREGISTERED, 5GS update status to 5U2 NOT UPDATED, and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. Other values are considered as abnormal cases. The behaviour of the UE in those cases is specified in clause 5.5.1.3.6.

3GPP TS 24.301

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

CT WG1

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

5.5.1.3.5

16.10.6.5.2 Service Continuity in RRC_CONNECTED

To ensure service continuity of MBS broadcast, the UE in RRC_CONNECTED state may send MBS Interest Indication to the gNB, consisting of the following information: - List of MBS frequencies UE is receiving or interested to receive, sorted in decreasing order of interest; - Priority between the reception of all listed MBS frequencies and the reception of any unicast bearer and multicast MRB; - List of MBS broadcast services the UE is receiving or interested to receive, in case SIB20 is provided for PCell or SCell. MBS Interest Indication information reporting can be implicitly enabled/disabled by the presence of SIB21. The gNB may use this information, together with the information about the UE's capabilities (e.g., supported band combinations), when providing an RRC configuration and/or downlink assignments to the UE or to release DRBs/multicast MRBs, to allow the UE to receive the MBS services the UE is interested in. MBS Interest Indication information can be exchanged between source gNB and target gNB during handover.

3GPP TS 38.300

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

RAN2

3GPP Series : 38 , Radio technology beyond LTE

16.10.6.5.2

5.15.5.2.1 Registration to a set of Network Slices

When a UE registers over an Access Type with a PLMN, if the UE has either or both of: - a Configured NSSAI for this PLMN; - an Allowed NSSAI for this PLMN and Access Type; the UE shall provide to the network, in AS layer under the conditions described in clause 5.15.9 and in NAS layer, a Requested NSSAI containing the S-NSSAI(s) corresponding to the Network Slice(s) to which the UE wishes to register, unless they are stored in the UE in the Pending NSSAI. The Requested NSSAI shall be one of: - the Default Configured NSSAI, i.e. if the UE has no Configured NSSAI nor an Allowed NSSAI for the serving PLMN; - the Configured-NSSAI, or a subset thereof as described below, e.g. if the UE has no Allowed NSSAI for the Access Type for the serving PLMN; - the Allowed-NSSAI for the Access Type over which the Requested NSSAI is sent, or a subset thereof; or - the Allowed-NSSAI for the Access Type over which the Requested NSSAI is sent, or a subset thereof, plus one or more S-NSSAIs from the Configured-NSSAI not yet in the Allowed NSSAI for the Access Type as described below. NOTE 1: If the UE wishes to register only a subset of the S-NSSAIs from the Configured NSSAI or the Allowed NSSAI, to be able to register with some Network Slices e.g. to establish PDU Sessions for some application(s), and the UE uses the URSP rules (which includes the NSSP) or the UE Local Configuration as defined in clause 6.1.2.2.1 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45], then the UE uses applicable the URSP rules or the UE Local Configuration to ensure that the S-NSSAIs included in the Requested NSSAI are not in conflict with the URSP rules or with the UE Local Configuration. The subset of S-NSSAIs in the Configured-NSSAI provided in the Requested NSSAI consists of one or more S-NSSAI(s) in the Configured NSSAI applicable to this PLMN, if one is present, and for which no corresponding S-NSSAI is already present in the Allowed NSSAI for the access type for this PLMN. The UE shall not include in the Requested NSSAI any S-NSSAI that is currently rejected by the network (i.e. rejected in the current registration area or rejected in the PLMN). For the registration to a PLMN for which neither a Configured NSSAI applicable to this PLMN or an Allowed NSSAI are present, the S-NSSAIs provided in the Requested NSSAI correspond to the S-NSSAI(s) in the Default Configured NSSAI unless the UE has HPLMN S-NSSAI for established PDU Session(s) in which case the HPLMN S-NSSAI(s) shall be provided in the mapping of Requested NSSAI in the NAS Registration Request message, with no corresponding VPLMN S-NSSAI in the Requested NSSAI. If the UE has been provided with NSSRG information together with the Configured NSSAI, the UE only includes in the Requested NSSAI S-NSSAIs that share a common NSSRG, see clause 5.15.12.2. If the UE has stored Pending NSSAI and the UE is still interested in the Pending NSSAI then all the S-NSSAIs in the Requested NSSAI and the Pending S-NSSAI shall share a common NSSRG. When a UE registers over an Access Type with a PLMN, the UE shall also indicate in the Registration Request message when the Requested NSSAI is based on the Default Configured NSSAI. The UE shall include the Requested NSSAI in the RRC Connection Establishment and in the establishment of the connection to the N3IWF/TNGF (as applicable) and in the NAS Registration procedure messages subject to conditions set out in clause 5.15.9. However, the UE shall not indicate any NSSAI in RRC Connection Establishment or Initial NAS message unless it has either a Configured NSSAI for the corresponding PLMN, an Allowed NSSAI for the corresponding PLMN and Access Type, or the Default Configured NSSAI. If the UE has HPLMN S-NSSAI(s) for established PDU Session(s), the HPLMN S-NSSAI(s) shall be provided in the mapping of Requested NSSAI in the NAS Registration Request message, independent of whether the UE has the corresponding VPLMN S-NSSAI. The (R)AN shall route the NAS signalling between this UE and an AMF selected using the Requested NSSAI obtained during RRC Connection Establishment or connection to N3IWF/TNGF respectively. If the (R)AN is unable to select an AMF based on the Requested NSSAI, it routes the NAS signalling to an AMF from a set of default AMFs. In the NAS signalling, if the UE is roaming, the UE provides the mapping of each S-NSSAI of the Requested NSSAI to a corresponding HPLMN S-NSSAI. When a UE registers with a PLMN, if for this PLMN the UE has not included a Requested NSSAI nor a GUAMI while establishing the connection to the (R)AN, the (R)AN shall route all NAS signalling from/to this UE to/from a default AMF. When receiving from the UE a Requested NSSAI and a 5G-S-TMSI or a GUAMI in RRC Connection Establishment or in the establishment of connection to N3IWF/TNGF, if the 5G-AN can reach an AMF corresponding to the 5G-S-TMSI or GUAMI, then 5G-AN forwards the request to this AMF. Otherwise, the 5G-AN selects a suitable AMF based on the Requested NSSAI provided by the UE and forwards the request to the selected AMF. If the 5G-AN is not able to select an AMF based on the Requested NSSAI, then the request is sent to a default AMF. When the AMF selected by the AN during Registration Procedure receives the UE Registration request, or after an AMF selection by MME (i.e. during EPS to 5GS handover) the AMF receives S-NSSAI(s) from SMF+PGW-C in 5GC: - As part of the Registration procedure described in clause 4.2.2.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3], or as part of the EPS to 5GS handover using N26 interface procedure described in clause 4.11.1.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3], the AMF may query the UDM to retrieve UE subscription information including the Subscribed S-NSSAIs. - The AMF verifies whether the S-NSSAI(s) in the Requested NSSAI or the S-NSSAI(s) received from SMF+PGW-C are permitted based on the Subscribed S-NSSAIs (to identify the Subscribed S-NSSAIs the AMF may use the mapping to HPLMN S-NSSAIs provided by the UE, in the NAS message, for each S-NSSAI of the Requested NSSAI). - When the UE context in the AMF does not yet include an Allowed NSSAI for the corresponding Access Type, the AMF queries the NSSF (see (B) below for subsequent handling), except in the case when, based on configuration in this AMF, the AMF is allowed to determine whether it can serve the UE (see (A) below for subsequent handling). The IP address or FQDN of the NSSF is locally configured in the AMF. NOTE 2: The configuration in the AMF depends on operator's policy. - When the UE context in the AMF already includes an Allowed NSSAI for the corresponding Access Type, based on the configuration for this AMF, the AMF may be allowed to determine whether it can serve the UE (see (A) below for subsequent handling). - AMF or NSSF may have previously subscribed to slice load level and/or Observed Service Experience and/or Dispersion Analytics related network data analytics for a Network Slice from NWDAF, optionally for an Area of Interest composed of one or several TAIs. If AMF subscribes to analytics, AMF may determine that it cannot serve the UE based on received analytics (see (A) below). If AMF subscribes to notifications on changes on the Network Slice or Network Slice instance availability information from NSSF optionally indicating a list of supported TAIs, it may determine that it cannot serve the UE after the restriction notification is received (see (A) below). If AMF does not subscribe to notifications on changes on the availability information from NSSF, NSSF may take the analytics information into account when AMF queries NSSF (see (B) below). NOTE 3: The configuration in the AMF depends on the operator's policy. (A) Depending on fulfilling the configuration as described above, the AMF may be allowed to determine whether it can serve the UE, and the following is performed: - For the mobility from EPS to 5GS, the AMF first derives the serving PLMN value(s) of S-NSSAI(s) based on the HPLMN S-NSSAI(s) in the mapping of Requested NSSAI (in CM-IDLE state) or the HPLMN S-NSSAI(s) received from SMF+PGW-C (in CM-CONNECTED state). After that the AMF regards the derived value(s) as the Requested NSSAI. - For the inter PLMN within 5GC mobility, the new AMF derives the serving PLMN value(s) of S-NSSAI(s) based on the HPLMN S-NSSAI(s) in the mapping of Requested NSSAI. After that the AMF regards the derived value(s) as the Requested NSSAI. - AMF checks whether it can serve all the S-NSSAI(s) from the Requested NSSAI present in the Subscribed S-NSSAIs (potentially using configuration for mapping S-NSSAI values between HPLMN and Serving PLMN), or all the S-NSSAI(s) marked as default in the Subscribed S-NSSAIs in the case that no Requested NSSAI was provided or none of the S-NSSAIs in the Requested NSSAI are permitted, i.e. do not match any of the Subscribed S-NSSAIs or not available at the current UE's Tracking Area (see clause 5.15.3). If the AMF is configured with a local policy to include in the Allowed NSSAI subscribed S-NSSAIs that are not in the Requested NSSAI and some of the Subscribed S-NSSAIs are not supported by the AMF, the AMF queries the NSSF (see (B) below). - If AMF has subscribed to slice load level and/or Observed Service Experience and/or Dispersion Analytics related network data analytics for a Network Slice from NWDAF, or if AMF had received a Network Slice restriction from NSSF that applies to the list of TAIs supported by the AMF, it may use that information to determine whether the AMF can serve the UE on the S-NSSAI(s) in the Requested NSSAI. - If the AMF can serve the S-NSSAIs in the Requested NSSAI and any additional S-NSSAI added due to local policy as described below, the AMF remains the serving AMF for the UE. The Allowed NSSAI is then determined by taking into account the list of S-NSSAI(s) in the Requested NSSAI permitted based on the Subscribed S-NSSAIs and/or the list of S-NSSAI(s) for the Serving PLMN which are mapped to the HPLMN S-NSSAI(s) provided in the mapping of Requested NSSAI permitted based on the Subscribed S-NSSAIs, or, if neither Requested NSSAI nor the mapping of Requested NSSAI was provided or none of the S-NSSAIs in the Requested NSSAI are permitted, all the S-NSSAI(s) marked as default in the Subscribed S-NSSAIs and taking also into account the availability of the Network Slice instances as described in clause 5.15.8 that are able to serve the S-NSSAI(s) in the Allowed NSSAI in the current UE's Tracking Areas in addition to any Network Slice instance restriction for the S-NSSAI(s) in the Allowed NSSAI provided by the NSSF. The AMF based on local policy may determine to include in the Allowed NSSAI additional Subscribed S-NSSAIs e.g. Subscribed S-NSSAIs not marked as default and/or Subscribed S-NSSAIs that were not provided in the Requested NSSAI (See NOTE 4). If the AMF has received NSSRG Information for the Subscribed S-NSSAIs as part of the UE subscription information, it shall only include in the Allowed NSSAI S-NSSAIs that all share a common NSSRG (see clause 5.15.12). If at least one S-NSSAI in the Requested NSSAI is not available in the current UE's Tracking Area, then either the AMF may determine a Target NSSAI or step (B) is executed. The AMF also determines the mapping if the S-NSSAI(s) included in the Allowed NSSAI needs to be mapped to Subscribed S-NSSAI(s) values. If no Requested NSSAI is provided, or the mapping of the S-NSSAIs in Requested NSSAI to HPLMN S-NSSAIs is incorrect, or the Requested NSSAI includes an S-NSSAI that is not valid in the Serving PLMN, or the UE indicated that the Requested NSSAI is based on the Default Configured NSSAI, the AMF, based on the Subscribed S-NSSAI(s) and operator's configuration, may also determine the Configured NSSAI for the Serving PLMN and, if applicable, the associated mapping of the Configured NSSAI to HPLMN S-NSSAIs, so these can be configured in the UE. Then Step (C) is executed. NOTE 4: The ability for the AMF to construct the Allowed NSSAI with values not contained in Requested NSSAI but permitted by subscribed NSSAI can be used to allow the UE to use newly-added S-NSSAI(s) in the case of Network Slicing Subscription Change (see clause 4.2.2.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]). - Else, the AMF queries the NSSF (see (B) below). (B) When required as described above, the AMF needs to query the NSSF, and the following is performed: - The AMF queries the NSSF, with Requested NSSAI, Default Configured NSSAI Indication, mapping of Requested NSSAI to HPLMN S-NSSAIs, the Subscribed S-NSSAIs (with an indication if marked as default S-NSSAI), NSSRG Information (if provided by the UDM, see clause 5.15.12), any Allowed NSSAI it might have for the other Access Type (including its mapping to HPLMN S-NSSAIs), PLMN ID of the SUPI and UE's current Tracking Area. If the AMF has pending NSSAI for the UE then the AMF includes pending NSSAI in the Requested NSSAI. NOTE 5: The Default Configured NSSAI Indication is provided when received from the UE or when the AMF indicates to the NSSF to return Configured NSSAI in case of the Network Slicing Subscription Change Indication is received from UDM. - Based on this information, local configuration, and other locally available information including RAN capabilities in the current Tracking Area for the UE or load level information for a Network Slice instance provided by the NWDAF, the NSSF does the following: - It verifies which S-NSSAI(s) in the Requested NSSAI are permitted based on comparing the Subscribed S-NSSAIs with the S-NSSAIs in the mapping of Requested NSSAI to HPLMN S-NSSAIs. It considers the S-NSSAI(s) marked as default in the Subscribed S-NSSAIs in the case that no Requested NSSAI was provided or no S-NSSAI from the Requested NSSAI are permitted i.e. are not present in the Subscribed S-NSSAIs or not available e.g. at the current UE's Tracking Area. If NSSRG information is provided, the NSSF only selects S-NSSAIs that share a common NSSRG (see clause 5.15.12). - If AMF has not subscribed to notifications on changes on the Network Slice or Network Slice instance availability information from NSSF and NSSF has subscribed to slice load level and/or Observed Service Experience and/or Dispersion Analytics related network data analytics for a Network Slice from NWDAF, NSSF may use the analytics information for the determination of the (Network Slice instance(s) and the) list of S-NSSAI(s) in the Allowed NSSAI(s) to serve the UE. - It selects the Network Slice instance(s) to serve the UE. When multiple Network Slice instances in the UE's Tracking Area are able to serve a given S-NSSAI, based on operator's configuration, the NSSF may select one of them to serve the UE, or the NSSF may defer the selection of the Network Slice instance until a NF/service within the Network Slice instance needs to be selected. - It determines the target AMF Set to be used to serve the UE, or, based on configuration, the list of candidate AMF(s), possibly after querying the NRF. NOTE 6: If the target AMF(s) returned from the NSSF is the list of candidate AMF(s), the Registration Request message can only be redirected via the direct signalling between the initial AMF and the selected target AMF as described in clause 5.15.5.2.3. The NSSF does not provide the target AMF(s), when it provides a Target NSSAI in order to redirect or handover the UE to a cell of another TA as described in clause 5.3.4.3.3. - It determines the Allowed NSSAI(s) for the applicable Access Type, by taking into account the list of S-NSSAI(s) in the Requested NSSAI permitted based on the Subscribed S-NSSAIs and/or the list of S-NSSAI(s) for the Serving PLMN which are mapped to the HPLMN S-NSSAIs provided in the mapping of Requested NSSAI permitted based on the Subscribed S-NSSAIs, or, if neither Requested NSSAI nor the mapping of Requested NSSAI was provided or none of the S-NSSAIs in the Requested NSSAI are permitted, all the S-NSSAI(s) marked as default in the Subscribed S-NSSAIs, and taking also into account the availability of the Network Slice instances as described in clause 5.15.8 that are able to serve the S-NSSAI(s) in the Allowed NSSAI in the current UE's Tracking Areas and taking also into account local policy in the NSSF that may determine to include in the Allowed NSSAI additional Subscribed S-NSSAIs e.g. Subscribed S-NSSAIs not marked as default and/or Subscribed S-NSSAIs that were not provided in the Requested NSSAI (see NOTE 7). If NSSRG information applies, the NSSF only selects S-NSSAIs that share a common NSSRG (see clause 5.15.12). NOTE 7: The ability for the NSSF to construct the Allowed NSSAI with values not contained in Requested NSSAI but permitted by Subscribed NSSAIs can be used to allow the UE to use newly-added S-NSSAI(s) in the case of Network Slicing Subscription Change (see clause 4.2.2.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]). - It also determines the mapping of each S-NSSAI of the Allowed NSSAI(s) to the Subscribed S-NSSAIs if necessary. - Based on operator configuration, the NSSF may determine the NRF(s) to be used to select NFs/services within the selected Network Slice instance(s). - Additional processing to determine the Allowed NSSAI(s) in roaming scenarios and the mapping to the Subscribed S-NSSAIs, as described in clause 5.15.6. - If no Requested NSSAI is provided or the Requested NSSAI includes an S-NSSAI that is not valid in the Serving PLMN, or the mapping of the S-NSSAIs in Requested NSSAI to HPLMN S-NSSAIs is incorrect, the NSSF based on the Subscribed S-NSSAI(s) and operator configuration may also determine the Configured NSSAI for the Serving PLMN and, if applicable, the associated mapping of the Configured NSSAI to HPLMN S-NSSAIs, so these can be configured in the UE. The NSSF shall return a Configured NSSAI when receiving Default Configured NSSAI Indication from the AMF. - If at least one S-NSSAI in the Requested NSSAI is not available in the current UE's Tracking Area, the NSSF may provide a Target NSSAI for the purpose of allowing the NG-RAN to redirect the UE to a cell of a TA in another frequency band supporting network slices not available in the current TA as described in clause 5.3.4.3.3. - The NSSF returns to the current AMF the Allowed NSSAI for the applicable Access Type, the mapping of each S-NSSAI of the Allowed NSSAI to the Subscribed S-NSSAIs if determined and the target AMF Set, or, based on configuration, the list of candidate AMF(s). The NSSF may return the NRF(s) to be used to select NFs/services within the selected Network Slice instance(s), and the NRF to be used to determine the list of candidate AMF(s) from the AMF Set. The NSSF may return NSI ID(s) to be associated to the Network Slice instance(s) corresponding to certain S-NSSAIs. NSSF may return the rejected S-NSSAI(s) as described in clause 5.15.4.1. The NSSF may return the Configured NSSAI for the Serving PLMN and the associated mapping of the Configured NSSAI to HPLMN S-NSSAIs. The NSSF may return Target NSSAI as described in clause 5.3.4.3.3. - Depending on the available information and based on configuration, the AMF may query the appropriate NRF (e.g. locally pre-configured or provided by the NSSF) with the target AMF Set. The NRF returns a list of candidate AMFs. - If AMF Re-allocation is necessary, the current AMF reroutes the Registration Request or forwards the UE context to a target serving AMF as described in clause 5.15.5.2.3. - Step (C) is executed. (C) The serving AMF shall determine a Registration Area such that all S-NSSAIs of the Allowed NSSAI for this Registration Area are available in all Tracking Areas of the Registration Area (and also considering other aspects as described in clause 5.3.2.3 and clause 5.3.4.3.3) and then return to the UE this Allowed NSSAI and the mapping of the Allowed NSSAI to the Subscribed S-NSSAIs if provided. The AMF may return the rejected S-NSSAI(s) as described in clause 5.15.4.1. NOTE 8: The S-NSSAIs in the Allowed NSSAI for Non-3GPP access are available homogeneously "in the PLMN" for the N3IWF case since a N3IWF providing access to a 5GC can be reached from any IP location. For other types of Non-3GPP access the S-NSSAIs in the Allowed NSSAI for Non-3GPP access can be not available homogeneously, for example different W-AGFs/TNGF(s) can be deployed in different locations and support different TAIs that support different network slices. When either no Requested NSSAI was included, or the mapping of the S-NSSAIs in Requested NSSAI to HPLMN S-NSSAIs is incorrect, or a Requested NSSAI is not considered valid in the PLMN and as such at least one S-NSSAI in the Requested NSSAI was rejected as not usable by the UE in the PLMN, or the UE indicated that the Requested NSSAI is based on the Default Configured NSSAI, the AMF may update the UE slice configuration information for the PLMN as described in clause 5.15.4.2. If the Requested NSSAI does not include S-NSSAIs which map to S-NSSAIs of the HPLMN subject to Network Slice-Specific Authentication and Authorization and the AMF determines that no S-NSSAI can be provided in the Allowed NSSAI for the UE in the current UE's Tracking Area and if no default S-NSSAI(s) could be added as described in step (A), the AMF shall reject the UE Registration and shall include in the rejection message the list of Rejected S-NSSAIs, each of them with the appropriate rejection cause value. If the Requested NSSAI includes S-NSSAIs which map to S-NSSAIs of the HPLMN subject to Network Slice-Specific Authentication and Authorization, the AMF shall include in the Registration Accept message an Allowed NSSAI containing only those S-NSSAIs that are not to be subject to Network Slice-Specific Authentication and Authorization and, based on the UE Context in AMF, those S-NSSAIs for which Network Slice-Specific Authentication and Authorization for at least one of the corresponding HPLMN S-NSSAIs succeeded previously regardless the Access Type, if any. The AMF shall also provide the list of Rejected S-NSSAIs, each of them with the appropriate rejection cause value. If the AMF determined the Target NSSAI or received a Target NSSAI from the NSSF, the AMF should provide the Target NSSAI to the PCF for retrieving a corresponding RFSP as described in clause 5.3.4.3.1 or, if the PCF is not deployed, the AMF should determine a corresponding RFSP based on local configuration. Then the AMF provides the Target NSSAI and the corresponding RFSP to the NG-RAN as described in clause 5.3.4.3.3. The S-NSSAIs which map to S-NSSAIs of the HPLMN subject to an ongoing Network Slice-Specific Authentication and Authorization shall be included in the Pending NSSAI and removed from Allowed NSSAI. The Pending NSSAI may contain a mapping of the S-NSSAI(s) for the Serving PLMN to the HPLMN S-NSSAIs, if applicable. The UE shall not include in the Requested NSSAI any of the S-NSSAIs from the Pending NSSAI the UE stores, regardless of the Access Type. If: - all the S-NSSAI(s) in the Requested NSSAI are still to be subject to Network Slice-Specific Authentication and Authorization; or - no Requested NSSAI was provided or none of the S-NSSAIs in the Requested NSSAI matches any of the Subscribed S-NSSAIs, and all the S-NSSAI(s) marked as default in the Subscribed S-NSSAIs are to be subject to Network Slice-Specific Authentication and Authorization; the AMF shall provide a "NSSAA to be performed" indicator and no Allowed NSSAI to the UE in the Registration Accept message. Upon receiving the Registration Accept message, the UE is registered in the PLMN but shall wait for the completion of the Network Slice-Specific Authentication and Authorization without attempting to use any service provided by the PLMN on any access, except e.g. emergency services (see TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]), until the UE receives an allowed NSSAI. Then, the AMF shall initiate the Network Slice-Specific Authentication and Authorization procedure as described in clause 5.15.10 for each S-NSSAI that requires it, except, based on Network policies, for those S-NSSAIs for which Network Slice-Specific Authentication and Authorization have been already initiated on another Access Type for the same S-NSSAI(s). At the end of the Network Slice-Specific Authentication and Authorization steps, the AMF by means of the UE Configuration Update procedure shall provide a new Allowed NSSAI to the UE which also contains the S-NSSAIs subject to Network Slice-Specific Authentication and Authorization for which the authentication and authorization is successful. The AMF may perform AMF selection when NSSAA completes for the S-NSSAIs subject to NSSAA. If an AMF change is required, this shall be triggered by the AMF using the UE Configuration Update procedure indicating a UE re-registration is required. The S-NSSAIs which were not successfully authenticated and authorized are not included in the Allowed NSSAI and are included in the list of Rejected S-NSSAIs with a rejection cause value indicating Network Slice-Specific Authentication and Authorization failure. Once completed the Network Slice-Specific (re-)Authentication and (re-)Authorization procedure, if the AMF determines that no S-NSSAI can be provided in the Allowed NSSAI for the UE, which is already authenticated and authorized successfully by a PLMN, and if no default S-NSSAI(s) could be added as described in step (A), the AMF shall execute the Network-initiated Deregistration procedure described in clause 4.2.2.3.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] and shall include in the explicit De-Registration Request message the list of Rejected S-NSSAIs, each of them with the appropriate rejection cause value. If an S-NSSAI is rejected with a rejection cause value indicating Network Slice-Specific Authentication and Authorization failure or revocation, the UE can re-attempt to request the S-NSSAI based on policy, local in the UE.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.15.5.2.1

8.1.2.6.1 Applicability rule and antenna connection for single carrier tests with 2Rx

For 4Rx capable UEs all single carrier tests specified in 8.2 to 8.8 with 2Rx are tested on any of the 2 Rx supported RF bands by connecting 2 out of the 4Rx with data source from system simulator, and the other 2 Rx are connected with zero input, depending on UE’s declaration and AP configuration. Same requirements specified with 2Rx should be applied. For 4Rx capable UEs without any 2Rx RF bands, all single carrier tests specified in 8.2 to 8.8 with 2Rx are tested on any of the 4Rx supported RF bands by duplicating the fading channel from each Tx antenna and add independent noise for each Rx antenna. Figure 8.1.2.6.1-1 shows an example of antenna connection for 4Rx UE in any one 4Rx supported RF band to perform a 2Rx performance test with antenna configuration as 2x2 without interference for information. The SNR requirements should be applied with 1.5 dB less than the number specified with 2Rx for test configuration with CRS-based TM and with 1.5 dB less than the number specified with 2Rx for test configuration with DMRS-based TM. Figure 8.1.2.6.1-1 Antenna connection example for 2Rx tests with antenna configuration as 2x2 without interference (informative) For 4Rx capable UEs without any 2Rx supported RF bands, for all single carrier tests listed in Table 8.1.2.6.1-0 specified from 8.2 to 8.8 with 2Rx can be skipped. Table 8.1.2.6.1-0: Requirement lists for 4Rx capable UEs For 4Rx capable UEs, if corresponding tests listed from the 4Rx test lists from Table 8.1.2.6.1-1 are tested, the test coverage can be considered fulfilled without executing the corresponding tests listed from the 2Rx test lists from Table 8.1.2.6.1-1. Table 8.1.2.6.1-1: Applicability rules for single carrier tests with 2Rx

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

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

Each gNB-DU serving a cell identified by a Cell Identity associated with a subset of PLMNs is connected to a gNB-CU via a single F1-C interface instance. Each F1-C interface instance is setup individually. F1-C interface instances terminating at gNB-DUs which share the same physical radio resources may share the same F1-C signalling transport resources. If this option is applied, - non-UE associated signalling is associated to an F1-C interface instance by allocating the corresponding Transaction ID from a value range associated to that F1-C interface instance. - node related, non-UE associated F1-C interface signalling may provide information destined for multiple logical nodes in a single F1AP procedure instance once the F1-C interface instance is setup. NOTE 1: If the Transaction ID corresponds to more than one interface instance, the respective F1AP message carries information destined for multiple logical nodes. - a UE associated signalling connection is associated to an F1-C interface instance by allocating values for the corresponding gNB-DU UE F1AP ID and gNB-CU UE F1AP ID so that they can be mapped to that interface instance. NOTE 2: One possible implementation is to partition the value ranges of the gNB-DU UE F1AP ID and gNB-CU UE F1AP ID and associate each value range with an F1-C interface instance. Interpreting the content of RRC MSG3 and other unciphered RRC message by the gNB-DU is supported. Content for System Information Broadcast is assumed to be coordinated among the sharing PLMNs. PLMN specific SIB1 content is controlled by the respective PLMN owner. Non PLMN specific content needs coordination to avoid contradicting indication by PLMN specific gNB-CUs. For Warning messages (SIB6, SIB7 and SIB8), if provided by more than one gNB-CU, warning message duplicates are identified by provision of the Message Number and the Serial Number by the gNB-CU and don’t trigger new broadcast or replace existing broadcast. Other coordination between gNB-CUs is ensured by appropriate implementation.

3GPP TS 38.401

NG-RAN; Architecture description

RAN3

3GPP Series : 38 , Radio technology beyond LTE

Annex

5.3.1 User notification procedure

The mobile terminating user notification procedure allows the network to notify a mobile station of any appropriate call-related event during the "active" state of a call. The procedure consists in the network sending a NOTIFY message to the mobile station. No state change occurs at any of the interface sides following the sending or the receipt of this message (but an appropriate indication may optionally be generated in the mobile station). The mobile originating notification procedure allows the mobile station to notify the remote user of any appropriate call-related event during the "active" state of a call by sending a NOTIFY message containing a notification indicator to the network; upon receipt of this message, the network sends a NOTIFY message containing the same notify indicator to the other user involved in the call. No state change occurs at any of the interface sides following the sending or the receipt of this message.

3GPP TS 24.008

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

CT WG1

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

5.3.1

K.2.1 Capability exchange

DS-TT and NW-TT indicate time synchronization information they support inside the Port management capabilities (see Table K.1-1). TSN AF and TSCTSF may determine the PTP functionalities supported by DS-TT and NW-TT by retrieving the following port management information or user plane node management information, respectively: - Supported PTP instance types; - Supported transport types; - Supported PTP delay mechanisms; - Grandmaster capability; - Supported PTP profiles; - Number of supported PTP instances. NOTE: If NW-TT or DS-TT do not indicate support for any of the PTP profiles and PTP instance types, then TSN AF or TSCTSF assume that the NW-TT or DS-TT only support acting as a PTP Relay instance with the gPTP GM connected on N6. If DS-TT and NW-TT support the PTP Relay instance type as defined by IEEE 802.1AS [104] then DS-TT and NW-TT shall include the IEEE 802.1AS [104] PTP profile in the "Supported PTP profiles" in PMIC and UMIC, respectively. The TSN AF or TSCTSF may retrieve the "Number of supported PTP instances" from NW-TT via UMIC and from DS-TT via PMIC.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

K.2.1

10.5.6.3.2 APN rate control parameters

The purpose of the APN rate control parameters container contents is to indicate the APN rate control parameters. The APN rate control parameters container contents are coded as shown in figure 10.5.136A/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.154A/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The APN rate control parameters container contents can be 1 octet long or 4 octets long. If the APN rate control parameters container contents is longer than 4 octets, the 5th octet and later octets are ignored. Figure 10.5.136A/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : APN rate control parameters Table 10.5.154A/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : APN rate control parameters

3GPP TS 24.008

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

CT WG1

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

10.5.6.3.2

5.1.3.2.1.3.3 5GMM-DEREGISTERED.LIMITED-SERVICE

The substate 5GMM-DEREGISTERED.LIMITED-SERVICE is chosen in the UE, when it is known that a selected cell for 3GPP access or TA for non-3GPP access is unable to provide normal service (e.g. the selected cell over 3GPP access is in a forbidden PLMN or SNPN or is in a forbidden tracking area or TA for non-3GPP access is forbidden) or the selected cell is a CAG cell for which none of CAG-ID(s) is authorized based on the "Allowed CAG list" in the entry of the "CAG information list" for the PLMN, or the selected cell is a non-CAG cell in a PLMN for which there exists an "indication that the UE is only allowed to access 5GS via CAG cells" in the entry of the "CAG information list" for the PLMN, or the selected cell is a CAG cell belonging to a PLMN and the "CAG information list" does not contain an entry for the PLMN.

3GPP TS 24.501

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

CT WG1

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

5.1.3.2.1.3.3

4.4.7 PCRF 4.4.7.1 General

PCRF is the policy and charging control element. PCRF functions are desbed in more detail in TS 23.203[ Policy and charging control architecture ] [6]. In non-roaming scenario, there is only a single PCRF in the HPLMN associated with one UE's IP-CAN session. The PCRF terminates the Rx interface and the Gx interface. In a roaming scenario with local breakout of traffic there may be two PCRFs associated with one UE's IP-CAN session: - H-PCRF that resides within the H-PLMN; - V-PCRF that resides within the V-PLMN.

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

6.1.2 Initiation of authentication and selection of authentication method

The initiation of the primary authentication is shown in Figure 6.1.2-1. Figure 6.1.2-1: Initiation of authentication procedure and selection of authentication method The SEAF may initiate an authentication with the UE during any procedure establishing a signalling connection with the UE, according to the SEAF's policy. The UE shall use SUCI or 5G-GUTI in the Registration Request. The SEAF shall invoke the Nausf_UEAuthentication service by sending a Nausf_UEAuthentication_Authenticate Request message to the AUSF whenever the SEAF wishes to initiate an authentication. The Nausf_UEAuthentication_Authenticate Request message shall contain either: - SUCI, as defined in the current specification, or - SUPI, as defined in TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The SEAF shall include the SUPI in the Nausf_UEAuthentication_Authenticate Request message in case the SEAF has a valid 5G-GUTI and re-authenticates the UE. Otherwise the SUCI is included in Nausf_UEAuthentication_Authenticate Request. SUPI/SUCI structure is part of stage 3 protocol design. The Nausf_UEAuthentication_Authenticate Request shall furthermore contain: - the serving network name, as defined in sub-clause 6.1.1.4 of the present document. NOTE 2: The local policy for the selection of the authentication method does not need to be on a per-UE basis, but can be the same for all UEs. The Nausf_UEAuthentication_Authenticate Request may furthermore contain: - Disaster Roaming service indication, as specified in TS 23.502[ Procedures for the 5G System (5GS) ] [8] clause 4.2.2.2. Upon receiving the Nausf_UEAuthentication_Authenticate Request message, the AUSF shall check that the requesting SEAF in the serving network is entitled to use the serving network name in the Nausf_UEAuthentication_Authenticate Request by comparing the serving network name with the expected serving network name. The AUSF shall store the received serving network name temporarily. If the serving network is not authorized to use the serving network name, the AUSF shall respond with "serving network not authorized" in the Nausf_UEAuthentication_Authenticate Response. NOTE 2: The AUSF and the UDM may be configured with Disaster Condition via OAM based on operator policy and the request by the government agencies. For the Disaster Roaming, the AUSF shall check the local configuration and, if allowed, the AUSF sends Nudm_UEAuthentication_Get Request to the UDM. The Nudm_UEAuthentication_Get Request sent from AUSF to UDM includes the following information: - SUCI or SUPI; - the serving network name; - if received from SEAF, Disaster Roaming service indication; Upon reception of the Nudm_UEAuthentication_Get Request, the UDM shall invoke SIDF if a SUCI is received. SIDF shall de-conceal SUCI to gain SUPI before UDM can process the request. Based on SUPI, the UDM/ARPF shall choose the authentication method. NOTE 3: The Nudm_UEAuthentication_Get Response in reply to the Nudm_UEAuthentication_Get Request and the Nausf_UEAuthentication_Authenticate Response message in reply to the Nausf_UEAuthentication_Authenticate Request message are described as part of the authentication procedures in clause 6.1.3. For the Disaster Roaming, the UDM shall check the local configuration and, if allowed, the UDM proceeds with the chosen authentication method.

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

6.1.2

A.13 Monitoring of Mobility Robustness Optimization (MRO)

The following measurement is defined specifically to monitor the performance of handover optimisation: - Number of handover failures for MRO. The measurement examines “handover related events” in which the serving cell of a RRC connected UE is changed. Handover related events are either normal successful handovers, or they are failures. Different failure modes are possible and the measurement provides counts for the occurrences of the failure modes related with MRO, “too early”, “too late” and “to wrong cell”. The detailed definitions of these modes are captured in [12]. The counters provide visibility of the mix of failure problems that the handover optimistion function is tackling. In “handover to wrong cell” case, an RLF occurs shortly after a successful handover from a source cell (cell A in Figure A.13-1) to a target cell (cell B in Figure A.13-1) or a HOF occurs during the handover procedure; the UE attempts to re-establish the radio link connection in a cell (Cell C in Figure A.13-1) other than the source cell and the target cell. (See 36.300 [12]). Figure A.13-1 Handover to wrong cell case For the “handover to wrong cell” case (ABC) above-mentioned, the handover parameters on Neighbour Relation AB, Neighbour Relation AC or both may be problematic and need to be corrected. So the performance measurements for both Neighbour Relation AB and Neighbour Relation AC are needed for problem detection. In addition to event-based (i.e. reactive) optimization of handover performance, a pro-active optimization is possible by monitoring the dynamics of handover triggering from UE measurement reports.

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

6.2 Message Granularity

The GTPv2-C messages shall be sent per UE on the S3, S10, S16 and N26 interfaces. The GTPv2-C messages shall be sent per PDN-Connection on the S2a, S2b, S4, S11, S5 and S8 interfaces apart from the following exclusion. The following GTPv2-C messages are sent per UE on the S4 and S11 interfaces: - Downlink Data Notification / Acknowledge / Failure Indication; - Stop Paging Indication; - Delete Indirect Data Forwarding Tunnel Request/Response; - Delete Session Request/Response with Scope Indication set to 1 during following procedures with SGW change: - Tracking Area Update procedure; - Routing Area Update procedure; - Handover procedure; - SRNS Relocation Cancel Using S4; - Inter RAT handover Cancel procedure; - S1 based handover cancel procedure; - Delete Bearer Request/Response during a TAU/RAU/Handover procedure if the Cause value "ISR deactivation" is included in the Delete Session Request message, or when it is sent to delete the bearer resources on the other ISR associated CN node if the ISRAI flag is not set in the Modify Bearer Request/Modify Access Bearers Request message. - Release Access Bearers Request/Response; - Create Indirect Data Forwarding Tunnel Request/Response; - Trace Session Activation; - Trace Session Deactivation; - Create Forwarding Tunnel Request/Response. The following GTPv2-C messages are sent per UE on the S11 interface: - Modify Access Bearers Request/Response. The following GTPv2-C messages are sent per GTP-C entity on the S2a, S2b, S5, S8, and S11 interfaces: - Delete PDN Connection Set Request/Response. The following GTPv2-C messages are sent per GTP-C entity on the S5 and S8 interfaces: - Update PDN Connection Set Request/Response. The following GTPv2-C messages are sent per GTP-C entity on the S4 and S11 interfaces: - PGW Restart Notification/Acknowledge. The following GTPv2-C path management messages are sent per GTP-C entity on all GTPv2-C interfaces: - Echo Request/Response; - Version Not Supported Indication.

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

6.2

6.3.12.2 Access Network Selection Procedure

The steps below specify the steps executed by the UE when the UE wants to select and connect to a PLMN over trusted non-3GPP access. Note that the UE executes these steps before connecting to a trusted non-3GPP access network. This is different from the untrusted non-3GPP access (see clause 6.3.6, "N3IWF selection"), where the UE first connects to a non-3GPP access network, it obtains IP configuration and then proceeds to PLMN selection and ePDG/N3IWF selection. In the case of trusted non-3GPP access, the UE uses 3GPP-based authentication for connecting to a non-3GPP access, so it must first select a PLMN and then attempt to connect to a non-3GPP access. Step 1: The UE constructs a list of available PLMNs, with which trusted connectivity is supported. This list contains the PLMNs included in the PLMN List-2 and PLMN List-3, advertised by all discovered non-3GPP access networks. For each PLMN the supported type(s) of trusted connectivity is also included. a. In the example shown in Figure 6.3.12.1-1, the list of available PLMNs includes: - PLMN-a: "S2a connectivity", "5G connectivity" - PLMN-b: "5G connectivity" - PLMN-c: "S2a connectivity", "5G connectivity" - PLMN-d: "S2a connectivity" Step 2: The UE selects a PLMN that is included in the list of available PLMNs, as follows: a. If the UE is connected to a PLMN via 3GPP access and this PLMN is included in the list of available PLMNs, the UE selects this PLMN. If this PLMN is not included in the list of available PLMNs, but it is included in the "Non-3GPP access node selection information" in the UE (see clause 6.3.6.1), the UE selects this PLMN and executes the combined ePDG/N3IWF selection procedure specified in clause 6.3.6.3. b. Otherwise (the UE is not connected to a PLMN via 3GPP access, or the UE is connected to a PLMN via 3GPP access but this PLMN is neither in the list of available PLMNs nor in the "Non-3GPP access node selection information"), the UE determines the country it is located in by using implementation specific means. i) If the UE determines to be located in its home country, then: - The UE selects the HPLMN, if included in the list of available PLMNs. Otherwise, the UE selects an E-HPLMN (Equivalent HPLMN), if an E-HPLMN is included in the list of available PLMNs. If the list of available PLMNs does not include the HPLMN and does not include an E-HPLMN, the UE stops the procedure and may attempt to connect via untrusted non-3GPP access (i.e. it may execute the N3IWF selection procedure specified in clause 6.3.6). ii) If the UE determines to be located in a visited country, then: - The UE determines if it is mandatory to select a PLMN in the visited country, as follows: - If the UE has IP connectivity (e.g. the UE is connected via 3GPP access), the UE sends a DNS query and receives a DNS response that indicates if a PLMN must be selected in the visited country. The DNS response includes also a lifetime that denotes how long the DNS response can be cached for. The FQDN in the DNS query shall be different from the Visited Country FQDN (see TS 23.003[ Numbering, addressing and identification ] [19]) that is used for ePDG/N3IWF selection. The DNS response shall not include a list of PLMNs that support trusted connectivity in the visited country, but shall only include an indication of whether a PLMN must be selected in the visited country or not. - If the UE has no IP connectivity (e.g. the UE is not connected via 3GPP access), then the UE may use a cached DNS response that was received in the past, or may use local configuration that indicates which visited countries mandate a PLMN selection in the visited country. - If the UE determines that it is not mandatory to select a PLMN in the visited country, and the HPLMN or an E-HPLMN is included in the list of available PLMNs, then the UE selects the HPLMN or an E-HPLMN, whichever is included in the list of available PLMNs. - Otherwise, the UE selects a PLMN in the visited country by considering, in priority order, the PLMNs, first, in the User Controlled PLMN Selector list and, next, in the Operator Controlled PLMN Selector list (see TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [17]). The UE selects the highest priority PLMN in a PLMN Selector list that is also included in the list of available PLMNs; - If the list of available PLMNs does not include a PLMN that is also included in a PLMN Selector list, the UE stops the procedure and may attempt to connect via untrusted non-3GPP access. c. In the example shown in Figure 6.3.12.1-1, the UE may select PLMN-c, for which "S2a connectivity" and "5G connectivity" is supported. Step 3: The UE selects the type of trusted connectivity ("S2a connectivity" or "5G connectivity") for connecting to the selected PLMN, as follows: a. If the list of available PLMNs indicates that both "S2a connectivity" and "5G connectivity" is supported for the selected PLMN, then the UE shall select "5G connectivity" because it is the preferred type of trusted access. b. Otherwise, if the list of available PLMNs indicates that only one type of trusted connectivity (either "S2a connectivity" or "5G connectivity") is supported for the selected PLMN, the UE selects this type of trusted connectivity. c. In the example shown in Figure 6.3.12.1-1, the UE may select PLMN-c and "5G connectivity". There are two non-3GPP access networks that support "5G connectivity" to PLMN-c: the WLAN access network 2 and the WLAN access network 4. Step 4: Finally, the UE selects a non-3GPP access network to connect to, as follows: a. The UE puts the available non-3GPP access networks in priority order. For WLAN access, the UE constructs a prioritized list of WLAN access networks by using the WLANSP rules (if provided) and the procedure specified in clause 6.6.1.3 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. When the UE supports the selection of Trusted access supporting the network slices it desires to use and has received extended WLANSP rule as specified in clause 6.6.1.1 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45], the UE selects the non-3GPP access network with the SSID(s) which can access to the TNGF supporting the S-NSSAI needed by the UE. If the UE is not provided with WLANSP rules, the UE constructs the prioritized list of WLAN access networks by using an implementation specific procedure. For other types of non-3GPP access, the UE may use access specific information to construct this prioritized list. b. From the prioritized list of non-3GPP access networks, the UE selects the highest priority non-3GPP access network that supports the selected type of trusted connectivity to the selected PLMN. c. In the example shown in Figure 6.3.12.1-1, the UE selects either the WLAN access network 2 or the WLAN access network 4, whichever has the highest priority in the prioritized list of non-3GPP access networks. d. Over the selected non-3GPP access network, the UE starts the 5GC registration procedure specified in clause 4.12a.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. e. If the AMF detects the UE is using a wrong TNGF, the AMF may trigger a UE policy update and reject the UE registration During the registration procedure the AMF may determine if the TNGF selected by the UE is suitable for the S-NSSAI(s) requested by the UE considering the UE subscription. If the AMF determines that a different TNGF should be selected as described in clause 4.12a.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3], the AMF: - may, if the UE supports slice-based TNGF selection, triggers the UE Policy Association Establishment or UE Policy Association Update procedure to provide the UE with updated TNGF selection information as described in clause 6.15.2.1; when the AMF is informed by the PCF that the update of UE policy information on the UE is completed as described in clause 4.12a.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3], the AMF releases UE Policy Association if the UE is not registered over 3GPP access before proceeding to the Registration Reject over trusted non-3GPP access; NOTE 1: To enable the V-PCF to provide the UE with Slice-specific TNGF selection information in the roaming case, the AMF provides the V-PCF with the Configured NSSAI for the serving PLMN during the UE Policy Association Establishment/Update procedure. - shall send a Registration Reject message to the UE. The AMF may include target TNAN information (SSID, TNGF ID) in the Registration Reject so that the UE can, if supported by the UE, use the target TNAN information to try again to register to 5GC if the UE wishes to send the same Requested NSSAI as during the previous Registration Request. The target TNAN information only applies to the one TNAN selection performed by the UE just after receiving the Registration Reject. The AMF may determine the target TNAN based on the list of supported TAs and the corresponding list of supported slices for each TA obtained as defined in clause 5.15.8, and considering UE location. NOTE 2: The operator is assumed to ensure that UEs that do not support slice-based TNGF selection always select a TNGF that supports at least one slice requested by the UE. This is to avoid unnecessary and potentially repetitive rejections of those UEs. To ensure this, the operator is assumed to provide identifiers of TNGFs that only support a subset of the slices configured in the network only to UEs that support slice-based TNGF selection.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

6.3.12.2

9.3.21 Retrieve Acknowledge

This message is sent by the network to indicate that the retrieve function has been successfully performed. See table 9.69c/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] for the content of the RETRIEVE ACKNOWLEDGE message. For the use of this message, see 3GPP TS 24.010[ Mobile radio interface layer 3; Supplementary services specification; General aspects ] [21]. Message type: RETRIEVE ACKNOWLEDGE Significance: local Direction: network to mobile station Table 9.69c/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : RETRIEVE ACKNOWLEDGE message content

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