Datasets:

Exploration-Lab

/

MM-TelecoBench

like 0

Follow

Exploration Lab 61

4.6 Radio Access Network Sharing

NG-RAN supports radio access network sharing as defined in TS 23.501[ System architecture for the 5G System (5GS) ] [3]. If NR access is shared, system information broadcast in a shared cell indicates a TAC and a Cell Identity for each subset of PLMNs, PNI-NPNs and SNPNs. NR access provides only one TAC and one Cell Identity per cell per PLMN, SNPN or PNI-NPN. In this version of the specification, a Cell Identity can only belong to one network type among PLMN, PNI-NPN or SNPN as defined in TS 23.501[ System architecture for the 5G System (5GS) ] [3]. Each Cell Identity associated with a subset of PLMNs, SNPNs or PNI-NPNs identifies its serving NG-RAN node.

3GPP TS 38.300

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

RAN2

3GPP Series : 38 , Radio technology beyond LTE

4.6

16.3 Network slice specific authentication and authorization

This clause specifies the optional-to-use NSSAA between a UE and an AAA server (AAA-S) which may be owned by an external 3rd party enterprise. NSSAA uses a User ID and credentials, different from the 3GPP subscription credentials (e.g. SUPI and credentials used for PLMN access) and takes place after the primary authentication. The EAP framework specified in RFC 3748 [27] shall be used for NSSAA between the UE and the AAA server. The SEAF/AMF shall perform the role of the EAP Authenticator and communicates with the AAA-S via the NSSAAF. The NSSAAF undertakes any AAA protocol interworking with the AAA-S. Multiple EAP methods are possible for NSSAA. If the AAA-S belongs to a third party the NSSAAF contacts the AAA-S via a AAA-P. The NSSAAF and the AAA-P may be co-located. To protect privacy of the EAP ID used for the EAP based NSSAA, a privacy-protection capable EAP method is recommended, if privacy protection is required. The steps involved in NSSAA are described below. Figure 16.3-1: NSSAA procedure 1. For S-NSSAIs that are requiring NSSAA, based on change of subscription information, or triggered by the AAA-S, the AMF may trigger the start of the NSSAA procedure. If NSSAA is triggered as a result of Registration procedure, the AMF may determine, based on UE Context in the AMF, that for some or all S-NSSAI(s) subject to NSSAA, the UE has already been authenticated following a Registration procedure on a first access. Depending on NSSAA result (e.g. success/failure) from the previous Registration, the AMF may decide, based on Network policies, to skip NSSAA for these S-NSSAIs during the Registration on a second access. If the NSSAA procedure corresponds to a re-authentication and re-authorization procedure triggered as a result of AAA Server-triggered UE re-authentication and re-authorization for one or more S-NSSAIs, as described in clause 16.4, or triggered by the AMF based on operator policy or a subscription change and if S-NSSAIs that are requiring Network Slice-Specific Authentication and Authorization are included in the Allowed NSSAI for each Access Type, the AMF selects an Access Type to be used to perform the NSSAA procedure based on network policies. 2. The AMF may request the UE User ID for EAP authentication (EAP ID) for the S-NSSAI in a NAS MM Transport message including the S-NSSAI. 3. The UE provides the EAP ID for the S-NSSAI alongside the S-NSSAI in an NAS MM Transport message towards the AMF. 4. The AMF sends the EAP ID to the NSSAAF which provides interface with the AAA, in an Nnssaaf_NSSAA_Authenticate Request (EAP ID Response, GPSI, S-NSSAI). 5. If the AAA-P is present (e.g. because the AAA-S belongs to a third party and the operator deploys a proxy towards third parties), the NSSAAF forwards the EAP ID Response message to the AAA-P, otherwise the NSSAAF forwards the message directly to the AAA-S. NSSAAF routes to the AAA-S based on the S-NSSAI. The NSSAAF/AAA-P forwards the EAP Identity message to the AAA-S together with S-NSSAI and GPSI. The AAA-S stores the GPSI to create an association with the EAP ID in the EAP ID response message so the AAA-S can later use it to revoke authorisation or to trigger reauthentication. The AAA-S uses the EAP-ID and S-NSSAI to identify for which UE and slice authorisation is requested. NOTE : If the AAA-S belongs to the 3rd party, the NSSAAF optionally maps the S-NSSAI to External Network Slice Information (ENSI), and forwards the EAP Identity message to the AAA-S together with ENSI and GPSI. In this case, the AAA-S uses the EAP-ID and ENSI to identify the UE for which slice authorisation is requested. 6 -11. EAP-messages are exchanged with the UE. One or more than one iterations of these steps may occur. 12. EAP authentication completes. An EAP-Success/Failure message is delivered to the NSSAAF/AAA-P along with GPSI and S-NSSAI/ENSI. 13. The NSSAAF sends the Nnssaaf_NSSAA_Authenticate Response (EAP-Success/Failure, S-NSSAI, GPSI) to the AMF. 14. The AMF transmits a NAS MM Transport message (EAP-Success/Failure) to the UE. 15. Based on the result of Slice specific authentication (EAP-Success/Failure), if a new Allowed NSSAI or new Rejected NSSAIs needs to be delivered to the UE, or if the AMF re-allocation is required, the AMF initiates the UE Configuration Update procedure, for each Access Type, as described in clause 4.2.4.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [8]. If the NSSAA procedure can not be completed (e.g. due to server error or UE becoming unreachable), the AMF sets the status of the corresponding S-NSSAI subject to Network Slice-Specific Authentication and Authorization in the UE context as defined in TS 29.526[ 5G System; Network Slice-Specific and SNPN Authentication and Authorization services; Stage 3 ] [96], so that an NSSAA is executed next time the UE requests to register with the S-NSSAI.

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

16.3

5.5 Usage of the GTPv2-C Header 5.5.1 General

The format of the GTPv2-C header is specified in clause 5.1 "General format". The usage of the GTP-C header across e.g. S101/S121 (3GPP TS 29.276[ 3GPP Evolved Packet System (EPS); Optimized handover procedures and protocols between E-UTRAN access and cdma2000 HRPD Access; Stage 3 ] [14]) and Sv (3GPP TS 29.280[ Evolved Packet System (EPS); 3GPP Sv interface (MME to MSC, and SGSN to MSC) for SRVCC ] [15]) interfaces are defined in their respective specifications. The usage of the GTPv2-C header for EPC specific interfaces shall be as defined below. The first octet of the header shall be used is the following way: - Bits 8 to 6, which represent the GTP-C version, shall be set to decimal 2 ("010"). - Bit 5 represents a "P" flag. If the "P" flag is set to "0", no piggybacked message shall be present. If the "P" flag is set to "1", then another GTPv2-C message with its own header and body shall be present at the end of the current message. When present, a piggybacked message shall have its "P" flag set to "0" in its own header. If a Create Session Response message (as part of EUTRAN initial attach, a Handover from Trusted or Untrusted Non-3GPP IP Access to E-UTRAN (see clauses 8.6 and 16.11 of 3GPP TS 23.402[ Architecture enhancements for non-3GPP accesses ] [45]) or UE-requested PDN connectivity procedure) has the "P" flag set to "1", then a single Create Bearer Request message shall be present as the piggybacked message. As a response to the Create Bearer Request message, if the Create Bearer Response has the "P" flag set to "1", then a single Modify Bearer Request (as part of EUTRAN initial attach, a Handover from Trusted or Untrusted Non-3GPP IP Access to E-UTRAN (see clauses 8.6 and 16.11 of 3GPP TS 23.402[ Architecture enhancements for non-3GPP accesses ] [45]) or UE-requested PDN connectivity procedure) shall be present as the piggybacked message. A Create Bearer Response with "P" flag set to "1" shall not be sent unless a Create Session Response with "P" flag set to "1" has been received for the same procedure. Apart from Create Session Response and Create Bearer Response messages, all the EPC specific messages shall have the "P" flag set to "0". - Bit 4 represents a "T" flag, which indicates if TEID field is present in the GTP-C header or not. If the "T" flag is set to 0, then the TEID field shall not be present in the GTP-C header. If the "T" flag is set to 1, then the TEID field shall immediately follow the Length field, in octets 5 to 8. Apart from the Echo Request, Echo Response and Version Not Supported Indication messages, in all EPC specific messages the value of the "T" flag shall be set to "1". - Bit 3 represents a "MP" flag. If the "MP" flag is set to "1", then bits 8 to 5 of octet 12 shall indicate the message priority. - Bit 2 is a spare bit. The sending entity shall set it to "0" and the receiving entity shall ignore it. - Bit 1 is a spare bit. The sending entity shall set it to "0" and the receiving entity shall ignore it. The usage of the fields in octets 2 - n of the header shall be as specified below. - Octet 2 represents the Message type field, which shall be set to the unique value for each type of control plane message. Message type values are specified in Table 6.1-1 "Message types for GTPv2". - Octets 3 to 4 represent the Message Length field. This field shall indicate the length of the message in octets excluding the mandatory part of the GTP-C header (the first 4 octets). The TEID (if present) and the Sequence Number shall be included in the length count. The format of the Length field of information elements is specified in clause 8.2 "Information Element Format". - A piggybacked initial message and the preceding triggered response message present in the common IP/UDP packet shall have their own length and sequence number in their respective GTP-C headers. The overall length of the IP/UDP packet shall indicate the total length of the two GTP-C messages. - For EPC specific interfaces, T=1, and therefore octets 5 to 8 represent the Tunnel Endpoint Identifier (TEID) field. This field shall unambiguously identify a tunnel endpoint in the receiving GTP-C entity. The Tunnel Endpoint Identifier is set by the sending entity in the GTP header of all control plane messages to the TEID value provided by the corresponding receiving entity (see clause 4.1). If a peer's TEID is not available the TEID field shall be present in a GTPv2-C header, but its value shall be set to "0", as specified in clause 5.5.2 "Conditions for sending TEID=0 in GTPv2-C header". NOTE: The TEID in the GTP header of a Triggered (or Triggered Reply) message is set to the TEID value provided by the corresponding receiving entity regardless of whether the source IP address of the Initial (or Triggered) message and the IP Destination Address provided by the receiving entity for subsequent control plane Initial messages (see clause 4.2.2.1) are the same or not. - Octets 9 to 11 represent GTP Sequence Number field. - Bits 8 to 5 of octet 12 shall indicate the relative priority of the GTP-C message, if the "MP" flag is set to 1 in Octet 1. It shall be encoded as the binary value of the Message Priority and it may take any value between 0 and 15, where 0 corresponds to the highest priority and 15 the lowest priority. If the "MP" flag is set to "0" in Octet 1, bits 8 to 5 of octet 12 shall be set to "0" by the sending entity and ignored by the receiving entity. - Bits 4 to 1 of octet 12 are spare bits. The sending entity shall set them to "0" and the receiving entity shall ignore them.

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

5.5

5.3.7.4 Actions related to transmission of RRCReestablishmentRequest message

The UE shall set the contents of RRCReestablishmentRequest message as follows: 1> if the procedure was initiated due to radio link failure as specified in 5.3.10.3 or reconfiguration with sync failure as specified in 5.3.5.8.3; or 1> if the procedure was initiated due to mobility from NR failure as specified in 5.4.3.5 and if voiceFallbackIndication is included in the MobilityFromNRCommand message: 2> set the reestablishmentCellId in the VarRLF-Report to the global cell identity of the selected cell; 1> set the ue-Identity as follows: 2> set the c-RNTI to the C-RNTI used in the source PCell (reconfiguration with sync or mobility from NR failure) or used in the PCell in which the trigger for the re-establishment occurred (other cases); 2> set the physCellId to the physical cell identity of the source PCell (reconfiguration with sync or mobility from NR failure) or of the PCell in which the trigger for the re-establishment occurred (other cases); 2> set the shortMAC-I to the 16 least significant bits of the MAC-I calculated: 3> over the ASN.1 encoded as per clause 8 (i.e., a multiple of 8 bits) VarShortMAC-Input; 3> with the KRRCint key and integrity protection algorithm that was used in the source PCell (reconfiguration with sync or mobility from NR failure) or of the PCell in which the trigger for the re-establishment occurred (other cases); and 3> with all input bits for COUNT, BEARER and DIRECTION set to binary ones; 1> set the reestablishmentCause as follows: 2> if the re-establishment procedure was initiated due to reconfiguration failure as specified in 5.3.5.8.2: 3> set the reestablishmentCause to the value reconfigurationFailure; 2> else if the re-establishment procedure was initiated due to reconfiguration with sync failure as specified in 5.3.5.8.3 (intra-NR handover failure) or 5.4.3.5 (inter-RAT mobility from NR failure): 3> set the reestablishmentCause to the value handoverFailure; 2> else: 3> set the reestablishmentCause to the value otherFailure; 1> re-establish PDCP for SRB1; 1> if the UE is acting as L2 U2N Remote UE: 2> establish or re-establish (e.g. via release and add) SL RLC entity for SRB1; 2> apply the default configuration of SL-RLC1 as defined in 9.2.4 for SRB1; 2> apply the default configuration of PDCP as defined in 9.2.1 for SRB1; 2> apply the default configuration of SRAP as defined in 9.2.5 for SRB1; 1> else: 2> re-establish RLC for SRB1; 2> apply the default configuration defined in 9.2.1 for SRB1; 1> configure lower layers to suspend integrity protection and ciphering for SRB1; NOTE: Ciphering is not applied for the subsequent RRCReestablishment message used to resume the connection. An integrity check is performed by lower layers, but merely upon request from RRC. 1> resume SRB1; 1> if ta-Report or ta-ReportATG is configured with value enabled and the UE supports TA reporting: 2> indicate TA report initiation to lower layers; 1> submit the RRCReestablishmentRequest 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.3.7.4

4.5.11 Distribution of UL total PRB usage

a) This measurement provides the distribution of samples with total usage (in percentage) of physical resource blocks (PRBs) on the uplink in different usage ranges. This measurement is a useful measure of whether a cell is under high loads or not in the scenario which a cell in the uplink may experience high load in certain short times (e.g. in a second) and recover to normal very quickly. b) CC c) Each measurememt sample is obtained according to the definition in TS 36.314[ Evolved Universal Terrestrial Radio Access (E-UTRA); Layer 2 - Measurements ] [11] clause 4.1.10.1. Depending on the value of the sample, the proper bin of the counter is increased. The number of samples during one measurement period is provided by the operator. d) A set of integers, each representing the (integer) number of samples with a UL PRB percentage usage in the range represented by that bin. e) RRU.PrbTotUlDist.BinX, which indicates the distribution of UL PRB Usage for all traffic. f) EUtranCellFDD EUtranCellTDD g) Valid for packet switched traffic h) EPS i) The distribution information is a key input to network capacity planning and load balancing.

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

9.11.3.94 TNAN information

The purpose of the TNAN information information element is to enable the network to assign the UE, a suitable TNAN information (SSID and TNGF identifier) for the requested NSSAI. The TNAN information information element is coded as shown in figure 9.11.3.94.1 and table 9.11.3.94.1. The TNAN information information element is a type 4 information element with a minimum length of 3 octets. Figure 9.11.3.94.1: TNAN information information element Table 9.11.3.94.1: TNAN information information element

3GPP TS 24.501

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

CT WG1

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

9.11.3.94

– SL-BWP-DiscPoolConfig

The IE SL-BWP-DiscPoolConfig is used to configure UE specific NR sidelink discovery dedicated resource pool. SL-BWP-DiscPoolConfig information element -- ASN1START -- TAG-SL-BWP-DISCPOOLCONFIG-START SL-BWP-DiscPoolConfig-r17 ::= SEQUENCE { sl-DiscRxPool-r17 SEQUENCE (SIZE (1..maxNrofRXPool-r16)) OF SL-ResourcePool-r16 OPTIONAL, -- Cond HO sl-DiscTxPoolSelected-r17 SL-TxPoolDedicated-r16 OPTIONAL, -- Need M sl-DiscTxPoolScheduling-r17 SL-TxPoolDedicated-r16 OPTIONAL -- Need N } -- TAG-SL-BWP-DISCPOOLCONFIG-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

– LBT-FailureRecoveryConfig

The IE LBT-FailureRecoveryConfig-r16 is used to configure the parameters used for detection of consistent uplink LBT failures for operation with shared spectrum channel access, as specified in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3]. LBT-FailureRecoveryConfig information element -- ASN1START -- TAG-LBT-FAILURERECOVERYCONFIG-START LBT-FailureRecoveryConfig-r16 ::= SEQUENCE { lbt-FailureInstanceMaxCount-r16 ENUMERATED {n4, n8, n16, n32, n64, n128}, lbt-FailureDetectionTimer-r16 ENUMERATED {ms10, ms20, ms40, ms80, ms160, ms320}, ... } -- TAG-LBT-FAILURERECOVERYCONFIG-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

10.5.4.16 High layer compatibility

The purpose of the high layer compatibility information element is to provide a means which should be used by the remote user for compatibility checking. See annex B. The high layer compatibility information element is coded as shown in figure 10.5.102/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.125/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The high layer compatibility is a type 4 information element with a minimum length of 2 octets and a maximum length of 5 octets. NOTE: The high layer compatibility information element is transported transparently by a PLMN between a call originating entity (e.g. a calling user) and the addressed entity (e.g. a remote user or a high layer function network node addressed by the call originating entity). However, if explicitly requested by the user (at subscription time), a network which provides some capabilities to realize teleservices may interpret this information to provide a particular service. Figure 10.5.102/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] High layer compatibility information element If the value part of the IE is empty, the IE indicates "not applicable". NOTE: Octet 4a may be present e.g. when octet 4 indicates Maintenance or Management, or audio visual. Table 10.5.125/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : High layer compatibility information element

3GPP TS 24.008

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

CT WG1

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

10.5.4.16

6.2.12 UDSF

The UDSF is an optional function that supports the following functionality: - Storage and retrieval of information as unstructured data by any NF. Notify a NF consumer if information validity has expired. - Timer service to any NF. NOTE 1: Structured data in this specification refers to data for which the structure is defined in 3GPP specifications. Unstructured data refers to data for which the structure is not defined in 3GPP specifications. NOTE 2: Deployments can choose to collocate UDSF with UDR.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

6.2.12

4.13.8.2.2 group-level N4 session management procedures

The SMF shall create an group-level N4 session on the UPF for a 5G VN group when N19-based forwarding is applied. The group-level N4 Session management procedures enable the SMF to create, update or delete the group-level N4 Session, e.g. add or delete N4 rules, allocate or release the N19 tunnel resources. In the case of N19-based forwarding is applied, the followings apply for the PDU Sessions targeting the (DNN, S-NSSAI) associated with a 5G VN group: - If the PDU Sessions targeting the same 5G VN group are anchored at different UPFs, the SMF shall create the group-level N4 Session in each involved UPF via N4 Session Establishment procedure (clause 4.4.1.2) in order to establish N19 tunnel(s) between the UPFs and install the N4 rules. - If the last PDU Session for this 5G VN group is released on a UPF, the SMF may delete the group-level N4 Session in the UPF via N4 Session Release procedure (clause 4.4.1.4) and release the N19 tunnel(s) between this UPF and other UPF(s) serving the 5G VN group via update of the corresponding N4 rules. - If an address of the UE within the 5G VN group is allocated or released, the SMF may update the N4 rules(e.g. PDRs and FARs) related to the UE address into the group-level N4 Session context via N4 Session Modification procedure (clause 4.4.1.3).

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.13.8.2.2

15.5.1.5 Load reporting for inter-system load balancing

The load reporting function for inter-system load balancing is executed by exchanging load information between NG-RAN and E-UTRAN. Both event-triggered and periodic inter-system load reporting are supported. Event-triggered inter-system load reports are sent when the reporting node detects crossing of cell load thresholds. The following load related information should be supported: - Cell Capacity Class value (UL/DL relative capacity indicator); - Capacity value (per cell: UL/DL available capacity); - RRC connections (number of RRC connections, and available RRC Connection Capacity); - Number of active UEs; - Radio Resource Status (per cell PRB usage: UL/DL GBR PRB usage for MIMO, DL/UL non-GBR PRB usage for MIMO, DL/UL total PRB usage for MIMO). NGAP procedures used for inter-system load balancing are Uplink RAN Configuration Transfer and Downlink RAN Configuration Transfer. S1AP procedures used for inter-system load balancing are eNB Configuration Transfer and MME Configuration Transfer.

3GPP TS 38.300

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

RAN2

3GPP Series : 38 , Radio technology beyond LTE

15.5.1.5

F.5 5GS DetNet node information reporting

The TSCTSF collects the information for Deterministic Networking from the UPF/NW-TT and the SMF as shown in Figure F.5-1, with the addition of new parameters as shown in Figure F.5-1. Figure F.5-1: 5GS DetNet node information reporting 1. PDU Session Establishment as defined clause 4.3.2.2.1-1 is used to establish a PDU Session. When Framed Routes applies, the SMF reports to the PCF Framed Route information. 2. SMF reports device port related information to PCF. When prefix delegation applies, the SMF reports to the PCF prefixes delegated to the UE by IPv6 prefix delegation. The PCF notifies TSCTSF of the Bridge/Router information. The TSCTSF subscribes for notifications on the Bridge/Router information and also subscribes for notifications on Reporting of extra addresses, so that the TSCTSF is notified when the SMF has reported to the PCF the Framed Route information or prefixes delegated to UE via IPv6 prefix delegation corresponding to the PDU Session. 3-4. Using the 5GS user-plane Node ID received in step 2b the TSCTSF can subscribe with the NW-TT for receiving user plane node management information changes for the 5GS router indicated by the 5GS user-plane Node ID in case it does not yet have such a subscription, as described in clause 5.28.3.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. After receiving a User plane node Management Information Container (UMIC) containing the NW-TT port numbers, the TSCTSF can subscribe with the NW-TT for receiving NW-TT port management information changes for the NW-TT port indicated by each of the NW-TT port numbers as described in clause 5.28.3.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The TSCTSF can use any PDU Session to subscribe with the NW-TT for node or port management information notifications. Similarly, the UPF can use any PDU Session to send bridge or port management information notifications. 5. The TSCTSF may provide collected exposure information to the DetNet controller. The information being reported to the DetNet controller is defined in clause 5.28.5.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2].

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

F.5

14.3.2 Exceptional scenarios

During a dedicated bearer creation procedure, temporary Bearer Context mismatch may occur at the SGW, e.g. due to the collision between Create Bearer Request and Modify (Access) Bearer Request messages. Applying the general requirements of clause 14.3.1 may in such case lead to unnecessary signalling and cause extra latency. The SGW should handle such Bearer Context mismatch in an implementation specific way, but in such a way to accept the Modify (Access) Bearer Request message and to not locally delete the missing Bearer Context. During a Network Triggered Service Request procedure, which is triggered by a dedicated bearer creation procedure towards a UE in Idle mode, the MME shall include only the existing Bearer Contexts (not the new Bearer Contexts just created) in the corresponding Modify (Access) Bearer Request message. The same principle shall apply when piggybacking is used, i.e. when the Modify Bearer Request is piggybacked in the Create Bearer Response message, the MME shall include only the existing Bearer Contexts (not the new Bearer Contexts just created) in the corresponding Modify (Access) Bearer Request message. NOTE: During a Network Triggered Service Request procedure, which is triggered by a dedicated bearer creation procedure towards a UE in Idle mode, bearer mismatches can be avoided by the MME sending the Create Bearer Response only after it receives the Modify Bearer Response message, however in some rare cases, the signalling can be delayed for the UE, e.g. if the Modify Bearer Response is lost.

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

14.3.2

– CA-ParametersNR

The IE CA-ParametersNR contains carrier aggregation and inter-frequency DAPS handover related capabilities that are defined per band combination. CA-ParametersNR information element -- ASN1START -- TAG-CA-PARAMETERSNR-START CA-ParametersNR ::= SEQUENCE { dummy ENUMERATED {supported} OPTIONAL, parallelTxSRS-PUCCH-PUSCH ENUMERATED {supported} OPTIONAL, parallelTxPRACH-SRS-PUCCH-PUSCH ENUMERATED {supported} OPTIONAL, simultaneousRxTxInterBandCA ENUMERATED {supported} OPTIONAL, simultaneousRxTxSUL ENUMERATED {supported} OPTIONAL, diffNumerologyAcrossPUCCH-Group ENUMERATED {supported} OPTIONAL, diffNumerologyWithinPUCCH-GroupSmallerSCS ENUMERATED {supported} OPTIONAL, supportedNumberTAG ENUMERATED {n2, n3, n4} OPTIONAL, ... } CA-ParametersNR-v1540 ::= SEQUENCE { simultaneousSRS-AssocCSI-RS-AllCC INTEGER (5..32) OPTIONAL, csi-RS-IM-ReceptionForFeedbackPerBandComb SEQUENCE { maxNumberSimultaneousNZP-CSI-RS-ActBWP-AllCC INTEGER (1..64) OPTIONAL, totalNumberPortsSimultaneousNZP-CSI-RS-ActBWP-AllCC INTEGER (2..256) OPTIONAL } OPTIONAL, simultaneousCSI-ReportsAllCC INTEGER (5..32) OPTIONAL, dualPA-Architecture ENUMERATED {supported} OPTIONAL } CA-ParametersNR-v1550 ::= SEQUENCE { dummy ENUMERATED {supported} OPTIONAL } CA-ParametersNR-v1560 ::= SEQUENCE { diffNumerologyWithinPUCCH-GroupLargerSCS ENUMERATED {supported} OPTIONAL } CA-ParametersNR-v15g0 ::= SEQUENCE { simultaneousRxTxInterBandCAPerBandPair SimultaneousRxTxPerBandPair OPTIONAL, simultaneousRxTxSULPerBandPair SimultaneousRxTxPerBandPair OPTIONAL } CA-ParametersNR-v1610 ::= SEQUENCE { -- R1 9-3: Parallel MsgA and SRS/PUCCH/PUSCH transmissions across CCs in inter-band CA parallelTxMsgA-SRS-PUCCH-PUSCH-r16 ENUMERATED {supported} OPTIONAL, -- R1 9-4: MsgA operation in a band combination including SUL msgA-SUL-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-9c: Joint search space group switching across multiple cells jointSearchSpaceSwitchAcrossCells-r16 ENUMERATED {supported} OPTIONAL, -- R1 14-5: Half-duplex UE behaviour in TDD CA for same SCS half-DuplexTDD-CA-SameSCS-r16 ENUMERATED {supported} OPTIONAL, -- R1 18-4: SCell dormancy within active time scellDormancyWithinActiveTime-r16 ENUMERATED {supported} OPTIONAL, -- R1 18-4a: SCell dormancy outside active time scellDormancyOutsideActiveTime-r16 ENUMERATED {supported} OPTIONAL, -- R1 18-6: Cross-carrier A-CSI RS triggering with different SCS crossCarrierA-CSI-trigDiffSCS-r16 ENUMERATED {higherA-CSI-SCS,lowerA-CSI-SCS,both} OPTIONAL, -- R1 18-6a: Default QCL assumption for cross-carrier A-CSI-RS triggering defaultQCL-CrossCarrierA-CSI-Trig-r16 ENUMERATED {diffOnly, both} OPTIONAL, -- R1 18-7: CA with non-aligned frame boundaries for inter-band CA interCA-NonAlignedFrame-r16 ENUMERATED {supported} OPTIONAL, simul-SRS-Trans-BC-r16 ENUMERATED {n2} OPTIONAL, interFreqDAPS-r16 SEQUENCE { interFreqAsyncDAPS-r16 ENUMERATED {supported} OPTIONAL, interFreqDiffSCS-DAPS-r16 ENUMERATED {supported} OPTIONAL, interFreqMultiUL-TransmissionDAPS-r16 ENUMERATED {supported} OPTIONAL, interFreqSemiStaticPowerSharingDAPS-Mode1-r16 ENUMERATED {supported} OPTIONAL, interFreqSemiStaticPowerSharingDAPS-Mode2-r16 ENUMERATED {supported} OPTIONAL, interFreqDynamicPowerSharingDAPS-r16 ENUMERATED {short, long} OPTIONAL, interFreqUL-TransCancellationDAPS-r16 ENUMERATED {supported} OPTIONAL } OPTIONAL, codebookParametersPerBC-r16 CodebookParameters-v1610 OPTIONAL, -- R1 16-2a-10 Value of R for BD/CCE blindDetectFactor-r16 INTEGER (1..2) OPTIONAL, -- R1 11-2a: Capability on the number of CCs for monitoring a maximum number of BDs and non-overlapped CCEs per span when configured -- with DL CA with Rel-16 PDCCH monitoring capability on all the serving cells pdcch-MonitoringCA-r16 SEQUENCE { maxNumberOfMonitoringCC-r16 INTEGER (2..16), supportedSpanArrangement-r16 ENUMERATED {alignedOnly, alignedAndNonAligned} } OPTIONAL, -- R1 11-2c: Number of carriers for CCE/BD scaling with DL CA with mix of Rel. 16 and Rel. 15 PDCCH monitoring capabilities on -- different carriers pdcch-BlindDetectionCA-Mixed-r16 SEQUENCE { pdcch-BlindDetectionCA1-r16 INTEGER (1..15), pdcch-BlindDetectionCA2-r16 INTEGER (1..15), supportedSpanArrangement-r16 ENUMERATED {alignedOnly, alignedAndNonAligned} } OPTIONAL, -- R1 11-2d: Capability on the number of CCs for monitoring a maximum number of BDs and non-overlapped CCEs per span for MCG and for -- SCG when configured for NR-DC operation with Rel-16 PDCCH monitoring capability on all the serving cells pdcch-BlindDetectionMCG-UE-r16 INTEGER (1..14) OPTIONAL, pdcch-BlindDetectionSCG-UE-r16 INTEGER (1..14) OPTIONAL, -- R1 11-2e: Number of carriers for CCE/BD scaling for MCG and for SCG when configured for NR-DC operation with mix of Rel. 16 and -- Rel. 15 PDCCH monitoring capabilities on different carriers pdcch-BlindDetectionMCG-UE-Mixed-r16 SEQUENCE { pdcch-BlindDetectionMCG-UE1-r16 INTEGER (0..15), pdcch-BlindDetectionMCG-UE2-r16 INTEGER (0..15) } OPTIONAL, pdcch-BlindDetectionSCG-UE-Mixed-r16 SEQUENCE { pdcch-BlindDetectionSCG-UE1-r16 INTEGER (0..15), pdcch-BlindDetectionSCG-UE2-r16 INTEGER (0..15) } OPTIONAL, -- R1 18-5 cross-carrier scheduling with different SCS in DL CA crossCarrierSchedulingDL-DiffSCS-r16 ENUMERATED {low-to-high, high-to-low, both} OPTIONAL, -- R1 18-5a Default QCL assumption for cross-carrier scheduling crossCarrierSchedulingDefaultQCL-r16 ENUMERATED {diff-only, both} OPTIONAL, -- R1 18-5b cross-carrier scheduling with different SCS in UL CA crossCarrierSchedulingUL-DiffSCS-r16 ENUMERATED {low-to-high, high-to-low, both} OPTIONAL, -- R1 13.19a Simultaneous positioning SRS and MIMO SRS transmission for a given BC simul-SRS-MIMO-Trans-BC-r16 ENUMERATED {n2} OPTIONAL, -- R1 16-3a, 16-3a-1, 16-3b, 16-3b-1: New Individual Codebook codebookParametersAdditionPerBC-r16 CodebookParametersAdditionPerBC-r16 OPTIONAL, -- R1 16-8: Mixed codebook codebookComboParametersAdditionPerBC-r16 CodebookComboParametersAdditionPerBC-r16 OPTIONAL } CA-ParametersNR-v1630 ::= SEQUENCE { -- R1 22-5b: Simultaneous transmission of SRS for antenna switching and SRS for CB/NCB /BM for inter-band UL CA -- R1 22-5d: Simultaneous transmission of SRS for antenna switching for inter-band UL CA simulTX-SRS-AntSwitchingInterBandUL-CA-r16 SimulSRS-ForAntennaSwitching-r16 OPTIONAL, -- R4 8-5: supported beam management type for inter-band CA beamManagementType-r16 ENUMERATED {ibm, dummy} OPTIONAL, -- R4 7-3a: UL frequency separation class with aggregate BW and Gap BW intraBandFreqSeparationUL-AggBW-GapBW-r16 ENUMERATED {classI, classII, classIII} OPTIONAL, -- RAN 89: Case B in case of Inter-band CA with non-aligned frame boundaries interCA-NonAlignedFrame-B-r16 ENUMERATED {supported} OPTIONAL } CA-ParametersNR-v1640 ::= SEQUENCE { -- R4 7-5: Support of reporting UL Tx DC locations for uplink intra-band CA. uplinkTxDC-TwoCarrierReport-r16 ENUMERATED {supported} OPTIONAL, -- RAN 22-6: Support of up to 3 different numerologies in the same NR PUCCH group for NR part of EN-DC, NGEN-DC, NE-DC and NR-CA -- where UE is not configured with two NR PUCCH groups maxUpTo3Diff-NumerologiesConfigSinglePUCCH-grp-r16 PUCCH-Grp-CarrierTypes-r16 OPTIONAL, -- RAN 22-6a: Support of up to 4 different numerologies in the same NR PUCCH group for NR part of EN-DC, NGEN-DC, NE-DC and NR-CA -- where UE is not configured with two NR PUCCH groups maxUpTo4Diff-NumerologiesConfigSinglePUCCH-grp-r16 PUCCH-Grp-CarrierTypes-r16 OPTIONAL, -- RAN 22-7: Support two PUCCH groups for NR-CA with 3 or more bands with at least two carrier types twoPUCCH-Grp-ConfigurationsList-r16 SEQUENCE (SIZE (1..maxTwoPUCCH-Grp-ConfigList-r16)) OF TwoPUCCH-Grp-Configurations-r16 OPTIONAL, -- R1 22-7a: Different numerology across NR PUCCH groups diffNumerologyAcrossPUCCH-Group-CarrierTypes-r16 ENUMERATED {supported} OPTIONAL, -- R1 22-7b: Different numerologies across NR carriers within the same NR PUCCH group, with PUCCH on a carrier of smaller SCS diffNumerologyWithinPUCCH-GroupSmallerSCS-CarrierTypes-r16 ENUMERATED {supported} OPTIONAL, -- R1 22-7c: Different numerologies across NR carriers within the same NR PUCCH group, with PUCCH on a carrier of larger SCS diffNumerologyWithinPUCCH-GroupLargerSCS-CarrierTypes-r16 ENUMERATED {supported} OPTIONAL, -- R1 11-2f: add the replicated FGs of 11-2a/c with restriction for non-aligned span case -- with DL CA with Rel-16 PDCCH monitoring capability on all the serving cells pdcch-MonitoringCA-NonAlignedSpan-r16 INTEGER (2..16) OPTIONAL, -- R1 11-2g: add the replicated FGs of 11-2a/c with restriction for non-aligned span case pdcch-BlindDetectionCA-Mixed-NonAlignedSpan-r16 SEQUENCE { pdcch-BlindDetectionCA1-r16 INTEGER (1..15), pdcch-BlindDetectionCA2-r16 INTEGER (1..15) } OPTIONAL } CA-ParametersNR-v1690 ::= SEQUENCE { csi-ReportingCrossPUCCH-Grp-r16 SEQUENCE { computationTimeForA-CSI-r16 ENUMERATED {sameAsNoCross, relaxed}, additionalSymbols-r16 SEQUENCE { scs-15kHz-additionalSymbols-r16 ENUMERATED {s14, s28} OPTIONAL, scs-30kHz-additionalSymbols-r16 ENUMERATED {s14, s28} OPTIONAL, scs-60kHz-additionalSymbols-r16 ENUMERATED {s14, s28, s56} OPTIONAL, scs-120kHz-additionalSymbols-r16 ENUMERATED {s14, s28, s56} OPTIONAL } OPTIONAL, sp-CSI-ReportingOnPUCCH-r16 ENUMERATED {supported} OPTIONAL, sp-CSI-ReportingOnPUSCH-r16 ENUMERATED {supported} OPTIONAL, carrierTypePairList-r16 SEQUENCE (SIZE (1..maxCarrierTypePairList-r16)) OF CarrierTypePair-r16 } OPTIONAL } CA-ParametersNR-v16a0 ::= SEQUENCE { pdcch-BlindDetectionMixedList-r16 SEQUENCE(SIZE(1..maxNrofPdcch-BlindDetectionMixed-1-r16)) OF PDCCH-BlindDetectionMixedList-r16 } CA-ParametersNR-v1700 ::= SEQUENCE { -- R1 23-9-1: Basic Features of Further Enhanced Port-Selection Type II Codebook (FeType-II) per band combination information codebookParametersfetype2PerBC-r17 CodebookParametersfetype2PerBC-r17 OPTIONAL, -- R4 18-4: Support of enhanced Demodulation requirements for CA in HST SFN FR1 demodulationEnhancementCA-r17 ENUMERATED {supported} OPTIONAL, -- R4 20-1: Maximum uplink duty cycle for NR inter-band CA power class 2 maxUplinkDutyCycle-interBandCA-PC2-r17 ENUMERATED {n50, n60, n70, n80, n90, n100} OPTIONAL, -- R4 20-2: Maximum uplink duty cycle for NR SUL combination power class 2 maxUplinkDutyCycle-SULcombination-PC2-r17 ENUMERATED {n50, n60, n70, n80, n90, n100} OPTIONAL, beamManagementType-CBM-r17 ENUMERATED {supported} OPTIONAL, -- R1 25-18: Parallel PUCCH and PUSCH transmission across CCs in inter-band CA parallelTxPUCCH-PUSCH-r17 ENUMERATED {supported} OPTIONAL, -- R1 23-9-5 Active CSI-RS resources and ports for mixed codebook types in any slot per band combination codebookComboParameterMixedTypePerBC-r17 CodebookComboParameterMixedTypePerBC-r17 OPTIONAL, -- R1 23-7-1 Basic Features of CSI Enhancement for Multi-TRP mTRP-CSI-EnhancementPerBC-r17 SEQUENCE { maxNumNZP-CSI-RS-r17 INTEGER (2..8), cSI-Report-mode-r17 ENUMERATED {mode1, mode2, both}, supportedComboAcrossCCs-r17 SEQUENCE (SIZE (1..16)) OF CSI-MultiTRP-SupportedCombinations-r17, codebookMode-NCJT-r17 ENUMERATED{mode1,mode1And2} } OPTIONAL, -- R1 23-7-1b Active CSI-RS resources and ports in the presence of multi-TRP CSI codebookComboParameterMultiTRP-PerBC-r17 CodebookComboParameterMultiTRP-PerBC-r17 OPTIONAL, -- R1 24-8b: 32 DL HARQ processes for FR 2-2 - maximum number of component carriers maxCC-32-DL-HARQ-ProcessFR2-2-r17 ENUMERATED {n1, n2, n3, n4, n6, n8, n16, n32} OPTIONAL, -- R1 24-9b: 32 UL HARQ processes for FR 2-2 - maximum number of component carriers maxCC-32-UL-HARQ-ProcessFR2-2-r17 ENUMERATED {n1, n2, n3, n4, n5, n8, n16, n32} OPTIONAL, -- R1 34-2: Cross-carrier scheduling from SCell to PCell/PSCell (Type B) crossCarrierSchedulingSCell-SpCellTypeB-r17 CrossCarrierSchedulingSCell-SpCell-r17 OPTIONAL, -- R1 34-1: Cross-carrier scheduling from SCell to PCell/PSCell with search space restrictions (Type A) crossCarrierSchedulingSCell-SpCellTypeA-r17 CrossCarrierSchedulingSCell-SpCell-r17 OPTIONAL, -- R1 34-1a: DCI formats on PCell/PSCell USS set(s) support dci-FormatsPCellPSCellUSS-Sets-r17 ENUMERATED {supported} OPTIONAL, -- R1 34-3: Disabling scaling factor alpha when sSCell is deactivated disablingScalingFactorDeactSCell-r17 ENUMERATED {supported} OPTIONAL, -- R1 34-4: Disabling scaling factor alpha when sSCell is deactivated disablingScalingFactorDormantSCell-r17 ENUMERATED {supported} OPTIONAL, -- R1 34-5: Non-aligned frame boundaries between PCell/PSCell and sSCell non-AlignedFrameBoundaries-r17 SEQUENCE { scs15kHz-15kHz-r17 BIT STRING (SIZE (1..496)) OPTIONAL, scs15kHz-30kHz-r17 BIT STRING (SIZE (1..496)) OPTIONAL, scs15kHz-60kHz-r17 BIT STRING (SIZE (1..496)) OPTIONAL, scs30kHz-30kHz-r17 BIT STRING (SIZE (1..496)) OPTIONAL, scs30kHz-60kHz-r17 BIT STRING (SIZE (1..496)) OPTIONAL, scs60kHz-60kHz-r17 BIT STRING (SIZE (1..496)) OPTIONAL } OPTIONAL } CA-ParametersNR-v1720 ::= SEQUENCE { -- R1 39-1: Parallel SRS and PUCCH/PUSCH transmission across CCs in intra-band non-contiguous CA parallelTxSRS-PUCCH-PUSCH-intraBand-r17 ENUMERATED {supported} OPTIONAL, -- R1 39-2: Parallel PRACH and SRS/PUCCH/PUSCH transmissions across CCs in intra-band non-contiguous CA parallelTxPRACH-SRS-PUCCH-PUSCH-intraBand-r17 ENUMERATED {supported} OPTIONAL, -- R1 25-9: Semi-static PUCCH cell switching for a single PUCCH group only semiStaticPUCCH-CellSwitchSingleGroup-r17 SEQUENCE { pucch-Group-r17 ENUMERATED {primaryGroupOnly, secondaryGroupOnly, eitherPrimaryOrSecondaryGroup}, pucch-Group-Config-r17 PUCCH-Group-Config-r17 } OPTIONAL, -- R1 25-9a: Semi-static PUCCH cell switching for two PUCCH groups semiStaticPUCCH-CellSwitchTwoGroups-r17 SEQUENCE (SIZE (1..maxTwoPUCCH-Grp-ConfigList-r17)) OF TwoPUCCH-Grp-Configurations-r17 OPTIONAL, -- R1 25-10: PUCCH cell switching based on dynamic indication for same length of overlapping PUCCH slots/sub-slots for a single -- PUCCH group only dynamicPUCCH-CellSwitchSameLengthSingleGroup-r17 SEQUENCE { pucch-Group-r17 ENUMERATED {primaryGroupOnly, secondaryGroupOnly, eitherPrimaryOrSecondaryGroup}, pucch-Group-Config-r17 PUCCH-Group-Config-r17 } OPTIONAL, -- R1 25-10a: PUCCH cell switching based on dynamic indication for different length of overlapping PUCCH slots/sub-slots -- for a single PUCCH group only dynamicPUCCH-CellSwitchDiffLengthSingleGroup-r17 SEQUENCE { pucch-Group-r17 ENUMERATED {primaryGroupOnly, secondaryGroupOnly, eitherPrimaryOrSecondaryGroup}, pucch-Group-Config-r17 PUCCH-Group-Config-r17 } OPTIONAL, -- R1 25-10b: PUCCH cell switching based on dynamic indication for same length of overlapping PUCCH slots/sub-slots for two PUCCH -- groups dynamicPUCCH-CellSwitchSameLengthTwoGroups-r17 SEQUENCE (SIZE (1..maxTwoPUCCH-Grp-ConfigList-r17)) OF TwoPUCCH-Grp-Configurations-r17 OPTIONAL, -- R1 25-10c: PUCCH cell switching based on dynamic indication for different length of overlapping PUCCH slots/sub-slots for two -- PUCCH groups dynamicPUCCH-CellSwitchDiffLengthTwoGroups-r17 SEQUENCE (SIZE (1..maxTwoPUCCH-Grp-ConfigList-r17)) OF TwoPUCCH-Grp-Configurations-r17 OPTIONAL, -- R1 33-2a: ACK/NACK based HARQ-ACK feedback and RRC-based enabling/disabling ACK/NACK-based -- feedback for dynamic scheduling for multicast ack-NACK-FeedbackForMulticast-r17 ENUMERATED {supported} OPTIONAL, -- R1 33-2d: PTP retransmission for multicast dynamic scheduling ptp-Retx-Multicast-r17 ENUMERATED {supported} OPTIONAL, -- R1 33-4: NACK-only based HARQ-ACK feedback for RRC-based enabling/disabling multicast with ACK/NACK transforming nack-OnlyFeedbackForMulticast-r17 ENUMERATED {supported} OPTIONAL, -- R1 33-4a: NACK-only based HARQ-ACK feedback for multicast corresponding to a specific sequence or a PUCCH transmission nack-OnlyFeedbackSpecificResourceForMulticast-r17 ENUMERATED {supported} OPTIONAL, -- R1 33-5-1a: ACK/NACK based HARQ-ACK feedback and RRC-based enabling/disabling ACK/NACK-based feedback -- for SPS group-common PDSCH for multicast ack-NACK-FeedbackForSPS-Multicast-r17 ENUMERATED {supported} OPTIONAL, -- R1 33-5-1d: PTP retransmission for SPS group-common PDSCH for multicast ptp-Retx-SPS-Multicast-r17 ENUMERATED {supported} OPTIONAL, -- R4 26-1: Higher Power Limit CA DC higherPowerLimit-r17 ENUMERATED {supported} OPTIONAL, -- R1 39-4: Parallel MsgA and SRS/PUCCH/PUSCH transmissions across CCs in intra-band non-contiguous CA parallelTxMsgA-SRS-PUCCH-PUSCH-intraBand-r17 ENUMERATED {supported} OPTIONAL, -- R1 24-11a: Capability on the number of CCs for monitoring a maximum number of BDs and non-overlapped CCEs per span when -- configured with DL CA with Rel-17 PDCCH monitoring capability on all the serving cells pdcch-MonitoringCA-r17 INTEGER (4..16) OPTIONAL, -- R1 24-11f: Capability on the number of CCs for monitoring a maximum number of BDs and non-overlapped CCEs for MCG and for SCG -- when configured for NR-DC operation with Rel-17 PDCCH monitoring capability on all the serving cells pdcch-BlindDetectionMCG-SCG-List-r17 SEQUENCE(SIZE(1..maxNrofPdcch-BlindDetection-r17)) OF PDCCH-BlindDetectionMCG-SCG-r17 OPTIONAL, -- R1 24-11c: Number of carriers for CCE/BD scaling with DL CA with mix of Rel. 17 and Rel. 15 PDCCH monitoring capabilities on -- different Carriers -- R1 24-11g: Number of carriers for CCE/BD scaling for MCG and for SCG when configured for NR-DC operation with mix of Rel. 17 and -- Rel. 15 PDCCH monitoring capabilities on different carriers pdcch-BlindDetectionMixedList1-r17 SEQUENCE(SIZE(1..maxNrofPdcch-BlindDetection-r17)) OF PDCCH-BlindDetectionMixed-r17 OPTIONAL, -- R1 24-11d: Number of carriers for CCE/BD scaling with DL CA with mix of Rel. 17 and Rel. 16 PDCCH monitoring capabilities on -- different Carriers -- R1 24-11h: Number of carriers for CCE/BD scaling for MCG and for SCG when configured for NR-DC operation with mix of Rel. 17 and -- Rel. 16 PDCCH monitoring capabilities on different carriers pdcch-BlindDetectionMixedList2-r17 SEQUENCE(SIZE(1..maxNrofPdcch-BlindDetection-r17)) OF PDCCH-BlindDetectionMixed-r17 OPTIONAL, -- R1 24-11e: Number of carriers for CCE/BD scaling with DL CA with mix of Rel. 17, Rel. 16 and Rel. 15 PDCCH monitoring -- capabilities on different carriers -- R1 24-11i: Number of carriers for CCE/BD scaling for MCG and for SCG when configured for NR-DC operation with mix of Rel. 17, -- Rel. 16 and Rel. 15 PDCCH monitoring capabilities on different carriers pdcch-BlindDetectionMixedList3-r17 SEQUENCE(SIZE(1..maxNrofPdcch-BlindDetection-r17)) OF PDCCH-BlindDetectionMixed1-r17 OPTIONAL } CA-ParametersNR-v1730 ::= SEQUENCE { -- R1 30-4a: DM-RS bundling for PUSCH repetition type A (per BC) dmrs-BundlingPUSCH-RepTypeAPerBC-r17 ENUMERATED {supported} OPTIONAL, -- R1 30-4b: DM-RS bundling for PUSCH repetition type B(per BC) dmrs-BundlingPUSCH-RepTypeBPerBC-r17 ENUMERATED {supported} OPTIONAL, -- R1 30-4c: DM-RS bundling for TB processing over multi-slot PUSCH(per BC) dmrs-BundlingPUSCH-multiSlotPerBC-r17 ENUMERATED {supported} OPTIONAL, -- R1 30-4d: DMRS bundling for PUCCH repetitions(per BC) dmrs-BundlingPUCCH-RepPerBC-r17 ENUMERATED {supported} OPTIONAL, -- R1 30-4g: Restart DM-RS bundling (per BC) dmrs-BundlingRestartPerBC-r17 ENUMERATED {supported} OPTIONAL, -- R1 30-4h: DM-RS bundling for non-back-to-back transmission (per BC) dmrs-BundlingNonBackToBackTX-PerBC-r17 ENUMERATED {supported} OPTIONAL, -- R1 39-3-1: Stay on the target CC for SRS carrier switching stayOnTargetCC-SRS-CarrierSwitch-r17 ENUMERATED {supported} OPTIONAL, -- R1 33-3-3a: FDM-ed Type-1 and Type-2 HARQ-ACK codebooks for multiplexing HARQ-ACK for unicast and HARQ-ACK for multicast fdm-CodebookForMux-UnicastMulticastHARQ-ACK-r17 ENUMERATED {supported} OPTIONAL, -- R1 33-3-3b: Mode 2 TDM-ed Type-1 and Type-2 HARQ-ACK codebook for multiplexing HARQ-ACK for unicast and HARQ-ACK for multicast mode2-TDM-CodebookForMux-UnicastMulticastHARQ-ACK-r17 ENUMERATED {supported} OPTIONAL, -- R1 33-3-4: Mode 1 for type1 codebook generation mode1-ForType1-CodebookGeneration-r17 ENUMERATED {supported} OPTIONAL, -- R1 33-5-1j: NACK-only based HARQ-ACK feedback for multicast corresponding to a specific sequence or a PUCCH transmission -- for SPS group-commmon PDSCH for multicast nack-OnlyFeedbackSpecificResourceForSPS-Multicast-r17 ENUMERATED {supported} OPTIONAL, -- R1 33-8-2: Up to 2 PUCCH resources configuration for multicast feedback for dynamically scheduled multicast multiPUCCH-ConfigForMulticast-r17 ENUMERATED {supported} OPTIONAL, -- R1 33-8-3: PUCCH resource configuration for multicast feedback for SPS GC-PDSCH pucch-ConfigForSPS-Multicast-r17 ENUMERATED {supported} OPTIONAL, -- The following parameter is associated with R1 33-2a, R1 33-3-3a, and R1 33-3-3b, and is not a RAN1 FG. maxNumberG-RNTI-HARQ-ACK-Codebook-r17 INTEGER (1..4) OPTIONAL, -- R1 33-3-5: Feedback multiplexing for unicast PDSCH and group-common PDSCH for multicast with same priority and different codebook -- type mux-HARQ-ACK-UnicastMulticast-r17 ENUMERATED {supported} OPTIONAL } CA-ParametersNR-v1740 ::= SEQUENCE { -- R1 33-5-1f: NACK-only based HARQ-ACK feedback for multicast RRC-based enabling/disabling NACK-only based feedback -- for SPS group-common PDSCH for multicast nack-OnlyFeedbackForSPS-Multicast-r17 ENUMERATED {supported} OPTIONAL, -- R1 33-8-1: PUCCH resource configuration for multicast feedback for dynamically scheduled multicast singlePUCCH-ConfigForMulticast-r17 ENUMERATED {supported} OPTIONAL } CA-ParametersNR-v1760 ::= SEQUENCE { prioSCellPRACH-OverSP-PeriodicSRS-Support-r17 ENUMERATED {supported} OPTIONAL } CA-ParametersNR-v1770 ::= SEQUENCE { parallelTxPUCCH-PUSCH-SamePriority-r17 ENUMERATED {supported} OPTIONAL } CA-ParametersNR-v1800 ::= SEQUENCE { codebookParametersetype2DopplerCSI-PerBC-r18 CodebookParametersetype2DopplerCSI-r18 OPTIONAL, codebookParametersfetype2DopplerCSI-PerBC-r18 CodebookParametersfetype2DopplerCSI-r18 OPTIONAL, -- R1 49-1b: Multi-cell PDSCH scheduling by DCI format 1_3 on a scheduling cell not included in a set of cells with different -- SCS/carrier type between scheduling cell and cells in the set multiCell-PDSCH-DCI-1-3-DiffSCS-r18 SEQUENCE { coScheduledCellSCS-r18 ENUMERATED {lowScheduling-highScheduled, highScheduling-lowScheduled, both}, combinationCarrierType-r18 SEQUENCE (SIZE(1..maxSchedulingBandCombination-r18)) OF CombinationCarrierType-r18, maxNumberCoScheduledCell-r18 INTEGER (2..4), maxNumberSetsOfCellAcrossPUCCH-Group-r18 INTEGER (1..8), maxNumberSetsOfCellScheduling-r18 INTEGER (1..4), harqFeedbackType-r18 ENUMERATED {type1, type2, type1And2}, coScheduledCellIndicationScheme-r18 ENUMERATED {fdra,cellInd, both} } OPTIONAL, -- R1 55-6a: Capability on the number of CCs for monitoring a maximum number of BDs and non-overlapped CCEs per span when configured -- with DL CA with Rel-16 PDCCH monitoring capability on all the serving cells pdcch-MonitoringCA-r18 SEQUENCE { maxNumberOfMonitoringCC-r18 INTEGER (2..16), supportedSpanArrangement-r18 ENUMERATED {alignedOnly, alignedAndNonAligned} } OPTIONAL, -- R1 55-6c: Number of carriers for CCE/BD scaling with DL CA with mix of Rel. 16 and Rel. 15 PDCCH monitoring capabilities on -- different carriers pdcch-BlindDetectionCA-Mixed-r18 SEQUENCE { blindDetectionCA-Mixed-r18 SEQUENCE(SIZE (1..maxNrofPdcch-BlindDetection-r17)) OF PDCCH-BlindDetectionCA-Mixed-r18, supportedSpanArrangement-r18 ENUMERATED{ alignedOnly, alignedAndNonAligned } } OPTIONAL, -- R1 55-6e: Number of carriers for CCE/BD scaling for MCG and for SCG when configured for NR-DC operation with mix of Rel. 16 -- and Rel. 15 PDCCH monitoring capabilities on different carriers pdcch-BlinkdDetectionMCG-SCG-List-r18 SEQUENCE(SIZE (1..maxNrofPdcch-BlindDetection-r17)) OF PDCCH-BlindDetectionMCG-SCG-r18 OPTIONAL, -- R1 55-6g: Number of carriers for CCE/BD scaling with DL CA with mix of Rel. 16 and Rel. 15 PDCCH monitoring capabilities on -- different carriers with restriction for non-aligned span case pdcch-BlindDetectionCA-Mixed-NonAlignedSpan-r18 SEQUENCE(SIZE (1..maxNrofPdcch-BlindDetection-r17)) OF PDCCH-BlindDetectionCA-Mixed-r18 OPTIONAL, -- R1 55-6f: Capability on the number of CCs for monitoring a maximum number of BDs and non-overlapped CCEs per span when configured -- with DL CA with Rel-16 PDCCH monitoring capability on all the serving cells with restriction for non-aligned span case pdcch-MonitoringCA-NonAlignedSpan-r18 INTEGER (2..16) OPTIONAL, -- R4 33-1: Support of intra-band non-collocated NR CA operation intraBandNR-CA-non-collocated-r18 ENUMERATED {supported} OPTIONAL } CrossCarrierSchedulingSCell-SpCell-r17 ::= SEQUENCE { supportedSCS-Combinations-r17 SEQUENCE { scs15kHz-15kHz-r17 ENUMERATED {supported} OPTIONAL, scs15kHz-30kHz-r17 ENUMERATED {supported} OPTIONAL, scs15kHz-60kHz-r17 ENUMERATED {supported} OPTIONAL, scs30kHz-30kHz-r17 BIT STRING (SIZE (1..496)) OPTIONAL, scs30kHz-60kHz-r17 BIT STRING (SIZE (1..496)) OPTIONAL, scs60kHz-60kHz-r17 BIT STRING (SIZE (1..496)) OPTIONAL }, pdcch-MonitoringOccasion-r17 ENUMERATED {val1, val2} } PDCCH-BlindDetectionMixedList-r16::= SEQUENCE { pdcch-BlindDetectionCA-MixedExt-r16 CHOICE { pdcch-BlindDetectionCA-Mixed-v16a0 PDCCH-BlindDetectionCA-MixedExt-r16, pdcch-BlindDetectionCA-Mixed-NonAlignedSpan-v16a0 PDCCH-BlindDetectionCA-MixedExt-r16 } OPTIONAL, pdcch-BlindDetectionCG-UE-MixedExt-r16 SEQUENCE{ pdcch-BlindDetectionMCG-UE-Mixed-v16a0 PDCCH-BlindDetectionCG-UE-MixedExt-r16, pdcch-BlindDetectionSCG-UE-Mixed-v16a0 PDCCH-BlindDetectionCG-UE-MixedExt-r16 } OPTIONAL } PDCCH-BlindDetectionCA-MixedExt-r16 ::= SEQUENCE { pdcch-BlindDetectionCA1-r16 INTEGER (1..15), pdcch-BlindDetectionCA2-r16 INTEGER (1..15) } PDCCH-BlindDetectionCG-UE-MixedExt-r16 ::= SEQUENCE { pdcch-BlindDetectionCG-UE1-r16 INTEGER (0..15), pdcch-BlindDetectionCG-UE2-r16 INTEGER (0..15) } PDCCH-BlindDetectionMCG-SCG-r17 ::= SEQUENCE { pdcch-BlindDetectionMCG-UE-r17 INTEGER (1..15), pdcch-BlindDetectionSCG-UE-r17 INTEGER (1..15) } PDCCH-BlindDetectionMixed-r17::= SEQUENCE { pdcch-BlindDetectionCA-Mixed-r17 PDCCH-BlindDetectionCA-Mixed-r17 OPTIONAL, pdcch-BlindDetectionCG-UE-Mixed-r17 SEQUENCE{ pdcch-BlindDetectionMCG-UE-Mixed-v17 PDCCH-BlindDetectionCG-UE-Mixed-r17, pdcch-BlindDetectionSCG-UE-Mixed-v17 PDCCH-BlindDetectionCG-UE-Mixed-r17 } OPTIONAL } PDCCH-BlindDetectionCG-UE-Mixed-r17 ::= SEQUENCE { pdcch-BlindDetectionCG-UE1-r17 INTEGER (0..15), pdcch-BlindDetectionCG-UE2-r17 INTEGER (0..15) } PDCCH-BlindDetectionCA-Mixed-r17 ::= SEQUENCE { pdcch-BlindDetectionCA1-r17 INTEGER (1..15) OPTIONAL, pdcch-BlindDetectionCA2-r17 INTEGER (1..15) OPTIONAL } PDCCH-BlindDetectionMixed1-r17::= SEQUENCE { pdcch-BlindDetectionCA-Mixed1-r17 PDCCH-BlindDetectionCA-Mixed1-r17 OPTIONAL, pdcch-BlindDetectionCG-UE-Mixed1-r17 SEQUENCE{ pdcch-BlindDetectionMCG-UE-Mixed1-v17 PDCCH-BlindDetectionCG-UE-Mixed1-r17, pdcch-BlindDetectionSCG-UE-Mixed1-v17 PDCCH-BlindDetectionCG-UE-Mixed1-r17 } OPTIONAL } PDCCH-BlindDetectionCG-UE-Mixed1-r17 ::= SEQUENCE { pdcch-BlindDetectionCG-UE1-r17 INTEGER (0..15), pdcch-BlindDetectionCG-UE2-r17 INTEGER (0..15), pdcch-BlindDetectionCG-UE3-r17 INTEGER (0..15) } PDCCH-BlindDetectionCA-Mixed1-r17 ::= SEQUENCE { pdcch-BlindDetectionCA1-r17 INTEGER (1..15) OPTIONAL, pdcch-BlindDetectionCA2-r17 INTEGER (1..15) OPTIONAL, pdcch-BlindDetectionCA3-r17 INTEGER (1..15) OPTIONAL } PDCCH-BlindDetectionMCG-SCG-r18 ::= SEQUENCE{ pdcch-BlindDetectionMCG-UE-Mixed-r18 PDCCH-BlindDetectionCG-UE-Mixed-r18, pdcch-BlindDetectionSCG-UE-Mixed-r18 PDCCH-BlindDetectionCG-UE-Mixed-r18 } PDCCH-BlindDetectionCA-Mixed-r18 ::= SEQUENCE { pdcch-BlindDetectionCA1-r18 INTEGER (1..15), pdcch-BlindDetectionCA2-r18 INTEGER (1..15) } PDCCH-BlindDetectionCG-UE-Mixed-r18 ::= SEQUENCE { pdcch-BlindDetectionCG-UE1-r18 INTEGER (0..15), pdcch-BlindDetectionCG-UE2-r18 INTEGER (0..15) } SimulSRS-ForAntennaSwitching-r16 ::= SEQUENCE { supportSRS-xTyR-xLessThanY-r16 ENUMERATED {supported} OPTIONAL, supportSRS-xTyR-xEqualToY-r16 ENUMERATED {supported} OPTIONAL, supportSRS-AntennaSwitching-r16 ENUMERATED {supported} OPTIONAL } TwoPUCCH-Grp-Configurations-r16 ::= SEQUENCE { pucch-PrimaryGroupMapping-r16 TwoPUCCH-Grp-ConfigParams-r16, pucch-SecondaryGroupMapping-r16 TwoPUCCH-Grp-ConfigParams-r16 } TwoPUCCH-Grp-Configurations-r17 ::= SEQUENCE { primaryPUCCH-GroupConfig-r17 PUCCH-Group-Config-r17, secondaryPUCCH-GroupConfig-r17 PUCCH-Group-Config-r17 } TwoPUCCH-Grp-ConfigParams-r16 ::= SEQUENCE { pucch-GroupMapping-r16 PUCCH-Grp-CarrierTypes-r16, pucch-TX-r16 PUCCH-Grp-CarrierTypes-r16 } CarrierTypePair-r16 ::= SEQUENCE { carrierForCSI-Measurement-r16 PUCCH-Grp-CarrierTypes-r16, carrierForCSI-Reporting-r16 PUCCH-Grp-CarrierTypes-r16 } PUCCH-Grp-CarrierTypes-r16 ::= SEQUENCE { fr1-NonSharedTDD-r16 ENUMERATED {supported} OPTIONAL, fr1-SharedTDD-r16 ENUMERATED {supported} OPTIONAL, fr1-NonSharedFDD-r16 ENUMERATED {supported} OPTIONAL, fr2-r16 ENUMERATED {supported} OPTIONAL } PUCCH-Group-Config-r17 ::= SEQUENCE { fr1-FR1-NonSharedTDD-r17 ENUMERATED {supported} OPTIONAL, fr2-FR2-NonSharedTDD-r17 ENUMERATED {supported} OPTIONAL, fr1-FR2-NonSharedTDD-r17 ENUMERATED {supported} OPTIONAL } -- TAG-CA-PARAMETERSNR-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

17.7.7 MBMS-Session-Duration AVP

The MBMS-Session-Duration AVP (AVP code 904) is of type OctetString with a length of three octets and indicates the estimated session duration (MBMS Service data transmission). Bit 8 of octet 1 to bit 8 of octet 3 (17 bits) express seconds, for which the maximum allowed value is 86400 seconds. Bits 7 to 1 of octet 3 (7 bits) express days, for which the maximum allowed value is 18 days. The coding is as follows (the ‘s’ bits represent the seconds, the ‘d’ bits represent the days): For the whole session duration the seconds and days are added together and the maximum session duration is 19 days. The lowest value of this AVP (i.e. all 0’s), is reserved to indicate an indefinite value to denote sessions that are expected to be always-on.

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

12.6 Shared Network Area Identifier

The Shared Network Area Identifier (SNA-Id) is used to identify an area consisting of one or more Location Areas. Such an area is called a Shared Network Area and can be used to grant access rights to parts of a Shared Network to a UE in connected mode (see 3GPP TS 25.401[ None ] [39]). The Shared Network Area Identifier consists of the PLMN-Id followed by the Shared Network Area Code (SNAC). - SNA-Id = PLMN-Id || SNAC The SNAC is defined by the operator. For the syntax description and the use of this identifier in RANAP signalling, see 3GPP TS 25.413[ UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling ] [17].

3GPP TS 23.003

Numbering, addressing and identification

CT WG4

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

12.6

6.5.1G Frequency error for V2X Communication

The UE modulated carrier frequency for V2X sidelink transmissions shall be accurate to within ±0.1 PPM observed over a period of one time slot (0.5 ms) compared to the absolute frequency in case of using GNSS synchronization source. The same requirements applied over a period of one time slot (0.5 ms) compared to the relative frequency in case of using the E-UTRA Node B or V2X UE sidelink synchronization signals. When UE is configured for simultaneous E-UTRA V2X sidelink and E-UTRA uplink transmissions for inter-band E-UTRA V2X / E-UTRA bands specified in Table 5.5G-2, the requirements in subclause 6.5.1G apply for V2X sidelink transmission and the requirements in subclause 6.5.1 apply for the E-UTRA uplink transmission. For V2X UE supporting Transmit Diversity, if the UE transmits on two antenna connectors at the same time, the UE modulated carrier frequency at each transmit antenna connector shall be accurate to within ±0.1 PPM observed over a period of one time slot (0.5 ms) in case of using GNSS synchronization source. The same requirements applied over a period of one time slot (0.5 ms) compared to the relative frequency in case of using the E-UTRA Node B or V2X UE sidelink synchronization signals. If the UE transmits on one antenna connector at a time, the requirements for single carrier shall apply to the active antenna connector.

3GPP TS 36.101

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

RAN4

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

6.5.1G

6.3.8 Handling of serving PLMN rate control

Serving PLMN rate control enables the serving PLMN to protect its MME and the signalling radio bearers in the E-UTRAN from load generated by NAS messages with user data over control plane. The MME can inform the UE of any local serving PLMN rate control during the default EPS bearer context activation procedure (see clause 6.4.1). If the serving PLMN rate control is enabled, the MME shall start the serving PLMN rate control for the PDN connection when the first NAS message with user data over control plane is received over the PDN connection. The UE shall limit the rate at which it generates uplink NAS messages with user data over control plane to comply with the serving PLMN policy provided by the network. The indicated rate in a NAS procedure applies to the PDN connection the NAS procedure corresponds to, and the indicated rate is valid until the PDN connection is released. Serving PLMN rate control is applicable for PDN connections established for control plane CIoT EPS optimization only. Any serving PLMN rate control information provided by the network to the UE is only applicable for the PLMN which provided this information. This serving PLMN rate control information shall be discarded when the UE successfully registers to another PLMN. NOTE: The serving PLMN can discard or delay NAS messages including user data over control plane that exceed the limit provided for serving PLMN rate control.

3GPP TS 24.301

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

CT WG1

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

6.3.8

4.4.3.2 DL PDCP SDU drop rate

This measurement provides the fraction of IP packets (PDCP SDUs) which are dropped on the downlink. Only user-plane traffic (DTCH) is considered. A dropped packet is one whose context is removed from the eNodeB/RN without any part of it having been transmitted on the air interface. Packets discarded during handover are excluded from the count. The measurement is split into subcounters per E-RAB QoS level (QCI). SI This measurement is obtained according to the definition in 3GPP TS 36.314[ Evolved Universal Terrestrial Radio Access (E-UTRA); Layer 2 - Measurements ] [11]. Separate counters are maintained for each QCI. In case only a subset of per QCI measurements is supported, a drop rate subcounter calculated across all QCIs will be provided first. Each measurement is an integer value representing the drop rate multiplied by 1E6. The number of measurements is equal to the number of QCIs plus a possible sum value identified by the .sum suffix. The measurement name has the form DRB.PdcpSduDropRateDl.QCI where QCI identifies the target E-RAB level quality of service class. EUtranCellFDD EUtranCellTDD Valid for packet switched traffic EPS

3GPP TS 32.425

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

SA WG5

3GPP Series : 32 , OAM&P and Charging

4.4.3.2

5.37.8.2 Periodicity and N6 Jitter Information associated with Periodicity

In the procedures for setting up or updating an AF session with QoS, the 5G System may be provided with UL/DL Periodicity information for NG-RAN to configure UE power management for connected mode DRX. The UL/DL Periodicity information is provided by the AF to the PCF via NEF or directly to the PCF when the AF is trusted. If UL/DL Periodicity information is available at the PCF, the PCF sends the Periodicity information received from the AF/NEF to the SMF. In accordance with the operator's local policies, the PCF may include an indication for SMF to request the UPF to perform N6 Traffic Parameter(s) measurement (i.e. N6 Jitter Information associated with the DL Periodicity and if not provided by the AF, UL/DL periodicity) within the PCC Rules. Upon reception of a PCC rule with Periodicity information, the SMF determines the TSCAI and forwards it to the NG-RAN. If the PCC rule indicates to perform N6 Traffic Parameter measurements, the SMF shall request the UPF to monitor and periodically report the N6 Traffic Parameters (i.e. the N6 Jitter Information associated with the DL Periodicity and, if not provided by the AF, UL/DL periodicity) using the N4 Session Modification procedure, see clause 5.8.5.11. If the measurement of N6 Jitter Information associated with the DL Periodicity is required and the DL Periodicity is available at the SMF, the SMF also sends the DL Periodicity to the UPF. The UPF reports the measured N6 Traffic Parameters to SMF via N4 interface. NOTE 1: How the UPF derives the N6 jitter and periodicity (i.e. when periodicity is not provided by the AF) is implementation dependent. At reception of measured N6 Traffic Parameter(s) from the UPF in the N4 Session Level Report, the SMF includes the N6 Jitter Information associated with the DL Periodicity together with the DL periodicity and the UL periodicity if not provided by the AF in the TSCAI and forwards it to the NG-RAN in an NGAP message, see clause 5.27.2. NOTE 2: In order to prevent frequent updates from the UPF, the UPF sends the N6 Jitter Measurement Report periodically or only when the N6 jitter is larger than a threshold. The N6 Jitter Information associated with the DL Periodicity indicates the range of the positive or negative deviation of the arrival time of first arrived packet of a Data Burst compared to the ideal Data Burst start time which is be determined based on the DL periodicity.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.37.8.2

8.2.2.2.7 Enhanced Performance Requirement Type B - 2 Tx Antenna Ports with TM9 interference model

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

3GPP TS 36.101

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

RAN4

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

8.2.2.2.7

7.14 RLM/BFD relaxation

For RLM and BFD relaxation, network may configure low mobility criterion in the NR PCell for the case of NE-DC/NR-DC, and in the NR PSCell for the case of EN-DC and NGEN-DC. MN informs SN when low mobility criterion has been configured in the NR PCell for NR-DC. For RLM relaxation, network may configure good serving cell criterion in the NR PCell for the case of NE-DC/NR-DC, and in the NR PSCell for the case of EN-DC, NGEN-DC and NR-DC. For BFD relaxation, network may configure good serving cell criterion in the NR PCell and/or SCell(s) for the case of NE-DC/NR-DC, and in the NR PSCell and/or SCell(s) for the case of EN-DC, NGEN-DC and NR-DC. For RLM/BFD relaxation, network may simultaneously configure the UE to perform radio link monitoring on the SCG and beam failure detection on the SCG while SCG is deactivated. In such case, UE initiates UE assistance information for the relaxation state report of RLM/BFD measurements for SCG. For RLM/BFD relaxation, network may simultaneously configure the UE not to perform radio link monitoring on the SCG and beam failure detection on the SCG while SCG is deactivated. In such case, UE assistance information for the relaxation state report of RLM/BFD measurements for SCG will not be initiated.

3GPP TS 37.340

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

RAN2

3GPP Series : 37 , Multiple radio access technology aspects

7.14

5.3.9.2 Initiation

The UE initiates the procedure when upper layers request the release of the RRC connection as specified in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [23]. The UE shall not initiate the procedure for power saving purposes. The UE shall: 1> if the upper layers indicate barring of the PCell: 2> treat the PCell used prior to entering RRC_IDLE as barred according to TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [20]; 1> perform the actions upon going to RRC_IDLE as specified in 5.3.11, with release cause 'other'.

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

5.3.9.2

9 Specified and default radio configurations

Specified and default configurations are configurations of which the details are specified in the standard. Specified configurations are fixed while default configurations can be modified using dedicated signalling. The default value for the parameters not listed in following clauses shall be set such as the corresponding features are not configured, i.e. release or false unless explicitly stated otherwise. NOTE: The UE applies the default values specified in the field description of ASN.1 parameters only when the parent IE is present. Hence, the UE does not apply all default values in field descriptions when it applies the "default radio configuration" in accordance with this clause.

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

9

6.1 Overview 6.1.1 General

This clause describes the procedures used for 5GS session management (5GSM) performed over an N1 NAS signalling connection. The main function of the 5GSM sublayer is to support the PDU session handling in the UE and in the SMF (transferred via the AMF). The 5GSM comprises procedures for: - the authentication and authorization, establishment, modification and release of PDU sessions; and - request for performing handover of an existing PDU session between 3GPP access and non-3GPP access, or to transfer an existing PDN connection in the EPS to the 5GS. Each PDU session represents a PDU session established between the UE and an SMF. PDU sessions can remain established even if the radio and network resources constituting the corresponding PDU session between the UE and the SMF are temporarily released. 5GSM procedures can be performed only if a 5GMM context has been established between the UE and the AMF, and the secure exchange of NAS messages has been initiated by the AMF by use of the 5GMM procedures described in clause 5. Once the UE is successfully registered to a PLMN, a PDU session can be established. If no 5GMM context has been established, the 5GMM sublayer has to initiate the establishment of a 5GMM context by use of the 5GMM procedures as described in clause 5. The UE can request the network to modify or release PDU sessions. The network can fulfil such a request from the UE by modifying a PDU session or releasing a PDU session using network-requested procedures (see subclause 6.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

6.1

4.11.4.3.3 Initial Attach with GTP on S2b

The procedure in clause 7.2.4 of TS 23.402[ Architecture enhancements for non-3GPP accesses ] [26] applies with the following modifications: - In Step A.1 IKEv2 tunnel establishment procedure, the 5GC NAS capable UE shall indicate its support of 5GC NAS in IKEv2. The UE allocates a PDU Session ID and also includes it in IKEv2 signalling sent to the ePDG. For 5GC NAS capable UE even if the NAS capability is currently disabled (i.e. N1 mode is disabled), the UE may also allocate a PDU Session ID and include it in IKEv2 signalling sent to the ePDG. - In Step A.1, UE's mobility restriction parameters related to 5GS or indication of support for interworking with 5GS for this APN or both as defined for MME in clause 4.11.0a.3 apply to the ePDG and are obtained by the ePDG as part of the reply from the HSS via the 3GPP AAA Server. These parameters and the 5G NAS support indicator from the UE, may be used by the ePDG to determine if a combined SMF+PGW-C or a standalone PGW should be selected. - In Step B.1, if the PDN connection is not restricted to interworking with 5GS by user subscription and if PDU Session ID is received from the UE, the ePDG shall send the 5GC Not Restricted Indication, 5GS Interworking Indication and the PDU Session ID to the SMF+PGW-C. - In Step B.1, if the SMF+PGW-C supports more than one S-NSSAI and the APN is valid for more than one S-NSSAI, the SMF+PGW-C selects S-NSSAI as specified in clause 4.11.0a.5. - In Step D.1 (Create Session Response), if the PDU Session ID is present and 5GC Not Restricted Indication is set, the SMF+PGW-C assigns a S-NSSAI to be associated with the PDN connection as specified in clause 5.15.7.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The SMF+PGW-C sends the S-NSSAI to the ePDG together with a PLMN ID that the S-NSSAI relates to. - In Steps B.1 and D.1, if the UE does not support 5GC NAS but has 5GS subscription and a SMF+PGW-C is selected and interaction with UDM, PCF and UPF is required, the SMF+PGW-C assigns PDU Session ID as specified in clause 4.11.0a.5. The SMF+PGW-C shall not provide any 5GS related parameters to the UE. - In the IKEv2 Authentication Response message, the ePDG sends S-NSSAI and the PLMN ID that the S-NSSAI relates to, to the UE. The UE associates the received S-NSSAI and the PLMN ID that the S-NSSAI relates to, with the PDN Connection. - After step D.1, the SMF+PGW-C provides the PCF ID selected for the PDN connection in the UDM using the Nudm_UECM_Registration service operation.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.11.4.3.3

15.5.2.2 Connection failure 15.5.2.2.1 General

For analysis of connection failures, the UE makes the RLF Report available to the network. The UE stores the latest RLF Report, including both LTE and NR RLF report until the RLF report is fetched by the network or for 48 hours after the connection failure is detected. The UE only indicates RLF report availability and only provides the RLF report to the network if the current RPLMN is a PLMN that was present in the UE's EPLMN List or was the RPLMN at the time the connection failure was detected. In case RLF happens in an E-UTRA cell, the UE makes the LTE RLF Report available to NG-RAN nodes and eNB(s), and in case RLF happens in an NR cell the UE makes the NR RLF Report available to gNB(s). If the LTE RLF Report is reported to a NG-RAN node, and the last serving node is an E-UTRAN node, the NG-RAN node may transfer it to the E-UTRAN node by triggering the Uplink RAN configuration transfer procedure over NG and the E-UTRAN node can take this into account as defined in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [2].

3GPP TS 38.300

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

RAN2

3GPP Series : 38 , Radio technology beyond LTE

15.5.2.2

6.11.2 Traffic Mapping from Upper Layers to Layer-2

In upstream direction, the IAB-donor-CU configures the IAB-node with mappings between upstream F1 and non-F1 traffic originated at the IAB-node, and the appropriate BAP routing ID, next-hop BAP address and BH RLC channel. A specific mapping is configured: - for each F1-U GTP-U tunnel; - for non-UE associated F1AP messages; - for UE-associated F1AP messages; - for non-F1 traffic. Multiple mappings can contain the same BH RLC channel and/or next-hop BAP address and/or BAP routing ID. In case the IAB-MT is NR-dual-connected (SA mode only), the mapping may include two separate BH RLC channels, where the two BH RLC channels are established toward different parent nodes. In case the IAB-node is configured with multiple IP addresses for F1-C on the NR leg, multiple mappings can be configured for non-UE-associated F1AP messages or UE-associated F1AP messages. The appropriate mapping is selected based on the IAB-node's implementation. These traffic mapping configurations are performed via F1AP. For a boundary IAB-node, the traffic mapping configuration includes information that allows the boundary IAB-node to determine the IAB topology the mapping applies to. During IAB-node integration, a default BH RLC channel and a default BAP routing ID may be configured via RRC, which can be used for non-F1-U traffic. These default configurations may be updated during topology adaptation scenarios as discussed in TS 38.401[ NG-RAN; Architecture description ] [4]. In downstream direction, traffic mapping occurs internal to the IAB-donor. Transport for IAB-donors that use split-gNB architecture is handled in TS 38.401[ NG-RAN; Architecture description ] [4].

3GPP TS 38.300

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

RAN2

3GPP Series : 38 , Radio technology beyond LTE

6.11.2

4.4.4.5 Location Update Attempt Counter

To limit the number of consecutive unsuccessful location updating attempts, an location update attempt counter is used. The location update attempt counter counts the number of consecutive unsuccessful location updating attempts. The location update attempt counter shall be incremented as specified in subclause 4.4.4.9. The location update attempt counter shall be reset when: - the mobile station is powered on; - a SIM/USIM is inserted; - a location updating procedure is successfully completed; - a location updating procedure is rejected with cause: a) #11, #12, #13, #15 or #25 (see subclause 4.4.4.7); b) #22 and T3346 value IE indicating neither zero nor deactivated (see subclause 4.4.4.7); - a normal or periodic routing area updating procedure or combined routing updating is not accepted by the network with cause #11, #12, #13, #15 or #25 (see subclause 4.7.5.1.4 and 4.7.5.2.4); - GPRS attach or combined GPRS attach procedure is not accepted by the network with cause #11, #12, #13, or #15 (see subclause 4.7.3.1.4 and 4.7.3.2.4); - service request procedure is not accepted by the network with cause #12, #13, or #15 (see subclause 4.7.13.4); - network initiated GPRS detach procedure is completed with cause #12, #13, or #15 (see subclause 4.7.4.2.2); - combined GPRS attach or combined routing area updating procedure is successful for GPRS and non-GPRS services; or - a new PLMN is selected. and additionally when the mobile station is in the state MM IDLE sub-state ATTEMPTING to UPDATE: - a new location area is entered; - expiry of timer T3212; - a location updating procedure is triggered upon entering MM IDLE after the release of the last MM connection, as defined in subclause 4.5.3.1; - a location updating procedure is triggered by CM sublayer requests; or - timer T3246 is started. The location update attempt counter shall be used when deciding whether to re-attempt a location updating procedure after expiry of timer T3211 as specified in subclause 4.4.4.9.

3GPP TS 24.008

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

CT WG1

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

4.4.4.5

4.4.4 Integrity protection of NAS signalling messages 4.4.4.1 General

For the UE, integrity protected signalling is mandatory for the 5GMM NAS messages once a valid 5G NAS security context exists and has been taken into use. For the network, integrity protected signalling is mandatory for the 5GMM NAS messages once a secure exchange of 5GS NAS messages has been established for the NAS signalling connection. Integrity protection of all NAS signalling messages is the responsibility of the NAS. It is the network which activates integrity protection. The use of "null integrity protection algorithm" 5G-IA0 (see subclause 9.11.3.34) in the current 5G NAS security context is only allowed: a) for an unauthenticated UE for which establishment of emergency services is allowed; b) for a W-AGF acting on behalf of an FN-RG; c) for a W-AGF acting on behalf of an N5GC device; and d) for a 5G-RG acting on behalf of an AUN3 device. For setting the security header type in outbound NAS messages, the UE and the AMF shall apply the same rules irrespective of whether the "null integrity protection algorithm" or any other integrity protection algorithm is indicated in the 5G NAS security context. If the "null integrity protection algorithm"5G-IA0 has been selected as an integrity protection algorithm, the receiver shall regard the NAS messages with the security header indicating integrity protection as integrity protected. Details of the integrity protection and verification of NAS signalling messages are specified in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. When a NAS message needs to be sent both ciphered and integrity protected, the NAS message is first ciphered and then the ciphered NAS message and the NAS sequence number are integrity protected by calculating the MAC. NOTE: NAS messages that are ciphered with the "null ciphering algorithm" 5G-EA0 are regarded as ciphered (see subclause 4.4.5). When a NAS message needs to be sent only integrity protected and unciphered, the unciphered NAS message and the NAS sequence number are integrity protected by calculating the MAC. When a 5GSM message is piggybacked in a 5GMM message, there is only one Sequence number IE and one Message authentication code IE for the 5GMM message piggybacking the 5GSM message.

3GPP TS 24.501

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

CT WG1

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

4.4.4

4.3.2.1 Charging Trigger Function

As outlined in clause 4.1.2, online charging is a process where charging information is collected in the network element in the same fashion as in offline charging. This implies that, from the functional perspective, the CTF defined in clause 4.3.1.1, also creates the charging events used for online charging. While the accounting metrics used in online charging are generally the same as in offline charging (i.e. the charging mechanism is transparent to the Accounting Metrics Collection), the following functional enhancements concerning the Accounting Data Forwarding are required in the CTF in order to support online charging: - The information collected for, and included in, the online charging events is not necessarily identical to the offline charging case (i.e. the chargeable events may not necessarily be identical to those observed in offline charging); - The charging events are forwarded to the Online Charging Function (OCF) in order to obtain authorisation for the chargeable event / network resource usage requested by the user; - The CTF must be able to delay the actual resource usage until permission by the OCS has been granted; - The CTF must be able to track the availability of resource usage permission ("quota supervision") during the network resource usage; - The CTF must be able to enforce termination of the end user’s network resource usage when permission by the OCS is not granted or expires. The underlying principles for requesting, granting and managing resource usage permissions are described in detail in clause 5.1. Note that the S-CSCF, although involved in online charging, does not create any online charging events, therefore clauses 4.3.2.1 and 4.3.2.2 are not completely applicable to the S-CSCF. Clause 4.3.2.2.2 describes online charging specifically for the S-CSCF. The charging events for online charging are transferred to the OCS using the CAP or Ro reference points. Refer to figure 4.2.1 for information on the applicability of CAP or Ro per NE type.

3GPP TS 32.240

Telecommunication management; Charging management; Charging architecture and principles

SA WG5

3GPP Series : 32 , OAM&P and Charging

4.3.2.1

5.4.4a UE MM Core Network Capability handling

The UE MM Core Network Capability is split into the S1 UE network capability (mostly for E-UTRAN access related core network parameters) and the UE 5GMM Core Network Capability (mostly to include other UE capabilities related to 5GCN or interworking with EPS) as defined in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47] and contains non radio-related capabilities, e.g. the NAS security algorithms, etc. The S1 UE network capability is transferred between all CN nodes at AMF to AMF, AMF to MME, MME to MME, and MME to AMF changes. The UE 5GMM Core Network Capability is transferred only at AMF to AMF changes. In order to ensure that the UE MM Core Network Capability information stored in the AMF is up to date (e.g. to handle the situation when the USIM is moved into a different device while out of coverage, and the old device did not send the Detach message; and the cases of inter-RAT Registration Area Update), the UE shall send the UE MM Core Network Capability information to the AMF during the Initial Registration and Mobility Registration Update procedure within the NAS message. The AMF shall store always the latest UE MM Core Network Capability received from the UE. Any UE MM Core Network Capability that an AMF receives from an old AMF/MME is replaced when the UE provides the UE MM Core Network Capability with Registration signalling. If the UE's UE MM Core Network Capability information changes (in either CM-CONNECTED or in CM-IDLE state), the UE shall perform a Mobility Registration Update procedure when it next returns to NG-RAN coverage. See clause 4.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. The UE shall indicate in the UE 5GMM Core Network Capability if the UE supports: - Attach in EPC with Request type "Handover" in PDN CONNECTIVITY Request message (clause 5.3.2.1 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [26]). - EPC NAS. - SMS over NAS. - LCS. - 5G SRVCC from NG-RAN to UTRAN, as specified in TS 23.216[ Single Radio Voice Call Continuity (SRVCC); Stage 2 ] [88]. - Radio Capabilities Signalling optimisation (RACS). - Network Slice-Specific Authentication and Authorization. - Network Slice Replacement as described in clause 5.15.19. - Parameters in Supported Network Behaviour for 5G CIoT as described in clause 5.31.2. - Receiving WUS Assistance Information (E-UTRA) see clause 5.4.9. - Paging Subgrouping Support Indication (NR) see clause 5.4.12. - CAG, see clause 5.30.3.3. - CAG with validity information (if UE supports CAG), see clause 5.30.3.3. - Subscription-based restrictions to simultaneous registration of network slices (see clause 5.15.12). - Support of NSAG (see clause 5.15.14). - Partial Network Slice support in a RA (see clause 5.15.17). - Minimization of Service Interruption (MINT), as described in clause 5.40. - Equivalent SNPNs (see clause 5.30.2.11). - Unavailability Period Support, as described in clause 5.4.1.4. - Support for network reconnection due to RAN timing synchronization status change, see clause 5.3.4.4. - UE Configuration of network-controlled Slice Usage Policy (see clause 5.15.15.2). - Temporarily available network slices (see clause 5.15.16). - Support of S-NSSAI location availability information, as described in clause 5.15.18.2. If a UE operating two or more USIMs, supports and intends to use one or more Multi-USIM features (see clause 5.38) in a PLMN for a USIM, it shall indicate in the UE 5GMM Core Network Capability for this USIM in this PLMN that it supports these one or more Multi-USIM features with the following indications: - Connection Release Supported. - Paging Cause Indication for Voice Service Supported. - Reject Paging Request Supported. - Paging Restriction Supported. Otherwise, the UE with the capabilities of Multi-USIM features but does not intend to use them shall not indicate support of these one or more Multi-USIM features. A UE not operating two or more USIMs shall indicate the Multi-USIM features are not supported. NOTE: It is not necessary for a UE operating two or more USIMs to use Multi-USIM features with all USIMs.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.4.4a

6.5.2.6 Abnormal cases on the network side

The following abnormal cases can be identified: a) No PDN connection with the linked EPS bearer identity activated: If the linked EPS bearer identity included in the PDN DISCONNECT REQUEST message does not belong to the default EPS bearer context of an established PDN connection, the MME shall reply with a PDN DISCONNECT REJECT message with ESM cause #43 "invalid EPS bearer identity". b) PDN DISCONNECT REQUEST message received from a UE which is in a location where the PLMN is not allowed to operate If the MME determines that the UE is in a location where the PLMN is not allowed to operate, the MME discards the message.

3GPP TS 24.301

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

CT WG1

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

6.5.2.6

17.7.12 RAI AVP

The RAI AVP (AVP Code 909) is of type UTF8String, and contains the Routing Area Identity of the SGSN where the UE is registered. RAI use and structure is specified in 3GPP TS 23.003[ Numbering, addressing and identification ] [40]. Its value shall be encoded as a UTF-8 string on either 11 (if the MNC contains two digits) or 12 (if the MNC contains three digits) octets as follows: - The MCC shall be encoded first using three UTF-8 characters on three octets, each character representing a decimal digit starting with the first MCC digit. - Then, the MNC shall be encoded as either two or three UTF-8 characters on two or three octets, each character representing a decimal digit starting with the first MNC digit. - The Location Area Code (LAC) is encoded next using four UTF-8 characters on four octets, each character representing a hexadecimal digit of the LAC which is two binary octets long. - The Routing Area Code (RAC) is encoded last using two UTF-8 characters on two octets, each character representing a hexadecimal digit of the RAC which is one binary octet long. NOTE: As an example, a RAI with the following information: MCC=123, MNC=45, LAC=41655(0xA2C1) and RAC=10(0x0A) is encoded within the RAI AVP as a UTF-8 string of "12345A2C10A".

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

14.2 Detection of Bearer Context Mismatch

Bearer Context mismatch can be detected by a receiving GTP-C entity in the following cases: - when at least one dedicated bearer context in the request message is unknown; or - when at least one dedicated bearer context is missing in the request message in comparison to the bearer contexts stored; or - when receiving a response message indicating that one of the dedicated bearer context(s) was unknown, by using the cause code "Context not found" at the Bearer Context level. See also clause 8.4. The Modify Bearer Request/Response and the Modify Access Bearer Request/Response in particular enables an easy detection of bearer contexts mismatch since all the bearer contexts, either of the PDN connection for a Modify Bearer Request/Response or of all the UE's PDN connections for a Modify Access Bearer Request/Response, need to be included in the messages.

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

14.2

6.1.3.3.2 MS initiated PDP Context Modification accepted by the network

In order to initiate the procedure, the MS sends the MODIFY PDP CONTEXT REQUEST message to the network, enters the state PDP-MODIFY-PENDING and starts timer T3381. The message may contain the requested new QoS and/or the TFT and the requested LLC SAPI (used in A/Gb mode). If the selected Bearer Control Mode is 'MS/NW' and the MS wants to modify the QoS, it shall include a TFT with packet filter(s), or if no packet filters are proposed to be either added, replaced or deleted, it shall set TFT operation code to "No TFT operation" and include packet filter identifier(s) in the Packet filter identifier parameter in the parameters list to indicate which packet filter(s) in the TFT is associated with the QoS change. If the TFT information element is included in the MODIFY PDP CONTEXT REQUEST message and packet filters are proposed to be added, the MS shall allocate packet filter identifier(s) for all packet filters to be added to the TFT. The MS shall allocate packet filter identifier value s which are currently not allocated to any existing packet filter of the TFT. If a PDP context is associated with a TFT containing packet filters established by both the MS and the network, the only parameters in the QoS profile of that PDP context the MS is allowed to modify are the bitrate parameters. Upon receipt of the MODIFY PDP CONTEXT REQUEST message, the network may reply with the MODIFY PDP CONTEXT ACCEPT message in order to accept the context modification. The reply message may contain the negotiated QoS and the radio priority level based on the new QoS profile and the negotiated LLC SAPI that shall be used in A/Gb mode by the logical link. Upon receipt of the MODIFY PDP CONTEXT ACCEPT message, the MS shall stop the timer T3381. If the offered QoS parameters received from the network differs from the QoS requested by the MS, the MS shall either accept the negotiated QoS or initiate the PDP context deactivation procedure. If a modification of QoS is requested by the MS, which the network can not accept, being unable to provide the requested QoS, it should maintain the QoS negotiated as previously negotiated or propose a new QoS. That means that the network should not reject the MS initiated PDP context modification request due to the unavailability of the QoS. If the MS requested a value for a QoS parameter that is not within the range specified by 3GPP TS 23.107[ Quality of Service (QoS) concept and architecture ] [81], the network should negotiate the parameter to a value that lies within the specified range.

3GPP TS 24.008

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

CT WG1

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

6.1.3.3.2

4.1 Composition of the Location Area Identification (LAI)

The Location Area Identification shall be composed as shown in figure 3: Figure 3: Structure of Location Area Identification The LAI is composed of the following elements: - Mobile Country Code (MCC) identifies the country in which the GSM PLMN is located. The value of the MCC is the same as the three digit MCC contained in international mobile subscriber identity (IMSI); - Mobile Network Code (MNC) is a code identifying the GSM PLMN in that country. The MNC takes the same value as the two or three digit MNC contained in IMSI; - Location Area Code (LAC) is a fixed length code (of 2 octets) identifying a location area within a PLMN. This part of the location area identification can be coded using a full hexadecimal representation except for the following reserved hexadecimal values: 0000, and FFFE. These reserved values are used in some special cases when no valid LAI exists in the MS (see 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [5], 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [27] and 3GPP TS 51.011[ Specification of the Subscriber Identity Module - Mobile Equipment (SIM-ME) interface ] [9]).

3GPP TS 23.003

Numbering, addressing and identification

CT WG4

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

4.1

6.27.1 Description

5G positioning services aims to support verticals and applications with positioning accuracies better than 10 meters, thus more accurate than the ones of TS 22.071[ Location Services (LCS); Service description; Stage 1 ] [24] for LCS. High accuracy positioning is characterized by ambitious system requirements for positioning accuracy in many verticals and applications, including regulatory needs. In Location-Based-Services and eHealth, higher accuracy is instrumental to new services and applications, both outdoor and indoor. For example, on the factory floor, it is important to locate assets and moving objects such as forklifts, or parts to be assembled. Similar needs exist in transportation and logistics, for example rail, road and use of UAVs. In some road user cases, UE's supporting V2X application(s) are also applicable to such needs. In cases such as guided vehicles (e.g. industry, UAVs) and positioning of objects involved in safety-related functions, availability needs to be very high. Mission Critical Organizations require mission critical services to have accurate positioning such that first responders can be located at all times during normal and critical operations, indoors as well as outdoors. The level of positioning accuracy (and other KPIs) required is much more stringent than that required by local and regional regulatory requirements for commercial 5G users.

3GPP TS 22.261

Service requirements for the 5G system

SA WG1

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

6.27.1

5.27.1.8 Exposure of Time Synchronization

5G System supports time synchronization service that can be activated and deactivated by AF. Exposure of time synchronization comprises the following capabilities: - The AF may learn 5GS and/or UE availability and capabilities for time synchronization service. - The AF controls activation and deactivation of the time synchronization service for the target UE(s). - The AF may subscribe to time synchronization service status for the target UE(s). The AF may use the service-specific parameters to control the time synchronization service for targeted UE(s). These parameters are specified in clause 4.15.9.3 and 4.15.9.4 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] for (g)PTP-based and 5G access stratum-based time synchronization services, respectively. The AF may subscribe for 5GS and/or UE availability and capabilities for time synchronization service. The AF indicates in the request the DNN, S-NSSAI, and in addition the AF may indicate a list of UE identities or group identity to limit the subscription only to corresponding UEs. If the AF does not indicate DNN, S-NSSAI, the NEF determines the DNN, S-NSSAI based on the AF Identifier. The TSCTSF (directly or via NEF) exposes the 5GS and/or UE availability and capabilities for synchronization service to the AF as described in clause 4.15.9.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. The exposed information includes the list of user plane node identities, the list of UE identities and may include the supported capabilities for (g)PTP time synchronization service per user plane node and UE. The AF request to control the (g)PTP time synchronization service is sent to the TSCTSF (directly or via NEF). The request is targeted to a set of AF-sessions that are associated with the exposure of UE availability and capabilities for synchronization service. The AF may request to use a specific PTP instance type when requesting the (g)PTP-based time synchronization distribution method (IEEE Std 1588 [126] or IEEE Std 802.1AS [104] operation (i.e. as a Boundary Clock, peer-to-peer Transparent Clock, or end-to-end Transparent Clock or as a PTP relay instance)). The request to control the (g)PTP time synchronization service may contain other service parameters as specified in Table 4.15.9.3-1 in clause 4.15.9.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. The AF may request to use the 5G access stratum as a time synchronization distribution method. In this case, the time source is provided by the 5GS. 5G-AN provides the 5GS time to the UE via 3GPP radio access; UE/DS-TT may provide 5G access stratum timing information to end stations using implementation specific means. The request to control the 5G access stratum time distribution (including the parameters such AF requests may contain) is described in clause 4.15.9.4 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. The AF or NEF selects the TSCTSF as specified in clause 6.3.24. The AF request may include a time synchronization error budget (see also clause 5.27.1.9). The time synchronization error budget defines an upper bound for time synchronization errors introduced by 5GS. The AF uses the procedure for configuring the (g)PTP instance in 5GS as described in clause 4.15.9.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] and uses the procedure for providing the 5G access stratum time distribution as described in clause 4.15.9.4 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] for the UEs. The TSCTSF uses the Time Synchronization parameters (Table 4.15.9.3-1 in TS 23.502[ Procedures for the 5G System (5GS) ] [3]) as received from the AF (directly or via NEF) to control the (g)PTP time synchronization service. When IEEE Std 1588 [126] or IEEE Std 802.1AS [104] operation have been selected, the TSCTSF determines the necessary (g)PTP parameters to activate and control the service in DS-TT(s) and NW-TTs. For this purpose, the TSCTSF uses the PMIC or UMIC to manage the IEEE Std 1588 [126] or IEEE Std 802.1AS [104] operation in the DS-TT(s) or NW-TTs, respectively (see clause 5.27.1.4). The TSCTSF may indicate whether it can support the service or not as per the requested acceptance criteria (e.g. based on the known timing synchronization status attribute thresholds also pre-configured at gNB) and provide notification when there is a service status update if the AF subscribes to service status updates (see also clause 5.27.1.12). The TSCTSF uses the Time Synchronization parameters (Table 4.15.9.4-1 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]) as received from the AF (directly or via NEF) to control the 5G access stratum time synchronization distribution as described in clause 4.15.9.4 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. For handling (g)PTP traffic, the PCF, according to PCC rule authorization, chooses a 5QI and dynamically set the PDB and/or MDBV according to requirements for (g)PTP protocol. The PCF provides the SMF with a PCC rule generated based on the AF request to control the (g)PTP time synchronization service. The SMF may take the information in the PCC rule to modify a PDU Session to create or modify or release a QoS Flow for transmitting the (g)PTP messages. The PCF acknowledges the policy request to the TSCTSF. The TSCTSF may report the result of the time synchronization request to the AF (directly or via NEF). The AF may provide a temporal validity condition to the TSCTSF (directly or via NEF) when the AF activates or modifies the time synchronization service. Temporal validity condition contains the start-time and stop-time (in absolute time value) attributes that describe the time period when the time synchronization service is active for the targeted AF sessions. The TSCTSF manages the temporal validity condition as described in clauses 4.15.9.3 and 4.15.9.4 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. The AF may provide clock quality detail level and clock quality acceptance criteria to the TSCTSF (directly or via NEF) when the AF activates or modifies the time synchronization service. For ASTI based time synchronization services, the TSCTSF provides the clock quality reporting control information to AMF (see also clause 5.27.1.12). The AF may provide a requested coverage area for the time synchronization service to the TSCTSF (directly or via NEF) when the AF activates or modifies the time synchronization service. The requested coverage area defines a spatial validity condition for the service using a geographical area (e.g. a civic address or shapes), or a list of Tracking Area Identities (TAIs).

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.27.1.8

16a.4.1 AAR Command

The AAR command, defined in Diameter NASREQ (IETF RFC 7155 [120]), is indicated by the Command-Code field set to 265 and the ‘R’ bit set in the Command Flags field. It may be sent by the GGSN to a Diameter server, during Primary PDP Context activation only, in order to request user authentication and authorization. In the case of P-GW, the AAR may be sent upon reception of an initial access request (e.g. Create Session Request or Proxy Binding Update) message for a given APN to request user authentication and authorization. The relevant AVPs that are of use for the Gi/Sgi interface are detailed in the ABNF description below. Other valid AVPs for this command are not used for Gi/Sgi purposes and should be ignored by the receiver or processed according to the relevant specifications. The bold marked AVPs in the message format indicate optional AVPs for Gi/Sgi, or modified existing AVPs. For Sgi, some of the optional 3GPP vendor-specific AVPs listed in the message format below are not applicable. See table 9a in subclause 16a.5 to see the list of vendor-specific AVPs that are applicable to the GGSN and the P-GW. Message Format: <AA-Request> ::= < Diameter Header: 265, REQ, PXY > < Session-Id > { Auth-Application-Id } { Origin-Host } { Origin-Realm } { Destination-Realm } { Auth-Request-Type } [ Destination-Host ] [ NAS-Port ] [ NAS-Port-Id ] [ NAS-Port-Type ] [ Origin-State-Id ] [ Port-Limit ] [ User-Name ] [ User-Password ] [ Service-Type ] [ Authorization-Lifetime ] [ Auth-Grace-Period ] [ Auth-Session-State ] [ Callback-Number ] [ Called-Station-Id ] [ Calling-Station-Id ] [ Originating-Line-Info ] [ Connect-Info ] [ CHAP-Auth ] [ CHAP-Challenge ] * [ Framed-Compression ] [ Framed-Interface-Id ] [ Framed-IP-Address ] * [ Framed-IPv6-Prefix ] * [ Delegated-IPv6-Prefix ] [ Framed-IP-Netmask ] [ Framed-MTU ] [ Framed-Protocol ] * [ Login-IP-Host ] * [ Login-IPv6-Host ] [ Login-LAT-Group ] [ Login-LAT-Node ] [ Login-LAT-Port ] [ Login-LAT-Service ] * [ Tunneling ] * [ Proxy-Info ] * [ Route-Record ] [ 3GPP-IMSI] [ External-Identifier] [ 3GPP-Charging-ID ] [ 3GPP-PDP-Type ] [ 3GPP-CG-Address ] [ 3GPP-GPRS-Negotiated-QoS-Profile ] [ 3GPP-SGSN-Address ] [ 3GPP-GGSN-Address ] [ 3GPP-IMSI-MCC-MNC ] [ 3GPP-GGSN-MCC-MNC ] [ 3GPP-NSAPI ] [ 3GPP-Selection-Mode ] [ 3GPP-Charging-Characteristics ] [ 3GPP-CG-IPv6-Address ] [ 3GPP-SGSN-IPv6-Address ] [ 3GPP-GGSN-IPv6-Address ] [ 3GPP-SGSN-MCC-MNC ] [ 3GPP-User-Location-Info ] [ 3GPP-RAT-Type ] [ 3GPP-CAMEL-Charging-Info ] [ 3GPP-Negotiated-DSCP ] [ 3GPP-Allocate-IP-Type ] [ TWAN-Identifier ] [ 3GPP-UE-Local-IP-Address ] [ 3GPP-UE-Source-Port ] * [ AVP ]

3GPP TS 29.061

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

CT WG3

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

16a.4.1

D.3 Process automation D.3.0 General

Process automation has much in common with factory automation (see clause D.2). Instead of discrete products (cars, chocolate bars, etc.), process automation addresses the production of bulk products such as petrol and reactive gases. In contrast to factory automation, motion control is of limited or no importance. Typical end-to-end latencies are 50 ms. User-experienced data rates, communication service availability, and connection density vary noticeably between applications. Below, we describe one emerging use case (remote control via mobile computational units, clause D.3.1) and a contemporary use case (monitoring, clause D.3.2). Note that automation fieldbuses (see clause D.2.0) are also used in process automation.

3GPP TS 22.261

Service requirements for the 5G system

SA WG1

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

D.3

5.31.13 Paging for Enhanced Coverage

Support of UEs in E-UTRA Enhanced Coverage is specified in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [30]. Whenever N2 is released and Paging Assistance Data for CE capable UE is available for the UE, the NG-RAN sends it to the AMF as described in clause 4.2.6 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. The AMF stores the received Paging Assistance Data for CE capable UE and then the AMF includes it in every subsequent Paging message for all NG-RAN nodes selected by the AMF for paging. If Enhanced Coverage is restricted for the UE as described in clause 5.31.12, the AMF sends the Enhanced Coverage Restriction parameter as defined in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [34]. NOTE: Only the NG-RAN node which cell ID is included in the Paging Assistance Data considers the assistance data.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.31.13

8.4.1.2.9 Enhanced Downlink Control Channel Performance Requirement Type A - 4 Tx Antenna Port with Non-Colliding CRS Dominant Interferer

The purpose of this test is to verify the Enhanced Downlink Control Channel Performance Requirement Type A for PDCCH/PCFICH with 4 transmit antennas for the case of dominant interferer with the non-colliding CRS pattern and applying interference model defined in clause B.7.1. For the parameters specified in Table 8.4.1-1 and Table 8.4.1.2.9-1, the average probability of a missed downlink scheduling grant (Pm-dsg) shall be below the specified value in Table 8.4.1.2.9-2. In Table 8.4.1.2.9-1, Cell 1 is the serving cell, and Cell 2 and Cell 3 are the aggressor cells. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1, Cell 2 and Cell 3, respectively. The CRS assistance information [7] is provided and includes information on Cell 2 and Cell 3. Table 8.4.1.2.8-1: Test Parameters for PDCCH/PCFICH Table 8.4.1.2.9-2: Minimum Performance for PDCCH/PCFICH for Enhanced Downlink Control Channel Performance Requirement Type A

3GPP TS 36.101

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

RAN4

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

8.4.1.2.9

6.3.2.4 Network-requested PDU session modification procedure not accepted by the UE

Upon receipt of a PDU SESSION MODIFICATION COMMAND message and a PDU session ID, using the NAS transport procedure as specified in subclause 5.4.5, if the UE rejects the PDU SESSION MODIFICATION COMMAND message, the UE shall create a PDU SESSION MODIFICATION COMMAND REJECT message. If the PDU SESSION MODIFICATION COMMAND message contains the PTI value allocated in the UE-requested PDU session modification procedure, the UE shall stop the timer T3581. The UE should ensure that the PTI value assigned to this procedure is not released immediately. NOTE 1: The way to achieve this is implementation dependent. For example, the UE can ensure that the PTI value assigned to this procedure is not released during the time equal to or greater than the default value of timer T3591. While the PTI value is not released, the UE regards any received PDU SESSION MODIFICATION COMMAND message with the same PTI value as a network retransmission (see subclause 7.3.1). The UE shall set the 5GSM cause IE of the PDU SESSION MODIFICATION COMMAND REJECT message to indicate the reason for rejecting the PDU session modification. The 5GSM cause IE typically indicates one of the following 5GSM cause values: #26 insufficient resources; #44 semantic error in packet filter(s); #45 syntactical error in packet filter(s); #83 semantic error in the QoS operation; or #84 syntactical error in the QoS operation. If the selected SSC mode of the PDU session is "SSC mode 3" and the PDU SESSION MODIFICATION COMMAND messages includes 5GSM cause #39 "reactivation requested", while the UE does not have sufficient resources for initiating the PDU session establishment procedure as specified in subclause 6.4.1 then the UE shall set cause IE to #26 "insufficient resources". If the PDU SESSION MODIFICATION COMMAND message includes a request to add a new authorized QoS rule, or a request to modify the authorized QoS rules, or both, and the UE decides to reject the request due to e.g. the supported number of authorized QoS rules or number of packet filters associated with a PDU session having reached the maximum number, then the UE shall set the 5GSM cause IE to #26 "insufficient resources". NOTE 2: The maximum number of supported authorized QoS rules or packet filters associated with a PDU session is implementation specific. If the PDU SESSION MODIFICATION COMMAND message includes a request to add a new authorized QoS flow description, or a request to modify the authorized QoS flow descriptions, or both and the UE decides to reject the request due to e.g. the supported number of authorized QoS flow descriptions, then the UE shall set the 5GSM cause IE to #26 "insufficient resources". NOTE 3: The maximum number of supported authorized QoS flow descriptions associated with a PDU session is implementation specific. If the PDU SESSION MODIFICATION COMMAND message includes the Authorized QoS rules IE, the UE shall process the QoS rules sequentially starting with the first QoS rule. The UE shall check the QoS rule and the QoS flow description provided in the PDU SESSION MODIFICATION COMMAND message for different types of errors as follows: NOTE 4: If an error is detected in a QoS rule or a QoS flow description which requires rejecting the PDU SESSION MODIFICATION COMMAND message, then the Authorized QoS rules IE, the Authorized QoS flow descriptions IE, the Mapped EPS bearer contexts IE and any other IE (RQ timer value IE, Always-on PDU session indication IE, etc) included in the PDU SESSION MODIFICATION COMMAND message are discarded, if any. a) Semantic errors in QoS operations: 1) When the rule operation is "Modify existing QoS rule and add packet filters", "Modify existing QoS rule and replace all packet filters", "Modify existing QoS rule and delete packet filters" or "Modify existing QoS rule without modifying packet filters" on the default QoS rule and the DQR bit is set to "the QoS rule is not the default QoS rule". 2) When the rule operation is "Modify existing QoS rule and add packet filters", "Modify existing QoS rule and replace all packet filters", "Modify existing QoS rule and delete packet filters" or "Modify existing QoS rule without modifying packet filters" on a QoS rule which is not the default QoS rule and the DQR bit is set to "the QoS rule is the default QoS rule". 3) When the rule operation is "Create new QoS rule" and the DQR bit is set to "the QoS rule is the default QoS rule" when there's already a default QoS rule with different QoS rule identifier. 4) When the rule operation is "Delete existing QoS rule" on the default QoS rule. 5) When the rule operation is "Create new QoS rule", "Modify existing QoS rule and add packet filters", "Modify existing QoS rule and replace all packet filters", "Modify existing QoS rule and delete packet filters ", or "Modify existing QoS rule without modifying packet filters" and two or more QoS rules associated with this PDU session would have identical precedence values, and the UE is not in NB-N1 mode. 6) When the rule operation is "Modify existing QoS rule and delete packet filters", the QoS rule is a QoS rule of a PDU session of IPv4, IPv6, IPv4v6 or Ethernet PDU session type, and the packet filter list in the resultant QoS rule is empty. 7) When the rule operation is "Create new QoS rule", there is already an existing QoS rule with the same QoS rule identifier and the UE is not in NB-N1 mode. 8) When the rule operation is "Modify existing QoS rule and add packet filters", "Modify existing QoS rule and replace all packet filters", "Modify existing QoS rule and delete packet filters" or "Modify existing QoS rule without modifying packet filters", the associated QoS rule does not exist and the UE is not in NB-N1 mode. 9) When the rule operation is different than "Delete existing QoS rule", the DQR bit of the QoS rule is set to "the QoS rule is not the default QoS rule" and the UE is in NB-N1 mode. 10) When the rule operation is "Create new QoS rule", the DQR bit is set to "the QoS rule is not the default QoS rule", and the PDU session type of the PDU session is "Unstructured". 11) When the rule operation is "Delete existing QoS rule" and there is no existing QoS rule with the same QoS rule identifier. 12) When the flow description operation is "Create new QoS flow description", there is already an existing QoS flow description with the same QoS flow identifier and the UE is not in NB-N1 mode. 13) When the flow description operation is "Modify existing QoS flow description", the associated QoS flow description does not exist and the UE is not in NB-N1 mode. 14) When the flow description operation is "Delete existing QoS flow description" and there is no existing QoS flow description with the same QoS flow identifier. 15) When the flow description operation is different than "Delete existing QoS flow description", the QFI is not the same as the QFI of the default QoS rule and the UE is in NB-N1 mode. 16) When the flow description operation is "Create new QoS flow description" or "Modify existing QoS flow description", the QFI associated with the QoS flow description is not the same as the QFI of the default QoS rule, and the PDU session type of the PDU session is "Unstructured". 17) When the rule operation is "Modify existing QoS rule and add packet filters", the "packet filter list" field contains a match-all packet filter, the resultant QoS rule is the default QoS rule and there is already an existing match-all packet filter associated with the default QoS rule. 18) When the rule operation is "Create new QoS rule" and the DQR bit is set to "the QoS rule is not the default QoS rule", or the rule operation is "Modify existing QoS rule and add packet filters" on a QoS rule which is not the default QoS rule or "Modify existing QoS rule and replace all packet filters" on a QoS rule which is not the default QoS rule, and one match-all packet filter is to be associated with the resultant QoS rule. In case 4, the UE shall initiate a PDU session release procedure by sending a PDU SESSION RELEASE REQUEST message with 5GSM cause #83 "semantic error in the QoS operation". In case 5, if the old QoS rule (i.e. the QoS rule that existed before the PDU SESSION MODIFICATION COMMAND message was received) is not the default QoS rule, the UE shall not diagnose an error, shall further process the new request and, if it was processed successfully, shall delete the old QoS rule which has identical precedence value. Furthermore, after sending the PDU SESSION MODIFICATION COMPLETE for the ongoing PDU session modification procedure, the UE shall send a PDU SESSION MODIFICATION REQUEST message with 5GSM cause #83 "semantic error in the QoS operation" to delete the QoS rule. In case 5, if the old QoS rule (i.e. the QoS rule that existed before the PDU SESSION MODIFICATION COMMAND message was received) is the default QoS rule, the UE shall initiate a PDU session release procedure by sending a PDU SESSION RELEASE REQUEST message with 5GSM cause #83 "semantic error in the QoS operation". In case 6, if the QoS rule is not the default QoS rule, after sending the PDU SESSION MODIFICATION COMPLETE for the ongoing PDU session modification procedure, the UE shall send a PDU SESSION MODIFICATION REQUEST message with 5GSM cause #83 "semantic error in the QoS operation" to delete the QoS rule. In case 6, if the QoS rule is the default QoS rule, the UE shall initiate a PDU session release procedure by sending a PDU SESSION RELEASE REQUEST message with 5GSM cause #83 "semantic error in the QoS operation". In case 7, if the existing QoS rule is not the default QoS rule and the DQR bit of the new QoS rule is set to "the QoS rule is not the default QoS rule", the UE shall not diagnose an error, further process the create request and, if it was processed successfully, delete the old QoS rule (i.e. the QoS rule that existed when case 7 was detected). If the existing QoS rule is the default QoS rule or the DQR bit of the new QoS rule is set to "the QoS rule is the default QoS rule", the UE shall reject the PDU SESSION MODIFICATION COMMAND message with 5GSM cause #83 "semantic error in the QoS operation". In case 9 or case 10, after sending the PDU SESSION MODIFICATION COMPLETE for the ongoing PDU session modification procedure, the UE shall send a PDU SESSION MODIFICATION REQUEST message with 5GSM cause #83 "semantic error in the QoS operation" to delete the QoS rule. In case 11, the UE shall not diagnose an error, further process the delete request and, if it was processed successfully, consider the respective QoS rule as successfully deleted. In case 12, the UE shall not diagnose an error, further process the create request and, if it was processed successfully, delete the old QoS flow description (i.e. the QoS flow description that existed when case 12 was detected). In case 14, the UE shall not diagnose an error, further process the delete request and, if it was processed successfully, consider the respective QoS flow description as successfully deleted. In case 15 or case 16, after sending the PDU SESSION MODIFICATION COMPLETE for the ongoing PDU session modification procedure, the UE shall send a PDU SESSION MODIFICATION REQUEST message with 5GSM cause #83 "semantic error in the QoS operation" to delete the QoS flow description. Otherwise, the UE shall reject the PDU SESSION MODIFICATION COMMAND message with 5GSM cause #83 "semantic error in the QoS operation". b) Syntactical errors in QoS operations: 1) When the rule operation is "Create new QoS rule", "Modify existing QoS rule and add packet filters", "Modify existing QoS rule and replace all packet filters" or "Modify existing QoS rule and delete packet filters", the PDU session type of the PDU session is IPv4, IPv6, IPv4v6 or Ethernet PDU session type, and the packet filter list in the QoS rule is empty. 2) When the rule operation is "Delete existing QoS rule" or "Modify existing QoS rule without modifying packet filters" with a non-empty packet filter list in the QoS rule. 3) When the rule operation is "Modify existing QoS rule and delete packet filters" and the packet filter to be deleted does not exist in the original QoS rule. 4) Void. 5) When there are other types of syntactical errors in the coding of the Authorized QoS rules IE or the Authorized QoS flow descriptions IE, such as: a mismatch between the number of packet filters subfield and the number of packet filters in the packet filter list when the rule operation is "delete existing QoS rule" or "create new QoS rule", or the number of packet filters subfield is larger than the maximum possible number of packet filters in the packet filter list (i.e., there is no QoS rule precedence subfield included in the QoS rule IE), the QoS Rule Identifier is set to "no QoS rule identifier assigned" when the rule operation is not "delete existing QoS rule", or the QoS flow identifier is set to "no QoS flow identifier assigned" when the flow description operation is not "Delete existing QoS flow description". 6) When the rule operation is "Modify existing QoS rule and add packet filters" or "Modify existing QoS rule and replace all packet filters", the DQR bit is set to "the QoS rule is the default QoS rule", the PDU session type of the PDU session is "Unstructured", and the packet filter list in the QoS rule is not empty. 7) When, the A) rule operation is "Create new QoS rule", "Modify existing QoS rule and add packet filters", "Modify existing QoS rule and replace all packet filters", "Modify existing QoS rule and delete packet filters" or "Modify existing QoS rule without modifying packet filters", there is no QoS flow description with a QFI corresponding to the QFI of the resulting QoS rule and the UE determines, by using the QoS rule’s QFI as the 5QI, that there is a resulting QoS rule for a GBR QoS flow (as described in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8] table 5.7.4-1). B) flow description operation is "Delete existing QoS flow description", and the UE determines, by using the QoS rule’s QFI as the 5QI, that there is a resulting QoS rule for a GBR QoS flow (as described in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8] table 5.7.4-1) with a QFI corresponding to the QFI of the QoS flow description that is deleted (i.e. there is no associated QoS flow description with the same QFI). 8) When the flow description operation is "Create new QoS flow description" or "Modify existing QoS flow description", and the UE determines that there is a QoS flow description of a GBR QoS flow (as described in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8] table 5.7.4-1) which lacks at least one of the mandatory parameters (i.e., GFBR uplink, GFBR downlink, MFBR uplink and MFBR downlink). If the QoS flow description does not include a 5QI, the UE determines this by using the QFI as the 5QI, In case 3 the UE shall not diagnose an error, further process the deletion request and, if no error according to items c and d was detected, consider the respective packet filter as successfully deleted. In case 6, after completion of the PDU session modification procedure, the UE shall send a PDU SESSION MODIFICATION REQUEST message with 5GSM cause #84 "syntactical error in the QoS operations" to delete all the packet filters for the default QoS rule. In case 7, if the Authorized QoS rules IE contains at least one other valid QoS rule, the UE shall not diagnose an error and shall further process the request, if no error according to items c and d was detected. After completion of the PDU session modification procedure, if the resulting QoS rule for a GBR QoS flow which has no QoS flow description is the default QoS rule, the UE shall initiate a PDU session release procedure by sending a PDU SESSION RELEASE REQUEST message with 5GSM cause #84 "syntactical error in the QoS operation". Otherwise, the UE shall delete the QoS rule for which no corresponding QoS flow description is available and initiate UE-requested PDU session modification procedure with 5GSM cause #84 "syntactical error in the QoS operation" to delete the QoS rule for which it has deleted. In case 8, if the default QoS rule is associated with the QoS flow description which lacks at least one of the mandatory parameters, the UE shall initiate a PDU session release procedure by sending a PDU SESSION RELEASE REQUEST message with 5GSM cause #84 "syntactical error in the QoS operation". Otherwise, if the Authorized QoS rules IE contains at least one other valid QoS rule or the QoS flow description IE contains at least one other valid QoS flow description, the UE shall not diagnose an error and shall further process the request, if no error according to items c and d was detected. After completion of the PDU session modification procedure, the UE shall delete the QoS flow description which lacks at least one of the mandatory parameters and the associated QoS rule(s), if any, and initiate UE-requested PDU session modification procedure with 5GSM cause #84 "syntactical error in the QoS operation" to delete the QoS flow description and the associated QoS rule(s), if any, which it has deleted. Otherwise the UE shall reject the PDU SESSION MODIFICATION COMMAND message with 5GSM cause #84 "syntactical error in the QoS operation". NOTE 5: It is not considered an error if the UE determines that after processing all QoS operations on QoS rules and QoS flow descriptions there is a QoS flow description that is not associated with any QoS rule and the UE is not in NB-N1 mode. NOTE 5a: An implementation that strictly follows QoS rule operation as defined in subclause 9.11.4.13 might not detect case 2). c) Semantic errors in packet filters: 1) When a packet filter consists of conflicting packet filter components which would render the packet filter ineffective, i.e. no IP packet will ever fit this packet filter. How the UE determines a semantic error in a packet filter is outside the scope of the present document. The UE shall reject the PDU SESSION MODIFICATION COMMAND message with 5GSM cause #44 "semantic error in packet filter(s)". d) Syntactical errors in packet filters: 1) When the rule operation is "Create new QoS rule", "Modify existing QoS rule and add packet filters" or "Modify existing QoS rule and replace all packet filters", and two or more packet filters in the resultant QoS rule would have identical packet filter identifiers. 2) When there are other types of syntactical errors in the coding of packet filters, such as the use of a reserved value for a packet filter component identifier. In case 1, if two or more packet filters with identical packet filter identifiers are contained in the PDU SESSION MODIFICATION COMMAND message, the UE shall reject the PDU SESSION MODIFICATION COMMAND with 5GSM cause #45 "syntactical errors in packet filter(s)". Otherwise, the UE shall not diagnose an error, further process the PDU SESSION MODIFICATION COMMAND message and, if it was processed successfully, replace the old packet filter with the new packet filter which have the identical packet filter identifiers. Otherwise the UE shall reject the PDU SESSION MODIFICATION COMMAND message with 5GSM cause #45 "syntactical errors in packet filter(s)". If: a) the UE detects errors in QoS rules that require to delete at least one QoS rule as described above which requires sending a PDU SESSION MODIFICATION REQUEST message to delete the erroneous mapped EPS bearer contexts; and b) optionally, if the UE detects different errors in the mapped EPS bearer contexts as described in subclause 6.3.2.3 which requires sending a PDU SESSION MODIFICATION REQUEST message to delete the erroneous QoS rules; the UE, after sending the PDU SESSION MODIFICATION COMPLETE message for the ongoing PDU session modification procedure, may send a single PDU SESSION MODIFICATION REQUEST message to delete the erroneous QoS rules, and optionally to delete the erroneous mapped EPS bearer contexts. The UE shall include a 5GSM cause IE in the PDU SESSION MODIFICATION REQUEST message. NOTE 6: The 5GSM cause to use cannot be different from #41 "semantic error in the TFT operation", #42 "syntactical error in the TFT operation", #44 "semantic error in packet filter(s)", #45 "syntactical errors in packet filter(s)", #83 "semantic error in the QoS operation", #84 "syntactical error in the QoS operation", or #85 "Invalid mapped EPS bearer identity". The selection of a 5GSM cause is up to UE implementation. The UE shall transport the PDU SESSION MODIFICATION COMMAND REJECT message and the PDU session ID, using the NAS transport procedure as specified in subclause 5.4.5. Upon receipt of a PDU SESSION MODIFICATION COMMAND REJECT message with 5GSM cause value in state PDU SESSION MODIFICATION PENDING, the SMF shall stop timer T3591, enter the state PDU SESSION ACTIVE and abort the PDU session modification procedure.

3GPP TS 24.501

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

CT WG1

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

6.3.2.4

4.2.2 User Plane

In MR-DC, from a UE perspective, three bearer types exist: MCG bearer, SCG bearer and split bearer. These three bearer types are depicted in Figure 4.2.2-1 for MR-DC with EPC (EN-DC) and in Figure 4.2.2-2 for MR-DC with 5GC (NGEN-DC, NE-DC and NR-DC). In E-UTRA connected to EPC, if the UE supports EN-DC, regardless whether EN-DC is configured or not, the network can configure either E-UTRA PDCP or NR PDCP for MN terminated MCG bearers while NR PDCP is always used for all other bearers. Change from E-UTRA to NR PDCP or vice-versa can be performed via a reconfiguration procedure (with or without handover), either using release and add of the DRBs or using the full configuration option. In MR-DC with 5GC, NR PDCP is always used for all bearer types. In NGEN-DC, E-UTRA RLC/MAC is used in the MN while NR RLC/MAC is used in the SN. In NE-DC, NR RLC/MAC is used in the MN while E-UTRA RLC/MAC is used in the SN. In NR-DC, NR RLC/MAC is used in both MN and SN. Figure 4.2.2-1: Radio Protocol Architecture for MCG, SCG and split bearers from a UE perspective in MR-DC with EPC (EN-DC) Figure 4.2.2-2: Radio Protocol Architecture for MCG, SCG and split bearers from a UE perspective in MR-DC with 5GC (NGEN-DC, NE-DC and NR-DC). From a network perspective, each bearer (MCG, SCG and split bearer) can be terminated either in MN or in SN. Network side protocol termination options are shown in Figure 4.2.2-3 for MR-DC with EPC (EN-DC) and in Figure 4.2.2-4 for MR-DC with 5GC (NGEN-DC, NE-DC and NR-DC). NOTE 1: Even if only SCG bearers are configured for a UE, for SRB1 and SRB2 the logical channels are always configured at least in the MCG, i.e. this is still an MR-DC configuration and a PCell always exists. NOTE 2: If only MCG bearers are configured for a UE, i.e. there is no SCG, this is still considered an MR-DC configuration, as long as at least one of the bearers is terminated in the SN. Figure 4.2.2-3: Network side protocol termination options for MCG, SCG and split bearers in MR-DC with EPC (EN-DC). Figure 4.2.2-4: Network side protocol termination options for MCG, SCG and split bearers in MR-DC with 5GC (NGEN-DC, NE-DC and NR-DC).

3GPP TS 37.340

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

RAN2

3GPP Series : 37 , Multiple radio access technology aspects

4.2.2

4.14.2.9 Number of attempted reconfigurations of LWIP DRB

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

3GPP TS 32.425

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

SA WG5

3GPP Series : 32 , OAM&P and Charging

4.14.2.9

9.11.2.15 Service-level-AA payload type

The purpose of the Service-level-AA payload type information element is to indicates type of payload included in the Service-level-AA payload information element. The Service-level-AA payload type information element is coded as shown in figure 9.11.2.15.1 and table 9.11.2.15.1. The Service-level-AA payload type information element is a type 4 information element with length of 3 octets. Figure 9.11.2.15.1: Service-level-AA payload type information element Table 9.11.2.15.1: Service-level-AA payload type 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.15

5.6.1.6 Abnormal cases in the UE

The following abnormal cases can be identified: a) Access barred because of access class barring, EAB, ACDC or NAS signalling connection establishment rejected by the network without "Extended wait time" received from lower layers In WB-S1 mode, if the service request procedure is started in response to a paging request from the network, access class barring, EAB or ACDC is not applicable. In NB-S1 mode, if the service request procedure is started in response to a paging request from the network, access barring is not applicable. If the trigger for the service request procedure is the response to a paging request from the network and the NAS signalling connection establishment is rejected by the network, the service request procedure shall not be started. The UE stays in the current serving cell and applies normal cell reselection process. During an implementation dependent time period, the service request procedure may be started when access for "terminating calls" is granted or upon a cell change. If the service request was initiated for CS fallback and the access is barred for "mobile originating CS fallback" (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]) and the lower layer indicates "the barring is due to CSFB specific access barring information", the service request procedure shall not be started. The UE stays in the current serving cell and applies normal cell reselection process. The service request procedure may be started if it is still necessary, i.e. when access for "mobile originating CS fallback" is granted or because of a cell change. If the service request was initiated for CS fallback and a CS fallback cancellation request was not received and the access is barred for "mobile originating CS fallback" (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]) and the lower layer does not indicate "the barring is due to CSFB specific access barring information", the UE shall attempt to select GERAN or UTRAN radio access technology. If the UE finds a suitable GERAN or UTRAN cell, it then proceeds with the appropriate MM and CC specific procedures and the EMM sublayer shall not indicate the abort of the service request procedure to the MM sublayer. Otherwise the EMM sublayer shall indicate the abort of the service request procedure to the MM sublayer. If the service request was initiated for 1xCS fallback and the access is barred for "originating calls" (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]), the UE shall select cdma2000® 1x radio access technology. The UE then proceeds with appropriate cdma2000® 1x CS procedures. If the lower layer indicated the access was barred because of access class barring for "originating calls" (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]) and if: - the service request is initiated due to a request from upper layers for user plane radio resources, and the MO MMTEL voice call is started, the MO MMTEL video call is started or the MO SMSoIP is started; - the service request is initiated due to a mobile originated SMS over NAS or SMS over S102; or - the service request is initiated due to a request from upper layers for user plane radio resources, ACDC is applicable to the request and the UE supports ACDC. then the service request procedure shall be started. The call type used shall be per annex D of this document. NOTE 1: If more than one of MO MMTEL voice call is started, MO MMTEL video call is started or MO SMSoIP is started conditions are satisfied, it is left to UE implementation to determine the call type based on annex D of this document. If access is barred for a certain ACDC category (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]), and if the upper layers request user plane radio resources for a higher ACDC category and the UE supports ACDC, then the service request procedure shall be started. If an access request for an uncategorized application is barred due to ACDC (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]), and if the upper layers request user plane radio resources for a certain ACDC category and the UE supports ACDC, then the service request procedure shall be started. Otherwise: - In WB-S1 mode, if access is barred for "originating calls" (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]), the service request procedure shall not be started. The UE stays in the current serving cell and applies normal cell reselection process. The service request procedure may be started if it is still necessary when access for "originating calls" is granted or because of a cell change. - In NB-S1 mode, if access is barred for "originating calls" (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]), the service request procedure shall not be started. The UE stays in the current serving cell and applies normal cell reselection process. Further UE behaviour is implementation specific, e.g. the service request procedure is started again after an implementation dependent time; or In NB-S1 mode, if access is barred for "originating calls" (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]), and a request for an exceptional event is received from the upper layers, then the service request procedure shall be started. NOTE 2: In NB-S1 mode, the EMM layer cannot receive the access barring alleviation indication from the lower layers (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]). b) Lower layer failure or release of the NAS signalling connection without "Extended wait time", without "Extended wait time CP data", and without redirection indication received from lower layers before the service request procedure is completed (see clause 5.6.1.4) or before SERVICE REJECT message is received If the service request was initiated for CS fallback and a CS fallback cancellation request was not received, the UE shall attempt to select GERAN or UTRAN radio access technology. If the UE finds a suitable GERAN or UTRAN cell, it then proceeds with the appropriate MM and CC specific procedures and the EMM sublayer shall not indicate the abort of the service request procedure to the MM sublayer. Otherwise the EMM sublayer shall indicate the abort of the service request procedure to the MM sublayer, and the UE shall also set the EPS update status to EU2 NOT UPDATED and enter the state EMM-REGISTERED.ATTEMPTING-TO-UPDATE. If the service request was initiated for CS fallback and a CS fallback cancellation request was received, the UE shall set the EPS update status to EU2 NOT UPDATED and enter the state EMM-REGISTERED.ATTEMPTING-TO-UPDATE. If the service request was initiated for 1xCS fallback, the UE shall either: - attempt to select cdma2000® 1x radio access technology and proceed with appropriate cdma2000® 1x CS procedures. If the UE fails to select cdma2000® 1x radio access technology, the UE shall set the EPS update status to EU2 NOT UPDATED and enter the state EMM-REGISTERED.ATTEMPTING-TO-UPDATE; or - set the EPS update status to EU2 NOT UPDATED and enter the state EMM-REGISTERED.ATTEMPTING-TO-UPDATE, and perform cell selection according to 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [21]. If the service request was not initiated for CS fallback or 1xCS fallback, the UE shall enter state EMM-REGISTERED. The UE shall abort the service request procedure, stop timer T3417, T3417ext or T3417ext-mt and locally release any resources allocated for the service request procedure. For case o) in clause 5.6.1.1 the UE may retry the service request procedure a certain number of times (maximum re-attempts 5). c) T3417 expired The UE shall enter the state EMM-REGISTERED. If the UE triggered the service request procedure in EMM-IDLE mode in order to obtain packet services, then the EMM sublayer shall increment the service request attempt counter, abort the procedure and release locally any resources allocated for the service request procedure. The service request counter shall not be incremented, if: - the service request procedure is initiated to establish a PDN connection for emergency bearer services; - the UE has a PDN connection for emergency bearer services established; - the UE is a UE configured to use AC11 – 15 in selected PLMN; - the service request is initiated in response to paging from the network; or - the UE in NB-S1 mode is requested by the upper layer to transmit user data related to an exceptional event and the UE is allowed to use exception data reporting (see the ExceptionDataReportingAllowed leaf of the NAS configuration MO in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] or the USIM file EFNASCONFIG in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]). If the service request attempt counter is greater than or equal to 5, the UE shall start timer T3325 (see 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13]). Additionally if the service request was initiated for an "originating MMTEL voice" call type or an "originating MMTEL video" call type, a notification that the service request was not accepted and that timer T3325 is running shall be provided to the upper layers. NOTE 3: This can result in the upper layers requesting establishment of a CS voice call (if not already attempted in the CS domain), or other implementation specific mechanisms (see 3GPP TS 24.173[ IMS Multimedia telephony communication service and supplementary services; Stage 3 ] [13E]). The UE shall not attempt service request until expiry of timer T3325 unless: - the service request is initiated in response to paging from the network; - the UE is a UE configured to use AC11 – 15 in selected PLMN; - the service request is initiated to establish a PDN connection for emergency bearer services; - the UE has a PDN connection for emergency bearer services established; - the UE is registered in a new PLMN; or - the UE in NB-S1 mode is requested by the upper layer to transmit user data related to an exceptional event and the UE is allowed to use exception data reporting (see the ExceptionDataReportingAllowed leaf of the NAS configuration MO in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] or the USIM file EFNASCONFIG in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]). If the service request for "originating MMTEL voice" call type was triggered while T3325 is running, a notification that the service request was not accepted and that timer T3325 is running shall be provided to the upper layers. NOTE 4: This can result in the upper layers requesting establishment of a CS voice call (if not already attempted in the CS domain), or other implementation specific mechanisms (see 3GPP TS 24.173[ IMS Multimedia telephony communication service and supplementary services; Stage 3 ] [13E]). NOTE 5: The NAS signalling connection can also be released if the UE deems that the network has failed the authentication check as specified in clause 5.4.2.7. If the UE triggered the service request procedure in order to obtain services other than packet services from EMM-IDLE mode, then the EMM sublayer shall abort the procedure and release locally any resources allocated for the service request procedure. If the UE triggered the service request procedure in EMM-CONNECTED mode, the EMM sublayer shall abort the procedure and consider the service request procedure with "active" flag set or the 1xCS fallback procedure as failed. The UE shall stay in EMM-CONNECTED mode. d) T3417ext or T3417ext-mt expired If a CS fallback cancellation request was not received, the UE shall attempt to select GERAN or UTRAN radio access technology. If the UE finds a suitable GERAN or UTRAN cell, it then proceeds with the appropriate MM and CC specific procedures and the EMM sublayer shall not indicate the abort of the service request procedure to the MM sublayer. Otherwise the EMM sublayer shall indicate the abort of the service request procedure to the MM sublayer, and the UE shall also set the EPS update status to EU2 NOT UPDATED and enter the state EMM-REGISTERED.ATTEMPTING-TO-UPDATE. If a CS fallback cancellation request was received the UE shall set the EPS update status to EU2 NOT UPDATED and enter the state EMM-REGISTERED.ATTEMPTING-TO-UPDATE. e) SERVICE REJECT received, other EMM cause values than those treated in clause 5.6.1.5, and cases of EMM cause values #22, #25, #31 and #78 if considered as abnormal cases according to clause 5.6.1.5. If the service request was initiated for CS fallback and a CS fallback cancellation request was not received, the UE shall attempt to select GERAN or UTRAN radio access technology. If the UE finds a suitable GERAN or UTRAN cell, it then proceeds with the appropriate MM and CC specific procedures and the EMM sublayer shall not indicate the abort of the service request procedure to the MM sublayer. Otherwise the EMM sublayer shall indicate the abort of the service request procedure to the MM sublayer, and the UE shall also set the EPS update status to EU2 NOT UPDATED and enter the state EMM-REGISTERED.ATTEMPTING-TO-UPDATE. If the service request was initiated for CS fallback and a CS fallback cancellation request was received, the UE shall set the EPS update status to EU2 NOT UPDATED and enter the state EMM-REGISTERED.ATTEMPTING-TO-UPDATE. If the service request was initiated for 1xCS fallback, the UE shall select cdma2000® 1x radio access technology. The UE then proceeds with appropriate cdma2000® 1x CS procedures. If the service request was initiated for 1xCS fallback and the UE has dual Rx/Tx configuration and supports enhanced 1xCS fallback, then upon entering EMM-IDLE mode the UE shall perform tracking area updating procedure. If the service request was not initiated for CS fallback or 1xCS fallback, the UE shall enter state EMM-REGISTERED. The UE shall abort the service request procedure, stop timer T3417, T3417ext or T3417ext-mt and locally release any resources allocated for the service request procedure. f) Tracking area updating procedure is triggered The UE shall abort the service request procedure, stop timer T3417, T3417ext or T3417ext-mt if running and perform the tracking area updating procedure. The "active" flag or "signalling active" flag shall be set in the TRACKING AREA UPDATE REQUEST message as specified in clause 5.5.3.2.2. If the service request was initiated for CS fallback or 1xCS fallback, and the CS fallback cancellation request was not received, the UE shall send the EXTENDED SERVICE REQUEST message to the MME by using the existing NAS signalling connection after the completion of the tracking area updating procedure. If the TRACKING AREA UPDATE ACCEPT message includes a UE radio capability ID deletion indication IE set to "Network-assigned UE radio capability IDs deletion requested", the UE shall not initiate a new tracking area update procedure, but shall proceed with sending the EXTENDED SERVICE REQUEST message by using the existing NAS signalling connection after the completion of the tracking area updating procedure. g) Switch off If the UE is in state EMM-SERVICE-REQUEST-INITIATED at switch off, the detach procedure shall be performed. h) Detach procedure collision EPS detach containing detach type "re-attach required": If the UE receives a DETACH REQUEST message from the network in state EMM-SERVICE-REQUEST-INITIATED, the UE shall take the following actions: - If the service request was initiated for CS fallback, the UE shall attempt to select GERAN or UTRAN radio access technology. If the UE finds a suitable GERAN or UTRAN cell, it then proceeds with the appropriate MM, CC and GMM specific procedures and the EMM sublayer shall not indicate the abort of the service request procedure to the MM sublayer. Otherwise the EMM sublayer shall indicate the abort of the service request procedure to the MM sublayer; - If the service request was initiated for 1xCS fallback, the UE shall attempt to select cdma2000® 1x radio access technology. The UE then proceeds with appropriate cdma2000® 1x CS procedures; or - If the service request was not initiated for CS fallback or 1xCS fallback, the detach procedure shall be progressed and the service request procedure shall be aborted. EPS detach containing detach type "re-attach not required": If the UE receives a DETACH REQUEST message from the network in state EMM-SERVICE-REQUEST-INITIATED, the UE shall take the following actions: - If the DETACH REQUEST message contains an EMM cause other than #2 "IMSI unknown in HSS" or no EMM cause IE, the detach procedure shall be progressed and the service request procedure shall be aborted. Additionally, if the service request was initiated for CS fallback or 1xCS fallback, but not for CS fallback for emergency call or 1xCS fallback for emergency call, the EMM sublayer shall indicate to the MM sublayer or the cdma2000® upper layers that the CS fallback or 1xCS fallback procedure has failed; or If the DETACH REQUEST message contains EMM cause #2 "IMSI unknown in HSS", the UE will follow the procedure as described below for the detach type "IMSI detach". EPS detach containing detach type "IMSI detach": If the UE receives a DETACH REQUEST message from the network in state EMM-SERVICE-REQUEST-INITIATED, the UE shall take the following actions: - if the service request was initiated for SMS over NAS or CS fallback, but not for CS fallback for emergency call, the UE shall abort the service request procedure and progress the detach procedure; or - otherwise the UE shall progress both procedures. i) Transmission failure of SERVICE REQUEST, CONTROL PLANE SERVICE REQUEST or EXTENDED SERVICE REQUEST message indication with TAI change from lower layers If the current TAI is not in the TAI list, the service request procedure shall be aborted to perform the tracking area updating procedure. The "active" flag or "signalling active" flag shall be set in the TRACKING AREA UPDATE REQUEST message as specified in clause 5.5.3.2.2. If the service request was initiated for CS fallback or 1xCS fallback, and the CS fallback cancellation request was not received, the UE shall send the EXTENDED SERVICE REQUEST message to the MME by using the existing NAS signalling connection after the completion of the tracking area updating procedure. If the current TAI is still part of the TAI list, the UE shall restart the service request procedure unless the service request procedure is initiated for case p) or q) in clause 5.6.1.1. For case p) and q) in clause 5.6.1.1 the UE shall abort the service request procedure, enter state EMM-REGISTERED, stop timer T3417, and locally release the NAS signalling connection and any resources allocated for the service request procedure. j) Transmission failure of SERVICE REQUEST, CONTROL PLANE SERVICE REQUEST or EXTENDED SERVICE REQUEST message indication without TAI change from lower layers The UE shall restart the service request procedure unless the service request procedure is initiated for case p) or q) in clause 5.6.1.1. For case p) and q) in clause 5.6.1.1 the UE shall abort the service request procedure, enter state EMM-REGISTERED, stop timer T3417, and locally release the NAS signalling connection and any resources allocated for the service request procedure. k) Default or dedicated bearer set up failure If the lower layers indicate a failure to set up a radio bearer, the UE shall locally deactivate the EPS bearer as described in clause 6.4.4.6. l) "Extended wait time" from the lower layers The UE shall abort the service request procedure, enter state EMM-REGISTERED, and stop timer T3417, T3417ext or T3417ext-mt if still running. If the EXTENDED SERVICE REQUEST or CONTROL PLANE SERVICE REQUEST message contained the low priority indicator set to "MS is configured for NAS signalling low priority", the UE shall start timer T3346 with the "Extended wait time" value. If the SERVICE REQUEST message was sent by a UE configured for NAS signalling low priority, the UE shall start timer T3346 with the "Extended wait time" value. If the EXTENDED SERVICE REQUEST or CONTROL PLANE SERVICE REQUEST message did not contain the low priority indicator set to "MS is configured for NAS signalling low priority" or if the SERVICE REQUEST message was sent by a UE not configured for NAS signalling low priority, the UE is operating in NB-S1 mode and the UE is not a UE configured to use AC11 – 15 in selected PLMN, then the UE shall start timer T3346 with the "Extended wait time" value. In other cases the UE shall ignore the "Extended wait time". The UE stays in the current serving cell and applies normal cell reselection process. The service request procedure is started, if still necessary, when timer T3346 expires or is stopped. If the service request was initiated for CS fallback and a CS fallback cancellation request was not received, the UE in CS/PS mode 1 of operation shall attempt to select GERAN or UTRAN radio access technology. If the UE finds a suitable GERAN or UTRAN cell, it then proceeds with the appropriate MM and CC specific procedures and the EMM sublayer shall not indicate the abort of the service request procedure to the MM sublayer. Otherwise the EMM sublayer shall indicate the abort of the service request procedure to the MM sublayer. NOTE 5: If the UE disables the E-UTRA capability, then subsequent mobile terminating calls could fail. If the service request was initiated for CS fallback for emergency call and a CS fallback cancellation request was not received, the UE may attempt to select GERAN or UTRAN radio access technology. It then proceeds with appropriate MM and CC specific procedures. The EMM sublayer shall not indicate the abort of the service request procedure to the MM sublayer. If the service request was initiated for 1xCS fallback, the UE shall select cdma2000® 1x radio access technology. The UE then proceeds with appropriate cdma2000® 1x CS procedures. If the service request was initiated for 1xCS fallback for emergency call, the UE may select cdma2000® 1x radio access technology. The UE then proceeds with appropriate cdma2000® 1x CS procedures. If the service request was initiated due to a request from the SMS entity to send an SMS and timer T3246 is not running, the UE, if operating in CS/PS mode 1 of operation, may select GERAN or UTRAN radio access technology. It then proceeds with the appropriate MM procedure. NOTE 6: If the UE disables the E-UTRA capability, then subsequent mobile terminating calls could fail. la) "Extended wait time CP data" from the lower layers The UE shall abort the service request procedure for transfer of user data via the control plane, enter state EMM-REGISTERED, and stop timer T3417 if still running. If the UE is operating in NB-S1 mode and supports the timer T3448, the UE shall start the timer T3448 with the "Extended wait time CP data" value. If the UE is operating in NB-S1 mode and does not support the timer T3448, the UE shall start the timer T3346 with the "Extended wait time CP data" value. In other cases the UE shall ignore the "Extended wait time CP data". The UE stays in the current serving cell and applies normal cell reselection process. The service request procedure for transfer of user data via the control plane is started, if still necessary, when the timer T3448 expires or is stopped. m) Timer T3346 is running The UE shall not start the service request procedure unless: - the UE receives a paging; - the UE is a UE configured to use AC11 – 15 in selected PLMN; - the UE has a PDN connection for emergency bearer services established or is establishing a PDN connection for emergency bearer services; - the UE is requested by the upper layer for a CS fallback for emergency call or a 1xCS fallback for emergency call; - the UE has a PDN connection established without the NAS signalling low priority indication or is establishing a PDN connection without the NAS signalling low priority indication and if the timer T3346 was started due to rejection of a NAS request message (e.g. ATTACH REQUEST, TRACKING AREA UPDATE REQUEST, EXTENDED SERVICE REQUEST or CONTROL PLANE SERVICE REQUEST) which contained the low priority indicator set to "MS is configured for NAS signalling low priority"; - the UE in NB-S1 mode is requested by the upper layer to transmit user data related to an exceptional event and: - the UE is allowed to use exception data reporting (see the ExceptionDataReportingAllowed leaf of the NAS configuration MO in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] or the USIM file EFNASCONFIG in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]); and - timer T3346 was not started when NAS signalling connection was established with RRC establishment cause set to "MO exception data"; or - the MUSIM UE is in EMM-CONNECTED mode and requests the network to release the NAS signalling connection (see case p in clause 5.6.1.1). If the UE is in EMM-IDLE mode, the UE stays in the current serving cell and applies normal cell reselection process. The service request procedure is started, if still necessary, when timer T3346 expires or is stopped. Upon upper layer's request for a mobile originated CS fallback which is not for emergency call, the UE in CS/PS mode 1 of operation shall attempt to select GERAN or UTRAN radio access technology. If the UE finds a suitable GERAN or UTRAN cell, it then proceeds with the appropriate MM and CC specific procedures and the EMM sublayer shall not indicate the abort of the service request procedure to the MM sublayer. Otherwise the EMM sublayer shall indicate the abort of the service request procedure to the MM sublayer. NOTE 7: If the UE disables the E-UTRA capability, then subsequent mobile terminating calls could fail. Upon upper layer's request for a CS fallback for emergency call, the UE may select GERAN or UTRAN radio access technology. It then proceeds with appropriate MM and CC specific procedures. The EMM sublayer shall not indicate the abort of the service request procedure to the MM sublayer. Upon a request from the SMS entity to send an SMS and timer T3246 is not running, the UE, if operating in CS/PS mode 1 of operation, may select GERAN or UTRAN radio access technology. It then proceeds with the appropriate MM procedure. NOTE 8: If the UE disables the E-UTRA capability, then subsequent mobile terminating calls could fail. Upon upper layer's request for a mobile originated 1x CS fallback which is not for emergency call, the UE shall select cdma2000® 1x radio access technology. The UE then proceeds with appropriate cdma2000® 1x CS call procedures. Upon upper layer's request for a 1xCS fallback for emergency call, the UE may select cdma2000® 1x radio access technology. The UE then proceeds with appropriate cdma2000® 1x CS call procedures. If the service request procedure was triggered for an MO MMTEL voice call is started, a notification that the service request procedure was not initiated due to congestion shall be provided to the upper layers. NOTE 9: This can result in the upper layers requesting establishment of the originating voice call on an alternative manner e.g. requesting establishment of a CS voice call (see 3GPP TS 24.173[ IMS Multimedia telephony communication service and supplementary services; Stage 3 ] [13E]). n) Failure to find a suitable GERAN or UTRAN cell, after release of the NAS signalling connection without "Extended wait time" and with redirection indication received from lower layers when the service request was initiated for CS fallback The EMM sublayer shall indicate the abort of the service request procedure to the MM sublayer, and the UE shall also set the EPS update status to EU2 NOT UPDATED and enter the state EMM-REGISTERED.ATTEMPTING-TO-UPDATE. The UE shall abort the service request procedure, stop timer T3417ext or T3417ext-mt and locally release any resources allocated for the service request procedure. o) Timer T3448 is running The UE in EMM-IDLE mode shall not initiate the service request procedure for transport of user data via the control plane unless: - the UE is a UE configured to use AC11 – 15 in selected PLMN; - the UE which is only using EPS services with control plane CIoT EPS optimization received a paging; or - the UE in NB-S1 mode is requested by the upper layer to transmit user data related to an exceptional event and the UE is allowed to use exception data reporting (see the ExceptionDataReportingAllowed leaf of the NAS configuration MO in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] or the USIM file EFNASCONFIG in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]). The UE stays in the current serving cell and applies the normal cell reselection process. p) Timer T3447 is running The UE shall not start any service request procedure unless: - the UE receives a paging; - the UE is a UE configured to use AC11 – 15 in selected PLMN; - the UE has a PDN connection for emergency bearer services established or is establishing a PDN connection for emergency bearer services; or - the MUSIM UE is in EMM-CONNECTED mode and requests the network to release the NAS signalling connection (see case p in clause 5.6.1.1). The UE stays in the current serving cell and applies the normal cell reselection process. The service request procedure is started, if still necessary, when timer T3447 expires.

3GPP TS 24.301

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

CT WG1

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

5.6.1.6

4.4.2 Handling of EPS security contexts 4.4.2.1 General

The security parameters for authentication, integrity protection and ciphering are tied together in an EPS security context and identified by a key set identifier for E-UTRAN (eKSI). The relationship between the security parameters is defined in 3GPP TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [19]. Before security can be activated, the MME and the UE need to establish an EPS security context. Usually, the EPS security context is created as the result of an EPS authentication procedure between MME and UE. Alternatively: - during inter-system handover from A/Gb mode to S1 mode or from Iu mode to S1 mode, the MME and the UE derive a mapped EPS security context from a UMTS security context that has been established while the UE was in A/Gb mode or Iu mode; or - during CS to PS SRVCC handover from A/Gb mode to S1 mode or from Iu mode to S1 mode, the MME and the UE derive a mapped EPS security context from a CS UMTS security context that has been established while the UE was in A/Gb mode or Iu mode. The EPS security context is taken into use by the UE and the MME, when the MME initiates a security mode control procedure or during the inter-system handover procedure from A/Gb mode to S1 mode or Iu mode to S1 mode. The EPS security context which has been taken into use by the network most recently is called current EPS security context. This current EPS security context can be of type native or mapped, i.e. originating from a native EPS security context or mapped EPS security context. The key set identifier eKSI is assigned by the MME either during the EPS authentication procedure or, for the mapped EPS security context, during the inter-system handover procedure. The eKSI consists of a value and a type of security context parameter indicating whether an EPS security context is a native EPS security context or a mapped EPS security context. When the EPS security context is a native EPS security context, the eKSI has the value of KSIASME, and when the current EPS security context is of type mapped, the eKSI has the value of KSISGSN. The EPS security context which is indicated by an eKSI can be taken into use to establish the secure exchange of NAS messages when a new NAS signalling connection is established without executing a new EPS authentication procedure (see clause 4.4.2.3) or when the MME initiates a security mode control procedure. For this purpose the initial NAS messages (i.e. ATTACH REQUEST, TRACKING AREA UPDATE REQUEST, DETACH REQUEST, SERVICE REQUEST, EXTENDED SERVICE REQUEST, and CONTROL PLANE SERVICE REQUEST) and the SECURITY MODE COMMAND message contain an eKSI in the NAS key set identifier IE or the value part of eKSI in the KSI and sequence number IE indicating the current EPS security context used to integrity protect the NAS message. In the present document, when the UE is required to delete an eKSI, the UE shall set the eKSI to the value "no key is available" and consider also the associated keys KASME or K'ASME, EPS NAS ciphering key and EPS NAS integrity key invalid (i.e. the EPS security context associated with the eKSI as no longer valid). NOTE: In some specifications the term ciphering key sequence number might be used instead of the term Key Set Identifier (KSI). The UE and the MME need to be able to maintain two EPS security contexts simultaneously, i.e. a current EPS security context and a non-current EPS security context, since: - after an EPS re-authentication, the UE and the MME can have both a current EPS security context and a non-current EPS security context which has not yet been taken into use (i.e. a partial native EPS security context); and - after an inter-system handover from A/Gb mode to S1 mode or Iu mode to S1 mode, the UE and the MME can have both a mapped EPS security context, which is the current EPS security context, and a non-current native EPS security context that was created during a previous access in S1 mode or S101 mode. The number of EPS security contexts that need to be maintained simultaneously by the UE and the MME is limited by the following requirements: - After a successful EPS (re-)authentication, which creates a new partial native EPS security context, the MME and the UE shall delete the non-current EPS security context, if any. - When a partial native EPS security context is taken into use through a security mode control procedure, the MME and the UE shall delete the previously current EPS security context. - When the MME and the UE create an EPS security context using null integrity and null ciphering algorithm during an attach procedure for emergency bearer services, or a tracking area updating procedure for a UE that has a PDN connection for emergency bearer services (see clause 5.4.3.2), the MME and the UE shall delete the previous current EPS security context. The UE shall not update the USIM and non-volatile ME memory with the current EPS security context and shall delete the current EPS security context when the UE is detached from emergency services (e.g. before attaching for normal service). - When a new mapped EPS security context or EPS security context created using null integrity and null ciphering algorithm is taken into use during the inter-system handover from A/Gb mode to S1 mode or Iu mode to S1 mode, the MME and the UE shall not delete the previously current native EPS security context, if any. Instead, the previously current native EPS security context shall become a non-current native EPS security context, and the MME and the UE shall delete any partial native EPS security context. If no previously current native EPS security context exists, the MME and the UE shall not delete the partial native EPS security context, if any. - When the MME and the UE derive a new mapped EPS security context during inter-system handover from A/Gb mode to S1 mode or Iu mode to S1 mode, the MME and the UE shall delete any existing current mapped EPS security context. - When a non-current full native EPS security context is taken into use by a security mode control procedure, then the MME and the UE shall delete the previously current mapped EPS security context. - When the UE or the MME moves from EMM-REGISTERED to EMM-DEREGISTERED state, if the current EPS security context is a mapped EPS security context and a non-current full native EPS security context exists, then the non-current EPS security context shall become the current EPS security context. Furthermore, the UE and the MME shall delete any mapped EPS security context or partial native EPS security context. The UE shall mark the EPS security context on the USIM or in the non-volatile memory as invalid when the UE initiates an attach procedure as described in clause 5.5.1 or when the UE leaves state EMM-DEREGISTERED for any other state except EMM-NULL. The UE shall store the current native EPS security context as specified in annex C and mark it as valid only when the UE enters state EMM-DEREGISTERED from any other state except EMM-NULL or when the UE aborts the attach procedure without having left EMM-DEREGISTERED.

3GPP TS 24.301

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

CT WG1

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

4.4.2

4.7.4.2.2 Network initiated GPRS detach procedure completion by the MS

When receiving the DETACH REQUEST message and the detach type indicates "re-attach required", the MS shall deactivate the PDP context(s), the MBMS context(s) and deactivate the logical link(s), if any. The MS shall stop the timer T3346, if it is running. The MS shall also stop timer(s) T3396, if it is running. The MS shall send a DETACH ACCEPT message to the network and shall enter the state GMM-DEREGISTERED. The MS shall, after the completion of the GPRS detach procedure, initiate a GPRS attach procedure. The MS should also activate PDP context(s) that were originally activated by the MS to replace any previously MS activated PDP context(s). The MS should also perform the procedures needed in order to activate any previously active multicast service(s). NOTE 1: When the detach type indicates "re-attach required", user interaction is necessary in some cases when the MS cannot re-activate the PDP/MBMS context(s) automatically. A GPRS MS operating in MS operation mode A or B in network operation mode I, which receives an DETACH REQUEST message with detach type indicating "re-attach required" or "re-attach not required" and no cause code, is only detached for GPRS services in the network. When receiving the DETACH REQUEST message and the detach type IE indicates "IMSI detach", the MS shall not deactivate the PDP/MBMS contexts. The MS shall set the MM update status to U2 NOT UPDATED. An MS in operation mode A or B in network operation mode I may send a DETACH ACCEPT message to the network, and shall re-attach to non-GPRS service by performing the combined routing area updating procedure according to subclause 4.7.5.2, sending a ROUTING AREA UPDATE REQUEST message with Update type IE indicating "combined RA/LA updating with IMSI attach". An MS in operation mode A that is in an ongoing circuit-switched transaction shall initiate the combined routing area updating after the circuit-switched transaction has been released. An MS in operation mode C, or in MS operation mode A or B in network operation mode II, shall send a DETACH ACCEPT message to the network. If the detach type IE indicates "IMSI detach", or "re-attach required" then the MS shall ignore the cause code if received. If the MS is attached for GPRS and non-GPRS services and the network operates in network operation mode I, then if in the MS the timer T3212 is not already running, the timer T3212 shall be set to its initial value and restarted if: - the detach type IE indicates "re-attach required"; or - the detach type IE indicates "re-attach not required" and no cause code is included. When receiving the DETACH REQUEST message and the detach type IE indicates "re-attach not required" and no cause code, or "re-attach not required" and the cause code is not #2 "IMSI unknown in HLR", the MS shall deactivate the PDP contexts, the MBMS contexts and deactivate the logical link(s), if any. The MS shall then send a DETACH ACCEPT message to the network and shall change state to GMM-DEREGISTERED. If the detach type IE indicates "re-attach not required" and no cause code is included, - the MS shall set the GPRS update status to GU2 NOT UPDATED, delete the GMM parameters P-TMSI, P-TMSI signature, RAI, and GPRS ciphering key sequence number, and start timer T3302. If the MS is operating in MS operation mode C, it may enter the state GMM-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]; otherwise the MS shall enter the state GMM-DEREGISTERED.ATTEMPTING-TO-ATTACH; and - if S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, GUTI, last visited registered TAI, TAI list and KSI, as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when a DETACH REQUEST is received with the no EMM cause included and with detach type set to "re-attach not required". If the detach type IE indicates "re-attach not required" and a cause code is included, then, depending on the received cause code, the MS shall act as follows: # 2 (IMSI unknown in HLR); The MS shall set the update status to U3 ROAMING NOT ALLOWED and shall delete any TMSI, LAI and ciphering key sequence number. The new MM state is MM IDLE. The SIM/USIM shall be considered as invalid for non-GPRS services until switching off or the SIM/USIM is removed. If the message has been successfully integrity checked by the lower layers and the MS maintains a counter for "SIM/USIM considered invalid for non-GPRS services", then the MS shall set this counter to MS implementation-specific maximum value. A GPRS MS operating in MS operation mode A or B in network operation mode I, is still IMSI attached for GPRS services in the network. # 3 (Illegal MS); # 6 (Illegal ME); The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to subclause 4.1.3.2) and shall delete any P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number. The MS shall delete the list of equivalent PLMNs. The new GMM state is GMM-DEREGISTERED.NO-IMSI. The SIM/USIM shall be considered as invalid for GPRS services until switching off or the SIM/USIM is removed. If the message has been successfully integrity checked by the lower layers and the MS maintains a counter for "SIM/USIM considered invalid for GPRS services", then the MS shall set this counter to MS implementation-specific maximum value. A GPRS MS operating in MS operation mode A or B shall in addition set the update status to U3 ROAMING NOT ALLOWED, shall delete any TMSI, LAI and ciphering key sequence number. If the MS is operating in MS operation mode A and an RR connection exists, the MS shall abort the RR connection, unless an emergency call is ongoing. The SIM/USIM shall be considered as invalid also for non-GPRS services until switching off or the SIM/USIM is removed. If the message has been successfully integrity checked by the lower layers and the MS maintains a counter for "SIM/USIM considered invalid for non-GPRS services", then the MS shall set this counter to MS implementation-specific maximum value. If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, GUTI, last visited registered TAI, TAI list and KSI as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when a DETACH REQUEST is received with the EMM cause with the same value and with detach type set to "re-attach not required". NOTE 2: The possibility to configure an MS so that the radio transceiver for a specific radio access technology is not active, although it is implemented in the MS, is out of scope of the present specification. # 7 (GPRS services not allowed); The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to subclause 4.1.3.2) and shall delete any P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number. The SIM/USIM shall be considered as invalid for GPRS services until switching off or the SIM/USIM is removed. The new state is GMM-DEREGISTERED. If the message has been successfully integrity checked by the lower layers and the MS maintains a counter for "SIM/USIM considered invalid for GPRS services", then the MS shall set this counter to MS implementation-specific maximum value. A GPRS MS operating in MS operation mode A or B which is already IMSI attached for CS services is still IMSI attached for CS services in the network. A GPRS MS operating in MS operation mode A or B in network operation mode I shall then proceed with the appropriate MM specific procedure. NOTE 3: Optionally the MS starts the timer T3340 as described in subclause 4.7.1.9. If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, GUTI, last visited registered TAI, TAI list and KSI as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when a DETACH REQUEST is received with the EMM cause with the same value and with detach type set to "re-attach not required". # 8 (GPRS services and non-GPRS services not allowed); The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to subclause 4.1.3.2) and shall delete any P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number. The MS shall delete the list of equivalent PLMNs. The new GMM state is GMM-DEREGISTERED.NO-IMSI. The MS shall set the update status to U3 ROAMING NOT ALLOWED, shall delete any TMSI, LAI and ciphering key sequence number. If the MS is operating in MS operation mode A and an RR connection exists, the MS shall abort the RR connection, unless an emergency call is ongoing. The SIM/USIM shall be considered as invalid for GPRS and non-GPRS services until switching off or the SIM/USIM is removed. If the message has been successfully integrity checked by the lower layers and the MS maintains a counter for "SIM/USIM considered invalid for GPRS services", then the MS shall set this counter to MS implementation-specific maximum value. If the message has been successfully integrity checked by the lower layers and the MS maintains a counter for "SIM/USIM considered invalid for non-GPRS services", then the MS shall set this counter to MS implementation-specific maximum value. NOTE 4: Optionally the MS starts the timer T3340 as described in subclause 4.7.1.9. If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, GUTI, last visited registered TAI, TAI list and KSI as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when a DETACH REQUEST is received with the EMM cause with the same value and with detach type set to "re-attach not required". # 11 (PLMN not allowed); The MS shall delete any RAI or LAI, P-TMSI, P-TMSI signature and GPRS ciphering key sequence number, shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to subclause 4.1.3.2) and shall reset the GPRS attach attempt counter. The MS shall delete the list of equivalent PLMNs. The new GMM state is GMM-DEREGISTERED. The MS shall store the PLMN identity in the "forbidden PLMN list" and if the MS is configured to use timer T3245 (see 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [135] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [112]) then the MS shall start timer T3245 and proceed as described in subclause 4.1.1.6. If the message has been successfully integrity checked by the lower layers and the MS maintains a PLMN-specific attempt counter for that PLMN, then the MS shall set this counter to the MS implementation-specific maximum value. The MS shall start timer T3340 as described in subclause 4.7.1.9. If no RR connection exists, the MS shall perform the following additional actions immediately. If the MS is operating in MS operation mode A and an RR connection exists, the MS shall perform these actions when the RR connection is subsequently released: - A GPRS MS operating in MS operation mode A or B shall set the update status to U3 ROAMING NOT ALLOWED and shall delete any TMSI, LAI and ciphering key sequence number. The new MM state is MM IDLE. - The MS shall perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14]. An MS in GAN mode shall request a PLMN list in GAN (see 3GPP TS 44.318[ None ] [76b]) prior to perform a PLMN selection from this list according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14]. If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, GUTI, last visited registered TAI, TAI list, KSI and attach attempt counter as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when a DETACH REQUEST is received with the EMM cause with the same value and with detach type set to "re-attach not required". # 12 (Location area not allowed); The MS shall delete any RAI, P-TMSI, P-TMSI signature GPRS ciphering key sequence number, shall set the GPRS update status to GU3 ROAMING NOT ALLOWED(and shall store it according to clause 4.1.3.2) and shall reset the GPRS attach attempt counter. The state is changed to GMM-DEREGISTERED.LIMITED-SERVICE. The MS shall store the LAI in the list of "forbidden location areas for regional provision of service". The MS shall start timer T3340 as described in subclause 4.7.1.9. If no RR connection exists, the MS shall perform the following additional actions immediately. If the MS is operating in MS operation mode A and an RR connection exists, the MS shall perform these actions when the RR connection is subsequently released: - If the MS is IMSI attached, the MS shall set the update status to U3 ROAMING NOT ALLOWED, shall delete any TMSI, LAI and ciphering key sequence number and shall reset the location update attempt counter. The new MM state is MM IDLE. - The MS shall perform a cell selection according to 3GPP TS 43.022[ None ] [82] and 3GPP TS 25.304[ None ] [98]. NOTE 5: The cell selection procedure is not applicable for an MS in GAN mode. If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, GUTI, last visited registered TAI, TAI list, KSI and attach attempt counter as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when a DETACH REQUEST is received with the EMM cause with the same value and with detach type set to "re-attach not required". # 13 (Roaming not allowed in this location area); The MS shall delete any RAI, P-TMSI, P-TMSI signature and GPRS ciphering key sequence number, shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to clause 4.1.3.2) and shall reset the GPRS attach attempt counter. The MS shall delete the list of equivalent PLMNs. The state is changed to GMM-DEREGISTERED.LIMITED-SERVICE or optionally to GMM-DEREGISTERED.PLMN-SEARCH. The MS shall store the LAI in the list of "forbidden location areas for roaming". The MS shall start timer T3340 as described in subclause 4.7.1.9. If no RR connection exists, the MS shall perform the following additional actions immediately. If the MS is operating in MS operation mode A and an RR connection exists, the MS shall perform these actions when the RR connection is subsequently released: - If the MS is IMSI attached, the MS shall set the update status to U3 ROAMING NOT ALLOWED, shall delete any TMSI, LAI and ciphering key sequence number and shall reset the location update attempt counter. The new MM state is MM IDLE. - The MS shall perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14]. An MS in GAN mode shall request a PLMN list in GAN (see 3GPP TS 44.318[ None ] [76b]) prior to perform a PLMN selection from this list according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14]. If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, GUTI, last visited registered TAI, TAI list, KSI and attach attempt counter as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when a DETACH REQUEST is received with the EMM cause with the same value and with detach type set to "re-attach not required". # 14 (GPRS services not allowed in this PLMN); The MS shall delete any RAI, P-TMSI, P-TMSI signature, and GPRS ciphering key sequence number stored, shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to subclause 4.1.3.2), shall reset the GPRS attach attempt counter and shall change to state GMM-DEREGISTERED. The MS shall store the PLMN identity in the "forbidden PLMNs for GPRS service" list and if the MS is configured to use timer T3245 (see 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [135] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [112]) then the MS shall start timer T3245 and proceed as described in subclause 4.1.1.6. If the message has been successfully integrity checked by the lower layers and the MS maintains a PLMN-specific PS-attempt counter for that PLMN, then the MS shall set this counter to the MS implementation-specific maximum value. A GPRS MS operating in MS operation mode C shall delete the list of equivalent PLMNs and perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14]. A GPRS MS operating in MS operation mode A or B which is already IMSI attached for CS services is still IMSI attached for CS services in the network. A GPRS MS operating in MS operation mode A or B in network operation mode I shall then proceed with the appropriate MM specific procedure. If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, GUTI, last visited registered TAI, TAI list, KSI and attach attempt counter as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when a DETACH REQUEST is received with the EMM cause with the same value and with detach type set to "re-attach not required". # 15 (No Suitable Cells In Location Area); The MS shall delete any RAI, P-TMSI, P-TMSI signature and GPRS ciphering key sequence number, shall set the GPRS update status to GU3 ROAMING NOT ALLOWED(and shall store it according to clause 4.1.3.2) and shall reset the GPRS attach attempt counter. The state is changed to GMM-DEREGISTERED.LIMITED-SERVICE. The MS shall store the LAI in the list of "forbidden location areas for roaming". The MS shall start timer T3340 as described in subclause 4.7.1.9. If no RR connection exists, the MS shall perform the following additional actions immediately. If the MS is operating in MS operation mode A and an RR connection exists, the MS shall perform these actions when the RR connection is subsequently released: - If the MS is IMSI attached, the MS shall set the update status to U3 ROAMING NOT ALLOWED, shall delete any TMSI, LAI and ciphering key sequence number and shall reset the location update attempt counter. The new MM state is MM IDLE. - The MS shall search for a suitable cell in another location area or a tracking area according to 3GPP TS 43.022[ None ] [82] and 3GPP TS 25.304[ None ] [98] or 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [121]. NOTE 6: The cell selection procedure is not applicable for an MS in GAN mode. If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state and EPS update status, GUTI, last visited registered TAI, TAI list, KSI and attach attempt counter as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when a DETACH REQUEST is received with the EMM cause with the same value and with detach type set to "re-attach not required". # 25 (Not authorized for this CSG) The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and store it according to subclause 4.1.3.2) and shall reset the GPRS attach attempt counter. The state is changed to GMM-DEREGISTERED.LIMITED-SERVICE. If the cell where the MS has received the DETACH REQUEST message is a CSG cell and the CSG ID and associated PLMN identity of the cell are contained in the Allowed CSG list stored in the MS, the MS shall remove the CSG ID and associated PLMN identity from the Allowed CSG list. If the cell where the MS has received the DETACH REQUEST message is a CSG cell and the CSG ID and associated PLMN identity of the cell are contained in the Operator CSG list, the MS shall proceed as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14] subclause 3.1A. The MS shall start timer T3340 as described in subclause 4.7.1.9. If the MS is IMSI attached for non-GPRS services, the MS shall set the update status to U3 ROAMING NOT ALLOWED and shall reset the location update attempt counter. The new MM state is MM IDLE. The MS shall search for a suitable cell according to 3GPP TS 43.022[ None ] [82] and 3GPP TS 25.304[ None ] [98]. If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state and EPS update status, GUTI, last visited registered TAI, TAI list, KSI and attach attempt counter as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when a DETACH REQUEST is received with the EMM cause with the same value and with detach type set to "re-attach not required". NOTE 7: CSG is applicable only for UMTS. Other cause values shall not impact the update status. Further actions of the MS are implementation dependent.

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

9.1.3 QoS considerations

If the sender of IPsec traffic uses DiffServ Code Points (DSCPs) to distinguish different QoS classes, either by copying DSCP from the inner IP header or directly setting the encapsulating IP header's DSCP, the resulting traffic may be reordered to the point where the receiving node's anti-replay check discards the packet. If different DSCPs are used on the encapsulating IP header, then to avoid packet discard under one IKE SA and with the same set of traffic selectors, distinct Child-SAs should be established for each of the traffic classes (using the DSCPs as classifiers) as specified in RFC 4301 [6].

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

9.1.3

5.4.11.8 Support for mobility Forbidden Area and Service Area Restrictions for NR satellite access

Forbidden Area functionality is supported as described in clause 5.3.4.1.1 with the modifications described below: - The AMF and the UE receive the broadcast TAI (if a single TAI is broadcast) or all broadcast TAIs (if multiple TAIs are broadcast) from the NG-RAN as described clause 5.4.11.7. The AMF considers the UE to be in a Forbidden Area if the only received TAI is forbidden or if all received TAIs are forbidden based on subscription data. The UE considers it is in a Forbidden Area if the only received TAI is forbidden, or if all received TAIs are forbidden and is not within a Forbidden Area in the case that at least one broadcast TAI is not forbidden. - If AMF receives multiple TAIs from the NG-RAN and determines that some, but not all of them are forbidden by subscription or by operator policy, the AMF shall send the forbidden TAI(s) to the UE as described in clauses 4.2.2.2 and 4.2.3 in TS 23.502[ Procedures for the 5G System (5GS) ] [3]. The UE stores the TAI(s) in the appropriate Forbidden Area list and removes the TAI(s) from Registration Area if present. Service Area Restrictions functionality is supported as described in clause 5.3.4.1.2 with the modifications described below: - The AMF receives the broadcast TAI (if a single TAI is broadcast) or all broadcast TAIs (if multiple TAIs are broadcast) from the NG-RAN as described clause 5.4.11.7. The AMF provides the UE with Service Area Restrictions which consist of either Allowed Areas or Non-Allowed Areas, as described in clause 5.3.4.1.2. The UE and AMF consider the UE to be in a Non-Allowed Area if none of the broadcast TAIs is Allowed. The UE and AMF consider the UE to be in an Allowed Area if at least one broadcast TAI is allowed.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.4.11.8

5.7.2a.3 Actions related to transmission of ULInformationTransferMRDC message

The UE shall set the contents of the ULInformationTransferMRDC message as follows: 1> if there is a need to transfer MR-DC dedicated information related to NR: 2> set the ul-DCCH-MessageNR to include the NR MR-DC dedicated information to be transferred (e.g., NR RRC MeasurementReport, UEAssistanceInformation, FailureInformation, RRCReconfigurationComplete, MCGFailureInformation, or IABOtherInformation message); 1> else if there is a need to transfer MR-DC dedicated information related to E-UTRA: 2> set the ul-DCCH-MessageEUTRA to include the E-UTRA MR-DC dedicated information to be transferred (e.g., E-UTRA RRC MeasurementReport, or MCGFailureInformation message); 1> submit the ULInformationTransferMRDC message to lower layers for transmission, upon which the procedure ends.

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

5.7.2a.3

17.6.2 AAA Command

The AAA command, defined in Diameter NASREQ (IETF RFC 7155 [120]), is indicated by the Command-Code field set to 265 and the ‘R’ bit cleared in the Command Flags field., It is sent by the BM-SC to the GGSN in response to the AAR command. When the AAA command is used to acknowledge an AAR that activated a Trace Session, the only Gmb specific AVP that shall be included is the 3GPP-IMSI AVP. The relevant AVPs that are of use for the Gmb interface are detailed in the ABNF description below. Other valid AVPs for this command are not used for Gmb purposes and should be ignored by the receiver or processed according to the relevant specifications. The bold marked AVPs in the message format indicate new optional AVPs for Gmb, or modified existing AVPs. Message Format: <AA-Answer> ::= < Diameter Header: 265, PXY > < Session-Id > { Auth-Application-Id } { Origin-Host } { Origin-Realm } [ Result-Code ] [ Experimental-Result ] [ Error-Message ] [ Error-Reporting-Host ] [ Failed-AVP ] * [ Proxy-Info ] [ Alternative-APN ] [ 3GPP-IMSI] [ TMGI ] [ Required-MBMS-Bearer-Capabilities ]

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

4.15.4.3 Exposure of Communication trends from SMF

During Session Management procedures, the SMF may store and update the UE access behaviour trends specified in Table 4.15.4.3-1 and the UE communication trends specified in Table 4.15.4.3-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 session behaviour trends" and/or "UE communication trends", respectively, by invoking Nsmf_EventExposure_Subscribe. Table 4.15.4.3-1: UE session behaviour trends exposed by SMF Table 4.15.4.3-2: UE communication trends

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.15.4.3

5.12 MCH reception

MCH transmission may occur in subframes configured by upper layer for MCCH or MTCH transmission. For each such subframe, upper layer indicates if signallingMCS or dataMCS applies. The transmission of an MCH occurs in a set of subframes defined by PMCH-Config. An MCH Scheduling Information MAC control element is included in the first subframe allocated to the MCH within the MCH scheduling period to indicate the position of each MTCH and unused subframes on the MCH. If pmch-InfoListExt is configured for an MCH, an Extended MCH Scheduling Information MAC control element is included in the first subframe allocated to the corresponding MCH within the MCH scheduling period to indicate the position of each MTCH and unused subframes on the MCH, and to indicate whether MTCH transmission is to be suspended. The MAC entity shall assume that the first scheduled MTCH starts immediately after the MCCH or the MCH Scheduling Information MAC control element or the Extended MCH Scheduling Information MAC control element if the MCCH is not present, and the other scheduled MTCH(s) start immediately after the previous MTCH, at the earliest in the subframe where the previous MTCH stops. When the MAC entity needs to receive MCH, the MAC entity shall: - attempt to decode the TB on the MCH; - if a TB on the MCH has been successfully decoded: - demultiplex the MAC PDU and deliver the MAC SDU(s) to upper layers. When the MAC entity receives the Extended MCH Scheduling Information MAC control element, the MAC entity shall indicate the MTCH(s) to be suspended to the upper layers. NOTE: The MAC entity should continue receiving MCH until the MTCH is removed from the MCCH.

3GPP TS 36.321

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

RAN2

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

5.12

4.7.5.1.4 Normal and periodic routing area updating procedure not accepted by the network

If the routing area updating cannot be accepted, the network sends a ROUTING AREA UPDATE REJECT message to the MS. An MS, which receives a ROUTING AREA UPDATE REJECT message with a reject cause other than GMM cause value #25 or the message is integrity protected, shall stop the timer T3330. If a ROUTING AREA UPDATE REJECT message containing a reject cause other than GMM cause value #25 is received or the message is integrity protected, the MS shall stop any ongoing transmission of user data. If the ROUTING AREA UPDATE REJECT message containing GMM cause value cause #25 was received without integrity protection, then the MS shall discard the message. If the routing area update request is rejected due to general NAS level mobility management congestion control, the network shall set the GMM cause value to #22 "congestion" and assign a back-off timer T3346. The MS shall then take different actions depending on the received reject cause value: # 3 (Illegal MS); # 6 (Illegal ME); The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to subclause 4.1.3.2) and shall delete any P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number. The MS shall consider the SIM/USIM as invalid for GPRS services until switching off or the SIM/USIM is removed. If the message has been successfully integrity checked by the lower layers and the MS maintains a counter for "SIM/USIM considered invalid for GPRS services", then the MS shall set this counter to MS implementation-specific maximum value. The MS shall delete the list of equivalent PLMNs, and shall enter the state GMM-DEREGISTERED.NO-IMSI. If the MS is IMSI attached, the MS shall in addition set the update status to U3 ROAMING NOT ALLOWED, shall delete any TMSI, LAI and ciphering key sequence number. If the MS is operating in MS operation mode A and an RR connection exists, the MS shall abort the RR connection, unless an emergency call is ongoing. The SIM/USIM shall be considered as invalid also for non-GPRS services until switching off or the SIM/USIM is removed or the timer T3245 expires as described in subclause 4.1.1.6. If the MS maintains a counter for "SIM/USIM considered invalid for non-GPRS services", then the MS shall set this counter to MS implementation-specific maximum value. If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, GUTI, last visited registered TAI, TAI list and KSI as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when the tracking area update procedure is rejected with the EMM cause with the same value. NOTE 1: The possibility to configure a MS so that the radio transceiver for a specific radio access technology is not active, although it is implemented in the MS, is out of scope of the present specification. # 7 (GPRS services not allowed); The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to subclause 4.1.3.2.9) and shall delete any P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number. The SIM/USIM shall be considered as invalid for GPRS services until switching off or the SIM/USIM is removed. The MS shall enter the state GMM-DEREGISTERED. If the message has been successfully integrity checked by the lower layers and the MS maintains a counter for "SIM/USIM considered invalid for GPRS services", then the MS shall set this counter to MS implementation-specific maximum value. A GPRS MS operating in MS operation mode A or B which is already IMSI attached for CS services in the network is still IMSI attached for CS services in the network. If the update type is "periodic updating", a GPRS MS operating in MS operation mode A or B in network operation mode I shall then proceed with the appropriate MM specific procedure. NOTE 2: Optionally the MS starts the timer T3340 as described in subclause 4.7.1.9. If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, GUTI, last visited registered TAI, TAI list and KSI as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when the tracking area update procedure is rejected with the EMM cause with the same value. # 8 (GPRS services and non-GPRS services not allowed); The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to subclause .2) and shall delete any P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number. The MS shall delete the list of equivalent PLMNs, and shall enter the GMM state GMM-DEREGISTERED.NO-IMSI. The MS shall set the update status to U3 ROAMING NOT ALLOWED, shall delete any TMSI, LAI and ciphering key sequence number. If the MS is operating in MS operation mode A and an RR connection exists, the MS shall abort the RR connection, unless an emergency call is ongoing. The SIM/USIM shall be considered as invalid for GPRS and non-GPRS services until switching off or the SIM/USIM is removed. If the message has been successfully integrity checked by the lower layers and the MS maintains a counter for "SIM/USIM considered invalid for GPRS services", then the MS shall set this counter to MS implementation-specific maximum value. If the message has been successfully integrity checked by the lower layers and the MS maintains a counter for "SIM/USIM considered invalid for non-GPRS services", then the MS shall set this counter to MS implementation-specific maximum value. NOTE 3: Optionally the MS starts the timer T3340 as described in subclause 4.7.1.9. If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, GUTI, last visited registered TAI, TAI list and KSI as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when the tracking area procedure is rejected with the EMM cause with the same value. # 9 (MS identity cannot be derived by the network); The MS shall set the GPRS update status to GU2 NOT UPDATED (and shall store it according to subclause 4.1.3.2), enter the state GMM-DEREGISTERED.NORMAL-SERVICE, and shall delete any P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number. A GPRS MS operating in MS operation mode A or B which is already IMSI attached for CS services in the network is still IMSI attached for CS services in the network. If the rejected request was not for initiating a PDN connection for emergency bearer services, then - a GPRS MS operating in MS operation mode A in network operation mode I shall proceed with appropriate MM specific procedures. Additionally, the MS shall initiate a normal or combined GPRS attach procedure depending on whether it is in an ongoing circuit-switched transaction. If the MS is in an ongoing circuit-switched transaction, it shall initiate the appropriate MM specific procedure after the circuit-switched transaction has been released. The MM sublayer shall act as in network operation mode II as long as the combined GMM procedures are not successful and no new RA is entered; - if the update type is "periodic updating", a GPRS MS operating in MS operation mode B in network operation mode I shall proceed with appropriate MM specific procedures. Additionally, the MS shall initiate a combined GPRS attach procedure. The MM sublayer shall act as in network operation mode II as long as the combined GMM procedures are not successful and no new RA is entered; - a GPRS MS operating in MS operation mode A or B in network operation mode II which is configured to use CS fallback and SMS over SGs, or SMS over SGs only, and which did not perform a successful generic location updating procedure since the last intersystem change from S1 mode to A/Gb or Iu mode shall proceed with appropriate MM specific procedures. Additionally, a GPRS MS operating in MS operation mode A or B in network operation mode II shall initiate a GPRS attach procedure; and - a GPRS MS operating in MS operation mode A or B in network operation mode II which is not configured to use CS fallback and SMS over SGs, or SMS over SGs only, and a GPRS MS operating in MS operation mode C may subsequently, automatically initiate the GPRS attach procedure. If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, GUTI, last visited registered TAI, TAI list and KSI as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when the tracking area update procedure is rejected with the EMM cause with the same value. # 10 (Implicitly detached); If the update type is "periodic updating", a GPRS MS operating in MS operation mode B in network operation mode I, is IMSI detached for both GPRS and CS services in the network. A GPRS MS operating in MS operation mode A in network operation mode I is detached for GPRS services. If no RR connection exists then the MS is also IMSI detached for the CS services. The MS shall enter the state GMM-DEREGISTERED.NORMAL-SERVICE. If the rejected request was not for initiating a PDN connection for emergency bearer services, then - a GPRS MS operating in MS operation mode A or B in network operation mode II which is configured to use CS fallback and SMS over SGs, or SMS over SGs only, and which did not perform a successful generic location updating procedure since the last intersystem change from S1 mode to A/Gb or Iu mode shall proceed with appropriate MM specific procedures; - regardless of the MS operation mode and the network operation mode, the MS shall then perform a new attach procedure. The MS should also activate PDP context(s) that were originally activated by the MS to replace any previously MS activated PDP context(s). The MS should also perform the procedures needed in order to activate any previously active multicast service(s); and - additionally, a GPRS MS operating in MS operation mode A in network operation mode I which is configured to use CS fallback and SMS over SGs, or SMS over SGs only, and which is in an ongoing circuit-switched transaction shall initiate the appropriate MM specific procedure after the circuit-switched transaction has been released. The MM sublayer shall act as in network operation mode II as long as the combined GMM procedures are not successful and no new RA is entered. If S1 mode is supported in the MS, the MS shall handle the EMM state as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when the tracking area update procedure is rejected with the EMM cause with the same value. NOTE 4: In some cases, user interaction may be required and then the MS cannot activate the PDP and MBMS context(s) automatically. # 11 (PLMN not allowed); The MS shall delete any RAI, P-TMSI, P-TMSI signature and GPRS ciphering key sequence number, shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to subclause 4.1.3.2), shall reset the routing area updating attempt counter, shall delete the list of equivalent PLMNs, and enter the state GMM-DEREGISTERED. The MS shall store the PLMN identity in the "forbidden PLMN list" and if the MS is configured to use timer T3245 (see 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [135] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [112]) then the MS shall start timer T3245 and proceed as described in subclause 4.1.1.6. If the message has been successfully integrity checked by the lower layers and the MS maintains a PLMN-specific attempt counter for that PLMN, then the MS shall set this counter to the MS implementation-specific maximum value. The MS shall start timer T3340 as described in subclause 4.7.1.9. If no RR connection exists, the MS shall perform the following additional actions immediately. If the MS is operating in MS operation mode A and an RR connection exists, the MS shall perform these actions when the RR connection is subsequently released: - If the MS is IMSI attached, the MS shall set the update status to U3 ROAMING NOT ALLOWED and shall delete any TMSI, LAI and ciphering key sequence number and shall reset the location update attempt counter. The new MM state is MM IDLE. - The MS shall perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14]. An MS in GAN mode shall request a PLMN list in GAN (see 3GPP TS 44.318[ None ] [76b]) prior to perform a PLMN selection from this list according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14]. If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, GUTI, last visited registered TAI, TAI list, KSI and tracking area updating attempt counter as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when the tracking area update procedure is rejected with the EMM cause with the same value. # 12 (Location area not allowed); The MS shall delete any RAI, P-TMSI, P-TMSI signature and GPRS ciphering key sequence number, shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to clause 4.1.3.2), shall reset the routing area updating attempt counter and shall change to state GMM-DEREGISTERED.LIMITED-SERVICE. The mobile station shall store the LAI in the list of "forbidden location areas for regional provision of service". The MS shall start timer T3340 as described in subclause 4.7.1.9. If no RR connection exists, the MS shall perform the following additional actions immediately. If the MS is operating in MS operation mode A and an RR connection exists, the MS shall perform these actions when the RR connection is subsequently released: - If the MS is IMSI attached, the MS shall set the update status to U3 ROAMING NOT ALLOWED, shall delete any TMSI, LAI and ciphering key sequence number and shall reset the location update attempt counter. The new MM state is MM IDLE. - The MS shall perform a cell selection according to 3GPP TS 43.022[ None ] [82] and 3GPP TS 25.304[ None ] [98]. NOTE 5: The cell selection procedure is not applicable for an MS in GAN mode. If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, GUTI, last visited registered TAI, TAI list, KSI and tracking area updating attempt counter as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when the tracking area update procedure is rejected with the EMM cause with the same value. # 13 (Roaming not allowed in this location area); The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to clause 4.1.3.2) and shall delete the list of equivalent PLMNs. The MS shall reset the routing area updating attempt counter, and shall enter the state GMM-REGISTERED.LIMITED-SERVICE. The MS shall store the LAI in the list of "forbidden location areas for roaming". The MS shall start timer T3340 as described in subclause 4.7.1.9. If no RR connection exists, the MS shall perform the following additional actions immediately. If the MS is operating in MS operation mode A and an RR connection exists, the MS shall perform these actions when the RR connection is subsequently released: - If the MS is IMSI attached, the MS shall set the update status to U3 ROAMING NOT ALLOWED and shall reset the location update attempt counter. The new MM state is MM IDLE. - The MS shall perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14]. An MS in GAN mode shall request a PLMN list in GAN (see 3GPP TS 44.318[ None ] [76b]) prior to perform a PLMN selection from this list according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14]. If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status and tracking area updating attempt counter as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when the tracking area update procedure is rejected with the EMM cause with the same value. # 14 (GPRS services not allowed in this PLMN); The MS shall delete any RAI, P-TMSI, P-TMSI signature, and GPRS ciphering key sequence number stored, shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to subclause 4.1.3.2), shall reset the routing area updating attempt counter and shall change to state GMM-DEREGISTERED. The MS shall store the PLMN identity in the "forbidden PLMNs for GPRS service" list and if the MS is configured to use timer T3245 (see 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [135] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [112]) then the MS shall start timer T3245 and proceed as described in subclause 4.1.1.6. A GPRS MS operating in MS operation mode C shall perform a PLMN selection instead of a cell selection. If the message has been successfully integrity checked by the lower layers and the MS maintains a PLMN-specific PS-attempt counter for that PLMN, then the MS shall set this counter to the MS implementation-specific maximum value. A GPRS MS operating in MS operation mode A or B which is already IMSI attached for CS services in the network is still IMSI attached for CS services in the network. If the update type is "periodic updating" a GPRS MS operating in MS operation mode A or B in network operation mode I shall then proceed with the appropriate MM specific procedure. As an implementation option, a GPRS MS operating in operation mode A or B may perform the following additional action. If no RR connection exists the MS may perform the action immediately. If the MS is operating in MS operation mode A and an RR connection exists, the MS may only perform the action when the RR connection is subsequently released: - The MS may perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14]. If an MS in GAN mode performs a PLMN selection, it shall request a PLMN list in GAN (see 3GPP TS 44.318[ None ] [76b]) prior to perform a PLMN selection from this list according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14]. The MS shall not perform the optional PLMN selection in the case where the PLMN providing this reject cause is: - On the "User Controlled PLMN Selector with Access Technology " or, - On the "Operator Controlled PLMN Selector with Access Technology " list or, - A PLMN identified as equivalent to any PLMN, within the same country, contained in the lists above. If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, GUTI, last visited registered TAI, TAI list, KSI and tracking area updating attempt counter as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when the tracking area update procedure is rejected with the EMM cause with the same value. # 15 (No Suitable Cells In Location Area); The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to subclause 4.1.3.2) shall reset the routing area updating attempt counter and shall change to state GMM-REGISTERED.LIMITED-SERVICE. The MS shall store the LAI in the list of "forbidden location areas for roaming". The MS shall start timer T3340 as described in subclause 4.7.1.9. If no RR connection exists, the MS shall perform the following additional actions immediately. If the MS is operating in MS operation mode A and an RR connection exists, the MS shall perform these actions when the RR connection is subsequently released: - If the MS is IMSI attached, the MS shall set the update status to U3 ROAMING NOT ALLOWED and shall reset the location update attempt counter. The new MM state is MM IDLE. - The MS shall search for a suitable cell in another location area or a tracking area according to 3GPP TS 43.022[ None ] [82] and 3GPP TS 25.304[ None ] [98] or 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [121]. NOTE 6: The cell selection procedure is not applicable for an MS in GAN mode. If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status and tracking area updating attempt counter as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when the tracking area update procedure is rejected with the EMM cause with the same value. #22 (Congestion); If the T3346 value IE is present in the ROUTING AREA UPDATE REJECT message and the value indicates that this timer is neither zero nor deactivated, the MS shall proceed as described below, otherwise it shall be considered as an abnormal case and the behaviour of the MS for this case is specified in subclause 4.7.5.1.5. The MS shall abort the routing area updating procedure, reset the routing area updating attempt counter and set the GPRS update status to GU2 NOT UPDATED. If the rejected request was not for initiating a PDN connection for emergency bearer services, the MS shall change to state GMM-REGISTERED.ATTEMPTING-TO-UPDATE. The MS shall stop timer T3346 if it is running. If the ROUTING AREA UPDATE REJECT message is integrity protected, the MS shall start timer T3346 with the value provided in the T3346 value IE. If the ROUTING AREA UPDATE REJECT message is not integrity protected, the MS shall start timer T3346 with a random value from the default range specified in table 11.3a. The MS stays in the current serving cell and applies the normal cell reselection process. The routing area updating procedure is started, if still necessary, when timer T3346 expires or is stopped. A GPRS MS operating in MS operation mode A or B which is already IMSI attached for CS services in the network is still IMSI attached for CS services in the network. If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, and tracking area updating attempt counter as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when the tracking area update procedure is rejected with the EMM cause with the same value. A GPRS MS operating in MS operation mode A or B in network operation mode II which is configured to use CS fallback and SMS over SGs, or SMS over SGs only, and which did not perform a successful generic location updating procedure since the last intersystem change from S1 mode to A/Gb or Iu mode shall proceed with appropriate MM specific procedures. # 25 (Not authorized for this CSG) Cause #25 is only applicable in UTRAN Iu mode and when received from a CSG cell. Other cases are considered as abnormal cases and the specification of the mobile station behaviour is given in subclause 4.7.5.1.5. The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and store it according to subclause 4.1.3.2) and shall reset the routing area updating attempt counter. The state is changed to GMM-REGISTERED.LIMITED-SERVICE. If the CSG ID and associated PLMN identity of the cell where the MS has sent the ROUTING AREA UPDATE REQUEST message are contained in the Allowed CSG list stored in the MS, the MS 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 MS has sent the ROUTING AREA UPDATE REQUEST message are contained in the Operator CSG list, the MS shall proceed as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14] subclause 3.1A. The MS shall start timer T3340 as described in subclause 4.7.1.9. If no RR connection exists, the MS shall perform the following additional actions immediately. If the MS is operating in MS operation mode A and an RR connection exists, the MS shall perform these actions when the RR connection is subsequently released: - If the MS is IMSI attached, the MS shall set the update status to U3 ROAMING NOT ALLOWED and shall reset the location update attempt counter. The new MM state is MM IDLE. - The MS shall search for a suitable cell according to 3GPP TS 43.022[ None ] [82] and 3GPP TS 25.304[ None ] [98]. If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status and tracking area updating attempt counter as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when the tracking area update procedure is rejected with the EMM cause with the same value. Other values are considered as abnormal cases. The specification of the MS behaviour in those cases is described in subclause 4.7.5.1.5.

3GPP TS 24.008

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

CT WG1

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

4.7.5.1.4

9.9.4.7A Notification indicator

The purpose of the Notification indicator information element is to inform the UE about an event which is relevant for the upper layer using an EPS bearer context or having requested a procedure transaction. The Notification indicator information element is coded as shown in figure 9.9.4.7A.1 and table 9.9.4.7A.1. The Notification indicator is a type 4 information element with 3 octets length. Figure 9.9.4.7A.1: Notification indicator information element Table 9.9.4.7A.1: Notification indicator information element

3GPP TS 24.301

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

CT WG1

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

9.9.4.7A

16.9.4 Uu Control 16.9.4.1 General

When a UE is inside NG-RAN coverage, NR sidelink communication and/or V2X sidelink communication can be configured and controlled by NG-RAN via dedicated signalling or system information: - The UE should support and be authorized to perform NR sidelink communication and/or V2X sidelink communication in NG-RAN; - If configured, the UE performs V2X sidelink communication as 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 ] [2] unless otherwise specified, with the restriction that the dynamic scheduling for V2X sidelink communication (i.e. based on SL-V-RNTI) is not supported; - NG-RAN can provide the UE with intra-carrier sidelink configuration, inter-carrier sidelink configuration and anchor carrier(s) which provide sidelink configuration via a Uu carrier for NR sidelink communication and/or V2X sidelink communication; - When the UE cannot simultaneously perform both NR sidelink transmission and NR uplink transmission in time domain, prioritization between both transmissions is done based on their priorities and thresholds configured by the NG-RAN or pre-configured. When the UE cannot simultaneously perform both V2X sidelink transmission and NR uplink transmission in time domain, prioritization between both transmissions is done based on the priorities (i.e. PPPP) of V2X sidelink communication and a threshold configured by the NG-RAN or pre-configured. When a UE is outside NG-RAN coverage, SL DRB configuration(s) are preconfigured to the UE for NR sidelink communication. If UE changes the RRC state but has not received the SL DRB configuration(s) for the new RRC state, UE continues using the configuration obtained in the previous RRC state to perform sidelink data transmissions and receptions until the configuration for the new RRC state is received.

3GPP TS 38.300

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

RAN2

3GPP Series : 38 , Radio technology beyond LTE

16.9.4

6.1.3.3.1 Network initiated PDP Context Modification

In order to initiate the procedure, the network sends the MODIFY PDP CONTEXT REQUEST message to the MS and starts timer T3386. The message shall contain the new QoS and the radio priority level and LLC SAPI that shall be used by the MS in A/Gb mode at the lower layers for the transmission of data related to the PDP context. The MODIFY PDP CONTEXT REQUEST message may also contain packet filters in the TFT information element. If the selected Bearer Control Mode is 'MS/NW' and the TFT information element is included in the MODIFY PDP CONTEXT REQUEST message, the network shall include packet filter(s), or if no packet filters are proposed to be either added, replaced or deleted, it shall set TFT operation code to "No TFT operation" and include packet filter identifier(s) in the Packet filter identifier parameter in the parameters list to indicate which packet filter(s) in the TFT is associated with the QoS change. If the TFT information element is included in the MODIFY PDP CONTEXT REQUEST message and packet filter(s) is proposed to be added, the network shall allocate packet filter identifier(s) for all packet filters to be added to the TFT. The network shall allocate packet filter identifier value s which are currently not allocated to any existing packet filter of the same TFT. The network informs the MS about the Bearer Control Mode to be applied for all active PDP contexts sharing the same PDP Address and APN by including the selected Bearer Control Mode parameter in the protocol configuration options information element. This information is either explicitly given in the MODIFY PDP CONTEXT REQUEST message or implicitly given by not being present. The MS shall act according to the presence of the protocol configuration options information element and the value of the selected Bearer Control Mode parameter in the MODIFY PDP CONTEXT REQUEST message: - if the protocol configuration options information element is not present, the MS shall apply Bearer Control Mode 'MS only' for all active PDP contexts sharing the same PDP Address and APN. - if the selected Bearer Control Mode parameter is not present in the protocol configuration options information element, the MS shall apply Bearer Control Mode 'MS only' for all active PDP contexts sharing the same PDP Address and APN. - if the selected Bearer Control Mode parameter is present in the protocol configuration options information element, the MS shall apply Bearer Control Mode according to the value of this parameter for all active PDP contexts sharing the same PDP Address and APN. If a WLAN offload indication information element is included in the MODIFY PDP CONTEXT REQUEST message, the MS shall replace stored WLAN offload acceptability values for this PDN connection with the newly received offload indications and use the UTRAN offload acceptability value to determine whether this PDN connection is offloadable to WLAN or not. Upon receipt of the MODIFY PDP CONTEXT REQUEST message, if the MS sent an APN for the establishment of the PDN connection, the MS shall stop the timer T3396 if it is running for the APN sent by the MS.If the MS did not send an APN for the establishment of the PDN connection and the request type was different from "emergency", the MS shall stop the timer T3396 associated with no APN if it is running. If the MODIFY PDP CONTEXT REQUEST message was received for an emergency PDN connection, the MS shall not stop the timer T3396 associated with no APN if it is running. For any case, the MS shall then reply with the MODIFY PDP CONTEXT ACCEPT message, if the MS accepts the new QoS and the indicated LLC SAPI. The network shall upon receipt of the MODIFY PDP CONTEXT ACCEPT message stop timer T3386. In A/Gb mode, the network shall establish, reconfigure or continue using the logical link with the new QoS for the LLC SAPI indicated in the MODIFY PDP CONTEXT REQUEST message. In Iu mode, if the Radio Access Bearer supporting the PDP context is active, then the network shall reconfigure and continue using the Radio Access Bearer with the new QoS indicated in the MODIFY PDP CONTEXT REQUEST message; if the PDP context is preserved, then the network may re-establish a Radio Access Bearer with the new QoS indicated in the MODIFY PDP CONTEXT REQUEST 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

6.1.3.3.1

5.3.2.3 Registration Area management

Registration Area management comprises the functions to allocate and reallocate a Registration area to a UE. Registration area is managed per access type i.e. 3GPP access or Non-3GPP access. When a UE registers with the network over the 3GPP access, the AMF allocates a set of tracking areas in TAI List to the UE. When the AMF allocates registration area, i.e. the set of tracking areas in TAI List, to the UE it may take into account various information (e.g. Mobility Pattern and Allowed/Non-Allowed Area (refer to clause 5.3.4.1)). An AMF which has the whole PLMN as serving area may alternatively allocate the whole PLMN ("all PLMN") as registration area to a UE in MICO mode (refer to clause 5.4.1.3). When AMF allocates registration area for UE registered for Disaster Roaming service as specified in clause 5.40.4, AMF shall only consider TAIs covering the area with the Disaster Condition. The 5G System shall support allocating a Registration Area using a single TAI List which includes tracking areas of any NG-RAN nodes in the Registration Area for a UE. In the case of SNPN, the TAI list allocated by AMF does not support Tracking Areas belonging to different SNPNs. TAI used for non-3GPP access shall be dedicated to non-3GPP access. TAI(s) dedicated to Non-3GPP access may be defined in a PLMN and apply within this PLMN. Each N3IWF, TNGF, TWIF and W-AGF is locally configured with one TAI value. Each N3IWF, TNGF, TWIF and W-AGF may be configured with a different TAI value or with the same TAI value as other N3IWFs, TNGFs, TWIFs and/or W-AGFs. The TAI is provided to the AMF during N2 interface setup and as part of the User Location Information in UE associated messages as described in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [34]. When a UE registers with the network over a Non-3GPP access, the AMF allocates to the UE a registration area that only includes the TAI received from the serving N3IWF, TNGF, TWIF or W-AGF. NOTE 1: For example, two W-AGFs can each correspond to a different TAI (one TAI per W-AGF) and thus support different sets of S-NSSAI(s). When generating the TAI list, the AMF shall include only TAIs that are applicable on the access type (i.e. 3GPP access or Non-3GPP access) where the TAI list is sent. NOTE 2: To prevent extra signalling load resulting from Mobility Registration Update occurring at every RAT change, it is preferable to avoid generating a RAT-specific TAI list for a UE supporting more than one RAT. NOTE 3: For a UE registered on N3GPP access the TAI(s) provided to the UE as part of the Registration Area is expected to enable the support of the slices that are intended to be provided for this UE over this specific Non-3GPP access. In addition, the Registration Area provided to the UE for non-3GPP access will never change until the UE deregisters from non-3GPP access (either explicit deregistration or implicit deregistration due to Deregistration timer expiring due to UE entering CM_IDLE state). For all 3GPP Access RATs in NG-RAN and for Non-3GPP Access, the 5G System supports the TAI format as specified in TS 23.003[ Numbering, addressing and identification ] [19] consisting of MCC, MNC and a 3-byte TAC only. The additional aspects for registration management when a UE is registered over one access type while the UE is already registered over the other access type is further described in clause 5.3.2.4. To ensure a UE initiates a Mobility Registration procedure when performing inter-RAT mobility to or from NB-IoT, a Tracking Area shall not contain both NB-IoT and other RATs cells (e.g. WB-E-UTRA, NR), and the AMF shall not allocate a TAI list that contains both NB-IoT and other RATs Tracking Areas. For 3GPP access the AMF determines the RAT type the UE is camping on based on the Global RAN Node IDs associated with the N2 interface and additionally the Tracking Area indicated by NG-RAN. When the UE is accessing NR using unlicensed bands, as defined in clause 5.4.8, an indication is provided in N2 interface as defined in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [34]. The AMF may also determine more precise RAT Type information based on further information received from NG-RAN: - The AMF may determine the RAT Type to be LTE-M as defined in clause 5.31.20; or - The AMF may determine the RAT Type to be NR using unlicensed bands, as defined in clause 5.4.8. - The AMF may determine the RAT Type to be one of the RAT types for satellite access, as defined in clause 5.4.10. - The AMF may determine the RAT Type to be NR RedCap as defined in clause 5.41. For Non-3GPP accesses the AMF determines the RAT type the UE is camping based on the 5G-AN node associated with N2 interface as follows: - The RAT type is Untrusted Non-3GPP if the 5G-AN node has a Global N3IWF Node ID; - The RAT type is Trusted Non-3GPP if the 5G-AN node has a Global TNGF Node ID or a Global TWIF Node ID; and - The RAT type is Wireline -BBF if the 5G-AN node has a Global W-AGF Node ID corresponding to a W-AGF supporting the Wireline BBF Access Network. The RAT type is Wireline-Cable if the 5G-AN node has a Global W-AGF Node ID corresponding to a W-AGF supporting the Wireline Cable Access Network. If not possible to distinguish between the two, the RAT type is Wireline. NOTE 4: How to differentiate between W-AGF supporting either Wireline BBF Access Network or the Wireline (e.g. different Global W-AGF Node ID IE or the Global W-AGF Node ID including a field to distinguish between them) is left to Stage 3 definition. NOTE 5: If an operator supports only one kind of Wireline Access Network (either Wireline BBF Access Network or a Wireline Cable Access Network) the AMF may be configured to use RAT type Wireline or the specific one. For Non-3GPP access the AMF may also use the User Location Information provided at N2 connection setup to determine a more precise RAT Type, e.g. identifying IEEE 802.11 access, Wireline-Cable access, Wireline-BBF access. When the 5G-AN node has either a Global N3IWF Node ID, or a Global TNGF Node ID, or a Global TWIF Node ID, or a Global W-AGF Node ID, the Access Type is Non-3GPP Access.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.3.2.3

7.7.1 Support of dynamic PTP and PTM switching

For UEs in RRC_CONNECTED, NG-RAN supports dynamic switch between PTP and PTM for MBS as specified in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [2]. In case of split gNB architecture, for a MRB with common PDCP involving both PTP (RLC leg) and PTM (RLC leg), upon receiving the MBS data from the gNB-CU via a shared F1-U tunnel, the gNB-DU makes decision of using PTP (RLC leg) or PTM (RLC leg) or both. For UEs in RRC_INACTIVE only PTM is supported as specified in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [2].

3GPP TS 38.401

NG-RAN; Architecture description

RAN3

3GPP Series : 38 , Radio technology beyond LTE

7.7.1

8.7.4 TDD (EPDCCH scheduling)

The parameters specified in Table 8.7.4-1 are valid for all TDD tests unless otherwise stated. Table 8.7.4-1: Common test parameters (TDD) The requirements are specified in Table 8.7.4-3, with the addition of the parameters in Table 8.7.4-2 and the downlink physical channel setup according to Annex C.3.2. The test points are applied to UE category, CA capability and bandwidth combination with maximum aggregated bandwidth as specified inTable 8.7.4-4. The TB success rate shall be sustained during at least 300 frames. Table 8.7.4-2: Test parameters for SDR test for PDSCH scheduled by EPDCCH (TDD) Table 8.7.4-3: Minimum requirement (TDD) Table 8.7.4-4: Test points for sustained data rate (FRC)

3GPP TS 36.101

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

RAN4

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

8.7.4

4.3.12a.6 PCC for Restricted Local Operator Services

Dynamic PCC based on the procedures described in TS 23.203[ Policy and charging control architecture ] [6] may be used for UEs accessing Restricted Local Operator Services which involve voice services. When establishing PDN connection towards the RLOS APN with a PDN GW, according to clause 4.7.5, the PCRF provides the PDN GW with the QoS parameters, based on operator policy, including an ARP value reserved for the Restricted Local Operator Services where RLOS has a lower priority in terms of admission control than regular PDN connections The PCRF ensures that the RLOS PDN connection is used only for Restricted Local Operator Services. The PCRF rejects an IMS session established via the RLOS PDN connection if the AF (i.e. P-CSCF) does not provide an RLOS indication to the PCRF.

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

5.1.1 Description

As a UAS requests permission to access UAS data services from an MNO, the MNO performs a secondary check (after or in parallel to the initial mutual authentication) to establish the UASs credentials to operate. The MNO is responsible for transporting and potentially adding additional data to the request to operate from the UAS to an Unmanned Aerial System Traffic Management (UTM). Note that the UTM is a 3GPP entity. This UTM is responsible for the authorization of UAS to operate and checks the credentials of the UAS and UAV operator. One option is that the UTM is operated by air traffic control agencies. It stores all the data regarding the UAV, UAV controller and their live location. If the UAS fails any part of this check, the MNO may refuse service to the UAS and hence deny permission to operate. Figure 5.1.1-1: Initial authorisation to operate

3GPP TS 22.825

Study on Remote Identification of Unmanned Aerial Systems (UAS)

SA WG1

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

5.1.1

8.1 Information Element Types

A GTP control plane (signalling) message may contain several information elements. In order to have forward compatible type definitions for the GTPv2 information elements, all of them shall be TLIV (Type, Length, Instance, Value) coded. GTPv2 information element type values are specified in the Table 8.1-1. The last column of this table indicates whether the information element is: - Fixed Length: the IE has a fixed set of fields, and a fixed number of octets. - Variable Length: the IE has a fixed set of fields, and has a variable number of octets. For example, the last octets may be numbered similar to "5 to (n+4)". In this example, if the value of the length field, n, is 0, then the last field is not present. - Extendable: the IE has a variable number of fields, and has a variable number of octets. The last fields are typically specified with the statement: "These octet(s) is/are present only if explicitly specified". The legacy receiving entity shall ignore the unknown octets. In order to improve the efficiency of troubleshooting, it is recommended that the information elements should be arranged in the signalling messages as well as in the grouped IEs, according to the order the information elements are listed in the message definition table or grouped IE definition table in clause 7. However the receiving entity shall be prepared to handle the messages with information elements in any order. Within information elements, certain fields may be described as spare. These bits shall be transmitted with the value set to 0. To allow for future features, the receiver shall not evaluate these bits. GTPv2-C information elements that have similar semantics in GTPv1-C shall be converted into GTPv1-C format, as specified in TS 29.060[ General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface ] [4], before sending them to a pre-R8 GSN. Table 8.1-1: Information Element types for GTPv2

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

8.8 EPS Bearer ID (EBI)

EPS Bearer ID (EBI) is coded as depicted in Figure 8.8-1. The overall length of the IE is 5 octets. In future releases of the spec additional octets may be specified and new semantic for the spare bits may be defined. Figure 8.8-1: EPS Bearer ID (EBI) The following bits within Octet 5 shall indicate: - Bit 8 to 5 – Spare, for future use and set to zero. - Bit 4 to 1 – EPS Bearer ID (EBI) field, the coding of EBI field and its value range is specified in 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [30], clause 11.2.3.1.5, bits 5 to 8. The sending GTPv2 entity shall include a EBI with a value between '1' and '4' only when the target GTPv2 entity is known to support 15 EPS Bearers, based on per PLMN local configuration.

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

5.4.2 PUCCH formats 2, 2a and 2b

The block of bits shall be scrambled with a UE-specific scrambling sequence, resulting in a block of scrambled bits according to where the scrambling sequence is given by clause 7.2. The scrambling sequence generator shall be initialised with at the start of each subframe where is C-RNTI. The block of scrambled bits shall be QPSK modulated as described in clause 7.1, resulting in a block of complex-valued modulation symbols . Each complex-valued symbol shall be multiplied with a cyclically shifted length sequence for each of the antenna ports used for PUCCH transmission according to where is defined by clause 5.5.1 with and . Resources used for transmission of PUCCH formats 2/2a/2b are identified by a resource index from which the cyclic shift is determined according to where and for and by for . For PUCCH formats 2a and 2b, supported for normal cyclic prefix only, the bit(s) shall be modulated as described in Table 5.4.2-1 resulting in a single modulation symbol used in the generation of the reference-signal for PUCCH format 2a and 2b as described in clause 5.5.2.2.1. Table 5.4.2-1: Modulation symbol for PUCCH formats 2a and 2b

3GPP TS 36.211

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

RAN1

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

5.4.2

5.7.19 Satellite switch with re-synchronization in RRC_CONNECTED

The UE shall: 1> stop timer T430 if running; 1> inform lower layers that UL synchronisation is lost due to satellite switch with re-synchronization; 1> start re-synchronising to the DL of the SpCell served by the satellite indicated by ntn-Config in SatSwitchWithReSync; 1> start timer T430 with the timer value set to ntn-UlSyncValidityDuration from the subframe indicated by epochTime in ntn-Config in SatSwitchWithReSync; 1> inform lower layers when UL synchronisation is obtained. Editor's Note: FFS whether in the soft-switch scenario a UE can obtain DL synchronization from the target satellite without losing UL synchronization to the source satellite.

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

5.7.19

4.15.6.5 Change the chargeable party during the session

Figure 4.15.6.5-1: Change the chargeable party during the session 1. For the ongoing AF session, the AF may send a Nnef_ChargeableParty_Update request message (AF Identifier, Transaction Reference ID, Sponsoring Status, Background Data Transfer Reference ID) to the NEF. The Sponsoring Status indicates whether sponsoring is enabled or disabled, i.e. whether the 3rd party service provider is the chargeable party or not. The Background Data Transfer Reference ID parameter identifies a previously negotiated transfer policy for background data transfer as defined in clause 4.16.7. The Transaction Reference ID provided in the Change chargeable party request message is set to the Transaction Reference ID that was assigned, by the NEF, to the a Nnef_ChargeableParty_Create request. 2. The NEF authorizes the AF request of changing the chargeable party. If the authorisation is not granted, step 3 is skipped and the NEF replies to the AF with a Result value indicating that the authorisation failed. NOTE: Based on operator configuration, the NEF may skip this step. In this case the authorization is performed by the PCF in step 3. 3. The NEF interacts with the PCF by triggering a Npcf_PolicyAuthorization_Update request and provides IP filter information or Ethernet filter information, sponsored data connectivity information (as defined in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]), Background Data Transfer Reference ID (if received from the AF) and Sponsoring Status (if received from the AF) to the PCF. 4. The PCF determines whether the request is allowed and notifies the NEF if the request is not authorized. If the request is not authorized, NEF responds to the AF in step 5 with a Result value indicating that the authorization failed. 5. The NEF sends a Nnef_ChargeableParty_Update response message (Transaction Reference ID, Result) to the AF. Result indicates whether the request is granted or not.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.15.6.5

5.22 System Enablers for priority mechanism 5.22.1 General

The 5GS and the 5G QoS model allow classification and differentiation of specific services such as listed in clause 5.16, based on subscription-related and invocation-related priority mechanisms. These mechanisms provide abilities such as invoking, modifying, maintaining, and releasing QoS Flows with priority, and delivering QoS Flow packets according to the QoS characteristics under network congestion conditions. Subscription-related Priority Mechanisms include the ability to prioritize flows based on subscription information, including the prioritization of RRC Connection Establishment based on Unified Access Control mechanisms and the establishment of prioritized QoS Flows. Invocation-related Priority Mechanisms include the ability for the service layer to request/invoke the activation of prioritized QoS Flows through an interaction over Rx/N5 and packet detection in the UPF. QoS Mechanisms applied to established QoS Flows include the ability to fulfil the QoS characteristics of QoS Flows through preservation of differentiated treatment for prioritized QoS Flow and resource distribution prioritization. Messages associated with priority services that are exchanged over service-based interfaces may include a Message Priority header to indicate priority information, as specified in TS 23.502[ Procedures for the 5G System (5GS) ] [3] and TS 29.500[ 5G System; Technical Realization of Service Based Architecture; Stage 3 ] [49]. In addition, the separation of concerns between the service classification provided by the core network through the association of Service Data Flows to QoS, and the enforcing of QoS differentiation in (R)AN through the association of QoS Flows to Data Radio bearers, supports the prioritization of QoS Flows when a limitation of the available data radio bearers occurs. In addition, it also includes the ability for the service layer to provide instructions on how to perform pre-emption of media flows with the same priority assigned through an interaction over Rx as defined in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45].

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.22

7B.4 Authentication for UE behind 5G-RG and FN-RG

A UE that is connected to a 5G-RG or FN-RG, can access the 5GC via the N3IWF or via the TNGF. A UE behind a FN-RG can use the untrusted non-3GPP access procedure as defined in TS 23.502[ Procedures for the 5G System (5GS) ] [8] clause 4.12.2.2 to access the 5GC via the N3IWF. A UE behind a 5G-RG can use either the untrusted non-3GPP access as defined in TS 23.502[ Procedures for the 5G System (5GS) ] [8] clause 4.12.2.2, or trusted N3GPP-access as defined in TS 23.502[ Procedures for the 5G System (5GS) ] [8] clause 4.12a.2.2. A UE connecting to the 5G-RG or FN-RG via WLAN supporting IEEE 802.1X can use the NSWO authentication procedure as specified in Annex S of the present document. When the UE uses untrusted non-3GPP access, the authentication of the UE is as specified in clause 7.2.1. When the UE uses trusted non-3GPP access, the authentication of the UE is as specified in clause 7A.2.1.

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

7B.4

4.4.1.3 Maximum DL cell PDCP SDU bit-rate

a) This measurement provides the maximum cell bit-rate of PDCP SDUs on the downlink. This represents the maximum ingress rate of user plane traffic to the eNodeB/RN (via X2 or S1). This is a sum counter measured across all QCIs. b) SI c) This measurement is obtained by sampling at pre-defined intervals the DL cell PDCP SDU bit-rate summed across all QCIs (see clause 4.4.1.1), and then taking the arithmetic maximum of these samples. d) A single integer value representing the maximum bit-rate measured in kbit/s. e) DRB.PdcpSduBitrateDlMax f) EUtranCellFDD EUtranCellTDD g) Valid for packet switched traffic h) EPS

3GPP TS 32.425

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

SA WG5

3GPP Series : 32 , OAM&P and Charging

4.4.1.3

8.105 Trusted WLAN Mode Indication

The purpose of the Trusted WLAN Mode Indication information element is to convey the selected trusted WLAN Mode. The content and encoding of the Trusted WLAN Mode Indication is depicted on Figure 8.105-1. Figure 8.105-1: Trusted WLAN Mode Indication The following bits within Octet 5 shall indicate: - Bit 8 to 3 – Spare, for future use and set to zero. - Bit 2 – MCM (Multiple-connection mode Indication): if this bit is set to 1, it indicates that the Multiple-connection mode is used. - Bit 1 – SCM (Single-connection mode Indication): if this bit is set to 1, it indicates that the Single-connection mode is 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.105

5.3.4 Support of Dual Services

The behaviour described in this subclause is used to realize the following required services throughout subclause 5.3.4. The mobile station is not obliged to support the network originated in-call modification procedure. In that case, the mobile station shall, when receiving a MODIFY message, treat the message as unknown and react as described in subclause 8.4. If the mobile station is already prepared to support the procedure in both directions, it shall act as described in this subclause. Alternate Speech/Group 3 fax (Teleservice 61 according to 3GPP TS 22.003[ Circuit Teleservices supported by a Public Land Mobile Network (PLMN) ] [4]).

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

20.3.3 Session stop procedure

The BM-SC initiates the MBMS session stop procedure when it considers the MBMS session terminated. Typically this will happen when there is no more MBMS data expected to be transmitted for a sufficiently long period of time to justify the release of bearer plane resources in the network. Figure 20.3.3.1: MBMS Session Stop procedure 1. The BM-SC sends an RAR message to all MBMS GWs listed in the "list of downstream nodes" parameter of the affected MBMS Bearer Context to indicate that the MBMS session is terminated and the bearer plane resources can be released. 2. The MBMS GW releases the resources regarding the session and sends an RAA message to the BM-SC. An AAR message is not mandated for the SGmb application in response to an RAR- RAA command exchange.

3GPP TS 29.061

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

CT WG3

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

20.3.3

4.4.13 UCMF

The UCMF is used for storage of dictionary entries corresponding to either PLMN-assigned or UE manufacturer-assigned UE Radio Capability IDs. An MME may subscribe with the UCMF to obtain from the UCMF new values of UE Radio Capability ID that the UCMF assigns for the purpose of caching them locally. Provisioning of UE manufacturer-assigned UE Radio Capability ID entries in the UCMF is performed from an AS that interacts with the UCMF either directly or via the SCEF (or via Network Management) (see TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [74] for further information). A UCMF that serves both EPS and 5GS shall require provisioning the UE Radio Capability ID with the TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [89] format or the TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [37] format or both the formats of the UE radio capabilities. For PLMN-assigned UE Radio Capability ID the UCMF also is the entity that assigns the UE Radio Capability ID values. Figure 4.4.13-1: UCMF connected to MME Each PLMN-assigned UE Radio Capability ID is also associated to the IMEI/TAC of the UE model(s) that it is related to. When an MME requests the UCMF to assign a UE Radio Capability ID for a set of UE radio capabilities, it indicates the IMEI/TAC of the UE that the UE Radio Capability information is related to. The UCMF may be provisioned with a dictionary of UE manufacturer-assigned UE Radio Capability IDs which include a "Vendor ID" that applies to the Manufacturers of these UE, and a list of IMEI/TACs for which the PLMN has obtained UE manufacturer-assigned UE Radio Capability IDs. A PLMN-assigned UE Radio Capability IDs is kept in the UCMF storage as long as it is associated with at least a IMEI/TAC value. When a IMEI/TAC value is related to a UE model that is earmarked for operation based on UE manufacturer-assigned UE Radio Capability IDs, this IMEI/TAC value is disassociated in the UCMF from any PLMN assigned UE Radio Capability IDs. For the case the PLMN is configured to store PLMN assigned IDs in the UE manufacturer-assigned operation requested list defined in clause 5.11.3a, the UCMF does not remove from UE manufacturer-assigned operation requested list any PLMN assigned UE Radio Capability ID no longer used, and rather quarantines it to avoid any future reassignment. The UCMF stores a Version ID value for the PLMN assigned UE Radio Capability IDs so it is included in the PLMN assigned UE Radio Capability IDs it assigns. This shall be configured in the UCMF. A UCMF dictionary entry shall include also the related UE Radio Capability for Paging for each RAT.

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

4.12a.4.1 Service Request procedures via Trusted non-3GPP Access

The Service Request procedure via trusted non-3GPP access shall be supported as specified in clause 4.12.4.1 for the untrusted non-3GPP access with the following modifications: - The untrusted non-3GPP access is substituted by a trusted non-3GPP access. - The N3IWF is substituted by the TNGF. - The user plane between the UE and TNGF is established with IKEv2 signalling, as specified in clause 4.12a.5 (i.e. by using an IKEv2 Create_Child_SA exchange). The IKEv2 Create Child SA Request shall include the Additional QoS Information to reserve non-3GPP specific QoS resources as defined in clause 4.12a.5.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.12a.4.1

5.45.3 Congestion information monitoring

The NG-RAN may be required to provide the UL and/or DL QoS Flow congestion information to UPF (i.e. a percentage of congestion level for exposure). The UPF may be required to monitor and expose the UL and/or DL QoS Flow congestion information reported from the NG-RAN. QoS monitoring request for congestion information provided by the SMF to the NG-RAN is to trigger the NG-RAN to measure and report UL and/or DL QoS Flow congestion information to PSA UPF as defined in 5.37.3. NOTE 1: How the RAN measures and reports the congestion information is up to RAN implementation. NOTE 2: It is assumed that the RAN reports whenever there is a change in the percentage of packets to be marked with ECN for L4S marking and/or congestion information. The granularity of change in percentage determination is up to RAN implementation. For the reporting of the congestion information from PSA UPF, the periodical reporting is not applied and only the Reporting frequency 'event triggered' applies, see clause 5.8.2.18. The PSA UPF shall send a report when the measurement result crosses the indicated Reporting threshold. Subsequent reports shall not be sent by the PSA UPF during the Minimum waiting time. The PSA UPF reports the received UL and/or DL QoS Flow congestion information to the target NF as instructed by the QoS Monitoring request (see clause 5.8.2.18) from the SMF. Only one of ECN marking for L4S (in the case of ECN marking for L4S in RAN as described in clause 5.37.3) or QoS monitoring of congestion information may be requested to NG-RAN for a QoS Flow. They are mutually exclusive, therefore, measurements of Congestion information on a QoS Flow are not provided in QoS Monitoring reports if SMF enables ECN marking for L4S in RAN (see clause 5.37.3).

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.45.3

– VarLogMeasConfig

The UE variable VarLogMeasConfig includes the configuration of the logging of measurements to be performed by the UE while in RRC_IDLE, RRC_INACTIVE, covering intra-frequency, inter-frequency and inter-RAT mobility related measurements. The UE performs logging of measurements only while in RRC_IDLE and RRC_INACTIVE. VarLogMeasConfig UE variable -- ASN1START -- TAG-VARLOGMEASCONFIG-START VarLogMeasConfig-r16-IEs ::= SEQUENCE { areaConfiguration-r16 AreaConfiguration-r16 OPTIONAL, bt-NameList-r16 BT-NameList-r16 OPTIONAL, wlan-NameList-r16 WLAN-NameList-r16 OPTIONAL, sensor-NameList-r16 Sensor-NameList-r16 OPTIONAL, loggingDuration-r16 LoggingDuration-r16, reportType CHOICE { periodical LoggedPeriodicalReportConfig-r16, eventTriggered LoggedEventTriggerConfig-r16 }, earlyMeasIndication-r17 ENUMERATED {true} OPTIONAL, areaConfiguration-r17 AreaConfiguration-r17 OPTIONAL, areaConfiguration-v1800 AreaConfiguration-v1800 OPTIONAL } -- TAG-VARLOGMEASCONFIG-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

5.1.3.2.1.4.4 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE

The substate 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE is chosen by the UE if the registration procedure for mobility and periodic registration update failed due to a missing response from the network, or due to the circumstances described in subclauses 5.3.9, 5.5.1.3.5 and 5.5.1.3.7. No 5GMM procedure except registration procedure for mobility and periodic registration update (i.e. the 5GS registration type IE set to "mobility registration updating" or "periodic registration updating" in the REGISTRATION REQUEST message) and de-registration procedure, shall be initiated by the UE in this substate. No data shall be sent or received. NOTE 1: The registration procedure for mobility and periodic registration update over non-3GPP access can be triggered by, e.g. the change of S1 UE network capability or renegotiating some parameters. NOTE 2: This substate is entered irrespective whether: - the UE is camped on a cell which is in the registered PLMN, a PLMN from the list of equivalent PLMNs, or the registered SNPN, and the current TAI is not in the list of "allowed tracking areas"; or - the current TAI is in the list of "non-allowed tracking areas".

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

5.2.6.11.5 Nnef_ServiceParameter_Get operation

Service operation name: Nnef_ServiceParameter_Get Description: The consumer retrieves service specific parameters in the UDR via the NEF. Inputs, Required: Service Descriptor (e.g. the combination of DNN and S-NSSAI, an AF-Service-Identifier or an External Application Identifier). Inputs, Optional: Service Parameters and Target UE identifiers (e.g. the address (IP or Ethernet) of the UE if available, GPSI if available, External Group Identifier if available), or "PLMN ID(s) of inbound roamers". Outputs, Required: Transaction Reference ID, operation execution result indication, requested data. Outputs, Optional: None.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

5.2.6.11.5

4.3.1.1.3 Attempted outgoing intra-DeNB handover preparations from DeNB cell to RN per handover cause

This measurement provides the number of attempted outgoing intra-DeNB handover preparations from DeNB cell to RN per handover cause; this measurement is only applicable to DeNB. CC. Transmission of the X2AP message HANDOVER REQUEST from the DeNB to RN (see TS 36.423[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 Application Protocol (X2AP) ] [10]), indicating the attempt of an outgoing intra-DeNB handover preparation from DeNB cell to RN, the forwarded X2AP message HANDOVER REQUEST for the handover from another RN, eNB or DeNB to the RN is exclusive, the measurement is only incemented by one for one handover in case the X2AP message HANDOVER REQUEST are sent to multiple RNs. Each attempted outgoing intra-DeNB handover preparation from DeNB cell to RN is added to the relevant per handover cause measurement, the possible causes are included in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [9]. The sum of all supported per cause measurements shall equal the total number of attempted outgoing intra-DeNB handover preparations from DeNB cell to RN. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first. A single integer value. HO.IntraDenbOutPrepToRnAtt.Cause where Cause identifies the cause for handover EUtranCellFDD EUtranCellTDD Valid for packet switched traffic EPS

3GPP TS 32.425

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

SA WG5

3GPP Series : 32 , OAM&P and Charging

4.3.1.1.3

9.8.2.1 FDD and half-duplex FDD

The following requirements apply to UE supporting coverage enhancement. For the parameters specified in Table 9.8.2.1-1, and using the downlink physical channels specified in Annex C.3.2, the minimum requirements are specified in Table 9.8.2.1-2 and by the following a) the ratio of the throughput obtained when transmitting on the best narrowband reported by the UE the corresponding TBS and that obtained when transmitting the TBS indicated by the reported wideband CQI median on a randomly selected narrowband within the set of narrowbands in which MPDCCH is monitored shall be ≥ ; The requirements only apply for narrowbands of full size and the random scheduling across the narrowbands is done by selecting a new narrowband in each TTI for FDD and half-duplex FDD. The transport block size TBS (wideband CQI median) is that resulting from the code rate which is closest to that indicated by the wideband CQI median and theentry in Table 7.1.7.2.1-1 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [6] that corresponds to the narrowband size. Table 9.8.2.1-1 Sub-band test for single antenna transmission (FDD and half-duplex FDD) Table 9.8.2.1-2 Minimum requirement (FDD and half-duplex 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.8.2.1

15.5.2.6 PSCell change failure

For analysis of PSCell change failures, the UE makes the SCG Failure Information available to the MN. If the MN can perform an initial analysis, it transfers the SCG Failure Information together with the analysis results to the relevant SN which is responsible for the PSCell change failures. Otherwise, the MN transfers the SCG Failure Information to the last serving SN, which may respond using the SCG Failure Transfer procedure to inform the MN it is not responsible for the SCG failure. If needed, the MN transfer the SCG Failure Information to the source SN.

3GPP TS 38.300

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

RAN2

3GPP Series : 38 , Radio technology beyond LTE

15.5.2.6

4.2.2.3 Number of E-RABs attempted to release

a) This measurement provides the number of E-RABs attempted to release. The measurement is split into subcounters per E-RAB QoS level (QCI). b) CC c) On receipt by the eNodeB/RN of an E-RAB RELEASE COMMAND or UE CONTEXT RELEASE COMMAND or RESET message from MME/DeNB; or receipt by the eNodeB/RN of an UE CONTEXT RELEASE message from another eNodeB/DeNB or transmission by the eNodeB/RN of a an E-RAB Release Indication or RESET message to MME/DeNB; or on receipt by the eNB/RN of a PATH SWITCH REQUEST ACKNOWLEDGE or PATH SWITCH REQUEST FAILED message by which some or all E-RABs in the corresponding PATH SWITCH REQUEST need to be released; or on receipt by the eNB/RN of a RRCConnectionReconfigurationComplete message from the UE, indicating a successful intra-eNB/RN handover (see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]), i.e., the E-RABs in the cooresponding RRCConnectionReconfiguration message can be be released by the source EUtran cell. Each corresponding E-RAB to release is added to the relevant measurement per QCI, the possible QCIs are included in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [9]. , the same E-RAB shall not be counted repeatly but only one in case it appears more than one time in the same or different messages triggering this measurement The sum of all supported per QCI measurements shall equal the total number of E-RABs attempted to release. In case only a subset of per QCI measurements is supported, a sum subcounter will be provided first. d) Each measurement is an integer value. The number of measurements is equal to the number of QCIs plus a possible sum value identified by the .sum suffix. e) The measurement name has the form ERAB.RelAttNbr.QCI where QCI identifies the E-RAB level quality of service class. f) EUtranCellFDD EUtranCellTDD g) Valid for packet switched traffic h) EPS i) One usage of this measurement is to support the coverage ratio (CR) calculation for EE coverage area determination in [21].

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

5.7.2 Preamble sequence generation

The random access preambles are generated from Zadoff-Chu sequences with zero correlation zone, generated from one or several root Zadoff-Chu sequences. The network configures the set of preamble sequences the UE is allowed to use. There are up to two sets of 64 preambles available in a cell where Set 1 corresponds to higher layer PRACH configuration using prach-ConfigurationIndex and prach-FrequencyOffset and Set 2, if configured, corresponds to higher layer PRACH configuration using prach-ConfigurationIndexHighSpeed and prach-FrequencyOffsetHighSpeed. The set of 64 preamble sequences in a cell is found by including first, in the order of increasing cyclic shift, all the available cyclic shifts of a root Zadoff-Chu sequence with the logical index rootSequenceIndexHighSpeed (for Set 2, if configured) or with the logical index RACH_ROOT_SEQUENCE (for Set 1), where both rootSequenceIndexHighSpeed (if configured) and RACH_ROOT_SEQUENCE are broadcasted as part of the System Information. Additional preamble sequences, in case 64 preambles cannot be generated from a single root Zadoff-Chu sequence, are obtained from the root sequences with the consecutive logical indexes until all the 64 sequences are found. The logical root sequence order is cyclic: the logical index 0 is consecutive to 837. The relation between a logical root sequence index and physical root sequence index is given by Tables 5.7.2-4 and 5.7.2-5 for preamble formats 0 – 3 and 4, respectively. The root Zadoff-Chu sequence is defined by where the length of the Zadoff-Chu sequence is given by Table 5.7.2-1. From the root Zadoff-Chu sequence, random access preambles with zero correlation zones of length are defined by cyclic shifts according to where the cyclic shift is given by and is given by Tables 5.7.2-2 and 5.7.2-3 for preamble formats 0-3 and 4, respectively, where the higher-layer parameters zeroCorrelationZoneConfig and zeroCorrelationZoneConfigHighSpeed shall be used for PRACH preamble Set 1 and Set 2 (if configured), respectively. Restricted set type B shall be used for PRACH preamble Set 2 (if configured), and the parameter High-speed-flag provided by higher layers determines if unrestricted set or restricted set type A shall be used for PRACH preamble Set 1. The variable is the cyclic shift corresponding to a Doppler shift of magnitude and is given by where is the smallest non-negative integer that fulfils . The parameters for restricted sets of cyclic shifts depend on . For restricted set type A and , the parameters are given by For restricted set type A and , the parameters are given by For restricted set type B and , the parameters are given by For restricted set type B and , the parameters are given by For restricted set type B and , the parameters are given by For restricted set type B and , the parameters are given by For restricted set type B and , the parameters are given by For restricted set type B and , the parameters are given by For all other values of , there are no cyclic shifts in the restricted set. Table 5.7.2-1: Random access preamble sequence length Table 5.7.2-2: for preamble generation (preamble formats 0-3) Table 5.7.2-3: for preamble generation (preamble format 4) Table 5.7.2-4: Root Zadoff-Chu sequence order for preamble formats 0 – 3 Table 5.7.2-5: Root Zadoff-Chu sequence order for preamble format 4

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

– MeasResultCellListSFTD-NR

The IE MeasResultCellListSFTD-NR consists of SFN and radio frame boundary difference between the PCell and an NR cell as specified in TS 38.215[ NR; Physical layer measurements ] [9] and TS 38.133[ NR; Requirements for support of radio resource management ] [14]. MeasResultCellListSFTD-NR information element -- ASN1START -- TAG-MEASRESULTCELLLISTSFTD-NR-START MeasResultCellListSFTD-NR ::= SEQUENCE (SIZE (1..maxCellSFTD)) OF MeasResultCellSFTD-NR MeasResultCellSFTD-NR ::= SEQUENCE { physCellId PhysCellId, sfn-OffsetResult INTEGER (0..1023), frameBoundaryOffsetResult INTEGER (-30720..30719), rsrp-Result RSRP-Range OPTIONAL } -- TAG-MEASRESULTCELLLISTSFTD-NR-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

5.4.2.2 NAS security mode control initiation by the network

The AMF initiates the NAS security mode control procedure by sending a SECURITY MODE COMMAND message to the UE and starting timer T3560 (see example in figure 5.4.2.2). The AMF shall reset the downlink NAS COUNT counter and use it to integrity protect the initial SECURITY MODE COMMAND message if the security mode control procedure is initiated: a) to take into use the security context created after a successful execution of the 5G AKA based primary authentication and key agreement procedure or the EAP based primary authentication and key agreement procedure; or b) upon receipt of REGISTRATION REQUEST message, if the AMF needs to create a mapped 5G NAS security context (i.e. the type of security context flag is set to "mapped security context" in the ngKSI IE included in the SECURITY MODE COMMAND message). The AMF shall send the SECURITY MODE COMMAND message unciphered, but shall integrity protect the message with the 5G NAS integrity key based on KAMF or mapped K'AMF indicated by the ngKSI included in the message. The AMF shall set the security header type of the message to "integrity protected with new 5G NAS security context". The AMF shall create a locally generated KAMF and send the SECURITY MODE COMMAND message including an ngKSI value in the ngKSI IE set to "000" and 5G-IA0 and 5G-EA0 as the selected NAS security algorithms only when the security mode control procedure is initiated: a) during an initial registration procedure for emergency services if no valid 5G NAS security context is available; b) during a registration procedure for mobility and periodic registration update for a UE that has an emergency PDU session if no valid 5G NAS security context is available; c) during a service request procedure for a UE that has an emergency PDU session if no valid 5G NAS security context is available; or d) after a failed primary authentication and key agreement procedure for a UE that has an emergency PDU session or is establishing an emergency PDU session, if continued usage of a valid 5G NAS security context is not possible. When the AMF sends the SECURITY MODE COMMAND message including an ngKSI value in the ngKSI IE set to "000" and 5G-IA0 and 5G-EA0 as the selected NAS security algorithms, if: a) the AMF supports N26 interface; b) the UE set the S1 mode bit to "S1 mode supported" in the 5GMM capability IE of the REGISTRATION REQUEST message; and c) the security mode control procedure is initiated during an initial registration procedure for emergency services, during a registration procedure for mobility and periodic registration update for a UE that has an emergency PDU session, or during a service request procedure for a UE that has an emergency PDU session, the SECURITY MODE COMMAND message shall also include the Selected EPS NAS security algorithms IE. The selected EPS NAS security algorithms shall be set to EIA0 and EEA0. The UE shall process a SECURITY MODE COMMAND message including an ngKSI value in the ngKSI IE set to "000" and 5G-IA0 and 5G-EA0 as the selected NAS security algorithms and, if accepted, create a locally generated KAMF when the security mode control procedure is initiated: a) during an initial registration procedure for emergency services; b) during a registration procedure for mobility and periodic registration update for a UE that has an emergency PDU session; c) during a service request procedure for a UE that has an emergency PDU session; or d) after a primary authentication and key agreement procedure for a UE that has an emergency PDU session or is establishing an emergency PDU session. NOTE 1: The process for creation of the locally generated KAMF by the AMF and the UE is implementation dependent. The KAMF is specified in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. Upon receipt of a REGISTRATION REQUEST message, if the AMF does not have the valid current 5G NAS security context indicated by the UE, the AMF shall either: a) indicate the use of the new mapped 5G NAS security context to the UE by setting the type of security context flag in the ngKSI IE to "mapped security context" and the KSI value related to the security context of the source system; or b) set the ngKSI value to "000" in the ngKSI IE if the AMF sets 5G-IA0 and 5G-EA0 as the selected NAS security algorithms for a UE that has an emergency PDU session. Upon receipt of a REGISTRATION REQUEST message, if the AMF has the valid current 5G NAS security context indicated by the UE, the AMF supports N26 interface and the UE set the S1 mode bit to "S1 mode supported" in the 5GMM capability IE of the REGISTRATION REQUEST message and the UE is not registered for disaster roaming services, the AMF shall check whether the selected EPS NAS security algorithms was successfully provided to the UE. If not, the AMF shall initiate the NAS security mode control procedure by sending a SECURITY MODE COMMAND message with the Selected EPS NAS security algorithms IE to the UE. While having a current mapped 5G NAS security context with the UE, if the AMF needs to take the native 5G NAS security context into use, the AMF shall include the ngKSI that indicates the native 5G NAS security context in the SECURITY MODE COMMAND message. The AMF shall include the replayed security capabilities of the UE (including the security capabilities with regard to NAS, RRC and UP (user plane) ciphering as well as NAS and RRC integrity, and other possible target network security capabilities, i.e. E-UTRAN if the UE included them in the message to network), the selected 5GS ciphering and integrity algorithms and the ngKSI. If a UE is already registered over one access to a PLMN and the AMF decides to skip primary authentication and key agreement procedure when the UE attempts to register over the other access to the same PLMN, the AMF shall take into use the UE's current 5G NAS security context over the other access that the UE is registering. In this case, SECURITY MODE COMMAND message is not sent to the UE. If the UE is registered to the same AMF and the same PLMN over both 3GPP access and non-3GPP access, and the UE is in 5GMM-CONNECTED mode over both the 3GPP and non-3GPP accesses, then at any time the primary authentication and key agreement procedure has successfully completed over: a) the 3GPP access, the AMF includes the ngKSI in the SECURITY MODE COMMAND message over the 3GPP access. When the AMF sends the SECURITY MODE COMMAND message to UE over the non-3GPP access to take into use the new 5G NAS security context, the AMF shall include the same ngKSI in the SECURITY MODE COMMAND message to identify the new 5G NAS security context; or b) the non-3GPP access, the AMF includes the ngKSI in the SECURITY MODE COMMAND message over the non-3GPP access. When the AMF sends the SECURITY MODE COMMAND message to UE over the 3GPP access to take into use the new 5G NAS security context, the AMF shall include the same ngKSI in the SECURITY MODE COMMAND message to identify the new 5G NAS security context. The AMF may initiate a SECURITY MODE COMMAND in order to change the 5G security algorithms for a current 5G NAS security context already in use. The AMF re-derives the 5G NAS keys from KAMF with the new 5G algorithm identities as input and provides the new 5GS algorithm identities within the SECURITY MODE COMMAND message. The AMF shall set the security header type of the message to "integrity protected with new 5G NAS security context". If, during an ongoing registration procedure, the AMF is initiating a SECURITY MODE COMMAND (i.e. after receiving the REGISTRATION REQUEST message, but before sending a response to that message) and: a) the REGISTRATION REQUEST message does not successfully pass the integrity check at the AMF; or b) the AMF can not decipher the value part of the NAS message container IE in the REGISTRATION REQUEST message; the AMF shall include the Additional 5G security information IE with the RINMR bit set to "Retransmission of the initial NAS message requested" in the SECURITY MODE COMMAND message requesting the UE to send the entire REGISTRATION REQUEST message in the SECURITY MODE COMPLETE message as described in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. If, during an ongoing deregistration procedure, the AMF is initiating a SECURITY MODE COMMAND (i.e. after receiving the DEREGISTRATION REQUEST message, but before sending a response to that message) and: a) the DEREGISTRATION REQUEST message does not successfully pass the integrity check at the AMF; or b) the AMF can not decipher the value part of the NAS message container IE in the DEREGISTRATION REQUEST message; the AMF shall include the Additional 5G security information IE with the RINMR bit set to "Retransmission of the initial NAS message requested" in the SECURITY MODE COMMAND message requesting the UE to send the entire DEREGISTRATION REQUEST message in the SECURITY MODE COMPLETE message as described in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. NOTE 2: The AMF uses the UE security capability which was provided by the UE. If, during an ongoing service request procedure for a UE with an emergency PDU session, the AMF is initiating a SECURITY MODE COMMAND (i.e. after receiving the SERVICE REQUEST message or the CONTROL PLANE SERVICE REQUEST message, but before sending a response to that message) and the SERVICE REQUEST message or the CONTROL PLANE SERVICE REQUEST message does not successfully pass the integrity check at the AMF, the AMF shall include the Additional 5G security information IE with the RINMR bit set to "Retransmission of the initial NAS message requested" in the SECURITY MODE COMMAND message requesting the UE to send the entire: a) SERVICE REQUEST message; or b) CONTROL PLANE SERVICE REQUEST message excluding non-cleartext IEs, except the Uplink data status IE if needed (see subclause 5.4.2.3); in the SECURITY MODE COMPLETE message as described in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. Additionally, the AMF may request the UE to include its IMEISV in the SECURITY MODE COMPLETE message. If the AMF supports N26 interface and the UE set the S1 mode bit to "S1 mode supported" in the 5GMM capability IE of the REGISTRATION REQUEST message and the AMF needs to provide the selected EPS NAS security algorithms to the UE, the AMF shall select ciphering and integrity algorithms to be used in the EPS and indicate them to the UE via the Selected EPS NAS security algorithms IE in the SECURITY MODE COMMAND message. NOTE 3: The AS and NAS security capabilities are the same, i.e. if the UE supports one algorithm for NAS, the same algorithm is also supported for AS. If the AMF performs horizontal key derivation e.g. during the mobility and periodic registration update or when the UE is already registered in the PLMN with another access type as described in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24], the AMF shall include horizontal derivation parameter in the SECURITY MODE COMMAND message. If the security mode control procedure is initiated after successful EAP based primary authentication and key agreement procedure and the security mode control procedure intends to bring into use the partial native 5G NAS security context created by the EAP based primary authentication and key agreement procedure, the AMF shall set the EAP message IE of the SECURITY MODE COMMAND message to an EAP-success message to be sent to the UE. If the SECURITY MODE COMMAND message is provided to a 5G-RG that is acting on behalf of an AUN3 device and the EAP message IE is set to an EAP-success message, the AMF shall include the AUN3 device security key IE in the SECURITY MODE COMMAND message with its value set to: a) the Master session key, if the AUN3 device does not support 5G key hierarchy; or b) the KWAGF key, if the AUN3 device supports 5G key hierarchy. NOTE 4: The network is aware from the AUN3 device subscription data in UDM whether the AUN3 device supports 5G key hierarchy or not as specified in subclause 7B.7 of 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. Figure 5.4.2.2: Security mode control procedure

3GPP TS 24.501

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

CT WG1

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

5.4.2.2

10.5.6.13 Temporary Mobile Group Identity (TMGI)

The purpose of the TMGI element is for group paging in MBMS. The TMGI information element is a type 4 information element with a minimum length of 5 octets and a maximum length of 8 octets. If octet 6 is included, then octets 7 and 8 shall also be included. The content of the TMGI element is shown in Figure 10.5.154/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.168/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.154/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : TMGI information element Table 10.5.168/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : TMGI 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.13

I.9 Security of UE onboarding in SNPNs I.9.1 General

Onboarding of UEs for SNPNs is specified in clause 5.30.2.10 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. Onboarding of UEs for SNPNs allows the UE to access an Onboarding Network (ONN) based on Default UE credentials for the purpose of provisioning the UE with SNPN credentials and any other necessary information. The Default UE credentials are pre-configured on the UE. Default UE credentials consist of credentials for primary authentication and optionally credentials for secondary authentication. To provision SNPN credentials in a UE that is configured with Default UE credentials, the UE selects an SNPN as ONN and establishes a secure connection with that SNPN referred to as Onboarding SNPN (ON-SNPN). The present clause specifies security of UE onboarding.

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

I.9

4.11.0a.8 5GC NAS capability (re-)enabled and disabled

When 5G NAS (i.e. N1 mode) capability is (re-)enabled, the UE triggers Tracking Area Update procedure as specified in clause 5.3.3.0 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13]. If the MME determines that interworking with 5GS is changed to Supported and if the MME has selected a standalone PGW, the MME may initiate PDN disconnection with reactivation required as specified in clause 5.10.3 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13] at the end of the tracking area update procedure. NOTE 1: MME requesting PDN disconnection with reactivation required is to allow MME to select a SMF+PGW-C so that session continuity can be achieved when UE moves to 5GS. If a UE disables its support of N1 mode and moves from 5GS to EPS, the UE and the SMF+PGW-C maintain the mapped 5GS parameters for PDU session(s) that are transferred to EPS. NOTE 2: The mapped 5GS parameters are used when the UE re-enables N1 mode and moves back to 5GS.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.11.0a.8

Annex K (informative): Isolated E-UTRAN Operation for Public Safety K.1 General description of the IOPS concept

Isolated E-UTRAN Operation for Public Safety (IOPS) provides the ability to maintain a level of communications for public safety users, via an IOPS-capable eNodeB (or set of connected IOPS-capable eNodeBs), following the loss of backhaul communications. The Isolated E-UTRAN mode of operation is also applicable to the formation of a Nomadic EPS deployment, i.e. a deployment of one or more standalone IOPS-capable eNodeBs, creating a serving radio access network without backhaul communications and also providing local connectivity \(e.g. for IP or Ethernet) and services to public safety users in the absence of normal EPS infrastructure availability. This annex provides implementation and deployment guidelines for the operation of public safety networks in the no backhaul (to Macro EPC) scenario using a Local EPC approach.

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")

Annex

4.7.7 Support of rate control of user data using CIoT EPS Optimisation 4.7.7.1 General

The rate of user data sent to and from a UE (e.g. a UE using CIoT EPS Optimisations) can be controlled in two different ways: - Serving PLMN Rate Control - APN Rate Control Serving PLMN Rate Control is intended to allow the Serving PLMN to protect its MME and the Signalling Radio Bearers in the E-UTRAN from the load generated by NAS Data PDUs. APN Rate Control is intended to allow HPLMN operators to offer customer services such as "maximum of Y messages per day". NOTE: Existing AMBR mechanisms are not suitable for such a service since, for radio efficiency and UE battery life reasons, an AMBR of e.g. > 100kbit/s is desirable and such an AMBR translates to a potentially large daily data volume. The PDN GW in the visited PLMN may send the APN rate control parameter for an emergency PDN connection.

3GPP TS 23.401

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

SA WG2

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

4.7.7

4.8.1 Network Configuration for Interaction with UTRAN/GERAN

GPRS idle mode mobility within GERAN or UTRAN and also between GERAN and UTRAN specifies a set of sequence number handling functions, e.g. the exchange of sequence numbers during Routing Area Update procedures. EPS idle mode mobility procedures don't specify any such sequence number mappings for IRAT mobility scenarios. To avoid interoperation issues a network that deploys E-UTRAN together with GERAN and/or UTRAN shall not configure usage of the GPRS feature "reordering required" for PDP contexts of PDP type IPv4, IPv6 or IPv4v6. Also the network shall not configure usage of lossless PDCP of UTRAN and the GERAN SGSN shall not configure usage of acknowledged mode LLC/NSAPI/SNDCP.

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

5.5.3.2.5B Tracking area updating for access to RLOS not accepted by the network

If the tracking area updating request for access to RLOS cannot be accepted by the network, the UE shall perform the procedures as described in clause 5.5.3.2.5 along with the following conditions: a) if the action for the reject involves searching for a suitable cell in E-UTRAN radio access technology, the UE shall proceed with the action and shall attempt to perform a tracking area updating procedure or an attach procedure for access to RLOS in the new tracking area, if found, depending on the EMM state. b) if the action for the reject involves attempting to select GERAN or UTRAN radio access technology or disabling the E-UTRAN capability, the UE shall skip the action for as long as access to RLOS is still needed. NOTE: How long the UE attempts to access RLOS is up to UE implementation. Then if a) the UE is in the same selected PLMN where the last tracking area updating procedure was attempted and rejected; b) the tracking area updating procedure was rejected with an EMM cause value other than #9, #10 and #40; and c) timer T3346 is not running, the UE shall: a) detach locally, if not detached already, perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6] to attempt EPS attach for access to RLOS via another PLMN. If the tracking area updating request for access to RLOS fails due to abnormal case a) in clause 5.5.3.2.6, the UE shall perform the actions as described in clause 5.5.3.2.6 and inform the upper layers of the failure to access the network. If the tracking area updating request for access to RLOS fails due to abnormal cases b), c) or d) in clause .2.6, the UE shall perform the procedures as described in clause 5.5.3.2.6 with the exception that the UE shall skip actions that involve attempting to select GERAN or UTRAN radio access technology and actions that involve disabling of the E-UTRA capability, for as long as access to RLOS is still needed. Then if the UE is in the same selected PLMN where the last tracking area updating request was attempted, the UE shall: a) detach locally, if not detached already, perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6] to attempt EPS attach for access to RLOS via another PLMN.

3GPP TS 24.301

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

CT WG1

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

5.5.3.2.5B

9.2.6.2 Frame structure type 3 with TDD Pcell

The following requirements apply to UE Category ≥1. For the parameters specified in Table 9.2.6.2-1, Table 9.2.6.2-2, and using the downlink physical channels specified in tables C.3.2-1 and C.3.2-2, two sets of CQI reports are obtained for LAA Scell. The first one is obtained by reports whose reference resource is in the downlink subframes with 6 dB transmission power boost, i.e., high power subframes. The second one is obtained by reports whose reference resource is in the downlink subframe with 0 dB transmission power boost, i.e., low power subframe. In the test, PDSCH transport format in high power subframe is determined by first set of CQI reports and PDSCH transport format in low power subframe is determined by second set of CQI reports. The reported CQI value in the first set of reports shall be in the range of ±1 of the reported median more than 90% of the first set of reports. The reported CQI value in the second set of reports shall be in the range of ±1 of the reported median more than 90% of the second set of reports. If the PDSCH BLER in the high power subframes using the transport format indicated by wideband CQI median is less than or equal to 0.1, the BLER in high power subframes using the transport format indicated by the (wideband CQI median + 1) shall be greater than 0.1. If the PDSCH BLER in the high power subframes using the transport format indicated by the wideband CQI median is greater than 0.1, the BLER in high power subframes using transport format indicated by (wideband CQI median – 1) shall be less than or equal to 0.1. If the PDSCH BLER in the low power subframes using the transport format indicated by wideband CQI median is less than or equal to 0.1, the BLER in low power subframes using the transport format indicated by the (wideband CQI median + 1) shall be greater than 0.1. If the PDSCH BLER in the low power subframes using the transport format indicated by the wideband CQI median is greater than 0.1, the BLER in low power subframes using transport format indicated by (wideband CQI median – 1) shall be less than or equal to 0.1. The value of the wideband CQI median for first set of CQI reports minus the wideband CQI median for second set of CQI reports shall be larger than or equal to 2 in Test 1 and Test 2. Table 9.2.6.2-1: Parameters for PUSCH 3-0 static test on TDD Pcell Table 9.2.6.2-2: PUSCH 3-0 static test on LAA Scell

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

5.7.6.3 Ethernet Packet Filter Set

For Ethernet PDU Session Type, the Packet Filter Set shall support Packet Filters based on at least any combination of: - Source/destination MAC address. - Ethertype as defined in IEEE 802.3 [131]. - Customer-VLAN tag (C-TAG) and/or Service-VLAN tag (S-TAG) VID fields as defined in IEEE Std 802.1Q [98]. - Customer-VLAN tag (C-TAG) and/or Service-VLAN tag (S-TAG) PCP/DEI fields as defined in IEEE Std 802.1Q [98]. - IP Packet Filter Set, in the case that Ethertype indicates IPv4/IPv6 payload. - Packet Filter direction. NOTE 1: The MAC address may be specified as address ranges. NOTE 2: A value left unspecified in a Packet Filter matches any value of the corresponding information in a packet.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.7.6.3

D.5 Intelligent transport systems – infrastructure backhaul D.5.0 General

Intelligent Transport Systems (ITS) embrace a wide variety of communications-related applications that are intended to increase travel safety, minimize environmental impact, improve traffic management, and maximize the benefits of transportation to both commercial users and the general public. Over recent years, the emphasis in intelligent vehicle research has turned to co-operative systems, in which the traffic participants (vehicles, bicycles, pedestrians, etc.) communicate with each other and/or with the infrastructure. Cooperative ITS is the term used to describe technology that allows vehicles to become connected to each other, and to the infrastructure and other parts of the transport network. In addition to what drivers can immediately see around them, and what vehicle sensors can detect, all parts of the transport system will increasingly be able to share information to improve decision making. Thus, this technology can improve road safety through avoiding collisions, but also assist in reducing congestion and improving traffic flows, and reduce environmental impacts. Once the basic technology is in place as a platform, an array of applications can be developed. Cooperative ITS can greatly increase the quality and reliability of information available about vehicles, their location and the road environment. In the future, cars will know the location of road works and the switching phases of traffic lights ahead, and they will be able to react accordingly. This will make for safer and more convenient travel and faster arrival at the destination. On-board driver assistance, coupled with two-way communication between vehicles and between vehicles and road infrastructure, can help drivers to better control their vehicle and hence have positive effects in terms of safety and traffic efficiency. An important role in this plays the so-called road side units (RSUs). Vehicles can also function as sensors reporting weather and road conditions including incidents. In this way, cars can be used as information sources for high-quality information services. RSUs are connected to the traffic control centre for management and control purposes. They broadcast, e.g., traffic light information (RSU vehicle) and traffic information from the traffic-control centre (TCC) via the RSU to the vehicles (TCC RSU vehicle). RSUs also collect vehicle probe data for the traffic control centre (vehicle RSU TCC). For reliable distribution of data, low-latency and high-capacity connections between RSUs (e.g. traffic lights, traffic signs, etc.) and the TCC are required. This type of application comes with rather tight end-to-end latency requirements for the communication service between RSU and TCC (10 ms), since relayed data needs to be processed in the TCC and, if needed, the results are forwarded to neighbouring RSUs. Also, the availability of the communication service has to be very high (99,9999%) in order to compete with existing wired technology and in order to justify the costly deployment and maintenance of RSUs. Furthermore, due to considerably large aggregation areas (see clause D.5.1), considerable amounts of data need to be backhauled to the TCC (up to 10 Mbit/s per RSU).

3GPP TS 22.261

Service requirements for the 5G system

SA WG1

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

D.5