Datasets:

Exploration-Lab

/

MM-TelecoBench

like 0

Follow

Exploration Lab 61

5.27.1.3 Support for multiple (g)PTP domains

This clause describes support for multiple domains for gPTP and PTP and for GM clocks connected to DS-TT and NW-TT and only applies if DS-TT and NW-TT support the related functionality. PTP support and support of gPTP for GM clocks connected to DS-TT by DS-TT and NW-TT may be determined as described in clause K.2.1. Each (g)PTP domain sends its own (g)PTP messages. The (g)PTP message carries a specific PTP "domainNumber" that indicates the time domain they are referring to. The PTP port in ingress TT makes ingress timestamping (TSi) for the (g)PTP event messages of all domains and forwards the (g)PTP messages of all domains to the UPF/NW-TT that further distributes the (g)PTP messages to the egress TTs as specified in clause 5.27.1.2.2. The PTP port in the egress TT receives the original PTP GM clock timing information and the corresponding TSi via (g)PTP messages for one or more (g)PTP domains. The PTP port in the egress TT then makes egress timestamping (TSe) for the (g)PTP event messages for every (g)PTP domain. Ingress and egress time stamping are based on the 5G system clock at NW-TT and DS-TT. NOTE 1: An end-station can select PTP timing information of interest based on the "domainNumber" in the (g)PTP message. The process described in clause 5.27.1.2.2 is thus repeated for each (g)PTP domain between a DS-TT and the NW-TT it is connected to. NOTE 2: If all (g)PTP domains can be made synchronous and the synchronization can be provided by the 5G clock, the NW-TT or DS-TT(s) generates the (g)PTP event messages of all domains using 5G clock as described in clause 5.27.1.7. NOTE 3: This Release of the specification supports multiple gPTP domains as defined in IEEE Std 802.1AS [104]. If a 5GS TSN bridge supports stream gates and/or transmission gates as defined in IEEE Std 802.1Q [98], then they operate based on a single given gPTP domain.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.27.1.3

6.5.3.2 UE requested bearer resource allocation procedure initiation

In order to request the allocation of bearer resources for one traffic flow aggregate, the UE shall send a BEARER RESOURCE ALLOCATION REQUEST message to the MME, start timer T3480 and enter the state PROCEDURE TRANSACTION PENDING (see example in figure 6.5.3.2.1). The UE shall include the EPS bearer identity of the default EPS bearer associated with the requested bearer resource in the Linked EPS bearer identity IE. The UE shall set the TFT operation code in the Traffic flow aggregate IE to "Create new TFT". The packet filters in the Traffic flow aggregate IE shall include at least one packet filter applicable for the uplink direction. In the Required traffic flow QoS IE, the UE shall indicate a QCI and, if the UE also includes a GBR, the additional GBR required for the traffic flow aggregate. Figure 6.5.3.2.1: UE requested bearer resource allocation procedure For the NBIFOM procedures as defined in 3GPP TS 24.161[ Network-Based IP Flow Mobility (NBIFOM); Stage 3 ] [36], the UE may send a BEARER RESOURCE ALLOCATION REQUEST message to the MME. If the traffic flow aggregate IE is not needed in those procedures, the UE shall set: - the length indicator of the Traffic flow aggregate IE to the value 1; - the TFT operation code to "000"; - the E bit to zero; and - the number of packet filters to zero; and in the Required traffic flow QoS IE: - the length indicator to the value 1; and - the QCI to zero.

3GPP TS 24.301

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

CT WG1

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

6.5.3.2

7.7.1 Protocol Errors

A protocol error is defined as a message or an Information Element received from a peer entity with unknown type, or if it is unexpected, or if it has an erroneous content. The term silently discarded is used in the following clauses to mean that the receiving GTP entity's implementation shall discard such a message without further processing, or that the receiving GTP entity discards such an IE and continues processing the message. The conditions for the receiving GTP entity to silently discard an IE are specified in the subsequent clauses. The handling of unknown, unexpected or erroneous GTP messages and IEs shall provide for the forward compatibility of GTP. Therefore, the sending GTP entity shall be able to safely include in a message a new conditional-optional or an optional IE. Such an IE may also have a new type value. Any legacy receiving GTP entity shall, however, silently discard such an IE and continue processing the message. If a protocol error is detected by the receiving GTP entity, it should log the event including the erroneous message and may include the error in a statistical counter. For Request messages and Response messages without a rejection Cause value, the following applies: - An information element with "Mandatory" in the "Presence requirement" column of a message definition shall always be present in that message. - An information element with "Conditional" in the "Presence requirement" column of a message definition shall be sent when the conditions detailed in the "Condition / Comment" column are met. For Response messages containing a rejection Cause value, see clause 6.1.1. The Version Not Supported Indication message shall be considered as a Triggered message as specified in clause 4.2.5 "Messages with GTPv2 defined replies: Classification of Initial and Triggered Messages". The receiving GTP entity shall apply the error handling specified in the subsequent clauses in decreasing priority. If the received erroneous message is a reply to an outstanding GTP message, the GTP transaction layer shall stop retransmissions and notify the GTP application layer of the error even if the reply is silently discarded.

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

5.16.4.3 Mobility Restrictions and Access Restrictions for Emergency Services

When Emergency Services are supported and local regulation requires IMS Emergency Sessions to be provided regardless of Mobility Restrictions or Access Restrictions, the Mobility Restrictions or Access Restrictions (see clause 5.3.4.1) should not be applied to UEs receiving Emergency Services. Additionally, due to Mobility Restrictions or Access Restrictions (e.g. CAG restrictions) for normally registered UEs, that have established both non-emergency PDU Sessions and emergency PDU Session, the AMF indicates to the SMF to perform a local release of all non-emergency PDU Sessions via PDU Session Release procedure as specified in clause 4.3.4 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. The UE locally releases non-emergency PDU Sessions. The AMF and the UE behave as if the UE is emergency registered as described in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]. When the (R)AN resources for Emergency Services are established, the ARP value for Emergency Services indicates the usage for Emergency Services to the 5G-AN. During handover, the source NG-RAN and source AMF ignore any UE related restrictions during handover evaluation when there is an active PDU Session associated with emergency service. During Mobility Registration Update procedures, including a Mobility Registration Update as part of a handover, the target AMF ignores any Mobility Restrictions or access restrictions for UE with emergency services where required by local regulation. Any non-emergency services are not allowed, by the target network when not allowed by the subscription for the target location. To allow the UE in limited service state (either Emergency Registered or registered for normal service) over a given Access Type to get access to normal services over this Access Type after the Emergency Session has ended and when it has moved to a new area that is not stored by the UE as a forbidden area, after allowing a period of time for subsequent Emergency Services, the UE may explicitly deregister and register for normal services over this Access Type without waiting for the emergency PDU Session Release by the SMF. This functionality applies to all mobility procedures.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.16.4.3

8.13.2.1.2 Minimum Requirement Multi-Layer Spatial Multiplexing 4 Tx Antenna Port for dual connectivity

For dual connectivity the requirements are specified in Table 8.13.2.1.2-3, for 2DL CCs, in Table 8.13.2.1.2-4 for 3DL CCs, and Table 8.13.2.1.2-5 for 4DL CCs, based on single carrier requirement specified in Table 8.13.2.1.2-2, with the addition of the parameters in Table 8.13.2.1.2-1 and the downlink physical channel setup according to Annex C.3.2.The purpose of these tests is to verify the closed loop rank-two performance with wideband and frequency selective precoding by using dual connectivity. Table 8.13.2.1.2-1: Test Parameters for Multi-Layer Spatial Multiplexing (FRC) for dual connectivity Table 8.13.2.1.1-2: Single carrier performance for multiple DC configurations Table 8.13.2.1.2-3: Minimum performance Multi-Layer Spatial Multiplexing (FRC) for dual connectivity Table 8.13.2.1.2-4: Minimum performance Multi-Layer Spatial Multiplexing (FRC) for dual connectivity Table 8.13.2.1.2-5: Minimum performance Multi-Layer Spatial Multiplexing (FRC) for dual connectivity

3GPP TS 36.101

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

RAN4

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

8.13.2.1.2

5.3.4 Mapping to physical resources

For each antenna port used for transmission of the PUSCH in a subframe the block of complex-valued symbols shall be multiplied with the amplitude scaling factor in order to conform to the transmit power specified in clause 5.1.1.1 in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4], and mapped in sequence starting with to physical resource blocks on antenna port and assigned for transmission of PUSCH. The relation between the index and the antenna port number is given by Table 5.2.1-1. The mapping to resource elements corresponding to the physical resource blocks assigned for transmission shall fulfil the following criteria: - not used for transmission of reference signals, and - not part of the last SC-FDMA symbol in a subframe, if the UE transmits SRS in the same subframe in the same serving cell, and - not part of the last SC-FDMA symbol in a subframe configured with cell-specific SRS for non-BL/CE UEs and BL/CE UEs in CEModeA, if the PUSCH transmission partly or fully overlaps with the cell-specific SRS bandwidth, and - not part of an SC-FDMA symbol reserved for possible trigger type 1 SRS transmission as specified in [4] in a UE-specific aperiodic SRS subframe in the same serving cell, and - not part of an SC-FDMA symbol reserved for possible trigger type 0 SRS transmission as specified in [4] in a UE-specific periodic SRS subframe in the same serving cell when the UE is configured with multiple TAGs - not part of the first SC-FDMA symbol in a subframe if the associated DCI indicates PUSCH starting position '01', '10', or '11' and does not indicate PUSCH mode 2. - not part of the first SC-FDMA symbol in the second slot in a subframe if the associated DCI indicates PUSCH starting position '01', '10', or '11' and PUSCH mode 2. - not part of the last SC-FDMA symbol in a subframe if the associated DCI indicates PUSCH ending symbol '1' and does not indicate PUSCH mode 3. - not part of the second slot in a subframe if the associated DCI indicates PUSCH ending symbol '0' and PUSCH mode 3. - not part of SC-FDMA symbols 5 to 13 in a subframe if the associated DCI indicates PUSCH ending symbol '1' and PUSCH mode 3. The mapping to resource elements shall be in increasing order of first the index , then the index . The mapping starts with the first slot in an uplink subframe, except for slot-PUSCH, subslot-PUSCH transmission, or PUSCH mode 2. In case of PUSCH transmissions using sub-PRB allocations for BL/CE UEs, the mapping starts over in every valid uplink subframe composing an UL resource unit. In case of slot-PUSCH, the mapping shall start at in the slot assigned for transmission. In case of PUSCH mode 2, the mapping shall start at in the second slot of the subframe assigned for transmission. In case of subslot-PUSCH, the mapping shall start at symbol where the start of the mapping is dependent on the uplink subslot number in the subframe assigned for transmission and the DMRS-pattern field in the related uplink DCI format [3] according to Table 5.3.4-1 where starting symbol index "4" for subslot #5 is applied if the UE has indicated the capability ul-pattern-ddd-r15. Table 5.3.4-1: Starting symbol index for subslot-PUSCH transmission In case of a semi-persistently scheduled subslot-PUSCH, and semi-persistent scheduling (i.e. higher layer parameter sps-ConfigUL-STTI is configured, see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [9]) with a configured periodicity of 1 subslot (i.e. semiPersistSchedIntervalUL-STTI set to sTTI1), the mapping shall start at symbol depending on the DMRS-pattern field in the related uplink DCI format [3] according to Table 5.3.4-2. In case of a semi-persistently scheduled subslot-PUSCH and semi-persistent scheduling (the higher layer parameter sps-ConfigUL-sTTI-r15 is configured, see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [9]) with repetitions enabled (the higher layer parameter totalNumberPUSCH-SPS-STTI-UL-Repetitions is configured), the mapping shall start at symbol depending on the DMRS-pattern field in the related uplink DCI format [3] according to Table 5.3.4-2. Table 5.3.4-2: Starting symbol index for subslot-PUSCH transmission in case of semi-persistent scheduling with a configured periodicity of 1 subslot In case of subslot-PUSCH and semi-persistent scheduling with a configured periodicity longer than 1 subslot the mapping shall start at symbol according to the first row of Table 5.3.4-2 (i.e. equivalent to a signalling of DMRS-pattern field set to '00'). For the UpPTS, the mapping shall start at symbol and if dmrsLess-UpPts is set to true the mapping shall end at symbol in the second slot of a special subframe, otherwise, the mapping shall end at symbol in the second slot of a special subframe. For BL/CE UEs, the PUSCH transmission is restricted as follows: - For CEModeA, if the PUSCH is associated with C-RNTI or SPS C-RNTI and the higher layer parameter ce-pusch-maxBandwidth-config is set to 5 MHz, the maximum number of allocatable PRBs for PUSCH is 24 PRBs. The allocatable PRBs include the PRBs belonging to the narrowbands defined in clause 5.2.4 and the odd PRB at the center of the uplink system bandwidth in case of odd total number of uplink PRBs. If a resource assignment or frequency hopping would result in a PUSCH resource allocation outside the allocatable PRBs then the PUSCH transmission in that subframe is dropped. - For all other cases, the maximum number of allocatable PRBs for PUSCH is 6 PRBs restricted to one of the narrowbands defined in clause 5.2.4. For BL/CE UEs in CEModeB, resource elements in the last SC-FDMA symbol in a subframe configured with cell-specific SRS shall be counted in the PUSCH mapping but not used for transmission of the PUSCH. For BL/CE UEs, if one or more SC-FDMA symbol(s) are left empty due to guard period for narrowband or wideband retuning, the affected SC-FDMA symbol(s) shall be counted in the PUSCH mapping but not used for transmission of the PUSCH. For a UE configured with SRS carrier switching, if the first symbol in a subframe overlaps with an SRS transmission (including any interruption due to uplink or downlink RF retuning time) in a carrier without PUSCH/PUCCH, the resource elements in the first SC-FDMA symbol shall be counted in the PUSCH mapping but not used for transmission of PUSCH. For a UE configured with SRS carrier switching, if the last symbol in a subframe is counted in the PUSCH mapping and the last symbol in the subframe overlaps with an SRS transmission (including any interruption due to uplink or downlink RF retuning time) in a carrier without PUSCH/PUCCH, the resource elements in the last SC-FDMA symbol shall be counted in the PUSCH mapping but not used for transmission of PUSCH. For a UE configured with SRS carrier switching, if the last symbol in a subframe is not counted in the PUSCH mapping and the second-to-last symbol in the subframe overlaps with an SRS transmission (including any interruption due to uplink or downlink RF retuning time) in a carrier without PUSCH/PUCCH, the resource elements in the second-to-last SC-FDMA symbol shall be counted in the PUSCH mapping but not used for transmission of PUSCH. For a UE configured with PUSCH Mode 1, if DCI indicates PUSCH mode 1 enabled and the corresponding transmission of PUSCH starts in the second slot of a subframe, the resource elements in the first slot of the subframe shall be counted in the PUSCH mapping but not used for transmission of PUSCH. For a UE configured with autonomous uplink, - if the UE indicates PUSCH ending symbol '1' in uplink control information, or endingSymbolAUL is set to '12', the resource elements in the last SC-FDMA symbol shall be counted in the PUSCH mapping but not used for transmission of PUSCH; - if the UE indicates PUSCH starting symbol '1' in uplink control information, the resource elements in the first SC-FDMA symbol shall be counted in the PUSCH mapping but not used for transmission of PUSCH. If uplink frequency-hopping is disabled or the resource blocks allocated for PUSCH transmission are not contiguous in frequency, the set of physical resource blocks to be used for transmission is given by where is obtained from the uplink scheduling grant as described in clause 8.1 in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4]. If uplink frequency-hopping with type 1 PUSCH hopping is enabled, the set of physical resource blocks to be used for transmission is given by clause 8.4.1 in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4]. If uplink frequency-hopping with predefined hopping pattern is enabled, the set of physical resource blocks to be used for transmission in slot is given by the scheduling grant together with a predefined pattern according to where is obtained from the scheduling grant as described in clause 8.1 in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4]. The parameter pusch-HoppingOffset,, is provided by higher layers. The size of each sub-band is given by, where the number of sub-bands is given by higher layers. The function determines whether mirroring is used or not. The parameter Hopping-mode provided by higher layers determines if hopping is "inter-subframe" or "intra and inter-subframe". The hopping function and the function are given by where and the pseudo-random sequence is given by clause 7.2 and CURRENT_TX_NB indicates the transmission number for the transport block transmitted in slot as defined in [8]. The pseudo-random sequence generator shall be initialised with for frame structure type 1 and for frame structure type 2 at the start of each frame. For BL/CE UEs, the PRB resources for PUSCH transmission in the first subframe are obtained from the DCI as described in clauses 5.3.3.1.10 and 5.3.3.1.11 in [3], or from higher layers in PUR-Config when PUSCH is transmitted using preconfigured uplink resources. Each of the PUSCH codewords is transmitted with repetitions, where is the number of transport blocks defined in clause 8.0 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4]. The PUSCH transmission spans consecutive subframes, including subframes that are not BL/CE UL subframes where the UE postpones the PUSCH transmission if . - If uplink 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 PUSCH transmission with associated with C-RNTI or SPS C-RNTI using UE-specific MPDCCH search space including PUSCH transmission without a corresponding MPDCCH, - In a subframe that is fully reserved as defined in clause 8.0 in [4], the PUSCH transmission is postponed until the next BL/CE uplink subframe that is not fully reserved. - In a subframe that is partially reserved, the reserved SC-FDMA symbols shall be counted in the PUSCH mapping but not used for transmission of the PUSCH. - In case the UE is a BL/CE UE configured with higher layer parameter ce-PUSCH-SubPRB-Config-r15 or subPRB-Allocation in PUR-PUSCH-Config, the PUSCH transmission spans consecutive subframes including subframes that are not BL/CE UL subframes where the UE postpones the PUSCH transmission, where is the number of scheduled TBs if ce-PUSCH-MultiTB-Config is enabled and multiple TBs are scheduled, otherwise . - For BL/CE UE in CEModeA, - If PUSCH is transmitted using preconfigured uplink resources, - PUSCH frequency hopping is enabled when the higher layer parameter pur-PUSCH-FreqHopping is set, otherwise frequency hopping is disabled. - Else, if PUSCH scheduled by DCI format 6-0A is associated with PUR-RNTI, - PUSCH frequency hopping is enabled when the higher layer parameter pur-PUSCH-FreqHopping is set and the frequency hopping flag in DCI format 6-0A indicates frequency hopping, otherwise frequency hopping is disabled. - Else, - PUSCH frequency hopping is enabled when the higher-layer parameter pusch-HoppingConfig is set and the frequency hopping flag in DCI format 6-0A indicates frequency hopping, otherwise frequency hopping is disabled. - For BL/CE UE in CEModeB, - If PUSCH is transmitted using preconfigured uplink resources, - PUSCH frequency hopping is enabled when the higher layer parameter pur-PUSCH-FreqHopping is set, otherwise frequency hopping is disabled. - Else, if PUSCH scheduled by DCI format 6-0B is associated with PUR-RNTI, - PUSCH frequency hopping is enabled when the higher layer parameter pur-PUSCH-FreqHopping is set, otherwise frequency hopping is disabled. - Else, - PUSCH frequency hopping is enabled when the higher-layer parameter pusch-HoppingConfig is set, otherwise frequency hopping is disabled. - If frequency hopping is not enabled for PUSCH, all PUSCH repetitions are located at the same PRB resources. - If a BL/CE UE is configured with higher layer parameter ce-PUSCH-FlexibleStartPRB-AllocConfig, the UE is not expected to have the frequency hopping enabled for PUSCH with the resource allocation including the center PRB not belonging to any narrowband. - If frequency hopping is enabled for PUSCH and the UE is not configured with CEModeA and higher layer parameter ce-PUSCH-FlexibleStartPRB-AllocConfig, - PUSCH is transmitted in uplink subframe within the consecutive subframes using the same number of consecutive PRBs as in the previous subframe starting from 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 UL subframe intended for carrying the PUSCH and and are cell-specific higher-layer parameters. For the consecutive subframes, the UE shall not transmit PUSCH in subframe if it is not a BL/CE UL subframe. - If frequency hopping is enabled for PUSCH and the UE is configured with CEModeA and higher layer parameter ce-PUSCH-FlexibleStartPRB-AllocConfig, - Except when the PUSCH resource allocation includes the center PRB not belonging to any narrowband, PUSCH is transmitted in uplink subframe within the consecutive subframes using the same number of consecutive PRBs as in the previous subframe, where is the narrowband index that starting PRB located in the absolute subframe number of the first UL subframe , defined as - If 0 or with , - If with where is the number of edge PRB(s) not belonging to narrowbands in one side of system bandwidth , is the number of narrowbands, the starting PRB index and the length of the allocated resources are defined in clause 8.1.1 of [4]. After hopping, the narrowband in subframe is defined as where and are cell-specific higher-layer parameters. For the consecutive subframes, the UE shall not transmit PUSCH in subframe if it is not a BL/CE UL subframe. After hopping, the resource blocks have the same relative location of starting PRB in as in narrowband . - If frequency hopping is enabled for PUSCH and the UE is configured with higher layer parameter ce-PUSCH-FlexibleStartPRB-AllocConfig, - If a frequency hopping leads to a split resource allocation, where some PRB(s) is (are) on one edge and some PRB(s) is (are) on the other edge of the system bandwidth, the PUSCH transmission is dropped in that subframe. - If a frequency hopping leads to a resource allocation, where some PRB(s) is (are) not belonging to any narrowband, the PUSCH transmission is dropped in that subframe. For BL/CE UEs, for PUSCH transmission corresponding to the random access response grant and its retransmission, frequency hopping of the PUSCH 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-UlHoppingConfigCommonModeA; - if PRACH CE level 2 or 3 is used for the last PRACH attempt, is set to the higher layer parameter interval-UlHoppingConfigCommonModeB. For BL/CE UEs in CEModeB, for PUSCH transmission not associated with Temporary C-RNTI, for frame structure type 1, after a transmission duration of time units (which may include subframes that are not BL/CE UL subframes), a gap of time units shall be inserted, according to the UE capability ue-CE-NeedULGaps, as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [9]. BL/CE UL subframes within the gap of time units shall be counted for the PUSCH resource mapping but not used for transmission of the PUSCH. For BL/CE UEs, for PUSCH transmission associated with Temporary C-RNTI for frame structure type 1, and if PRACH CE level 2 or 3 is used for the last PRACH attempt, after a transmission duration of time units (which may include subframes that are not BL/CE UL subframes), a gap of time units shall be inserted. BL/CE UL subframes within the gap of time units shall be counted for the PUSCH resource mapping but not used for transmission of the PUSCH. For UEs configured with PUSCH-EnhancementsConfig, the number of PUSCH subframe repetitions and the PRB resources for PUSCH transmission in the first subframe are obtained from the DCI as described in clause 5.3.3.1.1C in [3]. The PUSCH transmission spans consecutive subframes, including DL subframes where the UE postpones the PUSCH transmission in the case of frame structure type 2. PUSCH frequency hopping is enabled when the higher-layer parameters pusch-HoppingOffsetPUSCH-Enh and interval-ULHoppingPUSCH-Enh are set and the frequency hopping flag in DCI format 0C indicates frequency hopping, otherwise frequency hopping is disabled. If frequency hopping is not enabled for PUSCH, the PUSCH repetitions are located at the same PRB resources as in the first subframe. If frequency hopping is enabled for PUSCH, PUSCH is transmitted in uplink subframe within the consecutive subframes using the PRB resources starting at PRB index where is the absolute subframe number of the first UL subframe carrying the PUSCH and is given by the higher-layer parameter interval-ULHoppingPUSCH-Enh and is given by the higher-layer parameter pusch-HoppingOffsetPUSCH-Enh. For BL/CE UEs communicating over NTN, for PUSCH transmission, for frame structure type 1, after a transmission duration of time units (which may include subframes that are not BL/CE UL subframes), a transmission gap of time units shall be counted for the PUSCH resource mapping but not used for transmission of the PUSCH, according to the single UE capability ntn-SegmentedPrecompensationGaps-r17, as specified in 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [9]. The quantity is provided by higher layers, and the quantity is configured by higher layers based on the UE capability, if signalled.

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

19.4.2.13 PGW Set FQDN

A PGW Set Identifier is a globally unique identifier of a set of equivalent and interchangeable PGWs from a given network that provides distribution, redundancy and scalability. A PGW Set Identifier shall be constructed from the MCC, MNC and a Set ID. The PGW Set FQDN shall be constructed as follows: set<Set Id>.pgwset.epc.mnc<MNC>.mcc<MCC>.3gppnetwork.org where - <MNC> = 3 digits - <MCC> = 3 digits If there are only 2 significant digits in the MNC, one "0" digit shall be inserted at the left side to fill the 3 digits coding of MNC in the PGW Set FQDN. - <Set Id> is the string representing a PGW Set within the PLMN, chosen by the operator, that shall consist of alphabetic characters (A-Z and a-z), digits (0-9) and/or the hyphen (-) and that shall end with either an alphabetic character or a digit, where the case of alphabetic characters is not significant (i.e. two PGW Set IDs with the same characters but using different lower and upper cases identify the same PGW Set). EXAMPLE: "set12.pgwset.epc.mnc012.mcc345.3gppnetwork.org" (for the PGW set from MCC 345, MNC 12 and Set ID "12")

3GPP TS 23.003

Numbering, addressing and identification

CT WG4

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

19.4.2.13

7.2.11.3 Downlink Data Notification Failure Indication

A Downlink Data Notification Failure indication shall be sent from an MME/SGSN to a SGW indicating that the UE did not respond to paging. It shall also be sent in the case that the UE responded to the page with a Service Request but that the MME has rejected the request by sending a Service Reject to the UE. It may happen, for example, because the requested service is not supported or there is a bearer context mismatch. Additionally, a Downlink Data Notification Failure indication shall be sent in case the UE has rejected the page as specified in clause 4.3.33 in 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [3]. This message should not be used after an MME/SGSN successfully receives the Service Request message from the UE in the Network Triggered Service Request procedure as defined in the 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [3]. NOTE: Either the Modify Bearer Request message or the Delete Bearer Command message is used by the MME/SGSN to indicate a possible failure case after an MME/SGSN successfully receives the Service Request message from the UE. Possible Cause values are: - "UE not responding". - "Service denied". - "UE already re-attached". - "Rejection due to paging restriction". Table .3-1 specifies the presence of the IEs in the message. Table .3-1: Information Elements in a Downlink Data Notification Failure Indication

3GPP TS 29.274

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

CT WG4

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

7.2.11.3

5.8.2.9.2 SMF Constructing the "End marker" Packets

UPF referred in this clause is the UPF terminates N3 reference point. It is assumed that the PDU Session for the UE comprises of an UPF that acts as a PDU Session Anchor and an intermediate UPF terminating N3 reference point at the time of this Handover procedure. In the case of inter NG-RAN Handover procedure without UPF change, SMF shall indicate the UPF to switch the N3 path(s) by sending an N4 Session Modification Request message (N4 session ID, new AN Tunnel Info of NG RAN). After sending the last PDU on the old path, UPF shall replace the old AN Tunnel Info with the new one and responds with an N4 Session Modification Response message to acknowledge the success of path switch. When the path switch is finished, SMF constructs the end marker packet(s) and sends it to the UPF. UPF then forwards the packet(s) to the source NG RAN. In the case of inter NG-RAN Handover procedure with UPF change, SMF shall indicate the PSA UPF to switch the N9 user plane path(s) by sending an N4 Session Modification Request message (N4 session ID, new CN Tunnel Info of UPF). After sending the last PDU on the old N9 path, PSA UPF shall replace the old CN Tunnel Info with the new one and responds with an N4 Session Modification Response message to acknowledge the success of path switch. When the path switch is finished, SMF constructs the end marker packet(s) and sends it to PSA UPF. PSA UPF then forwards the packet(s) to the source UPF.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.8.2.9.2

8.141 Services Authorized

Services Authorized shall be coded as depicted in Figure 8.141-1. Figure 8.141-1: Services Authorized Vehicle UE Authorized represents an indication if the UE is authorized to use the V2X services as Vehicle UE, as specified in 3GPP TS 29.272[ Evolved Packet System (EPS); Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol ] [70]. Vehicle UE Authorized field is encoded as a one octet long enumeration. Currently, Vehicle UE Authorized field specifies two enumeration values: 0 (indicates "authorized") and 1 (indicates "not authorized"). Pedestrian UE Authorized represents an indication if the UE is authorized to use the V2X services as Pedestrian UE, as specified in 3GPP TS 29.272[ Evolved Packet System (EPS); Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol ] [70]. Pedestrian UE Authorized field is encoded as a one octet long enumeration. Currently, Pedestrian UE Authorized field specifies two enumeration values: 0 (indicates "authorized") and 1 (indicates "not authorized").

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

5.27.3 Support for TSC QoS Flows

TSC QoS Flows use a Delay-critical GBR resource type and TSC Assistance Information. TSC QoS Flows may use standardized 5QIs, pre-configured 5QIs or dynamically assigned 5QI values (which requires signalling of QoS characteristics as part of the QoS profile) as specified in clause 5.7.2. For each instance of Periodicity, within each Period (defined by periodicity value), TSC QoS Flows are required to transmit only one burst of maximum size MDBV within the 5G-AN PDB. Known QoS Flow traffic characteristics provided in the TSCAI may be used to optimize scheduling in the 5GS. The following is applicable for the QoS profile defined for TSC QoS Flows: 1. The TSC Burst Size may be used to set the MDBV as follows: The maximum TSC Burst Size is considered as the largest amount of data within a time period that is equal to the value of 5G-AN PDB of the 5QI. The maximum value of TSC Burst Size should be mapped to a 5QI with MDBV that is equal or higher. When integration with IEEE TSN applies, this 5QI also shall have a PDB value that satisfies the bridge delay capabilities (see clause 5.27.5 for more details) reported for the corresponding traffic class. For TSC QoS Flows, the Maximum Burst Size of the aggregated TSC streams to be allocated to this QoS Flow can be similarly mapped to a 5QI with MDBV value that is equal or higher. If interworking with a TSN network deployed in the transport network is supported, the maximum value of TSC Burst Size should be mapped to a 5QI with MDBV that is equal. 2. The PDB is explicitly divided into 5G-AN PDB and CN PDB as described in clause 5.7.3.4. Separate delay budgets are necessary for calculation of expected packet transmit times on 5G System interfaces. For the TSC QoS Flow, the5G-AN PDB is set to value of 5QI PDB minus the CN PDB as described in clause 5.7.3.4. The CN PDB may be static value or dynamic value and is up to the implementation of 5GS bridge. 3. When integration with IEEE TSN applies, the Maximum Flow Bitrate calculated by the TSN AF as per Annex I.1 may be used to set GBR. In this case, MBR is set equal to GBR. 4. ARP is set to a pre-configured value. 5. 5QI value is derived using QoS mapping tables and TSN QoS information as described in clause 5.28.4 in the case of integration with IEEE TSN network, or using QoS Reference parameters and Requested PDB, Burst Size, Priority parameters as described in clause 4.15.6.6 or clause 4.15.6.6a of TS 23.502[ Procedures for the 5G System (5GS) ] [3] in the case of AF requested Time Sensitive Communication.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.27.3

4.3.3.2 UE or network requested PDU Session Modification (non-roaming and roaming with local breakout)

The UE or network requested PDU Session Modification procedure (non-roaming and roaming with local breakout scenario) is depicted in figure 4.3.3.2-1. Figure 4.3.3.2-1: UE or network requested PDU Session Modification (for non-roaming and roaming with local breakout) 1. The procedure may be triggered by following events: 1a. (UE initiated modification) The UE initiates the PDU Session Modification procedure by the transmission of an NAS message (N1 SM container (PDU Session Modification Request (PDU session ID, Packet Filters, Operation, Requested QoS, Segregation, 5GSM Core Network Capability, Number Of Packet Filters, [Connection Capabilities], [Always-on PDU Session Requested], [Requested Non-3GPP Delay Budget])), PDU Session ID, UE Integrity Protection Maximum Data Rate, [Port Management Information Container]) message. Depending on the Access Type, if the UE was in CM-IDLE state, this SM-NAS message is preceded by the Service Request procedure. The NAS message is forwarded by the (R)AN to the AMF with an indication of User location Information. The AMF invokes Nsmf_PDUSession_UpdateSMContext (SM Context ID, N1 SM container (PDU Session Modification Request)). When the UE requests specific QoS handling for selected SDF(s), the PDU Session Modification Request includes Packet Filters describing the SDF(s), the requested Packet Filter Operation (add, modify, delete) on the indicated Packet Filters, the Requested QoS and optionally a Segregation indication. The Segregation indication is included when the UE recommends to the network to bind the applicable SDF(s) on a distinct and dedicated QoS Flow e.g. even if an existing QoS Flow can support the requested QoS. The network should abide by the UE request, but is allowed to proceed instead with binding the selected SDF(s) on an existing QoS Flow. NOTE 1: Only one QoS Flow is used for traffic segregation. If UE makes subsequent requests for segregation of additional SDF(s), the additional SDF(s) are multiplexed on the existing QoS Flow that is used for segregation. The UE shall not trigger a PDU Session Modification procedure for a PDU Session corresponding to a LADN when the UE is outside the area of availability of the LADN. The PS Data Off status, if changed, shall be included in the PCO in the PDU Session Modification Request message. For a PDU Session which was established in the EPS, when the UE moves from EPS to 5GS for the first time, the UE includes an Always-on PDU Session Requested indication in the PDU Session Modification Request message if it wants to change the PDU Session to an always-on PDU Session. If UE supports to report URSP rule enforcement to network and the URSP rule that triggered this PDU Session Establishment Request included the Indication for reporting URSP rule enforcement, the UE may provide Connection Capabilities as described in clause 6.6.2.4 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. When PCF is deployed, the SMF shall further report the PS Data Off status to PCF if the PS Data Off event trigger is provisioned, the additional behaviour of SMF and PCF for 3GPP PS Data Off is defined in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. The 5GSM Core Network Capability is provided by the UE and handled by SMF as defined in clause 5.4.4b of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The UE Integrity Protection Maximum Data Rate indicates the maximum data rate up to which the UE can support UP integrity protection. It is set as defined in TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The Number Of Packet Filters indicates the number of supported packet filters for signalled QoS rules as described in clause 5.17.2.2.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. When it moves from EPS to 5GS for the first time, a UE that supports EAS re-discovery as described in clause 6.2.3.3 of TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [74], may indicate so in the PCO. When it moves from EPS to 5GS for the first time, a UE that hosts the EDC functionality shall indicate in the PCO its capability to support the EDC functionality (see clause 5.2.1 of TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [74]). Port Management Information Container may be received from DS-TT and includes DS-TT port related management information as defined in clause 5.28.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 1b. (PCF initiated SM Policy Association Modification) The PCF performs a PCF initiated SM Policy Association Modification procedure as defined in clause 4.16.5.2 to notify SMF about the modification of policies. This may e.g. have been triggered by a policy decision or upon AF requests, e.g. Application Function influence on traffic routing as described in step 5 in clause 4.3.6.2 or AF to provide Port management information Container. If QoS Monitoring is requested by the AF, the PCF generates the QoS Monitoring policy for the corresponding service data flow and provides the policy in the PCC rules to the SMF in this step. If Periodicity is provided by the AF, the PCF provides the Periodicity information in the PCC rules. Based on operator's local policies, the PCF sends to the SMF an indication in the PCC Rule to perform N6 Traffic Parameter Measurements for N6 Jitter and, if not received from the AF, also UL and/ or DL Periodicity measurements. The PCF may provision a PDU Set Control Information as described in clause 6.1.3.27.4 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20] within PCC Rules based on the information provided by the AF and/or the local operator policies. 1c. (SMF requested modification) The UDM updates the subscription data of SMF by Nudm_SDM_Notification (SUPI, Session Management Subscription Data). The SMF updates the Session Management Subscription Data and acknowledges the UDM by returning an Ack with (SUPI). 1d. (SMF requested modification) The SMF may decide to modify PDU Session. This procedure also may be triggered based on locally configured policy or triggered from the (R)AN (see clause 4.2.6 and clause 4.9.1). It may also be triggered if the UP connection is activated (as described in Service Request procedure) and the SMF has marked that the status of one or more QoS Flows are deleted in the 5GC but not synchronized with the UE yet. It may also be triggered to update QoS profile in the NG RAN and PDU Set information marking in the PSA UPF upon completion of mobility procedure as defined in clause 5.37.5.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If interworking with TSN deployed in the transport network is supported and either the UPF supports CN-TL or NG-RAN supports AN-TL (see clause 4.4.8 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]), the procedure may be triggered due to reception of Status group from TN CNC. The SMF may decide to modify PDU Session to send updated ECS Address Configuration Information to the UE as defined in clause 6.5.2 of TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [74]. The SMF may decide to modify PDU Session to send updated DNS server address to the UE as defined in clause 6.2.3.2.3 of TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [74]. The SMF may decide to modify PDU Session to send the EAS rediscovery indication to the UE as defined in clause 6.2.3.3 of TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [74]. If the SMF receives one of the triggers in step 1b ~ 1d, the SMF starts SMF requested PDU Session Modification procedure. 1e. (AN initiated modification) (R)AN shall indicate to the SMF when the AN resources onto which a QoS Flow is mapped are released irrespective of whether notification control is configured. (R)AN sends the N2 message (PDU Session ID, N2 SM information) to the AMF. The N2 SM information includes the QFI, User location Information and an indication that the QoS Flow is released. The AMF invokes Nsmf_PDUSession_UpdateSMContext (SM Context ID, N2 SM information). (AN initiated notification control) If notification control is configured for a GBR QoS Flow, (R)AN sends a N2 message (PDU Session ID, N2 SM information) to SMF when the (R)AN decides the QoS targets of the QoS Flow cannot be fulfilled or can be fulfilled again, respectively. The N2 SM information includes the QFI and an indication that the QoS targets for that QoS Flow cannot be fulfilled or can be fulfilled again, respectively. When QoS targets cannot be fulfilled, the N2 SM information indicates a reference to the Alternative QoS Profile matching the values of the QoS parameters that the NG-RAN is currently fulfilling as specified in clause 5.7.2.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the QoS Flow has a TSCAI including Capability for BAT adaptation and without Burst Arrival Time, the N2 SM information can also include a BAT offset as described in clause 5.27.2.5 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The AMF invokes Nsmf_PDUSession_UpdateSMContext (SM Context ID, N2 SM information). If the PCF has subscribed to the event, SMF reports this event to the PCF for each PCC Rule for which notification control is set in step 2. 1f. (AMF initiated modification) If the UE supports CE mode B and use of CE mode changes from restricted to unrestricted or vice versa in the Enhanced Coverage Restriction information in the UE context in the AMF and the UE has already established PDU sessions, then the AMF shall trigger a PDU session modification to the SMFs serving the UE's PDU sessions when the AMF determines that NAS-SM timer shall be updated due to the change of Enhanced Coverage Restriction and include the extended NAS-SM indication only if use of CE mode B is now unrestricted in the Enhanced Coverage Restriction information in the UE context in the AMF. If the AMF, based on configuration, is aware that the UE is accessing over a gNB using GEO satellite backhaul and GEO Satellite ID needs to be updated to the SMF, the AMF may, based on configuration, include the latest GEO Satellite ID as described in clause 5.43.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 1g. (AMF initiated modification) the AMF informs the SMF of updates of the NWDAF ID(s) used for UE related Analytics and corresponding Analytics ID(s). Also, If the PCF request notification of SM Policy Association and there is any PDU Session established to that DNN, S-NSSAI [PCF binding information, notification of SM Policy Association establishment Indication]. 1h. (AMF initiated modification) When the AMF determines that the S-NSSAI is to be replaced with an Alternative S-NSSAI (as described in clause 5.15.19 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]), the AMF invokes Nsmf_PDUSession_UpdateSMContext Request (SM Context ID, S-NSSAI, Alternative S-NSSAI) to the SMF of the PDU session associated with the S-NSSAI. Based on the extended NAS-SM timer indication, the SMF shall use the extended NAS-SM timer setting for the UE as specified in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [25]. 2. The SMF may need to report some subscribed event to the PCF by performing an SMF initiated SM Policy Association Modification procedure as defined in clause 4.16.5.1. This step may be skipped if PDU Session Modification procedure is triggered by step 1b or 1d. If dynamic PCC is not deployed, the SMF may apply local policy to decide whether to change the QoS profile. Steps 2a to 7 are not invoked when the PDU Session Modification requires only action at a UPF (e.g. gating). 2a. The SMF may update the UPF with N4 Rules related to new or modified QoS Flow(s). NOTE 2: This allows the UL packets with the QFI of a new or modified QoS Flow to be transferred. If the SMF initiated the PDU Session Modification procedure in step 1b due to PCF initiated SM Policy Association Modification that adds one or more PCC Rule(s) with a TSC Assistance Container and if interworking with TSN deployed in the transport network is supported, the SMF may instruct the UPF to assign or remove a distinct N3 tunnel end point address for the QoS Flow(s) assigned with a TSC Assistance Container. If the SMF initiated the PDU Session Modification procedure in step 1d due to reception of Status group from TN CNC, the SMF includes a TL-Container with a set-request to the N4 Session Modification request that is sent to the UPF, as described in clause 5.28a.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the SMF initiated the PDU Session Modification procedure in step 1b due to PCF initiated SM Policy Association Modification that adds one or more PCC Rule(s) with UL and/or DL Periodicity, the SMF composes the TSCAI with the periodicity information. If the SMF initiated the PDU Session Modification procedure in step 1b due to PCF initiated SM Policy Association Modification that adds one or more PCC Rule(s) with an indication to perform N6 Traffic Parameter measurements (e.g. the N6 Jitter range associated with the DL Periodicity, and the UL/DL periodicity), the SMF instructs the UPF to perform N6 Traffic Parameter measurement associated with the DL Periodicity for the QoS Flow, as described in clause 5.37.8.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If N6 Jitter measurements are requested and DL Periodicity is received in the PCC Rule, the SMF shall include the DL Periodicity in the request to the UPF, see clause 5.8.5.11 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the PCC Rule includes a Protocol Description and the SMF decides to enable PDU Set Identification and marking for PDU Set based Handling by PSA UPF, the SMF should provide the Protocol Description information to the UPF and request the UPF to mark the PDU Set Information in each PDU belonging to the PDU Sets as described in clause 5.37.5.2 and 5.8.5.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] and to mark the End of Data burst in the last PDU in downlink based on the protocol header identified by the Protocol Description information, according to the local operator policies, see clause 5.37.8.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the PDU Set information marking has been activated in the UPF for a QoS flow, the SMF may request the UPF to stop the marking of the PDU Set information based on the indication from the RAN or PCF, e.g. if the Target RAN does not support the PDU Set based handling as described in clause 5.37.5.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the PCF initiated SM Policy Association Modification that adds one or more PCC Rule(s) with PDU Set Control Information, the SMF performs PDU Set based QoS handling, see clause 5.37.5 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If redundant transmission has not been activated to the PDU session and the SMF decides to perform redundant transmission for the QoS Flow, the SMF indicates to the UPF to perform packet duplication and elimination for the QoS Flow. If redundant transmission has been activated on the PDU Session and the SMF decides to stop redundant transmission, the SMF indicates the UPF to release the CN Tunnel Info which is used as the redundancy tunnel of the PDU Session and also indicates the UPF to stop packet duplication and elimination for the corresponding QoS Flow(s). NOTE 3: The method to perform elimination and reordering on RAN/UPF based on the packets received from the two GTP-U tunnels is up to RAN/UPF implementation. The two GTP-U tunnels are terminated at the same RAN node and UPF. If redundant transmission has not been activated to the PDU Session and the SMF decides to perform redundant transmission for the QoS Flow with two I-UPFs between the PSA UPF and the NG-RAN, the SMF sends a N4 Session Establishment Request message to the I-UPFs including UL CN Tunnel Info of the PSA UPF and a request to allocate CN Tunnel Info. SMF may make use of Redundant Transmission Experience analytics provided by NWDAF, when SMF takes a decision whether to perform redundant transmission, or stop redundant transmission if it had been activated, as described in clause 6.13 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]. If the AMF initiated the PDU Session Modification procedure in step 1h due to network slice replacement with the Alternative S-NSSAI and if the SMF determines that the PDU Session is retained, the SMF sends N4 Session Modification request message to the UPF to replace the S-NSSAI with the Alternative S-NSSAI, as described in clause 5.15.19 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 2b. The UPF(s) respond to the SMF. If redundant transmission has not been activated to the PDU session and the SMF indicated the UPF to perform packet duplication and elimination for the QoS Flow in step 2a, the UPF allocates an additional CN Tunnel Info. The additional CN Tunnel Info is provided to the SMF. If redundant transmission has not been activated to the PDU Session and the SMF decides to perform redundant transmission for the QoS Flow with two I-UPFs in step 2a, the UPFs allocate CN Tunnel Info. The CN Tunnel Info of each I-UPF is provided to the SMF. If interworking with TSN deployed in the transport network is supported and the UPF supports CN-TL and received a TL-Container with a set-request from the SMF/CUC in step 2a (see clause 4.4.8 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]), the UPF/CN-TL includes a TL-Container with a set-response to the N4 Session Modification response, as described in clause 5.28a.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If requested by SMF in step 2a, the PSA UPF will initiate N4 Session Level reporting for N6 Traffic Parameter Measurement Report as described in clause 4.4.2.2. If N6 Traffic Parameter(s) are available then the response to the SMF in this step may include the N6 Traffic Parameter(s) (e.g., the N6 Jitter range associated with the DL Periodicity, and the UL/DL periodicity) for the QoS Flow (see clause 5.37.8.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]). The SMF composes the TSCAI with the received N6 Traffic Parameters. 3a. For UE or AN initiated modification or AMF initiated modification, the SMF responds to the AMF through Nsmf_PDUSession_UpdateSMContext Response ([N2 SM information (PDU Session ID, QFI(s), QoS Profile(s), [Alternative QoS Profile(s)], Session-AMBR], [CN Tunnel Info(s)]), N1 SM container (PDU Session Modification Command (PDU Session ID, QoS rule(s), QoS rule operation, QoS Flow level QoS parameters if needed for the QoS Flow(s) associated with the QoS rule(s), Session-AMBR, [Always-on PDU Session Granted], [Port Management Information Container], [Non-3GPP QoS Assistance Information Container]))). See clause 5.7 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] for the QoS Profile, Alternative QoS Profile and QoS rule and QoS Flow level QoS parameters. Alternative QoS Profile is only valid for AN initiated modification. If the PDU Session Modification was requested by the UE to modify a PDU Session to an always-on PDU Session, the SMF shall include an Always-on PDU Session Granted indication in the PDU Session Modification Command to indicate whether the PDU Session is to be changed to an always-on PDU Session or not via the Always-on PDU Session Granted indication in the PDU Session Modification Command. The N2 SM information carries information that the AMF shall provide to the (R)AN. It may include the QoS profiles and the corresponding QFIs to notify the (R)AN that one or more QoS flows were added, or modified. It may include only QFI(s) to notify the (R)AN that one or more QoS flows were removed. The SMF may indicate for each QoS Flow whether redundant transmission shall be performed by a corresponding redundant transmission indicator. If the SMF decides to activate redundant transmission in step 2a, the SMF includes the allocated additional CN Tunnel Info in the N2 SM information. If the SMF decides to perform redundant transmission for new QoS Flow with two I-UPFs in step 2a, the SMF includes the allocated CN Tunnel Info of the two I-UPFs in the N2 SM information. If the PDU Session Modification was triggered by the (R)AN Release in step 1e the N2 SM information carries an acknowledgement of the (R)AN Release. If the PDU Session Modification was requested by the UE for a PDU Session that has no established User Plane resources, the N2 SM information provided to the (R)AN includes information for establishment of User Plane resources. For Network Slice Replacement if the SMF determines that the PDU Session is to be retained, the S-NSSAI in N2 SM information is set to Alternative S-NSSAI. - If the SMF has received a Requested Non-3GPP Delay Budget for a QoS flow from the PEGC, the SMF may adjust the dynamic CN PDB signalled to the NG-RAN as defined in clause 5.44.3.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If redundant transmission has been activated on the PDU Session and the SMF decides to stop redundant transmission in step 2a, the SMF indicates the (R)AN to release the AN Tunnel and stop packet duplication and elimination associated with the redundancy tunnel of the PDU Session. The N1 SM container carries the PDU Session Modification Command that the AMF shall provide to the UE. It may include the QoS rules, QoS Flow level QoS parameters if needed for the QoS Flow(s) associated with the QoS rule(s) and corresponding QoS rule operation and QoS Flow level QoS parameters operation to notify the UE that one or more QoS rules were added, removed or modified. For the AMF initiated the PDU Session Modification procedure in step 1h due to network slice replacement, and if the SMF determines that the PDU Session is to be retained, the SMF includes the Alternative S-NSSAI in the PDU Session Modification Command to the UE and a cause value indicating that the S-NSSAI of the PDU Session is replaced with the Alternative S-NSSAI. If the AMF initiated the PDU Session Modification procedure in step 1h due to network slice replacement and if the PDU Session is SSC mode 3 and if the SMF determines that the PDU Session is to be re-established on the Alternative S-NSSAI, the SMF includes the Alternative S-NSSAI in the PDU Session Modification Command to the UE and a cause value indicating that a PDU Session re-establishment on the Alternative S-NSSAI is required. The UE re-establishes a new PDU Session on the Alternative S-NSSAI, as described in clause 5.15.19 in TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the PDU Session is SSC mode 1 or SSC mode 2, the SMF may initiate release of the PDU Session as described in clause 4.3.4.2. If port number and a Port Management Information Container have been received from PCF in Step 2 and the port number matches the port number assigned for the DS-TT port for this PDU session, then SMF includes the Port Management Information Container in the N1 SM container. The SMF may need to send transparently through NG-RAN the PDU Session Modification Command to inform the UE about changes in the QoS parameters (i.e. 5QI, GFBR, MFBR) that the NG-RAN is currently fulfilling after the SMF receives QoS Notification Control as defined in clause 5.7.2.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. When the SMF sends on the PDU Session Modification Command transparently through NG-RAN, the N2 SM information is not included as part of the Namf_Communication_N1N2MessageTransfer. If the UE indicated in the PCO that it supports the EDC functionality, the SMF may indicate to the UE either that the use of the EDC functionality is allowed for the PDU Session or that the use of the EDC functionality is required for the PDU Session (see clause 5.2.1 of TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [74]). Based on the S-NSSAI and DNN for PIN, the SMF may provide the UE with per QoS-flow Non-3GPP QoS Assistance Information in the N1 SM container. 3b. For SMF requested modification, the SMF invokes Namf_Communication_N1N2MessageTransfer ([N2 SM information] (PDU Session ID, QFI(s), QoS Profile(s), [Alternative QoS Profile(s)], Session-AMBR, [CN Tunnel Info(s)], QoS Monitoring indication, QoS Monitoring reporting frequency), [TSCAI(s)], TL-Container(s), [ECN marking for L4S indicator(s)]), N1 SM container (PDU Session Modification Command (PDU Session ID, QoS rule(s), QoS Flow level QoS parameters if needed for the QoS Flow(s) associated with the QoS rule(s), QoS rule operation and QoS Flow level QoS parameters operation, Session-AMBR))). - For each QoS Flow: - an ECN marking for L4S indicator to (R)AN in the case of ECN marking for L4S in RAN as described in clause 5.37.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]; or - a QoS monitoring configuration for congestion information as described in clause 5.45.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] in the case of ECN marking for L4S by PSA UPF as described in clause 5.37.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] or QoS monitoring for congestion information as described in clause 5.45.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the SMF initiated the PDU Session Modification procedure in step 1b due to PCF initiated SM Policy Association Modification that adds one or more PCC Rule(s) with a TSC Assistance Container and if interworking with TSN deployed in the transport network is supporte, the SMF may instruct the NG-RAN to assign or remove a distinct N3 tunnel end point address for the QoS Flow(s) assigned with a TSC Assistance Container. The SMF may indicate for each QoS Flow whether redundant transmission shall be performed by a corresponding redundant transmission indicator. If the SMF decides to activate redundant transmission in step 2a, the SMF includes the allocated additional CN Tunnel Info in the N2 SM information. If the SMF decides to perform redundant transmission for new QoS Flow with two I-UPFs in step 2a, the SMF includes the allocated CN Tunnel Info of the two I-UPFs in the N2 SM information. If redundant transmission has been activated on the PDU Session and the SMF decides to stop redundant transmission in step 2a, the SMF indicates the (R)AN to release the AN Tunnel and stop packet duplication and elimination associated with the redundancy tunnel of the PDU Session. The SMF indicates the request for QoS Monitoring for the QoS Flow according to the information received from the PCF in step 1b, or based on SMF local policy, e.g. when the RAN rejected the creation of a specific QoS Flow. In the case of receiving the QoS Monitoring indication, the RAN enables the RAN part of UL/DL packet delay measurement for the QoS Flow and the QoS Monitoring reporting frequency is used by RAN to determine the packet delay measurement frequency of the RAN part. In the case of receiving QoS monitoring configuration for congestion information, RAN initiates reporting of UL and/or DL QoS Flow congestion information to PSA UPF as defined in clause 5.45.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The TSCAI is defined in clause 5.27.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the SMF initiated the PDU Session Modification procedure in step 1d due to reception of Status group from TN CNC, the SMF includes a TL-Container with a set-request to the N2 SM information, as described in clause 5.28a.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the UE is in CM-IDLE state and an ATC is activated, the AMF updates and stores the UE context based on the Namf_Communication_N1N2MessageTransfer and steps 4, 5, 6 and 7 are skipped. When the UE is reachable e.g. when the UE enters CM-CONNECTED state, the AMF forwards the N1 message to synchronize the UE context with the UE. 3c. For SMF requested modification due to updated SMF-Associated parameters from the UDM, the SMF may provide the SMF derived CN assisted RAN parameters tuning to the AMF. The SMF invokes Nsmf_PDUSession_SMContextStatusNotify (SMF derived CN assisted RAN parameters tuning) towards the AMF. The AMF stores the SMF derived CN assisted RAN parameters tuning in the associated PDU Session context for this UE. 3d. For SMF requested modification due to updated NWDAF ID, the SMF informs the AMF of updates of the NWDAF ID(s) used for UE related Analytics and corresponding Analytics ID(s). 4. The AMF may send N2 ([N2 SM information received from SMF], NAS message (PDU Session ID, N1 SM container (PDU Session Modification Command))) Message to the (R)AN. 5. The (R)AN may issue AN specific signalling exchange with the UE that is related with the information received from SMF. For example, in the case of a NG-RAN, an RRC Connection Reconfiguration may take place with the UE modifying the necessary (R)AN resources related to the PDU Session or if only N1 SM container is received in step 4 from AMF, RAN transports only the N1 SM container to the UE. The (R)AN may consider the updated CN assisted RAN parameters tuning to reconfigure the AS parameters. As part of this, the N1 SM container is provided to the UE. If the N1 SM container includes a Port Management Information Container then the UE provides the container to DS-TT. If new DNS server address is provided to the UE in the PCO, the UE can refresh all EAS(s) information (e.g. DNS cache) bound to the PDU Session, based on UE implementation as described in clause 6.2.3.2.3 of TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [74]. 6. The (R)AN may acknowledge N2 PDU Session Request by sending a N2 PDU Session Ack (N2 SM information (List of accepted/rejected QFI(s), AN Tunnel Info, PDU Session ID, Secondary RAT usage data, TL-Container(s), BAT offset, Periodicity, established QoS Flows status (active/not active) for QoS monitoring configuration for congestion information, established QoS Flows status (active/not active) for ECN marking for L4S, PDU Set Based Handling Support Indication), User location Information) Message to the AMF. In the case of Dual Connectivity, if one or more QFIs were added to the PDU Session, the Master RAN node may assign one or more of these QFIs to a NG-RAN node which was not involved in the PDU Session earlier. In this case the AN Tunnel Info includes a new N3 tunnel endpoint for QFIs assigned to the new NG-RAN node. Correspondingly, if one or more QFIs were removed from the PDU Session, a (R)AN node may no longer be involved in the PDU Session anymore and the corresponding tunnel endpoint is removed from the AN Tunnel Info. The NG-RAN may reject QFI(s) if it cannot fulfil the User Plane Security Enforcement information for a corresponding QoS Profile, e.g. due to the UE Integrity Protection Maximum Data Rate being exceeded. When receiving the request for QoS Monitoring, the (R)AN may indicate its rejection to perform QoS Monitoring, e.g. due to the (R)AN load condition. The (R)AN may reject the addition or modification of a QoS Flow, e.g. due to handling of the UE-Slice-MBR as described in clause 5.7.1.10 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the (R)AN rejects the addition or modification of a QoS Flow, the SMF is responsible of updating the QoS rules and QoS Flow level QoS parameters associated to that QoS Flow in the UE accordingly. NG-RAN includes the PDU Set Based Handling Support Indication in N2 SM information as defined in clause 5.37.5.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] If the PLMN has configured secondary RAT usage reporting, the NG-RAN node may provide RAN Usage Data Report. The User Location Information shall include the serving cell's ID and if Dual Connectivity is activated for the UE, the PSCell ID. If the redundant transmission has not been activated to the PDU session and the SMF indicates to the RAN that one of the QoS Flow shall perform redundant transmission, the RAN includes an additional AN tunnel info in N2 SM information. If interworking with TSN deployed in the transport network is supported and the NG-RAN supports AN-TL and received a TL-Container with a set-request from the SM/CUC in step 3b (see clause 4.4.8 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]), the NG-RAN/AN-TL includes a TL-Container with a set-response to the N2 SM information, as described in clause 5.28a.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the NG-RAN has determined a BAT offset and optionally a periodicity as described in clause 5.27.2.5 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], the NG-RAN provides the BAT offset and optionally the periodicity in the N2 SM information. 7. The AMF forwards the N2 SM information and the User location Information received from the AN to the SMF via Nsmf_PDUSession_UpdateSMContext service operation. The SMF replies with a Nsmf_PDUSession_UpdateSMContext Response. If the N2 SM information indicates failure of whole N2 SM request (i.e. no part of the N2 SM request is successful in (R)AN), the SMF assumes that the NAS PDU, if provided in step 3, was not forwarded by NG-RAN to UE, as described in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [10]. In this case, if the PDU Session modification is UE triggered the SMF shall reject the PDU session modification by including a N1 SM container with a PDU Session Modification Reject message (see clause 8.3.3 of TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [25]) in the Nsmf_PDUSession_UpdateSMContext Response in step 7b. Step 8 is skipped in this case. Otherwise, the SMF assumes that the NAS PDU was sent to UE successfully. If the (R)AN rejects QFI(s), the SMF is responsible of updating the QoS rules and QoS Flow level QoS parameters if needed for the QoS Flow(s) associated with the QoS rule(s) in the UE accordingly, i.e. the SMF shall trigger a separate NAS PDU Session Modification procedure after step 11 to align the SM context of this PDU Session in UE. 8. The SMF may update N4 session of the UPF(s) that are involved by the PDU Session Modification by sending N4 Session Modification Request message to the UPF (see NOTE 3). The SMF may update the UPF with N4 Rules related to new, modified or removed QoS Flow(s), unless it was done already in step 2a. NOTE 4: This allows the DL packets of the new or modified QoS Flow to be transferred. If an additional AN Tunnel Info is returned by RAN in step 6, the SMF informs the UPF about this AN Tunnel Info for redundant transmission. In the case of redundant transmission with two I-UPFs, the SMF provides AN Tunnel Info to two I-UPFs. If CN Tunnel Info of two I-UPFs is allocated by the UPFs in step 2b, the SMF also provides the DL CN Tunnel Info of two I-UPFs to the UPF (PSA). If the QoS Monitoring is enabled for the QoS Flow, the SMF provides the N4 rules containing the QoS Monitoring policy generated according to the information received in step 1b to the UPF via the N4 Session Modification Request message. If port number and a Port Management Information Container have been received from PCF in Step 2 and the port number matches the port number of the NW-TT port for this PDU session, then SMF includes the Port Management Information Container in the N4 Session Modification Request. If the N4 Session Modification Request includes a Port Management Information Container, then UPF also includes a Port Management Information Container in the N4 Session Modification Response. If SMF decides to enable ECN marking for L4S by PSA UPF, a QoS Flow level ECN marking for L4S indicator shall be sent by SMF to PSA UPF over N4 as described in clause 5.37.3.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the N2 SM information includes the PDU Set Based Handling Support Indication, SMF configures PSA UPF to activate PDU set identification and marking for the QoS flow as described in clause 5.37.5.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 9. The UE acknowledges the PDU Session Modification Command by sending a NAS message (PDU Session ID, N1 SM container (PDU Session Modification Command Ack, [Port Management Information Container])) message. 10. The (R)AN forwards the NAS message to the AMF. 11. The AMF forwards the N1 SM container (PDU Session Modification Command Ack) and User Location Information received from the AN to the SMF via Nsmf_PDUSession_UpdateSMContext service operation. The SMF replies with a Nsmf_PDUSession_UpdateSMContext Response. If the SMF initiated modification is to delete QoS Flows (e.g. triggered by PCF) which do not include QoS Flow associated with the default QoS rule and the SMF does not receive response from the UE, the SMF marks that the status of those QoS Flows is to be synchronized with the UE. If interworking with TSN deployed in the transport network is supported, for any QoS Flow including a TSC Assistance Container, the SMF/CUC derives the merged stream requirements as described in Annex M of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If AN-TL and CN-TL are supported, the SMF/CUC uses the information provided in the get-responses stored during the PDU Session Establishment procedure to derive the merged stream requirements. The SMF/CUC interacts with the CNC deployed in the transport network and provides the merged stream requirements in the Talker and Listener groups to the TN CNC. The TN CNC uses the merged stream requirements as input to select respective path(s) and calculate schedules in TN. Based on the processing results, the TN CNC provides a Status group that contains the merged end station communication-configuration back to the SMF/CUC. 12. The SMF may update N4 session of the UPF(s) that are involved by the PDU Session Modification by sending N4 Session Modification Request (N4 Session ID) message to the UPF. For a PDU Session of Ethernet PDU Session Type, the SMF may notify the UPF to add or remove Ethernet Packet Filter Set(s) and forwarding rule(s). NOTE 5: The UPFs that are impacted in the PDU Session Modification procedure depends on the modified QoS parameters and on the deployment. For example in the case of the session AMBR of a PDU Session with an UL CL changes, only the UL CL is involved. This note also applies to the step 8. 13. If the SMF interacted with the PCF in step 1b or 2, the SMF notifies the PCF whether the PCC decision could be enforced or not by performing an SMF initiated SM Policy Association Modification procedure as defined in clause 4.16.5.1. If the trigger for 5GS Bridge/Router information available is armed and the SMF received a Port Management Information Container from either UE or UPF, then SMF provides the Port Management Information Container and the port number of the related port to the PCF in this step, as described in clause 5.28.3.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the trigger for 5GS Bridge/Router information available is armed and the SMF received the User Plane node Management Information Container from UPF, then the SMF provides the User Plane node Management Information Container to the PCF as described in clause 5.28.3.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If trigger for Notification on BAT offset is armed and the SMF received BAT offset and/or Periodicity from the RAN, then the SMF provides the BAT offset and/or Periodicity to the PCF as described in clause 5.27.2.5 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. SMF notifies any entity that has subscribed to User Location Information related with PDU Session change. If step 1b is triggered to perform Application Function influence on traffic routing by step 5 in clause 4.3.6.2, the SMF may reconfigure the User Plane of the PDU Session as described in step 6 in clause 4.3.6.2. If interworking with TSN deployed in the transport network is supported and if the Status group from TN CNC to SMF/CUC in step 11 includes InterfaceConfiguration and if the AN-TL/CN-TL are supported, the SMF/CUC initiates a PDU Session Modification procedure as in step 1d.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.3.3.2

5.4.5 DRX (Discontinuous Reception) framework

The 5G System supports DRX architecture which allows Idle mode DRX cycle is negotiated between UE and the AMF. The Idle mode DRX cycle applies in CM-IDLE state and in CM-CONNECTED with RRC_INACTIVE state. If the UE wants to use UE specific DRX parameters, the UE shall include its preferred values consistently in every Initial Registration and Mobility Registration procedure separately for NR/WB-EUTRA and NB-IoT. During Initial Registration and Mobility Registration procedures performed on NB-IoT cells, the normal 5GS procedures apply. For NB-IoT, the cell broadcasts an indication of support of UE specific DRX for NB-IoT in that cell, and the UE can request UE specific DRX for NB-IoT in the Registration procedure irrespective of whether the cell broadcasts that support indication. The AMF shall determine Accepted DRX parameters based on the received UE specific DRX parameters and the AMF should accept the UE requested values, but subject to operator policy the AMF may change the UE requested values. The AMF shall respond to the UE with the Accepted DRX parameters separately for NR/WB-EUTRA and NB-IoT. For details of DRX parameters, see TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [28] and TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [51]. The UE shall apply the DRX cycle broadcast in the cell by the RAN unless it has received Accepted DRX parameters for the RAT from the AMF and for NB-IoT the cell supports UE specific DRX for NB-IoT, in which case the UE shall apply either the DRX cycle broadcast in the cell or the Accepted DRX parameters for the RAT, as defined in TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [50] and TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [52]. The Periodic Registration procedure does not change the UE's DRX settings. In CM-CONNECTED with RRC_INACTIVE state, the UE applies either the DRX cycle negotiated with AMF, or the DRX cycle broadcast by RAN or the UE specific DRX cycle configured by RAN, as defined in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27] and TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [50].

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.4.5

4.3.2.3a 128-bit circuit-switched GSM ciphering key

The ME and the network may derive and store a 128-bit circuit-switched GSM ciphering key or GSM Kc128 from an established UMTS security context. If the GSM Kc128 exists, then it is also part of the UMTS security context. The ME with a USIM in use shall compute a new GSM Kc128 using the UMTS ciphering key and the UMTS integrity key from an established UMTS security context as specified in 3GPP TS 33.102[ 3G security; Security architecture ] [5a]. The new GSM Kc128 shall be stored only in the ME. The ME shall overwrite the existing GSM Kc128 with the new GSM Kc128. The ME shall delete the GSM Kc128 at switch off, when the USIM is disabled as well as under the conditions identified in the subclause 4.1.2.2 and 4.3.2.4. The ME with a USIM in use shall apply the GSM Kc128 when in A/Gb mode an A5 ciphering algorithm that requires a 128-bit ciphering key is taken into use. The network shall compute the GSM Kc128 using the UMTS integrity key and the UMTS ciphering key from an established UMTS security context as specified in 3GPP TS 33.102[ 3G security; Security architecture ] [5a] only when in A/Gb mode an A5 ciphering algorithm that requires a 128-bit ciphering key is to be used.

3GPP TS 24.008

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

CT WG1

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

4.3.2.3a

6.6.3.3A Additional spurious emissions for CA

These requirements are specified in terms of an additional spectrum emission requirement. Additional spurious emission requirements are signalled by the network to indicate that the UE shall meet an additional requirement for a specific deployment scenario as part of the cell reconfiguration message. NOTE: For measurement conditions at the edge of each frequency range, the lowest frequency of the measurement position in each frequency range should be set at the lowest boundary of the frequency range plus MBW/2. The highest frequency of the measurement position in each frequency range should be set at the highest boundary of the frequency range minus MBW/2. MBW denotes the measurement bandwidth defined for the protected band.

3GPP TS 36.101

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

RAN4

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

6.6.3.3A

6.10.3A Demodulation reference signals associated with EPDCCH, MPDCCH, or SPDCCH

The demodulation reference signal associated with EPDCCH/MPDCCH/SPDCCH - is transmitted on the same antenna port as the associated EPDCCH/MPDCCH/SPDCCH physical resource; - is present and is a valid reference for EPDCCH/MPDCCH/SPDCCH demodulation only if the EPDCCH/MPDCCH/SPDCCH transmission is associated with the corresponding antenna port; - is transmitted only on the physical resource blocks upon which the corresponding EPDCCH/MPDCCH/SPDCCH is mapped. A demodulation reference signal associated with EPDCCH/MPDCCH/SPDCCH is not transmitted in resource elements in which one of the physical channels or physical signals other than the demodulation reference signals defined in 6.1 are transmitted using resource elements with the same index pair regardless of their antenna port .

3GPP TS 36.211

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

RAN1

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

6.10.3A

8.2.3.3 Intra-CU topology adaptation procedure in NSA using SCG SRB (SRB3)

This procedure is used when the migrating IAB-MT moves from source parent node to target parent node within the same IAB-donor-CU, when SCG SRB (SRB3) is available for IAB-node during EN-DC operation. The target parent node may use a different IAB-donor-DU than the source parent node. The source path may have common nodes with the target path. The procedure is the same as intra-CU topology adaptation procedure in SA scenario as defined in clause 8.2.3.1 but the UE CONTEXT SETUP REQUEST message includes CG-ConfigInfo in step 3.

3GPP TS 38.401

NG-RAN; Architecture description

RAN3

3GPP Series : 38 , Radio technology beyond LTE

8.2.3.3

5.4.8 Support for identification and restriction of using unlicensed spectrum

Support for NG-RAN using unlicensed spectrum is defined in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27] and TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [30]. For NG-RAN, in the case of NR in stand-alone mode, all cells are in unlicensed spectrum and the NR is used as primary RAT. NR or E-UTRA cells in unlicensed spectrum, can be used as secondary cells as specified in the Dual Connectivity architecture defined in clause 5.11 or in addition can be configured to support the Carrier Aggregation Architecture (CA) defined in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27] and TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [30]. For either case the serving PLMN can enforce Access Restriction for Unlicensed Spectrum (either signalled from the UDM, or, locally generated by VPLMN policy in the AMF) with the following: - To restrict the use of NR in unlicensed spectrum as primary RAT, the AMF rejects the UE Registration procedure with appropriate cause code defined in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47] if the UE performs initial access from NR using unlicensed spectrum. If the UE is accessing through some other allowed RAT, the AMF signals this access restriction to NG-RAN as part of Mobility Restriction List. - To restrict the use of use of unlicensed spectrum with NR or E-UTRA as secondary RAT using Dual Connectivity or Carrier Aggregation Architecture (CA) defined in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27] and TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [30], the AMF signals this access restriction to NG-RAN as part of Mobility Restriction List. An NG-RAN node supporting aggregation with unlicensed spectrum using either NR or E-UTRA checks whether the UE is allowed to use unlicensed spectrum based on received Mobility Restriction List. If the UE is not allowed to use Unlicensed Spectrum, the NG-RAN node shall restrict the using of unlicensed spectrum, either NR or E-UTRA as secondary RATs when using either Dual Connectivity or Carrier Aggregation (CA) as defined in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27] and TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [30]. At inter-RAT handover from E-UTRAN/EPS, the Access Restriction for Unlicensed Spectrum is either already in the AMF's UE context, or is obtained from the UDM during the subsequent Registration Area Update procedure (i.e. not from the source MME or source RAN). In both inter-RAT handover cases, any Access Restriction for use of Unlicensed Spectrum is then signalled to NG-RAN or enforced in AMF. NOTE: This signalling of the Access Restriction during the Registration Area Update after the inter-RAT handover procedure means that there is a small risk that unlicensed spectrum resources are transiently allocated. When the UE is accessing 5GS using unlicensed spectrum as primary RAT: - The NG-RAN node shall provide an indication to the AMF in N2 interface that NR access is using unlicensed spectrum as defined in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [34]. - In order to restrict access to NR in unlicensed spectrum, cells supporting NR in unlicensed spectrum have to be deployed in Tracking Area(s) different to cells supporting licensed spectrum. - When the AMF receives an indication from NG-RAN over N2 whether NR in unlicensed spectrum is being used as defined in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [34], the AMF provides to the SMF an indication that the RAT type is NR with usage of unlicensed spectrum during PDU Session Establishment or as part of the UP activation and Handover procedures. - The PCF will also receive the indication whether the UE is using NR in unlicensed spectrum, when applicable, from the SMF during SM Policy Association Establishment or SM Policy Association Modification procedure. - The NFs generating CDRs shall include the indication that the UE is using NR in unlicensed spectrum in their CDRs. When the UE is accessing NR or E-UTRA using unlicensed spectrum as secondary RAT, procedures for Usage Data Reporting for Secondary RAT as defined in clause 5.12.2 can apply.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.4.8

3.4 Mobile Station Roaming Number (MSRN) for PSTN/ISDN routeing

The Mobile Station Roaming Number (MSRN) is used to route calls directed to an MS. On request from the Gateway MSC via the HLR it is temporarily allocated to an MS by the VLR with which the MS is registered; it addresses the Visited MSC collocated with the assigning VLR. More than one MSRN may be assigned simultaneously to an MS. The MSRN is passed by the HLR to the Gateway MSC to route calls to the MS. The Mobile Station Roaming Number for PSTN/ISDN routing shall have the same structure as international E.164 numbers in the area in which the roaming number is allocated, i.e.: - the country code of the country in which the visitor location register is located; - the national destination code of the visited PLMN or numbering area; - a subscriber number with the appropriate structure for that numbering area. The MSRN shall not be used for subscriber dialling. It should be noted that the MSRN can be identical to the MSISDN (clause 3.3) in certain circumstances. In order to discriminate between subscriber generated access to these numbers and re-routeing performed by the network, re-routeing or redirection indicators or other signalling means should be used, if available.

3GPP TS 23.003

Numbering, addressing and identification

CT WG4

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

3.4

– FeatureSetDownlinkPerCC

The IE FeatureSetDownlinkPerCC indicates a set of features that the UE supports on the corresponding carrier of one band entry of a band combination. FeatureSetDownlinkPerCC information element -- ASN1START -- TAG-FEATURESETDOWNLINKPERCC-START FeatureSetDownlinkPerCC ::= SEQUENCE { supportedSubcarrierSpacingDL SubcarrierSpacing, supportedBandwidthDL SupportedBandwidth, channelBW-90mhz ENUMERATED {supported} OPTIONAL, maxNumberMIMO-LayersPDSCH MIMO-LayersDL OPTIONAL, supportedModulationOrderDL ModulationOrder OPTIONAL } FeatureSetDownlinkPerCC-v1620 ::= SEQUENCE { -- R1 16-2a: Mulit-DCI based multi-TRP multiDCI-MultiTRP-r16 MultiDCI-MultiTRP-r16 OPTIONAL, -- R1 16-2b-3: Support of single-DCI based FDMSchemeB supportFDM-SchemeB-r16 ENUMERATED {supported} OPTIONAL } FeatureSetDownlinkPerCC-v1700 ::= SEQUENCE { supportedMinBandwidthDL-r17 SupportedBandwidth-v1700 OPTIONAL, broadcastSCell-r17 ENUMERATED {supported} OPTIONAL, -- R1 33-2g: MIMO layers for multicast PDSCH maxNumberMIMO-LayersMulticastPDSCH-r17 ENUMERATED {n2, n4, n8} OPTIONAL, -- R1 33-2h: Dynamic scheduling for multicast for SCell dynamicMulticastSCell-r17 ENUMERATED {supported} OPTIONAL, supportedBandwidthDL-v1710 SupportedBandwidth-v1700 OPTIONAL, -- R4 24-1/24-2/24-3/24-4/24-5 supportedCRS-InterfMitigation-r17 CRS-InterfMitigation-r17 OPTIONAL } FeatureSetDownlinkPerCC-v1720 ::= SEQUENCE { -- R1 33-2j: Supported maximum modulation order used for maximum data rate calculation for multicast PDSCH maxModulationOrderForMulticastDataRateCalculation-r17 ENUMERATED {qam64, qam256, qam1024} OPTIONAL, -- R1 33-1-2: FDM-ed unicast PDSCH and group-common PDSCH for broadcast fdm-BroadcastUnicast-r17 ENUMERATED {supported} OPTIONAL, -- R1 33-3-2: FDM-ed unicast PDSCH and one group-common PDSCH for multicast fdm-MulticastUnicast-r17 ENUMERATED {supported} OPTIONAL } FeatureSetDownlinkPerCC-v1730 ::= SEQUENCE { -- R1 33-3-3: Intra-slot TDM-ed unicast PDSCH and group-common PDSCH intraSlotTDM-UnicastGroupCommonPDSCH-r17 ENUMERATED {yes, no} OPTIONAL, -- R1 33-5-3: One SPS group-common PDSCH configuration for multicast for SCell sps-MulticastSCell-r17 ENUMERATED {supported} OPTIONAL, -- R1 33-5-4: Up to 8 SPS group-common PDSCH configurations per CFR for multicast for SCell sps-MulticastSCellMultiConfig-r17 INTEGER (1..8) OPTIONAL, -- R1 33-1-1: Dynamic slot-level repetition for broadcast MTCH dci-BroadcastWith16Repetitions-r17 ENUMERATED {supported} OPTIONAL } FeatureSetDownlinkPerCC-v1800 ::= SEQUENCE { -- R1 40-2-1: Basic feature for multi-DCI based intra-cell Multi-TRP operation with two TA enhancement multiDCI-IntraCellMultiTRP-TwoTA-r18 ENUMERATED {supported} OPTIONAL, -- R1 40-2-2: Basic feature for multi-DCI based inter-cell Multi-TRP operation with two TA enhancement multiDCI-InterCellMultiTRP-TwoTA-r18 INTEGER (1..2) OPTIONAL, -- R1 40-2-6: Rx timing difference larger than CP length rxTimingDiff-r18 ENUMERATED {supported} OPTIONAL, -- R1 55-7: Two QCL TypeD for CORESET monitoring in multi-DCI based multi-TRP multiDCI-MultiTRP-CORESET-Monitoring-r18 ENUMERATED {supported} OPTIONAL, broadcastNonServingCell-r18 ENUMERATED {supported} OPTIONAL } MultiDCI-MultiTRP-r16 ::= SEQUENCE { maxNumberCORESET-r16 ENUMERATED {n2, n3, n4, n5}, maxNumberCORESETPerPoolIndex-r16 INTEGER (1..3), maxNumberUnicastPDSCH-PerPool-r16 ENUMERATED {n1, n2, n3, n4, n7} } CRS-InterfMitigation-r17 ::= SEQUENCE { -- R4 24-1 CRS-IM (Interference Mitigation) in DSS scenario crs-IM-DSS-15kHzSCS-r17 ENUMERATED {supported} OPTIONAL, -- R4 24-2 CRS-IM in non-DSS and 15 kHz NR SCS scenario, without the assistance of network signaling on LTE channel bandwidth crs-IM-nonDSS-15kHzSCS-r17 ENUMERATED {supported} OPTIONAL, -- R4 24-3 CRS-IM in non-DSS and 15 kHz NR SCS scenario, with the assistance of network signaling on LTE channel bandwidth crs-IM-nonDSS-NWA-15kHzSCS-r17 ENUMERATED {supported} OPTIONAL, -- R4 24-4 CRS-IM in non-DSS and 30 kHz NR SCS scenario, without the assistance of network signaling on LTE channel bandwidth crs-IM-nonDSS-30kHzSCS-r17 ENUMERATED {supported} OPTIONAL, -- R4 24-5 CRS-IM in non-DSS and 30 kHz NR SCS scenario, with the assistance of network signaling on LTE channel bandwidth crs-IM-nonDSS-NWA-30kHzSCS-r17 ENUMERATED {supported} OPTIONAL } -- TAG-FEATURESETDOWNLINKPERCC-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

10.0.1.2 Frame structure type 2

Frame structure type 2 is applicable to TDD operation only. The following restrictions apply: - Uplink-downlink configuration 0 and 6 are not supported. - UpPTS is not used for NPUSCH or NPRACH. - DwPTS and UpPTS in special subframe configuration 10 is not used for transmissions. - On an NB-IoT carrier for which higher-layer parameter operationModeInfo indicates inband-SamePCI or inband-DifferentPCI, or higher-layer parameter inbandCarrierInfo is present, or on an NB-IoT carrier for SystemInformationBlockType1-NB for which sib1-carrierInfo indicates non-anchor and the value of the higher layer parameter sib-GuardbandInfo is set to sib-GuardbandInbandSamePCI or sib-GuardbandinbandDiffPCI, DwPTS in special subframe configuration 0 and 5 for normal cyclic prefix is not used for NPDCCH and NPDSCH transmission, in addition when npdsch-16QAM-Config-r17 is configured DwPTS in special subframe configuration 9 for normal cyclic prefix is not used for NPDSCH transmission with 16QAM. - Higher-layer parameter symbolBitmap does not apply to special subframes.

3GPP TS 36.211

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

RAN1

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

10.0.1.2

7.5.1A Minimum requirements for CA

For inter-band carrier aggregation with one component carrier per operating band and the uplink assigned to one E-UTRA band, the adjacent channel requirements are defined with the uplink active on the band(s) other than the band whose downlink is being tested. The UE shall meet the requirements specified in subclause 7.5.1 for each component carrier while all downlink carriers are active. For E-UTRA CA configurations including an operating band without uplink operation or an operating band with an unpaired DL part (as noted in Table 5.5-1), the requirements for all downlinks shall be met with the single uplink carrier active in each band capable of UL operation. For a component carrier configured in Band 46 or Band 49, the requirements specified in subclause 7.5.1 are replaced by the requirements in Table 7.5.1A-0a with test parameters in Table 7.5.1A-0b and Table 7.5.1A-0c. Table 7.5.1A-0a: Adjacent channel selectivity Table 7.5.1A-0b: Test parameters for Adjacent channel selectivity, Case 1 Table 7.5.1A-0c: Test parameters for Adjacent channel selectivity, Case 2 For E-UTRA CA configurations listed in Table 7.3.1A-0a under conditions for which reference sensitivity for the operating band being tested is N/A, the adjacent channel requirements of subclause 7.5.1A do not apply. For intra-band contiguous carrier aggregation the downlink SCC(s) shall be configured at nominal channel spacing to the PCC. For FDD, the PCC shall be configured closest to the uplink band. All downlink carriers shall be active throughout the test. The uplink output power shall be set as specified in Table 7.5.1A-2 and Table -3 with the uplink configuration set according to Table 7.-1 for the applicable carrier aggregation configuration. For UE(s) supporting one uplink carrier, the uplink configuration of the PCC shall be in accordance with Table 7.3.1-2. The UE shall fulfil the minimum requirement specified in Table -1 for an adjacent channel interferer on either side of the aggregated downlink signal at a specified frequency offset and for an interferer power up to -25 dBm. The throughput of each carrier shall be ≥ 95% of the maximum throughput of the reference measurement channels as specified in Annexes , A.2.3 and A.3.2 (with one sided dynamic OCNG Pattern OP.1 FDD/TDD for the DL-signal as described in Annex /A.5.2.1) with parameters specified in Tables 7.5.1A-2 and 7.5.1A-3. For operating bands with an unpaired DL part (as noted in Table 5.5-1), the requirements also apply for an SCC assigned in the unpaired part with parameters specified in Tables 7.5.1A-2 and 7.5.1A-3. For intra-band non-contiguous carrier aggregation with one uplink carrier and two or more downlink sub-blocks, each larger than or equal to 5 MHz, the adjacent channel selectivity requirements are defined with the uplink configuration in accordance with Table 7.3.1A-3. For this uplink configuration, the UE shall meet the requirements for each sub-block as specified in subclauses 7.5.1 and 7.5.1A for one component carrier and two component carriers per sub-block, respectively. The UE shall fulfil the minimum requirements all values of a single adjacent channel interferer in-gap and out-of-gap up to a –25 dBm interferer power while all downlink carriers are active. For the lower range of test parameters (Case 1), the interferer power Pinterferer shall be set to the maximum of the levels given by the carriers of the respective sub-blocks as specified in Table 7.5.1-2 and Table 7.5.1A-2 for one component carrier and two component carriers per sub-block, respectively. The wanted signal power levels for the carriers of each sub-block shall then be adjusted relative to Pinterferer in accordance with the ACS requirement for each sub-block (Table 7.5.1-1 and Table 7.5.1A-1). For the upper range of test parameters (Case 2) for which the interferer power Pinterferer is -25 dBm (Table 7.5.1-3 and Table 7.5.1A-3) the wanted signal power levels for the carriers of each sub-block shall be adjusted relative to Pinterferer like for Case 1. Table -1: Adjacent channel selectivity Table -2: Test parameters for Adjacent channel selectivity, Case 1 Table 7.5.1A-3: Test parameters for Adjacent channel selectivity, Case 2 For combinations of intra-band and inter-band carrier aggregation and one uplink carrier assigned to one E-UTRA band, the requirement is defined with the uplink active in each band other than that supporting the downlink(s) under test. The uplink configuration shall be in accordance with Table 7.3.1A-3 when the uplink is active in the band supporting two or more non-contiguous component carriers, Table 7.3.1A-1 when the uplink is active in a band supporting two contiguous component carriers and in accordance with Table 7.3.1-2 when the uplink is active in a band supporting one carrier per band. The downlink PCC shall be configured closer to the uplink operating band than the downlink SCC(s) when the uplink is active in band(s) supporting contiguous aggregation. For these uplink configurations, the UE shall meet the adjacent channel selectivity requirements for intra-band non-contiguous carrier aggregation with RIBNC = 0 dB for all sub-block gaps (Table 7.3.1A-3) for the two or more non-contiguous downlink sub-blocks, the requirements for intra-band contiguous carrier aggregation for the contiguously aggregated downlink carriers and for any remaining component carrier(s) the requirements specified in subclause 7.5.1. For contiguously aggregated component carriers configured in Band 46, the said requirements for intra-band contiguous carrier aggregation of downlink carriers are replaced by requirements in Table 7.5.1A-4 with test parameters in Table 7.5.1A-5 and Table 7.5.1A-6. For non-contiguously aggregated component carriers configured in Band 46, the said requirements are applied to each sub-block for in-gap and out-of-gap interferers. For the sub-block with a single component carrier, the requirement is replaced by Table 7.5.1A-0a with test parameters in Table 7.5.1A-0b and Table 7.5.1A-0c. For the sub-block with two or more contiguous component carriers, the requirement is replaced by Table 7.5.1A-4 with test parameters in Table 7.5.1A-5 and Table 7.5.1A-6. All downlink carriers shall be active throughout the tests and the requirements for downlinks shall be met with the single uplink carrier active in each band capable of UL operation. Table -4: Adjacent channel selectivity Table -5: Test parameters for Adjacent channel selectivity, Case 1 Table 7.5.1A-6: Test parameters for Adjacent channel selectivity, Case 2

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

7.5.1A

6.3.16 SCP discovery and selection

An NF is configured with its serving SCP(s). In a deployment where several SCPs are deployed, a message may traverse several SCP instances until reaching its final destination. A SCP may discover and select a next hop SCP by querying the Nnrf_NFDiscovery Service of the NRF or it may be configured with next SCP in the message path. An SCP may use the SCP profile parameters in clause 6.2.6.3 as discovery parameters in Nnrf_NFDiscovery. The parameter(s) to be used depend(s) on network deployment. The NRF returns a list SCP Profiles as per the provided discovery parameters. If an SCP receives a Routing Binding Indication within a service or notification request and decides to forward that request to a next-hop SCP, it shall include the Routing Binding Indication in the forwarded request. NOTE: It is up to SCP implementation, deployment specific configuration and operator policies as to how the SCP will use information retrieved from the NRF to resolve the optimal route to a producer. Based on SCP configuration, an SCP deciding to address a next-hop SCP for a service request may then delegate the NF (instance) and/or service (instance) selection to subsequent SCPs and provide discovery and selection parameters to the next-hop SCP.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

6.3.16

23.3.2.3 Multi-vendor eNodeB Plug-and Play Vendor-Specific OAM System 23.3.2.3.1 General

This clause describes the Fully Qualified Domain Names (FQDNs) used in Multi Vendor Plug and Connect (MvPnC) procedures (see 3GPP TS 32.508[ Telecommunication management; Procedure flows for multi-vendor plug-and-play eNode B connection to the network ] [102]). The FQDNs used in MvPnC shall be in the form of an Internet domain name and follow the general encoding rules specified in clause 19.4.2.1. The format of FQDNs used in MvPnC shall follow the "<vendor ID>.<system>.<OAM realm>" pattern. NOTE: "<vendor ID>.<system>.oam" represents the <service_id> shown in the first row of table E.1. The <vendor ID> label is optional and is only used in the operator deployments where multiple instances of a particular network entity type are not provided by the same vendor. If present, the <vendor ID> label shall be in the form "vendor<ViD>", where <ViD> field corresponds to the ID of the vendor. The format of the ViD is vendor specific. The details of the <system> label are specified in the clauses below.

3GPP TS 23.003

Numbering, addressing and identification

CT WG4

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

23.3.2.3

5.2.7.2.6 Nnrf_NFManagement_NFStatusNotify service operation

Service Operation name: Nnrf_NFManagement_NFStatusNotify. Description: NRF notifies subscribed consumers of the following: - Newly registered NF along with its NF services. - Updated NF profile. - Deregistered NF. Inputs, Required: Notification Event type; NF instance ID; for newly registered NF, NF profile; for updated NF, NF profile or NF profile changes. NOTE: See clause 6.1.6.3.6 of TS 29.510[ 5G System; Network function repository services; Stage 3 ] [37] for the detailed use of Notification Event type. Inputs, Optional: None. Outputs, Required: None. Outputs, Optional: None.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

5.2.7.2.6

10.5.3.2 Authentication Response parameter

The purpose of the authentication response parameter information element is to provide the network with the authentication response calculated in the SIM/USIM. The Authentication Parameter SRES information element is coded as shown in figure 10.5.76/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and tables 10.5.90 a & b /3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The Authentication Response Parameter is a type 3 information element with 5 octets length. In a GSM authentication challenge, the response calculated in the SIM/USIM (SRES) is 4 bytes in length, and is placed in the Authentication Response Parameter information element. In a UMTS authentication challenge, the response calculated in the USIM (RES) may be up to 16 octets in length. The 4 most significant octets shall be included in the Authentication Response Parameter information element. The remaining part of the RES shall be included in the Authentication Response Parameter (extension) IE (see subclause 10.5.3.2.1) Figure 10.5.76/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Authentication Response Parameter information element Table 10.5.90a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Authentication Response Parameter information element (SRES) (GSM authentication challenge only) Table 10.5.90b/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Authentication Response Parameter information element (RES) (UMTS authentication challenge only)

3GPP TS 24.008

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

CT WG1

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

10.5.3.2

17.6.5 Re-Auth-Request Command

The Re-Auth-Request (RAR) command, defined in IETF RFC 6733 (DIAMETER BASE) [111], is indicated by the Command-Code set to 258 and the message flags’ ‘R’ bit set. The relevant AVPs that are of use for the Gmb interface are detailed in the ABNF description below. Other valid AVPs for this command are not used for Gmb purposes and should be ignored by the receiver or processed according to the relevant specifications. The bold marked AVPs in the message format indicate new optional AVPs for Gmb, or modified existing AVPs. Message Format: <RAR> ::= < Diameter Header: 258, REQ, PXY > < Session-Id > { Origin-Host } { Origin-Realm } { Destination-Realm } { Destination-Host } { Auth-Application-Id } { Re-Auth-Request-Type } [ Called-Station-Id ] [ Framed-IP-Address] [ Framed-IPv6-Prefix ] [ Framed-Interface-Id ] [ MBMS-StartStop-Indication ] [ MBMS-Service-Area ] [ MBMS-Required-QoS ] [ MBMS-Session-Duration ] [ MBMS-Service-Type ] [ MBMS-Counting-Information ] [ MBMS-Session-Identity ] [ MBMS-Session-Repetition-number ] [ TMGI ] * [ 3GPP-SGSN-Address ] ; broadcast case only * [ 3GPP-SGSN-IPv6-Address ] ; broadcast case only [ MBMS-2G-3G-Indicator ] [ MBMS-Time-To-Data-Transfer ] [ MBMS-User-Data-Mode-Indication ] [ MBMS-BMSC-SSM-IP-Address ] [ MBMS-BMSC-SSM-IPv6-Address ] [ MBMS-Flow-Identifier ] [ CN-IP-Multicast-Distribution ] [ MBMS-HC-Indicator ] [ Origin-State-Id ] * [ Proxy-Info ] * [ Route-Record ] The MBMS-StartStop-Indication AVP will indicate if the command is indicating an MBMS Session Start procedure, an MBMS Session Update procedure or an MBMS Session Stop procedure. The Diameter Session-Id is used in subsequent procedures to identify the corresponding MBMS session. In the multicast case, the BM-SC shall use the Diameter Session-Id that was received during the GGSN Registration procedure. In the broadcast case, the BM-SC shall allocate a Diameter Session-Id for the first RAR message that is used for the first MBMS Session Start procedure of the MBMS bearer service. Then this Diameter Session-Id will be used for the subsequent MBMS sessions of the same MBMS bearer service. The BM-SC will create a new Diameter Session-Id for a subsequent Session Start procedure if, in exceptional cases, the Diameter session for the MBMS bearer service has been deleted. BM-SC shall not initiate a new Session Start procedure for a certain MBMS bearer service until the previous MBMS session for that service has been stopped. For the MBMS Session Start procedure, RAR is sent by the BM-SC to the GGSN(s) that will deliver the MBMS service (e.g. in the multicast case these are the GGSNs that have previously registered for the corresponding multicast MBMS bearer service), when it is ready to send data. This is a request to activate all necessary bearer resources in the network for the transfer of MBMS data and to notify interested UEs of the imminent start of the transmission. For broadcast MBMS bearer services the RAR message contains either an IPv4 address or an IPv6 address for each participating SGSN. For the MBMS Session Update procedure, RAR is sent by the BM-SC in order for the GGSN(s) to update their session attributes. The updated MBMS-Service-Area AVP shall be included. The MBMS-StartStop-Indication AVP with the value UPDATE shall be included. The MBMS-Time-To-Data-Transfer with the value set to 0 shall be included. The MBMS-Session-Duration AVP shall be included to indicate the duration of the remaining part of the MBMS session. The 3GPP-SGSN-Address AVP and the 3GPP-SGSN-IPv6-Address AVP shall be included if the related lists of downstream nodes in the GGSN(s) have changed. The other bold marked AVPs shall be included as given by the previous, corresponding MBMS Session Start procedure. For the MBMS Session Stop procedure, RAR is sent by the BM-SC to the GGSN(s) when it considers the MBMS session to be terminated. The session is typically terminated when there is no more MBMS data expected to be transmitted for a sufficiently long period of time to justify a release of bearer plane resources in the network. For the MBMS Session Start procedure, the MBMS-Required-QoS indicates the QoS that is required for the MBMS bearer service for the actual MBMS session. The information of the MBMS-2G-3G-Indicator, the MBMS-Service-Area and the MBMS-Counting-Information is passed from BM-SC transparently through GGSN to the SGSN(s) that are relevant for the actual MBMS bearer service. According to 3GPP TS 23.246[ Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description ] [65], a specific MBMS bearer service is uniquely identified by its IP multicast address and an APN. For the MBMS Session Start procedure for broadcast MBMS bearer services, the following AVPs are included (either IPv4 or IPv6 address) to enable GGSN to relate incoming payload packets to the actual MBMS bearer service and distribute the packets to the downstream SGSNs related to this service: - The Framed-IPv6-Prefix AVP contains the IPv6 prefix of the multicast address. - The Framed-Interface-Id AVP contains the IPv6 interface identifier of the multicast address. - The Framed-IP-Address AVP contains the IPv4 multicast address. - The Called-Station-Id AVP contains the Access Point Name (APN) for which the MBMS bearer service is defined. According to 3GPP TS 23.246[ Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description ] [65], the MBMS-Flow-Identifier is optional, used only for broadcast services with location dependent content. For such services, several sessions with the same TMGI, but different MBMS-Flow-Identifiers, may be going on in parallel. However, at any specific location only one version of the content may be available at any point in time. Hence, the MBMS-Service-Areas of the related MBMS bearer contexts shall not overlap.

3GPP TS 29.061

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

CT WG3

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

17.6.5

D.3 Support for access to PLMN services via Stand-alone Non-Public Network and access to Stand-alone Non Public Network services via PLMN

Figure D.3-1: Access to PLMN services via Stand-alone Non-Public Network NOTE 1: The reference architecture in Figure D.3-1 and Figure D.3-2 only shows the network functions directly connected to the UPF or N3IWF and other parts of the architecture are same as defined in clause 4.2. In order to obtain access to PLMN services when the UE is camping in NG-RAN of Stand-alone Non-Public Network, the UE obtains IP connectivity, discovers and establishes connectivity to an N3IWF in the PLMN. In the Figure D.3-1, the N1 (for NPN) represents the reference point between UE and the AMF in Stand-alone Non-Public Network. The NWu (for PLMN) represents the reference point between the UE and the N3IWF in the PLMN for establishing secure tunnel between UE and the N3IWF over the Stand-alone Non-Public Network. N1 (for PLMN) represents the reference point between UE and the AMF in PLMN. Figure D.3-2: Access to Stand-alone Non-Public Network services via PLMN In order to obtain access to Non-Public Network services when the UE is camping in NG-RAN of a PLMN, the UE obtains IP connectivity, discovers and establishes connectivity to an N3IWF in the Stand-alone Non-Public Network. In Figure D.3-2, the N1 (for PLMN) represents the reference point between UE and the AMF in the PLMN. The NWu (for NPN) represents the reference point between the UE and the N3IWF in the stand-alone Non-Public Network for establishing a secure tunnel between UE and the N3IWF over the PLMN. The N1 (for NPN) represents the reference point between UE and the AMF in NPN. When using the mechanism described above to access overlay network via underlay network, the overlay network can act as authorized 3rd party with AF to interact with NEF in the underlay network, to use the existing network exposure capabilities provided by the underlay network defined in clause 4.15 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. This interaction is subject of agreements between the overlay and the underlay network.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

D.3

6.3.24 TSCTSF Discovery

The NFs (e.g. NEF, AF and PCF) may utilize the NRF to discover TSCTSF instance(s) unless TSCTSF information is available by other means, e.g. locally configured in the requested NF. The following factors may be considered for TSCTSF discovery and selection: - DNN and S-NSSAI. When the NF discovers the TSCTSF for a DNN/S-NSSAI, the NRF provides the NF with NF profile(s) of TSCTSF instance(s) belonging to single TSCTSF Set for a given DNN/S-NSSAI. For example, the same TSCTSF Set shall be selected by the PCF serving PDU Sessions for this DNN and S-NSSAI to notify the TSCTSF for a PDU Session that is potentially impacted by the (g)PTP time synchronization service. - GPSI or External Group Identifier. TSCTSF NF consumers (which manage network signalling not based on SUPI/SUCI (e.g. the NEF)) select a TSCTSF instance based on the GPSI or External Group ID range the UE's GPSI or External Group ID belongs to or based on the results of a discovery procedure with NRF using the UE's GPSI or External Group ID as input for TSCTSF discovery. - SUPI or Internal Group ID. TSCTSF NF consumers select a TSCTSF instance based on the SUPI range the UE's SUPI belongs to or based on the results of a discovery procedure with NRF using the UE's SUPI or Internal Group ID as input for TSCTSF discovery. If the TSCTSF is locally configured in NFs, it shall be ensured that the same TSCTSF Set is configured in all NFs (e.g. NEF, AF and PCF) for the given DNN and S-NSSAI. NOTE: Thus, it is assumed that there is only one TSCTSF Set for a given DNN/S-NSSAI in this Release of the specification.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

6.3.24

4.15.3.2.4 Exposure with bulk subscription

Based on operator configuration NEF may perform bulk subscription with the NFs that provides necessary services. This feature is controlled by local policies of the NEF that control which events (set of Event ID(s)) and UE(s) are target of a bulk subscription. When the NEF performs bulk subscription (subscribes for any UE (i.e. all UEs), group of UE(s) (e.g. identifying a certain type of UEs such as IoT UEs)), it subscribes to all the NFs that provide the necessary services (e.g. In a given PLMN, NEF may subscribe to all AMFs that support reachability notification for IoT UEs). Upon receiving bulk subscription from the NEF, the NFs store this information. Whenever the corresponding event(s) occur for the requested UE(s) as in bulk subscription request, NFs notify the NEF with the requested information. The following call flow shows how network exposure can happen for one UE, groups of UE(s) (e.g. identifying a certain type of UEs such as IoT UEs) or any UE. Figure 4.15.3.2.4-1: NF registration/status notification and Exposure with bulk subscription 1. NEF registers with the NRF for any newly registered NF along with its NF services. 2. When an NF instantiates, it registers itself along with the supported NF services with the NRF. 3. NRF acknowledges the registration 4. NRF notifies the NEF with the newly registered NF along with the supported NF services. 5. NEF evaluates the NF and NF services supported against the pre-configured events within NEF. Based on that, NEF subscribes with the corresponding NF either for a single UE, group of UE(s) (e.g. identifying a certain type of UEs such as IoT UEs), any UE. NF acknowledges the subscription with the NEF. 6 - 7. When the event trigger happens, NF notifies the requested information towards the subscribing NEF along with the time stamp. NEF may store the information in the UDR along with the time stamp using either Nudr_DM_Create or Nudr_DM_Update service operation as appropriate. 8. Application registers with the NEF for a certain event identified by event filters. If the registration for the event is authorized by the NEF, the NEF records the association of the event and the requester identity. 9 - 10. When the event trigger happens, NF notifies the requested information towards the subscribing NEF. NEF may store the information in the UDR using either Nudr_DM_Create or Nudr_DM_Update service operation as appropriate. 11a-b. NEF reads from UDR with Nudr_DM_Query and notifies the application along with the time stamp for the corresponding subscribed events.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.15.3.2.4

8.13.3.7.1 Minimum Requirement for FDD PCell

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

3GPP TS 36.101

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

RAN4

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

8.13.3.7.1

6.1.2A.2 IP address allocation via NAS signalling

The MS shall set the PDP type in the PDP address IE in the ACTIVATE PDP CONTEXT REQUEST message when requesting establishment of a default PDP context; the detailed rules with regards to IP version for MS and network side are defined in subclause 6.1.3.1. If the MS wants to use DHCPv4 for IPv4 address assignment, it shall indicate that to the network within the Protocol Configuration Options IE in the ACTIVATE PDP CONTEXT REQUEST. If the MS requests allocation of an IPv6 address, the network constructs it of two parts: a /64 IPv6 prefix and an interface identifier of 64 bits length. The IPv6 prefix part is not used immediately by the MS; however, the network shall use the same IPv6 prefix in subsequent procedures for IETF-based IP address allocation. The interface identifier is only used for building a unique link-local IPv6 address.

3GPP TS 24.008

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

CT WG1

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

6.1.2A.2

4.3.25.1a UE assisted Dedicated Core Network selection

This feature is to reduce the need for DECOR reroute by using an indication (DCN-ID) sent from the UE and used by RAN to select the correct DCN. The DCN-ID shall be assigned to the UE by the serving PLMN and is stored in the UE per PLMN ID. Both standardized and operator specific values for DCN-ID are possible. The UE shall use the PLMN specific DCN-ID whenever a PLMN specific DCN-ID is stored for the target PLMN. The HPLMN may provision the UE with a single default standardized DCN-ID which shall be used by the UE only if the UE has no PLMN specific DCN-ID of the target PLMN. When a UE configuration is changed with a new default standardized DCN-ID, the UE shall delete all stored PLMN specific DCN-IDs. The UE provides the DCN-ID to RAN at registration to a new location in the network, i.e. in Attach, TAU and RAU. RAN selects serving node (MME or SGSN) based on the DCN-ID provided by the UE and configuration in RAN. For E-UTRAN the eNodeB is configured with DCNs supported by the connected MMEs at the setup of the S1 connection. For UTRAN and GERAN the BSS/RNC is configured with the DCNs supported in the connected SGSN via O&M. Both standardized DCN-IDs and PLMN specific DCN-IDs can in the RAN configuration be assigned to the same network. If information provided by the UE (e.g. GUTI, NRI, etc.) indicates a node (MME or SGSN) for attach/TAU/RAU and a serving node (MME or SGSN) corresponding to the UE information can be found by the RAN node, the normal node selection shall take precedence over the selection based on DCN-ID. At registration the MME/SGSN may check if the correct DCN is selected. The check is performed as specified in clause 4.3.25.1. If the MME/SGSN concludes that the selected DCN is not the correct DCN, a DECOR reroute is performed and the SGSN/MME in the new DCN assigns a new DCN-ID to the UE. The serving MME/SGSN can also assign a new DCN-ID to the UE if e.g. the DCN-ID in the UE has become obsolete or when the UE Usage Type has been updated in the subscription information leading to a change of DCN. This is performed as part of the GUTI Reallocation procedure.

3GPP TS 23.401

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

SA WG2

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

4.3.25.1a

5.4.2 Security mode control procedure 5.4.2.1 General

The purpose of the NAS security mode control procedure is to take a 5G NAS security context into use, and initialise and start NAS signalling security between the UE and the AMF with the corresponding 5G NAS keys and 5G NAS security algorithms. Furthermore, the network may also initiate the security mode control procedure in the following cases: a)- in order to change the 5G NAS security algorithms for a current 5G NAS security context already in use; b) in order to change the value of uplink NAS COUNT used in the latest SECURITY MODE COMPLETE message as described in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24], subclause 6.9.4.4; and c) in order to provide the Selected EPS NAS security algorithms to the UE. For restrictions concerning the concurrent running of a security mode control procedure with other security related procedures in the AS or inside the core network see 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24], subclause 6.9.5. If the security mode control procedure is initiated after successful 5G AKA based primary authentication and key agreement procedure and the security mode control procedure intends to bring into use the partial native 5G NAS security context created by the 5G AKA based primary authentication and key agreement procedure and the UE accepts received security mode command (see subclause 5.4.2.3), the ME shall: a) delete the valid KAUSF and the valid KSEAF, if any; and b) consider the new KAUSF to be the valid KAUSF, and the new KSEAF to be the valid KSEAF, reset the SOR counter and the UE parameter update counter to zero, and store the valid KAUSF, the valid KSEAF, the SOR counter and the UE parameter update counter as specified in annex C and use the valid KAUSF in the verification of SOR transparent container and UE parameters update transparent container, if any are received. NOTE: The AMF does not perform a security mode control procedure when the 5G AKA based primary authentication procedure successfully authenticates a 5G ProSe layer-3 remote UE accessing the network via a 5G ProSe layer-3 UE-to-network relay UE served by the AMF.

3GPP TS 24.501

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

CT WG1

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

5.4.2

5.5E Operating bands for UE category 0, UE category M1 and M2 and UE category 1bis

UE category 0 is designed to operate in the E-UTRA operating bands 2, 3, 4, 5, 8, 13, 20, 25, 26 and 28 in both half duplex FDD mode and full-duplex FDD mode and in bands 39, 40 and 41 in TDD mode. The E-UTRA bands are defined in Table 5.5-1. UE category M1 and M2 is designed to operate in the E-UTRA operating bands 1, 2, 3, 4, 5, 7, 8, 11, 12, 13, 14, 18, 19, 20, 21, 24, 25, 26, 27, 28, 31, 54, 66, 71, 72, 73, 74, 85, 87, 88, 106 in both half duplex FDD mode and full-duplex FDD mode, and in bands 39, 40, 41, 42, 43 and 48 in TDD mode. The E-UTRA bands are defined in Table 5.5-1. UE category 1bis is designed to operate in the E-UTRA operating bands 1, 2, 3, 4, 5, 7, 8, 12, 13, 18, 20, 26, 28, 31, 66 and 72 in full duplex FDD mode and in bands 34, 39, 40 and 41 in TDD mode. The E-UTRA bands are defined in Table 5.5-1

3GPP TS 36.101

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

RAN4

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

5.5E

– EUTRA-MBSFN-SubframeConfigList

The IE EUTRA-MBSFN-SubframeConfigList is used to define an E-UTRA MBSFN subframe pattern (for the purpose of NR rate matching). EUTRA-MBSFN-SubframeConfigList information element -- ASN1START -- TAG-EUTRA-MBSFN-SUBFRAMECONFIGLIST-START EUTRA-MBSFN-SubframeConfigList ::= SEQUENCE (SIZE (1..maxMBSFN-Allocations)) OF EUTRA-MBSFN-SubframeConfig EUTRA-MBSFN-SubframeConfig ::= SEQUENCE { radioframeAllocationPeriod ENUMERATED {n1, n2, n4, n8, n16, n32}, radioframeAllocationOffset INTEGER (0..7), subframeAllocation1 CHOICE { oneFrame BIT STRING (SIZE(6)), fourFrames BIT STRING (SIZE(24)) }, subframeAllocation2 CHOICE { oneFrame BIT STRING (SIZE(2)), fourFrames BIT STRING (SIZE(8)) } OPTIONAL, -- Need R ... } -- TAG-EUTRA-MBSFN-SUBFRAMECONFIGLIST-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

Annex J (informative): High Level ISR description J.1 General description of the ISR concept

Idle state Signalling Reduction (ISR) aims at reducing the frequency of TAU and RAU procedures caused by UEs reselecting between E-UTRAN and GERAN/UTRAN which are operated together. Especially the update signalling between UE and network is reduced. But also network internal signalling is reduced. To some extent the reduction of network internal signalling is also available when ISR is not used or not activated by the network. UMTS described already RAs containing GERAN and UTRAN cells, which also reduces update signalling between UE and network. The combination of GERAN and UTRAN into the same RAs implies however common scaling, dimensioning and configuration for GERAN and UTRAN (e.g. same RA coverage, same SGSN service area, no GERAN or UTRAN only access control, same physical node for GERAN and UTRAN). As an advantage it does not require special network interface functionality for the purpose of update signalling reduction. ISR enables signalling reduction with separate SGSN and MME and also with independent TAs and RAs. Thereby the interdependency is drastically minimized compared with the GERAN/UTRAN RAs. This comes however with ISR specific node and interface functionality. SGSN and MME may be implemented together, which reduces some interface functions but results also in some dependencies. ISR support is mandatory for E-UTRAN UEs that support GERAN and/or UTRAN and optional for the network. ISR requires special functionality in both the UE and the network (i.e. in the SGSN, MME and Serving GW) to activate ISR for a UE. For this activation, the MME/SGSN detects whether S-GW supports ISR based on the configuration and activates ISR only if the S-GW supports the ISR. The network can decide for ISR activation individually for each UE. Gn/Gp SGSNs do not support ISR functionality. No specific HSS functionality is required to support ISR. NOTE. A Release 7 HSS needs additional functionality to support the 'dual registration' of MME and SGSN. Without such an upgrade, at least PS domain MT Location Services and MT Short Messages are liable to fail. It is inherent functionality of the MM procedures to enable ISR activation only when the UE is able to register via E-UTRAN and via GERAN/UTRAN. For example, when there is no E-UTRAN coverage there will be also no ISR activation. Once ISR is activated it remains active until one of the criteria for deactivation in the UE occurs, or until SGSN or MME indicate during an update procedure no more the activated ISR, i.e. the ISR status of the UE has to be refreshed with every update. When ISR is activated this means the UE is registered with both MME and SGSN. Both the SGSN and the MME have a control connection with the Serving GW. MME and SGSN are both registered at HSS. The UE stores MM parameters from SGSN (e.g. P-TMSI and RA) and from MME (e.g. GUTI and TA(s)) and the UE stores session management (bearer) contexts that are common for E-UTRAN and GERAN/UTRAN accesses. In idle state the UE can reselect between E-UTRAN and GERAN/UTRAN (within the registered RA and TAs) without any need to perform TAU or RAU procedures with the network. SGSN and MME store each other's address when ISR is activated. When ISR is activated and downlink data arrive, the Serving GW initiates paging processes on both SGSN and MME. In response to paging or for uplink data transfer the UE performs normal Service Request procedures on the currently camped-on RAT without any preceding update signalling (there are however existing scenarios that may require to perform a RAU procedure prior to the Service Request even with ISR is activated when GERAN/UTRAN RAs are used together, as specified in clause 6.13.1.3 of TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7]). The UE and the network run independent periodic update timers for GERAN/UTRAN and for E-UTRAN. When the MME or SGSN do not receive periodic updates MME and SGSN may decide independently for implicit detach, which removes session management (bearer) contexts from the CN node performing the implicit detach and it removes also the related control connection from the Serving GW. Implicit detach by one CN node (either SGSN or MME) deactivates ISR in the network. It is deactivated in the UE when the UE cannot perform periodic updates in time. When ISR is activated and a periodic updating timer expires the UE starts a Deactivate ISR timer. When this timer expires and the UE was not able to perform the required update procedure the UE deactivates ISR. Part of the ISR functionality is also available when ISR is not activated because the MM contexts are stored in UE, MME and SGSN also when ISR is not active. This results in some reduced network signalling, which is not available for Gn/Gp SGSNs. These SGSNs cannot handle MM and session management contexts separately. Therefore all contexts on Gn/Gp SGSNs are deleted when the UE changes to an MME. The MME can keep their MME contexts in all scenarios.

3GPP TS 23.401

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

SA WG2

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

Annex

– PUCCH-SpatialRelationInfo-Id

The IE PUCCH-SpatialRelationInfo-Id is used to identify a PUCCH-SpatialRelationInfo PUCCH-SpatialRelationInfo-Id information element -- ASN1START -- TAG-PUCCH-SPATIALRELATIONINFO-START PUCCH-SpatialRelationInfoId ::= INTEGER (1..maxNrofSpatialRelationInfos) PUCCH-SpatialRelationInfoId-r16 ::= INTEGER (1..maxNrofSpatialRelationInfos-r16) PUCCH-SpatialRelationInfoId-v1610::= INTEGER (maxNrofSpatialRelationInfos-plus-1..maxNrofSpatialRelationInfos-r16) -- TAG-PUCCH-SPATIALRELATIONINFO-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

17.7.17 MBMS-Counting-Information AVP

The MBMS-Counting-Information AVP (AVP code 914) is of type Enumerated, and contains explicit information about whether the MBMS Counting procedures are applicable for the MBMS Service that is about to start. See 3GPP TS 25.346[ None ] [72]. This AVP is only valid for UTRAN access type. The following values are supported: COUNTING-NOT-APPLICABLE (0) The MBMS Session Start Procedure signalled by the BM-SC is for a MBMS Service where MBMS Counting procedures are not applicable. COUNTING-APPLICABLE (1) The MBMS Session Start Procedure signalled by the BM-SC is for a MBMS Service where MBMS Counting procedures are applicable.

3GPP TS 29.061

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

CT WG3

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

17.7.17

8.3.3.1.1 FDD PCell (FDD single carrier)

The parameters specified in Table 8.3.3.1.1-1 are valid for FDD CC and LAA SCell(s) unless otherwise stated. And the additional parameters specified in Table 8.3.3.1.1-2 are valid for LAA SCell(s). Table 8.3.3.1.1-1: Common Test Parameters Table 8.3.3.1.1-2: Addtional Test Parameters for LAA SCell(s) For CA with LAA SCell(s), the requirements for dual-layer transmission on antenna ports 7 and 8 upon detection of a PDCCH with DCI format 2C are specified in Table 8.3.3.1.1-7, with the addition of the parameters in Table 8.3.3.1.1-3, Table 8.3.3.1.1-4 and Table 8.3.3.1.1-5. The downlink physical channel setup is set according to Annex C.3.2. The purpose of these tests is to verify the rank-2 performance for full RB allocation for CA with LAA SCell(s). Table 8.3.3.1.1-3: Test Parameters for Large Delay CDD (FRC) for PCell Table 8.3.3.1.1-4: Test Parameters for CDM-multiplexed DM RS (dual layer) for CA with LAA SCell(s) Table 8.3.3.1.1-5: Single carrier performance Large Delay CDD (FRC) for PCell for multiple CA configurations Table 8.3.3.1.1-6: Single carrier performance for CDM-multiplexed DM RS (dual layer) for LAA SCell for multiple CA configurations Table 8.3.3.1.1-7: Minimum performance (FRC) based on single carrier performance for CA with one LAA SCell Table 8.3.3.1.1-8: Minimum performance (FRC) based on single carrier performance for CA with two LAA SCells Table 8.3.3.1.1-9: Minimum performance (FRC) based on single carrier performance for CA with three LAA SCells Table 8.3.3.1.1-10: Minimum performance (FRC) based on single carrier performance for CA with four LAA SCells Table 8.3.3.1.1-11: Minimum performance (FRC) based on single carrier performance for CA with five LAA SCells Table 8.3.3.1.1-12: Minimum performance (FRC) based on single carrier performance for CA with six LAA SCells

3GPP TS 36.101

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

RAN4

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

8.3.3.1.1

5.31.7.2.1 Overview

The UE and the network may negotiate over non-access stratum signalling the use of extended idle mode DRX for reducing its power consumption, while being available for mobile terminating data and/or network originated procedures within a certain delay dependent on the DRX cycle value. Extended DRX in CM-IDLE is supported for E-UTRA and NR connected to 5GC. Extended DRX in CM-CONNECTED with RRC_INACTIVE mode is supported for WB-E-UTRA, LTE-M and NR connected to 5GC. RRC_INACTIVE is not supported by NB-IoT connected to 5GC. The negotiation of the eDRX parameters for NR, WB-E-UTRA and LTE-M is supported over any RAT. Applications that want to use extended idle mode DRX need to consider specific handling of mobile terminating services or data transfers, and in particular they need to consider the delay tolerance of mobile terminated data. A network side application may send mobile terminated data, an SMS, or a device trigger, and needs to be aware that extended idle mode DRX may be in place. A UE should request for extended idle mode DRX only when all expected mobile terminating communication is tolerant to delay. NOTE 1: The extended idle mode DRX cycle length requested by UE takes into account requirements of applications running on the UE. Subscription based determination of eDRX cycle length can be used in those rare scenarios when applications on UE cannot be modified to request appropriate extended idle mode DRX cycle length. The network accepting extended DRX while providing an extended idle mode DRX cycle length value longer than the one requested by the UE, can adversely impact reachability requirements of applications running on the UE. UE and NW negotiate the use of extended idle mode DRX as follows: If the UE decides to request for extended idle mode DRX, the UE includes an extended idle mode DRX parameters information element in the Registration Request message. The UE may also include the UE specific DRX parameters information element for regular idle mode DRX according to clause 5.4.5. The extended DRX parameters information element includes the extended idle mode DRX cycle length. The AMF decides whether to accept or reject the UE request for enabling extended idle mode DRX. If the AMF accepts the extended idle mode DRX, the AMF based on operator policies and, if available, the extended idle mode DRX cycle length value in the subscription data from the UDM, may also provide different values of the extended idle mode DRX parameters than what was requested by the UE. The AMF taking into account the RAT specific Subscribed Paging Time Window, the UE's current RAT and local policy also assigns a Paging Time Window length to be used, and provides this value to the UE during Registration Update procedures together with the extended idle mode DRX cycle length in the extended DRX parameter information element. If the AMF accepts the use of extended idle mode DRX, the UE shall apply extended idle mode DRX based on the received extended idle mode DRX length, the UE's current RAT (NR, NB-IoT, WB-E-UTRA or LTE-M) and RAT specific Paging Time Window length. If the UE does not receive the extended DRX parameters information element in the relevant accept message because the AMF rejected its request or because the request was received by AMF not supporting extended idle mode DRX, the UE shall apply its regular discontinuous reception as defined in clause 5.4.5. For NR, Paging Time Window applies for extended DRX lengths greater than 10.24s as defined in TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [50]. For WB-E-UTRA, Paging Time Window applies for extended DRX lengths of 10.24s and greater as defined in TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [52]. When the UE is accessing NR, if the AMF provides an extended idle mode DRX cycle length value of 10.24s, and the registration area of the UE contains only NR cells, the AMF does not include a Paging Time Window. If the AMF provides an extended idle mode DRX cycle length value of 10.24s, and the registration area of the UE contains E-UTRA cells and NR cells if the UE supports both E-UTRA and NR, the AMF includes a Paging Time Window. For WB-E-UTRA and LTE-M the eNB broadcasts an indicator for support of extended idle mode DRX in 5GC in addition to the existing indicator for support of extended idle mode DRX in EPC as defined in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [51]. For NR the gNB broadcasts an indicator for support of extended idle mode DRX as defined in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [28]. This indicator is used by the UE in CM-IDLE state. NOTE 2: A broadcast indicator for support of extended idle mode DRX is not needed for NB-IoT as it is always supported in NB-IoT. The specific negotiation procedure handling is described in TS 23.502[ Procedures for the 5G System (5GS) ] [3]. NOTE 3: If the Periodic Registration Update timer assigned to the UE is not longer than the extended idle mode DRX cycle the power savings are not maximised. For RAT types that support extended DRX for CM-CONNECTED with RRC_INACTIVE state, the AMF passes the UE's accepted idle mode eDRX values to NG-RAN. If the UE supports eDRX in RRC_INACTIVE, based on its UE radio capabilities, NG-RAN configures the UE with an eDRX cycle in RRC_INACTIVE as specified in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27] up to the value for the UE's idle mode eDRX cycle as provided by the AMF in "RRC Inactive Assistance Information" as defined in clause 5.3.3.2.5. If an eDRX cycle is applied in RRC_INACTIVE, the RAN can buffer DL packets up to the duration of the eDRX cycle chosen by NG-RAN if the eDRX cycle does not last more than 10.24 seconds. If the CN based MT communication handling support indication is received in RRC Inactive Assistance Information, the NG-RAN may select an eDRX cycle that lasts more than 10.24s. In this case, based on implementation the NG-RAN may send an indication in N2 message that the UE is transitioning to RRC_INACTIVE state and the NG-RAN determined eDRX values (i.e. the eDRX cycle length and the Paging Time Window length) for RRC_INACTIVE to the AMF. The CN takes the indication in the N2 message into account, then handles mobile terminated (MT) communication as specified in clause 5.31.7.2.4 and it can apply high latency communication as specified in clause 5.31.8. The AMF replies to NG-RAN that the indication in the N2 message has been taken into account and the MT signalling or data may be buffered by the Core Network based on high latency communication. If and when the NG-RAN chooses to send the indication is up to NG-RAN implementation. If the NG-RAN delays sending the indication and it receives a DL NAS message for the UE, the NG-RAN proceeds as described in clause 4.8.1.1a of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. NOTE 4: If the indication that the UE is transitioning to RRC_INACTIVE state is not sent (or sent after UE has entered RRC_INACTIVE state) by the NG-RAN then until CN receives it the CN cannot apply the high latency communication functionality, other NFs will not be aware of the UE reachability, certain high latency communication related services provided to the AF via NEF would not be available, NAS message delivery might fail and downlink data in RAN might be lost. NOTE 5: The CN based MT communication handling support indication in RRC Inactive Assistance Information is provided when all entities (e.g. AMF, SMF and UPF) involved in the CN support corresponding functionalities (including the support providing buffered downlink data size) based on deployment and configuration. When the UE has PDU Session associated with emergency services, the UE and AMF follow regular discontinuous reception as defined in clause 5.4.5 and shall not use the extended idle mode DRX. Extended idle mode DRX parameters may be negotiated while the UE has PDU Session associated with emergency services. When the PDU Session associated with emergency services is released, the UE and AMF shall reuse the negotiated extended idle mode DRX parameters in the last Registration Update procedure. The UE shall include the extended DRX parameters information element in each Registration Request message if it still wants to use extended idle mode DRX. At AMF to AMF, AMF to MME and MME to AMF mobility, the extended idle mode DRX parameters are not sent from the old CN node to the new CN node as part of the MM context information.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.31.7.2.1

– FeatureSetCombination

The IE FeatureSetCombination is a two-dimensional matrix of FeatureSet entries. Each FeatureSetsPerBand contains a list of feature sets applicable to the carrier(s) of one band entry of the associated band combination. Across the associated bands, the UE shall support the combination of FeatureSets at the same position in the FeatureSetsPerBand. All FeatureSetsPerBand in one FeatureSetCombination must have the same number of entries. The number of FeatureSetsPerBand in the FeatureSetCombination must be equal to the number of band entries in an associated band combination. The first FeatureSetPerBand applies to the first band entry of the band combination, and so on. Each FeatureSet contains either a pair of NR or E-UTRA feature set IDs for UL and DL. In case of NR, the actual feature sets for UL and DL are defined in the FeatureSets IE and referred to from here by their ID, i.e., their position in the featureSetsUplink / featureSetsDownlink list in the FeatureSet IE. In case of E-UTRA, the feature sets referred to from this list are defined in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10] and conveyed as part of the UE-EUTRA-Capability container. The FeatureSetUplink and FeatureSetDownlink referred to from the FeatureSet comprise, among other information, a set of FeatureSetUplinkPerCC-Ids and FeatureSetDownlinkPerCC-Ids. The number of these per-CC IDs determines the number of carriers that the UE is able to aggregate contiguously in frequency domain in the corresponding band. The number of carriers supported by the UE is also restricted by the bandwidth class indicated in the associated BandCombination, if present. In feature set combinations the UE shall exclude entries with same or lower capabilities, since the network may anyway assume that the UE supports those. NOTE 1: The UE may advertise fallback band-combinations in which it supports additional functionality explicitly in two ways: Either by setting FeatureSet IDs to zero (inter-band and intra-band non-contiguous fallback) and by reducing the number of FeatureSet-PerCC Ids in a Feature Set (intra-band contiguous fallback). Or by separate BandCombination entries with associated FeatureSetCombinations. NOTE 2: The UE may advertise a FeatureSetCombination containing only fallback band combinations. That means, in a FeatureSetCombination, each group of FeatureSets across the bands may contain at least one pair of FeatureSetUplinkId and FeatureSetDownlinkId which is set to 0/0. NOTE 3: The Network configures serving cell(s) and BWP(s) configuration to comply with capabilities derived from the combination of FeatureSets at the same position in the FeatureSetsPerBand, regardless of activated/deactivated serving cell(s) and BWP(s). FeatureSetCombination information element -- ASN1START -- TAG-FEATURESETCOMBINATION-START FeatureSetCombination ::= SEQUENCE (SIZE (1..maxSimultaneousBands)) OF FeatureSetsPerBand FeatureSetsPerBand ::= SEQUENCE (SIZE (1..maxFeatureSetsPerBand)) OF FeatureSet FeatureSet ::= CHOICE { eutra SEQUENCE { downlinkSetEUTRA FeatureSetEUTRA-DownlinkId, uplinkSetEUTRA FeatureSetEUTRA-UplinkId }, nr SEQUENCE { downlinkSetNR FeatureSetDownlinkId, uplinkSetNR FeatureSetUplinkId } } -- TAG-FEATURESETCOMBINATION-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

28.10 Presence Reporting Area Identifier (PRA ID)

The Presence Reporting Area Identifier (PRA ID) is used to identify a Presence Reporting Area (PRA). PRAs can be used for reporting changes of UE presence in a PRA, e.g. for policy control or charging decisions. See 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [119] and 3GPP TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [121]. A PRA is composed of a short list of TAs and/or NG-RAN nodes and/or cells identifiers in a PLMN.A PRA can be: - either a "UE-dedicated PRA", defined in the subscriber profile; - or a "Core Network predefined PRA", pre-configured in AMF. PRA IDs used to identify "Core Network predefined PRAs" shall not be used for identifying "UE-dedicated PRAs". The same PRA ID may be used for different UEs to identify different "UE-dedicated PRAs", i.e. PRA IDs may overlap between different UEs, while identifying different "UE-dedicated PRAs". The PRA ID shall be formatted as an integer within the following ranges: 0 .. 8 388 607 for UE-dedicated PRA 8 388 608 to 16 777 215 for Core Network predefined PRA. NOTE: The PRA ID is encoded over the Service Based Interfaces as a string of digits representing an integer. See 3GPP TS 29.571[ 5G System; Common Data Types for Service Based Interfaces; Stage 3 ] [129].

3GPP TS 23.003

Numbering, addressing and identification

CT WG4

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

28.10

4.15.6.10 Application guidance for URSP determination

This clause describes the procedures to allow an AF to provide guidance for URSP determination to 5G system via NEF. The AF may belong to the operator or to an external party. The PCF may be in the Home PLMN, as it is the PCF that determines the URSP for the UE, or in the VPLMN and then the Application guidance for URSP determination is provided to the PCF in the HPLMN via the PCF of the VPLMN. The PCF in the VPLMN translates the Service Parameters values provided by the AF for inbound roamer to values applicable to the HPLMN, e.g. S-NSSAI as described in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. NOTE 1: The operator can negotiate with external party (typically a Corporate represented by an AF) dedicated DNN(s) and/or S-NSSAI(s) for the traffic of UE(s) of this external party. UE(s) of the external party can be identified by a group identifier. The guidance for URSP determination may be used to provide 5GC with guidance for the URSPs depending on the UE location. This is further described in TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [74]. For providing guidance for URSP determination, the procedure defined in clause 4.15.6.7 is performed with the following considerations: 1) Service Description indicates an AF Identifier. 2) Service Parameters. Information on the AF guidance for URSP determination which consists of a list of URSP rules that associate an application traffic descriptor with requested features for the candidate PDU sessions the application traffic may use: - An application traffic descriptor, whose definition corresponds to that of the URSP Traffic Descriptors (as defined for the URSP rule in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20] Table 6.6.2.1-2). When AF provides application guidance for URSP determination for PIN, the application traffic descriptor shall include PIN ID. - one or more sets of Route selection parameters, each parameter may correspond to: - (DNN, S-NSSAI). This may be provided by the AF or determined by the NEF based on the AF Identifier when it is not provided by the AF and the AF provides only one instance of AF guidance for URSP determination. In the case of AF guidance for URSP determination for PIN, this shall be provided by the AF. - Requested PDU session type. Editor's note: It is FFS whether the AF can provide SSC mode. - a default Route selection precedence value to be used for the application traffic when Route selection precedence with a corresponding spatial validity condition is not provided. - Route selection precedence with a corresponding spatial validity condition that indicates where the Route selection parameters apply. This may correspond to a geographical area (e.g. a civic address or shapes). NOTE 2: The different sets of Route selection parameters indicate different sets of PDU Session information (DNN, S-NSSAI) that can be associated with applications matching the application traffic descriptor. Each set is meant to apply for a specific (set of) spatial validity condition. Each set is associated with a Route selection precedence to cope with the case where multiple spatial validity conditions overlap. - VPLMN ID(s) that indicates the PLMN(s) where the AF guidance on URSP determination and all its RSD(s), applies. If the AF provides a geographical area as spatial validity condition, it is up to the NEF to transform this information into 3GPP identifiers (e.g. TAI(s)). An AF sets the Requested PDU session type if the AF requests to change the PDU session type of the URSP rules. NEF may, based on local configuration, complement missing service parameters. Additionally, based on operator's local policy, NEF may request UDM for service specific authorization for the service parameters for an individual UE (e.g. to authorize the Corporate or MTC provider represented by the AF and the requested DNN, S-NSSAI for the related UE) before storing the service parameters into the UDR. If the request is targeting a group of UEs, NEF may also request UDM for service specific authorization for the group related data (see table 4.15.6.3b-1), i.e. the DNN, S-NSSAI associated to the group. If the request is targeting any UE (all UEs), NEF authorizes the request based on local policy (e.g. based on AF Id) without requesting for any service specific authorization from UDM. NEF requests UDM for service specific authorization for the service parameters provisioned via the Nudm_ServiceSpecificAuthorisation_Create service operation as defined in clause 4.15.6.7a. If a group of UEs or any UE is requested, each individual UE authorization is performed at a later stage by PCF. NOTE 3: The operator needs to ensure the consistency between the group related data and the UE group members subscription data, i.e. if a group is authorized for a given DNN/S-NSSAI as defined in the group related data, it needs to be ensured that all UE members of the group are provisioned with such DNN/S-NSSAI, since no individual UE check is required to be done by NEF against UDM. NOTE 4: AF guidance for application traffic is not related with 5G VN group. 3) The Target UE identifier(s) that may be a specific UE, identified by a GPSI, or a group of UE(s), identified by an External-Group-ID, or any UE of the PLMN of the NEF, or the PLMN ID(s) of inbound roamers that the AF request may be associated with. The information on the AF guidance for URSP determination provided by the AF may be associated to: a) UEs of the PLMN (of the NEF) when roaming in other PLMNs. In this case, the AF guidance for URSP determination targets to a specific UE, a group of UEs or any UE of the PLMN. In this case, the AF guidance for URSP determination associated to a specific UE, a group of UEs or any UE of the PLMN shall be also associated with the corresponding VPLMN(s) where the AF guidance for URSP determination shall be applied if the UE roams to that VPLMN(s). The list of VPLMN ID(s) is included in the Service Parameters. b) An inbound roamer from one or more PLMN(s). In this case, the AF targets the AF guidance for URSP determination only with the inbound roamers of corresponding PLMN(s). The PLMN ID is included in the Service Parameters. NOTE 5: Wildcarding of "PLMN ID of inbound roamers" will be handled by stage 3. 4) Subscription to events. The AF may subscribe to notifications about the outcome of the UE Policies delivery due to application guidance for URSP determination. The usage of the AF guidance for application traffic is described in clause 6.6 of TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [74].

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.15.6.10

6.6.6 UEA identification

Each UEA will be assigned a 4-bit identifier. Currently the following values have been defined: "00002" : UEA0, no encryption. "00012" : UEA1, Kasumi. "00102" : UEA2, SNOW 3G. The remaining values are not defined. UEs shall implement UEA0, UEA1 and UEA2. The use of Kasumi for the ciphering function f8 is specified in TS 35.201[ 3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 1: f8 and f9 specification ] [11] and TS 35.202[ 3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 2: Kasumi specification ] [12]. Implementers' test data and design conformance data is provided in TS 35.203[ 3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 3: Implementors' test data ] [13] and TS 35.204[ 3G Security; Specification of the 3GPP confidentiality and integrity algorithms; Document 4: Design conformance test data ] [14]. The use of SNOW 3G for the ciphering function f8 is specified in TS 35.215[ Specification of the 3GPP Confidentiality and Integrity Algorithms UEA2 & UIA2; Document 1: UEA2 and UIA2 specifications ] [24] and TS 35.216[ Specification of the 3GPP Confidentiality and Integrity Algorithms UEA2 & UIA2; Document 2: SNOW 3G specification ] [25]. Implementers' test data and design conformance data is provided in TS 35.217[ Specification of the 3GPP Confidentiality and Integrity Algorithms UEA2 & UIA2; Document 3: Implementors' test data ] [26] and TS 35.218[ Specification of the 3GPP Confidentiality and Integrity Algorithms UEA2 & UIA2; Document 4: Design conformance test data ] [27].

3GPP TS 33.102

3G security; Security architecture

SA WG3

3GPP Series : 33 , Security aspects

6.6.6

5.2.5.6.5 Npcf_UEPolicyControl_Update service operation

Service operation name: Npcf_UEPolicyControl_Update Description: NF Service Consumer, e.g. AMF can request the update of the UE Policy Association to receive updated Policy information for the UE context. Inputs, Required: UE Policy Association ID. Inputs, Optional: Information on the UE policy related Policy Control Request Trigger condition that has been met, as defined in Table 6.1.2.5-1 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. Outputs, Required: Success or Failure. Outputs, Optional: Policy Control Request Trigger of UE Policy Association. In the case of H-PCF is producer, UE related policy information.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

5.2.5.6.5

4.11.2.2 5GS to EPS Mobility

The following procedure is used by UEs in single-registration or dual registration mode on mobility from 5GS to EPS. In the case of network sharing the UE selects the target PLMN ID according to clause 5.18.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. Figure 4.11.2.2-1: Mobility procedure from 5GS to EPS without N26 interface The UE operating in single-registration mode can start the procedure from Step 1 or Step 5. The UE operating in dual-registration mode starts the procedure from Step 5. NOTE 1: The network has indicated the " Interworking without N26" to the UE. To support IP address preservation, the UE in single-registration mode starts the procedure from Step 5. If the UE in single-registration mode starts the procedure from Step 1, the IP address preservation is not provided. 0. UE is registered in 5GS and established PDU sessions. The FQDN for the S5/S8 interface of the SMF+PGW-C is also stored in the UDM by the SMF+PGW-C during PDU Session setup in addition to what is specified in clause 4.3.2.2.1 and clause 4.3.2.2.2. NOTE 2: At 5GS to EPS mobility, the MME use the FQDN for the S5/S8 interface of the SMF+PGW-C to find the SMF+PGW-C and when UE moves back from EPS to 5GS, the AMF uses FQDN for the S5/S8 interface of the SMF+PGW-C to find the SMF+PGW-C. 1. Step 1 as in clause 5.3.3.1 (Tracking Area Update) in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13]. 2. Step 2 as in clause 5.3.3.1 (Tracking Area Update) in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13] with the following modifications: The UE shall provide a EPS-GUTI that is mapped from the 5G-GUTI following the mapping rules specified in TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The UE indicates that it is moving from 5GC. 3. Step 3 as in clause 5.3.3.1 (Tracking Area Update) in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13]. 4. If the MME determined that the old node is an AMF based on UE's GUTI mapped from 5G-GUTI and the MME is configured to support 5GS-EPS interworking without N26 procedure, the MME sends a TAU Reject to the UE. 5. Step 1 as in clause 5.3.2.1 (E-UTRAN Initial Attach) in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13] with the modifications captured in clause 4.11.2.4.1. 6. Step 2 as in clause 5.3.2.1 (E-UTRAN Initial Attach) in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13]. 7. Steps 4-7 as in clause 5.3.2.1 (E-UTRAN Initial Attach) in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13], with the modifications captured in clause 4.11.2.4.1. 8. Step 8 as in clause 5.3.2.1 (E-UTRAN Initial Attach) in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13], with the modifications captured in clause 4.11.2.4.1. 9. Step 11 as in clause 5.3.2.1 (E-UTRAN Initial Attach) in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13], with the following modifications: The subscription profile the MME receives from HSS+UDM includes per DNN/APN at most one SMF+PGW-C FQDN as described in in clause 5.17.2.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 10. Steps 12-24 as in clause 5.3.2.1 (E-UTRAN Initial Attach) in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13], with the modifications as described in clause 4.11.2.4.1. 11. Step 25 as in clause 5.3.2.1 (E-UTRAN Initial Attach) in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13]. 12. Step 26 as in clause 5.3.2.1 (E-UTRAN Initial Attach) in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13]. 13. If the UE has remaining PDU Sessions in 5GS which it wants to transfer to EPS and maintain the same IP address/prefix, the UE performs the UE requested PDN Connectivity Procedure as specified in clause 5.10.2 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13] and sets the Request Type to "handover" or "handover of emergency bearer services" in Step 1 of the procedure with modification captured in clause 4.11.2.4.2. UE provides an APN and the PDU Session ID corresponding to the PDU Session it wants to transfer to EPS. The UE provides the PDU Session ID in PCO as described in clause 4.11.1.1. UEs in single-registration mode performs this step for each PDU Session immediately after completing the E-UTRAN Initial Attach procedure. UEs in dual-registration mode may perform this step any time after the completing of E-UTRAN Initial Attach procedure. Also, UEs in dual-registration mode may perform this step only for a subset of PDU Sessions. The MME determines the SMF+PGW-C address for the Create Session Request based on the APN if received from the UE, local Emergency Configuration Data (as in clause 4.11.0a.4) and the subscription profile which may include the Emergency Information received from the HSS+UDM in Step 9 or when the HSS+UDM notifies the MME for the new SMF+PGW-C ID in the updated subscription profile. The SMF+PGW-C uses the PDU Session ID to correlate the transferred PDN connection with the PDU Session in 5GC. As a result of the procedure the PGW-U+UPF starts routing DL data packets to the Serving GW for the default and any dedicated EPS bearers established for this PDN connection. 14. For Non-Roaming case and Roaming with Local Breakout, the SMF+PGW-C initiates release of the PDU Session(s) in 5GS transferred to EPS as specified in clause 4.3.4.2 with the following clarification: - In step 2, the SMF+PGW-C shall not release IP address/prefix(es) allocated for the PDU Session; - If UP connection of the PDU Session is not active, step 3b is not executed, thus the steps triggered by step 3b are not executed; If UP connection of the PDU Session is active, the SMF invokes the Namf_Communication_N1N2MessageTransfer service operation in step 3b without including N1 SM container (PDU Session Release Command); - In step 11, Nsmf_PDUSession_SMContexStatusNotify service operation invoked by the SMF to notify AMF that the SM context for this PDU Session is released due to handover to EPS. For Home Routed roaming, the SMF+PGW-C initiates release of the PDU Session(s) in 5GS transferred to EPS as specified in clause 4.3.4.3 with the following clarification: - In step 3a, the H-SMF invokes the Nsmf_PDUSession_Update service operation without including N1 SM container (PDU Session Release Command); - In step 16a, Nsmf_PDUSession_StatusNotify operation invoked by H-SMF to notify the V-SMF that the PDU session context is released due to handover to EPS; - In step 16b, Nsmf_PDUSession_SMContexStatusNotify service operation invoked by the V-SMF to notify AMF that the SM context for this PDU Session is released due to handover to EPS.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

4.11.2.2

7.2.22 Release Access Bearers Response

The Release Access Bearers Response message is sent on the S11 interface by the SGW to the MME as part of the S1 release procedure and eNodeB initiated Connection Suspend procedure. It may also be sent on the S11 interface by the SGW to the MME as part of the Establishment of S1-U bearer during Data Transport in Control Plane CIoT EPS optimisation procedure (see clause 5.3.4B.4 of 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [3]). NOTE: The S1 release procedure is also used to release S11-U bearers for the Control Plane CIoT EPS optimisation, except in the case of data buffering in the MME. The message shall also be sent on the S4 interface by the SGW to the SGSN as part of the procedures: - RAB release using S4 - Iu Release using S4 - READY to STANDBY transition within the network Possible Cause values are specified in Table 8.4-1. Message specific cause values are: - "Request accepted". - "Request accepted partially". - "Context not found". Table 7.2.22-1: Information Element in Release Access Bearers Response Table 7.2.22-2: Load Control Information within Release Access Bearers Response Table 7.2.22-3: Overload Control Information within Release Access Bearers Response

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

– NR-NS-PmaxList

The IE NR-NS-PmaxList is used to configure a list of additionalPmax and additionalSpectrumEmission, as defined in TS 38.101[ None ] -1 [15], table 6.2.3.1-1A, TS 38.101[ None ] -2 [39], table 6.2.3.1-2, and TS 38.101[ None ] -5 [75], table 6.2.3.1-1A for a given frequency band. NR-NS-PmaxList information element -- ASN1START -- TAG-NR-NS-PMAXLIST-START NR-NS-PmaxList ::= SEQUENCE (SIZE (1..maxNR-NS-Pmax)) OF NR-NS-PmaxValue NR-NS-PmaxValue ::= SEQUENCE { additionalPmax P-Max OPTIONAL, -- Need N additionalSpectrumEmission AdditionalSpectrumEmission } NR-NS-PmaxList-v1760 ::= SEQUENCE (SIZE (1.. maxNR-NS-Pmax)) OF NR-NS-PmaxValue-v1760 NR-NS-PmaxValue-v1760 ::= SEQUENCE { additionalSpectrumEmission-v1760 AdditionalSpectrumEmission-v1760 OPTIONAL -- Need N } NR-NS-PmaxListAerial-r18 ::= SEQUENCE (SIZE (1..maxNR-NS-Pmax)) OF NR-NS-PmaxValueAerial-r18 NR-NS-PmaxValueAerial-r18 ::= SEQUENCE { additionalPmax-r18 P-Max OPTIONAL, -- Need N additionalSpectrumEmission-r18 AdditionalSpectrumEmission-r18 } -- TAG-NR-NS-PMAXLIST-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

10.5.6.11 Packet Flow Identifier

The Packet Flow Identifier (PFI) information element indicates the Packet Flow Identifier for a Packet Flow Context. The Packet Flow Identifier is a a type 4 information element with 3 octets length. The Packet Flow Identifier information element is coded as shown in figure 10.5.143/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.161/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.143/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Packet Flow Identifier information element Table 10.5.161/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Packet Flow Identifier information element

3GPP TS 24.008

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

CT WG1

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

10.5.6.11

– MAC-Parameters

The IE MAC-Parameters is used to convey capabilities related to MAC. MAC-Parameters information element -- ASN1START -- TAG-MAC-PARAMETERS-START MAC-Parameters ::= SEQUENCE { mac-ParametersCommon MAC-ParametersCommon OPTIONAL, mac-ParametersXDD-Diff MAC-ParametersXDD-Diff OPTIONAL } MAC-Parameters-v1610 ::= SEQUENCE { mac-ParametersFRX-Diff-r16 MAC-ParametersFRX-Diff-r16 OPTIONAL } MAC-Parameters-v1700 ::= SEQUENCE { mac-ParametersFR2-2-r17 MAC-ParametersFR2-2-r17 OPTIONAL } MAC-ParametersCommon ::= SEQUENCE { lcp-Restriction ENUMERATED {supported} OPTIONAL, dummy ENUMERATED {supported} OPTIONAL, lch-ToSCellRestriction ENUMERATED {supported} OPTIONAL, ..., [[ recommendedBitRate ENUMERATED {supported} OPTIONAL, recommendedBitRateQuery ENUMERATED {supported} OPTIONAL ]], [[ recommendedBitRateMultiplier-r16 ENUMERATED {supported} OPTIONAL, preEmptiveBSR-r16 ENUMERATED {supported} OPTIONAL, autonomousTransmission-r16 ENUMERATED {supported} OPTIONAL, lch-PriorityBasedPrioritization-r16 ENUMERATED {supported} OPTIONAL, lch-ToConfiguredGrantMapping-r16 ENUMERATED {supported} OPTIONAL, lch-ToGrantPriorityRestriction-r16 ENUMERATED {supported} OPTIONAL, singlePHR-P-r16 ENUMERATED {supported} OPTIONAL, ul-LBT-FailureDetectionRecovery-r16 ENUMERATED {supported} OPTIONAL, -- R4 8-1: MPE tdd-MPE-P-MPR-Reporting-r16 ENUMERATED {supported} OPTIONAL, lcid-ExtensionIAB-r16 ENUMERATED {supported} OPTIONAL ]], [[ spCell-BFR-CBRA-r16 ENUMERATED {supported} OPTIONAL ]], [[ srs-ResourceId-Ext-r16 ENUMERATED {supported} OPTIONAL ]], [[ enhancedUuDRX-forSidelink-r17 ENUMERATED {supported} OPTIONAL, --27-10: Support of UL MAC CE based MG activation request for PRS measurements mg-ActivationRequestPRS-Meas-r17 ENUMERATED {supported} OPTIONAL, --27-11: Support of DL MAC CE based MG activation request for PRS measurements mg-ActivationCommPRS-Meas-r17 ENUMERATED {supported} OPTIONAL, intraCG-Prioritization-r17 ENUMERATED {supported} OPTIONAL, jointPrioritizationCG-Retx-Timer-r17 ENUMERATED {supported} OPTIONAL, survivalTime-r17 ENUMERATED {supported} OPTIONAL, lcg-ExtensionIAB-r17 ENUMERATED {supported} OPTIONAL, harq-FeedbackDisabled-r17 ENUMERATED {supported} OPTIONAL, uplink-Harq-ModeB-r17 ENUMERATED {supported} OPTIONAL, sr-TriggeredBy-TA-Report-r17 ENUMERATED {supported} OPTIONAL, extendedDRX-CycleInactive-r17 ENUMERATED {supported} OPTIONAL, simultaneousSR-PUSCH-DiffPUCCH-groups-r17 ENUMERATED {supported} OPTIONAL, lastTransmissionUL-r17 ENUMERATED {supported} OPTIONAL ]], [[ sr-TriggeredByTA-ReportATG-r18 ENUMERATED {supported} OPTIONAL, -- similar to R1 26-4: UE reporting of information related to TA pre-compensation defined for ATG uplinkTA-ReportingATG-r18 ENUMERATED {supported} OPTIONAL, extendedDRX-CycleInactive-r18 ENUMERATED {supported} OPTIONAL ]] } MAC-ParametersFRX-Diff-r16 ::= SEQUENCE { directMCG-SCellActivation-r16 ENUMERATED {supported} OPTIONAL, directMCG-SCellActivationResume-r16 ENUMERATED {supported} OPTIONAL, directSCG-SCellActivation-r16 ENUMERATED {supported} OPTIONAL, directSCG-SCellActivationResume-r16 ENUMERATED {supported} OPTIONAL, -- R1 19-1: DRX Adaptation drx-Adaptation-r16 SEQUENCE { non-SharedSpectrumChAccess-r16 MinTimeGap-r16 OPTIONAL, sharedSpectrumChAccess-r16 MinTimeGap-r16 OPTIONAL } OPTIONAL, ... } MAC-ParametersFR2-2-r17 ::= SEQUENCE { directMCG-SCellActivation-r17 ENUMERATED {supported} OPTIONAL, directMCG-SCellActivationResume-r17 ENUMERATED {supported} OPTIONAL, directSCG-SCellActivation-r17 ENUMERATED {supported} OPTIONAL, directSCG-SCellActivationResume-r17 ENUMERATED {supported} OPTIONAL, drx-Adaptation-r17 SEQUENCE { non-SharedSpectrumChAccess-r17 MinTimeGapFR2-2-r17 OPTIONAL, sharedSpectrumChAccess-r17 MinTimeGapFR2-2-r17 OPTIONAL } OPTIONAL, ... } MAC-ParametersXDD-Diff ::= SEQUENCE { skipUplinkTxDynamic ENUMERATED {supported} OPTIONAL, logicalChannelSR-DelayTimer ENUMERATED {supported} OPTIONAL, longDRX-Cycle ENUMERATED {supported} OPTIONAL, shortDRX-Cycle ENUMERATED {supported} OPTIONAL, multipleSR-Configurations ENUMERATED {supported} OPTIONAL, multipleConfiguredGrants ENUMERATED {supported} OPTIONAL, ..., [[ secondaryDRX-Group-r16 ENUMERATED {supported} OPTIONAL ]], [[ enhancedSkipUplinkTxDynamic-r16 ENUMERATED {supported} OPTIONAL, enhancedSkipUplinkTxConfigured-r16 ENUMERATED {supported} OPTIONAL ]], [[ ptm-Retransmission-r18 ENUMERATED {supported} OPTIONAL, ptm-RetransmissionInactive-r18 ENUMERATED {supported} OPTIONAL ]] } MinTimeGap-r16 ::= SEQUENCE { scs-15kHz-r16 ENUMERATED {sl1, sl3} OPTIONAL, scs-30kHz-r16 ENUMERATED {sl1, sl6} OPTIONAL, scs-60kHz-r16 ENUMERATED {sl1, sl12} OPTIONAL, scs-120kHz-r16 ENUMERATED {sl2, sl24} OPTIONAL } MinTimeGapFR2-2-r17 ::= SEQUENCE { scs-120kHz-r17 ENUMERATED {sl2, sl24} OPTIONAL, scs-480kHz-r17 ENUMERATED {sl8, sl96} OPTIONAL, scs-960kHz-r17 ENUMERATED {sl16, sl192} OPTIONAL } -- TAG-MAC-PARAMETERS-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

5.2.6.17.3 Nnef_UCMFProvisioning_Delete operation

Service operation name: Nnef_UCMFProvisioning_Delete Description: The consumer deletes a UCMF dictionary entry for a Manufacturer-assigned UE Radio Capability ID via the NEF. The consumer provides a (list of) UE radio capability ID value(s) to be deleted or it may provide the IMEI/TAC values for which the associated UE radio capability ID entries shall be no longer used. Inputs, Required: UE Radio Capability ID(s) of the UCMF dictionary entry(ies) to be deleted or IMEI/TAC(s) that no longer use associated UE radio Capability ID(s). Inputs, Optional: None. Outputs, Required: None. Outputs, Optional: None.

3GPP TS 23.502

Procedures for the 5G System (5GS)

SA WG2

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

5.2.6.17.3

9.1.2 Implementation requirements

IPsec ESP implementation shall be done according to RFC 4303 [4] as profiled by TS 33.210[ Network Domain Security (NDS); IP network layer security ] [3]. For IPsec implementation, tunnel mode is mandatory to support while transport mode is optional. IKEv2 certificate-based authentication implementation shall be done according to TS 33.310[ Network Domain Security (NDS); Authentication Framework (AF) ] [5]. The certificates shall be supported according to the profile described by TS 33.310[ Network Domain Security (NDS); Authentication Framework (AF) ] [5]. IKEv2 shall be supported conforming to the IKEv2 profile described in TS 33.310[ Network Domain Security (NDS); Authentication Framework (AF) ] [5].

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

9.1.2

5.5.2.9 Measurement gap configuration

The UE shall: 1> if gapFR1 is set to setup: 2> if an FR1 measurement gap configuration configured by gapFR1 is already setup, release the FR1 measurement gap configuration; 2> setup the FR1 measurement gap configuration indicated by the gapFR1 in accordance with the received gapOffset, i.e., the first subframe of each gap occurs at an SFN and subframe meeting the following condition: SFN mod T = FLOOR(gapOffset/10); subframe = gapOffset mod 10; with T = MGRP/10 as defined in TS 38.133[ NR; Requirements for support of radio resource management ] [14]; 2> apply the specified timing advance mgta to the gap occurrences calculated above (i.e. the UE starts the measurement mgta ms before the gap subframe occurrences); 1> else if gapFR1 is set to release: 2> release the FR1 measurement gap configuration configured by gapFR1; 1> if gapFR2 is set to setup: 2> if an FR2 measurement gap configuration configured by gapFR2 is already setup, release the FR2 measurement gap configuration; 2> setup the FR2 measurement gap configuration indicated by the gapFR2 in accordance with the received gapOffset, i.e., the first subframe of each gap occurs at an SFN and subframe meeting the following condition: SFN mod T = FLOOR(gapOffset/10); subframe = gapOffset mod 10; with T = MGRP/10 as defined in TS 38.133[ NR; Requirements for support of radio resource management ] [14]; 2> apply the specified timing advance mgta to the gap occurrences calculated above (i.e. the UE starts the measurement mgta ms before the gap subframe occurrences); 1> else if gapFR2 is set to release: 2> release the FR2 measurement gap configuration configured by gapFR2; 1> if gapUE is set to setup: 2> if a per UE measurement gap configuration configured by gapUE is already setup, release the per UE measurement gap configuration; 2> setup the per UE measurement gap configuration indicated by the gapUE in accordance with the received gapOffset, i.e., the first subframe of each gap occurs at an SFN and subframe meeting the following condition: SFN mod T = FLOOR(gapOffset/10); subframe = gapOffset mod 10; with T = MGRP/10 as defined in TS 38.133[ NR; Requirements for support of radio resource management ] [14]; 2> apply the specified timing advance mgta to the gap occurrences calculated above (i.e. the UE starts the measurement mgta ms before the gap subframe occurrences); 1> else if gapUE is set to release: 2> release the per UE measurement gap configuration configured by gapUE. 1> for each measGapId included in the received gapToReleaseList: 2> release the measurement gap configuration associated with the measGapId; 1> for each measPosPreConfigGapId included in the received posMeasGapPreConfigToReleaseList: 2> release the measurement gap configuration associated with the measPosPreConfigGapId; 1> for each GapConfig received in gapToAddModList: 2> setup measurement gap configuration indicated by the GapConfig in accordance with the received gapOffset, i.e., the first subframe of each gap occurs at an SFN and subframe meeting the following condition: SFN mod T = FLOOR(gapOffset/10); subframe = gapOffset mod 10; with T = MGRP/10 as defined in TS 38.133[ NR; Requirements for support of radio resource management ] [14]; 2> apply the specified timing advance mgta to the gap occurrences calculated above (i.e. the UE starts the measurement mgta ms before the gap subframe occurrences); 2> apply the measurement gap as per UE measurement gap, FR1 measurement gap, or FR2 measurement gap according to the gapType indicated by the GapConfig; 2> associate the measurement gap with the measGapId indicated by the GapConfig; 2> if gapSharing in the GapConfig is present: 3> setup the gap sharing configuration for the measurement gap in accordance with the received gapSharing as defined in TS 38.133[ NR; Requirements for support of radio resource management ] [14]; 2> else: 3> release the gap sharing configuration (if configured) for the measurement gap; 1> for each PosGapConfig received in PosMeasGapPreConfigToAddModList: 2> if a measurement gap configuration associated with the measPosPreConfigGapId indicated by the PosGapConfig is already setup: 3> release the measurement gap configuration; 2> setup measurement gap configuration indicated by the PosGapConfig in accordance with the received gapOffset, i.e., the first subframe of each gap occurs at an SFN and subframe meeting the following condition: SFN mod T = FLOOR(gapOffset/10); subframe = gapOffset mod 10; with T = MGRP/10 as defined in TS 38.133[ NR; Requirements for support of radio resource management ] [14]; 2> apply the specified timing advance mgta to the gap occurrences calculated above (i.e. the UE starts the measurement mgta ms before the gap subframe occurrences); 2> configure the measurement gap as indicated by gapType; 1> for each FR1, FR2, and per UE measurement gap that is setup: 2> if the measurement gap is configured by GapConfig and preConfigInd-r17 in the corresponding GapConfig is present: 3> determine whether the measurement gap is activated or not according to TS 38.133[ NR; Requirements for support of radio resource management ] [14]; 2> else if the measurement gap is configured by PosGapConfig: 3> consider the measurement gap to be deactivated; 2> else: 3> consider the measurement gap to be activated. NOTE 1: For FR2 gap configuration with synchronous CA, for the UE in NE-DC or NR-DC, the SFN and subframe of the serving cell indicated by the refServCellIndicator is used in the gap calculation. Otherwise, the SFN and subframe of a serving cell on FR2 frequency is used in the gap calculation NOTE 2: For FR1 gap or per UE gap configuration, for the UE in NE-DC or NR-DC, the SFN and subframe of the serving cell indicated by the refServCellIndicator in is used in the gap calculation. Otherwise, the SFN and subframe of the PCell is used in the gap calculation. NOTE 3: For FR2 gap configuration with asynchronous CA, for the UE in NE-DC or NR-DC, the SFN and subframe of the serving cell indicated by the refServCellIndicator and refFR2ServCellAsyncCA is used in the gap calculation. Otherwise, the SFN and subframe of a serving cell on FR2 frequency indicated by the refFR2ServCellAsyncCA is used in the gap calculation

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

5.5.2.9

8.5 Non-semantical mandatory information element errors

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; or - an IE unknown in the message, but encoded as "comprehension required" (see 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [20]); or - an out of sequence IE encoded as "comprehension required" (see 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [20]) is received, the mobile station shall proceed as follows: If the message is not one of the messages listed in subclauses 8.5.1, 8.5.2, 8.5.3, 8.5.4 and 8.5.5 a), b) , f) or h), the mobile station shall ignore the message except for the fact that, if an RR connection exists, it shall return a status message (STATUS, MM STATUS depending on the protocol discriminator) with cause # 96 "Invalid mandatory information". If the message was a GMM message the GMM-STATUS message with cause #96 " Invalid mandatory information" shall be returned. If the message was an SM message the SM-STATUS message with cause # 96 "invalid mandatory information" shall be returned. - the network shall proceed as follows: When the message is not one of the messages listed in subclause 8.5.3 b), c), d) or e) and 8.5.5 a), c), d), e) or g), 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 (STATUS, or MM STATUS (depending on the protocol discriminator), GMM STATUS, or SM STATUS) with cause # 96 "Invalid mandatory information".

3GPP TS 24.008

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

CT WG1

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

8.5

8.9.6.1 RRC Connected to RRC Inactive

The procedure for changing the UE state from RRC-connected to RRC-inactive is shown in Figure 8.9.6.1-1. Figure 8.9.6.1-1: RRC Connected to RRC Inactive state transition. 1. The gNB-CU-CP sends BEARER CONTEXT SETUP REQUEST message with UE/PDU session/DRB level inactivity timer. 2. The gNB-CU-UP sends BEARER CONTEXT SETUP RESPONSE message. 3. The gNB-CU-UP sends BEARER CONTEXT INACTIVITY NOTIFICATION message with inactivity monitoring results. 4. The gNB-CU-CP determines that the UE should enter RRC-inactive (e.g., after receiving Bearer Context Inactivity Notification procedure). 5. The gNB-CU-CP sends BEARER CONTEXT MODIFICATION REQUEST message with a Bearer Context Status Change to the gNB-CU-UP, which indicates that the UE is entering RRC-inactive state. The gNB-CU-CP keeps the F1 UL TEIDs. 6. The gNB-CU-UP sends the BEARER CONTEXT MODIFICATION RESPONSE message including the PDCP UL and DL status that may be needed for e.g., data volume reporting. The gNB-CU-UP keeps the Bearer Context, the UE-associated logical E1-connection, the NG-U related resource (e.g., NG-U DL TEIDs) and the F1 UL TEIDs. 7. The gNB-CU-CP sends the UE CONTEXT RELEASE COMMAND message to the gNB-DU serving the UE, together with the RRCRelease message to be sent to the UE. NOTE: step 5 and step 7 can be performed at the same time. 8. The gNB-DU sends the RRCRelease message to the UE. 9. The gNB-DU sends the UE CONTEXT RELEASE COMPLETE message to the gNB-CU-CP.

3GPP TS 38.401

NG-RAN; Architecture description

RAN3

3GPP Series : 38 , Radio technology beyond LTE

8.9.6.1

4.11 Satellite access for CIoT 4.11.1 General

The UE and the network may support a satellite E-UTRAN access in WB-S1 mode or NB-S1 mode with CIoT EPS optimization. Support for satellite E-UTRAN access is specified in 3GPP TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [20]. An MME can determine a UE is accessing the network using a satellite E-UTRAN access and may enforce mobility restriction for the UE as specified in 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10]. If unavailability period is activated due to discontinuous coverage (see 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10]), all NAS timers are stopped and associated procedures aborted except for T3412, T3346, T3396, T3447, T3448, any backoff timers, T3245, T3247, the timer T controlling the periodic search for HPLMN or EHPLMN (if EHPLMN list is present) or higher prioritized PLMNs, and the timer TSENSE controlling the periodic search for PLMNs satisfying the operator controlled signal level threshold (see 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]) and the UE may deactivate access stratum.

3GPP TS 24.301

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

CT WG1

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

4.11

5.4.3 Mapping to physical resources

The block of complex-valued symbols shall be multiplied with the amplitude scaling factor in order to conform to the transmit power specified in Clause 5.1.2.1 in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4], and mapped in sequence starting with to resource elements. PUCCH uses one or more resource block in each of the two slots in a subframe. Within the physical resource block(s) used for transmission, the mapping of to resource elements on antenna port and not used for transmission of reference signals shall be in increasing order of first , then and finally the slot number, starting with the first slot in the subframe. The relation between the index and the antenna port number is given by Table 5.2.1-1. For non-BL/CE UEs, except for PUCCH format 4, the physical resource blocks to be used for transmission of PUCCH in slot are given by For BL/CE UEs, PUCCH is transmitted with repetitions. - The BL/CE UE is not expected to transmit with when ce-PDSCH-14HARQ-Config is configured. The PUCCH transmission spans consecutive subframes, including subframes that are not BL/CE UL subframes where the UE postpones the PUCCH transmission if . If the BL/CE UE is configured with ce-HARQ-AckDelay-r17 indicating Alt-2e, the UE does not postpone the PUCCH transmission. - The quantity is given - by the higher layer parameter pucch-NumRepetitionCE-Format1 for PUCCH format 1/1a and pucch-NumRepetitionCE-Format2 for PUCCH format 2/2a/2b, if configured. Otherwise - by the higher-layer parameter pucch-NumRepetitionCE-Msg4-Level0-r13, pucch-NumRepetitionCE-Msg4-Level1-r13, pucch-NumRepetitionCE-Msg4-Level2-r13 or pucch-NumRepetitionCE-Msg4-Level3-r13. - 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 PUCCH transmission is postponed until the next BL/CE uplink subframe that is not fully reserved. - In a subframe that is partially reserved, the reserved SC-FDMA symbols shall be counted in the PUCCH mapping but not used for transmission of the PUCCH. The physical resource blocks to be used for transmission of PUCCH in subframe within the consecutive subframes are given by where is the absolute subframe number of the first uplink subframe intended for PUCCH. The variable depends on the PUCCH format. - Formats 1, 1a and 1b: - Formats 2, 2a and 2b: - Format 3: - Format 5 (non-BL/CE UEs only): For non-BL/CE UEs, for PUCCH format 4, the physical resource blocks to be used for transmission of PUCCH in slot are given by where is obtained from [4]. Mapping of modulation symbols for the physical uplink control channel for PUCCH formats 1 – 3 is illustrated in Figure 5.4.3-1. In case of simultaneous transmission of sounding reference signal and PUCCH format 1, 1a, 1b, 3, 4 or 5 when there is one serving cell configured, the shortened PUCCH format shall be used where the last SC-FDMA symbol in the second slot of a subframe shall be left empty. In case of guard period for narrowband or wideband retuning for BL/CE UEs, if an SC-FDMA symbol is left empty due to guard period, the SC-FDMA symbol shall be counted in the PUCCH mapping but not used for transmission of the PUCCH. The SC-FDMA symbol affected by the guard period can be the first SC-FDMA symbol in the first slot of a subframe and/or the last SC-FDMA symbol in the second slot of a subframe. For BL/CE UEs communicating over NTN, for PUCCH transmission, for frame structure type 1, after a transmission duration of time units (which may include subframes that are not BL/CE UL subframes), a transmission gap of time units shall be counted for the PUCCH resource mapping but not used for transmission of the PUCCH, according to the single UE capability ntn-SegmentedPrecompensationGaps-r17, as specified in 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [9]. The quantity is provided by higher layers, and the quantity is configured by higher layers based on the UE capability, if signalled. Figure 5.4.3-1: Mapping to physical resource blocks for PUCCH formats 1 – 3 for non-BL/CE UEs.

3GPP TS 36.211

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

RAN1

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

5.4.3

8.4.2 Procedure

Figure 8.4.2-1: Handover from EPS to 5GS over N26 NOTE 1: This procedure is based on clause 4.11.1.2.2 in TS 23.502[ Procedures for the 5G System (5GS) ] [8] and only includes steps and description that are relevant to security. As the UE is connected to the EPS, the source MME has a current EPS security context for the UE. The current EPS security context may be a mapped EPS security context resulting from a previous mobility from 5GC, or a native EPS security context resulting from a primary authentication with the EPS. 1. The source eNB sends a Handover Required message to the source MME, including UE's identity . NOTE 2: The source MME checks whether the UE's security capabilities and access rights are valid in order to decide whether it can initiate handover to 5GS. 2. The source MME selects the target AMF and sends a Forward Relocation Request to the selected target AMF. The source MME includes UE's EPS security context including KASME, eKSI, UE EPS security capabilities, selected EPS NAS algorithm identifiers, uplink and downlink EPS NAS COUNTs, {NH, NCC} pair, in this message. If the source MME has the UE NR security capabilities stored, then it will forward the UE NR security capabilities as well to the target AMF. 3. The target AMF shall construct a mapped 5G security context from the EPS security context received from the source MME. The target AMF shall derive a mapped KAMF' key from the received KASME and the NH value in the EPS security context received from the source MME as described in clause 8.6.2. If the target AMF receives the UE 5G security capabilities, then the target AMF shall select the 5G NAS security algorithms (to be used in the target AMF for encryption and integrity protection) which have the highest priority from its configured list. If the target AMF does not receive the UE 5G security capabilities from the source MME, then the target AMF shall assume that the following default set of 5G security algorithms are supported by the UE (and shall set the UE 5G security capabilities in the mapped 5G NAS security context according to this default set): a. NEA0, 128-NEA1 and 128-NEA2 for NAS signalling ciphering, RRC signalling ciphering and UP ciphering; b. 128-NIA1 and 128-NIA2 for NAS signalling integrity protection, RRC signalling integrity protection and UP integrity protection. The target AMF then derives the complete mapped 5G security context. The target AMF shall derive the 5G NAS keys (i.e., KNASenc and KNASint) from the new KAMF' with the selected 5G NAS security algorithm identifiers as input, to be used in AMF as described in clause A.8. The uplink and downlink 5G NAS COUNTs associated with the derived 5G NAS keys are set to the value as described in clause 8.6. 2. The ngKSI for the newly derived KAMF' key is defined such as the value is taken from the eKSI of the KASME key (i.e. included in the received EPS security context) and the type is set to indicate a mapped security context. The target AMF shall store the EPS NAS security algorithms received from the source MME in the mapped 5G security context. Similar to N2-Handover defined in Clause 6.9.2.3.3, the target AMF shall also set the NCC to zero and shall further derive the temporary KgNB using the mapped KAMF' key and the uplink NAS COUNT value of 232-1 as specified in Annex A.9. The target AMF associates this mapped 5G Security context with ngKSI. NOTE 3: The target AMF derives a temporary KgNB using the mapped KAMF' instead of using the {NH, NCC} pair received from the MME. The uplink NAS COUNT value for the initial KgNB derivation is set to 232-1. The reason for choosing such a value is to avoid any possibility that the value may be used to derive the same KgNB again. The target AMF shall create a NAS Container to signal the necessary security parameters to the UE. The NAS Container shall include a NAS MAC, the selected 5G NAS security algorithms, the ngKSI associated with the derived KAMF' and the NCC value associated with the NH parameter used in the derivation of the KAMF'. The target AMF shall calculate the NAS MAC as described in clause 6.9.2.3.3. with the COUNT parameter set to the maximal value of 232-1. The target AMF shall increment the downlink NAS COUNT by one after creating a NAS Container. 4. The target AMF requests the target gNB/ng-eNB to establish the bearer(s) by sending the Handover Request message. The target AMF sends the NAS Container created in step 3 along with, the {NCC=0, NH=derived temporary KgNB}, the New Security Context Indicator (NSCI), and the UE security capabilities in the Handover Request message to the target gNB/ng-eNB. The target AMF shall further set the NCC to one and shall further compute a NH as specified in Annex A.10. The target AMF shall further store the {NCC=1, NH} pair. 5. The target gNB/ng-eNB shall selects the 5G AS security algorithms from the list in the UE security capabilities The target gNB/ng-eNB shall compute the KgNB to be used with the UE by performing the key derivation defined in Annex A.11 with the {NCC, NH} pair received in the Handover Request message and the target PCI and its frequency ARFCN-DL. The target gNB/ng-eNB shall associate the NCC value received from AMF with the KgNB.The target gNB /ng-eNB shall then derive the 5G AS security context, by deriving the 5G AS keys (KRRCint, KRRCenc, KUPint, and KUPenc) from the KgNB and the selected 5G AS security algorithm identifiers as described in Annex A.8 for gNB and in Annex A.7 in TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [10]. The target gNB/ng-eNB sends a Handover Request Ack message to the target AMF. Included in the Handover Request Ack message is the Target to Source Container, which contains the selected 5G AS algorithms, the keySetChangeIndicator, the NCC value from the received {NH, NCC} pair, and the NAS Container received from the target AMF. If the target gNB/ng-eNB had received the NSCI, it shall set the keySetChangeIndicator field to true, otherwise it shall set the keySetChangeIndicator field to false. 6. The target AMF sends the Forward Relocation Response message to the source MME. The required security parameters obtained from gNB/ng-eNB in step 5 as the Target to Source Container are forwarded to the source MME. 7. The source MME sends the Handover Command to the source eNB. The source eNB commands the UE to handover to the target 5G network by sending the Handover Command. This message includes all the security related parameters in the NAS Container obtained from the target AMF in step 6. 8. The UE derives a mapped KAMF' key from the KASME in the same way the AMF did in step 3. It shall also derive the 5G NAS keys and KgNB corresponding to the AMF and the target gNB/ng-eNB in step 3 and step 5. The UE shall further set the selected EPS NAS security algorithms in the 5G security context to the NAS security algorithms used with the source MME. It associates this mapped 5G security context with the ngKSI included in the NAS Container. The UE shall verify the NAS MAC in the NAS Container. If verification of the NAS MAC fails, the UE shall abort the handover procedure. Furthermore, the UE shall discard the new NAS security context if it was derived and continue to use the existing NAS and AS security contexts. NOTE 4: Void. The mapped 5G security context shall become the current 5G security context. 9. The UE sends the Handover Complete message to the target gNB/ng-eNB. This shall be ciphered and integrity protected by the AS keys in the current 5G security context. 10. The target gNB/ng-eNB notifies the target AMF with a Handover Notify message. If the UE has a native 5G security context established during the previous visit to 5GS, then the UE shall provide the associated the 5G GUTI as an additional GUTI in the Registration Request following the handover procedure. The UE shall use the mapped 5G security context to protect the subsequent Registration Request message over 3GPP access. The target AMF shall validate the integrity of the Registration Request message using the mapped security context. Upon successful validation, the target AMF shall send a context request message to the old AMF and shall include the additional GUTI and an indication that the UE is validated. Upon receiving the context request message with the indication that the UE is validated, the old AMF shall skip the integrity check and transfer the native 5G security context to the target AMF.The AMF shall retrieve the native security context using the 5G GUTI. If the AMF determines to activate the native security context, the AMF shall perform a NAS SMC procedure. NOTE 5: It is up to AMF when to activate the native 5G security context. If the handover is not completed successfully, the new mapped 5G security context cannot be used in the future. In this case, the AMF shall delete the new mapped 5G security context. If the AMF has no native 5G security context available when the UE performs the Registration Request (protected by the mapped 5G security context) following the handover procedure, then the AMF via the SEAF should run a primary authentication depending on local operator policy. The handling of security contexts in the case of multiple active NAS connections in the same PLMN’s serving network is given in clasue 6.4.2.2.

3GPP TS 33.501

Security architecture and procedures for 5G System

SA WG3

3GPP Series : 33 , Security aspects

8.4.2

7.11 F1-C transfer over E-UTRA

In EN-DC, the F1-AP message encapsulated in SCTP/IP or F1-C related (SCTP/)IP packet can be transferred between IAB-donor and IAB-node via E-UTRA, if configured by IAB-donor, as specified in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [4]. When both E-UTRA and NR are configured to transfer the F1-AP message encapsulated in SCTP/IP or F1-C related (SCTP/)IP packet, it is up to the IAB implementation when to select the E-UTRA. SRB2 is used for transporting the F1-AP message encapsulated in SCTP/IP or F1-C related (SCTP/)IP packet between IAB-MT and MN [10], and the F1-AP message encapsulated in SCTP/IP or F1-C related (SCTP/)IP packet is transferred as a container via X2-AP between MN and SN, see TS 36.423[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 Application Protocol (X2AP) ] [9]. 7.12 F1-C transfer in NR-DC In NR-DC, the F1-AP message encapsulated in SCTP/IP or F1-C related (SCTP/)IP packet can be transferred via BAP sublayer or via SRB between the IAB-node and F1-terminating IAB-donor (as specified in TS 38.401[ NG-RAN; Architecture description ] [7]), as specified in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [4]. When both MCG and SCG are configured to transfer the F1-AP message encapsulated in SCTP/IP or F1-C related (SCTP/)IP packet, it is up to the IAB-node implementation for path selection. Two scenarios are supported, as shown in Figure 7.12-1. Figure 7.12-1: F1-C transfer in NR-DC; a) Scenario 1; b) Scenario 2 Scenario 1: IAB-node exchanges F1-AP message encapsulated in SCTP/IP or F1-C related (SCTP/)IP packet with the SN (F1-terminating IAB-donor as specified in TS 38.401[ NG-RAN; Architecture description ] [7]) using NR access link via MN (non-F1-terminating IAB-donor), and exchanges F1-U traffic using backhaul link(s) with SN. SRB2 is used for transporting the F1-AP message encapsulated in SCTP/IP or F1-C related (SCTP/)IP packet between IAB-MT and MN (see TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [4]), and the F1-AP message encapsulated in SCTP/IP or F1-C related (SCTP/)IP packet is transferred in a container via XnAP between MN and SN, see TS 38.423[ NG-RAN; Xn Application Protocol (XnAP) ] [5]. Scenario 2: IAB-node exchanges F1-AP message encapsulated in SCTP/IP or F1-C related (SCTP/)IP packet with the MN (F1-terminating IAB-donor) using NR access link via SN (non-F1-terminating IAB-donor), and exchanges F1-U traffic using backhaul link(s) with MN. Split SRB2 is used for transporting the F1-AP message encapsulated in SCTP/IP or F1-C related (SCTP/)IP packet between IAB-MT and SN (see TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [4]), and the F1-AP message encapsulated in SCTP/IP or F1-C related (SCTP/)IP packet is transferred in a container via XnAP between SN and MN, see TS 38.423[ NG-RAN; Xn Application Protocol (XnAP) ] [5]. The F1-AP message encapsulated in SCTP/IP or the F1-C related (SCTP/)IP packet can be transferred either over BAP sublayer or over SRB, but the two mechanisms cannot be supported simultaneously on the same parent link. The F1-AP message encapsulated in SCTP/IP or the F1-C related (SCTP/)IP packet is transferred over BAP sublayer, if the BH RLC channel used for transferring the F1-C traffic is configured on the cell group indicated for F1-C traffic transfer according to TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [4]. 7.13 Activation and Deactivation of SCG To enable reasonable UE battery consumption while having fast usage of SCG when (NG)EN-DC or NR-DC is configured, an activation/deactivation mechanism of SCG is supported. While the SCG is deactivated, there is no transmission via SCG RLC bearers. Only the NR SCG can be deactivated, and all SCG SCell(s) are in deactivated state while the SCG is deactivated. Upon SCG deactivation and while the SCG is deactivated, the network ensures that there is no uplink control PDU transmission to the deactivated SCG (e.g. the network releases statusReportRequired from PDCP entities of SCG bearers if configured, the network does not perform QoS flow remapping from a DRB associated to the deactivated SCG to another DRB). The network ensures the SCG is activated while PDCP duplication is activated for SCG RLC entities associated with a PDCP entity. NOTE: Upon SCG (de)activation, it is up to the network to ensure there is no pending SDUs or PDUs in SCG RLC entity (e.g. instructs the UE to perform PDCP data recovery and RLC re-establishment/release, if needed). While the SCG is deactivated, the UE will not transmit PUSCH, SRS and CSI report on SCG, and the UE is not required to monitor PDCCH or receive DL-SCH on SCG. If configured by the network, the UE performs radio link monitoring on the SCG and beam failure detection on the SCG while SCG is deactivated. In case of SCG activation without performing random access, the network can indicate TCI states to UE for PDCCH/PDSCH reception on PSCell, if not provided, the UE uses the previously activated TCI states. The MN can configure the SCG as activated or deactivated upon e.g. PSCell addition, PSCell change, RRC Resume or handover. In case the SCG is configured as deactivated, the UE does not perform random access towards the PSCell. The network can trigger SCG RRC reconfiguration (e.g. PSCell change, configuration update) when deactivating the SCG and while the SCG is in deactivated state. SCG activation can be requested by the MN, by the SN and by the UE. SCG deactivation can be requested by the MN and by the SN. For UL data arrival on SCG bearer(s) while the SCG is deactivated, the UE indicates to the MN that it has UL data to transmit over SCG bearer. During handover procedure, the target MN can indicate the SCG state in the RRC reconfiguration message sent to the UE by the source MN. Network can configure whether the UE is allowed to indicate a preference for SCG deactivation to the MN.

3GPP TS 37.340

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

RAN2

3GPP Series : 37 , Multiple radio access technology aspects

7.11

4.2.8.3.1 Overview

The description of the reference points specific for the non-3GPP access: N2, N3, N4, N6: these are defined in clause 4.2. Y1 Reference point between the UE and the untrusted non-3GPP access (e.g. WLAN). This depends on the non-3GPP access technology and is outside the scope of 3GPP. Y2 Reference point between the untrusted non-3GPP access and the N3IWF for the transport of NWu traffic. Y4 Reference point between the 5G-RG and the W-AGF which transports the user plane traffic and the N1 NAS protocol. The definition of this interface is outside the scope of 3GPP. Y5 Reference point between the FN-RG and the W-AGF. The definition of this interface is outside the scope of 3GPP. Yt Reference point between the UE and the TNAP. See e.g. Figure 4.2.8.2.1-2. Yt' Reference point between the N5CW devices and the TWAP. It is defined in clause 4.2.8.5. NWu Reference point between the UE and N3IWF for establishing secure tunnel(s) between the UE and N3IWF so that control-plane and user-plane exchanged between the UE and the 5G Core Network is transferred securely over untrusted non-3GPP access. NWt Reference point between the UE and the TNGF. A secure NWt connection is established over this reference point, as specified in clause 4.12a.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. NAS messages between the UE and the AMF are transferred via this NWt connection. Ta A reference point between the TNAP and the TNGF, which is used to support an AAA interface. Ta requirements are documented in clause 4.2.8.3.2. Tn A reference point between two TNGFs, which is used to facilitate UE mobility between different TNGFs (inter-TNGF mobility). Tn and inter-TNGF mobility are not specified in this Release of the specification.

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

4.2.8.3.1

8.10.1.1.3 Closed-loop spatial multiplexing Enhanced Performance Requirements Type A - Single-Layer Spatial Multiplexing 2 Tx Antenna Port with TM4 interference model (Cell-Specific Reference Symbols)

The requirements are specified in Table 8.10.1.1.3-2, with the addition of the parameters in Table 8.10.1.1.3-1 and the downlink physical channel setup according to Annex C.3.2. The purpose of these tests is to verify the closed loop rank-one performance with wideband precoding with two transmit antennas when the PDSCH transmission in the serving cell is interfered by PDSCH of one dominant interfering cell applying transmission mode 4 interference model defined in clause B.5.3. In Table 8.10.1.1.3-1, Cell 1 is the serving cell, and Cell 2 is the interfering cell. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1 and Cell 2, respectively. Table 8.10.1.1.3-1: Test Parameters for Single-Layer Spatial Multiplexing (FRC) with TM4 interference model and 4 RX Antenna Ports Table 8.10.1.1.3-2: Enhanced Performance Requirement Type A, Single-Layer Spatial Multiplexing (FRC) with TM4 interference model and 4 RX Antenna Ports

3GPP TS 36.101

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

RAN4

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

8.10.1.1.3

10.5.5.37 Non-3GPP NW provided policies

The purpose of the Non-3GPP NW provided policies information element is to indicate to the MS whether emergency numbers provided via non-3GPP access (see 3GPP TS 24.302[ Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networks; Stage 3 ] [156]) can be used to initiate UE detected emergency calls. The Non-3GPP NW provided policies is indicated by the network and sent with the ATTACH ACCEPT message or ROUTING AREA UPDATE ACCEPT message to the mobile station. The Non-3GPP NW provided policies information element is coded as shown in figure 10.5.5.37-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.5.37-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The Non-3GPP NW provided policies is a type 1 information element. Figure 10.5.5.37-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Non-3GPP NW provided policies IE Table 10.5.5.37-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Non-3GPP NW provided policies IE

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

6.46.9 UE-Satellite-UE communication

Subject to regulatory requirements and operator’s policy, a 5G system with satellite access shall support UE-Satellite-UE communication regardless of whether the feeder link is available or not. Subject to regulatory requirements and operator’s policy, a 5G system with satellite access shall be able to provide QoS control of a UE-Satellite-UE communication. Subject to regulatory requirements and operator’s policy, a 5G system with satellite access shall be able to support different types of UE-Satellite-UE communication (e.g. voice, messaging, broadband, unicast, multicast, broadcast).

3GPP TS 22.261

Service requirements for the 5G system

SA WG1

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

6.46.9

– RRCResume

The RRCResume message is used to resume the suspended RRC connection. Signalling radio bearer: SRB1 RLC-SAP: AM Logical channel: DCCH Direction: Network to UE RRCResume message -- ASN1START -- TAG-RRCRESUME-START RRCResume ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { rrcResume RRCResume-IEs, criticalExtensionsFuture SEQUENCE {} } } RRCResume-IEs ::= SEQUENCE { radioBearerConfig RadioBearerConfig OPTIONAL, -- Need M masterCellGroup OCTET STRING (CONTAINING CellGroupConfig) OPTIONAL, -- Need M measConfig MeasConfig OPTIONAL, -- Need M fullConfig ENUMERATED {true} OPTIONAL, -- Need N lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension RRCResume-v1560-IEs OPTIONAL } RRCResume-v1560-IEs ::= SEQUENCE { radioBearerConfig2 OCTET STRING (CONTAINING RadioBearerConfig) OPTIONAL, -- Need M sk-Counter SK-Counter OPTIONAL, -- Need N nonCriticalExtension RRCResume-v1610-IEs OPTIONAL } RRCResume-v1610-IEs ::= SEQUENCE { idleModeMeasurementReq-r16 ENUMERATED {true} OPTIONAL, -- Need N restoreMCG-SCells-r16 ENUMERATED {true} OPTIONAL, -- Need N restoreSCG-r16 ENUMERATED {true} OPTIONAL, -- Need N mrdc-SecondaryCellGroup-r16 CHOICE { nr-SCG-r16 OCTET STRING (CONTAINING RRCReconfiguration), eutra-SCG-r16 OCTET STRING } OPTIONAL, -- Cond RestoreSCG needForGapsConfigNR-r16 SetupRelease {NeedForGapsConfigNR-r16} OPTIONAL, -- Need M nonCriticalExtension RRCResume-v1700-IEs OPTIONAL } RRCResume-v1700-IEs ::= SEQUENCE { sl-ConfigDedicatedNR-r17 SetupRelease {SL-ConfigDedicatedNR-r16} OPTIONAL, -- Cond L2RemoteUE sl-L2RemoteUE-Config-r17 SetupRelease {SL-L2RemoteUE-Config-r17} OPTIONAL, -- Cond L2RemoteUE needForGapNCSG-ConfigNR-r17 SetupRelease {NeedForGapNCSG-ConfigNR-r17} OPTIONAL, -- Need M needForGapNCSG-ConfigEUTRA-r17 SetupRelease {NeedForGapNCSG-ConfigEUTRA-r17} OPTIONAL, -- Need M scg-State-r17 ENUMERATED {deactivated} OPTIONAL, -- Need N appLayerMeasConfig-r17 AppLayerMeasConfig-r17 OPTIONAL, -- Need M nonCriticalExtension RRCResume-v1800-IEs OPTIONAL } RRCResume-v1800-IEs ::= SEQUENCE { needForInterruptionConfigNR-r18 ENUMERATED { enabled, disabled } OPTIONAL, -- Need M nonCriticalExtension SEQUENCE {} OPTIONAL } -- TAG-RRCRESUME-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

5.5.2.2.1 UE initiated detach procedure initiation

The detach procedure is initiated by the UE by sending a DETACH REQUEST message (see example in figure 5.5.2.2.1.1). The Detach type IE included in the message indicates whether detach is due to a "switch off" or not. The Detach type IE also indicates whether the detach is for EPS services only, for non-EPS services only, or for both. If the UE has a mapped EPS security context as the current EPS security context, the UE shall set the type of security context flag to "mapped security context". Otherwise, the UE shall set the type of security context flag to "native security context". If the UE has a valid GUTI, the UE shall populate the EPS mobile identity IE with the valid GUTI. If the UE does not have a valid GUTI, the UE shall populate the EPS mobile identity IE with its IMSI. If the UE does not have a valid GUTI and it does not have a valid IMSI, then the UE shall populate the EPS mobile identity IE with its IMEI. NOTE: During the attach for emergency bearer services or attach for access to RLOS when the UE (with no USIM or invalid USIM) is in EMM-REGISTERED-INITIATED STATE, the UE has neither a valid GUTI nor a valid IMSI. If the detach is not due to switch off and the UE is in the state EMM-REGISTERED or EMM-REGISTERED-INITIATED, timer T3421 shall be started in the UE after the DETACH REQUEST message has been sent. If the detach type indicates that the detach is for non-EPS services only the UE shall enter the state EMM-REGISTERED.IMSI-DETACH-INITIATED, otherwise the UE shall enter the state EMM-DEREGISTERED-INITIATED. If the detach type indicates that the detach is for non-EPS services or both EPS and non-EPS services, the UE shall enter the state MM IMSI DETACH PENDING. If the UE to be switched off is not operating in NB-S1 mode and not operating in WB-S1 mode in any enhanced coverage CE mode, the UE shall try for a period of 5 seconds to send the DETACH REQUEST message. If the UE to be switched off: - is operating in NB-S1 mode, then the UE should try for at least a period of 85 seconds to send the DETACH REQUEST; or - is operating in WB-S1 mode in any enhanced coverage CE mode, then the UE should try for at least a period of 14 seconds to send the DETACH REQUEST. During this period, the UE may be switched off as soon as the DETACH REQUEST message has been sent. After the last DETACH REQUEST message is sent, the UE shall proceed as follows: - if the current EPS security context is a native EPS security context, then the UE shall store the current EPS security context as specified in annex C and mark it as valid; - else if the current EPS security context is a mapped EPS security context and a non-current full native EPS security context exists, then the UE shall store the non-current EPS security context as specified in annex C and mark it as valid, and finally the UE shall delete any mapped EPS security context or partial native EPS security context. Figure 5.5.2.2.1.1: UE initiated detach 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

5.5.2.2.1

10.5.4.3 Non-locking shift procedure

The non-locking shift procedure provides a temporary shift to the specified lower or higher codeset. The non-locking shift procedure uses a type 1 information element to indicate the codeset to be used to interpret the next information element. After the interpretation of the next information element, the active codeset is again used for interpreting any following information elements. For example, codeset 0 is active at the beginning of message content analysis. If a non-locking shift to codeset 6 is encountered, only the next information element is interpreted according to the information element identifiers assigned in codeset 6. After this information element is interpreted, codeset 0 will again be used to interpret the following information elements. A non-locking shift information element indicating the current codeset shall not be regarded as an error. A locking shift information element shall not follow directly a non-locking shift information element. If this combination is received, it shall be interpreted as though a locking shift information element had been received. The non-locking shift information element uses the type 1 information format and coding shown in figure 10.5.86/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.99/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.86/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Non-locking shift element Table 10.5.99/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Non-locking shift 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.3

16a.4.6 STA Command

The STA command, defined in IETF RFC 6733 (Diameter Base) [111], is indicated by the Command-Code field set to 275 and the ‘R’ bit cleared in the Command Flags field. It is sent by the Diameter server to the GGSN/P-GW in response to an STR command. The relevant AVPs that are of use for the Gi/Sgi interface are detailed in the ABNF description below. Other valid AVPs for this command are not used for Gi/Sgi purposes and should be ignored by the receiver or processed according to the relevant specifications. Message Format: <ST-Answer> ::= < Diameter Header: 275, PXY > < Session-Id > { Result-Code } { Origin-Host } { Origin-Realm } [ User-Name ] * [ Class ] [ Error-Message ] [ Error-Reporting-Host ] [ Failed-AVP ] [ Origin-State-Id ] * [ Redirect-Host ] [ Redirect-Host-Usage ] [ Redirect-Max-Cache-Time ] * [ Proxy-Info ] * [ AVP ]

3GPP TS 29.061

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

CT WG3

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

16a.4.6

9.9.4.2.1 FDD

The minimum performance requirement in Table 9.9.4.2.1-2 is defined as a) The ratio of the throughput obtained when transmitting based on UE reported RI and that obtained when transmitting with fixed rank 1 shall be ≥ ; b) The ratio of the throughput obtained when transmitting based on UE reported RI and that obtained when transmitting with fixed rank 2 shall be ≥ ; For the parameters specified in Table 9.9.4.2.1-1, and using the downlink physical channels specified in Annex C.3.2, the minimum requirements are specified in Table 9.9.4.2.1-2. Table 9.9.4.2.1-1: RI Test (FDD) Table 9.9.4.2.1-2: Minimum requirement (FDD)

3GPP TS 36.101

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

RAN4

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

9.9.4.2.1

5.31.9 Support for Monitoring Events

The Monitoring Events feature is intended for monitoring of specific events in the 3GPP system and reporting such Monitoring Events via the NEF. The feature allows NFs in 5GS to be configured to detect specific events and report the events to the requested party. Clause 5.20 further discusses the Monitoring capabilities of the NEF. For CIoT, the list of supported monitoring events is specified in Table 4.15.3.1-1 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. Support for Monitoring Events can be offered via AMF, UDM, NSACF and SMF, and can be reported via the NEF, as specified in clause 4.15.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3].

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.31.9

10.9.2 MR-DC with 5GC

The ng-eNB/gNB to MN change procedure is used to transfer UE context data from a source ng-eNB/gNB to a target MN that adds an SN during the handover. Only the cases where the source node and the target MN belong to the same RAT (i.e. they are both ng-eNBs or both gNBs) are supported. Figure 10.9.2-1: ng-eNB/gNB to MN change procedure Figure 10.9.2-1 shows an example signalling flow for ng-eNB/gNB to MN change: 1. The source ng-eNB/gNB starts the handover procedure by initiating the Xn Handover Preparation procedure. 2. The target MN sends SN Addition Request to the target SN. 3. The target SN replies with SN Addition Request Acknowledge. If data forwarding is needed, the target SN provides forwarding addresses to the target MN. NOTE 0: Void. 3a. For SN terminated bearers using MCG resources, the target MN provides Xn-U DL TNL address information in the Xn-U Address Indication message. 4. The target MN includes within the Handover Request Acknowledge message the SN RRC reconfiguration message to be sent to the UE that includes the SCG configuration to perform the handover, and may also provide forwarding addresses to the source ng-eNB/gNB. 5. The source ng-eNB/gNB triggers the UE to perform handover and apply the new configuration. 6/7. The UE synchronizes to the target MN and replies with MN RRC reconfiguration complete message including the SN RRC reconfiguration complete message. 8. If configured with bearers requiring SCG radio resources, the UE synchronizes to the target SN. NOTE 1: The order the UE performs Random Access towards the target MN (step 6) and performs the Random Access procedure towards the target SN (step 8) is not defined. 9. If the RRC connection reconfiguration procedure was successful, the target MN informs the target SN via SN Reconfiguration Complete message. 10. For bearers using RLC AM, the source ng-eNB/gNB sends the SN Status Transfer message, which the target MN forwards then to the target SN, if needed. 11. Data forwarding from the source ng-eNB/gNB takes place. 12-15. The target MN initiates the PDU Session Path Switch procedure. NOTE 2: If new UL TEIDs of the UPF are included, the target MN performs MN initiated SN Modification procedure to provide them to the target SN. 16. The target MN initiates the UE Context Release procedure towards the source ng-eNb/gNB.

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

15.5.5.3 Dynamic coverage configuration changes

An NG-RAN node may autonomously adjust within and switch between coverage configurations. When a change is executed, a NG-RAN node may notify its neighbour NG-RAN nodes using the NG-RAN NODE CONFIGURATION UPDATE message with the list of cells and SSBs with modified coverage included. The list contains the CGI of each modified cell with its coverage state indicator and optionally the SSB index of each modified SSB with its coverage state indicator. The coverage state indicator may be used at the receiving NG-RAN node to adjust the functions of the Mobility Robustness Optimisation, e.g. by using the coverage state indicator to retrieve a previously stored Mobility Robustness Optimisation state. The coverage state indicator may also be used at the receiving NG-RAN node to adopt coverage configurations matching with neighbouring cells coverage configurations. If the list includes indication about planned reconfiguration and possibly a list of replacing cells, the receiving NG-RAN node may use this to avoid connection or re-establishment failures during the reconfiguration. Also, if the sending NG-RAN node adds cells in inactive state, the receiving NG-RAN node may use this information to avoid connection or re-establishment failures. The receiving NG-RAN node may also use the notification to reduce the impact on mobility. The receiving NG-RAN node should avoid triggering handovers towards cell(s) that are indicated to be inactive.

3GPP TS 38.300

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

RAN2

3GPP Series : 38 , Radio technology beyond LTE

15.5.5.3

8.3.18.1 Message definition

This message is sent by the network to the UE to request modification of an active EPS bearer context, or to request re-negotiation of header compression configuration associated to an EPS bearer context if the UE has previously indicated support of Control plane CIoT EPS optimization and Header compression for control plane CIoT EPS optimization. See table 8.3.18.1. Message type: MODIFY EPS BEARER CONTEXT REQUEST Significance: dual Direction: network to UE Table 8.3.18.1: MODIFY EPS BEARER CONTEXT REQUEST message content

3GPP TS 24.301

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

CT WG1

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

8.3.18.1

4.2.1.2 Triggered Messages

The UDP Destination Port value of a GTPv2 Triggered message and for a Triggered Reply message shall be the value of the UDP Source Port of the corresponding message to which this GTPv2 entity is replying, except in the case of the SGSN pool scenario. The UDP Source Port of a GTPv2 Triggered message and for a Triggered Reply message shall be the value from the UDP Destination Port of the corresponding message to which this GTPv2 entity is replying, except in the case of the SGSN pool scenario. In the SGSN pool scenario, if the Identification Request, the Context Request or the Suspend Notification messages have been forwarded by another SGSN in the pool, the UDP Destination Port for the Identification Response, the Context Response or the Suspend Acknowledge message shall be determined in the following way. The value from the information element "UDP Source Port Number", which was sent in the corresponding forwarded request, shall be copied into the UDP Destination Port field. The UDP Source Port for the Identification Response, the Context Response or the Suspend Acknowledge message may be a locally allocated port number at the sending GTP entity. In the handover scenario when the CIoT feature is deployed, if the Forward Relocation Request message has been forwarded by the target MME, the UDP Destination Port for the Forward Relocation Response shall be set to the value of Source UDP Port Number IE included in the Forward Relocation Request message; the UDP Source Port for the Forward Relocation Response message may be a locally allocated port number at the sending GTP entity.

3GPP TS 29.274

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

CT WG4

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

4.2.1.2

6.1.3.19 Downlink Channel Quality Report and AS RAI MAC Control Element

DCQR and AS RAI MAC control element is identified by a MAC PDU subheader with LCID as specified in Table 6.2.1-2. A MAC PDU shall contain at most one DCQR and AS RAI MAC control element. It has a fixed size and consists of a single octet defined as follows (Figure 6.1.3.19-1): - R: Reserved bit, set to "0"; - AS RAI: The field corresponds to Access Stratum Release Assistance Indication as shown in Table 6.1.3.19-1. The length of the field is 2 bits; - Quality Report: For a NB-IoT UE, if npdsch-16QAM-Config is not configured, the report mapping is defined in Table 9.1.22.15-1 in TS 36.133[ Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for support of radio resource management ] [9] and if npdsch-16QAM-Config is configured the report mapping is defined in Table 9.1.22.17-1 in TS 36.133[ Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for support of radio resource management ] [9]. For a BL UE or UE in CE, the field corresponds to DL channel quality report as defined in TS 36.133[ Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for support of radio resource management ] [9]. The length of the field is 4 bits. Figure 6.1.3.19-1: DCQR and AS RAI MAC control element Table 6.1.3.19-1: Values for AS RAI

3GPP TS 36.321

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

RAN2

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

6.1.3.19

6.2.4.3 Additional RG related requirements for IP address allocation

If IPv6 PDU session type or IPv4v6 PDU session type is selected, an IPv6 address, one or more IPv6 prefixes or both are allocated to the 5G-RG or the W-AGF acting on behalf of the FN-RG (or on behalf of the N5GC device). If the 5G-RG or the W-AGF acting on behalf of the FN-RG (or on behalf of the N5GC device) receives a Router Advertisement Message as specified in IETF RFC 4861 [38B] with the "Managed address configuration" flag set to zero, the 5G-RG and the W-AGF acting on behalf of the FN-RG (or on behalf of the N5GC device): a) shall obtain /64 IPv6 prefix via IPv6 stateless address autoconfiguration as specified in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8] and IETF RFC 4862 [39]; b) may obtain IPv6 configuration parameters via stateless DHCPv6 as specified in IETF RFC 8415 [33D]; and c) may request additional IPv6 prefixes using DHCPv6. If the 5G-RG and the W-AGF acting on behalf of the FN-RG (or on behalf of the N5GC device) request IPv6 prefixes using DHCPv6, the 5G-RG and the W-AGF acting on behalf of the FN-RG (or on behalf of the N5GC device) shall act as a "Requesting Router" as described in IETF RFC 8415 [33D], shall perform procedures described in subclause 6.2.4.2a. Additionally, the 5G-RG or the W-AGF acting on behalf of the FN-RG (or on behalf of the N5GC device) may include DHCPv6 OPTION_ORO option with the OPTION_PD_EXCLUDE option code as specified in IETF RFC 6603 [40A] in the DHCP. If the 5G-RG or the W-AGF acting on behalf of the FN-RG (or on behalf of the N5GC device) receives a Router Advertisement Message as specified in IETF RFC 4861 [38B] with the "Managed address configuration" flag set to one, the 5G-RG and the W-AGF acting on behalf of the FN-RG (or on behalf of the N5GC device): a) shall obtain an IPv6 address via DHCPv6 and the DHCPv6 Identity association for non-temporary addresses option as specified in IETF RFC 8415 [33D]; b) may obtain IPv6 configuration parameters via DHCPv6 as specified in IETF RFC 8415 [33D]; and c) may request IPv6 prefixes using DHCPv6. If the 5G-RG and the W-AGF acting on behalf of the FN-RG (or on behalf of the N5GC device) requests IPv6 prefixes using DHCPv6, the 5G-RG and the W-AGF acting on behalf of the FN-RG (or on behalf of the N5GC device) shall act as a "Requesting Router" as described in IETF RFC 8415 [33D], shall perform procedures described in subclause 6.2.4.2a. Additionally, the 5G-RG or the W-AGF acting on behalf of the FN-RG (or on behalf of the N5GC device) may include DHCPv6 OPTION_ORO option with the OPTION_PD_EXCLUDE option code as specified in IETF RFC 6603 [40A] in the DHCP message. The 5G-RG or the W-AGF acting on behalf of the FN-RG (or on behalf of the N5GC device) may include both IA_PD option and IA_NA option to request the delegated prefix together with the IPv6 address in the same DHCPv6 message. NOTE: The 5G-RG and the W-AGF acting on behalf of the FN-RG (or on behalf of the N5GC device) can send multiple DHCPv6 requests with different DHCPv6 Identity association for non-temporary addresses options when the 5G-RG or the FN-RG acts as a DHCP relay for devices behind the 5G-RG or the FN-RG. The 5G-RG may obtain ACS information via DHCP as specified in subclause 3.1 of BBF TR-069 [49] or in BBF TR-369 [50] R-DIS.1 and R-DIS.2.

3GPP TS 24.501

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

CT WG1

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

6.2.4.3

9.9.4.2 APN aggregate maximum bit rate

The purpose of the APN aggregate maximum bit rate information element is to indicate the initial subscribed APN-AMBR when the UE establishes a PDN connection or to indicate the new APN-AMBR if it is changed by the network. The APN aggregate maximum bit rate information element is coded as shown in figure 9.9.4.2.1 and table 9.9.4.2.1. The APN aggregate maximum bit rate is a type 4 information element with a minimum length of 4 octets and a maximum length of 8 octets. Octets 5-8 are optional. If octet 5 is included, then octet 6 shall also be included, and octets 7-8 may be included. If octet 7 is included, then octet 8 shall also be included. The length of the APN-AMBR IE can be either 4 octets, 6 octets or 8 octets. Figure 9.9.4.2.1: APN aggregate maximum bit rate information element Table 9.9.4.2.1: APN aggregate maximum bit rate information element

3GPP TS 24.301

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

CT WG1

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

9.9.4.2

– SIB17

SIB17 contains configurations of TRS resources for idle/inactive UEs. SIB17 information element -- ASN1START -- TAG-SIB17-START SIB17-r17 ::= SEQUENCE { segmentNumber-r17 INTEGER (0..63), segmentType-r17 ENUMERATED {notLastSegment, lastSegment}, segmentContainer-r17 OCTET STRING } SIB17-IEs-r17 ::= SEQUENCE { trs-ResourceSetConfig-r17 SEQUENCE (SIZE (1..maxNrofTRS-ResourceSets-r17)) OF TRS-ResourceSet-r17, validityDuration-r17 ENUMERATED {t1, t2, t4, t8, t16, t32, t64, t128, t256, t512, infinity, spare5, spare4, spare3, spare2, spare1} OPTIONAL, -- Need S lateNonCriticalExtension OCTET STRING OPTIONAL, ... } TRS-ResourceSet-r17 ::= SEQUENCE { powerControlOffsetSS-r17 ENUMERATED {db-3, db0, db3, db6}, scramblingID-Info-r17 CHOICE { scramblingIDforCommon-r17 ScramblingId, scramblingIDperResourceListWith2-r17 SEQUENCE (SIZE (2)) OF ScramblingId, scramblingIDperResourceListWith4-r17 SEQUENCE (SIZE (4)) OF ScramblingId, ... }, firstOFDMSymbolInTimeDomain-r17 INTEGER (0..9), startingRB-r17 INTEGER (0..maxNrofPhysicalResourceBlocks-1), nrofRBs-r17 INTEGER (24..maxNrofPhysicalResourceBlocksPlus1), ssb-Index-r17 SSB-Index, periodicityAndOffset-r17 CHOICE { slots10 INTEGER (0..9), slots20 INTEGER (0..19), slots40 INTEGER (0..39), slots80 INTEGER (0..79) }, frequencyDomainAllocation-r17 BIT STRING (SIZE (4)), indBitID-r17 INTEGER (0..5), nrofResources-r17 ENUMERATED {n2, n4} } -- TAG-SIB17-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

– SL-ConfigDedicatedNR

The IE SL-ConfigDedicatedNR specifies the dedicated configuration information for NR sidelink communication/discovery/positioning. SL-ConfigDedicatedNR information element -- ASN1START -- TAG-SL-CONFIGDEDICATEDNR-START SL-ConfigDedicatedNR-r16 ::= SEQUENCE { sl-PHY-MAC-RLC-Config-r16 SL-PHY-MAC-RLC-Config-r16 OPTIONAL, -- Need M sl-RadioBearerToReleaseList-r16 SEQUENCE (SIZE (1..maxNrofSLRB-r16)) OF SLRB-Uu-ConfigIndex-r16 OPTIONAL, -- Need N sl-RadioBearerToAddModList-r16 SEQUENCE (SIZE (1..maxNrofSLRB-r16)) OF SL-RadioBearerConfig-r16 OPTIONAL, -- Need N sl-MeasConfigInfoToReleaseList-r16 SEQUENCE (SIZE (1..maxNrofSL-Dest-r16)) OF SL-DestinationIndex-r16 OPTIONAL, -- Need N sl-MeasConfigInfoToAddModList-r16 SEQUENCE (SIZE (1..maxNrofSL-Dest-r16)) OF SL-MeasConfigInfo-r16 OPTIONAL, -- Need N t400-r16 ENUMERATED {ms100, ms200, ms300, ms400, ms600, ms1000, ms1500, ms2000} OPTIONAL, -- Need M ..., [[ sl-PHY-MAC-RLC-Config-v1700 SetupRelease { SL-PHY-MAC-RLC-Config-v1700 } OPTIONAL, -- Need M sl-DiscConfig-r17 SetupRelease { SL-DiscConfig-r17} OPTIONAL -- Need M ]], [[ sl-DiscConfig-v1800 SetupRelease { SL-DiscConfig-v1800} OPTIONAL -- Need M ]] } SL-DestinationIndex-r16 ::= INTEGER (0..maxNrofSL-Dest-1-r16) SL-PHY-MAC-RLC-Config-r16::= SEQUENCE { sl-ScheduledConfig-r16 SetupRelease { SL-ScheduledConfig-r16 } OPTIONAL, -- Need M sl-UE-SelectedConfig-r16 SetupRelease { SL-UE-SelectedConfig-r16 } OPTIONAL, -- Need M sl-FreqInfoToReleaseList-r16 SEQUENCE (SIZE (1..maxNrofFreqSL-r16)) OF SL-Freq-Id-r16 OPTIONAL, -- Need N sl-FreqInfoToAddModList-r16 SEQUENCE (SIZE (1..maxNrofFreqSL-r16)) OF SL-FreqConfig-r16 OPTIONAL, -- Need N sl-RLC-BearerToReleaseList-r16 SEQUENCE (SIZE (1..maxSL-LCID-r16)) OF SL-RLC-BearerConfigIndex-r16 OPTIONAL, -- Need N sl-RLC-BearerToAddModList-r16 SEQUENCE (SIZE (1..maxSL-LCID-r16)) OF SL-RLC-BearerConfig-r16 OPTIONAL, -- Need N sl-MaxNumConsecutiveDTX-r16 ENUMERATED {n1, n2, n3, n4, n6, n8, n16, n32} OPTIONAL, -- Need M sl-CSI-Acquisition-r16 ENUMERATED {enabled} OPTIONAL, -- Need R sl-CSI-SchedulingRequestId-r16 SetupRelease {SchedulingRequestId} OPTIONAL, -- Need M sl-SSB-PriorityNR-r16 INTEGER (1..8) OPTIONAL, -- Need R networkControlledSyncTx-r16 ENUMERATED {on, off} OPTIONAL -- Need M } SL-PHY-MAC-RLC-Config-v1700 ::= SEQUENCE { sl-DRX-Config-r17 SL-DRX-Config-r17 OPTIONAL, -- Need M sl-RLC-ChannelToReleaseList-r17 SEQUENCE (SIZE (1..maxSL-LCID-r16)) OF SL-RLC-ChannelID-r17 OPTIONAL, -- Cond L2U2N sl-RLC-ChannelToAddModList-r17 SEQUENCE (SIZE (1..maxSL-LCID-r16)) OF SL-RLC-ChannelConfig-r17 OPTIONAL, -- Cond L2U2N ..., [[ sl-RLC-BearerToAddModListSizeExt-v1800 SEQUENCE (SIZE (1..maxSL-LCID-r16)) OF SL-RLC-BearerConfig-r16 OPTIONAL, -- Need N sl-RLC-BearerToReleaseListSizeExt-v1800 SEQUENCE (SIZE (1..maxSL-LCID-r16)) OF SL-RLC-BearerConfigIndex-v1800 OPTIONAL, -- Need N sl-FreqInfoToAddModListExt-v1800 SEQUENCE (SIZE (1..maxNrofFreqSL-r16)) OF SL-FreqConfigExt-v1800 OPTIONAL, -- Need N sl-LBT-SchedulingRequestId-r18 SetupRelease {SchedulingRequestId} OPTIONAL, -- Need M sl-SyncFreqList-r18 SEQUENCE (SIZE (1..maxNrofFreqSL-r16)) OF SL-Freq-Id-r16 OPTIONAL, -- Need M sl-SyncTxMultiFreq-r18 ENUMERATED {true} OPTIONAL, -- Need R sl-MaxTransPowerCA-r18 P-Max OPTIONAL, -- Need R sl-SCCH-CarrierSetConfig-r18 SetupRelease {SL-SCCH-CarrierSetConfig-r18} OPTIONAL -- Need R ]] } SL-DiscConfig-r17::= SEQUENCE { sl-RelayUE-Config-r17 SetupRelease { SL-RelayUE-Config-r17} OPTIONAL, -- Cond L2RelayUE sl-RemoteUE-Config-r17 SetupRelease { SL-RemoteUE-Config-r17} OPTIONAL -- Cond L2RemoteUE } SL-DiscConfig-v1800 ::= SEQUENCE { sl-RelayUE-ConfigU2U-r18 SetupRelease { SL-RelayUE-ConfigU2U-r18} OPTIONAL, -- Cond U2URelayUE sl-RemoteUE-ConfigU2U-r18 SetupRelease { SL-RemoteUE-ConfigU2U-r18} OPTIONAL -- Cond U2URemoteUE } SL-SCCH-CarrierSetConfig-r18 ::= SEQUENCE { sl-DestinationList-r18 SEQUENCE (SIZE (1..maxNrofSL-Dest-r16)) OF SL-DestinationIdentity-r16, sl-SRB-Identity-r18 SEQUENCE (SIZE (1..3)) OF SRB-Identity, sl-AllowedCarrierFreqSet1-r18 SEQUENCE (SIZE (1..maxNrofFreqSL-r16)) OF INTEGER (1..maxNrofFreqSL-r16), sl-AllowedCarrierFreqSet2-r18 SEQUENCE (SIZE (1..maxNrofFreqSL-r16)) OF INTEGER (1..maxNrofFreqSL-r16) } -- TAG-SL-CONFIGDEDICATEDNR-STOP -- ASN1STOP

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

–

17.5.2 Session start procedure

The BM-SC initiates the MBMS session start procedure when it is ready to send data. This informs the GGSN of the imminent start of the transmission and MBMS session attributes are provided to the GGSNs included in the list of downstream nodes in BM-SC. For a multicast MBMS service these are the GGSNs that have previously registered for the corresponding MBMS bearer service. The bearer plane is allocated. BM-SC and GGSN shall at least support IP unicast encapsulation of IP multicast datagrams, which shall be default mode of sending user plane data. BM-SC may support sending user plane IP multicast datagrams to GGSN, and GGSN also may support this mode of operation. Figure 27: MBMS Session Start procedure 1. The BM-SC sends a RAR message to indicate the impending start of the transmission and to provide the session attributes to the GGSNs listed in the "list of downstream nodes" parameter of the corresponding MBMS Bearer Context. BM-SC may indicate to GGSN that BM-SC supports sending the user plane IP multicast data without IP unicast encapsulation. In such case BM-SC shall send multicast source address as specified by IETF RFC 4604 [73] and IETF RFC 4607 [74]. The BM-SC sets the state attribute of its MBMS Bearer Context to ‘Active’. By sending "CN IP Multicast Distribution" parameter to GGSN, the BM-SC indicates if IP multicast mechanism should be used for user plane data distribution to UTRAN. "MBMS HC Indicator" parameter, if present, indicates that a header compression is used for MBMS user plane data. 2. For a broadcast MBMS bearer service the GGSN creates an MBMS Bearer Context. The GGSN stores the session attributes in the MBMS Bearer Context, sets the state attribute of its MBMS Bearer Context to ‘Active’ and sends a RAA message to the BM-SC. In case GGSN receives BM-SC multicast source address, which indicates BM-SC support for both modes of sending user plane data, GGSN decides in which mode GGSN shall receive the user plane data. In case GGSN decides to receive unicast encapsulated data, then GGSN shall send own IP address and UDP port for the encapsulating unicast IP and UDP layer of the user plane to BM-SC. In case GGSN decides to receive IP multicast packets, then GGSN shall join the multicast group as specified by IETF RFC 4604 [73] and IETF RFC 4607 [74], and indicate to BM-SC about the decision.

3GPP TS 29.061

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

CT WG3

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

17.5.2

5.5.1.2.5B1 Attach by a UE transferring an emergency PDU session using a standalone PDN CONNECTIVITY REQUEST message

If the network cannot accept attach request including a PDN CONNECTIVITY REQUEST message with request type set to "handover" and the UE also intends to transfer an emergency PDU session, the UE shall attempt EPS attach for emergency bearer services including a PDN CONNECTIVITY REQUEST message with request type set to "handover of emergency bearer services" for the emergency PDU session. If the attach request, including a PDN CONNECTIVITY REQUEST message with request type set "handover", fails due to abnormal case a) in clause 5.5.1.2.6 and the UE intends to transfer an emergency PDU session, the UE shall attempt EPS attach including a PDN CONNECTIVITY REQUEST message with request type set to "handover of emergency bearer services" for the emergency PDU session. If the attach request including a PDN CONNECTIVITY REQUEST message with request type set "handover" fails due to abnormal cases b), c), d) or o) in clause 5.5.1.2.6, the UE intends to transfer an emergency PDU session: - if an EMM cause set to #19 "ESM failure" is received, the UE shall attempt EPS attach; and - otherwise, the UE shall attempt EPS attach for emergency bearer services, with the ATTACH REQUEST message including a PDN CONNECTIVITY REQUEST message with request type set to "handover of emergency bearer services" for the emergency PDU session.

3GPP TS 24.301

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

CT WG1

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

5.5.1.2.5B1

4.5.8.2 Mean carrier transmit power

a) This measurement provides the mean carrier transmit power in the measurement granularity interval. b) SI c) This measurement is obtained by computing the mean value of the total carrier power transmitted in the cell within the measurement granularity period. The power includes all radio power transmitted, included common channels, traffic channels, control channels. The value is expressed in dBm. d) Float in dBm. e) CARR.AvgTxPwr 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.5.8.2

9.4.17.1 T3302 value

This IE may be included to indicate a value for the T3302 timer. In Iu mode, if the MS is not attached for emergency bearer services, the network shall not include this IE if this message is to be sent non-integrity protected. If the MS is attached for emergency bearer services, the network may include this IE if this message is to be sent non-integrity protected. In Iu mode, the MS not attached for emergency bearer services shall ignore the contents of this IE if this message is received without integrity protection. If the MS is attached for emergency bearer services, the MS shall use the received contents of this IE if this message is received without integrity protection. If this IE is not included or if in Iu mode the message is not integrity protected, the MS shall use the default value.

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

5.8.9.8.3 Reception of RemoteUEInformationSidelink message by the L2 U2N Relay UE

The L2 U2N Relay UE shall: 1> if the RemoteUEInformationSidelink includes the sl-PagingInfo-RemoteUE: 2> if the UE is in RRC_CONNECTED on an active BWP with common search space configured including pagingSearchSpace; or 2> if the UE is in RRC_IDLE or RRC_INACTIVE: 3> if the sl-PagingInfo-RemoteUE is set to setup: 4> monitor the Paging message at the L2 U2N Remote UE's paging occasion calculated according to sl-PagingIdentityRemoteUE and sl-PagingCycleRemoteUE included in sl-PagingInfo-RemoteUE; 3> else (the sl-PagingInfo-RemoteUE is set to release): 4> stop monitoring the Paging message at the L2 U2N Remote UE's paging occasion; 4> release the received paging information in sl-PagingInfo-RemoteUE; 2> else (the UE is in RRC_CONNECTED on an active BWP without pagingSearchSpace configured): 3> if the sl-PagingInfo-RemoteUE is set to setup: 4> include the received sl-PagingIdentityRemoteUE in SidelinkUEInformationNR message and perform Sidelink UE information transmission in accordance with 5.8.3; 3> else (the sl-PagingInfo-RemoteUE is set to release): 4> initiate transmission of the SidelinkUEInformationNR message to release the sl-PagingIdentityRemoteUE in SidelinkUEInformationNR message in accordance with 5.8.3; 4> release the received paging information in sl-PagingInfo-RemoteUE; 1> if the RemoteUEInformationSidelink includes the sl-RequestedSIB-List: 2> if the sl-RequestedSIB-List is set to setup: 3> if the L2 U2N Relay UE has not stored a valid version of SIB(s) indicated in sl-RequestedSIB-List: 4> perform acquisition of the system information indicated in sl-RequestedSIB-List in accordance with 5.2.2; 3> perform the Uu message transfer procedure in accordance with 5.8.9.9; 2> if the sl-RequestedSIB-List is set to release: 3> release received SIB request in sl-RequestedSIB-List; 1> if the RemoteUEInformationSidelink includes the sl-RequestedPosSIB-List: 2> if the sl-RequestedPosSIB-List is set to setup: 3> if the L2 U2N Relay UE has not stored a valid version of posSIB(s) indicated in sl-RequestedPosSIB-List: 4> perform acquisition of the positioning system information indicated in sl-RequestedPosSIB-List in accordance with 5.2.2; 3> perform the Uu message transfer procedure in accordance with 5.8.9.9; 2> if the sl-RequestedPosSIB-List is set to release: 3> release received posSIB request in sl-RequestedPosSIB-List. 1> if the RemoteUEInformationSidelink includes the connectionForMP: 2> if the L2 U2N Relay UE is in RRC_IDLE: 3> initiate an RRC connection establishment as specified in 5.3.3; 2> else if the L2 U2N Relay UE is in RRC_INACTIVE: 3> initiate an RRC connection resume as specified in 5.3.13;

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

5.8.9.8.3

10.5.4.15 Facility

The purpose of the facility information element is to transport supplementary service related information. Within the scope of 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] the content of the Facility information field is an array of octets. The usage of this transportation mechanism is defined in 3GPP TS 24.080[ Mobile radio interface layer 3 supplementary services specification; Formats and coding ] [24]. The facility information element is coded as shown in figure 10.5.101/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The facility is a type 4 information element with a minimum length of 2 octets. No upper length limit is specified except for that given by the maximum number of octets in a L3 message (see 3GPP TS 44.006[ None ] [19]). Figure 10.5.101/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ]

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

8.2.13.5 Universal time and local time zone

This IE may be sent by the network. The UE should assume that this time zone applies to the tracking area the UE is currently in, and also applies to the tracking area list if available in the UE. The UE shall not assume that the time information is accurate. NOTE: The time information can be inaccurate, especially when the TAI list includes tracking areas belonging to different time zones. If the local time zone has been adjusted for daylight saving time, the network shall indicate this by including the Network daylight saving time IE.

3GPP TS 24.301

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

CT WG1

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

8.2.13.5

5.10.3.3 Multicast MRB release

Upon release of a multicast MRB, the UE shall: 1> release the PDCP entity, RLC entity as well as the related MAC and physical layer configuration; 1> if the SDAP entity associated with the corresponding mbs-SessionId has no associated MRB: 2> release the SDAP entity, as specified in TS 37.324[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Service Data Adaptation Protocol (SDAP) specification ] [24] clause 5.1.2; 2> indicate the release of the user plane resources for the mbs-SessionId to upper layers.

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

5.10.3.3

4.23.3 5GS mobility management via a satellite NG-RAN cell

For 5GS mobility management via a satellite NG-RAN cell the UE shall apply the value of the applicable NAS timer indicated in table 10.2.1 for access via a satellite NG-RAN cell. NOTE 1: The applied NAS timer values are based on the current satellite NG-RAN access RAT type determined based on information from lower layers. The NAS timer value obtained is used as described in the appropriate procedure subclause of this specification. The NAS timer value shall be calculated at start of a NAS procedure, and shall not be re-calculated until the NAS procedure is completed, restarted or aborted. The access via a satellite NG-RAN cell by a UE is indicated to the AMF by lower layers and shall be stored by the AMF. When an AMF that supports access via satellite NG-RAN cells performs NAS signalling with a UE via satellite NG-RAN cells, the AMF shall calculate the value of the applicable NAS timer indicated in table 10.2.2 for access via a satellite NG-RAN cell. NOTE 2: The applied NAS timer values are based on the current satellite NG-RAN access RAT type determined based on information from lower layers. The NAS timer value obtained is used as described in the appropriate procedure subclause of this specification. The NAS timer value shall be calculated at start of a NAS procedure and shall not be re-calculated until the NAS procedure is completed, restarted or aborted.

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

5.3.5.13d Application layer measurement configuration

The UE shall: 1> if measConfigAppLayerToReleaseList is included in appLayerMeasConfig within RRCReconfiguration or RRCResume: 2> for each measConfigAppLayerId value included in the measConfigAppLayerToReleaseList: 3> forward the measConfigAppLayerId and inform upper layers about the release of the application layer measurement configuration including any RAN visible application layer measurement configuration; 3> discard any application layer measurement report received from upper layers; 3> if stored, release the application layer measurement configuration in UE variables VarAppLayerIdleConfig and VarAppLayerPLMN-ListConfig; 3> consider itself not to be configured to send application layer measurement report for the measConfigAppLayerId. 1> if measConfigAppLayerToAddModList is included in appLayerMeasConfig within RRCReconfiguration or RRCResume: 2> for each measConfigAppLayerId value included in the measConfigAppLayerToAddModList: 3> if measConfigAppLayerContainer is included for the corresponding MeasConfigAppLayer configuration: 4> forward the measConfigAppLayerContainer, the measConfigAppLayerId and the serviceType to upper layers considering the serviceType; 3> consider itself to be configured to send application layer measurement report for the measConfigAppLayerId in accordance with 5.7.16; 3> forward the transmissionOfSessionStartStop, if configured, and measConfigAppLayerId to upper layers considering the serviceType; 3> if ran-VisibleParameters is set to setup and the parameters have been received: 4> forward the measConfigAppLayerId, the ran-VisiblePeriodicity, if configured, the numberOfBufferLevelEntries, if configured, and the reportPlayoutDelayForMediaStartup, if configured, to upper layers considering the serviceType; 3> else if ran-VisibleParameters is set to release: 4> forward the measConfigAppLayerId and inform upper layers about the release of the RAN visible application layer measurement configuration; 3> if pauseReporting is set to true: 4> if at least one segment, but not all segments, of a segmented MeasurementReportAppLayer message containing an application layer measurement report associated with the measConfigAppLayerId has been submitted to lower layers for transmission: 5> submit the remaining segments of the MeasurementReportAppLayer message to lower layers for transmission; 4> suspend submitting application layer measurement report containers to lower layers for the application layer measurement configuration associated with the measConfigAppLayerId; 4> store any previously or subsequently received application layer measurement report containers associated with the measConfigAppLayerId for which no segment, or full message, has been submitted to lower layers for transmission; 4> if the memory reserved for storing application layer measurement report containers becomes full while the reporting is paused and if the UE is configured with appLayerMeasPriority: 5> discard reports in priority order where reports with the lowest priority are discarded first; 3> else if pauseReporting is set to false and if transmission of application layer measurement report containers has previously been suspended for the application layer measurement configuration associated with the measConfigAppLayerId: 4> submit stored application layer measurement report containers to lower layers, if any, for the application layer measurements configuration associated with the measConfigAppLayerId; 4> resume submitting application layer measurement report containers to lower layers for the application layer measurement configuration associated with the measConfigAppLayerId; 3> if configForRRC-IdleInactive is set to true: 4> store the received qoe-Reference, measConfigAppLayerId, serviceType, qoe-MeasurementType, qoe-AeaScope, mce-Id, configForRRC-IdleInactive, appLayerMeasPriority, if included, in VarAppLayerIdleConfig; 4> if the qoe-AreaScope includes plmn-IdentityList: 5> set plmn-IdentityList in VarAppLayerPLMN-ListConfig to include the RPLMN as well as the PLMNs included in plmn-IdentityList; 4> else: 5> set plmn-IdentityList in VarAppLayerPLMN-ListConfig to include the RPLMN; NOTE 1: The UE may discard reports when the memory reserved for storing application layer measurement report containers becomes full. If no appLayerMeasPriority is configured, older reports may be discarded first. NOTE 2: The transmission of RAN visible application layer measurement reports and appLayerSessionStatus is not paused when pauseReporting is set to true. NOTE 3: The UE may discard an application layer measurement configuration and associated unsent reports after 48 hours. Editor's Note: FFS on when the 48 hours start for when the UE may discard application layer measurement configuration and reports.

3GPP TS 38.331

NR; Radio Resource Control (RRC); Protocol specification

RAN2

3GPP Series : 38 , Radio technology beyond LTE

5.3.5.13d

6.3.2 Requirements 6.3.2.1 General

Based on operator policy, the 5G system shall enable the UE to select, manage, and efficiently provision services over the 3GPP or non-3GPP access. Based on operator policy, the 5G system shall support steering a UE to select certain 3GPP access network(s). Based on operator policy, the 5G system shall be able to dynamically offload part of the traffic (e.g. from 3GPP RAT to non-3GPP access technology), taking into account traffic load and traffic type. Based on operator policy, the 5G system shall be able to provide simultaneous data transmission via different access technologies (e.g. NR, E-UTRA, non-3GPP), to access one or more 3GPP services. When a UE is using two or more access technologies simultaneously, the 5G system shall be able to optimally distribute user traffic over the access technologies in use, taking into account e.g. service, traffic characteristics, radio characteristics, and UE's moving speed. The 5G system shall be able to support data transmissions optimized for different access technologies (e.g. 3GPP, non-3GPP) and accesses to local data networks (e.g. local traffic routing) for UEs that are simultaneously connected to the network via different accesses. NOTE: This applies to the scenario with simultaneous 3GPP and non-3GPP accesses. Based on operator policy, the 5G system shall be able to add or drop the various access connections for a UE during a session. The 5G system shall be able to support mobility between the supported access networks (e.g. NG-RAN, WLAN, fixed broadband access network, 5G satellite access network). The 5G system shall support UEs with multiple radio and single radio capabilities. The 5G system shall support dynamic and static network address allocation of a common network address to the UE over all supported access types. The 5G system shall support a set of identities for a single user in order to provide a consistent set of policies and a single set of services across 3GPP and non-3GPP access types. The 5G system shall support the capability to operate in licensed and/or unlicensed bands.

3GPP TS 22.261

Service requirements for the 5G system

SA WG1

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

6.3.2

4.2.2.1 Service State, NORMAL SERVICE

When in state MM IDLE and service state NORMAL SERVICE, the mobile station shall: - provided that T3246 is not running, perform normal location updating when a new location area is entered; - perform location updating procedure at expiry of timer T3211 or T3213; - perform periodic updating at expiration of timer T3212; - perform IMSI detach; - provided that T3246 is not running, support requests from the CM layer; - support request for emergency calls; - respond to paging; and - for an eCall only mobile station (as determined by information configured in USIM), perform the eCall inactivity procedure at expiry of timer T3242 or timer T3243. In addition, mobile stations supporting VGCS listening or VBS listening shall: - indicate notifications to the GCC or BCC sublayer; - respond to notification if the GCC or BCC sublayer requests the reception of a voice group or broadcast call for which no channel description has been received in the notification by the RR sublayer; - request the RR sublayer to receive a voice group or broadcast call if the GCC or BCC sublayer requests the reception of a voice group or broadcast call for which a channel description has been received in the notification by the RR sublayer and then go to the service state RECEIVING GROUP CALL (NORMAL SERVICE).

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

8.2.4.1.2 TDD PCell (TDD single carrier)

The parameters specified in Table 8.2.4.1.2-1 are valid for TDD CC and LAA SCell(s) unless otherwise stated. And the additional parameters specified in Table 8.2.4.1.2-2 are valid for LAA SCell(s). Table 8.2.4.1.2-1: Common Test Parameters (TDD) Table 8.2.4.1.2-2: Addtional Test Parameters for LAA SCell(s) For CA with LAA SCell(s), the requirements are specified in Table 8.2.4.1.2-4, with the addition of the parameters in Table 8.2.4.1.2-1, Table 8.2.4.1.2-2, Table 8.2.4.1.2-3 and the downlink physical channel setup according to Annex C.3.2. The purpose of these tests is to verify the closed loop rank-two performance with frequency selective precoding for CA with LAA SCell(s). The test coverage for different number of component carriers is defined in 8.1.2.4. Table 8.2.4.1.2-3: Test Parameters for Dual-Layer Spatial Multiplexing (FRC) Table 8.2.4.1.2-4: Single carrier performance for PCell for multiple CA configurations Table 8.2.4.1.2-5: Single carrier performance for LAA SCell for multiple CA configurations Table 8.2.4.1.2-6: Minimum performance (FRC) based on single carrier performance for CA with one LAA SCell Table 8.2.4.1.2-7: Minimum performance (FRC) based on single carrier performance for CA with two LAA SCells Table 8.2.4.1.2-8: Minimum performance (FRC) based on single carrier performance for CA with three LAA SCells Table 8.2.4.1.2-9: Minimum performance (FRC) based on single carrier performance for CA with four LAA SCells Table 8.2.4.1.2-10: Minimum performance (FRC) based on single carrier performance for CA with five LAA SCells Table 8.2.4.1.2-11: Minimum performance (FRC) based on single carrier performance for CA with six LAA SCells

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

6.4.1 Services and Functions

The main services and functions of the PDCP sublayer include: - Transfer of data (user plane or control plane); - Maintenance of PDCP SNs; - Header compression and decompression using the ROHC protocol; - Header compression and decompression using EHC protocol; - Compression and decompression of uplink PDCP SDUs: DEFLATE based UDC only; - Ciphering and deciphering; - Integrity protection and integrity verification; - Timer based SDU discard; - For split bearers, routing; - Duplication; - Reordering and in-order delivery; - Out-of-order delivery; - Duplicate discarding. Since PDCP does not allow COUNT to wrap around in DL and UL, it is up to the network to prevent it from happening (e.g. by using a release and add of the corresponding radio bearer or a full configuration).

3GPP TS 38.300

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

RAN2

3GPP Series : 38 , Radio technology beyond LTE

6.4.1

8.2.2.4.3 Minimum Requirement Multi-Layer Spatial Multiplexing 4 Tx Antenna Port

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

3GPP TS 36.101

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

RAN4

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

8.2.2.4.3

4.3.15a Selected IP Traffic Offload (SIPTO) at the Local Network 4.3.15a.1 General

The SIPTO at the Local Network function enables an IP capable UE connected via a (H)eNB to access a defined IP network (e.g. the Internet) without the user plane traversing the mobile operator's network. The subscription data in the HSS are configured per user and per APN to indicate to the MME if offload at the local network is allowed or not. SIPTO at the Local Network can be achieved by selecting a L-GW function collocated with the (H)eNB or selecting stand-alone GWs (with S-GW and L-GW collocated) residing in the Local Network. In both cases the selected IP traffic is offloaded via the Local Network. Specific to the HeNB subsystem, the applicability of SIPTO at the Local Network does not depend on CSG membership and the feature can be applied to any UE, as long as the UE is allowed to access the cell. For this release of the specification, no interface between the L-GW and the PCRF is specified and there is no support for dedicated bearers on the PDN connection used for SIPTO at the Local Network. The Local GW (L-GW) shall reject any UE requested bearer resource modification. For this release of the specification, SIPTO at the Local Network is intended for offloading Internet traffic only, thus the L-GW does not provide APN specific connectivity. Therefore if the subscription data in the HSS indicate that offload at the Local Network is allowed, this implies that the related APN is typically used for providing Internet connectivity. If the MME detects a change in SIPTO permissions in the subscription data for a given subscriber for a given APN and the subscriber has already established a SIPTO at the local network PDN connection to that APN, the MME shall release the SIPTO at the Local Network PDN connection for that APN with "reactivation requested" cause as specified in clause 5.10.3. NOTE: In this release of the specification it is assumed that the target S-GW selected during the Handover also has connectivity to the L-GW.

3GPP TS 23.401

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

SA WG2

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

4.3.15a

A.3 Monitor of E-RAB level QoS modification

When an E-RAB has been established, the QoS it experiences in the E-UTRAN is dependent upon the E-RAB level QoS parameters established for the bearer, together with settings of other bearers established in the same cell. If the QoS experienced by a bearer does not meet the expected performance, or the resource need be reassigned for other bearers, the E-RAB level QoS may be adjusted (typically with a knock-on effect onto other bearers). So the modification of E-RAB level QoS parameters needs to be monitored, and due to different priority and tolerance for different service type with different OoS level in the networks, the monitor needs to be opened on each target service type with OoS level. The E-RAB level QoS can be modified by E-RAB Modify procedure (see 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [9]), in which the MME entity instructs the eNodeB to change one or more QoS parameters on an E-RAB using the E-RAB MODIFY REQUEST message. The eNodeB typically makes the adjustments as instructed (and adjusts the RRM applied to the bearer appropriately) but in some circumstances the bearer modification can fail. The eNodeB returns an E-RAB MODIFY RESPONSE message that tells the MME whether the modification was successful or not – for an unsuccessful modification a cause value is included. It is important for OAM to measure the failure rate of the bearer modifications, this information can be used, for example, to make adjustments to OAM CM settings.

3GPP TS 32.425

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

SA WG5

3GPP Series : 32 , OAM&P and Charging

A.3

5.2.2.3.8 eCALL-INACTIVE

The UE camps on a suitable cell or an acceptable cell in a PLMN selected as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6] but initiates no EMM signalling with the network and ignores any paging requests. The UE shall leave substate EMM-DEREGISTERED.eCALL-INACTIVE state only when one of the following events occur: - if the USIM is removed, the UE enters substate EMM-DEREGISTERED.NO-IMSI; - if coverage is lost, the UE enters substate EMM-DEREGISTERED.PLMN-SEARCH; - if the UE is deactivated (e.g. powered off) by the user, the UE enters state EMM-NULL; - if the UE receives a request from upper layers to establish an eCall over IMS, the UE enters state EMM-DEREGISTERED.ATTEMPTING-TO-ATTACH. The UE then uses the relevant EMM and ESM procedures to establish the eCall over IMS at the earliest opportunity; or - if the UE receives a request from upper layers to establish a call to an HPLMN designated non-emergency MSISDN or URI for test or terminal reconfiguration service, the UE enters state EMM-DEREGISTERED.ATTEMPTING-TO-ATTACH. Once the attach procedure is completed, the UE uses the relevant EMM and ESM procedures to establish the non-emergency call.

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

6.2.5C Configured transmitted power for Dual Connectivity

For inter-band dual connectivity with one uplink serving cell per CG, the UE is allowed to set its configured maximum output power PCMAX,c(i),i for serving cell c(i) of CG i, i = 1,2, and its total configured maximum output power PCMAX. The configured maximum output power PCMAX,c(i),i (p) in subframe p of serving cell c(i) on CG i shall be set within the following bounds: PCMAX_L,c(i),i (p) ≤ PCMAX,c(i), i (p) ≤ PCMAX_H,c(i),i (p) where PCMAX_L,c(i),i (p) and PCMAX_H,c(i),i (p) are the limits for a serving cell c(i) of CG i as specified in subclause 6.2.5. The total UE configured maximum output power PCMAX (p,q) in a subframe p of CG 1 and a subframe q of CG 2 that overlap in time shall be set within the following bounds for synchronous and asynchronous operation unless stated otherwise: PCMAX_L(p,q) ≤ PCMAX (p,q) ≤ PCMAX_H (p,q) with PCMAX_L (p,q) = MIN {10 log10 [pCMAX_L,c(1),1 (p) + pCMAX_L,c(2),2 (q)], PPowerClass} PCMAX_H (p,q) = MIN {10 log10 [pCMAX_H,c(1),1 (p) + pCMAX_H,c(2),2 (q)], PPowerClass} where pCMAX_L,c(i),i is pCMAX_H,c(i),i are the respective limits PCMAX_L,c(i),i (p) and PCMAX_H,c(i),i (p) expressed in linear scale. If the UE is configured in Dual Connectivity and synchronous transmissions of the UE on subframe p for a serving cell in one CG overlaps some portion of the first symbol of the transmission on subframe q +1 for a different serving cell in the other CG, the UE minimum of PCMAX_L between subframes pairs (p, q) and (p+1, q +1) respectively applies for any overlapping portion of subframes (p, q) and (p +1, q+1). PPowerClass shall not be exceeded by the UE during any period of time. The measured total maximum output power PUMAX over both CGs is PUMAX = 10 log10 [pUMAX,c(1),1 + pUMAX,c(2),2], where pUMAX,c(i),i denotes the measured output power of serving cell c(i) of CG i expressed in linear scale. If the UE is configured in Dual Connectivity and synchronous transmissions PCMAX_L(p, q) – TLOW (PCMAX_L(p, q)) ≤ PUMAX ≤ PCMAX_H(p, q) + THIGH (PCMAX_H(p, q)) where PCMAX_L (p,q) and PCMAX_H (p,q) are the limits for the pair (p,q) and with the tolerances TLOW(PCMAX) and THIGH(PCMAX) for applicable values of PCMAX specified in Table 6.2.5C-1. PCMAX_L may be modified for any overlapping portion of subframes (p, q) and (p +1, q+1). If the UE is configured in Dual Connectivity and asynchronous transmissions, the subframes of the leading CG are taken as reference subframes for the measurement of the total configured output power PUMAX. If subframe p of CG 1 and subframe q of CG 2 overlap in time in their respective slot 0 and 1. if p leads in time over q, then p is the reference subframe and the (p,q) and (p,q-1) pairs are considered for determining the PCMAX tolerance 2. if q leads in time over p, then q is the reference subframe and the (p-1,q) and (p,q) pairs are considered for determining the PCMAX tolerance; for the reference subframe p duration (when subframe p in CG 1 leads): P’CMAX_L = MIN {PCMAX_L (p,q) , PCMAX_L (p,q-1)} P’CMAX_H = MAX {PCMAX_H (p,q) , PCMAX_H (p,q-1)} while for the reference subframe q duration (when subframe q in CG 2 leads): P’CMAX_L = MIN {PCMAX_L (p-1,q) , PCMAX_L (p,q)} P’CMAX_H = MAX {PCMAX_H (p-1,q) , PCMAX_H (p,q)} where PCMAX_L and PCMAX_H are the applicable limits for each overlapping subframe pairs (p,q) , (p, q-1) and (p-1,q). The measured total configured maximum output power PUMAX shall be within the following bounds: P’CMAX_L – TLOW (P’CMAX_L) ≤ PUMAX ≤ P’CMAX_H + THIGH (P’CMAX_H) with the tolerances TLOW(PCMAX) and THIGH(PCMAX) for applicable values of PCMAX specified in Table 6.2.5C-1. Table 6.2.5C-1: PCMAX tolerance for inter-band Dual Connectivity

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

5.5.1.3 Combined attach procedure for EPS services and non-EPS services (S1 mode only) 5.5.1.3.1 General

The combined attach procedure is used by a UE in CS/PS mode 1 or CS/PS mode 2 of operation to attach for both EPS and non-EPS services, or both EPS services and "SMS only". The combined attach procedure is also used by a UE in CS/PS mode 1 or CS/PS mode 2 of operation to attach for EPS services if it is already IMSI attached for non-EPS services. When the UE initiates a combined attach procedure, the UE shall indicate "combined EPS/IMSI attach" in the EPS attach type IE. The combined attach procedure follows the attach procedure for EPS described in clause 5.5.1.2 with exception of clause 5.5.1.2.4A and clause 5.5.1.2.6A.

3GPP TS 24.301

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

CT WG1

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

5.5.1.3

5.12 Charging 5.12.1 General

5GC supports interactions towards CHF for network resource usage, as defined in TS 32.240[ Telecommunication management; Charging management; Charging architecture and principles ] [41]. The CHF and the Nchf service are defined in TS 32.290[ Telecommunication management; Charging management; 5G system; Services, operations and procedures of charging using Service Based Interface (SBI) ] [67]. The SMF supports the interactions towards the CHF, as defined in TS 32.255[ Telecommunication management; Charging management; 5G data connectivity domain charging; Stage 2 ] [68]. The UPF supports functionality to collect and report usage data to SMF. The N4 reference point supports the SMF control of the UPF collection and reporting of usage data. The AMF supports interactions towards the CHF, as defined in TS 32.256[ Charging management; 5G connection and mobility domain charging; Stage 2 ] [114]. The SMSF supports interactions towards the CHF, as defined in TS 32.274[ Telecommunication management; Charging management; Short Message Service (SMS) charging ] [118]. The NEF supports interactions towards the CHF, as defined in TS 32.254[ Telecommunication management; Charging management; Exposure function Northbound Application Program Interfaces (APIs) charging ] [123].

3GPP TS 23.501

System architecture for the 5G System (5GS)

SA WG2

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

5.12