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
⌀ |
|---|---|---|---|---|---|---|---|
5,101 | – SL-SRAP-ConfigU2U | The IE SL-SRAP-ConfigU2U is used to set the configurable SRAP parameters used by L2 U2U Relay UE and L2 U2U Remote UE as specified in TS 38.351[ NR; Sidelink Relay Adaptation Protocol (SRAP) Specification ] [66]. SL-SRAP-ConfigU2U information element -- ASN1START -- TAG-SL-SRAP-CONFIGU2U-START SL-SRAP-ConfigU2U-r18 ::= SEQUENCE { sl-MappingToAddMod-U2U-List-r18 SEQUENCE (SIZE (1..maxSL-LCID-r16)) OF SL-MappingToAddMod-U2U-r18 OPTIONAL, -- Need N sl-MappingToRelease-U2U-List-r18 SEQUENCE (SIZE (1..maxSL-LCID-r16)) OF SLRB-Uu-ConfigIndex-r16 OPTIONAL -- Need N } SL-MappingToAddMod-U2U-r18 ::= SEQUENCE { sl-RemoteUE-SLRB-Identity-r18 SLRB-Uu-ConfigIndex-r16, sl-EgressRLC-ChannelPC5-r18 SL-RLC-ChannelID-r17, ... } -- TAG-SL-SRAP-CONFIGU2U-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,102 | 5.5.3.3 Sounding reference signal subframe configuration | The cell-specific subframe configuration period and the cell-specific subframe offset for the transmission of sounding reference signals are listed in Tables 5.5.3.3-1 and 5.5.3.3-2, for frame structures type 1 and 2 respectively, where the parameter srs-SubframeConfig is provided by higher layers. Sounding reference signal subframes are the subframes satisfying. For frame structure type 2, a sounding reference signal is transmitted only in uplink subframes or UpPTS. Table 5.5.3.3-1: Frame structure type 1 sounding reference signal subframe configuration Table 5.5.3.3-2: Frame structure type 2 sounding reference signal subframe configuration | 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.3.3 |
5,103 | 8.2.4.1.1 FDD PCell (FDD single carrier) | The parameters specified in Table 8.2.4.1.1-1 are valid for FDD CC and LAA SCell(s) unless otherwise stated. And the additional parameters specified in Table 8.2.4.1.1-2 are valid for LAA SCell(s). Table 8.2.4.1.1-1: Common Test Parameters Table 8.2.4.1.1-2: Addtional Test Parameters for LAA SCell(s) For CA with LAA SCell(s), the requirements are specified in Table 8.2.4.1.1-4, with the addition of the parameters in Table 8.2.4.1.1-1, Table 8.2.4.1.1-2, Table 8.2.4.1.1-3 and the downlink physical channel setup according to Annex C.3.2. The purpose of these tests is to verify the closed loop rank-two performance with frequency selective precoding for CA with LAA SCell(s). The test coverage for different number of component carriers is defined in 8.1.2.4. Table 8.2.4.1.1-3: Test Parameters for Dual-Layer Spatial Multiplexing (FRC) Table 8.2.4.1.1-4: Single carrier performance for PCell for multiple CA configurations Table 8.2.4.1.1-5: Single carrier performance for LAA SCell(s) for multiple CA configurations Table 8.2.4.1.1-6: Minimum performance (FRC) based on single carrier performance for CA with one LAA SCell Table 8.2.4.1.1-7: Minimum performance (FRC) based on single carrier performance for CA with two LAA SCells Table 8.2.4.1.1-8: Minimum performance (FRC) based on single carrier performance for CA with three LAA SCells Table 8.2.4.1.1-9: Minimum performance (FRC) based on single carrier performance for CA with four LAA SCells Table 8.2.4.1.1-10: Minimum performance (FRC) based on single carrier performance for CA with five LAA SCells Table 8.2.4.1.1-11: Minimum performance (FRC) based on single carrier performance for CA with six LAA SCells | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.2.4.1.1 |
5,104 | 4.22.8.2 UE or network requested MA PDU Session Modification (non-roaming and roaming with local breakout) | The signalling flow for a MA PDU Session Modification when the UE is not roaming, or when the UE is roaming and the PDU Session Anchor (PSA) is located in the VPLMN, is based on the signalling flow in Figure 4.3.3.2-1 with the following differences and clarifications: - In step 1b, the SMF may decide to update ATSSS rules and/or N4 rules based on updated PCC rules. - In step 1d, if the UPF determines that it cannot send GBR traffic over the current ongoing access e.g. based on the N4 rules and access availability and unavailability report from the UE, the UPF shall send Access Availability report to the SMF. When the SMF receives the Access Availability report, the SMF may decide to move the GBR QoS Flow to the other access as described in clause 5.32.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the SMF decides to move the GBR QoS Flow, the SMF triggers this procedure and afterwards moves the GBR QoS Flow to the target access. - In step 3, if the SMF decides to move the GBR QoS Flow to the other access, the SMF sends N2 SM information to the target AN. The PDU Session Modification Command message is sent to the UE to update ATSSS rule of the UE so that the UE sends uplink GBR traffic over the target access. The SMF releases AN resources of the GBR QoS Flow in the source access. - In step 3, when the SMF establishes user plane resources for a QoS flows, the SMF provides QoS profile to the AN as follows: - for Non-GBR QoS Flow, steps 3 to 8 are performed over each access for which the user plane resources are activated. - for GBR QoS Flow allowed in a single access, steps 3 to 8 are performed in the allowed access. - for GBR QoS Flow allowed in both accesses, steps 3 to 8 are performed in the access according to the decision by the SMF (as described in clause 5.32.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]). - In step 3, if the SMF wants to update ATSSS rules, the SMF includes updated ATSSS rules in the N1 SM container (PDU Session Modification Command). When the SMF provides N1 SM container and/or N2 SM information, the SMF includes access type in the Namf_Communication_N1N2MessageTransfer to provide routing information to the AMF. - In step 8, if the SMF decides to moves GBR QoS Flow to the other access, the SMF may send updated N4 rules to the UPF. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.22.8.2 |
5,105 | D.3.8.3 Execution phase | Figure D.3.8.3-1: GERAN A/Gb mode to E-UTRAN Inter RAT HO, execution phase NOTE 1: For a PMIP-based S5/S8, procedure steps (A) are defined in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [2]. Steps 9 and 9a concern GTP based S5/S8. The old SGSN continues to receive downlink and uplink user plane PDUs. When old SGSN receives the Forward Relocation Response message it may start downlink N-PDU relay and duplication to the target eNodeB, and the target eNodeB may start blind transmission of downlink user data towards the UE over the allocated radio channels. 1. The Source SGSN completes the preparation phase towards Source BSS by sending the message PS HO Required Acknowledge (TLLI, List of Set Up PFCs, Target to Source Transparent Container). This message includes all PFIs that could be established on the Target side. Before sending the PS Handover Required Acknowledge message, the source SGSN may suspend downlink data transfer for any PDP contexts. Before sending the PS Handover Command message to the UE the source BSS, may try to empty the downlink BSS buffer for any BSS PFCs. NOTE 2: The Source SGSN acts as the old SGSN. 2. The Source BSS will command the UE to handover to the target eNodeB via the message PS Handover Command. The access system specific message to UE includes a transparent container including radio aspect parameters that the Target eNodeB has set-up in the preparation phase. 3. There is no RAN context transfer during inter RAT handovers with E-UTRAN. If the source SGSN originates any SRNS contexts the MME acknowledges the receipt towards the SGSN and ignores the message content. 4. The UE moves to the E-UTRAN and performs access procedures toward Target eNodeB. 5. When the UE has got access to Target eNodeB it sends the message HO to E-UTRAN Complete. The UE shall implicitly derive the EPS bearers for which an E-RAB was not established from the PS Handover Command and deactivate them locally without an explicit NAS message at this step. 6. When the UE has successfully accessed the Target eNodeB, the Target eNodeB informs the Target MME by sending the message Handover Notify. Upon receipt of the Handover Notify message the target MME starts a timer if the target MME applies indirect forwarding. 7. Then the Target MME knows that the UE has arrived to the target side and Target MME informs the old SGSN by sending the Forward Relocation Complete () message. The old SGSN will also acknowledge that information. When the Forward Relocation Complete message has been received and there is no longer any need for the Old SGSN to forward data, the old SGSN stops data forwarding. A timer in old SGSN is started to supervise when resources shall be released. 8. The Target MME will now complete the Handover procedure by informing the Serving GW (for Serving GW relocation this will be the Target Serving GW) that the Target MME is now responsible for all the EPS bearers the UE have established. This is performed in the message Modify Bearer Request (Cause, MME Tunnel Endpoint Identifier for Control Plane, EPS Bearer ID(s), MME Address for Control Plane, eNodeB Address(es) and TEID(s) for User Traffic for the accepted EPS bearers, PDN GW addresses and TEIDs (for GTP-based S5/S8) or GRE keys (for PMIP-based S5/S8) at the PDN GW(s) for uplink traffic and RAT type) per PDN connection. If any EPS bearers are to be released the MME triggers the bearer release procedure as specified in clause 5.4.4.2. If the Serving GW receives a DL packet for a non-accepted bearer, the Serving GW drops the DL packet and does not send a Downlink Data Notification to the MME. NOTE 3: The text regarding "Target Serving GW" shall be ignored. 9. The Serving GW (for Serving GW relocation this will be the Target Serving GW) informs the PDN GW(s) the change of, for example, for Serving GW relocation or the RAT type, that e.g. can be used for charging, by sending the message Modify Bearer Request per PDN connection. Serving Network should be included in this message if it is received in step 4. For Serving GW relocation, the Serving GW allocates DL TEIDs on S5/S8 even for non-accepted bearers. The PDN GW must acknowledge the request with the message Modify Bearer Response (APN Restriction). When the UE moves from Gn/Gp SGSN to the MME, the PDN GW shall send the APN restriction of each bearer context to the Serving GW. If PCC infrastructure is used, the PDN GW informs the PCRF about the change of, for example, the RAT type. The Modify Bearer Response also indicates the identity of the default bearer and the Charging Id towards the S-GW. NOTE 4: The text regarding "Target Serving GW" shall be ignored. 10. The Serving GW (for Serving GW relocation this will be the Target Serving GW) acknowledges the user plane switch to the Target MME via the message Modify Bearer Response (Cause, Serving GW Tunnel Endpoint Identifier for Control Plane, Serving GW (for Serving GW relocation this will be the Target Serving GW) Address for Control Plane, Protocol Configuration Options, PDN GW addresses and TEIDs (for GTP-based S5/S8) or GRE keys (for PMIP-based S5/S8) at the PDN GW(s) for uplink traffic, APN Restriction).The Serving GW shall forward the received APN Restriction to the MME. At this stage the user plane path is established for all bearers between the UE, Target eNodeB, Serving GW (for Serving GW relocation this will be the Target Serving GW) and PDN GW. In addition, the Modify Bearer Response indicates the identity of the default bearer towards the MME. 11. When the timer started in step 7 expires the Source SGSN will clean-up all its resources towards Source BSS by performing the BSS Packet Flow Delete procedure. When the timer started in step 6 expires the target MME releases the resources that have been allocated for indirect forwarding. NOTE 5: The text regarding "Target Serving GW" shall be ignored. 12. The RAN triggers the UE to initiate a Tracking Area Update procedure with the target MME. It is RAN functionality to provide the ECM CONNECTED UE with the trigger information. The target MME knows that an IRAT Handover has been performed for this UE as it received the bearer context(s) by handover messages and therefore the target MME performs only a subset of the TA update procedure, specifically it excludes the context transfer procedures between source SGSN and target MME. The target MME gets the subscribed UE-AMBR value and the subscribed APN-AMBR value from the HSS during the TA update procedure. If the Subscription Data received from the HSS (during the TAU) contains information that is necessary for the E-UTRAN to be aware of (e.g. a restriction in the UE's permission to use NR as a secondary RAT, Unlicensed Spectrum in the form of LAA/LWA/LWIP/NR-U (as specified in clause 4.3.30) or a combination of them), or an existing UE context in the MME indicates that the UE is not permitted to use NR as a secondary RAT, Unlicensed Spectrum or a combination of them, and the MME has not provided this information to the target eNodeB during step 5 of the Handover preparation phase, then the MME sends an updated Handover Restriction List in the Downlink NAS Transport message that it sends to E-UTRAN. 13. The target MME calculates UE-AMBR as defined in clause 4.7.3. If this calculated value is different from the UE-AMBR computed during step 6, or the APN-AMBR mapped from the subscribed MBR is different from the subscribed APN-AMBR, or the mapped subscribed QoS profile (i.e. the subscribed QoS profile mapped according to Annex E) of the default bearer is different from the EPS Subscribed QoS profile received from the HSS, the new MME shall initiate Subscribed QoS Modification procedure as described in clause 5.4.2.2, Figure 5.4.2.2-1 | 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") | D.3.8.3 |
5,106 | 9.2.4 Resource pool | The subframe pools and resource block pools are defined in [4]. For PSSCH, the number of the current slot in the subframe pool , where is the number of the current slot within the current sidelink subframe with equal to the subscript of , defined in clauses 14.1.4 and 14.2.3 of [4] for sidelink transmission modes 1 and 2, respectively; and where is the number of the current slot within the current sidelink subframe with equal to the subscript of , defined in clauses 14.1.1.5 of [4] for sidelink transmission modes 3 and 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 | 9.2.4 |
5,107 | 5.17.2.3.2 Mobility for UEs in single-registration mode | When the UE supports single-registration mode and network supports interworking procedure without N26 interface: - For mobility from 5GC to EPC, the UE with at least one PDU Session established in 5GC may either: - if supported and if it has received the network indication that interworking without N26 is supported, perform Attach in EPC with a native EPS GUTI, if available, otherwise with IMSI with Request type "Handover" in PDN CONNECTIVITY Request message (clause 5.3.2.1 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [26]) and indicating that the UE is moving from 5GC and subsequently moves all its other PDU Session using the UE requested PDN connectivity establishment procedure with Request Type "handover" flag (clause 5.10.2 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [26]), or. - perform TAU with 4G-GUTI mapped from 5G-GUTI sent as old Native GUTI (clause 5.3.3 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [26]) indicating that it is moving from 5GC, in which case the MME instructs the UE to re-attach. IP address preservation is not provided in this case. - for the first TAU after 5GC initial Registration, the UE and MME for the handling of UE Radio Capabilities follow the procedures as defined in clause 5.11.2 TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [26] for first TAU after GERAN/UTRAN Attach. NOTE 1: The first PDN connection may be established during the E-UTRAN Initial Attach procedure (see TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [26]). NOTE 2: At inter-PLMN mobility to a PLMN that is not an equivalent PLMN the UE always uses the TAU procedure. - For mobility from 5GC to EPC, the UE with no PDU Session established in 5GC - performs Attach in EPC (clause 5.3.2.1 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [26]) indicating that the UE is moving from 5GC. - For mobility from EPC to 5GC, the UE performs Mobility Registration Update in 5GC with 5G-GUTI mapped from EPS GUTI and a native 5G-GUTI, if available, as Additional GUTI and indicating that the UE is moving from EPC. In this case, the AMF determines that old node is an MME, but proceeds as if the Registration is of type "initial registration". The UE may either: - if supported and if it has received the network indication "interworking without N26 supported", move all its PDN connections from EPC using the UE initiated PDU Session Establishment procedure with "Existing PDU Sessions" flag (clause 4.3.2.2.1 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]), or - re-establish PDU Sessions corresponding to the PDN connections that it had in EPS. IP address preservation is not provided in this case. NOTE 3: The additional native 5G-GUTI enables the AMF to find the UE's 5G security context (if available). NOTE 4: When single-registration mode UE uses interworking procedures without N26, the registration states during the transition period (e.g. while UE is transferring all PDU Sessions / PDN Connections on the target side) are defined in Stage 3 specifications. - If the network determines that the UE is changing RAT type, if the UE requests to relocate the PDU session from EPC to 5GC or 5GC to EPC, the SMF/MME uses the "PDU session continuity at inter RAT mobility" or "PDN continuity at inter-RAT mobility" information, respectively, in the subscription to determine whether to maintain the PDU session/PDN connection (if being handed over) or reject the PDU session request, with the relevant cause. - If the UE requested to move the PDU session and the "PDN continuity at inter RAT mobility" information indicated "disconnect the PDN connection with a reactivation request" the network should provide a suitable cause code to the UE so that it can request a new PDU session. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.17.2.3.2 |
5,108 | 5.1.3.2.2.4 EMM-REGISTERED | In the state EMM-REGISTERED an EMM context has been established. Additionally a default EPS bearer context has been activated in the UE: - if EMM-REGISTERED without PDN connection is not supported by the UE or the MME; or - if EMM-REGISTERED without PDN connection is supported by the UE and the MME, the UE has requested connectivity to a PDN and a default EPS bearer context is successfully established. When the UE is in EMM-IDLE mode, the UE location is known to the MME with an accuracy of a list of tracking areas containing a certain number of tracking areas. When the UE is in EMM-CONNECTED mode, the UE location is known to the MME with an accuracy of a serving eNodeB. The UE may initiate sending and receiving user data and signalling information and reply to paging. Additionally, tracking area updating or combined tracking area updating procedure is performed (see clause 5.5.3). | 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.1.3.2.2.4 |
5,109 | 6.26.2.3 Creation and management | The 5G network shall enable the network operator to scale up/down a 5G LAN-VN, e.g. the coverage, capacity for efficient consumption of network resources. The 5G network shall enable the network operator to create, manage, and remove 5G LAN-VN including their related functionality (subscription data, routing and addressing functionality). The 5G network shall enable the network operator to add one or more authorized UEs to an existing 5G LAN-VN. NOTE 1: A UE needs to be authorized by the MNO to use 5G LAN-type service before it can be added to any 5G LAN-VN. NOTE 2: some use cases will require user permission for a UE to be added to a 5G LAN-VN. The 5G system shall enable the network operator to add an authorized UE to multiple independent 5G LAN-VNs. The 5G network shall enable the network operator to remove one or more UEs from an existing 5G LAN-VN. NOTE 3: Removing a UE from a 5G LAN-VN does not have impact on other 5G LAN-VNs that the UE is a member of. The 5G system shall enable the network operator to configure a 5G LAN-VN that is available only within a geographical area. Based on MNO policy, the 5G network shall provide suitable means to allow an authorised third party to - monitor changes in QoS policy that pertains to LAN-VN performance; - configure and receive information regarding the achieved performance for a specific UE; - configure and receive information regarding the achieved performance for a specific network; - receive notification of changes in specific configuration aspects of the UE in the VN (e.g., changes in group membership information.) | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.26.2.3 |
5,110 | 5.2.2.7 Traffic channel assignment at mobile terminating call establishment | After receiving the SETUP message, the mobile station supporting multicall may either require a new traffic channel or reuse an existing traffic channel. If a mobile station in the network supporting multicall requires a new traffic channel, it shall: - send a CALL CONFIRMED message including the SI indicating a new value, not used by any of the existing traffic channels. If a mobile station in the network supporting multicall does not require a new traffic channel, it shall: - send a CALL CONFIRMED message including the SI equal to "no bearer". After the mobile station has send the CALL CONFIRMED with SI="no bearer", the SI value in the CONNECT message will tell to the network if a user requests a new traffic channel or one of the existing ones will be re-uesd. If a new traffic channel is requested by the user, the mobile station in the network supporting multicall shall: - send a CONNECT message containing the SI with a new value, not used by any existing traffic channel. If the user decides that an existing traffic channel will be reused, the mobile station in the network supporting multicall shall: - send a CONNECT message with an SI indicating an existing value used by an existing traffic channel. It is a network dependent decision when to initiate the assignment of a traffic channel during the mobile terminating call establishment phase. Initiation of the assignment phase does not directly change the state of a CC entity nor affect any call control timer, but may have some secondary effects (see e.g. subclause 5.2.2.3.2). | 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.2.7 |
5,111 | 4.1.2 Online charging | Online charging is a process where charging information for network resource usage is collected concurrently with that resource usage in the same fashion as in offline charging. However, authorization for the network resource usage must be obtained by the network prior to the actual resource usage to occur. This authorization is granted by the OCS or CCS upon request from the network. When receiving a network resource usage request, the network assembles the relevant charging information and generates a charging event towards the OCS or CCS in real-time. The OCS or CCS then returns an appropriate resource usage authorization. The resource usage authorization may be limited in its scope (e.g. volume of data or duration), therefore the authorization may have to be renewed from time to time as long as the user’s network resource usage persists. Note that the charging information utilized in online charging is not necessarily identical to the charging information employed in offline charging. In conclusion, online charging is a mechanism where charging information can affect, in real-time, the service rendered and therefore a direct interaction of the charging mechanism with the control of network resource usage is required. | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.1.2 |
5,112 | 4.5.1 Subscriber Data Update Notification to AMF | Whenever the user profile is changed for a user in the UDM/UDR and the changes affect the user profile in the AMF, the UDM shall notify these changes to the affected AMF by the means of invoking Nudm_SDM_Notification service operation. Then the AMF adds or modifies the user profile. The Nudm_SDM_Notification service operation specified in clause 5.2.3.3 is used by the UDM to update subscriber data stored in the AMF. The AMF takes appropriate action according to the changed subscriber data as follows, e.g.: - initiating an AMF initiated Deregistration procedure if the updated subscription data indicates the UE is not allowed to roam in this network; and - updating UE context stored at AN to modify the UE-AMBR. - updating UE context stored at RAN to modify the UE-Slice-MBR corresponding to an S-NSSAI. - initiating UE Configuration Update procedure as defined in clause 4.2.4.2. - initiating UE Parameters Update via UDM Control Plane Procedure as defined in clause 4.20. UDM can also use the Nudm_SDM_Notification service operation to update the Steering of Roaming information stored in the UE via the AMF (i.e. a list of preferred PLMN/access technology combinations and/or Credentials Holder controlled prioritized lists of preferred SNPNs and GINs and/or Credentials Holder controlled prioritized lists of preferred SNPNs and GINs for accessing Localized Services or HPLMN/Credentials Holder indication that 'no change of the above list(s) stored in the UE is needed'). UDM can include an indication for the UE to send an acknowledgement of the reception of this information. The AMF provides the acknowledgement sent from the UE to UDM using the Nudm_SDM_Info service operation. For more details regarding the handling of Steering of Roaming information refer to TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [22]. When the subscribed S-NSSAIs change, UDM provides a Network Slicing Subscription Change Indication to the UE via the AMF. Once the AMF updates the UE and obtains an acknowledgment from the UE, the AMF informs the UDM that the UE received the Network Slicing Subscription Change Indication using the Nudm_SDM_Info service operation. When the CAG information in the subscription data changes, or when the SUPI and PEI association changes, UDM provides a CAG information Subscription Change Indication to the AMF. Once the AMF updates the UE and obtains an acknowledgment from the UE, the AMF informs the UDM that the UE received the CAG information using the Nudm_SDM_Info service operation. If the AMF received a changed Service Gap Time parameter in the updated subscription data and if the UE has indicated Service Gap Control capability the AMF shall provide the new Service Gap Time value to the UE in the next Registration Accept message, or, if the UE does not send any Registration Request within a certain time period that shall be longer than any MICO mode or eDRX interval used by the UE, the AMF may initiate a UE Configuration Update procedure. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.5.1 |
5,113 | 5.15 Network slicing 5.15.1 General | A Network Slice instance is defined within a PLMN or within an SNPN and shall include: - the Core Network Control Plane and User Plane Network Functions, as described in clause 4.2, and, in the serving PLMN, at least one of the following: - the NG-RAN described in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27]; - the N3IWF or TNGF functions to the non-3GPP Access Network described in clause 4.2.8.2 or the TWIF functions to the trusted WLAN in the case of support of N5CW devices described in clause 4.2.8.5; - the W-AGF function to the Wireline Access Network described in clause 4.2.8.4. The 5G System deployed in a PLMN shall always support the procedures, information and configurations specified to support Network Slice instance selection in the present document, TS 23.502[ Procedures for the 5G System (5GS) ] [3] and TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. NOTE 1: Management of network slices are described in TS 28.530[ Management and orchestration; Concepts, use cases and requirements ] [175], the procedures for provisioning of networks and network slices are described in TS 28.531[ Management and orchestration; Provisioning ] [176] and TS 28.541[ Management and orchestration; 5G Network Resource Model (NRM); Stage 2 and stage 3 ] [149] describes the resource model for managing the resources. Network slicing support for roaming is described in clause 5.15.6. Network slices may differ for supported features and network functions optimisations, in which case such Network Slices may have e.g. different S-NSSAIs with different Slice/Service Types (see clause 5.15.2.1). The operator can deploy multiple Network Slices delivering exactly the same features but for different groups of UEs, e.g. as they deliver a different committed service and/or because they are dedicated to a customer, in which case such Network Slices may have e.g. different S-NSSAIs with the same Slice/Service Type but different Slice Differentiators (see clause 5.15.2.1). The network may serve a single UE with one or more Network Slice instances simultaneously via a 5G-AN regardless of the access type(s) over which the UE is registered (i.e. 3GPP Access and/or N3GPP Access). The AMF instance serving the UE logically belongs to each of the Network Slice instances serving the UE, i.e. this AMF instance is common to the Network Slice instances serving a UE. NOTE 2: Number of simultaneous connection of Network Slice instances per UE is limited by the number of S-NSSAIs in the Requested/Allowed NSSAI as described in clause 5.15.2.1. NOTE 3: In this Release of the specification it is assumed that in any (home or visited) PLMN it is always possible to select an AMF that can serve any combination of S-NSSAIs that will be provided as an Allowed NSSAI. The selection of the set of Network Slice instances for a UE is triggered by the first contacted AMF in a Registration procedure normally by interacting with the NSSF, and can lead to a change of AMF. This is further described in clause 5.15.5. A PDU Session belongs to one and only one specific Network Slice instance per PLMN. Different Network Slice instances do not share a PDU Session, though different Network Slice instances may have slice-specific PDU Sessions using the same DNN. During the Handover procedure the source AMF selects a target AMF by interacting with the NRF as specified in clause 6.3.5. Network Slice-Specific Authentication and Authorization (NSSAA) enables Network Slice specific authentication as described in clause 5.15.10. Network Slice Admission Control (NSAC) controls the number of registered UEs per network slice, the number of UEs with at least one PDU Session/PDN Connection per network slice in the case of EPC interworking and the number of PDU Sessions per network slice as described in clause 5.15.11. Support of subscription-based restrictions to simultaneous registration of network slices uses Network Slice Simultaneous Registration Group (NSSRG) information to enable control of which Network Slices that can be registered simultaneously by a UE as described in clause 5.15.12. Support of data rate limitation per Network Slice for a UE enables enforcement of Maximum Bit Rate per Network Slice for a UE as described in clause 5.15.13. The selection of N3IWF/TNGF supporting a set of slice(s) is described in clause 6.3.6 and clause 6.3.12 respectively. The support of Network Slice usage control is described in clause 5.15.15. Support of Optimized handling of temporarily available network slices is described in clause 5.15.16. It also covers aspects related to graceful release of network slices connectivity during slice decommissioning. The Partial Network Slice support in a Registration Area is described in clause 5.15.17. Support for Network Slices with Network Slice Area of Service not matching deployed Tracking Areas is described in clause 5.15.18. Support of Network Slice Replacement is described in clause 5.15.19. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.15 |
5,114 | 4.2.1 MAC Entities | E-UTRA defines two MAC entities; one in the UE and one in the E-UTRAN. These MAC entities handle the following transport channels: - Broadcast Channel (BCH); - Downlink Shared Channel(s) (DL-SCH); - Paging Channel (PCH); - Uplink Shared Channel(s) (UL-SCH); - Random Access Channel(s) (RACH); - Multicast Channel(s) (MCH); - Sidelink Broadcast Channel (SL-BCH); - Sidelink Discovery Channel (SL-DCH); - Sidelink Shared Channel (SL-SCH). The exact functions performed by the MAC entities are different in the UE from those performed in the E-UTRAN. The RN includes both types of MAC entities; one type for communication with UEs and one type for communication with the E-UTRAN. In Dual Connectivity, two MAC entities are configured in the UE: one for the MCG and one for the SCG. In DAPS handover, two MAC entities are configured in the UE: one MAC entity for the source cell (source MAC entity) and one MAC entity for the target cell (target MAC entity). Each MAC entity is configured by RRC with a serving cell supporting PUCCH transmission and contention based Random Access. In this specification, the term SpCell refers to such cell, whereas the term SCell refers to other serving cells. The term SpCell either refers to the PCell of the MCG or the PSCell of the SCG depending on if the MAC entity is associated to the MCG or the SCG, respectively. A Timing Advance Group containing the SpCell of a MAC entity is referred to as pTAG, whereas the term sTAG refers to other TAGs. The functions of the different MAC entities in the UE operate independently if not otherwise indicated. The timers and paramenters used in each MAC entity are configured independently if not otherwise indicated. The Serving Cells, C-RNTI, radio bearers, logical channels, upper and lower layer entities, LCGs, and HARQ entities considered by each MAC entity refer to those mapped to that MAC entity if not otherwise indicated. If the MAC entity is configured with one or more SCells, there are multiple DL-SCH and there may be multiple UL-SCH and RACH per MAC entity; one DL-SCH, one UL-SCH, and one RACH on the SpCell, one DL-SCH, zero or one UL-SCH and zero or one RACH for each SCell. The physical layer may perform a listen-before-talk procedure, according to which transmissions are not performed if the channel is identified as being occupied or the physical layer may monitor for PUSCH trigger, as specified in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2], according to which transmissions are not performed if PUSCH trigger B is not received. In both cases a MAC entity considers the transmission to have been performed anyway, unless stated otherwise. Figure 4.2.1-1 illustrates one possible structure for the UE side MAC entity when SCG is not configured and for each MAC entity during DAPS handover, and it should not restrict implementation. Figure 4.2.1-1: MAC structure overview, UE side Figure 4.2.1-2 illustrates one possible structure for the UE side MAC entities when MCG and SCG are configured, and it should not restrict implementation. MBMS reception and SC-PTM reception are excluded from this figure for simplicity. Figure 4.2.1-2: MAC structure overview with two MAC entities, UE side Figure 4.2.1-3 illustrates one possible structure for the UE side MAC entity when sidelink is configured, and it should not restrict implementation. Figure 4.2.1-3: MAC structure overview for sidelink, UE side | 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 | 4.2.1 |
5,115 | Y.5 Authentication and Authorization between message Gateway and MSGin5G Server | The authentication and authorization between Message Gateway and the MSGin5G Server can reuse the authentication and authorization between network functions in 13.3.2 in this document. In direct communication, authentication between message gateway and MSGin5GServer shall use one of the following methods: - If the PLMN uses protection at the transport layer as described in clause 13.1, authentication provided by the transport layer protection solution shall be used for authentication between message gateway and MSGin5GServer. - If the PLMN does not use protection at the transport layer, authentication between message gateway and MSGin5GServer may be implicit by NDS/IP or physical security. If the PLMN uses token-based authorization, the network shall use protection at the transport layer as described in clause 13.1. In indirect communication scenarios, 13.3.2 in this document also applies. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | Y.5 |
5,116 | 20.4.6 Abort-Session-Answer Command | The Abort-Session-Answer (ASA) command, defined in IETF RFC 6733 (DIAMETER BASE) [111], is indicated by the Command-Code set to 274 and the message flags’ ‘R’ bit clear, is sent in response to the ASR. The relevant AVPs that are of use for the SGmb interface are detailed in the ABNF description below. Other valid AVPs for this command are not used for SGmb purposes and should be ignored by the receiver or processed according to the relevant specifications. Message Format <ASA> ::= < Diameter Header: 274, PXY > < Session-Id > { Result-Code } { Origin-Host } { Origin-Realm } [ Origin-State-Id ] [ Error-Message ] [ Error-Reporting-Host ] [ Failed-AVP ] * [ Redirected-Host ] [ Redirected-Host-Usage ] [ Redirect-Max-Cache-Time ] * [ Proxy-Info ] [ Restart-Counter ] | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 20.4.6 |
5,117 | 5.37.5.2 PDU Set Information and Identification | To support PDU Set based QoS handling, the PSA UPF identifies PDUs that belong to PDU Sets and determines the below PDU Set Information which it sends to the NG-RAN in the GTP-U header. The PDU Set information is used by the NG-RAN for PDU Set based QoS handling as described above. The PDU Set Information comprises: - PDU Set Sequence Number. - Indication of End PDU of the PDU Set. - PDU Sequence Number within a PDU Set. - PDU Set Size in bytes. - PDU Set Importance, which identifies the relative importance of a PDU Set compared to other PDU Sets within a QoS Flow. The NG-RAN may use the Priority Level (see clause 5.7.3.3) across QoS Flows and PDU Set Importance within a QoS Flow for PDU Set level packet discarding in presence of congestion. NOTE 1: In addition to considering the PDU Set Importance within a QoS Flow, NG-RAN could also consider the relative PDU Set Importance across QoS Flows of the same Priority Level when determining which PDU Set needs to be discarded, which is up to implementation and configuration of operator. NOTE 2: The PDU Set Information can be different for different PDU Sets within a QoS Flow. The SMF instructs PSA UPF to perform PDU Set marking and may provide the PSA UPF the Protocol Description used by the service data flow. The Protocol Description may be received in the PCC rule, based on information provided by the AF or by PCF local policies as described in clause 5.37.5.1. PSA UPF can identify the PDU Set Information using the Protocol Description and the received transport protocol headers and payload or using implementation specific means. The details of the RTP/SRTP headers, header extensions and/or payloads used to identify PDU Set Information are defined in TS 26.522[ 5G Real-time Media Transport Protocol Configurations ] [179]. For each DL PDU received on N6 for which PDU Set based QoS handling is indicated from the SMF, the PSA UPF applies the rules for PDU Set identification and provides the available PDU Set Information to the RAN in the GTP-U header. NOTE 3: The PSA UPF is expected to assign a unique PDU Set Sequence Number in the GTP-U header to each PDU Set of the QoS Flow. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.37.5.2 |
5,118 | 5.20b.2 Support LADN service area for a group | The procedure as defined in clause 4.15.6.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] is applicable for provisioning of LADN service area for a group with the following clarifications and enhancements: - The AF request additionally contains the LADN service area as part of DNN and S-NSSAI specific Group Parameters, and the LADN service area is stored in UDR as subscription data and delivered to AMF. If the AMF receives the LADN service area for a group, the AMF configures the DNN of the group as LADN DNN. - If the AF provides the LADN service area in the form of geographical information, the NEF maps the geographical information to a list of TAs before sending the service area to the UDM. LADN per DNN and S-NSSAI as defined in clause 5.6.5a is applicable for enforcement of LADN service area. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.20b.2 |
5,119 | 5.2.13.2.2 Nbsf_Management_Register service operation | Service Operation name: Nbsf_Management_Register Description: Registers the tuple (UE address(es), SUPI, GPSI, MBS session ID, DNN, S-NSSAI, PCF address(es), PCF instance id, PCF Set ID, level of Binding) for a PDU Session or for a UE. NOTE 1: In some cases only subset of these parameters may be registered (e.g. UE address(es) will be registered only if PCF registration is for a PDU Session and for MBS sessions SUPI and GPSI are also not available). Inputs, Required: [Required, if PCF registration is for a PDU Session], UE address(es), PCF address(es), DNN [Required, if PCF registration is for a PDU Session], S-NSSAI [Required, if PCF registration is for a PDU Session], MBS session ID as defined in TS 23.247[ Architectural enhancements for 5G multicast-broadcast services ] [78] [Required, if PCF registration is for a MBS Session]. UE address can contain IP address/prefix or MAC address as defined in TS 23.501[ System architecture for the 5G System (5GS) ] [2]. It can optionally include Framed Route information. W-5GAN specific UE IP address information is specified in TS 23.316[ Wireless and wireline convergence access support for the 5G System (5GS) ] [53]. Framed Route information is defined in Table 5.2.3.3.1-1. NOTE 2: For support of time sensitive communication and time synchronization (as described in clause 5.28.3.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]) the UE address contains the DS-TT port MAC address for Ethernet type PDU Session. Inputs, Conditional: SUPI [Required, if PCF registration is for a UE or required by the local policy in PCF if the registration is for a PDU session, otherwise it is optional]. NOTE 3: The PCF can be configured to always provide a SUPI to the BSF, e.g. to support UE ID retrieval from the BSF. Inputs, Optional: GPSI, PCF instance ID and PCF Set ID, level of Binding (see clause 6.3.1.0 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]). NOTE 4: DNN and S-NSSAI are not applicable when the PCF registration is for a UE. NOTE 5: It is up to stage3 to ensure an unambiguous error proof way for the BSF to differentiate between PCF for a PDU Session and PCF for a UE. This may or may not require providing the BSF additional parameter(s) when a PCF registers itself with the BSF. Outputs, Required: Result indication, Binding Identifier for a PDU Session, or for a UE, or for an MBS session. Outputs, Optional: None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.13.2.2 |
5,120 | 5.9.2.2 NRF security requirements | The Network Repository Function (NRF) receives NF Discovery Request from an NF instance, provides the information of the discovered NF instances to the NF instance, and maintains NF profiles. The NRF receives from NF Service Consumers or SCPs access token requests for service consumption and provides authorization tokens. The NRF shall act as authorization server.The following NRF service-based architecture security requirements shall apply: NRF and NFs that are requesting service shall be mutually authenticated. NRF may provide authentication and authorization to NFs for establishing secure communication between each other. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 5.9.2.2 |
5,121 | 5.15.7 Network slicing and Interworking with EPS 5.15.7.1 General | A 5GS supports Network Slicing and might need to interwork with the EPS in its PLMN or in other PLMNs as specified in clause 5.17.2. The EPC may support the Dedicated Core Networks (DCN). In some deployments, the MME selection may be assisted by a DCN-ID provided by the UE to the RAN (see TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [26]). Mobility between 5GC to EPC does not guarantee all active PDU Session(s) can be transferred to the EPC. During PDN connection establishment in the EPC, the UE allocates the PDU Session ID and sends it to the SMF+PGW-C via PCO. As described in clause 4.11.0a.5 of TS 23.502[ Procedures for the 5G System (5GS) ] [3], an S-NSSAI associated with the PDN connection is determined based on the S-NSSAI(s) supported by the SMF+PGW-C, the Subscribed S-NSSAI from UDM, whether interworking with EPS is supported for the DNN and S-NSSAI in the Session Management Subscription data and the operator policy by the SMF+PGW-C, e.g. based on a combination of SMF+PGW-C address and APN, and is sent to the UE in PCO together with a PLMN ID that the S-NSSAI relates to. In Home Routed roaming case, the UE receives a HPLMN S-NSSAI value from the SMF+PGW-C. If the SMF+PGW-C supports more than one S-NSSAI and the APN is valid for more than one S-NSSAI, the SMF+PGW-C should only select an S-NSSAI that is mapped to the subscribed S-NSSAI of the UE and this subscribed S-NSSAI is not subject to Network Slice-Specific Authentication and Authorization. The UE stores this S-NSSAI and the PLMN ID associated with the PDN connection. The UE derives Requested NSSAI by taking into account of the received PLMN ID. The Requested NSSAI is included in the NAS Registration Request message and, subject to the conditions in clause 5.15.9, the RRC message carrying this Registration Request when the UE registers in 5GC if the UE is non-roaming or the UE has Configured NSSAI for the VPLMN in roaming case. If the UE has no Configured NSSAI of the VPLMN, the UE includes the HPLMN S-NSSAIs in the NAS Registration Request message as described in clause 5.15.5.2.1. When UE moves from EPS to 5GS, AMF reallocation may happen as described in clause 5.15.7.2 and clause 5.15.7.3. NOTE: It is assumed that if a MME is configured with a N26 interface towards an AMF, the MME has N26 interfaces with all AMFs serving the same area than the initial AMF and that can serve UE subject to EPS to 5GS mobility. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.15.7 |
5,122 | 24.2 ProSe Application ID 24.2.1 General | The ProSe Application ID is composed of two parts as follows: - The ProSe Application ID Name, which is described in its entirety by a data structure characterized by different levels e.g, broad-level business category (Level 0) / business sub-category (Level 1) / business name (Level 2) / shop ID (Level 3). - The PLMN ID, which corresponds to the PLMN that assigned the ProSe Application ID Name. The PLMN ID is placed before the ProSe Application ID Name as shown in Figure 24.2.1. The PLMN ID and the ProSe Application ID Name shall be separated by a dot. Figure 24.2.1-1: Structure of ProSe Application ID | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 24.2 |
5,123 | 4.15.13.5.2 Member UE Selection Assistance with Service Experience filtering criteria | Figure 4.15.13.5.2-1: 5GC assistance to Member UE selection based on Service Experience 1. AF subscribes to the Member UE selection assistance functionality by sending Nnef_MemberUESelectionAssistance_subscribe request including the Application Identity, AoI, DNN/S-NSSAI, DNAI(s), Service Experience Type and contribution weights associated to location, time window, Application ID and Service Experience type. 2. NEF verifies the authorization of the AF Request and identifies which information needs to be collected and executed based on the Service Experience filtering criteria provided by the AF. 3. If S-NSSAI/DNN and DNAI(s) are not included in the request from the AF, the NEF derives the S-NSSAI, DNN and DNAI(s) which this Application has access to. NEF discovers and selects the NWDAF(s) by invoking Nudm_UECM_Get or Nnrf_NFDiscovery_Request including Analytics ID = Service Experience, AoI, S-NSSAI, etc. 4. NEF sends an Analytics request/subscribe to NWDAF by invoking a Nnwdaf_AnalyticsInfo_Request or a Nnwdaf_AnalyticsSubscription_Subscribe, including Analytics ID = Service Experience, Application ID, S-NSSAI, DNN, AoI, DNAI(s), and target UEs based on the initial list obtained from the AF. 5-7. Procedures as specified in clause 6.4.6 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50] are followed. 8. The NWDAF provides the data analytics, i.e. the observed Service Experience (which can be a range of values) to the consumer NF by means of either Nnwdaf_AnalyticsInfo_Request response or Nnwdaf_AnalyticsSubscription_Notify, depending on the service used in step 4. 9. Based on the Analytics report received from the NWDAF, NEF consolidates results and derives the list(s) of candidate UE(s). For applying that, NEF may use the Service Experience type provided by the AF consumer in the filtering information and use operator policies to interpret a customized MoS. Additionally, NEF may use the contribution weight associated to an application and a Service Experience Type (e.g. AI/ML traffic) and apply them to a location and time window, as provided by the AF consumer, to be used as reporting thresholds when selecting candidate Member UEs, e.g. the NEF may select a UE with a specific Service Experience Type as a Member UE candidate, if the associated Service Experience fulfils the threshold for Service Experience filtering criteria provided by the AF. 10. NEF sends a Nnef_MemberUESelectionAssistance_Notify request to the AF including the list(s) of candidate UE(s) and additional information. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.13.5.2 |
5,124 | 5.5.3.5 Fixed network operators and other service providers | The settlement of accounts with the operators of fixed networks for traffic carried, is generally performed on a bulk basis according to the principles outlined in the ITU-T D-series recommendations. The traffic accounted for in this manner may include: - outgoing ( to Land) traffic; - incoming (Land to ) traffic; - transit traffic, carried by intermediate networks; - signalling (MAP/SCCP, CAP/SCCP) traffic such as location updates. Accounting information may also be required for the use of services provided by other operators such as short message service centres and other Value Added Service (VAS) providers. The charges for the various traffic shares may be determined on the basis of the CDRs generated by the network elements or on the basis of bulk counters (accounting meter records) in the gateway MSC servers (GMSC servers). For the purpose of the present document, the management information required is assumed to be derived from CDRs. The management of accounting meters is outside the scope of the present document. | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 5.5.3.5 |
5,125 | 6.1.3.2 Secondary PDP Context Activation Procedure | The purpose of this procedure is to establish an additional PDP context between the MS and the network for a specific Traffic Flow Template (TFT) and QoS profile on a specific NSAPI, when one or more PDP contexts has/have already been established for the particular PDP address and APN. The MS shall include a request for a TFT comprising at least one packet filter applicable for the uplink direction. Depending on the selected Bearer Control Mode being 'MS only' or 'MS/NW', the secondary PDP context activation procedure may either be initiated by the MS or by either the MS or the network, respectively. However, the network and the MS shall not initiate a secondary PDP context activation procedure for established PDP context of "non IP" PDP type. The network shall allocate packet filter identifiers and manage packet filter evaluation precedence for the packet filters added by the network. The MS shall allocate packet filter identifiers and manage packet filter evaluation precedence for the packet filters added by the MS. If there is a PDN connection for emergency bearer services established, the MS shall not initiate a secondary PDP context activation procedure for this connection unless triggered by the network. NOTE: 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [74] subclause 9.3 specifies that a packet filter applicable for the downlink direction is not mandatory in a TFT. | 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.2 |
5,126 | A.4.3.3 Typical example of evolution of IE with local extensions | The following example illustrates the use of the extension marker for a number of elementary cases (sequence, enumerated, choice). The example also illustrates how the IE may be revised in case the critical extension mechanism is used. NOTE In case there is a need to support further extensions of release n while the ASN.1 of release (n+1) has been frozen, without requiring the release n receiver to support decoding of release (n+1) extensions, more advanced mechanisms are needed e.g. including multiple extension markers. -- /example/ ASN1START InformationElement1 ::= SEQUENCE { field1 ENUMERATED { value1, value2, value3, value4-v880, ..., value5-v960 }, field2 CHOICE { field2a BOOLEAN, field2b InformationElement2b, ..., field2c-v960 InformationElement2c-r9 }, ..., [[ field3-r9 InformationElement3-r9 OPTIONAL -- Need R ]], [[ field3-v9a0 InformationElement3-v9a0 OPTIONAL, -- Need R field4-r9 InformationElement4 OPTIONAL -- Need R ]] } InformationElement1-r10 ::= SEQUENCE { field1 ENUMERATED { value1, value2, value3, value4-v880, value5-v960, value6-v1170, spare2, spare1, ... }, field2 CHOICE { field2a BOOLEAN, field2b InformationElement2b, field2c-v960 InformationElement2c-r9, ..., field2d-v12b0 INTEGER (0..63) }, field3-r9 InformationElement3-r10 OPTIONAL, -- Need R field4-r9 InformationElement4 OPTIONAL, -- Need R field5-r10 BOOLEAN, field6-r10 InformationElement6-r10 OPTIONAL, -- Need R ..., [[ field3-v1170 InformationElement3-v1170 OPTIONAL -- Need R ]] } -- ASN1STOP Some remarks regarding the extensions of InformationElement1 as shown in the above example: – The InformationElement1 is initially extended with a number of non-critical extensions. In release 10 however, a critical extension is introduced for the message using this IE. Consequently, a new version of the IE InformationElement1 (i.e. InformationElement1-r10) is defined in which the earlier non-critical extensions are incorporated by means of a revision of the original field. – The value4-v880 is replacing a spare value defined in the original protocol version for field1. Likewise value6-v1170 replaces spare3 that was originally defined in the r10 version of field1. – Within the critically extended release 10 version of InformationElement1, the names of the original fields/IEs are not changed, unless there is a real need to distinguish them from other fields/IEs. E.g. the field1 and InformationElement4 were defined in the original protocol version (release 8) and hence not tagged. Moreover, the field3-r9 is introduced in release 9 and not re-tagged; although, the InformationElement3 is also critically extended and therefore tagged InformationElement3-r10 in the release 10 version of InformationElement1. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | A.4.3.3 |
5,127 | 4.2.8a UE Capability Match Request procedure | If the AMF requires more information on the UE radio capabilities support to be able to set the IMS voice over PS Session Supported Indication (see clause 5.16.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]), then the AMF may send a UE Radio Capability Match Request message to the NG-RAN. This procedure is typically used during the registration procedure or when AMF has not received the Voice Support Match Indicator (as part of the 5GMM Context). Figure 4.2.8a-1: UE Capability Match Request 1. The AMF indicates whether the AMF wants to receive Voice support match indicator. The AMF may include the UE radio capability information it has previously received from NG-RAN. 2. Upon receiving the UE Capability Match Request message, if the NG-RAN has not already received the UE radio capabilities from the UE or from AMF in step 1, the NG-RAN requests the UE to upload the UE radio capability information. 3. The UE provides the NG-RAN with its UE radio capabilities sending the RRC UE Capability Information. 4. The NG-RAN checks whether the UE radio capabilities are compatible with the network configuration for ensuring voice service continuity of voice calls initiated in IMS. For determining the appropriate UE Radio Capability Match Response, the NG-RAN is configured by the operator to check whether the UE supports certain capabilities required for Voice continuity of voice calls using IMS PS. In a shared network, the NG-RAN keeps a configuration separately per PLMN. NOTE 1: What checks to perform depends on network configuration, i.e. following are some examples of UE capabilities to be taken into account: - E-UTRAN/NG-RAN Voice over PS capabilities; - the Radio capabilities for E-UTRAN/NG-RAN FDD and/or TDD; and/or - the support of E-UTRAN/NG-RAN frequency bands; - the SRVCC from NG-RAN to UTRAN capabilities and the support of UTRAN frequency bands. NOTE 2: The network configuration considered in the decision for the Voice Support Match Indicator is homogenous within a certain area (e.g. AMF Set) in order to guarantee that the Voice Support Match Indicator from the NG-RAN is valid within such area. The NG-RAN provides a Voice Support Match Indicator to the AMF to indicate whether the UE capabilities and networks configuration are compatible for ensuring voice service continuity of voice calls initiated in IMS. The AMF stores the received Voice support match indicator in the 5GMM Context and uses it as an input for setting the IMS voice over PS Session Supported Indication. 5. If NG-RAN requested radio capabilities from UE in step 2 and 3, the NG-RAN also sends the UE radio capabilities to the AMF. The AMF stores the UE radio capabilities without interpreting them for further provision to the NG-RAN according to clause 5.4.4.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. NOTE 3: Steps 4 and 5 could be received by the AMF in any order. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2.8a |
5,128 | 16.14.1 Overview | Figure 16.14.1-1 below illustrates an example of a Non-Terrestrial Network (NTN) providing non-terrestrial NR access to the UE by means of an NTN payload and an NTN Gateway, depicting a service link between the NTN payload and a UE, and a feeder link between the NTN Gateway and the NTN payload. Figure 16.14.1-1: Overall illustration of an NTN NOTE 1: Figure 16.14.1-1 illustrates an NTN; RAN4 aspects are out of scope. The NTN payload transparently forwards the radio protocol received from the UE (via the service link) to the NTN Gateway (via the feeder link) and vice-versa. The following connectivity is supported by the NTN payload: - An NTN gateway may serve multiple NTN payloads; - An NTN payload may be served by multiple NTN gateways. NOTE 2: In this release, the NTN-payload may change the carrier frequency, before re-transmitting it on the service link, and vice versa (respectively on the feeder link). For NTN, the following applies in addition to Network Identities as described in clause 8.2: - A Tracking Area corresponds to a fixed geographical area. Any respective mapping is configured in the RAN; - A Mapped Cell ID as specified in clause 16.14.5. Three types of service links are supported: - Earth-fixed: provisioned by beam(s) continuously covering the same geographical areas all the time (e.g., the case of GSO satellites); - Quasi-Earth-fixed: provisioned by beam(s) covering one geographic area for a limited period and a different geographic area during another period (e.g., the case of NGSO satellites generating steerable beams); - Earth-moving: provisioned by beam(s) whose coverage area slides over the Earth surface (e.g., the case of NGSO satellites generating fixed or non-steerable beams). With NGSO satellites, the gNB can provide either quasi-Earth-fixed service link or Earth-moving service link, while gNB operating with GSO satellite can provide Earth fixed service link. In this release, the UE supporting NTN is GNSS-capable. In NTN, the distance refers to Euclidean distance. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.14.1 |
5,129 | 6.7.1 Description | The 5G network will support many commercial services (e.g. medical) and regional or national regulatory services (e.g. MPS, Emergency, Public Safety) with requirements for priority treatment. Some of these services share common QoS characteristics such as latency and packet loss rate but can have different priority requirements. For example, UAV control and air traffic control can have stringent latency and reliability requirements but not necessarily the same priority requirements. In addition, voice-based services for MPS and Emergency share common QoS characteristics as applicable for normal public voice communications yet can have different priority requirements. The 5G network will need to support mechanisms that enable the decoupling of the priority of a particular communication from the associated QoS characteristics such as latency and reliability to allow flexibility to support different priority services (that need to be configurable to meet operator needs, consistent with operator policies and corresponding national and regional regulatory policies). The network needs to support flexible means to make priority decisions based on the state of the network (e.g. during disaster events and network congestion) recognizing that the priority needs can change during a crisis. The priority of any service can be different for a user of that service based on operational needs and regional or national regulations. Therefore, the 5G system should allow a flexible means to prioritise and enforce prioritisation among the services (e.g. MPS, Emergency, medical, Public Safety) and among the users of these services. The traffic prioritisation can be enforced by adjusting resource utilization or pre-empting lower priority traffic. The network must offer means to provide the required QoS (e.g. reliability, latency, and bandwidth) for a service and the ability to prioritize resources when necessary to meet the service requirements. Existing QoS and policy frameworks handle latency and improve reliability by traffic engineering. In order to support 5G service requirements, it is necessary for the 5G network to offer QoS and policy control for reliable communication with latency required for a service and enable the resource adaptations as necessary. The network needs to allow multiple services to coexist, including multiple priority services (e.g. Emergency, MPS and MCS) and must provide means to prevent a single service from consuming or monopolizing all available network resources, or impacting the QoS (e.g. availability) of other services competing for resources on the same network under specific network conditions. For example, it is necessary to prevent certain services (e.g. citizen-to-authority Emergency) sessions from monopolizing all available resources during events such as disaster, emergency, and DDoS attacks from impacting the availability of other priority services such as MPS and MCS. Also, as 5G network is expected to operate in a heterogeneous environment with multiple access technologies, multiple types of UE, etc., it should support a harmonised QoS and policy framework that applies to multiple accesses. Further, for QoS control in EPS only covers RAN and core network, but for 5G network E2E QoS (e.g. RAN, backhaul, core network, network to network interconnect) is needed to achieve the 5G user experience (e.g. ultra-low latency, ultra-high bandwidth). | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.7.1 |
5,130 | 6.9.3 Key handling in mobility registration update | The procedure shall be invoked by the target AMF after the receiving of a Registration Request message of type mobility registration update from the UE wherein the UE and the source AMF are identified by means of a temporary identifier 5G-GUTI. The protocol steps for the source AMF and target AMF performing context transfer are as follows: a) The target AMF sends a message to the source AMF, this message contains the 5G-GUTI, the Access Type and the received Registration Request message. b) The source AMF searches the data of the UE in the database and checks the integrity protection on the Registration Request message. The source AMF uses the 5G NAS security context corresponding to the Access Type to perform the integrity check. i) If the UE is found and the integrity check succeeds, when the source AMF does not change KAMF according to its local policy, the source AMF shall send a response back that: - shall include the SUPI, and - may include any current 5G security context it holds. ii) If the UE is found and the integrity check succeeds, when the source AMF changes KAMF according to its local policy, the source AMF shall send a response back that: - shall include the SUPI, - keyAmfHDerivationInd, and - may include a new 5G security context it derives from the current one it holds. The source AMF subsequently deletes the 5G security context which it holds. If the UE cannot be identified or the integrity check fails, then the source AMF shall send a response indicating that the temporary identifier 5G-GUTI cannot be retrieved. c) If the target AMF receives a response with a SUPI, it creates an entry and stores the 5G security context that may have beenreceived . If the target AMF receives a response indicating that the UE could not be identified, it shall initiate the subscription identification procedure described in clause 6.12.4 of the present document. NOTE: Void. NOTE 1: The source AMF does not have KSEAF because it is deleted after KAMF derivation as per clause 6.2.2.1 and therefore the context transfer from the source AMF to the target AMF does not contain KSEAF. At mobility registration update, the source AMF shall use local policy to determine whether to perform horizontal KAMF derivation. If the source AMF determines not to perform horizontal KAMF derivation, the source AMF shall transfer current security context to the target AMF. If the source AMF determines to perform horizontal KAMF derivation, the source AMF shall derive a new key KAMF from the currently active KAMF and the uplink NAS COUNT value in the received Registration Request message. The ngKSI for the newly derived KAMF key is defined such as the value field and the type field are taken from the ngKSI of the current KAMF. The source AMF shall transfer the new KAMF, the new ngKSI, the UE security capability, the keyAmfHDerivationInd to the target AMF. The key derivation of the new KAMF is specified in Annex A.13. If the source AMF has derived a new key KAMF, the source AMF shall not transfer the old KAMF to the target AMF and the source AMF shall in this case also delete any stored non-current 5G security context, and not transfer any non-current 5G security context to the target AMF. When the target AMF receives the new KAMF together with the keyAmfHDerivationInd, then the target AMF shall decide whether to use the KAMF directly according to its local policy after receiving the response from the source AMF. If the target AMF, according to its local policy, decides to not use the KAMF received from the source AMF, it can perform a re-authentication procedure to the UE to establish a new NAS security context. If the target AMF decides to use the key KAMF received from source AMF (i.e., no re-authentication), it shall send the K_AMF_change_flag set to 1 to the UE in the NAS SMC including replayed UE security capabilities, the selected NAS algorithms and the ngKSI for identifying the new KAMF from which the UE shall derive a new KAMF to establish a new NAS security context between the UE and target AMF. The target AMF shall reset the NAS COUNTs to zero and derive new NAS keys (KNASint and KNASenc) from the new KAMF using the selected NAS algorithm identifiers as input. The target AMF shall integrity protect the NAS Security Mode Command message with the new KNASint key. If the UE receives the K_AMF_change_flag set to 1 in the NAS Security Mode Command message, then the UE shall derive a new key KAMF from the current active KAMF identified by the received ngKSI in the NAS Security Mode Command message using the uplink NAS COUNT valuethat was sent in the Registration Request message. The UE shall assign the received ngKSI in the NAS Security Mode Command message to the ngKSI of the new derived KAMF. The UE shall derive new NAS keys (KNASint and KNASenc) from the new KAMF and integrity check the NAS Security Mode Command message using the new KNASint key. The UE shall then derive a new initial KgNB from the new KAMF as specified in Annex A.9. The UE shall associate the derived new initial KgNB with a new NCC value equal to zero and reset the NAS COUNTs to zero. After the ongoing mobility registration procedure is successfully completed, the ME shall replace the currently stored KAMF and ngKSI values on both USIM and ME with the new KAMF and the associated ngKSI. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.9.3 |
5,131 | 6.36.1 Overview | 5G systems rely on reference precision timing signals for network synchronization in order to operate. These synchronization references are generated by Primary reference Time Clocks that typically get the timing reference from GNSS receivers and in order to meet the relevant synchronization requirements also during failure conditions, the synchronization network designs typically include means to address potential degradation of the GNSS signal performance. Some deployment of 5G involve applications that themselves can be sensitive to any degradation of the timing signal. In such cases it is beneficial for the 5G system to be enhanced to act as a backup for loss of their GNSS references. In some implementations, timing resiliency enhancements to the 5G system can work in collaboration with different types of time sources (e.g., atomic clock, time service delivered over the fibre) to provide a robust time synchronization. 5G as a consumer of time synchronization benefits from timing resiliency which enables the support of many critical services within the 5G network even during the event of a loss or degradation of the primary GNSS reference timing. Additionally, for time critical services (e.g. financial sector or smart grid), the 5G system can operate in collaboration with or as backup to other timing solutions. A base of clock synchronization requirements when 5G is providing a time signal, if it is deployed in conjunction with an IEEE TSN network or if it is providing support for IEEE 1588 related protocols, is included in [21] clause 5.6. The enhancements in this clause build on this to add timing resiliency to the 5G system enabling its use as a replacement or backup for other timing sources. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.36.1 |
5,132 | 8.19 EPS Bearer Level Traffic Flow Template (Bearer TFT) | EPS Bearer Level Traffic Flow Template (Bearer TFT) is transferred via GTP tunnels. The sending entity copies the value part of the EPS Bearer Level TFT into the Value field of the EPS Bearer Level TFT IE. The detailed coding and maximum length of the EPS Bearer Level TFT IE is specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [5], clause 10.5.6.12, beginning with octet 3. Figure 8.19-1: EPS Bearer Level Traffic Flow Template (Bearer TFT) | 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.19 |
5,133 | 8.21.1 CGI field | The coding of CGI (Cell Global Identifier) is depicted in Figure 8.21.1-1. Only zero or one CGI field shall be present in ULI IE. Figure 8.21.1-1: CGI field The Location Area Code (LAC) consists of 2 octets. Bit 8 of Octet a+3 is the most significant bit and bit 1 of Octet a+4 the least significant bit. The coding of the location area code is the responsibility of each administration. Coding using full hexadecimal representation (binary, not ASCII encoding) shall be used. The Cell Identity (CI) consists of 2 octets. Bit 8 of Octet a+5 is the most significant bit and bit 1 of Octet a+6 the least significant bit. The coding of the cell identity is the responsibility of each administration. Coding using full hexadecimal representation (binary, not ASCII encoding) shall be used. | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 8.21.1 |
5,134 | 8.3.1.1H Single-layer Spatial Multiplexing (With Enhanced DMRS table configured) | For single-layer transmission on antenna port 7, 8, 11 or 13 upon detection of a PDCCH with DCI format 2C, the requirement is specified in Table 8.3.1.1H-2, with the addition of the parameters in Table 8.3.1.1H-1 and the downlink physical channel setup according to Annex C.3.2. The purpose of the test is to verify rank-1 performance on antenna port 11 with a simultaneous transmission on the antenna port 7, 8 or 13 with DMRS enhancement table and 4 orthogonal DMRS ports (dmrs-Enhancements-r13 UE-EUTRA-Capability [7]). Table 8.3.1.1H-1: Test Parameters for Testing CDM-multiplexed DM RS (single layer) with interfering simultaneous transmission (FRC) with multiple CSI-RS configurations with Enhanced DMRS table Table 8.3.1.1H-2: Minimum performance for CDM-multiplexed DM RS with interfering simultaneous transmission (FRC) with multiple CSI-RS configurations with Enhanced DMRS table | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.3.1.1H |
5,135 | 6.8C.5 Mapping to resource elements | The mapping to resource elements is defined by operations on vectors of complex-valued symbols. Let denotes symbol vector and represents the signal for antenna port. The block of vectors , shall be mapped in sequence starting with to resource elements on the associated antenna port(s) which meet all of the following criteria: - they are part of the SREGs assigned for the SPDCCH transmission, and - they are assumed by the UE not to be used for cell-specific reference signals, where the positions of the cell-specific reference signals are given by clause 6.10.1.2 with the number of antenna ports and the frequency shift of cell-specific reference signals derived as described in clause 6.10.1.2 unless other values for these parameters are provided by clause 9.1.4.3 in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4], and - they are assumed by the UE not to be used for transmission of: - UE-specific reference signal associated with SPDCCH - zero-power CSI reference signals, where the positions of the CSI reference signals are given by clause 6.10.5.2. The configuration for zero power CSI reference signals is - obtained as described in clause 6.10.5.2 unless other values are provided by clause 9.1.4.3 in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4], and - obtained by higher-layer configuration of up to five reserved CSI-RS resources as part of the discovery signal configuration following the procedure for zero-power CSI-RS in clause 6.10.5.2. - non-zero-power CSI reference signals for CSI reporting with the configuration for non-zero power CSI reference signals for CSI reporting obtained as described in clause 6.10.5.2. - The set of indices of where the SPDCCH can be mapped to is dependent on if slot or subslot based SPDCCH is used, the subslot number, if CRS or DMRS based SPDCCH is configured and the number of symbols used for PDCCH. In case CRS based SPDCCH is configured, the set of indices is also dependent on the number of symbols, , configured by higher layers (see spdcch-NoOfSymbols in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [9]), that the SPDCCH is mapped over. - For slot-SPDCCH and for frame structure type 1 and 2, the set of indices of for the second slot in the subframe is given in Table 6.8C.5-1. It can be noted that no SPDCCH is transmitted in the first slot of the subframe, where the DCI instead is carried in PDCCH, see [3]. - For subslot-SPDCCH and for frame structure type 1, the set of indices of for a given downlink subslot number in a subframe is given in Table 6.8C.5-2. It can be noted that for subslot number 0 where no SPDCCH is transmitted, and the DCI is instead carried in PDCCH, see [3]. If has been precoded according to clause 6.3.4.3 and if there is an uneven number of resource elements per PRB that fulfil all the above criteria, is not mapped to the resource element of the PRB with largest . Resource elements belonging to synchronization signals, the core part of PBCH, PBCH repetitions, or resource elements reserved for reference signals in the mapping operation of PBCH but not used for transmission of reference signals, shall be assumed available in the SPDCCH mapping but not used for transmission of SPDCCH. NOTE: For DMRS based SPDCCH, the UE is not required to use the PRGs of size 2 (see TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4]) which is/are partially overlapped with PBCH/PSS/SSS for SPDCCH monitoring. For DMRS based SPDCCH, the mapping to resource elements on antenna port , meeting the criteria above, shall be in increasing order of first the index and then the index . For localized and distributed CRS based SPDCCH, the SREGs of a SPDCCH candidate are first interleaved according to step 1 below and then the modulated symbols are mapped to resource elements of the interleaved SREGs according to step 2 below. - Step 1: Perform a block interleaver on the SREGs building the SPDCCH candidate, where the number of rows equal to the number of SCCEs for the SPDCCH candidate and the number of columns equal to 4 (i.e. the number of SREGs in an SCCE). The SREGs are written into the matrix row by row and read out column by column. - Step 2: The modulated symbols are mapped in sequence starting with to resource elements on antenna port in increasing order of the index k, meeting the criteria above, over the interleaved SREGs in the order given by the block interleaver of step 1. Table 6.8C.5-1: Set of indices of for slot-SPDCCH Table 6.8C.5-2: Set of indices of for subslot-SPDCCH | 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.8C.5 |
5,136 | 4.23.16a Handover of a PDU Session procedure between 3GPP and trusted non-3GPP access 4.23.16a.1 General | The handover of a PDU Session between 3GPP access and trusted non-3GPP access shall be supported as specified in clause 4.23.16 for all types of handover of a PDU Session between 3GPP access and untrusted non-3GPP access, with the following modifications and clarifications: - The untrusted non-3GPP access is substituted by a trusted non-3GPP access point (TNAP). - The N3IWF is substituted by the TNGF. - The reference to clause 4.9.2 is substituted by clause 4.9.3 specifying handover of a PDU Session procedure between 3GPP and trusted non-3GPP access. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.23.16a |
5,137 | 9.11.4.17 Re-attempt indicator | The purpose of the Re-attempt indicator information element is to indicate a condition under which the UE is allowed in the current PLMN or its equivalent PLMN(s) or the current SNPN or its equivalent SNPNs for the same DNN, to re-attempt a session management procedure (see 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]) corresponding to the 5GS session management procedure which was rejected by the network. The Re-attempt indicator information element is coded as shown in figure 9.11.4.17.1 and table 9.11.4.17.1. The Re-attempt indicator is a type 4 information element with a length of 3 octets. Figure 9.11.4.17.1: Re-attempt indicator Table 9.11.4.17.1: Re-attempt indicator | 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.17 |
5,138 | 10.5.1.9 Descriptive group or broadcast call reference | The purpose of the Descriptive Group or Broadcast Call Reference is to provide information describing a voice group or broadcast call. The IE of the Descriptive Group or Broadcast Call Reference is composed of the group or broadcast call reference together with a service flag, an acknowledgement flag, the call priority and the group cipher key number. The Descriptive Group or Broadcast Call Reference information element is coded as shown in figure 10.5.8/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and Table10.5.8/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] The Descriptive Group or Broadcast Call Reference is a type 3 information element with 6 octets length. Figure 10.5.8/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Descriptive Group or Broadcast Call Reference Table 10.5.8/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Descriptive Group or Broadcast Call Reference | 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.1.9 |
5,139 | 4.23.4.3 UE Triggered Service Request with I-SMF insertion/change/removal | When, as part of a UE Triggered Service Request, I-SMF is to be inserted, changed or removed, the procedure in this clause is used. It includes the following cases: - the UE moves from SMF service area to new I-SMF service area, a new I-SMF is inserted (i.e. I-SMF insertion); or - the UE moves from old I-SMF service area to new I-SMF service area, the I-SMF is changed (i.e. I-SMF change); or - the UE moves from old I-SMF service area to SMF service area, the old I-SMF is removed (i.e. I-SMF removal). If the service request is triggered by network due to downlink data and a new I-UPF is selected, forwarding tunnel is established between the old I-UPF(if the old I-UPF is different from PSA) and the new I-UPF to forward buffered data. For Home Routed Roaming case, the I-SMF (old and new) and I-UPF (old and new) are located in Visited PLMN, while the SMF and UPF(PSA) are located in the Home PLMN. In this HR roaming case only the case of I-SMF change applies (there is always a V-SMF for the PDU Session). Figure 4.23.4.3-1: UE Triggered Service Request procedure with I-SMF insertion/change/removal 1. Same as the steps 1-3 defined clause 4.2.3.2. 2. The AMF determines whether new I-SMF needs to be selected based on UE location and service area of the SMF, if new I-SMF needs to be selected, the AMF selects a new I-SMF as described in clause 4.23.2. Case: I-SMF insertion or I-SMF change, steps 3-9 are skipped for I-SMF removal case. 3. If the AMF has selected a new I-SMF, the AMF sends a Nsmf_PDUSession_CreateSMContext Request (PDU Session ID, SM Context ID, UE location info, Access Type, RAT Type, Operation Type) to the new I-SMF. The SM Context ID points to the old I-SMF in the case of I-SMF change or to SMF in the case of I-SMF insertion. The AMF Set the Operation Type to "UP activate" to indicate establishment of N3 tunnel User Plane resources for the PDU Session(s). The AMF determines Access Type and RAT Type based on the Global RAN Node ID associated with the N2 interface. If the UE Time Zone has changed compared to the last reported UE Time Zone then the AMF shall include the UE Time Zone IE in this message. 4a. The new I-SMF retrieves SM Context from the old I-SMF (in the case of I-SMF change) or SMF (in the case of I-SMF insertion) by invoking Nsmf_PDUSession_Context Request (SM context type, SM Context ID). The new I-SMF uses SM Context ID received from AMF for this service operation. SM Context ID is used by the recipient of Nsmf_PDUSession_Context Request in order to determine the targeted PDU Session. SM context type indicates that the requested information is all SM context, i.e. PDN Connection Context and 5G SM context. 4b. The old I-SMF in the case of I-SMF change or SMF in the case of I-SMF insertion responds with the SM context of the indicated PDU Session. If there is Extended Buffering is applied and the Extended Buffering timer is still running in old-SMF or old I-UPF, or the service request is triggered by downlink data, the old I-SMF or SMF includes a forwarding indication in the response to indicate that a forwarding tunnel is needed for sending buffered downlink packets. For I-SMF insertion, if I-UPF controlled by SMF was available for the PDU Session, the SMF includes a forwarding indication. 5. The new I-SMF selects a new I-UPF: Based on the received SM context, e.g. S-NSSAI and UE location information, the new I-SMF selects a new I-UPF as described in clause 6.3.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 6. The new I-SMF initiates a N4 Session Establishment to the new I-UPF. The new I-UPF provide tunnel endpoints to the new I-SMF. If forwarding indication was received, the new I-SMF also requests the new I-UPF to allocate tunnel endpoints to receive the buffered DL data from the old I-UPF and to indicate end marker reception on this tunnel via usage reporting. In this case, the new I-UPF begins to buffer the downlink packet(s) received from the UPF (PSA). 7a. If the tunnel endpoints for the buffered DL data were allocated, the new I-SMF invokes Nsmf_PDUSession_UpdateSMContext Request (tunnel endpoints for buffered DL data) to the old I-SMF in the case of I-SMF change in order to establish the forwarding tunnel. The new I-SMF uses the SM Context ID received from AMF for this service operation. 7b. The old I-SMF, in the case of I-SMF change initiates a N4 session modification to the old I-UPF to send the tunnel endpoints for buffered DL data to the old I-UPF. After this step, the old I-UPF starts to send buffered DL data to the new I-UPF. If the old I-UPF receives end marker packets and there is no associated tunnel to forward these packets, the old I-UPF discards the received end marker packets and does not send any Data Notification to SMF. 7c. The old I-SMF, in the case of I-SMF change responds the new I-SMF with Nsmf_PDUSession_UpdateSMContext response. 8a. In the case of I-SMF change, the new I-SMF invokes Nsmf_PDUSession_Update Request (SM Context ID, new I-UPF DL tunnel information, SM Context ID at I-SMF, Access Type, RAT Type, DNAI list supported by the new I-SMF, Operation Type) towards the SMF. The new I-SMF uses the SM Context ID at SMF received from old I-SMF for this service operation. In the case of I-SMF insertion, the new I-SMF invokes Nsmf_PDUSession_Create Request (new I-UPF DL tunnel information, new I-UPF tunnel endpoint for buffered DL data, SM Context ID at I-SMF, Access Type, RAT type, DNAI list supported by the new I-SMF, Operation Type) towards the SMF. The SM Context ID at I-SMF is to be used by the SMF for further PDU Session operation, e.g. to notify the new I-SMF of PDU Session Release. If SM Context ID at the I-SMF exists (i.e. in the case of I-SMF change), the SMF shall replace the SM Context ID at I-SMF. The new I-UPF tunnel endpoint for buffered DL data is used to establish the forwarding tunnel (from old I-UPF controlled by SMF to new I-UPF controlled by new I-SMF). If the old I-UPF receives end marker packets and there is no associated tunnel to forward these packets, the old I-UPF discards the received end marker packets and does not send any Data Notification to SMF. The Operation Type is set to "UP activate" to indicate that User Plane resource for the PDU Session is to be established. 8b. The SMF initiates N4 Session Modification toward the PDU Session Anchor UPF. During this step: - The SMF provides the new I-UPF DL tunnel information. - If different CN Tunnel Info need be used by PSA UPF, i.e. the CN Tunnel Info at the PSA for N3 and N9 are different, a CN Tunnel Info for the PDU Session Anchor UPF is allocated. - For I-SMF insertion, if a new I-UPF tunnel endpoint for buffered DL data is received, the SMF triggers the transfer of buffered DL data to the new I-UPF tunnel endpoint for buffered DL data. If the DL tunnel information has changed, the SMF indicates the UPF (PSA) to send one or more "end marker" packets for each N9 tunnel to the old I-UPF immediately after switching the path to new I-UPF. From now on the PDU Session Anchor UPF begins to send the DL data to the new I-UPF as indicated in the new I-UPF DL tunnel information. The UPF (PSA) sends one or more "end marker" packets for each N9 tunnel to the old I-UPF immediately after switching the path to new I-UPF. If indicated by the new I-SMF in step 6, the new I-UPF reports to SMF when "end marker" has been received. The new SMF initiates N4 Session Modification procedure to indicate the new I-UPF to send the DL packet(s) received from the UPF (PSA). 8c. The SMF responds to the new I-SMF with Nsmf_PDUSession_Update Response (the DNAI(s) of interest for this PDU Session in the case of I-SMF change) or Nsmf_PDUSession_Create Response (the DNAI(s) of interest for this PDU Session, Tunnel Info at UPF(PSA) for UL data in the case of I-SMF insertion if it is allocated in step 8b). In the case of I-SMF insertion and the PDU session corresponds to a LADN, the SMF shall release the PDU session after the service request procedure is completed. In the case of I-SMF insertion the SMF starts a timer to release resource, i.e. resource for the indirect data forwarding tunnel. In the case of I-SMF insertion and the CN Tunnel Info at PSA for N9 is received in the response, I-SMF provides the CN Tunnel Info at the PSA for N9 to I-UPF via N4 Session Modification Request. 9. The new I-SMF sends a Nsmf_PDUSession_CreateSMContext Response (N2 SM information (PDU Session ID, QFI(s), QoS profile(s), CN N3 Tunnel Info, S-NSSAI, User Plane Security Enforcement, UE Integrity Protection Maximum Data Rate), N1 SM Container, Cause)) to the AMF. The CN N3 Tunnel Info is the UL Tunnel Info of the new I-UPF. If the PDU Session has been assigned any EPS bearer ID, the new I-SMF also includes the mapping between EPS bearer ID(s) and QFI(s) into the N2 SM information to be sent to the NG-RAN. The new I-SMF starts a timer to release resource, i.e. resource for the indirect data forwarding tunnel. Case: I-SMF removal: steps 10 to 16 are skipped for I-SMF insertion or I-SMF change cases. 10. If the UE has moved from service area of old I-SMF into the service area of SMF, the AMF sends a Nsmf_PDUSession_CreateSMContext Request (SUPI, PDU Session ID, AMF ID, SM Context ID at I-SMF, UE location info, Access Type, RAT Type) to the SMF. If the UE Time Zone has changed compared to the last reported UE Time Zone then the AMF shall include the UE Time Zone IE in this message. The AMF Set the Operation Type to "UP activate" to indicate establishment of User Plane resources for the PDU Session(s). The AMF determines Access Type and RAT Type based, as defined in clause 4.2.3.2. 11a. The SMF retrieves SM Context from the I-SMF by invoking Nsmf_PDUSession_Context Request (SM context type). The SMF uses SM Context ID received from AMF for this service operation. SM context type indicates that the requested SM context is all, i.e. PDN Connection Context and 5G SM context. 11b. The old I-SMF responds with the SM context of the indicated PDU Session. If there is Extended Buffering is applied and the Extended Buffering timer is still running in old-SMF or old I-UPF, or the service request is triggered by downlink data (i.e. the old I-SMF received downlink data notification from old I-UPF), the old I-SMF includes a forwarding indication in the response to indicate that a forwarding tunnel is needed for sending buffered downlink packets from old I-UPF to new I-UPF or PSA (in the case that new I-UPF is not selected). 12. The SMF may select a new I-UPF: If the SMF determines that the service area of the PSA does not cover the UE location, the SMF selects a new I-UPF based on S-NSSAI and UE location information as described in clause 6.3.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 13. If a new I-UPF is selected by SMF, the SMF initiates a N4 Session Establishment to the new I-UPF. The new I-UPF provides tunnel endpoints to the SMF. If forwarding indication was received, the SMF requests the new I-UPF to allocate tunnel endpoints for forwarding data and to indicate end marker reception on this tunnel. In this case, the new I-UPF begins to buffer the downlink packet(s) received from the UPF (PSA). If the new I-UPF is not selected, i.e. the PSA can serve the UE location, the SMF may initiate N4 Session Modification to the PSA to allocate UL N3 tunnel endpoints Info of PSA. The PSA provides the UL N3 tunnel endpoints to SMF. If the forwarding indication was received, the SMF requests the PSA to allocate the tunnel endpoints for the buffered DL data from the old I-UPF and indicate the PSA via usage reporting rule to report end marker to the SMF. In this case, the UPF (PSA) begins to buffer the DL data it may receive at the same time from the N6 interface. The UPF (PSA) sends one or more "end marker" packets according to the indication from SMF for each N9 tunnel to the old I-UPF immediately after switching the path to (R)AN. If indicated by the SMF, the UPF (PSA) reports to SMF when "end marker" packet is received. Then the SMF initiates N4 Session Modification procedure to indicate the UPF (PSA) to send the DL data received from the N6 interface. 14a. If the tunnel endpoints for the buffered DL data were allocated, the SMF invokes Nsmf_PDUSession_UpdateSMContext Request (tunnel endpoints for buffered DL data) to the old I-SMF in order to establish the forwarding tunnel. The SMF uses the SM Context ID received from AMF for this service operation. 14b. The old I-SMF initiates a N4 session modification to the old I-UPF and sends the tunnel endpoints for buffered DL data to the old I-UPF. After this step, the old I-UPF start to send buffered DL data to the new I-UPF or PSA if new I-UPF is not selected. If the old I-UPF receives end marker packets and there is no associated tunnel to forward these packets, the old I-UPF discards the received end marker packets and does not send any Data Notification to SMF. 14c. The old I-SMF responds the SMF with Nsmf_PDUSession_UpdateSMContext response. 15. If a new I-UPF was selected by SMF, the SMF initiates N4 Session Modification toward the PDU Session Anchor UPF, providing the new I-UPF DL tunnel information. The PSA begins to send the DL data to the new I-UPF as indicated in the new I-UPF DL tunnel information. If the forwarding indication was received, the SMF indicates the PDU Session Anchor UPF to send one or more "end marker" packets. The UPF (PSA) sends one or more "end marker" packets according to the indication from SMF for each N9 tunnel to the old I-UPF immediately after switching the path to new I-UPF. If indicated by the SMF in step 13, the new I-UPF reports to SMF when "end marker" packet is received. The SMF initiates N4 Session Modification procedure to indicate the new I-UPF to send the DL packet(s) received from the UPF (PSA). 16. The SMF sends a Nsmf_PDUSession_CreateSMContext Response (N2 SM information (PDU Session ID, QFI(s), QoS profile(s), CN N3 Tunnel Info, S-NSSAI), N1 SM Container, Cause)) to the AMF. The CN N3 Tunnel Info is the UL Tunnel Info of the new I-UPF. If the PDU Session has been assigned any EPS bearer ID, the SMF also includes the mapping between EPS bearer ID(s) and QFI(s) into the N2 SM information to be sent to the NG-RAN. The SMF starts a timer to release the resource, i.e. resource for indirect data forwarding tunnel. 17. These steps are same as steps 12 to 14 in clause 4.2.3.2. After step 16, the Uplink data is transferred from (R)AN via new I-UPF (if exists) to PSA. If procedure in clause 4.2.3 is triggered together with this procedure, this step can be executed together with the corresponding steps in clause 4.2.3. 17a. If the step 9 or step 16 was successful response, in the case of I-SMF removal or change, the AMF sends Nsmf_PDUSession_ReleaseSMContext Request (I-SMF only indication) to old I-SMF for the release of resources in old I-SMF. The I-SMF only indication indicates to old I-SMF not to invoke resource release in SMF. The old I-SMF starts a timer to release resources, i.e. resource for indirect data forwarding tunnel. 17b. The old I-SMF responds to AMF with Nsmf_PDUSession_ReleaseSMContext response. Case: I-SMF insertion or I-SMF change: steps 18 to 21 are skipped for the I-SMF removal case. 18. The AMF sends an Nsmf_PDUSession_UpdateSMContext Request (N2 SM information, RAT type, Access type) to the new I-SMF. If the AMF received N2 SM information (one or multiple) in step 17, then the AMF shall forward the N2 SM information to the relevant new I-SMF per PDU Session ID. 19. The new I-SMF updates the new I-UPF with the AN Tunnel Info and List of accepted QFI(s). Downlink data is now forwarded from new I-UPF to UE. 20a. The new I-SMF invokes Nsmf_PDUSession_Update request (RAT type, Access type, Operation Type) to SMF. The SMF updates associated access of the PDU Session. The Operation Type is set to "UP activated" to indicate User Plane resource for the PDU Session has been established. 20b. If dynamic PCC is deployed, SMF may initiate notification about new location information to the PCF (if subscribed) by performing an SMF initiated SM Policy Modification procedure as defined in clause 4.16.5.1. The PCF may provide updated policies. If the PCC rule(s) are updated, the SMF may initiate a N4 Session Modification procedure to UPF (PSA) based on the updated PCC rule(s). 20c. The SMF responds with Nsmf_PDUSession_Update Response. 21. The new I-SMF sends a Nsmf_PDUSession_UpdateSMContext Response to AMF. Case: I-SMF removal: steps 22 to 25 are skipped for the I-SMF insertion or I-SMF change cases. 22. The AMF sends a Nsmf_PDUSession_UpdateSMContext Request (N2 SM information, RAT Type, Access Type) to the SMF. The AMF determines Access Type and RAT Type based on the Global RAN Node ID associated with the N2 interface. If the AMF received N2 SM information (one or multiple) in step 17, then the AMF shall forward the N2 SM information to the relevant new I-SMF per PDU Session ID. 23. If dynamic PCC is deployed, SMF may initiate notification about new location information to the PCF by performing an SMF initiated SM Policy Modification procedure as defined in clause 4.16.5.1. The PCF may provide updated policies. 24. If a new I-UPF was selected by the SMF, the SMF updates the new I-UPF with the AN Tunnel Info and List of accepted QFI(s), otherwise, the SMF updates the PSA with the AN Tunnel Info and List of accepted QFI(s). 25. The SMF sends a Nsmf_PDUSession_UpdateSMContext Response to AMF. 26a. In the case of I-SMF insertion or I-SMF change, upon timer set in step 9 expires and the indirect data forwarding tunnel was established before, the new I-SMF sends N4 Session Modification request to new I-UPF to release resources for the forwarding tunnel. In the case of I-SMF removal, upon timer set in step 16 expires and the indirect data forwarding tunnel was established before, the SMF sends N4 Session Modification request to the new I-UPF or PSA to release the resource for the forwarding tunnel. 26b. In the case of I-SMF removal or change, upon timer set in step 17a expires and the indirect data forwarding tunnel was established before, the old I-SMF sends N4 Session Release request to the old I-UPF to release resources for the PDU Session. The old I-SMF releases the SM Context for the PDU Session. If the old I-UPF acts as UL CL and is not co-located with local PSA, the old I-SMF also sends N4 Session Release request to the local PSA to release resources for the PDU Session. In the case of I-SMF insertion, upon timer set in step 8c expires and the indirect data forwarding tunnel was established before, the SMF sends N4 Session Release request to the old I-UPF to release the resource for the PDU Session. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.23.4.3 |
5,140 | 10.5.1.10a PD and SAPI $(CCBS)$ | The purpose of the PD and SAPI information element is to provide information concerning Protocol Discriminators and Service Access Point Identifiers. The PD and SAPI information element is coded as shown in figure 10.5.10/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.10/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The PD and SAPI is a type 3 information element with 2 octets length. Figure10.5.10/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] PD and SAPI information element Table 10.5.1.10/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : PD and SAPI 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.1.10a |
5,141 | Annex A (normative): Handling of measurement gaps | In this specification, the subframes which cannot be used for transmission according to clause 8.1.2.1 of TS 36.133[ Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for support of radio resource management ] [9] are also considered as part of measurement gaps in uplink. Measurement gaps are defined in TS 36.133[ Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for support of radio resource management ] [9]. In a subframe that is part of a measurement gap, the UE shall not perform the transmission of HARQ feedback and CQI/PMI/RI/PTI/CRI, and SRS shall not be reported. | 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 | Annex |
5,142 | 5.16.3.7 UE's usage setting | If the UE is configured to support IMS voice, the UE shall include the information element "UE's usage setting" in Registration Request messages. The UE's usage setting indicates whether the UE behaves in a "voice centric" or "data centric" way (as defined in clause 5.16.3.5). A UE supporting IMS voice over 3GPP access connected to 5GC and that is EPS capable shall also support IMS voice over E-UTRA connected to EPC. NOTE: Depending on operator's configuration, the UE's usage setting can be used by the network to choose the RFSP Index in use (see clause 5.3.4.3). As an example, this enables the enforcement of selective idle mode camping over E-UTRA for voice centric UEs. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.16.3.7 |
5,143 | Annex D (informative): Applicability and use of the ".3gppnetwork.org" domain name | There currently exists a private IP network between operators to provide connectivity for user transparent services that utilise protocols that rely on IP. This includes (but is not necessarily limited to) such services as GPRS/PS roaming, WLAN roaming, GPRS/PS inter-PLMN handover and inter-MMSC MM delivery. This inter-PLMN IP backbone network consists of indirect connections using brokers (known as GRXs – GPRS Roaming Exchanges) and direct inter-PLMN connections (e.g. private wire); it is however not connected to the Internet. More details can be found in GSMA PRD IR.34 [57]. Within this inter-PLMN IP backbone network, the domain name ".gprs" was originally conceived as the only domain name to be used to enable DNS servers to translate logical names for network nodes to IP addresses (and vice versa). However, after feedback from the Internet Engineering Task Force (IETF) it was identified that use of this domain name has the following drawbacks: 1. Leakage of DNS requests for the ".gprs" top level domain into the public Internet is inevitable at sometime or other, especially as the number of services (and therefore number of nodes) using the inter-PLMN IP backbone increases. In the worst case scenario of faulty clients, the performance of the Internet's root DNS servers would be seriously degraded by having to process requests for a top level domain that does not exist. 2. It would be very difficult for network operators to detect if/when DNS requests for the ".gprs" domain were leaked to the public Internet (and therefore the security policies of the inter-PLMN IP backbone network were breached), because the Internet's root DNS servers would simply return an error message to the sender of the request only. To address the above, the IETF recommended using a domain name that is routable in the pubic domain but which requests to it are not actually serviced in the public domain. The domain name ".3gppnetwork.org" was chosen as the new top level domain name to be used (as far as possible) within the inter-PLMN IP backbone network. Originally, only the DNS servers connected to the inter-PLMN IP backbone network were populated with the correct information needed to service requests for all sub-domains of this domain. However, it was later identified that some new services needed their allocated sub-domain(s) to be resolvable by the UE and not just inter-PLMN IP network nodes. To address this, additional, higher-level sub-domains were created: - "pub.3gppnetwork.org", which is to be used for domain names that need to be resolvable by UEs (and possibly network nodes too) that are connected to a local area network that is connected to the Internet; and - "ipxuni.3gppnetwork.org", which is to be used for domain names for UNI interfaces that need to be resolvable by UEs that are connected to a local area network that is not connected to the Internet (e.g. local area networks connected to the inter-PLMN IP network of the IPX). Therefore, DNS requests for the above domain names can be resolved, while requests for all other sub-domains of "3gppnetwork.org" can simply be configured to return the usual DNS error for unknown hosts (thereby avoiding potential extra, redundant load on the Internet's root DNS servers). The GSM Association is in charge of allocating new sub-domains of the ".3gppnetwork.org" domain name. The procedure for requesting new sub-domains can be found in Annex E. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | Annex |
5,144 | 6.6.3.3 Additional spurious emissions | These requirements are specified in terms of an additional spectrum emission requirement. Additional spurious emission requirements are signalled by the network to indicate that the UE shall meet an additional requirement for a specific deployment scenario as part of the cell handover/broadcast message. NOTE: For measurement conditions at the edge of each frequency range, the lowest frequency of the measurement position in each frequency range should be set at the lowest boundary of the frequency range plus MBW/2. The highest frequency of the measurement position in each frequency range should be set at the highest boundary of the frequency range minus MBW/2. MBW denotes the measurement bandwidth defined for the protected band. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.6.3.3 |
5,145 | 4.7.3 5GS session management aspects | The session management procedures defined over 3GPP access are re-used over non-3GPP access with the following exceptions: a) Serving PLMN rate control does not apply for non-3GPP access; b) Small data rate control does not apply for non-3GPP access; c) Handling of 5GSM cause value #82 "maximum data rate per UE for user-plane integrity protection is too low" does not apply for non-3GPP access; d) MBS does not apply for non-3GPP access; and e) Support of redundant PDU sessions does not apply for non-3GPP access. | 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.7.3 |
5,146 | 6.5.3.4A Handling the maximum number of active EPS bearer contexts | If the UE requests allocation of additional bearer resources, and the network has reached its maximum number of active EPS bearer contexts, then the network can: - reject the request if the network decides that it is necessary to allocate a dedicated EPS bearer context; or - accept the request by sending a MODIFY EPS BEARER CONTEXT REQUEST message. NOTE: An example of where the network will reject the request for allocation of additional bearer resources is when the request includes a GBR requirement while all existing bearers are non-GBR bearers, and the maximum number of active EPS bearer contexts has been reached at the network. If the maximum number of active EPS bearer contexts is reached at the UE (see clause 6.5.0) and the UE de-activates an active EPS bearer context prior to sending the request for additional bearer resources, then choosing which EPS bearer context to de-activate is a implementation specific, however the UE shall not deactivate a default EPS bearer context for emergency. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.5.3.4A |
5,147 | 7.1 Network Function Service Framework 7.1.1 General | Service Framework functionalities include e.g. service registration/de-registration, consumer authorization, service discovery, and inter service communication, which include selection and message passing. Four communication options are listed in Annex E and can all co-exist within one and the same network. An NF service is one type of capability exposed by an NF (NF Service Producer) to other authorized NF (NF Service Consumer) through a service-based interface. A Network Function may expose one or more NF services. Following are criteria for specifying NF services: - NF services are derived from the system procedures that describe end-to-end functionality, where applicable (see TS 23.502[ Procedures for the 5G System (5GS) ] [3], Annex B drafting rules). Services may also be defined based on information flows from other 3GPP specifications. - System procedures can be described by a sequence of NF service invocations. NF services may communicate directly between NF Service consumers and NF Service Producers, or indirectly via an SCP. Direct and Indirect Communication are illustrated in Figure 7.1.1-1. For more information, see Annex E and clauses 6.3.1 and 7.1.2. Whether a NF Service Consumer (e.g. in the case of requests or subscriptions) or NF Service Producer (e.g. in the case of notifications) uses Direct Communication or Indirect Communication by using an SCP is based on the local configuration of the NF Service Consumer/NF Service Producer. An NF may not use SCP for all its communication based on the local configuration. NOTE: The SCP can be deployed in a distributed manner. In Direct Communication, the NF Service consumer performs discovery of the target NF Service producer by local configuration or via NRF. The NF Service consumer communicates with the target NF Service producer directly. In Indirect Communication, the NF Service consumer communicates with the target NF Service producer via a SCP. The NF Service consumer may be configured to perform discovery of the target NF Service producer directly, or delegate the discovery of the target NF Service Producer to the SCP used for Indirect Communication. In the latter case, the SCP uses the parameters provided by NF Service consumer to perform discovery and/or selection of the target NF Service producer. The SCP address may be locally configured in NF Service consumer. Figure 7.1.1-1: NF/NF service inter communication | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 7.1 |
5,148 | 5.7.2.4.1a Notification Control without Alternative QoS Profiles | If, for a given GBR QoS Flow, Notification control is enabled and the NG-RAN determines that the GFBR, the PDB or the PER of the QoS profile cannot be fulfilled, NG-RAN shall send a notification towards SMF that the "GFBR can no longer be guaranteed". Furthermore, the NG-RAN shall keep the QoS Flow (i.e. while the NG-RAN is not fulfilling the requested QoS profile for this QoS Flow), unless specific conditions at the NG-RAN require the release of the NG-RAN resources for this GBR QoS Flow, e.g. due to Radio link failure or RAN internal congestion. The NG-RAN should try to fulfil the GFBR, the PDB and the PER of the QoS profile again. NOTE 1: NG-RAN can decide that the "GFBR can no longer be guaranteed" based on, e.g. measurements like queuing delay or system load. Upon receiving a notification from the NG-RAN that the "GFBR can no longer be guaranteed", the SMF may forward the notification to the PCF, see TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. When the NG-RAN determines that the GFBR, the PDB and the PER of the QoS profile can be fulfilled again for a QoS Flow (for which a notification that the "GFBR can no longer be guaranteed" has been sent), the NG-RAN shall send a notification, informing the SMF that the "GFBR can be guaranteed" again and the SMF may forward the notification to the PCF, see TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. The NG-RAN shall send a subsequent notification that the "GFBR can no longer be guaranteed" whenever necessary. NOTE 2: It is assumed that NG-RAN implementation will apply some hysteresis before determining that the "GFBR can be guaranteed again" and therefore a frequent signalling of "GFBR can be guaranteed again" followed by "GFBR can no longer be guaranteed" is not expected. NOTE 3: If the QoS Flow is modified, the NG-RAN restarts the check whether the "GFBR can no longer be guaranteed" according to the updated QoS profile. If the Notification control parameter is not included in the updated QoS profile, the Notification control is disabled. During a handover, the Source NG-RAN does not inform the Target NG-RAN about whether the Source NG-RAN has sent a notification for a QoS Flow that the "GFBR can no longer be guaranteed". The Target NG-RAN performs admission control rejecting any QoS Flows for which resources cannot be permanently allocated. The accepted QoS Flows are included in the N2 Path Switch Request or N2 Handover Request Acknowledge message from the NG-RAN to the AMF. The SMF shall interpret the fact that a QoS Flow is listed as transferred QoS Flow in the Nsmf_PDUSession_UpdateSMContext Request received from the AMF as a notification that "GFBR can be guaranteed again" for this QoS Flow unless the SMF is also receiving a reference to an Alternative QoS Profile for this QoS Flow (which is described in clause 5.7.2.4.2). After the handover is successfully completed, the Target NG-RAN shall send a subsequent notification that the "GFBR can no longer be guaranteed" for such a QoS Flow whenever necessary. If the SMF has previously notified the PCF that the "GFBR can no longer be guaranteed" and the SMF does not receive an explicit notification that the "GFBR can no longer be guaranteed" for that QoS Flow from the Target NG-RAN within a configured time, the SMF shall notify the PCF that the "GFBR can be guaranteed again". | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.7.2.4.1a |
5,149 | 4.3.4.2 IMSI detach procedure in the network | When receiving an IMSI DETACH INDICATION message, the network may set an inactive indication for the IMSI. No response is returned to the mobile station. After reception of the IMSI DETACH INDICATION message the network shall release locally any ongoing MM connections, and start the normal RR connection release procedure (see 3GPP TS 44.018[ None ] [84] subclause 3.5 (A/Gb mode only), 3GPP TS 25.331[ None ] [23c] (UTRAN Iu mode only), or in 3GPP TS 44.118[ None ] [111] (GERAN Iu mode only)). Only applicable for a network supporting VGCS: If an IMSI DETACH INDICATION message is received from the talking mobile station in a group call while the network is in service state MM CONNECTION ACTIVE (GROUP TRANSMIT MODE), the network shall release locally the ongoing MM connection and then go to the service state GROUP CALL ACTIVE. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.3.4.2 |
5,150 | 4.3.3.2 Roaming architecture | Figure 4.3.3.2-1 represents the Roaming architecture with local breakout and Figure 4.3.3.2-2 represents the Roaming architecture with home-routed traffic for interworking between 5GC via non-3GPP access and EPC/E-UTRAN. Figure 4.3.3.2-1: Local breakout roaming architecture for interworking between 5GC via non-3GPP access and EPC/E-UTRAN NOTE 1: There can be another UPF (not shown in the figure above) between the N3IWF/TNGF and the UPF + PGW-U, i.e. the UPF + PGW-U can support N9 towards the additional UPF, if needed. NOTE 2: S9 interface from EPC is not required since no known deployment exists. NOTE 3: N26 interface is not precluded, but it not shown in the figure because it is not required for the interworking between 5GC via non-3GPP access and EPC/E-UTRAN. Figure 4.3.3.2-2: Home-routed roaming architecture for interworking between 5GC via non-3GPP access and EPC/E-UTRAN NOTE 4: N26 interface is not precluded, but it not shown in the figure because it is not required for the interworking between 5GC via non-3GPP access and EPC/E-UTRAN. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3.3.2 |
5,151 | 8.3.10.1 Message definition | This message is sent by the UE to the network to request the modification of a dedicated bearer resource, or to request re-negotiation of header compression configuration associated to an EPS bearer context if the network has previously indicated support of Control plane CIoT EPS optimization and Header compression for control plane CIoT EPS optimization. See table 8.3.10.1. Message type: BEARER RESOURCE MODIFICATION REQUEST Significance: dual Direction: UE to network Table 8.3.10.1: BEARER RESOURCE MODIFICATION REQUEST message content | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 8.3.10.1 |
5,152 | 8.16 Flow Quality of Service (Flow QoS) | Flow Quality of Service (Flow QoS) is transferred via GTP tunnels. The sending entity copies the value part of the Flow QoS into the Value field of the Flow QoS IE. Figure 8.16-1: Flow Quality of Service (Flow QoS) Octet 5 contains the "QCI" value, as specified in 3GPP TS 23.203[ Policy and charging control architecture ] [48]. The UL/DL MBR and GBR fields are encoded as kilobits per second (1 kbps = 1000 bps) in binary value. For non-GBR bearers, both the UL/DL MBR and GBR should be set to zero. The range of QCI, Maximum bit rate for uplink, Maximum bit rate for downlink, Guaranteed bit rate for uplink and Guaranteed bit rate for downlink are specified in 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [10]. NOTE: The encoding in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [23] and 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [10] is different from the encoding within this specification. | 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.16 |
5,153 | 6.5.2 UE requested PDN disconnect procedure 6.5.2.1 General | The purpose of the UE requested PDN disconnection procedure is for a UE to request disconnection from one PDN. If EMM-REGISTERED without PDN connection is not supported by the UE or the MME, the UE can initiate this procedure to disconnect from any PDN as long as it is connected to at least one other PDN. If EMM-REGISTERED without PDN connection is supported by the UE and the MME, the UE can initiate this procedure to disconnect from any PDN. With this procedure, all EPS bearer contexts established towards this PDN, including the default EPS bearer context, are released. The UE is allowed to initiate the PDN disconnection procedure even if the timer T3396 is running. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.5.2 |
5,154 | 5.9.4.3 MBS frequencies of interest determination | The UE shall: 1> consider a frequency to be part of the MBS frequencies of interest if the following conditions are met: 2> at least one MBS session the UE is receiving or interested to receive via a broadcast MRB is ongoing or about to start; and NOTE 1: The UE may determine whether the session is ongoing from the start and stop time indicated in the User Service Description (USD), see TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [2] or TS 23.247[ Architectural enhancements for 5G multicast-broadcast services ] [67]. 2> for at least one of these MBS sessions, SIB21 acquired from the PCell or a non-serving cell includes mapping between the concerned frequency and one or more MBS FSAIs indicated in the USD for this session, or for at least one of these MBS sessions, the concerned frequency is not included in SIB21 but is indicated in the USD for this session; and NOTE 2: The UE considers a frequency to be part of the MBS frequencies of interest even though NG-RAN may (temporarily) not employ a broadcast MRB for the concerned session, i.e., the UE does not verify if the session is indicated on MCCH. 2> the supportedBandCombinationList the UE included in UE-NR-Capability contains at least one band combination including the concerned MBS frequency. NOTE 3: When evaluating which frequencies the UE is capable of receiving, the UE does not take into account whether they are currently configured as serving frequencies. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.9.4.3 |
5,155 | 4.16.16.1 Forwarding of URSP Rule Enforcement Information | This procedure applies when the PCF serving the PDU session receives URSP rule enforcement information from the SMF and forwards this information to the PCF serving the UE (see clause 6.1.3.18 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]). Figure 4.16.16.1-1: Forwarding of URSP Rule Enforcement Information 1. The UE Policy Association is established, as described in clause 4.16.11. 2. If the PCF indicates the UE to send reporting of URSP rule enforcement 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], then depending on operator policies in the PCF, the PCF may subscribe to the BSF, then step 3 follows, or provides its PCF binding information to the AMF in step 1 with the indication to be notified about the PCF for the PDU Session for a UE, then step 4 follows. 3. The PCF for the UE determines that URSP rules depend on the UE reporting of URSP rule enforcement, it then subscribes to the BSF to be notified when a PCF for the PDU Session for this SUPI is registered in the BSF, by invoking Nbsf_Management_Subscribe (SUPI; DNN). Steps 4 and 5 are repeated for each PCF registered for a PDU Session to a SUPI included in the Nbsf_Management. 4. The SMF establishes a SM Policy Association as described in clause 4.16.4. The allocated UE address/prefix, SUPI, DNN, S-NSSAI and the PCF address is registered in the BSF, as described in clause 6.1.1.2.2 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. 5a. If the PCF for the UE subscribed to the BSF in step 3, then the BSF notifies that a PCF for the PDU Session is registered in the BSF, by invoking Nbsf_Management_Notify (UE address(es), PCF address, PCF instance id, PCF Set ID, level of binding). When there are multiple PDU Sessions to the same UE the BSF provides multiple notification to the PCF. 5b. If the PCF for the UE sent the request to notify that a PCF for the PDU Session is available to the AMF in step 1, then the PCF for the PDU Sessions sends Npcf_PolicyAuthorization_Notify (EventID set to SM Policy Association established, UE address, PCF address, PCF instance is, PCF Set ID) to the PCF indicated in the PCF binding information provided by the SMF. 6. 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 of 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") and immediate reporting flag set to the PCF for the PDU Session. The response includes the NotificationCorrelationId and any Connection Capabilities if already available at the PCF for the PDU Session. 7. If not already installed, the PCF installs the Policy Control Request Trigger to detect "UE reporting Connection Capabilities from associated URSP rule" in the SMF. 8. When the SMF receives a UE report of URSP rule enforcement via PDU session establishment/modification as described in clauses 4.3.2 and 4.3.3 (step 8a) and the Policy Control Request Trigger is met, it then reports the received information traffic to the PCF serving the PDU Session, by invoking Npcf_SMPolicyControl_Update 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] (step 8b). 9. The PCF for the UE is notified on the "UE reporting Connection Capabilities from associated URSP rule" by Npcf_PolicyAuthorization_Notify (NotificationCorrelationId, EventId set to "UE reporting Connection Capabilities from associated URSP rule", EventInformation including the Connection Capabilities) 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]. 10. The PCF for the UE checks operator policies and then may make policy control decisions based on awareness of URSP rule enforcement as described in clause 6.1.6 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. 11. The SM Policy Association is terminated as described in clause 4.16.6. The allocated UE address/prefix, SUPI, DNN, S-NSSAI and the PCF address are deregistered in the BSF. 12a. If the PCF for the UE subscribed to the BSF, then the BSF notifies that the PCF serving a PDU Session is deregistered in the BSF, by invoking Nbsf_Management_Notify (Binding Identifier for the PDU Session). 12b. If the PCF for the UE sent the request to notify that a PCF for the PDU Session is available to the AMF in step 1, then the PCF for the PDU Session sends Npcf_PolicyAuthoritation_Notify (EventID set to SM Policy Association termination, Notification Correlation Id). | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.16.16.1 |
5,156 | 6.7.1G Minimum requirement for V2X Communication | When UE is configured for E-UTRA V2X sidelink transmissions non-concurrent with E-UTRA uplink transmissions for E-UTRA V2X operating bands specified in Table Table 5.5G-1, the requirements in subclause 6.7.1 apply for E-UTRA V2X sidelink transmission. When UE is configured for simultaneous E-UTRA V2X sidelink and E-UTRA uplink transmissions for inter-band E-UTRA V2X / E-UTRA bands specified in Table 5.5G-2, the requirements in subclause 6.7.1 apply for V2X sidelink transmission and the E-UTRA uplink transmission. For intra-band contiguous multi-carrier operation, the transmit intermodulation requirement for CA Bandwidth Class B specified in subclause 6.7.1A shall apply for V2X Bandwdith Class B, the general CA spectrum emission mask for CA Bandwidth Class C specified in subclause 6.7.1A shall apply for V2X Bandwdith Class C and C1. For V2X UE supporting Transmit Diversity, if the UE transmits on two antenna connectors at the same time, the requirements specified for single carrier shall apply to each transmit antenna connector. If the UE transmits on one antenna connector, the requirements specified for single carrier shall apply to the active antenna connector. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.7.1G |
5,157 | 5.9.1 Location Reporting Procedure | This procedure is used by an MME to request the eNodeB to report where the UE is currently located when the target UE is in ECM-CONNECTED state. The need for the eNodeB to continue reporting ceases when the UE transitions to ECM-IDLE. This procedure may be used for services that require accurate cell identification (e.g. for emergency services, lawful intercept, charging). When Dual Connectivity is activated, the PSCell information is only reported if requested by the MME. In the case of satellite access for Cellular IoT, this procedure may be used by the MME to determine the TAI where the UE is geographically located. Figure 5.9.1-1: Location Reporting Procedure 1) The MME sends a Location Reporting Control message to the eNodeB. The Location Reporting Control message shall identify the UE for which reports are requested, the requested location information and may contain information such as reporting type. Requested location information is TAI+EGCI, and if requested by the MME, PSCell ID. Reporting type indicates whether the message is intended to trigger: - a single stand-alone report about the current Cell ID serving the UE; or - start the eNodeB to report whenever the UE changes cell. In addition, the MME shall be able to control whether or not the RAN reports changes in the UE's PSCell ID. NOTE 1: Requesting reports whenever the UE changes cell can increase signalling load on multiple interfaces. Requesting reports for changes in PSCell ID can further increase signalling load. Hence it is recommended that any such reporting is only applied for a limited number of subscribers. 2) The eNodeB sends a Location Report message informing the MME about the location of the UE which shall include the requested location information. If the MME requests UE location, in the case of satellite access for Cellular IoT, the eNodeB provides all broadcast TAIs to the MME as part of the ULI. The eNodeB also reports the TAI where the UE is geographically located if this TAI can be determined. The cell and TAI reporting by eNodeB refer to a fixed cell and fixed TA in which a UE is geographically located. As part of the User Location Information, eNodeB also reports one or more TACs for the Selected PLMN as described in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36], but it is not guaranteed that the UE is always located in one of these TACs. 3) The MME can send a Cancel Location Reporting message to inform the eNodeB that it should terminate location reporting for a given UE. This message is needed only when the reporting was requested for a reporting period. NOTE 2: Location reporting is transferred during X2 handover, although new control signalling is not transferred during an active handover. | 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.9.1 |
5,158 | 4.3.6 Application Function influence on traffic routing and service function chaining 4.3.6.1 General | Clause 4.3.6 describes the procedures between an Application Function and the SMF to maintain an efficient user plane path and/or to provide N6-LAN service function chaining for Application Functions that require it. As described in clauses 5.6.7 and 5.6.16 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], an Application Function may send requests to influence SMF routeing decisions for User Plane traffic of PDU Sessions. The AF requests may influence UPF (re)selection and allow routeing of user traffic to a local access (identified by a DNAI) to a Data Network and/or influence the steering of user traffic to service function chain(s) identified by SFC identifier(s). The AF may also provide in its request subscriptions to SMF events. The following cases can be distinguished: NOTE 1: Such requests target an on-going PDU Session. When receiving an AF request on Application Function influence on traffic routing targeting an individual UE IP address the NEF needs to determine whether the target PDU Session is working in HR-SBO mode. If the target PDU Session is NOT working in HR-SBO mode (non roaming or LBO PDU Session) then the NEF contacts the PCF of the PDU Session as further defined in the clause 4.3.6.4; If the target PDU Session is working in HR-SBO mode, the NEF does not contact the PCF of the PDU session but needs to store the AF request in UDR as defined in clause 4.3.6.5. The NEF determines whether the PDU Session that the AF requests to influence is working in HR-SBO mode or not and in the former case determines the HPLMN of the UE, the DNN/S-NSSAI of the PDU Session as follows: If the AF has not provided the (H)PLMN ID, DNN, S-NSSAI: - If the IP address of the UE in the AF request is a private IP address, the NEF determines the HPLMN of the UE, the DNN/S-NSSAI of the PDU Session based on local configuration. - If the IP address of the UE in the AF request is a public IP address: - if this Public address belongs to a range NOT owned by the PLMN of the NEF, then the target PDU Session is working in HR-SBO mode and the NEF determines the HPLMN of UE, the DNN/S-NSSAI of the PDU Session based on that range. The NEF (that has received the AF request) contacts the NEF of the HPLMN in order to retrieve the UE IP address of the PDU Session from the PSA UPF in the HPLMN. - Otherwise, if the UE IP Address in the AF request is an IP address NATed by the PLMN that the NEF belongs to, the NEF invokes steps 3 to 6 of the AF specific UE ID retrieval procedure defined in clause 4.15.10 to get the corresponding private UE IP address, an indication that the PDU Session is working in HR-SBO mode, the HPLMN of UE, the DNN/S-NSSAI of the PDU Session from the L-PSA UPF in the local PLMN. NOTE 2: In this Release, the HPLMN allows HR-SBO for a PDU session only if the UE IP address of the PDU Session has not been allocated in a range that may overlap with other PDU sessions to the same DNN and S-NSSAI of that HPLMN. NOTE 3: It is assumed that the NEF is configured with the NATed IP range of its own PLMN. It is assumed that the NEF is configured based on HR-SBO roaming agreements for the DNN/S-NSSAI with the association of Public IP address ranges with an HPLMN ID, a DNN/S-NSSAI. NOTE 4: Whether the AF needs to use the NEF or not is according to local deployment. If the AF request is expected to possibly address PDU Sessions in HR-SBO mode, then the AF sends its requests via the NEF. When AF requests are routed (by the AF or by the NEF) to an individual PCF this may use the BSF. This case applies to both AF influence on traffic routing as well as AF influence on Service Function Chaining. This is described in clause 4.3.6.4. - AF requests described in clause 5.6.7 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] or clause 5.6.16 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] targeting a group of UE(s), or any UE accessing a combination of DNN and S-NSSAI, or targeting individual UE(s) by one or more GPSI(s) or targeting UEs with External Subscriber Category(s) which can be combined with External Group ID(s) or any UE as described in table 5.6.7-1. These AF requests may also affect UE(s) with an established PDU session. For such requests the AF shall contact the NEF and the NEF stores the AF request information in the UDR. PCF(s) receive a corresponding notification if they had subscribed to the creation / modification/ deletion of the AF request information corresponding to UDR Data Keys / Data Sub-Keys. This is defined in clause 6.3.7.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] and further described in clause 4.3.6.2. NOTE 5: Such requests can target on-going or future PDU Sessions. If the AF request targets any UE the procedure described in clause 4.3.6.5 may also be performed. In that case if the HPLMN Id, DNN and S-NSSAI has not been provided by the AF, the NEF determines the target HPLMN Id, DNN and S-NSSAI based on local configuration, This version of the specification does not support the procedure described in clause 4.3.6.5 if the AF request targets an external group of UE(s), or UE(s) identified by SUPI. If the AF request targets a GPSI, the NEF determines the GPSI owner PLMN Id from the GPSI and invokes the NEF of that PLMN that retrieves the SUPI from HPLMN. In that case if the DNN and/or S-NSSAI has not been provided by the AF a preconfigured DNN and/or S-NSSAI is used. If the AF interacts with 5GC via the NEF, the NEF performs the following mappings or determinations where needed: - Map the AF-Service-Identifier into DNN and S-NSSAI combination, determined by local configuration. - Map the AF-Service-Identifier into a list of DNAI(s) and Routing Profile ID(s) determined by local configuration. The NEF can only provide this mapping when the DNAI(s) being used by the applications are statically defined. When the DNAI(s) where applications are instantiated may vary dynamically, the AF should provide the target DNAI(s) in its request together with either Routing Profile ID(s) or with N6 traffic routing information. - Map the GPSI in Target UE Identifier into SUPI, according to information received from UDM. - Map the External Group Identifier in Target UE Identifier into Internal Group Identifier, according to information received from UDM. - Map the External Subscriber Category(s) and any UE, or External Subscriber Category and External Group ID(s) to, Internal Group ID(s) or Internal Group ID(s) and Subscriber Category(s). - Map the geographical area in Spatial Validity Condition into areas of validity, determined by local configuration. - Determine whether an AF request targeting an UE IP address corresponds to HR-SBO and if yes determine as defined above the HPLMN of UE, the DNN/S-NSSAI of the PDU Session based on the AF request, the received UE IP address and its local configuration, NOTE 6: As a user can be associated with multiple Subscriber Category(s), some values of Subscriber Category(s) can correspond to an SLA between an application provider represented by an AF and the 5GC operator. In the NEF API, the combination of application identifier and External Subscriber Category can also be used to refer to this SLA. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3.6 |
5,159 | G.4 An SCP deployment example based on name-based routing G.4.0 General Information | This clause provides a deployment example for the SCP which is based on a name-based routing mechanism that provides IP over ICN capabilities such as those described in Xylomenos, George, et al. [G1]. The scenario describes an SCP offering based on an SBA-platform to interconnect 5GC Services (or a subset of the respective services). The Name-based Routing mechanism, described in this deployment example, is realized through a Path Computation Element which is the core part of the SCP. The 5GC Services are running as microservices on cloud/deployment units (clusters). A Service Router is the communication node (access node/gateway) between the SCP and the 5GC Services and resides as a single unit within a Service Deployment Cluster. The Service Router acts as communication proxy and it is responsible for mapping IP based messages onto ICN publication and subscriptions. The Service Router serves multiple 5GC Service Endpoints within that cluster. For direct communication the Service Router is not used. 5GC Functionalities communicate with the Service Router using standardized 3GPP SBIs. The Functionalities within the Service Deployment Cluster are containerized Service Functions. Depicted in Figure G.4-1, the Service Router act as SCP termination point and offer the SBI to the respective 5GC Service Functionalities. In this example, Service Routers and 5GC functionality, although co-located, are separate components within the Service Deployment Cluster. Multiple Functionalities can exist within the Service Deployment Cluster, all served by the respective Service Router when needed to communicate to other Service Functionalities within different clusters. Figure G.4-1: Deployment unit: 5GC functionality and co-located Service Agent(s) implementing peripheral tasks In Figure G.4-1, the two depicted 5GC Service Functionalities (realized as Network Function Service Instances) may communicate in two ways. However, before the communication can be established between two 5GC Functionalities, Service Registration and Service Discovery need to take place, as described in Figure G.4.1-1. Service Registration and Service Discovery are provided in a standardized manner using 3GPP Service Based Interfaces. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | G.4 |
5,160 | 5.5.2.3.1 Reference signal sequence | The SPUCCH demodulation reference signal sequence for subslot-SPUCCH format 4, and, slot-SPUCCH formats 1, 1a, 1b, 3 and 4 is as defined for in clause 5.5.2.2.1 for PUCCH format 1, 1a, 1b, 2, 2a, 2b and 3, using the parameter settings in Table 5.5.2.3.1-1, and with the number of reference symbols replaced by and given by Table 5.5.2.3.1-2. NOTE: Subslot-SPUCCH format 1/1a/1b does not employ a reference signal based design. The sequence is given by clause 5.5.1 with , where the expression for the cyclic shift is determined depending on the SPUCCH format, see table 5.5.2.3.1-3. Table 5.5.2.3.1-1: Parameters for SPUCCH demodulation reference signal Table 5.5.2.3.1-2: Number of SPUCCH demodulation reference symbols per slot or per subslot Table 5.5.2.3.1-3: | 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.3.1 |
5,161 | 5.2.6.22.5 Nnef_AMPolicyAuthorization_Notify service operation | Service operation name: Nnef_AMPolicyAuthorization_Notify Description: provided by the NEF to notify NF consumers when the NEF receives from the PCF notifications about subscribed events. Inputs, Required: Subscription Correlation ID, Event ID. The event that can be subscribed is the event for reporting change of coverage defined in clause 6.1.3.18 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. Inputs, Optional: Event information 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]. Outputs, Required: Operation execution result indication. Outputs, Optional: None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.6.22.5 |
5,162 | 5.1 Overview 5.1.1 General | This clause describes the procedures used for mobility management for EPS services (EMM) at the radio interface (reference point "LTE-Uu"). The main function of the mobility management sublayer is to support the mobility of a user equipment, such as informing the network of its present location and providing user identity confidentiality. A further function of the mobility management sublayer is to provide connection management services to the session management (SM) sublayer and the short message services (SMS) entity of the connection management (CM) sublayer. All the EMM procedures described in this clause can only be performed if a NAS signalling connection has been established between the UE and the network. Else, the EMM sublayer has to initiate the establishment of a NAS signalling connection (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]). NOTE: In a satellite E-UTRAN access, a GNSS fix time in lower layers can delay transmission of an initial UL NAS message by up to 100 seconds (GNSS cold state). | 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.1 |
5,163 | 19.4.2.11 Local Home Network identifier | The Local Home Network identifier uniquely identifies a local home network. For the definition of a local home network see 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [3] and 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [72]. A subdomain name shall be derived from the MNC and MCC from the visited network by adding the label "lhn" to the beginning of the Home Network Realm/Domain (see clause 19.2). The Local Home Network-ID FQDN shall be constructed as: lhn< LHN name >.lhn.epc.mnc<MNC>.mcc<MCC>.3gppnetwork.org The <LHN-name> length and content is an operator choice. The labels shall follow the rules specified in clause 19.4.2.1. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 19.4.2.11 |
5,164 | 5.4.1.2.3 EAP-TLS related procedures | 5.4.1.2.3.1 General The UE may support acting as EAP-TLS peer as specified in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. The AUSF may support acting as EAP-TLS server as specified in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. The AAA server of the CH or the DCS may support acting as EAP server of such EAP method as specified in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]. The EAP-TLS enables mutual authentication of the UE and the network. When initiating an EAP based primary authentication and key agreement procedure using EAP-TLS, the network shall select an ngKSI value. If an ngKSI is contained in an initial NAS message during a 5GMM procedure, the network shall select a different ngKSI value. The network shall send the selected ngKSI value to the UE along with each EAP message. The network shall send the ABBA value as described in subclause 9.11.3.10 to the UE along with the EAP-request message and EAP-success message. When the EAP based primary authentication and key agreement procedure uses EAP-TLS: a) if the UE operates in SNPN access operation mode and: 1) the default UE credentials for primary authentication, if the UE is registering or registered for onboarding services in SNPN; or 2) credentials in the selected entry of the "list of subscriber data", if the UE is not registering or registered for onboarding services in SNPN; contain an indication to use MSK for derivation of KAUSF after success of primary authentication and key agreement procedure then the ME shall generate MSK as described in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24] otherwise the ME shall generate EMSK as described in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]; b) if the AUSF acts as the EAP-TLS server, the AUSF shall generate EMSK as described in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]; and c) if the AAA server of the CH or the DCS acts as the EAP-TLS server, the AAA server of the CH or the DCS shall generate MSK as described in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. When handling of an EAP-request message results into generation of MSK or EMSK, if the UE operates in SNPN access operation mode and: a) the default UE credentials for primary authentication, if the UE is registering or registered for onboarding services in SNPN; or b) credentials in the selected entry of the "list of subscriber data", if the UE is not registering or registered for onboarding services in SNPN; contain an indication to use MSK for derivation of KAUSF after success of primary authentication and key agreement procedure, then the ME may generate a new KAUSF from the MSK otherwise the ME may generate a new KAUSF from the EMSK. If the ME generates a new KAUSF, the ME shall generate a new KSEAF from the new KAUSF, and the KAMF from the ABBA received together with the EAP-request message, and the new KSEAF as described in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24], and create a partial native 5G NAS security context identified by the ngKSI value received together with the EAP-request message in subclause 5.4.1.2.4.2, in the volatile memory of the ME. If the KAMF and the partial native 5G NAS security context are created, the ME shall store the KAMF in the created partial native 5G NAS security context. NOTE 1: Generation of the new KAUSF and the new KSEAF does not result into deletion of the valid KAUSF and the valid KSEAF, if any. The ME shall not use the new KAUSF in the verification of SOR transparent container and UE parameters update transparent container, if any are received, until receipt of an EAP-success message. When the AUSF acts as the EAP-TLS server and handling of an EAP response message results into generation of EMSK, the AUSF shall generate the KAUSF from the EMSK, and the KSEAF from the KAUSF as described in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. NOTE 2: When the AAA server of the CH or the DCS acts as the EAP-TLS server, the AAA server of the CH or the DCS provides (via the NSSAAF) the MSK and the SUPI to the AUSF. Upon reception of the MSK, the AUSF generates the KAUSF from the MSK, and the KSEAF from the KAUSF as described in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. NOTE 3: The AUSF provides the KSEAF and optionally the SUPI (unless the SEAF provided the AUSF with the SUPI before) to the SEAF as described in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. Upon reception of the KSEAF and optionally the SUPI, the SEAF generates the KAMF based on the ABBA, the KSEAF and the SUPI as described in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24], and provides ngKSI and the KAMF to the AMF. Upon reception of the ngKSI and the KAMF, the AMF creates a partial native 5G NAS security context identified by the ngKSI, and stores the KAMF in the created partial native 5G NAS security context. If the UE does not accept the server certificate of the network, the UE shall start timer T3520 when the AUTHENTICATION RESPONSE message containing the EAP-response message is sent. Furthermore, the UE shall stop any of the retransmission timers that are running (e.g. T3510, T3517 or T3521). Upon receiving an AUTHENTICATION REQUEST message with the EAP message IE containing an EAP-request message from the network, the UE shall stop timer T3520, if running, and then process the EAP-request message as normally. If the network does not accept the client certificate of the UE, the network handling depends upon the type of identity used by the UE in the initial NAS message, that is: - if the 5G-GUTI was used; or - if the SUCI was used. If the 5G-GUTI was used, the network should transport the EAP-failure message in the AUTHENTICATION RESULT message of the EAP result message transport procedure, initiate an identification procedure to retrieve SUCI from the UE and restart the EAP based primary authentication and key agreement procedure with the received SUCI. If the SUCI was used for identification in the initial NAS message or in a restarted EAP based primary authentication and key agreement procedure, or the network decides not to initiate the identification procedure to retrieve SUCI from the UE after an unsuccessful the EAP based primary authentication and key agreement procedure, the network should transport the EAP-failure message in an AUTHENTICATION REJECT message of the EAP result message transport procedure. Depending on local requirements or operator preference for emergency services, if the UE initiates a registration procedure with 5GS registration type IE set to "emergency registration" and the AMF is configured to allow emergency registration without user identity, the AMF needs not follow the procedures specified for transporting the EAP-failure message in the AUTHENTICATION REJECT message of the EAP result message transport procedure in the present subclause. The AMF may include the EAP-failure message in a response of the current 5GMM specific procedure or in the AUTHENTICATION RESULT of the EAP result message transport procedure. If the EAP-failure message is received in an AUTHENTICATION REJECT message: a) if the AUTHENTICATION REJECT message has been successfully integrity checked by the NAS: 1) the UE shall set the update status to 5U3 ROAMING NOT ALLOWED, delete the stored 5G-GUTI, TAI list, last visited registered TAI and ngKSI. In case of PLMN, the USIM shall be considered invalid until switching off the UE or the UICC containing the USIM is removed. In case of SNPN, if the UE is neither registered for onboarding services in SNPN nor performing initial registration for onboarding services in SNPN and the UE does not support access to an SNPN using credentials from a credentials holder and does not support equivalent SNPNs, the entry of the "list of subscriber data" with the SNPN identity of the current SNPN shall be considered invalid until the UE is switched off or the entry is updated; In case of SNPN, if the UE is neither registered for onboarding services in SNPN nor performing initial registration for onboarding services in SNPN and the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs, or both, the UE shall consider the selected entry of the "list of subscriber data" as invalid until the UE is switched off or the entry is updated. If the UE is registered for onboarding services in SNPN or is performing initial registration for onboarding services in SNPN, the UE shall store the SNPN identity in the "permanently forbidden SNPNs" list for onboarding services, enter state 5GMM-DEREGISTERED.PLMN-SEARCH, and perform an SNPN selection or an SNPN selection for onboarding services according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]; 2) if the UE is neither registered for onboarding services in SNPN nor performing initial registration for onboarding services in SNPN, the UE shall set: i) the counter for "SIM/USIM considered invalid for GPRS services" events, the counter for "USIM considered invalid for 5GS services over non-3GPP access" events, and the counter for "SIM/USIM considered invalid for non-GPRS services" events if maintained by the UE, in case of PLMN; or ii) the counter for "the entry for the current SNPN considered invalid for 3GPP access" events and the counter for "the entry for the current SNPN considered invalid for non-3GPP access" events in case of SNPN; . to UE implementation-specific maximum value. If the UE is registered for onboarding services in SNPN or performing initial registration for onboarding services in SNPN, the UE shall set the SNPN-specific attempt counter for the current SNPN to the UE implementation-specific maximum value; and 3) if the UE is operating in single-registration mode, the UE shall handle EMM parameters, 4G-GUTI, last visited registered TAI, TAI list and eKSI as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] for the case when the authentication procedure is not accepted by the network. The USIM shall be considered as invalid also for non-EPS services until switching off or the UICC containing the USIM is removed; and b) if the AUTHENTICATION REJECT message is received without integrity protection, the UE shall start timer T3247 with a random value uniformly drawn from the range between 30 minutes and 60 minutes, if the timer is not running (see subclause 5.3.20). Additionally, if the UE is neither registered for onboarding services in SNPN nor performing initial registration for onboarding services in SNPN, the UE shall: 1) if the AUTHENTICATION REJECT message is received over 3GPP access, and the counter for "SIM/USIM considered invalid for GPRS services" events in case of PLMN or the counter for "the entry for the current SNPN considered invalid for 3GPP access" events in case of SNPN has a value less than a UE implementation-specific maximum value, proceed as specified in subclause 5.3.20, list item 1)-a) of subclause 5.3.20.2 (if the UE is not SNPN enabled or is not operating in SNPN access operation mode) or list item a) 1) of subclause 5.3.20.3 (if the UE is operating in SNPN access operation mode) for the case that the 5GMM cause value received is #3; 2) if the AUTHENTICATION REJECT message is received over non-3GPP access, and the counter for "USIM considered invalid for 5GS services over non-3GPP access" events in case of PLMN or the counter for "the entry for the current SNPN considered invalid for non-3GPP access" events in case of SNPN has a value less than a UE implementation-specific maximum value, proceed as specified in subclause 5.3.20, list item 1)-b) of subclause 5.3.20.2 (if the UE is not operating in SNPN access operation mode) or list item a)-2) of subclause 5.3.20.3 (if the UE is operating in SNPN access operation mode) for the case that the 5GMM cause value received is #3; or 3) otherwise: i) if the AUTHENTICATION REJECT message is received over 3GPP access: A) the UE shall set the update status for 3GPP access to 5U3 ROAMING NOT ALLOWED, delete for 3GPP access only the stored 5G-GUTI, TAI list, last visited registered TAI and ngKSI. In case of PLMN, the UE shall consider the USIM as invalid for 5GS services via 3GPP access and invalid for non-EPS service until switching off the UE or the UICC containing the USIM is removed. In case of SNPN, if the UE does not support access to an SNPN using credentials from a credentials holder and does not support equivalent SNPNs, the UE shall consider the entry of the "list of subscriber data" with the SNPN identity of the current SNPN as invalid for 3GPP access until the UE is switched off or the entry is updated; In case of SNPN, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs, or both, the UE shall consider the selected entry of the "list of subscriber data" as invalid for 3GPP access until the UE is switched off or the entry is updated; B) the UE shall set: - the counter for "SIM/USIM considered invalid for GPRS services" events and the counter for "SIM/USIM considered invalid for non-GPRS services" events if maintained by the UE, in case of PLMN; or - the counter for "the entry for the current SNPN considered invalid for 3GPP access" events in case of SNPN; to UE implementation-specific maximum value; and C) If the UE is operating in single-registration mode, the UE shall handle 4G-GUTI, TAI list and eKSI as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] for the case when the authentication procedure is not accepted by the network. The USIM shall be considered as invalid also for non-EPS services until switching off or the UICC containing the USIM is removed; and ii) if the AUTHENTICATION REJECT message is received over non-3GPP access: A) the UE shall set the update status for non-3GPP access to 5U3 ROAMING NOT ALLOWED, delete for non-3GPP access only the stored 5G-GUTI, TAI list, last visited registered TAI and ngKSI. In case of PLMN, the USIM shall be considered invalid for 5GS services via non-3GPP access until switching off the UE or the UICC containing the USIM is removed. In case of SNPN, the UE shall consider the entry of the "list of subscriber data" with the SNPN identity of the current SNPN shall be considered invalid for non-3GPP access until the UE is switched off or the entry is updated; and B) the UE shall set the counter for "USIM considered invalid for 5GS services over non-3GPP access" events in case of PLMN or the counter for "the entry for the current SNPN considered invalid for non-3GPP access" events in case of SNPN to UE implementation-specific maximum value. If the UE is registered for onboarding services in SNPN or performing initial registration for onboarding services in SNPN, the UE shall: 1) if the SNPN-specific attempt counter for the SNPN sending the AUTHENTICATION REJECT message has a value less than a UE implementation-specific maximum value, increment the SNPN-specific attempt counter for the SNPN; or 2) otherwise, the UE shall set the update status to 5U3.ROAMING NOT ALLOWED, delete the stored 5G-GUTI, TAI list, last visited registered TAI, and ngKSI, store the SNPN identity in the "permanently forbidden SNPNs" list for onboarding services, enter state 5GMM-DEREGISTERED.PLMN-SEARCH, and perform an SNPN selection or an SNPN selection for onboarding services according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]. If the AUTHENTICATION REJECT message is received by the UE, the UE shall abort any 5GMM signalling procedure, stop any of the timers T3510, T3517, T3519 or T3521 (if they were running), enter state 5GMM-DEREGISTERED and delete any stored SUCI. Upon receiving an EAP-success message, the ME shall: a) delete the valid KAUSF and the valid KSEAF, if any; b) if the ME has not generated a new KAUSF and a new KSEAF and has not created a partial native 5G NAS security context when handling the EAP-request message which resulted into generation of EMSK or MSK as described above: 1) if the UE operates in SNPN access operation mode and: i) the default UE credentials for primary authentication, if the UE is registering or registered for onboarding services in SNPN; or ii) credentials in the selected entry of the "list of subscriber data", if the UE is not registering or registered for onboarding services in SNPN; contain an indication to use MSK for derivation of KAUSF after success of primary authentication and key agreement procedure then generate a new KAUSF from the MSK otherwise generate a new KAUSF from the EMSK; 2) generate a new KSEAF from the new KAUSF, and the KAMF from the ABBA that was received with the EAP-success message, and the new KSEAF as described in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]; 3) create a partial native 5G NAS security context identified by the ngKSI value in the volatile memory of the ME; and 4) store the KAMF in the created partial native 5G NAS security context; and c) consider the new KAUSF to be the valid KAUSF, and the new KSEAF to be the valid KSEAF, reset the SOR counter and the UE parameter update counter to zero, store the valid KAUSF, the valid KSEAF, the SOR counter and the UE parameter update counter as specified in annex C, and use the valid KAUSF in the verification of SOR transparent container and UE parameters update transparent container, if any are received. The UE shall consider the procedure complete. Upon receiving an EAP-failure message, the UE shall delete the partial native 5G NAS security context and shall delete the new KAUSF and the new KSEAF, if any were created when handling the EAP-request message which resulted into generation of EMSK or MSK as described above. The UE shall consider the procedure complete. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.4.1.2.3 |
5,165 | 9.11.2.7 N1 mode to S1 mode NAS transparent container | The purpose of the N1 mode to S1 mode NAS transparent container information element is to provide the UE with information that enables the UE to create a mapped EPS security context. The N1 mode to S1 mode NAS transparent container information element is coded as shown in figure 9.11.2.7.1 and table 9.11.2.7.1. The N1 mode to S1 mode NAS transparent container is a type 3 information element with a length of 2 octets. The value part of the N1 mode to S1 mode NAS transparent container information element is included in specific information elements within some RRC messages sent to the UE; see 3GPP TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [30]. For these cases the coding of the information element identifier and length information is defined in 3GPP TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [30]. Figure 9.11.2.7.1: N1 mode to S1 mode NAS transparent container information element Table 9.11.2.7.1: N1 mode to S1 mode NAS transparent container information element | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.11.2.7 |
5,166 | 6.6.4.1 PBCH repetition in the cell acquisition subframe | For a MBMS-dedicated cell with , - symbols mapped to core resource element in slot 1 in subframe 0 within a radio frame according to the mapping operation in clause 6.6.4, and - cell-specific reference signals in OFDM symbols in slot 1 in subframe 0 within a radio frame with according to the mapping operation in clause 6.6.4 shall additionally be multiplied by and mapped to resource elements in slot number within radio frame where and are given by Table 6.6.4.1-1 in frames fulfilling - for ; - for Resource elements already reserved or used for transmission of cell-specific reference signals in absence of repetition shall not be used for additional mapping of cell-specific reference signals. The quantity is given by where the relationship between and is defined in clause 6.6.4, and the pseudo-random sequence is given by clause 7.2 and initialized for each OFDM symbol with Table 6.6.4.1-1: Slot and symbol number pair for repetition of PBCH. | 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.6.4.1 |
5,167 | 6.2.4.2 IP address allocation via NAS signalling | The UE shall set the PDU session type IE in the PDU SESSION ESTABLISHMENT REQUEST message, based on its IP stack capabilities if the UE requests IP connectivity as follows: a) A UE: 1) which is IPv6 and IPv4 capable, shall set the PDU session type IE to IPv4, IPv6 or IPv4v6 according to UE configuration or received policy. 2) which is only IPv6 capable, shall set the PDU session type IE to IPv6. 3) which is only IPv4 capable, shall set the PDU session type IE to IPv4. b) When the IP version capability of the UE is unknown in the UE (as in the case when the MT and TE are separated and the capability of the TE is not known in the MT), the UE shall set the PDU session type IE to IPv4v6. If the UE wants to use DHCPv4 for IPv4 address assignment, it shall indicate that to the network within the Extended protocol configuration options IE in the PDU SESSION ESTABLISHMENT REQUEST. On receipt of the PDU SESSION ESTABLISHMENT REQUEST message sent by the UE, the network when allocating an IP address shall take into account the PDU session type IE, the operator's policies of the network, and the user's subscription data and: a) if the network sets the Selected PDU session type IE to IPv4, the network shall include an IPv4 address in the PDU address IE; b) if the network sets the Selected PDU session type IE to IPv6, the network shall include an interface identifier for the IPv6 link local address in the PDU address IE; and c) if the network sets the Selected PDU session type IE to IPv4v6, the network shall include an IPv4 address and an interface identifier for the IPv6 link local address in the PDU address IE. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.2.4.2 |
5,168 | 4.3 Frame structure type 3 | Frame structure type 3 is applicable to LAA secondary cell operation with normal cyclic prefix only. Each radio frame is long and consists of 20 slots of length, numbered from 0 to 19. A subframe is defined as two consecutive slots where subframe consists of slots and. The 10 subframes within a radio frame are available for downlink or uplink transmissions. Downlink transmissions occupy one or more consecutive subframes, starting anywhere within a subframe and ending with the last subframe either fully occupied or following one of the DwPTS durations in Table 4.2-1. Uplink transmisisons occupy one or more consecutive subframes. | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 4.3 |
5,169 | 5.8.17.2 NR Sidelink U2U Remote UE threshold conditions | A UE capable of NR sidelink U2U Remote UE operation shall: 1> if the threshold conditions for direct PC5 link specified in this clause were previously not met: 2> if sl-RSRP-ThreshU2U is not configured, or if the SL-RSRP measurement of the peer NR sidelink U2U Remote UE is available and is below sl-RSRP-ThreshU2U by sl-HystMinU2U if configured; or 2> if sd-RSRP-ThreshU2U is not configured, or if the SD-RSRP measurement of the peer NR sidelink U2U Remote UE is available and is below sd-RSRP-ThreshU2U by sd-HystMinU2U if configured: 3> consider the threshold conditions to be met (entry); 1> else: 2> if the SL-RSRP measurement of the peer NR sidelink U2U Remote UE is available and is above sl-RSRP-ThreshU2U if configured; or 2> if the SD-RSRP measurement of the peer NR sidelink U2U Remote UE is available and is above sd-RSRP-ThreshU2U if configured: 3> consider the threshold conditions not to be met (leave); 1> if the threshold conditions for U2U relay discovery with Model B specified in this clause were previously not met: 2> if the sd-RSRP-ThreshU2U is not configured, or if the SD-RSRP of the NR sidelink U2U Relay UE is available and is above sd-RSRP-ThreshU2U if configured: 3> consider the threshold conditions to be met (entry); 1> else: 2> if the SD-RSRP of the NR sidelink U2U Relay UE is available and is below sl-RSRP-ThreshU2U by sd-HystMinU2U if configured: 3> consider the threshold conditions not to be met (leave); Editor's Note: FFS whether/how to capture if the SL-RSRP/SD-RSRP measurement of the peer NR sidelink U2U Remote UE is not available. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.17.2 |
5,170 | 5.7.3.4 Packet Delay Budget | The Packet Delay Budget (PDB) defines an upper bound for the time that a packet may be delayed between the UE and the N6 termination point at the UPF. The PDB applies to the DL packet received by the UPF over the N6 interface, and to the UL packet sent by the UE. For a certain 5QI the value of the PDB is the same in UL and DL. In the case of 3GPP access, the PDB is used to support the configuration of scheduling and link layer functions (e.g. the setting of scheduling priority weights and HARQ target operating points). For GBR QoS Flows using the Delay-critical resource type, a packet delayed more than PDB is counted as lost if the data burst is not exceeding the MDBV within the period of PDB and the QoS Flow is not exceeding the GFBR. For GBR QoS Flows with GBR resource type not exceeding GFBR, 98 percent of the packets shall not experience a delay exceeding the 5QI's PDB. The 5G Access Network Packet Delay Budget (5G-AN PDB) is determined by subtracting a static value for the Core Network Packet Delay Budget (CN PDB), which represents the delay between any N6 termination point at the UPF (for any UPF that may possibly be selected for the PDU Session) and the 5G-AN from a given PDB. NOTE 1: For a standardized 5QI, the static value for the CN PDB is specified in the QoS characteristics Table 5.7.4-1. NOTE 2: For a non-standardized 5QI, the static value for the CN PDB is homogeneously configured in the network. For GBR QoS Flows using the Delay-critical resource type, in order to obtain a more accurate delay budget PDB available for the NG-RAN, a dynamic value for the CN PDB, which represents the delay between the UPF terminating N6 for the QoS Flow and the 5G-AN, can be used. If used for a QoS Flow, the NG-RAN shall apply the dynamic value for the CN PDB instead of the static value for the CN PDB (which is only related to the 5QI). Different dynamic value for CN PDB may be configured per uplink and downlink direction. NOTE 3: The configuration of transport network on CN tunnel can be different per UL and DL, which can be different value for CN PDB per UL and DL. NOTE 4: It is expected that the UPF deployment ensures that the dynamic value for the CN PDB is not larger than the static value for the CN PDB. This avoids that the functionality that is based on the 5G-AN PDB (e.g. MDBV, NG-RAN scheduler) has to handle an unexpected value. The dynamic value for the CN PDB of a Delay-critical GBR 5QI may be configured in the network in two ways: - Configured in each NG-RAN node, based on a variety of inputs such as different IP address(es) or TEID range of UPF terminating the N3 tunnel and based on different combinations of PSA UPF to NG-RAN under consideration of any potential I-UPF, etc; - Configured in the SMF, based on different combinations of PSA UPF to NG-RAN under consideration of any potential I-UPF. The dynamic value for the CN PDB for a particular QoS Flow shall be signalled to NG-RAN (during PDU Session Establishment, PDU Session Modification, Xn/N2 handover and the Service Request procedures) when the QoS Flow is established or the dynamic value for the CN PDB of a QoS Flow changes, e.g. when an I-UPF is inserted by the SMF. If the NG-RAN node is configured locally with a dynamic value for the CN PDB for a Delay-critical GBR 5QI, and receives a different value via N2 signalling for a QoS Flow with the same 5QI, local configuration in RAN node determines which value takes precedence. Services using a GBR QoS Flow and sending at a rate smaller than or equal to the GFBR can in general assume that congestion related packet drops will not occur. NOTE 5: Exceptions (e.g. transient link outages) can always occur in a radio access system which may then lead to congestion related packet drops. Packets surviving congestion related packet dropping may still be subject to non-congestion related packet losses (see PER below). Services using Non-GBR QoS Flows should be prepared to experience congestion-related packet drops and delays. In uncongested scenarios, 98 percent of the packets should not experience a delay exceeding the 5QI's PDB. The PDB for Non-GBR and GBR resource types denotes a "soft upper bound" in the sense that an "expired" packet, e.g. a link layer SDU that has exceeded the PDB, does not need to be discarded and is not added to the PER. However, for a Delay-critical GBR resource type, packets delayed more than the PDB are added to the PER and can be discarded or delivered depending on local decision. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.7.3.4 |
5,171 | 5.15.17 Partial Network Slice support in a Registration Area | A Network Slice may be supported in one or more TAs in a PLMN/SNPN. The Partial Network Slice support in a Registration Area for a UE includes configuring the UE with a Partially Allowed NSSAI and/or S-NSSAI(s) rejected partially in the RA. When creating a Registration Area for UEs registering over the 3GPP access and supporting the Partial Network Slice support in a Registration Area, the AMF may consider the trade-off between signalling for paging in TAs where the S-NSSAI is not supported versus the signalling for Mobility Registration Updates to register with the S-NSSAI in the TA(s) where the S-NSSAI is supported, so that the AMF may create a Registration Area including the TA(s) where a requested S-NSSAI is not supported. For supporting UEs, whether the AMF uses the Partially Allowed NSSAI or rejects the S-NSSAIs partially in the RA, or whether the AMF rejects the S-NSSAI for the current RA, is a per S-NSSAI decision which is based on AMF local policy. If supported and allowed by local policy, the Partially Allowed NSSAI and S-NSSAIs rejected partially in the RA may be applied simultaneously for one UE for different S-NSSAIs. For such S-NSSAI: - If requested by the UE from a TA where the S-NSSAI is not supported (including the case when the S-NSSAI is provided as a rejected S-NSSAI for the TA from the NSSF): - the S-NSSAI is included either in the Partially Allowed NSSAI or the AMF rejects the S-NSSAI partially in the RA; or - if the S-NSSAI is subject to NSAC for maximum number of UEs, then the AMF should send this S-NSSAI as rejected partially in the RA, in the Registration Accept message. - If the S-NSSAI is subject to NSSAA and successful NSSAA status for the S-NSSAI is not present in the AMF, then the AMF either sends this S-NSSAI as rejected partially in the RA in the Registration Accept message, or the AMF starts executing NSSAA and includes the S-NSSAI in the Pending NSSAI in the Registration Accept message. If the S-NSSAI is subject to NSSAA and successful NSSAA status for the S-NSSAI is present, then the AMF may include the S-NSSAI either in the Partially Allowed NSSAI or the AMF rejects the S-NSSAI partially in the RA. NOTE 1: In roaming case the NSSAA requirement is based on the mapped S-NSSAI of the HPLMN. - if the slice deregistration inactivity timer is configured for the S-NSSAI (see clause 5.15.15.3), then AMF should send this S-NSSAI as rejected partially in the RA. - If requested by the UE from a TA where the S-NSSAI is supported (including the case when the S-NSSAI is provided in the Allowed NSSAI from the NSSF): - the S-NSSAI is included in the Partially Allowed NSSAI; or - if the S-NSSAI is subjected to NSAC for maximum number of UEs, then the AMF should restrict the RA so that the S-NSSAI is supported in all the TAs of the RA and includes the S-NSSAI in the Allowed NSSAI. - If the S-NSSAI is subject to NSSAA, then the AMF starts executing NSSAA and sends this S-NSSAI in the Pending NSSAI in the Registration Accept message, unless successful NSSAA status is present in the AMF for this S-NSSAI (in which case it can be sent in the Partially Allowed NSSAI). NOTE 2: In roaming case the NSSAA requirement is based on the mapped S-NSSAI of the HPLMN. - if the S-NSSAI is included in neither the Partially Allowed NSSAI nor the Allowed NSSAI, the AMF may reject the S-NSSAI as described in clause 5.15.4.1.1. While the S-NSSAIs of the Allowed NSSAI are supported in all the TAs of the Registration Area, the S-NSSAIs of the Partially Allowed NSSAI are supported only in the TAs corresponding to the list of TAs (which are subset of the list of TAIs forming the Registration Area) associated with the S-NSSAI. If the UE supports Partial Network Slice support in a Registration Area, the AMF may create a Registration Area for the UE considering the support of the S-NSSAIs of the Requested NSSAI in the current TA and in the neighbouring TAs and provides to the UE in the Registration Accept message or in the UE Configuration Update Command message the Partially Allowed NSSAI or the S-NSSAIs rejected partially in the RA as follows: - If one or more of the requested S-NSSAI(s) are supported in a subset of the TAs of the (potential) Registration Area, the AMF may include such S-NSSAI(s) in the Partially Allowed NSSAI and corresponding mapping information of the S-NSSAI(s) of the Partially Allowed NSSAI to the HPLMN S-NSSAI(s). For each S-NSSAI of the Partially Allowed NSSAI the AMF provides a list of TAs where the S-NSSAI is supported. The UE is considered registered with the S-NSSAI in the whole Registration area. The AMF also provides the Partially Allowed NSSAI (without indication of the TA list where the partially allowed S-NSSAIs are supported) to the NG-RAN together with the UE's context. - Alternatively, the AMF may reject the S-NSSAI(s) with reject cause indicating "partially in the RA". For each S-NSSAI of the S-NSSAIs rejected partially in the RA the AMF provides a list of TAs where the S-NSSAI is not supported. NOTE 3: If the UE requests an S-NSSAI in a cell of a TA where the NS-AoS of the S-NSSAI does not match deployed Tracking Areas (see clause 5.15.18), the AMF includes the S-NSSAI in the Allowed NSSAI or Partially Allowed NSSAI. When the UE stores Partially Allowed NSSAI the following applies: - the UE is considered registered with an S-NSSAI of the Partially Allowed NSSAI in the whole Registration area. The UE does not trigger registration when moving between the TAs of support and non-support for the S-NSSAI within the RA. - The UE is allowed to initiate PDU Session establishment for the S-NSSAI only when the UE is in a TA where the S-NSSAI is supported. - If the AMF determines a PDU Session is associated with S-NSSAI present in the Partially Allowed NSSAI, the AMF indicates to the SMF that the PDU Session is subject to area restrictions for the S-NSSAI. As a result, the SMF subscribes to "UE mobility event notification" for reporting UE presence in Area of Interest by providing S-NSSAI to the AMF as described in clauses 5.6.11 and 5.3.4.4. - When the UE has already established a PDU Session with an S-NSSAI part of the Partially Allowed NSSAI, the UE is allowed to activate the User Plane resources of the PDU Session only when the UE is in a TA part of the list of TAs associated with the S-NSSAI. - When the User Plane resources are activated for a PDU Session of an S-NSSAI part of the Partially Allowed NSSAI and the UE moves to a TA which is not part of the list of TAs associated with the S-NSSAI, the User Plane resources for the PDU Session shall be deactivated, but the PDU Session context in UE and SMF is not released. The User Plane resources for the PDU Session shall not be activated as long as the UE is located in a TA which is not part of the list of TAs associated with the S-NSSAI of the Partially Allowed NSSAI. The UE shall not send user data as payload of a NAS message (see clause 5.31.4.1) in uplink directions. When the SMF is notified by the AMF that the UE location is outside of the Area of Interest, the SMF shall not send user data as payload of NAS message (see clause 5.31.4.1) in downlink directions and disable data notification. When the SMF is notified by the AMF that the UE location is UNKNOWN as defined in Annex D, clauses D.1 and D.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3], then based on operator policy SMF may enable downlink data notification and trigger the Network triggered Service Request procedure to active the UP connection or send user data as payload of a NAS message (see clause 5.31.4.1) when the SMF receives downlink data or Data Notification from UPF. Editor's note: Whether and based on what criteria to trigger the reporting and the applicability to the CP CIOT optimization use cases are FFS. For an already established PDU Session associated with an S-NSSAI included in the Partially Allowed NSSAI, even when the UE is in a TA where the S-NSSAI is not supported, the UE and the SMF may initiate a PDU Session release procedure or PDU Session modification procedure (i.e. for PS data off status change reporting). When the UE stores a S-NSSAI rejected partially in the RA with the associated list of TAs, the UE is allowed to initiate a Mobility Registration Update procedure to request registration with the S-NSSAI only when the UE is in a TA which is not part of the list of TAs associated with this S-NSSAI. For a UE in CM-CONNECTED state, when a PDU Session is established on an S-NSSAI included in the Partially Allowed NSSAI, the User Plane resources are activated and the UE moves to a TA where the S-NSSAI is not supported, the NG-RAN releases the User Plane resources of the PDU sessions associated with the S-NSSAIs, as described in step 1d of clause 4.3.4.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] and the SMF deactivates the PDU session as described in step 3a of clause 4.3.4.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.15.17 |
5,172 | 4.22.9.4 Network Triggered Service Request | The signalling flow for a Network Triggered Service Request is based on the signalling flow in Figure 4.2.3.3-1 with the following differences and clarifications: - In step 2a, the SMF determines over which access (3GPP access or non-3GPP access or both accesses) the user plane resources need to be activated for the MA PDU Session. The SMF may consider Steering Mode to determine the target access. - In step 3a, the SMF indicates to the AMF the access type (3GPP access or non-3GPP access) over which the user plane resources are to be activated for the MA PDU Session. NOTE 1: If the SMF determines to activate both accesses, the SMF performs this step two times, i.e. one for 3GPP access and the other one for non-3GPP access. In the case of DN-AAA or SMF initiated Secondary re-authentication procedure, when the SMF invokes the Namf_Communication_N1N2MessageTransfer service operation, SMF may indicate the target access type of sending N1 NAS message to the UE. - In step 4, the AMF considers the MA PDU Session is associated with the access type the SMF has indicated in step 3a. The AMF determines the access type of which to send the N1 NAS message to the UE based on the target access type value if received from the SMF in step 3a. If the AMF does not receive a target access type value and the UE is CM-CONNECTED in both accesses, the AMF determines the target access type. - In step 5, if the SMF requested to re-activate user-plane resources over 3GPP access and the AMF has determined the UE is unreachable over 3GPP access (e.g. the AMF receives no response from the UE to the Paging), the AMF shall notify that the UE is unreachable. The (H-) SMF shall indicate the Anchor UPF that the user-plane resources on 3GPP access is unavailable by triggering N4 Session Modification procedure. Further action by the UPF is implementation dependent. If the SMF requested to re-activate the user-plane resources over non-3GPP access and the AMF has determined the UE is unreachable over non-3GPP access (e.g. the UE is in CM-IDLE on non-3GPP access), the AMF shall reject the request from the SMF. The (H-) SMF shall indicate the Anchor UPF that the user-plane resources on non-3GPP access is unavailable by triggering N4 Session Modification procedure. Further action by the UPF is implementation dependent. If this procedure is triggered for Secondary Re-authentication and UE and SMF+PGW-C supports for DN authentication and authorization over EPC as described in clause 5.4.4b, SMF+PGW-C selects one access type from non-3GPP access connected to 5GC or 3GPP access connected to EPC in step 3a. If the SMF+PGW-C receives failure indication from the AMF or MME that UE is unreachable then SMF+PGW-C retries by sending it to the other access type. Only when the failure is received from both AMF and MME, then SMF+PGW-C informs the DN-AAA Server that UE is not reachable for re-authentication according to clauses 4.3.2.3 and H.2.1. NOTE 2: The provision of access availability/unavailability reports via user plane specified in clause 5.32.5.3 is UE implementation dependent. Such reporting by UE to UPF, can assist Anchor UPF to decide on handling DL traffic for the UE. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.22.9.4 |
5,173 | 5.2.6.25.3 Nnef_TimeSynchronization_ConfigUpdate operation | Service operation name: Nnef_TimeSynchronization_ConfigUpdate Description: The consumer requests to update the time synchronization configuration, for which the NEF authorizes the request and invokes the corresponding service operation with TSCTSF (clause 5.2.27.2.3). Inputs, Required: As specified in clause 5.2.27.2.3. Inputs, Optional: As specified in clause 5.2.27.2.3. Outputs, Required: Operation execution result indication and in the case of successful operation, any outputs as specified in clause 5.2.27.2.3. Outputs, Optional: As specified in clause 5.2.27.2.3. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.6.25.3 |
5,174 | 10.5.5.9 Identity type 2 | The purpose of the identity type 2 information element is to specify which identity is requested. The identity type 2 is a type 1 information element. The identity type 2 information element is coded as shown in figure 10.5.125/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.142/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.125/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Identity type 2 information element Table 10.5.142/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Identity type 2 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.9 |
5,175 | 9.3.1.3 Measurements | Inter RAT measurements in NR for this use case are limited to E-UTRA. Whether a measurement is non-gap-assisted or gap-assisted depends on the capability of the UE and the current operating frequency: - For E-UTRA Inter RAT measurement, if the measurement gap requirement information is reported by the UE, a measurement gap configuration may be provided according to the information. Otherwise, a measurement gap configuration is always provided when: - The UE only supports per-UE measurement gaps; or - The UE supports per-FR measurement gaps and at least one of the NR serving cells is in FR1. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 9.3.1.3 |
5,176 | 6.3.2 Principles of address handling for ESM procedures | Transaction related procedures use the procedure transaction identity as address parameter in the ESM message header. When the UE or the network initiates a transaction related procedure, it shall include a valid procedure transaction identity value in the message header and set the EPS bearer identity to "no EPS bearer identity assigned". When the ProSe UE-to-network relay initiates the transaction related procedure remote UE report, it shall include a valid procedure transaction identity value in the message header and set the EPS bearer identity to a valid EPS bearer identity value. If the response message is again a transaction related message, e.g. a PDN CONNECTIVITY REJECT, PDN DISCONNECT REJECT, BEARER RESOURCE ALLOCATION REJECT, BEARER RESOURCE MODIFICATION REJECT, ESM INFORMATION REQUEST message or ESM DUMMY MESSAGE from the network or an ESM INFORMATION RESPONSE message or ESM DUMMY MESSAGE from the UE, the sending entity shall include the procedure transaction identity value received with the request message and set the EPS bearer identity to "no EPS bearer identity assigned" (see examples in figures 6.3.2.1, 6.3.2.1a and 6.3.2.2). If the response message is the transaction related message REMOTE UE REPORT RESPONSE message from the network, the network shall include the procedure transaction identity value received with the request message and set the EPS bearer identity to the EPS bearer identity value received from the ProSe UE-to-network relay (see example in figure 6.3.2.2a). If an ESM DUMMY MESSAGE is sent in response to a received ESM DUMMY MESSAGE, the sending entity shall include the received procedure transaction identity value in the message header and set the EPS bearer identity to "no EPS bearer identity assigned". Figure 6.3.2.1: Transaction related procedure initiated by the UE and rejected by the network Figure 6.3.2.1a: Transaction related procedure initiated by the UE and responded by a network initiated transaction related request Figure 6.3.2.2: Transaction related procedure initiated by the network Figure 6.3.2.2a: Transaction related procedure initiated by the UE EPS bearer context related procedures use the EPS bearer identity as address parameter in the ESM message header. When the network initiates an EPS bearer context related procedure, it shall include a valid EPS bearer identity value in the message header. The procedure transaction identity value shall be set as follows: - If the EPS bearer context related procedure was triggered by the receipt of a transaction related request message from the UE, the network shall include the procedure transaction identity value received with the transaction related request message in the message header of the EPS bearer context related request message (see example in figure 6.3.2.3). - If the procedure was triggered network-internally, the network shall set the procedure transaction identity value in the message header of the EPS bearer context related request message to "no procedure transaction identity assigned" (see example in figure 6.3.2.4). - If the procedure was triggered by the transport of user data via the control plane, the network shall set the procedure transaction identity value in the message header of the EPS bearer context related request message to "no procedure transaction identity assigned" (see example in figure 6.3.2.5). In the response message of the EPS bearer context related procedure, the UE shall include the EPS bearer identity value received from the network and set the procedure transaction identity value to "no procedure transaction identity assigned". When the UE initiates an EPS bearer context related procedure and the procedure was triggered by the transport of user data via the control plane, it shall include a valid EPS bearer identity value and set the procedure transaction identity value to "no procedure transaction identity assigned" in the message header (see example in figure 6.3.2.6). Figure 6.3.2.3: EPS bearer context related procedure triggered by a transaction related request Figure 6.3.2.4: EPS bearer context related procedure triggered network-internally Figure 6.3.2.5: EPS bearer context related procedure triggered by network for the transport of user data via the control plane Figure 6.3.2.6: EPS bearer context related procedure triggered by UE for the transport of user data via the control plane | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.3.2 |
5,177 | 5.5.2.3.5 Abnormal cases in the network side | The following abnormal cases can be identified: a) T3522 time-out On the first expiry of the timer, the network shall retransmit the DEREGISTRATION REQUEST message and shall start timer T3522. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3522, the de-registration procedure shall be aborted. The network shall change to the state 5GMM-DEREGISTERED for the access type which the de-registration procedure is intended for. b) Lower layer failure The de-registration procedure is aborted. The network shall change to the state 5GMM-DEREGISTERED for the access type which the de-registration procedure is intended for. c) De-registration procedure collision If the network receives a DEREGISTRATION REQUEST message with "switch off" indication, before the network-initiated de-registration procedure has been completed: - If the access type included in the DEREGISTRATION REQUEST message sent by the UE is same as access type sent by the network, both procedures shall be considered completed; or - If the access type included in the DEREGISTRATION REQUEST message sent by the UE is not same as access type sent by the network, the network shall consder UE initiated de-registration completed. The network shall re-initiate the de-registration procedure, if required, for the access type not indicated in the DEREGISTRATION REQUEST message sent by the UE. If the network receives a DEREGISTRATION REQUEST message without "switch off" indication, before the network-initiated de-registration procedure has been completed, the network shall send a DEREGISTRATION ACCEPT message to the UE. d) De-registration and registration procedure for initial registration collision If the network receives a REGISTRATION REQUEST message indicating either "initial registration" or "emergency registration" in the 5GS registration type IE before the network-initiated de-registration procedure has been completed, the network shall abort the de-registration procedure and the registration procedure shall be progressed after the PDU sessions associated with the access type the REGISTRATION REQUEST message is sent over have been deleted. NOTE 1: The above collision case is valid if the DEREGISTRATION REQUEST message indicates the access type over which the initial registration procedure is attempted otherwise both the procedures are progressed. e) De-registration and registration procedure for mobility and periodic registration update collision If the network sent a DEREGISTRATION REQUEST message without 5GMM cause value #11, #12, #13 or #15 and the network receives a REGISTRATION REQUEST message indicating either "mobility registration updating" or "periodic registration updating" in the 5GS registration type IE before the network-initiated de-registration procedure has been completed, the de-registration procedure shall be progressed, i.e. the REGISTRATION REQUEST message shall be ignored. If the network sent a DEREGISTRATION REQUEST message with 5GMM cause value #11, #12, #13 or #15 and the network receives a REGISTRATION REQUEST message indicating either "mobility registration updating" or "periodic registration updating" in the 5GS registration type IE before the network-initiated de-registration procedure has been completed, the de-registration procedure shall be aborted and the registration procedure shall be progressed. NOTE 2: The above collision case is valid if the DEREGISTRATION REQUEST message indicates the access type over which the mobility and periodic registration procedure is attempted otherwise both the procedures are progressed. f) De-registration and service request procedure collision If the network receives a SERVICE REQUEST message or a CONTROL PLANE SERVICE REQUEST message before the network-initiated de-registration procedure has been completed (e.g. the DEREGISTRATION REQUEST message is pending to be sent to the UE), the network shall progress the de-registration procedure. NOTE 3: The above collision case is valid if the DEREGISTRATION REQUEST message indicates the access type over which the service request procedure is attempted otherwise both the procedures are progressed. g) De-registration requested for a UE not supporting CAG due to CAG restrictions Based on operator policy, if the network-initiated de-registration procedure is triggered for a UE not supporting CAG due to CAG restrictions, the network shall send the DEREGISTRATION REQUEST message including a 5GMM cause value other than the 5GMM cause #76 (Not authorized for this CAG or authorized for CAG cells only). NOTE 4: 5GMM cause #7 (5GS services not allowed), 5GMM cause #11 (PLMN not allowed), 5GMM cause #27 (N1 mode not allowed), 5GMM cause #73 (Serving network not authorized) can be used depending on the subscription of the UE and whether the UE roams or not. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.2.3.5 |
5,178 | A.2 New QoS Flow with RQoS | The following figure shows an example message flow when RQoS is used for a new QoS flow. In this example, the gNB receives from UPF a first downlink packet associated with a QFI for which the QoS parameters are known from the PDU session establishment, but for which there is no association to any DRB yet in AS. Figure A.2-1: DL data with new QFI sent over existing DRB 0. PDU session and DRB(s) have been already established. 1. gNB receives a downlink packet with a new QFI from UPF. 2. gNB decides to send the new QoS flow over an existing DRB. NOTE: If gNB decides to send it over a new DRB, it needs to establish the DRB first. 3. gNB sends the DL packet over the selected DRB with the new QFI and RDI set in the SDAP header. 4. UE identifies the QFI and RDI in the received DL packet and the DRB on which the packet was received. The AS mapping rules are then updated accordingly. 5. User Plane Data for the new QoS flow can then be exchanged between UE and gNB over the DRB according to the updated mapping rules and between UPF and gNB over the tunnel for the PDU session. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | A.2 |
5,179 | Annex G (informative): Components of Mobility Latency | HO interruption time for L1/L2-based inter-cell mobility is the time from UE receives the cell switch command to UE performs the first DL/UL reception/transmission on the indicated beam of the target cell. For Rel-18, RAN2 assumed the latency of the mobility procedure is characterized by the terms illustrated in Figure G-1. Figure G-1: Components of Mobility Latency Each component of mobility latency is described in the table below, the values of which are specified in TS 38.133[ NR; Requirements for support of radio resource management ] [13]. Table G-1: Components of Mobility Latency For Rel-18, RAN2 assumed that the latency of the RACH-based and RACH-less LTM procedure is characterized by the terms illustrated in Figure G-2 and Figure G-3. The overall mobility latency of LTM can be largely reduced by early synchronization procedure. Figure G-2: Mobility Latency for RACH-based LTM Figure G-3: Mobility Latency for RACH-less LTM | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | Annex |
5,180 | 4.16.8.4 Final Spending Limit Report Retrieval | This clause describes the signalling flow for the PCF to cancel the subscriptions to status changes for the policy counters available at the CHF. Figure 4.16.8.4.1: Final Spending Limit Report Retrieval 1. The PCF decides that notifications of policy counter status changes are no longer needed. 2. The PCF sends Nchf_SpendingLimitControl_Unsubscribe including the SubscriptionCorrelationId to the CHF to cancel the subscription to notifications of policy counter status changes from the CHF. 3. The CHF removes the PCF's subscription to spending limit reporting and responds to the Nchf_SpendingLimitControl_Unsubscribe service operation to the PCF. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.16.8.4 |
5,181 | 10.5.4.4a Backup bearer capability | The purpose of the backup bearer capability IE is to indicate a requested service to a MS in case a complete description of the bearer service by a bearer capability IE is not available. The backup bearer capability information element is not subject to compatibility checking as described in annex B. The backup bearer capability IE is coded as shown in figure 10.5.87a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and tables 10.5.101a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] to 10.5.101m/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The backup bearer capability is a type 4 information element with a minimum length of 3 octets and a maximum length of 15 octets. Figure 10.5.87a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Backup bearer capability information element NOTE: The coding of the octets of the backup bearer capability IE is not conforming to the coding of the bearer capability IE in ITU-T Recommendation Q.931 [53]. Table 10.5.101a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Backup bearer capability information element Table 10.5.101b/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Backup bearer capability information element Table 10.5.101c/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Backup bearer capability information element Table 10.5.101d/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Backup bearer capability information element Table 10.5.101e/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Backup bearer capability information element Table 10.5.101f/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Backup bearer capability information element Table 10.5.101g/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Backup bearer capability information element Table 10.5.101h/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Backup bearer capability information element Table 10.5.101i/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Backup bearer capability information element Table 10.5.101j/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Backup bearer capability information element Table 10.5.101k/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Backup bearer capability information element Table 10.5.101l/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Backup bearer capability information element Table 10.5.101m/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Backup bearer capability 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.4a |
5,182 | 5.3.13.1b Conditions for initiating SDT | A UE in RRC_INACTIVE initiates the resume procedure for SDT when all of the following conditions are fulfilled: 1> for the resume procedure initiated by the upper layers (i.e. mobile originated case): 2> SIB1 includes sdt-ConfigCommon; and 2> sdt-Config is configured; and 2> all the pending data in UL is mapped to the radio bearers configured for SDT; and 2> for an (e)RedCap UE when (e)RedCap-specific initial downlink BWP includes no CD-SSB, ncd-SSB-RedCapInitialBWP-SDT is configured; and 2> lower layers indicate that conditions for initiating MO-SDT as specified in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3] are fulfilled. 1> for the resume procedure initiated in response to RAN paging (i.e. mobile terminated case): 2> mt-SDT indication was included in the paging message for the UE's stored fullI-RNTI; and 2> lower layers indicate that conditions for initiating MT-SDT as specified in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3] are fulfilled. NOTE: How the UE determines that all pending data in UL is mapped to radio bearers configured for SDT is left to UE implementation. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.13.1b |
5,183 | B.2 Support of rate control of user data B.2.0 General | The rate of user data sent to and from a UE (e.g. a UE using CIoT EPS Optimizations) can be controlled in two different ways: - Serving PLMN rate control - APN rate control Serving PLMN rate control is further described in 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [77]. The APN rate control parameters are a part of the configuration data stored in the GGSN/PGW and is configured on per APN basis. APN rate control allows HPLMN operators on per APN and user to control the amount of user data sent DL and UL. This is done with help of policing user data on a maximum number of user data packets per time unit both DL and UL. APN rate control DL policing is done in the GGSN/PGW or the SCEF and the APN rate control policing UL is done in the UE. The GGSN/PGW or SCEF can also do APN rate control UL policing. For further information on APN rate control UL in the UE, see 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [84]. For further information on APN rate control in the SCEF, see 3GPP TS 29.128[ Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) interfaces for interworking with packet data networks and applications ] [110]. NOTE: Existing AMBR mechanisms are not suitable for such a service since, for radio efficiency and UE battery life reasons, an AMBR of e.g. > 100kbit/s is desirable and such an AMBR translates to a potentially large daily data volume. | 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 | B.2 |
5,184 | 10.12.2 MR-DC with 5GC | The Activity Notification function is used to report user plane activity within SN resources or to report a RAN Paging Failure event to the SN. It can either report inactivity or resumption of activity after inactivity was reported. In MR-DC with 5GC the Activity Reporting is provided from the SN only. The MN may take further actions. RAN Paging Failure Reporting is provided from the MN only. MR-DC with 5GC Activity Notification Figure 10.12.2-1: Support of Activity Notification in MR-DC with 5GC 1. The SN notifies the MN about user data inactivity. 2. The MN decides further actions that impact SN resources (e.g. send UE to RRC_INACTIVE, bearer reconfiguration). In the case shown, MN takes no action. 3. The SN notifies the MN that the (UE or PDU Session or QoS flow) is no longer inactive. MR-DC with 5GC with RRC_INACTIVE – SCG configuration released in SN The Activity Notification function may be used to enable MR-DC with 5GC with RRC_INACTIVE operation. The MN node may decide, after inactivity is reported from the SN and also MN resources show no activity, to send the UE to RRC_INACTIVE. Resumption to RRC_CONNECTED may take place after activity is reported from the SN for SN terminated bearers. Figure 10.12.2-2: Support of Activity Notification in MR-DC with 5GC with RRC_Inactive – SCG configuration released in SN Figure 10.12.2-2 shows how Activity Notification function interacts with NG-RAN functions for RRC_INACTIVE and SN Modification procedures in order to keep the higher layer MR-DC NG-RAN resources established for UEs in RRC_INACTIVE, including NG and Xn interface C-plane, U-plane and bearer contexts established while lower layer MCG and SCG resources are released. NG-RAN memorises the cell group configuration for MCG in order to apply delta signalling at resume, as specified in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [4]. After the UE has transited successfully back to RRC_CONNECTED, lower layer SCG resources are established afterwards by means of RRC Connection Reconfiguration. 1. The SN notifies the MN about user data inactivity for SN terminated bearers. 2. The MN decides to send the UE to RRC_INACTIVE. 3/4. The MN triggers the MN initiated SN Modification procedure, requesting the SN to release lower layers. 5. The UE is sent to RRC_INACTIVE. 6-8. After a period of inactivity, upon activity notification from the SN, the UE returns to RRC_CONNECTED. 8bis. MN decides whether to reactivate the SN terminated bearers. If (e.g. due to UE mobility), MN decides not to reactivate the SN terminated bearers, it initiates the MN initiated SN release procedure and the procedure ends. 9/10. The MN triggers the MN initiated SN Modification procedure to re-establish lower layers. The SN provides configuration data within an SN RRC reconfiguration message. 11-14. The RRC Connection Reconfiguration procedure commences. MR-DC with 5GC with RRC_INACTIVE - SCG configuration suspended in SN The Activity Notification function may be used to enable MR-DC with 5GC with RRC_INACTIVE operation. The MN node may decide, after inactivity is reported from the SN and also MN resources show no activity, to send the UE to RRC_INACTIVE, while keeping the SCG configuration. Resumption to RRC_CONNECTED may take place after activity is reported from the SN for SN terminated bearers. Figure 10.12.2-3: Support of Activity Notification in MR-DC with 5GC with RRC_Inactive - SCG configuration suspended in SN Figure 10.12.2-3 shows how Activity Notification function interacts with NG-RAN functions for RRC_INACTIVE and SN Modification procedures in order to keep the full MR-DC NG-RAN resources established for UEs in RRC_INACTIVE. When the UE transits successfully back to RRC_CONNECTED, lower layer MCG and SCG configurations are restored or reconfigured by means of RRC (Connection) Resume. 1. The SN notifies the MN about user data inactivity for SN terminated bearers. 2. The MN decides to send the UE to RRC_INACTIVE. 3/4. The MN triggers the MN initiated SN Modification procedure, requesting the SN to suspend lower layers. 5. The UE is sent to RRC_INACTIVE. 6-7. After a period of inactivity, the MN receives activity notification from the SN. 8. The MN decides whether to reactivate the SN terminated bearers. If (e.g. due to UE mobility), the MN decides not to reactivate the SN terminated bearers, it initiates the MN initiated SN release procedure, rather than the MN initiated SN modification procedure in steps 9/10. If the MN decides to return the UE to RRC_CONNECTED, the network triggered state transition from RRC_INACTIVE to RRC_CONNECTED commences as described in clause 9.2.2.4.2 in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [3]. 9/10. The MN triggers the MN initiated SN Modification procedure to resume the SCG lower layers. If the SCG configuration needs to be updated, the SN provides the configuration data within an SN RRC reconfiguration message. 11/12. The UE is instructed to resume both the MCG and the SCG. If the SCG configuration is to be updated, the new configuration is provided in the RRC(Connection)Resume message. 13. The MN informs the SN that the UE has completed the reconfiguration procedure successfully, via the SN Reconfiguration Complete message, including the SN RRC response message, if received from the UE. 14. The UE performs synchronisation towards the PSCell of the SN. | 3GPP TS 37.340 | Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 | RAN2 | 3GPP Series : 37 , Multiple radio access technology aspects | 10.12.2 |
5,185 | 5.3.12 UE actions upon PUCCH/SRS release request | Upon receiving a PUCCH release request from lower layers, for all bandwidth parts of an indicated serving cell the UE shall: 1> release PUCCH-CSI-Resources configured in CSI-ReportConfig; 1> release SchedulingRequestResourceConfig instances configured in PUCCH-Config. Upon receiving an SRS release request from lower layers, for all bandwidth parts of an indicated serving cell the UE shall: 1> release SRS-Resource instances configured in SRS-Config. Upon receiving a positioning SRS configuration for RRC_INACTIVE release request from lower layers, the UE shall: 1> release the configured srs-PosRRC-Inactive. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.12 |
5,186 | 5.5.4.6 Event A5 (SpCell becomes worse than threshold1 and neighbour becomes better than threshold2) | The UE shall: 1> consider the entering condition for this event to be satisfied when both condition A5-1 and condition A5-2, as specified below, are fulfilled; 1> consider the leaving condition for this event to be satisfied when condition A5-3 or condition A5-4, i.e. at least one of the two, as specified below, is fulfilled; 1> use the SpCell for Mp. NOTE 1: The parameters of the reference signal(s) of the cell(s) that triggers the event are indicated in the measObjectNR associated to the event which may be different from the measObjectNR of the NR SpCell. Inequality A5-1 (Entering condition 1) Mp + Hys < Thresh1 Inequality A5-2 (Entering condition 2) Mn + Ofn + Ocn – Hys > Thresh2 Inequality A5-3 (Leaving condition 1) Mp – Hys > Thresh1 Inequality A5-4 (Leaving condition 2) Mn + Ofn + Ocn + Hys < Thresh2 The variables in the formula are defined as follows: Mp is the measurement result of the NR SpCell, not taking into account any offsets. Mn is the measurement result of the neighbouring cell, not taking into account any offsets. Ofn is the measurement object specific offset of the neighbour cell (i.e. offsetMO as defined within measObjectNR corresponding to the neighbour cell). Ocn is the cell specific offset of the neighbour cell (i.e. cellIndividualOffset as defined within measObjectNR corresponding to the neighbour cell, or cellIndividualOffset as defined within reportConfigNR), and set to zero if not configured for the neighbour cell. Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigNR for this event). Thresh1 is the threshold parameter for this event (i.e. a5-Threshold1 as defined within reportConfigNR for this event). Thresh2 is the threshold parameter for this event (i.e. a5-Threshold2 as defined within reportConfigNR for this event). Mn, Mp are expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR. Ofn, Ocn, Hys are expressed in dB. Thresh1is expressed in the same unit as Mp. Thresh2 is expressed in the same unit as Mn. NOTE 2: The definition of Event A5 also applies to CondEvent A5. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.5.4.6 |
5,187 | 4.14.2.3 Number of attempted WLAN releases from the LWIP WLAN mobility set | a) This measurement provides the number of attempted WLAN releases from the LWIP WLAN mobility set. b) CC c) On transmission of RRCConnectionReconfiguration message which includes the wlan-ToReleaseList in the lwip-MobilityConfig of lwip-Configuration information element (see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]) by the eNB. d) An integer value e) LWI.LwipWlanRelAtt f) WLANMobilitySet g) Valid for packet switched traffic h) EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.14.2.3 |
5,188 | 4.1.3.1 GMM states in the MS | In this subclause, the possible GMM states are described of a GMM entity in the mobile station. subclause 4.1.3.1.1 summarises the main states of a GMM entity, see figure 4.1b of the present document. The substates that have been defined are described in subclause 4.1.3.1.2 and subclause 4.1.3.1.3. However, it should be noted that this subclause does not include a description of the detailed behaviour of the MS in the single states and does not cover abnormal cases. Thus, figure 4.1b of the present document is rather intended to give an overview of the state transitions than to be a complete state transition diagram. A detailed description of the behaviour of the MS is given in subclause 4.2. Especially, with respect to the behaviour of the MS in abnormal cases it is referred to subclause 4.7. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.1.3.1 |
5,189 | 10.5.4.26 Alerting Pattern $(NIA)$ | The purpose of the Alerting Pattern information element is to allow the network to convey information related to the alert to be used by the MS (see 3GPP TS 22.101[ Service aspects; Service principles ] [8]). The Alerting Pattern information element is coded as shown in figure 10.5.115/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.132/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The Alerting Pattern IE is a type 4 information element with 3 octet length. Figure 10.5.115/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Alerting Pattern information element Table 10.5.132/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Alerting Pattern information element Alerting pattern 1, 2 and 3 indicate alerting levels 0, 1 and 2. Alerting pattern 5 to 9 indicate alerting categories 1 to 5 | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.4.26 |
5,190 | 4.4.4.2 Integrity checking of NAS signalling messages in the UE | Except the messages listed below, no NAS signalling messages shall be processed by the receiving 5GMM entity in the UE or forwarded to the 5GSM entity, unless the network has established secure exchange of 5GS NAS messages for the NAS signalling connection: a) IDENTITY REQUEST (if requested identification parameter is SUCI); b) AUTHENTICATION REQUEST; c) AUTHENTICATION RESULT; d) AUTHENTICATION REJECT; e) REGISTRATION REJECT (if the 5GMM cause is not #76, #78, #81 or #82); f) DEREGISTRATION ACCEPT (for non switch off); and g) SERVICE REJECT (if the 5GMM cause is not #76 or #78). NOTE: These messages are accepted by the UE without integrity protection, as in certain situations they are sent by the network before security can be activated. Integrity protection is never applied directly to 5GSM messages, but to the 5GMM message in which the 5GSM message is included. Once the secure exchange of NAS messages has been established, the receiving 5GMM entity in the UE shall not process any NAS signalling messages unless they have been successfully integrity checked by the NAS. If NAS signalling messages, having not successfully passed the integrity check, are received, then the NAS in the UE shall discard that message. The processing of the SECURITY MODE COMMAND message that has not successfully passed the integrity check is specified in subclause 5.4.2.5. If any NAS signalling message is received as not integrity protected even though the secure exchange of NAS messages has been established by the network, then the NAS shall discard this message. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.4.4.2 |
5,191 | 5.6.1 Service request procedure 5.6.1.1 General | The purpose of the service request procedure is to change the 5GMM mode from 5GMM-IDLE to 5GMM-CONNECTED mode. If the UE is not using 5GS services with control plane CIoT 5GS optimization, this procedure is used to request the establishment of user-plane resources for PDU sessions which are established without user-plane resources. In latter case, the 5GMM mode can be the 5GMM-IDLE mode or the 5GMM-CONNECTED mode if the UE requires to establish user-plane resources for PDU sessions. If the UE is using 5GS services with control plane CIoT 5GS optimization, this procedure can be used for UE initiated transfer of user data via the control plane from 5GMM-IDLE mode. NOTE 1: The lower layer indicates when the user-plane resources for PDU sessions are successfully established or released. This procedure is used when: - the network has downlink signalling pending over 3GPP access and the UE is in 5GMM-IDLE mode over 3GPP access; - the network has downlink signalling pending over non-3GPP access, the UE is in 5GMM-IDLE mode over non-3GPP access and in 5GMM-IDLE or 5GMM-CONNECTED mode over 3GPP access; - the UE has uplink signalling pending over 3GPP access and the UE is in 5GMM-IDLE mode over 3GPP access; - the network has downlink user data pending over 3GPP access and the UE is in 5GMM-IDLE mode over 3GPP access; - the network has downlink user data pending over non-3GPP access, the UE is in 5GMM-IDLE mode over non-3GPP access and in 5GMM-IDLE or 5GMM-CONNECTED mode over 3GPP access; - the UE has user data pending over 3GPP access and the UE is in 5GMM-IDLE or 5GMM-CONNECTED mode over 3GPP access; - the UE has user data pending over non-3GPP access and the UE is in 5GMM-CONNECTED mode over non-3GPP access; - the UE in 5GMM-IDLE mode over non-3GPP access, receives an indication from the lower layers of non-3GPP access, that the access stratum connection is established between the UE and the network, if T3346 is not running; - the UE in 5GMM-IDLE or 5GMM-CONNECTED mode over 3GPP access receives a request from the upper layers to perform emergency services fallback and performs emergency services fallback as specified in subclause 4.13.4.2 of 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9]; - the UE has to request resources for V2X communication over PC5; - the UE has to request resources for 5G ProSe direct discovery over PC5 or 5G ProSe direct communication over PC5; - the UE has to request resources for A2X communication over PC5; NOTE 2: The purpose for the UE to request resources for V2X communication over PC5, 5G ProSe direct discovery over PC5 and 5G ProSe direct communication over PC5 can be to perform the ranging and sidelink positioning service over PC5. - the MUSIM UE in 5GMM-IDLE mode requests the network to remove the paging restriction; - the MUSIM UE requests the release of the NAS signalling connection or rejects the paging request from the network; or - the UE supporting the reconnection to the network due to RAN timing synchronization status change receives an indication of a change in the RAN timing synchronization status. This procedure shall not be used for: a) initiating user data transfer or CIoT user data via the control plane; or b) PDU session management related signalling other than for performing UE-requested PDU session release procedure related to a PDU session for LADN or for performing the UE-requested PDU session modification procedure to indicate a change of 3GPP PS data off UE status; when the UE is located outside the LADN service area. In NB-N1 mode, this procedure shall not be used to request the establishment of user-plane resources: a) for a number of PDU sessions that exceeds the UE' s maximum number of supported user-plane resources if there is currently: 1) no user-plane resources established for the UE; 2) user-plane resources established for: i) one PDU session and the Multiple user-plane resources support bit was set to "Multiple user-plane resources not supported" in the 5GMM capability IE; or ii) two PDU sessions and the Multiple user-plane resources support bit was set to "Multiple user-plane resources supported" in the 5GMM capability IE; or b) for additional PDU sessions, if the number of PDU sessions for which user-plane resources are currently established is equal to the UE's maximum number of supported user-plane resources. The service request procedure is initiated by the UE, however, it can be triggered by the network by means of: - the paging procedure (see subclause 5.6.2) for the transfer of downlink signalling or user data pending over 3GPP access to a UE in 5GMM-IDLE mode over 3GPP access; - the paging procedure (see subclause 5.6.2) for the transfer of downlink signalling or user data pending over non-3GPP access to a UE in 5GMM-IDLE mode over 3GPP access and in 5GMM-IDLE mode over non-3GPP access; - the notification procedure (see subclause 5.6.3) for the transfer of downlink signalling or user data pending over non-3GPP access to a UE in 5GMM-CONNECTED mode over 3GPP access and in 5GMM-IDLE mode over non-3GPP access; or - the notification procedure (see subclause 5.6.3) for the transfer of downlink signalling or user data pending over 3GPP access to a UE in 5GMM-IDLE mode over 3GPP access and in 5GMM-CONNECTED mode over non-3GPP access. NOTE 3: In case the UE is in 5GMM-IDLE mode over 3GPP access and in 5GMM-CONNECTED mode over non-3GPP access and downlink signalling or user data pending over 3GPP access needs to be transferred, the AMF can trigger either the notification procedure or the paging procedure based on implementation. The UE shall invoke the service request procedure when: a) the UE, in 5GMM-IDLE mode over 3GPP access, receives a paging request from the network; NOTE 4: As an implementation option, the MUSIM UE is allowed to not invoke service request to respond to paging based on the information available in the paging message, e.g. voice service indication. b) the UE, in 5GMM-CONNECTED mode over 3GPP access, receives a notification from the network with access type indicating non-3GPP access; c) the UE, in 5GMM-IDLE mode over 3GPP access, has uplink signalling pending (except in case i); d) the UE, in 5GMM-IDLE mode over 3GPP access, has uplink user data pending (except in case j); e) the UE, in 5GMM-CONNECTED mode or in 5GMM-CONNECTED mode with RRC inactive indication, has user data pending due to no user-plane resources established for PDU session(s) used for user data transport; f) the UE in 5GMM-IDLE mode over non-3GPP access, with T3346 not active or upon expiry of T3346, receives or has already received an indication from the lower layers of non-3GPP access, that the access stratum connection is established between the UE and the network; g) the UE, in 5GMM-IDLE mode over 3GPP access, receives a notification from the network with access type indicating 3GPP access when the UE is in 5GMM-CONNECTED mode over non-3GPP access; h) the UE, in 5GMM-IDLE, 5GMM-CONNECTED mode over 3GPP access, or 5GMM-CONNECTED mode with RRC inactive indication, receives a request from the upper layers to perform emergency services fallback and performs emergency services fallback as specified in subclause 4.13.4.2 of 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9]; i) the UE, in 5GMM-CONNECTED mode over 3GPP access or in 5GMM-CONNECTED mode with RRC inactive indication, receives a fallback indication from the lower layers (see subclauses 5.3.1.2 and 5.3.1.4) and the UE has a pending NAS procedure other than a registration, service request, or de-registration procedure; the UE, in 5GMM-CONNECTED mode over 3GPP access, receives a "RRC Connection failure" from the lower layers and the UE has a pending NAS procedure other than a registration, service request, or de-registration procedure; j) the UE, in 5GMM-CONNECTED mode over 3GPP access or in 5GMM-CONNECTED mode with RRC inactive indication, receives a fallback indication from the lower layers (see subclauses 5.3.1.2 and 5.3.1.4) and the UE has pending uplink user data for PDU session(s) with user-plane resources already established but no pending NAS procedure; the UE, in 5GMM-CONNECTED mode over 3GPP access, receives a "RRC Connection failure" indication from the lower layers and the UE has pending uplink user data for PDU session(s) with user-plane resources already established but no pending NAS procedure; k) the UE, in 5GMM-CONNECTED mode and has a NAS signalling connection only, is using 5GS services with control plane CIoT 5GS optimization and has pending user data to be sent via user-plane resources; l) the UE in 5GMM-IDLE mode over 3GPP access has to request resources for V2X communication over PC5 (see 3GPP TS 23.287[ Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services ] [6C]); la) the UE in 5GMM-IDLE mode over 3GPP access has to request resources for A2X communication over PC5 (see 3GPP TS 23.256[ Support of Uncrewed Aerial Systems (UAS) connectivity, identification and tracking; Stage 2 ] [6AB]); m) the network supports the paging restriction, and the MUSIM UE in 5GMM-IDLE mode is requesting the network to remove the paging restriction; n) the UE in 5GMM-IDLE mode over 3GPP access - has to request resources for 5G ProSe direct discovery over PC5 or 5G ProSe direct communication over PC5 (see 3GPP TS 23.304[ Proximity based Services (ProSe) in the 5G System (5GS) ] [6E]); or - acts as a 5G ProSe layer-2 UE-to-network relay UE and receives a trigger from lower layers to establish the NAS signalling connection (see 3GPP TS 23.304[ Proximity based Services (ProSe) in the 5G System (5GS) ] [6E]); o) the network supports the N1 NAS signalling connection release, the MUSIM UE, - is in 5GMM-CONNECTED mode, requests the network to release the NAS signalling connection and, if the network supports the paging restriction, optionally includes paging restriction; - is in 5GMM-CONNECTED mode with RRC inactive indication, requests the network to release the NAS signalling connection and, if the network supports the paging restriction, optionally includes paging restriction; or - is in 5GMM-CONNECTED mode with RRC inactive indication, rejects the RAN paging, requests the network to release the NAS signalling connection and, if the network supports the paging restriction, optionally includes paging restriction; p) the network supports the reject paging request, the MUSIM UE in 5GMM-IDLE mode when responding to paging rejects the paging request from the network, requests the network to release the NAS signalling connection and, if the network supports the paging restriction, optionally includes paging restriction; or q) the UE supporting the reconnection to the network due to RAN timing synchronization status change has been requested to reconnect to the network upon receiving an indication of a change in the RAN timing synchronization status (see subclauses 5.4.4.2, 5.5.1.2.4, and 5.5.1.3.4) and the UE in 5GMM-IDLE mode receives an indication of a change in the RAN timing synchronization status; If one of the above criteria to invoke the service request procedure is fulfilled, then the service request procedure shall only be initiated by the UE when the following conditions are fulfilled: - its 5GS update status is 5U1 UPDATED, and the TAI of the current serving cell is included in the TAI list; and - no 5GMM specific procedure is ongoing. The UE shall not invoke the service request procedure when the UE is in the state 5GMM-SERVICE-REQUEST-INITIATED. The MUSIM UE shall not initiate service request procedure for requesting the network to release the N1 NAS signalling connection if the UE is registered for emergency services or if the UE has an emergency PDU session established. To enable the emergency call back, the UE shall not initiate service request procedure for requesting the network to release the NAS signalling connection for a UE implementation-specific duration of time after the completion of the emergency services. The UE supporting S-NSSAI location validity information shall not invoke the service request procedure to establish user-plane resources for PDU sessions associated to an S-NSSAI when the UE is not in the NS-AoS of the S-NSSAI. Figure 5.6.1.1.1: Service Request procedure (Part 1) Figure 5.6.1.1.2: Service Request procedure (Part 2) A service request attempt counter is used to limit the number of service request attempts and no response from the network. The service request attempt counter shall be incremented as specified in subclause 5.6.1.7. The service request attempt counter shall be reset when: - a registration procedure for mobility and periodic registration update is successfully completed; - a service request procedure is successfully completed; - a service request procedure is rejected as specified in subclause 5.6.1.5 or subclause 5.3.20; or - the UE moves to 5GMM-DEREGISTERED state. | 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 |
5,192 | 6.19.1 Description | The 5G system will support the concept of "network slices" where different NG-RANs potentially are connected to network slices of different SSTs. A 5G UE can provide assistance information (e.g. SST) to enable the network to select one or more network slices. A 5G system is foreseen to support one or more SSTs, but possibly not all existing SSTs. A 5G network operator controls and is responsible for what SSTs that should be available to a specific UE and subscription combination, based on associated subscription type, network operator policies, network capabilities and UE capabilities. The network operator can populate the Operator Controlled PLMN Selector list with associated access technology identifiers, stored in the 5G UE, with the PLMN/RAT combinations enabling access to the SSTs that are available to the 5G UE with associated subscription. The UE uses the list of PLMN/RAT combinations for PLMN selection, if available, typically during roaming situations. In non-roaming situations, the UE and subscription combination typically matches the HPLMN/EHPLMN capabilities and policies, from a SST perspective. That is, a 5G UE accessing its HPLMN/EHPLMN should be able to access SSTs according to UE capabilities and the related subscription. Optionally, a 5G system supports, subject to operator policies, a User Controlled PLMN Selector list that enables the 5G UE user to specify preferred PLMNs with associated access technology identifier in priority order. The user can obtain information about suitable PLMN/RAT combination that would support services preferred by the user. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.19.1 |
5,193 | 5.6.3.3 Notification procedure completion | Upon reception of SERVICE REQUEST message, CONTROL PLANE SERVICE REQUEST message or REGISTRATION REQUEST message, the AMF shall stop timer T3565 and proceed service request procedure as specified in subclauses 5.6.3.1 or registration procedure for mobility and periodic registration update as specified in subclauses 5.5.1.3. If no user-plane resources of PDU session(s) need to be re-established, the AMF should notify the SMF that the UE was reachable but did not accept to re-establish the user-plane resources of PDU session(s). When the 5GMM entity in the AMF receives an indication from the lower layer that it has received the NGAP UE context resume request message as specified in 3GPP TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [31], the AMF shall stop timer T3565. Upon reception of NOTIFICATION RESPONSE message over non-3GPP access, the AMF shall stop timer T3565 and should notify the SMF that the UE is unreachable. If the NOTIFICATION RESPONSE message includes the PDU session status information element, then: a) for single access PDU sessions, the AMF shall: 1) perform a local release of all those PDU sessions which are not in 5GSM state PDU SESSION INACTIVE on the AMF side associated with 3GPP access, but are indicated by the UE in the PDU session status information element in the NOTIFICATION RESPONSE message as being in 5GSM state PDU SESSION INACTIVE; and 2) shall request the SMF to perform a local release of all those PDU sessions associated with 3GPP access. 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; and b) For MA PDU sessions, the AMF shall: 1) for MA PDU sessions having user plane resources established only on the 3GPP access in the AMF side, but are indicated by the UE in the PDU session status information element in the NOTIFICATION RESPONSE message as no user plane resources established on the 3GPP access: i) perform a local release of all those MA PDU sessions; and ii) request the SMF to perform a local release of all those MA PDU sessions. If the MA PDU session is associated with one or more multicast MBS sessions, the SMF shall consider the UE as removed from the associated multicast MBS sessions; and 2) for MA PDU sessions having user plane resources established on both accesses in the AMF side, but are indicated by the UE in the PDU session status information element in the NOTIFICATION RESPONSE message as no user plane resources established on the 3GPP access: i) perform a local release of 3GPP access user plane resources of all those MA PDU sessions; and ii) request the SMF to perform a local release of 3GPP access user plane resources of all those MA PDU sessions. If the MA PDU session is associated with one or more MBS sessions, the SMF shall consider the UE as removed from the associated MBS sessions. | 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.3 |
5,194 | 5.5.7.2 Start DTMF response by the network | Upon receiving the START DTMF message the network shall either: - convert the received digit into a DTMF tone which is applied toward the remote user, or - send the DTMF digit as an out-of-band message (see 3GPP TS 23.205[ Bearer-independent circuit-switched core network; Stage 2 ] [96]) and return a START DTMF ACKNOWLEDGE message to the mobile station. This acknowledgement may be used in the mobile station to generate an indication as a feedback for a successful transmission. If the network cannot accept the START DTMF message a START DTMF REJECT message will be sent to the mobile station. Upon receipt of a START DTMF ACK message or a START DTMF REJECT message, the MS shall stop timer T336. | 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.5.7.2 |
5,195 | 5.2.2.3.1 Acquisition of MIB and SIB1 | The UE shall: 1> apply the specified BCCH configuration defined in 9.1.1.1; 1> if the UE is in RRC_IDLE or in RRC_INACTIVE; or 1> if the UE is in RRC_CONNECTED while T311 is running: 2> acquire the MIB, which is scheduled as specified in TS 38.213[ NR; Physical layer procedures for control ] [13]; 2> if the UE is unable to acquire the MIB; 3> perform the actions as specified in clause 5.2.2.5; 2> else: 3> perform the actions specified in clause 5.2.2.4.1. 1> if the UE is in RRC_CONNECTED with an active BWP with common search space configured by searchSpaceSIB1 and pagingSearchSpace and has received an indication about change of system information; or 1> if the UE is in RRC_CONNECTED with an active BWP with common search space configured by searchSpaceSIB1 and the UE has not stored a valid version of a SIB or posSIB, in accordance with clause 5.2.2.2.1, of one or several required SIB(s) or posSIB(s) in accordance with clause 5.2.2.1, and, UE has not acquired SIB1 in current modification period; or 1> if the UE is in RRC_CONNECTED with an active BWP with common search space configured by searchSpaceSIB1, and, the UE has not stored a valid version of a SIB or posSIB, in accordance with clause 5.2.2.2.1, of one or several required SIB(s) or posSIB(s) in accordance with clause 5.2.2.1, and, si-BroadcastStatus for the required SIB(s) or posSI-BroadcastStatus for the required posSIB(s) is set to notBroadcasting in acquired SIB1 in current modification period; or 1> if the UE is in RRC_IDLE or in RRC_INACTIVE; or 1> if the UE is in RRC_CONNECTED while T311 is running: 2> if ssb-SubcarrierOffset indicates SIB1 is transmitted in the cell (TS 38.213[ NR; Physical layer procedures for control ] [13]) and if SIB1 acquisition is required for the UE: 3> acquire the SIB1, which is scheduled as specified in TS 38.213[ NR; Physical layer procedures for control ] [13]; 3> if the UE is unable to acquire the SIB1: 4> perform the actions as specified in clause 5.2.2.5; 3> else: 4> upon acquiring SIB1, perform the actions specified in clause 5.2.2.4.2. 2> else if SIB1 acquisition is required for the UE and ssb-SubcarrierOffset indicates that SIB1 is not scheduled in the cell: 3> perform the actions as specified in clause 5.2.2.5. NOTE 1: The UE in RRC_CONNECTED is only required to acquire broadcasted SIB1 and MBS broadcast if the UE can acquire it without disrupting unicast or MBS multicast data reception, i.e., the broadcast and unicast/MBS multicast beams are quasi co-located. The UE in RRC_INACTIVE state while SDT procedure is ongoing, is only required to acquire broadcasted SIB1 and MIB if the UE can acquire them without disrupting unicast data reception, i.e. the broadcast and unicast beams are quasi co-located. NOTE 2: UE in RRC_INACTIVE that does not support inactiveStateNTN-r17 enters RRC_IDLE upon cell reselection between TN cell and NTN cell, and initiates the NAS signalling connection recovery (see TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [23]). | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.2.2.3.1 |
5,196 | 28.3.2.7 AMF Set FQDN | An AMF Set within an operator's PLMN is identified by its AMF Set ID, AMF Region ID, MNC and MCC. A subdomain name shall be derived from the MNC and MCC by adding the label "amfset" to the beginning of the Home Network Realm/Domain (see clause 28.2). The AMF Set FQDN shall be constructed as follows: set<AMF Set Id>.region<AMF Region Id>.amfset.5gc.mnc<MNC>.mcc<MCC>.3gppnetwork.org where - <MNC> = 3 digits - <MCC> = 3 digits If there are only 2 significant digits in the MNC, one "0" digit shall be inserted at the left side to fill the 3 digits coding of MNC in the AMF Set FQDN. - <AMF Set Id> and <AMF Region Id> are the hexadecimal strings of the AMF Set ID and AMF Region ID. If there are less than 2 significant digits in <AMF Region Id>, "0" digit(s) shall be inserted at the left side to fill the 2 digits coding. If there are less than 3 significant digits in <AMF Set Id>, "0" digit(s) shall be inserted at the left side to fill the 3 digits coding. As an example, the AMF Set FQDN for the AMF Set 1, AMF Region 48 (hexadecimal), MCC 345 and MNC 12 is coded as: "set001.region48.amfset.5gc.mnc012.mcc345.3gppnetwork.org" An AMF Set within an operator's Stand-alone Non-Public Network (SNPN) shall be identified by its AMF Set ID, AMF Region ID and by either its Network Identifier (NID), MNC and MCC or an SNPN domain name pre-configured in the NF. The AMF Set FQDN shall be constructed as follows: set<AMF Set Id>.region<AMF Region Id>.amfset.5gc.nid<NID>.mnc<MNC>.mcc<MCC>.3gppnetwork.org or set<AMF Set Id>.region<AMF Region Id>.amfset.<SNPN domain name> where - <MNC> and <MCC> shall be encoded as specified above; - NID shall be encoded as hexadecimal digits as specified in clause 12.7; - <SNPN domain name> is a domain name chosen by the SNPN operator. As an example, the AMF Set FQDN for the AMF Set 1, AMF Region 48 (hexadecimal), NID 000007ed9d5 (hexadecimal), MCC 345 and MNC 12 is coded as: "set001.region48.amfset.5gc.nid000007ed9d5. mnc012.mcc345.3gppnetwork.org" | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 28.3.2.7 |
5,197 | 4.3.1.5.2 Successful outgoing handovers with DRX | This measurement provides the number of successful outgoing handovers, when DRX is used (for DRX see [12]). CC. Receipt of a RRC message RRCConnectionReconfigurationComplete sent from the UE to the target (=source) eNB, indicating a successful outgoing intra-eNB handover when DRX is used (see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]), or receipt at the source eNB of UE CONTEXT RELEASE [10] over the X2 from the target eNB following a successful handover when DRX is used, or if handover is performed via S1, receipt of UE CONTEXT RELEASE COMMAND[9] at the source eNB following a successful handover when DRX is used. A single integer value. HO.DrxOutSucc EUtranCellFDD EUtranCellTDD Valid for packet switched traffic EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.3.1.5.2 |
5,198 | 5.4.4.2a UE Radio Capability Match Request | If the AMF requires more information on the UE radio capabilities support to be able to set the IMS voice over PS Session Supported Indication (see clause 5.16.3), then the AMF may send a UE Radio Capability Match Request message to the NG-RAN. This procedure is typically used during the Registration Procedure or when AMF has not received the Voice Support Match Indicator (as part of the 5GMM Context). NOTE: During the Registration Procedure, if the AMF does not already have the UEs radio capabilities, and if the RAT where the UE is requires the establishment of AN security context prior to retrieval of radio capabilities, the AMF needs to initiate "Initial Context Setup" procedure as defined in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [34] to provide the 5G-AN with security context, before sending a UE Radio Capability Match Request message. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.4.4.2a |
5,199 | 9.5.4.1 FDD | For the parameters specified in Table 9.5.4.1-1, the minimum performance requirement in Table 9.5.4.1-2 is defined as a) The ratio of the throughput obtained when transmitting based on UE reported RI and that obtained when transmitting with fixed rank 1 shall be 1; b) The ratio of the throughput obtained when transmitting based on UE reported RI and that obtained when transmitting with fixed rank 2 shall be ≥ ; In Table 9.5.4.1-1, Cell 1 is the serving cell, and Cell 2 and Cell 3 are the aggresso cells. The downlink physical channel setup for Cell 1 is according to Annex C.3.2 and for Cell 2 and Cell 3 is according to Annex C.3.3, respectively. The CRS assistance information [7] including Cell 2 and Cell 3 is provided. Table 9.5.4.1-1: RI Test (FDD) Table 9.5.4.1-2: Minimum requirement (FDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.5.4.1 |
5,200 | 5.6.4.4 Abnormal cases in the UE | The following abnormal case can be identified: a) Timer T3346 is running The UE shall not send an UPLINK GENERIC NAS TRANSPORT message unless: the UE is a UE configured to use AC11 – 15 in selected PLMN; - the UE has a PDN connection for emergency bearer services established; or the UE is configured for dual priority and has a PDN connection established without low access priority but the timer T3346 was started in response to NAS signalling request with low access priority. The UPLINK GENERIC NAS TRANSPORT message can be sent, if still necessary, when timer T3346 expires or is stopped. b) Timer T3447 is running The UE shall not send an UPLINK GENERIC NAS TRANSPORT message when the UE is in EMM-CONNECTED mode, unless: - the UE is a UE configured to use AC11 – 15 in the selected PLMN; - the UE has a PDN connection for emergency bearer services established; or - a network initiated signalling message has been received. The UPLINK GENERIC NAS TRANSPORT message can be sent, if still necessary, when timer T3447 expires. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.6.4.4 |
Subsets and Splits
No saved queries yet
Save your SQL queries to embed, download, and access them later. Queries will appear here once saved.