Search is not available for this dataset
doc_id
int64 1
6.72k
β | Section
stringlengths 5
247
β | Content
stringlengths 501
147k
β | Source
stringclasses 456
values | Document Title
stringclasses 22
values | Working Group
stringclasses 21
values | Series Subject
stringclasses 9
values | Subclause
stringlengths 1
13
β |
|---|---|---|---|---|---|---|---|
4,001 | 9.3.17 Progress | This message is sent from the network to the mobile station to indicate the progress of a call in the event of interworking or in connection with the provision of in-band information/patterns. See table 9.67/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Message type: PROGRESS Significance: global Direction: network to mobile station Table 9.67/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : PROGRESS message content | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.3.17 |
4,002 | 5.7.1.6 DL traffic | The following characteristics apply for processing of DL traffic: - UPF maps User Plane traffic to QoS Flows based on the PDRs. - UPF performs Session-AMBR enforcement as specified in clause 5.7.1.8 and performs counting of packets for charging. - UPF transmits the PDUs of the PDU Session in a single tunnel between 5GC and (R)AN, the UPF includes the QFI in the encapsulation header. In addition, UPF may include an indication for Reflective QoS activation in the encapsulation header. - UPF performs transport level packet marking in DL on a per QoS Flow basis. The UPF uses the transport level packet marking value provided by the SMF (as described in clause 5.8.2.7). - (R)AN maps PDUs from QoS Flows to access-specific resources based on the QFI and the associated 5G QoS profile, also taking into account the N3 tunnel associated with the DL packet. NOTE: Packet Filters are not used for the mapping of QoS Flows onto access-specific resources in (R)AN. - If Reflective QoS applies, the UE creates a new derived QoS rule as defined in clause 5.7.5.2. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.7.1.6 |
4,003 | A.7 Guidelines regarding use of conditions | Conditions are primarily used to specify network restrictions, for which the following types can be distinguished: - Message Contents related constraints e.g. that a field B is mandatory present if the same message includes field A and when it is set value X. - Configuration Constraints e.g. that a field D can only be signalled if field C is configured and set to value Y. (i.e. regardless of whether field C is present in the same message or previously configured). The use of these conditions is illustrated by an example. -- /example/ ASN1START RRCMessage-IEs ::= SEQUENCE { fieldA FieldA OPTIONAL, -- Need M fieldB FieldB OPTIONAL, -- Cond FieldAsetToX fieldC FieldC OPTIONAL, -- Need M fieldD FieldD OPTIONAL, -- Cond FieldCsetToY nonCriticalExtension SEQUENCE {} OPTIONAL } -- /example/ ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | A.7 |
4,004 | 11.2.1.3.4 IPv6 Router Configuration Variables | For IPv6 Address Autoconfiguration to work properly , network entities which act as an access router towards the MS/UE, i.e. PDN GW, Serving GW, ePDG and TWAN, shall be consistent with the RFCs specifying this process (for example RFC 4862 [83] and RFC 4861 [89]), unless stated otherwise in this or other 3GPP specifications. RFC 4861 [89] specifies a set of conceptual router configuration variables. Some of these variables require particular attention in GPRS and EPC in order to preserve radio resources and MS/UE power consumption while still allowing for appropriate robustness and fast user-plane set-up time even in bad radio conditions, or simply because they have a particular meaning in GPRS and EPC. These particular variables are listed below with appropriate (default) values and shall be configurable per APN. The values specified hereafter are specific to GPRS and EPC, and supersede those specified in RFC 4861 [89]. MaxRtrAdvInterval Shall have a default value of 21 600 s (6 h). MinRtrAdvInterval Shall have a default value of 0,75 Γ MaxRtrAdvInterval i.e.16 200 s (4,5 h). AdvValidLifetime Shall have a value giving Prefixes infinite lifetime, i.e. 0xFFFFFFFF. The assigned prefix remains Preferred until PDP Context/Bearer Deactivation. AdvPreferredLifetime Shall have a value giving Prefixes infinite lifetime, i.e. 0xFFFFFFFF. The assigned prefix remains Preferred until PDP Context/Bearer Deactivation. RFC 4861 [89] also specifies a number of protocol constants. The following shall have specific values for GPRS and EPC: MAX_INITIAL_RTR_ADVERT_INTERVAL This constant may be a variable within GPRS and EPC. It may have a value that gradually increases (exponentially or by some other means) with the number of initial Router Advertisements sent. This will enable a fast set-up of the MS-GGSN or MS/UE-PDN GW/Serving GW/ePDG/TWAN links in most cases, while still allowing the MS/UE to receive a Router Advertisement within the initial phase, even in case of bad radio conditions or slow response time, without having to send a large number of initial Router Advertisements. MAX_INITIAL_RTR_ADVERTISEMENTS This is the number of Router Advertisements sent during the initial phase after the MS-GGSN or MS/UE-PDN GW/Serving GW/ePDG/TWAN links have been established. The value of this constant shall be chosen carefully, and in conjunction with MAX_INITIAL_RTR_ADVERT_INTERVAL, so as to not overload the radio interface while still allowing the MS/UE to complete its configuration in a reasonable delay. For instance, the default value could be chosen so that initial Router Advertisements are sent for at least 30 s. After the initial phase, the periodicity is controlled by the MaxRtrAdvInterval and the MinRtrAdvInterval constants. | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 11.2.1.3.4 |
4,005 | 4.3.7.1a.2 GTP-C Overload Control | GTP-C Overload Control feature is an optional feature. Nodes using GTP control plane signalling may support communication of Overload Control Information in order to mitigate overload situation for the overloaded node through actions taken by the peer node(s). This feature is supported over S4, S11, S5 and S8 interfaces via GTPv2 control plane protocol. A GTP-C node is considered to be in overload when it is operating over its nominal capacity resulting in diminished performance (including impacts to handling of incoming and outgoing traffic). Overload Control Information reflects an indication of when the originating node has reached such situation. This information, when transmitted between GTP-C nodes may be used to reduce and/or throttle the amount of GTP-C signalling traffic between these nodes. As such, the Overload Control Information provides guidance to the receiving node to decide actions which leads to mitigation towards the sender of the information. NOTE 1: How a node determines its Overload Control Information is implementation dependent. The Overload Control Information may convey information regarding the node itself and/or regarding specific APN(s) status. In order to mitigate overload, - it shall be possible to signal control information about the overload of a GTP-C node (e.g. S-GW, P-GW); - the PDN GW may detect overload for certain APNs, e.g. based on Diameter overload indication received from a PCRF or from an external AAA server, or e.g. based on shortage of resources for an APN (IP address pool). It shall be possible to signal appropriate control information about the APN status in addition to the mechanism described in clause 4.3.7.5. For a given APN, the PDN GW shall either activate the congestion control by conveying the Overload Control Information at APN level or by conveying the "PDN GW back-off time" (as specified in clause 4.3.7.5), but not both at the same time, as specified in more detail in clause 12.3.8 of TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [43]. GTP-C Overload Control feature allows the MME/SGSN to send its Overload Control Information to the PDN GW via Serving GW. GTP-C Overload Control feature allows the Serving GW to send its Overload Control Information to the MME/SGSN and P-GW. GTP-C Overload Control feature also allows the PDN GW to send its Overload Control Information to the MME/SGSN via a Serving GW. GTP-C overload Control feature should continue to allow for preferential treatment of priority users (eMPS) and emergency services as per existing specifications. An MME/SGSN may during ESM and EMM procedures apply certain restrictions towards GWs (Serving GW and/or PDN GW as applicable) that have indicated overload, e.g.: - reject EPS Session Management requests from the UE (e.g. PDN Connectivity, Bearer Resource Allocation or Bearer Resource Modification Requests) with a Session Management back-off timer as described in clause 4.3.7.4.2; - reject Mobility Management signalling requests from UEs (such as Attach, Detach, Service Request, Tracking Area Update) with a Mobility Management back-off timer (e.g. reject Service Request requiring to activate user plane bearers in an overloaded SGW) as described in clause 4.3.7.4.2; - reject or accept requests for data transmission via Control Plane CIoT EPS Optimisation from UEs (e.g. Control Plane Service Request and ESM Data Transport) with a Control Plane data back-off timer as described in clause 4.3.7.4.2.7; - may reduce/throttle messages towards the GWs indicating overload status; - other implementation specific mechanisms, which are outside the scope of 3GPP specifications. A PDN GW may take the following actions for MME/SGSN which have indicated overload: - Limit or completely block non-GBR dedicated bearer establishment; - Limit or completely block all Dedicated Bearer establishments or modification, except QCI=1 bearers; - Limit or completely block all Dedicated Bearer establishments, including the QCI=1 bearers; - other implementation specific mechanisms, which are outside the scope of 3GPP specifications. A node supporting GTP-C Overload Control feature sends Overload Control Information in any GTP control plane request or response message such that exchange of Overload Control Information does not trigger extra signalling. The computation and transfer of the Overload Control Information shall not add significant additional load to the node itself and to its corresponding peer nodes. The calculation of Overload Control Information should not severely impact the resource utilization of the node. Based on local policies/configuration, a GTP-C node may support Overload Control feature and act upon or ignore Overload Control Information in the VPLMN when received from HPLMN and in the HPLMN when received from VPLMN. When this feature is supported, a GTP-C node may decide to send different values of Overload Control Information on inter-network (roaming) and on intra-network (non-roaming) interfaces based on local policies/configuration. NOTE 2: Refer to clause 12 of TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [43] for the details, such as exact format of the Overload Control Information, mechanisms to discover the support of the feature by the peer node, interfaces for which this feature is applicable, APN level overload control, etc. | 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.7.1a.2 |
4,006 | 8.95 Absolute Time of MBMS Data Transfer | The Absolute Time of MBMS Data Transfer indicates the absolute time of the actual start, update or stop of the MBMS data transfer to ensure a synchronized session control and facilitate a graceful reallocation of resources for the MBSFN (MBMS Single Frequency Network) when needed for E-UTRAN access. It is coded as shown in figure 8.95-1. Figure 8.95-1: Absolute Time of MBMS Data Transfer Octets 5 to 12 are coded as the time in seconds relative to 00:00:00 on 1 January 1900 (calculated as continuous time without leap seconds and traceable to a common time reference) where binary encoding of the integer part is in the 32 most significant bits and binary encoding of the fraction part in the 32 least significant bits. The fraction part is expressed with a granularity of 1 /2**32 second. | 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.95 |
4,007 | β MBS-NeighbourCellList | The IE MBS-NeighbourCellList indicates a list of neighbour cells where ongoing MBS sessions provided via broadcast MRB in the current cell may also be provided, as indicated in the mtch-NeighbourCell. MBS-NeighbourCellList information element -- ASN1START -- TAG-MBS-NEIGHBOURCELLLIST-START MBS-NeighbourCellList-r17 ::= SEQUENCE (SIZE (0..maxNeighCellMBS-r17)) OF MBS-NeighbourCell-r17 MBS-NeighbourCell-r17 ::= SEQUENCE { physCellId-r17 PhysCellId, carrierFreq-r17 ARFCN-ValueNR OPTIONAL -- Need S } -- TAG-MBS-NEIGHBOURCELLLIST-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
4,008 | 5.2.1 Description | Infrastructure may be deployed in certain regions to ensure the safety of UAS operations. The purpose of such an infrastructure would be to keep drones separated from each other and also from the few aircraft such as low flying helicopters with which they may need to share the airspace. The UTM may offer an Unmanned Aerial Vehicle Collision Avoidance System (UCAS) service. The primary scope of the 3GPP involvement in such a UCAS would be to provide accurate live positioning information into the UTM from the UAS or MNO, thereby offering a primary or complementary positioning solution able to allow an independent verification of the location reported by the UCAS, if applicable, and to ensure timely feedback from the UTM to the UAS. Most drones of a certain class already have collision avoidance systems on board. Such systems range is very wide from very poor to good β depending on size, quality, price of the drone and the know-how of the manufacturer. Active control from UTM is important and onboard systems can be used as a backup. Figure 5.2.1-1: Live data acquisition by UTM | 3GPP TS 22.825 | Study on Remote Identification of Unmanned Aerial Systems (UAS) | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 5.2.1 |
4,009 | 4.2 Coordination between the protocols for 5GS mobility management and 5GS session management | A 5GS session management (5GSM) message is piggybacked in specific 5GS mobility management (5GMM) transport messages. To this purpose, the 5GSM messages can be transmitted in an information element in the 5GMM transport messages. In this case, the UE, the AMF and the SMF execute the 5GMM procedure and the 5GSM procedure in parallel. The success of the 5GMM procedure is not dependent on the success of the piggybacked 5GSM procedure. The UE can only initiate the 5GSM procedure when there is a 5GMM context established at the UE. During 5GMM procedures, the UE and the AMF shall suspend the transmission of 5GSM messages, except when: a) the 5GMM procedure is piggybacking 5GSM messages; or b) the UE is in 5GMM-CONNECTED mode and a service request procedure for re-establishing user-plane resources of PDU session(s) is initiated without including PDU session status IE or Allowed PDU session status IE. In this case, the UE and the AMF need not suspend the transmission of 5GSM messages related to other PDU session(s) than the one(s) for which the user- plane resources re-establishment is requested. If the UE determines to locally release the N1 NAS signalling connection upon receiving an SOR transparent container during a registration procedure as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] Annex C.2, the UE shall suspend the transmission of 5GSM messages after sending the REGISTRATION COMPLETE message and until the N1 NAS signalling connection is released to obtain service on a higher priority PLMN, with the exception of the case when the UE has an emergency PDU session. A 5GMM message piggybacking a 5GSM message for a PDU session shall be delivered via the access associated with the PDU session, if any, with the following exceptions: a) the AMF shall send, via 3GPP access, a DL NAS TRANSPORT message piggybacking a downlink 5GSM message of a network-requested 5GSM procedure for a PDU session associated with non-3GPP access if the conditions specified in subclause 5.5.1.3.4 or subclause 5.6.1.4 are met; b) the UE shall send an UL NAS TRANSPORT message piggybacking a response message to the 5GSM message described in a) via either: 1) 3GPP access; or 2) non-3GPP access if the UE is in 5GMM-CONNECTED mode over non-3GPP access; and NOTE: The interaction between the 5GMM sublayer and the 5GSM sublayer to enable the UE to send the UL NAS TRANSPORT message containing the response message via 3GPP access is required. This is achieved via UE implementation. c) the UE shall send, via the target access, an UL NAS TRANSPORT message piggybacking a 5GSM message associated with a request type set to "existing PDU session" or "existing emergency PDU session" for handover of an existing PDU session between 3GPP access and non-3GPP access. A 5GMM message piggybacking a 5GSM message as a response message to a request message associated with an MA PDU session, shall be delivered via the same access that the initial message was received. | 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.2 |
4,010 | 4.4 NAS security 4.4.1 General | This clause describes the principles for the handling of EPS security contexts in the UE and in the MME and the procedures used for the security protection of EPS NAS messages between UE and MME. Security protection involves integrity protection and ciphering of the EMM and ESM NAS messages. The signalling procedures for the control of NAS security are part of the EMM protocol and are described in detail in clause 5. NOTE: The use of ciphering in a network is an operator option. In this clause, for the ease of description, it is assumed that ciphering is used, unless explicitly indicated otherwise. Operation of a network without ciphering is achieved by configuring the MME so that it always selects the "null ciphering algorithm", EEA0. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.4 |
4,011 | 4.7.2.10 Extended idle-mode DRX cycle | The MS can request the use of extended idle mode DRX cycle (eDRX) during an attach or routing area updating procedure by including the extended DRX parameters IE (see 3GPP TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [11A] and 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [74]). The MS shall not request the use of eDRX during: - an attach for emergency bearer services procedure; or - a routing area updating procedure for the MS attached for emergency bearer services. The MS and the network may negotiate eDRX parameters during a routing area updating procedure when the MS has a PDP context for emergency bearer services. The network accepts the request to use eDRX by providing the extended DRX parameters IE when accepting the attach or the routing area updating procedure. The MS shall use extended idle mode DRX cycle only if it received the extended DRX parameters IE during the last attach or routing area updating procedure and the MS does not have a PDP context for emergency bearer services. NOTE: If the MS wants to keep using eDRX, the MS includes the extended DRX parameters IE in each attach or routing area updating procedure. If the MS received the extended DRX parameters IE during the last attach or routing area updating procedure, upon the successful completion of the PDP context deactivation procedure for a PDP context for emergency bearer services, the MS shall resume eDRX. If the network has provided the extended DRX parameters IE during the last attach or routing area updating procedure, upon the successful completion of the PDP context deactivation procedure for a PDP context for emergency bearer services, the network shall resume eDRX. If the MS or the network locally deactivates the PDP context for emergency bearer service, the MS or the network shall not use eDRX until the MS receives eDRX parameters during a routing area updating procedure with PDP context synchronization or upon successful completion of a service request procedure. If the MS did not receive the extended DRX parameters IE, or if the MS has a PDP context for emergency bearer services, the MS shall use the stored DRX parameters, if available. If the network did not accept the request to use eDRX, or if the MS has a PDP context for emergency bearer services, the network shall use the stored DRX parameters, if available. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.2.10 |
4,012 | β UE-CapabilityRequestFilterCommon | The IE UE-CapabilityRequestFilterCommon is used to request filtered UE capabilities. The filter is common for all capability containers that are requested. UE-CapabilityRequestFilterCommon information element -- ASN1START -- TAG-UE-CAPABILITYREQUESTFILTERCOMMON-START UE-CapabilityRequestFilterCommon ::= SEQUENCE { mrdc-Request SEQUENCE { omitEN-DC ENUMERATED {true} OPTIONAL, -- Need N includeNR-DC ENUMERATED {true} OPTIONAL, -- Need N includeNE-DC ENUMERATED {true} OPTIONAL -- Need N } OPTIONAL, -- Need N ..., [[ codebookTypeRequest-r16 SEQUENCE { type1-SinglePanel-r16 ENUMERATED {true} OPTIONAL, -- Need N type1-MultiPanel-r16 ENUMERATED {true} OPTIONAL, -- Need N type2-r16 ENUMERATED {true} OPTIONAL, -- Need N type2-PortSelection-r16 ENUMERATED {true} OPTIONAL -- Need N } OPTIONAL, -- Need N uplinkTxSwitchRequest-r16 ENUMERATED {true} OPTIONAL -- Need N ]], [[ requestedCellGrouping-r16 SEQUENCE (SIZE (1..maxCellGroupings-r16)) OF CellGrouping-r16 OPTIONAL -- Cond NRDC ]], [[ fallbackGroupFiveRequest-r17 ENUMERATED {true} OPTIONAL -- Need N ]], [[ lowerMSDRequest-r18 SEQUENCE { pc1dot5-r18 ENUMERATED {true} OPTIONAL, -- Need N pc2-r18 ENUMERATED {true} OPTIONAL, -- Need N pc3-r18 ENUMERATED {true} OPTIONAL -- Need N } OPTIONAL -- Need N ]] } CellGrouping-r16 ::= SEQUENCE { mcg-r16 SEQUENCE (SIZE (1..maxBands)) OF FreqBandIndicatorNR, scg-r16 SEQUENCE (SIZE (1..maxBands)) OF FreqBandIndicatorNR, mode-r16 ENUMERATED {sync, async} } -- TAG-UE-CAPABILITYREQUESTFILTERCOMMON-STOP -- ASN1STOP -- Editor Note: The power class related part can be updated further pending RAN4 discussion. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
4,013 | 5.3.13.8 RNA update | In RRC_INACTIVE state, the UE shall: 1> if T380 expires; or 1> if RNA Update is triggered at reception of SIB1, as specified in 5.2.2.4.2: 2> if T319 is not running and SDT procedure is not ongoing: 3> initiate RRC connection resume procedure in 5.3.13.2 with resumeCause set to rna-Update; 1> if barring is alleviated for Access Category '8' or Access Category '2', as specified in 5.3.14.4: 2> if upper layers do not request RRC the resumption of an RRC connection, and 2> if the variable pendingRNA-Update is set to true: 3> initiate RRC connection resume procedure in 5.3.13.2 with resumeCause value set to rna-Update. If the UE in RRC_INACTIVE state fails to find a suitable cell and camps on the acceptable cell to obtain limited service as defined in TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [20], the UE shall: 1> perform the actions upon going to RRC_IDLE as specified in 5.3.11 with release cause 'other'. NOTE: It is left to UE implementation how to behave when T380 expires while the UE is camped neither on a suitable nor on an acceptable cell. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.13.8 |
4,014 | 5.3.6.3 Reception of the CounterCheck message by the UE | Upon receiving the CounterCheck message, the UE shall: 1> for each DRB that is established: 2> if no COUNT exists for a given direction (uplink or downlink) because it is a uni-directional bearer configured only for the other direction: 3> assume the COUNT value to be 0 for the unused direction; 2> if the drb-Identity is not included in the drb-CountMSB-InfoList: 3> include the DRB in the drb-CountInfoList in the CounterCheckResponse message by including the drb-Identity, the count-Uplink and the count-Downlink set to the value of TX_NEXT β 1 and RX_NEXT β 1 (specified in TS 38.323[ NR; Packet Data Convergence Protocol (PDCP) specification ] [5]), respectively; 2> else if, for at least one direction, the most significant bits of the COUNT are different from the value indicated in the drb-CountMSB-InfoList: 3> include the DRB in the drb-CountInfoList in the CounterCheckResponse message by including the drb-Identity, the count-Uplink and the count-Downlink set to the value of TX_NEXT β 1 and RX_NEXT β 1 (specified in TS 38.323[ NR; Packet Data Convergence Protocol (PDCP) specification ] [5]), respectively; 1> for each DRB that is included in the drb-CountMSB-InfoList in the CounterCheck message that is not established: 2> include the DRB in the drb-CountInfoList in the CounterCheckResponse message by including the drb-Identity, the count-Uplink and the count-Downlink with the most significant bits set identical to the corresponding values in the drb-CountMSB-InfoList and the least significant bits set to zero; 1> submit the CounterCheckResponse message to lower layers for transmission upon which the procedure ends. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.6.3 |
4,015 | 4.3.2.2.1 Non-roaming and Roaming with Local Breakout | Clause 4.3.2.2.1 specifies PDU Session establishment in the non-roaming and roaming with local breakout cases. The procedure is used to: - Establish a new PDU Session; - Handover a PDN Connection in EPS to PDU Session in 5GS without N26 interface; - Switching an existing PDU Session between non-3GPP access and 3GPP access. The specific system behaviour in this case is further defined in clauses 4.9.2 and 4.9.3; or - Request a PDU Session for Emergency services. In the case of roaming, the AMF determines if a PDU Session is to be established in LBO or Home Routing. In the case of LBO, the procedure is as in the case of non-roaming with the difference that the AMF, the SMF, the UPF and the PCF are located in the visited network. PDU Sessions for Emergency services are never established in Home Routed mode. If Control Plane CIoT 5GS Optimisation is enabled for the PDU session with LBO, the NEF is not used as the anchor of this PDU Session. NOTE 1: UE provides both the S-NSSAIs of the Home PLMN and Visited PLMN to the network as described in clause 5.15.5.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. Figure 4.3.2.2.1-1: UE-requested PDU Session Establishment for non-roaming and roaming with local breakout The procedure assumes that the UE has already registered on the AMF thus unless the UE is Emergency Registered the AMF has already retrieved the user subscription data from the UDM. 1. From UE to AMF: NAS Message (S-NSSAI(s), [Alternative S-NSSAI], UE Requested DNN, PDU Session ID, Request type, Old PDU Session ID, N1 SM container (PDU Session Establishment Request, [Port Management Information Container])). In order to establish a new PDU Session, the UE generates a new PDU Session ID. The UE initiates the UE Requested PDU Session Establishment procedure by the transmission of a NAS message containing a PDU Session Establishment Request within the N1 SM container. The PDU Session Establishment Request includes a PDU session ID, Requested PDU Session Type, a Requested SSC mode, 5GSM Capability, PCO, SM PDU DN Request Container, [Number Of Packet Filters], [Header Compression Configuration], UE Integrity Protection Maximum Data Rate, [Always-on PDU Session Requested], [RSN], [Connection Capabilities] and [PDU Session Pair ID]. The Request Type indicates "Initial request" if the PDU Session Establishment is a request to establish a new PDU Session and indicates "Existing PDU Session" if the request refers to an existing PDU Session switching between 3GPP access and non-3GPP access or to a PDU Session handover from an existing PDN connection in EPC. If the request refers to an existing PDN connection in EPC, the S-NSSAI is set as described in clause 5.15.7.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] When Emergency service is required and an Emergency PDU Session is not already established, a UE shall initiate the UE Requested PDU Session Establishment procedure with a Request Type indicating "Emergency Request". The Request Type indicates "Emergency Request" if the PDU Session Establishment is a request to establish a PDU Session for Emergency services. The Request Type indicates "Existing Emergency PDU Session" if the request refers to an existing PDU Session for Emergency services switching between 3GPP access and non-3GPP access or to a PDU Session handover from an existing PDN connection for Emergency services in EPC. 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 Number Of Packet Filters indicates the number of supported packet filters for signalled QoS rules for the PDU Session that is being established. The number of packet filters indicated by the UE is valid for the lifetime of the PDU Session. For presence condition, see TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [25]. The UE Integrity Protection Maximum Data Rate indicates the maximum data rate up to which the UE can support UP integrity protection. The UE shall provide the UE Integrity Protection Data Rate capability independently of the Access Type over which the UE sends the PDU Session Establishment Request. If the use of header compression for Control Plane CIoT 5GS optimisation was negotiated successfully between the UE and the network in the previous registration procedure, the UE shall include the Header Compression Configuration, unless "Unstructured" PDU Session Type is indicated. The Header Compression Configuration includes the information necessary for the header compression channel setup. Optionally, the Header Compression Configuration may include additional header compression context parameters. The NAS message sent by the UE is encapsulated by the AN in a N2 message towards the AMF that should include User location information and Access Type Information. The PDU Session Establishment Request message may contain SM PDU DN Request Container containing information for the PDU Session authorization by the external DN. The UE includes the S-NSSAI from the Allowed NSSAI of the current access type or Partially Allowed NSSAI. If the UE is provided with the mapping of an S-NSSAI that is replaced by an Alternative S-NSSAI, the UE shall provide both the Alternative S-NSSAI and the S-NSSAI that is replaced by it. If the Mapping of Allowed NSSAI or Mapping Of Partially Allowed NSSAI was provided to the UE, the UE shall provide both the S-NSSAI of the VPLMN from the Allowed NSSAI or Partially Allowed NSSAI and the corresponding S-NSSAI of the HPLMN from the Mapping Of Allowed NSSAI or Mapping Of Partially Allowed NSSAI. If the UE is provided with the mapping of the VPLMN S-NSSAI to a VPLMN Alternative S-NSSAI, the UE provides both the VPLMN Alternative S-NSSAI and the VPLMN S-NSSAI in the PDU Session Establishment message. If the UE is provided with the mapping of the HPLMN S-NSSAI to a HPLMN Alternative S-NSSAI, the UE provides both the HPLMN Alternative S-NSSAI and the HPLMN S-NSSAI in the PDU Session Establishment message. If the procedure is triggered for SSC mode 3 operation, the UE shall also include the Old PDU Session ID which indicates the PDU Session ID of the on-going PDU Session to be released, in NAS message. The Old PDU Session ID is included only in this case. The AMF receives from the AN the NAS SM message (built in step 1) together with User Location Information (e.g. Cell Id in the case of the NG-RAN). The UE shall not trigger a PDU Session establishment for a PDU Session corresponding to a LADN when the UE is outside the area of availability of the LADN. The UE shall not trigger a PDU Session establishment for a PDU Session associated to an S-NSSAI if the S-NSSAI is not valid as per the S-NSSAI location availability information. If the UE is establishing a PDU session for IMS and the UE is configured to discover the P-CSCF address during connectivity establishment, the UE shall include an indicator that it requests a P-CSCF IP address(es) within the SM container. The PS Data Off status is included in the PCO in the PDU Session Establishment Request message. The UE capability to support Reliable Data Service is included in the PCO in the PDU Session Establishment Request message. If the UE has indicated that it supports transfer of Port Management Information Containers as per UE 5GSM Core Network Capability and if the PDU session type is Ethernet, then the UE shall include the MAC address of the DS-TT Ethernet port used for this Ethernet PDU session. If the UE is aware of the UE-DS-TT Residence Time, then the UE shall additionally include the UE-DS-TT Residence Time. If the UE requests to establish always-on PDU session, the UE includes an Always-on PDU Session Requested indication in the PDU Session Establishment Request message. As described in TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [74], a UE that hosts EEC(s) may indicate in the PCO that it supports the ability to receive ECS address(es) via NAS and to transfer the ECS Address(es) to the EEC(s). 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]). The UE may also include PDU Session Pair ID and/or RSN in PDU Session Establishment Request message as described in clause 5.33.2.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 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. Port Management Information Container may be received from DS-TT and includes port management capabilities, i.e. information indicating which standardized and deployment-specific port management information is supported by DS-TT as defined in clause 5.28.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 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]. 2. For NR satellite access, the AMF may decide to verify the UE location as described in clause 5.4.11.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The AMF determines that the message corresponds to a request for a new PDU Session based on that Request Type indicates "initial request" and that the PDU Session ID is not used for any existing PDU Session of the UE. If the NAS message does not contain an S-NSSAI, the AMF determines an S-NSSAI of the Serving PLMN for the requested PDU Session from the current Allowed NSSAI for the UE. If there is only one S-NSSAI in the Allowed NSSAI, this S-NSSAI shall be used. If there is more than one S-NSSAI in the Allowed NSSAI, the S-NSSAI selected is either according to the UE subscription, if the subscription contains only one default S-NSSAI and the corresponding mapped HPLMN S-NSSAI of the Serving PLMN is included in the Allowed NSSAI, or based on operator policy (e.g. also ensures any UE Requested DNN is allowed for the selected S-NSSAI)). When the NAS Message contains an S-NSSAI of the Serving PLMN but it does not contain a DNN, the AMF determines the DNN for the requested PDU Session by selecting the default DNN for this S-NSSAI if the default DNN is present in the UE's Subscription Information (or for the corresponding S-NSSAI of the HPLMN, in the case of LBO); otherwise the serving AMF selects a locally configured DNN for this S-NSSAI of the Serving PLMN. If the AMF cannot select an SMF (e.g. the UE requested DNN is not supported by the network, or the UE requested DNN is not in the Subscribed DNN List for the S-NSSAI (or its mapped value for the HPLMN in the case of LBO) and wildcard DNN is not included in the Subscribed DNN list), the AMF shall, based on operator policies received from PCF, either reject the NAS Message containing PDU Session Establishment Request from the UE with an appropriate cause or request PCF to replace the UE requested DNN by a selected DNN. If the DNN requested by the UE is present in the UE subscription information but indicated for replacement in the operator policies received from PCF, the AMF shall request the PCF to perform a DNN replacement to a selected DNN. AMF requests DNN replacement as specified in clause 4.16.2.1.1. If the DNN requested by the UE is present in the UE subscription information but not supported by the network and not indicated for replacement in the operator policies received from PCF, the AMF shall reject the NAS Message containing PDU Session Establishment Request from the UE with an appropriate cause value. The AMF selects an SMF as described in clause 6.3.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] and clause 4.3.2.2.3. If the Request Type indicates "Initial request" or the request is due to handover from EPS or from non-3GPP access serving by a different AMF, the AMF stores an association of the S-NSSAI(s), the DNN, the PDU Session ID, the SMF ID as well as the Access Type of the PDU Session. If the AMF determines to replace the S-NSSAI received from the UE with the Alternative S-NSSAI or the AMF receives the Alternative S-NSSAI and the S-NSSAI is by the UE, the AMF selects the SMF based on the Alternative S-NSSAI. During registration procedures, the AMF determines the use of the Control Plane CIoT 5GS Optimisation or User Plane CIoT 5GS Optimisation based on UEs indications in the 5G Preferred Network Behaviour, the serving operator policies and the network support of CIoT 5GS optimisations. The AMF selects an SMF that supports Control Plane CIoT 5GS optimisation or User Plane CIoT 5GS Optimisation as described in clause 6.3.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the Request Type is "initial request" and if the Old PDU Session ID indicating the existing PDU Session is also contained in the message, the AMF selects an SMF as described in clause 4.3.5.2 and stores an association of the new PDU Session ID, the S-NSSAI(s), the selected SMF ID as well as Access Type of the PDU Session. If the Request Type indicates "Existing PDU Session", the AMF selects the SMF based on SMF-ID received from UDM. The case where the Request Type indicates "Existing PDU Session" and either the AMF does not recognize the PDU Session ID or the subscription context that the AMF received from UDM during the Registration or Subscription Profile Update Notification procedure does not contain an SMF ID corresponding to the PDU Session ID constitutes an error case. The AMF updates the Access Type stored for the PDU Session. If the Request Type indicates "Existing PDU Session" referring to an existing PDU Session moved between 3GPP access and non-3GPP access, then if the Serving PLMN S-NSSAI of the PDU Session is present in the Allowed NSSAI of the target access type or Partially Allowed NSSAI, the PDU Session Establishment procedure can be performed in the following cases: - the SMF ID corresponding to the PDU Session ID and the AMF belong to the same PLMN; - the SMF ID corresponding to the PDU Session ID belongs to the HPLMN; Otherwise the AMF shall reject the PDU Session Establishment Request with an appropriate reject cause. NOTE 2: The SMF ID includes the PLMN ID that the SMF belongs to. The AMF shall reject a request coming from an Emergency Registered UE and the Request Type indicates neither "Emergency Request" nor "Existing Emergency PDU Session". When the Request Type indicates "Emergency Request", the AMF is not expecting any S-NSSAI and DNN value provided by the UE and uses locally configured values instead. The AMF stores the Access Type of the PDU Session. If the Request Type indicates "Emergency Request" or "Existing Emergency PDU Session", the AMF selects the SMF as described in clause 5.16.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the AMF is running a slice deregistration inactivity timer for the S-NSSAI of the PDU Session, the AMF stops the timer. 3. From AMF to SMF: Either Nsmf_PDUSession_CreateSMContext Request (SUPI, selected DNN, UE requested DNN, S-NSSAI(s), [Alternative S-NSSAI], PDU Session ID, AMF ID, Request Type, [PCF ID, Same PCF Selection Indication], Priority Access, [Small Data Rate Control Status], N1 SM container (PDU Session Establishment Request), User location information, Access Type, RAT Type, PEI, GPSI, UE presence in LADN service area, Subscription For PDU Session Status Notification, DNN Selection Mode, Trace Requirements, Control Plane CIoT 5GS Optimisation indication, Control Plane Only indicator, Satellite backhaul category, GEO Satellite ID, [PVS FQDN(s) and/or PVS IP address(es), Onboarding Indication], Disaster Roaming service indication) or Nsmf_PDUSession_UpdateSMContext Request (SUPI, DNN, S-NSSAI(s), SM Context ID, AMF ID, Request Type, N1 SM container (PDU Session Establishment Request), User location information, Access Type, RAT type, PEI, Serving Network (PLMN ID, or PLMN ID and NID, see clause 5.18 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]), Satellite backhaul category, GEO Satellite ID), [PCF binding information, notification of SM Policy Association establishment Indication]. If the AMF does not have an association with an SMF for the PDU Session ID provided by the UE (e.g. when Request Type indicates "initial request"), the AMF invokes the Nsmf_PDUSession_CreateSMContext Request, but if the AMF already has an association with an SMF for the PDU Session ID provided by the UE (e.g. when Request Type indicates "existing PDU Session"), the AMF invokes the Nsmf_PDUSession_UpdateSMContext Request. The AMF sends the S-NSSAI of the Serving PLMN from the Allowed NSSAI or Partially Allowed NSSAI to the SMF. If the AMF determined to replace the S-NSSAI received from the UE with an Alternative S-NSSAI and the AMF selected the SMF based on the Alternative S-NSSAI in step 2, the AMF sends both the S-NSSAI value of the Alternative S-NSSAI and the S-NSSAI value of the S-NSSAI received from the UE to the SMF. If the Alternative S-NSSAI and the S-NSSAI is provided by the UE and the AMF selected the SMF based on the Alternative S-NSSAI in step 2, the AMF sends both the S-NSSAI value of the Alternative S-NSSAI and the S-NSSAI value of the S-NSSAI received from the UE to the SMF. For roaming scenario in local breakout (LBO), the AMF also sends the corresponding S-NSSAI of the HPLMN from the Mapping Of Allowed NSSAI or Mapping Of Partially Allowed NSSAI to the SMF. If the AMF determines to replace the HPLMN S-NSSAI received from the UE with the HPLMN Alternative S-NSSAI or the AMF receives the HPLMN Alternative S-NSSAI and the HPLMN S-NSSAI provided by the UE, the AMF sends both HPLMN S-NSSAI and HPLMN Alternative S-NSSAI to the SMF. The AMF ID is the UE's GUAMI which uniquely identifies the AMF serving the UE. The AMF forwards the PDU Session ID together with the N1 SM container containing the PDU Session Establishment Request received from the UE. The GPSI shall be included if available at AMF. The AMF determines Access Type and RAT Type, see clause 4.2.2.2.1. The AMF provides the PEI instead of the SUPI when the UE in limited service state has registered for Emergency services (i.e. Emergency Registered) without providing a SUPI. The PEI is defined in clause 5.9.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the UE in limited service state has registered for Emergency services (i.e. Emergency Registered) with a SUPI but has not been authenticated the AMF indicates that the SUPI has not been authenticated. The SMF determines that the UE has not been authenticated when it does not receive a SUPI for the UE or when the AMF indicates that the SUPI has not been authenticated. If the AMF determines that the selected DNN corresponds to an LADN then the AMF provides the "UE presence in LADN service area" that indicates if the UE is IN or OUT of the LADN service area. If the AMF enforces the LADN Service Area per LADN DNN and S-NSSAI, then the AMF also provides an indication that "the PDU Session is subject to LADN per LADN DNN and S-NSSAI". If the Old PDU Session ID is included in step 1 and if the SMF is not to be reallocated, the AMF also includes Old PDU Session ID in the Nsmf_PDUSession_CreateSMContext Request. DNN Selection Mode is determined by the AMF. It indicates whether an explicitly subscribed DNN has been provided by the UE in its PDU Session Establishment Request. The SMF may use DNN Selection Mode when deciding whether to accept or reject the UE request. When the Establishment cause received as part of AN parameters during the Registration procedure or Service Request procedure is associated with priority services (e.g. MPS, MCX), or when the AMF determines the UE has priority subscription (e.g. MPS, MCX) in the UDM, the AMF includes a Message Priority header to indicate priority information. The SMF uses the Message Priority header to determine if the UE request is subject to exemption from NAS level congestion control. Other NFs relay the priority information by including the Message Priority header in service-based interfaces, as specified in TS 29.500[ 5G System; Technical Realization of Service Based Architecture; Stage 3 ] [17]. In the local breakout case, if the SMF (in the VPLMN) is not able to process some part of the N1 SM information that Home Routed Roaming is required and the SMF responds to the AMF that it is not the right SMF to handle the N1 SM message by invoking Nsmf_PDUSession_CreateSMContext Response service operation. The SMF includes a proper N11 cause code triggering the AMF to proceed with home routed case. The procedure starts again at step 2 of clause 4.3.2.2.2. In the non-roaming case, for PDU Session with Request Type "initial request", the AMF checks if the PCF Selection Assistance info from the UDM indicates that the same PCF is required for the requested DNN and S-NSSAI and if required, the AMF includes in Nsmf_PDUSession_CreateSMContext Request both the Same PCF Selection Indication and the PCF ID selected by the AMF, this PCF ID identifies the H-PCF, If PCF Selection Assistance info is not received from the UDM, the AMF may include a PCF ID in the Nsmf_PDUSession_CreateSMContext Request based on operator policies. This PCF ID identifies the H-PCF in the non-roaming case and the V-PCF in the local breakout roaming case. The AMF includes Trace Requirements if Trace Requirements have been received in subscription data. If the AMF decides to use the Control Plane CIoT 5GS Optimisation or User Plane CIoT 5GS Optimisation as specified in step 2 or to only use Control Plane CIoT 5GS Optimisation for the PDU session as described in clause 5.31.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], the AMF sends the Control Plane CIoT 5GS Optimisation indication or Control Plane Only indicator to the SMF. If the AMF determines that the RAT type is NB-IoT and the number of PDU Sessions with user plane resources activated for the UE has reached the maximum number of supported user plane resources (0, 1 or 2) based on whether the UE supports UP data transfer and the UE's 5GMM Core Network Capability as described in clause 5.31.19 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], the AMF may either reject the PDU Session Establishment Request or continue with the PDU Session establishment and include the Control Plane CIoT 5GS Optimisation indication or Control Plane Only indicator to the SMF. The AMF includes the latest Small Data Rate Control Status if it has stored it for the PDU Session. If the RAT type was included in the message, then the SMF stores the RAT type in SM Context. If the UE supports CE mode B and use of CE mode B is not restricted according to the Enhanced Coverage Restriction information in the UE context in the AMF, then the AMF shall include the extended NAS-SM timer indication. 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]. If the identity of an NWDAF is available to the AMF, the AMF informs the SMF of the NWDAF ID(s) used for UE related Analytics and corresponding Analytics ID(s). If the AMF, based on configuration, is aware that the UE is accessing over a gNB using satellite backhaul as defined in clause 5.43.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], the AMF determines the type of satellite backhaul category and includes Satellite backhaul category to the SMF. If the AMF, based on configuration, is aware that the UE is accessing over a gNB using GEO satellite backhaul, the AMF may, based on configuration, include the GEO satellite ID as described in clause 5.43.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The AMF may provide the Disaster Roaming service indication as specified in TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 4. If Session Management Subscription data for corresponding SUPI, DNN and S-NSSAI of the HPLMN is not available, then SMF retrieves the Session Management Subscription data using Nudm_SDM_Get (SUPI, Session Management Subscription data, selected DNN, S-NSSAI of the HPLMN, Serving PLMN ID, [NID]) and subscribes to be notified when this subscription data is modified using Nudm_SDM_Subscribe (SUPI, Session Management Subscription data, selected DNN, S-NSSAI of the HPLMN, Serving PLMN ID, [NID]). UDM may get this information from UDR by Nudr_DM_Query (SUPI, Subscription Data, Session Management Subscription data, selected DNN, S-NSSAI of the HPLMN, Serving PLMN ID, [NID]) and may subscribe to notifications from UDR for the same data by Nudr_DM_subscribe. If a S-NSSAI is subject to network slice usage control and the S-NSSAI is dedicated to a single AF, for a PDU Session for non-roaming subscribers, the UDM may provide a Slice Usage Policy information including whether a network slice is on demand and a PDU Session inactivity timer value as described in clause 5.15.15 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The SMF may use DNN Selection Mode when deciding whether to retrieve the Session Management Subscription data e.g. if the (selected DNN, S-NSSAI of the HPLMN) is not explicitly subscribed, the SMF may use local configuration instead of Session Management Subscription data. If the Request Type in step 3 indicates "Existing PDU Session" or "Existing Emergency PDU Session" the SMF determines that the request is due to switching between 3GPP access and non-3GPP access or due to handover from EPS. The SMF identifies the existing PDU Session based on the PDU Session ID. In such a case, the SMF does not create a new SM context but instead updates the existing SM context and provides the representation of the updated SM context to the AMF in the response. If the Request Type is "Initial request" and if the Old PDU Session ID is included in Nsmf_PDUSession_CreateSMContext Request, the SMF identifies the existing PDU Session to be released based on the Old PDU Session ID. Subscription data includes the Allowed PDU Session Type(s), Allowed SSC mode(s), default 5QI and ARP, subscribed Session-AMBR, SMF-Associated external parameters. IP Index or Static IP address/prefix may be included in the subscription data if the UE has subscribed to it. The SMF checks the validity of the UE request: it checks: - Whether the UE request is compliant with the user subscription and with local policies; - (If the selected DNN corresponds to an LADN), whether the UE is located within the LADN service area based on the "UE presence in LADN service area" indication from the AMF. If the AMF does not provide the "UE presence in LADN service area" indication and the SMF determines that the selected DNN corresponds to a LADN, then the SMF considers that the UE is OUT of the LADN service area. The SMF determines whether the PDU Session requires redundancy and the SMF determines the RSN as described in clause 5.33.2.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the SMF determines that redundant handling is not allowed or not possible for the given PDU Session, the SMF shall either reject the establishment of the PDU Session or accept the establishment of a PDU session without redundancy handling based on local policy. If the UE request is considered as not valid, the SMF decides to not accept to establish the PDU Session. NOTE 3: The SMF can, instead of the Nudm_SDM_Get service operation, use the Nudm_SDM_Subscribe service operation with an Immediate Report Indication that triggers the UDM to immediately return the subscribed data if the corresponding feature is supported by both the SMF and the UDM. For a Disaster Roaming service, the UDM provides the Session Management Subscription data to the SMF based on the local policy and/or the local configuration as specified in clause 5.40.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. For an S-NSSAI subject to NSAC and if LBO applies, the SMF in supporting VPLMN stores the applicable NSAC admission mode. 5. From SMF to AMF: Either Nsmf_PDUSession_CreateSMContext Response (Cause, SM Context ID or N1 SM container (PDU Session Reject (Cause))) or an Nsmf_PDUSession_UpdateSMContext Response depending on the request received in step 3. If the SMF received Nsmf_PDUSession_CreateSMContext Request in step 3 and the SMF is able to process the PDU Session establishment request, the SMF creates an SM context and responds to the AMF by providing an SM Context ID. If the UP Security Policy for the PDU Session is determined to have Integrity Protection set to "Required", the SMF may, based on local configuration, decide whether to accept or reject the PDU Session request based on the UE Integrity Protection Maximum Data Rate. NOTE 4: The SMF can e.g. be configured to reject a PDU Session if the UE Integrity Protection Maximum Data Rate has a very low value, if the services provided by the DN would require higher bitrates. When the SMF decides to not accept to establish a PDU Session, the SMF rejects the UE request via NAS SM signalling including a relevant SM rejection cause by responding to the AMF with Nsmf_PDUSession_CreateSMContext Response. The SMF also indicates to the AMF that the PDU Session ID is to be considered as released, the SMF proceeds to step 20 and the PDU Session Establishment procedure is stopped. 6. Optional Secondary authentication/authorization. If the Request Type in step 3 indicates "Existing PDU Session", the SMF does not perform secondary authentication/authorization. If the Request Type received in step 3 indicates "Emergency Request" or "Existing Emergency PDU Session", the SMF shall not perform secondary authentication\authorization. If the SMF needs to perform secondary authentication/authorization during the establishment of the PDU Session by a DN-AAA Server as described in clause 5.6.6 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], the SMF triggers the PDU Session establishment authentication/authorization as described in clause 4.3.2.3. 7a. If dynamic PCC is to be used for the PDU Session, the SMF performs PCF selection as described in clause 6.3.7.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the Request Type indicates "Existing PDU Session" or "Existing Emergency PDU Session", the SMF shall use the PCF already selected for the PDU Session. Otherwise, the SMF may apply local policy. 7b. The SMF may perform an SM Policy Association Establishment procedure as defined in clause 4.16.4 to establish an SM Policy Association with the PCF and get the default PCC Rules for the PDU Session. The SMF shall include the 3GPP Data Off status if received in step 1. The GPSI, PVS FQDN(s) and/or PVS IP address(es) and the Onboarding Indication shall be included if available at SMF in the case of ON-SNPN. The SMF shall include both the S-NSSAI and the Alternative S-NSSAI, if received in step 3. If the Request Type in step 3 indicates "Existing PDU Session", the SMF provides information on the Policy Control Request Trigger condition(s) that have been met by an SMF initiated SM Policy Association Modification procedure as defined in clause 4.16.5.1. The PCF may provide policy information defined in clause 5.2.5.4 (and in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]) to SMF. The URSP rule enforcement in step 1 may be included if SMF receives the URSP rule enforcement from UE 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]. The PCF for the UE subscribes to notifications of event "UE reporting Connection Capabilities from associated URSP rule" as defined in clause 6.1.3.18 in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20], using Npcf_PolicyAuthorization_Subscribe (EventId set to "UE reporting Connection Capabilities from associated URSP rule", EventFilter set to at least "list of Connection Capabilities") to the PCF for the PDU Session. The PCF for session may notify the PCF for UE about the URSP rule enforcement together with the PDU session parameters that this application associated with by Npcf_PolicyAuthorization_Notify. During the SM Policy Association Establishment procedure, if the PCF detects the request relates to SM Policy Association enabling integration with TSN or TSC or Deterministic Networking (as defined in TS 23.501[ System architecture for the 5G System (5GS) ] [2] clause 5.28) based on local configuration, the PCF may provide policy control request trigger for 5GS Bridge/Router Information as defined in clause 6.1.3.5 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. The PCF, based on the Emergency DNN, sets the ARP of the PCC rules to a value that is reserved for Emergency services as described in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. NOTE 5: The purpose of step 7 is to receive PCC rules before selecting UPF. If PCC rules are not needed as input for UPF selection, step 7 can be performed after step 8. - During the SM Policy Association Establishment procedure for a non-roaming PDU Session, if a S-NSSAI is subject to network slice usage control, the PCF may provide a Slice Usage Policy information including whether a network slice is on demand and a PDU Session inactivity timer value as described in clause 5.15.15 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 8. If the Request Type in step 3 indicates "Initial request", the SMF selects an SSC mode for the PDU Session as described in clause 5.6.9.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The SMF also selects one or more UPFs as needed as described in clause 6.3.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. In the case of PDU Session Type IPv4 or IPv6 or IPv4v6, the SMF allocates an IP address/prefix for the PDU Session (unless configured otherwise) as described in clause 5.8.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. In the case of PDU Session Type IPv6 or IPv4v6, the SMF also allocates an interface identifier to the UE for the UE to build its link-local address. For Unstructured PDU Session Type the SMF may allocate an IPv6 prefix for the PDU Session and N6 point-to-point tunnelling (based on UDP/IPv6) as described in clause 5.6.10.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. For Ethernet PDU Session Type, neither a MAC nor an IP address is allocated by the SMF to the UE for this PDU Session. If the AMF indicated Control Plane CIoT 5GS Optimisation in step 3 for this PDU session, then, 1) For Unstructured PDU Session Type, the SMF checks whether UE's subscription include a "NEF Identity for NIDD" for the DNN/S-NSSAI combination. When the "NEF Identity for NIDD" is present in the UE's subscription data, the SMF will select the NEF identified for the S-NSSAI and selected DNN in the "NEF Identity for NIDD" as the anchor of this PDU Session. Otherwise, the SMF will select a UPF as the anchor of this PDU Session. 2) For other PDU Session Types, the SMF will perform UPF selection to select a UPF as the anchor of this PDU Session. If the Request Type in Step 3 is "Existing PDU Session", the SMF maintains the same IP address/prefix that has already been allocated to the UE in the source network. If the Request Type in step 3 indicates "Existing PDU Session" referring to an existing PDU Session moved between 3GPP access and non-3GPP access the SMF maintains the SSC mode of the PDU Session, the current PDU Session Anchor and IP address. NOTE 6: The SMF may decide to trigger e.g. new intermediate UPF insertion or allocation of a new UPF as described in step 5 in clause 4.2.3.2. If the Request Type indicates "Emergency Request", the SMF selects the UPF as described in clause 5.16.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] and selects SSC mode 1. SMF may select a UPF (e.g. based on requested DNN/S-NSSAI) that supports NW-TT functionality. SMF may select a PSA UPF that supports PDU Set identification and marking for a QoS flow with PDU Set based handling capability. 9. SMF may perform an SMF initiated SM Policy Association Modification procedure as defined in clause 4.16.5.1 to provide information on the Policy Control Request Trigger condition(s) that have been met. If Request Type is "initial request" and dynamic PCC is deployed and PDU Session Type is IPv4 or IPv6 or IPv4v6, SMF notifies the PCF (if the Policy Control Request Trigger condition is met) with the allocated UE IP address/prefix(es). NOTE 7: If an IP address/prefix has been allocated before step 7 (e.g. subscribed static IP address/prefix in UDM/UDR) or the step 7 is performed after step 8, the IP address/prefix can be provided to PCF in step 7 and the IP address/prefix notification in this step can be skipped. PCF may provide updated policies to the SMF. The PCF may provide policy information defined in clause 5.2.5.4 (and in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]) to SMF. The PCF for PDU Session may generate PCC rule based on the URSP rule (e.g.: Connection Capability) referring to the clause 6.1.6 in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. NOTE 8: Mapping between Connection Capability and SDF templates in the PCC rule is implementation specific. 10. If Request Type indicates "initial request", the SMF initiates an N4 Session Establishment procedure with the selected UPF(s), otherwise it initiates an N4 Session Modification procedure with the selected UPF(s): 10a. The SMF sends an N4 Session Establishment/Modification Request to the UPF and provides Packet detection, enforcement and reporting rules to be installed on the UPF for this PDU Session. If the SMF is configured to request IP address allocation from UPF as described in clause 5.8.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] then the SMF indicates to the UPF to perform the IP address/prefix allocation and includes the information required for the UPF to perform the allocation. If the selective User Plane deactivation is required for this PDU Session, the SMF determines the inactivity timer and provides it to the UPF. For a PDU Session for non-roaming subscribers, if the S-NSSAI of the PDU Session is subject to network slice usage control, the SMF obtains the PDU Session inactivity timer value for the PDU Session as described in step 4 or step 7 or uses preconfigured value and configures the UPF to run the PDU Session inactivity timer. The SMF provides Trace Requirements to the UPF if it has received Trace Requirements. If the Reliable Data Service is enabled for the PDU Session by the SMF as specified in TS 23.501[ System architecture for the 5G System (5GS) ] [2], the RDS Configuration information is provided to the UPF in this step. The SMF provides Small Data Rate Control parameters to the UPF for the PDU Session, if required. The SMF provides the Small Data Rate Control Status to the UPF, if received from the AMF. If the Serving PLMN intends to enforce Serving PLMN Rate Control (see clause 5.31.14.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]) for this PDU session then the SMF shall provide Serving PLMN Rate Control parameters to UPF for limiting the rate of downlink control plane data packets. For a PDU Session of type Ethernet or IP, the SMF (e.g. for a certain requested DNN/S-NSSAI for which Time Sensitive Networking, Time Sensitive Communications, Time Synchronization and/or Deterministic Networking is applicable) may include an indication to request UPF to provide a port number. If SMF decides to perform redundant transmission for one or more QoS Flows of the PDU session as described in clause 5.33.1.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], two CN Tunnel Info are requested by the SMF from the UPF. The SMF also indicates the UPF to eliminate the duplicated packet for the QoS Flow in uplink direction. The SMF indicates the UPF that one CN Tunnel Info is used as the redundancy tunnel of the PDU session described in clause 5.33.2.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If SMF decides to insert two I-UPFs between the PSA UPF and the NG-RAN for redundant transmission as described in clause 5.33.1.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], the SMF requests the corresponding CN Tunnel Info and provides them to the I-UPFs and PSA UPF respectively. The SMF also indicates the PSA UPF to eliminate the duplicated packet for the QoS Flow in uplink direction. The SMF indicates the PSA UPF that one CN Tunnel Info is used as the redundancy tunnel of the PDU session described in clause 5.33.2.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. NOTE 9: 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 Control Plane CIoT 5GS Optimisation is enabled for this PDU session and the SMF selects the NEF as the anchor of this PDU Session in step 8, the SMF performs SMF-NEF Connection Establishment Procedure as described in clause 4.25.2. If interworking with TSN deployed in the transport network is supported (see clause 4.4.8 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]) and the UPF supports CN-TL, the SMF includes a TL-Container with a get-request to the N4 Session Establishment/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 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]. 10b. The UPF acknowledges by sending an N4 Session Establishment/Modification Response. If the SMF indicates in step 10a that IP address/prefix allocation is to be performed by the UPF then this response contains the requested IP address/prefix. The requested CN Tunnel Info is provided to SMF in this step. If SMF indicated the UPF to perform packet duplication and elimination for the QoS Flow in step 10a, two CN Tunnel Info are allocated by the UPF and provided to the SMF. If SMF decides to insert two I-UPFs between the PSA UPF and the NG-RAN for redundant transmission as described in clause 5.33.1.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], CN Tunnel Info of two I-UPFs and the UPF (PSA) are allocated by the UPFs and provided to the SMF. The UPF indicates the SMF that one CN Tunnel Info is used as the redundancy tunnel of the PDU session as described in clause 5.33.2.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If SMF requested UPF to provide a port number then UPF includes the port number and user-plane Node ID in the response according to TS 23.501[ System architecture for the 5G System (5GS) ] [2]. To support integration with IEEE TSN, the user-plane node ID is Bridge ID. To support integration with IETF DetNet, the user-plane node ID can be Router ID. Besides the network instance, the SMF may also provide DNN/S-NSSAI for the UPF to respond with user-plane Node ID based on pre-configuration information. If multiple UPFs are selected for the PDU Session, the SMF initiate N4 Session Establishment/Modification procedure with each UPF of the PDU Session in this step. NOTE 10: If the PCF has subscribed to the UE IP address change Policy Control Trigger (as specified in clause 6.1.3.5 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]) then the SMF notifies the PCF about the IP address/prefix allocated by the UPF. This is not shown in figure 4.3.2.2.1-1. If interworking with TSN deployed in the transport network is supported and the UPF supports CN-TL and received a TL-Container with a get-request from the SMF/CUC in step 10a (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 get-response in the N4 Session Establishment/Modification response, as described in clause 5.28a.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The SMF/CUC stores the information provided in the get-response. 11. SMF to AMF: Namf_Communication_N1N2MessageTransfer (PDU Session ID, N2 SM information (PDU Session ID, QFI(s), QoS Profile(s), CN Tunnel Info, S-NSSAI from the Allowed NSSAI or Partially Allowed NSSAI, Session-AMBR, PDU Session Type, User Plane Security Enforcement information, UE Integrity Protection Maximum Data Rate, RSN, PDU Session Pair ID, TL-Container), N1 SM container (PDU Session Establishment Accept ([QoS Rule(s) and QoS Flow level QoS parameters if needed for the QoS Flow(s) associated with the QoS rule(s)], selected SSC mode, S-NSSAI(s), UE Requested DNN, allocated IPv4 address, interface identifier, Session-AMBR, selected PDU Session Type, [Reflective QoS Timer] (if available), [P-CSCF address(es)], [Control Plane Only indicator], [Header Compression Configuration], [Always-on PDU Session Granted], [Small Data Rate Control parameters], [Small Data Rate Control Status], [Serving PLMN Rate Control], [PVS FQDN(s) and/or PVS IP address(es)], [Non-3GPP QoS Assistance Information Container]))). If multiple UPFs are used for the PDU Session, the CN Tunnel Info contains tunnel information related with the UPFs that terminate N3. The SMF may provide the SMF derived CN assisted RAN parameters tuning to the AMF by invoking Nsmf_PDUSession_SMContextStatusNotify (SMF derived CN assisted RAN parameters tuning) service. The AMF stores the SMF derived CN assisted RAN parameters tuning in the associated PDU Session context for this UE. The N2 SM information carries information that the AMF shall forward to the (R)AN which includes: - The CN Tunnel Info corresponds to the Core Network address(es) of the N3 tunnel corresponding to the PDU Session. If two CN Tunnel Info are included for the PDU session for redundant transmission, the SMF also indicates the NG-RAN that one of the CN Tunnel Info used as the redundancy tunnel of the PDU session as described in clause 5.33.2.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. - One or multiple QoS profiles and the corresponding QFIs can be provided to the (R)AN. This is further described in clause 5.7 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The SMF may indicate for each QoS Flow whether redundant transmission shall be performed by a corresponding redundant transmission indicator. - The PDU Session ID may be used by AN signalling with the UE to indicate to the UE the association between (R)AN resources and a PDU Session for the UE. - A PDU Session is associated to an S-NSSAI of the HPLMN and if applicable, to an S-NSSAI of the VPLMN and a DNN. The S-NSSAI provided to the (R)AN, is the S-NSSAI with the value for the Serving PLMN (i.e. the HPLMN S-NSSAI or, in LBO roaming case, the VPLMN S-NSSAI). When Alternative S-NSSAI is received from AMF in step 3, the S-NSSAI provided to the (R)AN is the Alternative S-NSSAI. - User Plane Security Enforcement information is determined by the SMF as described in clause 5.10.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. - If the User Plane Security Enforcement information indicates that Integrity Protection is "Preferred" or "Required", the SMF also includes the UE Integrity Protection Maximum Data Rate as received in the PDU Session Establishment Request. - The use of the RSN parameter and the PDU Session Pair ID by NG-RAN are described in clause 5.33.2.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. - 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]. - TL-Container as described in clause 5.28a.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If interworking with TSN deployed in the transport network is supported and the NG-RAN supports AN-TL (see clause 4.4.8 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]), the SMF includes a TL-Container with a get-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]. The N1 SM container contains the PDU Session Establishment Accept that the AMF shall provide to the UE. If the UE requested P-CSCF discovery then the message shall also include the P-CSCF IP address(es) as determined by the SMF and as described in clause 5.16.3.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The PDU Session Establishment Accept includes S-NSSAI from the Allowed NSSAI or Partially Allowed NSSAI. The S-NSSAI value of the Alternative S-NSSAI is included in the PDU session Establishment Accept if the SMF has received the Alternative S-NSSAI from the AMF. For LBO roaming scenario, the PDU Session Establishment Accept includes the S-NSSAI from the Allowed NSSAI or Partially Allowed NSSAI for the VPLMN and also it includes the corresponding S-NSSAI of the HPLMN from the Mapping Of Allowed NSSAI or Mapping Of Partially Allowed NSSAI that SMF received in step 3. If the SMF has received the VPLMN Alternative S-NSSAI from the AMF, the PDU Session Establishment Accept includes the VPLMN Alternative S-NSSAI. If the SMF has received the HPLMN Alternative S-NSSAI from the AMF, the PDU Session Establishment Accept includes the HPLMN Alternative S-NSSAI. If the PDU Session being established was requested to be an always-on PDU Session, the SMF shall indicate whether the request is accepted by including an Always-on PDU Session Granted indication in the PDU Session Establishment Accept message. If the PDU Session being established was not requested to be an always-on PDU Session but the SMF determines that the PDU Session needs to be established as an always-on PDU Session, the SMF shall include an Always-on PDU Session Granted indication in the PDU Session Establishment Accept message indicating that the PDU session is an always-on PDU Session. If Control Plane CIoT 5GS Optimisation is enabled for this PDU session, the N2 SM information is not included in this step. If Control Plane CIoT 5GS optimisation is enabled for this PDU session and the UE has sent the Header Compression Configuration in the PDU Session Establishment Request and the SMF supports the header compression parameters, the SMF shall include the Header Compression Configuration in the PDU Session Establishment Accept message. If the UE has included Header Compression context parameters in Header Compression Configuration in the PDU Session Establishment Request, the SMF shall establish the header compression context and may acknowledge the Header Compression context parameters. If the header compression context is not established during the PDU Session Establishment procedure, before using the compressed format for sending the data, the UE and the SMF need to establish the header compression context based on the Header Compression Configuration. If the SMF has received the Control Plane Only Indicator in step 3, the SMF shall include the Control Plane Only Indicator in the PDU Session Establishment Accept message. The SMF shall indicate the use of Control Plane only on its CDR. If the Small Data Rate Control is configured in the SMF, the SMF shall also include Small Data Rate Control parameters and the Small Data Rate Control Status (if received from the AMF) in the PDU Session Establishment Accept message as described in clause 5.31.14.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the Serving PLMN intends to enforce Serving PLMN Rate Control (see clause 5.31.14.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]) for this PDU session then the SMF shall include the Serving PLMN Rate Control parameters in the PDU Session Establishment Accept message. The UE shall store and use Serving PLMN Rate Control parameters as the maximum allowed limit of uplink control plane user data. If the UE indicates the support of RDS in the PCO in the PDU Session Establishment Request and RDS is enabled for the PDU Session, the SMF shall inform the UE that RDS is enabled in the PCO in the PDU Session Establishment Accept (see clause 5.31.6 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]). If the NIDD parameters (e.g. maximum packet size) were received from NEF during the SMF-NEF Connection Establishment procedure in step 10, the SMF shall inform the UE of the NIDD parameters in the PCO in the PDU Session Establishment Accept (see clause 5.31.5 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]). If the UE indicated in the PCO that it supports the ability to receive ECS address(es) via NAS, the SMF may provide the ECS Address Configuration Information (as described in clause 6.5.2 of TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [74]) to the UE in the PCO. The SMF may derive the ECS Address Configuration Information based on local configuration and/or UE subscription information. In non-roaming scenarios, the SMF may also derive the ECS Address Configuration Information based on the UE's location. 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]). Multiple QoS Rules, QoS Flow level QoS parameters if needed for the QoS Flow(s) associated with those QoS rule(s) and QoS Profiles may be included in the PDU Session Establishment Accept within the N1 SM and in the N2 SM information. The Namf_Communication_N1N2MessageTransfer contains the PDU Session ID allowing the AMF to know which access towards the UE to use. If the PDU session establishment failed anywhere between step 5 and step 11, then the Namf_Communication_N1N2MessageTransfer request shall include the N1 SM container with a PDU Session Establishment Reject message (see clause 8.3.3 of TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [25]) and shall not include any N2 SM container. The (R)AN sends the NAS message containing the PDU Session Establishment Reject to the UE. In this case, steps 12-17 are skipped. 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 as specified in clause 5.44.3.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 12. AMF to (R)AN: N2 PDU Session Request (N2 SM information, NAS message (PDU Session ID, N1 SM container (PDU Session Establishment Accept)), [CN assisted RAN parameters tuning]). If the N2 SM information is not included in the step 11, an N2 Downlink NAS Transport message is used instead. The AMF sends the NAS message containing PDU Session ID and PDU Session Establishment Accept targeted to the UE and the N2 SM information received from the SMF within the N2 PDU Session Request to the (R)AN. If the SMF derived CN assisted RAN parameters tuning are stored for the activated PDU Session(s), the AMF may derive updated CN assisted RAN parameters tuning and provide them the (R)AN. 13. (R)AN to UE: 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 establishing the necessary NG-RAN resources related to the QoS Rules for the PDU Session request received in step 12. (R)AN also allocates (R)AN Tunnel Info for the PDU Session. In the case of Dual Connectivity, the Master RAN node may assign some (zero or more) QFIs to be setup to a Master RAN node and others to the Secondary RAN node. The AN Tunnel Info includes a tunnel endpoint for each involved (R)AN node and the QFIs assigned to each tunnel endpoint. A QFI can be assigned to either the Master RAN node or the Secondary RAN node and not to both. If the (R)AN receives two CN Tunnel Info for a PDU session in step 12 for redundant transmission, (R)AN also allocates two AN Tunnel Info correspondingly and indicate to SMF one of the AN Tunnel Info is used as the redundancy tunnel of the PDU session as described in clause 5.33.2.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. (R)AN forwards the NAS message (PDU Session ID, N1 SM container (PDU Session Establishment Accept)) provided in step 12 to the UE. (R)AN shall only provide the NAS message to the UE if the AN specific signalling exchange with the UE includes the (R)AN resource additions associated to the received N2 command. If MICO mode is active and the NAS message Request Type in step 1 indicated "Emergency Request", then the UE and the AMF shall locally deactivate MICO mode. If the N2 SM information is not included in the step 11, then the following steps 14 to 16b and step 17 are omitted. If the AMF is running a slice deregistration inactivity timer for the S-NSSAI PDU Session, the AMF stops the timer as described in clause 5.15.15 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the UE is running a slice deregistration inactivity timer for the S-NSSAI of the established PDU Session, the UE stops the timer as described in clause 5.15.15 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 14. (R)AN to AMF: N2 PDU Session Response (PDU Session ID, Cause, N2 SM information (PDU Session ID, AN Tunnel Info, List of accepted/rejected QFI(s), User Plane Enforcement Policy Notification, TL-Container, 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)). The AN Tunnel Info corresponds to the Access Network address of the N3 tunnel corresponding to the PDU Session. 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 QFI(s) the SMF is responsible of updating the QoS rules and QoS Flow level QoS parameters associated to the rejected QoS Flow(s) in the UE accordingly. The NG-RAN rejects the establishment of UP resources for the PDU Session when it cannot fulfil User Plane Security Enforcement information with a value of Required. The NG-RAN notifies the SMF when it cannot fulfil a User Plane Security Enforcement with a value of Preferred. If the NG-RAN cannot establish redundant user plane for the PDU Session as indicated by the RSN parameter and PDU Session Pair ID, the NG-RAN takes the decision on whether to reject the establishment of RAN resources for the PDU Session based on local policies as described in TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 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 get-request from the SMF/CUC in step 12 (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 get-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]. 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]. 15. AMF to SMF: Nsmf_PDUSession_UpdateSMContext Request (SM Context ID, N2 SM information, Request Type). The AMF forwards the N2 SM information received from (R)AN to the SMF. If the list of rejected QFI(s) is included in N2 SM information, the SMF shall release the rejected QFI(s) associated QoS profiles. If the N2 SM information indicates failure of user plane resource setup, the SMF shall reject the PDU session establishment by including a N1 SM container with a PDU Session Establishment 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 17. Step 16 is skipped in this case and instead the SMF releases the N4 Session with UPF. If the User Plane Enforcement Policy Notification in the N2 SM information indicates that no user plane resources could be established and the User Plane Enforcement Policy indicated "required" as described in clause 5.10.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], the SMF shall reject the PDU session establishment by including a N1 SM container with a PDU Session Establishment 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 17. Step 16 is skipped in this case. If the N2 SM information includes a TL-Container with a get-response as described in clause 5.28a.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], the SMF/CUC stores the information provided in the get-response. 16a. The SMF initiates an N4 Session Modification procedure with the UPF. The SMF provides AN Tunnel Info to the UPF as well as the corresponding forwarding rules. If SMF decides to perform redundant transmission for one or more QoS Flows of the PDU, the SMF also indicates the UPF to perform packet duplication for the QoS Flow(s) in downlink direction by forwarding rules. In the case of redundant transmission with two I-UPFs for one or more QoS Flows of the PDU, the SMF provides AN Tunnel Info to two I-UPFs and also indicates the UPF (PSA) to perform packet duplication for the QoS Flow(s) in downlink direction by forwarding rules. The SMF also provides the UL Tunnel Info of the UPF (PSA) to the two I-UPFs and the DL Tunnel Info of the two I-UPFs to the UPF (PSA). If the N2 SM information includes the PDU Set Based Handling Support Indication, SMF configures PSA UPF to perform PDU Set information marking for the QoS flow as defined in clause 5.37.5.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. NOTE 11: If the PDU Session Establishment Request was due to mobility between 3GPP and non-3GPP access or mobility from EPC, the downlink data path is switched towards the target access in this step. 16b. The UPF provides an N4 Session Modification Response to the SMF. If multiple UPFs are used in the PDU Session, the UPF in step 16 refers to the UPF terminating N3. After this step, the UPF delivers any down-link packets to the UE that may have been buffered for this PDU Session. 16c. If Request Type in step 3 indicates neither "Emergency Request" nor "Existing Emergency PDU Session" and if the SMF has not yet registered for this PDU Session, then the SMF registers with the UDM using Nudm_UECM_Registration (SUPI, DNN, S-NSSAI of HPLMN, PDU Session ID, SMF Identity, Serving Node PLMN ID, [NID]) for a given PDU Session. As a result, the UDM stores following information: SUPI, SMF identity and the associated DNN, S-NSSAI of HPLMN, PDU Session ID and Serving Network (PLMN ID, [NID], see clause 5.18 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]). The UDM may further store this information in UDR by Nudr_DM_Update (SUPI, Subscription Data, UE context in SMF data). If the UDM has existing applicable event exposure subscriptions for events detected in SMF for this UE or any of the groups this UE belongs to (possibly retrieved from UDR), UDM invokes the Nsmf_EventExposure_Subscribe service for creating the event exposure subscriptions. If the Request Type received in step 3 indicates "Emergency Request": - For an authenticated non-roaming UE, based on operator configuration (e.g. related with whether the operator uses a fixed SMF for Emergency calls, etc.), the SMF may register in the UDM using Nudm_UECM_Registration (SUPI, PDU Session ID, SMF identity, Indication of Emergency Services) for a given PDU Session that is applicable for emergency services. As a result, the UDM shall store the applicable PDU Session for Emergency services. - For an unauthenticated UE or a roaming UE, the SMF shall not register in the UDM for a given PDU Session. 17. SMF to AMF: Nsmf_PDUSession_UpdateSMContext Response (Cause). The SMF may subscribe to the UE mobility event notification from the AMF (e.g. location reporting, UE moving into or out of Area Of Interest), after this step by invoking Namf_EventExposure_Subscribe service operation as specified in clause 5.2.2.3.2. For LADN, the SMF subscribes to the UE moving into or out of LADN service area event notification by providing the LADN DNN as an indicator for the Area Of Interest (see clause 5.6.5 and 5.6.11 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]). If SMF receives the indication in step 3 that "the PDU Session is subject to LADN per LADN DNN and S-NSSAI", the SMF subscribes to the UE moving into or out of LADN service area event notification by providing the LADN DNN and S-NSSAI as an indicator for the Area Of Interest. After this step, the AMF forwards relevant events subscribed by the SMF. For those scenarios where the PCFs serving the AMF and the SMF are different, the SMF informs the AMF of the NWDAF ID(s) used for UE related Analytics and corresponding Analytics ID(s). 18. [Conditional] SMF to AMF: Nsmf_PDUSession_SMContextStatusNotify (Release) If during the procedure, any time after step 5, the PDU Session establishment is not successful, the SMF informs the AMF by invoking Nsmf_PDUSession_SMContextStatusNotify (Release). The SMF also releases any N4 session(s) created, any PDU Session address if allocated (e.g. IP address) and releases the association with PCF, if any. In this case, step 19 is skipped. For a PDU Session for non-roaming subscribers, if the S-NSSAI of the PDU Session is subject to network slice usage control and there is no other PDU Session using the S-NSSAI, the AMF starts the slice deregistration inactivity timer for the S-NSSAI as described in clause 5.15.15.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 19. SMF to UE: In the case of PDU Session Type IPv6 or IPv4v6, the SMF generates an IPv6 Router Advertisement and sends it to the UE. If Control Plane CIoT 5GS Optimisation is enabled for this PDU Session the SMF sends the IPv6 Router Advertisement via the AMF for transmission to the UE using the Mobile Terminated Data Transport in Control Plane CIoT 5GS Optimisation procedures (see clause 4.24.2), otherwise the SMF sends the IPv6 Router Advertisement via N4 and the UPF. 20. When the trigger for 5GS Bridge/Router information available is armed, then the SMF may initiate the SM Policy Association Modification as described in clause 4.16.5.1. If the UE has indicated support of transferring Port Management Information Containers, then SMF informs PCF that 5GS Bridge/Router information is available. SMF provides the 5GS Bridge/Router information (e.g. 5GS user-plane Node ID, port number for the PDU session, MAC address of the DS-TT Ethernet port for Ethernet PDU Session type, UE IP address for IP PDU Session type and UE-DS-TT Residence Time (if available) as provided by the UE) to PCF. In the case of Deterministic Networking, the SMF may also provide the MTU size for IPv4 or the MTU size for IPv6. If the SMF received a Port Management Information Container from either the UE or the UPF, then the SMF provides the Port Management Information Container and port number of the related port to the PCF as described in clause 5.28.3.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the SMF has received User Plane Node Management Information from the UPF, then the SMF provides the User Plane Node Management Information Container to the PCF as part of 5GS Bridge/Router information and as described in clause 5.28.3.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. To support IEEE TSN, the TSN AF calculates the bridge delay for each port pair, i.e. composed of DS-TT Ethernet port and NW-TT Ethernet port, using the UE-DS-TT Residence Time for all NW-TT Ethernet port(s) serving the 5GS Bridge indicated by the 5GS user-plane Node ID. Additionally, the TSN AF determines the 5GS bridge delay for port pair composed of two DS-TT ports connecting to the same 5GS Bridge as sum of bridge delays related to PDU Sessions of the two DS-TT ports. 21. If the PDU Session establishment failed after step 4, the SMF shall perform the following: The SMF unsubscribes to the modifications of Session Management Subscription data for the corresponding (SUPI, DNN, S-NSSAI of the HPLMN), using Nudm_SDM_Unsubscribe (SUPI, Session Management Subscription data, DNN, S-NSSAI of the HPLMN), if the SMF is no more handling a PDU Session of the UE for this (DNN, S-NSSAI of the HPLMN). The UDM may unsubscribe to the modification notification from UDR by Nudr_DM_Unsubscribe (SUPI, Subscription Data, Session Management Subscription data, S-NSSAI of the HPLMN, DNN). | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3.2.2.1 |
4,016 | 21.4 RAN Visible QoE Measurements | RAN visible QoE measurements are configured at the UE by the gNB, where a subset of configured QoE metrics is reported from the UE to the gNB as an explicit IE readable by the gNB. The RAN visible QoE measurements can be used by the gNB for network optimization. The RAN visible QoE measurements are supported for the DASH streaming and VR services. The gNB configures the RAN visible QoE measurement of all or some of the available RAN visible QoE metrics, where the indication of metric availability is received by the gNB as part of management-based or the signalling-based QoE configuration. The set of available RAN visible QoE metrics is a subset of the metrics configured as part of QoE measurement configuration encapsulated in the application layer measurement configuration container. RAN visible QoE measurements and encapsulated QoE measurements can be configured together or separately. RAN visible QoE measurements can only be configured if there is a corresponding QoE measurement configuration for the same service type configured at the UE. The gNB may modify a RAN visible QoE configuration by releasing it and configuring the UE with a new RAN visible QoE configuration pertaining to the same QoE reference. In this case, the new RAN visible QoE configuration applies immediately, i.e., even during the same application session. Multiple simultaneous RAN visible QoE measurement configurations and reports can be supported for RAN visible QoE measurements, and each RAN visible QoE measurement configuration and report is identified by the same measurement configuration application layer ID as the corresponding QoE measurement configuration and measurement report. After receiving the RAN visible QoE measurement configuration, the UE RRC layer forwards the configuration to the application layer, indicating the service type, the measurement configuration application layer ID and, optionally, the reporting periodicity for RAN visible QoE. The application layer sends the RAN visible QoE measurement report associated with the measurement configuration application layer ID to the UE's AS layer. The PDU session ID(s) and QoS Flow ID(s) per PDU session ID corresponding to the service that is subject to QoE measurements can also be reported by the UE along with the RAN visible QoE measurement results. If there is no reporting periodicity defined in the RAN visible QoE configuration, the UE sends both RAN visible QoE measurement reports and the QoE measurement reports to the gNB in the same MeasurementReportAppLayer message, except when QoE measurement reporting pause indication is received (e.g., in case of RAN overload). When a QoE measurement collection is paused, if there is no reporting periodicity defined in the RAN visible QoE configuration, the encapsulated QoE reports are stored at the UE's RRC layer, but the RAN visible QoE reports continue to be reported to the gNB with the reporting periodicity configured for encapsulated QoE reporting. The RAN visible QoE measurements can be reported with a reporting periodicity different from the one of the corresponding encapsulated QoE measurements, when a dedicated RAN visible QoE reporting periodicity is configured by the gNB. The UE Application layer can measure the RAN visible QoE metrics based on this reporting periodicity. The gNB can release one or multiple RAN visible QoE measurement configurations from the UE in one RRCReconfiguration message at any time. If the encapsulated QoE configuration is released, the corresponding RAN visible QoE configuration shall be released as well. The RAN visible QoE configuration can be transferred from the source gNB to the target gNB upon mobility and from the old gNB to the new gNB during context retrieval. The target gNB or the new gNB can generate a new RAN visible QoE configuration based on the available RAN visible QoE metrics received and can send the new RAN visible QoE configuration to the UE during handover or the RRC resume procedure. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 21.4 |
4,017 | 6.1.3.8.4 Abnormal cases | The following abnormal cases can be identified: a) Expiry of timers in the mobile station: On the first expiry of the timer T3380, the MS shall resend the ACTIVATE MBMS CONTEXT REQUEST and shall reset and restart timer T3380. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3380, the MS shall release all resources possibly allocated for this invocation and shall abort the procedure; no automatic MBMS context activation re-attempt shall be performed. b) Expiry of timers on the network side: On the first expiry of the timer T3385, the network shall resend the message REQUEST MBMS CONTEXT ACTIVATION and shall reset and restart timer T3385. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3385, the network shall release possibly allocated resources for this activation and shall abort the procedure. c) MBMS context activation request for an already activated MBMS context (on the mobile station side): If the MS receives a REQUEST MBMS CONTEXT ACTIVATION message with the same combination of APN and IP multicast address (i.e. PDP type and PDP address) as an already activated MBMS context, the MS shall deactivate the existing MBMS context locally without notification to the network and proceed with the requested MBMS context activation. d) MBMS context activation request for an already activated MBMS context (on the network side): If the network receives an ACTIVATE MBMS CONTEXT REQUEST message with the same combination of APN and IP multicast address (i.e. PDP type and PDP address) as an already activated MBMS context, the network shall deactivate the existing MBMS context locally without notification to the MS and proceed with the requested MBMS context activation. Figure 6.10/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : MBMS context activation procedure | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.1.3.8.4 |
4,018 | 8.8.6.1 FDD | For the parameters specified in Table 8.8.6.1-1 the average probability of a missed downlink scheduling grant (Pm-dsg) shall be below the specified value in Table 8.8.6.1-2. The purpose of this test is to verify the distributed EPDCCH performance when the serving cell EPDCCH transmission is interfered by two interfering cells applying asynchronous TM3 interference model. In Table 8.8.6.1-1, Cell 1 is the serving cell, and Cell 2 and Cell 3 are the aggressor cells. The downlink physical setup is in accordance with Annex C.3.2 for each of Cell 1, Cell 2 and Cell 3, respectively. The CRS assistance information [7] is not provided. Table 8.8.6.1-1: Test Parameters for EPDCCH Table 8.8.6.1-2: Minimum performance for EPDCCH for enhanced downlink control channel performance requirements Type A | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.8.6.1 |
4,019 | 5.2.5.5 Reception of SIB1 | The Master Information Block (MIB) on PBCH provides the UE with parameters (e.g. CORESET#0 configuration) for monitoring of PDCCH for scheduling PDSCH that carries the System Information Block 1 (SIB1). PBCH may also indicate that there is no associated SIB1, in which case the UE may be pointed to another frequency from where to search for an SSB that is associated with a SIB1 as well as a frequency range where the UE may assume no SSB associated with SIB1 is present. The indicated frequency range is confined within a contiguous spectrum allocation of the same operator in which SSB is detected. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.2.5.5 |
4,020 | 5.8.2.2.2 Routing rules configuration | When the UE has an IPv6 multi-homed PDU Session the UE selects the source IPv6 prefix according to IPv6 multi-homed routing rules pre-configured in the UE or received from network. IPv6 multi-homed routing rules received from the network have a higher priority than IPv6 multi-homed routing rules pre-configured in the UE The SMF can generate the IPv6 multi-homed routing rules for a UE based on local configuration or dynamic PCC rules received from the PCF as defined in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. If dynamic PCC is deployed, the SMF generates the IPv6 multi-home routing rules for a source IPv6 prefix based on the SDF Templates of those PCC rules which contain the DNAI corresponding to the newly assigned IPv6 prefix. The SMF can send IPv6 multi-homed routing rules to the UE to influence the source IPv6 prefix selection in IPv6 Router Advertisement (RA) messages according to RFC 4191 [8] at any time during the lifetime of the IPv6 multi-homed PDU Session. Such messages are sent via the UPF. NOTE: For multiple IPv4 PDU Session and multiple IPv6 PDU Session cases, routing rule based PDU Session selection is 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") | 5.8.2.2.2 |
4,021 | 8.2.2.4.1D Enhanced Performance Requirement Type B - Single-layer Spatial Multiplexing 2 Tx Antenna Port with TM4 interference model | The requirements are specified in Table 8.2.2.4.1D-2, with the addition of the parameters in Table 8.2.2.4.1D-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 two interfering cells applying transmission mode 4 interference model defined in clause B.6.3. In Table 8.2.2.4.1D-1, Cell 1 is the serving cell, and Cell 2, 3 are interfering cells. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1, Cell 2 and Cell 3, respectively. Table 8.2.2.4.1D-1: Test Parameters for Single-layer Spatial Multiplexing (FRC) with TM4 interference model Table 8.2.2.4.1D-2: Minimum Performance for Enhanced Performance Requirement Type B, Single-layer Spatial Multiplexing (FRC) with TM4 interference model | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.2.2.4.1D |
4,022 | 10.5.6.2 Network service access point identifier | The purpose of the Network service access point identifier information element is to identify the service access point that is used for the GPRS data transfer at layer 3. The Network service access point identifier is a type 3 information element with a length of 2 octets. The value part of a Network service access point identifier information element is coded as shown in figure 10.5.153/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.167/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.153/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Network service access point identifier information element Table 10.5.167/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Network service access point 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.2 |
4,023 | 4.4.8.3 Architecture for AF requested support of Time Sensitive Communication and Time Synchronization | This clause describes the architecture to enable Time Sensitive Communication AF requested time sensitive communication and time synchronization services. The Time Sensitive Communication and Time Synchronization related features that are supported based on AF request are described in clauses 5.27.1 and 5.27.2, respectively. Figure 4.4.8.3-1 shows the architecture to support Time Sensitive Communication and Time Synchronization services. As shown in Figure 4.4.8.3-1, to support Time Synchronization service based on IEEE Std 802.1AS [104] or IEEE Std 1588 [126] for Ethernet or IP type PDU Sessions, the DS-TT, NW-TT and Time Sensitive Communication and Time Synchronization Function (TSCTSF) are required in order to support the features in IEEE Std 802.1AS [104] or IEEE Std 1588 [126] as described in clause 5.27. The NEF exposes 5GS capability to support Time Synchronization service as described in clause 5.27.1.8. TSCTSF controls the DS-TT(s) and NW-TT for the (g)PTP based time synchronization service. In addition, TSCTSF supports TSC assistance container related functionalities. Figure 4.4.8.3-1: Architecture to enable Time Sensitive Communication and Time Synchronization services NOTE 1: If the AF is considered to be trusted by the operator, the AF could interact directly with TSCTSF, the connection between AF and TSCTSF is not depicted in the architecture diagram for brevity. UPF/NW-TT distributes the (g)PTP messages as described in clause 5.27.1. When the UPF supports one or more NW-TT(s), there is one-to-one association between an NW-TT and the network instance or between an NW-TT and network instance together with DNN/S-NSSAI in the UPF. When there are multiple network instances within a UPF, each network instance is considered logically separate. The network instance for the N6 interface (clause 5.6.12) may be indicated by the SMF to the UPF for a given PDU Session during PDU Session establishment procedure. UPF allocates resources based on the Network Instance and S-NSSAI and it is supported according to TS 29.244[ Interface between the Control Plane and the User Plane nodes ] [65]. DNN/S-NSSAI may be indicated by the SMF together with the network instance to the UPF for a given PDU Session during PDU Session establishment procedure. NOTE 2: The same NW-TT is used for all PDU Sessions in the UPF for the given DNN/S-NSSAI; the NW-TT is unique per DNN/S-NSSAI. This ensures that the UPF selects an N4 session associated with the correct TSCTSF when the NW-TT initiates an UMIC or PMIC. At any given time, the NW-TT is associated with a single TSCTSF. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.4.8.3 |
4,024 | 10.5.5.14 GMM cause | The purpose of the GMM cause information element is to indicate the reason why a GMM request from the mobile station is rejected by the network. The GMM cause information element is coded as shown in figure 10.5.129/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.147/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The GMM cause is a type 3 information element with 2 octets length. Figure 10.5.129/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : GMM cause information element Table 10.5.147/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : GMM cause information element | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.5.14 |
4,025 | X.10 Security for AI/ML model storage and sharing | The detailed procedure for secured and authorized AI/ML model sharing between different vendors is depicted in Figure X.10-1: Figure X.10-1: Secured and authorized AI/ML model sharing between different vendors 0a. NF Service producer i.e. NWDAF containing MTLF registers its NF profile in the NRF with ML Model Interoperability indicator per Analytics ID as described in clause 5.2 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [105]. The ML Model Interoperability indicator is a list of NWDAF providers (vendors) that are allowed to retrieve ML models from this NWDAF containing MTLF. 0b. NF Service consumer e.g., NWDAF containing AnLF registers at the NRF including its Vendor ID, Editor's Note: The inclusion of Interoperability indicator of NFc and Vendor ID of NFc are needed for authorization is ffs. 0c. The model is stored in encrypted format unless both the AI/ML model producer (NWDAF MTLF) and storage platform (ADRF) are part of the same system and belong to the same vendor and operator security domain. Storage of the model in encrypted format can be required by the trust model established to store and share AI/ML models. The trust model between AI/ML NF producer (NWDAF MtLF), storage platform (ADRF) and NF consumer (e.g., AnLF) is to be determined during the implementation phase among operator and the providers of the different platforms (MTLF, AnLF, ADRF). How the model is encrypted is vendor specific. Key distribution is not specified in this document. 1. NWDAF containing MTLF triggers the Nadrf_MLModelManagement_StorageRequest as described in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [105], optionally including an allowed NFc list. The absence of allowed NFc list indicates that only the MTLF which stored the model is allowed to retrieve the model. 2. ADRF sends the response to NWDAF containing MTLF as described in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [105]. 3. NF Service consumer e.g., NWDAF containing AnLF performs Nnrf_NFDiscovery_Request operation with the requested Analytics ID to select a suitable NF Service Producer e.g., NWDAF containing MTLF. 4a. NF Service consumer e.g., NWDAF containing AnLF requests an access token from the NRF using the Nnrf_AccessToken_Get request operation. The token request message contains, besides the parameters described in clause 13.4.1.1.2, the Vendor ID of NWDAF containing AnLF and the Analytics ID. 4b. NRF checks whether the NWDAF containing AnLF is authorized to access the requested service in NWDAF containing MTLF and verifies that the NF Consumer's Vendor ID is included in the NWADF containing MTLF 's interoperability indicator for the Analytics ID and grants the token (token1), based on the vendor ID provided by the NF consumer during registration. 5. NF Service Consumer performs Nnwdaf_MLModelProvision (Analytics ID, Vendor ID and token1) service operation at the NWDAF containing MTLF to retrieve ML models for the Analytics ID. 6a. The NWDAF containing MTLF authenticates the NF Service Consumer and verifies the access token as specified in the clause 13.4.1.1.2 and ensures that the Analytics ID is included in the access token. If verification is successful, NWDAF containing MTLF determines the ML model to be shared for the requested Analytics ID and stored the NF instance ID of NWDAF containing AnLF as part of allowed NF instance list for the ML model. 6b. If the determined ML model is stored in ADRF, and if the NF Service Consumer is not yet in the allowed NFc list stored at the ADRF, the NWDAF containing MTLF triggers the update of Nadrf_MLModelManagement_StorageRequest at the ADRF, with NF ID of NWDAF containing MTLF and Model ID, adding the NF Service Consumer to the allowed NFc list. The ADRF verifies that the requesting NWDAF containing MTLF is same as the one that stored the model. Then, ADRF stores the allowed NF instance list for the ML model referenced by the Model ID. Editor's Note: New service operation Nadrf_MLModelManagement_StorageRequest Update needs to be defined by SA2. Editor's Note: How the MTLF and ADRF can identify which list of allowed NF consumers belongs to which model stored in the ADRF (e.g. by Storage Transaction ID) is ffs. 6c. ADRF sends the response to NWDAF containing MTLF which contains Model ID. Editor's Note: How the AnLF retrieve the model via MTLF should be align with SA2 and the diagram should be update accordingly. 7. NWDAF containing MTLF sends Nnwdaf_MLModelProvision Notify to the NF Service Consumer with Model ID, the address of the determined ML model, which can be either the one stored in NWDAF containing MTLF or in ADRF. If the model is stored in ADRF, this message may also contain ADRF ID. If the ML model is to be retrieved from ADRF, the following steps are applied: 8a. NF Service Consumer requests an access token from the NRF to be authorized to retrieve the model stored in ADRF as specified in clause 13.4.1. 8b. NRF verifies that the NF Service consumer e.g., NWDAF containing AnLF is authorized to access the service provided by the ADRF. If verification is successful, NRF grants the token (token2), based on the information provided in ADRF's NF profile. 9. NF Service consumer e.g., NWDAF containing AnLF requests to retrieve the target model by sending Nadrf_MLModelManagement_Retrieval Request as described in clause 10.3.4 TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [105], including token2. 10. ADRF authenticates the NF Service Consumer and verifies the access token (token2) as specified in the clause 13.4.1.1.2. ADRF verifies also the NF Service Consumerβs NF ID is included in the allowed NF instance list for the ML model and/or is same as the NF ID of the MTLF that stored the model. If verification is successful, ADRF sends Nadrf_MLModelManagement_Retrieval Response to the NF Service Consumer, which contains the address of the stored model in ADRF. 11. NF Service Consumer retrieves the ML model from ADRF and decrypts the model per the vendorβs implementation. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | X.10 |
4,026 | 4.5.4 UL Total PRB Usage | This measurement provides the total usage (in percentage) of physical resource blocks (PRBs) on the uplink for any purpose. If there is one or more RNs served in a cell, for that cell the eNodeB performs PRB usage measurements separately for all traffic (including transmissions to/from RNs and UEs directly connected to the eNodeB) and for RN traffic. The measurement is also applicable to RNs. SI This measurement is obtained according to the definition in 3GPP TS 36.314[ Evolved Universal Terrestrial Radio Access (E-UTRA); Layer 2 - Measurements ] [11]. A single integer value from 0 to 100. RRU.PrbTotUl, which indicats the UL PRB Usage for all traffic RRU.PrbTotUlRN, which indicates the UL PRB Usage for the RN traffic EUtranCellFDD EUtranCellTDD Valid for packet switched traffic EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.5.4 |
4,027 | 4.3.3 Converged charging functions 4.3.3.0 General | Figure 4.3.3.0.1 provides an overview of converged charging architecture. The figure 4.3.3.0.1 depicts the logical charging functions in the network and interface between these functions and to the BD. This charging architecture is used for 5G system. CTF: Charging Trigger Function CHF: CHarging Function ABMF: Account Balance Management Function RF: Rating Function CGF: Charging Gateway Function BD: Billing Domain. This may also be a billing system/ billing mediation device. Figure 4.3.3.0.1: Logical ubiquitous converged charging architecture | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.3.3 |
4,028 | 6.7.3.1 Xn-handover | At handover from a source gNB/ng-eNB over Xn to a target gNB/ng-eNB, the source gNB/ng-eNB shall include the UE's 5G security capabilities and ciphering and integrity algorithms used in the source cell in the handover request message. The target gNB/ng-eNB shall select the algorithm with highest priority from the received 5G security capabilities of the UE according to the prioritized locally configured list of algorithms (this applies for both integrity and ciphering algorithms). The chosen algorithms shall be indicated to the UE in the Handover Command message if the target gNB/ng-eNB selects different algorithms compared to the source gNB/ng-eNB. If the UE does not receive any selection of integrity and ciphering algorithms, it continues to use the same algorithms as before the handover (see TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [22] for gNB or TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [69] for ng-eNB). When a Xn-handover takes place from ng-eNB to gNB or vice versa, then the selected algorithms in the target node shall always be signalled in the Handover Command to the UE. In the Path-Switch message, the target gNB/ng-eNB shall send the UE's 5G security capabilities received from the source gNB/ng-eNB to the AMF. The AMF shall verify that the UE's 5G security capabilities received from the target gNB/ng-eNB are the same as the UE's 5G security capabilities that the AMF has locally stored. If there is a mismatch, the AMF shall send its locally stored 5G security capabilities of the UE to the target gNB/ng-eNB in the Path-Switch Acknowledge message. The AMF shall support logging capabilities for this event and may take additional measures, such as raising an alarm. If the target gNB/ng-eNB receives UE's 5G security capabilities from the AMF in the Path-Switch Acknowledge message, the target gNB/ng-eNB shall update the AS security context of the UE with these 5G security capabilities of the UE. The target gNB/ng-eNB shall select the algorithm with highest priority from these 5G security capabilities according to the locally configured prioritized list of algorithms (this applies for both integrity and ciphering algorithms). If the algorithms selected by the target gNB/ng-eNB are different from the algorithms used at the source gNB/ng-eNB, then the target gNB/ng-eNB shall initiate intra-cell handover procedure which includes RRC Connection Reconfiguration procedure indicating the selected algorithms and an NCC to the UE. NOTE: Transferring the ciphering and integrity algorithms used in the source cell to the target gNB/ng-eNB in the handover request message allows for the target gNB/ng-eNB to decipher and verify the integrity of the RRC Reestablishment Complete message on SRB1 in the potential RRC Connection Re-establishment procedure. The information is also used by the target gNB/ng-eNB to decide if it is necessary to include a new selection of security algorithms in the Handover Command message. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.7.3.1 |
4,029 | 5.37.3.3 Support of ECN marking for L4S in PSA UPF | To enable ECN marking for L4S by a PSA UPF, a QoS Flow level ECN marking for L4S indicator may be sent by SMF to PSA UPF over N4. SMF also indicates to NG-RAN to report the congestion information (i.e. a percentage of packets that UPF uses for ECN marking for L4S) of the QoS Flow on UL and/or DL directions via GTP-U header extension to PSA UPF. If there is no UL packet when report for DL and/or UL needs to be provided, NG-RAN may generate an UL Dummy GTP-U Packet for such a reporting. The SMF may be instructed, based on either dynamic or predefined PCC rule, to provide an indication for ECN marking for L4S to PSA UPF for a corresponding QoS Flow(s) in UL and/or DL directions. Upon successful activation of congestion information reporting for UL and/or DL directions, PSA UPF uses information sent by NG-RAN in GTP-U header extension (see TS 38.415[ NG-RAN; PDU session user plane protocol ] [116] and TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27]) to perform ECN bits marking for L4S for the corresponding direction. NOTE: How the congestion information is converted to ECN markings is UPF implementation specific. The criteria based on which NG-RAN decides to provide the congestion information is up to NG-RAN implementation. In the case of PSA UPF relocation, if the ECN marking for L4S has been enabled on source PSA UPF, SMF should select a target PSA UPF supporting ECN marking for L4S. If the target PSA UPF does not support ECN marking for L4S, then SMF may, if supported, switch to ECN marking for L4S in target NG-RAN by following clause 5.37.3.2. In such case, the target NG-RAN stops sending congestion information to the target PSA UPF. In the case of inter NG-RAN UE mobility, if the congestion information reporting has been enabled on source NG-RAN while the target NG-RAN does not support congestion information reporting, then the SMF shall inform PSA UPF to stop ECN marking for L4S. If ECN marking for L4S is supported by the target NG-RAN, the SMF may instruct the target NG-RAN to perform ECN marking for L4S in NG-RAN by following clause 5.37.3.2. For a given QoS Flow, if the target NG-RAN supports congestion information reporting, the target NG-RAN shall report congestion information to UPF once it is available. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.37.3.3 |
4,030 | 6.2 5G LAN-type service charging 6.2.1 General | The 5G LAN-type service charging specified in the clause 5.34.10 of TS 23.501[ System architecture for the 5G System (5GS) ] [215], including the 5G VN group management and 5G VN group communication. The 5G VN group configuration is either provided by OA&M or provided by an AF to the NEF. The 5G VN group management charging is applicable for the 5G VN group addition/deletion/modification (i.e.5G VN members), including the following two optional architecture specified in TS 32.254[ Telecommunication management; Charging management; Exposure function Northbound Application Program Interfaces (APIs) charging ] [14]. which optional charging architecture to be used is depended on the operatorβs decision. - CEF based charging: obtains the 5G VN group information from UDM by CEF, and reports to CHF. - NEF based charging: reports the 5G VN group charging information by NEF based on the API invocation from AF. NEF exposure function Northbound Application Program Interfaces (APIs) charging, using the NEF embedding the CTF. The 5G VN group communication includes one to one communication and one to many communications. The 5G VN group communication charging is applicable for traffic forwarding via PDU session of 5G VN group members which covered by 5G data connectivity domain converged charging architecture specified in TS 32.255[ Telecommunication management; Charging management; 5G data connectivity domain charging; Stage 2 ] [15], using the SMF embedding the CTF. | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 6.2 |
4,031 | 14.7.3 Alternative Format of W-APN Operator Identifier | For situations when the PDG serving the W-APN is located in such network that is not part of the GRX (i.e. the Interoperator IP backbone), the default Operator Identifier described in clause 14.7.2 is not available for use. This restriction originates from the ".3gppnetwork.org" domain, which is only available in GRX DNS for actual use. Thus an alternative format of W-APN Operator Identifier is required for this case. The Alternative W-APN Operator Identifiers shall be constructed as follows: "w-apn.<valid operator's REALM>" where: <valid operator's REALM> corresponds to REALM names owned by the operator hosting the PDG serving the desired W-APN. REALM names are required to be unique, and are piggybacked on the administration of the Public Internet DNS namespace. REALM names may also belong to the operator of the VPLMN. As an example, the W-APN OI for the Operator REALM "notareal.com" is coded in the Public Internet DNS as: "w-apn.notareal.com". | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 14.7.3 |
4,032 | 4.12.4.2 Procedure for the UE context release in the N3IWF | This procedure is used to release the N2 signalling connection and the N3 User Plane connection. If the procedure is initiated by the AMF the IKEv2 SA for a UE is being released. The procedure will move the UE from CM-CONNECTED to CM-IDLE in AMF and all UE related context information is deleted in the N3IWF. Both N3IWF-initiated and AMF-initiated UE context release in the N3IWF procedures are shown in Figure 4.12.4.2-1. Figure 4.12.4.2-1: Procedure for the UE context release in the N3IWF 1. The UE has already registered in the 5GC and may have established one or multiple PDU Sessions. 2. The N3IWF detects that the UE is not reachable. 3. The N3IWF sends a N2 UE Context Release Request message to the AMF This step is equivalent to step 1b of Figure 4.2.6-1. NOTE: AN Release procedure can also be triggered by an AMF internal event and in that case step 2 and step 3 do not take place. 4. AMF to N3IWF: If the AMF receives the N2 UE Context Release Request from N3IWF or if due to an internal AMF event the AMF wants to release N2 signalling, the AMF sends an N2 UE Context Release Command (Cause) to the N3IWF. The cause indicated is cause from step 3 or a cause due to internal AMF event. This step is equivalent to step 2 of Figure 4.2.6-1. 5. If the IKEv2 tunnel has not been released yet, the N3IWF performs the release of the IPsec tunnel as defined in RFC 7296 [3] indicating to release the IKE SA and any Child IPSec SA if existing. The N3IWF sends to the UE the indication of the release reason if received in step 4. 6. The UE sends an empty INFORMATIONAL Response message to acknowledge the release of the IKE SA as described in RFC 7296 [3]. The N3IWF deletes the UE's context after receiving the empty INFORMATIONAL Response message. 7. N3IWF to AMF: The N3IWF confirms the release of the UE-associated N2-logical connection by returning N2 UE Release Complete (list of PDU Session ID(s) with active N3 user plane) to the AMF as in step 4 defined in clause 4.2.6. The AMF marks the UE as CM-IDLE state in untrusted non-3GPP access. 8. For each of the PDU Sessions in the N2 UE Context Release Complete, the steps 5 to 7 in clause 4.2.6 are performed (PDU Session Update SM Context). After the AMF receives the Nsmf_PDUSession_UpdateSMContext Response as in step 7 of clause 4.2.6, the AMF considers the N3 connection as released. If list of PDU Session ID(s) with active N3 user plane is included in step 3, then this step is performed before step 4. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.12.4.2 |
4,033 | 5.19.2 Attach, TAU and RAU procedure for Dedicated Core Network | When DCNs are used, the Attach, TAU and RAU procedures in this clause apply. Figure 5.19.2-1: Attach,TAU and RAU procedure for Dedicated Core Network 1. Attach, TAU, or RAU procedure is initiated as specified in the relevant clauses of this specification and TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7]. The relevant steps of the procedure as specified in the figure above are executed. The following modifications apply: - In the RRC Connection Complete message transferring the NAS Request message, the UE provides the DCN-ID, if available. If the UE has a PLMN specific DCN-ID the UE shall provide this value and if no PLMN specific DCN-ID exist the pre-provisioned default standardized DCN-ID shall be provided, if pre-provisioned in the UE. The RAN node selects a DCN and a serving MME/SGSN within the network of the selected core network operator based on the DCN-ID and configuration in the RAN node. The NAS Request message is sent to the selected node. The DCN-ID is provided by the RAN to the MME/SGSN together with the NAS Request message. - E-UTRAN Initial Attach Procedure (clause 5.3.2.1 (Figure 5.3.2.1-1)) and Combined GPRS/IMSI Attach procedure (TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7] clause 6.5.3 (Figure 22)): In the Identification Response message, the old MME/SGSN provides UE Usage Type parameter, if available. - Tracking area update procedure (clause 5.3.3.1 (Figure 5.3.3.1-1) and 5.3.3.2 (Figure 5.3.3.2-1)): In the Context Response message, the old MME/SGSN provides UE Usage Type parameter, if available. - Routing area update procedure (clause 5.3.3.3 (Figure 5.3.3.3-1) and 5.3.3.6 (Figure 5.3.3.6-1), TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7] clauses 6.9.1.2.2 (Figure 33), 6.9.1.2.2a (Figure 33a), 6.9.1.3.2 (Figure 35), 6.9.2.1 (Figure 36), 6.9.2.1a (Figure 36a), 6.13.1.1.1 (Figure 52), 6.13.2.1.1 (Figure 54), 6.13.2.1.2 (Figure 54-2), 6.13.2.2.1 (Figure 55), 6.13.2.2.2 (Figure 55-2)): In the Context Response message, the old MME/SGSN provides UE Usage Type parameter, if available. 2. If the (first) new MME/SGSN, i.e. the MME/SGSN that has not received any MMEGI or Null-NRI/SGSN Group ID from RAN, does not have sufficient information to determine whether it should serve the UE, it sends an Authentication Information Request message to the HSS requesting UE Usage Type by adding the parameter "Send UE Usage Type" flag in the message. The MME/SGSN may also request one or more authentication vectors in addition to the UE Usage Type. The (first) new MME/SGSN has sufficient information in the following cases and may then skip this step and step 3: i. The (first) new MME/SGSN has received the UE Usage Type from the old MME/SGSN in the Identification Response (for Attach) or Context Response (for TAU/RAU) message or Forward Relocation Request (for Handover). ii. Based on configuration in the (first) new MME/SGSN and UE context information, the MME/SGSN is able to determine whether it should serve the UE. This step and redirection of NAS message (i.e. step 5 onwards) shall not be performed for TAU/RAU procedure triggered in connected mode, e.g. during handover. 3. The HSS, if supporting DCNs, provides the UE Usage Type in the Authentication Information Answer message, if any is stored for the UE. The UE Usage Type is returned by the HSS in addition to requested authentication vectors. 4. If the (first) new MME/SGSN determines that it shall not reroute the NAS message to another CN node, the MME/SGSN either continues from the designated step as stated in the figure above or depending on operator configuration rejects the NAS request message and the NAS procedure ends in this step. The NAS message is rejected with parameters, e.g. backoff timer, such that the UE does not immediately re-initiate the NAS procedure. The MME/SGSN sends the DCN-ID, if available, for the DCN to the UE in the NAS Accept message. The UE updates its stored DCN-ID parameter for the serving PLMN if DCN-ID for serving PLMN is changed. 5. If the (first) new MME/SGSN determines that it should reroute the NAS request message to another CN node, the procedure is a TAU or RAU procedure and UE context was received from the old MME/SGSN, the (first) new MME sends a Context Acknowledge message with cause code indicating that the procedure is not successful. The old MME/SGSN shall continue as if Context Request was never received. 6. If the (first) new MME/SGSN determines that it should reroute the NAS request message to another CN node, it uses the "NAS Message Redirection Procedure" in clause 5.19.1. The NAS message is re-routed to a (second) new MME/SGSN. If the IMSI was retrieved unencrypted from the UE by the (first) new MME/SGSN in step 1, the (first) new MME/SGSN shall include the IMSI in the Reroute Message Request. 7. The (second) new MME/SGSN, i.e. the MME/SGSN that receives the rerouted NAS message from RAN with MMEGI or Null-NRI/SGSN Group ID, performs NAS procedure as stated for E-UTRAN in this specification and for GERAN/UTRAN in TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7] from the steps shown in the figure above. The following modifications apply: - E-UTRAN Initial Attach Procedure (clause 5.3.2.1 (Figure 5.3.2.1-1)) and Combined GPRS/IMSI Attach procedure (TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7] Clause 6.5.3 (Figure 22)): In the Identification Response message, the old MME/SGSN provides UE Usage Type parameter, if available. - Tracking area update procedure (clause 5.3.3.1 (Figure 5.3.3.1-1) and 5.3.3.2 (Figure 5.3.3.2-1)): In the Context Response message, the old MME/SGSN provides UE Usage Type parameter, if available. - If the IMSI was received from the first (new) MME/SGSN as part of the NAS Message Redirection Procedure, the second (new) MME/SGSN does not have to retrieve the IMSI from the UE. - Routing area update procedure (clause 5.3.3.3 (Figure 5.3.3.3-1) and 5.3.3.6 (Figure 5.3.3.6-1), TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7] clauses 6.9.1.2.2 (Figure 33), 6.9.1.2.2a (Figure 33a), 6.9.1.3.2 (Figure 35), 6.9.2.1 (Figure 36), 6.9.2.1a (Figure 36a), 6.13.1.1.1 (Figure 52), 6.13.2.1.1 (Figure 54), 6.13.2.1.2 (Figure 54-2), 6.13.2.2.1 (Figure 55), 6.13.2.2.2 (Figure 55-2)): In the Context Response message, the old MME/SGSN provides UE Usage Type parameter, if available. - The MME/SGSN sends the DCN-ID, if available, for the new DCN to the UE in the NAS Accept message. The UE updates its stored DCN-ID parameter for the serving PLMN if DCN-ID for serving PLMN is changed. If network sharing and the Selected PLMN information is not provided by the UE, the SGSN may also include the PLMN ID of selected CN operator in the NAS Accept message. The (second) new MME/SGSN shall not reroute the NAS message to another CN node since the Initial UE message/UL-Unitdata message from RAN includes MMEGI or Null-NRI/SGSN Group ID. The (second) new MME/SGSN either completes the NAS procedure as stated above or depending on operator configuration rejects the NAS request message and the NAS procedure ends. When rejecting the NAS request, an appropriate cause and backoff time should be included. In the case of TAU or RAU procedure, the (second) new MME/SGSN may check (e.g. based on the indication that the NAS message has been rerouted and on local configuration) if the PDN GW (for one or more PDN connection(s)) of the UE needs to be changed. If the PDN GW needs to be changed, the (second) new MME/SGSN initiates Detach with reattach required or PDN disconnection with reactivation required procedure after the completion of the TAU or RAU procedure. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.19.2 |
4,034 | 4.3.1.1 NG User Plane | The NG user plane interface (NG-U) is defined between the NG-RAN node and the UPF. The user plane protocol stack of the NG interface is shown on Figure 4.3.1.1-1. The transport network layer is built on IP transport and GTP-U is used on top of UDP/IP to carry the user plane PDUs between the NG-RAN node and the UPF. Figure 4.3.1.1-1: NG-U Protocol Stack NG-U provides non-guaranteed delivery of user plane PDUs between the NG-RAN node and the UPF. Further details of NG-U can be found in TS 38.410[ NG-RAN; NG general aspects and principles ] [16]. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 4.3.1.1 |
4,035 | 4.2.2.1 Number of E-RABs requested to release initiated by eNodeB/RN per QCI | This measurement provides the number of E-RABs requested to release initiated by eNodeB/RN. The measurement is split into subcounters per E-RAB QoS level (QCI). CC On transmission by the eNodeB/RN of an E-RAB RELEASE INDICATION, or an UE CONTEXT RELEASE REQUEST, or a RESET message to MME or DeNB( in case of RN), each corresponding E-RAB requested to release is added to the relevant measurement per QCI, the possible QCIs are included in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [9]. The sum of all supported per QCI measurements shall equal the total number of E-RABs requested to release initiated by eNodeB/RN. In case only a subset of per QCI measurements is supported, a sum subcounter will be provided first. Each measurement is an integer value. The number of measurements is equal to the number of QCIs plus a possible sum value identified by the .sum suffix. The measurement name has the form ERAB.RelEnbNbr.QCI where QCI identifies the E-RAB level quality of service class. EUtranCellFDD EUtranCellTDD Valid for packet switched traffic EPS 4.2.2.2 Number of E-RABs requested to release initiated by eNodeB/RN per cause This measurement provides the number of E-RABs requested to release initiated by eNodeB/RN. The measurement is split into subcounters per cause. CC On transmission by the eNodeB/RN of an E-RAB RELEASE INDICATION, or an UE CONTEXT RELEASE REQUEST, or a RESET message to MME or DeNB( in case of RN), each corresponding E-RAB requested to release is added to the relevant measurement per cause. Possible causes are included in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [9]. Each measurement is an integer value. The number of measurements is equal to the number of supported causes. The measurement names have the form ERAB.RelEnbNbr.cause where cause identifies the reason for the E-RABs release request initiated by eNodeB/RN. EUtranCellFDD EUtranCellTDD Valid for packet switched traffic EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.2.2.1 |
4,036 | 4.17.12.4 Binding for subscription requests | Binding for notifications can be created as part of an explicit or implicit subscription request. In this case, illustrated in Figure 4.17.12.4-1, the subscription request may include a Binding Indication 1 referring to NF service instance, NF service Set, NF instance or NF Set and additionally includes a service name of the NF service consumer as specified in Table 6.3.1.0-1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The NF Service Set ID, NF service instance ID and service name relate to the service of a NF service consumer that will handle the notification. For direct communication, the NF service producer selects the target for the related notifications using the notification endpoint received in the subscription request. If the notification endpoint included in the subscription is not reachable, the Binding Indication received is used to discover an alternative notification endpoint, as specified in Table 6.3.1.0-1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. For indirect communication, the NF service producer includes the notification endpoint received in the subscription and may include a Routing Binding Indication with the same contents as the received Binding Indication. If the notification endpoint included in the subscription is not reachable, the SCP selects the target for the related notifications using the received Routing Binding Indication as specified in Table 6.3.1.0-1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the Binding Indication for Notifications needs to be updated, the NF service consumer may initiate a new Subscription request to the NF service producer with an updated Binding Indication or may include the Binding Indication in the acknowledgment of a Notification. A Subscription request may also contain updated Notification Correlation ID and Notification Target Address. Binding for the subscription resource at the NF service producer can also be created: The Subscription Response message may contain a Binding Indication 2 referring to NF service instance, NF instance or NF Set of the NF service producer. For direct communication, the NF service consumer selects the target for the related request to the producer, such as the request to update the subscription shown in Figure 4.17.12.4-1, using the received Binding Indication 2 as specified in Table 6.3.1.0-1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. For indirect communication with delegated discovery, the NF service consumer includes a Routing Binding Indication with the same contents as the received Binding Indication 2. For indirect communication without delegated discovery, the NF service consumer also includes the Routing Binding Indication with the same contents as the received Binding Indication 2 unless it performs a reselection. The SCP selects the target for the related request using the received Routing Binding Indication 2 as specified in Table 6.3.1.0-1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the Binding Indication for Subscription needs to be updated, the NF service producer may provide an updated binding indication in a notification request to the NF service consumer or in the response to a subsequent subscription update request from the NF service consumer. Figure 4.17.12.4-1: Binding in a subscription request Figure 4.17.12.4-2: Binding during subscription via another network function An NF service consumer may subscribe via another network function. For example, NF_A may subscribe to NF_B on behalf of NF_C. NF_A additionally subscribe to subscription related events. In this case, both the binding indication from NF_C and NF_A are provided to the NF service producer NF_B. The Binding Indication for notifications to subscription related events shall be associated with an applicability indicating "subscription events". The NF_C's binding indication is used for reselection of a notification endpoint, which is used for event notification. The NF_A's binding indication is used for reselection of a notification endpoint, which is used for subscription change event notification. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.17.12.4 |
4,037 | 6.5.4.4 UE requested bearer resource modification procedure not accepted by the network 6.5.4.4.1 General | If the bearer resource modification requested cannot be accepted by the network, the MME shall send a BEARER RESOURCE MODIFICATION REJECT message to the UE. The message shall contain the PTI and an ESM cause value indicating the reason for rejecting the UE requested bearer resource modification. The ESM cause value typically indicates one of the following: #26: insufficient resources; #30: request rejected by Serving GW or PDN GW; #31: request rejected, unspecified; #32: service option not supported; #33: requested service option not subscribed; #34: service option temporarily out of order; #35: PTI already in use; #37: EPS QoS not accepted; #41: semantic error in the TFT operation; #42: syntactical error in the TFT operation; #43: invalid EPS bearer identity; #44: semantic error(s) in packet filter(s); #45: syntactical error(s) in packet filter(s); #56: collision with network initiated request; #59: unsupported QCI value; #60: bearer handling not supported; or #95 β 111: protocol errors. If the bearer resource modification requested is for an established LIPA PDN connection or SIPTO at the local network PDN connection, then the network shall reply with a BEARER RESOURCE MODIFICATION REJECT message with ESM cause #60 "bearer handling not supported". If the requested new TFT is not available, then the BEARER RESOURCE MODIFICATION REJECT message shall be sent. The TFT in the request message is checked by the network for different types of TFT IE errors as follows: a) Semantic errors in TFT operations: 1) When the TFT operation is an operation other than "Replace packet filters in existing TFT", "Add packet filters to existing TFT", "Delete packet filters from existing TFT" or "No TFT operation". 2) When the TFT operation is "Replace packet filters in existing TFT", "Add packet filters to existing TFT" or "Delete packet filters from existing TFT", the EPS bearer context being modified is the default EPS bearer content and there is no TFT for the default EPS bearer context. 3) TFT operation = "Delete packet filters from existing TFT" when it would render the TFT empty. In case 1 the network shall reject the modification request with ESM cause #41 "semantic error in the TFT operation". In case 2, if the TFT operation is "Delete packet filters from existing TFT", the network shall further process the new request and, if no error according to items b, c, and d was detected, shall perform an EPS bearer context modification procedure including the value of EPS bearer identity for packet filter IE in the EPS bearer identity IE and a TFT IE with TFT operation = "Delete existing TFT" in the MODIFY EPS BEARER CONTEXT REQUEST message. In case 2, if the TFT operation is "Replace packet filters in existing TFT" or "Add packet filters to existing TFT", the network shall process the new request as a request with TFT operation = "Create a new TFT". In case 3, if the packet filters belong to a dedicated EPS bearer context, the network shall process the new deletion request and, if no error according to items b, c, and d was detected, delete the existing TFT. After successful deletion of the TFT, the network shall perform an EPS bearer context deactivation request procedure to deactivate the dedicated EPS bearer context between the UE and the network. In case 3, if the packet filters belong to the default EPS bearer context, the network shall process the new deletion request and if no error according to items b, c, and d was detected then perform an EPS bearer context modification procedure to remove the existing TFT of the default EPS bearer context, this corresponds to using match-all packet filter for the default EPS bearer context. b) Syntactical errors in TFT operations: 1) When the TFT operation = "Replace packet filters in existing TFT", "Add packet filters to existing TFT" or "Delete packet filters from existing TFT", and the packet filter list in the TFT IE is empty. 2) TFT operation = "No TFT operation" with a non-empty packet filter list in the TFT IE. 3) TFT operation = "Replace packet filters in existing TFT" when the packet filter to be replaced does not exist in the original TFT. 4) TFT operation = "Delete packet filters from existing TFT" when the packet filter to be deleted does not exist in the original TFT. 5) Void 6) When there are other types of syntactical errors in the coding of the TFT IE, such as a mismatch between the number of packet filters subfield, and the number of packet filters in the packet filter list. 7) TFT operation = "No TFT operation" with an empty parameters list. In case 3 the network shall not diagnose an error, shall further process the replace request and, if no error according to items c and d was detected, shall perform an EPS bearer context modification procedure using TFT operation = "Add packet filters to existing TFT" to include the packet filters received to the existing TFT. In case 4 the network shall not diagnose an error, shall further process the deletion request and, if no error according to items c and d was detected, shall perform an EPS bearer context modification procedure including the value of EPS bearer identity for packet filter IE in the EPS bearer identity IE and a TFT IE with TFT operation = "Delete packet filters from existing TFT" and the received packet filter identifier(s) in the MODIFY EPS BEARER CONTEXT REQUEST message. Otherwise the network shall reject the modification request with ESM cause #42 "syntactical error in the TFT operation". NOTE: An implementation that strictly follows packet filter list as defined in subclause 10.5.6.12 in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] might not detect case 2). c) Semantic errors in packet filters: 1) When a packet filter consists of conflicting packet filter components which would render the packet filter ineffective, i.e. no IP packet will ever fit this packet filter. How the network determines a semantic error in a packet filter is outside the scope of the present document. 2) When the resulting TFT, which is assigned to a dedicated EPS bearer context, does not contain any packet filter applicable for the uplink direction. The network shall reject the modification request with ESM cause #44 "semantic errors in packet filter(s)". d) Syntactical errors in packet filters: 1) When the TFT operation = "Replace packet filters in existing TFT" or "Add packet filters to existing TFT", and two or more packet filters in the resultant TFT would have identical packet filter identifiers. 2) When the TFT operation = "Replace packet filters in existing TFT" or "Add packet filters to existing TFT", and two or more packet filters in all TFTs associated with the PDN connection would have identical packet filter precedence values. 3) When there are other types of syntactical errors in the coding of packet filters, such as the use of a reserved value for a packet filter component identifier. In case 2, if the old packet filters do not belong to the default EPS bearer context, the network shall not diagnose an error, shall further process the new request and, if it was processed successfully, shall delete the old packet filters which have identical filter precedence values. Furthermore, the network shall perform an EPS bearer context deactivation procedure to deactivate the dedicated EPS bearer context(s) for which it has deleted the packet filters. In case 2, if one or more old packet filters belong to the default EPS bearer context, the network shall release the relevant PDN connection using the EPS bearer context deactivation procedure. If the relevant PDN connection is the last one and EMM-REGISTERED without PDN connection is not supported by the UE or the MME, the network shall detach the UE using detach type "re-attach required". Otherwise the network shall reject the modification request with ESM cause #45 "syntactical errors in packet filter(s)". The network may include a Back-off timer value IE in the BEARER RESOURCE MODIFICATION REJECT message. The network shall not include the ESM cause value #26 "insufficient resources" in the BEARER RESOURCE MODIFICATION REJECT message due to APN based congestion control being active. If the Back-off timer value IE is included and the ESM cause value is not #26 "insufficient resources", the network may include the Re-attempt indicator IE to indicate: - whether the UE is allowed to attempt a PDP context modification procedure in the PLMN for the same in A/Gb or Iu mode or a PDU session modification procedure in the PLMN for the same APN in N1 mode; and - whether another attempt in A/Gb and Iu mode, in S1 mode or in N1 mode is allowed in an equivalent PLMN. Upon receipt of a BEARER RESOURCE MODIFICATION REJECT message, the UE shall stop the timer T3481, release the traffic flow aggregate description associated to the PTI value, and enter the state PROCEDURE TRANSACTION INACTIVE. If the ESM cause included in the BEARER RESOURCE MODIFICATION REJECT message is #43 "invalid EPS bearer identity", the UE locally deactivates the EPS bearer context(s) without peer-to-peer ESM signalling. | 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.4.4 |
4,038 | 5.4.1.2 EAP based primary authentication and key agreement procedure 5.4.1.2.1 General | The purpose of the EAP based primary authentication and key agreement procedure is to provide mutual authentication between the UE and the network and to agree on the keys KAUSF, KSEAF and KAMF (see 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]). Extensible authentication protocol (EAP) as specified in IETF RFC 3748 [34] enables authentication using various EAP methods. EAP defines four types of EAP messages: a) an EAP-request message; b) an EAP-response message; c) an EAP-success message; and d) an EAP-failure message. Several rounds of exchanges of an EAP-request message and a related EAP-response message can be required to achieve the authentication (see example in figure 5.4.1.2.1.1). The EAP based primary authentication and key agreement procedure is always initiated and controlled by the network. The EAP-request message, the ngKSI and the ABBA are transported from the network to the UE using the AUTHENTICATION REQUEST message of the EAP message reliable transport procedure. The EAP-response message is transported from the UE to the network using the AUTHENTICATION RESPONSE message of the EAP message reliable transport procedure. If the authentication of the UE completes successfully, the serving AMF intends to initiate a security mode control procedure after the EAP based primary authentication and key agreement procedure and the security mode control procedure intends to bring into use the partial native 5G NAS security context created by the EAP based primary authentication and key agreement procedure, then the EAP-success message and the ngKSI are transported from the network to the UE using the SECURITY MODE COMMAND message of the security mode control procedure (see subclause 5.4.2). If the authentication of the UE completes successfully and the serving AMF does not intend to initiate a security mode control procedure bringing into use the partial native 5G NAS security context created by the EAP based primary authentication and key agreement procedure, then the EAP-success message, and the ngKSI are transported from the network to the UE using the AUTHENTICATION RESULT message of the EAP result message transport procedure. NOTE 1: The serving AMF will not initiate a security mode control procedure after the EAP based primary authentication and key agreement procedure e.g. in case of AMF relocation during registration procedure. If the authentication of the UE completes unsuccessfully, the EAP-failure message is transported from the network to the UE using the AUTHENTICATION RESULT message or the AUTHENTICATION REJECT message of the EAP result message transport procedure or in a response of the initial 5GMM procedure as part of which the EAP based primary authentication and key agreement procedure is performed. The AMF shall set the authenticator retransmission timer specified in IETF RFC 3748 [34] subclause 4.3 to infinite value. NOTE 2: The EAP message reliable transport procedure provides a reliable transport of EAP messages and therefore retransmissions at the EAP layer do not occur. The AUSF and the AMF support exchange of EAP messages using N12. The UE shall detect and handle any duplication of EAP message as specified in IETF RFC 3748 [34]. Figure 5.4.1.2.1.1: EAP based primary authentication and key agreement procedure | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.4.1.2 |
4,039 | 5.2.3.2.1 Recall Alignment Procedure | The recall alignment procedure consists of three parts: - basic service group alignment, - facility alignment, and - stream identifier alignment. Basic service group alignment: The mobile station shall check that the Bearer Capability, HLC and LLC and Repeat Indicator fields, which are embedded in the Setup Container IE, match a basic service group supported by the mobile station. If this check fails, then the recall alignment procedure has failed. The mobile station shall use the cause #88 "incompatible destination" afterwards. Otherwise, the mobile station is allowed to alter the content within the Bearer Capability, HLC and LLC Information Elements (e.g. the speech codec version(s), the data rate, the radio channel requirement) provided that the basic service group is not changed. Furthermore, for speech calls the mobile station is allowed to add or remove the Supported Codec List Information Element, or to alter the contents of this information element dependent on the codecs supported by the mobile station. The result shall be that the mobile station has derived Bearer Capability, HLC, LLC, and Supported Codec List Information Elements, which it can use for a later call setup according to its configuration and capabilities. Facility alignment: This only applies if the Setup Container contains 1 or more Facility IEs. Each Facility IE within the Setup Container will be associated with the common SS Version IE, if present. The handling for each Facility IE is defined below. The mobile station shall align each facility IE contained in the Setup Container. The rules defined in 3GPP TS 24.010[ Mobile radio interface layer 3; Supplementary services specification; General aspects ] [21] also apply. The Facility IE is encoded as 'simple recall alignment', 'advanced recall alignment' or 'recall alignment not essential' (see 3GPP TS 24.010[ Mobile radio interface layer 3; Supplementary services specification; General aspects ] [21]). If the encoding indicates, that - a simple recall alignment is required, the mobile station shall copy the Facility IE and the common SS version IE from the Setup Container to the SETUP message without modifying the content. - an advanced recall alignment is required, the mobile station must recognise and support the operation defined in the facility. If the mobile station does not recognise or support the operation, then the recall alignment procedure has failed and the mobile station shall use the cause #29 "facility rejected" in the subsequent rejection of the CC establishment request. - the recall alignment is not essential, then the facility operation is not an essential part of the SETUP. If the MS does not recognise the operation then the SS Version IE and Facility IE are discarded, and NOT copied into the SETUP message. NOTE: A mobile station may include a Facility IE without an associated SS Version IE. This would indicate that the SS operation is encoded using Phase 1 protocols. Further details on Facility handling are given in 3GPP TS 24.010[ Mobile radio interface layer 3; Supplementary services specification; General aspects ] [21]. Stream identifier alignment: The mobile station shall check whether the Stream Identifier field is contained in the Setup Container or not. If the Stream Identifier is contained in the Setup Container, the mobile station shall behave as one of the following. - the mobile station re-assign the Stream Identifier value, and modify the Stream Identifier field. - the mobile station remove the Stream Identifier field. If the Stream Identifier is not contained in the Setup Container, the mobile station may behave as follows. - the mobile station assign the Stream Identifier value, and add the Stream Identifier IE to the end of the SETUP message. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.2.3.2.1 |
4,040 | 5.5.2.1.2 Mapping to physical resources | For each antenna port used for transmission of the PUSCH, the sequence shall be multiplied with the amplitude scaling factor and mapped in sequence starting with to the resource blocks. - when either - the higher-layer parameter ul-DMRS-IFDMA is set and the most recent uplink-related DCI contains the Cyclic Shift Field mapping table for DMRS bit field which is set to 1 to indicate the use of Table 5.5.2.1.1-3, or - the Cyclic Shift Field mapping table for DMRS bit field is set to 1 in the most recent uplink-related DCI format 7 which indicates the use of Table 5.5.2.1.1-4, and - otherwise. If higher-layer parameter ul-DMRS-IFDMA is set and the most recent uplink-related DCI contains the Cyclic Shift Field mapping table for DMRS bit field which is set to 1 to indicate the use of Table 5.5.2.1.1-3, the mapping to resource elements , with for normal cyclic prefix and for extended cyclic prefix, in the subframe shall be in increasing order of first for all values of satisfying , then the slot number. The quantity is given by Table 5.5.2.1.1-3 using the cyclic shift field in the most recent uplink-related DCI. In case of slot-PUSCH, the mapping to resource elements , with for normal cyclic prefix, in the slot of the subframe where slot-PUSCH is transmitted shall be in increasing order of first for all values of , except if the Cyclic Shift Field mapping table for DMRS bit field is set to 1 in the most recent uplink-related DCI format 7, which indicates the use of Table 5.5.2.1.1-4. In this case the mapping to resource element shall be in increasing order of first only for values of satisfying . In case of subslot-PUSCH, the mapping to resource elements , in the subframe shall be in increasing order of first for all values of , except if the Cyclic Shift Field mapping table for DMRS bit field is set to 1 in the most recent uplink-related DCI format 7, which indicates the use of Table 5.5.2.1.1-4. In this case the mapping to resource element shall be in increasing order of first only for values of satisfying . The value of depends on the uplink subslot number and the DMRS-pattern field in the most recent uplink-related DCI, according to Table 5.5.2.1.2-1, or according to Table 5.5.2.1.2-2 in case of semi-persistent scheduling of subslot-PUSCH (i.e. higher layer patameter sps-ConfigUL-sTTI-r15 is configured, se TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [9]) and with a configured periodicity of 1 subslot (i.e. semiPersistSchedIntervalUL-STTI-r15 set to sTTI1). 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.5.2.1.2-2 (i.e. equivalent to a signalling of DMRS-pattern field set to '00'). In case no value of is defined for the uplink subslot number, and in case no valid starting symbol index (see table 5.3.4-1), no reference signal is transmitted associated with the uplink-related DCI format. Table 5.5.2.1.2-1: The quantity for subslot-PUSCH Table 5.5.2.1.2-2: The quantity for subslot-PUSCH for semi-persistent scheduling For all other cases, the set of physical resource blocks used in the mapping process and the relation between the index and the antenna port number shall be identical to the corresponding PUSCH transmission as defined in clause 5.3.4. The mapping to resource elements , with , or with according to Table 5.5.2.1.2-1 for subslot-PUSCH, for normal cyclic prefix and for extended cyclic prefix, in the subframe shall be in increasing order of first, then the slot number, except for slot-PUSCH and subslot-PUSCH where the reference signal is only mapped to the slot where the slot-PUSCH/subslot-PUSCH is transmitted). No DM-RS shall be transmitted in UpPTS if dmrsLess-UpPts is set to true. For BL/CE UEs, 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 demodulation reference signal transmission is postponed until the next BL/CE uplink subframe that is not fully reserved. - In a subframe that is partially reserved, the demodulation reference signal transmission in a SC-FDMA symbol that is reserved is dropped. | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.5.2.1.2 |
4,041 | 5.3.3 Physical uplink control channel | Physical uplink control channel (PUCCH) carries the Uplink Control Information (UCI) from the UE to the gNB. Five formats of PUCCH exist, depending on the duration of PUCCH and the UCI payload size: - Format #0: Short PUCCH of 1 or 2 symbols with small UCI payloads of up to two bits with UE multiplexing capacity of up to 6 UEs with 1-bit payload in the same PRB; - Format #1: Long PUCCH of 4-14 symbols with small UCI payloads of up to two bits with UE multiplexing capacity of up to 84 UEs without frequency hopping and 36 UEs with frequency hopping in the same PRB; - Format #2: Short PUCCH of 1 or 2 symbols with large UCI payloads of more than two bits with no UE multiplexing capability in the same PRBs; - Format #3: Long PUCCH of 4-14 symbols with large UCI payloads with no UE multiplexing capability in the same PRBs; - Format #4: Long PUCCH of 4-14 symbols with moderate UCI payloads with multiplexing capacity of up to 4 UEs in the same PRBs. The short PUCCH format of up to two UCI bits is based on sequence selection, while the short PUCCH format of more than two UCI bits frequency multiplexes UCI and DMRS. The long PUCCH formats time-multiplex the UCI and DMRS. Frequency hopping is supported for long PUCCH formats and for short PUCCH formats of duration of 2 symbols. Short and long PUCCH formats can be repeated over multiple slots or sub-slots, where the repetition factor is either indicated dynamically in the DCI or semi-statically in an RRC configuration. For operation with shared spectrum channel access in FR1, PUCCH Format #0, #1, #2, #3 are extended to use resource in one PRB interlace (up to two interlaces for Format #2 and Format #3) in one RB Set. PUCCH Format #2 and #3 are enhanced to support multiplexing capacity of up to 4 UEs in the same PRB interlace when one interlace is used. For operation in FR2-2, PUCCH Format #0, #1, #4 are extended to use resource in configurable number of continuous PRBs, up to 16 PRBs. Up to two PUCCH configurations can be configured for a UE per PUCCH group (see TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12]), where the first PUCCH configuration is associated with a PUCCH of priority index 0 (low) and the second PUCCH configuration is associated with a PUCCH of priority index 1 (high). UCI multiplexing in PUCCH is supported when PUCCH transmissions of UCIs coincide in time, and are associated with the same priority (high/low). In addition, multiplexing of HARQ-ACK of priority index 0 (low) and UCI of priority index 1 (high) in PUCCH of priority index 1 (high) is supported when PUCCH transmissions of HARQ-ACK of priority index 0 and UCI of priority index 1 (high) coincide in time. UCI multiplexing in PUSCH is supported when UCI and PUSCH transmissions coincide in time, either due to transmission of a UL-SCH transport block or due to triggering of A-CSI transmission without UL-SCH transport block, and are associated with the same priority (high/low). In addition, HARQ-ACK multiplexing of a certain priority in PUSCH of a different priority is supported when HARQ-ACK and PUSCH transmissions coincide in time, either due to transmission of a UL-SCH transport block or due to triggering of A-CSI transmission without UL-SCH transport block: - UCI carrying HARQ-ACK feedback with 1 or 2 bits is multiplexed by puncturing PUSCH; - In all other cases UCI is multiplexed by rate matching PUSCH. UCI consists of the following information: - CSI; - ACK/NAK; - Scheduling request. Simultaneous transmission of PUCCH and PUSCH associated with different priorities on cells of different bands in a PUCCH group is supported, where UCI multiplexing in the PUCCH associated with a priority in combination of UCI multiplexing in a PUSCH associated with a different priority is supported if the UCI multiplexed on PUSCH is of same priority as the PUSCH. For operation with shared spectrum channel access, multiplexing of CG-UCI and PUCCH carrying HARQ-ACK feedback can be configured by the gNB. If not configured, when PUCCH overlaps with PUSCH scheduled by a configured grant within a PUCCH group and PUCCH carries HARQ ACK feedback, PUSCH scheduled by configured grant is skipped. QPSK and Ο/2 BPSK modulation can be used for long PUCCH with more than 2 bits of information, QPSK is used for short PUCCH with more than 2 bits of information and BPSK and QPSK modulation can be used for long PUCCH with up to 2 information bits. Transform precoding is applied to PUCCH Format #3 and Format #4. Channel coding used for uplink control information is described in table 5.3.3-1. Table 5.3.3-1: Channel coding for uplink control information | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.3 |
4,042 | 5.3.1.2.4 IPv4 address allocation, renewal and release and IPv4 parameter configuration via DHCPv4 | When the PLMN allocates an IPv4 address, it is the PDN GW responsibility to allocate, renew and release the IPv4 address. When external PDN allocation is used, the PDN GW functions as a DHCPv4 server towards the UE. The PDN GW may act as a DHCP Client when interacting with a DHCPv4 server in the external PDN in order to obtain, renew and release the IPv4 address and to obtain the configuration parameters. Or, if RADIUS or Diameter is used towards the external PDN as described in TS 29.061[ Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) ] [38], the IPv4 address and the requested configuration parameters can be obtained, renewed and released as part of these procedures. If dynamic policy provisioning is deployed, and the PCRF was not informed about the IPv4 address at IP-CAN session establishment, the PDN GW shall initiate an IP-CAN Session Modification procedure to inform the PCRF about an allocated IPv4 address. If the IPv4 address is released, the PDN GW shall inform the PCRF about the de-allocation of an IPv4 address. If the UE sends DHCPv4 lease renewal message to renew the lease of the allocated IPv4 address, the PDN GW shall renew the lease of the allocated IPv4 address. If the IPv4 address was obtained from an external PDN, the PDN GW shall perform the DHCPv4 lease renewal procedure with the external PDN if DHCPv4 was used for obtaining IPv4 address from external PDN. If Diameter or RADIUS procedures where used to obtain the IPv4 address from external PDN, the PDN GW may perform corresponding update procedures as applicable. If the external PDN extends lease of the allocated IPv4 address, the PDN GW responds accordingly to the UE. Otherwise, if the external PDN does not extend the lease of the allocated IPv4 address, the PDN GW responds with the remaining lease time of the IPv4 address. If there is no PDN address allocated to the UE for this PDN connection, the PDN GW shall perform PDN GW initiated bearer deactivation procedure as defined in clause 5.4.4.1. If the UE sends DHCPv4 release message to release the allocated IPv4 address for the PDN connection, the PDN GW may any time thereafter release the IPv4 address. If the PDN connection has no allocated PDN address, the PDN GW may at any time initiate PDN GW initiated bearer deactivation procedure as defined in clause 5.4.4.1. NOTE: If the PDN type is IPv4v6 the release of the allocated IPv4 address does not mean that there is no allocated PDN address for the PDN connection, as the IPv6 prefix still remains allocated to that PDN connection. If the PDN connection is released without any DHCPv4 release signalling with the UE, the UE and the PDN GW shall release the IPv4 address implicitly, as soon as the PDN connection is released. After releasing the IPv4 address, the PDN GW should not assign that IPv4 address to any other user immediately. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.3.1.2.4 |
4,043 | 6.41.2.4 UE Configuration, Provisioning, Authentication and Authorization | Subject to localized services agreements, the 5G system shall enable a home network operator to authorize a UE for using its home network services via a hosting network for a certain period of time and/or location. The 5G system shall allow a trusted 3rd party service provider to provide UEs with localized service policy (e.g., QoS, network slice in the hosting or home network, service restriction such as time and location) via the hosting network or the UEβs home network. The 5G system shall enable a UE to use credentials provided by the hosting network with or without coordination with the home network of the UE, to make use of localized services via the hosting network with a certain time (including starting time and the duration) and location validity. The 5G system shall be able to allow the home network to steer its UE(s) to a hosting network with the consideration of the location, times, coverage of the hosting network and services offered by the home network and hosting network. The 5G system shall provide support to enable secure means to authenticate and authorize a user of a UE accessing a hosting network, including cases in which a UE has no subscription to the hosting network and still needs to get authorized to use localized services via the hosting network. NOTE: It can be assumed that a network provider deploying a hosting network has access to respective identification information about the user, e.g., through a separate registration process outside the scope of 3GPP. The 5G system shall be able to authenticate and authorize the UE of a user authenticated to a hosting network to access the hosting network and its localized services on request of a service provider. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.41.2.4 |
4,044 | 4.3.5.7 Simultaneous change of Branching Point or UL CL and additional PSA for a PDU Session | Simultaneous change of UL CL or Branching Point and additional PSA can be performed after Xn based handover, N2 based handover and Service Request procedures. The following procedure is triggered by SMF in order to change the Branching Point or the UL CL and additional PSA serving a PDU Session for a UE. Figure 4.3.5.7-1: Simultaneous change of Branching Point or UL CL and additional PSA for a PDU Session UE has an established PDU Session with a UPF including the PDU Session Anchor (Remote UPF). The PDU Session user plane involves at least the Source (R)AN, Source Branching Point or Source UL CL, local Source UPF (PSA2) and the Remote UPF (PDU Session Anchor, PSA1), where Source Branching Point or Source UL CL and PSA2 can be co-located. 1. At some point SMF decides to change the Branching Point or the UL CL due to UE mobility. 2. The SMF selects a local Target UPF (PSA3) and using N4 establishes the local Target UPF for the PDU Session. In the case of IPv6 multi-homing PDU Session, a new IPv6 prefix corresponding to PSA3 is allocated (by the SMF or by the UPF depending on the deployment) and if the PCF has subscribed to the IP allocation/release event, the SMF performs the Session Management Policy Modification procedure as defined in clause 4.16.5 to provide the new allocated IPv6 prefix to the PCF. The SMF may send an Early notification to the AF after PSA3 is selected. If the runtime coordination between 5GC and AF is enabled based on local configuration as specified in clause 4.3.6.3, according to the indication of "AF acknowledgment to be expected" included in AF subscription to SMF events, the SMF waits for a notification response from the AF before configuring the PSA3. If the SMF receives a negative notification response from the AF, the SMF may stop the procedure. This is defined in Figure 4.3.6.3-1. 3. The SMF selects a UPF and using N4 establishes the Target Branching Point or Target UL CL for the PDU Session. SMF provides the necessary uplink forwarding rules towards the PSA3 and PSA1 including the Tunnel Info for each UPF. If session continuity upon UL CL relocation is used, the SMF also uses N4 to establish an N9 forwarding tunnel between the Source UL CL and Target UL CL, including the Tunnel Info for each UPF. In addition, the AN Tunnel Info to target (R)AN is provided for downlink forwarding. In the case of UL CL, the SMF provides traffic filters indicating what traffic shall be forwarded towards PSA3, PSA1 and Source UL CL, respectively. In the case of IPv6 multi-homing, the SMF also provides traffic filters for the IPv6 prefixes corresponding to PSA3 and PSA1 indicating what traffic shall be forwarded towards PSA3 and PSA1 respectively. Target Branching Point or Target UL CL provides the CN Tunnel Info for downlink traffic. NOTE 1: If the Target Branching Point or Target UL CL and the PSA3 are co-located in a single UPF then steps 2 and 3 can be merged. NOTE 2: When session continuity upon UL CL relocation is used, the downlink traffic at this point goes through Source UL CL, Target UL CL and Target (R)AN. 4. The SMF updates the PSA1 via N4. It provides the PDU Session CN Tunnel Info for the downlink traffic. 5. The SMF updates the PSA3 via N4. It provides the CN Tunnel Info for downlink traffic. The SMF may also indicate PSA3 to buffer uplink data. NOTE 3: If the Target Branching Point or the Target UL CL and the PSA3 are co-located in a single UPF then step 5 is not needed. 6. In the case of PDU session with UL CL, if the runtime coordination between 5GC and AF is enabled based on local configuration, according to the indication of "AF acknowledgment to be expected" included in AF subscription to SMF events, the SMF sends a late notification to the AF and waits for a notification response from the AF as described in step 9. If the SMF receives a negative notification response from the AF, the SMF may stop the procedure and remove the Target Branching Point or Target UL CL and PSA3. This is further defined in Figure 4.3.6.3-1. The SMF updates (R)AN via N2 SM information over N11. It provides the new CN Tunnel Info corresponding to the Target Branching Point or the Target UL CL. If there is an existing UPF between the Target (R)AN and Target Branching Point or Target UL CL, the SMF updates the existing UPF via N4 instead of updating the (R)AN. NOTE 4: When session continuity upon UL CL relocation is used, the uplink traffic destined to PSA2 at this point goes through Target (R)AN, Target UL CL and Source UL CL. 7. In the case of IPv6 multi-homing PDU Session, if the runtime coordination between 5GC and AF is enabled based on local configuration, according to the indication of "AF acknowledgment to be expected" included in AF subscription to SMF events, the SMF sends a late notification to the AF and waits for a notification response from the AF as described in step 9. If the SMF receives a negative notification response from the AF, the SMF may stop the procedure. This is further defined in Figure 4.3.6.3-1. In the case of IPv6 multi-homing, the SMF notifies the UE of the availability of the new IP prefix @ PSA3. This is performed using an IPv6 Router Advertisement message (RFC 4861 [6]). Also, the SMF sends IPv6 multi-homed routing rule along with the IPv6 prefix to the UE using an IPv6 Router Advertisement message (RFC 4191 [21]) as described in clause 5.8.2.2.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 8. In the case of IPv6 multi-homing, the SMF may re-configure the UE for the original IP prefix @ PSA1, i.e. SMF sends IPv6 multi-homed routing rule along with the IPv6 prefix to the UE using an IPv6 Router Advertisement message (RFC 4191 [21]) as described in clause 5.8.2.2.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 9. The SMF sends a Late Notification to the AF indicating a change of DNAI as described in clause 4.3.6.3. In cases where target local DN is associated with another AF instance, SMF also sends notification to target AF as described in 4.3.6.3 and cancels any future notification message to source AF as it is no longer involved. The SMF may also indicate PSA3 to stop buffering and start forwarding uplink data based on the positive response for the Late Notification. NOTE 5: The message can include routing information to the application located in the target local DN. Alternatively the routing information to the application located in the target local DN can be determined by the AF based on the new DNAI, in which case the AF can invoke the AF triggered influence on traffic routing procedure targeting single UE as described in clause 4.3.6.4, which assists the SMF in generation of the routing rule on the Target UL CL towards PSA3 (i.e. towards the application located in the target local DN). It is up to network configuration whether the routing information to the application located in the target local DN is configured in the SMF or in the AF. NOTE 6: When session continuity upon UL CL relocation is used the AF can also trigger mechanisms that are out of the scope of this specification (e.g. IP-level or HTTP-level redirection) by which the traffic is redirected towards the application in the target local DN. Based on this redirection the UE starts using a new destination IP address which leads the Target UL CL to force the traffic towards PSA3. 10. When session continuity upon UL CL relocation is used, detection of no active traffic over the N9 forwarding tunnel is performed during a time interval provisioned by SMF for User Plane inactivity report in order to release the N9 forwarding tunnel. The detection can be done by Source UL CL, which notifies the SMF of no active traffic over the N9 forwarding tunnel. NOTE 7: It is up to network configuration whether the detection of no active traffic is performed by the Source UL CL or the Target UL CL. As an alternative to the detection of no active traffic, the AF can send an explicit notification to the SMF when traffic to/from this UE ceases to exist, leading the SMF to release the Source UL CL and the Source UPF (PSA2). 11. The SMF releases via N4 the PSA2. 12. The SMF releases the Source Branching Point or the Source UL CL. NOTE 8: If the Source Branching Point or UL CL and the PSA2 are co-located in a single UPF then steps 11 and 12 can be merged. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3.5.7 |
4,045 | 4.16.1.6 Failed Secondary Node Additions with SN terminated bearers | a) This measurement provides the number of failures when Secondary Node Addition with SN terminated bearers. The measurement is split into subcounters per failure cause. b) CC c) On MN failed receipt of SGNB ADDITION REQUEST ACKNOWLEGE Message or on transmission by MN of an SgNB Release Message after receipt of SGNB ADDITION REQUEST ACKNOWLEGE Message when Secondary Node Additions with SN terminated bearers. Each Secondary Node failed to add is added to the relevant measurement per cause, the possible causes are included in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [9]. The sum of all supported per cause measurements shall equal the total number of Additions failed to setup at Secondary Node Additions with SN terminated bearers case. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first. SGNB Addition Trigger Indication (TS 36.423[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 Application Protocol (X2AP) ] [10]) excludes SN change, inter-eNB HO, intra-eNB HO. d) Each measurement is an integer value. The number of measurements is equal to the number of causes plus a possible sum value identified by the .sum suffix. e) The measurement name has the form ENDC.SNAdditionFailWithSnErab.Cause where Cause identifies the cause resulting in the Secondary Node Addition failure for with SN terminated bearers case. f) EUtranCellFDD EUtranCellTDD g) Valid for packet switched traffic h) EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.16.1.6 |
4,046 | 6.2.5.1.4 Reflective QoS 6.2.5.1.4.1 General | The UE may support reflective QoS. If the UE supports the reflective QoS, the UE shall support the procedures in the following subclauses. The reflective QoS is applicable in a PDU session of IPv4, IPv6, IPv4v6 and Ethernet PDU session type. The reflective QoS is not applicable in a PDU session of Unstructured PDU session type. Reflective QoS is not applicable for a PDU session with control plane only indication. The UE may request to revoke the usage of reflective QoS for an existing PDU session for which the UE had previously indicated support for reflective QoS. | 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.5.1.4 |
4,047 | B.2 Description of BWP configuration options | There are two possible ways to configure BWP#0 (i.e. the initial BWP) for a UE: 1) Configure BWP-DownlinkCommon and BWP-UplinkCommon in ServingCellConfigCommon, but do not configure dedicated configurations in BWP-DownlinkDedicated or BWP-UplinkDedicated in ServingCellConfig. 2) Configure both BWP-DownlinkCommon and BWP-UplinkCommon in ServingCellConfigCommon and configure dedicated configurations in at least one of BWP-DownlinkDedicated or BWP-UplinkDedicated in ServingCellConfig. The same way of configuration is used for UL BWP#0 and DL BWP#0 if both are configured. With the first option (illustrated by figure B2-1 below), the BWP#0 is not considered to be an RRC-configured BWP, i.e., UE only supporting one BWP can still be configured with BWP#1 in addition to BWP#0 when using this configuration. The BWP#0 can still be used even if it does not have the dedicated configuration, albeit in a more limited manner since only the SIB1-defined configurations are available. For example, only DCI format 1_0 can be used with BWP#0 without dedicated configuration, so changing to another BWP requires RRCReconfiguration since DCI format 1_0 doesn't support DCI-based switching. Figure B2-1: BWP#0 configuration without dedicated configuration With the second option (illustrated by figure B2-2 below), the BWP#0 is considered to be an RRC-configured BWP, i.e. UE only supporting one BWP cannot be configured with BWP#1 in addition to BWP#0 when using this configuration. However, UE supporting more than one BWP can still switch to and from BWP#0 e.g. via DCI normally, and there are no explicit limitations to using the BWP#0 (compared to the first option). Figure B2-2: BWP#0 configuration with dedicated configuration For BWP#0, the BWP-DownlinkCommon and BWP-UplinkCommon in ServingCellConfigCommon should match the parameters configured by MIB and SIB1 (if provided) in the corresponding serving cell. If an (e)RedCap-specific initial DL BWP is configured, for BWP switching, the BWP #0 always maps to the (e)RedCap-specific initial DL BWP. If a RedCap-specific initial UL BWP is configured, for BWP switching on NUL, the BWP #0 always maps to the RedCap-specific initial UL BWP, for BWP switching on SUL, the BWP#0 always maps to the initial UL BWP. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | B.2 |
4,048 | 5.45.4 Data rate monitoring | The QoS Monitoring for data rate allows the measurement of the UL and/or DL data rate per QoS flow at the PSA UPF and it can be applied to a Non-GBR or GBR QoS flow. The data rate is measured over a monitoring averaging window with a standardized value. The SMF may configure the UPF to perform and report QoS monitoring for data rates as described in clause 5.8.2.18. According to the QoS Monitoring request for UL and/or DL data rate from the SMF, the UPF is required to initiate data rate measurement for a QoS Flow and to report the measured data rate as instructed. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.45.4 |
4,049 | β ConditionalReconfiguration | The IE ConditionalReconfiguration is used to add, modify and release the configuration of conditional reconfiguration. ConditionalReconfiguration information element -- ASN1START -- TAG-CONDITIONALRECONFIGURATION-START ConditionalReconfiguration-r16 ::= SEQUENCE { attemptCondReconfig-r16 ENUMERATED {true} OPTIONAL, -- Cond CHO condReconfigToRemoveList-r16 CondReconfigToRemoveList-r16 OPTIONAL, -- Need N condReconfigToAddModList-r16 CondReconfigToAddModList-r16 OPTIONAL, -- Need N ..., [[ scpac-ReferenceConfiguration-r18 SetupRelease {ReferenceConfiguration-r18} OPTIONAL, -- Need M servingSecurityCellSetId-r18 SecurityCellSetId-r18 OPTIONAL, -- Cond condInitialSCPAC sk-CounterConfiguration-r18 SK-CounterConfiguration-r18 OPTIONAL -- Need M ]] } CondReconfigToRemoveList-r16 ::= SEQUENCE (SIZE (1.. maxNrofCondCells-r16)) OF CondReconfigId-r16 SK-CounterConfiguration-r18 ::= SEQUENCE { sk-CounterConfigToReleaseList-r18 SEQUENCE (SIZE (1..maxSecurityCellSet-r18)) OF SecurityCellSetId-r18 OPTIONAL, -- Need N sk-CounterConfigToAddModList-r18 SEQUENCE (SIZE (1..maxSecurityCellSet-r18)) OF SK-CounterConfig-r18 OPTIONAL -- Need N } SK-CounterConfig-r18 ::= SEQUENCE { securityCellSetId-r18 SecurityCellSetId-r18, sk-CounterList-r18 SEQUENCE (SIZE (1..maxSK-Counter-r18)) OF SK-Counter } SecurityCellSetId-r18 ::= INTEGER (1.. maxSecurityCellSet-r18) -- TAG-CONDITIONALRECONFIGURATION-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
4,050 | 4.4.8 PDN GW's associated AAA Server | The PDN Gateway may interact with a AAA server over the SGi interface. This AAA Server may maintain information associated with UE access to the EPC and provide authorization and other network services. This AAA Server could be a RADIUS or Diameter Server in an external PDN network, as defined in TS 29.061[ Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) ] [38]. This AAA Server is logically separate from the HSS and the 3GPP AAA Server. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.4.8 |
4,051 | Y.3 Transport security protection for MSGin5G interfaces | The MSGin5G-1 interface may be protected by TLS based on KAF established by AKMA as specified in TS 33.535[ Authentication and Key Management for Applications (AKMA) based on 3GPP credentials in the 5G System (5GS) ] [91]. The MSGin5G Client and the MSGin5G Server establish the TLS session following the procedures defined in Annex B of TS 33.535[ Authentication and Key Management for Applications (AKMA) based on 3GPP credentials in the 5G System (5GS) ] [91]. The MSGin5G-1 interface may be protected using mechanisms other than TLS with AKMA, depending on the Ua* protocols. For the data protection over MSGin5G-3 interface between MSGin5G Server and Application Server, if the Application Server is inside the operator domain, the transport security protection on SBI interface shall be reused as specified in clause 13. If the Application Server is outside the operator domain, the Application Server shall connect to the MSGin5G Server via NEF, clause 12.3 in the present document is applicable with the Appplication Server taking the role of the AF. For MSGin5G-2, MSGin5G-4 and MSGin5G-7 interfaces, TLS shall be used for transport protection unless network security is provided by other means. The interconnection between the two MSGin5G Servers shall be protected by TLS as specified in TS 33.210[ Network Domain Security (NDS); IP network layer security ] [3]. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | Y.3 |
4,052 | 8.1.2.12.1 Applicability rule and antenna connection for single carrier PDSCH tests | 8.1.2.12.1.1 Applicability rule and antenna connection for single carrier PDSCH tests with 2Rx and 4Rx For 8Rx capable UEs, all single carrier tests specified in 8.2 to 8.8 with 2Rx are tested on any of the 2Rx supported RF bands by connecting 2 out of the 8Rx with data source from system simulator, and the other 6 Rx are connected with zero input, depending on UEβs declaration and AP configuration. Same requirements specified with 2Rx should be applied. For 8Rx capable UEs, all single carrier test cases specified in 8.10 with 4Rx are tested on any of the 4Rx supported RF bands by connecting 4 out of 8 Rx with data source from system simulator, and the other 4 Rx are connected with zero input, depending on UEβs declaration and AP configuration. Same requirements specified with 4Rx should be applied. For 8Rx capable UEs without support of any 4Rx RF bands, all single carrier tests specified in 8.10 with 4Rx are tested on any of the 8Rx supported RF bands by duplicating the fading channel from each Tx antenna and add independent noise for each Rx antenna. The SNR requirements should be applied with 1.5 dB less than the number specified for 4Rx tests. For 8Rx capable UEs without support of any 2Rx and 4Rx RF bands, all single carrier tests specified in 8.2 to 8.8 with 2Rx are tested on any of the 8Rx supported RF bands by duplicating the fading channel from each Tx antenna and add independent noise for each Rx antenna. The SNR requirements should be applied with 3 dB less than the number specified for 2Rx tests. For 8Rx capable UEs without support of any 2Rx RF bands but with support of 4Rx RF bands, all single carrier tests specified in 8.2 to 8.8 with 2Rx are tested on any of the 4Rx supported RF bands by duplicating the fading channel from each Tx antenna and add independent noise for each Rx antenna. 4 out of 8 Rx are connected with data source from system simulator, and the other 4 Rx are connected with zero input, depending on UEβs declaration and AP configuration. SNR requirements should be applied with 1.5 dB less than the number specified for 2Rx tests. Figure 8.1.2.12.1-1 ~ Figure 8.1.2.12.1-4 show examples of antenna connection for 8Rx capable UE in any one 8Rx supported RF band to perform a 2Rx or 4Rx performance test with antenna configuration as 2x2 or 4x2 for 2Rx tests and 2x4 or 4x4 for 4Rx tests without interference for information. Figure 8.1.2.12.1-1: Antenna connection example for 2Rx tests with antenna configuration as 2x2 without interference (informative) Figure 8.1.2.12.1-2: Antenna connection example for 2Rx tests with antenna configuration as 4x2 without interference (informative) Figure 8.1.2.12.1-3: Antenna connection example for 4Rx tests with antenna configuration as 2x4 without interference (informative) Figure 8.1.2.12.1-4: Antenna connection example for 4Rx tests with antenna configuration as 4x4 without interference (informative) For 8Rx capable UEs without any 2Rx supported RF bands, for all single carrier tests listed in Table 8.1.2.12.1-1 specified from 8.2 to 8.8 with 2Rx can be skipped. Table 8.1.2.12.1-1: Requirement lists with 2Rx not applicable to 8Rx capable UEs For 8Rx capable UEs without any 4Rx supported RF bands, for all single carrier tests listed in Table 8.1.2.12.1-2 specified in 8.10 with 4Rx can be skipped. Table 8.1.2.12.1-2: Requirement lists with 4Rx not applicable to 8Rx capable UEs For 8Rx capable UEs, if corresponding tests listed from the 8Rx test lists from Table 8.1.2.12.1-3 are tested, the test coverage can be considered fulfilled without executing the corresponding tests listed from botht the 4Rx test lists and the 2Rx test lists from Table 8.1.2.12.1-3. For 8Rx capable UEs, if corresponding tests listed from the 4Rx test lists from Table 8.1.2.12.1-3 are tested, the test coverage can be considered fulfilled without executing the corresponding tests listed from the 2Rx test lists from Table 8.1.2.12.1-3. Table 8.1.2.12.1-3: Applicability rules for single carrier tests with 2Rx 8.1.2.12.1.2 Applicability rule and antenna connection for single carrier PDSCH tests with 8Rx For 8Rx capable UEs all single carrier tests specified in 8.14 with 8Rx are tested on any of the 8Rx supported RF bands by connecting all 8Rx with data source from system simulator. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.1.2.12.1 |
4,053 | 6.3.4.2.3 Codebook for precoding and CSI reporting | For transmission on two antenna ports, , and for the purpose of CSI reporting based on two antenna ports or , the precoding matrix shall be selected from Table 6.3.4.2.3-1 or a subset thereof. For the closed-loop spatial multiplexing transmission mode defined in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4], the codebook index 0 is not used when the number of layers is . Table 6.3.4.2.3-1: Codebook for transmission on antenna ports and for CSI reporting based on antenna ports or For transmission on four antenna ports, , the precoding matrix shall be selected from Table 6.3.4.2.3-2 or a subset thereof. For the purpose of CSI reporting based on four antenna ports or , the precoding matrix shall be selected from Table 6.3.4.2.3-2 or a subset thereof except for alternativeCodeBookEnabledFor4TX-r12 =TRUE in which case the precoding matrix shall be selected from Tables 7.2.4-0A, 7.2.4-0B, 7.2.4-0C, 7.2.4-0D in [4] or a subset thereof, and except for advancedCodebookEnabled = TRUE in which case the precoding matrix shall be selected from Table 7.2.4-17C in [4] or a subset thereof. The quantity denotes the matrix defined by the columns given by the set from the expression where is the identity matrix and the vector is given by Table 6.3.4.2.3-2. Table 6.3.4.2.3-2: Codebook for transmission on antenna ports and for CSI reporting based on antenna ports or For the purpose of CSI reporting for 8, 12, 16, 20, 24, 28, and 32 CSI reference signals the codebooks are given in clause 7.2.4 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4]. | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.3.4.2.3 |
4,054 | 5.32.5 Access Network Performance Measurements 5.32.5.1 General principles | When an MA PDU Session is established, the network may provide the UE with Measurement Assistance Information. This information assists the UE in determining which measurements shall be performed over both accesses, as well as whether measurement reports need to be sent to the network. Measurement Assistance Information shall include the addressing information of a Performance Measurement Function (PMF) in the UPF, the UE can send PMF protocol messages to: - For a PDU Session of IP type, Measurement Assistance Information contains one IP address for the PMF, one UDP port associated with 3GPP access and another UDP port associated with non-3GPP access. PMF messages sent by UE to one of these UDP ports, shall be transmitted to UPF via the QoS Flow associated with the default QoS rule. - For a PDU Session of Ethernet type, Measurement Assistance Information contains one MAC address associated with 3GPP access and another MAC address associated with non-3GPP access. PMF messages sent by UE to one of these MAC addresses, shall be transmitted to UPF via the QoS Flow associated with the default QoS rule. NOTE 1: To protect the PMF in the UPF (e.g. to block DDOS to the PMF), the IP addresses of the PMF are only accessible from the UE IP address via the N3/N9 interface. NOTE 2: After the MA PDU Session is released, the same UE IP address/prefix is not allocated to another UE for MA PDU Session in a short time. If the SMF determines that access performance measurements per QoS Flow shall be applied for the MA PDU Session, then the Measurement Assistance Information shall also include a list of QoS Flows on which access performance measurements may be performed. For each QoS Flow in this list, the following information is included: - The QFI of the associated QoS Flow. - For a PDU Session of IP type, one UDP port associated with 3GPP access and another UDP port associated with non-3GPP access. PMF messages sent by UE to one of these UDP ports, shall be transmitted to UPF via the associated QoS Flow. - For a PDU Session of Ethernet type, one MAC address associated with 3GPP access and another MAC address associated with non-3GPP access. PMF messages sent by UE to one of these MAC addresses, shall be transmitted to UPF via the associated QoS Flow. The QoS rules and the N4 rules provided by SMF to UE and to UPF respectively shall include information (e.g. packet filters containing the UDP port or the MAC address associated with a QoS Flow), which enables the UE and UPF to route a PMF message to a specific QoS Flow. The UE and the UPF may need to perform access performance measurements in order to estimate the Round-Trip Time (RTT) and/or the Packet Loss Rate (PLR) that an SDF is expected to experience when transmitted on a certain access type. Based on these measurements and the provisioned ATSSS rules in the UE and MAR rules in the UPF, the UE and the UPF decide how to distribute the traffic of an SDF across the two accesses. If the UE and the UPF decide to initiate access performance measurements to estimate the RTT and/or the PLR for an SDF, the access performance measurements shall be performed either (a) using the QoS Flow associated with the default QoS rule; or (b) using the target QoS Flow, which is the QoS Flow that the SDF traffic is transmitted on. When the access performance measurements are using the target QoS Flow, it is termed that "access performance measurements per QoS Flow" are applied for the MA PDU Session. The UE shall indicate in its ATSSS capabilities that it supports access performance measurements per QoS Flow. Based on this UE capability and other information (such as local policy), the SMF determines whether access performance measurements per QoS Flow shall be applied for the MA PDU Session or not. If the SMF determines that access performance measurements per QoS Flow shall be applied for the MA PDU Session, then: - The SMF determines a list of QoS Flows over which access performance measurements may be performed and provides this list to the UE (within the Measurement Assistance Information) and to the UPF. - The UE and the UPF may initiate access performance measurements on one or more of the QoS Flows included in this list. The UE and the UPF shall be able to receive and respond to PMF messages sent on any QoS Flow included in this list. - The SMF may update the list of QoS Flows over which access performance measurements may be performed during the lifetime of a MA PDU Session, e.g. when a new PCC rule that could benefit from PMF access performance measurements is bound to a QoS Flow. NOTE 3: The SMF can e.g. add a QoS Flow into the list when at least one PCC Rule is bound to that QoS Flow that is using one of the Steering Modes where performance measurements via PMF are applicable, such as Lowest Delay Steering Mode or a Steering Mode where threshold values have been provided. The UE shall perform access performance measurements per QoS Flow only when this is explicitly indicated in the Measurement Assistance Information, i.e. only when the UE receives the list of QoS Flows over which access performance measurements may be performed. Otherwise, the UE shall perform access performance measurements based on the QoS Flow associated with the default QoS rule. The UPF shall perform access performance measurements per QoS Flow only when this is explicitly indicated by SMF, i.e. only when the UPF receives the list of QoS Flows over which access performance measurements may be performed. Otherwise, the UPF shall perform access performance measurements based on the QoS Flow associated with the default QoS rule. In this case the UPF learns what QoS Flow to use as described in TS 29.244[ Interface between the Control Plane and the User Plane nodes ] [65]. The UE and the UPF may decide not to initiate access performance measurements using PMF over a certain target QoS Flow, when they already have access performance measurements for another target QoS Flow which they determine can be reused. NOTE 4: How the UE and UPF determine that the performance measurements using a certain target QoS Flow apply to another target QoS Flow is based on implementation, e.g. AN resource to QoS Flow mapping in the UE or getting similar access measurements results with other QoS Flow. When access performance measurements for an SDF are performed based on the target QoS Flow, the UE needs to be able to determine the QoS Flow a downlink packet arrives on. In order to enable this, the SMF shall include downlink Packet Filter information in the QoS rule provided to UE matching this SDF, unless Reflective QoS is used for the SDF. NOTE 5: For example, if a QoS Flow requires to activate Reflective QoS, the SMF does not need to provide downlink QoS Flow information for the QoS Flow to minimize usage of packet filters. When a data packet is received over a QoS Flow, the UE can decide whether to check the downlink QoS Flow information based on the existence of SDAP header for the QoS Flow. The addressing information of the PMF in the UPF is retrieved by the SMF from the UPF during N4 session establishment. If the UPF receives from the SMF, during N4 session establishment or modification procedure, a list of QoS Flows over which access performance measurements may be performed, the UPF allocates different UDP ports per QoS Flow per access for IP PDU sessions, or allocates different MAC addresses per QoS Flow per access for Ethernet PDU sessions. For IP PDU sessions, the UPF sends the PMF IP addressing information and the UDP ports with the QFI of the associated QoS Flow to the SMF. For Ethernet PDU sessions, the UPF sends the MAC addresses with the QFI of the associated QoS Flow to the SMF. The following PMF protocol messages can be exchanged between the UE and the UPF: - Messages to allow for Round Trip Time (RTT) measurements, i.e. when the "Smallest Delay" steering mode is used or when either "Priority-based", "Load-Balancing" or "Redundant" steering mode is used with RTT threshold value being applied; - Messages to allow for Packet Loss Rate (PLR) measurements, i.e. when steering mode is used either "Priority-based", "Load-Balancing" or "Redundant" steering mode is used with PLR threshold value being applied; - Messages for reporting Access availability/unavailability by the UE to the UPF. - Messages for sending UE-assistance data to UPF. Such messages may be sent from the UE to UPF only when the UE receives the UE-assistance indicator in an ATSSS rule, as specified in clause 5.32.8. Further details are provided in clause 5.32.5.5. - Messages for sending Suspend Traffic Duplication and Resume Traffic Duplication from UPF to UE to suspend or resume traffic duplication as defined in clause 5.32.5.6. Since steering modes can be different in up-link and down-link, the UE needs to be able to handle PMF protocol messages for RTT and PLR measurements received from UPF even if it is not using one of the steering modes associated with the RTT and PLR measurements (and vice versa). The PMF protocol is specified in TS 24.193[ 5G System;Access Traffic Steering, Switching and Splitting (ATSSS); Stage 3 ] [109]. The PMF protocol messages used for access availability/unavailability reports shall be sent on the QoS Flow associated with the default QoS rule. The PMF protocol messages used for access performance measurements shall be sent either on the QoS Flow associated with the default QoS rule, or on the target QoS Flow, as specified above. The QoS Flow associated with the default QoS rule for MA PDU Session is Non-GBR QoS Flow. The UE shall not apply the ATSSS rules and the UPF shall not apply the MAR rules for the PMF protocol messages. When the UE requests a MA PDU session and indicates it is capable to support: - the MPTCP functionality with any steering mode and the ATSSS-LL functionality with only the Active-Standby steering mode (as specified in clause 5.32.6.1); or - the MPQUIC functionality with any steering mode and the ATSSS-LL functionality with only the Active-Standby steering mode (as specified in clause 5.32.6.1); or - the MPTCP functionality with any steering mode, and the MPQUIC functionality with any steering mode and the ATSSS-LL functionality with only the Active-Standby steering mode (as specified in clause 5.32.6.1); the network may send Measurement Assistance Information for the UE to send Access availability/unavailability reports to the UPF. In this case, the UE and UPF shall not perform RTT and PLR measurements using PMF as the UE and UPF can use measurements available at the MPTCP layer and/or at the MPQUIC layer. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.32.5 |
4,055 | β SharedSpectrumChAccessParamsPerBand | The IE SharedSpectrumChAccessParamsPerBand is used to convey shared channel access related parameters specific for a certain frequency band (not per feature set or band combination). SharedSpectrumChAccessParamsPerBand information element -- ASN1START -- TAG-SHAREDSPECTRUMCHACCESSPARAMSPERBAND-START SharedSpectrumChAccessParamsPerBand-r16 ::= SEQUENCE { -- R1 10-1: UL channel access for dynamic channel access mode ul-DynamicChAccess-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-1a: UL channel access for semi-static channel access mode ul-Semi-StaticChAccess-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-2: SSB-based RRM for dynamic channel access mode ssb-RRM-DynamicChAccess-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-2a: SSB-based RRM for semi-static channel access mode ssb-RRM-Semi-StaticChAccess-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-2b: MIB reading on unlicensed cell mib-Acquisition-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-2c: SSB-based RLM for dynamic channel access mode ssb-RLM-DynamicChAccess-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-2d: SSB-based RLM for semi-static channel access mode ssb-RLM-Semi-StaticChAccess-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-2e: SIB1 reception on unlicensed cell sib1-Acquisition-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-2f: Support monitoring of extended RAR window extRA-ResponseWindow-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-2g: SSB-based BFD/CBD for dynamic channel access mode ssb-BFD-CBD-dynamicChannelAccess-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-2h: SSB-based BFD/CBD for semi-static channel access mode ssb-BFD-CBD-semi-staticChannelAccess-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-2i: CSI-RS-based BFD/CBD for NR-U csi-RS-BFD-CBD-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-7: UL channel access for 10 MHz SCell ul-ChannelBW-SCell-10mhz-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-10: RSSI and channel occupancy measurement and reporting rssi-ChannelOccupancyReporting-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-11:SRS starting position at any OFDM symbol in a slot srs-StartAnyOFDM-Symbol-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-20: Support search space set configuration with freqMonitorLocation-r16 searchSpaceFreqMonitorLocation-r16 INTEGER (1..5) OPTIONAL, -- R1 10-20a: Support coreset configuration with rb-Offset coreset-RB-Offset-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-23:CGI reading on unlicensed cell for ANR functionality cgi-Acquisition-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-25: Enable configured UL transmissions when DCI 2_0 is configured but not detected configuredUL-Tx-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-27: Wideband PRACH prach-Wideband-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-29: Support available RB set indicator field in DCI 2_0 dci-AvailableRB-Set-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-30: Support channel occupancy duration indicator field in DCI 2_0 dci-ChOccupancyDuration-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-8: Type B PDSCH length {3, 5, 6, 8, 9, 10, 11, 12, 13} without DMRS shift due to CRS collision typeB-PDSCH-length-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-9: Search space set group switching with explicit DCI 2_0 bit field trigger or with implicit PDCCH decoding with DCI 2_0 monitoring searchSpaceSwitchWithDCI-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-9b: Search space set group switching with implicit PDCCH decoding without DCI 2_0 monitoring searchSpaceSwitchWithoutDCI-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-9d: Support Search space set group switching capability 2 searchSpaceSwitchCapability2-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-14: Non-numerical PDSCH to HARQ-ACK timing non-numericalPDSCH-HARQ-timing-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-15: Enhanced dynamic HARQ codebook enhancedDynamicHARQ-codebook-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-16: One-shot HARQ ACK feedback oneShotHARQ-feedback-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-17: Multi-PUSCH UL grant multiPUSCH-UL-grant-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-26: CSI-RS based RLM for NR-U csi-RS-RLM-r16 ENUMERATED {supported} OPTIONAL, dummy ENUMERATED {supported} OPTIONAL, -- R1 10-31: Support of P/SP-CSI-RS reception with CSI-RS-ValidationWith-DCI-r16 configured periodicAndSemi-PersistentCSI-RS-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-3: PRB interlace mapping for PUSCH pusch-PRB-interlace-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-3a: PRB interlace mapping for PUCCH pucch-F0-F1-PRB-Interlace-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-12: OCC for PRB interlace mapping for PF2 and PF3 occ-PRB-PF2-PF3-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-13a: Extended CP range of more than one symbol for CG-PUSCH extCP-rangeCG-PUSCH-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-18: Configured grant with retransmission in CG resources configuredGrantWithReTx-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-21a: Support using ED threshold given by gNB for UL to DL COT sharing ed-Threshold-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-21b: Support UL to DL COT sharing ul-DL-COT-Sharing-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-24: CG-UCI multiplexing with HARQ ACK mux-CG-UCI-HARQ-ACK-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-28: Configured grant with Rel-16 enhanced resource configuration cg-resourceConfig-r16 ENUMERATED {supported} OPTIONAL } SharedSpectrumChAccessParamsPerBand-v1630 ::= SEQUENCE { -- R4 4-1: DL reception in intra-carrier guardband dl-ReceptionIntraCellGuardband-r16 ENUMERATED {supported} OPTIONAL, -- R4 4-2: DL reception when gNB does not transmit on all RB sets of a carrier as a result of LBT dl-ReceptionLBT-subsetRB-r16 ENUMERATED {supported} OPTIONAL } SharedSpectrumChAccessParamsPerBand-v1640 ::= SEQUENCE { -- 10-26b(1-4): CSI-RS based RRM measurement with associated SS-block csi-RSRP-AndRSRQ-MeasWithSSB-r16 ENUMERATED {supported} OPTIONAL, -- 10-26c(1-5): CSI-RS based RRM measurement without associated SS-block csi-RSRP-AndRSRQ-MeasWithoutSSB-r16 ENUMERATED {supported} OPTIONAL, -- 10-26d(1-6): CSI-RS based RS-SINR measurement csi-SINR-Meas-r16 ENUMERATED {supported} OPTIONAL, -- 10-26e(1-8): RLM based on a mix of SS block and CSI-RS signals within active BWP ssb-AndCSI-RS-RLM-r16 ENUMERATED {supported} OPTIONAL, -- 10-26f(1-9): CSI-RS based contention free RA for HO csi-RS-CFRA-ForHO-r16 ENUMERATED {supported} OPTIONAL } SharedSpectrumChAccessParamsPerBand-v1650 ::= SEQUENCE { -- Extension of R1 10-9 capability to configure up to 16 instead of 4 cells or cell groups, respectively extendedSearchSpaceSwitchWithDCI-r16 ENUMERATED {supported} OPTIONAL } SharedSpectrumChAccessParamsPerBand-v1710 ::= SEQUENCE { -- R1 25-12: UE initiated semi-static channel occupancy with dependent configurations ul-Semi-StaticChAccessDependentConfig-r17 ENUMERATED {supported} OPTIONAL, -- R1 25-13: UE initiated semi-static channel occupancy with independent configurations ul-Semi-StaticChAccessIndependentConfig-r17 ENUMERATED {supported} OPTIONAL } -- TAG-SHAREDSPECTRUMCHACCESSPARAMSPERBAND-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
4,056 | 4.2.8.3.2 Requirements on Ta | Ta shall be able to - Carry EAP-5G traffic and user location information before the NWt connection is established between the UE and the TNGF. - Allow the UE and the TNGF to exchange IP traffic. In deployments where the TNAP does not allocate the local IP addresses to UE(s), Ta shall be able to: - Allow the UE to request and receive IP configuration from the TNAN (including a local IP address), e.g. with DHCP. This is to allow the UE to use an IP stack to establish a NWt connection between the UE and the TNGF. NOTE: The "local IP address" is the IP address that allows the UE to contact the TNGF; the entity providing this local IP address is part of TNAN and out of 3GPP scope In this Release of the specification, Ta is not specified. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2.8.3.2 |
4,057 | 4.3.1.1 Common MR-DC principles | In MR-DC, there is an interface between the MN and the SN for control plane signalling and coordination. For each MR-DC UE, there is also one control plane connection between the MN and a corresponding CN entity. The MN and the SN involved in MR-DC for a certain UE control their radio resources and are primarily responsible for allocating radio resources of their cells. Figure 4.3.1.1-1 shows C-plane connectivity of MN and SN involved in MR-DC for a certain UE. Figure 4.3.1.1-1: C-Plane connectivity for EN-DC (left) and MR-DC with 5GC (right). | 3GPP TS 37.340 | Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 | RAN2 | 3GPP Series : 37 , Multiple radio access technology aspects | 4.3.1.1 |
4,058 | 5.2.6.33.2 Nnef_AF_request_for_QoS_Create service operation | Service operation name: Nnef_AF_request_for_QoS Create Description: The consumer requests the network to provide a specific QoS for a traffic flow for a UE or a group of UEs. Inputs, Required: AF Identifier, Target UE identifier (GPSI or External Group Identifier), Flow description(s) or External Application Identifier, QoS Reference or individual QoS parameters as described in clause 6.1.3.22 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. Inputs, Optional: time period, traffic volume, Alternative Service Requirements (containing one or more QoS reference parameters or Requested Alternative QoS Parameter Sets in a prioritized order), QoS parameter(s) to be measured, Reporting frequency, Target of reporting and optional an indication of local event notification as described in clause 6.1.3.21 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20], DNN if available, S-NSSAI if available, traffic characteristics as described in clause 6.1.3.23 or 6.1.3.23a of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. Outputs, Required: Transaction Reference ID, result. Output (optional): None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.6.33.2 |
4,059 | 4.7.2.9 Power saving mode | The MS can request the use of power saving mode (PSM) during an attach or routing area updating procedures (see 3GPP TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [133A] and 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [74]). The MS shall not request the use of PSM during: - an attach for emergency bearer services procedure; - a routing area updating procedure for initiating a PDN connection for emergency bearer services; or - a routing area updating procedure when the MS has a PDN connection established for emergency bearer services. The network accepts the use of PSM by providing a specific value for timer T3324 when accepting the attach or routing area updating procedure. The MS may use PSM only if the network has provided the T3324 value IE during the last attach or routing area updating procedure with a value different from "deactivated". Upon expiry of the timer T3324 or if the T3324 value provided by the network is zero, the MS may deactivate the AS layer and activate PSM by entering the state GMM-REGISTERED.NO-CELL-AVAILABLE if: a) the MS is not attached for emergency bearer services; b) the MS has no PDN connection for emergency bearer services; c) the MS is in PMM-IDLE mode (in Iu mode) or the READY timer is not running (in A/Gb mode); d) the MS is in the GMM-REGISTERED.NORMAL-SERVICE state; and e) no RR connection exists. If conditions a, b, c and e are fulfilled, but the MS is in a state other than GMM-REGISTERED.NORMAL-SERVICE when timer T3324 expires, the MS may activate PSM when the MS returns to state GMM-REGISTERED.NORMAL-SERVICE. If conditions a, b, c and d are fulfilled, but an RR connection exists, the MS may activate PSM when the RR connection has been released. An MS that has already been allocated timer T3324 with a value different from "deactivated" and the timer T3324 has expired, may activate PSM if it receives an "Extended wait time" from lower layers. When PSM is activated all NAS timers are stopped and associated procedures aborted except for timers T3312, T3346, T3396, any backoff timers, and the timer T controlling the periodic search for HPLMN or EHPLMN (if the EHPLMN list is present) or higher prioritized PLMNs (see 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14]). If the MS is attached for emergency bearer services or has a PDN connection for emergency bearer services, the MS shall not activate PSM. The MS may deactivate PSM at any time (e.g. for transfer of mobile originated signalling or user data, or to initiate a mobile originated circuit-switched transaction), by activating the AS layer before initiating the necessary GMM or MM procedures (if any). | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.2.9 |
4,060 | β VarConditionalReconfig | The UE variable VarConditionalReconfig includes the accumulated configuration of the conditional handover, conditional PSCell addition or conditional PSCell change configurations including the pointers to conditional handover, conditional PSCell addition, conditional PSCell change, or subsequent CPAC execution condition (associated measId(s)), the stored target candidate SpCell RRCReconfiguration, the stored reference configuration, and the stored SK-Counter configuration. VarConditionalReconfig UE variable -- ASN1START -- TAG-VARCONDITIONALRECONFIG-START VarConditionalReconfig ::= SEQUENCE { condReconfigList CondReconfigToAddModList-r16 OPTIONAL, scpac-ReferenceConfiguration-r18 ReferenceConfiguration-r18 OPTIONAL, sk-CounterConfiguration-r18 SK-CounterConfiguration-r18 OPTIONAL } -- TAG-VARCONDITIONALRECONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
4,061 | 5.3.20 UE radio capability signalling optimisation | UE radio capability signalling optimisation (RACS) is a feature that is optional at both the UE and the network and which aims to optimise the transmission of UE radio capability over the radio interface (see 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10]). RACS works by assigning an identifier to represent a set of UE radio capabilities. This identifier is called the UE radio capability ID. A UE radio capability ID can be either manufacturer-assigned or network-assigned. The UE radio capability ID is an alternative to the signalling of the radio capabilities container over the radio interface. In this release of the specification, RACS is not applicable to NB-S1 mode. If the UE supports RACS: - the UE shall indicate support for RACS by setting the RACS bit to "RACS supported" in the UE network capability IE of the ATTACH REQUEST and TRACKING AREA UPDATE REQUEST messages; - if the UE performs an attach procedure and the UE has an applicable UE radio capability ID for the current UE radio configuration in the selected network, the UE shall include the UE radio capability ID availability IE in the ATTACH REQUEST message and set the IE to "UE radio capability ID available"; - if the UE performs a tracking area updating procedure and the UE has an applicable UE radio capability ID for the current UE radio configuration in the selected network, the UE shall include the UE radio capability ID availability IE in the TRACKING AREA UPDATE REQUEST message and set the IE to "UE radio capability ID available"; - If the UE is requested to provide the UE radio capability ID by the network during a security mode control procedure, the UE shall include the UE radio capability ID in the UE radio capability ID IE of the SECURITY MODE COMPLETE message according to the rules in clause 5.4.3.3.; - if the radio configuration at the UE changes (for instance because the UE has disabled a specific radio capability) then: a) if the UE has an applicable UE radio capability ID for the new UE radio configuration, the UE shall initiate a tracking area updating procedure, include a UE radio capability information update needed IE in the TRACKING AREA UPDATE REQUEST message and set the URCIDA bit to "UE radio capability ID available" in the UE radio capability ID availability IE in the TRACKING AREA UPDATE REQUEST message; and b) if the UE does not have an applicable UE radio capability ID for the new UE radio configuration, the UE shall initiate a tracking area updating procedure and shall include a UE radio capability information update needed IE in the TRACKING AREA UPDATE REQUEST message; NOTE: Performing the tracking area updating procedure with the UE radio capability information update needed IE included in the TRACKING AREA UPDATE REQUEST message and without the UE radio capability ID availability IE set to "UE radio capability ID available" in the TRACKING AREA UPDATE REQUEST message as specified in b) above can trigger the network to assign a new UE radio capability ID to the UE. - upon receiving a network-assigned UE radio capability ID in the ATTACH ACCEPT message, in the TRACKING AREA UPDATE ACCEPT message or in the GUTI REALLOCATION COMMAND message, the UE shall store the network-assigned UE radio capability ID and the PLMN ID of the serving network along with a mapping to the current UE radio configuration in its non-volatile memory as specified in annex C. The UE shall be able to store at least the last 16 received network-assigned UE radio capability IDs with the associated PLMN ID and the mapping to the corresponding UE radio configuration; - the UE shall not use a network-assigned UE radio capability ID in PLMNs equivalent to the PLMN which assigned it; and - upon receiving a UE radio capability ID deletion indication IE set to "Network-assigned UE radio capability IDs deletion requested" in the ATTACH ACCEPT message, in the TRACKING AREA UPDATE ACCEPT message or in the GUTI REALLOCATION COMMAND message, the UE shall delete all network-assigned UE radio capability IDs stored at the UE for the serving network and initiate a tracking area updating procedure. If the UE has an applicable manufacturer-assigned UE radio capability ID for the current UE radio configuration in the selected network, the UE shall include a UE radio capability ID availability IE set to "UE radio capability ID available" in the TRACKING AREA UPDATE REQUEST message. If the network supports RACS: - if the UE has included the UE radio capability ID availability IE in the ATTACH REQUEST message and set the IE to "UE radio capability ID available", the network shall initiate a security mode control procedure to retrieve the UE radio capability ID from the UE; - if the UE has included the UE radio capability ID availability IE in the TRACKING AREA UPDATE REQUEST message and set the IE to "UE radio capability ID available", the network may initiate a security mode control procedure to retrieve the UE radio capability ID from the UE; - if the UE has included the UE radio capability ID availability IE in the TRACKING AREA UPDATE REQUEST message, set the URCIDA bit to "UE radio capability ID available" in the UE radio capability ID availability IE and no UE radio capability ID is available in the UE context in the MME, the network shall initiate a security mode control procedure to retrieve the UE radio capability ID from the UE; - the network may assign a network-assigned UE radio capability ID to a UE which supports RACS by including a UE radio capability ID IE in the ATTACH ACCEPT message, in the TRACKING AREA UPDATE ACCEPT message or in the GUTI REALLOCATION COMMAND message; and - the network may trigger the UE to delete all network-assigned UE radio capability IDs stored at the UE for the serving network by including a UE radio capability ID deletion indication IE set to "Network-assigned UE radio capability IDs deletion requested" in the ATTACH ACCEPT message, in the TRACKING AREA UPDATE ACCEPT message or in the GUTI REALLOCATION COMMAND message. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.3.20 |
4,062 | 5.2.1.9 Traffic channel assignment at mobile originating call establishment | The mobile station supporting multicall includes the Stream Identifier (SI) in the SETUP message. The multicall supporting network shall interprets the SI value as follows: a) Mobile station generates a new SI value at the initiation of an originating call, then a new traffic channel shall be assigned to the mobile originating call. b) Mobile station indicates an existing SI value, then the indicated traffic channel shall be used for the mobile originating call. Mobile station supporting multicall shall never send an additional SETUP with indication that a new traffic channel is requested to a network that does not support multicall. It is a network dependent decision when to initiate the assignment of an appropriate traffic channel during the mobile originating call establishment phase. Initiation of a suitable RR procedure to assign an appropriate traffic channel does neither change the state of a call control entity nor affect any call control timer. NOTE: During certain phases of such an RR procedure, transmission of CC and MM messages may be suspended, see 3GPP TS 44.018[ None ] [84], clause 3 and 3GPP TS 48.008[ None ] [85]. The assignment procedure does not affect any call control timer. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.2.1.9 |
4,063 | 9.3.28 Status enquiry | This message is sent by the mobile station or the network at any time to solicit a STATUS message from the peer layer 3 entity. Sending of STATUS message in response to a STATUS ENQUIRY message is mandatory. See table 9.75/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Message type: STATUS ENQUIRY Significance: local Direction: both Table 9.75/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : STATUS ENQUIRY message content | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.3.28 |
4,064 | 4.16.2.1.2 AM Policy Association Modification with old PCF during AMF relocation | This procedure is applicable to Case C. In this case, AMF relocation is performed without PCF change in handover procedure and registration procedure. Figure 4.16.2.1.2-1: AM Policy Association Modification with the old PCF during AMF relocation This procedure concerns both roaming and non-roaming scenarios. In the non-roaming case the role of the V-PCF is performed by the PCF. For the roaming scenarios, the V-PCF interacts with the AMF: 1. [Conditional] When the old AMF and the new AMF belong to the same PLMN, the old AMF transfers to the new AMF the AM Policy Association information including Policy Control Request Trigger(s) and the PCF ID. For the roaming case, the new AMF receives V-PCF ID. 2. Based on local policies, the new AMF decides to establish an AM Policy Association with the (V-)PCF and contacts the (V-)PCF identified by the PCF ID received in step 1. 3. The new AMF sends Npcf_AMPolicyControl_Update to the (V-)PCF to update the AM Policy Association with the (V-)PCF. The request may include the following information: Policy Control Request Trigger which has been met, Subscribed Service Area Restrictions (if updated), subscribed RFSP index (if updated) which are retrieved from the UDM during the update location procedure and may include access type and RAT, PEI, ULI, UE time zone, service network. The (V-)PCF updates the stored information provided by the old AMF with the information provided by the new AMF. In the non-roaming case, the PCF may subscribe to Analytics from NWDAF as defined in clause 6.1.1.3 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. If the PCF determines a change to policy counter status reporting is required, it may alter the subscribed list of policy counters using the Initial, Intermediate or Final Spending Limit Report Retrieval procedures as defined in clause 4.16.8. When AMF utilizes an NWDAF, it may add the NWDAF serving the UE identified by the NWDAF instance ID. Per NWDAF service instance the Analytics ID(s) are also included. 4. The (V-)PCF may update the policy decision based on the information provided by the new AMF and responds to the Npcf_AMPolicyControl_Update service operation providing access and mobility related policy information as defined in clause 6.5 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. If an AF has previously subscribed to request for allocation of service area coverage outcome event the (V-)PCF checks if reporting is needed, using the Policy Control Request Trigger that was met (see step 1) as input, then sends a respective notification to the AF using Npcf_AMPolicyAuthorization_Notify, as defined in clause 6.1.3.18 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. 5. The AMF deploys the access and mobility related policy information, which includes storing the Service Area Restrictions, provisioning Service Area Restrictions to the UE and provisioning the RFSP index, UE-AMBR, Service Area Restrictions to the NG-RAN and request for notification of SM Policy association establishment and termination to a list of (DNN, S-NSSAI)(s) together with PCF for the UE binding information. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.16.2.1.2 |
4,065 | 5.3.5.17.2.3 T421 expiry (Indirect path addition/change failure) | The UE shall: 1> if T421 expires; or 1> if the (target) L2 U2N Relay UE (i.e., the UE indicated by sl-IndirectPathRelayUE-Identity in the received sl-IndirectPathAddChange) changes its serving PCell to a different cell from the target cell (i.e. the cell indicated by sl-IndirectPathCellIdentity in the received sl-IndirectPathAddChange) before path addition or change: 2> if MCG transmission is not suspended: 3> initiate the indirect path failure information procedure as specified in clause 5.7.3c to report indirect path addition/change failure; 2> else: 3> initiate the connection re-establishment procedure as specified in clause 5.3.7; | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.5.17.2.3 |
4,066 | 6.3.5A.1 Absolute power tolerance | The absolute power tolerance is the ability of the UE transmitter to set its initial output power to a specific value for the first sub-frame at the start of a contiguous transmission or non-contiguous transmission with a transmission gap on each active component carriers larger than 20ms. For component carriers with Frame Structure Type 3 the absolute power toerlance requirements apply when the said transmission gaps are larger than 40 ms. The requirement can be tested by time aligning any transmission gaps on the component carriers. When SRS carrier based switching is used, then the above mentioned absolute power tolerance is the ability of the UE transmitter to set its initial output power to a specific value for the first sub-frame at the start of a contiguous transmission or non-contiguous transmission with a transmission gap on component carriers (to which SRS switching occurs) larger than 40ms. | 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.3.5A.1 |
4,067 | β SL-RelayUE-ConfigU2U | The IE SL-RelayUE-ConfigU2U specifies the threshold configuration information for NR sidelink U2U Relay UE. SL-RelayUE-ConfigU2U information element -- ASN1START -- TAG-SL-RELAYUE-CONFIGU2U-START SL-RelayUE-ConfigU2U-r18::= SEQUENCE { sl-RSRP-Thresh-DiscConfig-r18 SL-RSRP-Range-r16 OPTIONAL, -- Need R sl-hystMaxRelay-r18 Hysteresis OPTIONAL, -- Cond SL-RSRP-ThreshRelay sd-RSRP-Thresh-DiscConfig-r18 SL-RSRP-Range-r16 OPTIONAL, -- Need R sd-hystMaxRelay-r18 Hysteresis OPTIONAL -- Cond SD-RSRP-ThreshRelay } -- TAG-SL-RELAYUE-CONFIGU2U-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
4,068 | 5.6.1.4.2 UE is using 5GS services with control plane CIoT 5GS optimization | For case a in subclause 5.6.1.1, upon receipt of the CONTROL PLANE SERVICE REQUEST message with Control plane service type indicating "mobile terminating request", after completion of the 5GMM common procedures (if initiated) according to subclause 5.6.1.3, the AMF shall send a SERVICE ACCEPT message. For cases c, d and m in subclause 5.6.1.1, upon receipt of the CONTROL PLANE SERVICE REQUEST message with Control plane service type indicating "mobile originating request", after completion of the 5GMM common procedures (if initiated) according to subclause 5.6.1.3, the AMF shall send a SERVICE ACCEPT message, except for case d when the DDX field of the Release assistance indication IE or the DDX field of the CIoT small data container IE indicates "No further uplink and no further downlink data transmission subsequent to the uplink data transmission is expected". For case a, c and d: a) if the CIoT small data container IE is included in the message, the AMF shall decipher the value part of the CIoT small data container IE and: 1) if the Data type field indicates "control plane user data", extract the PDU session ID and data content from the CIoT small data container IE, look up a PDU session routing context for the UE and the PDU session ID, and forward the content of the CIoT small data container IE to the SMF associated with the UE. If the corresponding PDU session is a PDU session for LADN, the AMF determines the UE presence in LADN service area (see subclause 6.2.6) and forwards the UE presence in LADN service area towards the SMF; 2) if the Data type field indicates "SMS", forward the content of the CIoT small data container IE to the SMSF associated with the UE; or 3) if the Data type field indicates "Location services message container", and if i) length of additional information field in the CIoT small data container IE is zero, forward the value of Data type field and the content of the CIoT small data container IE to the to the location services application; or ii) otherwise forward the value of Data type field and the content of the CIoT small data container IE to the LMF associated with the routing information that is included in the additional information field of the CIoT small data container IE; or NOTE 1: If the AMF determines there is no pending data or signalling for the UE, the AMF provides an indication of control plane CIoT 5GS Optimisation to the LMF as specified in 3GPP TS 29.518[ 5G System; Access and Mobility Management Services; Stage 3 ] [20B]. b) otherwise, the AMF shall decipher the value part of NAS message container IE and: 1) if the Payload container IE is included in the CONTROL PLANE SERVICE REQUEST message and if the Payload container type IE is set to "CIoT user data container", the AMF shall look up a PDU session routing context for the UE and the PDU session ID, and forward the content of the Payload container IE to the SMF associated with the UE. If the corresponding PDU session is a PDU session for LADN, the AMF determines the UE presence in LADN service area (see subclause 6.2.6) and forwards the UE presence in LADN service area towards the SMF; 2) if the Payload container IE is included in the CONTROL PLANE SERVICE REQUEST message and if the Payload container type IE is set to "SMS", the AMF shall forward the content of the Payload container IE to the SMSF associated with the UE; 3) if the PDU session status IE is included in the CONTROL PLANE SERVICE REQUEST message or the AMF needs to perform a PDU session status synchronization, the AMF shall include a PDU session status IE in the SERVICE ACCEPT message to indicate which PDU sessions associated with the access type the SERVICE ACCEPT message is sent over are active in the AMF; 4) if the Uplink data status IE is included in the CONTROL PLANE SERVICE REQUEST message and the UE is: i) not in NB-N1 mode; or ii) in NB-N1 mode and the UE does not indicate a request to have user-plane resources established for a number of PDU sessions that exceeds the UE's maximum number of supported user-plane resources; the AMF shall: i) indicate the SMF to re-establish the user-plane resources for the corresponding PDU sessions; and ii) include the PDU session reactivation result IE in the SERVICE ACCEPT message to indicate the user-plane resources re-establishment result of the PDU sessions for which the UE requested to re-establish the user-plane resources; 5) if the Uplink data status IE is included in the CONTROL PLANE SERVICE REQUEST, the UE is in NB-N1 mode, and the UE indicates a request to have user-plane resources established for a number of PDU sessions that exceeds the UE's maximum number of supported user-plane resources, the AMF shall not indicate to the SMF to re-establish the user-plane resources for the corresponding PDU sessions; or 6) otherwise, if the Payload container IE is included in the message and if the Payload container type IE is set to "Location services message container", the AMF shall forward the Payload container type and the content of the Payload container IE to the LMF associated with the routing information included in the Additional information IE of the CONTROL PLANE SERVICE REQUEST message. NOTE 2: If the AMF determines there is no pending data or signalling for the UE, the AMF provides an indication of control plane CIoT 5GS Optimisation to the LMF as specified in 3GPP TS 29.518[ 5G System; Access and Mobility Management Services; Stage 3 ] [20B]. For case k) in subclause 5.6.1.1, if the Uplink data status IE is included in the CONTROL PLANE SERVICE REQUEST message and the UE is: a) not in NB-N1 mode; or b) in NB-N1 mode and the UE does not indicate a request to have user-plane resources established for a number of PDU sessions that exceeds the UE's maximum number of supported user-plane resources, the AMF shall: a) indicate the SMF to re-establish the user-plane resources for the corresponding PDU sessions; and b) include the PDU session reactivation result IE in the SERVICE ACCEPT message to indicate the user-plane resources re-establishment result of the PDU sessions for which the UE requested to re-establish the user-plane resources. If the Allowed PDU session status IE is included in the CONTROL PLANE SERVICE REQUEST message, the AMF shall: a) for a 5GSM message from each SMF that has indicated pending downlink signalling only, forward the received 5GSM message via 3GPP access to the UE after the SERVICE ACCEPT message is sent; b) for each SMF that has indicated pending downlink data only: 1) notify the SMF that reactivation of the user-plane resources for the corresponding PDU session(s) associated with non-3GPP access cannot be performed if the corresponding PDU session ID(s) are not indicated in the Allowed PDU session status IE; and 2) notify the SMF that reactivation of the user-plane resources for the corresponding PDU session(s) associated with non-3GPP access can be performed if: i) for a UE not in NB-N1 mode, the corresponding PDU session ID(s) are indicated in the Allowed PDU session status IE; or ii) for a UE in NB-N1 mode, the corresponding PDU session ID(s) are indicated in the Allowed PDU session status IE and the resulting number of PDU sessions with established user-plane resources does not exceed the UE's maximum number of supported user-plane resources; c) for each SMF that have indicated pending downlink signalling and data: 1) notify the SMF that reactivation of the user-plane resources for the corresponding PDU session(s) associated with non-3GPP access cannot be performed if the corresponding PDU session ID(s) are not indicated in the Allowed PDU session status IE; 2) notify the SMF that reactivation of the user-plane resources for the corresponding PDU session(s) associated with non-3GPP access can be performed if: i) for a UE not in NB-N1 mode, the corresponding PDU session ID(s) are indicated in the Allowed PDU session status IE; or ii) for a UE in NB-N1 mode, the corresponding PDU session ID(s) are indicated in the Allowed PDU session status IE and the resulting number of PDU sessions with established user-plane resources does not exceed the UE's maximum number of supported user-plane resources; and 3) discard the received 5GSM message for PDU session(s) associated with non-3GPP access; and d) include the PDU session reactivation result IE in the SERVICE ACCEPT message to indicate the successfully re-established user-plane resources for the corresponding PDU sessions, if any. If the DDX field in the CIoT small data container IE or the DDX field of the Release assistance indication IE indicates: 1) "No further uplink and no further downlink data transmission subsequent to the uplink data transmission is expected" and if there is no downlink signalling or downlink data for the UE; or 2) "Only a single downlink data transmission and no further uplink data transmission subsequent to the uplink data transmission is expected" and upon subsequent delivery of the next received downlink data transmission to the UE and if there is no additional downlink signalling or downlink data for the UE, the AMF initiates the release of the N1 NAS signalling connection (see 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9]). If the MUSIM UE does not include the Paging restriction IE in the CONTROL PLANE SERVICE REQUEST message, the AMF shall delete any stored paging restriction for the UE and stop restricting paging. For case m in subclause 5.6.1.1 when the MUSIM UE sets the Request type to "NAS signalling connection release" in the CONTROL PLANE SERVICE REQUEST message, the AMF shall initiate the release of the N1 NAS signalling connection after the completion of the service request procedure. For cases o and p in subclause 5.6.1.1 when the MUSIM UE sets the Request type to "NAS signalling connection release" or to "Rejection of paging" in the UE request type IE in the CONTROL PLANE SERVICE REQUEST message and if the UE requests restriction of paging by including the Paging restriction IE, the AMF: - if accepts the paging restriction, shall include the 5GS additional request result IE in the SERVICE ACCEPT message and set the Paging restriction decision to "paging restriction is accepted". The AMF shall store the paging restriction of the UE and enforce these restrictions in the paging procedure as described in subclause 5.6.2; or - if rejects the paging restriction, shall include the 5GS additional request result IE in the SERVICE ACCEPT message and set the Paging restriction decision to "paging restriction is rejected", and shall discard the received paging restriction. The AMF shall delete any stored paging restriction for the UE and stop restricting paging; and the AMF shall send the SERVICE ACCEPT message and initiate the release of the N1 NAS signalling connection as follows: - for case o in subclause 5.6.1.1, after the completion of the service request procedure; - for case p in subclause 5.6.1.1, after the completion of the generic UE configuration update procedure that is triggered after the completion of the service request procedure. Upon successful completion of the procedure, the UE shall reset the service request attempt counter, stop the timer T3517 and enter the state 5GMM-REGISTERED. If the PDU session status information element is included in the CONTROL PLANE SERVICE REQUEST message, then the AMF: a) shall perform a local release of all those PDU sessions which are not in 5GSM state PDU SESSION INACTIVE on the AMF side associated with the access type the CONTROL PLANE SERVICE REQUEST message is sent over, but are indicated by the UE as being inactive, and b) request the SMF to perform a local release of all those PDU sessions. If any of those PDU sessions is associated with one or more multicast MBS sessions, the SMF shall consider the UE as removed from the associated multicast MBS sessions. If the PDU session status information element is included in the SERVICE ACCEPT message, then the UE shall perform a local release of all those PDU sessions which are not in 5GSM state PDU SESSION INACTIVE or PDU SESSION ACTIVE PENDING on the UE side associated with the 3GPP access but are indicated by the AMF as being inactive. If a locally released PDU session: a) is associated with one or more multicast MBS sessions, the UE shall locally leave the associated multicast MBS sessions; or b) has the same PDU session identity value as that used by the UE in the CONTROL PLANE SERVICE REQUEST message, and the message contained CIoT user data, then the UE determines that the CIoT user data was not successfully sent. If the user-plane resources cannot be established for a PDU session, the AMF shall include the PDU session reactivation result IE in the SERVICE ACCEPT message indicating that user-plane resources for the corresponding PDU session cannot be re-established, and: a) if the user-plane resources cannot be established because the SMF indicated to the AMF that the UE is located out of the LADN service area (see 3GPP TS 29.502[ 5G System; Session Management Services; Stage 3 ] [20A]), the AMF shall include the PDU session reactivation result error cause IE with the 5GMM cause set to #43 "LADN not available"; b) if the user-plane resources cannot be established because the SMF indicated to the AMF that only prioritized services are allowed (see 3GPP TS 29.502[ 5G System; Session Management Services; Stage 3 ] [20A]), the AMF shall include the PDU session reactivation result error cause IE with the 5GMM cause set to #28 "restricted service area"; or c) if the user-plane resources cannot be established because: 1) the SMF indicated to the AMF that the resource is not available in the UPF (see 3GPP TS 29.502[ 5G System; Session Management Services; Stage 3 ] [20A]); or 2) the UE is in NB-N1 mode and the result will lead to user-plane resources established for more than two PDU sessions (see 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9]) the AMF shall include the PDU session reactivation result error cause IE with the 5GMM cause set to #92 "insufficient user-plane resources for the PDU session": NOTE 3: For a UE that is not in NB-N1 mode, it is up to UE implementation when to re-send a request for user-plane re-establishment for the associated PDU session after receiving a PDU session reactivation result error cause IE with a 5GMM cause set to #92 "insufficient user-plane resources for the PDU session". For case a and b, - if the AMF has a service area list or LADN information which is applicable to the current TAI of the UE and was not yet provided to the UE, before sending the SERVICE ACCEPT message the AMF shall initiate the generic UE configuration update procedure and include the service area list or LADN information or both in the CONFIGURATION UPDATE COMMAND message; and - if timer T3540 is not started (see subclause 5.3.1.3, item f), and the UE did not receive a CONFIGURATION UPDATE COMMAND message during the service request procedure, the UE may initiate a registration procedure for mobility or periodic registration update. If timer T3540 is started and the UE does not receive a CONFIGURATION UPDATE COMMAND message before the established N1 NAS signalling connection is released by the network or timer T3540 expires or is stopped as specified in subclause 5.3.1.3, the UE may initiate the registration procedure for mobility or periodic registration update upon release of the N1 NAS signalling connection. If the PDU session reactivation result IE is included in the SERVICE ACCEPT message indicating that the user-plane resources cannot be established for a PDU session that was indicated by the UE in the Allowed PDU session status IE as allowed to be re-established over 3GPP access, the UE considers the corresponding PDU session to be associated with the non-3GPP access. For case d) in subclause 5.6.1.1, the UE shall also treat the indication from the lower layers that the RRC connection has been released as successful completion of the procedure. The UE shall reset the service request attempt counter, stop the timer T3517 and enter the state 5GMM-REGISTERED. Upon receipt of the CONTROL PLANE SERVICE REQUEST message with uplink data: - if the DDX field of the Release assistance indication IE or the DDX field of the CIoT small data container IE is set to "No further uplink and no further downlink data transmission subsequent to the uplink data transmission is expected" in the message; - if the AMF decides to forward the uplink data piggybacked in the CONTROL PLANE SERVICE REQUEST message; and - if the AMF decides to activate the congestion control for transport of user data via the control plane, then the AMF shall send SERVICE ACCEPT message with the T3448 value IE included. If the AMF decides to deactivate the congestion control for transport of user data via the control plane, then the AMF shall delete the stored control plane data back-off time for the UE and the AMF shall not include timer T3448 value IE in the SERVICE ACCEPT message. If the T3448 value IE is present in the received SERVICE ACCEPT message and the value indicates that this timer is neither zero nor deactivated, the UE shall: a) stop timer T3448 if it is running; b) consider the transport of user data via the control plane as successful; and c) start timer T3448 with the value provided in the T3448 value IE. If the UE is using 5GS services with control plane CIoT 5GS optimization, the T3448 value IE is present in the SERVICE ACCEPT message and the value indicates that this timer is either zero or deactivated, the UE shall ignore the T3448 value IE and proceed as if the T3448 value IE was not present. If the UE in 5GMM-IDLE mode initiated the service request procedure by sending a CONTROL PLANE SERVICE REQUEST message and the SERVICE ACCEPT message does not include the T3448 value IE and if timer T3448 is running, then the UE shall stop timer T3448. For case h) in subclause 5.6.1.1, a) the UE shall treat the indication from the lower layers when the UE has changed to S1 mode as successful completion of the procedure and stop timer T3517; b) if a UE operating in single-registration mode has changed to S1 mode, it shall disable the N1 mode capability for 3GPP access (see subclause 4.9.2); and c) the AMF shall not check for CAG restrictions. If the CONTROL PLANE SERVICE REQUEST message is for emergency services fallback, the AMF triggers the emergency services fallback procedure as specified in subclause 4.13.4.2 of 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9]. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.6.1.4.2 |
4,069 | 8.2.28.1 Message definition | This message is sent by the UE or the network to transfer a plain 5GS NAS message as specified in subclause 8.2 together with the sequence number and the message authentication code protecting the message. See table 8.2.28.1.1. Message type: SECURITY PROTECTED 5GS NAS MESSAGE Significance: dual Direction: both Table 8.2.28.1.1: SECURITY PROTECTED 5GS NAS MESSAGE message content NOTE: The minimum length of Plain 5GS NAS message IE can be 2 octets if it includes a Test Mode Control message specified in 3GPP TS 38.509[ 5GS; Special conformance testing functions for User Equipment (UE) ] [31AA]. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 8.2.28.1 |
4,070 | 13.8 Instance-ID | An instance-id is a SIP Contact header parameter that uniquely identifies the SIP UA performing a registration. When an IMEI is available, the instance-id shall take the form of a IMEI URN (see RFC 7254 [79]). The format of the instance-id shall take the form "urn:gsma:imei:<imeival>" where by the imeival shall contain the IMEI encoded as defined in RFC 7254 [79]. The optional <sw-version-param> and <imei-version-param> parameters shall not be included in the instance-id. RFC 7255 [104] specifies additional considerations for using the IMEI as an instance-id. An example of such an instance-id is as follows: EXAMPLE: urn:gsma:imei:90420156-025763-0 If no IMEI is available, the instance-id shall take the form of a string representation of a UUID as a URN as defined in IETF RFC 4122 [80]. An example of such an instance-id is as follows: EXAMPLE: urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6 For more information on the instance-id and when it is used, see 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [81]. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 13.8 |
4,071 | 6.1.3.1 Buffer Status Report MAC Control Elements | Buffer Status Report (BSR) MAC control elements consist of either: - Short BSR and Truncated BSR format: one LCG ID field and one corresponding Buffer Size field (figure 6.1.3.1-1); or - Long BSR format: four Buffer Size fields, corresponding to LCG IDs #0 through #3 (figure 6.1.3.1-2). The BSR formats are identified by MAC PDU subheaders with LCIDs as specified in table 6.2.1-2. The fields LCG ID and Buffer Size are defined as follow: - LCG ID: The Logical Channel Group ID field identifies the group of logical channel(s) which buffer status is being reported. The length of the field is 2 bits. For NB-IoT, the LCG ID is set to #0. - Buffer Size: The Buffer Size field identifies the total amount of data available across all logical channels of a logical channel group after all MAC PDUs for the TTI have been built. The amount of data is indicated in number of bytes. It shall include all data that is available for transmission in the RLC layer and in the PDCP layer; the definition of what data shall be considered as available for transmission is specified in TS 36.322[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Link Control (RLC) protocol specification ] [3] and TS 36.323[ Evolved Universal Terrestrial Radio Access (E-UTRA); Packet Data Convergence Protocol (PDCP) specification ] [4] or TS 38.323[ NR; Packet Data Convergence Protocol (PDCP) specification ] [17] respectively. The size of the RLC and MAC headers are not considered in the buffer size computation. The length of this field is 6 bits. If extendedBSR-Sizes is not configured, the values taken by the Buffer Size field are shown in Table 6.1.3.1-1. If extendedBSR-Sizes is configured, the values taken by the Buffer Size field are shown in Table 6.1.3.1-2. Figure 6.1.3.1-1: Short BSR and Truncated BSR MAC control element Figure 6.1.3.1-2: Long BSR MAC control element Table 6.1.3.1-1: Buffer size levels for BSR Table 6.1.3.1-2: Extended Buffer size levels for BSR | 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.1 |
4,072 | 6.1.3.14 Activation/Deactivation of CSI-RS resources MAC Control Element | The Activation/Deactivation of CSI-RS resources MAC control element is identified by a MAC PDU subheader with LCID as specified in table 6.2.1-1. It has variable size as the number of CSI process configured with csi-RS-NZP-Activation by RRC, see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8], (N) and the N number of octets with A fields are included in ascending order of CSI process ID, i.e., CSI-ProcessId, as defined in Figure 6.1.3.14-1. Activation/Deactivation CSI-RS command is defined in Figure 6.1.3.14-2 and activates or deactivates CSI-RS resources for a CSI process. For a UE configured with transmission mode 9, N equals 1. Activation/Deactivation of CSI-RS resources MAC control element applies to the serving cell on which the UE receives the Activation/Deactivation of CSI-RS resources MAC control element. The Activation/Deactivation of CSI-RS resources MAC control elements is defined as follows: - Ai: this field indicates the activation/deactivation status of the CSI-RS resources configured by upper layers for the CSI process. A1 corresponds to the 1st entry in the list of CSI-RS specified by csi-RS-ConfigNZP-ApList as configured by upper layers, A2 corresponds to the 2nd entry in this list and so on. The Ai field is set to "1" to indicate that ith entry in the list of CSI-RS specified by csi-RS-ConfigNZP-ApList shall be activated. The Ai field is set to "0" to indicate that ith entry in the list shall be deactivated. For each CSI process, the number of Ai fields (i=1, 2,β¦, 8) which are set to "1" shall be equal to the value of the higher-layer parameter activatedResources in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]. Figure 6.1.3.14-1: Activation/Deactivation of CSI-RS resources MAC Control Element Figure 6.1.3.14-2: Activation/Deactivation CSI-RS command | 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.14 |
4,073 | 13.2.2 Principles | The following principles shall apply if this procedure is supported and enabled by operator policy. A GTP-C entity originating a Create Session Request (i.e. MME, SGSN, TWAN or ePDG) shall include in the message the Origination Time Stamp indicating the absolute time at which the request is initiated. The SGW shall forward this parameter over the S5/S8 interface, if it is received from the MME/SGSN. Upon receipt of a session establishment request which collides with an existing session context, the PGW shall accept the new session establishment request only if it contains a more recent time stamp than the time stamp stored for the existing session. An incoming session request shall be considered as more recent than an existing session and be accepted if no Origination Time Stamp information was provided for at least one of the two sessions. The PGW shall reject an incoming request whose time stamp is less recent than the time stamp of the existing session with the cause 'Late Overlapping Request'. 3GPP TS 29.212[ Policy and Charging Control (PCC); Reference points ] [29] and 3GPP TS 29.273[ Evolved Packet System (EPS); 3GPP EPS AAA interfaces ] [68] further specify: - the PGW requirements regarding the forwarding of the Origination Time Stamp parameter over the Gx and/or S6b interfaces, when received from the SGW or TWAN/ePDG; - the handling of the Origination Time Stamp parameter by the PCRF and 3GPP AAA Server for an incoming request colliding with an existing session context. An originating entity which detects a NTP failure shall not include the Origination Time Stamp towards other entities. | 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 | 13.2.2 |
4,074 | Annex M (normative): Security for Integrated Access and Backhaul (IAB) M.1 General | This Annex provides the security procedures applied to NR IAB architecture and functional entities for supporting wireless backhauling of NR base stations. The overall stage 2 description for IAB architecture and functional entities are described in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [2] and 3GPP TS 38.401[ NG-RAN; Architecture description ] [78]. The security requirements and security procedures applied to IAB in EN-DC architecture are defined in both TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [10] and in the present document. The security requirements and security procedures between the IAB-node and the MeNB (i.e., when the IAB-node connects via E-UTRA to a MeNB), are defined in TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [10] and between the IAB-node and the SgNB (F1 interface) are defined in this clause. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | Annex |
4,075 | 10.5.4.35 Network-initiated Service Upgrade indicator | The purpose of the Network-initiated Service Upgrade indicator information element is to indicate to the mobile station that the in-call modification procedure is due to a network-initiated upgrade from speech to UDI/RDI multimedia (see 3GPP TS 23.172[ Technical realization of Circuit Switched (CS) multimedia service UDI/RDI fallback and service modification; Stage 2 ] [97]). The Network- initiated Service Upgrade indicator information element is coded as shown in figure 10.5.118f/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The Network-initiated Service Upgrade indicator is a type 2 information element with a length of 1 octet. Figure 10.5.118f/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Network-initiated Service Upgrade indicator information element | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.4.35 |
4,076 | 7.10.2 KPI requirement for direct device connection | The 5G system shall support split AI/ML inference between AI/ML endpoints by leveraging direct device connection with performance requirements as given in Table 7.10.2-1. Table 7.10.2-1 KPI Table of Split AI/ML operation between AI/ML endpoints for AI inference by leveraging direct device connection The 5G system shall support AI/ML model/data distribution and sharing by leveraging direct device connection with performance requirements as given in Table 7.10.2-2. Table 7.10.2-2 KPI Table of AI/ML model/data distribution and sharing by leveraging direct device connection The 5G system shall support AI/ML model/data distribution and sharing by leveraging direct device connection with performance requirements as given in Table 7.10.2-3. Table 7.10.2-3 KPI Table of Distributed/Federated Learning by leveraging direct device connection | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 7.10.2 |
4,077 | 12.3.9.3.3 Based on session parameters | Message prioritization may be performed based on the session parameters, such as: APN, QCI, ARP and/or Low Access Priority Indicator (LAPI). The procedures and messages associated with the higher priority sessions shall be given lesser preference whilst throttling, as compared to the procedures and messages associated with the lower priority sessions. Within each group of sessions, the messages may be further prioritized based on the category of the procedure for which the message is being sent (as described in clause 12.3.9.3.2). NOTE: This type of prioritization scheme ensures a good handling of all the messages and procedures related to higher priority sessions but can lead to throttle messages related to a critical procedure, e.g. UE mobility, for lower priority sessions over messages related to less critical procedures, e.g. location reporting, for a higher priority session. | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 12.3.9.3.3 |
4,078 | 8.25 S103 PDN Data Forwarding Info (S103PDF) | The HSGW Address and GRE Key identify a GRE Tunnel towards a HSGW over S103 interface for a specific PDN connection of the UE. The EPS Bearer IDs specify the EPS Bearers which require data forwarding that belonging to this PDN connection. The number of EPS bearer Ids included is specified by the value of EPS Bearer ID Number. The spare bits indicate unused bits, which shall be set to 0 by the sending side and which shall not be evaluated by the receiving side. Figure 8.25-1: S103 PDN Data Forwarding Info | 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.25 |
4,079 | 8.2.1.9.2 Minimum Requirement for Rel-16 further enhanced HST | The requirements are specified in Table 8.2.1.9.2-2, with the addition of the parameters in Table 8.2.1.9.2-1 and the downlink physical channel setup according to Annex C.3.2. The purpose of these tests is to verify UE performance in the HST-SFN-500 and HST-500 scenario. The test for HST-SFN-500 scenario defined in B.3B is applied when highSpeedEnhDemodFlag2-r16 [7] is received. The test for HST-500 scenario defined in B.3C is applied when highSpeedEnhDemodFlag2-r16 [7] is not received. HST-500 test is not applicable to UE that has passed HST-SFN-500 test. Table 8.2.1.9.2-1: Test Parameters for UE performance in HST-SFN-500 and HST-500 scenario (FRC) Table 8.2.1.9.2-2: Minimum performance UE in HST-SFN-500 and HST-500 scenario (FRC) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.2.1.9.2 |
4,080 | 5.2.3.2.2 Nudm_UECM_DeregistrationNotification service operation | Service operation name: Nudm_UECM_DeregistrationNotification. Description: UDM notifies the NF consumer which has previously registered (using Nudm_UECM_Registration operation) has been deregistered in the UDM. As a result, the consumer is no longer registered in UDM as a serving NF for that UE. NOTE: This notification corresponds to an implicit subscription. Inputs, Required: SUPI, Access Type, PDU Session ID, serving NF deregistration reason. Inputs, Optional: NF ID in the case of SM Context Transfer. Outputs, Required: None. Outputs, Optional: None. See step 14d of clauses 4.2.2.2.2 and 4.26.5.3 for an example usage of this service operation. The serving NF deregistration reason tells the reason for sending the deregistration notification to the consumer NF. The reason for AMF deregistration can be one of the following: - UE Initial Registration. - UE Registration area change. - Subscription Withdrawn. - 5GS to EPS Mobility. The reason for SMF deregistration can be one of the following: - SMF Context Transfer. - Removal of duplicated PDU Sessions in the old SMF. - PDU session being released requested to be re-activated. - Other UDM determined reason as specified in TS 29.503[ 5G System; Unified Data Management Services; Stage 3 ] [52]. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.3.2.2 |
4,081 | 4.3.33.4 Reject Paging Request | A Multi-USIM UE may respond to a page for a USIM with an indication to the MME that the UE does not accept the paging and requests to be released to ECM-IDLE state after sending this response, if both UE and network indicate to each other the Reject Paging Request feature is supported. Upon being paged, the Multi-USIM UE attempts to send an Extended Service Request message to the paging network including the Reject Paging Indication as the response to the paging, unless it is unable to do so, e.g. due to UE implementation constraints. In addition to the Reject Paging Indication, the UE may include Paging Restriction Information as specified in clause 4.3.33.6 in the Extended Service Request message, if the Paging Restrictions are supported by UE and network. | 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.33.4 |
4,082 | 16.2 RADIUS Accounting | RADIUS Accounting shall be used according to IETF RFC 2866 [39] , IETF RFC 2869 [116], IETF RFC 3162 [50] and IETF RFC 4818 [97]. The RADIUS accounting client function may reside in a GGSN/P-GW. The RADIUS accounting client may send information to an accounting server, which is identified during the APN provisioning. The accounting server may store this information and use it to automatically identify the user. This information can be trusted because the Packet Domain network has authenticated the subscriber (i.e. SIM card and possibly other authentication methods). The GGSN/P-GW may use the RADIUS Accounting-Request Start and Stop messages during IP-CAN bearer (e.g. primary and secondary PDP context, default and dedicated bearer) activations and deactivations procedures, respectively. For EPC based Packet domain, if the P-GW is not aware of the IP-CAN bearers, e.g. in case of PMIP-based S5/S8, the P-GW may use the RADIUS Accounting-Request Start and Stop messages per IP-CAN session as it would be one IP-CAN bearer. The use of Accounting-Request STOP and in addition the Accounting ON and Accounting OFF messages may be used to ensure that information stored in the accounting server is synchronised with the GGSN/P-GW information. If the AAA server is used for IPv4 address and/or IPv6 prefix assignment, then, upon reception of a RADIUS Accounting-Request STOP message for all IP-CAN bearers associated to an IP-CAN session defined by APN and IMSI or MSISDN, the AAA server may make the associated IPv4 address and/or IPv6 prefix available for assignment. For PDN/PDP type IPv4v6 and deferred IPv4 address allocation, when the IPv4 address is allocated or re-allocated, the accounting session that was established for the IPv6 prefix allocation shall be used to inform the accounting server about the allocated IPv4 address by sending RADIUS Accounting-Request Interim-Update with Framed-IP-Address attribute and its value field containing the allocated IPv4 address. Similarly, the release of IPv4 address shall be indicated to the accounting server by sending RADIUS Accounting-Request Interim-Update without the Framed-IP-Address attribute. In order to avoid race conditions, the GGSN/P-GW shall include a 3GPP Vendor-Specific sub-attribute "Session Stop indicator" when it sends the Accounting-Request STOP for the last IP-CAN bearer of an IP-CAN session and the IP-CAN session is terminated (i.e. the IPv4 address and/or IPv6 prefix and any associated GTP tunnels or PMIP tunnel can be released). The AAA server shall not assume the IP-CAN session terminated until an Accounting-Request STOP with the Session Stop indicator is received. | 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 | 16.2 |
4,083 | 16.21.2.1 L2 MP Relay using SL indirect path | For multi-path relay operation by using SL indirect path, the protocol stacks for the user plane and control plane of L2 MP Relay architecture are illustrated in Figure 16.21.2.1-1, 16.21.2.1-2. If PC5 interface is used between L2 MP Remote UE and L2 MP Relay UE, the SRAP sublayer is placed above the RLC sublayer for both CP and UP at both PC5 interface and Uu interface of the indirect path. For the direct path, the Uu SDAP, PDCP, RLC, MAC, PHY, and RRC are terminated at gNB and MP Remote UE. But for the indirect path, only the Uu SDAP, PDCP and RRC are terminated at gNB and MP Remote UE, while SRAP, RLC, MAC, and PHY are terminated in each hop (i.e., the link between L2 MP Remote UE and L2 MP Relay UE and the link between L2 MP Relay UE and the gNB). If duplication is not activated for a split bearer, in UL, a PDCP entity in the L2 MP Remote UE delivers a PDCP PDU to either a Uu RLC entity or a PC5 RLC entity having an SRAP entity over it. If duplication is activated for a split bearer, a PDCP entity in the L2 MP Remote UE delivers the same PDCP PDU to the Uu RLC entity and the PC5 RLC entity. Figure 16.21.2.1-1: User plane protocol stack for L2 Multi-path Relay using SL indirect path Figure 16.21.2.1-2: Control plane protocol stack for L2 Multi-path Relay using SL indirect path | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.21.2.1 |
4,084 | 5.22 Entering Dormant SCell state | If the MAC entity is configured with one or more SCells, the network may transition configured SCells into Dormant State. Dormant State is not applicable for SpCell or PUCCH SCell. The network transitions SCell(s) in and out of Dormant State by sending Activation/Deactivation and/or Hibernation MAC control element as described in clause 6.1.3.8 and 6.1.3.15 respectively. Furthermore, the MAC entity maintains two timers related to the dormant state: - If configured, an sCellHibernationTimer timer per configured SCell (except the SCell configured with PUCCH, if any). Upon the timer expiry, the MAC entity hibernates the associated SCell if it is in activated state. The same initial timer value applies to each instance of the sCellHibernationTimer and it is configured by RRC. - If configured, a dormantSCellDeactivationTimer per configured SCell (except the SCell configured with PUCCH, if any). Upon the timer expiry, the MAC entity deactivates the associated SCell if it is in dormant state. The same initial timer value applies to each instance of the dormantSCellDeactivationTimer and it is configured by RRC. An SCell will be in Dormant SCell state upon SCell configuration in case the parameter sCellState is set to dormant for the SCell within RRC configuration. The configured SCG SCells are dormant after a SCG change in case the parameter sCellState is set to dormant for the SCell within RRC configuration. The MAC entity shall for each TTI and for each configured SCell: - if the MAC entity is configured with dormant SCell upon SCell configuration or receives MAC control element(s) in this TTI for transitioning the SCell into Dormant State: - in the TTI according to the timing defined in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2]: - transition the SCell into Dormant State; - stop the sCellDeactivationTimer associated with the SCell; - if sCellHibernationTimer associated with the SCell is configured; - stop the sCellHibernationTimer associated with the SCell; - start or restart the dormantSCellDeactivationTimer associated with the SCell; - clear any configured downlink assignments and uplink grants associated with the SCell; - flush all HARQ buffers associated with the SCell. - if the sCellHibernationTimer associated with the activated SCell expires in this TTI: - in the TTI according to the timing defined in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2]: - hibernate the SCell; - stop the sCellDeactivationTimer associated with the SCell; - stop the sCellHibernationTimer associated with the SCell; - start the dormantSCellDeactivationTimer associated with the SCell; - clear any configured downlink assignments and uplink grants associated with the SCell; - flush all HARQ buffers associated with the SCell. - if the dormantSCellDeactivationTimer associated with the dormant SCell expires in this TTI: - in the TTI according to the timing defined in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2]: - deactivate the SCell; - stop the dormantSCellDeactivationTimer associated with the SCell; - if the SCell is in Dormant State: - not transmit SRS on the SCell; - report CQI/PMI/RI/PTI/CRI for the SCell according to the periodicity indicated by cqi-ReportPeriodic-SCell-r15; - not transmit on UL-SCH on the SCell; - not transmit on RACH on the SCell; - not monitor the PDCCH on the SCell; - not monitor the PDCCH for the SCell; - not transmit PUCCH on the SCell. HARQ feedback for the MAC PDU containing Hibernation MAC control element shall not be impacted by PCell, PSCell and PUCCH SCell interruptions due to SCell activation/deactivation or hibernation (TS 36.133[ Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for support of radio resource management ] [9]). NOTE: When SCell is in Dormant State, any ongoing Random Access procedure on the SCell is aborted. | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.22 |
4,085 | 9.11.4.34 ECS address | The purpose of the ECS address information element is to indicate the ECS address (either IPv4 address, IPv6 address, or FQDN) and the associated spatial validity condition. The ECS address information element is coded as shown in figure 9.11.4.34.1, figure 9.11.4.34.2, table 9.11.4.34.1, and table 9.11.4.34.2. The ECS address information element is a type 6 information element with minimum length of 8 octets and a maximum length of 65538 octets. Figure 9.11.4.34.1: ECS address information element Figure 9.11.4.34.2: Spatial validity condition contents Table 9.11.4.34.1: ECS address information element Table 9.11.4.34.2: Spatial validity condition contents | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.11.4.34 |
4,086 | 5.30.2.4.2 Automatic network selection | NOTE 1: If the UE has multiple subscriptions (SNPN and/or PLMN) it is assumed that the subscription to use for automatic selection is determined by implementation specific means prior to network selection. If the UE supports accessing an SNPN providing access for Localized Services and the end user enables to access Localized Services, for automatic network selection, the UE shall select and attempts registration on available SNPN in the following order: (a) if the UE supports access to an SNPN using Credentials from a Credentials Holder then the UE continues by selecting and attempting registration on available and allowable SNPNs which broadcasts the indication that access using credentials from a Credentials Holder is supported in the following order: i the SNPN with the validity information the UE was last registered with (if the validity information is met) or the SNPN's equivalent SNPN(s) (if available and the validity information of the SNPN that the UE was last registered with is met); NOTE 2: The equivalent SNPN(s) are assumed to provide access to the same Localized Services as the SNPN the UE was last registered with. ii SNPNs in the Credentials Holder controlled prioritized list of preferred SNPNs for accessing Localized Services (in priority order) if the validity information is met; iii SNPNs, which additionally broadcast a GIN contained in the Credentials Holder controlled prioritized list of preferred GINs for accessing Localized Services (in priority order) if validity information is met; (b) the SNPN without validity information the UE was last registered with (if available) or the equivalent SNPN (if available); (c) the subscribed SNPN, which is identified by the PLMN ID and NID for which the UE has SUPI and credentials; (d) the available and allowable SNPNs which broadcast the indication that access using credentials from a Credentials Holder is supported in the following order: i SNPNs in the user controlled prioritized list of preferred SNPNs (in priority order); ii SNPNs in the Credentials Holder controlled prioritized list of preferred SNPNs (in priority order); iii SNPNs, which additionally broadcast a GIN contained in the Credentials Holder controlled prioritized list of preferred GINs (in priority order); iv- SNPNs, which additionally broadcast an indication that the SNPN allows registration attempts from UEs that are not explicitly configured to select the SNPN, i.e. the broadcasted NID or GIN is not present in the Credentials Holder controlled prioritized lists of preferred SNPNs/GINs, nor in the Credentials Holder controlled prioritized lists of preferred SNPNs/GINs for accessing Localized Services in the UE. If the UE supports accessing an SNPN providing access for Localized Services and the end user enables to access Localized Services, the UE shall periodically attempt reselection and registration on a higher priority SNPN 1) based on the order of the above sub-bullets (i) to (iii) of bullet (a), bullet (c), sub-bullets (i) to (iii) of bullet (d) if the UE is not registered to the sub-bullet (i) of bullet (a) or 2) based on the order of the above sub-bullets (ii) to (iii) of bullet (a), bullet (c), sub-bullets (i) to (iii) of bullet (d) if the UE is registered to the sub-bullet (i) of bullet (a) if any of the below conditions is met: - if there are one or more SNPNs with validity information which is met, and the UE is not registered to an SNPN which has highest priority among the one or more SNPNs; or - if there is no SNPN with validity information which is met, and there are one or more GINs with the validity information which is met, and the UE is not registered to an SNPN broadcasting a GIN which has highest priority among the one or more GINs; or - if there is no SNPN with validity information which is met and there is no GIN with validity information which is met, and the UE is not registered to the subscribed SNPN Otherwise, the UE does not trigger periodic reselection and does not attempt registration on a higher priority SNPN NOTE 3: Details of network selection (e.g. validity information handling, periodicity determination) specified in TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [17]. If a validity condition in Credentials Holder controlled prioritized lists of preferred SNPNs/GINs for accessing Localized Services changes from met to not met (and vice versa), the UE shall attempt selection and registration on an SNPN based on the above bullets (a) to (d). If the UE does not support to access an SNPN providing access for Localized Services or the end user does not enable to access the Localized Services, for automatic network selection the UE shall select and attempts registration on available and allowable SNPNs in the following order: - the SNPN without validity information the UE was last registered with (if available) or the equivalent SNPN (if available); - the subscribed SNPN, which is identified by the PLMN ID and NID for which the UE has SUPI and credentials.; - If the UEs supports access to an SNPN using credentials from a Credentials Holder then the UE continues by selecting and attempting registration on available and allowable SNPNs which broadcast the indication that access using credentials from a Credentials Holder is supported in the following order: - SNPNs in the user controlled prioritized list of preferred SNPNs (in priority order); - SNPNs in the Credentials Holder controlled prioritized list of preferred SNPNs (in priority order); - SNPNs, which additionally broadcast a GIN contained in the Credentials Holder controlled prioritized list of preferred GINs (in priority order); NOTE 4: If multiple SNPNs are available that broadcast the same GIN, the order in which the UE selects and attempts a registration with those SNPNs is implementation specific. - SNPNs, which additionally broadcast an indication that the SNPN allows registration attempts from UEs that are not explicitly configured to select the SNPN, i.e. the broadcasted NID or GIN is not present in the Credentials Holder controlled prioritized lists of preferred SNPNs/GINs in the UE. NOTE 5: If multiple SNPNs are available that broadcast the indication that the SNPN allows registration attempts from UEs that are not explicitly configured to select the SNPN, the order in which the UE selects and attempts a registration with those SNPNs is implementation specific. When a UE performs Registration or Service Request to an SNPN, the UE shall indicate the PLMN ID and NID as broadcast by the selected SNPN to NG-RAN. NG-RAN shall inform the AMF of the selected PLMN ID and NID. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.30.2.4.2 |
4,087 | 5.4.2.5 Authentication not accepted by the network | If the authentication response (RES) returned by the UE is not valid, the network response depends upon the type of identity used by the UE in the initial NAS message, that is: - if the GUTI was used; or - if the IMSI was used. If the GUTI was used, the network should initiate an identification procedure. If the IMSI given by the UE during the identification procedure differs from the IMSI the network had associated with the GUTI, the authentication should be restarted with the correct parameters. Otherwise, if the IMSI provided by the UE is the same as the IMSI stored in the network (i.e. authentication has really failed), the network should send an AUTHENTICATION REJECT message to the UE. If the IMSI was used for identification in the initial NAS message, or the network decides not to initiate the identification procedure after an unsuccessful authentication procedure, the network should send an AUTHENTICATION REJECT message to the UE. The network shall maintain, if any, the EMM-context and EPS security context unchanged. Upon receipt of an AUTHENTICATION REJECT message, a) if the message has been successfully integrity checked by the NAS, the UE shall set the update status to EU3 ROAMING NOT ALLOWED, delete the stored GUTI, TAI list, last visited registered TAI and KSIASME. The USIM shall be considered invalid until switching off the UE or the UICC containing the USIM is removed. If the UE maintains a counter for "SIM/USIM considered invalid for GPRS services", then the UE shall set this counter to UE implementation-specific maximum value. If the UE maintains a counter for "SIM/USIM considered invalid for non-GPRS services", then the UE shall set this counter to UE implementation-specific maximum value. If A/Gb or Iu mode is supported by the UE, the UE shall in addition handle the GMM parameters GMM state, GPRS update status, P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number and the MM parameters update status, TMSI, LAI and ciphering key sequence number as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the authentication and ciphering procedure is not accepted by the network. If the UE is operating in single-registration mode, the UE shall in addition handle the 5GMM parameters 5GMM state, 5GS update status, 5G-GUTI, last visited registered TAI, TAI list and ngKSI as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the authentication procedure performed over 3GPP access is not accepted by the network; and b) if the message is received without integrity protection and if timer T3416, T3418 or T3420 is running, the UE shall start timer T3247 (see 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13]) with a random value uniformly drawn from the range between 30 minutes and 60 minutes, if the timer is not running (see clause 5.3.7b). Additionally, the UE shall: - if the UE maintains a counter for "SIM/USIM considered invalid for GPRS services" events and the counter has a value less than a UE implementation-specific maximum value, proceed as specified in clause 5.3.7b, list item 1a for the case that the EMM cause value received is #3; and - otherwise proceed as specified under list item a above for the case that the message has been successfully integrity checked. If the AUTHENTICATION REJECT message is received by the UE, the UE shall abort any EMM signalling procedure, stop any of the timers T3410, T3416, T3417, T3430, T3421, T3418 or T3420 (if they were running) and enter state EMM-DEREGISTERED. Depending on local requirements or operator preference for emergency bearer services, if the UE has a PDN connection for emergency bearer services established or is establishing a PDN connection for emergency bearer services, the MME need not follow the procedures specified for the authentication failure in the present clause. The MME may continue a current EMM specific procedure or PDN connectivity request procedure. Upon completion of the authentication procedure, if not initiated as part of another procedure, or upon completion of the EMM procedure or PDN connectivity request procedure, the MME shall deactivate all non-emergency EPS bearers, if any, by initiating an EPS bearer context deactivation procedure. The network shall consider the UE to be attached for emergency bearer services only. Depending on local regulation and operator policy, if the UE is requesting attach for access to RLOS, the MME need not follow the procedures specified for the authentication failure in the present clause. The MME may continue a current EMM specific 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.4.2.5 |
4,088 | 9.2.6 Random Access Procedure | The random access procedure is triggered by a number of events: - Initial access from RRC_IDLE; - RRC Connection Re-establishment procedure; - DL or UL data arrival, during RRC_CONNECTED or during RRC_INACTIVE while SDT procedure (see clause 18.0) is ongoing, when UL synchronisation status is "non-synchronised"; - UL data arrival, during RRC_CONNECTED or during RRC_INACTIVE while SDT procedure is ongoing, when there are no PUCCH resources for SR available; - Handover; - SR failure; - Explicit request by RRC upon synchronous reconfiguration; - RRC Connection Resume procedure from RRC_INACTIVE; - To establish time alignment for a primary or a secondary TAG; - Request for Other SI (see clause 7.3); - Beam failure recovery; - Consistent UL LBT failure on SpCell; - SDT in RRC_INACTIVE (see clause 18); - Positioning purpose during RRC_CONNECTED requiring random access procedure, e.g., when timing advance is needed for UE positioning; - Early UL synchronization with an LTM candidate cell; - RACH-based LTM cell switch. Two types of random access procedure are supported: 4-step RA type with MSG1 and 2-step RA type with MSGA. Both types of RA procedure support contention-based random access (CBRA) and contention-free random access (CFRA) as shown on Figure 9.2.6-1 below. The UE selects the type of random access at initiation of the random access procedure based on network configuration: - when CFRA resources are not configured, an RSRP threshold is used by the UE to select between 2-step RA type and 4-step RA type; - when CFRA resources for 4-step RA type are configured, UE performs random access with 4-step RA type; - when CFRA resources for 2-step RA type are configured, UE performs random access with 2-step RA type. The network does not configure CFRA resources for 4-step and 2-step RA types at the same time for a Bandwidth Part (BWP). CFRA with 2-step RA type is only supported for handover. The MSG1 of the 4-step RA type consists of a preamble on PRACH. After MSG1 transmission, the UE monitors for a response from the network within a configured window. For CFRA, dedicated preamble for MSG1 transmission is assigned by the network and upon receiving random access response from the network, the UE ends the random access procedure as shown in Figure 9.2.6-1(c). For CBRA, upon reception of the random access response, the UE sends MSG3 using the UL grant scheduled in the response and monitors contention resolution as shown in Figure 9.2.6-1(a). If contention resolution is not successful after MSG3 (re)transmission(s), the UE goes back to MSG1 transmission. The MSGA of the 2-step RA type includes a preamble on PRACH and a payload on PUSCH. After MSGA transmission, the UE monitors for a response from the network within a configured window. For CFRA, dedicated preamble and PUSCH resource are configured for MSGA transmission and upon receiving the network response, the UE ends the random access procedure as shown in Figure 9.2.6-1(d). For CBRA, if contention resolution is successful upon receiving the network response, the UE ends the random access procedure as shown in Figure 9.2.6-1(b); while if fallback indication is received in MSGB, the UE performs MSG3 transmission using the UL grant scheduled in the fallback indication and monitors contention resolution as shown in Figure 9.2.6-2. If contention resolution is not successful after MSG3 (re)transmission(s), the UE goes back to MSGA transmission. If the random access procedure with 2-step RA type is not completed after a number of MSGA transmissions, the UE can be configured to switch to CBRA with 4-step RA type. For the random access procedure towards an LTM candidate cell for early UL TA acquisition, CFRA triggered by a PDCCH order is used. The UE sends MSG1 towards the cell without monitoring for a response from it as shown in Figure 9.2.6-1 (e). To support UE power ramping, the UE may perform MSG1 retransmission as indicated by the network. (a) CBRA with 4-step RA type (b) CBRA with 2-step RA type (c) CFRA with 4-step RA type (d) CFRA with 2-step RA type (e) CFRA without network response with 4-step RA type Figure 9.2.6-1: Random Access Procedures Figure 9.2.6-2: Fallback for CBRA with 2-step RA type For random access in a cell configured with SUL, the network can explicitly signal which carrier to use (UL or SUL). Otherwise, the UE selects the SUL carrier if and only if the measured quality of the DL is lower than a broadcast threshold. UE performs carrier selection before selecting between 2-step and 4-step RA type. The RSRP threshold for selecting between 2-step and 4-step RA type can be configured separately for UL and SUL. Once started, all uplink transmissions of the random access procedure remain on the selected carrier. The network can associate a set of RACH resources with feature(s) applicable to a Random Access procedure: Network Slicing (see clause 16.3), (e)RedCap (see clause 16.13), SDT (see clause 18), and NR coverage enhancement (see clause 19). A set of RACH resources associated with a feature is only valid for random access procedures applicable to at least that feature; and a set of RACH resources associated with several features is only valid for random access procedures having at least all of these features. The UE selects the set(s) of applicable RACH resources, after uplink carrier (i.e. NUL or SUL) and BWP selection and before selecting the RA type. When CA is configured, random access procedure with 2-step RA type is only performed on PCell while contention resolution can be cross-scheduled by the PCell. When CA is configured, for random access procedure with 4-step RA type, the first three steps of CBRA always occur on the PCell while contention resolution (step 4) can be cross-scheduled by the PCell. The three steps of a CFRA started on the PCell remain on the PCell. CFRA on SCell can only be initiated by the gNB to establish timing advance for a secondary TAG: the procedure is initiated by the gNB with a PDCCH order (step 0) that is sent on an activated SCell of the secondary TAG, preamble transmission (step 1) takes place on the SCell, and Random Access Response (step 2) takes place on PCell. When two TAG IDs are configured for the serving cell, the TAG for which the TA command is applied is indicated in Random Access Response message or in MSGB. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 9.2.6 |
4,089 | β RRCReestablishmentRequest | The RRCReestablishmentRequest message is used to request the reestablishment of an RRC connection. Signalling radio bearer: SRB0 RLC-SAP: TM Logical channel: CCCH Direction: UE to Network RRCReestablishmentRequest message -- ASN1START -- TAG-RRCREESTABLISHMENTREQUEST-START RRCReestablishmentRequest ::= SEQUENCE { rrcReestablishmentRequest RRCReestablishmentRequest-IEs } RRCReestablishmentRequest-IEs ::= SEQUENCE { ue-Identity ReestabUE-Identity, reestablishmentCause ReestablishmentCause, spare BIT STRING (SIZE (1)) } ReestabUE-Identity ::= SEQUENCE { c-RNTI RNTI-Value, physCellId PhysCellId, shortMAC-I ShortMAC-I } ReestablishmentCause ::= ENUMERATED {reconfigurationFailure, handoverFailure, otherFailure, spare1} -- TAG-RRCREESTABLISHMENTREQUEST-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
4,090 | 6.2.3.3 Key lifetimes | KAUSF, and KSEAF shall be created when running a successful primary authentication as described in clause 6.1.3. KAMF shall be created in the following cases: 1. Primary authentication 2. NAS key re-keying as described in clause 6.9.4.2 3. NAS key refresh as described in clause 6.9.4.3 4. Interworking procedures with EPS (cf. clauses 8 and 10) In case the UE does not have a valid KAMF, an ngKSI with value "111" shall be sent by the UE to the network, which can initiate (re)authentication procedure to get a new KAMF based on a successful primary authentication. KNASint and KNASenc are derived based on a KAMF when running a successful NAS SMC procedure as described in clause 6.7.2. KN3IWF is derived from KAMF and remains valid as long as the UE is connected to the 5GC over non- 3gpp access or until the UE is reauthenticated. KgNB and NH are derived based on KAMF or KgNB or NH in the following cases: 1. Inter-gNB-CU-handover as described in clause 6.9.2.3.1 2. State transitions as described in clause 6.8 3. AS key re-keying as described in clause 6.9.4.4 4. AS key refresh as described in clause 6.9.4.5 The KRRCint, KRRCenc, KUPint and KUPenc are derived based on KgNB after a new KgNB is derived. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.2.3.3 |
4,091 | 10.4.2 Composition of the IFPEI | 6 digits 2d 6 digits 2d <-----------><---><-----------><---> +-----------++---++-----------++---+ | || || || | +------++--++------++--+ TAC FAC SNR SVN IFPEI 16 digits <> Figure 17: Structure of IFPEI The IFPEI is composed of the following elements (each element shall consist of decimal digits only): - Type Approval Code (TAC). Its length is 6 decimal digits; - Final Assembly Code (FAC). Its length is 2 decimal digits; - Serial NumbeR (SNR). Its length is 6 decimal digits; - Software Version Number (SVN) identifies the software version number of the fixed part equipment. Its length is 2 digits. Regarding updates of the IFPEI: the TAC, FAC and SNR shall be physically protected against unauthorised change (see 3GPP TS 42.009[ Security aspects ] [36]); i.e. only the SVN part of the IFPEI can be modified. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 10.4.2 |
4,092 | 10.5.6.10 Tear down indicator | The purpose of the tear down indicator information element is to indicate whether only the PDP context associated with this specific TI or all active PDP contexts sharing the same PDP address and APN as the PDP context associated with this specific TI shall be deactivated. The tear down indicator is a type 1 information element. The tear down indicator information element is coded as shown in figure 10.5.142/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.160/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.142/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Tear down indicator information element Table 10.5.160/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Tear down indicator 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.10 |
4,093 | 5.6.3.2 Notification procedure initiation | The network shall initiate the notification procedure by sending the NOTIFICATION message to the UE and start timer T3565 (see example in figure 5.6.3.2.1). For case a) in subclause 5.6.3.1, the NOTIFICATION message is sent from the network to the UE via 3GPP access with access type indicating non-3GPP access. For case b) in subclause 5.6.3.1, the NOTIFICATION message is sent from the network to the UE via non-3GPP access with access type indicating 3GPP access when the UE is not in MICO mode. Figure 5.6.3.2.1: Notification procedure For case b) in subclause 5.6.3.1, if the network has downlink user data pending for a UE and the AMF has stored paging restriction of the UE and the Paging restriction type in the stored paging restriction is set to: a) "All paging is restricted", the network should not send the NOTIFICATION message to the UE; b) "All paging is restricted except for voice service", the network should send the NOTIFICATION message to the UE only when the pending downlink user data for the UE is considered as voice service related by the network and the MUSIM UE does not support the paging indication for voice services or the network has not indicated "paging indication for voice services supported" to the UE; c) "All paging is restricted except for specified PDU session(s)", the network should send the NOTIFICATION message to the UE only when: 1) for PDU session(s) that paging is not restricted based on the stored paging restriction, the network has downlink user data pending; d) "All paging is restricted except for voice service and specified PDU session(s)" the network should send the NOTIFICATION message to the UE only: 1) when the pending downlink user data for the UE is considered as voice service related by the network and the MUSIM UE does not support the paging indication for voice services, or the network has not indicated "paging indication for voice services supported" to the UE; or 2) for PDU session(s) that paging is not restricted based on the stored paging restriction, the network has downlink user data pending. For case b) in subclause 5.6.3.1, if the network has downlink signalling pending for a UE and the AMF has stored paging restriction of the UE and the Paging restriction type in the stored paging restriction is set to: a) "All paging is restricted", the network should not send the NOTIFICATION message to the UE; b) "All paging is restricted except for voice service", then the network should send the NOTIFICATION message to the UE only when: 1) the pending downlink signalling for the UE is 5GMM signalling or 5GSM signalling of the PDU session of voice service; c) "All paging is restricted except for specified PDU session(s)", the network should send the NOTIFICATION message to the UE only when: 1) the pending downlink signalling for the UE is 5GMM signalling; or 2) for PDU session(s) that paging is not restricted based on the stored paging restriction, the network has downlink 5GSM signalling pending; or d) "All paging is restricted except for voice service and specified PDU session(s)" then the network should send the NOTIFICATION message to the UE only when: 1) the pending downlink signalling for the UE is 5GMM signalling or 5GSM signalling pending of the PDU session of voice service; or 2) for PDU session(s) that paging is not restricted based on the stored paging restriction, the network has downlink 5GSM signalling pending. NOTE 1: If the network sends NOTIFICATION message to the UE due to downlink signalling pending, the network initiates the release of the N1 NAS signalling connection over 3GPP access after network-requested procedure is completed. Upon reception of a NOTIFICATION message, the UE shall stop the timer T3346, if running. For case a) in subclause 5.6.3.1, upon reception of NOTIFICATION message, the UE shall initiate a service request procedure over 3GPP access as specified in subclauses 5.6.1. NOTE 2: For a UE in NB-NI mode, if there is DL user data pending for a PDU session associated with non-3GPP access then the AMF notifies the SMF that reactivation of user plane resources cannot be performed if the number of PDU sessions that currently has user-plane resources established equals to the UE's maximum number of supported user-plane resources. For case b) in subclause 5.6.3.1, upon reception of NOTIFICATION message: a) if control plane CIoT 5GS optimization is not used by the UE, the UE shall: 1) initiate a service request procedure over 3GPP access as specified in subclause 5.6.1.2.1, if the UE is in 5GMM-REGISTERED.NORMAL-SERVICE or 5GMM-REGISTERED.NON-ALLOWED-SERVICE (as described in subclause 5.3.5.2) state over 3GPP access or 5GMM-REGISTERED.NON-ALLOWED-SERVICE state (see subclause 5.3.5.2), and the UE is in the 5GMM-IDLE mode without suspend indication; 2) initiate a registration procedure for mobility and periodic registration update over 3GPP access as specified in subclause 5.5.1.3.2, if the UE is in 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE state over 3GPP access; or 3) proceed as specified in subclause 5.3.1.5 if the UE is in the 5GMM-IDLE mode with suspend indication; b) if control plane CIoT 5GS optimization is used by the UE, the UE shall: 1) initiate a service request procedure over 3GPP access as specified in subclause 5.6.1.2.2, if the UE is in 5GMM-REGISTERED.NORMAL-SERVICE or 5GMM-REGISTERED.NON-ALLOWED-SERVICE (as described in subclause 5.3.5.2) state and the UE is in the 5GMM-IDLE mode without suspend indication; 2) initiate a registration procedure for mobility and periodic registration update over 3GPP access as specified in subclause 5.5.1.3.2, if the UE is in 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE state; or 3) proceed as specified in subclause 5.3.1.5 if the UE is in the 5GMM-IDLE mode with suspend indication; or c) if: 1) the UE is in 5GMM-REGISTERED.NO-CELL-AVAILABLE state, 5GMM-REGISTERED.PLMN-SEARCH state, 5GMM-REGISTERED.LIMITED-SERVICE state or 5GMM-REGISTERED.UPDATE-NEEDED state over 3GPP access; or 2) the MUSIM UE is not able to respond the NOTIFICATION message as specified in case a) and b) above, e.g., due to UE implementation constraints; the UE shall respond with NOTIFICATION RESPONSE message over non-3GPP access indicating inability of the UE to initiate a service request procedure or a registration procedure over 3GPP access and may include the PDU session status information element to indicate: 1) the single access PDU session(s) not in 5GSM state PDU SESSION INACTIVE in the UE associated with the 3GPP access type; and 2) the MA PDU session(s) not in 5GSM state PDU SESSION INACTIVE in the UE and having user plane resources established associated with the 3GPP access type. Upon reception of NOTIFICATION message: For case b) in subclause 5.6.3.1, if the UE is in 5GMM-REGISTERED.NO-CELL-AVAILABLE state or 5GMM-REGISTERED.PLMN-SEARCH state and a local release was performed in the UE for the single access PDU sessions associated with the 3GPP access or for user plane resources on the 3GPP access of MA PDU sessions; then the UE shall respond with NOTIFICATION RESPONSE message over non-3GPP access indicating with the PDU session status information element that: - the local release of its single access PDU sessions associated with the 3GPP access was performed; and - the local release of its 3GPP access user plane resources of MA PDU sessions was performed. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.6.3.2 |
4,094 | 4.7.1.2a Integrity protection of layer 3 signalling messages (A/Gb mode only and when integrity protection is required) 4.7.1.2a.1 General | The requirements in subclause 4.7.1.2a are only applicable for MSs and networks supporting EC-GSM-IoT (see 3GPP TS 43.064[ None ] [159]). For the MS, integrity protected signalling is mandatory for the GMM messages and SM messagres once a valid UMTS security context exists and has been taken into use. For the network, integrity protected signalling is mandatory for the GMM messages and SM messages once authentication and ciphering procedure is initiated by the network. Integrity protection of all GMM signalling messages and SM messages is the responsibility of the LLC layer. In addition, the GMM layer protects the AUTHENTICATION AND CIPHERING REQUEST message and the AUTHENTICATION AND CIPHERING RESPONSE message by a message authentication code (MAC) calculated at the GMM layer when an authentication takes place in the Authentication and Ciphering procedure. This message authentication code is included in the AUTHENTICATION AND CIPHERING REQUEST message and the AUTHENTICATION AND CIPHERING RESPONSE message. The GMM layer is always using the new UMTS security context derived from the AKA taking place in the Authentication and Ciphering procedure when calculating the message authentication code (MAC) at GMM layer. The GMM layer activates integrity protection in the LLC layer by providing an indication when integrity protection shall be started. Integrity protection is initiated in the MS upon request from the network. This is done using the authentication and ciphering procedure at the GMM layer (3GPP TS 43.020[ Security related network functions ] [13] and 3GPP TS 44.064[ Mobile Station - Serving GPRS Support Node (MS-SGSN); Logical Link Control (LLC) Layer Specification ] [78a]). Details of the integrity protection and verification of GMM signalling messages are specified in 3GPP TS 43.020[ Security related network functions ] [13]. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.1.2a |
4,095 | 9.5.11 Modify PDP context accept (MS to network direction) | This message is sent by the MS to the network to acknowledge the modification of an active PDP context. See table 9.5.11/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Message type: modify PDP context accept (MS to network direction) Significance: global Direction: MS to network Table 9.5.11/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : modify PDP context accept (MS to network direction) message content | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.5.11 |
4,096 | 6.25.2 Requirements | The 5G system shall support non-public networks. The 5G system shall support non-public networks that provide coverage within a specific geographic area. The 5G system shall support both physical and virtual non-public networks. The 5G system shall support standalone operation of a non-public network, i.e. a non-public network may be able to operate without dependency on a PLMN. Subject to an agreement between the operators and service providers, operator policies and the regional or national regulatory requirements, the 5G system shall support for non-public network subscribers: - access to subscribed PLMN services via the non-public network; - seamless service continuity for subscribed PLMN services between a non-public network and a PLMN; - access to selected non-public network services via a PLMN; - seamless service continuity for non-public network services between a non-public network and a PLMN. Subject to an agreement between the operators and service providers, operator policies and the regional or national regulatory requirements, the 5G system shall enable a UE, with multiple subscriptions, to simultaneously access multiple non-public networks and corresponding services, via those NPNs or via a different network (PLMN or NPN). Subject to regional or national regulatory requirements for emergency services, 5G system shall be able to support IMS emergency services for non-public networks. A non-public network subscriber to access a PLMN service shall have a service subscription using 3GPP identifiers and credentials provided or accepted by a PLMN. The 5G system shall support a mechanism for a UE to identify and select a non-public network. NOTE: Different network selection mechanisms may be used for physical vs virtual non-public networks. The 5G system shall support identifiers for a large number of non-public networks to minimize collision likelihood between assigned identifiers. The 5G system shall support a mechanism to prevent a UE with a subscription to a non-public network from automatically selecting and attaching to a PLMN or non-public network it is not authorized to select. The 5G system shall support a mechanism to prevent a UE with a subscription to a PLMN from automatically selecting and attaching to a non-public network it is not authorized to select. The 5G system shall support a mechanism for a PLMN to control whether a user of a UE can manually select a non-public network hosted by this PLMN that the UE is not authorized to select automatically. The 5G system may broadcast a human readable network name that a UE may display for manual selection of a non-public network. The 5G system shall support a change of host of a non-public network from one PLMN to another PLMN without changing the network selection information stored in the UEs of the non-public network. The 5G system shall enable an NPN to support multiple third-party service providers. In the event of a loss of communication between RAN and core network, the 5G system shall be able to provide capability to securely re-connect an NPN network function within a short period of time (< 1s). | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.25.2 |
4,097 | 6.1.3.8.2.2 Handling of network rejection due to SM cause #26 | If the SM cause value is #26 "insufficient resources" and the Back-off timer value IE is included, the MS shall ignore the Re-attempt indicator IE provided by the network, if any, and take different actions depending on the timer value received for timer T3396 in the Back-off timer value IE (if the MS is configured for dual priority, exceptions are specified in subclause 6.1.3.12): i) if the timer value indicates neither zero nor deactivated, the MS shall stop timer T3396 associated with the corresponding APN, if it is running. The MS shall then start timer T3396 with the value provided in the Back-off timer value IE and shall not send another ACTIVATE MBMS CONTEXT REQUEST message for the same APN that was sent by the MS until timer T3396 expires or timer T3396 is stopped. The MS shall not stop timer T3396 upon a PLMN change or inter-system change; ii) if the timer value indicates that this timer is deactivated, the MS shall not send another ACTIVATE MBMS CONTEXT REQUEST message for the same APN that was sent by the MS, until the MS is switched off or the SIM/USIM is removed or the MS receives REQUEST MBMS CONTEXT ACTIVATION message for the same APN from the network. The timer T3396 remains deactivated upon a PLMN change or inter-system change; and iii) if the timer value indicates that this timer is zero, the MS may send another ACTIVATE MBMS CONTEXT REQUEST message for the same APN. If the Back-off timer value IE is not included, then the MS may send another ACTIVATE MBMS CONTEXT REQUEST message for the same APN. If the MS is switched off when the timer T3396 is running, the MS shall behave as follows when the MS is switched on and the SIM/USIM in the MS remains the same: - let t1 be the time remaining for T3396 timeout at switch off and let t be the time elapsed between switch off and switch on. If t1 is greater than t, then the timer shall be restarted with the value t1 β t. If t1 is equal to or less than t, then the timer need not be restarted. If the MS is not capable of determining t, then the MS shall restart the timer with the value t1; and - if prior to switch off, timer T3396 was running because an ACTIVATE PDP CONTEXT REQUEST, ACTIVATE SECONDARY PDP CONTEXT REQUEST, MODIFY PDP CONTEXT REQUEST or ACTIVATE MBMS CONTEXT REQUEST message containing the low priority indicator set to "MS is configured for NAS signalling low priority" was rejected with timer T3396, and if timer T3396 is restarted at switch on, then the MS configured for dual priority shall handle session management requests as indicated in subclause 6.1.3.12. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.1.3.8.2.2 |
4,098 | β FeatureSetUplinkPerCC-Id | The IE FeatureSetUplinkPerCC-Id identifies a set of features applicable to one carrier of a feature set. The FeatureSetUplinkPerCC-Id of a FeatureSetUplinkPerCC is the index position of the FeatureSetUplinkPerCC in the featureSetsUplinkPerCC. The first element in the list is referred to by FeatureSetUplinkPerCC-Id = 1, and so on. FeatureSetUplinkPerCC-Id information element -- ASN1START -- TAG-FEATURESETUPLINKPERCC-ID-START FeatureSetUplinkPerCC-Id ::= INTEGER (1..maxPerCC-FeatureSets) -- TAG-FEATURESETUPLINKPERCC-ID-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
4,099 | 6.3.4.5 Symbol / Subslot boundary time mask for subslot TTI | The subslot boundary time mask defines the observation period between the previous/subsequent subslot and the (reference) subslot. A transient period at a symbol boundary within a subslot is only allowed in the case of Intra-subslot frequency hopping. For the cases when the subslot contains SRS the time masks in subclause 6.3.4.6 apply. There are no additional requirements on UE transmit power beyond that which is required in subclause 6.2.2 and subclause 6.6.2.3 Following time masks requirements shall be applied: - the transient period shall be equally shared between two consecutive Reference symbols or Data symbols (figure 6.3.4.5-1 and figure 6.3.4.5-4). - Otherwise, the transient period shall be placed in the Reference symbol (figure 6.3.4.5-2 and figure 6.3.4.5-3). Figure 6.3.4.5-1: Transmission power template for subslot TTI β transient period shared Figure 6.3.4.5-2: Transmission power template for subslot TTI β transient period not shared Figure 6.3.4.5-3: Transmission power template for subslot TTI β transient period not shared Figure 6.3.4.5-4: Transmission power template for subslot TTI β transient period shared | 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.3.4.5 |
4,100 | 10.20 Subsequent Conditional PSCell Addition or Change | A Subsequent Conditional PSCell Addition or Change (subsequent CPAC) is defined as a conditional PSCell addition or change procedure that is executed after a PSCell addition, a PSCell change, a PCell change or an SCG release based on pre-configured subsequent CPAC configuration of candidate PSCell(s) without reconfiguration and re-initiation of CPC/CPA. The UE keeps the configured subsequent CPAC configuration (unless the network indicates to release it) and evaluates the execution conditions of candidate PSCells after completion of a PSCell addition, a PSCell change, a PCell change or an SCG release. Intra-SN subsequent CPAC initiated by the SN, inter-SN subsequent CPAC initiated by either MN or SN are supported. The following principles apply to subsequent CPAC: - For MN initiated subsequent CPAC, the MN initially triggers the candidate cell preparation of subsequent CPAC procedure and generates the execution conditions for the initial execution of subsequent CPAC (e.g. CPA or CPC). - For SN initiated subsequent CPAC, the source SN initially triggers the candidate cell preparation of subsequent CPAC procedure and generates the execution conditions for the initial execution of subsequent CPAC. - For both MN and SN initiated inter-SN subsequent CPAC, the candidate SN generates the execution conditions for the following execution of subsequent CPAC when the candidate SN prepares the candidate SCG configuration(s) for candidate PSCell(s). For SN initiated intra-SN subsequent CPAC, the source SN generates the execution conditions for the following execution of subsequent CPAC when the source SN prepares the candidate SCG configuration(s) for candidate PSCell(s). - The subsequent CPAC configuration contains candidate SCG configuration(s) of candidate PSCell(s), execution conditions, and may contain the MCG configuration (to be applied when subsequent CPAC execution is triggered), the reference configuration and the security update configuration. - The subsequent CPAC configuration for CPA or inter-SN CPC candidate PSCell(s) is provided in MN format. The subsequent CPAC configuration for intra-SN CPC candidate PSCell(s) is provided in MN format or SN format. It's up to the source SN to decide which format to be used for intra-SN subsequent CPAC. - For one UE, the subsequent CPAC configuration for all candidate PSCells (including inter-SN and/or intra-SN) is provided in the same format, i.e., either MN format, or SN format. If the configured candidate PSCell(s) includes at least one inter-SN CPC candidate PSCell, the subsequent CPAC configuration can only be provided in MN format. If only intra-SN CPC candidate PSCell(s) is configured, the subsequent CPAC configuration can be provided in either MN format or SN format. - Each candidate PSCell configuration is provided as a delta configuration on top of a reference configuration or a complete configuration. Only one reference configuration is supported. - The MN generates the MCG part of the reference configuration (if any), while the SN generates the SCG part of the reference configuration. The MN can request an SCG reference configuration from any one of the involved SNs. - The network explicitly configures a subsequent CPAC configuration for the current serving PSCell if the network wants to use that PSCell as a candidate PSCell for subsequent CPAC. - The network always explicitly releases the subsequent CPAC configuration for candidate PSCells after an inter-MN PCell change. - Upon the release of SCG, the UE releases the stored subsequent CPAC configuration in SN format. Upon the release of SCG, the UE releases or maintains the stored subsequent CPAC configuration in MN format according to the network indication. - The same candidate PSCell configuration can be used for CPA execution and CPC execution, but with different execution conditions of the candidate PSCell. - The subsequent CPAC configuration with CPA execution condition(s) maintained after SCG release can be used for the subsequent CPA execution. - Upon inter-SN subsequent CPAC execution, the UE uses the first unused sk-Counter value for S-KgNB generation, based on the per-SN pre-configured sk-Counter value list. - Upon PCell change, PSCell change or SCG release, if the subsequent CPAC configuration is maintained, the UE also maintains the unused sk-Counter values. MN initiated subsequent CPAC The subsequent CPAC procedure is initiated by the MN for inter-SN subsequent CPAC configuration and inter-SN subsequent CPAC execution. Figure 10.20-1: Inter-SN subsequent CPAC - MN initiated Figure 10.20-1 shows an example signalling flow for the inter-SN subsequent CPAC initiated by the MN: 1/2/3/4. The MN initiates the inter-SN subsequent CPAC by requesting the candidate SN(s) to allocate resources for the UE by means of the SN Addition procedure, indicating that the request is for subsequent CPAC. The MN also provides the candidate cells recommended by MN via the latest measurement results for the candidate SN(s) to choose and configure the SCG cell(s), provides the upper limit for the number of PSCells that can be prepared by each candidate SN, and provides a list of KSN and associated sk-Counter values for each candidate SN. In the SN Addition procedure, the MN also includes information of other candidate SN(s), and for each candidate SN, a list of cells recommended by the MN via the latest measurement results for the candidate SN to select the PSCell(s) for the following execution of subsequent CPAC. Within the list of cells as indicated within the measurement results indicated by the MN, the candidate SN decides the list of PSCell(s) to prepare (considering the maximum number indicated by the MN) and, for each prepared PSCell, the candidate SN decides other SCG SCells and provides the new corresponding SCG radio resource configuration to the MN in an NR RRCReconfiguration** message contained in the SN Addition Request Acknowledge message with the prepared PSCell ID(s). For each prepared PSCell, the candidate SN also decides the list of PSCell(s) and associated execution conditions proposed for the following execution of subsequent CPAC. If data forwarding is needed, the candidate SN provides data forwarding addresses to the MN. The candidate SN may also propose data forwarding to the MN or other candidate SN(s) for subsequent CPAC. The candidate SN includes the indication of the complete or delta RRC configuration with respect to the SCG reference configuration. For the prepared PSCell(s) and the proposed PSCell(s) for the following execution of subsequent CPAC, the candidate SN can either accept or reject each of the candidate cells listed within the measurement results indicated by the MN, i.e. it cannot configure any alternative candidates. The MN may select one of the candidate SN(s) and requests providing the SCG reference configuration as part of the SN Addition procedure. Once obtained, the MN provides the SCG reference configuration to other candidate SN(s). NOTE 1: If the UE was configured with SN-1 in Dual Connectivity operation (i.e. SN-1 is the source SN), then the MN starts the subsequent CPAC operation with SN-1 via the MN-initiated SN Modification procedure instead of the SN Addition procedure. NOTE 2: If the UE was configured with SN-1 in Dual Connectivity operation (i.e. SN-1 is the source SN), then the MN may trigger the MN-initiated SN Modification procedure to SN-1 to retrieve the current SCG configuration or request a SCG reference configuration for the subsequent CPAC, and to allow provision of data forwarding related information before step 1. NOTE 3: If applicable, the MN stores the data forwarding addresses and data forwarding proposals provided from all the candidate SN(s). 5. For SN terminated bearers using MCG resources, the MN provides Xn-U DL TNL address information in the Xn-U Address Indication message to the candidate SN(s). 6/7. If the lists of prepared PSCells received from the candidate SN(s) in steps 2 and 4 are different than the lists of proposed PSCells, e.g., when not all proposed PSCells were accepted by the candidate SN(s), the MN may initiate the SN Modification procedures towards all the candidate SN(s) to inform them about the updated lists of prepared PSCells in other candidate SN(s). If requested, the candidate SN(s) sends an SN Modification Request Acknowledge message and if needed, provides the updated candidate SCG configurations and/or the execution conditions for the following execution of subsequent CPAC to the MN. 8. The MN sends to the UE an RRCReconfiguration message including the subsequent CPAC configuration, i.e. a list of RRCReconfiguration* messages and associated execution conditions for the subsequent CPAC, in which each RRCReconfiguration* message contains the SCG configuration in the RRCReconfiguration** message received from one of the candidate SN(s) in steps 2 and 4, and possibly an MCG configuration. Besides, the RRCReconfiguration message can also include an updated source MCG configuration, e.g., to configure the required conditional measurements. The RRCReconfiguration message also includes a security update configuration and may also include a reference configuration. 9. The UE applies the RRCReconfiguration message received in step 8, stores the subsequent CPAC configuration and replies to the MN with an RRCReconfigurationComplete message. In case the UE is unable to comply with (part of) the configuration included in the RRCReconfiguration message, it performs the reconfiguration failure procedure. 11. The UE starts evaluating the execution conditions. If the execution condition of one candidate PSCell is satisfied, the UE applies RRCReconfiguration* message corresponding to the selected candidate PSCell, and sends an MN RRCReconfigurationComplete* message, including an RRCReconfigurationComplete** message for the selected candidate PSCell, and information enabling the MN to identify the SN of the selected candidate PSCell. The RRCReconfigurationComplete* message may also include the sk-Counter value associated with the selected candidate PSCell if a new sk-Counter value is selected. 12. The MN informs the SN of the selected candidate PSCell that the UE has completed the reconfiguration procedure successfully via SN Reconfiguration Complete message, including the RRCReconfigurationComplete** message. If the sk-Counter value is received by the RRCReconfigurationComplete* message, the MN also indicates the received sk-Counter value to the SN. 13. The UE performs synchronisation towards the PSCell indicated in the RRCReconfiguration* message applied in step 11. The order the UE sends the MN RRCReconfigurationComplete* message and performs the Random Access procedure towards the SCG is not defined. The successful RA procedure towards the SCG is not required for a successful completion of the RRC Reconfiguration procedure. 14. If PDCP termination point is changed to the SN for bearers using RLC AM, and when RRC full configuration is not used, the MN sends the SN Status Transfer message. 15. For SN terminated bearers or QoS flows moved from the MN, dependent on the characteristics of the respective bearer or QoS flow, the MN may take actions to minimise service interruption due to activation of MR-DC (Data forwarding). 16. If data forwarding is needed, the MN may send the Xn-U Address Indication message to the selected candidate SN. The SN may decide to perform, if applicable, early data forwarding for SN-terminated bearers, together with the sending of an Early Status Transfer message to the source MN. NOTE 4: Separate Xn-U Address Indication procedures may be initiated to provide different forwarding addresses of the prepared subsequent CPAC. In this case, it is up to the MN and the candidate SN implementations to make sure that the Early Status Transfer message(s) from the selected SN, if any, is forwarded to the right other candidate SN. 18. The UE starts evaluating the execution conditions. If the execution condition of one candidate PSCell is satisfied, the UE applies RRCReconfiguration* message corresponding to the selected candidate PSCell, and sends an MN RRCReconfigurationComplete* message, including an RRCReconfigurationComplete** message for the selected candidate PSCell, and information enabling the MN to identify the SN of the selected candidate PSCell. The RRCReconfigurationComplete* message may also include a sk-Counter value associated with the selected candidate PSCell if a new sk-Counter value is selected. 19. The MN informs the SN of the selected candidate PSCell that the UE has completed the reconfiguration procedure successfully via SN Reconfiguration Complete message, including the RRCReconfigurationComplete** message. If the sk-Counter value is received by the RRCReconfigurationComplete* message, the MN also indicates the received sk-Counter value to the SN. 20. The UE performs synchronisation towards the PSCell indicated in the RRCReconfiguration* message applied in step 18. The order the UE sends the MN RRCReconfigurationComplete* message and performs the Random Access procedure towards the SCG is not defined. The successful RA procedure towards the SCG is not required for a successful completion of the RRC Reconfiguration procedure. 21/22/23. The MN triggers the MN initiated SN Modification procedure to inform the last serving SN to stop providing user data to the UE, to switch to the prepared state, and if applicable, to allow provisioning of new data forwarding addresses. If applicable, the MN triggers the Xn-U Address Indication procedure to inform the last serving SN the address of the SN of the selected candidate PSCell, to start late data forwarding. 24/25. If PDCP termination point is changed for bearers using RLC AM, and when RRC full configuration is not used, the SN sends the SN Status Transfer message to MN, which the MN sends then to the SN of the selected candidate PSCell, if needed. 26. If applicable, data forwarding from the last serving SN takes place. It may be initiated as early as the the last serving SN receives the early data forwarding address in step 17. 27. If data forwarding is needed, the MN may send the Xn-U Address Indication message to the selected candidate SN. The SN may decide to perform, if applicable, early data forwarding for SN-terminated bearers, together with the sending of an Early Status Transfer message to the source MN. NOTE 5: Separate Xn-U Address Indication procedures may be initiated to provide different forwarding addresses of the prepared subsequent CPAC. In this case, it is up to the MN and candidate SN implementations to make sure that the Early Status Transfer message(s) from the selected SN, if any, is forwarded to the right other candidate SN. SN initiated subsequent CPAC The subsequent CPAC procedure is initiated by the SN for inter-SN subsequent CPAC configuration and inter-SN subsequent CPAC execution. Figure 10.20-2: Inter-SN subsequent CPAC - SN initiated Figure 10.20-2 shows an example signalling flow for the inter-SN subsequent CPAC initiated by the source SN: 1. The source SN (i.e. SN-1) initiates the inter-SN subsequent CPAC procedure by sending the SN Change Required message, which contains a subsequent CPAC initiation indication. The message also contains candidate node ID(s) and may include an SCG reference configuration (to support delta configuration), and contains the measurements results which may include cells that are not subsequent CPAC candidates. The message also includes a list of proposed PSCell candidates recommended by the source SN, including execution conditions for the initial evaluation, the upper limit for the number of PSCells that can be prepared by each candidate SN, and may also include the SCG measurement configurations for subsequent CPAC (e.g. measurement ID(s) to be used for subsequent CPAC). 2/3/4/5. The MN requests each candidate SN(s) to allocate resources for the UE by means of the SN Addition procedure(s), indicating the request is for subsequent CPAC, and the measurements results which may include cells that are not subsequent CPAC candidates received from the source SN to the candidate SN, and indicating a list of proposed PSCell candidates to the candidate SN(s) received from the source SN, but not including execution conditions. The MN also includes information of other candidate SN(s), and for each candidate SN, a list of proposed PSCell candidates recommended by the source SN for the candidate SN to select the PSCell(s) for the following execution of subsequent CPAC. The MN also provides the upper limit for the number of PSCells that can be prepared by each candidate SN and provides a list of KSN and associated sk-Counter values for each candidate SN. Within the list of PSCells suggested by the source SN, the candidate SN decides the list of PSCell(s) to prepare (considering the maximum number indicated by the MN) and, for each prepared PSCell, the candidate SN decides other SCG SCells and provides the new corresponding SCG radio resource configuration to the MN in an NR RRCReconfiguration** message contained in the SN Addition Request Acknowledge message with the prepared PSCell ID(s). For each prepared PSCell, the candidate SN also decides the list of PSCell(s) and associated execution conditions proposed for the following execution of subsequent CPAC. If data forwarding is needed, the candidate SN provides data forwarding addresses to the MN. The candidate SN may also propose data forwarding to the MN or other candidate SN(s) for subsequent CPAC. The candidate SN includes the indication of the complete or delta RRC configuration with respect to the SCG reference configuration. For the prepared PSCell(s) and the proposed PSCell(s) for the following execution of subsequent CPAC, the candidate SN can either accept or reject each of the candidate cells suggested by the source SN, i.e. it cannot configure any alternative candidates. The MN may select one of the candidate SN(s) and requests providing the reference SCG configuration as part of the SN Addition procedure. Once obtained, the MN provides the reference configuration to other candidate SN(s). NOTE 6: The MN may trigger the MN-initiated SN Modification procedure (to the source SN) to request a reference configuration for the subsequent CPAC before step 2. NOTE 7: If applicable, the MN stores the data forwarding addresses and data forwarding proposals provided from all the candidate SN(s) and the source SN. 6. For SN terminated bearers using MCG resources, the MN provides Xn-U DL TNL address information in the Xn-U Address Indication message to the candidate SN(s). 7/8. If the lists of prepared PSCells received from the candidate SN(s) in steps 3 and 5 are different than the lists of proposed PSCells, e.g., when not all proposed PSCells were accepted by the candidate SN(s), the MN may initiate the SN Modification procedures towards the source SN and all the candidate SN(s) to inform them about the updated lists of prepared PSCells in other candidate SN(s). If requested, the source SN or the candidate SN(s) sends an SN Modification Request Acknowledge message and if needed, provides the updated candidate SCG configurations and/or the execution conditions for the following execution of subsequent CPAC for the prepared PSCell to the MN. 9. The MN sends to the UE an RRCReconfiguration message including the subsequent CPAC configuration, i.e. a list of RRCReconfiguration* messages and associated execution conditions for the subsequent CPAC, in which each RRCReconfiguration* message contains the SCG configuration in the RRCReconfiguration** message received from one of the candidate SN(s) in steps 3 and 5, and possibly an MCG configuration. Besides, the RRCReconfiguration message can also include an updated MCG configuration, as well as the NR RRCReconfiguration*** message generated by the source SN, e.g., to configure the required conditional measurements. The RRCReconfiguration message also includes a security update configuration and may also include a reference configuration. 10. The UE applies the RRCReconfiguration message received in step 9, stores the subsequent CPAC configuration and replies to the MN with an RRCReconfigurationComplete message, which can include an NR RRCReconfigurationComplete*** message. In case the UE is unable to comply with (part of) the configuration included in the RRCReconfiguration message, it performs the reconfiguration failure procedure. 11/12. If an SN RRC response message is included, the MN informs the source SN with the SN RRCReconfigurationComplete*** message via SN Change Confirm message. If step 7 and 8 towards the source SN are skipped, the MN will indicate the candidate PSCells accepted by each candidate SN to the source SN in the SN Change Confirm message. The MN sends the SN Change Confirm message towards the source SN to indicate that subsequent CPAC is prepared, and in such case the source SN continues providing user data to the UE. If early data forwarding is applied, the MN informs the source SN the data forwarding addresses as received from the candidate SN(s), the source SN, if applicable, together with the Early Status Transfer procedure, starts early data forwarding. The PDCP SDU forwarding may take place during early data forwarding. In case multiple candidate SNs are prepared, the MN includes a list of Target SN ID and list of data forwarding addresses to the source SN. NOTE 8: The Xn-U Address Indication procedure may further be invoked to indicate to the source SN to stop already initiated early data forwarding for some PDCP SDUs if they are no longer subject to data forwarding due to the modification or cancellation of the prepared conditional PSCell change. NOTE 9: For the early transmission of MN terminated split/SCG bearers, the MN forwads the PDCP PDU to the candidate SN(s). 13. The UE starts evaluating the execution conditions. If the execution condition of one candidate PSCell is satisfied, the UE applies RRCReconfiguration* message corresponding to the selected candidate PSCell, and sends an MN RRCReconfigurationComplete* message, including an RRCReconfigurationComplete** message for the selected candidate PSCell, and information enabling the MN to identify the SN of the selected candidate PSCell. The RRCReconfigurationComplete* message may also include the sk-Counter value associated with the selected candidate PSCell if a new sk-Counter value is selected. 14. The MN informs the SN of the selected candidate PSCell that the UE has completed the reconfiguration procedure successfully via SN Reconfiguration Complete message, including the RRCReconfigurationComplete** message. If the sk-Counter value is received by the RRCReconfigurationComplete* message, the MN also indicates the received sk-Counter value to the SN. 15. The UE performs synchronisation towards the PSCell indicated in the RRCReconfiguration* message applied in step 13. The order the UE sends the MN RRCReconfigurationComplete* message and performs the Random Access procedure towards the SCG is not defined. The successful RA procedure towards the SCG is not required for a successful completion of the RRC Reconfiguration procedure. 16/17/18. If the source SN is configured as a candidate SN, the MN triggers the MN initiated SN Modification procedure to inform the source SN to stop providing user data to the UE, to switch to the prepared state, and if applicable, to allow provisioning of new data forwarding addresses. If applicable, the MN triggers the Xn-U Address Indication procedure to inform the source SN the address of the SN of the selected candidate PSCell, to start late data forwarding. If the source SN is not configured as a candidate SN, the MN triggers the MN initiated SN Release procedure to inform the source SN to stop providing user data to the UE, and triggers the Xn-U Address Indication procedure to inform the source SN the address of the SN of the selected candidate PSCell and if applicable, starts late data forwarding. 19/20. If PDCP termination point is changed for bearers using RLC AM, and when RRC full configuration is not used, the SN sends the SN Status Transfer message to MN, which the MN sends then to the SN of the selected candidate PSCell, if needed. 21. If applicable, data forwarding from the source SN takes place. It may be initiated as early as the the source SN receives the early data forwarding address in step 12. 22. If data forwarding is needed, the MN may send the Xn-U Address Indication message to the selected candidate SN. The SN may decide to perform, if applicable, early data forwarding for SN-terminated bearers, together with the sending of an Early Status Transfer message to the source MN. NOTE 10: Separate Xn-U Address Indication procedures may be initiated to provide different forwarding addresses of the prepared subsequent CPAC. In this case, it is up to the MN and the candidate SN implementations to make sure that the Early Status Transfer message(s) from the selected SN, if any, is forwarded to the right other candidate SN. 24. In subsequent evaluation and execution phase, i.e., for the following execution of subsequent CPAC, the similar steps as steps 13~23 are performed. | 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.20 |
Subsets and Splits
No saved queries yet
Save your SQL queries to embed, download, and access them later. Queries will appear here once saved.