Datasets:

Exploration-Lab

/

MM-TelecoBench

like 0

Follow

Exploration Lab 61

5.5.1 Attach procedure 5.5.1.1 General

The attach procedure is used to attach to an EPC for packet services in EPS. The attach procedure is used for the following purposes: - by a UE in PS mode of operation to attach for EPS services only; - by a UE in CS/PS mode 1 or CS/PS mode 2 of operation to attach for both EPS and non-EPS services; - by a UE supporting NB-S1 mode only in PS mode of operation to attach for EPS services and "SMS only"; - to attach for emergency bearer services; - an attach for access to RLOS; or - the UE has initiated a GPRS attach procedure while in A/Gb mode or Iu mode or an initial registration procedure while in N1 mode and moves to E-UTRAN coverage. The lower layers indicate to NAS that the network does not support emergency bearer services for the UE in limited service state (3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]). This information is taken into account when deciding whether to initiate attach for emergency bearer services in WB-S1 mode. If the MME does not support an attach for emergency bearer services, the MME shall reject any request to attach with an attach type set to "EPS emergency attach". If the MUSIM UE initiates the attach procedure and sets the attach type to "EPS emergency attach" in the ATTACH REQUEST message, the network shall not indicate the support of: - the NAS signalling connection release; - the paging indication for voice services; - the reject paging request; - the paging restriction; or - the paging timing collision control; in the ATTACH ACCEPT message. The lower layers may indicate to NAS whether the network supports access to RLOS (3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]). This information is taken into account when deciding whether to initiate attach for access to RLOS in WB-S1 mode. With a successful attach procedure, a context is established for the UE in the MME. Furthermore, if the UE requested PDN connectivity, a default bearer is established between the UE and the PDN GW, thus enabling always-on IP connectivity to the UE. In WB-S1 mode, the network may also initiate the activation of dedicated bearers as part of the attach procedure. In NB-S1 mode the network shall not initiate the activation of dedicated bearers. With a successful attach procedure in NB-S1 mode, a context is established for the UE in the MME. If the attach request included information to request PDN connectivity, a default bearer is also established between the UE and the PDN. If EMM-REGISTERED without PDN connection is supported by the UE and the MME, a default bearer need not be requested by the UE during the attach procedure. If EMM-REGISTERED without PDN connection is not supported by the UE or the MME, then the UE shall request establishment of a default bearer. During the attach procedure with default bearer establishment, the UE may also obtain the home agent IPv4 or IPv6 address or both. In a shared network, the UE shall choose one of the PLMN identities as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. The UE shall construct the TAI of the cell from this chosen PLMN identity and the TAC received for this PLMN identity as part of the broadcast system information. The chosen PLMN identity shall be indicated to the E-UTRAN (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]). Whenever an ATTACH REJECT message with the EMM cause #11 "PLMN not allowed" is received by the UE, the chosen PLMN identity shall be stored in the "forbidden PLMN list" and if the UE is configured to use timer T3245 (see 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]) then the UE shall start timer T3245 and proceed as described in clause 5.3.7a. Whenever an ATTACH REJECT message with the EMM cause #14 "EPS services not allowed in this PLMN" is received by the UE, the chosen PLMN identity shall be stored in the "forbidden PLMNs for GPRS service" and if the UE is configured to use timer T3245 (see 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]) then the UE shall start timer T3245 and proceed as described in clause 5.3.7a. Whenever an ATTACH REJECT message is received by the UE with the EMM cause #12 "tracking area not allowed", #13 "roaming not allowed in this tracking area", or #15 "no suitable cells in tracking area", the constructed TAI shall be stored in the suitable list. An attach attempt counter is used to limit the number of subsequently rejected attach attempts. The attach attempt counter shall be incremented as specified in clause 5.5.1.2.6. Depending on the value of the attach attempt counter, specific actions shall be performed. The attach attempt counter shall be reset when: - the UE is powered on; - a USIM is inserted; - an attach or combined attach procedure is successfully completed; NOTE: The attach procedure can be initiated in S1 or S101 mode as described in clause 5.5.1. - a GPRS attach or combined GPRS attach procedure is successfully completed in A/Gb or Iu mode; - a registration procedure for initial registration performed over 3GPP access is successfully completed in N1 mode and the UE is operating in single-registration mode; - a combined attach procedure is completed for EPS services only with cause #2, #16, #17, #18 or #22; - an attach or combined attach procedure is rejected with cause #11, #12, #13, #14, #15, #25 or #35: - a network initiated detach procedure is completed with cause #11, #12, #13, #14, #15 or #25; or - a new PLMN is selected. Additionally the attach attempt counter shall be reset when the UE is in substate EMM-DEREGISTERED.ATTEMPTING-TO-ATTACH and: - a new tracking area is entered; - timer T3402 expires; or - timer T3346 is started.

3GPP TS 24.301

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

CT WG1

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

5.5.1

4.23 Support of deployments topologies with specific SMF Service Areas 4.23.1 General

This clause captures changes to 5GC procedures in other clauses of this specification and new procedures to support deployments topologies with specific SMF Service Areas that are defined in clause 5.34 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. In the case of roaming for a Home Routed PDU Session the following cases may occur: - A UE moves out of V-SMF serving area in the serving PLMN; - A UE moves to another (serving) VPLMN; - A UE moves between HPLMN and a VPLMN. In the above cases, the procedures in clauses 4.23.2-16 for I-SMF apply for the V-SMF insertion/change/removal by replacing the I-SMF with V-SMF and SMF with H-SMF. When an AMF detects the need to change the V-SMF while the H-SMF does not support V-SMF change, the AMF shall not trigger the V-SMF change but shall trigger the release of the PDU Session. For an established PDU session an I-SMF is inserted if the UE is not in the SMF Service Area. In this case, when an UE moves from HPLMN to a VPLMN, a V-SMF is inserted and the I-SMF is removed. For mobility from VPLMN to HPLMN, an I-SMF is inserted and the V-SMF is removed. The procedures of this clause apply in this case, i.e. by replacing the target or new I-SMF by a V-SMF for mobility from HPLMN to VPLMN and by replacing the source or old I-SMF by a V-SMF for mobility from VPLMN to HPLMN. For additional consideration for Home-routed PDU sessions see clause 4.23.17. If at UE mobility the service area of the SMF does not include the location where the UE camps and the PDU Session is a MA PDU Session, then the AMF initiates the release of the MA PDU Session over all accesses served by this AMF. This applies to following procedures: - Registration as defined in clause 4.23.3, - Service Request as defined in clause 4.23.4, - Xn Hand-over as defined in clause 4.23.11, or - N2 Hand-Over as defined in clause 4.23.7. For an established PDU Session supporting mechanisms for redundant transmission defined in clause 5.33.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], or for a PDU Session supporting Time Sensitive Communications as defined in clauses 5.27 and 5.28 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], if the UE moves out of SMF Service Area, the SMF may, based on local policy, release the PDU Session after the mobility procedure. This applies to following procedures: Registration procedure, Service Request procedure, Xn based handover procedure, N2 based handover procedure. If dynamic CN PDB needs to be configured by the SMF and the I-SMF is involved in the PDU session, the I-SMF receives the Dynamic CN PDB value as part of QoS profile from SMF (over N16a) and forwards it to (R)AN via N2 SM message.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.23

7.7 HARQ RTT Timers

The parameters RTToffset and DLoffset provides offsets for determining the HARQ round trip time. The parameter RTToffset is set to 0 in terrestrial networks and RTToffset is set to UE-eNB RTT in Non-terrestrial networks. The parameter DLoffset is set to 0 in terrestrial networks and DLoffset is set to Koffset + k-Mac in Non-terrestrial networks where Koffset is defined in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2]. For each serving cell, in case of FDD configuration not configured with subframeAssignment-r15 and in case of Frame Structure Type 3 configuration on the serving cell which carries the HARQ feedback for this serving cell the HARQ RTT Timer is set to 8 subframes. For each serving cell, in case of TDD configuration or FDD with subframeAssignment-r15 configured on the serving cell which carries the HARQ feedback for this serving cell the HARQ RTT Timer is set to k + 4 subframes, where k is the interval between the downlink transmission and the transmission of associated HARQ feedback, as indicated in clauses 10.1 and 10.2 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2], and for an RN configured with rn-SubframeConfig, as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8] and not suspended, as indicated in Table 7.5.1-1 of TS 36.216[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer for relaying operation ] [11]. For each serving cell, for HARQ processes scheduled using Short Processing Time (TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]) the HARQ RTT Timer is set to 6 subframes for FDD and Frame Structure Type 3 and set to k + 3 subframes for TDD, where k is the interval between the downlink transmission and the transmission of associated HARQ feedback, as indicated in clauses 10.1 and 10.2 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2]. For each serving cell, for HARQ processes scheduled using short TTI (TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]) the HARQ RTT Timer is set to 8 TTIs if the TTI length is one slot or if proc-Timeline is set to n+4 set1, to 12 TTIs if proc-Timeline is set to n+6 set1 or n+6 set2 and to 16 TTIs if proc-Timeline is set to n+8 set2 for FDD and Frame Structure Type 3. For TDD short TTI the HARQ RTT Timer is set to k + 4 TTIs, where k is the interval between the downlink transmission and the transmission of associated HARQ feedback, as indicated in clauses 10.1 and 10.2 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2]. For BL UEs and UEs in enhanced coverage, when single TB is scheduled by PDCCH the HARQ RTT Timer corresponds to 7 + N subframes plus DLoffset, where N is the used PUCCH repetition factor, where only valid (configured) UL subframes as configured by upper layers in fdd-UplinkSubframeBitmapBR are counted for N. In case of TDD, HARQ RTT Timer corresponds to 3 + k + N subframes, where k is the interval between the last repetition of downlink transmission and the first repetition of the transmission of associated HARQ feedback, and N is the used PUCCH repetition factor, where only valid UL subframes are counted for N as indicated in clauses 10.1 and 10.2 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2]. For BL UEs and UEs in enhanced coverage, when multiple TBs are scheduled by PDCCH and HARQ-ACK bundling is not configured, the HARQ RTT Timer corresponds to 7 + m * N subframes plus DLoffset, where N is the used PUCCH repetition factor and m is the number of scheduled TBs as indicated in PDCCH whose associated HARQ process is with enabled HARQ feedback, where only valid (configured) UL subframes as configured by upper layers in fdd-UplinkSubframeBitmapBR are counted for m * N. For BL UEs and UEs in enhanced coverage, when multiple TBs are scheduled by PDCCH and HARQ-ACK bundling is configured the HARQ RTT Timer corresponds to 7 + M * N subframes plus DLoffset, where N is the used PUCCH repetition factor and M is the number of TB bundles as specified in clause 7.3 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2], where only valid (configured) UL subframes as configured by upper layers in fdd-UplinkSubframeBitmapBR are counted for M * N. For NB-IoT, when single TB is scheduled by PDCCH or when multiple TBs are scheduled for the interleaved case when HARQ-ACK bundling is configured the HARQ RTT Timer is set to k+3+N subframes plus RTToffset + deltaPDCCH, where k is the interval between the last subframe of the downlink transmission and the first subframe of the associated HARQ feedback transmission and N is the transmission duration in subframes of the associated HARQ feedback, and deltaPDCCH is the interval starting from the subframe following the last subframe of the associated HARQ feedback transmission plus 3 subframes plus RTToffset to the first subframe of the next PDCCH occasion. For NB-IoT, when multiple TBs are scheduled by PDCCH for the non-interleaved case or for the interleaved case when HARQ-ACK bundling is not configured, the HARQ RTT Timer is set to k+m*N+1 subframes plus RTToffset + deltaPDCCH where k is the interval between the last subframe of the downlink transmission and the first subframe of the first HARQ feedback transmission and N is the transmission duration in subframes of the associated HARQ feedback and m is the number of scheduled TBs as indicated in PDCCH whose associated HARQ process is with enabled HARQ feedback, and deltaPDCCH is the interval starting from the subframe following the last subframe of the last HARQ feedback transmission plus 1 subframe plus RTToffset to the first subframe of the next PDCCH occasion. Except for NB-IoT and for HARQ processes scheduled using Short Processing Time and for short TTI, UL HARQ RTT Timer length is set to 4 subframes plus RTToffset for FDD and Frame Structure Type 3, and set to kULHARQRTT subframes for TDD, where kULHARQRTT equals to the kPHICH value indicated in Table 9.1.2-1 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2] if the UE is not configured with upper layer parameter symPUSCH-UpPts for the serving cell, otherwise the kPHICH value is indicated in Table 9.1.2-3. For NB-IoT, when single TB is scheduled by PDCCH the UL HARQ RTT timer length is set to 4 subframes plus RTToffset + deltaPDCCH, where deltaPDCCH is the interval starting from the subframe following the last subframe of the PUSCH transmission plus 3 subframes plus RTToffset to the first subframe of the next PDCCH occasion. For NB-IoT, when multiple TBs are scheduled by PDCCH the UL HARQ RTT timer length is set to 2 subframes plus RTToffset + deltaPDCCH, where deltaPDCCH is the interval starting from the subframe following the last subframe of the PUSCH transmission plus 1 subframe plus RTToffset to the first subframe of the next PDCCH occasion. For HARQ processes scheduled using Short Processing Time (TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]), the UL HARQ RTT Timer length is set to 3 subframes for FDD and for Frame Structure Type 3, and set to kULHARQRTT subframes for TDD, where kULHARQRTT equals the value indicated in Table 7.7-1 and Table 7.7-2. For HARQ processes scheduled using short TTI (TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]), the UL HARQ RTT Timer length is set to 8 TTIs if the TTI length is one slot or if proc-Timeline is set to n+4 set1, to 12 TTIs if proc-Timeline is set to n+6 set1 or n+6 set2 and to 16 TTIs if proc-Timeline is set to n+8 set2 for FDD and Frame Structure Type 3. For TDD short TTI the UL HARQ RTT Timer is set to kULHARQRTT TTIs, where kULHARQRTT equals the value indicated in Table 7.7-3, Table 7.7-4 and Table 7.7-5. Table 7.7-1: kULHARQRTT for TDD Short Processing Time when special subframe configurations 0~9 is configured Table 7.7-2: kULHARQRTT for TDD Short Processing Time applied when special subframe configuration 10 is configured Table 7.7-3: kULHARQRTT for TDD short TTI applied when special subframe configurations 1, 2, 3, 4, 6, 7 and 8 are configured Table 7.7-4: kULHARQRTT for TDD short TTI applied when special subframe configurations 0, 5 and 9 are configured Table 7.7-5: kULHARQRTT for TDD short TTI applied when special subframe configuration 10 is configured NOTE 1: Void NOTE 2: Void

3GPP TS 36.321

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

RAN2

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

7.7

10.5.6.1 Access point name

The purpose of the Access point name information element is to identify the packet data network to which the GPRS user wishes to connect and to notify the access point of the packet data network that wishes to connect to the MS. The Access point name is a label or a fully qualified domain name according to DNS naming conventions (see 3GPP TS 23.003[ Numbering, addressing and identification ] [10]). The Access point name is a type 4 information element with a minimum length of 3 octets and a maximum length of 102 octets. The Access point name information element is coded as shown in figure 10.5.152/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.152/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Access point name information element The value part is defined in 3GPP TS 23.003[ Numbering, addressing and identification ] [10].

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

5.7.3 5G QoS characteristics 5.7.3.1 General

This clause specifies the 5G QoS characteristics associated with 5QI. The characteristics describe the packet forwarding treatment that a QoS Flow receives edge-to-edge between the UE and the UPF in terms of the following performance characteristics: 1 Resource type (Non-GBR, GBR, Delay-critical GBR); 2 Priority Level; 3 Packet Delay Budget (including Core Network Packet Delay Budget); 4 Packet Error Rate; 5 Averaging window (for GBR and Delay-critical GBR resource type only); 6 Maximum Data Burst Volume (for Delay-critical GBR resource type only). The 5G QoS characteristics should be understood as guidelines for setting node specific parameters for each QoS Flow e.g. for 3GPP radio access link layer protocol configurations. Standardized or pre-configured 5G QoS characteristics, are indicated through the 5QI value, and are not signalled on any interface, unless certain 5G QoS characteristics are modified as specified in clauses 5.7.3.3, 5.7.3.4, 5.7.3.6, and 5.7.3.7. NOTE: As there are no default values specified, pre-configured 5G QoS characteristics have to include all of the characteristics listed above. Signalled 5G QoS characteristics are provided as part of the QoS profile and shall include all of the characteristics listed above.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.7.3

8.93 MDT Configuration

MDT Configuration is coded as depicted in Figure 8.93-1. Figure 8.93-1: MDT Configuration Parameters in octets 5 to 14, p to q, u, v, w and y to z shall be encoded as specified in 3GPP TS 32.422[ Telecommunication management; Subscriber and equipment trace; Trace control and configuration management ] [18]. If Length of Area Scope equals zero, then Area Scope octets p to q shall not be present. If CRRMI (Collection period for RRM measurements LTE Indicator), bit 1 of octet 's', is set to "1", then the Collection period for RRM measurements LTE parameter field shall be present, otherwise octet 'u' shall not be present. If MPI (Measurement period LTE Indicator), bit 2 of octet 's', is set to "1", then the Measurement period LTE parameter field shall be present, otherwise octet 'v' shall not be present. If PMI (Positioning Method Indicator), bit 3 of octet 's', is set to "1", then the Positioning Method parameter field shall be present, otherwise octet 'w' shall not be present. If PLI (PLMN List Indicator), bit 4 of octet 's', is set to "1", then the Number of MDT PLMNs and MDT PLMN List parameters shall be present, otherwise octet 'x' and octets 'y to z' shall not be present. The value of the Number of MDT PLMNs represents the number of 3-octet PLMNs contained within the MDT PLMN List parameter and shall be a number from 1 to 16. Each PLMN ID in the list shall be encoded as defined for octets 5 to 7 in clause 8.18.

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

15.3.3.5 Inter-system Automatic Neighbour Cell Relation Function

For Inter-system ANR, each cell contains an Inter Frequency Search list. This list contains all frequencies that shall be searched. Figure 15.3.3.5-1 depicts an example where the NG-RAN node serving cell A has an ANR function. Figure 15.3.3.5-1: Automatic Neighbour Relation Function in case of E-UTRAN detected cell In RRC_CONNECTED, the NG-RAN node instructs a UE to perform measurements and detect E-UTRA cells connected to EPC.: 1 The NG-RAN node instructs a UE to look for neighbour cells in the target system. To do so the NG-RAN node may need to schedule appropriate idle periods to allow the UE to scan all cells in the target system. 2 The UE reports the PCI and carrier frequency of the detected cells in the target system. NOTE: The NG-RAN node may use different policies for instructing the UE to do measurements, and when to report them to the NG-RAN node. When the NG-RAN node receives the UE reports containing PCIs of cell(s), the following sequence may be used: 3 The NG-RAN node instructs the UE, using the newly discovered PCI as parameter, to read the ECGI, the TAC and all available PLMN ID(s) of the newly detected cell in case of E-UTRA detected cells. The UE ignores transmissions from the serving cell while finding the requested information transmitted in the broadcast channel of the detected inter-system/inter-frequency neighbour cell. To do so, the NG-RAN node may need to schedule appropriate idle periods to allow the UE to read the requested information from the broadcast channel of the detected inter-system neighbour cell. 4 After the UE has read the requested information in the new cell, it reports the detected ECGI, TAC, and available PLMN ID(s) to the serving cell NG-RAN node. 5 The NG-RAN node updates its inter-system NCRT.

3GPP TS 38.300

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

RAN2

3GPP Series : 38 , Radio technology beyond LTE

15.3.3.5

6.7 Reception of an ESM STATUS message by an ESM entity

The purpose of the sending of the ESM STATUS message is to report at any time certain error conditions detected upon receipt of ESM protocol data. The ESM STATUS message can be sent by both the MME and the UE (see example in figure 6.7.1). If the ESM entity of the UE receives an ESM STATUS message the UE shall take different actions depending on the received ESM cause value: #43 (Invalid EPS bearer identity); The UE shall abort any ongoing ESM procedure related to the received EPS bearer identity, stop any related timer, and deactivate the corresponding EPS bearer context locally (without peer to peer signalling between the UE and the MME). #81 (Invalid PTI value); The UE shall abort any ongoing ESM procedure related to the received PTI value and stop any related timer. #97 (Message type non-existent or not implemented); The UE shall abort any ongoing ESM procedure related to the PTI or EPS bearer identity and stop any related timer. On receipt of an ESM STATUS message with any other ESM cause value no state transition and no specific action shall be taken as seen from the radio interface, i.e. local actions are possible. If the ESM entity of the MME receives an ESM STATUS message the MME shall take different actions depending on the received ESM cause value: #43 (Invalid EPS bearer identity); The MME shall abort any ongoing ESM procedure related to the received EPS bearer identity, stop any related timer, and deactivate the corresponding EPS bearer context locally (without peer to peer signalling between the MME and the UE). #81 (Invalid PTI value); The MME shall abort any ongoing ESM procedure related to the received PTI value and stop any related timer. #97 (Message type non-existent or not implemented); The MME shall abort any ongoing ESM procedure related to the PTI or EPS bearer identity and stop any related timer. The local actions to be taken by the MME on receipt of an ESM STATUS message with any other ESM cause value are implementation dependent. Figure 6.7.1: ESM status procedure

3GPP TS 24.301

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

CT WG1

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

6.7

8 Protocol data unit abstract syntax 8.1 General

The RRC PDU contents in clause 6 and clause 10 are described using abstract syntax notation one (ASN.1) as specified in ITU-T Rec. X.680 [6] and X.681 [7]. Transfer syntax for RRC PDUs is derived from their ASN.1 definitions by use of Packed Encoding Rules, unaligned as specified in ITU-T Rec. X.691 [8]. The following encoding rules apply in addition to what has been specified in X.691: - When a bit string value is placed in a bit-field as specified in 15.6 to 15.11 in X.691, the leading bit of the bit string value shall be placed in the leading bit of the bit-field, and the trailing bit of the bit string value shall be placed in the trailing bit of the bit-field; NOTE: The terms 'leading bit' and 'trailing bit' are defined in ITU-T Rec. X.680. When using the 'bstring' notation, the leading bit of the bit string value is on the left, and the trailing bit of the bit string value is on the right. - When decoding types constrained with the ASN.1 Contents Constraint ("CONTAINING"), automatic decoding of the contained type should not be performed because errors in the decoding of the contained type should not cause the decoding of the entire RRC message PDU to fail. It is recommended that the decoder first decodes the outer PDU type that contains the OCTET STRING or BIT STRING with the Contents Constraint, and then decodes the contained type that is nested within the OCTET STRING or BIT STRING as a separate step; - When decoding a) RRC message PDUs, b) BIT STRING constrained with a Contents Constraint, or c) OCTET STRING constrained with a Contents Constraint, PER decoders are required to never report an error if there are extraneous zero or non-zero bits at the end of the encoded RRC message PDU, BIT STRING or OCTET STRING.

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

8

4.1.3.3 GMM mobility management states on the network side

In this subsubclause, the possible states are described for the GMM on the network side. Subclause 4.1.3.3.1 summarises the main states. The corresponding substates are described in subclause 4.1.3.3.2. However, it should be noted that this subclause does not include a description of the detailed behaviour of the network in the single states and does not cover abnormal cases. Thus, figure 4.1c/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] is rather intended to give an overview of the state transitions than to be a complete state transition diagram. A detailed description of the behaviour of the MS is given in subclause 4.2. Especially, with respect to the behaviour of the MS in abnormal cases it is referred to subclause 4.7.

3GPP TS 24.008

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

CT WG1

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

4.1.3.3

5.3.13.2 Initiation

The UE initiates the procedure when upper layers or AS (when responding to RAN paging, upon triggering RNA updates while the UE is in RRC_INACTIVE, upon requesting multicast reception as specified in clause 5.3.13.1d, for NR sidelink communication/discovery/V2X sidelink communication as specified in clause 5.3.13.1a, for NR sidelink positioning as specified in clause 5.3.13.1c, for requesting configuration for SRS for positioning, for activation of preconfigured Positioning SRS in RRC_INACTIVE, upon receiving RRCRelease message including resumeIndication) requests the resume of a suspended RRC connection or requests the resume for initiating SDT as specified in clause 5.3.13.1b. The UE shall ensure having valid and up to date essential system information as specified in clause 5.2.2.2 before initiating this procedure. Upon initiation of the procedure, the UE shall: 1> if the resumption of the RRC connection is triggered by response to NG-RAN paging; or 1> if the resumption of the RRC connection is triggered by receiving RRCRelease message including resumeIndication; or 1> if the resumption of the RRC connection is triggered by multicast reception request as specified in clause 5.3.13.1d: 2> select '0' as the Access Category; 2> perform the unified access control procedure as specified in 5.3.14 using the selected Access Category and one or more Access Identities provided by upper layers; 3> if the access attempt is barred, the procedure ends; 1> else if the resumption of the RRC connection is triggered by upper layers: 2> if the upper layers provide an Access Category and one or more Access Identities: 3> perform the unified access control procedure as specified in 5.3.14 using the Access Category and Access Identities provided by upper layers; 4> if the access attempt is barred, the procedure ends; 2> if the upper layers provide NSAG information and one or more S-NSSAI(s) triggering the access attempt (TS 23.501[ System architecture for the 5G System (5GS) ] [32] and TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [23]): 3> apply the NSAG with highest NSAG priority among the NSAGs that are included in SIB1 (i.e., in FeatureCombination and/or in RA-PrioritizationSliceInfo), and that are associated with the S-NSSAI(s) triggering the access attempt, in the Random Access procedure (TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3], clause 5.1); NOTE: If there are multiple NSAGs with the same highest NAS-provided NSAG priority identified for access attempt as above, it is left to UE implementation to select the NSAG to be applied in the Random Access procedure. 2> if the resumption occurs after release with redirect with mpsPriorityIndication: 3> set the resumeCause to mps-PriorityAccess; 2> else: 3> set the resumeCause in accordance with the information received from upper layers; 1> else if the resumption of the RRC connection is triggered due to an RNA update as specified in 5.3.13.8: 2> if an emergency service is ongoing: NOTE 1: How the RRC layer in the UE is aware of an ongoing emergency service is up to UE implementation. 3> select '2' as the Access Category; 3> set the resumeCause to emergency; 2> else: 3> select '8' as the Access Category; 2> perform the unified access control procedure as specified in 5.3.14 using the selected Access Category and one or more Access Identities to be applied as specified in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [23]; 3> if the access attempt is barred: 4> set the variable pendingRNA-Update to true; 4> the procedure ends; 1> else if srs-PosRRC-InactiveValidityAreaConfig is configured and the resumption of the RRC connection is triggered due to cell reselection to a cell that is not included in srs-PosConfigValidityArea and there is an on-going SRS for positioning transmission: 2> select '8' as the Access Category; 2> set the resumeCause to srs-PosConfigOrActivationReq; 1> else if srs-PosRRC-InactiveValidityAreaConfig is configured and the resumption of the RRC connection is triggered due to upper layers request for configuration or activation of preconfigured SRS for positioning when the UE is camped in one of the cells indicated in srs-PosConfigValidityArea: 2> select '8' as the Access Category; 2> set the resumeCause to srs-PosConfigOrActivationReq; NOTE 2: In case the L2 U2N Relay UE initiates RRC connection resume triggered by reception of message from a L2 U2N Remote UE via SL-RLC0 or SL-RLC1 as specified in 5.3.13.1a, the L2 U2N Relay UE sets the resumeCause by implementation, but it can only set the emergency, mps-PriorityAccess, or mcs-PriorityAccess as resumeCause, if the same cause value in the message received from the L2 U2N Remote UE via SL-RLC0. 1> if the UE is in NE-DC or NR-DC: 2> if the UE does not support maintaining SCG configuration upon connection resumption: 3> release the MR-DC related configurations (i.e., as specified in 5.3.5.10) from the UE Inactive AS context, if stored; 1> if the UE does not support maintaining the MCG SCell configurations upon connection resumption: 2> release the MCG SCell(s) from the UE Inactive AS context, if stored; 1> if the UE is acting as L2 U2N Remote UE: 2> establish a SRAP entity as specified in TS 38.351[ NR; Sidelink Relay Adaptation Protocol (SRAP) Specification ] [66], if no SRAP entity has been established; 2> apply the default configuration of SL-RLC1 as defined in 9.2.4 for SRB1; 2> apply the default PDCP configuration 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> apply the default L1 parameter values as specified in corresponding physical layer specifications, except for the parameters for which values are provided in SIB1; 2> apply the default SRB1 configuration as specified in 9.2.1; 2> apply the default MAC Cell Group configuration as specified in 9.2.2; 1> release delayBudgetReportingConfig from the UE Inactive AS context, if stored; 1> stop timer T342, if running; 1> release overheatingAssistanceConfig from the UE Inactive AS context, if stored; 1> stop timer T345, if running; 1> release idc-AssistanceConfig from the UE Inactive AS context, if stored; 1> release drx-PreferenceConfig for all configured cell groups from the UE Inactive AS context, if stored; 1> stop all instances of timer T346a, if running; 1> release maxBW-PreferenceConfig and maxBW-PreferenceConfigFR2-2 for all configured cell groups from the UE Inactive AS context, if stored; 1> stop all instances of timer T346b, if running; 1> release maxCC-PreferenceConfig for all configured cell groups from the UE Inactive AS context, if stored; 1> stop all instances of timer T346c, if running; 1> release maxMIMO-LayerPreferenceConfig and maxMIMO-LayerPreferenceConfigFR2-2 for all configured cell groups from the UE Inactive AS context, if stored; 1> stop all instances of timer T346d, if running; 1> release minSchedulingOffsetPreferenceConfig and minSchedulingOffsetPreferenceConfigExt for all configured cell groups from the UE Inactive AS context, if stored; 1> stop all instances of timer T346e, if running; 1> release rlm-RelaxationReportingConfig for all configured cell groups from the UE Inactive AS context, if stored; 1> stop all instances of timer T346j, if running; 1> release bfd-RelaxationReportingConfig for all configured cell groups from the UE Inactive AS context, if stored; 1> stop all instances of timer T346k, if running; 1> release releasePreferenceConfig from the UE Inactive AS context, if stored; 1> release wlanNameList from the UE Inactive AS context, if stored; 1> release btNameList from the UE Inactive AS context, if stored; 1> release sensorNameList from the UE Inactive AS context, if stored; 1> release obtainCommonLocation from the UE Inactive AS context, if stored; 1> stop timer T346f, if running; 1> stop timer T346i, if running; 1> release referenceTimePreferenceReporting from the UE Inactive AS context, if stored; 1> release sl-AssistanceConfigNR from the UE Inactive AS context, if stored; 1> release musim-GapAssistanceConfig from the UE Inactive AS context, if stored and stop timer T346h, if running; 1> release musim-GapConfig from the UE Inactive AS context, if stored; 1> release musim-GapPriorityAssistanceConfig from the UE Inactive AS context, if stored; 1> release musim-LeaveAssistanceConfig from the UE Inactive AS context, if stored; 1> release musim-CapabilityRestrictionConfig from the UE Inactive AS context, if stored and stop timer T346n, if running; 1> release propDelayDiffReportConfig from the UE Inactive AS context, if stored; 1> release ul-GapFR2-PreferenceConfig, if configured; 1> release rrm-MeasRelaxationReportingConfig from the UE Inactive AS context, if stored; 1> release multiRx-PreferenceReportingConfigFR2 if configured, and stop timer T440, if running; 1> release uav-FlightPathAvailabilityConfig from the UE Inactive AS context, if stored; 1> release ul-TrafficInfoReportingConfig from the UE Inactive AS context, if stored; 1> stop all instances of timer T346x, if running; 1> if the UE is acting as L2 U2N Remote UE: 2> apply the specified configuration of SL-RLC0 used for the delivery of RRC message over SRB0 as specified in 9.1.1.4; 2> apply the SDAP configuration and PDCP configuration as specified in 9.1.1.2 for SRB0; 1> else: 2> apply the CCCH configuration as specified in 9.1.1.2; 2> apply the timeAlignmentTimerCommon included in SIB1; 1> if sdt-MAC-PHY-CG-Config is configured: 2> if the resume procedure is initiated in a cell that is different to the PCell in which the UE received the stored sdt-MAC-PHY-CG-Config: 3> release the stored sdt-MAC-PHY-CG-Config; 3> instruct the MAC entity to stop the cg-SDT-TimeAlignmentTimer, if it is running; 1> if ncd-SSB-RedCapInitialBWP-SDT is configured: 2> if the resume procedure is initiated in a cell that is different to the PCell in which the UE received the stored ncd-SSB-RedCapInitialBWP-SDT: 3> release the stored ncd-SSB-RedCapInitialBWP-SDT; 1> if conditions for initiating SDT in accordance with 5.3.13.1b are fulfilled: 2> consider the resume procedure is initiated for SDT; 2> start timer T319a when the lower layers first transmit the CCCH message; 2> consider SDT procedure is ongoing; 1> else: 2> start timer T319; 2> instruct the MAC entity to stop the cg-SDT-TimeAlignmentTimer, if it is running; 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> set the variable pendingRNA-Update to false; 1> release successHO-Config from the UE Inactive AS context, if stored; 1> release successPSCell-Config configured by the PCell from the UE Inactive AS context, if stored; 1> release successPSCell-Config configured by the PSCell from the UE Inactive AS context, if stored; 1> initiate transmission of the RRCResumeRequest message or RRCResumeRequest1 in accordance with 5.3.13.3.

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

5.3.13.2

13.4.1.1.1 OAuth 2.0 roles

OAuth 2.0 roles, as defined in clause 1.1 of RFC 6749 [43], are as follows: a. The Network Repository Function (NRF) shall be the OAuth 2.0 Authorization server. b. The NF Service Consumer shall be the OAuth 2.0 client. c. The NF Service Producer shall be the OAuth 2.0 resource server. OAuth 2.0 client (NF Service Consumer) registration with the OAuth 2.0 authorization server (NRF) The NF Service registration procedure, as defined in clause 4.17.1 of TS 23.502[ Procedures for the 5G System (5GS) ] [8], may be used to register the OAuth 2.0 client (NF Service Consumer) with the OAuth 2.0 Authorization server (NRF), as described in clause 2.0 of RFC 6749 [43]. The client id, used during OAuth 2.0 registration, shall be the NF Instance Id of the NF. OAuth2.0 clients may also register with the NRF using OAM. A Network Function that does not implement this option shall be able to get an access token from the NRF as long as the NRF is able to authenticate and authorize the Network Function during the NF access token get service request. OAuth 2.0 resource server (NF Service Producer) registration with the OAuth 2.0 authorization server (NRF) The NF Service registration procedure, as defined in clause 4.17.1 of TS 23.502[ Procedures for the 5G System (5GS) ] [8], shall be used to register the OAuth 2.0 resource server (NF Service Producer) with the OAuth 2.0 Authorization server (NRF). The NF Service Producer, as part of its NF profile, may include "additional scope" information related to the allowed service operations and resources per NF Service Consumer type. Figure 13.4.1.1-1b NF Service Producer registers in NRF 1) The NF Service Producer registers as OAuth 2.0 resource server in the NRF. The NF profile configuration data of the NF Service Producer may include the "additional scope". The "additional scope" information indicates the resources and the actions (service operations) that are allowed on these resources for the NF Service Consumer. These resources may be per NF type of the NF Service Consumer or per NF instance ID of the NF Service Consumer. 2-3) After storing the NF Profile, NRF responds successfully.

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

13.4.1.1.1

16.10.3 Protocol Architecture

Figure 16.10.3-1 and 16.10.3-2 depict the downlink Layer 2 architecture for multicast session and broadcast session respectively, where MBS protocol stack comprises the same layer 2 sublayers as described in clause 6 with the following differences: - SDAP sublayer provides only the following functionalities: - Mapping between an MBS QoS flow and an MRB; - Transfer of user plane data. - PDCP sublayer provides only the following functionalities: - Transfer of user plane data; - Maintenance of PDCP SNs; - Header compression and decompression using the ROHC protocol or EHC protocol; - Reordering and in-order delivery; - Duplicate discarding. - For a multicast session, gNB provides one or more of the following multicast MRB configuration(s) to the UE via dedicated RRC signalling: - Multicast MRB with DL only RLC-UM or bidirectional RLC-UM configuration for PTP transmission; - Multicast MRB with RLC-AM entity configuration for PTP transmission; - Multicast MRB with DL only RLC-UM entity for PTM transmission; - Multicast MRB with two RLC-UM entities, one DL only RLC-UM entity for PTP transmission and the other DL only RLC-UM entity for PTM transmission; - Multicast MRB with three RLC-UM entities, one DL RLC-UM entity and one UL RLC-UM entity for PTP transmission and the other DL only RLC-UM entity for PTM transmission; - Multicast MRB with two RLC entities, one RLC-AM entity for PTP transmission and the other DL only RLC-UM entity for PTM transmission. - For a multicast session, gNB may change the MRB type using RRC signalling. Figure 16.10.3-1: Downlink Layer 2 Architecture for Multicast Session - For broadcast session, gNB provides the following broadcast MRB configuration to the UE using broadcast RRC signalling: - Broadcast MRB with one DL only RLC-UM entity for PTM transmission. Figure 16.10.3-2: Downlink Layer 2 Architecture for Broadcast Session

3GPP TS 38.300

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

RAN2

3GPP Series : 38 , Radio technology beyond LTE

16.10.3

5.5.4.17 Event X1 (Serving L2 U2N Relay UE becomes worse than threshold1 and NR Cell becomes better than threshold2)

The UE shall: 1> consider the entering condition for this event to be satisfied when both condition X1-1 and condition X1-2, as specified below, are fulfilled; 1> consider the leaving condition for this event to be satisfied when condition X1-3 or condition X1-4, i.e. at least one of the two, as specified below, is fulfilled; Inequality X1-1 (Entering condition 1) Mr + Hys < Thresh1 Inequality X1-2 (Entering condition 2) Mn + Ofn + Ocn – Hys > Thresh2 Inequality X1-3 (Leaving condition 1) Mr – Hys > Thresh1 Inequality X1-4 (Leaving condition 2) Mn + Ofn + Ocn + Hys < Thresh2 The variables in the formula are defined as follows: Mr is the measurement result of the serving L2 U2N Relay UE, not taking into account any offsets. Mn is the measurement result of the NR cell, not taking into account any offsets. Ofn is the measurement object specific offset of the reference signal of the NR cell (i.e. offsetMO as defined within measObjectNR corresponding to the NR cell). Ocn is the cell specific offset of the NR cell (i.e. cellIndividualOffset as defined within measObjectNR corresponding to the frequency of the NR cell, or cellIndividualOffset as defined within reportConfigNR), and set to zero if not configured for the cell. Hys is the hysteresis parameter for this event. Thresh1 is the threshold parameter for this event (i.e. x1-Threshold1-Relay as defined within reportConfigNR for this event). Thresh2 is the threshold parameter for this event (i.e. x1-Threshold2 as defined within reportConfigNR for this event). Mr is expressed in dBm. Mn is expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR. Ofn, Ocn, Hys are expressed in dB. Thresh1 is expressed in the same unit as Mr. Thresh2 is expressed in the same unit as Mn.

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

5.5.4.17

6.2.4D UE maximum output power with additional requirements for ProSe

When UE is configured for E-UTRA ProSe sidelink transmissions non-concurrent with E-UTRA uplink transmissions for E-UTRA ProSe operating bands specified in Table 5.5D-1, the allowed A-MPR for the maximum output power for ProSe physical channels PSDCH, PSCCH, PSSCH, and PSBCH shall be as specified in subclause 6.2.4 for PUSCH for the corresponding modulation and transmission bandwidth. The allowed A-MPR for the maximum output power for ProSe physical signal PSSS and SSSS shall be as be as specified in subclause 6.2.4 for PUSCH QPSK modulation for the corresponding transmission bandwidth. When UE is configured for simultaneous E-UTRA ProSe sidelink and E-UTRA uplink transmissions for inter-band E-UTRA ProSe / E-UTRA bands specified in Table 5.5D-2, the requirements in subclause 6.2.4D apply for ProSe transmission and the requirements in subclause 6.2.4 apply for uplink transmission.

3GPP TS 36.101

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

RAN4

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

6.2.4D

8.4 NR sidelink communication and V2X sidelink communication related identities

The following identities are used for NR sidelink communication: - Source Layer-2 ID: Identifies the sender of the data in NR sidelink communication. The Source Layer-2 ID is 24 bits long and is split in the MAC layer into two bit strings: - One bit string is the LSB part (8 bits) of Source Layer-2 ID and forwarded to physical layer of the sender. This identifies the source of the intended data in sidelink control information and is used for filtering of packets at the physical layer of the receiver; - Second bit string is the MSB part (16 bits) of the Source Layer-2 ID and is carried within the MAC header. This is used for filtering of packets at the MAC layer of the receiver. - Destination Layer-2 ID: Identifies the target of the data in NR sidelink communication. For NR sidelink communication, the Destination Layer-2 ID is 24 bits long and is split in the MAC layer into two bit strings: - One bit string is the LSB part (16 bits) of Destination Layer-2 ID and forwarded to physical layer of the sender. This identifies the target of the intended data in sidelink control information and is used for filtering of packets at the physical layer of the receiver; - Second bit string is the MSB part (8 bits) of the Destination Layer-2 ID and is carried within the MAC header. This is used for filtering of packets at the MAC layer of the receiver. - PC5 Link Identifier: Uniquely identifies the PC5 unicast link in a UE for the lifetime of the PC5 unicast link as specified in TS 23.287[ Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services ] [40]. The PC5 Link Identifier is used to indicate to upper layers the PC5 unicast link in which sidelink RLF was declared and corresponding PC5-RRC connection was released. V2X sidelink communication related identities are specified in clause 8.3 of 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

8.4

C.3.4.2 Profile B

The ME and SIDF shall implement this profile. The ECIES parameters for this profile shall be the following: - EC domain parameters : secp256r1 [30] - EC Diffie-Hellman primitive : Elliptic Curve Cofactor Diffie-Hellman Primitive [29] - point compression : true - KDF : ANSI-X9.63-KDF [29] - Hash : SHA-256 - SharedInfo1 : (the ephemeral public key octet string – see [29] section 5.1.3) - MAC : HMAC–SHA-256 - mackeylen : 32 octets (256 bits) - maclen : 8 octets (64 bits) - SharedInfo2 : the empty string - ENC : AES–128 in CTR mode - enckeylen : 16 octets (128 bits) - icblen : 16 octets (128 bits) - backwards compatibility mode : false

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

C.3.4.2

5.16.3.2a IMS voice over PS Session Supported Indication over non-3GPP access

The serving PLMN AMF shall send an indication toward the UE during the Registration procedure over non-3GPP access to indicate whether an IMS voice over PS session is supported or not supported via non-3GPP access. A UE with "IMS voice over PS" voice capability over non-3GPP access should take this indication (received in the Registration procedure performed over either 3GPP access or Non-3GPP access) into account when performing the selection between N3IWF/TNGF and ePDG described in clause 6.3.6. The serving PLMN AMF may only indicate IMS voice over PS session supported over non-3GPP access if the network is able to provide a successful IMS voice over PS session over N3IWF/TNGF connected to 5GC with a 5G QoS Flow that supports voice as specified in clause 5.7.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.16.3.2a

4.1 Overview

The non-access stratum (NAS) described in the present document forms the highest stratum of the control plane between UE and AMF (reference point "N1" see 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]) for both 3GPP and non-3GPP access. Main functions of the protocols that are part of the NAS are: - support of mobility of the user equipment (UE) including also common procedures such as authentication, identification, generic UE configuration update and security mode control procedures; - support of session management procedures to establish and maintain data connectivity between the UE and the data network; and - NAS transport procedure to provide a transport of SMS, LPP, SLPP, LCS, UPP-CMI container, UE policy container, SOR transparent container and UE parameters update information payload. Principles for the handing of 5GS security contexts and for the activation of ciphering and integrity protection, when a NAS signalling connection is established, are provided in subclause 4.4. For the support of the above functions, the following procedures are supplied within this specification: - elementary procedures for 5GS mobility management in clause 5; and - elementary procedures for 5GS session management in clause 6. Signalling procedures for the control of NAS security are described as part of the 5GMM common procedures in subclause 5.4. Complete NAS transactions consist of specific sequences of elementary procedures. Examples of such specific sequences can be found in 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9]. The NAS for 5GS follows the protocol architecture model for layer 3 as described in 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [11].

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

Annex C (normative): Storage of EMM information

The following EMM parameters shall be stored on the USIM if the corresponding file is present: - GUTI; - last visited registered TAI; - EPS update status; - Allowed CSG list; - Operator CSG list; and - EPS security context parameters from a full native EPS security context (see 3GPP TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [19]). The presence and format of corresponding files on the USIM is specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]. If the corresponding file is not present on the USIM, these EMM parameters except allowed CSG list are stored in a non-volatile memory in the ME together with the IMSI from the USIM. The allowed CSG list is stored in a non-volatile memory in the ME if the UE supports CSG selection. These EMM parameters can only be used if the IMSI from the USIM matches the IMSI stored in the non-volatile memory; else the UE shall delete the EMM parameters. The following EMM parameters shall be stored in a non-volatile memory in the ME together with the IMSI from the USIM: - TIN; - DCN-ID list; and - network-assigned UE radio capability IDs. The TIN parameter can only be used if the IMSI from the USIM matches the IMSI stored in the non-volatile memory of the ME; else the UE shall delete the TIN parameter. The DCN-ID list consists of DCN-IDs stored together with a PLMN identity. The list can have zero or more entries and the maximum length shall be at least 32 entries. When the maximum length is reached any new entry shall replace the oldest entry in the list. There shall be no duplicated PLMN identities in the list and any existing DCN-ID shall be deleted when a new DCN-ID is added for the same PLMN. The DCN-ID list can only be used if the IMSI from the USIM matches the IMSI stored in the non-volatile memory of the ME; else the UE shall delete the DCN-ID list. The UE shall delete the stored DCN-ID list if the default standardized DCN-ID in the UE is changed. Each network-assigned UE radio capability ID is stored together with a PLMN identity of the PLMN that provided it as well as a mapping to the corresponding UE radio configuration, and is valid in that PLMN. A network-assigned UE radio capability ID can only be used if the IMSI from the USIM matches the IMSI stored in the non-volatile memory of the ME, else the UE shall delete the network-assigned UE radio capability ID. The UE shall be able to store at least the last 16 received network-assigned UE radio capability IDs. There shall be only one network-assigned UE radio capability ID stored for a given combination of PLMN identity and UE radio configuration and any existing UE radio capability ID shall be deleted when a new UE radio capability ID is added for the same combination of PLMN identity and UE radio configuration. If the UE receives a network-assigned UE radio capability ID with a Version ID value different from the value included in the network-assigned UE radio capability ID(s) stored at the UE for the serving PLMN, the UE may delete these stored network-assigned UE radio capability ID(s). If the UE is attached for emergency bearer services, the UE shall not store the EMM parameters described in this annex on the USIM or in non-volatile memory. Instead the UE shall temporarily store these parameters locally in the ME and the UE shall delete these parameters when the UE is detached from emergency services (e.g before attaching for normal service. If the UE is configured for eCall only mode as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17], the UE shall not store the EMM parameters described in this annex on the USIM or in non-volatile memory. Instead the UE shall temporarily store these parameters locally in the ME and the UE shall delete these parameters when the UE enters EMM-DEREGISTERED.eCALL-INACTIVE state, the UE is switched-off or the USIM is removed. If the UE is attached for access to RLOS, the UE shall not store the EMM parameters described in this annex on the USIM or in non-volatile memory. Instead, the UE shall temporarily store these parameters locally in the ME and the UE shall delete these parameters after detach.

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

Annex

8.19.4.3 Inter-gNB-CU switch from direct to indirect path

The signalling flow for U2N Remote UE switch from direct to indirect path with gNB-CU change is shown in Figure 8.19.4.3-1. Figure 8.19.4.3-1. U2N Remote UE Direct-to-indirect Path Switch with gNB-CU change procedure 1. The Uu measurement configuration and measurement report signalling are performed between U2N Remote UE and source gNB-CU to evaluate both relay link measurement and Uu link measurement. The U2N Remote UE may report one or multiple candidate U2N Relay UE(s) and Uu measurement results after it measures/discovers the candidate U2N Relay UE(s). 2. The source gNB-CU decides to switch the U2N Remote UE to one of the candidate U2N Relay UE(s). 3. The source gNB-CU sends the HANDOVER REQUEST message to the target gNB-CU. The HANDOVER REQUEST message may include a list of candidate U2N Relay UE(s) of same cell of the target gNB. 4. The target gNB-CU decides to accept the indirect path switching to the target U2N Relay UE among the candidate U2N Relay UE(s). 5. The reconfiguration to target U2N Relay UE is performed among target U2N Relay UE, the target gNB-DU and target gNB-CU, if the target U2N Relay UE is in RRC_CONNECTED state. The target gNB-CU allocates the local ID for the U2N Remote UE. The target gNB-CU sends an RRCReconfiguration message to the target U2N Relay UE. If the target U2N Relay UE is in RRC_IDLE/INACTIVE state, this step is skipped and the configuration to the target U2N Relay UE is performed in Step 15. 6. The target gNB-CU sends the UE CONTEXT SETUP REQUEST message for the U2N Remote UE to the target gNB-DU, which contains the path switch configuration at least. 7. The target gNB-DU responds with the UE CONTEXT SETUP RESPONSE message to the target gNB-CU. 8. The target gNB-CU responds the source gNB-CU with an HANDOVER REQUEST ACKNOWLEDGE message by including the RRCReconfiguration message. The contents in the RRCReconfiguration message may include at least path switch configuration, PC5 Relay RLC channel configuration for relay traffic, bearer mapping and the associated radio bearer(s). 9. The source gNB-CU sends to the source gNB-DU the UE CONTEXT MODIFICATION REQUEST message to send the handover command to the U2N Remote UE, and to indicate to stop the data transmission for the U2N Remote UE. 10. The source gNB-DU sends the RRCReconfiguration message to the U2N Remote UE. The U2N Remote UE stops UP and CP transmission over Uu after reception of RRCReconfiguration message from the source gNB. 11. The source gNB-DU sends the UE CONTEXT MODIFICATION RESPONSE message to the source gNB-CU. 12. The source gNB-CU sends an SN STATUS TRANSFER message to the target gNB-CU. 13. Data Forwarding may be performed from the source gNB-CU to the target gNB-CU. 14. The U2N Remote UE establishes PC5 connection with target U2N Relay UE. 15. The U2N Remote UE completes the path switch procedure by sending the RRCReconfigurationComplete message to the target gNB-DU via the target U2N Relay UE. In case the target U2N Relay UE is in RRC_IDLE/ INACTIVE state when receiving the RRCReconfigurationComplete message, the reception of the RRCReconfigurationComplete message will first trigger RRC setup/resume procedure for the target U2N Relay UE to enter RRC_CONNECTED state. 16. The target gNB-DU sends the UL RRC MESSAGE TRANSFER message to target gNB-CU by including the RRCReconfigurationComplete message. 17. Path Switch procedure is performed to switch the DL data path towards the target gNB-CU and to establish an NG-C interface instance towards the target gNB-CU. 18. The target gNB-CU sends an UE CONTEXT RELEASE message to the source gNB-CU. 19. The source gNB-CU initiates a F1 UE Context Release procedure to release the UE context of the U2N Remote UE in the source gNB-DU.

3GPP TS 38.401

NG-RAN; Architecture description

RAN3

3GPP Series : 38 , Radio technology beyond LTE

8.19.4.3

4.11.1.5.6 UE triggered Service Request

The following changes are applied to clause 5.3.4.1 (UE triggered Service Request) in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13]: - Step 4: MME may steer the UE from EPC by rejecting the service request with an appropriate cause value. The MME should take into account availability of 5GC to the UE and the Preferred and Supported Network Behaviour (see clause 5.31.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]) before steering the UE from EPC.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.11.1.5.6

A.3 Representation in an information flow

Invoking a service or service operation within an information flow is represented using a disaggregated representation (see figure A.3-1). The disaggregated representations on figure A.3-1 shall be used as follows: - The <step> represents the actual step number in the information flow e.g. ″7.″. - Representation a) shall be used when the step is required. - Representation b) shall be used when the step is optional or conditional. Figure A.3-1: Disaggregated representation of a NF service or service operation in information flows NOTE: Depending on the information flow, the order of NF Producer and NF Consumer can be reversed.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

A.3

P.3 Security aspects of ICMP

ICMP (Internet Control Message Protocol) is part of the internet protocol (IP) suite. The lack of security in ICMP may be exploited to launch further attacks on the 3GPP system. To mitigate such attacks, it is recommended that the use of ICMP is restricted in the UE and the UPF (e.g., by default, use of ICMP is not allowed). In scenarios where the use of ICMP is required, it is recommended that one or more of following mitigations be enforced: - Disable the UE from responding to ICMP requests received over 3GPP network interface(s). - Install IP filter(s) at the UPF in order to block ICMP messages. This filter can be activated either on a per N4 Session basis or on a UPF basis. For ICMPv6, the recommendations in RFC 4890 [85] can be used for filtering ICMPv6 messages. - Limit the maximum size of ICMP messages (e.g., to 64 bytes). Any ICMP messages that are greater than this limit needs to be dropped by the UE as well as by the UPF.

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

P.3

8.1.2.3 Applicability and test rules for different CA configurations and bandwidth combination sets

The performance requirement for CA UE demodulation tests in Clause 8 are defined independent of CA configurations and bandwidth combination sets specified in Clause 5.6A. For UEs supporting different CA configurations and bandwidth combination sets, the applicability and test rules are defined for the tests for 2 DL CCs in Table 8.1.2.3-1 and 3 or more DL CCs in Table 8.2.2.3-2. For simplicity, CA configuration below refers to combination of CA configuration and bandwidth combination set. Table 8.1.2.3-1: Applicability and test rules for CA UE demodulation tests with 2 DL CCs Table 8.1.2.3-2: Applicability and test rules for CA UE demodulation tests with 3 or more DL CCs

3GPP TS 36.101

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

RAN4

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

8.1.2.3

5.2.7.3.2 Nnrf_NFDiscovery_Request service operation

Service operation name: Nnrf_NFDiscovery_Request Description: provides the IP address or FQDN of the expected NF instance(s) and if present in NF profile, the Endpoint Address(es) of NF service instance(s) to the NF service consumer or SCP. Inputs, Required: one or more target NF service Name(s), NF type of the target NF, NF type of the NF service consumer. If the NF service consumer intends to discover an NF service producer providing all the standardized services, it provides a wildcard NF service name. Inputs, Optional: - S-NSSAI and the associated NSI ID (if available), DNN, target NF/NF service PLMN ID (or realm in the case of network specific identifier type SUCI/SUPI, see clause 4.17.5a), NRF to be used to select NFs/services within HPLMN or Credentials Holder, Serving PLMN ID (or PLMN ID and NID in the case of SNPN, see clause 4.17.5a), the NF service consumer ID, preferred target NF location, TAI. NOTE 1: For network slicing the NF service consumer ID is a required input. - FQDN for the S5/S8 interface of the SMF+PGW-C, to discover the N11/N16 interface of the SMF+PGW-C in the case of EPS to 5GS mobility. - If the target NF stores Data Set(s) (e.g. UDR, BSF): SUPI, GPSI, IMPI, IMPU, Data Set Identifier(s). (UE) IPv4 address, IP domain or (UE) IPv6 Prefix. NOTE 2: GPSI is relevant for BSF. NOTE 3: If the request includes a subscriber identifier the NRF may need to use the association between the supplied subscriber identifier and the appropriate NF Group ID as described in clause 6.3.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] to determine the applicable set of NF instances for the response. NOTE 4: The (UE) IPv4 address or (UE) IPv6 Prefix is provided for BSF discovery: in that case the NRF looks up for a match within one of the Range(s) of (UE) IPv4 addresses or Range(s) of (UE) IPv6 prefixes provided by BSF(s) as part of the invocation of Nnrf_NFManagement_NFRegister operation. The NRF is not meant to store individual (UE) IPv4 addresses or (UE) IPv6 prefixes. - If the target NF is UDM or AUSF, the request may include the UE's Routing Indicator, or the UE's Routing Indicator and Home Network Public Key identifier. - If the target UDM or NF is AUSF, the request may include the UE's HNI: PLMN ID in the case of PLMN, PLMN ID + NID in the case of SNPN. Optionally, some NFs may additionally include a Home Network Identifier in the form of a realm e.g. in the case of access to an SNPN using credentials owned by CH with AAA Server or in the case of SNPN Onboarding using a DCS with AAA Server. - If the target NF is NSSAAF, the request may include Home Network Identifier in the form of a realm e.g. in the case of access to an SNPN using credentials owned by CH with AAA Server or in the case of SNPN Onboarding using credentials from a DCS with AAA Server. - If the target NF is AMF and the consumer NF is MB-SMF for broadcast service, the request includes TAI(s) (see clause 7.3 of TS 23.247[ Architectural enhancements for 5G multicast-broadcast services ] [78]). - If the target NF is AMF and the consumer NF is other than MB-SMF, the request may include: - AMF region, AMF Set, GUAMI and Target TAI(s). - If the target NF is UDR or UDM or AUSF or PCF or BSF, the request may include UDR Group ID or UDM Group ID or AUSF Group ID or PCF Group ID or BSF Group ID respectively. NOTE 5: It is assumed that the corresponding NF service consumer is either configured with the corresponding Group ID or it received it via earlier Discovery output. - If the target NF is UDM, the request may include SUPI, GPSI, Internal Group ID and External Group ID. - If the target NF is UPF, the request may include SMF Area Identity, UE IPv4 Address/IPv6 Prefix, supported ATSSS steering functionality, the supported UPF event exposure service and the supported Event IDs that can be subscribed. And if UPF can expose NAT information, the UE IPv4 address/IPv6 Prefix seen by the DN (e.g. a Public IP address). NOTE 6: If UE's IPv4 address or IPv6 Prefix is provided for UPF discovery, then the NRF looks up for a match within one of the Range(s) of IPv4 addresses or IPv6 prefixes provided by UPF in the NF profile at the invocation of Nnrf_NFManagement_NFRegister operation. The NRF is not meant to store the UE's individual IPv4 addresses or IPv6 prefixes. NOTE 7: Discovering UPF at PDU Session Establishment time and creating the N4 association assumes full connectivity between SMF and UPFs. - If the target NF is CHF, the request may include SUPI or GPSI as specified in TS 32.290[ Telecommunication management; Charging management; 5G system; Services, operations and procedures of charging using Service Based Interface (SBI) ] [42]. - If the target NF is PCF or SMF, the request may include the MA PDU Session capability to indicate that a NF instance supporting MA PDU session capability is requested. - If the target NF is PCF, the request may include the DNN replacement capability to indicate that a NF instance supporting DNN replacement capability is preferred. - If the target NF is PCF or SMF, the request may include the slice replacement capability to indicate that a NF instance supporting slice replacement capability is preferred. - If the target NF is PCF, the request may include the 5G ProSe Capability as specified in TS 23.304[ Proximity based Services (ProSe) in the 5G System (5GS) ] [77]. - If the target NF is PCF, the request may include the V2X capability as specified in TS 23.287[ Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services ] [73]. - If the target NF is PCF, the request may include the A2X capability as specified in TS 23.256[ Support of Uncrewed Aerial Systems (UAS) connectivity, identification and tracking; Stage 2 ] [80]. - If the target NF is NWDAF, the request may include: - Analytics ID(s) (possibly per service). - TAI(s). - Analytics aggregation capability and/or Analytics metadata provisioning capability. - A Real-Time Communication Indication per Analytics ID, NF Set ID and NF Type of the NF data sources. - Roaming exchange capability if data/analytics exchange between PLMNs is needed. - The S-NSSAI(s), Area(s) of Interest of the Trained ML Model required and NF consumer information when the target is an NWDAF containing MTLF. - Required FL capability type (i.e. FL server, FL client, if available) and Time period of interest when the target is an NWDAF containing MTLF with FL capability. When the target is an NWDAF containing MTLF with FL client capability, NF Set ID(s) of data source and NF type(s) where data can be collected as input for local model training may be included. - If the target NF is NWDAF containing MTLF with ML Model Accuracy checking capability, it includes ML Model Accuracy checking capability for ML model Accuracy Monitoring (see clause 5.2 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]). - If the target NF is NWDAF containing AnLF with Analytics Accuracy checking capability, it includes Analytics Accuracy checking capability for Analytics Accuracy Monitoring (see clause 5.2 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]). Details about NWDAF discovery and selection are described in clause 6.3.13 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. NOTE 8: Analytics metadata provisioning capability is only applicable when NF service consumer is NWDAF. NOTE 9: NF consumer information such as vendor ID is defined in stage 3. - If target NF is ADRF, the request may include: - Data and analytics storage and retrieval capability. - ML model storage and retrieval capability. Details about ADRF discovery and selection are described in clause 6.3.20 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. - If the target NF is HSS, the request may include IMPI and/or IMPU and/or HSS Group ID. - If the NF service consumer needs to discover NF service producer instance(s) within an NF instance, the request includes the target NF Instance ID and NF Service Set ID of the producer. - If the NF service consumer needs to discover NF service producer instance(s) in an equivalent NF Service Set within an NF Set, the request includes the identification of the equivalent NF service Set and NF Set ID of producer. NOTE 10: TS 29.510[ 5G System; Network function repository services; Stage 3 ] [37] specifies the mechanism to identify equivalent NF Service Sets. - If the NF service consumer needs to discover NF service producer instance(s) in the NF Set, the request includes the target NF Set ID of the producer. - If the target NF is SMF, the request may include: - the UE location (TAI); or - TAI list. - If the target NF is P-CSCF, the request may include UE location information, UE IP address/IP prefix, Access Type. - If the target NF is NEF, the request may include Event ID(s) provided by AF and optional AF identification as described in clause 6.2.2.3 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]. When the consumer is an AF, the request may include an External Identifier, External Group Identifier, or a domain name. If the target NF is local NEF, the request may include the parameters of list of supported TAI or list of supported DNAI additionally. - If the target NF is SMF, the request may include the Control Plane CIoT 5GS Optimisation Indication or User Plane CIoT 5GS Optimisation Indication. - If the target NF is a NSACF, the request may include the S-NSSAI(s) of the PLMN or SNPN where the NSACF is located , the NSAC Service Area Identifier and NSACF service capability. Details about NSACF discovery and selection are described in clause 6.3.22 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. - If the target NF is SCP, the request may include information about: - SCP domain(s). - Remote PLMN reachable through SCP. - Endpoint addresses or Address Domain(s) (e.g. IP Address or FQDN ranges) accessible via the SCP. - NF sets of NFs served by the SCP. - If the target NF is MB-SMF, the request may include UE location (i.e. TAI), MBS Session ID and Area Session ID. Details about MB-SMF discovery and selection are described in TS 23.247[ Architectural enhancements for 5G multicast-broadcast services ] [78]. - If the target NF is 5G DDNMF, the request may include SUPI, IP Address or FQDN of 5G DDNMF. - If the target NF is DCCF, the request may include TAI(s), NF type of the NF data sources, NF Set ID of the NF data sources, support for relocation of data subscription. Details about DCCF discovery and selection are described in clause 6.3.19 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. - If the target NF is EASDF, the request may include S-NSSAI, DNN, N6 IP address of the PSA UPF, location as per NF profile and DNAI(if exist). Details about EASDF discovery and selection are described in clause 6.3.23 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. - If the target NF is AMF, the request may include the support of SNPN Onboarding to indicate whether the target NF instance supports SNPN Onboarding or not. - If the target NF is SMF, the request may include the support of User Plane Remote Provisioning to indicate whether the target NF instance supports User Plane Remote Provisioning or not as described in clause 5.30.2.10.4.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. - If the target NF is NEF, the request may include the support of UAS NF functionality, the capability to support Multi-member AF session with required QoS and the capability to support member UE selection assistance functionality. - If the target NF is NSSAAF, the request may include SUPI or Internal Group ID. - If the target NF is DCSF, the request may include IMPU of calling party, SIP URI or Tel URI of called party. - If the target NF is MF, the request may include the list of required data channel media capabilities or MF location information as specified in TS 23.228[ IP Multimedia Subsystem (IMS); Stage 2 ] [55]. - If the target NF is MRF or MRFP, it includes the list of required IMS media services (as defined in TS 23.228[ IP Multimedia Subsystem (IMS); Stage 2 ] [55]). Outputs, Required: A set of NF instances, a validity period for the discovery result, containing per NF Instance: NF type, NF instance ID, FQDN or IP address(es) of the NF instance and if applicable, a list of services instances, where each service instance has a service name, a NF service instance ID and optionally Endpoint Address(es) Endpoint Address(es) may be a list of IP addresses or an FQDN for the NF service instance. NOTE 11: SCPs does not have any service instances. Outputs, Optional: Per NF instance, other information in the NF profile listed in clause 6.2.6 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] related to the NF instance, such as: - NF load information. - NF capacity information. - NF priority information. - If the target NF stores Data Set(s) (e.g. UDR): Range(s) of SUPIs, range(s) of GPSIs, range(s) of external group identifiers, Data Set Identifier(s). If the target NF is BSF or P-CSCF: Range(s) of (UE) IPv4 addresses or Range(s) of (UE) IPv6 prefixes, Range(s) of SUPIs, range(s) of GPSIs. NOTE 12: Range of SUPI(s) is limited in this release to a SUPI type of IMSI as defined in TS 23.003[ Numbering, addressing and identification ] [33]. - If the target NF is UDM, UDR, PCF, BSF or AUSF, they can include UDM Group ID, UDR Group ID, PCF Group ID, BSF Group ID, AUSF Group ID respectively. - If the target NF is HSS, it can include HSS Group ID. - For UDM and AUSF, Routing Indicator, or Routing Indicator and Home Network Public Key identifier. - If the target NF is AMF, it includes list of GUAMI(s). In addition, it may include list of GUAMI(s) for which it can serve as backup for failure/maintenance. - If the target NF is CHF, it includes primary CHF instance and the secondary CHF instance pair(s), if configured in CHF instance profile. - For the UPF Management: UPF Provisioning Information as defined in clause 4.17.6. - S-NSSAI(s) and the associated NSI ID(s) (if available). - Information about the location of the target NF (operator specific information, e.g. geographical location, data centre). - TAI(s). - PLMN ID. - If the target is PCF or SMF, it includes the MA PDU Session capability to indicate if the NF instance supports MA PDU session or not. - If the target is PCF, it includes the DNN replacement capability to indicate if the NF instance supports DNN replacement or not. - If the target NF is NWDAF, it may include: - Analytics ID(s) (possibly per service). - NF Set ID and NF Type of the NF data sources, if available, NWDAF Serving Area information. - Analytics aggregation capability and/ or Analytics metadata provisioning capability, if such capability is provided by the NWDAF. - Supported Analytics Delay per Analytics ID. - If the target NF is NWDAF, it may also include the ML model Filter information parameters S-NSSAI(s) and Area(s) of Interest for the trained ML model(s) per Analytics ID(s) and ML Model Interoperability indicator per Analytics ID(s), if available (see clause 5.2 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]). - If the target NF is NWDAF with FL capability, it may also include FL capability information per analytics ID containing FL capability type (i.e. FL server, FL client, if available) and Time interval supporting FL, if available (see clause 5.2 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]). Details about NWDAF specific information are described in clause 6.3.13 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. NOTE 13: The Supported Analytics Delay is provided for an Analytics ID only when the NRF had received Real-Time Communication Indication for this Analytics ID in the NWDAF discovery request. - If the target is a trusted AF, it includes one or multiple combination(s) of the S-NSSAI and DNN corresponding to the AF. In addition, it may include supported Application Id(s), Event ID(s) supported by the AF and Internal-Group Identifier. - NF Set ID. - NF Service Set ID. - If the target NF is SMF, it may include the SMF(s) Service Area. NOTE 14: If no SMF Service Area is provided, the AMF assumes that a SMF can serve the whole PLMN. - If the target NF is P-CSCF, it includes P-CSCF FQDN(s) or IP address(es) and optional Access Type(s) associated with each P-CSCF. - If the target NF is NEF, it may include Event ID(s) provided by AF and/or it includes one or multiple combination(s) of the S-NSSAI and DNN corresponding to the untrusted AF served by the NEF. - SCP domain the NF belongs to. NOTE 15: Only one SCP domain is registered in NF profile for an NF. - If the target is SCP: - SCP domain(s). - Remote PLMNs reachable through SCP. - Endpoint addresses or Address Domain(s) (e.g. IP Address or FQDN ranges) accessible via the SCP. - NF sets of NFs served by the SCP. - If the target NF is 5G DDNMF, it may include IP Address or FQDN of 5G DDNMF. - If the target NF is MB-SMF, it may include the MBS Session ID(s), Area Session ID(s), corresponding MBS service area(s) as described in TS 23.247[ Architectural enhancements for 5G multicast-broadcast services ] [78]. - If the target NF is DCCF, it includes DCCF serving area information, NF type of the NF data sources, NF Set ID of the NF data sources, support for relocation of data subscription. Details about DCCF specific information are described in clause 6.3.19 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. See clause 4.17.4 and 4.17.5 for details on the usage of this service operation.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

5.2.7.3.2

17.8 Gmb specific Experimental-Result-Code AVP values 17.8.0 General

There are two different types of errors in Diameter; protocol and application errors. A protocol error is one that occurs at the base protocol level, those are covered in the Diameter Base IETF RFC 6733 [111] specific procedures. Application errors, on the other hand, generally occur due to a problem with a function specified in a Diameter application. Diameter Base IETF RFC 6733 [111] defines a number of Result-Code AVP values that are used to report protocol errors and how those are used. Those procedures and values apply for the present specification. Due to the Gmb specific AVPs, new applications errors can occur. The Gmb specific errors are described by the Experimental-Result-Code AVP in this clause, below. Note that according to IETF RFC 6733 [111], the Diameter node reports only the first error encountered and only one Result-Code AVP or one Experimental-Result AVP is included in the Diameter answer.

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

12.3.10.2.1 Good throughput of the network

A source GTP-C entity should avoid any mechanism resulting in over throttling of the messages. Enforcement of the overload control whilst ensuring that good throughput (i.e. measured in terms of the rate of total number of messages the overloaded GTP-C entity can successfully process) of the network remains consistent to that when no overload control is applied, should be one of the prime objective of the source GTP-C entity. NOTE: Over throttling of messages would negatively affect end user services and cause potential additional signalling in the network e.g. if the corresponding procedure is retried at a later time.

3GPP TS 29.274

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

CT WG4

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

12.3.10.2.1

21.2.3 Handling of QMC during RAN Overload

The QoE measurement collection pause/resume procedure is used to pause/resume reporting of one or multiple QoE measurement configurations in a UE in RAN overload situation. The gNB can use the RRCReconfiguration message to temporarily stop the UE from sending application layer measurement reports associated with one or multiple application layer measurement configurations. When the UE receives the QoE measurement collection pause indication, the UE temporarily stores application layer measurement reports in AS layer. When the UE receives the QoE measurement collection resume indication, the UE sends the stored application layer measurement reports to the gNB. For a QoE measurement configuration, the assistance information provided by the OAM may be considered by the gNB for deciding whether to pause/resume the measurement reporting of certain QoE measurement configurations in case of RAN overload.

3GPP TS 38.300

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

RAN2

3GPP Series : 38 , Radio technology beyond LTE

21.2.3

5.3.11.2 UE Reachability Notification Request procedure

The UE Reachability Notification Request procedure is illustrated in Figure 5.3.11.2-1. Figure 5.3.11.2-1: UE Reachability Notification Request Procedure 1) If a service-related entity requests the HSS to provide an indication regarding UE reachability on EPS, the HSS stores the service-related entity and sets the URRP-MME parameter to indicate that such request is received. If the value of URRP-MME parameter has changed from "not set" to "set", the HSS sends a UE-REACHABILITY-NOTIFICATION-REQUEST (URRP-MME) to the MME. If the MME has an MM context for that user, the MME sets URRP-MME to indicate the need to report to the HSS information regarding changes in UE reachability, e.g. when the next NAS activity with that UE is detected.

3GPP TS 23.401

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

SA WG2

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

5.3.11.2

5.2.5.2.4 Npcf_AMPolicyControl_Delete service operation

Service operation name: Npcf_AMPolicyControl_Delete Description: Provides means for the NF Consumer to delete the AM Policy Association. Inputs, Required: AM Policy Association ID. Inputs, Optional: None. Outputs, Required: Success or Failure. Outputs, Optional: None. See clause 4.16.3.2 (step 2 and 3) for the detail usage of this service operation for AMF. In step 2, the AMF initiates the AM Policy Association Termination procedure; in step 3 the PCF deletes the AM Policy Association for this AM Policy Association ID.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

5.2.5.2.4

5.5.2.2.6 Abnormal cases in the UE

The following abnormal cases can be identified: a) Lower layer failure or release of the N1 NAS signalling connection before reception of DEREGISTRATION ACCEPT message. The de-registration procedure shall be aborted and the UE proceeds as follows: 1) if the de-registration procedure was performed due to disabling of 5GS services, the UE shall enter the 5GMM-NULL state; or 2) if the de-registration type "normal de-registration" was requested for reasons other than disabling of 5GS services, the UE shall enter the 5GMM-DEREGISTERED state. b) The lower layers indicate that the access attempt is barred. The UE shall not start the de-registration signalling procedure. The UE stays in the current serving cell and applies the normal cell reselection process. Receipt of the access barred indication shall not trigger the selection of a different core network type (EPC or 5GCN). The UE may perform a local de-registration either immediately or after an implementation-dependent time. The de-registration signalling procedure is started, if still needed, when the lower layers indicate that the barring is alleviated for the access category with which the access attempt was associated. ba) The lower layers indicate that: 1) access barring is applicable for all access categories except categories 0 and 2 and the access category with which the access attempt was associated is other than 0 and 2; or 2) access barring is applicable for all access categories except category 0 and the access category with which the access attempt was associated is other than 0. If the DEREGISTRATION REQUEST message has not been sent, the UE shall proceed as specified for case b. If the DEREGISTRATION REQUEST message has been sent, the UE shall proceed as specified for case a. c) T3521 timeout. If the de-registration procedure was performed based on conditions specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] annex C, on the expiry of timer T3521 the de-registration procedure shall be aborted and the UE shall locally release the established N1 NAS signalling connection and enter the 5GMM-DEREGISTERED state. Otherwise, on the first four expiries of the timer, the UE shall retransmit the DEREGISTRATION REQUEST message and shall reset and restart timer T3521. On the fifth expiry of timer T3521, the de-registration procedure shall be aborted and the UE proceeds as follows: 1) if the de-registration procedure was performed due to disabling of 5GS services, the UE shall enter the 5GMM-NULL state; or 2) if the de-registration type "normal de-registration" was requested for reasons other than disabling of 5GS services, the UE shall enter the 5GMM-DEREGISTERED state. d) De-registration procedure collision. De-registration containing de-registration type "switch off": - If the UE receives a DEREGISTRATION REQUEST message before the UE-initiated de-registration procedure has been completed, this message shall be ignored and the UE-initiated de-registration procedure shall continue. Otherwise: - If the UE receives a DEREGISTRATION REQUEST message before the UE-initiated de-registration procedure has been completed, it shall treat the message as specified in subclause 5.5.2.3.2 with the following modification: - If the DEREGISTRATION REQUEST message received by the UE contains de-registration type "re-registration required", and the UE-initiated de-registration procedure is with de-registration type "normal de-registration": - If the access type included in the DEREGISTRATION REQUEST message sent by the UE is same as access type sent by the network, the UE need not initiate the registration procedure for initial registration; or - If the access type included in the DEREGISTRATION REQUEST message sent by the UE is not same as access type sent by the network, the UE shall initiate the registration procedure for initial registration for the access type not indicated in the DEREGISTRATION REQUEST message sent by the UE but indicated by the network. e) De-registration and 5GMM common procedure collision. De-registration containing de-registration type "switch off": - If the UE receives a message used in a 5GMM common procedure before the de-registration procedure has been completed, this message shall be ignored and the de-registration procedure shall continue. Otherwise: - If the UE receives a message used in a 5GMM common procedure before the de-registration procedure has been completed, both the 5GMM common procedure and the de-registration procedure shall continue; or - If the UE receives a DL NAS TRANSPORT message containing payload container type "Service-level-AA container" before the de-registration procedure has been completed, this message shall be ignored and the de-registration procedure shall continue. f) Change in the current TAI. If that the current TAI is not in the stored TAI list before the UE-initiated de-registration procedure is completed, the UE proceeds as follows: 1) if the de-registration procedure was initiated for reasons other than removal of the USIM, the UE is to be switched off or due to the last Tsor-cm timer expiry or stopped (see 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]), the de-registration procedure shall be aborted and re-initiated after successfully performing a registration procedure for mobility or periodic update used for mobility (i.e. the 5GS registration type IE set to "mobility registration updating" in the REGISTRATION REQUEST message); or 2) if the de-registration procedure was initiated due to removal of the USIM or the UE is to be switched off or due to the last Tsor-cm timer expiry or stopped (see 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]), the UE shall abort the de-registration procedure, perform a local de-registration and enter the state 5GMM-DEREGISTERED. g) Transmission failure of DEREGISTRATION REQUEST message indication with change in the current TAI. If the current TAI is not in the TAI list, the UE proceeds as follows: 1) if the de-registration procedure was initiated for reasons other than removal of the USIM ,the UE is to be switched off or due to the last Tsor-cm timer expiry or stopped (see 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]), the de-registration procedure shall be aborted and re-initiated after successfully performing a registration procedure for mobility or periodic update; or 2) if the de-registration procedure was initiated due to removal of the USIM or the UE is to be switched off or due to the last Tsor-cm timer expiry or stopped (see 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]), the UE shall abort the de-registration procedure, perform a local de-registration and enter the state 5GMM-DEREGISTERED. If the current TAI is still part of the TAI list, the UE shall restart the de-registration procedure. h) Transmission failure of DEREGISTRATION REQUEST message indication without change in the current TAI. The UE shall restart the de-registration procedure. i) The lower layers indicate that the RRC connection has been suspended. De-registration containing de-registration type "switch off": - The UE may perform a local de-registration either immediately or after an implementation-dependent time. Otherwise: - The UE shall wait for an implementation-dependent time and shall restart the de-registration procedure, if still needed, upon expiry of the implementation-dependent time. For the cases a, f, g and i: - Timer T3521 shall be stopped if still running.

3GPP TS 24.501

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

CT WG1

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

5.5.2.2.6

6.4.1 Physical downlink shared channel for BL/CE UEs

For BL/CE UEs, the following additions and exceptions hold in addition to those in clause 6.4: - The maximum number of allocatable PRBs for PDSCH is restricted as follows: - If the PDSCH is associated with C-RNTI or SPS C-RNTI and the higher layer parameter ce-pdsch-maxBandwidth-config is set, - if the higher layer parameter ce-pdsch-maxBandwidth-config is set to 20 MHz, the maximum number of allocatable PRBs for PDSCH is 96 PRBs restricted to the narrowbands defined in clause 6.2.7; - if the higher layer parameter ce-pdsch-maxBandwidth-config is set to 5 MHz, the maximum number of allocatable PRBs for PDSCH is 24 PRBs restricted to no more than four of the narrowbands defined in clause 6.2.7. - If the PDSCH is associated with G-RNTI and the higher layer parameter pdsch-MaxBandwidth-SC-MTCH is set to 24 PRBs, the maximum number of allocatable PRBs for PDSCH is 24 PRBs restricted to no more than four of the narrowbands defined in clause 6.2.7. - For all other cases, the maximum number of allocatable PRBs for PDSCH is 6 PRBs restricted to one of the narrowbands defined in clause 6.2.7. - Resource elements occupied by CSI reference signals shall be counted in the PDSCH mapping but not used for transmission of the PDSCH. - Resource elements belonging to synchronization signals, the core part of PBCH, PBCH repetitions, or resource elements reserved for reference signals in the mapping operation of PBCH but not used for transmission of reference signals, shall be counted in the PDSCH mapping but not used for transmission of the PDSCH. - PRB pairs occupied by RSS shall be counted in the PDSCH mapping but not used for transmission of the PDSCH. - For BL/CE UEs in CEModeB configured in transmission mode 9, in MBSFN subframe(s), resource elements that correspond to the positions of cell-specific reference signals as in subframe #0 shall not be counted in the PDSCH mapping and not used for transmission of the PDSCH. - Resource elements belonging to PRBs in which PRS is transmitted (including PRS muted subframes) shall be counted in the PDSCH mapping but not used for transmission of the PDSCH. - If the higher layer parameter ce-punctured-subcarriers-DL is configured, and the DCI associated with the PDSCH uses C-RNTI or SPS C-RNTI, and transmit diversity according to clause 6.3.4.3 is used, - In the mapping to resource elements, when the complex-valued symbols and , where is an even number, are mapped to resource elements and in the same OFDM symbol with , then if ce-punctured-subcarriers-DL indicates that any of and shall be counted but not used for transmission, the UE shall assume that both and are counted but not used for transmission. - If PDSCH transmission in the LTE control region is configured by higher layer parameter transmissionInControlChRegion, after the initial mapping of the PDSCH to resource elements starting from in the first slot to the last OFDM symbol available for downlink transmission in the subframe has been performed, the mapping shall continue with resource elements not reserved for cell-specific reference signals in increasing order of first the index over the assigned physical resource blocks and then the index starting from in the first slot to in the first slot, where is given by clause 7.1.6.4 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4]. For BL/CE UEs, if the PDSCH is not carrying SIB1-BR the PRB resources for PDSCH transmission in the first subframe are obtained from the DCI as described in clauses 5.3.3.1.12, 5.3.3.1.13, and 5.5.1.3.14 in [3], or provided by higher layers. Each of the PDSCH codewords is transmitted with repetitions, where is the number of transport blocks defined in clause 7.1.11 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4]. The PDSCH transmission spans consecutive subframes, including subframes that are not BL/CE DL subframes where the PDSCH transmission is postponed. - If downlink resource reservation is enabled for the UE as specified in [9], and the Resource reservation field in the DCI is set to 1, then in case of PDSCH transmission associated with C-RNTI or SPS C-RNTI using UE-specific MPDCCH search space including PDSCH transmission without a corresponding MPDCCH, - In a subframe that is fully reserved as defined in clause 7.1 in [4], the PDSCH transmission is postponed until the next BL/CE downlink subframe that is not fully reserved. - In a subframe that is partially reserved, the reserved resource elements shall be counted in the PDSCH mapping but not used for transmission of the PDSCH. - If frequency hopping is not enabled for PDSCH, all PDSCH repetitions are located at the same PRB resources, and - if frequency hopping is enabled for PDSCH, the PDSCH shall be transmitted in subframe within the consecutive downlink subframes using the PRB resources of the narrowband with the same RIV as that of narrowband . The narrowband is defined as where is the absolute subframe number of the first downlink subframe intended for PDSCH and , and are cell-specific higher-layer parameters. For PDSCH carrying SI other than SIB1-BR and for PDSCH associated with P-RNTI, if interval-DlHoppingConfigCommonModeB is signalled in SIB1-BR, then the frequency hopping granularity is set to interval-DlHoppingConfigCommonModeB; otherwise, is set to interval-DlHoppingConfigCommonModeA signalled in SIB1-BR. For BL/CE UE in CEModeA, frequency hopping of PDSCH associated with C-RNTI or SPS C-RNTI is enabled when higher layer parameter mpdcch-pdsch-HoppingConfig is set and the frequency hopping flag in DCI format 6-1A indicates frequency hopping, otherwise, frequency hopping of is not enabled. For BL/CE UE in CEModeB, frequency hopping of PDSCH associated with C-RNTI or SPS C-RNTI is enabled when higher layer parameter mpdcch-pdsch-HoppingConfig is set, otherwise, frequency hopping of is not enabled. The UE shall not expect PDSCH in subframe if it is not a BL/CE DL subframe. For BL/CE UEs, if the PDSCH carries SIB1-BR, the PDSCH transmission is repeated periodically in every period of 8 radio frames, where a period starts with a radio frame with where is the system frame number. The PDSCH is transmitted times in each period of 8 frames, Let be the set of narrowbands, excluding narrowbands overlapping with the 72 center subcarriers for , and ordered in increasing order of narrowband index. The PDSCH transmission cycles through the set of narrowbands in increasing order of , starting with for the first subframe, according to where is the number of narrowbands in the set . The set of frames and subframes used for SIB1-BR transmission in each period are given by Tables 6.4.1-1 and 6.4.1-2. Table 6.4.1-1: The set of frames and subframes for SIB1-BR for . Table 6.4.1-2: The set of frames and subframes for SIB1-BR for . BL/CE UEs may assume the same precoding matrix being used for a PRB across a block of consecutive subframes when UE-specific reference signals are transmitted together with the PDSCH, where the subframe number of the first subframe in each block of consecutive subframes, denoted as , satisfies . For PDSCH transmission associated with SI-RNTI or P-RNTI to BL/CE UEs, frequency hopping of the PDSCH is enabled when higher layer parameter si-HoppingConfigCommon is set. For PDSCH transmission associated with PUR-RNTI to BL/CE UEs using UE-specific MPDCCH search space, frequency hopping of the PDSCH is enabled when higher layer parameter pur-PDSCH-FreqHopping is set. For PDSCH transmission associated with RA-RNTI or temporary C-RNTI to BL/CE UEs, frequency hopping of the PDSCH is enabled when higher layer parameter rar-HoppingConfig is set. Further - if PRACH CE level 0 or 1 is used for the last PRACH attempt, is set to the higher layer parameter interval-DlHoppingConfigCommonModeA; - if PRACH CE level 2 or 3 is used for the last PRACH attempt, is set to the higher layer parameter interval-DlHoppingConfigCommonModeB. For PDSCH transmission associated with SC-RNTI to BL/CE UEs, frequency hopping of the PDSCH is enabled when higher layer parameter mpdcch-pdsch-HoppingConfig-SC-MCCH is set. Further - if mpdcch-pdsch-HoppingConfig-SC-MCCH is set to CEModeA, is set to the higher layer parameter interval-DlHoppingConfigCommonModeA; - if mpdcch-pdsch-HoppingConfig-SC-MCCH is set to CEModeB, is set to the higher layer parameter interval-DlHoppingConfigCommonModeB. For PDSCH transmission associated with G-RNTI to BL/CE UEs, - if the higher layer parameter mpdcch-pdsch-CEmodeConfig-SC-MTCH is set to CEModeA, - if the higher layer parameter mpdcch-pdsch-HoppingConfig-SC-MTCH is set and the frequency hopping flag in DCI format 6-1A indicates frequency hopping, then frequency hopping of the PDSCH is enabled and is set to the higher layer parameter interval-DlHoppingConfigCommonModeA, otherwise frequency hopping is not enabled; - if the higher layer parameter mpdcch-pdsch-CEmodeConfig-SC-MTCH is set to CEModeB, - if the higher layer parameter mpdcch-pdsch-HoppingConfig-SC-MTCH is set, then frequency hopping of the PDSCH is enabled and is set to the higher layer parameter interval-DlHoppingConfigCommonModeB, otherwise frequency hopping is not enabled.

3GPP TS 36.211

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

RAN1

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

6.4.1

9.11.3.36 Network slicing indication

The purpose of the Network slicing indication information element is to indicate additional information associated with network slicing in the generic UE configuration update procedure and the registration procedure, other than the user's configured NSSAI, allowed NSSAI, pending NSSAI and rejected NSSAI information. The Network slicing indication information element is coded as shown in figure 9.11.3.36.1 and table 9.11.3.36.1. The Network slicing indication is a type 1 information element. Figure 9.11.3.36.1: Network slicing indication Table 9.11.3.36.1: Network slicing indication

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

F.2 Network Diagnostics

Network diagnostics helps with scanning, diagnosing and identifying problems within a network. Diagnostics includes gathering data and continuously providing sufficient performance parameters that characterize the quality of the network connection. This includes data of the physical connection as well as of logical links and sub-networks. Exposure of relevant (and possibly aggregated) performance parameters ensures a quick reaction in case of failure as well as identifying network connectivity, performance and other related problems. Network diagnostic should be able to: - be proactive (to early detect failures) and not only reactive (to deal with faults that have already occurred). - accurately differentiate malfunctions/failures and evaluate their impact on the service/network. - provide clear explanations about what happened. - suggest corrective actions, and possibly perform them automatically. Furthermore, specific connectivity information is also of interest as well as usage information (e.g. traffic load) of the node (e.g. RAN). Network diagnostic information needs to be generated automatically and, in case of a hosted or virtual network deployment, be made available to the tenant of the network via a suitable API.

3GPP TS 22.261

Service requirements for the 5G system

SA WG1

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

F.2

6.2.4A.10 A-MPR for CA_NS_10

If the UE is configured to CA_48C and it receives IE CA_NS_10 the allowed maximum output power reduction applied to transmission on the PCC and the SCC for contiguously aggregated signals is specified in Table 6.2.4A.10-2 or Table 6.2.4A.10-3. Which table is determined by the position of the carrier centre frequency in Table 6.2.4A.10-1. Table 6.2.4A.10-1: A-MPR regions for CA_48C Table 6.2.4A.10-2: A-MPR regions for CA_48C at the band edge Table 6.2.4A.10-3: A-MPR regions for CA_48C at the band center (“range for lower A-MPR”) If the UE is configured to CA_48C and it receives IE CA_NS_10 the allowed maximum output power reduction applied to transmissions on the PCell and the SCell with non-contiguous resource allocation is defined with both an edge and a center scenario and is determined in Table 6.2.4A.10-4. Table 6.2.4A.10-4: A-MPR regions for CA_48C The Edge scenario is defined as follows A-MPR = CEIL {MA, 0.5} where MA is defined as follows MA = 18.00 - 10.00 A; 0 ≤ A < 0.05 18.50 - 20.00 A; 0.05 ≤ A < 0.2 15.50 - 5.00 A; 0.2 ≤ A < 1 where A = NRB_alloc / NRB_agg. The Center scenario is defined as follows A-MPR = CEIL {MA, 0.5} where MA is defined as follows MA = 11.50 - 10.00 A; 0 ≤ A < 0.15 10.88 - 5.88 A; 0.15 ≤ A < 1 where A = NRB_alloc / NRB_agg For CA_48B contiguous resource allocation when 3560 MHz ≤ Fagg_alloc_low and Fagg_alloc_high <= 3690 MHz if allocation is inner 1 then A-MPR = 0 dB where inner 1 is defined as RBStart,Low = max(1, floor(LCRB/2)) where max() indicates the largest value of all arguments and floor(x) is the greatest integer less than or equal to x. RBStart,High = NRB_agg – RBStart,Low – LCRB with following conditions RBStart,Low ≤ RBStart ≤ RBStart,High, and LCRB ≤ ceil(NRB_agg /2) Inner 1 region exceptions thresholds are RBstart < 12 or RBend ≥ 92 for BWChannel_CA = 20MHz For which AMPR = 4 dB. else A-MPR= 4 dB For CA_48B contiguous resource allocation when Fagg_alloc_low < 3560 MHz if allocation is inner 3 then A-MPR = 0 dB Inner 3 region exceptions thresholds are RBstart < 30 for BWChannel_CA = 20MHz For which AMPR = 7dB. where inner 3 is defined as NRB_agg /4 < RBStart < NRB_agg 3/4 LCRB AND LCRB < NRB_agg/4 else A-MPR = 7 dB. For CA_48B contiguous resource allocation when Fagg_alloc_high > 3690 MHz if allocation is inner 3 then A-MPR = 0 dB Inner 3 region exceptions thresholds are RBstart > 70 for BWChannel_CA = 20MHz For which AMPR = 7dB. where inner 3 is defined as NRB_agg /4 < RBStart < NRB_agg 3/4 LCRB AND LCRB < NRB_agg/4 else A-MPR = 7 dB. For CA_48B non-contiguous resource allocation when 3560 MHz ≤ Fagg_alloc_low and Fagg_alloc_high <= 3690 MHz A = NRB_alloc / NRB_agg A-MPR= 13.00; 0.00 <= A <= 0.08 13.78 - 9.78 A; 0.08 < A <= 1.00 For CA_48B non-contiguous resource allocation when Fagg_alloc_low < 3560 MHz or Fagg_alloc_high > 3690 MHz A-MPR= 13.00; 0.00 <= A <= 0.08 14.13 -14.06 A; 0.08 < A <= 0.40 9.17 – 1.67 A; 0.40 < A <= 1.00

3GPP TS 36.101

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

RAN4

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

6.2.4A.10

8.2 Bearer type selection

In EN-DC, for each radio bearer the MN decides the location of the PDCP entity and in which cell group(s) radio resources are to be configured. Once an SN terminated split bearer is established, e.g. by means of the Secondary Node Addition procedure or MN initiated Secondary Node Modification procedure, the SN may remove SCG resources for the respective E-RAB, as long as the QoS for the respective E-RAB is guaranteed. In case an SN terminated bearer is released or reconfigured to an MN terminated bearer, only the MN generates the corresponding configuration and the SN does not generate the release configuration. In MR-DC with 5GC, the following principles apply: - The MN decides per PDU session the location of the SDAP entity, i.e. whether it shall be hosted by the MN or the SN or by both (split PDU session); - If the MN decides to host an SDAP entity it may decide some of the related QoS flows to be realized as MCG bearer, some as SCG bearer, and others to be realized as split bearer; - If the MN decides that an SDAP entity shall be hosted in the SN, some of the related QoS flows may be realized as SCG bearer, some as MCG bearer, while others may be realized as split bearer. In this case, the SN decides how to realise the QoS flow, but if the MN does not offer MCG resources, the SN can only realize the QoS flow as SCG bearer. The SN may remove or add SCG resources for the respective QoS flows, as long as the QoS for the respective QoS flow is guaranteed - If the MN decides that an SDAP entity shall be hosted in the SN, coordination of DRB IDs between the MN and the SN is needed to ensure unique allocation of DRBs for a UE. The SN is responsible to assign the DRB IDs for the DRBs it terminates, based on the DRB IDs indicated by the MN. - For each PDU session, including split PDU sessions, at most one default DRB may be configured (see [3]). The MN decides whether the SN is allowed to setup the default DRB or not; - In case an SN terminated bearer is released or reconfigured to an MN terminated bearer, the MN generates the corresponding configuration and the SN does not generate the release configuration. The only exceptional case where SN generates the release configuration is for the DRB release due to QoS flow to DRB remapping within SN.

3GPP TS 37.340

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

RAN2

3GPP Series : 37 , Multiple radio access technology aspects

8.2

4.4.6.4 Scheduled IP Throughput in UL

a) This measurement provides the volume of a data burst during IP throughput measurement, excluding the data transmitted in the TTI when the buffer is emptied in uplink. For an eNodeB serving one or more RNs, packets transmitted between the E-UTRAN and RNs are excluded, i.e., only packets transmitted between the eNodeB (or RN) and UEs are counted. The measurement is also applicable to RN. b) DER(n=1). c) This measurement is obtained according to the definition in 3GPP TS 36.314[ Evolved Universal Terrestrial Radio Access (E-UTRA); Layer 2 - Measurements ] [11] clause 4.1.6 as sum of ThpVolUl. Separate counters are maintained for each QCI. d) Each measurement is a real value representing volume of a data burst in kbit. The number of measurements is equal to the number of QCIs. e) The measurement name has the form DRB.IPVolUl.QCI where QCI identifies the E-RAB level quality of service class. f) EUtranCellFDD EUtranCellTDD g) Valid for packet switched traffic. h) EPS. i) This measurement is to support the Integrity KPI "E-UTRAN IP Throughput" defined in [13].

3GPP TS 32.425

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

SA WG5

3GPP Series : 32 , OAM&P and Charging

4.4.6.4

4.6.3.1 Session management based network slice admission control

A serving PLMN or the HPLMN, or SNPN can perform network slice admission control for the S-NSSAI(s) subject to NSAC to monitor and control the total number of established PDU sessions per network slice. The SMF performs network slice admission control on the S-NSSAI during the PDU session establishment procedure. If the maximum number of PDU sessions on a network slice associated with an S-NSSAI has been already reached, the SMF rejects the PDU session establishment request using S-NSSAI based congestion control as specifed in subclause 6.2.8 and 6.4.1.4.2. The SMF performs network slice admission control on the S-NSSAI for a PDU session that is associated with the non-3GPP access, when the UE requests to transfer a session from the non-3GPP access to the 3GPP access with the Allowed PDU session status IE as described in subclause 5.6.1.4. If the maximum number of PDU sessions on a network slice associated with an S-NSSAI has been already reached, the SMF rejects the request to establish the user-plane resources (see 3GPP TS 29.502[ 5G System; Session Management Services; Stage 3 ] [20A]). Based on operator policy, the session management based network slice admission control is not applicable for the PDU session for emergency services, or the session management based network slice admission control result is ignored for the PDU session for emergency services. Based on operator policy, the session management based network slice admission control is not applicable for the PDU session for priority services, or the session management based network slice admission control result is ignored for the PDU session for priority services. NOTE 1: The SMF can use the Sbi-Message-Priority field, as defined in TS 29.500[ 5G System; Technical Realization of Service Based Architecture; Stage 3 ] [20AA], to determine whether the PDU session is for priority services. The session management based network slice admission control is not applicable to PDU session established for onboarding services in SNPN. NOTE 2: For the MA PDU session during the PDU session establishment procedure, the SMF performs network slice admission control only when it is newly established over the associated access type. NOTE 3: For a set of redundant PDU sessions, the SMF performs network slice admission control for each PDU session independently.

3GPP TS 24.501

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

CT WG1

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

4.6.3.1

10.3 Field set to a not comprehended value

The UE shall, when receiving an RRC message or PC5 RRC message on any logical channel: 1> if the message includes a field that has a value that the UE does not comprehend: 2> if a default value is defined for this field: 3> treat the message while using the default value defined for this field; 2> else if the concerned field is optional: 3> treat the message as if the field were absent and in accordance with the need code for absence of the concerned field; 2> else: 3> treat the message as if the field were absent and in accordance with clause 10.4.

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

10.3

10.5.4.6 Call state

The purpose of the call state information element is to describe the current status of a call, (see subclause 5.1). The call state information element is coded as shown in figure 10.5.90/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.117/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The call state is a type 3 information element with 2 octets length. Figure 10.5.90/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Call state information element Table 10.5.117/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Call state 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.6

6.5.1.3 UE requested PDN connectivity procedure accepted by the network

Upon receipt of the PDN CONNECTIVITY REQUEST message, the MME checks whether the ESM information transfer flag is included. If the flag is included the MME waits for completion of the ESM information request procedure before proceeding with the PDN connectivity procedure. The MME then checks if connectivity with the requested PDN can be established. If no requested APN is included in the PDN CONNECTIVITY REQUEST message or the ESM INFORMATION RESPONSE message and the request type is different from "emergency" and from "handover of emergency bearer services" and from "RLOS", the MME shall use the default APN as the requested APN. If the request type is "emergency" or "handover of emergency bearer services", the MME shall use the APN configured for emergency bearer services or select the statically configured PDN GW for unauthenticated UEs, if applicable. If the request type is "RLOS", the MME shall use the APN configured for RLOS. If the network receives a PDN CONNECTIVITY REQUEST message with the same combination of APN and PDN type as an already existing PDN connection, and multiple PDN connections for a given APN are allowed, the network retains the existing EPS bearer contexts for the PDN connection and proceeds with the requested PDN connectivity procedure. If the lower layers provide a GW Transport Layer Address value identifying a L-GW together with the PDN CONNECTIVITY REQUEST message and a PDN connection is established as a LIPA PDN connection due to the PDN CONNECTIVITY REQUEST message, then the MME shall store the GW Transport Layer Address value as the P-GW address in the EPS bearer context of the LIPA PDN connection. If the lower layers provide a SIPTO L-GW Transport Layer Address value identifying a L-GW together with the PDN CONNECTIVITY REQUEST message and a PDN connection is established as a SIPTO at the local network PDN connection due to the PDN CONNECTIVITY REQUEST message, then the MME shall store the SIPTO L-GW Transport Layer Address value as the P-GW address in the EPS bearer context of the SIPTO at the local network PDN connection. If the lower layers provide a LHN-ID value together with the PDN CONNECTIVITY REQUEST message and a PDN connection is established as a SIPTO at the local network PDN connection due to the PDN CONNECTIVITY REQUEST message, then the MME shall store the LHN-ID value in the EPS bearer context of the SIPTO at the local network PDN connection. NOTE 1: The receipt of a LHN-ID value during the establishment of the PDN connection, during tracking area updating procedure or during inter-MME handover can be used as an indication by the MME that the SIPTO at the local network PDN connection is established to a stand-alone GW (see 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10]). If connectivity with the requested PDN is accepted by the network, the MME shall initiate the default EPS bearer context activation procedure (see clause 6.4.1). If connectivity with the requested PDN is accepted and the network considers this PDN connection a LIPA PDN connection, then subject to operator policy the MME shall include in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message the Connectivity type IE indicating "the PDN connection is considered a LIPA PDN connection". If connectivity with the requested PDN is accepted, but with a restriction of IP version (i.e. both an IPv4 address and an IPv6 prefix is requested, but only one particular IP version, or only single IP version bearers are supported/allowed by the network), ESM cause #50 "PDN type IPv4 only allowed", #51 "PDN type IPv6 only allowed", or #52 "single address bearers only allowed", respectively, shall be included in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message. If connectivity with the requested PDN is accepted and the UE provided the Header compression configuration IE in the PDN CONNECTIVITY REQUEST message, the MME may include the Header compression configuration IE in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message. Furthermore, if the MME decides that the associated PDN connection is only for control plane CIoT EPS optimization (see clause 5.3.15), the MME shall include the Control plane only indication in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message. Upon receipt of the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message, the UE shall stop timer T3482 and enter the state PROCEDURE TRANSACTION INACTIVE. The UE should ensure that the procedure transaction identity (PTI) assigned to this procedure is not released immediately. The way to achieve this is implementation dependent. While the PTI value is not released, the UE regards any received ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message with the same PTI value as a network retransmission (see clause 7.3.1). Upon receipt of the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message with the Connectivity type IE indicating "the PDN connection is considered a LIPA PDN connection", the UE provides an indication to the upper layers that the connectivity is provided by a LIPA PDN connection. Upon receipt of the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message, if the 3GPP PS data off UE status is "activated", the UE behaves as described in clause 6.3.10. Upon receipt of the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message, if the SCEF or P-GW indicates acceptance of use of Reliable Data Service to transfer data for the PDN connection, the UE behaves as described in clause 6.3.11. Upon receipt of the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message, if an S-NSSAI and the PLMN ID that this S-NSSAI relates to are provided in the Protocol configuration options IE or Extended protocol configuration options IE, the UE shall delete the stored S-NSSAI and the PLMN ID that this S-NSSAI relates to, if any, and shall store the S-NSSAI and the PLMN ID this S-NSSAI relates to provided in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message and the associated PLMN ID along with the corresponding PDU session ID that the UE provided in the PDN CONNECTIVITY REQUEST message. The usage of the PDU session ID and the corresponding S-NSSAI with the associated PLMN ID is specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54]. Additionally, the UE shall remove the S-NSSAI, if present, from the rejected NSSAI as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] clause 4.6.2.2. Upon receipt of the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message with a session-AMBR and QoS rule(s), which correspond to the default EPS bearer of the PDN connectivity being activated, in the Protocol configuration options IE or the Extended protocol configuration options IE, the UE stores the session-AMBR and QoS rule(s) for use during inter-system change from S1 mode to N1 mode. If the UE requests the PDN type "IPv4v6", receives the selected PDN type set to "IPv4" and the ESM cause value #50 "PDN type IPv4 only allowed", the UE shall not automatically send another PDN CONNECTIVITY REQUEST message to the same APN (or no APN, if no APN was indicated by the UE) to obtain a PDN type different from the one allowed by the network until: - the UE is registered to a new PLMN; - the UE is switched off; or - the USIM is removed. If the UE requests the PDN type "IPv4v6", receives the selected PDN type set to "IPv6" and the ESM cause value #51 "PDN type IPv6 only allowed", the UE shall not automatically send another PDN CONNECTIVITY REQUEST message to the same APN (or no APN, if no APN was indicated by the UE) to obtain a PDN type different from the one allowed by the network until: - the UE is registered to a new PLMN; - the UE is switched off; or - the USIM is removed. NOTE 2: For the ESM cause values #50 "PDN type IPv4 only allowed" and #51 "PDN type IPv6 only allowed", re-attempt in A/Gb, Iu, or N1 mode for the same APN (or no APN, if no APN was indicated by the UE) is only allowed using the PDN type(s) indicated by the network.

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

9.11.3.89 Relay key request parameters

The purpose of the relay key request parameters information element is to transport the parameters of the key request for 5G ProSe UE-to-network relay or 5G ProSe UE-to-UE relay as specified in 3GPP TS 33.503[ Security Aspects of Proximity based Services (ProSe) in the 5G System (5GS) ] [56]. The relay key request parameters information element is coded as shown in figure 9.11.3.89.1, figure 9.11.3.89.2 and table 9.11.3.89.1. The relay key request parameters is a type 6 information element. Figure 9.11.3.89.1: Relay key request parameters information element Figure 9.11.3.89.2: UE identity Table 9.11.3.89.1: Relay key request parameters 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.89

4.8.1.2 Peak processor usage

a) This measurement provides the peak usage of each key processor during the granularity period. Each equipment may have more than one key processor, how to indentify key processor is vendor specific. b) SI. c) This measurement is obtained by sampling at a pre-defined interval the usage of the processor and then taking the maximum for each key processor. d) Each measurement is an integer value (Unit: %). e) EQPT.PeakProcessorUsage.ProcessorID where ProcessorID identifies the key processor of this equipment, the format of ProcessorID is vendor specific. f) ManagedElement. 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.8.1.2

11.2.1.3.1 IPv6 PDP Context Activation

In this case: - The GGSN provides the MS with an IPv6 Prefix belonging to the Intranet/ISP addressing space. A dynamic IPv6 address shall be given using stateless address autoconfiguration. This IPv6 address is used for packet forwarding within the packet domain and for packet forwarding on the Intranet/ISP; - the MS may send an authentication request at PDP context activation and the GGSN may request user authentication from a server, e.g. AAA, …, belonging to the Intranet/ISP; - the protocol configuration options are retrieved (if requested by the MS at PDP context activation) from some server, e.g. AAA, …, belonging to the Intranet/ISP; - in order to avoid any conflict between the link-local address of the MS and that of the GGSN, the Interface-Identifier used by the MS to build its link-local address shall be assigned by the GGSN. The GGSN ensures the uniqueness of this interface-identifier. The MT shall then enforce the use of this Interface-Identifier by the TE. - the communication between the Packet Domain and the Intranet/ISP may be performed over any network, even an insecure e.g. the Internet. In case of an insecure connection between the GGSN and the Intranet/ISP there may be a specific security protocol over the insecure connection. This security protocol is defined by mutual agreement between PLMN operator and Intranet/ISP administrator. - the MS may request for DNS server IPv6 addresses using the PCO IE in e.g. the PDP Context Request message. In that case the GGSN may return the IP address of one or more DNS servers in the PCO in the PDP Context Response message. The DNS address(es) shall be coded in the PCO as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [54]. If a list of servers is received, the MS shall adhere to the explicit prioritisation order of the list. In the following signalling flow example, PPP is used as layer 2 protocol over the R reference point. The MT behaves as a PPP server and translates Protocol Configuration Options into SM message Ies. GTP-C carries this information unchanged to the GGSN which uses the information e.g. for RADIUS authentication. The result of the host authentication is carried via GTP-C back to the SGSN, which then relays the result to the MT. The MT finalises the IPV6CP negotiation by sending an IPV6CP Configure-Ack message to the TE with the appropriate options included, e.g. Interface-Identifier. The Interface-Identifier shall be used in the TE to create a link-local address to be able to perform the IPv6 address autoconfiguration (see subclauses 11.2.1.3.2 and 11.2.1.3.3). 1) The TE sends an AT-command to the MT to set up parameters and enter PPP mode. The MT responds with an AT-response. 2) LCP negotiates Maximum-Receive-Unit and authentication protocol. The negotiated authentication protocol is either CHAP, PAP or ‘none’. The MT shall try to negotiate for CHAP as first priority. 3) If the negotiated authentication protocol is either of CHAP or PAP, the TE authenticates itself towards the MT by means of that protocol. The MT stores the necessary authentication data and sends a forced positive acknowledgement of the authentication to the TE. 4) The TE requests IPv6 Interface-Identifier negotiation by sending the IPV6CP Configure-Request message to the MT. 5) The MT sends the Activate PDP Context Request message to the SGSN, including the Protocol Configuration Options. The Protocol Configuration Options IE may contain negotiated LCP options such as negotiated Authentication Protocol as well as any authentication data previously stored in the MT. It may also contain a request for dynamic configuration of DNS server IPv6 addresses. The MS shall for dynamic address allocation leave PDP Address empty and set PDP Type to IPv6 or IPv4v6. The SGSN sends the Create PDP context request message to the chosen GGSN including the unmodified Protocol Configuration Options. 6) The GGSN deduces from local configuration data associated with the APN: - the source of IPv6 Prefixes (GGSN internal prefix pool, or external address allocation server); - any server(s) to be used for address allocation, authentication and/or protocol configuration options retrieval (e.g. IMS related configuration, see 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [47]); - the protocol e.g. RADIUS, to be used with the server(s); - the communication and security feature needed to communicate with the server(s); As an example the GGSN may use one of the following options: - GGSN internal Prefix pool for IPv6 prefix allocation and no authentication; - GGSN internal Prefix pool for IPv6 prefix allocation and RADIUS for authentication. The AAA server responds with either an Access-Accept or an Access-Reject to the RADIUS client in the GGSN; - RADIUS for authentication and IPv6 prefix allocation. The AAA server responds with either an Access-Accept or an Access-Reject to the RADIUS client in the GGSN; NOTE: DHCPv6 may be used for IPv6 prefix allocation. IPv6 Prefixes in a GGSN internal Prefix pool shall be configurable and structured per APN. The GGSN shall in the PDP Address IE in the Create PDP Context Response return an IPv6 address composed of a Prefix and an Interface-Identifier. The Interface-Identifier may have any value and it does not need to be unique within or across APNs. It shall however not conflict with the Interface-Identifier the GGSN has selected for its own side of the MS-GGSN link. The Prefix assigned by the GGSN or the external AAA server shall be globally or site-local unique. The GGSN shall analyse the requested values of all the protocol options contained in the received Protocol Configurations Options IE. The contents of the Protocol Configurations Options IE sent in the GGSN response shall be in accordance with the relevant standards e.g. the PPP standard RFC 1661 [21a] and RFC 1662 [21b]. 7) The GGSN sends back to the SGSN a Create PDP Context Response message, containing the PDP Address IE and the Protocol Configuration Options IE. The Protocol Configuration Options IE may contain configuration data such as a list of DNS server IPv6 addresses. The cause value shall be set according to the outcome of the host authentication and configuration. 8) Depending on the cause value received in the Create PDP Context Response, the SGSN either stores the PDP Address and sends an Activate PDP Context Accept to the MS or, sends an Activate PDP Context Reject, to the MS. If Protocol Configuration Options are received from the GGSN, the SGSN shall relay those to the MS. 9) The MT extracts the Interface-Identifier from the address received in the PDP Address IE and ignores the Prefix part. If this Interface-Identifier is identical to the tentative Interface-Identifier indicated in the IPV6CP Configure-Request message sent from the TE, the MT sends an IPV6CP Configure Ack packet, indicating this Interface-Identifier, to the TE. If the Interface-Identifier extracted from the address contained in the PDP Address IE is not identical to the tentative Interface-Identifier indicated in the IPV6CP Configure-Request message sent from the TE, the MT sends an IPV6CP Configure-Nak packet, indicating the Interface-Identifier extracted from the address contained in the PDP Address IE, to the TE. The TE then sends a new IPV6CP Configure-Request message to the MT, indicating the same Interface-Identifier as was indicated in the received IPV6CP Configure Nak (as indicated by the dotted IPV6CP Configure-Request and Configure-Ack in the figure below). Finally the MT responds with a IPV6CP Configure Ack packet. In case a PDP Context Reject was sent to the MS the MT sends an LCP Terminate-Request to the TE. 10) When the TE has accepted the Interface-Identifier given by the MT, the user plane link from the TE to the GGSN and the external ISP/Intranet is established and the IPv6 address autoconfiguration may proceed. In case a link terminate request packet was sent to the TE, the TE and MT negotiates for link termination. The MT may then send a final AT-response to inform the TE about the rejected PDP Context activation. An LCP Terminate-request causes a PDP context deactivation. NOTE: DHCPv6 may be used for IPv6 prefix allocation. Figure 11ba: PDP Context Activation for the IPv6 Non-transparent case

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

11.2.1.3.1

5.5.4 Measurement report triggering 5.5.4.1 General

If AS security has been activated successfully, the UE shall: 1> for each measId included in the measIdList within VarMeasConfig: 2> if the corresponding reportConfig includes a reportType set to eventTriggered or periodical: 3> if the corresponding measObject concerns NR: 4> if the corresponding reportConfig includes measRSSI-ReportConfig: 5> consider the resource indicated by the rmtc-Config on the associated frequency to be applicable; 4> if the eventA1 or eventA2 is configured in the corresponding reportConfig: 5> consider only the serving cell to be applicable; 4> if the eventA3 or eventA5 or eventA3H1 or eventA3H2 or eventA5H1 or eventA5H2 is configured in the corresponding reportConfig: 5> if a serving cell is associated with a measObjectNR and neighbours are associated with another measObjectNR, consider any serving cell associated with the other measObjectNR to be a neighbouring cell as well; 4> if the eventX2 is configured in the corresponding reportConfig: 5> consider only the serving L2 U2N Relay UE to be applicable; 4> if corresponding reportConfig includes reportType set to periodical; or 4> for measurement events other than eventA1, eventA2, eventD1, eventX2, eventH1 or eventH2: 5> if useAllowedCellList is set to true: 6> consider any neighbouring cell detected based on parameters in the associated measObjectNR to be applicable when the concerned cell is included in the allowedCellsToAddModList defined within the VarMeasConfig for this measId; 5> else: 6> consider any neighbouring cell detected based on parameters in the associated measObjectNR to be applicable when the concerned cell is not included in the excludedCellsToAddModList defined within the VarMeasConfig for this measId; 4> if the eventH1 or eventH2 is configured in the corresponding reportConfig: 5> for all the events of the same type for which simulMultiTriggerSingleMeasReport is set to true and the entry condition applicable for the event has been satisfied: 6> consider only the event with the smallest value between the altitude of the UE and the corresponding altitude threshold to be applicable; 4> else if the eventA3H1 or eventA3H2 or eventA4H1 or eventA4H2 or eventA5H1 or eventA5H2 is configured in the corresponding reportConfig: 5> for all the events of the same type associated with the same measObjectNR for which simulMultiTriggerSingleMeasReport is set to true and the entry conditions applicable for the event has been satisfied: 6> consider only the event with the smallest value between the altitude of the UE and the corresponding altitude threshold to be applicable; 3> else if the corresponding measObject concerns E-UTRA: 4> if eventB1 or eventB2 is configured in the corresponding reportConfig: 5> consider a serving cell, if any, on the associated E-UTRA frequency as neighbour cell; 4> consider any neighbouring cell detected on the associated frequency to be applicable when the concerned cell is not included in the excludedCellsToAddModListEUTRAN defined within the VarMeasConfig for this measId; 3> else if the corresponding measObject concerns UTRA-FDD: 4> if eventB1-UTRA-FDD or eventB2-UTRA-FDD is configured in the corresponding reportConfig; or 4> if corresponding reportConfig includes reportType set to periodical: 5> consider a neighbouring cell on the associated frequency to be applicable when the concerned cell is included in the cellsToAddModList defined within the VarMeasConfig for this measId; 3> else if the corresponding measObject concerns L2 U2N Relay UE: 4> if eventY1-Relay or eventY2-Relay or eventZ1-Relay is configured in the corresponding reportConfig; or 4> if corresponding reportConfig includes reportType set to periodical: 5> consider any L2 U2N Relay UE fulfilling upper layer criteria detected on the associated frequency to be applicable for this measId; 2> else if the corresponding reportConfig includes a reportType set to reportCGI: 3> consider the cell detected on the associated measObject which has a physical cell identity matching the value of the cellForWhichToReportCGI included in the corresponding reportConfig within the VarMeasConfig to be applicable; 2> else if the corresponding reportConfig includes a reportType set to reportSFTD: 3> if the corresponding measObject concerns NR: 4> if the reportSFTD-Meas is set to true: 5> consider the NR PSCell to be applicable; 4> else if the reportSFTD-NeighMeas is included: 5> if cellsForWhichToReportSFTD is configured in the corresponding reportConfig: 6> consider any NR neighbouring cell detected on the associated measObjectNR which has a physical cell identity that is included in the cellsForWhichToReportSFTD to be applicable; 5> else: 6> consider up to 3 strongest NR neighbouring cells detected based on parameters in the associated measObjectNR to be applicable when the concerned cells are not included in the excludedCellsToAddModList defined within the VarMeasConfig for this measId; 3> else if the corresponding measObject concerns E-UTRA: 4> if the reportSFTD-Meas is set to true: 5> consider the E-UTRA PSCell to be applicable; 2> else if the corresponding reportConfig includes a reportType set to cli-Periodical or cli-EventTriggered: 3> consider all CLI measurement resources included in the corresponding measObject to be applicable; 2> else if the corresponding reportConfig includes a reportType set to rxTxPeriodical: 3> consider all Rx-Tx time difference measurement resources included in the corresponding measObject to be applicable; 2> if the corresponding reportConfig concerns the reporting for NR sidelink communication/discovery (i.e. reportConfigNR-SL): 3> consider the transmission resource pools indicated by the tx-PoolMeasToAddModList defined within the VarMeasConfig for this measId to be applicable; 2> if the reportType is set to eventTriggered, and if the corresponding reportConfig does not include numberOfTriggeringCells, and if the entry condition applicable for this event, i.e. the event corresponding with the eventId of the corresponding reportConfig within VarMeasConfig, is fulfilled for one or more applicable cells for all measurements after layer 3 filtering taken during timeToTrigger defined for this event within the VarMeasConfig, while the VarMeasReportList does not include a measurement reporting entry for this measId (a first cell triggers the event): 3> include a measurement reporting entry within the VarMeasReportList for this measId; 3> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0; 3> include the concerned cell(s) in the cellsTriggeredList defined within the VarMeasReportList for this measId; 3> if useT312 is set to true in reportConfig for this event: 4> if T310 for the corresponding SpCell is running; and 4> if T312 is not running for corresponding SpCell: 5> start timer T312 for the corresponding SpCell with the value of T312 configured in the corresponding measObjectNR; 3> initiate the measurement reporting procedure, as specified in 5.5.5; 2> else if the reportType is set to eventTriggered, and if the corresponding reportConfig does not include numberOfTriggeringCells, and if the entry condition applicable for this event, i.e. the event corresponding with the eventId of the corresponding reportConfig within VarMeasConfig, is fulfilled for one or more applicable cells not included in the cellsTriggeredList for all measurements after layer 3 filtering taken during timeToTrigger defined for this event within the VarMeasConfig (a subsequent cell triggers the event): 3> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0; 3> include the concerned cell(s) in the cellsTriggeredList defined within the VarMeasReportList for this measId; 3> if useT312 is set to true in reportConfig for this event: 4> if T310 for the corresponding SpCell is running; and 4> if T312 is not running for corresponding SpCell: 5> start timer T312 for the corresponding SpCell with the value of T312 configured in the corresponding measObjectNR; 3> initiate the measurement reporting procedure, as specified in 5.5.5; 2> if the reportType is set to eventTriggered, and if the corresponding reportConfig includes numberOfTriggeringCells, and if the entry condition applicable for this event, i.e. the event corresponding with the eventId of the corresponding reportConfig within VarMeasConfig, is fulfilled for one or more applicable cells for all measurements after layer 3 filtering taken during timeToTrigger defined for this event within the VarMeasConfig: 3> if the VarMeasReportList does not include a measurement reporting entry for this measId (a first cell triggers the event): 4> include a measurement reporting entry within the VarMeasReportList for this measId; 3> if the number of cell(s) in the cellsTriggeredList is larger than or equal to numberOfTriggeringCells: 4> include the concerned cell(s) in the cellsTriggeredList defined within the VarMeasReportList for this measId; 3> else: 4> include the concerned cell(s) in the cellsTriggeredList defined within the VarMeasReportList for this measId; 4> if the number of cell(s) in the cellsTriggeredList is larger than or equal to numberOfTriggeringCells: 5> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0; 5> initiate the measurement reporting procedure, as specified in 5.5.5; 2> if the reportType is set to eventTriggered and if the leaving condition applicable for this event is fulfilled for one or more of the cells included in the cellsTriggeredList defined within the VarMeasReportList for this measId for all measurements after layer 3 filtering taken during timeToTrigger defined within the VarMeasConfig for this event: 3> remove the concerned cell(s) in the cellsTriggeredList defined within the VarMeasReportList for this measId; 3> if reportOnLeave is set to true for the corresponding reporting configuration: 4> if the corresponding reportConfig does not include numberOfTriggeringCells; or 4> if the corresponding reportConfig includes numberOfTriggeringCells and a measurement report was previously sent to the network for at least one of the concerned cell(s): 5> initiate the measurement reporting procedure, as specified in 5.5.5; 3> if the cellsTriggeredList defined within the VarMeasReportList for this measId is empty: 4> remove the measurement reporting entry within the VarMeasReportList for this measId; 4> stop the periodical reporting timer for this measId, if running; 2> if the reportType is set to eventTriggered and if the entry condition applicable for this event, i.e. the event corresponding with the eventId of the corresponding reportConfig within VarMeasConfig, is fulfilled for one or more applicable L2 U2N Relay UEs for all measurements after layer 3 filtering taken during timeToTrigger defined for this event within the VarMeasConfig, while the VarMeasReportList does not include a measurement reporting entry for this measId (a first L2 U2N Relay UE triggers the event): 3> include a measurement reporting entry within the VarMeasReportList for this measId; 3> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0; 3> include the concerned L2 U2N Relay UE(s) in the relaysTriggeredList defined within the VarMeasReportList for this measId; 3> initiate the measurement reporting procedure, as specified in 5.5.5; 2> else if the reportType is set to eventTriggered and if the entry condition applicable for this event, i.e. the event corresponding with the eventId of the corresponding reportConfig within VarMeasConfig, is fulfilled for one or more applicable L2 U2N Relay UEs not included in the relaysTriggeredList for all measurements after layer 3 filtering taken during timeToTrigger defined for this event within the VarMeasConfig (a subsequent L2 U2N Relay UE triggers the event): 3> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0; 3> include the concerned L2 U2N Relay UE(s) in the relaysTriggeredList defined within the VarMeasReportList for this measId; 3> initiate the measurement reporting procedure, as specified in 5.5.5; 2> else if the reportType is set to eventTriggered and if the leaving condition applicable for this event is fulfilled for one or more of the L2 U2N Relay UEs included in the relaysTriggeredList defined within the VarMeasReportList for this measId for all measurements after layer 3 filtering taken during timeToTrigger defined within the VarMeasConfig for this event: 3> remove the concerned L2 U2N Relay UE(s) in the relaysTriggeredList defined within the VarMeasReportList for this measId; 3> if reportOnLeave is set to true for the corresponding reporting configuration: 4> initiate the measurement reporting procedure, as specified in 5.5.5; 3> if the relaysTriggeredList defined within the VarMeasReportList for this measId is empty: 4> remove the measurement reporting entry within the VarMeasReportList for this measId; 4> stop the periodical reporting timer for this measId, if running; 2> else if the reportType is set to eventTriggered and if the entry condition applicable for this event, i.e. the event corresponding with the eventId of the corresponding reportConfig within VarMeasConfig, is fulfilled for one or more applicable transmission resource pools for all measurements taken during timeToTrigger defined for this event within the VarMeasConfig, while the VarMeasReportList does not include an measurement reporting entry for this measId (a first transmission resource pool triggers the event): 3> include a measurement reporting entry within the VarMeasReportList for this measId; 3> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0; 3> include the concerned transmission resource pool(s) in the poolsTriggeredList defined within the VarMeasReportList for this measId; 3> initiate the measurement reporting procedure, as specified in 5.5.5; 2> else if the reportType is set to eventTriggered and if the entry condition applicable for this event, i.e. the event corresponding with the eventId of the corresponding reportConfig within VarMeasConfig, is fulfilled for one or more applicable transmission resource pools not included in the poolsTriggeredList for all measurements taken during timeToTrigger defined for this event within the VarMeasConfig (a subsequent transmission resource pool triggers the event): 3> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0; 3> include the concerned transmission resource pool(s) in the poolsTriggeredList defined within the VarMeasReportList for this measId; 3> initiate the measurement reporting procedure, as specified in 5.5.5; 2> if the reportType is set to eventTriggered and if the leaving condition applicable for this event is fulfilled for one or more applicable transmission resource pools included in the poolsTriggeredList defined within the VarMeasReportList for this measId for all measurements taken during timeToTrigger defined within the VarMeasConfig for this event: 3> remove the concerned transmission resource pool(s) in the poolsTriggeredList defined within the VarMeasReportList for this measId; 3> if the poolsTriggeredList defined within the VarMeasReportList for this measId is empty: 4> remove the measurement reporting entry within the VarMeasReportList for this measId; 4> stop the periodical reporting timer for this measId, if running 2> else if the reportType is set to eventTriggered and if the eventId is set to eventD1 or eventH1 or eventH2 and if the entering condition applicable for this event, i.e. the event corresponding with the eventId of the corresponding reportConfig within VarMeasConfig, is fulfilled during timeToTrigger defined for this event within the VarMeasConfig, while the VarMeasReportList does not include a measurement reporting entry for this measId: 3> include a measurement reporting entry within the VarMeasReportList for this measId; 3> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0; 3> initiate the measurement reporting procedure, as specified in 5.5.5; 2> else if the reportType is set to eventTriggered and if the eventId is set to eventD1 or eventH1 or eventH2 and if the leaving condition applicable for this event is fulfilled for the associated VarMeasReport within the VarMeasReportList for this measId during timeToTrigger defined within the VarMeasConfig for this event: 3> if reportOnLeave is set to true for the corresponding reporting configuration: 4> initiate the measurement reporting procedure, as specified in 5.5.5; 3> remove the measurement reporting entry within the VarMeasReportList for this measId; 3> stop the periodical reporting timer for this measId, if running; NOTE 1: Void. 2> if reportType is set to periodical and if a (first) measurement result is available: 3> include a measurement reporting entry within the VarMeasReportList for this measId; 3> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0; 3> if the corresponding reportConfig includes measRSSI-ReportConfig: 4> initiate the measurement reporting procedure as specified in 5.5.5 immediately when RSSI sample values are reported by the physical layer after the first L1 measurement duration; 3> else if the corresponding reportConfig includes the ul-DelayValueConfig: 4> initiate the measurement reporting procedure, as specified in 5.5.5, immediately after a first measurement result is provided from lower layers of the associated DRB identity; 3> else if the corresponding reportConfig includes the ul-ExcessDelayConfig: 4> initiate the measurement reporting procedure, as specified in 5.5.5, immediately after a first measurement result is provided from lower layers of the associated DRB identity(ies) according to the configured threshold per DRB identity(ies); 3> else if the reportAmount exceeds 1: 4> initiate the measurement reporting procedure, as specified in 5.5.5, immediately after the quantity to be reported becomes available for the NR SpCell or for the serving L2 U2N Relay UE (if the UE is a L2 U2N Remote UE); 3> else (i.e. the reportAmount is equal to 1): 4> initiate the measurement reporting procedure, as specified in 5.5.5, immediately after the quantity to be reported becomes available for the NR SpCell and for the strongest cell among the applicable cells, or for the NR SpCell and for the strongest L2 U2N Relay UEs among the applicable L2 U2N Relay UEs; or initiate the measurement reporting procedure, as specified in 5.5.5, immediately after the quantity to be reported becomes available for the serving L2 U2N Relay UE and for the strongest cell among the applicable cells, or for the serving L2 U2N Relay UE and for the strongest L2 U2N Relay UEs among the applicable L2 U2N Relay UEs (if the UE is a L2 U2N Remote UE); 2> if, in case the corresponding reportConfig concerns the reporting for NR sidelink communication/discovery, reportType is set to periodical and if a (first) measurement result is available: 3> include a measurement reporting entry within the VarMeasReportList for this measId; 3> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0; 3> initiate the measurement reporting procedure, as specified in 5.5.5, immediately after the quantity to be reported becomes available for the NR SpCell and CBR measurement results become available; 2> if the reportType is set to cli-EventTriggered and if the entry condition applicable for this event, i.e. the event corresponding with the eventId of the corresponding reportConfig within VarMeasConfig, is fulfilled for one or more applicable CLI measurement resources for all measurements after layer 3 filtering taken during timeToTrigger defined for this event within the VarMeasConfig, while the VarMeasReportList does not include a measurement reporting entry for this measId (a first CLI measurement resource triggers the event): 3> include a measurement reporting entry within the VarMeasReportList for this measId; 3> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0; 3> include the concerned CLI measurement resource(s) in the cli-TriggeredList defined within the VarMeasReportList for this measId; 3> initiate the measurement reporting procedure, as specified in 5.5.5; 2> else if the reportType is set to cli-EventTriggered and if the entry condition applicable for this event, i.e. the event corresponding with the eventId of the corresponding reportConfig within VarMeasConfig, is fulfilled for one or more CLI measurement resources not included in the cli-TriggeredList for all measurements after layer 3 filtering taken during timeToTrigger defined for this event within the VarMeasConfig (a subsequent CLI measurement resource triggers the event): 3> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0; 3> include the concerned CLI measurement resource(s) in the cli-TriggeredList defined within the VarMeasReportList for this measId; 3> initiate the measurement reporting procedure, as specified in 5.5.5; 2> if the reportType is set to cli-EventTriggered and if the leaving condition applicable for this event is fulfilled for one or more of the CLI measurement resources included in the cli-TriggeredList defined within the VarMeasReportList for this measId for all measurements after layer 3 filtering taken during timeToTrigger defined within the VarMeasConfig for this event: 3> remove the concerned CLI measurement resource(s) in the cli-TriggeredList defined within the VarMeasReportList for this measId; 3> if reportOnLeave is set to true for the corresponding reporting configuration: 4> initiate the measurement reporting procedure, as specified in 5.5.5; 3> if the cli-TriggeredList defined within the VarMeasReportList for this measId is empty: 4> remove the measurement reporting entry within the VarMeasReportList for this measId; 4> stop the periodical reporting timer for this measId, if running; 2> if reportType is set to cli-Periodical and if a (first) measurement result is available: 3> include a measurement reporting entry within the VarMeasReportList for this measId; 3> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0; 3> initiate the measurement reporting procedure, as specified in 5.5.5, immediately after the quantity to be reported becomes available for at least one CLI measurement resource; 2> if reportType is set to rxTxPeriodical and if a (first) measurement result is available: 3> include a measurement reporting entry within the VarMeasReportList for this measId; 3> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0; 3> initiate the measurement reporting procedure, as specified in 5.5.5; 2> upon expiry of the periodical reporting timer for this measId: 3> initiate the measurement reporting procedure, as specified in 5.5.5. 2> if the corresponding reportConfig includes a reportType is set to reportSFTD: 3> if the corresponding measObject concerns NR: 4> if the drx-SFTD-NeighMeas is included: 5> if the quantity to be reported becomes available for each requested pair of PCell and NR cell: 6> stop timer T322; 6> initiate the measurement reporting procedure, as specified in 5.5.5; 4> else 5> initiate the measurement reporting procedure, as specified in 5.5.5, immediately after the quantity to be reported becomes available for each requested pair of PCell and NR cell or the maximal measurement reporting delay as specified in TS 38.133[ NR; Requirements for support of radio resource management ] [14]; 3> else if the corresponding measObject concerns E-UTRA: 4> initiate the measurement reporting procedure, as specified in 5.5.5, immediately after the quantity to be reported becomes available for the pair of PCell and E-UTRA PSCell or the maximal measurement reporting delay as specified in TS 38.133[ NR; Requirements for support of radio resource management ] [14]; 2> if reportType is set to reportCGI: 3> if the UE acquired the SIB1 or SystemInformationBlockType1 for the requested cell; or 3> if the UE detects that the requested NR cell is not transmitting SIB1 (see TS 38.213[ NR; Physical layer procedures for control ] [13], clause 13): 4> stop timer T321; 4> include a measurement reporting entry within the VarMeasReportList for this measId; 4> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0; 4> initiate the measurement reporting procedure, as specified in 5.5.5; 2> upon the expiry of T321 for this measId: 3> include a measurement reporting entry within the VarMeasReportList for this measId; 3> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0; 3> initiate the measurement reporting procedure, as specified in 5.5.5. 2> upon the expiry of T322 for this measId: 3> initiate the measurement reporting procedure, as specified in 5.5.5. If AS security has been activated successfully and if SCell activation(s) indication is received from lower layer, the UE shall: 1> if reportType is set to reportOnActivation for any measId included in the measIdList within VarMeasConfig: 2> if the activated SCell(s) fulfills the measurement requirement as specified in TS 38.133[ NR; Requirements for support of radio resource management ] [14]: 3> include a measurement reporting entry within the VarMeasReportList for this measId: 3> set the numberOfReportsSent defined within the VarMeasReportList for this measId to 0; 4> initiate the measurement reporting procedure, as specified in 5.5.5.

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

5.5.4

A.4.2 Critical extension of messages and fields

The mechanisms to critically extend a message are defined in A.3.3. There are both "outer branch" and "inner branch" mechanisms available. The "outer branch" consists of a CHOICE having the name criticalExtensions, with two values, c1 and criticalExtensionsFuture. The criticalExtensionsFuture branch consists of an empty SEQUENCE, while the c1 branch contains the "inner branch" mechanism. The "inner branch" structure is a CHOICE with values of the form "MessageName-rX-IEs" (e.g., "RRCConnectionReconfiguration-r8-IEs") or "spareX", with the spare values having type NULL. The "-rX-IEs" structures contain the complete structure of the message IEs for the appropriate release; i.e., the critical extension branch for the Rel-10 version of a message includes all Rel-8 and Rel-9 fields (that are not obviated in the later version), rather than containing only the additional Rel-10 fields. The following guidelines may be used when deciding which mechanism to introduce for a particular message, i.e. only an 'outer branch', or an 'outer branch' in combination with an 'inner branch' including a certain number of spares: - For certain messages, e.g. initial uplink messages, messages transmitted on a broadcast channel, critical extension may not be applicable. - An outer branch may be sufficient for messages not including any fields. - The number of spares within inner branch should reflect the likelihood that the message will be critically extended in future releases (since each release with a critical extension for the message consumes one of the spare values). The estimation of the critical extension likelihood may be based on the number, size and changeability of the fields included in the message. - In messages where an inner branch extension mechanism is available, all spare values of the inner branch should be used before any critical extensions are added using the outer branch. The following example illustrates the use of the critical extension mechanism by showing the ASN.1 of the original and of a later release -- /example/ ASN1START -- Original release RRCMessage ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { c1 CHOICE{ rrcMessage-r8 RRCMessage-r8-IEs, spare3 NULL, spare2 NULL, spare1 NULL }, criticalExtensionsFuture SEQUENCE {} } } -- ASN1STOP -- /example/ ASN1START -- Later release RRCMessage ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { c1 CHOICE{ rrcMessage-r8 RRCMessage-r8-IEs, rrcMessage-r10 RRCMessage-r10-IEs, rrcMessage-r11 RRCMessage-r11-IEs, rrcMessage-r14 RRCMessage-r14-IEs }, later CHOICE { c2 CHOICE{ rrcMessage-r16 RRCMessage-r16-IEs, spare7 NULL, spare6 NULL, spare5 NULL, spare4 NULL, spare3 NULL, spare2 NULL, spare1 NULL }, criticalExtensionsFuture SEQUENCE {} } } } -- ASN1STOP It is important to note that critical extensions may also be used at the level of individual fields i.e. a field may be replaced by a critically extended version. When sending the extended version, the original version may also be included (e.g. original field is mandatory, E-UTRAN is unaware if UE supports the extended version). In such cases, a UE supporting both versions may be required to ignore the original field. The following example illustrates the use of the critical extension mechanism by showing the ASN.1 of the original and of a later release. -- /example/ ASN1START -- Original release RRCMessage ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { c1 CHOICE{ rrcMessage-r8 RRCMessage-r8-IEs, spare3 NULL, spare2 NULL, spare1 NULL }, criticalExtensionsFuture SEQUENCE {} } } RRCMessage-rN-IEs ::= SEQUENCE { field1-rN ENUMERATED { value1, value2, value3, value4} OPTIONAL, -- Need N field2-rN InformationElement2-rN OPTIONAL, -- Need N nonCriticalExtension RRCConnectionReconfiguration-vMxy-IEs OPTIONAL } RRCConnectionReconfiguration-vMxy-IEs ::= SEQUENCE { field2-rM InformationElement2-rM OPTIONAL, -- Cond NoField2rN nonCriticalExtension SEQUENCE {} OPTIONAL } -- ASN1STOP Finally, it is noted that a critical extension may be introduced in the same release as the one in which the original field was introduced e.g. to correct an essential ASN.1 error. In such cases a UE capability may be introduced, to assist the network in deciding whether or not to use the critical extension. In the case of list fields (SEQUENCE OF types in ASN.1) using the ToAddMod/ToRelease construction, the use of critical extensions to increase the size of a list should be avoided; that is, replacing the original list field by a new field also used to signal entries previously covered by the original field (i.e. extensions done according to the following example) should be avoided: -- /example/ ASN1START -- Discouraged example ContainingStructure ::= SEQUENCE { listElementToAddModList SEQUENCE (SIZE (1..maxNrofListElements)) OF ListElement OPTIONAL, -- Need N ..., [[ listElementToAddModList-rN SEQUENCE (SIZE (1..maxNrofListElements-rN)) OF ListElement OPTIONAL -- Need N ]] }-- ASN1STOP Instead, a non-critical list extension mechanism should typically be used, such that the extension field only adds the new entries of the list. This approach is further described in clause A.4.3.6. If the critical extension mechanism for a list is used, it should be clarified in the field description that the two versions of the list are not configured together, and that the network should release the contents of the original version when configuring the replacement version.

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

A.4.2

8.18.4 MT-SDT

The procedure for mobile terminated small data transmission in RRC Inactive is shown in Figure 8.18.4-1. Figure 8.18.4-1: Mobile Terminated Small Data Transmission in RRC Inactive state. 1. During the setup or modification of the bearer context as specified in 8.9.2, the gNB-CU-CP requests the gNB-CU-UP to provide MT-SDT information. 2a-0. The gNB-CU-UP receives DL data for the UE in RRC Inactive on NG-U interface. 2a-1. The gNB-CU-UP sends DL DATA NOTIFICATION message to the gNB-CU-CP. If determining that DL data packets are only mapped to SDT bearers, as requested in step 1, the gNB-CU-UP includes the MT-SDT information in the DL DATA NOTIFICATION message. 2b. The gNB-CU-CP receives DL NAS signalling over NGAP. 3. After 2a or 2b, the gNB-CU-CP sends PAGING message to the gNB-DU. The MT-SDT indication may be included in the PAGING message. 4. The gNB-DU sends the Paging message to the UE. In case the MT-SDT indication is received in step 3, the gNB-DU includes the MT-SDT indicator in the Paging message. 5. If the UE has been successfully reached, it initiates the RRC connection resume procedure as described in 8.6.2 or 8.9.6.2, or initiates the SDT procedure as described from step 1 in 8.18.1 or from step 9 in 8.18.2 or from step 1 in 8.18.3 with the following difference: - In case SDT procedure is initiated, the UE may indicate MT-SDT in the RRCResumeRequest, which may be without UL data.

3GPP TS 38.401

NG-RAN; Architecture description

RAN3

3GPP Series : 38 , Radio technology beyond LTE

8.18.4

5.19.4 AMF Load Re-Balancing

The AMF load re-balancing functionality permits cross-section of its subscribers that are registered on an AMF (within an AMF Set) to be moved to another AMF within the same AMF set with minimal impacts on the network and end users. AMF may request some or all of the 5G-AN node(s) to redirect a cross-section of UE(s) returning from CM-IDLE state to be redirected to another AMF within the same AMF set, if the 5G-AN is configured to support this. The AMF may request some or all of the 5G-AN node(s) to redirect the UEs served by one of its GUAMI(s) to a specific target AMF within the same AMF set or to any different AMF within the same AMF set. When indicating a specific target AMF, the AMF should ensure that the load re-balancing will not cause overload in the target AMF. NOTE: This requirement can be fulfilled by the AMF itself or by the OAM. For UE(s) in CM-IDLE state, when UE subsequently returns from CM-IDLE state and the 5G-AN receives an initial NAS message with a 5G S-TMSI or GUAMI pointing to an AMF that requested for redirection, the 5G-AN should select the specific target AMF (provided by the original AMF) or a different AMF from the same AMF set and forward the initial NAS message. For UE(s) in CONNECTED mode, similar mechanisms for AMF Management can be used to move the UE to another AMF in the same AMF set as described in clause 5.21.2, except that the old AMF deregisters itself from NRF. The newly selected/target AMF (which is now the serving AMF) will re-assign the GUTI (using its own GUAMI(s)) to the UE(s). It is not expected that the 5G-AN node rejects any request or enables access control restriction when it receives a request for redirection for load control from the connected AMF(s). When the AMF wants to stop redirection, the AMF can indicate that it can serve all UE(s) in CM-IDLE state to stop the redirection. NOTE 1: An example use for the AMF load re-balancing functionality is for the AMF to pro-actively re-balance its load prior to reaching overload i.e. to prevent overload situation. NOTE 2: Typically, AMF Load Re-Balancing is not needed when the AMF becomes overloaded because the Load Balancing function should have ensured that the other AMFs within the AMF Set are similarly overloaded.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.19.4

7B.3 Authentication for FN-RG

The FN-RG connects to 5GC via W-5GAN, which has the W-AGF function that provides connectivity to the 5GC via N2 and N3 reference points. Since the FN-RG is a non-wireless entity defined by BBF or CableLabs, it doesn’t support N1. The W-AGF provides N1 connectivity on behalf of the FN-RG. The authentication method is executed between the FN-RG and AUSF as shown in Figure 7B.c. The W-AGF may authenticate the FN-RG; this is controlled by local policies. It is assumed that there is a trust relationship between the wireline operator that manages the W-5GAN and the PLMN operator managing the 5GC. The AMF trusts the W-5GAN based on mutual authentication executed when security is established on the interface between the two using NDS/IP or DTLS. Figure7B.c FN-RG authentication procedure 1. A layer-2 (L2) connection is established between the FN-RG and the FAGF function in the W-AGF. 2. The FN-RG is authenticated by the W-AGF. Authentication method used for FN-RG is defined by BBF or CableLabs and out of scope of 3GPP. 3-4. The W-AGF shall perform initial registration on behalf of the FN-RG. The W-AGF shall generate a Registration Request message and send it to the AMF over N2. The Registration Request message contains the SUCI of the FN-RG. The N2 message contains an indication that the W-AGF has authenticated the FN-RG. 5. The AMF shall select an AUSF based on the received SUCI. The AMF shall send a Nausf_UEAuthentication_Authenticate Request message to the AUSF. It contains the SUCI of the FN-RG. It also contains the authenticated indication generated by the W-AGF. 6. The AUSF shall send a Nudm_UEAuthentication_Get Request to the UDM. It contains the SUCI of the FN-RG and the authenticated indication. 7. The UDM shall invoke the SIDF and maps the SUCI to the SUPI. 8. The UDM decides, based on the subscription profile of the SUPI and the authenticated indication that authentication has been completed by the W-5GAN, that authentication by the home network is not required for the FN-RG. 9. The UDM shall send a Nudm_UEAuthentication_Get Response to the AUSF. It contains the SUPI of the FN-RG and an indication that authentication by the home network is not required. 10. After checking the indication set by the UDM, The AUSF shall not perform authentication and shall send a Nausf_UEAuthentication_Authenticate Response to the AMF. It contains the SUPI of the FN-RG and the indication that authentication by the home network is not required set by the UDM. This response from AUSF indicates that authentication is not required, and no KSEAF is included. 11. After checking the indication to make sure that the authentication by the home network is not required, the AMF shall estabilish the NAS security between AMF and W-AGF with NULL encryption and NULL integrity protection. 12. The AMF shall send Registration Accept message to the W-AGF. This message contains 5G-GUTI and other parameters. 13. The W-AGF shall send a Registration Complete message back to the AMF. The W-AGF shall store the 5G-GUTI for use in later NAS procedures.

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

7B.3

8.2.2.4.1C Minimum Requirement Single-Layer Spatial Multiplexing 2 Tx Antenna Ports (demodulation subframe overlaps with aggressor cell ABS and CRS assistance information are configured)

The requirements are specified in Table 8.2.2.4.1C-2, with the addition of parameters in Table 8.2.2.4.1C-1. The purpose is to verify the closed loop rank-one performance with wideband precoding if the PDSCH transmission in the serving cell takes place in subframes that overlap with ABS [9] of the aggressor cell with CRS assistance information. In Table 8.2.2.4.1C-1, Cell 1 is the serving cell, and Cell 2 and Cell 3 are the aggressor cells. The downlink physical channel setup for Cell 1 is according to Annex C.3.2 and for Cell 2 and Cell 3 is according to Annex C.3.3, respectively. The CRS assistance information [7] includes Cell 2 and Cell 3. Table 8.2.2.4.1C-1: Test Parameters for Single-Layer Spatial Multiplexing (FRC) – Non-MBSFN ABS Table 8.2.2.4.1C-2: Minimum Performance Single-Layer Spatial Multiplexing (FRC)– Non-MBSFN ABS

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.4.1C

4.11.1.5.5 5GS to EPS handover using N26 interface

In step 3 of clause 4.11.1.2.1, the Forward Relocation Request may include new information Return Preferred. Return Preferred is an indication by the AMF of a preferred return of the UE to the last used 5GS PLMN at a later access change to a 5GS shared network. RFSP in Use ValidityTime is provided by the AMF to the MME if the AMF selects the RFSP Index in use identical to the authorized RFSP Index as specified in clause 5.4.3.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] and validity time is received from PCF as specified in clause 4.16.2.2 and in clause 6.1.2.1 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. The MME handles RFSP Index as specified in clause 4.11.1.5.8. The MME may store the last used 5GS PLMN ID in UE's MM Context. The MME may provide E-UTRAN with a Handover Restriction List taking into account the last used 5GS PLMN ID and the Return Preferred indication. The Handover Restriction List contains a list of PLMN IDs as specified by TS 23.251[ Network sharing; Architecture and functional description ] [35].

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.11.1.5.5

10.5.6.3.6 Initial small data rate control parameters

The purpose of the Initial small data rate control parameters container contents is to indicate the Initial small data rate control parameters. The Initial small data rate control parameters container contents are coded as shown in figure 10.5.6.3.6-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.6.3.6-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The Initial small data rate control parameters container contents is 7 octets long. If the Initial small data rate control parameters container contents is longer than 7 octets, the 8th octet and later octets are ignored. Figure 10.5.6.3.6-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Initial small data rate control parameters Table 10.5.6.3.6-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Initial small data rate control parameters

3GPP TS 24.008

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

CT WG1

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

10.5.6.3.6

10.2.3 Conditional PSCell Addition

A Conditional PSCell Addition (CPA) is defined as a PSCell addition that is executed by the UE when execution condition(s) is met. The UE starts evaluating the execution condition(s) upon receiving the CPA configuration, and stops evaluating the execution condition(s) once PSCell addition or PCell change is triggered. The following principles apply to CPA: - The CPA configuration contains the configuration of CPA candidate PSCell(s), execution condition(s) and may contain the MCG configuration, to be applied when CPA execution is triggered. - An execution condition may consist of one or two trigger condition(s) (see CondEvent, as defined in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [4] or TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10]). Only a single RS type and at most two different trigger quantities (e.g. RSRP and RSRQ, RSRP and SINR, etc.) can be used for the evaluation of CPA execution condition of a single candidate PSCell. - Before any CPA execution condition is satisfied, upon reception of PSCell addition command or PCell change command, the UE executes the PSCell addition procedure as described in clause 10.2.1 or 10.2.2, or the PCell change procedure as described in clause 9.2.3.2 in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [3] or clause 10.1.2.1 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], regardless of any previously received CPA configuration. Upon the successful completion of PSCell addition procedure or PCell change procedure, the UE releases the stored CPA configuration. - While executing CPA, the UE is not required to continue evaluating the execution condition of other candidate PSCell(s) or PCell(s). - Once the CPA procedure is executed successfully, the UE releases all stored conditional reconfigurations (i.e. for CPA and for CHO, as specified in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [3] or TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [2]). CPA configuration in HO command, in PSCell addition command, or within any conditional reconfiguration (i.e., CPA, CPC or CHO configuration) is not supported.

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

10.2.3

7.4 Access Control

NG-RAN supports overload and access control functionality such as RACH back off, RRC Connection Reject, RRC Connection Release and UE based access barring mechanisms. One unified access control framework as specified in TS 22.261[ Service requirements for the 5G system ] [19] applies to all UE states (RRC_IDLE, RRC_INACTIVE and RRC_CONNECTED) for NR. NG-RAN broadcasts barring control information associated with Access Categories and Access Identities (in case of network sharing, the barring control information can be set individually for each PLMN). The UE determines whether an access attempt is authorized based on the barring information broadcast for the selected PLMN, and the selected Access Category and Access Identity(ies) for the access attempt: - For NAS triggered requests, NAS determines the Access Category and Access Identity(ies); - For AS triggered requests, RRC determines the Access Category while NAS determines the Access Identity(ies). The gNB handles access attempts with establishment causes "emergency", "mps-PriorityAccess" and "mcs-PriorityAccess" (i.e. Emergency calls, MPS, MCS subscribers) with high priority and responds with RRC Reject to these access attempts only in extreme network load conditions that may threaten the gNB stability. Unified access control does not apply to IAB-MTs or NCR-MTs.

3GPP TS 38.300

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

RAN2

3GPP Series : 38 , Radio technology beyond LTE

7.4

Subscriber charging 5.5.1.0 General

The charging data collected from the HPLMN, interrogating PLMN, and/or VPLMN network elements is employed to determine the network utilization charges for the basic and supplementary services utilized by the home subscribers of the PLMN. The charges calculated are then combined with the network access (subscription) charges and billed to those customers directly serviced by the PLMN. For those subscribers handled by Service Providers, the billing information is employed for both wholesale (Network Operator to Service Provider) and retail (Service Provider to Subscriber) billing. Consequently, having been processed by the PLMN billing system, the charging data collected from the network elements may also be sent to the Service Provider for further processing.

3GPP TS 32.240

Telecommunication management; Charging management; Charging architecture and principles

SA WG5

3GPP Series : 32 , OAM&P and Charging

Subscriber

9.7.1.4 TDD (Category 1bis UE)

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

3GPP TS 36.101

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

RAN4

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

9.7.1.4

5.7.1.10 UE-Slice-MBR enforcement and rate limitation

If a supporting NG-RAN receives for a UE a UE-Slice-MBR (see clause 5.7.2.6) for an S-NSSAI from the AMF, the NG-RAN shall apply this UE-Slice-MBR for all PDU Sessions of that UE corresponding to the S-NSSAI which have an active user plane if feasible. In particular, the NG-RAN shall enforce this UE-Slice-MBR as follows: 1) Whenever a request for a GBR QoS Flow establishment or modification is received, the NG-RAN admission control shall ensure that the sum of the GFBR values of the admitted GBR QoS Flows is not exceeding the UE-Slice-MBR and, if the QoS Flow cannot be admitted, the NG-RAN shall reject the establishment/modification of the QoS Flow. NOTE: If the UE-Slice-MBR would be exceeded by a new/modified GBR QoS Flow, the NG-RAN determines whether the new/modified GBR QoS Flow can pre-empt any existing GBR QoS Flow of the UE's PDU Session(s) corresponding to the same S-NSSAI based on their ARP values (as per clause 5.7.2.2), e.g. to support certain priority services (e.g. MPS). If this is not possible, the NG-RAN can reject the establishment/modification of the QoS Flow. 2) The NG-RAN shall ensure that the aggregated bitrate across all GBR and Non-GBR QoS Flows belonging to those PDU Sessions is not exceeding the UE-Slice-MBR, while always guaranteeing the GFBR of every GBR QoS Flow of those PDU Sessions as described in clause 5.7.2.5.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.7.1.10

4.2.5.2 Maximum Number of simultaneous E-RABs.

a) This measurement provides the maximum number of simultaneous E-RABs. The measurement is split into subcounters per E-RAB QoS level (QCI). b) SI. c) This measurement is obtained by sampling at a pre-defined interval, the number of simultaneous E-RABs and then taking the maximum. The measurement is split into subcounters per QCI, and the possible QCIs are included in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [9]. 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.UsageNbrMax.QCI where QCI identifies the E-RAB level quality of service class. f) EUtranCellFDD EUtranCellTDD g) Valid for packet switching. 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.2.5.2

5.2.2.6 T430 expiry

The UE shall: 1> if T430 for serving cell expires and if in RRC_CONNECTED: 2> inform lower layers that UL synchronisation is lost; 2> acquire SIB19 as defined in clause 5.2.2.3.2; 2> upon successful acquisition of SIB19: 3> inform lower layers when UL synchronisation is obtained; NOTE: The exact time when UL synchronisation is obtained (after SIB19 is acquired) is left to UE implementation, which can be from the subframe indicated by epochTime and optionally before the subframe indicated by epochTime.

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

5.2.2.6

– ZP-CSI-RS-Resource

The IE ZP-CSI-RS-Resource is used to configure a Zero-Power (ZP) CSI-RS resource (see TS 38.214[ NR; Physical layer procedures for data ] [19], clause 5.1.4.2). Reconfiguration of a ZP-CSI-RS-Resource between periodic or semi-persistent and aperiodic is not supported. ZP-CSI-RS-Resource information element -- ASN1START -- TAG-ZP-CSI-RS-RESOURCE-START ZP-CSI-RS-Resource ::= SEQUENCE { zp-CSI-RS-ResourceId ZP-CSI-RS-ResourceId, resourceMapping CSI-RS-ResourceMapping, periodicityAndOffset CSI-ResourcePeriodicityAndOffset OPTIONAL, --Cond PeriodicOrSemiPersistent ... } ZP-CSI-RS-ResourceId ::= INTEGER (0..maxNrofZP-CSI-RS-Resources-1) -- TAG-ZP-CSI-RS-RESOURCE-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

5.2.2.2 Namf_Communication service 5.2.2.2.1 General

Service description: This service enables an NF to communicate with the UE through N1 NAS messages or with the AN (both UE and non UE specific). The service operations defined below allow the NF to communicate with the UE and the AN. The following are the key functionalities of this NF service. - Provide service operations for transporting N1 messages to the UE; - Allow NFs to subscribe and unsubscribe for notifications of specific N1 messages from the UE; - Allow NFs to subscribe and unsubscribe for notifications about specific information from AN; - Provide service operations for initiating N2 messages towards the AN; - Security Context Management; and - UE information management and transfer (including its security context).

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

5.2.2.2

6.5.2B Transmit modulation quality for UL-MIMO

For UE supporting UL-MIMO, the transmit modulation quality requirements are specified at each transmit antenna connector. If UE is configured for transmission on single-antenna port, the requirements in subclause 6.5.2 apply. The transmit modulation quality is specified in terms of: - Error Vector Magnitude (EVM) for the allocated resource blocks (RBs) - EVM equalizer spectrum flatness derived from the equalizer coefficients generated by the EVM measurement process - Carrier leakage (caused by IQ offset) - In-band emissions for the non-allocated RB

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

5.5.2 De-registration procedure 5.5.2.1 General

The de-registration procedure is used: a) by the UE to de-register for 5GS services over 3GPP access when the UE is registered over 3GPP access; b) by the UE to de-register for 5GS services over non-3GPP access when the UE is registered over non-3GPP access; c) by the UE to de-register for 5GS services over 3GPP access, non-3GPP access or both when the UE is registered in the same PLMN over both accesses; d) by the network to inform the UE that it is deregistered for 5GS services over 3GPP access when the UE is registered over 3GPP access; e) by the network to inform the UE that it is deregistered for 5GS services over non-3GPP access when the UE is registered over non-3GPP access; f) by the network to inform the UE that it is deregistered for 5GS services over 3GPP access, non-3GPP access or both when the UE is registered in the same PLMN over both accesses; g) by the network to inform the UE to re-register to the network; h) by the network to inform the UE supporting UAS service that it is deregistered for UAS services in 5GS; and i) by the network to inform the UE operating as MBSR that it is deregistered for MBSR in 5GS. The de-registration procedure with appropriate de-registration type shall be invoked by the UE: a) if the UE is switched off; b) as part of the eCall inactivity procedure defined in subclause 5.5.3; and c) as part of USIM removal. The de-registration procedure with appropriate de-registration type shall be invoked by the network: a) if the network informs whether the UE should re-register to the network. The de-registration procedure with appropriate access type shall be invoked by the UE: a) to de-register for 5GS services over 3GPP access when the UE is registered over 3GPP access; b) to de-register for 5GS services over non-3GPP access when the UE is registered over non-3GPP access; c) to de-register for 5GS services over 3GPP access, non-3GPP access or both when the UE is registered in the same PLMN over both accesses; d) to de-register for 5GS services over 3GPP access, if the UE is registered for disaster roaming over 3GPP access and has successfully registered over non-3GPP access on another PLMN; or e) to de-register for 5GS services if an event is triggered in the UE that would make the UE unavailable for a certain period of time and the UE is not able to store its 5GMM and 5GSM context. NOTE 1: If the UE is able to store its 5GMM and 5GSM contexts, the UE triggers the registration procedure for mobility and periodic registration update. The de-registration procedure with appropriate access type shall be invoked by the network: a) if the network needs to inform the UE that it is deregistered over 3GPP access when the UE is registered over 3GPP access; b) if the network needs to inform the UE that it is deregistered over non-3GPP access when the UE is registered over non-3GPP access; or c) if the network needs to inform the UE that it is deregistered over 3GPP access, non-3GPP access or both when the UE is registered in the same PLMN over both accesses. If the de-registration procedure is triggered due to USIM removal, the UE shall indicate "switch off" in the de-registration type IE. If the de-registration procedure is requested by the network for a UE that has an emergency PDU session, the AMF shall not send a DEREGISTRATION REQUEST message to the UE and indicate to the SMF to release all non-emergency PDU sessions as specified in 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9]. If the de-registration procedure for 5GS services is performed, a local release of the PDU sessions over the indicated access(es), if any, for this particular UE is performed. If a PDU session that will be released is associated with one or more multicast MBS sessions, the UE is considered as removed from the associated multicast MBS sessions. The UE is allowed to initiate the de-registration procedure even if the timer T3346 is running. NOTE 2: When the UE has no PDU sessions over non-3GPP access, or the UE moves all the PDU sessions over a non-3GPP access to a 3GPP access, the UE and the AMF need not initiate de-registration over the non-3GPP access. The AMF shall provide the UE with a non-3GPP de-registration timer. When the AMF enters the state 5GMM-DEREGISTERED for 3GPP access, the AMF shall delete the stored UE radio capability information or the UE radio capability ID, if any. When upper layers indicate that emergency services are no longer required, the UE if still registered for emergency services, may perform UE-initiated de-registration procedure followed by a re-registration to regain normal services, if the UE is in or moves to a suitable cell. If the UE is registered for onboarding services in SNPN, after completing the configuration of one or more entries of the "list of subscriber data", the UE should perform UE-initiated de-registration procedure. To prevent the UE registered for onboarding services in SNPN from staying on the ON-SNPN or to prevent a UE whose subscription only allows for configuration of SNPN subscription parameters in PLMN via the user plane, from staying registered indefinitely, when an implementation specific timer expires: - if the AMF considers that the UE is in 5GMM-IDLE, the AMF shall locally de-registers the UE; or - if the UE is in 5GMM-CONNECTED, the AMF shall initiate the network-initiated de-registration procedure (see subclause 5.5.2.3). NOTE 3: The value of the implementation specific timer for onboarding services needs to be large enough to allow a UE to complete the configuration of one or more entries of the "list of subscriber data" taking into consideration that configuration of SNPN subscription parameters in PLMN via the user plane or onboarding services in SNPN involves third party entities outside of the operator's network. NOTE 4: How to determine the completion of the configuration of one or more entries of the "list of subscriber data" is UE implementation specific. If the de-registration procedure is not due to switch off and upper layers request establishing an emergency PDU session before the de-registration procedure has been completed, the UE shall abort the de-registration procedure, perform local de-registration and initiate a registration procedure. If the UE in 5GMM-CONNECTED mode determines to obtain service on a higher priority PLMN due to SOR, then based on the conditions as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] annex C, where applicable, the UE shall perform UE-initiated de-registration procedure. If the UE is registered for disaster roaming services, and the UE receives an indication of whether disaster roaming is enabled in the UE set to "Disaster roaming is disabled in the UE" in a UE parameters update transparent container, the UE shall perform UE-initiated de-registration 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.5.2

5.7.5.3 Reflective QoS Control

Reflective QoS is controlled on per-packet basis by using the Reflective QoS Indication (RQI) in the encapsulation header on N3 (and N9) reference point together with the QFI and together with a Reflective QoS Timer (RQ Timer) value that is either signalled to the UE upon PDU Session Establishment (or upon PDU Session Modification as described in clause 5.17.2.2.2) or set to a default value. The RQ Timer value provided by the core network is at the granularity of PDU Session (the details are specified in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]). When the 5GC determines that Reflective QoS has to be used for a specific SDF belonging to a QoS Flow, the SMF shall provide the RQA (Reflective QoS Attribute) within the QoS Flow's QoS profile to the NG-RAN on N2 reference point unless it has been done so before. When the RQA has been provided to the NG-RAN for a QoS Flow and the 5GC determines that the QoS Flow carries no more SDF for which Reflective QoS has to be used, the SMF should signal the removal of the RQA (Reflective QoS Attribute) from the QoS Flow's QoS profile to the NG-RAN on N2 reference point. NOTE 1: The SMF could have a timer to delay the sending of the removal of the RQA. This would avoid signalling to the RAN in the case of new SDFs subject to Reflective QoS are bound to this QoS Flow in the meantime. When the 5GC determines to use Reflective QoS for a specific SDF, the SMF shall ensure that the UPF applies the RQI marking (e.g. by setting the indication to use Reflective QoS in the QER associated with the DL PDR if not already set) for this SDF. The SMF shall also ensure that the uplink packets for this SDF can be received by the UPF from the QoS Flow to which the DL PDR of the SDF is associated with as specified in TS 29.244[ Interface between the Control Plane and the User Plane nodes ] [65], e.g. by generating a new UL PDR for this SDF for that QoS Flow and providing it to the UPF. When the UPF is instructed by the SMF to apply RQI marking, the UPF shall set the RQI in the encapsulation header on the N3 (or N9) reference point for every DL packet corresponding to this SDF. When an RQI is received by (R)AN in a DL packet on N3 reference point, the (R)AN shall indicate to the UE the QFI and the RQI of that DL packet. Upon reception of a DL packet with RQI: - if a UE derived QoS rule with a Packet Filter corresponding to the DL packet does not already exist, - the UE shall create a new UE derived QoS rule with a Packet Filter corresponding to the DL packet (as described in clause 5.7.5.2); and - the UE shall start, for this UE derived QoS rule, a timer set to the RQ Timer value. - otherwise, - the UE shall restart the timer associated to this UE derived QoS rule; and - if the QFI associated with the downlink packet is different from the QFI associated with the UE derived QoS rule, the UE shall update this UE derived QoS rule with the new QFI. NOTE 2: Non-3GPP ANs does not need N2 signalling to enable Reflective QoS. Non 3GPP accesses are expected to send transparently the QFI and RQI to the UE. If the UPF does not include the RQI, no UE derived QoS rule will be generated. If RQI is included to assist the UE to trigger an update of the UE derived QoS rule, the reception of PDU for a QFI restarts the RQ Timer. Upon timer expiry associated with a UE derived QoS rule the UE deletes the corresponding UE derived QoS rule. When the 5GC determines not to use Reflective QoS for a specific SDF any longer: - The SMF shall ensure that the UPF stops applying RQI marking as specified in TS 29.244[ Interface between the Control Plane and the User Plane nodes ] [65] (e.g. by removing the indication to use Reflective QoS from the QER associated with the DL PDR) for this SDF. - When the UPF receives this instruction to stop applying RQI marking, the UPF shall no longer set the RQI in the encapsulation header on the N3 (or N9) reference point DL packets corresponding to this SDF. - The SMF shall also ensure that, after an operator configurable time, the uplink packets for this SDF will not be accepted by the UPF over the QoS Flow on which Reflective QoS was applied for this SDF as specified in TS 29.244[ Interface between the Control Plane and the User Plane nodes ] [65], e.g. by removing the UL PDR for this SDF from that QoS Flow. NOTE 3: The operator configurable time has to be at least as long as the RQ Timer value to ensure that no UL packet would be dropped until the UE derived QoS rule is deleted by the UE. When the 5GC determines to change the binding of the SDF while Reflective QoS is used for this SDF, the SMF shall ensure that the uplink packets for this SDF are accepted over the newly bound QoS Flow and, for an operator configurable time, over the previously bound QoS Flow.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.7.5.3

5.2.1.4.2 Call progress in the PLMN/ISDN environment

In order to inform the mobile station that the call is progressing in the PLMN/ISDN environment the network may send a progress indicator information element to the calling mobile station either: a) in an appropriate call control message, if a state change is required (e.g., ALERTING or CONNECT); or b) in the PROGRESS message, if no state change is appropriate. This progress indicator information element shall contain progress description value #32 "Call is end-to-end ISDN/PLMN". See also subclause 5.5.6 for further reactions of the mobile station.

3GPP TS 24.008

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

CT WG1

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

5.2.1.4.2

5.10.3 PDU Session User Plane Security

The User Plane Security Enforcement information provides the NG-RAN with User Plane security policies for a PDU session. It indicates: - whether UP integrity protection is: - Required: for all the traffic on the PDU Session UP integrity protection shall apply. - Preferred: for all the traffic on the PDU Session UP integrity protection should apply. - Not Needed: UP integrity protection shall not apply on the PDU Session. - whether UP confidentiality protection is: - Required: for all the traffic on the PDU Session UP confidentiality protection shall apply. - Preferred: for all the traffic on the PDU Session UP confidentiality protection should apply. - Not Needed: UP confidentiality shall not apply on the PDU Session. User Plane Security Enforcement information applies only over 3GPP access. Once determined at the establishment of the PDU Session the User Plane Security Enforcement information applies for the life time of the PDU Session. NOTE 1: Applicability of UP integrity protection of UP Security Enforcement is defined in TS 33.501[ Security architecture and procedures for 5G System ] [29] and TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27]. The SMF determines at PDU session establishment a User Plane Security Enforcement information for the user plane of a PDU session based on: - subscribed User Plane Security Policy which is part of SM subscription information received from UDM; and - User Plane Security Policy locally configured per (DNN, S-NSSAI) in the SMF that is used when the UDM does not provide User Plane Security Policy information. - The maximum supported data rate per UE for integrity protection for the DRBs, provided by the UE in the Integrity protection maximum data rate IE during PDU Session Establishment. The UE supporting NR as primary RAT, i.e. NG-RAN access via Standalone NR, shall set the Integrity protection maximum data rate IE for Uplink and Downlink to full rate at PDU Session Establishment as defined in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]. A UE not supporting NR as primary RAT and supporting E-UTRA connected to 5GC, shall set the Integrity protection maximum data rate IE for Uplink and Downlink to NULL at PDU Session Establishment as defined in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]. The User Plane Security Enforcement information provides the MME with User Plane integrity protection policies for the PDU session (PDN Connection). The information indicates whether UP integrity protection is: - Required: for all the traffic on the PDU Session (PDN Connection) UP integrity protection shall apply. - Preferred: for all the traffic on the PDU Session (PDN Connection) UP integrity protection should apply. - Not Needed: UP integrity protection shall not apply on the PDU Session (PDN Connection). In turn, the MME provides per EPS bearer User Plane Security Enforcement information to the E-UTRAN. All the bearers within a PDN Connection share the same User Plane integrity protection policies. The UE capability to support user plane integrity protection with EPS is indicated to AMF in the S1 UE network capability information. If the UE supports user plane integrity protection with EPS, and the AMF supports the associated functionality, the AMF indicates this to SMF at PDU Session Establishment using NG-RAN. If the UE and AMF support user plane integrity protection with EPS, for PDU Sessions with UP integrity protection of UP Security Enforcement Information set to Required, the SMF may perform the EPS bearer ID allocation procedure as described in TS 23.502[ Procedures for the 5G System (5GS) ] [3] clause 4.11.1.4. If the UE does not support user plane integrity protection with EPS or the AMF does not support the associated functionality, the SMF shall not trigger the EPS bearer ID allocation procedure in clause 4.11.1.4 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. Unless the UE, the serving eNB and the MME support user plane integrity protection with EPS, the SMF+PGW-C shall reject a PDN Connection Establishment using EPS if the UP Security Enforcement Information has UP integrity protection set to Required. The SMF+PGW-C shall (e.g. based on the received RAT Type) reject a PDN Connection Establishment using GERAN/UTRAN if the UP Security Enforcement Information has UP integrity protection set to Required. NOTE 2: This assumes that the optional user plane integrity protection for GPRS specified in Release 13 has not been deployed. The SMF may, based on local configuration, reject the PDU Session Establishment request depending on the value of the maximum supported data rate per UE for integrity protection. NOTE 3: Reasons to reject a PDU Session Establishment request can e.g. be that the UP Integrity Protection is determined to be "Required" while the maximum supported data rate per UE for integrity protection is less than the expected required data rate for the DN. NOTE 4: The operator can take care to reduce the risk of such rejections when configuring the subscribed User Plane Security Policy for a DNN. For example, the operator may apply integrity protection "Required" only in scenarios where it can be assumed that the UE maximum supported data rate per UE for integrity protection is likely to be adequate for the DN. The User Plane Security Policy provide the same level of information than User Plane Security Enforcement information. User Plane Security Policy from UDM takes precedence over locally configured User Plane Security Policy. The User Plane Security Enforcement information may include the maximum supported data rate for integrity protection provided by the UE, is communicated from SMF to the NG-RAN for enforcement as part of PDU session related information. If the UP Integrity Protection is determined to be "Required" or "Preferred", the SMF also provides the maximum supported data rate per UE for integrity protection as received in the Integrity protection maximum data rate IE. This takes place at establishment of a PDU Session or at activation of the user plane of a PDU Session. The NG-RAN rejects the establishment of UP resources for the PDU Session when it cannot fulfil User Plane Security Enforcement information with a value of Required. The NG-RAN may also take the maximum supported data rate per UE for integrity protection into account in its decision on whether to accept or reject the establishment of UP resources. In this case the SMF releases the PDU Session. The NG-RAN notifies the SMF when it cannot fulfil a User Plane Security Enforcement with a value of Preferred. NOTE 5: For example, the NG-RAN cannot fulfil requirements in User Plane Security Enforcement information with UP integrity protection set to "Required" when it cannot negotiate UP integrity protection with the UE. It is responsibility of the NG-RAN to enforce that the maximum UP integrity protection data rate delivered to the UE in downlink is not exceeding the maximum supported data rate for integrity protection. It is expected that generally the UP integrity protection data rate applied by the UE in uplink will not exceed the indicated maximum supported data rate, but the UE is not required to perform strict rate enforcement. User Plane Security Enforcement information and the maximum supported data rate per UE for integrity protection is communicated from source to target NG-RAN node at handover. If the target RAN node cannot support requirements in User Plane Security Enforcement information, the target RAN node rejects the request to set up resources for the PDU Session. In this case the PDU Session is not handed over to the target RAN node and the PDU Session is released. If the UE or the new eNB or the MME does not indicate support of user plane integrity protection with EPS, PDU Sessions with UP integrity protection of the User Plane Security Enforcement information set to Required are not transferred to EPS as follows: - In the case of mobility without N26, the SMF+PGW-C shall reject a PDN connectivity request in EPS with handover indication if the UP integrity protection of the User Plane Security Enforcement is set to Required. NOTE 6: As described in clause 5.17.2.3.3, the UE does not know before trying to move a given PDU Session to EPC, whether that PDU session can be transferred to EPC. - In the case of idle mode and connected mode mobility with N26 to EPS, or mobility without N26, the SMF+PGW-C ensures that the PDU session is released. If the UE, target eNB and the target MME indicate support of User Plane Integrity Protection with EPS, PDU Sessions with UP integrity protection of the User Plane Security Enforcement information set to Required are transferred from 5GS to EPS according to existing procedures. For the bearers of PDN Connections with UP integrity protection set to Required, at (both idle mode and connected mode) mobility (including intra-TA mobility) to an eNB that does not support User Plane Integrity Protection with EPS, the MME shall inform the SMF+PGW-C and the SMF+PGW-C ensures that the PDU session is released. At connected mode mobility from EPS to GERAN/UTRAN or to a part of the EPS that does not support User Plane Integrity Protection, the source E-UTRAN shall ensure that EPS bearers with UP integrity protection of the User Plane Security Enforcement information set to Required are not handed over. In the case of idle mode mobility from an MME that supports User Plane Integrity Protection, to an MME that does not support User Plane Integrity Protection, the (home) SMF+PGW-C shall trigger (e.g. based on the lack of MME UPIP capability information) the release of the bearers of PDN Connections with UP integrity protection set to Required. At any (e.g. idle mode) mobility from EPS to GERAN/UTRAN, the (home) SMF+PGW-C shall trigger (e.g. based on the received RAT Type) the release of the bearers of PDN Connections with UP integrity protection set to Required. PDU Sessions with UP confidentiality protection of the User Plane Security Enforcement information set to Required and UP integrity protection of the User Plane Security Enforcement information not set to Required, are allowed to be handed over to EPS regardless of how UP confidentiality protection applies in EPS. In the case of dual connectivity, the Integrity Protection is set to "Preferred", the Master RAN node may notify the SMF when it cannot fulfil a User Plane Security Enforcement with a value of Preferred. The SMF handling of the PDU session with respect to the Integrity Protection status is up to SMF implementation decision.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.10.3

5.6.2.2.3 Abnormal cases in the UE

The following abnormal cases can be identified: a) Paging message received with access type set to non-3GPP access while the UE is in 5GMM-CONNECTED mode over non-3GPP access. The UE shall not respond to paging message. b) Paging message received with access type set to 3GPP access when UE-initiated 5GMM specific procedure or service request procedure is ongoing. The UE shall proceed with 5GMM specific procedure or service request procedure. If for registration procedure and service requestprocedure lower layers indicate that the access attempt is barred, then the UE shall handle the pending paging message as specified in subclause 5.6.2.2.1. Otherwise, the UE shall ignore the paging once lower layers confirm the establishment of the signalling connection.

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

– UERadioPagingInformation

This message is used to transfer radio paging information, covering both upload to and download from the 5GC, and between gNBs. Direction: gNB to/ from 5GC and gNB to/from gNB UERadioPagingInformation message -- ASN1START -- TAG-UE-RADIO-PAGING-INFORMATION-START UERadioPagingInformation ::= SEQUENCE { criticalExtensions CHOICE { c1 CHOICE{ ueRadioPagingInformation UERadioPagingInformation-IEs, spare7 NULL, spare6 NULL, spare5 NULL, spare4 NULL, spare3 NULL, spare2 NULL, spare1 NULL }, criticalExtensionsFuture SEQUENCE {} } } UERadioPagingInformation-IEs ::= SEQUENCE { supportedBandListNRForPaging SEQUENCE (SIZE (1..maxBands)) OF FreqBandIndicatorNR OPTIONAL, nonCriticalExtension UERadioPagingInformation-v15e0-IEs OPTIONAL } UERadioPagingInformation-v15e0-IEs ::= SEQUENCE { dl-SchedulingOffset-PDSCH-TypeA-FDD-FR1 ENUMERATED {supported} OPTIONAL, dl-SchedulingOffset-PDSCH-TypeA-TDD-FR1 ENUMERATED {supported} OPTIONAL, dl-SchedulingOffset-PDSCH-TypeA-TDD-FR2 ENUMERATED {supported} OPTIONAL, dl-SchedulingOffset-PDSCH-TypeB-FDD-FR1 ENUMERATED {supported} OPTIONAL, dl-SchedulingOffset-PDSCH-TypeB-TDD-FR1 ENUMERATED {supported} OPTIONAL, dl-SchedulingOffset-PDSCH-TypeB-TDD-FR2 ENUMERATED {supported} OPTIONAL, nonCriticalExtension UERadioPagingInformation-v1700-IEs OPTIONAL } UERadioPagingInformation-v1700-IEs ::= SEQUENCE { ue-RadioPagingInfo-r17 OCTET STRING (CONTAINING UE-RadioPagingInfo-r17) OPTIONAL, inactiveStatePO-Determination-r17 ENUMERATED {supported} OPTIONAL, numberOfRxRedCap-r17 ENUMERATED {one, two} OPTIONAL, halfDuplexFDD-TypeA-RedCap-r17 SEQUENCE (SIZE (1..maxBands)) OF FreqBandIndicatorNR OPTIONAL, nonCriticalExtension UERadioPagingInformation-v1800-IEs OPTIONAL } UERadioPagingInformation-v1800-IEs ::= SEQUENCE { numberOfRxERedCap-r18 ENUMERATED {one, two} OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } -- TAG-UE-RADIO-PAGING-INFORMATION-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

5.16.3.2 IMS voice over PS Session Supported Indication over 3GPP access

The serving PLMN AMF shall send an indication toward the UE during the Registration procedure over 3GPP access to indicate if an IMS voice over PS session is supported or not supported in 3GPP access and non-3GPP access. A UE with "IMS voice over PS" voice capability over 3GPP access should take this indication into account when performing voice domain selection, as described in clause 5.16.3.5. The serving PLMN AMF may only indicate IMS voice over PS session supported over 3GPP access in one of the following cases: - If the network and the UE are able to support IMS voice over PS session in the current Registration Area with a 5G QoS Flow that supports voice as specified in clause 5.7. - If the network or the UE are not able to support IMS voice over PS session over NR connected to 5GC, but is able for one of the following: - If the network and the UE are able to support IMS voice over PS session over E-UTRA connected to 5GC, and the NG-RAN supports a handover or redirection to E-UTRA connected to 5GC for this UE at QoS Flow establishment for IMS voice; - If the UE supports handover to EPS, the EPS supports IMS voice, and the NG-RAN supports a handover to EPS for this UE at QoS Flow establishment for IMS voice; or - If the UE supports redirection to EPS, the EPS supports IMS voice, and the NG-RAN supports redirection to EPS for this UE at QoS Flow establishment for IMS voice. - If the network is not able to provide a successful IMS voice over PS session over E-UTRA connected to 5GC, but is able for one of the following: - If the UE supports handover to EPS, the EPS supports IMS voice, and the NG-RAN supports a handover to EPS for this UE at QoS Flow establishment for IMS voice; or - If the UE supports redirection to EPS, the EPS supports IMS voice, and the NG-RAN supports redirection to EPS for this UE at QoS Flow establishment for IMS voice. The serving PLMN provides this indication based e.g. on local policy, UE capabilities, HPLMN, whether IP address preservation is possible, whether NG-RAN to UTRAN SRVCC is supported and how extended NG-RAN coverage is, and the Voice Support Match Indicator from the NG-RAN (see clause 4.2.8a of TS 23.502[ Procedures for the 5G System (5GS) ] [3]). NOTE 1: The terms "UE supports handover to EPS" or "UE supports redirection to EPS" used above also consider the case that the UE has signalled that S1 mode is enabled. In case the UE has signalled that S1 mode is disabled for a network that only supports IMS voice via EPS Fallback, the AMF will not indicate that IMS voice over PS session is supported over 3GPP access. A voice centric UE ensures its voice service as described in clauses 5.16.3.5 and 5.16.3.6. The AMF in serving PLMN shall indicate that IMS voice over PS is supported only if the serving PLMN has a roaming agreement that covers support of IMS voice with the HPLMN. This indication is per Registration Area. NOTE 2: If the network supports EPS fallback for voice the 5GC can be configured not to perform the Voice Support Match Indicator procedure in order to set the IMS voice over PS session Supported Indication. The serving SNPN provides the IMS voice over PS indication based e.g. on local policy, UE capabilities, whether IP address preservation is possible, and how extended NR coverage is. This indication is per Registration Area. NOTE 3: Since over 3GPP access, in SNPN access mode there is only support for NR and the "voice centric" UE cannot reselect to another RAT in the same registered SNPN if the first Registration Area that the UE tries to register from cannot support IMS voice, it is recommended that support for IMS voice is provided homogeneously in the whole SNPN if at all.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.16.3.2

– BSR-Config

The IE BSR-Config is used to configure buffer status reporting. BSR-Config information element -- ASN1START -- TAG-BSR-CONFIG-START BSR-Config ::= SEQUENCE { periodicBSR-Timer ENUMERATED { sf1, sf5, sf10, sf16, sf20, sf32, sf40, sf64, sf80, sf128, sf160, sf320, sf640, sf1280, sf2560, infinity }, retxBSR-Timer ENUMERATED { sf10, sf20, sf40, sf80, sf160, sf320, sf640, sf1280, sf2560, sf5120, sf10240, spare5, spare4, spare3, spare2, spare1}, logicalChannelSR-DelayTimer ENUMERATED { sf20, sf40, sf64, sf128, sf512, sf1024, sf2560, spare1} OPTIONAL, -- Need R ... } -- TAG-BSR-CONFIG-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

– MasterInformationBlockSidelink

The MasterInformationBlockSidelink includes the system information transmitted by a UE via SL-BCH. Signalling radio bearer: N/A RLC-SAP: TM Logical channel: SBCCH Direction: UE to UE MasterInformationBlockSidelink -- ASN1START -- TAG-MASTERINFORMATIONBLOCKSIDELINK-START MasterInformationBlockSidelink ::= SEQUENCE { sl-TDD-Config-r16 BIT STRING (SIZE (12)), inCoverage-r16 BOOLEAN, directFrameNumber-r16 BIT STRING (SIZE (10)), slotIndex-r16 BIT STRING (SIZE (7)), reservedBits-r16 BIT STRING (SIZE (2)) } -- TAG-MASTERINFORMATIONBLOCKSIDELINK-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

13.2.4.9 JOSE profile

SEPPs shall follow the JWE profile defined in TS 33.210[ Network Domain Security (NDS); IP network layer security ] [3] with the restriction that it shall only use AES GCM with a 128-bit or 256-bit key. The security considerations for the use of AES GCM in section 8.4 of RFC 7518 [59] shall be taken into account. In particular, the same key shall not be used more than 232 times and an IV value shall not be used more than once with the same key. SEPPs and IPXs shall follow the JWS profile as defined in TS 33.210[ Network Domain Security (NDS); IP network layer security ] [3] with the restriction that they shall only use ES256 algorithm.

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

13.2.4.9

4.7.4.1.5 Abnormal cases on the network side

The following abnormal cases can be identified: a) Detach request received in a CSG cell for which the MS has no valid CSG subscription If the MS initiates a detach procedure in a CSG cell the CSG ID of which is not valid for the MS and the detach procedure is not due to "switch off", the network shall proceed as follows: - if the detach type is "IMSI detach" and the MS has a PDN connection for emergency bearer services active, the SGSN shall send a DETACH ACCEPT message and deactivate all non-emergency PDP contexts, if any, by initiating a PDP context deactivation procedure; - otherwise, the network shall initiate the detach procedure. The network shall send a DETACH REQUEST message including the GMM cause value #25 "not authorized for this CSG".

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

8.99 Action Indication

Action Indication is coded as depicted in Figure 8.99-1. Figure 8.99-1: Action Indication Table 8.99-1: Indication If "deactivation indication" is set, it indicates that the receiving entity shall deactivate ISR and remove the UE resource locally as specified in 3GPP TS 23.007[ Restoration procedures ] [17] clause 27.3.1.2. If "paging indication" is set, it indicates that the receiving entity shall page the IDLE state UE as specified in 3GPP TS 23.007[ Restoration procedures ] [17] clause 27.3.2.2. If "paging stop indication" is set, it indicates that the receiving entity shall stop paging the UE as specified in 3GPP TS 23.380[ IMS Restoration Procedures ] [61] clause 5.4.2.1 and clause 5.4.3.2.

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

5.8.9.1 Sidelink RRC reconfiguration 5.8.9.1.1 General

Figure 5.8.9.1.1-1: Sidelink RRC reconfiguration, successful Figure 5.8.9.1.1-2: Sidelink RRC reconfiguration, failure The purpose of this procedure is to modify a PC5-RRC connection, e.g. to establish/modify/release sidelink DRBs or additional sidelink RLC bearer or PC5 Relay RLC channels, to add/modify/release sidelink carrier, to (re-)configure NR sidelink measurement and reporting, to (re-)configure sidelink CSI reference signal resources, to (re)configure CSI reporting latency bound, to (re)configure sidelink DRX, to (re-)configure the latency bound of SL Inter-UE coordination report, and to indicate the SFN-DFN offset. The UE may initiate the sidelink RRC reconfiguration procedure and perform the operation in clause 5.8.9.1.2 on the corresponding PC5-RRC connection in following cases: - the release of sidelink DRBs associated with the peer UE, or L2 U2U Relay UE and peer L2 U2U Remote UE in case of L2 U2U Relay operation, as specified in clause 5.8.9.1a.1; - the establishment of sidelink DRBs associated with the peer UE, or L2 U2U Relay UE and peer L2 U2U Remote UE in case of L2 U2U Relay operation, as specified in clause 5.8.9.1a.2; - the modification for the parameters included in SLRB-Config of sidelink DRBs associated with the peer UE, as specified in clause 5.8.9.1a.2; - the release of additional sidelink RLC bearer associated with the peer UE, as specified in clause 5.8.9.1a.5; - the establishment of additional sidelink RLC bearer associated with the peer UE, as specified in clause 5.8.9.1a.6; - the modification for the parameters included in SL-RLC-BearerConfig of additional sidelink RLC bearer associated with the peer UE, as specified in clause 5.8.9.1a.6; - the release of PC5 Relay RLC channels for L2 U2N/U2U Relay UE and Remote UE, as specified in clause 5.8.9.7.1; - the establishment of PC5 Relay RLC channels for L2 U2N/U2U Relay UE and Remote UE, as specified in clause 5.8.9.7.2; - the modification for the parameters included in SL-RLC-ChannelConfigPC5 of PC5 Relay RLC channels for L2 U2N/U2U Relay UE and Remote UE, as specified in clause 5.8.9.7.2; - the release of sidelink carrier associated with the peer UE, as specified in clause 5.8.9.1b.1; - the addition of sidelink carrier associated with the peer UE, as specified in clause 5.8.9.1b.2; - the modification of sidelink carrier associated with the peer UE, as specified in clause 5.8.9.1b.2; - the (re-)configuration of the peer UE to perform NR sidelink measurement and report. - the (re-)configuration of the sidelink CSI reference signal resources and CSI reporting latency bound; - the (re-)configuration of the peer UE to perform sidelink DRX; - the (re-)configuration of the latency bound of SL Inter-UE coordination report; - the (re-)configuration of the local UE ID for L2 U2U Remote UEs by L2 U2U Relay UE. - the response to the request in a RemoteUEInformationSidelink message for the SFN-DFN offset from the L2 U2N Remote UE; - the change in the value of the SFN-DFN offset at the L2 U2N Relay UE. NOTE: It is up to L2 U2N Relay UE implementation to determine when the SFN-DFN offset has changed in value to a degree requiring an update to be sent to the L2 U2N Remote UE. In RRC_CONNECTED, the UE applies the NR sidelink communications parameters provided in RRCReconfiguration (if any). In RRC_IDLE or RRC_INACTIVE, the UE applies the NR sidelink communications parameters provided in system information (if any). For other cases, UEs apply the NR sidelink communications parameters provided in SidelinkPreconfigNR (if any). When UE performs state transition between above three cases, the UE applies the NR sidelink communications parameters provided in the new state, after acquisition of the new configurations. Before acquisition of the new configurations, UE continues applying the NR sidelink communications parameters provided in the old state.

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

5.8.9.1

5.44.3.4 Non-3GPP delay budget between PINE and PEGC

For PIN indirect communication and PIN-DN communication via PEGC and 5GC, non-3GPP delay is the delay between the PEGC and the PINE. 5GC may need to be aware of the non-3GPP delay and compensate for this delay in 5GS. The compensation is achieved by adjusting the dynamic CN PDB for the 3GPP network by the non-3GPP delay (i.e. the network determined original PDB value is unchanged, but it needs to cover non-3GPP delay, besides the AN PDB and CN PDB). If the PEGC supports providing of the non-3GPP delay budget for a specific QoS flow of the PIN traffic, the PEGC may provide a non-3GPP delay budget to SMF by using the UE requested PDU Session Modification procedure. Based on the (DNN, S-NSSAI) combination of the PDU Session, the SMF may, according to operator policy and implementation, consider the non-3GPP delay budget when signalling the dynamic CN PDB to NG-RAN. The dynamic CN PDB signalled to the NG-RAN ismay be calculated as the sum of the value of dynamic CN PDB for the related GBR QoS flow and the requested non-3GPP delay budge. If the dynamic CN PDB changes in the SMF (e.g., when an I-UPF is inserted by the SMF), based on the (DNN, S-NSSAI) combination of the PDU Session, the SMF may apply the non-3GPP delay budget again before signalling the dynamic CN PDB to NG-RAN. The non-3GPP delay budget does not impact the QoS flow binding in SMF. NOTE 1: For deployments that support a PEGC to request a non-3GPP delay budget it is assumed that RAN is locally configured to give precedence to the CN PDB value received via N2 signalling as specified in clause 5.7.3.4. It is assumed that the PEGC will limit the frequency of triggering the UE-initiated PDU Session Modification request to provide the non-3GPP delay budget to the network to avoid unnecessary signalling. NOTE 2: It is up to CT WG1 to discuss to potentially introduce a timer to limit how often a PEGC is allowed to request a delay budget.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.44.3.4

9.3.25 Start DTMF Acknowledge

This message is sent by the network to the mobile station to indicate the successful initiation of the action requested by the START DTMF message (conversion of the digit contained in this message into a DTMF tone). See table 9.72/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Message type: START DTMF ACKNOWLEDGE Significance: local Direction: network to mobile station Table 9.72/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : START DTMF ACKNOWLEDGE message content

3GPP TS 24.008

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

CT WG1

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

9.3.25

4.4.3.2 Serving GW

The Serving GW is the gateway which terminates the user plane interface towards E-UTRAN (except when user data is transported using the Control Plane CIoT EPS Optimisation). For each UE associated with the EPS, at a given point of time, there is a single Serving GW. The functions of the Serving GW, for both the GTP-based and the PMIP-based S5/S8, include: - the local Mobility Anchor point for inter-eNodeB handover (except when user data is transported using the Control Plane CIoT EPS Optimisation); - sending of one or more "end marker" to the source eNodeB, source SGSN or source RNC immediately after the Serving GW switches the path during inter-eNodeB and inter-RAT handover, especially to assist the reordering function in eNodeB. - Mobility anchoring for inter-3GPP mobility (terminating S4 and relaying the traffic between 2G/3G system and PDN GW); - ECM-IDLE mode downlink packet buffering and initiation of network triggered service request procedure and optionally Paging Policy Differentiation; - Lawful Interception; - Packet routing and forwarding; - Transport level packet marking in the uplink and the downlink, e.g. setting the DiffServ Code Point, based on the QCI, and optionally the ARP priority level, of the associated EPS bearer; - Accounting for inter-operator charging. For GTP-based S5/S8, the Serving GW generates accounting data per UE and bearer; - Interfacing OFCS according to charging principles and through reference points specified in TS 32.240[ Telecommunication management; Charging management; Charging architecture and principles ] [51]; - Forwarding of "end marker" to the source eNodeB, source SGSN or source RNC when the "end marker" is received from PDN GW and the Serving GW has downlink user plane established. Upon reception of "end marker", the Serving GW shall not send Downlink Data Notification. Additional Serving GW functions for the PMIP-based S5/S8 are captured in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [2]. Connectivity to a GGSN is not supported.

3GPP TS 23.401

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

SA WG2

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

4.4.3.2

4.12.4.3 CN-initiated selective deactivation of UP connection of an existing PDU Session associated with Untrusted non-3GPP Access

The procedure described in clause 4.3.7 (CN-initiated selective deactivation of UP connection of an existing PDU Session) is used for CN-initiated selective deactivation of UP connection for an established PDU Session associated with non-3GPP Access of a UE in CM-CONNECTED state, with the following exceptions: - The NG-RAN corresponds to an N3IWF. - The user plane between the UE and N3IWF, i.e. Child SA(s) for the PDU Session, is released not with RRC signalling but with IKEv2 signalling, as specified in clause 4.12.7.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.12.4.3

6.2.3.2 Key identification

The key KAMF shall be identified by the key set identifier ngKSI. ngKSI may be either of type native or of type mapped. An ngKSI shall be stored in the UE and the AMF together with KAMF and the temporary identifier 5G-GUTI, if available. NOTE 1: The 5G-GUTI points to the AMF where the KAMF is stored. A native ngKSI is associated with the KSEAF and KAMF derived during primary authentication. It is allocated by the SEAF and sent with the authentication request message to the UE where it is stored together with the KAMF. The purpose of the ngKSI is to make it possible for the UE and the AMF to identify a native security context without invoking the authentication procedure. This is used to allow re-use of the native security context during subsequent connection set-ups. A mapped ngKSI is associated with the KAMF derived from EPS keys during interworking, cf. clause 8 of the present document. It is generated in both the UE and the AMF respectively when deriving the mapped KAMF when moving from EPS to 5GS. The mapped ngKSI is stored together with the mapped KAMF. The purpose of the mapped ngKSI is to make it possible for the UE and the AMF to indicate the use of the mapped KAMF in interworking procedures (for details cf. clause 8). The format of ngKSI shall allow a recipient of such a parameter to distinguish whether the parameter is of type native or of type mapped. The format shall contain a type field and a value field. The type field indicates the type of the key set. The value field consists of three bits where seven values, excluding the value '111', are used to identify the key set. The value '111' is reserved to be used by the UE to indicate that a valid KAMF is not available for use. The format of ngKSI is described in [35] KNASenc and KNASint in the key hierarchy specified in clause 6.2.1, which are derived from KAMF, can be uniquely identified by ngKSI together with those parameters from the set {algorithm distinguisher, algorithm identifier}, which are used to derive these keys from KAMF. The KN3IWF can be uniquely determined by ngKSI together with the uplink NAS COUNT are used to derive it according to clause A.9. The initial KgNB can be uniquely determined by ngKSI, together with the uplink NAS COUNT are used to derive it according to clause A.9. The intermediate key NH as defined in clause 6.9.2.1.1 can be uniquely determined by ngKSI, together with the initial KgNB derived from the current 5G NAS security context for use during the ongoing CM-CONNECTED state and a counter counting how many NH-derivations have already been performed from this initial KgNB according to clause A.10. The next hop chaining counter, NCC, represents the 3 least significant bits of this counter. Intermediate key KNG-RAN*, as well as non-initial KgNB, defined in clause 6.9.2.1.1 can be uniquely identified by ngKSI together with those parameters from the set {KgNB or NH, sequence of PCIs and ARFCN-DLs}, which are used to derive these keys from KgNB or NH. KRRCint, KRRCenc, KUPint, and KUPenc in the key hierarchy specified in clause 6.2.1 can be uniquely identified by ngKSI together with those parameters from the set {algorithm distinguisher, algorithm identifier}, which are used to derive these keys from KgNB. NOTE 2: In addition to 5G security contexts, the UE may also cache EPS security contexts. These EPS security contexts are identified by the eKSI, as defined in TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [10].

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

6.2.3.2

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

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

3GPP TS 36.101

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

RAN4

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

9.1.1.4.1

4.3.2.2 Xn Control Plane

The Xn control plane interface (Xn-C) is defined between two NG-RAN nodes. The control plane protocol stack of the Xn interface is shown on Figure 4.3.2.2-1. The transport network layer is built on SCTP on top of IP. The application layer signalling protocol is referred to as XnAP (Xn Application Protocol). The SCTP layer provides the guaranteed delivery of application layer messages. In the transport IP layer point-to-point transmission is used to deliver the signalling PDUs. Figure 4.3.2.2-1: Xn-C Protocol Stack The Xn-C interface supports the following functions: - Xn interface management; - UE mobility management, including context transfer and RAN paging; - Dual connectivity. Further details of Xn-C can be found in TS 38.420[ NG-RAN; Xn general aspects and principles ] [17].

3GPP TS 38.300

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

RAN2

3GPP Series : 38 , Radio technology beyond LTE

4.3.2.2

6.8B.2 Scrambling

Scrambling shall be perfomed according to Clause 6.8A.2 with EPDCCH replaced by MPDCCH except that the same scrambling sequence is applied per subframe to MPDCCH for a given block of subframes and is the MPDCCH set number. For an MPDCCH associated with a 2+4 PRB set as defined in [4], is used to generate the scrambling sequence for mapping to REs in 6 PRBs as well as 2 PRBs and 4 PRBs. The subframe number of the first subframe in each block of consecutive subframes, denoted as , satisfies . For the block of subframes, the scrambling sequence generator shall be initialised with where and is the absolute subframe number of the first downlink subframe intended for the MPDCCH. The MPDCCH transmission spans consecutive subframes, including subframes that are not BL/CE DL subframes where the MPDCCH transmission is postponed. For BL/CE UEs, - if the MPDCCH transmission is associated with P-RNTI or SC-RNTI: - for frame structure type 1 and for frame structure type 2 - otherwise - for UEs assuming CEModeA (according to the definition in Clause 12 of [4]) or configured with CEModeA: - for frame structure type 1 and for frame structure type 2 for UEs assuming CEModeB (according to the definition in Clause 12 of [4]) or configured with CEModeB.

3GPP TS 36.211

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

RAN1

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

6.8B.2

5.5.2.2.2 Mapping to physical resources

The sequence shall be multiplied with the amplitude scaling factor and mapped in sequence starting with to resource elements on antenna port . The mapping shall be in increasing order of first, then and finally the slot number. The set of values for and the relation between the index and the antenna port number shall be identical to the values used for the corresponding PUCCH transmission. The values of the symbol index in a slot are given by Table 5.5.2.2.2-1. Table 5.5.2.2.2-1: Demodulation reference signal location for different PUCCH formats. For BL/CE UEs, if uplink resource reservation is enabled for the UE as specified in [9], then in case of PUCCH transmission with associated with C-RNTI or SPS C-RNTI using UE-specific MPDCCH search space including PUCCH transmission without a corresponding MPDCCH, - In a subframe that is fully reserved as defined in clause 8.0 in [4], the demodulation reference signal transmission is postponed until the next BL/CE uplink subframe that is not fully reserved. - In a subframe that is partially reserved, the demodulation reference signal transmission in a SC-FDMA symbol that is reserved is dropped.

3GPP TS 36.211

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

RAN1

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

5.5.2.2.2

4.4.8 Architecture to enable Time Sensitive Communication, Time Synchronization and Deterministic Networking 4.4.8.1 General

The 5G System can be extended to support the following: a) Integration of 5GS into a TSN data network (DN): Integration as a bridge in an IEEE 802.1 Time Sensitive Networking (TSN). The 5GS bridge supports the Time sensitive communication as defined in IEEE 802.1 Time Sensitive Networking (TSN) standards. The architecture is described in clause 4.4.8.2. This Release supports of the specification, integration of the 5G System with IEEE 802.1 TSN networks that apply the fully centralized configuration model as defined in IEEE Std 802.1Q [98]. IEEE TSN is a set of standards to define mechanisms for the time-sensitive (i.e. deterministic) transmission of data over Ethernet networks. b) Enablers for AF requested support of Time Synchronization and/or some aspects of Time Sensitive Communication. The architecture is described in clause 4.4.8.3. c) Support for TSN enabled transport network (TN): Enablers for interworking with TSN network deployed in the transport network. This option can be used simultaneously with either option a) or b). The architecture is described in clause 5.28a. The interworking is applicable when the transport network deploys the fully centralized configuration model as defined in IEEE Std 802.1Q [98]. In this scenario, a TSN TN is deployed to realize the N3 interface between (R)AN and UPF. From the perspective of the TSN TN, (R)AN and UPF act as End Stations of the TSN TN. d) Integration as a router in a Deterministic Network as defined in IETF RFC 8655 [150]. The architecture is described in clause 4.4.8.4.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

4.4.8

4.3.2 PDU Session Establishment 4.3.2.1 General

A PDU Session establishment may correspond to: - a UE initiated PDU Session Establishment procedure. - a UE initiated PDU Session handover between 3GPP and non-3GPP. - a UE initiated PDU Session handover from EPS to 5GS. - a Network triggered PDU Session Establishment procedure. In this case the network sends the device trigger message to application(s) on the UE side. The payload included in Device Trigger Request message contains information on which application on the UE side is expected to trigger the PDU Session establishment request. Based on that information, the application(s) on the UE side trigger the PDU Session Establishment procedure. For more detail refer to clause 4.13.2. If the UE is simultaneously registered to a non-3GPP access via a N3IWF/TNGF/W-AGF located in a PLMN different from the PLMN of the 3GPP access, the functional entities in the following procedures are located in the PLMN of the access used to exchange NAS with the UE for the PDU Session. As specified in clause 5.6.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], a PDU Session may be associated either (a) with a single access type at a given time, i.e. either 3GPP access or non-3GPP access, or (b) simultaneously with multiple access types, i.e. one 3GPP access and one non-3GPP access. A PDU Session associated with multiple access types is referred to as Multi Access-PDU (MA PDU) Session and it may be requested by ATSSS-capable UEs. The following clause 4.3.2.2 specifies the procedures for establishing PDU Sessions associated with a single access type at a given time. The particular procedures associated with MA PDU Sessions are specified as part of the ATSSS procedures in clause 4.22.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.3.2

5.4.1.2.3C Procedures related to EAP methods used for primary authentication of an AUN3 device

5.4.1.2.3C.1 General This subclause applies when an EAP method is used for primary authentication of an AUN3 device, when a 5G-RG supports acting on behalf of the AUN3 device, the AMF supports serving the 5G-RG acting on behalf of the AUN3 device and the AUSF supports authentication of the AUN3 device. EAP-AKA' and EAP-TLS are examples of such EAP method. The AUSF supporting authentication of the AUN3 device shall support acting as EAP server of at least one such EAP method as specified in annex Z of 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. The 5G-RG acting on behalf of the AUN3 device provides to the AUN3 device an EAP-request message, an EAP-success message or an EAP-failure message received from the network according to subclause 5.4.1.2.1 and sends to the network according to subclause 5.4.1.2.1 an EAP-response provided by the AUN3 device. Details of communication between the AUN3 device and the 5G-RG acting on behalf of the AUN3 device are out of scope of this specification. When initiating an EAP based primary authentication and key agreement procedure using such EAP method, the network shall select an ngKSI value. The network shall send the selected ngKSI value to the 5G-RG acting on behalf of the AUN3 device along with each EAP message. The network shall send the ABBA value as described in subclause 9.11.3.10 to the 5G-RG acting on behalf of the AUN3 device along with the EAP-request message and EAP-success message. The 5G-RG acting on behalf of the AUN3 device shall not forward the ngKSI value or the ABBA value to the AUN3 device. NOTE 1: The network provides the ngKSI value and the ABBA value since the ngKSI IE and the ABBA IE are mandatory IEs in AUTHENTICATION REQUEST message. The 5G-RG acting on behalf of the AUN3 device does not use the ngKSI value or the ABBA value provided by the network. If the 5G-RG acting on behalf of the AUN3 device is informed by AUN3 about failure to authenticate the network, the 5G-RG acting on behalf of the AUN3 device shall start timer T3520 when the AUTHENTICATION RESPONSE message containing the EAP-response message is sent. Furthermore, the 5G-RG acting on behalf of the AUN3 device shall stop any of the retransmission timers that are running (e.g. T3510, T3517 or T3521). Upon receiving an AUTHENTICATION REQUEST message with the EAP message IE containing an EAP-request message from the network, the 5G-RG acting on behalf of the AUN3 device shall stop timer T3520, if running, and then provides the EAP-request message to the AUN3 device as normally. If the network fails to authenticate the AUN3 device, the network handling depends upon the type of identity used by the 5G-RG acting on behalf of the AUN3 device in the initial NAS message, that is: a) if the 5G-GUTI was used; or b) if the SUCI was used. If the 5G-GUTI was used, the network should transport the EAP-failure message in the AUTHENTICATION RESULT message as specified in the EAP result message transport procedure, initiate an identification procedure to retrieve SUCI from the 5G-RG acting on behalf of the AUN3 device and restart the EAP based primary authentication and key agreement procedure with the received SUCI. If the SUCI was used for identification in the initial NAS message or in a restarted EAP based primary authentication and key agreement procedure, or the network decides not to initiate the identification procedure to retrieve SUCI from the 5G-RG acting on behalf of the AUN3 device after an unsuccessful EAP based primary authentication and key agreement procedure, the network should transport the EAP-failure message in an AUTHENTICATION REJECT message as specified in the EAP result message transport procedure. If the EAP-failure message is received in an AUTHENTICATION REJECT message, the 5G-RG acting on behalf of the AUN3 device shall start timer T3247 with a random value uniformly drawn from the range between 30 minutes and 60 minutes, if the timer is not running (see subclause 5.3.20). Additionally, the 5G-RG acting on behalf of the AUN3 device shall: a) if the counter for "USIM considered invalid for 5GS services over non-3GPP access" events has a value less than a 5G-RG implementation-specific maximum value, proceed as specified in list item 1)-b) of subclause 5.3.20.2 for the case that the 5GMM cause value received is #3; or b) otherwise, set the update status to 5U3 ROAMING NOT ALLOWED, delete the stored 5G-GUTI, TAI list, last visited registered TAI and ngKSI. The USIM shall be considered invalid for 5GS services via non-3GPP access until switching off or the UICC containing the USIM is removed. If the AUTHENTICATION REJECT message is received by the 5G-RG acting on behalf of the AUN3 device, the 5G-RG acting on behalf of the AUN3 device shall abort any 5GMM signalling procedure, stop any of the timers T3510, T3517, T3519 or T3521 (if they were running), enter state 5GMM-DEREGISTERED and delete any stored SUCI. Upon receiving an EAP-success message from the network, the 5G-RG acting on behalf of the AUN3 device shall consider the procedure complete. The network shall provide: 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; to the 5G-RG along with the EAP-success message as specified in subclauses 5.4.1.2.5.2 and 5.4.2.2. The 5G-RG acting on behalf of the AUN3 device shall derive the Pairwise master key from the Master session key or the KWAGF key as specified in subclause 7B.7 of 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. The 5G-RG acting on behalf of the AUN3 device provides the EAP-success message to the AUN3 device. NOTE 2: 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]. Upon receiving an EAP-failure message from the network, the 5G-RG acting on behalf of the AUN3 device shall consider the procedure complete.

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.1.2.3C

4.4.6.7 DL scheduled IP throughput distribution

a) This measurement provides the distribution of samples with DL UE IP throughput in different throughput ranges during one measurement period. This measurement is a useful measure of the statistics information to distinguish the scenarios that when some UEs experience is not good in downlink. For an eNodeB serving one or more RNs, packets transmitted between the E-UTRAN and RNs are excluded, i.e., only packets transmitted between the eNodeB (or RN) and UEs are counted. The measurement is also applicable to RN. b) CC c) Each measurement 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.11.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 DL UE IP throughput in the range represented by that bin. e) DRB.IPThrDlDist. BinX which indicates the distribution of DL IP Throughput. 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.6.7

5.10.1 Description

The UAS has been broadly used for providing remote inspection services, e.g. inspection of buildings, assents, properties, power line infrastructure, forest, agricultural fields, or disaster scenes, etc. Such services would require a longer flying distance and reliable connection between the UAV and the UAV controller. Therefore, to enable UAS based remote inspection service using 3GPP connectivity, the 3GPP network shall be able to assist UAS operation with the following characteristics: - The 3GPP network shall be able to support low latency transmission for delivering commands sent by the UAV controller and response message sent by the UAV controller and UAV, respectively. - Bi-directional high throughput from the UAV to the UAV controller via 3GPP network, e.g. to send real-time video. Also for the UAS, the UAV and UAV controller needs to support - network assisted UAS discovery to be identified and operate as a UAS - 3GPP UE capabilities When a UAS has been identified and granted permission for operation after successful UAS discovery, the MNO provides UAS services such that the UAV operator can use the UAV controller to fly the UAV via the 3GPP network. The 3GPP network needs to able to provide low latency, and high reliability connection for transporting UAV commands/response between the UAV controller and the UAV. Depending on the UE capability and use cases, bi-directional high throughput may be needed for the data session to allow the UAV for providing real-time remote video to the UAV controller. The MNO is responsible for transporting and potentially adding additional data to the command of the UAV controller to operate the UAV. If the UAS is detected by the MNO/UTM for some misbehaviors, the MNO/UTM can take over the UAV controller and send the UAV command directly to fly the UAV. Figure 5.10.1-1: Network assisted UAS Operation (No direct communication between the UAV controller and the UAV)

3GPP TS 22.825

Study on Remote Identification of Unmanned Aerial Systems (UAS)

SA WG1

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

5.10.1

7.7.7 Invalid Length Information Element

An information element has invalid length when the actual length of the IE is different from the value of the Length field in the IE header. Here, the actual length of the IE means the length of the content field of the received IE. If a GTP message contains more than one information elements and one or more of them have invalid length, the receiving GTP entity can detect which of the IEs have invalid length only in the following cases: - If the Length value in the IE header is greater than the overall length of the message; - If the invalid length IE is the last one in the message. Apart from Echo Request message, if a receiving GTP entity detects information element with invalid length in a Request message, it shall send an appropriate error response with Cause IE value set to "Invalid length" together with the type and instance of the offending IE. Other Length field handling cases are specified below: - If the received value of the Length field and the actual length of the fixed length IE are consistent, but the length is greater than that expected by the fixed number of octets, then the extra octets shall be discarded. - If the received value of the Length field and the actual length of the fixed length IE are consistent, but the length is less than that expected by the fixed number of octets, this shall be considered an error, IE shall be discarded and if the IE was received as a Mandatory IE or a verifiable Conditional IE in a Request message, an appropriate error response with Cause IE value set to "Invalid length" together with the type and instance of the offending IE shall be returned to the sender. - If the received value of the Length field and the actual length of the extendable length IE are consistent, but the length is greater than that expected by the fixed number of octets preceding the extended field(s), then the extra unknown octets shall be discarded. - If the received value of the Length field and the actual length of the extendable length IE are consistent, but the length is less than the number of fixed octets defined for that IE, preceding the extended field(s), this shall be considered an error, IE shall be discarded and if the IE was received as a Mandatory IE or a verifiable Conditional IE in a Request message, an appropriate error response with Cause IE value set to "Invalid length" together with the type and instance of the offending IE shall be returned to the sender. Please refer to Table 8.1-1 for determining the number of fixed octets of an IE.

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

7.7.7

5.5.3 Potential service requirements

Editor’s note: These potential requirements require cross-checking with regulators and UAS OEMs before inclusion into normative work. The 3GPP system shall enable a UAV to broadcast the following identity data in a short-range area for collision avoidance: [UAV type, current location and time, route data, operating status]. The 3GPP system shall enable UAV to broadcast the identity information which preserves the privacy of the owner of the UAV and the UAV operator. The 3GPP system shall enable a UAV to receive local broadcast communication transport service from other UAV in short range. A UAV shall be able to use a direct UAV to UAV local broadcast communication transport service when served or not served by a 3GPP network. A UAV shall be able to use a direct UAV to UAV local broadcast communication transport service when served or not served by the same 3GPP network. The 3GPP system shall support a direct UAV to UAV local broadcast communication transport service at relative speeds of up to 320 kmph. The 3GPP system shall support a direct UAV to UAV local broadcast communication transport service at absolute speeds of up to 160 kmph. The 3GPP system shall support a direct UAV to UAV local broadcast communication transport service with variable message payloads of 50-1500 bytes, not including security-related message component(s). The 3GPP system shall support a direct UAV to UAV local broadcast communication transport service which can maintain a separation distance between two UAVs of greater than 50 m. The 3GPP system shall support a direct UAV to UAV local broadcast communication transport service which supports a range of up to 600 m The 3GPP system shall support a direct UAV to UAV local broadcast communication transport service which supports a range sufficient to give the UAVs ample time to perform manoeuvres to maintain a separation distance of 50m (e.g. 6.5 seconds). The 3GPP system shall support a direct UAV to UAV local broadcast communication transport service which can transmit messages at a frequency of at least 10 messages per second. The 3GPP system shall support a direct UAV to UAV local broadcast communication transport service which can transmit messages with an end-to-end latency of at most 100 ms.

3GPP TS 22.825

Study on Remote Identification of Unmanned Aerial Systems (UAS)

SA WG1

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

5.5.3

10.5.5.23A Additional network feature support

The purpose of the Additional network feature support information element is to indicate whether certain features are supported by the network. The Additional network feature support is a type 4 information element with a length of 3 octets. The Additional network feature support information element is coded as shown in figure 10.5.5.23A/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.5.23A/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.5.23A: Additional network feature support information element Table 10.5.5.23A: Additional network feature support 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.5.23A

F.4 5GS interworking with TSN deployed in the transport network

For 5GS to control the IEEE TSN features deployed in the transport network, the SMF/CUC interacts with the CNC in the transport network (TN CNC). Figure F.4-1: 5GS Bridge information configuration 1. The UE establishes a PDU Session as described in clause 4.3.2.2.1. 2. During the PDU Session Establishment procedure, the SMF/CUC requests the UPF to assign the N3 tunnel information via N4 Session Establishment or Modification procedure. If interworking with TSN deployed in the transport network is supported (see clause 4.4.8 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]), and the UPF supports CN-TL, the SMF/CUC includes a TL-Container to the N4 Session Establishment or Modification request including a get-request to the TL-Container, as described in clause 5.28a.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The UPF responds with a N4 Session Establishment or Modification response. If the UPF supports CN-TL, the UPF includes a TL-Container to the response. The TL-Container includes a get-response as described in clause 5.28a.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The SMF/CUC stores the information provided in the get-response. 3. During the PDU Session Establishment procedure, the SMF/CUC requests the NG-RAN to assign the N3 tunnel information by invoking the Namf_Communication_N1N2MessageTransfer request. The SMF/CUC includes a TL-Container to the N2 SM information in the request, the TL-Container contains a get-request as described in clause 5.28a.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The NG-RAN responds with a N2 SM information. If the NG-RAN supports AN-TL, the NG-RAN includes a TL-Container to the N2 SM information. The TL-Container includes a get-response as described in clause 5.28a.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The SMF/CUC stores the information provided in the get-response. 4. The AF (TSCTSF, AF, NEF or TSN AF) invokes the Npcf_PolicyAuthorization_Create/Update request. This may be due to reception of Ntsctsf_QoSandTSCAssistance_Create/Update request by the TSCTSF as described in clause 4.15.6.6 or clause 4.15.6.6.a, or due to reception of 5GS Bridge configuration by the TSN AF as described in clause F.2. The TSN AF or TSCTSF determines the TSC Assistance Container for one or more TSC streams and sends them to the PCF. 5-6.When PCF receives the request, the PCF initiates an SM Policy Association Modification procedure. The PCF notifies the corresponding SMF/CUC via Npcf_SMPolicyControl_UpdateNotify message as described in clause 4.16.5.2. The PCF updates the PCC rule to the SMF/CUC. The PCC rule includes the 5GS QoS profile along with TSC Assistance Container. SMF/CUC triggers the PDU Session Modification procedure as described in clause 4.3.3.2 to establish a QoS Flow to transfer the TSC streams. 7. During the PDU Session Modification procedure, the SMF/CUC provides the information received in PCC rules to the UPF via N4 Session Modification procedure. The SMF/CUC may instruct the UPF to assign a distinct N3 tunnel end point address for the QoS Flow as described in clause M.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The UPF responds with a N4 Session Modification response. 8. During the PDU Session Modification procedure, the SMF/CUC provides the information received in PCC rules to the NG-RAN by invoking the Namf_Communication_N1N2MessageTransfer request. The SMF also determines the TSCAI for the QoS Flow(s) and sends the TSCAI along with the QoS profile(s) to the NG-RAN. The SMF/CUC may instruct the NG-RAN to assign a distinct N3 tunnel end point address for the QoS Flow as described in clause M.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The NG-RAN responds with a N2 SM information. 9. The SMF/CUC determines the merged stream requirements in the TSN UNI towards the TN CNC as described in Annex M of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The TN CNC uses the merged stream requirements as input to select respective path(s) and calculate schedules in TN. 10. Based on the results, the TN CNC provides a Status group that contains the merged end station communication-configuration back to the SMF/CUC. 11. [Conditional] If the response from TN CNC includes InterfaceConfiguration, the SMF/CUC triggers the PDU Session Modification procedure as described in clause 4.3.3.2 to modify the QoS Flow to transfer the TSC streams. 12. [Conditional] During the PDU Session Modification procedure, if the UPF supports CN-TL, the SMF/CUC invokes N4 Session Modification procedure and includes TL-Container(s) to the N4 Session Modification request including a set-request to the TL-Container as described in clause 5.28a.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The UPF responds with a N4 Session Modification response. If the UPF supports CN-TL, the UPF includes a TL-Container to the response. The TL-Container includes a set-response as described in clause 5.28a.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 13. [Conditional] During the PDU Session Modification procedure, if the NG-RAN supports AN-TL, the SMF/CUC invokes the Namf_Communication_N1N2MessageTransfer request. The SMF/CUC includes TL-Container(s) to the N2 SM information in the request, the TL-Container contains a set-request as described in clause 5.28a.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The SMF/CUC may also update the TSCAI in the NG-RAN for the BAT in DL direction as described in Annex M, clause M.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], if the SMF/CUC received a TimeAwareOffset or AccumulatedLatency from TN CNC for a downlink stream (i.e. for a Talker in the UPF/CN-TL) in step 7. The NG-RAN responds with a N2 SM information. If the NG-RAN supports AN-TL, the NG-RAN includes TL-Container(s) to the N2 SM information. The TL-Container includes a set-response as described in clause 5.28a.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. NOTE: TL-Containers and related Gate Control information as described in clause M.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] are removed during PDU Session Release or QoS Flow(s) Release.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

F.4

8.2.2.2.8 Minimum Requirement 2 Tx Antenna Port (Superposed transmission)

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

3GPP TS 36.101

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

RAN4

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

8.2.2.2.8

7.5.1 Common procedures

When on receipt of a message, - an "imperative message part" error; or - a "missing mandatory IE" error is diagnosed or when a message containing: - a syntactically incorrect mandatory IE; - an IE unknown in the message, but encoded as "comprehension required" (see 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [12]); or - an out of sequence IE encoded as "comprehension required" (see 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [12]) is received, the UE shall proceed as follows: - If the message is not one of the messages listed in clause 7.5.3, item a, b, c, or d, the UE shall return a status message (EMM STATUS or ESM STATUS depending on the PD) with cause #96 "invalid mandatory information"; and the network shall proceed as follows: - If the message is not one of the messages listed in clause 7.5.3, item e, f, g or h, the network shall either: - try to treat the message (the exact further actions are implementation dependent); or - ignore the message except that it should return a status message (EMM STATUS or ESM STATUS depending on the PD) with cause #96 "invalid mandatory information".

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

7.5.1

8.120 Monitoring Event Information

The Monitoring Event Information contains the monitoring event parameters that are necessary to transfer over the S3/S16/S10 interface. The Monitoring Event Information is coded as depicted in Figure 8.120-1. Figure 8.120-1: Monitoring Event Information The SCEF Reference ID, the SCEF ID, SCEF Reference ID Ext shall be encoded as specified in clause 8.4.4, 8.4.5 and 8.4.82 of 3GPP TS 29.336[ Home Subscriber Server (HSS) diameter interfaces for interworking with packet data networks and applications ] [69]. The SCEF ID Length indicates the length of the SCEF ID in octets. When the SRIE (SCEF Reference Id Extension) is set to "1", the 64-bit SCEF Reference ID Ext field shall be present to contain the 64-bit SCEF Reference ID Ext for the event. In this case, the receiver shall ignore the SCEF Reference ID received in octets 5 to 8. NOTE 1: The sender can set any value for SCEF Reference ID if the SCEF Reference ID Ext field is included. The source MME/SGSN shall set the NSUR (Notify SCEF when UE becomes Reachable) flag to "1" to indicate that the target MME/SGSN shall send a notification to SCEF when the UE becomes reachable, if a monitoring event, with the Monitoring-Type is set to "AVAILABILITY_AFTER_DDN_FAILURE", or "UE_REACHABILITY_AND_IDLE_STATUS_INDICATION" or "AVAILABILITY_AFTER_DDN_FAILURE_AND_IDLE_STATUS_INDICATION" or "UE_REACHABILITY". The source MME/SGSN shall set the NSUI (Notify SCEF when UE becomes Idle) flag to "1" to indicate that the target MME/SGSN shall send a notification to SCEF when the UE gets into idle mode, if a monitoring event, with the Monitoring-Type is set to "UE_REACHABILITY_AND_IDLE_STATUS_INDICATION" or "AVAILABILITY_AFTER_DDN_FAILURE_AND_IDLE_STATUS_INDICATION". The source MME/SGSN shall set the NSCF (Notify SCEF about Communication Failure events) flag to "1" to indicate that the target MME/SGSN shall send a notification to the SCEF if it detects a communication failure event. NOTE 2: This enables the target MME/SGSN to notify the SCEF about communication failure events that can happen with the target RAN (e.g. radio link failure during the handover execution) before the target MME/SGSN interacts with the HSS. The Remaining Number of Reports indicates the number of reports which are outstanding to be sent to the SCEF. It shall be encoded as specified in clause 8.4.8 of 3GPP TS 29.336[ Home Subscriber Server (HSS) diameter interfaces for interworking with packet data networks and applications ] [69].

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

5.2.16.3.4 Nnssf_NSSAIAvailability_Subscribe service operation

Service operation name: Nnssf_NSSAIAvailability_Subscribe Description: This service operation enables a NF Service Consumer (e.g. AMF) to subscribe to a notification of any changes in status of the NSSAI availability information (e.g. S-NSSAI validity time, S-NSSAIs and optionally NSI IDs available per TA and the restricted S-NSSAI(s) and optionally NSI IDs per PLMN in that TA in the serving PLMN of the UE) upon this is updated by another AMF. This service also enables the NF Service Consumer (e.g. AMF or NSSF in the VPLMN) to subscribe to a notification of Network Slice Replacement and Network Slice Instance Replacement. Inputs, Required: Callback URI of the NF Service Consumer: Inputs, Conditional Required: If this service operation is invoked to subscribe for changes in status of the NSSAI availability information, then the following inputs are required: - list of TAIs supported by the NF service consumer, event to be subscribed. If this service operation is invoked to subscribe for changes in status of the NSSAI validity time information, then the following inputs are required: - The S-NSSAIs, event to be subscribed. If this service operation is invoked to subscribe to a notification for Network Slice Replacement, then the following inputs are required: - for the S-NSSAI of the serving PLMN: set of S-NSSAIs served by the NF Service Consumer that may be replaced, NF type of the NF Service Consumer (e.g. AMF), Requester ID, event to be subscribed. - for HPLMN S-NSSAI: S-NSSAIs for the HPLMN, NF type of the NF Service Consumer (e.g. AMF or NSSF), Requester ID and PLMN ID, event to be subscribed. If this service operation is invoked to subscribe to a notification when the Network Slice instance is congested or no longer available, then the following inputs are required: - The S-NSSAIs, NSI IDs, event to be subscribed. Inputs, Optional: Expiry time. Outputs, Required: Subscription Correlation ID. Outputs, Conditional Required: If this service operation is invoked to subscribe for changes in status of the NSSAI availability information, then the following outputs are required: - Expiry time (if present in the request, may be included in the response based on operator's policy and taking into account the expiry time present in the request (i.e. should be less than or equal to that value); if not present in the request, may be included in the response based on operator's policy. Whatever the case, if not included in the response, this means that the subscription is valid without an expiry time). Outputs, Optional: If this service operation is invoked to subscribe for changes in status of the NSSAI availability information, then the following outputs are optional: - A list of TAIs and for each TAI, the S-NSSAIs and optionally NSI IDs supported by the AMF and 5G-AN and authorized by the NSSF for the TAI and a list of S-NSSAIs and optionally NSI IDs restricted per PLMN for the TAI. The NSSS indicates to the AMF that the S-NSSAI(s) are not available in the corresponding TAIs.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

5.2.16.3.4

5.5.5 Measurement reporting 5.5.5.1 General

Figure 5.5.5.1-1: Measurement reporting The purpose of this procedure is to transfer measurement results from the UE to the network. The UE shall initiate this procedure only after successful AS security activation. For the measId for which the measurement reporting procedure was triggered, the UE shall set the measResults within the MeasurementReport message as follows: 1> set the measId to the measurement identity that triggered the measurement reporting; 1> for each serving cell configured with servingCellMO: 2> if the reportConfig associated with the measId that triggered the measurement reporting includes rsType: 3> if the serving cell measurements based on the rsType included in the reportConfig that triggered the measurement report are available: 4> set the measResultServingCell within measResultServingMOList to include RSRP, RSRQ and the available SINR of the serving cell, derived based on the rsType included in the reportConfig that triggered the measurement report; 2> else: 3> if SSB based serving cell measurements are available: 4> set the measResultServingCell within measResultServingMOList to include RSRP, RSRQ and the available SINR of the serving cell, derived based on SSB; 3> else if CSI-RS based serving cell measurements are available: 4> set the measResultServingCell within measResultServingMOList to include RSRP, RSRQ and the available SINR of the serving cell, derived based on CSI-RS; 1> set the servCellId within measResultServingMOList to include each NR serving cell that is configured with servingCellMO, if any; 1> if the reportConfig associated with the measId that triggered the measurement reporting includes reportQuantityRS-Indexes and maxNrofRS-IndexesToReport: 2> for each serving cell configured with servingCellMO, include beam measurement information according to the associated reportConfig as described in 5.5.5.2; 1> if the reportConfig associated with the measId that triggered the measurement reporting includes reportAddNeighMeas: 2> for each measObjectId referenced in the measIdList which is also referenced with servingCellMO, other than the measObjectId corresponding with the measId that triggered the measurement reporting: 3> if the measObjectNR indicated by the servingCellMO includes the RS resource configuration corresponding to the rsType indicated in the reportConfig: 4> set the measResultBestNeighCell within measResultServingMOList to include the physCellId and the available measurement quantities based on the reportQuantityCell and rsType indicated in reportConfig of the non-serving cell corresponding to the concerned measObjectNR with the highest measured RSRP if RSRP measurement results are available for cells corresponding to this measObjectNR, otherwise with the highest measured RSRQ if RSRQ measurement results are available for cells corresponding to this measObjectNR, otherwise with the highest measured SINR; 4> if the reportConfig associated with the measId that triggered the measurement reporting includes reportQuantityRS-Indexes and maxNrofRS-IndexesToReport: 5> for each best non-serving cell included in the measurement report: 6> include beam measurement information according to the associated reportConfig as described in 5.5.5.2; 1> if the reportConfig associated with the measId that triggered the measurement reporting is set to eventTriggered and eventID is set to eventA3, or eventA4, or eventA5, or eventB1, or eventB2, or eventA3H1, or eventA3H2, or eventA4H1, or eventA4H2, or eventA5H1, or eventA5H2: 2> if the UE is in NE-DC and the measurement configuration that triggered this measurement report is associated with the MCG: 3> set the measResultServFreqListEUTRA-SCG to include an entry for each E-UTRA SCG serving frequency with the following: 4> include carrierFreq of the E-UTRA serving frequency; 4> set the measResultServingCell to include the available measurement quantities that the UE is configured to measure by the measurement configuration associated with the SCG; 4> if reportConfig associated with the measId that triggered the measurement reporting includes reportAddNeighMeas: 5> set the measResultServFreqListEUTRA-SCG to include within measResultBestNeighCell the quantities of the best non-serving cell, based on RSRP, on the concerned serving frequency; 1> if reportConfig associated with the measId that triggered the measurement reporting is set to eventTriggered and eventID is set to eventA3, or eventA4, or eventA5, or eventA3H1, or eventA3H2, or eventA4H1, or eventA4H2, or eventA5H1, or eventA5H2: 2> if the UE is in NR-DC and the measurement configuration that triggered this measurement report is associated with the MCG: 3> set the measResultServFreqListNR-SCG to include for each NR SCG serving cell that is configured with servingCellMO, if any, the following: 4> if the reportConfig associated with the measId that triggered the measurement reporting includes rsType: 5> if the serving cell measurements based on the rsType included in the reportConfig that triggered the measurement report are available according to the measurement configuration associated with the SCG: 6> set the measResultServingCell within measResultServFreqListNR-SCG to include RSRP, RSRQ and the available SINR of the serving cell, derived based on the rsType included in the reportConfig that triggered the measurement report; 4> else: 5> if SSB based serving cell measurements are available according to the measurement configuration associated with the SCG: 6> set the measResultServingCell within measResultServFreqListNR-SCG to include RSRP, RSRQ and the available SINR of the serving cell, derived based on SSB; 5> else if CSI-RS based serving cell measurements are available according to the measurement configuration associated with the SCG: 6> set the measResultServingCell within measResultServFreqListNR-SCG to include RSRP, RSRQ and the available SINR of the serving cell, derived based on CSI-RS; 4> if results for the serving cell derived based on SSB are included: 5> include the ssbFrequency to the value indicated by ssbFrequency as included in the MeasObjectNR of the serving cell; 4> if results for the serving cell derived based on CSI-RS are included: 5> include the refFreqCSI-RS to the value indicated by refFreqCSI-RS as included in the MeasObjectNR of the serving cell; 4> if the reportConfig associated with the measId that triggered the measurement reporting includes reportQuantityRS-Indexes and maxNrofRS-IndexesToReport: 5> for each serving cell configured with servingCellMO, include beam measurement information according to the associated reportConfig as described in 5.5.5.2, where availability is considered according to the measurement configuration associated with the SCG; 4> if reportConfig associated with the measId that triggered the measurement reporting includes reportAddNeighMeas: 5> if the measObjectNR indicated by the servingCellMO includes the RS resource configuration corresponding to the rsType indicated in the reportConfig: 6> set the measResultNeighCellListNR within measResultServFreqListNR-SCG to include one entry with the physCellId and the available measurement quantities based on the reportQuantityCell and rsType indicated in reportConfig of the non-serving cell corresponding to the concerned measObjectNR with the highest measured RSRP if RSRP measurement results are available for cells corresponding to this measObjectNR, otherwise with the highest measured RSRQ if RSRQ measurement results are available for cells corresponding to this measObjectNR, otherwise with the highest measured SINR, where availability is considered according to the measurement configuration associated with the SCG; 7> if the reportConfig associated with the measId that triggered the measurement reporting includes reportQuantityRS-Indexes and maxNrofRS-IndexesToReport: 8> for each best non-serving cell included in the measurement report: 9> include beam measurement information according to the associated reportConfig as described in 5.5.5.2, where availability is considered according to the measurement configuration associated with the SCG; 1> if the measRSSI-ReportConfig is configured within the corresponding reportConfig for this measId: 2> set the rssi-Result to the linear average of sample value(s) provided by lower layers in the reportInterval; 2> set the channelOccupancy to the rounded percentage of sample values which are beyond the channelOccupancyThreshold within all the sample values in the reportInterval; 1> if the UE is acting as L2 U2N Remote UE: 2> set the sl-MeasResultServingRelay in accordance with the following: 3> set the cellIdentity to include the cellAccessRelatedInfo contained in the discovery message received from the serving L2 U2N Relay UE; 3> set the sl-RelayUE-Identity to include the Source L2 ID of the serving L2 U2N Relay; 3> if the measurement of serving L2 U2N Relay UE is based on SL-RSRP: 4> set the sl-MeasResult to include the SL-RSRP of the serving L2 U2N Relay UE; 4> set the sl-MeasQuantity to SL-RSRP, if supported by the UE; 3> else: 4> set the sl-MeasResult to include the SD-RSRP of the serving L2 U2N Relay UE; 4> set the sl-MeasQuantity to SD-RSRP, if supported by the UE; NOTE 1: In case of no data transmission from L2 U2N Relay UE to L2 U2N Remote UE, it is left to UE implementation whether to use SL-RSRP or SD-RSRP when setting the sl-MeasResultServingRelay of the serving L2 U2N Relay UE. 1> if there is at least one applicable neighbouring cell or candidate L2 U2N Relay UE to report: 2> if the reportType is set to eventTriggered or periodical: 3> if the measurement report concerns the candidate L2 U2N Relay UE: 4> set the sl-MeasResultsCandRelay in measResultNeighCells to include the best candidate L2 U2N Relay UEs up to maxNrofRelayMeas in accordance with the following: 5> if the reportType is set to eventTriggered: 6> include the L2 U2N Relay UEs included in the relaysTriggeredList as defined within the VarMeasReportList for this measId; 5> else: 6> include the applicable L2 U2N Relay UEs for which the new measurement results became available since the last periodical reporting or since the measurement was initiated or reset; 5> for each L2 U2N Relay UE that is included in the sl-MeasResultsCandRelay: 6> set the cellIdentity to include the cellAccessRelatedInfo contained in the discovery message received from the concerned L2 U2N Relay UE; 6> set the sl-RelayUE-Identity to include the Source L2 ID of the concerned L2 U2N Relay UE; 6> set the sl-MeasResult to include the SD-RSRP of the concerned L2 U2N Relay UE; 5> for each included L2 U2N Relay UE, include the layer 3 filtered measured results in accordance with the reportConfig for this measId, ordered as follows: 6> set the sl-MeasResult to include the quantity(ies) indicated in the reportQuantityRelay within the concerned reportConfigRelay in decreasing order of the sorting quantity, determined as specified in 5.5.5.3, i.e. the best L2 U2N Relay UE is included first; 3> else: 4> set the measResultNeighCells to include the best neighbouring cells up to maxReportCells in accordance with the following: 5> if the reportType is set to eventTriggered and eventId is not set to eventD1 or eventH1 or eventH2: 6> include the cells included in the cellsTriggeredList as defined within the VarMeasReportList for this measId; 5> else: 6> include the applicable cells for which the new measurement results became available since the last periodical reporting or since the measurement was initiated or reset; 5> for each cell that is included in the measResultNeighCells, include the physCellId; 5> if the reportType is set to eventTriggered or periodical: 6> for each included cell, include the layer 3 filtered measured results in accordance with the reportConfig for this measId, ordered as follows: 7> if the measObject associated with this measId concerns NR: 8> if rsType in the associated reportConfig is set to ssb: 9> set resultsSSB-Cell within the measResult to include the SS/PBCH block based quantity(ies) indicated in the reportQuantityCell within the concerned reportConfig, in decreasing order of the sorting quantity, determined as specified in 5.5.5.3, i.e. the best cell is included first; 9> if reportQuantityRS-Indexes and maxNrofRS-IndexesToReport are configured, include beam measurement information as described in 5.5.5.2; 8> else if rsType in the associated reportConfig is set to csi-rs: 9> set resultsCSI-RS-Cell within the measResult to include the CSI-RS based quantity(ies) indicated in the reportQuantityCell within the concerned reportConfig, in decreasing order of the sorting quantity, determined as specified in 5.5.5.3, i.e. the best cell is included first; 9> if reportQuantityRS-Indexes and maxNrofRS-IndexesToReport are configured, include beam measurement information as described in 5.5.5.2; 7> if the measObject associated with this measId concerns E-UTRA: 8> set the measResult to include the quantity(ies) indicated in the reportQuantity within the concerned reportConfigInterRAT in decreasing order of the sorting quantity, determined as specified in 5.5.5.3, i.e. the best cell is included first; 7> if the measObject associated with this measId concerns UTRA-FDD and if ReportConfigInterRAT includes the reportQuantityUTRA-FDD: 8> set the measResult to include the quantity(ies) indicated in the reportQuantityUTRA-FDD within the concerned reportConfigInterRAT in decreasing order of the sorting quantity, determined as specified in 5.5.5.3, i.e. the best cell is included first; 2> else: 3> if the cell indicated by cellForWhichToReportCGI is an NR cell: 4> if plmn-IdentityInfoList of the cgi-Info for the concerned cell has been obtained: 5> include the plmn-IdentityInfoList including plmn-IdentityList, trackingAreaCode (if available), trackingAreaList (if available), ranac (if available), cellIdentity and cellReservedForOperatorUse for each entry of the plmn-IdentityInfoList; 5> include frequencyBandList if available; 5> for each PLMN-IdentityInfo in plmn-IdentityInfoList: 6> if the gNB-ID-Length is broadcast: 7> include gNB-ID-Length; 4> if nr-CGI-Reporting-NPN is supported by the UE and npn-IdentityInfoList of the cgi-Info for the concerned cell has been obtained: 5> include the npn-IdentityInfoList including npn-IdentityList, trackingAreaCode, ranac (if available), cellIdentity and cellReservedForOperatorUse for each entry of the npn-IdentityInfoList; 5> for each NPN-IdentityInfo in NPN-IdentityInfoList: 6> if the gNB-ID-Length is broadcast: 7> include gNB-ID-Length; 5> include cellReservedForOtherUse if available; 4> else if MIB indicates the SIB1 is not broadcast: 5> include the noSIB1 including the ssb-SubcarrierOffset and pdcch-ConfigSIB1 obtained from MIB of the concerned cell; 3> if the cell indicated by cellForWhichToReportCGI is an E-UTRA cell: 4> if all mandatory fields of the cgi-Info-EPC for the concerned cell have been obtained: 5> include in the cgi-Info-EPC the fields broadcasted in E-UTRA SystemInformationBlockType1 associated to EPC; 4> if the UE is E-UTRA/5GC capable and all mandatory fields of the cgi-Info-5GC for the concerned cell have been obtained: 5> include in the cgi-Info-5GC the fields broadcasted in E-UTRA SystemInformationBlockType1 associated to 5GC; 4> if the mandatory present fields of the cgi-Info for the cell indicated by the cellForWhichToReportCGI in the associated measObject have been obtained: 5> include the freqBandIndicator; 5> if the cell broadcasts the multiBandInfoList, include the multiBandInfoList; 5> if the cell broadcasts the freqBandIndicatorPriority, include the freqBandIndicatorPriority; 1> if the corresponding measObject concerns NR: 2> if the reportSFTD-Meas is set to true within the corresponding reportConfigNR for this measId: 3> set the measResultSFTD-NR in accordance with the following: 4> set sfn-OffsetResult and frameBoundaryOffsetResult to the measurement results provided by lower layers; 4> if the reportRSRP is set to true; 5> set rsrp-Result to the RSRP of the NR PSCell derived based on SSB; 2> else if the reportSFTD-NeighMeas is included within the corresponding reportConfigNR for this measId: 3> for each applicable cell which measurement results are available, include an entry in the measResultCellListSFTD-NR and set the contents as follows: 4> set physCellId to the physical cell identity of the concerned NR neighbour cell. 4> set sfn-OffsetResult and frameBoundaryOffsetResult to the measurement results provided by lower layers; 4> if the reportRSRP is set to true: 5> set rsrp-Result to the RSRP of the concerned cell derived based on SSB; 1> else if the corresponding measObject concerns E-UTRA: 2> if the reportSFTD-Meas is set to true within the corresponding reportConfigInterRAT for this measId: 3> set the measResultSFTD-EUTRA in accordance with the following: 4> set sfn-OffsetResult and frameBoundaryOffsetResult to the measurement results provided by lower layers; 4> if the reportRSRP is set to true; 5> set rsrpResult-EUTRA to the RSRP of the EUTRA PSCell; 1> if average uplink PDCP delay values are available: 2> set the ul-PDCP-DelayValueResultList to include the corresponding average uplink PDCP delay values; 1> if PDCP excess delay measurements are available: 2> set the ul-PDCP-ExcessDelayResultList to include the corresponding PDCP excess delay measurements; 1> if the includeCommonLocationInfo is configured in the corresponding reportConfig for this measId and detailed location information that has not been reported is available, set the content of commonLocationInfo of the locationInfo as follows: 2> include the locationTimestamp; 2> include the locationCoordinate, if available; 2> include the velocityEstimate, if available; 2> include the locationError, if available; 2> include the locationSource, if available; 2> if available, include the gnss-TOD-msec, 1> if the coarseLocationRequest is set to true in the corresponding reportConfig for this measId: 2> include coarseLocationInfo, if available; 1> if the includeWLAN-Meas is configured in the corresponding reportConfig for this measId, set the wlan-LocationInfo of the locationInfo in the measResults as follows: 2> if available, include the LogMeasResultWLAN, in order of decreasing RSSI for WLAN APs; 1> if the includeBT-Meas is configured in the corresponding reportConfig for this measId, set the BT-LocationInfo of the locationInfo in the measResults as follows: 2> if available, include the LogMeasResultBT, in order of decreasing RSSI for Bluetooth beacons; 1> if the includeSensor-Meas is configured in the corresponding reportConfig for this measId, set the sensor-LocationInfo of the locationInfo in the measResults as follows: 2> if available, include the sensor-MeasurementInformation; 2> if available, include the sensor-MotionInformation; 1> if the includeAltitudeUE is configured in the corresponding reportConfig for this measId: 2> set the altitudeUE to include the altitude of the UE; 1> if there is at least one applicable transmission resource pool for NR sidelink communication/discovery (for measResultsSL): 2> set the measResultsListSL to include the CBR measurement results in accordance with the following: 3> if the reportType is set to eventTriggered: 4> include the transmission resource pools included in the poolsTriggeredList as defined within the VarMeasReportList for this measId; 3> else: 4> include the applicable transmission resource pools for which the new measurement results became available since the last periodical reporting or since the measurement was initiated or reset; 3> if the corresponding measObject concerns NR sidelink communication/discovery, then for each transmission resource pool to be reported: 4> set the sl-poolReportIdentity to the identity of this transmission resource pool; 4> set the sl-CBR-ResultsNR to the CBR measurement results on PSSCH and PSCCH of this transmission resource pool provided by lower layers, if available; NOTE 1: Void. 1> if there is at least one applicable CLI measurement resource to report: 2> if the reportType is set to cli-EventTriggered or cli-Periodical: 3> set the measResultCLI to include the most interfering SRS resources or most interfering CLI-RSSI resources up to maxReportCLI in accordance with the following: 4> if the reportType is set to cli-EventTriggered: 5> if trigger quantity is set to srs-RSRP i.e. i1-Threshold is set to srs-RSRP: 6> include the SRS resource included in the cli-TriggeredList as defined within the VarMeasReportList for this measId; 5> if trigger quantity is set to cli-RSSI i.e. i1-Threshold is set to cli-RSSI: 6> include the CLI-RSSI resource included in the cli-TriggeredList as defined within the VarMeasReportList for this measId; 4> else: 5> if reportQuantityCLI is set to srs-rsrp: 6> include the applicable SRS resources for which the new measurement results became available since the last periodical reporting or since the measurement was initiated or reset; 5> else: 6> include the applicable CLI-RSSI resources for which the new measurement results became available since the last periodical reporting or since the measurement was initiated or reset; 4> for each SRS resource that is included in the measResultCLI: 5> include the srs-ResourceId; 5> set srs-RSRP-Result to include the layer 3 filtered measured results in decreasing order, i.e. the most interfering SRS resource is included first; 4> for each CLI-RSSI resource that is included in the measResultCLI: 5> include the rssi-ResourceId; 5> set cli-RSSI-Result to include the layer 3 filtered measured results in decreasing order, i.e. the most interfering CLI-RSSI resource is included first; 1> if there is at least one applicable UE Rx-Tx time difference measurement to report: 2> set measResultRxTxTimeDiff to the latest measurement result; 1> increment the numberOfReportsSent as defined within the VarMeasReportList for this measId by 1; 1> stop the periodical reporting timer, if running; 1> if the numberOfReportsSent as defined within the VarMeasReportList for this measId is less than the reportAmount as defined within the corresponding reportConfig for this measId: 2> start the periodical reporting timer with the value of reportInterval as defined within the corresponding reportConfig for this measId; 1> else: 2> if the reportType is set to periodical or cli-Periodical or rxTxPeriodical: 3> remove the entry within the VarMeasReportList for this measId; 3> remove this measId from the measIdList within VarMeasConfig; 1> if the measurement reporting was configured by a sl-ConfigDedicatedNR received within the RRCConnectionReconfiguration: 2> submit the MeasurementReport message to lower layers for transmission via SRB1, embedded in E-UTRA RRC message ULInformationTransferIRAT as specified TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10], clause 5.6.28; 1> else if the UE is in (NG)EN-DC: 2> if SRB3 is configured and the SCG is not deactivated: 3> submit the MeasurementReport message via SRB3 to lower layers for transmission, upon which the procedure ends; 2> else: 3> submit the MeasurementReport message via E-UTRA embedded in E-UTRA RRC message ULInformationTransferMRDC as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10]. 1> else if the UE is in NR-DC: 2> if the measurement configuration that triggered this measurement report is associated with the SCG: 3> if SRB3 is configured and the SCG is not deactivated: 4> submit the MeasurementReport message via SRB3 to lower layers for transmission, upon which the procedure ends; 3> else: 4> submit the MeasurementReport message via SRB1 embedded in NR RRC message ULInformationTransferMRDC as specified in 5.7.2a.3; 2> else: 3> submit the MeasurementReport message via SRB1 to lower layers for transmission, upon which the procedure ends; 1> else: 2> submit the MeasurementReport 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.5.5

8.5 F1 Startup and cells activation

This function allows to setup the F1 interface between a gNB-DU and a gNB-CU and it allows to activate the gNB-DU cells. Figure 8.5-1: F1 startup and cell activation 0. The gNB-DU and its cells are configured by OAM in the F1 pre-operational state. The gNB-DU has TNL connectivity toward the gNB-CU. 1. The gNB-DU sends an F1 SETUP REQUEST message to the gNB-CU including a list of cells that are configured and ready to be activated. For each cell supporting NPN the gNB-DU includes NPN specific information. 2. In NG-RAN, the gNB-CU ensures the connectivity toward the core network. For this reason, the gNB-CU may initiate either the NG Setup or the gNB Configuration Update procedure towards 5GC. 3. The gNB-CU sends an F1 SETUP RESPONSE message to the gNB-DU that optionally includes a list of cells to be activated. The cells in the list of cells to be activated in F1 SETUP RESPONSE message become active, while the cells not in the list are inactive. The cells that are active are Out-of-Service until the gNB-DU indicates that they are In-Service . The gNB-DU will initiate the gNB-DU Configuration Update procedure towards the gNB-CU and includes the cell(s) that are In-Service and/or the cell(s) that are Out-Of-Service. The gNB-DU may also indicate cell(s) to be deleted, in which case the gNB-CU removes the corresponding cell(s) information. 4. The gNB-CU may send a GNB CU CONFIGURATION UPDATE message to the gNB-DU that optionally includes a list of cells to be activated, e.g., in case that these cells were not activated using the F1 SETUP RESPONSE message. 5. The gNB-DU replies with a GNB CU CONFIGURATION UPDATE ACKNOWLEDGE message that optionally includes a list of cells that failed to be activated. The gNB-CU regards all Active cells as Out-Of-Service until the gNB-DU indicates that they are In-Service. 6. The gNB-CU may initiate either the Xn Setup towards a neighbour NG-RAN node or the EN-DC X2 Setup procedure towards a neighbour eNB. NOTE 1: For NG-RAN in case that the F1 SETUP RESPONSE message is not used to activate any cell, step 2 may be performed after step 3. Over the F1 interface between a gNB-CU and a gNB-DU pair, the following two Cell States are possible: - Inactive: the cell is known by both the gNB-DU and the gNB-CU. The cell shall not serve UEs; - Active: the cell is known by both the gNB-DU and the gNB-CU. The cell should try to provide services to the UEs. The gNB-CU decides whether the Cell State should be “Inactive“ or “Active“. The gNB-CU can request the gNB-DU to change the Cell State using the F1 SETUP RESPONSE, theGNB DU CONFIGURATION UPDATE ACKNOWLEDGE, or the GNB CU CONFIGURATION UPDATE messages. The gNB-DU reports to the gNB-CU the Service Status. The Service Status is the state of the radio transmission over the air. The Service Status is reported by the gNB-DU for cells for which the Cell State is “Active “. The following Service Status are defined: - In-Service: the cell is operational and able to serve UEs. - Out-Of-Service: the cell is not operational, and it is not able to serve UEs. The gNB-DU is trying to make the cell operational. The gNB-DU reports the Service Status using the GNB DU CONFIGURATION UPDATE message. NOTE 2: If gNB-DU regards that one or more cells cannot become operational, the gNB-DU deletes them and reports them using the GNB DU CONFIGURATION UPDATE message.

3GPP TS 38.401

NG-RAN; Architecture description

RAN3

3GPP Series : 38 , Radio technology beyond LTE

8.5