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
⌀ |
|---|---|---|---|---|---|---|---|
1,701 | 6.2.4 IP address allocation 6.2.4.1 General | This clause specifies IP address allocation for the PDU session. In this release of specification, PDU session can be initiated with one IP version, i.e. IPv4 PDU session type or IPv6 PDU session type, or with both IP versions, i.e. IPv4v6 PDU session type. IP address allocation to the UE shall be performed by SMF based on one or both the selected IP versions and operator policies. If IPv4 PDU session type is selected, an IPv4 address is allocated to the UE. If IPv6 PDU session type is selected, an IPv6 prefix except when the SMF acts according to subclause 6.2.4.3, and an interface identifier for the IPv6 link local address are allocated to the UE. If IPv4v6 PDU session type is selected, an IPv4 address, an IPv6 prefix except when the SMF acts according to subclause 6.2.4.3 or 6.2.4.4, and an interface identifier for the IPv6 link local address are allocated to the UE. If IPv6 or IPv4v6 PDU session type is selected in a PDU session established by the W-AGF acting on behalf of the FN-RG and the PDU SESSION ESTABLISHMENT REQUEST message contains the Suggested interface identifier IE, the SMF shall allocate to the UE the interface identifier for the IPv6 link local address indicated in the Suggested interface identifier IE. For IPv4 PDU session type and for IPv4v6 PDU session type, the UE: a) shall obtain an IPv4 address via: 1) NAS signalling as specified in subclause 6.2.4.2; or 2) DHCPv4 as specified in IETF RFC 2131 [33E]; and b) may obtain IPv4 configuration parameters (e.g. DNS server address) via DHCPv4 as specified in IETF RFC 2132 [33F] or may receive IPv4 configuration parameters (e.g. DNS server address) as specified in subclause 6.4.1 and subclause 6.3.2. For IPv6 PDU session type and for IPv4v6 PDU session type, the UE: a) shall build an IPv6 link local address based on the allocated interface identifier for the IPv6 link local address; b) shall obtain /64 IPv6 prefix via IPv6 stateless address autoconfiguration as specified in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8] and IETF RFC 4862 [39], except when the 5G-RG or the W-AGF act according to subclause 6.2.4.3; c) may obtain IPv6 configuration parameters via stateless DHCPv6 as specified in IETF RFC 8415 [33D], except when the 5G-RG or the W-AGF act according to subclause 6.2.4.3, may receive IPv6 configuration parameters (e.g. DNS server address) as specified in subclause 6.4.1 and subclause 6.3.2, or may receive DNS server IPv6 addresses in a Router Advertisement Message as specified in IETF RFC 4861 [38B] with recursive DNS server option as specified in IETF RFC 8106 [52];and d) may obtain an additional IPv6 prefix for a PDU session by IPv6 prefix delegation via DHCPv6 as specified in subclause 6.2.4.2a. | 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 |
1,702 | 5.30.2.4 Network selection in SNPN access mode 5.30.2.4.1 General | An SNPN-enabled UE supports the SNPN access mode. When the UE is set to operate in SNPN access mode the UE selects and registers with SNPNs over Uu as described in clause 5.30.2.4. Network selection in SNPN access mode for access to SNPN services via Untrusted non-3GPP access, Trusted non-3GPP access and Wireline access is specified in clause 5.30.2.12, clause 5.30.2.13 and clause 5.30.2.14 respectively. Access network selection in SNPN access mode for 5G NSWO is specified in clause 6.3.12b. Emergency services are supported in SNPN access mode over Uu as defined in clause 5.16.4.1. Support for Emergency in SNPN access mode via Untrusted non-3GPP access is specified in clause 5.30.2.12. If a UE is not set to operate in SNPN access mode, even if it is SNPN-enabled, the UE does not select and register with SNPNs. A UE not set to operate in SNPN access mode performs PLMN selection procedures as defined in clause 4.4 of TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [17]. For a UE capable of simultaneously connecting to an SNPN and a PLMN, the setting for operation in SNPN access mode is applied to each of the Uu/Yt/NWu interfaces independently. Clause D.4 provides more details. An SNPN-enabled UE that supports access to an SNPN using credentials from a Credentials Holder and that is equipped with a PLMN subscription needs to first enter SNPN access mode to be able to select SNPNs. Once the UE has entered SNPN access mode, SNPN selection is performed as described in clause 5.30.2.4. Once an SNPN has been selected the UE attempts registration in the SNPN using the PLMN credentials. NOTE 1: Details of activation and deactivation of SNPN access mode are up to UE implementation. When a UE is set to operate in SNPN access mode the UE does not perform normal PLMN selection procedures as defined in clause 4.4 of TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [17]. UEs operating in SNPN access mode read the information described in clause 5.30.2.2 from the broadcast system information and take them into account during network selection. Furthermore, if the UE supports access to an SNPN providing access for Localized Services, and the end user enables to access the Localized Services the UE may select an SNPN providing access for Localized Services. NOTE 2: Details of how the user enables/disables access to Localized Services are up to UE implementation. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.30.2.4 |
1,703 | 4.13.3.9 Unsuccessful Mobile terminating SMS delivery re-attempt | The procedure of Unsuccessful Mobile terminating SMS delivery re-attempt is defined as follows: - For SMS delivery, the SMSF and the UDM support the SMSF and UDM role as specified in TS 23.040[ Technical realization of the Short Message Service (SMS) ] [7]. - If the UE is registered over both 3GPP access and non-3GPP access in the same AMF (i.e. the UE is registered in the same PLMN for both Access Types): - if the MT-SMS delivery over one Access Type has failed, the AMF, based on operator local policy, may re-attempt the MT-SMS delivery over the other Access Type before indicating failure to SMSF; - if the MT-SMS delivery on both Access Types has failed, the AMF shall inform the SMSF immediately. - If the AMF informs the SMSF that it cannot deliver the MT-SMS to the UE (including the cases that UE applies power saving enhancement as described in step 4 of clause 4.13.3.6), the SMSF sends a failure report to the first SMS-GMSC (which can be co-located with IP-SM-GW or SMS Router) as defined in TS 23.040[ Technical realization of the Short Message Service (SMS) ] [7] or TS 23.540[ 5G System: Technical realization of Service Based Short Message Service; Stage 2 ] [84]. If the SMS-GMSC has more than one entity for SMS transport towards the UE, then upon receiving MT-SMS failure report, the SMS-GMSC, based on operator local policy, may re-attempt the MT-SMS delivery via the other entity. - After the first SMS-GMSC informs the UDM/HSS that the UE is not able to receive MT-SMS, the UDM shall set the URRP-AMF flag and store the SC address in the MWD list as defined in TS 23.040[ Technical realization of the Short Message Service (SMS) ] [7] or TS 23.540[ 5G System: Technical realization of Service Based Short Message Service; Stage 2 ] [84]. - If the UE is registered in an AMF and the UDM has not subscribed to UE Reachability Notification in the AMF yet, the UDM immediately initiates a subscription procedure as specified in clause 4.2.5.2. - When the AMF detects UE activities, it notifies UDM with UE Activity Notification as described in clause 4.2.5.3. If the UE is registered in an SMSF, the UDM clears its URRP-AMF flag and the UDM/HSS clears the MWD list and alerts related SCs to retry MT-SMS delivery. Otherwise, if the UE is not registered in an SMSF, the UDM clears its URRP-AMF flag but the UDM/HSS keeps the MWD list to notify the SC upon subsequent SMSF registration for the UE. - When the SMS-GMSC requests routing information from UDM/HSS for a UE not registered in 5GC, or for a registered UE which has not been yet registered for SMS service, the UDM/HSS responds to the SMS-GMSC that the UE is absent, stores the SC address in the MWD list (if not yet stored) and indicates that to the SC as defined in TS 23.040[ Technical realization of the Short Message Service (SMS) ] [7] or TS 23.540[ 5G System: Technical realization of Service Based Short Message Service; Stage 2 ] [84]. When the UDM receives an Nudm_UECM_Registration Request from an SMSF for a UE for which the MWD list is stored and no URRP-AMF flag is set, the UDM/HSS alerts the related SCs to retry the MT-SMS delivery and clears the MWD list. NOTE: This scenario assumes that the UE is not in 2G/3G/4G coverage. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.13.3.9 |
1,704 | 20.3.2 Session update procedure | The BM-SC initiates the MBMS session update procedure when service attributes (e.g. Service Area, MBMS cell list, Access indicator or ARP) for an ongoing MBMS session shall be modified. The MBMS session update procedure update procedure is initiated towards one or more of the MBMS GWs in the list of downstream nodes in the BM-SC, according to the changes in the service area. NOTE: In addition, when the MBMS Service Area for an ongoing broadcast session is changed in the BM-SC, then MBMS GW(s) may be added to, or removed from, the list of downstream nodes in the BM-SC. The BM-SC will initiate MBMS session start procedures or MBMS session stop procedures towards these MBMS GWs accordingly. The attributes that can be modified by the RAR message are the MBMS Service Area, the MBMS-Cell-List, the ARP, the Access indicator and the list of MBMS control plane nodes (MMEs, SGSNs). When a session update message is received, the MBMS GW updates its MBMS Bearer Context accordingly and informs its downstream MMEs/SGSNs of the changed service attributes. If a list of MBMS control plane nodes (MMEs, SGSNs) is included in the session update message, MBMS GW shall initiate a session start procedure towards the new MMEs/SGSNs, and a session stop procedure towards the MMEs/SGSNs that have been removed from the list. Figure 20.3.2.1: MBMS Session Update procedure 1. The BM-SC sends an RAR message to all MBMS GWs listed in the "list of downstream nodes" parameter of the affected MBMS Bearer Context to indicate that the MBMS session is updated. 2. The MBMS GW stores the new session attributes in the MBMS Bearer Context, initiates session start, session stop or session update procedure towards the MMEs/SGSNs in its list of MBMS control plane nodes and sends an RAA message to the BM-SC. An AAR message is not mandated for the SGmb application in response to an RAR- RAA command exchange. | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 20.3.2 |
1,705 | 4.7.3.2 Combined GPRS attach procedure for GPRS and non-GPRS services | The combined GPRS attach procedure is a GMM procedure used by a GPRS MS operating in MS operation modes A or B for IMSI attach for GPRS and non-GPRS services if the network operates in network operation mode I. If a GPRS MS operating in MS operation modes A or B is already attached for non-GPRS services by use of the MM specific IMSI attach procedure, but additionally wishes to perform an IMSI attach for GPRS services, the combined GPRS attach procedure shall also be used. The attach type information element shall indicate "combined GPRS/IMSI attach". In this case, the messages ATTACH ACCEPT, ATTACH COMPLETE, and ATTACH REJECT used by the combined GPRS attach procedure carry information for both the GPRS and the non-GPRS services. A GPRS MS in MS operation mode A shall perform the normal GPRS/IMSI attach procedure during an ongoing circuit-switched transaction. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.3.2 |
1,706 | 7.9.2 Delete PDN Connection Set Response | This message is sent as a response to the Delete PDN Connection Set Request. Table 7.9.2: Information Elements in a Delete PDN Connection Set Response TEID of 0 shall be used for the Delete PDN Connection Set Response. The following Cause values are defined: - "Request Accepted" - "Request rejected" - "System failure". - "Mandatory IE incorrect". - "Conditional IE missing". - "Invalid message format". "Request Accepted" indicates the receiving node was capable of storing a CSID value for each PDN connection for the type of node (MME, SGW, PGW, TWAN or ePDG) in the Delete PDN Connection Set Request and has marked, or will mark immediately, the PDN connections for deletion as specified in 3GPP TS 23.007[ Restoration procedures ] [17]. "Request Accepted" shall be returned even if there are no PDN connections that match. "Request rejected" shall be used when the receiver of the Delete PDN Connection Set Request is not capable of storing at least one CSID value per PDN connection for the type of node (MME, SGW, PGW, TWAN or ePDG) received in the Delete PDN Connection Set Request. The SGW shall respond to the Delete PDN Connection Set Request independently, i.e. without waiting for replies. | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 7.9.2 |
1,707 | 6.44.1.4 Subscription-based routing to a particular core network (e.g. in a different country) | The “Subscription-based routing to a particular core network” service forwards the traffic from the HPLMN to a target PLMN. Some operators use more than one PLMN ID, e.g., multi-national operators. Due to certain business and operational demands, it might be necessary to route traffic of a certain customer segment, typically from a certain IMSI range of USIMs, of a PLMN to another PLMN and to further handle the subscriber there. This means the UE is not handled by the "real" HPLMN (according to MNC and MCC) but by some alternative PLMN. This subscription-based routing enables the case where several national subsidiaries of a multi-national operator offer various services for different customer segments but for operational efficiency the actual service for a certain group is provided by only one dedicated network. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.44.1.4 |
1,708 | 5.32.7.2 Interworking with N26 Interface | Interworking with N26 interface is based on clause 5.17.2.2, with the following differences and clarifications: - When the UE is registered to the same PLMN over 3GPP and non-3GPP accesses, and the UE request a new MA PDU Session via non-3GPP access, the AMF also includes the indication of interworking with N26 to SMF. - The SMF does not request EBI allocation when MA PDU Session is established only over non-3GPP access. If MA PDU Session is released over 3GPP access, the allocated EBI(s) for the MA PDU Session is revoked by the SMF as described in clause 4.11.1.4.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. - The SMF does not request EBI allocation for GBR QoS Flow if the GBR QoS Flow is only allowed over non-3GPP access. - If the UE and the network support MA PDU Sessions with 3GPP access connected to EPC, the MA PDU Session may be simultaneously associated with user-plane resources on 3GPP access network connected to EPC and with non-3GPP access network connected to 5GC. This case is further described in clause 5.32.1 and in clause 4.22.2.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. - If the UE or the network does not support MA PDU Session with 3GPP access connected to EPC, the MA PDU Session is handled as follows: - When UE moves from 5GS to EPS, for both idle mode and connected mode mobility, if the MA PDU Session is moved to EPS as a PDN connection, the SMF triggers PDU Session Release procedure to release the MA PDU Session over Non-3GPP access in 5GS. UE and SMF remove ATSSS related contexts e.g. ATSSS rules, Measurement Assistance Information. - When UE moves from 5GS to EPS, for both idle mode and connected mode mobility, if the MA PDU Session is not moved to EPS as a PDN connection, the 3GPP access of this MA PDU session becomes unavailable and the AMF notifies the SMF. In turn, the SMF may decide to move the traffic to Non-3GPP access of the MA PDU session, if it is available. When UE moves back from EPS to 5GS, after the UE is registered over the 3GPP, the UE may add user-plane resources over the 3GPP access to the MA PDU session by triggering PDU Session Establishment procedure as specified in clause 5.32.2. - After UE moves from EPS to 5GS, for both idle mode and connected mode mobility, if the UE requires MA PDU session, or if no policy in the UE (e.g. no URSP rule) and no local restrictions mandate a single access for the PDU Session, UE triggers the PDU Session Modification procedure as described in clause 4.22.6.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] to provide the ATSSS Capability to SMF+PGW-C. The SMF+PGW-C may determine whether to modify this PDU Session to a MA PDU Session in 5GS, e.g. based on SMF+PGW-C and UE's ATSSS Capability, subscription data and local policy. If dynamic PCC is to be used for the MA PDU Session, the PCF decides whether the MA PDU session is allowed or not based on operator policy and subscription data. If the MA PDU Session is allowed, the SMF provides ATSSS rule(s) and Measurement Assistance Information to the UE. If the UE receives ATSSS rules and is not registered to non-3GPP access, the UE establishes the second user-plane over non-3GPP access after the UE is registered to non-3GPP access. If UE was registered to non-3GPP access in 5GS, the UP resources over non-3GPP access are also established by the SMF using the PDU Session Modification procedure. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.32.7.2 |
1,709 | 5.6.16.2 Application Function influence on Service Function Chaining | An AF may request the steering of user plane traffic to a pre-configured chain of Service Functions on N6-LAN. In the non-roaming scenario, Application Function influence on Service Function Chaining and Application Function influence on traffic routing (as defined in clause 5.6.7) can be applicable to the same traffic simultaneously. It is assumed that a service level agreement exists between the operator and a third party that includes a list of authorized predefined Service Function Chains (SFCs), each SFC being identified based on a Service Function Chaining identifier (SFC ID). The AF may request the selected traffic flows to be steered towards a specific SFC, either at PDU Session establishment or any time after PDU Session establishment. The AF requests may be sent to the PCF via the NEF. When SFC ID is included in the AF request, the parameters listed in Table 5.6.16.2-1 may be included in the AF request. Table 5.6.16.2-1: Information element contained in AF request The PCF checks whether the SFC ID received from the AF corresponds to an authorized predefined SFC according to the service level agreement with this AF. Based on the SFC ID received from the AF, the PCF derives the TSP ID(s) (that can be different for uplink and downlink directions) and sends the TSP ID(s) and optionally Metadata (as provided by the AF) to the SMF as part of the PCC rule(s) as described in clause 6.3.1 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. The SMF behaves in the same way it is described in clause 5.6.16.1. If the SMF has received Metadata in the N6-LAN Traffic Steering Enforcement Control information of the PCC rule, the SMF forwards the Metadata to the UPF via N4 in the corresponding FAR as described in clause 5.8.5.6. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.6.16.2 |
1,710 | 6.5 Physical multicast channel | The physical multicast channel shall be processed and mapped to resource elements as described in clause 6.3 with the following exceptions: - No transmit diversity scheme is specified. - Layer mapping and precoding shall be done assuming a single antenna port and the transmission shall use antenna port 4. - The PMCH can only be transmitted in the MBSFN region. For PMCH with Δf = 15 kHz, the index in the first slot in the MBSFN subframe fulfils where is equal to the value given by the higher layer parameter non-MBSFNregionLength [9]. - The PMCH shall use extended cyclic prefix. - The PMCH is not mapped to resource elements used for transmission of MBSFN reference signals. - In clause 6.3.1, for Δf = 1.25 kHz and Δf ≈ 0.37 kHz, the scrambling generator shall be initialised at the start of each slot. - For the following exception applies to clause 6.3.5: - The text "which meet all of the following criteria in the current subframe" shall be replaced by "which meet all of the following criteria in the current slot" - The mapping to resource elements on antenna port not reserved for other purposes shall be in increasing order of first the index over the assigned physical resource blocks and then the index . - For PMCH symbols belonging to an MBSFN area with configured, shall be replaced by in clauses 6.3, 6.10.2, and 6.12. | 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.5 |
1,711 | 8.5.2.2.6 Enhanced Downlink Control Channel Performance Requirement Type A - 2 Tx Antenna Ports with Non-Colliding CRS Dominant Interferer | For the parameters specified in Table 8.5.2-1 and Table 8.5.2.2.6-1, the average probability of a miss-detecting ACK for NACK (Pm-an) shall be below the specified value in Table 8.5.2.2.6-2. The purpose of this test is to verify the PHICH performance with 2 transmit antennas when the serving cell PHICH transmission is interfered by two interfering cells with the dominant interferer having the non-colliding CRS pattern and applying interference model defined in clause B.7.1. In Table 8.5.2.2.6-1, Cell 1 is the serving cell, and Cell 2 and Cell 3 are the aggressor cells. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1, Cell 2 and Cell 3, respectively. The CRS assistance information [7] is provided and includes Cell 2 and Cell 3. Table 8.5.2.2.6-1: Test Parameters for PHICH Table 8.5.2.2.6-2: Minimum performance PHICH for Enhanced Downlink Control Channel Performance Requirement Type A | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.5.2.2.6 |
1,712 | – RRCSystemInfoRequest | The RRCSystemInfoRequest message is used to request SI message(s) required by the UE as specified in clause 5.2.2.3.3 and 5.2.2.3.3a. Signalling radio bearer: SRB0 RLC-SAP: TM Logical channel: CCCH Direction: UE to Network RRCSystemInfoRequest message -- ASN1START -- TAG-RRCSYSTEMINFOREQUEST-START RRCSystemInfoRequest ::= SEQUENCE { criticalExtensions CHOICE { rrcSystemInfoRequest RRCSystemInfoRequest-IEs, criticalExtensionsFuture-r16 CHOICE { rrcPosSystemInfoRequest-r16 RRC-PosSystemInfoRequest-r16-IEs, criticalExtensionsFuture SEQUENCE {} } } } RRCSystemInfoRequest-IEs ::= SEQUENCE { requested-SI-List BIT STRING (SIZE (maxSI-Message)), --32bits spare BIT STRING (SIZE (12)) } RRC-PosSystemInfoRequest-r16-IEs ::= SEQUENCE { requestedPosSI-List BIT STRING (SIZE (maxSI-Message)), --32bits spare BIT STRING (SIZE (11)) } -- TAG-RRCSYSTEMINFOREQUEST-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
1,713 | Annex Q (normative): Application specific Congestion control for Data Communication (ACDC) (Iu mode only) | The MS may support the procedures in this annex. When GMM requests the establishment of a PS signalling connection, if the MS supports ACDC, the GMM layer shall determine the ACDC category applicable to the request based on the application identifier received from the upper layers and the configuration information in the "ACDCConf" leaf of ACDC MO as specified in 3GPP TS 24.105[ Application specific Congestion control for Data Communication (ACDC) Management Object (MO) ] [154] or in the USIM EFACDC as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [112]. NOTE 1: As an implementation option, the upper layers can determine the ACDC category and send it to the GMM layer. Then the GMM layer need not read the ACDC MO or USIM to determine the ACDC category. The GMM sublayer shall indicate to the lower layers, for the purpose of access control: - the ACDC category that applies to this request if only one ACDC category is applicable; - the highest ranked ACDC category among the ACDC categories that applies to this request if multiple ACDC categories are applicable; or - this request is for an uncategorized application if an application identifier received from the upper layers is not mapped to any ACDC category, except for the following cases: - the MS is a MS configured to use AC11 – 15 in selected PLMN; - the MS is answering to paging; - the RRC Establishment cause is set to "Emergency call"; - if conditions MO MMTEL voice call is started or MO MMTEL video call is started or MO SMSoIP is started, is satisfied; or - if a "call-pull-initiated" indication is received from the upper layer (see 3GPP TS 24.174[ Support of multi-device and multi-identity in the IP Multimedia Subsystem (IMS); Stage 3 ] [185]). NOTE 2: The request from the GMM sublayer refers to either a request to establish an initial NAS signalling connection or a request to re-establish a NAS signalling connection. If the MS supports ACDC and access is barred because of ACDC, the GMM layer shall keep track of the ACDC category for which access is barred and it shall not send a request for the same ACDC category or a lower ACDC category until access is granted. If the MS supports ACDC and access is barred because of ACDC, the GMM layer shall not send a request for any uncategorized application until access is granted. | 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 | Annex |
1,714 | 5.9.8 Generic Public Subscription Identifier | Generic Public Subscription Identifier (GPSI) is needed for addressing a 3GPP subscription in different data networks outside of the 3GPP system. The 3GPP system stores within the subscription data the association between the GPSI and the corresponding SUPI. GPSIs are public identifiers used both inside and outside of the 3GPP system. The GPSI is either an MSISDN or an External Identifier, see TS 23.003[ Numbering, addressing and identification ] [19]. If MSISDN is included in the subscription data, it shall be possible that the same MSISDN value is supported in both 5GS and EPS. NOTE: There is no implied 1-to-1 relationship between GPSI and SUPI. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.9.8 |
1,715 | 6.4.4.6 Local EPS bearer context deactivation without NAS signalling | The UE and the MME deactivate EPS bearer contexts locally without peer-to-peer ESM signalling in the following cases: 1) during the service request procedure, if the E-UTRAN establishes the user plane radio bearers for one or more EPS bearer contexts but not for all the EPS bearer contexts, e.g. due to radio access control (see clause 5.6.1.4 for details); 1a) during the resume of NAS signalling connection procedure as specified in clause 5.3.1.3, if one or more but not all the suspended user plane radio bearers are resumed; 2) during the tracking area updating procedure but the network established the user plane radio bearers due to downlink pending data, if the E-UTRAN establishes the user plane radio bearers for one or more EPS bearer contexts but not for all the EPS bearer contexts indicated active by both UE and network; NOTE 1: The synchronisation of the EPS bearers, for which the user plane radio bearers need to be established, indicated in EPS bearer context status information element in TRACKING AREA UPDATE ACCEPT message is not applicable in item 2. 3) during handover, if the target E-UTRAN does not establish all the user plane radio bearers for the UE; 4) if the E-UTRAN releases one or more user plane radio bearers but not all the user plane radio bearers of the UE due to E-UTRAN specific reasons; or 5) if triggered by an NBIFOM procedure (see 3GPP TS 24.161[ Network-Based IP Flow Mobility (NBIFOM); Stage 3 ] [36]), for an NBIFOM multi-access PDN connection. For cases 1) to 4), based on the indication from the lower layers, the UE and the MME shall locally deactivate the EPS bearer contexts for which no user plane radio bearers are set up. NOTE 2: The above cases 1) to 4) do not apply for the UE when an RRC connection release occurs. The lower layers in the UE provide the user plane radio bearer context status to the ESM sublayer when a change in the user plane radio bearers is detected by the lower layers including establishment and release of user plane radio bearers for the UE in connected mode. NOTE 3: The above cases 1) to 4) do not apply for the MME when the S1 release procedure occurs as specified in 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10]). If due to any of the cases described above the UE locally deactivates a default EPS bearer context, the UE shall locally deactivate all EPS bearer contexts associated to the PDN connection with the default EPS bearer context. If the UE locally deactivates the EPS bearer context(s) of the last remaining PDN connection, and EMM-REGISTERED without PDN connection is not supported by the UE or the MME, the UE shall perform a local detach and enter state EMM-DEREGISTERED. If this occurs during a service request procedure for CS fallback, the UE shall reselect to GERAN or UTRAN and continue with the CS service, otherwise the UE shall initiate an attach procedure. If the UE locally deactivates the EPS bearer context(s) of the last remaining PDN connection, and EMM-REGISTERED without PDN connection is supported by the UE and the MME, the UE shall enter state EMM-REGISTERED. If the UE locally deactivates the EPS bearer context(s) of the last remaining PDN connection for non-emergency bearer services and only the PDN connection for emergency bearer services remains established, the UE shall consider itself attached for emergency bearer services only. The MME shall deactivate the GBR EPS bearer contexts locally without peer-to-peer ESM signalling, when the MME performs locally the release of the S1AP signalling connection due to the S1AP signalling connection is lost. All non-GBR EPS bearers established are preserved in the MME and in the PDN GW. If the E-UTRAN requests the MME to release the S1AP signalling connection, the MME shall deactivate or preserve the GBR EPS bearer contexts according to 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10], clause 5.3.5. All non-GBR EPS bearer contexts established are preserved in the MME and in the PDN GW. NOTE 4: The UE and the MME will synchronize the EPS bearer contexts subsequently during the next service request procedure, tracking area updating procedure or routing area updating procedure. If due to any of the cases described above the MME locally deactivates a default EPS bearer context, the MME shall locally deactivate all EPS bearer contexts associated to the PDN connection with the default EPS bearer context without peer-to-peer ESM signalling to the UE. If the MME locally deactivates the EPS bearer context(s) of the last remaining PDN connection, and EMM-REGISTERED without PDN connection is not supported by the UE or the MME, the MME shall perform a local detach and enter state EMM-DEREGISTERED. If the MME locally deactivates the EPS bearer context(s) of the last remaining PDN connection, and EMM-REGISTERED without PDN connection is supported by the UE and the MME, the MME shall enter state EMM-REGISTERED. For EPS bearer context deactivation procedure initiated by the network, if no NAS signalling connection exists, the MME locally deactivates the EPS bearer context(s) without peer-to-peer ESM signalling In the case of reactivation requested, the MME can perform this local deactivation only when the EMM-entity in the network was unable to re-establish the NAS signalling connection. The EPS bearer context deactivation procedure is not initiated by the network when the MME disconnects the UE from the last remaining PDN to which it is connected and EMM-REGISTERED without PDN connection is not supported by the UE or the MME. In this case, the MME initiates a network initiated detach procedure. If the MME locally deactivates the EPS bearer context(s) of the last remaining PDN connection for non-emergency bearer services and only the PDN connection for emergency bearer services remains established for the UE, the MME shall consider the UE to be attached for emergency bearer services only. | 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.4.4.6 |
1,716 | 12.2.1.1 Procedural description | In this case: - the MS is given an address belonging to the Intranet/ISP addressing space. The address is given either at subscription in which case it is a static address or at PDP context activation in which case it is a dynamic address. This address is used for packet forwarding within the GGSN and for packet forwarding on the Intranet/ISP. This requires a link between the GGSN and an address allocation server, such as AAA, or DHCP, belonging to the Intranet/ISP; - the communication between the Packet Domain and the Intranet/ISP may be performed over any network, even an insecure e.g. the Internet. In case of an insecure connection between the GGSN and the Intranet/ISP there may be a specific security protocol in between. This security protocol is defined by mutual agreement between PLMN operator and Intranet/ISP administrator. The following description bullet items describe the signal flow. 1) The TE sends an AT-command to the MT to set up parameters. 2) The MT sends the Activate PDP context request message to the SGSN which sends the Create PDP context request message to the chosen GGSN. 3) The GGSN deduces from the APN: - the server(s) to be used for address allocation and authentication; - the protocol such as RADIUS, DHCP or L2TP to be used with this / those server(s); - the communication and security feature needed to dialogue with this / those server(s) e.g. tunnel ,IPSec security association, dial-up connection (using possibly PPP). As an example the GGSN may use one of the following options: - RADIUS for authentication and IP-address allocation. The AAA server responds with either an Access-Accept or an Access-Reject to the RADIUS client in the GGSN; - RADIUS for authentication and DHCP for host configuration and address allocation. The AAA server responds with either an Access-Accept or an Access-Reject to the RADIUS client in the GGSN. After a successful authentication, the DHCP client discovers the DHCP server(s) in the ISP/Intranet and receives host configuration data; - L2TP for forwarding PPP frames to a L2TP Network Server. 4) The GGSN sends back to the SGSN a Create PDP Context Response message. 5) Depending on the cause value received in the Create PDP Context Response the SGSN may either send the Activate PDP Context Accept message or send the Activate PDP Context Reject message to the MS. 6) The MT responds with an AT-response that may indicate whether the context activation was successful or not. In the case of a non-successful context activation the response may also indicate the cause. In case of a successful context activation, the TE will start its PPP protocol after the LLC link has been established. The LCP, Authentication and NCP negotiations are then carried out. During these negotiations the GGSN may acknowledge values, for any LCP options related to ‘L2’ framing (e.g. ‘ACCM’, ‘ACFC’ and ‘FCS-Alternatives’), as proposed by the MT, which itself is forwarding these negotiations from the TE. NOTE: With the <PDP Type>"PPP" the MT may provide a PPP relay (or proxy) function between the TE and GGSN. This gives the opportunity for the MT to intercept the ‘L2’ framing end to end negotiations. EXAMPLE: In the following example the successful PDP context activation is shown. Figure 16a | 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 | 12.2.1.1 |
1,717 | 4.3.6.5 Processing AF requests to influence traffic routing for HR-SBO session | Processing an AF requests to influence traffic routing for HR-SBO session are based on procedure described in clause 4.3.6.2 and clause 4.3.6.4 with the following differences: In step 0 of figure 4.3.6.2-1, V-SMF supporting HR-SBO subscribes to notification of AF request by invoking Nnef_TrafficInfluenceData_Subscribe service from V-NEF (Data Set = Application Data; Data Subset = AF traffic influence request information; Data Key = S-NSSAI and/or DNN and UE IP address) and (Data Set = Application Data; Data Subset = AF traffic influence request information; Data Key = S-NSSAI and/or DNN and Any UE) and (Data Set = Application Data; Data Subset = AF traffic influence request information; Data Key = S-NSSAI and/or DNN and SUPI). - For any UE, the V-SMF supporting HR-SBO performs the above subscription using S-NSSAI and/or DNN as Data Key. - For individual UE or group of UE(s), when a PDU Session is authorized for HR-SBO as described in clause 6.7 of TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [74], the V-SMF serving the PDU Session performs the above subscription using S-NSSAI and/or DNN and/or Internal Group Identifier(s) or SUPI as Data Key. The V-NEF subscribes to notification of AF request from V-UDR. Steps 4 and 5 of figure 4.3.6.2-1 are replaced with the following steps: - Step 4: The V-UDR notifies the subscribed V-NEF of the AF traffic influence request information. - Step 5: The V-NEF notifies the subscribed V-SMF of the AF traffic influence request information. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3.6.5 |
1,718 | 4.5.1.7 Forced release during MO MM connection establishment | If the mobile station's CM layer initiated the MM connection establishment but the CM layer wishes to abort the establishment prior to the completion of the establishment phase, the mobile station shall send a CM SERVICE ABORT message any time after the completion of the RR connection and not after the first CM message (e.g. SETUP) is sent. If the first CM message has already been sent, the normal release procedure defined by the appropriate CM protocol applies and the CM SERVICE ABORT shall not be sent. Sending of the CM SERVICE ABORT message is only allowed during the establishment of the first MM connection, where no other MM connection exists in parallel. If parallel MM connections exist already, a new connection establishment cannot be aborted and normal MM connection release according to subclause 4.5.3 applies after MM connection establishment. Upon transmission of the CM SERVICE ABORT message the mobile station shall stop timer T3230 and shall follow the procedures specified in subclause 4.5.3.1. Upon receipt of the CM SERVICE ABORT message the network shall abort ongoing processes, release the appropriate resources, and unless another MM connection establishment is pending or an RRLP procedure (see 3GPP TS 44.031[ None ] [23b]) or LCS procedure over RRC (see 3GPP TS 25.331[ None ] [23c]) is ongoing, initiate a normal release of the RR connection. | 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.5.1.7 |
1,719 | 9.11.3.13 Allowed PDU session status | The purpose of the Allowed PDU session status information element is to indicate to the network user-plane resources of PDU sessions associated with non-3GPP access that are allowed to be re-established over 3GPP access or if there is no PDU session(s) for which the UE allows the user-plane resources to be re-established over 3GPP access. NOTE: Allowed PDU session status IE is not applicable for MA PDU session(s) in this release of specification. The Allowed PDU session status information element is coded as shown in figure 9.11.3.13.1 and table 9.11.3.13.1. The Allowed PDU session status is a type 4 information element with minimum length of 4 octets and maximum length of 34 octets. Figure 9.11.3.13.1: Allowed PDU session status information element Table 9.11.3.13.1: Allowed PDU session status information element | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.11.3.13 |
1,720 | – PUSCH-ServingCellConfig | The IE PUSCH-ServingCellConfig is used to configure UE specific PUSCH parameters that are common across the UE's BWPs of one serving cell. PUSCH-ServingCellConfig information element -- ASN1START -- TAG-PUSCH-SERVINGCELLCONFIG-START PUSCH-ServingCellConfig ::= SEQUENCE { codeBlockGroupTransmission SetupRelease { PUSCH-CodeBlockGroupTransmission } OPTIONAL, -- Need M rateMatching ENUMERATED {limitedBufferRM} OPTIONAL, -- Need S xOverhead ENUMERATED {xoh6, xoh12, xoh18} OPTIONAL, -- Need S ..., [[ maxMIMO-Layers INTEGER (1..4) OPTIONAL, -- Need M processingType2Enabled BOOLEAN OPTIONAL -- Need M ]], [[ maxMIMO-LayersDCI-0-2-r16 SetupRelease { MaxMIMO-LayersDCI-0-2-r16} OPTIONAL -- Need M ]], [[ nrofHARQ-ProcessesForPUSCH-r17 ENUMERATED {n32} OPTIONAL, -- Need R uplinkHARQ-mode-r17 SetupRelease { UplinkHARQ-mode-r17} OPTIONAL -- Need M ]], [[ maxMIMO-Layers-n8-r18 SetupRelease { MaxMIMO-LayersDCI-n8-r18} OPTIONAL, -- Need M maxMIMO-LayersforSDM-r18 INTEGER (1..2) OPTIONAL, -- Need R maxMIMO-LayersforSDM-DCI-0-2-r18 INTEGER (1..2) OPTIONAL, -- Need R maxMIMO-LayersforSFN-r18 INTEGER (1..2) OPTIONAL, -- Need R maxMIMO-LayersforSFN-DCI-0-2-r18 INTEGER (1..2) OPTIONAL -- Need R ]] } PUSCH-CodeBlockGroupTransmission ::= SEQUENCE { maxCodeBlockGroupsPerTransportBlock ENUMERATED {n2, n4, n6, n8}, ... } MaxMIMO-LayersDCI-0-2-r16 ::= INTEGER (1..4) MaxMIMO-LayersDCI-n8-r18 ::= INTEGER (5..8) UplinkHARQ-mode-r17 ::= BIT STRING (SIZE (32)) -- TAG-PUSCH-SERVINGCELLCONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
1,721 | 4.8.2.2 UE Triggered Connection Resume in RRC_INACTIVE procedure | The Connection Resume procedure is used by the UE in RRC_INACTIVE state, e.g. to transition to RRC_CONNECTED state or for Small Data Transmission while in RRC_INACTIVE as specified in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [9]. Triggers for the UE to initiate this procedure are defined in clause 5.3.3.2.5 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. Figure 4.8.2.2-1: Connection Resume in RRC_INACTIVE 1. UE to NG-RAN: RRC message (Resume ID). The UE initiates connection resume from RRC_INACTIVE state, see TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [9]. The UE provides its Resume ID needed by the NG-RAN to access the UE's stored Context. 2. [Conditional] NG-RAN performs UE Context Retrieval. UE Context Retrieval is performed when the UE Context associated with the UE attempting to resume its connection is not locally available at the accessed NG-RAN. The UE Context Retrieval procedure via NG-RAN is specified in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [9]. 3. NG-RAN to UE: RRC messages. NG-RAN determines whether the UE shall be transitioned to RRC_CONNECTED state or kept in RRC_INACTIVE (e.g. the latter in the case of Small Data Transmission as defined in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [9]). 4a. [Conditional] N2 Path switch procedure. If the accessed NG-RAN is able to retrieve the UE Context, the accessed NG-RAN node initiates N2 Path Switch procedure, i.e. steps 1 to 8 of clause 4.9.1.2.2 and including Xn data forwarding. If the Connection Resume procedure is a response to RAN paging which is triggered by 5GC due to an N2 interface procedure, NG-RAN and 5GC handle the N2 interface procedure as a collision described in clause 4.9.1.2. If Connection Inactive procedure with CN based MT communication handling (see clause 4.8.1.1a) has been performed previously then when the path switch procedure is performed downlink data or signalling delivery is triggered, if there is any. 4b. [Conditional] N2 Notification, 4b.1 If the accessed NG-RAN is the same as the NG-RAN that configured RRC_INACTIVE and still has the UE context, NG-RAN sends: - an N2 Notification to the AMF indicating the UE is in RRC_CONNECTED, if an AMF requested N2 Notification (see clause 4.8.3); or - an MT Communication Handling request to the AMF indicating the UE is now reachable for downlink data and/or signalling if Connection Inactive procedure with CN based MT communication handling (see clause 4.8.1.1a) has been performed previously. 4b.2 The AMF invokes Nsmf_PDUSession_UpdateSMContext Request towards SMF indicating the Downlink data delivery for each PDU session with active user plane, if the AMF has requested data buffering as described in clause 4.8.1.1a. 4b.3 N4 session modification procedure is triggered by the SMF. If data buffering is handled in the UPF, the SMF updates the UPF with appropriate rules to trigger data delivery. 4b.4 The SMF sends the Nsmf_PDUSession_UpdateSMContext response. 4b.5 The AMF sends the N2 MT Communication Handling response message to NG-RAN. If NG-RAN determines that the connection resume is for Small Data Transmission as defined in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [9] and step 4a or steps 4b.1 to 4b.5 have been performed, then NG-RAN keeps the UE in RRC_INACTIVE state and the UL/DL Small Data are transferred via the NG-RAN. Based on the procedures defined in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [9], if the UE is re-configured with RRC Inactive with eDRX>10.24s, the NG-RAN may send an N2 message to 5GC as described in step 2 in clause 4.8.1.1a so the CN can then handle mobile terminated (MT) communication. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.8.2.2 |
1,722 | 6.8.1.2 R99+ HLR/AuC | Upon receipt of an authentication data request from a R99+ VLR/SGSN for a UMTS subscriber, a R99+ HLR/AuC shall send quintets, generated as specified in 6.3. Upon receipt of an authentication data request from a R98- VLR/SGSN for a UMTS subscriber, a R99+ HLR/AuC shall send triplets, derived from quintets using the following conversion functions: a) c1: RAND[GSM] = b) c2: SRES[GSM] = XRES*1 xor XRES*2 xor XRES*3 xor XRES*4 c) c3: Kc[GSM] = CK1 xor CK2 xor IK1 xor IK2 whereby XRES* is 16 octets long and XRES* = XRES if XRES is 16 octets long and XRES* = XRES || 0...0 if XRES is shorter than 16 octets, XRES*i are all 4 octets long and XRES* = XRES*1 || XRES*2 || XRES*3 || XRES*4, CKi and IKi are both 64 bits long and CK = CK1 || CK2 and IK = IK1 || IK2 | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 6.8.1.2 |
1,723 | 6.49.1 Description | Mobile metaverse services refer to a shared, perceived set of interactive perceived spaces that can be persistent. The term metaverse has been used in various ways to refer to the broader implications of AR and VR. Metaverse in diverse sectors evokes a number of possible user experiences, products and services can emerge once virtual reality and augmented reality become commonly available and find application in our work, leisure and other activities. Functional enhancements and capabilities included in standards specifications make these services function well, consistently and with diverse support mechanisms over mobile telecommunications networks. In addition to services that offer virtual or location-independent user experiences, mobile metaverse services also supports content and services that are associated or applicable only in a particular location. These metaverse services are mobile in the sense that mobile users are able to interact with services anywhere and in particular when in the locations where specific services are offered. Requirements for diverse service enablers are introduced to the 5G system to support these services, including avatar call functionality, coordination of services, digital asset management and support for spatial anchors. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.49.1 |
1,724 | 5.9.1.3 MCCH information validity and notification of changes | Change of MCCH information only occurs at specific radio frames, i.e. the concept of a modification period is used. Within a modification period, the same MCCH information may be transmitted a number of times, as defined by its scheduling (which is based on a repetition period). When the network changes (some of) the MCCH information, it notifies the UEs about the change starting from the beginning of the MCCH modification period via PDCCH which schedules the MCCH in every repetition in that modification period. Upon receiving a change notification, a UE receiving or interested to receive MBS services transmitted using MBS broadcast acquires the new MCCH information starting from the same slot. The UE applies the previously acquired MCCH information until the UE acquires the new MCCH information. The notification is transmitted with a 2-bit bitmap, see TS 38.212[ NR; Multiplexing and channel coding ] [17] clause 7.3.1.5.1. The MSB in the 2-bit bitmap, when set to '1', indicates the start of new MBS service(s). The LSB in the 2-bit bitmap, when set to '1', indicates modification of MCCH information other than the change caused by start of new MBS service(s), e.g. modification of a configuration of an on-going MBS session(s), MBS session(s) stop or neighbouring cell information modification. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.9.1.3 |
1,725 | 8.2 Registration procedure for mobility from EPS to 5GS over N26 | During mobility from EPS to 5GS, the security handling described below shall apply. When the UE performs idle mode mobility from EPS to 5GS, and if the UE has a native non-current 5G context, then the UE shall make the native non-current 5G context as the current one. The UE shall discard any mapped 5G security context. The UE shall include the UE 5G security capability alongside the mapped 5G GUTI in the Registration Request message. The UE shall also include the 5G GUTI and the ngKSI that identify a current 5G security context if available, e.g. established during an earlier visit to 5G, and integrity protect the Registration Request using the selected security algorithms in the current 5G NAS security context as it is performed for a 5G NAS message over a 3GPP access. If the UE has no current 5G security context then the UE shall send the Registration Request message without integrity protection. As per clause 5.5.1.2.2 in 3GPP 24.501, the Registration Request shall contain the TAU request or ATTACH request integrity protected using the EPS NAS security context shared with the source MME as it is performed for a LTE NAS message, then the UE shall increment its stored uplink EPS NAS COUNT value by one. NOTE: The enclosed TAU request or ATTACH request in the Registration Request contains a complete TAU Request or ATTACH request. Upon receipt of the Registration Request, the AMF shall interact with the MME identified by the mapped 5G GUTI to retrieve the UE context. The AMF shall include the enclosed TAU request or ATTACH request in the Context Request message to the MME. The MME shall verify the TAU request or ATTACH request using the stored UE security context and if the verification is successful, the MME shall send the UE context to the AMF. The AMF shall verify the integrity of the Registration Request message if the AMF obtained the 5G security context identified by the 5G GUTI. In case the verification succeeds then the AMF shall then dispose of any EPS security parameters received from the source MME in the Context Response message. In case the verification fails or the 5G UE context is not available then the AMF shall treat the Registration Request message as if it was unprotected. In such case, the AMF may either derive a mapped 5G security context from the EPS context received from the source MME as described in clause 8.6.2 or initiate a primary authentication procedure to create a new native 5G security context. If the AMF derives a mapped 5G security context from the EPS security context, then the ngKSI associated with the newly derived mapped 5G security context and the uplink and downlink 5G NAS COUNTs are defined and set as described in clause 8.6.2. If the Registration Request contains a TAU Request or ATTACH request message, the network shall use the uplink EPS NAS COUNT corresponding to the TAU Request or ATTACH request message for deriving the KAMF' from the KASME. The AMF shall use and include the ngKSI to the UE in NAS SMC procedure, for the UE to identify the EPS security context used for the derivation of a mapped 5G security context. If a mapped 5G security context is created or the native 5G security context has been changed (e.g., due to a new KAMF' derivation or NAS algorithm change), the AMF shall activate the resulting 5G security context by a NAS SMC procedure. When a mapped 5G security context is created, the AMF shall store the selected EPS NAS security algorithms in the mapped 5G security context and include them in the NAS Security Mode Command. If the AMF wants to continue to use the native 5G security context used by the UE to protect the Registration Request, the AMF may skip the NAS SMC procedure and send the Registration Accept message protected using the native 5G security context identified by the 5G-GUTI and the ngKSI included in the Registration Request message. In case the type value in the received ngKSI in NAS SMC indicates a mapped security context, then the UE shall use the value field in the received ngKSI to identify the EPS security context from which the UE derives the mapped 5G security context as described in clause 8.6.2. The UE shall activate the mapped 5G security context to verify the integrity protection of the NAS SMC as it is performed for a 5G NAS message over a 3GPP access. The Registration Accept message shall be protected by the new mapped 5G security context (if a mapped 5G security context was activated by NAS SMC) or by the new native 5G security context (if a new native 5G security context was activated by NAS SMC) as it is performed for a 5G NAS message over a 3GPP access. Otherwise, the current native 5G security context shall be used. If the AMF chooses to derive an initial KgNB from a new KAMF key (either the mapped KAMF' key or the native KAMF key), then the initial KgNB is derived as specified in Annex A.9 using the start value of the uplink 5G NAS COUNT protecting the NAS Security Mode Command Complete message and an access type distinguisher set to "3GPP access". If the UE receives an AS SMC message, then the UE shall derive an initial KgNB from a new KAMF key in the same way as the AMF. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 8.2 |
1,726 | 4.4.12 RAN Congestion Awareness Function | The RAN Congestion Awareness Function (RCAF) is an element that provides RAN User Plane Congestion Information (RUCI) to the PCRF to enable the PCRF to take the RAN user plane congestion status into account for policy decisions. The RCAF collects information related to user plane congestion from the RAN's OAM system based on which the RCAF determines the congestion level (and the identifier) of an eNodeB or E-UTRAN cell. Via the Nq interface the RCAF determines the UEs served by a congested eNodeB or congested E-UTRAN cell and retrieves the APNs of the active PDN connections of those UEs. The decision whether the RCAF operates on eNodeB or E-UTRAN cell level is up to operator configuration. Via the Np reference point, the RCAF sends the RUCI to the PCRFs serving the UEs' PDN connections. NOTE 1: The details of congestion reporting to the PCRF and the Np reference point are specified in TS 23.203[ Policy and charging control architecture ] [6]. NOTE 2: In the case of roaming or RAN sharing as specified in TS 23.251[ Network sharing; Architecture and functional description ] [24], Np is an inter-operator reference point. Whether Np applies in the case of roaming and RAN sharing is subject to inter-operator agreements. Figure 4.4.12-1 illustrates the RCAF connected to the MME. The RCAF is located in the same PLMN as the serving MME except in network sharing scenarios where the RCAF belongs to the RAN operator. Figure 4.4.12-1: RCAF connected to MME | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.4.12 |
1,727 | A.6 UE Initiated UL QoS Flow | The following figure shows an example message flow when the UE AS receives an UL packet for a new QoS flow for which a QFI to DRB mapping rule does not exist. Figure A.6-1: UL packet with a new QoS flow for which a mapping does not exist in UE 0. PDU session and DRBs (including a default DRB) have been already established. 1. UE AS receives a packet with a new QFI from UE NAS. 2. UE uses the QFI of the packet to map it to a DRB. If there is no mapping of the QFI to a DRB in the AS mapping rules for this PDU session, then the packet is assigned to the default DRB. 3. UE sends the UL packet on the default DRB. The UE includes the QFI in the SDAP header. 4. gNB sends UL packets to UPF and includes the corresponding QFI. 5. If gNB wants to use a new DRB for this QoS flow, it sets up one. It can also choose to move the QoS flow to an existing DRB using RQoS or RRC signalling (see clauses A.2 and A.3). 6. 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.6 |
1,728 | 4.11.2.3 EPS to 5GS Mobility | The following procedure is used by UEs in single-registration mode on mobility from EPS to 5GS. In the case of network sharing the UE selects the target PLMN ID according to clause 5.18.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. This procedure is also used by UEs in dual-registration mode to perform registration in 5GS when the UE is also registered in EPC. The procedure is the General Registration procedure as captured in clause 4.2.2. Difference from that procedure are captured below. The UE has one or more ongoing PDN connections including one or more EPS bearers. During the PDN connection establishment, the UE allocates the PDU Session ID and sends it to the SMF+PGW-C via PCO, as described in clause 4.11.1.1. Figure 4.11.2.3-1: Mobility procedure from EPS to 5GS without N26 interface 0. The UE is attached in EPC as specified in clause 4.11.2.4.1. 1. Step 1 in clause 4.2.2.2.2 (General Registration) with the following clarifications: The UE indicates that it is moving from EPC. The UE in single registration mode provides the Registration type set to "mobility registration update", a 5G-GUTI mapped from the 4G-GUTI and a native 5G-GUTI (if available) as an Additional GUTI. The UE includes the UE Policy Container containing the list of PSIs, indication of UE support for ANDSP and OSId if available. The UE shall select the 5G-GUTI for the additional GUTI as follows, listed in decreasing order of preference: - a native 5G-GUTI assigned by the PLMN to which the UE is attempting to register, if available; - a native 5G-GUTI assigned by an equivalent PLMN to the PLMN to which the UE is attempting to register, if available; - a native 5G-GUTI assigned by any other PLMN, if available. The UE in dual registration mode provides the Registration type set to "initial registration" and a native 5G-GUTI or SUCI. In single registration mode, the UE also includes at least the S-NSSAIs (with values for the Serving PLMN) associated with the established PDN connections in the Requested NSSAI in RRC Connection Establishment. 2. Step 2 as in clause 4.2.2.2. 3. Step 3 as in clause 4.2.2.2.2 (General Registration), with the following modifications: If the Registration type is "mobility registration update" and the UE indicates that it is moving from EPC in step 1 and the AMF is configured to support 5GS-EPS interworking procedure without N26 interface, the AMF treats this registration request as "initial Registration" and the AMF skips the PDU Session status synchronization. NOTE 1: The UE operating in single registration mode includes the PDU Session IDs corresponding to the PDN connections to the PDU Session status. If the UE has provided a 5G-GUTI mapped from 4G-GUTI in step 1 and the AMF is configured to support 5GS-EPS interworking procedure without N26 interface, the AMF does not perform steps 4 and 5 in clause 4.2.2.2 (UE context transfer from the MME). 4. Steps 4-13 as in clause 4.2.2.2.2 (General Registration), with the following modifications: If the UE has included an additional GUTI in the Registration Request, then the new AMF attempts to retrieve the UE's security context from the old AMF in steps 4 and 5. If the UE's security context is not available in the old AMF or if the UE has not provided an additional GUTI then the AMF retrieves the SUCI from the UE in steps 6 and 7. 5. Step 14 as in clause 4.2.2.2.2 (General Registration), with the following modifications: If the UE indicates that it is moving from EPC and the Registration type is set to "initial registration" or "mobility registration update" in step 1 and AMF is configured to support 5GS-EPS interworking without N26 procedure, the AMF sends an Nudm_UECM_Registration Request message to the HSS+UDM indicating that registration of an MME at the HSS+UDM, if any, shall not be cancelled. The HSS+UDM does not send cancel location to the old MME. NOTE 2: If the UE does not maintain registration in EPC, upon reachability time-out, the MME can implicitly detach the UE and release the possible remaining PDN connections in EPC. The subscription profile the AMF receives from HSS+UDM includes the DNN/APN and SMF+PGW-C FQDN for S5/S8 interface for each PDN connection established in EPC. For emergency PDU Session, the AMF receives Emergency Information containing SMF+PGW-C FQDN from HSS+UDM. 6. Steps 15-19c as in clause 4.2.2.2.2 (General Registration). 7. Step 21 as in clause 4.2.2.2.2 (General Registration) with the following modifications: The AMF includes an "Interworking without N26" indicator to the UE. If the UE had provided PDU Session Status information in step 1, the AMF Sets the PDU Session Status to not synchronized. 8. Step 22 as in clause 4.2.2.2.2 (General Registration) 9. UE requested PDU Session Establishment procedure as in clause 4.3.2.2.1. If the UE had setup PDN Connections in EPC which it wants to transfer to 5GS and maintain the same IP address/prefix and the UE received "Interworking without N26" indicator in step 7, the UE performs the UE requested PDU Session Establishment Procedure as in clause 4.3.2.2 and sets the Request Type to "Existing PDU Session" or "Existing Emergency PDU Session" in step 1 of the procedure. The UE provides a DNN for non-emergency PDU Session, the PDU Session ID and S-NSSAI corresponding to the existing PDN connection it wants to transfer from EPS to 5GS. The S-NSSAI is set as described in clause 5.15.7.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the Request Type indicates "Existing Emergency PDU Session", the AMF shall use the Emergency Information received from the HSS+UDM which contains SMF+PGW-C FQDN for S5/S8 interface for the emergency PDN connection established in EPS and the AMF shall use the S-NSSAI locally configured in Emergency Configuration Data. UEs in single-registration mode performs this step for each PDN connection immediately after the step 8. UEs in dual-registration mode may perform this step any time after step 8. Also, UEs in dual-registration mode may perform this step only for a subset of PDU Sessions. The AMF determines the S5/S8 interface of the SMF+PGW-C for the PDU Session based on the DNN received from the UE and the SMF+PGW-C ID in the subscription profile received from the HSS+UDM in step 5 or when the HSS+UDM notifies the AMF for the new SMF+PGW-C ID in the updated subscription profile. The AMF queries the NRF in serving PLMN by issuing the Nnrf_NFDiscovery_Request including the FQDN for the S5/S8 interface of the SMF+PGW-C and the NRF provides the IP address or FQDN of the N11/N16 interface of the SMF+PGW-C. The AMF invokes the Nsmf_PDUSession_CreateSMContext service with the SMF address provided by the NRF. The AMF includes the PDU Session ID to the request sent to the SMF+PGW-C. The SMF+PGW-C uses the PDU Session ID to determine the correct PDU Session. After step 16a of Figure 4.3.2.2.1-1 in clause 4.3.2.2.1, user plane is switched from EPS to 5GS. As specified clause 4.3.2.2, if the SMF has not yet registered for the PDU Session ID, then the SMF registers with the UDM using Nudm_UECM_Registration (SUPI, DNN, PDU Session ID) and if Session Management Subscription data for corresponding SUPI, DNN and S-NSSAI is not available, then SMF retrieves the Session Management Subscription data using Nudm_SDM_Get (SUPI, Session Management Subscription data, DNN, S-NSSAI) and subscribes to be notified when this subscription data is modified using Nudm_SDM_Subscribe (SUPI, Session Management Subscription data, DNN, S-NSSAI). NOTE 3: The SMF can, instead of the Nudm_SDM_Get service operation, use the Nudm_SDM_Subscribe service operation with an Immediate Report Indication that triggers the UDM to immediately return the subscribed data if the corresponding feature is supported by both the SMF and the UDM. 10. The SMF+PGW-C performs release of the resources in EPC for the PDN connections(s) transferred to 5GS by performing the PDN GW initiated bearer deactivation procedure as defined in clause 5.4.4.1 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13], except the steps 4-7. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.11.2.3 |
1,729 | D.2.2 UE-initiated UE state indication procedure D.2.2.1 General | The purpose of the UE-initiated UE state indication procedure is: a) to deliver the UPSI(s) of the UE policy section(s) which are: - identified by a UPSI with the PLMN ID part indicating the HPLMN or the selected PLMN, and stored in the UE, if any; or - identified by a UPSI with the PLMN ID part indicating the PLMN ID part of the SNPN identity of the selected SNPN and associated with the NID of the selected SNPN, and stored in the UE, if any; b) to indicate whether UE supports ANDSP; c) to indicate whether UE supports URSP provisioning in EPS; c1) to indicate whether UE supports VPS URSP; d) to indicate whether UE supports reporting URSP rule enforcement; and e) to deliver the UE's one or more OS IDs; to the PCF. | 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 | D.2.2 |
1,730 | 6.6.3.2A Spurious emission band UE co-existence for CA | This clause specifies the additional requirements for inter-band uplink carrier aggregation configurations with the single CC uplink assigned to two E-UTRA bands for coexistence with protected bands for the specified uplink carrier aggregation configurations in Table 6.5A.3.2.3-1. The intersection of the requirements for the individual bands specified in clause 6.5.3.2 shall also apply for the specified uplink carrier aggregation configurations. Intersection of a requirement means that both UL constituent bands have the same protected band requirement specified and if one or both protected bands have note(s) associated those note(s) also apply . As exceptions, the additional requirements in Table 6.6.3.2A-0 apply on each component carrier with all component carriers are active. NOTE 1: 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. NOTE 2: For inter-band carrier aggregation with uplink assigned to two E-UTRA bands the requirements in Table 6.6A.3.2.3-1 could be verified by measuring spurious emissions at the specific frequencies where second and third order intermodulation products generated by the two transmitted carriers can occur; in that case, the requirements for remaining applicable frequencies in Table 6.6A.3.2.3-1 and in clause 6.6.3.2 would be considered to be verified by the measurements verifying the one uplink inter-band CA UE to UE co-existence requirements. Table 6.6.3.2A-0: Requirements for uplink inter-band carrier aggregation (two bands) Table 6.6.3.2A-1: Requirements for intraband carrier aggregation Table 6.6.3.2A-2: Requirements for intraband non-contiguous CA | 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.2A |
1,731 | 6.38.2 Requirements 6.38.2.1 General | The 5G system shall support mechanisms to identify a PIN, a PIN Element, an eRG and a PRAS. Subject to local regulations, the 5G system shall support regulatory requirements for emergency calls, PWS and eCall for UEs connected via a CPN. NOTE: The above requirement applies to UEs connected via 3GPP access. The 5G system shall support applications on an Application Server connected to a CPN or PIN. The 5G system shall be able to support PINs with PIN Elements subscribed to more than one network operator (e.g., a PIN Element that is a MUSIM UE and subscribes to different operators respectively, one PIN Element subscribed to network operator A and another PIN Element subscribed to network operator B). Subject to regulatory requirements and operator policy, the 5G system shall support an efficient data path within the CPN for intra-CPN communications. NOTE 1: For services an operator deploys in the 5G network (i.e. not in the CPN), local data routed via eRG does not apply. Subject to regulatory requirements and operator policy, the 5G system shall support a data path not traversing the 5G network for intra-PIN communications via direct connections. The 5G system shall enable the network operator to provide any 5G services to any UE via a PRAS connected via an eRG. NOTE 2: Whether the PRAS can be used by UEs from other PLMNs in the same country as the PLMN associated with the PRAS is subject to regulatory policy on national roaming. The 5G system shall minimize service disruption for a UE that is moving between CPN access and operator provided mobile access. NOTE 3: CPN access can imply access via a PRAS or can imply access directly via an eRG. Operator provided mobile access implies access via an operator owned base station. The 5G system shall minimize service disruption when a CPN communication path changes between two PRASes. The 5G system shall be able to minimize service disruption when a PIN Element changes the communication path from one PIN Element (e.g. PIN Element with Gateway Capability) to another PIN Element or operator provided mobile access. The communication path between PIN Elements may include licensed and unlicensed spectrum as well as 3GPP and non-3GPP access. The 5G system shall be able to support PRAS sharing between multiple PLMNs. The 5G system shall support mechanisms to aggregate, switch or split the service between non-3GPP RAT and PIN direct connections using licensed spectrum. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.38.2 |
1,732 | 6.3.2.5 Abnormal cases on the network side | The following abnormal cases can be identified: a) Expiry of timer T3591. On the first expiry of the timer T3591, the SMF shall resend the PDU SESSION MODIFICATION COMMAND message and shall reset and restart timer T3591. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3591, the SMF shall abort the procedure and enter the state PDU SESSION ACTIVE. The SMF may continue to use the previous configuration of the PDU session or initiate the network-requested PDU session release procedure. If the SMF decides to continue to use the previous configuration of the PDU session and i) the Authorized QoS rules IE is included in the PDU SESSION MODIFICATION COMMAND message, the SMF may mark the corresponding authorized QoS rule(s) of the PDU session as to be synchronised with the UE; and ii) the Authorized QoS flow descriptions IE is included in the PDU SESSION MODIFICATION COMMAND message, the SMF may mark the corresponding authorized QoS flow description(s) of the PDU session as to be synchronised with the UE. b) Void. c) Collision of UE-requested PDU session release procedure and network-requested PDU session modification procedure. If the SMF receives a PDU SESSION RELEASE REQUEST message during the network-requested PDU session modification procedure, and the PDU session indicated in the PDU SESSION RELEASE REQUEST message is the PDU session that the SMF had requested to modify, the SMF shall abort the PDU session modification procedure and proceed with the UE-requested PDU session release procedure. d) Collision of UE-requested PDU session modification procedure and network-requested PDU session modification procedure. If the network receives a PDU SESSION MODIFICATION REQUEST message during the network-requested PDU session modification procedure, and the PDU session indicated in the PDU SESSION MODIFICATION REQUEST message is the PDU session that the network had requested to modify, the network shall: i) if the PDU SESSION MODIFICATION REQUEST message includes connection capabilities, ignore the PDU SESSION MODIFICATION REQUEST message received in the state PDU SESSION MODIFICATION PENDING except for the connection capabilities and proceed with the network-requested PDU session modification procedure; or ii) otherwise, ignore the PDU SESSION MODIFICATION REQUEST message received in the state PDU SESSION MODIFICATION PENDING and proceed with the network-requested PDU session modification procedure as if no PDU SESSION MODIFICATION REQUEST message was received from the UE. e) 5G access network cannot forward the message. If the SMF determines based on content of the n2SmInfo attribute specified in 3GPP TS 29.502[ 5G System; Session Management Services; Stage 3 ] [20A] that the DL NAS TRANSPORT message carrying the PDU SESSION MODIFICATION COMMAND message was not forwarded to the UE by the 5G access network, then the SMF shall abort the procedure and enter the state PDU SESSION ACTIVE. f) 5G access network cannot forward the message due to handover. If the SMF determines based on content of the n2SmInfo attribute specified in 3GPP TS 29.502[ 5G System; Session Management Services; Stage 3 ] [20A] that the DL NAS TRANSPORT message carrying the PDU SESSION MODIFICATION COMMAND message was not forwarded to the UE by the 5G access network due to handover, then the SMF shall abort the procedure and enter the state PDU SESSION ACTIVE. The SMF may re-initiate, up to a pre-configured number of times, the network-requested PDU session modification procedure when the SMF detects that the handover is completed successfully or has failed or at the expiry of the configured guard timer as specified in 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9]. g) Collision of re-establishment of the user-plane resources and network-requested PDU session modification procedure for the same PDU session. If the SMF receives an indication from the AMF to re-establish the user-plane resources during the network-requested PDU session modification procedure for the same PDU session, the network shall abort the network-requested PDU session modification procedure and proceed with re-establishment of the user-plane resources for the PDU session as specified in 3GPP TS 29.502[ 5G System; Session Management Services; Stage 3 ] [20A] subclause 5.2.2.3.2.2. NOTE: After the completion of re-establishment of the user-plane resources for the PDU session, the SMF can re-initiate the network-requested PDU session modification procedure for the PDU session. h) Collision of UE-requested PDU session establishment procedure and network-requested PDU session modification procedure. If the network receives a PDU SESSION ESTABLISHMENT REQUEST message with request type set to "existing PDU session" or "existing emergency PDU session" during the network-requested PDU session modification procedure, and the PDU session ID indicated in the PDU SESSION ESTABLISHMENT REQUEST message is the PDU session that the network had requested to modify, the network shall abort the network-requested PDU session modification procedure and proceed with the UE-requested PDU session establishment procedure. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.3.2.5 |
1,733 | 7.6.4.3 Repeated IEs | If an information element with format TLV-E is repeated in a Type 6 IE container information element in which repetition of the information element is not specified in clause 8 and clause 9 of the present document, the UE shall handle only the contents of the information element appearing first and shall ignore all subsequent repetitions of the information element. When repetition of information elements in the Type 6 IE container information element is specified, the UE shall handle only the contents of specified repeated information elements. If the limit on repetition of information elements is exceeded, the UE shall handle the contents of information elements appearing first up to the limit of repetitions and shall ignore all subsequent repetitions of the information element. The network should follow the same procedures. | 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 | 7.6.4.3 |
1,734 | 4.11.3 Failed PUCCH allocations for SCell scheduling in Carrier Aggregation | a) This measurement provides the number of failed PUCCH allocations in the PCell for SCell scheduling in Carrier Aggregation. This measurement is split into subcounters for the PUCCH format 3 and PUCCH format 1bwcs. b) CC c) On the failure of a Scell scheduling due to lack of PUCCH resources in the PCell for Carrier Aggregation. d) Each measurement is an integer value. e) DRB.PucchAllocNbrFail.PUCCHFormat where PUCCHFormat identifies the PUCCH format, which is either “format3” or “format1bwcs”. f) EUtranCellFDD EUtranCellTDD g) Valid for packet switched traffic h) EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.11.3 |
1,735 | 4.22.2.2.2 Home-routed Roaming - UE registered to different PLMNs | When the UE is registered to different PLMNs over 3GPP access and non-3GPP access, the MA PDU Session is established first over one access as specified in Figure 4.3.2.2.2-1 ("UE-requested PDU Session Establishment for home-routed roaming scenarios") and then over the other access with the following differences and clarifications: - In step 1, the UE provides Request Type as "MA PDU Request" in UL NAS Transport message and its ATSSS Capabilities, as defined in clause 5.32.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The UE indicates to AMF whether it supports non-3GPP access path switching. - In step 2, if the AMF supports MA PDU sessions, then the AMF selects a V-SMF, which supports MA PDU sessions. If the AMF supports non-3GPP access path switching and the UE indicated in step 1 that the UE supports non-3GPP access path switching, the AMF may select a V-SMF and H-SMF supporting non-3GPP access path switching. - In step 3, the AMF informs the V-SMF that the request is for a MA PDU Session (i.e. it includes an "MA PDU Request" indication). If the AMF supports non-3GPP access path switching while maintaining two N2 connections for non-3GPP access, the selected SMFs supports non-3GPP path switching and UE indicated in step 1 that the UE supports non-3GPP access path switching, the AMF indicates whether the UE supports non-3GPP path switching to the V-SMF. - In step 6, the V-SMF informs the H-SMF that the request is for a MA PDU Session (i.e. it includes an "MA PDU Request" indication). - In step 7, the H-SMF retrieves, via Session Management subscription data, the information whether the MA PDU session is allowed or not. - In step 9, if dynamic PCC is to be used for the MA PDU Session, the H-SMF sends an "MA PDU Request" indication to PCF in the SM Policy Control Create message and the ATSSS Capabilities of the MA PDU session. The H-SMF provides the currently used Access Type(s) and RAT Type(s) for the MA-PDU session to the PCF. The PCF decides whether the MA PDU session is allowed or not based on operator policy and subscription data. - In step 14, the V-SMF indicates support of non-3GPP path switching in the PDU Session Establishment Accept message. - In step 16, the UE receives a PDU Session Establishment Accept message, which indicates to UE that the requested MA PDU session was successfully established. This message includes the ATSSS rules for the MA PDU session, which were derived by H-SMF and may include Measurement Assistance Information. - After the MA PDU Session is successfully established on the first access, the UE shall initiate again the MA PDU Session establishment procedure in Figure 4.3.2.2.2-1 over the other access with the following differences and clarifications: - In step 1, the UE shall send another PDU Session Establishment Request over the other access containing the same PDU Session ID that was provided over the first access. The UE also provides Request Type as "MA PDU Request" in UL NAS Transport message. The UE indicates to the AMF whether it supports non-3GPP access path switching. - In step 2, if the AMF supports non-3GPP access path switching while maintaining two N2 connections for non-3GPP access, the may select a V-SMF that support non-3GPP access path switching. - In step 3, if the AMF supports non-3GPP path switching and the UE indicated in step 1 that the UE supports non-3GPP access path switching, the AMF indicates whether the UE supports non-3GPP path switching to the V-SMF. - In step 12, new UL N9 tunnel CN info is allocated by the H-SMF or by the H-UPF. - In step 14, the V-SMF indicates support of non-3GPP path switching in the PDU Session Establishment Accept message. - In step 16, the UE receives another PDU Session Establishment Accept message, which may contain updated ATSSS rules for the MA PDU session. - After step 20, two N9 tunnels between the H-UPF and two different V-UPFs as well as two N3 tunnels between different V-UPF and RAN/AN are established, or two N3 tunnels, one is between V-UPF and RAN/AN over 3GPP access and the other is between H-UPF and RAN/AN over non 3GPP access, as well as one N9 tunnel between H-UPF and V-UPF are established. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.22.2.2.2 |
1,736 | 8.10.1.2.5A Single-layer Spatial Multiplexing (with multiple CSI-RS configurations) | The requirements are specified in Table 8.10.1.2.5A-2, with the addition of the parameters in Table 8.10.1.2.5A-1 and the downlink physical channel setup according to Annex C.3.2. The purpose of these tests is to verify closed loop rank one performance on one of the antenna ports 7 or 8 with a simultaneous transmission on the other antenna port in the serving cell, and to verify rate matching with multiple CSI reference symbol configurations with non-zero and zero transmission power. Table 8.10.1.2.5A-1: Test Parameters for Testing CDM-multiplexed DM RS (single layer) with multiple CSI-RS configurations Table 8.10.1.2.5A-2: Minimum performance for CDM-multiplexed DM RS with interfering simultaneous transmission (FRC) with multiple CSI-RS configurations Table 8.10.1.2.5A-3: Void | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.10.1.2.5A |
1,737 | 8.4.1.2.3 Minimum Requirement 2 Tx Antenna Port (demodulation subframe overlaps with aggressor cell ABS) | For the parameters for non-MBSFN ABS specified in Table 8.4.1-1 and Table 8.4.1.2.3-1, the average probability of a missed downlink scheduling grant (Pm-dsg) shall be below the specified value in Table 8.4.1.2.3-2. The downlink physical setup is in accordance with Annex C.3.2 and Annex C.3.3. In Table 8.4.1.2.3-1, Cell 1 is the serving cell, and Cell 2 is the aggressor cell. The downlink physical channel setup for Cell 1 is according to Annex C.3.2 and for Cell 2 is according to Annex C.3.3, respectively. For the parameters for MBSFN ABS specified in Table 8.4.1-1 and Table 8.4.1.2.3-3, the average probability of a missed downlink scheduling grant (Pm-dsg) shall be below the specified value in Table 8.4.1.2.3-4. The downlink physical channel setup for Cell 1 is according to Annex C.3.2 and for Cell 2 is according to Annex C.3.3, respectively. Table 8.4.1.2.3-1: Test Parameters for PDCCH/PCFICH – Non-MBSFN ABS Table 8.4.1.2.3-2: Minimum performance PDCCH/PCFICH – Non-MBSFN ABS Table 8.4.1.2.3-3: Test Parameters for PDCCH/PCFICH – MBSFN ABS Table 8.4.1.2.3-4: Minimum performance PDCCH/PCHICH – MBSFN ABS | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.4.1.2.3 |
1,738 | 8.12.1.1.4 Minimum Requirements for Standalone for UE with multiple TBs interleaved transmission | The requirements are specified in Table 8.12.1.1.4-2, with the addition of the parameters in Table 8.12.1.1.4-1 and the downlink physical channel setup according to Annex C.3.6. The purpose of these tests is to verify NPDSCH performance when multiple TBs with interleaved transmission are scheduled by one DCI as specified in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [6]. These requirements are applicable for UE of UE-Category-NB NB2 supporting multiple TBs scheduling with interleaved transmission when multiple TBs are scheduled. Table 8.12.1.1.4-1: Test Parameters for NPDSCH under Standalone Table 8.12.1.1.4-2: Minimum performance for NPDSCH under Standalone with 1 NRS port | 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.12.1.1.4 |
1,739 | 4.28.3.1 Control of (g)PTP time synchronization service without AF request | The TSCTSF may use the subscription data to control the (g)PTP-based time distribution without AF request. Figure 4.28.3.1-1: Subscription based control of (g)PTP time synchronization service without AF request 1. The UE performs the UE-requested PDU Session Establishment. 2. The PCF determines if the PDU Session is potentially impacted by time synchronization service and invokes Npcf_PolicyAuthorization_Notify service operation to the TSCTSF discovered and selected for time synchronization to indicate there is a UE connected to a specific DNN/S-NSSAI configured for (g)PTP-based time distribution. The TSCTSF retrieves the UE SUPI using IP address and /or DNN/S-NSSAI from BSF as specified in the clause 4.15.10. 3. The TSCSTF uses the SUPI to retrieve the Time Synchronization Subscription Data available at the UDM. 4. The TSCTSF controls the (g)PTP-based time synchronization service based on the Time Synchronization Subscription Data as defined in clause 5.27.1.11 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the Time Synchronization Subscription Data contains: a) one or more Subscribed Time Synchronization Service ID(s) that can be mapped to PTP instance configuration(s), the TSCTSF determines if one or more of the PTP instance configurations match with the DNN/S-NSSAI of the given PDU Session. The TSCTSF stores information that the time-synchronization service cannot be controlled by an AF for the given SUPI. b) An indication that an AF-requested (g)PTP time synchronization service is allowed for the given UE and DNN/S-NSSAI, the TSCTSF adds the given SUPI to the list of SUPIs for which the time-synchronization service can be controlled by an AF. c) If TSCTSF receives neither a) nor b), the TSCTSF assumes that the time-synchronization service cannot be controlled by an AF for the given SUPI. The TSCTSF releases the AF-session with the PCF. 5. For each matching PTP instance configuration determined in step 4, if no PTP instance exists for the given PTP instance configuration, the TSCTSF initializes the PTP instance in 5GS as described in clause K.2.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The TSCTSF configures a PTP port in DS-TT and adds it to the corresponding PTP instance in NW-TT as described in clause K.2.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The TSCTSF uses the procedure in clause 4.15.9.4 to activate or modify the 5G access stratum time distribution for the UE. If the PTP instance configuration referenced by the Time Synchronization Subscription data for the UE contains start and stop times or a coverage area, the TSCTSF updates the PTP port for the corresponding PTP instance as defined in clause 5.27.1.11 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The TSCTSF uses the procedure in clause 4.15.9.4 to activate or deactivate the 5G access stratum time distribution for the UEs that are part of the impacted PTP instance. 6. If a coverage area is included in the subscription data for UE related to the PTP instance, TSCTSF discovers the AMF(s) serving the TA(s) defined for the time synchronization coverage area (Area of Interest) and subscribe to receive notifications in UEs presence in the Area of Interest. Based on the outcome the TSCTSF determines whether to activate or deactivate the time synchronization service for the impacted PTP instance. The TSCTSF will activate/deactivate the service by modifying the PTP instance configuration as described in clause K.2.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.28.3.1 |
1,740 | 16.2.0 Support for IMS voice | For IMS voice support in NG-RAN, the following is assumed: - Network ability to support IMS voice sessions, i.e. ability to support QoS flows with 5QI for voice and IMS signalling (see clause 12 and TS 23.501[ System architecture for the 5G System (5GS) ] [3]), or through EPC System fallback; - UE capability to support "IMS voice over PS", see TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [28]. The capabilities indications check is handled at NAS layer. To maintain the voice service in NG-RAN, the UE provides additional capabilities over RRC (see TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12]), that are used to determine accurate NR voice support options. Further MMTEL IMS voice and video enhancements are facilitated by the mechanisms described in the following clauses. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.2.0 |
1,741 | 10.14.1 PDU Session Split at UPF during PDU session resource setup | When a new PDU session needs to be established, the 5GC may provide two UL TEID addresses during PDU Session Resource Setup in order to allow for PDU session split. The MN may perform the SN Addition or the MN-initiated SN Modification procedure. If the MN decides to split the PDU session, the MN provides two DL TEID addresses and also the QoS flows associated with each tunnel. Figure 10.14.1-1: PDU Session Split at UPF during PDU session resource setup 1. The 5GC provides two UL TEID addresses during PDU Session Resource Setup, to be applied as the first UL tunnel on the NG-U interface and the additional NG-U tunnel in case the MN decides to split the PDU session. 2. The MN decides to setup two tunnels. The MN uses the SN Addition procedure (as described in 10.2.2) or the MN-initiated SN Modification procedure (as described in 10.3.2) up to step 6. 3. The MN provides a DL TEID address to be applied as the first and an additional DL tunnel address on the NG-U interface. The MN also provides which QoS flows are associated with which tunnel. | 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.14.1 |
1,742 | 4.7.1.1 Number of paging records discarded at the eNodeB/RN | This measurement provides the number of paging records that are discarded at the eNB/RN for paging occasions in each cell. CC Reception of a S1AP PAGING message from MME/DeNB, see TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [9], with UE identity which satisfies the following formulae from TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [14]. X = (T div N)*(UE_ID mod N) Y = floor(UE_ID/N) mod Ns AND the maximum number of paging records that can be queued for each paging occasion has been reached. A single integer value. PAG. DiscardedNbr 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.7.1.1 |
1,743 | 6.2.16 Handling of header compression for control plane CIoT optimizations | The UE and the SMF may use: - IP header compression for PDU sessions of "IPv4", "IPv6" or "IPv4v6" PDU session type; and - Ethernet header compression for PDU sessions of "Ethernet" PDU session type. Both the UE and the AMF indicate whether header compression for control plane CIoT 5GS optimization is supported during registration procedures (see subclause 5.5.1). If both the UE and the network support header compression, the header compression configuration for each PDU session is negotiated during the PDU session establishment procedure and PDU session modification procedure as specified in subclauses 6.3.2, 6.4.1 and 6.4.2. For IP header compression, ROHC protocol specified in IETF RFC 5795 [39B] is used. The IP header compression configuration used for IP header compression is (re-)negotiated between the UE and the SMF using the IP header compression configuration IE as specified in subclauses 6.3.2.2, 6.4.1.2, 6.4.1.3 and 6.4.2.2, respectively. For Ethernet header compression, Ethernet Header Compression (EHC) protocol specified in 3GPP TS 38.323[ NR; Packet Data Convergence Protocol (PDCP) specification ] [29] is used. The Ethernet header compression configuration used for Ethernet header compression is (re-)negotiated between the UE and the SMF using the Ethernet header compression configuration IE as specified in subclauses 6.3.2.2, 6.4.1.2, 6.4.1.3 and 6.4.2.2, respectively. | 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.16 |
1,744 | – FrequencyInfoDL | The IE FrequencyInfoDL provides basic parameters of a downlink carrier and transmission thereon. FrequencyInfoDL information element -- ASN1START -- TAG-FREQUENCYINFODL-START FrequencyInfoDL ::= SEQUENCE { absoluteFrequencySSB ARFCN-ValueNR OPTIONAL, -- Cond SpCellAdd frequencyBandList MultiFrequencyBandListNR, absoluteFrequencyPointA ARFCN-ValueNR, scs-SpecificCarrierList SEQUENCE (SIZE (1..maxSCSs)) OF SCS-SpecificCarrier, ..., [[ referenceCell-r18 ServCellIndex OPTIONAL -- Cond SSBlessSCell ]] } -- TAG-FREQUENCYINFODL-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
1,745 | N.2 Enabling access to Localized Services N.2.1 General | To enable a PNI-NPN or SNPN to provide access to Localized Services, the PNI-NPN or SNPN operator configures the network with information enabling the UEs to access the Localized Services using the PNI-NPN or SNPN according to any validity of the Localized Services, and the information is determined in agreement with the Localized Service Provider e.g.: a. Identification of each Localized Service, e.g. to be used in URSP rules. b. validity restriction for each Localized Service, e.g. the validity of time and/or location. c. service parameters for each Localized Service, e.g. DNN, S-NSSAI and QoS requirements. d. service authorization methods, e.g. NSSAA or Secondary authentication/authorization during PDU Session establishment. To allow the UE to access the PNI-NPN providing access to Localized Services using credentials of the HPLMN, the PNI-NPN can be configured based on the Localized Service agreements between the PNI-NPN and the HPLMN, to allow primary authentication towards the HPLMN. To allow the UE to access the SNPN providing access to Localized Services using credentials of the Credentials Holder, the SNPN can be configured based on Localized Service agreements between the SNPN and the Credentials Holder, to allow primary authentication towards the Credentials Holder. To allow the UE to access the SNPN providing access to Localized Services when new credential is required, the SNPN can provide UE onboarding function as specified in clause 5.30.2.10 for the UE to obtain credential and necessary information to access the SNPN, or the UE can leverage existing credential and network connection to get access to a PVS via User Plane to obtain new credential. To allow the UE to access the PNI-NPN providing access to the Localized Services where NSSAA or secondary authentication/authorization during PDU session establishment is required, the UE can obtain new credential using remote provisioning functionality as defined in clause 5.39. To allow the UE to access the HPLMN or subscribed SNPN services while being registered in the PNI-NPN or SNPN, the PNI-NPN or SNPN can establish service agreements and configure inter-connect with the HPLMN or subscribed SNPN operator. If a PNI-NPN is providing access to the Localized Services, the existing roaming architecture with home-routed PDU Sessions are used. If an SNPN is providing access to the Localized Services, then the UE can access HPLMN or subscribed SNPN as described in Annex D, clauses D.3, D.6 and D.7. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | N.2 |
1,746 | 5.3.1.1 Establishment of the NAS signalling connection | When the UE is in EMM-IDLE mode without suspend indication and needs to transmit an initial NAS message, the UE shall request the lower layer to establish a RRC connection. In this request to the lower layer the NAS shall provide to the lower layer the RRC establishment cause and the call type as specified in annex D of this specification and, for the case specified in clause 5.6.1.2.2, shall also provide the initial NAS message, otherwise NAS may also provide the initial NAS message. Initial NAS messages are: - ATTACH REQUEST; - DETACH REQUEST; - TRACKING AREA UPDATE REQUEST; - SERVICE REQUEST; - EXTENDED SERVICE REQUEST; and - CONTROL PLANE SERVICE REQUEST. When the UE is in EMM-IDLE mode with suspend indication, the UE shall proceed the behaviour as specified in clauses 5.3.1.3. For the routing of the initial NAS message to the appropriate MME, the UE NAS provides the lower layers with either the S-TMSI, the registered globally unique MME identifier (GUMMEI) that consists of the PLMN ID, the MME group ID, and the MME code (see 3GPP TS 23.003[ Numbering, addressing and identification ] [2]), or none of them according to the following rules: - If the UE has received the interworking without N26 interface indicator set to "interworking without N26 interface not supported" from the network, the UE holds a valid 5G-GUTI and: a) the UE performs an initial EPS attach procedure or tracking area updating procedure following an inter-system change from N1 mode to S1 mode; or b) the UE which was previously registered in N1 mode before entering state 5GMM-DEREGISTERED, performs an initial EPS attach procedure, then the UE NAS shall provide the lower layers with the MME identifier part of the mapped GUTI, which is generated from the 5G-GUTI as specified in 3GPP TS 23.003[ Numbering, addressing and identification ] [4], an indication that the identifier is a native GUMMEI and an indication that the identifier is mapped from 5GS; - If the TIN indicates "GUTI" or "RAT-related TMSI", or the TIN is not available, and the UE holds a valid GUTI: a) When the UE in EMM-IDLE mode initiates a tracking area updating or combined tracking area updating procedure for load balancing purposes, the UE NAS shall provide the lower layers with neither S-TMSI nor registered MME identifier; b) When the tracking area of the current cell is in the list of tracking areas that the UE previously registered in the MME during the NAS signalling connection establishment, the UE NAS shall provide the lower layers with the S-TMSI, but shall not provide the registered MME identifier to the lower layers; or c) When the tracking area of the current cell is not in the list of tracking areas that the UE previously registered in the MME during the NAS signalling connection establishment, the UE NAS shall provide the lower layers with the MME identifier part of the valid GUTI with an indication that the identifier is a native GUMMEI. - If the TIN indicates "P-TMSI", or the TIN is not available, and the UE holds a valid P-TMSI and RAI, the UE NAS shall provide the lower layers with the MME identifier part of the mapped GUTI, which is generated from the P-TMSI and RAI with an indication that the identifier is a mapped GUMMEI; or - Otherwise, the UE NAS does not provide the lower layers with the S-TMSI, the registered GUMMEI and the mapped GUMMEI. The UE NAS also provides the lower layers with the identity of the selected PLMN (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]). In a shared network, the UE shall choose one of the PLMN identities as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. When an ATTACH REQUEST message, or a TRACKING AREA UPDATE REQUEST message when the current TAI of the current cell is not included in the TAI list, is sent to establish a signalling connection, the UE NAS also provides the lower layers with the DCN-ID according to the following rules: a) if a DCN-ID for the PLMN code of the selected PLMN is available in the UE, the UE NAS shall provide this DCN-ID to the lower layers; or b) if no DCN-ID for the PLMN code of the selected PLMN is available but a Default_DCN_ID value is available in the UE, as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] or in USIM file NASCONFIG as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17], the UE NAS shall provide this DCN-ID to the lower layers. If a relay node is attaching for relay node operation (see 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10]), the NAS in the relay node shall indicate to the lower layers that the establishment of the NAS signalling connection is for a relay node. If a UE operating as an IAB-node performs an attach procedure, tracking area updating procedure, or service request procedure (see 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10]), the UE NAS shall indicate to the lower layers that the establishment of the NAS signalling connection is for a UE operating as an IAB-node. In S1 mode, when the RRC connection has been established successfully, the UE shall enter EMM-CONNECTED mode and consider the NAS signalling connection established. In S101 mode, when the cdma2000® HRPD access network resources are available for tunnelled NAS signalling, the UE shall enter EMM-CONNECTED mode and consider the S101 mode NAS signalling connection established. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.3.1.1 |
1,747 | 4.2 Frame structure type 2 | Frame structure type 2 is applicable to TDD only. Each radio frame of length consists of two half-frames of length each. Each half-frame consists of five subframes of length. Each subframe is defined as two slots, and, of length each. Subframe in frame has an absolute subframe number where is the system frame number. The uplink-downlink configuration in a cell may vary between frames and controls in which subframes uplink or downlink transmissions may take place in the current frame. The uplink-downlink configuration in the current frame is obtained according to Clause 13 in [4]. The supported uplink-downlink configurations are listed in Table 4.2-2 where, for each subframe in a radio frame, "D" denotes a downlink subframe reserved for downlink transmissions, "U" denotes an uplink subframe reserved for uplink transmissions and "S" denotes a special subframe with the three fields DwPTS, GP and UpPTS. The length of DwPTS and UpPTS is given by Table 4.2-1 subject to the total length of DwPTS, GP and UpPTS being equal to where X is the number of additional SC-FDMA symbols in UpPTS provided by the higher layer parameter srs-UpPtsAdd if configured otherwise X is equal to 0. The UE is not expected to be configured with 2 additional UpPTS SC-FDMA symbols for special subframe configurations {3, 4, 7, 8} for normal cyclic prefix in downlink and special subframe configurations {2, 3, 5, 6} for extended cyclic prefix in downlink and 4 additional UpPTS SC-FDMA symbols for special subframe configurations {1, 2, 3, 4, 6, 7, 8} for normal cyclic prefix in downlink and special subframe configurations {1, 2, 3, 5, 6} for extended cyclic prefix in downlink. Uplink-downlink configurations with both 5 ms and 10 ms downlink-to-uplink switch-point periodicity are supported. - In case of 5 ms downlink-to-uplink switch-point periodicity, the special subframe exists in both half-frames. - In case of 10 ms downlink-to-uplink switch-point periodicity, the special subframe exists in the first half-frame only. Subframes 0 and 5 and DwPTS are always reserved for downlink transmission. For special subframe configurations 1, 2, 3, 4, 6, 7 and 8, DwPTS is split into two parts, of which the first part is a slot and the second part is of X-symbol duration within the second slot. Downlink subframes, downlink slots in the downlink subframe and DwPTS, and the X–symbol duration in the second slot of DwPTS are available for downlink transmission. The X-symbol transmission opportunity is only available for special subframe configuration 3,4 and 8. UpPTS and the subframe immediately following the special subframe are always reserved for uplink transmission. Uplink subframes, uplink slots and UpPTS with special subframe configuration 10 are available for uplink transmission. Note that UpPTS with special subframe configuration 10 are not available for SPUCCH transmission. In case multiple cells are aggregated, the UE may assume that the guard period of the special subframe in the cells using frame structure type 2 have an overlap of at least . In case multiple cells with different uplink-downlink configurations in the current radio frame are aggregated and the UE is not capable of simultaneous reception and transmission in the aggregated cells, the following constraints apply: - if the subframe in the primary cell is a downlink subframe, the UE shall not transmit any signal or channel on a secondary cell in the same subframe - if the subframe in the primary cell is an uplink subframe, the UE is not expected to receive any downlink transmissions on a secondary cell in the same subframe - if the subframe in the primary cell is a special subframe and the same subframe in a secondary cell is a downlink subframe, the UE is not expected to receive PDSCH/EPDCCH/PMCH/PRS transmissions in the secondary cell in the same subframe, and the UE is not expected to receive any other signals on the secondary cell in OFDM symbols that overlaps with the guard period or UpPTS in the primary cell. For frame structure type 2, the higher-layer parameters for symbol-level resource reservation for BL/CE UEs (symbolBitmap1 and symbolBitmap2) do not apply to special subframes. Figure 4.2-1: Frame structure type 2 (for 5 ms switch-point periodicity) Table 4.2-1: Configuration of special subframe (lengths of DwPTS/GP/UpPTS) Table 4.2-2: Uplink-downlink configurations | 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.2 |
1,748 | 5.34.6.2 N4 information sent from SMF to I-SMF for local traffic offload | The SMF generates N4 information for local traffic offload based on the available DNAI(s) indicated by the I-SMF, PCC rules associated with these DNAI(s) and charging requirement. This N4 information is sent from the SMF to the I-SMF after UL CL/Branching Point insertion/update/removal, and the I-SMF uses this N4 information to derive rules installed in the UPFs controlled by the I-SMF. The N4 information for local traffic offload corresponds to rules and parameters defined in clause 5.8.5, i.e. PDR, FAR, URR and QER. It contains identifiers allowing the SMF to later modify or delete these rules. N4 information for local traffic offload is generated by the SMF without knowledge of how many local UPF(s) are actually used by the I-SMF. The SMF indicates whether a rule within N4 information is enforced in UL CL/ Branching Point or local PSA. If the rule is applied to the local PSA, the N4 information includes the associated DNAI. The I-SMF generates suitable rules for the UPF(s) based on the N4 information received from SMF. NOTE: The SMF is not aware of whether there is a single PSA or multiple PSA controlled by I-SMF. The following parameters are managed by the I-SMF: - The 5G AN Tunnel Info. - CN tunnel info between local UPFs. - Network instance (if needed). The N4 information exchanged between I-SMF and SMF are not associated with a N4 Session ID but are associated with an N16a association allowing the SMF to modify or delete the N4 information at a later stage. The I-SMF generates an N4 Session ID and for each rule a Rule ID (unless the ones received from the SMF can be used) and maintains a mapping between the locally generated identifiers and the ones received from the SMF. The I-SMF replaces those IDs in the PDR(s), QER(s), URR(s) and FAR(s) received from the SMF. When the I-SMF receives the N4 information, the Network instance (if needed) included in the rules sent to the UPF is generated by I-SMF. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.34.6.2 |
1,749 | 4.15.6.2 NEF service operations information flow | Figure 4.15.6.2-1: Nnef_ParameterProvision_Create / Nnef_ParameterProvision_Update / Nnef_ParameterProvision_Delete request/response operations 0. NF subscribes to UDM notifications of UE and/or Group Subscription data updates. In the UDM subscription, the NF may request to be notified about expected UE behaviour parameter(s) in Table 4.15.6.3-1 or Application-Specific Expected UE Behaviour parameter(s) in Table 4.15.6.3f-1 that may have been externally provisioned by an AF. NOTE 1: The NF can subscribe to Group Subscription data from UDM in this step and be notified of Group Subscription data updates in step 7 using the Shared Data feature defined in TS 29.503[ 5G System; Unified Data Management Services; Stage 3 ] [52]. NOTE 2: The external parameters in Table 4.15.6.3-1 may be provisioned by an AF hosting an AI/ML based application. If an expected UE behaviour parameter subscription is provided by the NF, the subscription may include a threshold indicating that certain confidence and/or accuracy levels must be met for the parameter(s) to be notified by the UDM to the NF. Meeting the threshold condition may mean that the confidence and/or accuracy levels of a parameter are equal to certain threshold, or less than certain threshold, or greater than certain threshold, or less than or equal to certain threshold, or greater than or equal to certain threshold. The threshold may be in the form of a range (e.g. minimum value to maximum value, where each may be inclusive or exclusive) or a specific value. NOTE 3: The threshold may be used to e.g. prevent certain Expected UE Behaviour parameters from being stored in the network when certain minimum level of confidence and/or accuracy are not met. NOTE 4: Confidence level indicates a probability assertion for the associated Expected UE Behaviour parameter and accuracy level indicates the performance of the estimator (e.g. AI/ML model) used for the prediction. 0b. [Conditional, on using NWDAF-assisted values] The AF may subscribe to NWDAF via NEF in order to learn the UE mobility analytics and/or UE Communication analytics for a UE or group of UEs by applying the procedure specified in clause 6.1.1.2 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]. The Analytics ID is set to any of the values specified in clause 6.7.1 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]. 0c. [Conditional, on using NWDAF-assisted values] AF validates the received data and derives any of the Expected UE behaviour parameters defined in clause 4.15.6.3 for a UE or group of UEs. 1. The AF provides one or more parameter(s) to be created or updated, or deleted in a Nnef_ParameterProvision_Create or Nnef_ParameterProvision_Update or Nnef_ParameterProvision_Delete Request to the NEF. The parameters(s) may include corresponding confidence and/or accuracy levels. The AF provides target UE identifier (e.g. GPSI or External Group ID) as described in clause 5.2.6.4. The Transaction Reference ID identifies the transaction request between NEF and AF. For the case of Nnef_ParameterProvision_Create, The NEF assigns a Transaction Reference ID to the Nnef_ParameterProvision_Create request. NEF checks whether the requestor is allowed to perform the requested service operation by checking requestor's identifier (i.e. AF Identifier). NOTE 5: When multiple AF parameter provisioning Create or Update requests with different values of the same Expected UE Behaviour parameters are received from different AFs, the network behaviour is unspecified. For a Create request associated with a 5G VN group, the External Group ID identifies the 5G VN Group. The payload of the Nnef_ParameterProvision_Update Request includes one or more of the following parameters: - Expected UE Behaviour parameters (see clause 4.15.6.3); or - Network Configuration parameters (see clause 4.15.6.3a); or - 5G VN group data (i.e. 5G VN configuration parameters) (see clause 4.15.6.3b), or - 5G VN group membership management parameters (see clause 4.15.6.3c); or - Location Privacy Indication parameters of the "LCS privacy" Data Subset of the Subscription Data (see clause 5.2.3.3.1 and clause 7.1 of TS 23.273[ 5G System (5GS) Location Services (LCS); Stage 2 ] [51]); or - MTC Provider Information; or - AF provided ECS Address Configuration Information (see clause 4.15.6.3d); or - DNN and S-NSSAI specific Group Parameters (see clause 4.15.6.3e); or - Application-Specific Expected UE Behaviour parameters (see clause 4.15.6.3f). The AF may request to delete 5G VN configuration by sending Nnef_ParameterProvision_Delete to the NEF. 2. If the AF is authorised by the NEF to provision the parameters, the NEF requests to create, update and store, or delete the provisioned parameters as part of the subscriber data via Nudm_ParameterProvision_Create, Nudm_ParameterProvision_Update or Nudm_ParameterProvision_Delete Request message, the message includes the provisioned data and NEF reference ID and optionally MTC Provider Information. If the AF is not authorised to provision the parameters, then the NEF continues in step 6 indicating the reason to failure in Nnef_ParameterProvision_Create/Update/Delete Response message. Step 7 does not apply in this case. If the NEF did not receive DNN and/or S-NSSAI from the AF and such information is configured as needed within 5GC, the NEF determines the DNN and/or S-NSSAI from the AF Identifier. If the AF provides the DNN and S-NSSAI specific Group Parameters, the AF shall indicate the External Group ID, targeted DNN and S-NSSAI in the request. If the AF provides the service area in the form of geographical information, the NEF maps the geographical information to the list of TAs. NOTE 6: For non-roaming case and no authorisation or validation by the UDM required and if the request is not associated with a 5G VN group, the NEF can directly forward the external parameter to the UDR via Nudr_DM_Update Request message. And in this case, the UDR responds to NEF via Nudr_DM_Update Response message. 3. UDM may read from UDR, by means of Nudr_DM_Query, corresponding subscription information in order to validate required data updates and authorize these changes for this subscriber or Group for the corresponding AF. Based on local configuration, UDM may determine if there is any requirement in terms of threshold conditions that need to be met by the provisioned parameter before storing the parameter in UDR. If there are no such requirement(s) or the requirement(s) are satisfied, UDM may proceed seamlessly. If not satisfied, step 5 is triggered as a failed procedure and a related cause value is provided, e.g. "confidence level not sufficient". In that case step 4 is skipped. 4. If the AF is authorised by the UDM to provision the parameters for this subscriber, the UDM resolves the GPSI to SUPI and requests to create, update or delete the provisioned parameters as part of the subscriber data via Nudr_DM_Create/Update/Delete Request message, the message includes the provisioned data. If a new 5G VN group is created, the UDM shall assign a unique Internal Group ID for the 5G VN group and include the newly assigned Internal Group ID in the Nudr_DM_Create Request message. If the list of 5G VN group members is changed or if 5G VN group data has changed, the UDM updates the UE and/or Group subscription data according to the AF/NEF request. When the service area is configured or updated for a group, the UDM authorises the request. If the Default QoS is configured or updated for a group, the UDM authorises the request and uses such Default QoS to set 5GS Subscribed QoS profile in Session Management Subscription data for each UE within the group. The 5GS Subscribed QoS profile in Session Management Subscription data will be considered by SMF as described in clause 5.7.2.7 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. UDR stores the provisioned data as part of the UE and/or Group subscription data and responds with Nudr_DM_Create/Update/Delete Response message. If the Maximum Group Data Rate is configured or updated for a 5G VN group, the UDM authorises the request and the Maximum Group Data Rate is applied as described in clause 5.29.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. When the 5G VN group data (as described in clause 4.15.6.3b) or 5G VN group membership is updated, the UDR notifies to the subscribed PCF by sending Nudr_DM_Notify as defined in clause 4.16.12.2. If the AF is not authorised to provision the parameters, then the UDM continues in step 5 indicating the reason to failure in Nudm_ParameterProvision_Update Response message and step 7 is not executed. The UDM classifies the received parameters (i.e. Expected UE Behaviour parameters or Suggested Number of Downlink Packets or the 5G VN configuration parameters or DNN and S-NSSAI specific Group Parameters or Location Privacy Indication parameters or ECS Address Configuration Information), into AMF associated and SMF associated parameters. The UDM may use the AF Identifier received from the NEF in step 2 to relate the received parameter with a particular subscribed DNN and/or S-NSSAI. The UDM stores the SMF-Associated parameters under corresponding Session Management Subscription data type. Each parameter or parameter set may be associated with a validity time. The validity time is stored at the UDM/UDR and in each of the NFs, to which parameters are provisioned (e.g. in AMF or SMF). Upon expiration of the validity time, each node deletes the parameters autonomously without explicit signalling. If the ECS Address Configuration Information is provided to any UE in AF request, the UDM shall make use of the shared data mechanism defined in TS 29.503[ 5G System; Unified Data Management Services; Stage 3 ] [52] and notify all NFs (SMFs) that have subscribed to receiving such shared data change notifications. 5. UDM responds the request with Nudm_ParameterProvision_Create/Update/Delete Response. If the procedure failed, the cause value indicates the reason. 6. NEF responds the request with Nnef_ParameterProvision_Create/Update/Delete Response. If the procedure failed, the cause value indicates the reason. NOTE 7: If AF receives a failure update notification due to threshold conditions not met and AF does not want NFs to keep using the old parameters, then AF can send an Nnef_ParameterProvision_Delete request. 7. [Conditional this step occurs only after successful step 4] UDM notifies the subscribed Network Function of the updated UE and/or Group subscription data via Nudm_SDM_Notification Notify message. a) If the subscribed NF is AMF, the UDM performs Nudm_SDM_Notification (SUPI or Internal Group Identifier, AMF-Associated Expected UE Behaviour parameters, Subscribed Periodic Registration Timer, subscribed Active Time, 5G VN group data or DNN and S-NSSAI specific Group Parameters, etc.) service operation. If the AMF receives confidence and/or accuracy levels along the Expected UE behaviour parameter(s), the AMF may use the associated confidence level and/or accuracy level when handling the expected UE behaviour parameter(s). The AMF uses the received parameters to derive the appropriate UE configuration of the NAS parameters and to derive Core Network assisted RAN parameters. The AMF may determine a Registration area based on parameters Stationary indication or Expected UE Moving Trajectory. If the AMF obtains service area for a group or SUPI, the AMF configures the DNN for the group as LADN DNN and applies the LADN per DNN and S-NSSAI taking into account the service area for the group as described in clause 5.6.5a of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. b) If the subscribed NF is SMF, the UDM performs Nudm_SDM_Notification (SUPI or Internal Group Identifier, SMF-Associated Expected UE Behaviour parameter set, DNN/S-NSSAI, Suggested Number of Downlink Packets, 5G VN group data, etc.) service operation. The SMF stores the received parameters and associates them with a PDU Session based on the DNN and S-NSSAI included in the message from UDM. If the SMF receives confidence and/or accuracy levels along the Expected UE behaviour parameter(s), the SMF may use the associated confidence level and/or accuracy level when handling the expected UE behaviour parameter(s). The SMF may use the parameters as follows: - SMF configures the UPF accordingly. The SMF can use the Scheduled Communication Type parameter or Suggested Number of Downlink Packets parameter to configure the UPF with how many downlink packets to buffer. The SMF may use Communication duration time parameter and/or Expected Inactivity Time parameter and/or Battery Indication parameter combined with their confidence and/or accuracy levels to set the inactivity timer for a PDU Session. The SMF then waits for a UP inactivity report to be received from UPF. Based on the received UP inactivity report, the SMF may determine to deactivate the corresponding UP connection associated to the PDU Session of a single UE or determine a collective pattern of deactivating UP connections for multiple UEs (e.g. for a group of UEs receiving application AI/ML traffic during FL operation) and perform CN-initiated selective deactivation of UP connection of an existing PDU Session. - The SMF may derive SMF derived CN assisted RAN information for the PDU Session. The SMF provides the SMF derived CN assisted RAN information to the AMF as described in PDU Session establishment procedure or PDU Session modification procedure. NOTE 8: The NEF (in NOTE 1) or the UDM (in step 3) can also update the corresponding UDR data via Nudr_DM_Create/Delete as appropriate. NOTE 9: The change of AF provided ECS configuration information is not meant to apply immediately: the UDM interface to the SMF can refer to Shared Data for the Subscription provided ECS configuration information. NOTE 10: Specification details of confidence and accuracy levels are left to Stage 3 work. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.6.2 |
1,750 | 6.4.3.3 EPS bearer context modification accepted by the UE | Upon receipt of the MODIFY EPS BEARER CONTEXT REQUEST message, if the UE provided an APN for the establishment of the PDN connection, the UE shall stop timer T3396, if it is running for the APN provided by the UE. If the UE did not provide an APN for the establishment of the PDN connection and the request type was different from "emergency" and from "handover of emergency bearer services", the UE shall stop the timer T3396 associated with no APN if it is running. If the MODIFY EPS BEARER CONTEXT REQUEST message was received for an emergency PDN connection, the UE shall not stop the timer T3396 associated with no APN if it is running. For any case, the UE shall then check the received TFT before taking it into use and send a MODIFY EPS BEARER CONTEXT ACCEPT message to the MME. If the MODIFY EPS BEARER CONTEXT REQUEST message contains a PTI value other than "no procedure transaction identity assigned" and "reserved" (see 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [12]), the UE uses the PTI to identify the UE requested bearer resource allocation procedure or the UE requested bearer resource modification procedure to which the EPS bearer context modification is related (see clause 6.5.3 and clause 6.5.4). If the MODIFY EPS BEARER CONTEXT REQUEST message contains a PTI value other than "no procedure transaction identity assigned" and "reserved" (see 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [12]) and the PTI is associated to a UE requested bearer resource allocation procedure or a UE requested bearer resource modification procedure, the UE shall release the traffic flow aggregate description associated to the PTI value provided. If the EPS bearer context that is modified is a GBR bearer and the MODIFY EPS BEARER CONTEXT REQUEST message does not contain the Guaranteed Bit Rate (GBR) and the Maximum Bit Rate (MBR) values for uplink and downlink, the UE shall continue to use the previously received values for the Guaranteed Bit Rate (GBR) and the Maximum Bit Rate (MBR) for the corresponding bearer. The UE shall use the received TFT to apply mapping of uplink traffic flows to the radio bearer if the TFT contains packet filters for the uplink direction. If a WLAN offload indication information element is included in the MODIFY EPS BEARER CONTEXT REQUEST message, the UE shall store the WLAN offload acceptability values for this PDN connection and use the E-UTRAN offload acceptability value to determine whether this PDN connection is offloadable to WLAN or not. If the UE receives an APN rate control parameters container in the Protocol configuration options IE or Extended protocol configuration options IE in the MODIFY EPS BEARER CONTEXT REQUEST message, the UE shall store the APN rate control parameters value and use the stored APN rate control parameters value as the maximum allowed limit of uplink user data related to the corresponding APN in accordance with 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10]. If the UE has a previously stored APN rate control parameters value for this APN, the UE shall replace the stored APN rate control parameters value for this APN with the received APN rate control parameters value. If the UE receives an additional APN rate control parameters for exception data container in the Protocol configuration options IE or Extended protocol configuration options IE in the MODIFY EPS BEARER CONTEXT REQUEST message, the UE shall store the additional APN rate control parameters for exception data value and use the stored additional APN rate control parameters for exception data value as the maximum allowed limit of uplink exception data related to the corresponding APN in accordance with 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10]. If the UE has a previously stored additional APN rate control parameters for exception data value for this APN, the UE shall replace the stored additional APN rate control parameters for exception data value for this APN with the received additional APN rate control parameters for exception data value. If the UE receives a small data rate control parameters container in the Protocol configuration options IE or the Extended protocol configuration options IE in the MODIFY EPS BEARER CONTEXT REQUEST message, the UE shall store the small data rate control parameters value and use the stored small data rate control parameters value as the maximum allowed limit of uplink user data for the corresponding PDU session that becomes transferred after inter-system change from S1 mode to N1 mode in accordance with 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [58]. If the UE has a previously stored small data rate control parameters value for this PDU session, the UE shall replace the stored small data rate control parameters value for this PDU Session with the received small data rate control parameters value. If the UE receives an additional small data rate control parameters for exception data container in the Protocol configuration options IE or the Extended protocol configuration options IE in the MODIFY EPS BEARER CONTEXT REQUEST message, the UE shall store the additional small data rate control parameters for exception data value and use the stored additional small data rate control parameters for exception data value as the maximum allowed limit of uplink exception data for the corresponding PDU session that becomes transferred after inter-system change from S1 mode to N1 mode in accordance with 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [58]. If the UE has a previously stored additional small data rate control parameters for exception data value for this PDU session, the UE shall replace the stored additional small data rate control parameters for exception data value for this PDU session with the received additional small data rate control parameters for exception data value. Upon receipt of the MODIFY EPS BEARER CONTEXT REQUEST message with a session-AMBR and QoS rule(s) in the Protocol configuration options IE or the Extended protocol configuration options IE, the UE stores the session-AMBR and QoS rule(s) for use during inter-system change from S1 mode to N1 mode. If the UE receives the MODIFY EPS BEARER CONTEXT REQUEST message containing the Uplink data allowed parameter in the Extended protocol configuration options IE, then the UE may start transmitting uplink user data over EPS bearer context(s) of the corresponding PDN connection. The MODIFY EPS BEARER CONTEXT REQUEST message as a part of authorization procedure for the C2 communication, can include an Extended protocol configuration options IE containing the service-level-AA container with the length of two octets. The service-level-AA container with the length of two octets: a) contains the service-level-AA response with the C2AR field set to the C2 authorization result informed by the UAS NF; b) can contain the service-level-AA payload parameter set to the C2 authorization payload and the service-level-AA payload type parameter set to "C2 authorization payload"; and c) can contain the service-level device ID with the value set to a new CAA-level UAV ID. NOTE 1: The C2 authorization payload in the service-level-AA payload can include one, some or all of the pairing information for C2 communication, the C2 session security information, and the pairing information for direct C2 communication. If the EPS bearer context being modified is associated with a PDN connection for UAS services and the MODIFY EPS BEARER CONTEXT REQUEST message includes the service-level-AA container with the length of two octets in the Extended protocol configuration options IE, the UE supporting UAS services shall forward the contents of the service-level-AA container with the length of two octets to the upper layers. If the EPS bearer context being modified is associated with a PDN connection for UAS services, the MODIFY EPS BEARER CONTEXT REQUEST message includes the Extended protocol configuration options IE containing the service-level-AA container with the length of two octets containing the service-level-AA response parameter with the SLAR field set to "Service level authentication and authorization was successful", the UE supporting UAS services: a) shall consider the UUAA procedure as successfully completed and provide the service-level-AA response to the upper layers; b) if the service-level-AA container with the length of two octets contains the service-level device ID parameter carrying a CAA-level UAV ID, shall provide the CAA-level UAV ID to the upper layers; and c) if the service-level-AA container with the length of two octets contains the service-level-AA payload type parameter with the value "UUAA payload" and the service-level-AA payload parameter carrying the UUAA payload, shall provide the UUAA payload to the upper layers. Upon reception of a service-level-AA payload from the upper layers, the UE supporting UAS services shall include the Extended protocol configuration options IE in the MODIFY EPS BEARER CONTEXT ACCEPT message. In the Extended protocol configuration options IE, the UE shall include the service-level-AA container with the length of two octets. In the service-level-AA container with the length of two octets, the UE shall: a) include the service-level-AA payload parameter set to the service-level-AA payload received from the upper layers; and b) set the service-level-AA payload type parameter to the type of the service-level-AA payload. Upon receipt of the MODIFY EPS BEARER CONTEXT REQUEST message, if the SDNAEPC EAP message with the length of two octets is included in the Extended protocol configuration options IE, the UE supporting secondary DN authentication and authorization over EPC shall forward the SDNAEPC EAP message with the length of two octets to the upper layers. Upon reception of an SDNAEPC EAP message with the length of two octets from the upper layers and if the UE has received an SDNAEPC EAP message with the length of two octets included in the Extended protocol configuration options IE of the MODIFY EPS BEARER CONTEXT REQUEST message from the network, the UE supporting secondary DN authentication and authorization over EPC shall include the Extended protocol configuration options IE in the MODIFY EPS BEARER CONTEXT ACCEPT message and include the SDNAEPC EAP message with the length of two octets in the Extended protocol configuration options IE. If the UE supports provisioning of ECS configuration information to the EEC in the UE, then upon receiving: - at least one of ECS IPv4 address(es), ECS IPv6 address(es), ECS FQDN(s); - at least one associated ECSP identifier; and - optionally spatial validity conditions associated with the ECS address in the Extended protocol configuration options IE of the MODIFY EPS BEARER CONTEXT REQUEST message, the UE shall pass them to the upper layers. NOTE 2: The IP address(es) and/or FQDN(s) are associated with the ECSP identifier and replace previously provided ECS configuration information associated with the same ECSP identifier, if any. Upon receipt of the MODIFY EPS BEARER CONTEXT REQUEST message, if the UE indicated the URSP provisioning in EPS support indicator as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] in the UE requested PDN connectivity procedure establishing the PDN connection, and the UE policy container with the length of two octets as defined in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] is included in the Extended protocol configuration options IE of the MODIFY EPS BEARER CONTEXT REQUEST message: a) the UE shall forward the UE policy container with the length of two octets to the UE policy delivery service (see 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] annex D); and b) upon receipt of a UE policy container with the length of two octets from the UE policy delivery service, the UE shall include the UE policy container with the length of two octets from the UE policy delivery service in the Extended protocol configuration options IE of the MODIFY EPS BEARER CONTEXT ACCEPT message. Editor's note: (WI: eUEPO, CR: 3934) URSP provisioning in EPS in a PDN connection interworked from a PDU session, is FFS. Upon receipt of the MODIFY EPS BEARER CONTEXT ACCEPT message, the MME shall stop the timer T3486 and enter the state BEARER CONTEXT ACTIVE. | 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.4.3.3 |
1,751 | 5.30.2.12 Access to SNPN services via Untrusted non-3GPP access | Access to SNPN services via Untrusted non-3GPP access network follows the specification in the previous 5.30.2 clauses with the differences as specified in this clause. N3IWF selection is supported as follows: - When UE registers to SNPN with credentials owned by the SNPN, UE uses the same N3IWF selection procedure as specified for access to stand-alone non-public network services via PLMN in clause 6.3.6.2a. Emergency services are supported as follows: - UE initiates N3IWF selection for emergency services when the UE detects a user request for emergency session and determines that Untrusted non-3GPP access is to be used for the emergency access. The UE in SNPN access mode the following: - If the UE determines that it is located in the same country as the configured N3IWF of the subscribed SNPN, the UE uses the configured N3IWF FQDN for N3IWF selection. - Otherwise, the UE performs a DNS query using the Visited Country Emergency SNPN FQDN, as specified in clause 28.3.2.2.6.3 of TS 23.003[ Numbering, addressing and identification ] [19] to determine which SNPNs in the visited country support emergency services in untrusted non-3GPP access via N3IWF; and: - If the DNS response contains one or more records, the UE selects an SNPN that supports emergency services in untrusted non-3GPP access via N3IWF based on UE implementation specific methods. Each record in the DNS response shall contain the identity of an SNPN (i.e. SNPN ID) in the visited country supporting emergency services in untrusted non-3GPP access via N3IWF. NOTE 1: Self-assigned NIDs are not supported, since a DNS cannot be properly configured for multiple SNPNs using the same self-assigned NID (i.e. in collision scenarios). - Once the UE has selected an SNPN, the UE selects an N3IWF for Emergency for the selected SNPN, as specified in TS 23.003[ Numbering, addressing and identification ] [19]. When an N3IWF has been selected, the UE initiates an Emergency Registration. If the Emergency Registration fails, the UE shall select another SNPN supporting emergency services in untrusted non-3GPP access. If the DNS response of the Visited Country Emergency SNPN FQDN does not contain any record, or if the DNS response contains one or more records but the UE fails to select an SNPN that supports emergency services in untrusted non-3GPP access, or if the Emergency Registration procedure has failed for all SNPNs supporting emergency services in untrusted non-3GPP access, the UE deactivates the SNPN access mode over NWu and attempts emergency services via PLMN untrusted non-3GPP access, by following the N3IWF selection procedure as defined in clause 6.3.6.4.2. NOTE 2: If the UE determines that it is located in a different country as the configured N3IWF of the subscribed SNPN, the UE can deactivate the SNPN access mode over NWu and attempts emergency services via PLMN untrusted non-3GPP access, by following the N3IWF selection procedure defined in clause 6.3.6.4.2, without performing a DNS query using the Visited Country Emergency SNPN FQDN. UE onboarding is supported as follows: - When UE registers to SNPN over Untrusted non-3GPP access for UE Onboarding, if the UE determines that it is located in the country where the configured N3IWF for onboarding is located, the UE may select the N3IWF in the SNPN which supports UE Onboarding by using the configured N3IWF FQDN used for Onboarding. - If the UE determines that it is located in a country different from the country where the configured N3IWF for onboarding is located (called the visited country), then in order to determine which SNPNs in the visited country support Untrusted non-3GPP access for UE Onboarding via N3IWF performs a DNS query using the Visited Country FQDN for SNPN N3IWF supporting Onboarding, as specified in clause 28.3.2.2.6.2 of TS 23.003[ Numbering, addressing and identification ] [19]; and: - If no DNS response is received, the UE shall stop the N3IWF selection. - If the DNS response contains one or more records, the UE selects an SNPN that supports Untrusted non-3GPP access for UE Onboarding via N3IWF. Each record in the DNS response shall contain the identity of an SNPN in the visited country supporting Untrusted non-3GPP access for UE Onboarding via N3IWF. In this case: - The UE shall select an SNPN based on its own implementation means. If the UE cannot select any N3IWF included in the DNS response, then the UE shall stop the N3IWF selection. - If the DNS response contains no records, then the UE determines that the visited country does not mandate the selection of an N3IWF that supports Untrusted non-3GPP access for UE Onboarding via N3IWF in this country. In this case the UE uses the configured N3IWF for onboarding. - If the UE has selected an SNPN for onboarding, the UE constructs the Operator Identifier based Onboarding FQDN for SNPN N3IWF as specified in clause 28.3.2.2.7.2 of TS 23.003[ Numbering, addressing and identification ] [19], based on the SNPN ID of the selected SNPN and performs a DNS query: - The DNS response contains the identifier of the N3IWF supporting the onboarding in the SNPN identified by the SNPN ID. - If the PVS is reachable from the local Untrusted non-3GPP access network (e.g. via the Internet) using the local IP connectivity, UE may connect directly (i.e. without being connected to an N3WIF) with a PVS to obtain the SNPN credentials. - As part of UE registration via Untrusted non-3GPP access, in Figure 4.12.2.2-1, step 5 of TS 23.502[ Procedures for the 5G System (5GS) ] [3], the UE provides an onboarding indication inside the AN-Parameters. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.30.2.12 |
1,752 | 5.33.3.3 GTP-U Path Measurement | The SMF can request to activate QoS monitoring for the GTP-U path(s) between all UPF(s) and the (R)AN based on locally configured policies. Alternatively, when a QoS monitoring policy is received in a PCC rule and the QoS monitoring is not yet active for the DSCP corresponding to the 5QI in the PCC rule, the SMF activates QoS Monitoring for all UPFs currently in use for this PDU Session and the (R)AN. In this case, the SMF performs the QoS Flow Binding without taking the QoS Monitoring Policy within the PCC rule into account. The SMF sends the QoS monitoring policy to each involved UPF and the (R)AN via N4 interface and via N2 interface respectively. NOTE 1: The PCC rule containing a QoS monitoring policy is just a trigger for the SMF to instruct the UPFs to initiate the GTP-U based QoS Monitoring. A GTP-U sender performs an estimation of RTT to a GTP-U receiver on a GTP-U path by sending Echo messages and measuring time that elapses between the transmission of Request message and the reception of Response message. A GTP-U sender computes an accumulated packet delay by adding RTT/2, the processing time and, if available, an accumulated packet delay from an upstream GTP-U sender (i.e. an immediately preceding GTP-U sender in user plane path) thus the measured accumulated packet delay represents an estimated elapsed time since a user plane packet entered 3GPP domain. It is expected that a GTP-U sender determines RTT periodically in order to detect changes in transport delays. QoS monitoring is performed by a GTP-U end-point (UP function) that receives, stores and executes the QoS monitoring policy as described below for a QoS Flow. QoS monitoring is performed by comparing a measured accumulated packet delay with the stored parameters. If the GTP-U end-point (the PSA UPF, in the case of accumulated packet delay reporting) determines that the packet delay exceeds the value of a stored parameter, then the node triggers QoS monitoring alert signalling to the relevant SMF or to the OA&M function as further described in TS 29.244[ Interface between the Control Plane and the User Plane nodes ] [65]. NOTE 2: Echo Request message and Echo Response message are sent outside GTP-U tunnels (the messages are using TEID set to 0). If underlying transport is using QoS differentiation (e.g. IP DiffServ) then it is up to the implementation to ensure that the Echo messages are classified correctly and receive similar treatment by the underlaying transport as GTP-U GTP-PDUs carrying QoS Flows (user data). When QoS Monitoring is used to measure the packet delay for a QoS Flow, the following applies: - Packet delay measurement is performed by using GTP-U Echo Request/Response as defined in the TS 28.552[ Management and orchestration; 5G performance measurements ] [108], in the corresponding user plane transport path(s), independent of the corresponding PDU Session and the 5QI for a given QoS Flow. - RAN measures and provides the RAN part of UL/DL packet delay towards UPF (in the GTP-U header of the respective QoS Flow via N3). - The UPF calculates the UL/DL packet delay by combining the received measurements of RAN part with the measurements of N3/N9 interface (N9 is applicable when I-UPF exists). - The UPF reports the QoS Monitoring results as described in clause 5.8.2.18. QoS Monitoring can also be used to measure the packet delay for transport paths to influence the mapping of QoS Flows to appropriate network instances, DSCP values as follows: - SMF activates QoS monitoring for the GTP-U path(s) between all UPF(s) and all (R)AN nodes based on locally configured policies. - UPF does measurement of network hop delay per transport resources that it will use towards a peer network node identified by an IP destination address (the hop between these two nodes) and port. The network hop measured delay is computed by sending an Echo Request over such transport resource (Ti) and measuring RTT/2 when Echo Response is received. - UPF maps {network instance, DSCP} into Transport Resource and measures delay per IP destination address and port. Thus, for each IP destination address, the measured delay per (network instance, DSCP) entry is determined. - The UPF performing the QoS monitoring can provide the corresponding {Network instance, DSCP} along with the measured accumulated packet delay for the corresponding transport path to the SMF. The UPF reports the measurement results to the SMF based on some specific conditions e.g. first time, periodic, event triggered, when thresholds for reporting towards SMF (via N4) are reached. - Based on this, SMF can determine QoS Flow mapping to the appropriate {Network instance, DSCP} considering {5QI, QoS characteristics, ARP} for the given QoS Flow. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.33.3.3 |
1,753 | 23.3.2.3.2 Certification Authority server | The Certification Authority server (CA/RA) FQDN shall be derived as follows. The "cara" <system> label is added in front of the operator's OAM realm domain name: cara.oam.mnc<MNC>.mcc<MCC>.3gppnetwork.org If particular operator deployment scenarios where there are multiple CA/RA servers (one per vendor), the <vendor ID> label is added in front of the "cara" label: vendor<ViD>.cara.oam.mnc<MNC>.mcc<MCC>.3gppnetwork.org An example of a CA/RA FQDN is: MCC = 123; MNC = 45; ViD = abcd; which gives the CA/RA FQDN: "cara.oam.mnc045.mcc123.3gppnetwork.org" and "vendorabcd.cara.mnc045.mcc123.3gppnetwork.org". | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 23.3.2.3.2 |
1,754 | 4.7.1.2a.4 Establishment of integrity protection of layer 3 signalling messages | Establishment of integrity protection of layer 3 signalling messages and optionally user plane data is done during the attach procedure. The MS shall indicate support for integrity protection in the MS network capability IE included in the ATTACH REQUEST message and the ROUTING AREA UPDATE REQUEST message to the network. When an MS sends an ATTACH REQUEST message or a ROUTING AREA UPDATE REQUEST message, then if the MS has no UMTS security context, it shall send the ATTACH REQUEST or the ROUTING AREA UPDATE REQUEST message without integrity protection to the network. If the network supports integrity protection, then the network activates integrity protection by initiating an authentication and ciphering procedure. The network selects an integrity algorithm among the supported integrity algorithms indicated by the MS in the MS network capability IE. After successful completion of the authentication and ciphering procedure, all layer 3 signalling messages sent between the MS and network are integrity protected in the LLC layer using the new UMTS security context. When an MS sends an ATTACH REQUEST message or a ROUTING AREA UPDATE REQUEST message, then if the MS has a UMTS security context, it shall send the ATTACH REQUEST or the ROUTING AREA UPDATE REQUEST message integrity protected with the current UMTS security context to the network. The MS shall include the CKSN indicating the current UMTS security context value in the initial ATTACH REQUEST message or a ROUTING AREA UPDATE REQUEST message. The MS shall use the integrity algorithm identified by the stored integrity algorithm identifier. The network shall check whether the CKSN included in the initial ATTACH REQUEST message or the ROUTING AREA UPDATE REQUEST message belongs to an UMTS security context available in the network, and if yes, then the network re-establishes integrity protection of layer 3 signalling messages in the LLC layer: - by replying with a GMM message (ATTACH ACCEPT or ROUTING AREA UPDATE ACCEPT) that is integrity protected in LLC layer by using the current UMTS security context. From this time onward, all layer 3 signalling messages exchanged between the MS and the network are sent integrity protected, except for the messages specified in subclause 4.7.1.2a; or - by initiating an authentication and ciphering procedure. This procedure can be used by the network to select a new integrity algorithm different from the one currently used by the MS. NOTE: Even if the message authentication code protecting the ATTACH REQUEST or the ROUTING AREA UPDATE message in the LLC layer cannot be verified in the network due to the integrity key and the integrity algorithm in the LLC layer at the network not having been configured yet for this MS, the network progresses the attach procedure and the routing atra updating procedure at the GMM layer anyway without having to run a new authentication and ciphering procedure if the network decides to re-use the same encryption- and integrity keys and the same ciphering and integrity algorithms and not run a re-authentication. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.1.2a.4 |
1,755 | 4.2.3 Reference points | S1-MME: Reference point for the control plane protocol between E-UTRAN and MME. S1-U: Reference point between E-UTRAN and Serving GW for the per bearer user plane tunnelling and inter eNodeB path switching during handover. S1-U does not apply to the Control Plane CIoT EPS Optimisation. S3: It enables user and bearer information exchange for inter 3GPP access network mobility in idle and/or active state. This reference point can be used intra-PLMN or inter-PLMN (e.g. in the case of Inter-PLMN HO). S4: It provides related control and mobility support between GPRS Core and the 3GPP Anchor function of Serving GW. In addition, if Direct Tunnel is not established, it provides the user plane tunnelling. S5: It provides user plane tunnelling and tunnel management between Serving GW and PDN GW. It is used for Serving GW relocation due to UE mobility and if the Serving GW needs to connect to a non-collocated PDN GW for the required PDN connectivity. S6a: It enables transfer of subscription and authentication data for authenticating/authorizing user access to the evolved system (AAA interface) between MME and HSS. Gx: It provides transfer of (QoS) policy and charging rules from PCRF to Policy and Charging Enforcement Function (PCEF) in the PDN GW. S8: Inter-PLMN reference point providing user and control plane between the Serving GW in the VPLMN and the PDN GW in the HPLMN. S8 is the inter PLMN variant of S5. S9: It provides transfer of (QoS) policy and charging control information between the Home PCRF and the Visited PCRF in order to support local breakout function. S10: Reference point between MMEs for MME relocation and MME to MME information transfer. This reference point can be used intra-PLMN or inter-PLMN (e.g. in the case of Inter-PLMN HO). S11: Reference point providing control plane between MME and Serving GW. In addition, in order to support Control Plane CIoT EPS Optimisation, the S11-U reference point provides user plane between MME and Serving GW. S12: Reference point between UTRAN and Serving GW for user plane tunnelling when Direct Tunnel is established. It is based on the Iu-u/Gn-u reference point using the GTP-U protocol as defined between SGSN and UTRAN or respectively between SGSN and GGSN. Usage of S12 is an operator configuration option. S13: It enables UE identity check procedure between MME and EIR. S17: It enables procedures for RACS between MME and UCMF. SGi: It is the reference point between the PDN GW and the packet data network. Packet data network may be an operator external public or private packet data network or an intra operator packet data network, e.g. for provision of IMS services. This reference point corresponds to Gi for 3GPP accesses. Rx: The Rx reference point resides between the AF and the PCRF in the TS 23.203[ Policy and charging control architecture ] [6]. NOTE 1: Except where stated otherwise, this specification does not make an explicit assumption as to whether an interface is intra-PLMN or inter-PLMN. When data forwarding is used as part of mobility procedures different user plane routes may be used based on the network configuration (e.g. direct or indirect data forwarding). These routes can be between eNodeB and RNC, eNodeB and SGSN, RNC and S-GW or between S-GW and SGSN. Explicit reference points are not defined for these routes. These user plane forwarding routes can cross inter-PLMN boundaries (e.g. in the case of Inter-PLMN HO). Protocol assumption: - The S1-U is based on GTP-U protocol; - The S3 is based on GTP protocol; - The S4 and S11 are based on GTP protocol; - The S5 is based on GTP protocol. PMIP variant of S5 is described in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [2]; - The S8 is based on GTP protocol. PMIP variant of S8 is described in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [2]. - S3, S4, S5, S8, S10 and S11 interfaces are designed to manage EPS bearers as defined in clause 4.7.2. NOTE 2: Redundancy support on reference points S5 and S8 should be taken into account. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2.3 |
1,756 | 5.12 Warning message delivery 5.12.1 General | Warning message delivery is similar to Cell Broadcast Service defined in TS 23.041[ Technical realization of Cell Broadcast Service (CBS) ] [48], it permits a number of unacknowledged Warning messages to be broadcast to UEs within a particular area. The maximum size of the Warning message for E-UTRAN is different from that of UTRAN/GERAN. When S1-flex is used, the eNodeB may receive duplicated Warning messages. For details on the Warning system message delivery, see TS 23.041[ Technical realization of Cell Broadcast Service (CBS) ] [48]. | 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.12 |
1,757 | F.2.1 Centralized CHF deployment | The architecture options depicted in Figure F.2.1-1 provides an overview of the availability of a CHF instance in a central location. On this case, the SMF generates the charging events through CTF towards the CHF either for a converged or offline charging scenario. The flow is detailed TS 32.255[ Telecommunication management; Charging management; 5G data connectivity domain charging; Stage 2 ] [15] clause 4.2. The main point to address is that all CCS components are available in the same physical location. Figure F.2.1-1: 5G data connectivity converged charging architecture | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | F.2.1 |
1,758 | 8.4 Authorization | The 5G system shall allow the operator to authorize an IoT device to use one or more 5G system features that are restricted to IoT devices. The 5G system shall allow the operator to authorize /de-authorize UEs for using 5G LAN-type service. NOTE: When a UE is de-authorized from using 5G LAN-type service, it is removed from all 5G LAN-VNs. Based on operator policy, before establishing a direct device connection using a non-3GPP access technology, IoT devices may use 3GPP credentials to determine if they are authorized to engage in direct device connection. Based on operator policy, the 5G system shall provide a means to verify whether a UE is authorized to use prioritized network access for a specific service. A 5G system with satellite access supporting S&F Satellite operation shall be able to support mechanisms to authorize a UE to use the S&F satellite operation. A 5G system with satellite access shall be able to support mechanisms to authorize the UE-Satellite-UE communication, based on e.g., location information and subscription. NOTE: UEs can use satellite access directly or via a relay UE (using satellite access assuming that the 5G system with satellite access is authorized to assign spectrum resources for the communication between remote UE and relay UE). | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 8.4 |
1,759 | 5.17 Data inactivity monitoring | The MAC entity may be configured by RRC with a Data inactivity monitoring functionality, when in RRC_CONNECTED. RRC controls Data inactivity operation by configuring the timer DataInactivityTimer. When DataInactivityTimer is configured, the MAC entity shall: - if the MAC entity receives the MAC SDU for DTCH logical channel , DCCH logical channel, or CCCH logical channel; or - if the MAC entity transmits the MAC SDU for DTCH logical channel, DCCH logical channel; - start or restart DataInactivityTimer. - if DataInactivityTimer expires, indicate the expiry of DataInactivityTimer to upper layers. | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.17 |
1,760 | 9.4.9.3 Authentication Parameter AUTN | This IE shall be present if and only if the authentication challenge is a UMTS authentication challenge.The presence or absence of this IE defines- in the case of its absence- a GSM authentication challenge or- in the case of its presence- a UMTS authentication challenge. The MS shall ignore the IE if a SIM is inserted in the MS. In UMTS, the MS shall reject the AUTHENTICATION & CIPHERING REQUEST message as specified in subclause 4.7.7.5.1 if this IE is not present and a USIM is inserted in the MS. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.4.9.3 |
1,761 | 17.2.2 Full Authentication NAI | The Full Authentication NAI in both EAP-SIM and EAP-AKA shall take the form of an NAI as specified in clause 2.1 of IETF RFC 4282 [53]. The format of the Full Authentication NAI shall comply with IETF RFC 4187 [50] when EAP-AKA authentication is used and with IETF RFC 4186 [51], when EAP-SIM authentication is used. The realm used shall be a home network realm as defined in clause 17.2.1. The result will therefore be an identity of the form: "0<IMSI>@gan.mnc<MNC>.mcc<MCC>.3gppnetwork.org", for EAP-AKA authentication and "1<IMSI>@gan.mnc<MNC>.mcc<MCC>.3gppnetwork.org", for EAP-SIM authentication EXAMPLE 1: For EAP AKA authentication: If the IMSI is 234150999999999 (MCC = 234, MNC = 15), the Full Authentication NAI takes the form 0234150999999999@gan.mnc015.mcc234.3gppnetwork.org. EXAMPLE 2: For EAP SIM authentication: If the IMSI is 234150999999999 (MCC = 234, MNC = 15), the Full Authentication NAI takes the form 1234150999999999@gan.mnc015.mcc234.3gppnetwork.org. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 17.2.2 |
1,762 | 4.7.7.3b 128-bit packet-switched GSM integrity key (in A/Gb mode and only if MS supports integrity protection) | The ME and the network may derive and store a 128-bit packet-switched GPRS GSM Kint from an established UMTS security context. If the GPRS GSM Kint exits, then it is also part of the UMTS security context. The ME with a USIM in use shall compute a new GPRS GSM Kint using the GPRS UMTS ciphering key and the GPRS UMTS integrity key from an established UMTS security context as specified in 3GPP TS 43.020[ Security related network functions ] [13]. The new GPRS GSM Kint shall be stored only in the ME. The ME shall overwrite the existing GPRS GSM Kint with the new GPRS GSM Kint. The ME shall delete the GPRS GSM Kint at MS switch off, when the USIM is disabled as well as under the conditions identified in the subclause 4.1.3.2 and 4.7.7.4. The ME with a USIM in use shall apply the GPRS GSM Kint when in A/Gb mode a GIA integrityg algorithm that requires a 128-bit integrity key is taken into use. The network shall compute the GPRS GSM Kint using the GPRS UMTS integrity key and the GPRS UMTS ciphering key from an established UMTS security context as specified in 3GPP TS 43.020[ Security related network functions ] [13]only when in A/Gb mode a GIA integrity algorithm that requires a 128-bit integrity key is to be used. At MS power off, the information in the Integrity Algorithm IE shall be stored in a non-volatile memory in the ME together with the IMSI from the USIM. The information stored in the Integrity Algorithm IE can only be used if the IMSI from the USIM matches the IMSI stored in the ME non-volatile memory at MS power on; otherwise the MS shall delete the Integrity Algorithm IE. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.7.3b |
1,763 | 10.5.1 EN-DC | The Secondary Node Change procedure is initiated either by MN or SN and used to transfer a UE context from a source SN to a target SN and to change the SCG configuration in UE from one SN to another. In case of inter-SN CPC, the Conditional Secondary Node Change procedure initiated either by the MN or SN is also used for inter-SN CPC configuration and inter-SN CPC execution. NOTE 1: Inter-RAT SN change procedure with single RRC reconfiguration is not supported in this version of the protocol (i.e. no transition from EN-DC to DC). The Secondary Node Change procedure always involves signalling over MCG SRB towards the UE. MN initiated SN Change Figure 10.5.1-1: SN Change – MN initiated Figure 10.5.1-1 shows an example signalling flow for the MN initiated Secondary Node Change: 1/2. The MN initiates the SN change by requesting the target SN to allocate resources for the UE by means of the SgNB Addition procedure. The MN may include measurement results related to the target SN. If forwarding is needed, the target SN provides forwarding addresses to the MN. The target SN includes the indication of the full or delta RRC configuration. NOTE 2: The MN may trigger the MN-initiated SN Modification procedure (to the source SN) to retrieve the current SCG configuration before step 1. NOTE 2a: In case the target SN includes the indication of the full RRC configuration, the MN performs release of the SN terminated radio bearer configuration and release and add of the NR SCG configuration part towards the UE. 3. If the allocation of target SN resources was successful, the MN initiates the release of the source SN resources including a Cause indicating SCG mobility. The Source SN may reject the release. If data forwarding is needed the MN provides data forwarding addresses to the source SN. If direct data forwarding is used for SN terminated bearers, the MN provides data forwarding addresses as received from the target SN to source SN. Reception of the SgNB Release Request message triggers the source SN to stop providing user data to the UE and, if applicable, to start data forwarding. 4/5. The MN triggers the UE to apply the new configuration. The MN indicates to the UE the new configuration in the RRCConnectionReconfiguration message including the NR RRC configuration message generated by the target SN. The UE applies the new configuration and sends the RRCConnectionReconfigurationComplete message, including the encoded NR RRC response message for the target SN, if needed. In case the UE is unable to comply with (part of) the configuration included in the RRCConnectionReconfiguration message, it performs the reconfiguration failure procedure. 6. If the RRC connection reconfiguration procedure was successful, the MN informs the target SN via SgNBReconfigurationComplete message with the encoded NR RRC response message for the target SN, if received from the UE. 7. If configured with bearers requiring SCG radio resources, the UE synchronizes to the target SN. 8. For SN terminated bearers using RLC AM, the source SN sends the SN Status Transfer message, which the MN sends then to the target SN, if needed. 9. If applicable, data forwarding from the source SN takes place. It may be initiated as early as the source SN receives the SgNB Release Request message from the MN. 10. The source SN sends the Secondary RAT Data Usage Report message to the MN and includes the data volumes delivered to and received from the UE over the NR radio for the related E-RABs. NOTE 3: The order the SN sends the Secondary RAT Data Usage Report message and performs data forwarding with MN is not defined. The SN may send the report when the transmission of the related bearer is stopped. 11-15. If applicable, a path update is triggered by the MN. 16. Upon reception of the UE Context Release message, the source SN releases radio and C-plane related resources associated to the UE context. Any ongoing data forwarding may continue. SN initiated SN Change Figure 10.5.1-2: SN Change – SN initiated Figure 10.5.1-2 shows an example signalling flow for the Secondary Node Change initiated by the SN: 1. The source SN initiates the SN change procedure by sending SgNB Change Required message which contains target SN ID information and may include the SCG configuration (to support delta configuration) and measurement results related to the target SN. 2/3. The MN requests the target SN to allocate resources for the UE by means of the SgNB Addition procedure, including the measurement results related to the target SN received from the source SN. If forwarding is needed, the target SN provides forwarding addresses to the MN. The target SN includes the indication of the full or delta RRC configuration. NOTE 3a: In case the target SN includes the indication of the full RRC configuration, the MN performs release of the SN terminated radio bearer configuration and release and add of the NR SCG configuration part towards the UE. 4/5. The MN triggers the UE to apply the new configuration. The MN indicates the new configuration to the UE in the RRCConnectionReconfiguration message including the NR RRC configuration message generated by the target SN. The UE applies the new configuration and sends the RRCConnectionReconfigurationComplete message, including the encoded NR RRC response message for the target SN, if needed. In case the UE is unable to comply with (part of) the configuration included in the RRCConnectionReconfiguration message, it performs the reconfiguration failure procedure. 6. If the allocation of target SN resources was successful, the MN confirms the release of the source SN resources. If data forwarding is needed the MN provides data forwarding addresses to the source SN. If direct data forwarding is used for SN terminated bearers, the MN provides data forwarding addresses as received from the target SN to source SN. Reception of the SgNB Change Confirm message triggers the source SN to stop providing user data to the UE and, if applicable, to start data forwarding. 7. If the RRC connection reconfiguration procedure was successful, the MN informs the target SN via SgNB Reconfiguration Complete message with the encoded NR RRC response message for the target SN, if received from the UE. 8. The UE synchronizes to the target SN. 9. For SN terminated bearers using RLC AM, the source SN sends the SN Status Transfer message, which the MN sends then to the target SN, if needed. 10. If applicable, data forwarding from the source SN takes place. It may be initiated as early as the source SN receives the SgNB Change Confirm message from the MN. 11. The source SN sends the Secondary RAT Data Usage Report message to the MN and includes the data volumes delivered to and received from the UE over the NR radio for the related E-RABs. NOTE 4: The order the source SN sends the Secondary RAT Data Usage Report message and performs data forwarding with MN/target SN is not defined. The SgNB may send the report when the transmission of the related bearer is stopped. 12-16. If applicable, a path update is triggered by the MN. 17. Upon reception of the UE Context Release message, the source SN releases radio and C-plane related resources associated to the UE context. Any ongoing data forwarding may continue. MN initiated conditional SN Change The MN initiated conditional inter-SN change procedure is used for inter-SN CPC configuration and inter-SN CPC execution. Figure 10.5.1-3: Conditional SN Change – MN initiated Figure 10.5.1-3 shows an example signalling flow for the MN initiated Conditional Secondary Node Change: 1/2. The MN initiates the conditional SN change by requesting the candidate SN(s) to allocate resources for the UE by means of the SgNB Addition procedure, indicating that the request is for CPAC. The MN also provides the candidate cells recommended by MN via the latest measurement results for the candidate SN(s) to choose and configure the SCG cell(s), and provides the upper limit for the number of PSCells that can be prepared by the candidate SN. From the measurement results indicated by the MN, the candidate SN decides the list of PSCell(s) to prepare (considering the maximum number indicated by the MN) and, for each prepared PSCell, the candidate SN decides other SCG SCells and provides the new corresponding SCG radio resource configuration to the MN in an NR RRCReconfiguration** message contained in the SgNB Addition Request Acknowledge message with the prepared PSCell ID(s). If forwarding is needed, the candidate SN provides forwarding addresses to the MN. The candidate SN includes the indication of the full or delta RRC configuration. The candidate SN can either accept or reject each of the candidate cells listed within the measurement results indicated by the MN, i.e. it cannot configure any alternative candidates. NOTE 5: The MN may trigger the MN-initiated SN Modification procedure (to the source SN) to retrieve the current SCG configuration before step 1. NOTE 5a: In case the candidate SN includes the indication of the full RRC configuration, the MN performs release of the SN terminated radio bearer configuration and release and add of the NR SCG configuration part towards the UE in the conditional configuration. 3. The MN sends to the UE an RRCConnectionReconfiguration message including the CPC configuration, i.e. a list of RRCConnectionReconfiguration* messages and associated execution conditions, in which each RRCConnectionReconfiguration* message contains the SCG configuration in the RRCReconfiguration** message received from the candidate SN in step 2 and possibly an MCG configuration. Besides, the RRCConnectionReconfiguration message can also include an updated MCG configuration, e.g., to configure the required conditional measurements. 4. The UE applies the RRCConnectionReconfiguration message received in step 3, stores the CPC configuration and replies to the MN with an RRCConnectionReconfigurationComplete message. In case the UE is unable to comply with (part of) the configuration included in the RRCConnectionReconfiguration message, it performs the reconfiguration failure procedure. 4a. Upon receiving the RRCConnectionReconfigurationComplete message from the UE, the MN triggers the Data Forwarding Address Indication procedure to the source SN to inform that the CPC has been configured, the source SN, if applicable, together with the Early Status Transfer procedure, starts early data forwarding. The PDCP SDU forwarding may take place during early data forwarding. NOTE 5b: Separate Data Forwarding Address Indication procedures may be invoked to provide different forwarding addresses of the prepared candidate target SNs. In this case, it is up to the MN and the source SN implementations to make sure that the EARLY STATUS TRANSFER message(s) from the source SN, if any, is forwarded to the right target destination. The Data Forwarding Address Indication procedure may further be invoked to indicate to the source SN to stop already initiated early data forwarding for some SN-terminated bearers if they are no longer subject to data forwarding due to the modification or cancellation of the prepared conditional SN change procedures. NOTE 5c: For the early transmission of MN terminated split/SCG bearers, the MN forwards the PDCP PDU to the candidate SN(s). 5. The UE starts evaluating the execution conditions. If the execution condition of one candidate PSCell is satisfied, the UE applies RRCConnectionReconfiguration* message corresponding to the selected candidate PSCell, and sends an RRCConnectionReconfigurationComplete* message, including an NR RRCReconfigurationComplete** message for the selected candidate PSCell, and information enabling the MN to identify the SN of the selected candidate PSCell. 6a-6b. The MN triggers the MeNB initiated SgNB Release procedure to inform the source SN to stop providing user data to the UE, and, if applicable, the address of the SN of the selected candidate PSCell to start data forwarding. 7a-7c. If the RRC connection reconfiguration procedure was successful, the MN informs the SN of the selected candidate PSCell via SgNB Reconfiguration Complete message, including the SN RRCReconfigurationComplete** message. The MN sends the SgNB Release Request message(s) to cancel CPC in the other candidate SN(s), if configured. The other candidate SN(s) acknowledges the release request. 8. The UE synchronizes to the PSCell indicated in the RRCConnectionReconfiguration* message applied in step 5. 9a-9b. For SN terminated bearers using RLC AM, the source SN sends the SN Status Transfer message, which the MN sends to the SN of the selected candidate PSCell, if needed. 10. If applicable, data forwarding from the source SN takes place. It may be initiated as early as the source SN receives the early data forwarding address in step 4a. 11. The source SN sends the Secondary RAT Data Usage Report message to the MN and includes the data volumes delivered to and received from the UE over the NR radio for the related E-RABs. NOTE 6: The order the SN sends the Secondary RAT Data Usage Report message and performs data forwarding with MN is not defined. The SN may send the report when the transmission of the related bearer is stopped. 12-16. If applicable, a path update is triggered by the MN. 17. Upon reception of the UE Context Release message, the source SN releases radio and C-plane related resources associated to the UE context. Any ongoing data forwarding may continue. SN initiated conditional SN Change The SN initiated conditional SN change procedure is used for inter-SN CPC configuration and inter-SN CPC execution. The SN initiated conditional SN change procedure may also be initiated by the source SN, to modify the existing SN initiated inter-SN CPC configuration, or to trigger the release of the candidate SN by cancellation of all the prepared PSCells at the candidate SN and releasing the CPC related UE context at the candidate SN. NOTE 6a0: To modify or release an existing intra-SN CPC configuration, the source SN triggers an SN initiated Conditional SN Modification (with or without SRB3) without MN involvement, as specified in 10.3. Figure 10.5.1-4: Conditional SN Change – SN initiated Figure 10.5.1-4 shows an example signalling flow for the Conditional Secondary Node Change initiated by the SN: 1. The source SN initiates the conditional SN change procedure by sending SgNB Change Required message which contains a CPC initiation indication. The message also contains candidate SN ID(s) information and may include the SCG configuration (to support delta configuration), and contains the measurement results related to the candidate SN(s). The message also includes a list of proposed PSCell candidates recommended by the source SN, including execution conditions, the upper limit for the number of PSCells that can be prepared by each candidate SN, and may also include the SCG measurement configurations for CPC (e.g. measurement ID(s) to be used for CPC). 2/3. The MN requests each candidate SN to allocate resources for the UE by means of the SgNB Addition procedure(s) , indicating the request is for CPAC, and the measurements results related to the candidate SN and indicating a list of proposed PSCell candidates received from the source SN, but not including execution conditions. Within the list of PSCells suggested by the source SN, the candidate SN decides the list of PSCell(s) to prepare (considering the maximum number indicated by the MN) and, for each prepared PSCell, the candidate SN decides SCG SCells and provides the new corresponding SCG radio resource configuration to the MN in an NR RRCReconfiguration** message contained in the SgNB Addition Request Acknowledge message. If data forwarding is needed, the candidate SN provides data forwarding addresses to the MN. The candidate SN includes the indication of full or delta RRC configuration, and the list of prepared PSCell IDs to the MN. The candidate SN can either accept or reject each of the candidate cells suggested by the source SN, i.e. it cannot configure any alternative candidates. NOTE 6a: In case the candidate SN includes the indication of the full RRC configuration, the MN performs release of the SN terminated radio bearer configuration and release and add of the NR SCG configuration part towards the UE in the conditional configuration. 4/5. The MN may indicate the candidate PSCells accepted by each candidate SN to the source SN via SgNB Modification Request message before it configures the UE e.g., when not all candidate PSCells were accepted by the candidate SN(s). If the MN does not send such indication, step 4 and 5 are skipped. If requested,the source SN sends an SgNB Modification Request Acknowledge message and if needed, provides an updated measurement configurations and/or the execution conditions for CPC to the MN. 6. The MN sends to the UE an RRCConnectionReconfiguration message including the CPC configuration, i.e. a list of RRCConnectionReconfiguration* messages and associated execution conditions, in which each RRCConnectionReconfiguration* message contains the SCG configuration in the RRCReconfiguration** message received from the candidate SN in step 3 and possibly an MCG configuration. Besides, the RRCConnectionReconfiguration message can also include an updated MCG configuration, as well as the NR RRCReconfiguration*** message generated by the source SN, e.g., to configure the required conditional measurements. 7. The UE applies the RRCConnectionReconfiguration message received in step 6, stores the CPC configuration and replies to the MN with an RRCConnectionReconfigurationComplete message, which can include an NR RRCReconfigurationComplete*** message. In case the UE is unable to comply with (part of) the configuration included in the RRCConnectionReconfiguration message, it performs the reconfiguration failure procedure. 8. If an NR RRC response message is included, the MN informs the source SN with the NR RRCReconfigurationComplete*** message via SgNB Change Confirm message. If step 4 and 5 are skipped, the MN will indicate the candidate PSCells accepted by each candidate SN to the source SN in the SgNB Change Confirm message. The MN sends the SgNB Change Confirm message towards the source SN to indicate that CPC is prepared, and in such case the source SN continues providing user data to the UE. If early data forwarding is applied, the MN informs the source SN the data forwarding addresses as received from the candidate SN(s), the source SN, if applicable, together with the Early Status Transfer procedure, starts early data forwarding. The PDCP SDU forwarding may take place during early data forwarding. In case multiple candidate SNs are prepared, the MN includes a list of Target SgNB ID and list of data forwarding addresses to the source SN. NOTE 6b: The Data Forwarding Address Indication procedure may further be invoked to indicate to the source SN to stop already initiated early data forwarding for some PDCP SDUs if they are no longer subject to data forwarding due to the modification or cancellation of the prepared conditional PSCell change. NOTE 6c: For the early transmission of MN terminated split/SCG bearers, the MN forwards the PDCP PDU to the candidate SN(s). 9a-9d. The source SN may send the SgNB Modification Required message to trigger an update of CPC execution condition and/or corresponding SCG measurement configuration for CPC. In such case in step 9b, the MN reconfigures the UE and in step 9c the UE responds with RRCConnectionReconfigurationComplete, similarly as in steps 6 and 7. 10. The UE starts evaluating the execution conditions. If the execution condition of one candidate PSCell is satisfied, the UE applies the RRCConnectionReconfiguration* message corresponding to the selected candidate PSCell, and sends an RRCConnectionReconfigurationComplete* message, including the NR RRCReconfigurationComplete** message for the selected candidate PSCell, and information enabling the MN to identify the SN of the selected candidate PSCell. 11a-11b. The MN triggers the MeNB initiated SgNB Release procedure to inform source SN to stop providing user data to the UE, and if applicable, provides the address of the SN of the selected candidate PSCell to start late data forwarding. 12a-12c. If the RRC connection reconfiguration procedure was successful, the MN informs the SN of the selected candidate PSCell via SgNB Reconfiguration Complete message, including the SN RRCReconfigurationComplete** message. The MN sends the SgNB Release Request message(s) to cancel CPC in the other candidate SN(s), if configured. The other candidate SN(s) acknowledges the release request. 13. The UE synchronizes to the PSCell indicated in the RRCConnectionReconfiguration* message applied in step 10. 14a-14b. For SN terminated bearers using RLC AM, the source SN sends the SN Status Transfer message, which the MN sends then to the SN of the selected candidate PSCell, if needed. 15. If applicable, data forwarding from the source SN takes place. It may be initiated as early as the source SN receives the early data forwarding message from the MN. 16. The source SN sends the Secondary RAT Data Usage Report message to the MN and includes the data volumes delivered to and received from the UE over the NR radio for the related E-RABs. NOTE 7: The order the source SN sends the Secondary RAT Data Usage Report message and performs data forwarding with MN/target SN is not defined. The SgNB may send the report when the transmission of the related bearer is stopped. 17-21. If applicable, a path update is triggered by the MN. 22. Upon reception of the UE Context Release message, the source SN releases radio and C-plane related resources associated to the UE context. Any ongoing data forwarding may continue. | 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.5.1 |
1,764 | 6.15a.3.2 Requirements | The 5G system shall support different energy states of network elements and network functions. 5G system shall support dynamic changes of energy states of network elements and network functions. NOTE: This requirement also includes the condition when providing network elements or functions to an authorised 3rd party, the dynamic changes can be based on pre-configured policy (the time of changing energy states, which energy state map to which level of load, etc.) The 5G system shall support different charging mechanisms based on the different energy states of network elements and network functions. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.15a.3.2 |
1,765 | 4.5.2 Online mapping | The CTF is a mandatory integrated component of all network elements that are involved in online charging as depicted in figure 4.2.1, with the exception of the S-CSCF (see clause 4.3.2.2.2). If CDR generation by the OCS is required, as described in clause 4.3.2.3, then a CDF is integrated in each OCF that is required to produce the CDRs. All other possibilities for physical mapping, including e.g.: - integrated versus distributed CGF in the OCS, - use of another CGF by the OCS, - IMS GWF integrated in S-CSCF or OCS, or a stand-alone entity, are not specified within the 3GPP standards and are therefore implementation specific. The same is true for the composition of the OCS and its logical functions. | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.5.2 |
1,766 | Annex F (normative): Application specific Congestion control for Data Communication (ACDC) | The UE may support the procedures in this annex. If the UE supports ACDC, the EMM layer shall determine the ACDC category applicable to the request based on the application identifier received from the upper layers and the configuration information in the "ACDCConf" leaf of ACDC MO as specified in 3GPP TS 24.105[ Application specific Congestion control for Data Communication (ACDC) Management Object (MO) ] [35] or in the USIM EFACDC as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]. NOTE 1: As an implementation option, the upper layers can determine the ACDC category and send it to the EMM layer. Then the EMM layer need not read the ACDC MO or USIM to determine the ACDC category. The EMM sublayer shall indicate to the lower layers, for the purpose of access control: - the ACDC category that applies to this request if only one ACDC category is applicable; - the highest ranked ACDC category among the ACDC categories that applies to this request if multiple ACDC categories are applicable; or - this request is for an uncategorized application if an application identifier received from the upper layers is not mapped to any ACDC category, except for the following cases: - the UE is a UE configured to use AC11 – 15 in selected PLMN; - the UE is answering to paging; - the RRC Establishment cause is set to "Emergency call"; or - if conditions MO MMTEL voice call is started or MO MMTEL video call is started or MO SMSoIP is started, is satisfied. NOTE 2: The request from the EMM sublayer refers to either a request to establish an initial NAS signalling connection or a request to re-establish a NAS signalling connection. If the UE supports ACDC and access is barred because of ACDC, the EMM layer shall keep track of the ACDC category for which access is barred and it shall not send a request for the same ACDC category or a lower ACDC category until access is granted. If the UE supports ACDC and access is barred because of ACDC, the EMM layer shall not send a request for any uncategorized application until access is granted. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | Annex |
1,767 | 5.2.6.13.2 Nnef_NIDDConfiguration_Create service operation | Service operation name: Nnef_NIDDConfiguration_Create Description: This service operation is used by the consumer to request NIDD Configuration between NF consumer and NEF to support NIDD via NEF. Inputs, Optional: Reliable Data Service Configuration, Requested Action, TLTRI, NIDD Duration. Inputs, Required: GPSI or External Group Identifier, AF Identifier, T8 Destination Address, MTC Provider Information). Outputs, Required: TLTRI, Reliable Data Service Indication, Maximum Packet Size, Cause. Outputs, Optional: NIDD Duration. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.6.13.2 |
1,768 | 5.27.1.10 Support for coverage area filters for time synchronization service | This feature enables the AF to request time synchronization service for a UE or a group of UEs in a specific geographical area (so called coverage area). The requested coverage area contains a list of Tracking Area (TA) or a geographical area (e.g. a civic address or shapes that the NEF transforms to list of TAs based on pre-configuration). TSCTSF checks with the UDM if the UE is allowed to receive the time synchronization service requested by AF. The coverage area defines a spatial validity condition for the targeted UE(s) that is resolved at the TSCTSF. In order to do that, the TSCTSF may either: a) discover the AMF(s) serving the list of TA(s) that comprise the spatial validity using Nnrf_NFDiscovery_Request service from the NRF and subsequently, the TSCTSF subscribes to the discovered AMF(s) to receive notifications about presence of the UE in an Area of Interest events (as described in clause 5.3.4.4). The subscription is targeted to Any UE. To reduce the number of Area of Interest reports (based on presence of UE) for the discovered AMFs, the TSCTSF may provide additional filtering information (e.g. List of UE IDs, DNN(s)/S-NNSAI(s)) to limit the subscription to the indicated UE identities, or UEs having a PDU Session with the given DNN/S-NSSAI as specified in clause 5.3.4.4. b) determine the serving AMF for each of the targeted UE(s) using the UDM and subscribe to the serving AMF to receive notification about presence of the UE in an Area of Interest (as described in clause 5.3.4.4). An Area of Interest (AoI) for each AMF is represented by a list of TA(s), wherein the Area of Interest is identical to the requested coverage area. Based on the outcome provided by the AMF about the UE's presence in the AoI, the TSCTSF determines if the time synchronization service is activated or deactivated. For access stratum distribution activation/deactivation, the TSCTSF will enable/disable access stratum time distribution to the UE at the serving NG-RAN node reusing the procedures in clause 4.15.9.4 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. For (g)PTP distribution activation/deactivation, the TSCTSF will modify the PTP instance configuration by means of sending a PMIC to the impacted UE/DS-TTs and UMIC to the impacted UPF/NW-TT, as described in clause K.2.2. If the time synchronization service is modified based on the reports of UE presence in the Area of Interest, the TSCTSF informs the AF for the impacted UE(s) by indicating the PTP port state for the related DS-TT PTP port (in the case of (g)PTP based time distribution) or notifying the AF with the indication of 5G access status time distribution status (enabled or disabled, for ASTI based time distribution). If the Time Synchronization Coverage Area requested by the AF includes at least one TA that is a part of UE's Registration Area (RA), the 5GS may provide the AF-requested time synchronization service to the targeted UE within its RA, i.e. all TAs of the RA shall be treated as a Time Synchronization Coverage Area even if some of the TAs were not requested by the AF. NOTE 1: This ensures that (1) there is no impact on the Registration Area (RA) of UE if/when the AMF receives a time synchronization service request with a spatial validity condition (i.e. for specific geographical area); and (2) the UE can continue receiving the time synchronization service when it moves within the RA in the RRC_IDLE state. NOTE 2: Since the RA can be specific to the UE, the result can be different Time Synchronization Coverage Area for different DS-TT ports of different UEs within a PTP instance. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.27.1.10 |
1,769 | 4.5.5.1 Mean number of RACH preambles received | This measurement provides the mean number of RACH preambles received in a cell in one second. Separate counts are provided for dedicated preambles, randomly chosen preambles in group A (aka “low range”) and randomly chosen preambles in group B (aka “high range”). Gauge This measurement is obtained according to the definition in 36.314 [11]. Each measurement is an integer value. RRU.RachPreambleDedMean RRU.RachPreambleAMean RRU.RachPreambleBMean EUtranCellFDD EUtranCellTDD Valid for packet switched traffic EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.5.5.1 |
1,770 | 5.8.9.1a.6.1 Additional Sidelink RLC Bearer addition/modification conditions | For NR sidelink communication, additional sidelink RLC bearer addition is initiated only in the following cases: 1> for unicast, for sidelink DRB, if SL-RLC-BearerConfig is received in sl-RLC-BearerToAddModList in the RRCReconfigurationSidelink for a slrb-PC5-ConfigIndex; or 1> for groupcast and broadcast, for sidelink DRB, if SL-RLC-BearerConfig is received in sl-RLC-BearerToAddModListSizeExt in sl-ConfigDedicatedNR for a sl-ServedRadioBearer, and if the SL-TxProfile of all associated QoS flow(s) for the sl-ServedRadioBearer indicates backwardsIncompatible; or 1> for groupcast and broadcast, for sidelink DRB, if SL-RLC-BearerConfig is received in sl-RLC-BearerToAddModListSizeExt in sl-ConfigDedicatedNR for a sl-ServedRadioBearer, and if the SL-TxProfile of at least one associated QoS flow for the sl-ServedRadioBearer indicates backwardsCompatible and UE decides to use PDCP duplication; or 1> for unicast, for sidelink DRB, if SL-RLC-BearerConfig is received in sl-RLC-BearerToAddModListSizeExt in sl-ConfigDedicatedNR for a sl-ServedRadioBearer; or 1> for groupcast and broadcast, for sidelink DRB, if SL-RLC-BearerConfig is received in sl-RLC-BearerConfigListSizeExt in SIB12 or in SidelinkPreconfigNR for a sl-ServedRadioBearer, and if the SL-TxProfile of all associated QoS flow(s) for the sl-ServedRadioBearer indicates backwardsIncompatible; or 1> for groupcast and broadcast, for sidelink DRB, if SL-RLC-BearerConfig is received in sl-RLC-BearerConfigListSizeExt in SIB12 or in SidelinkPreconfigNR for a sl-ServedRadioBearer, and if the SL-TxProfile of at least one QoS flow for the sl-ServedRadioBearer indicates backwardsCompatible and UE decides to use PDCP duplication; or 1> for unicast, for sidelink DRB, if SL-RLC-BearerConfig is received in sl-RLC-BearerConfigListSizeExt in SIB12 or in SidelinkPreconfigNR for a sl-ServedRadioBearer, and if both UEs support PDCP duplication; or 1> for unicast, for sidelink SRB, if UE decides to use PDCP duplication; For NR sidelink communication, additional sidelink RLC bearer modification is initiated only in the following cases: 1> if any of the additional sidelink RLC bearer related parameters is changed by sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR or RRCReconfigurationSidelink for one additional sidelink RLC bearer, which is established; | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.9.1a.6.1 |
1,771 | – SecurityModeFailure | The SecurityModeFailure message is used to indicate an unsuccessful completion of a security mode command. Signalling radio bearer: SRB1 RLC-SAP: AM Logical channel: DCCH Direction: UE to Network SecurityModeFailure message -- ASN1START -- TAG-SECURITYMODEFAILURE-START SecurityModeFailure ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { securityModeFailure SecurityModeFailure-IEs, criticalExtensionsFuture SEQUENCE {} } } SecurityModeFailure-IEs ::= SEQUENCE { lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE{} OPTIONAL } -- TAG-SECURITYMODEFAILURE-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
1,772 | 17.7a Gmb re-used AVPs | Table 17.7a.1 lists the Diameter AVPs re-used by the Gmb reference point from other existing Diameter Application, reference to their respective specifications and short description of their usage witin the Gmb reference point. Other AVPs from existing Diameter Applications, except for the AVPs from Diameter base protocol, do not need to be supported. The AVPs from Diameter base protocol are not included in table 17.7a.1, but they are re-used for the Gmb reference point. Unless otherwise stated, re-used AVPs shall maintain their 'M', 'P' and 'V' flag settings. Where RADIUS VSAs are re-used, they shall be translated to Diameter AVPs as described in IETF RFC 7155 [120] with the exception that the 'M' flag shall be set and the 'P' flag may be set. Table 17.7a.1: Gmb re-used Diameter AVPs | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 17.7a |
1,773 | D.2.1 Roaming interoperation scenario | In the roaming scenario the vPLMN operates Gn/Gp 2G and/or 3G SGSNs as well as MME and S-GW for E-UTRAN access. The hPLMN operates a P-GW. Roaming and inter access mobility between Gn/Gp 2G and/or 3G SGSNs and an MME/S-GW are enabled by: - Gn functionality as specified between two Gn/Gp SGSNs, which is provided by the MME, and - Gp functionality as specified between Gn/Gp SGSN and Gn/Gp GGSN that is provided by the P-GW. All this Gp and Gn functionality bases on GTP version 1 only. The architecture for interoperation with Gn/Gp SGSNs in the non-roaming case is illustrated in Figure D.2.1-1. Figure D.2.1-1: Roaming architecture for interoperation with Gn/Gp SGSN | 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.2.1 |
1,774 | 5.27 Enablers for Time Sensitive Communications, Time Synchronization and Deterministic Networking 5.27.0 General | This clause describes 5G System features that can be used independently or in combination to enable time-sensitive communication, time synchronization and deterministic networking: - Delay-critical GBR; - A hold and forward mechanism to schedule traffic as defined in IEEE Std 802.1Q [98] for Ethernet PDU Sessions in DS-TT and NW-TT (see clause 5.27.4) to de-jitter flows that have traversed the 5G System if the 5G System is to participate transparently as a bridge in a TSN network; - TSC Assistance Information: describes TSC flow traffic characteristics as described in clause 5.27.2 that may be provided optionally for use by the gNB, to allow more efficiently schedule radio resources for periodic traffic and applies to PDU Session type Ethernet and IP. - Time Synchronization: describes how 5GS can operate as a PTP Relay (IEEE Std 802.1AS [104]), as a Boundary Clock or as Transparent Clock (IEEE Std 1588 [126]) for PDU Session type Ethernet and IP and how 5GS can detect and report the status of the time synchronization. - RAN feedback for BAT offset and adjusted periodicity describes a mechanism supported by NG-RAN and 5G CN that enables AF to adapt to received BAT offset and adjusted periodicity from NG-RAN for a given traffic flow. The 5G System integration as a bridge in an IEEE 802.1 TSN network as described in clause 5.28 can make use of all features listed above. To support any of the above features to enable time-sensitive communication, time synchronization and deterministic networking, during the PDU Session establishment, the UE shall request to establish a PDU Session as an always-on PDU Session, and the PDU Sessions are established as Always-on PDU session as described in clause 5.6.13. In this release of the specification, to use any of the above features to enable time-sensitive communication, time synchronization and deterministic networking: - Home Routed PDU Sessions are not supported; - PDU Sessions are supported only for SSC mode 1; - Service continuity is not supported when the UE moves from 5GS to EPS .i.e. interworking with EPS is not supported for a PDU Session for time synchronization or TSC or deterministic networking. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.27 |
1,775 | 8.3.2.1E Enhanced Performance Requirement Type B – Single-layer Spatial Multiplexing with CRS interference model | The requirements are specified in Table 8.3.2.1E-2, with the addition of the parameters in Table 8.3.2.1E-1 and the downlink physical channel setup according to Annex C.3.2. The purpose of these tests is to verify closed loop rank one performance on one of the antenna ports 7 or 8 without a simultaneous transmission on the other antenna port in the serving cell when the PDSCH transmission in the serving cell is interfered by the CRS of the interfering cell, applying the CRS interference model defined in clause B.6.5. In 8.3.2.1E-1, Cell 1 is the serving cell, and Cell 2, 3 are interfering cells. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1, Cell 2 and Cell 3, respectively. Table 8.3.2.1E-1: Test Parameters for Testing CDM-multiplexed DM RS (Single-layer) with CRS interference model Table 8.3.2.1E-2: Minimum Performance for Enhanced Performance Requirement Type B, CDM-multiplexed DM RS with CRS interference model | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.3.2.1E |
1,776 | 4.9.2 Disabling and re-enabling of UE's N1 mode capability for 3GPP access | The UE shall only disable the N1 mode capability for 3GPP access when in 5GMM-IDLE mode. When the UE is disabling the N1 mode capability for 3GPP access for a PLMN not due to redirection to EPC, it should proceed as follows: a) select an E-UTRA cell connected to EPC, or for the UE which supports CIoT EPS optimization select a satellite E-UTRA cell connected to EPC via "WB-E-UTRAN(LEO)", "WB-E-UTRAN(MEO)", or "WB-E-UTRAN(GEO)", of the registered PLMN or a PLMN from the list of equivalent PLMNs, if the UE supports S1 mode and the UE has not disabled its E-UTRA capability as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]; b) if an E-UTRA cell connected to EPC, or for the UE which supports CIoT EPS optimization if a satellite E-UTRA cell connected to EPC via "WB-E-UTRAN(LEO)", "WB-E-UTRAN(MEO)", or "WB-E-UTRAN(GEO)", of the registered PLMN or a PLMN from the list of equivalent PLMNs cannot be found, the UE does not support S1 mode or the UE has disabled its E-UTRA capability as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15], the UE may select another RAT of the registered PLMN or a PLMN from the list of equivalent PLMNs that the UE supports; c) if another RAT of the registered PLMN or a PLMN from the list of equivalent PLMNs cannot be found, then enter the state 5GMM-REGISTERED.PLMN-SEARCH or 5GMM-DEREGISTERED.PLMN-SEARCH, or the UE does not have a registered PLMN, then enter the state 5GMM-DEREGISTERED.PLMN-SEARCH and perform PLMN selection as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]. If disabling of the N1 mode capability for 3GPP access was not due to a UE-initiated de-registration procedure for 5GS services over 3GPP access not due to switch-off, the UE may re-enable the N1 capability for this PLMN selection. As an implementation option, if the UE does not have a registered PLMN, instead of performing PLMN selection, the UE may select another RAT of the selected PLMN if the UE has chosen a PLMN and the RAT is supported by the UE; or d) if no other allowed PLMN and RAT combinations are available, then the UE may re-enable the N1 mode capability for 3GPP access and indicate to lower layers to remain camped in NG-RAN of the registered PLMN, and may periodically scan for another PLMN and RAT combination which can provide EPS services or non-EPS services (if the UE supports EPS services or non-EPS services). How this periodic scanning is done, is UE implementation dependent. When the UE is disabling the N1 mode capability for 3GPP access for an SNPN, it should proceed as follows: a) enter the state 5GMM-REGISTERED.PLMN-SEARCH or 5GMM-DEREGISTERED.PLMN-SEARCH and perform SNPN selection as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]. If disabling of the N1 mode capability for 3GPP access was not due to a UE-initiated de-registration procedure for 5GS services over 3GPP access not due to switch-off, the UE may re-enable the N1 capability for this SNPN selection; or b) if no other SNPN is available, then the UE may re-enable the N1 mode capability for 3GPP access and indicate to lower layers to remain camped in NG-RAN of the registered SNPN. When the UE is disabling the N1 mode capability upon receiving cause value #31 "Redirection to EPC required" as specified in subclauses 5.5.1.2.5, 5.5.1.3.5 and 5.6.1.5, it should proceed as follows: a) If the UE is in NB-N1 mode: 1) if lower layers do not provide an indication that the current E-UTRA cell is connected to EPC or lower layers do not provide an indication that the current E-UTRA cell supports CIoT EPS optimizations that are supported by the UE, search for a suitable NB-IoT cell connected to EPC according to 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [25C]; 2) if lower layers provide an indication that the current E-UTRA cell is connected to EPC and the current E-UTRA cell supports CIoT EPS optimizations that are supported by the UE, perform a core network selection to select EPC as specified in subclause 4.8.4A.1; or 3) if lower layers cannot find a suitable NB-IoT cell connected to EPC or there is no suitable NB-IoT cell connected to EPC which supports CIoT EPS optimizations that are supported by the UE, the UE, as an implementation option, may indicate to lower layers to remain camped in E-UTRA cell connected to 5GCN, may then start an implementation-specific timer and enter the state 5GMM-REGISTERED.LIMITED-SERVICE. The UE may may re-enable the N1 mode capability for 3GPP access at expiry of the implementation-specific timer, if the timer had been started, and may then proceed with the appropriate 5GMM procedure. b) If the UE is in WB-N1 mode: 1) if lower layers do not provide an indication that the current E-UTRA cell is connected to EPC or lower layers do not provide an indication that the current E-UTRA cell supports CIoT EPS optimizations that are supported by the UE, search for a suitable E-UTRA cell connected to EPC, or for the UE which supports CIoT EPS optimization select a satellite E-UTRA cell connected to EPC via "WB-E-UTRAN(LEO)", "WB-E-UTRAN(MEO)", or "WB-E-UTRAN(GEO)", according to 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [25C]; 2) if lower layers provide an indication that the current E-UTRA cell is connected to EPC and the current E-UTRA cell supports CIoT EPS optimizations that are supported by the UE, then perform a core network selection to select EPC as specified in subclause 4.8.4A.1; or 3) if lower layers cannot find a suitable E-UTRA cell connected to EPC, or if the lower layers cannot find a suitable satellite E-UTRA cell via "WB-E-UTRAN(LEO)", "WB-E-UTRAN(MEO)", or "WB-E-UTRAN(GEO)", or there is no suitable E-UTRA cell connected to EPC, or there is no suitable satellite E-UTRA cell connected to EPC via "WB-E-UTRAN(LEO)", "WB-E-UTRAN(MEO)", or "WB-E-UTRAN(GEO)", which supports CIoT EPS optimizations that are supported by the UE, the UE, as an implementation option, may indicate to lower layers to remain camped in E-UTRA cell connected to 5GCN, may then start an implementation-specific timer and enter the state 5GMM-REGISTERED.LIMITED-SERVICE. The UE may re-enable the N1 mode capability for 3GPP access at expiry of the implementation-specific timer, if the timer had been started, and may then proceed with the appropriate 5GMM procedure. When the UE supporting both N1 mode and S1 mode needs to stay in E-UTRA connected to EPC (e.g. due to the domain selection for UE originating sessions as specified in subclause 4.3.2), in order to prevent unintentional handover or cell reselection from E-UTRA connected to EPC to NG-RAN connected to 5GCN, the UE operating in single-registration mode shall disable the N1 mode capability for 3GPP access and: a) shall set the N1mode bit to "N1 mode for 3GPP access not supported" in the UE network capability IE (see 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]) of the ATTACH REQUEST message and the TRACKING AREA UPDATE REQUEST message in EPC; and b) the UE NAS layer shall indicate the access stratum layer(s) of disabling of the N1 mode capability for 3GPP access. If the UE is required to disable the N1 mode capability for 3GPP access and select E-UTRA or another RAT, and the UE is in the 5GMM-CONNECTED mode, - if the UE has a persistent PDU session, then the UE waits until the radio bearer associated with the persistent PDU session has been released; - otherwise the UE shall locally release the established NAS signalling connection; and enter the 5GMM-IDLE mode before selecting E-UTRA or another RAT. If the UE is disabling its N1 mode capability for 3GPP access before selecting E-UTRA or another RAT, the UE shall not perform the UE-initiated de-registration procedure of subclause 5.5.2.2. The UE shall re-enable the N1 mode capability for 3GPP access when the UE performs PLMN selection, SNPN selection or SNPN selection for onboarding services over 3GPP access, unless - disabling of the N1 mode capability for 3GPP access was due to a UE-initiated de-registration procedure for 5GS services over 3GPP access not due to switch-off; or - the UE has already re-enabled the N1 mode capability for 3GPP access when performing items c) or d) above ; or - the UE disables the N1 mode capability for 3GPP access for cases described in subclauses 5.5.1.2.7 and 5.5.1.3.7. If the disabling of N1 mode capability for 3GPP access was due to IMS voice is not available over 3GPP access and the UE's usage setting is "voice centric", the UE shall re-enable the N1 mode capability for 3GPP access when the UE's usage setting is changed from "voice centric" to "data centric", as specified in subclauses 4.3.3. The UE should memorize the identity of the PLMN or SNPN where N1 mode capability for 3GPP access was disabled and should use that stored information in subsequent PLMN or SNPN selections as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]. If the disabling of N1 mode capability for 3GPP access was due to successful completion of an emergency services fallback, the criteria to enable the N1 mode capability again are UE implementation specific. The UE shall disable the N1 mode capability for 3GPP access if requested by the upper layers (e.g. see subclause U.2.2.6.4 in 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [14]). If the UE disabled the N1 mode capability for 3GPP access based on the request from the upper layers (e.g. see subclause U.2.2.6.4 in 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [14]), the criteria to re-enable the N1 mode capability for 3GPP access after the completion of an emergency service are UE implementation specific. If the N1 mode capability for 3GPP access was disabled due to the UE initiated de-registration procedure for 3GPP access or for 3GPP access and non-3GPP access and the UE is operating in single-registration mode (see subclause 5.5.2.2.3), upon request of the upper layers to re-register for 5GS services over 3GPP access or the UE needs to come out of unavailability period and resume normal services, the UE shall enable the N1 mode capability for 3GPP access again. As an implementation option, the UE may start a timer for enabling the N1 mode capability for 3GPP access when the UE's registration attempt counter reaches 5 and the UE disables the N1 mode capability for 3GPP access for cases described in subclauses 5.5.1.2.7 and 5.5.1.3.7. The UE should memorize the identity of the PLMNs or SNPNs where N1 mode capability for 3GPP access was disabled. On expiry of this timer: - if the UE is in Iu mode or A/Gb mode and is in idle mode as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13], the UE should enable the N1 mode capability for 3GPP access; - if the UE is in Iu mode and a PS signalling connection exists, but no RR connection exists, the UE may abort the PS signalling connection before enabling the N1 mode capability for 3GPP access; or - if the UE is in S1 mode and is in EMM-IDLE mode as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15], the UE should enable the N1 mode capability for 3GPP access; and - if the UE is in Iu mode or A/Gb mode and an RR connection exists, the UE should delay enabling the N1 mode capability for 3GPP access until the RR connection is released. If the UE is in S1 mode and is in EMM-CONNECTED mode as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15], the UE should delay enabling the N1 mode capability for 3GPP access until the NAS signalling connection in S1 mode is released. When the UE enables the N1 mode capability for 3GPP access, the UE shall remove the PLMN or SNPN from the memorized identity of the PLMNs or SNPNs where N1 mode capability for 3GPP access was disabled. NOTE 1: As described in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5], if the UE is in automatic PLMN selection mode or automatic SNPN selection mode, the UE does not consider the memorized PLMNs as PLMN selection candidates for NG-RAN access technology or the memorized SNPN as SNPN selection candidates till the timer expires. The UE may disable the N1 mode capability for currently camped PLMN or SNPN over 3GPP access (see 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]) if no network slice is available for the camped PLMN or SNPN (see subclauses 5.5.1.2.5 and 5.5.1.3.5). If the disabling of N1 mode capability for 3GPP access was due to no network slices available, the UE should memorize the identity of the PLMN or SNPN where N1 mode is disabled due to no available network slices or the list of SNPNs where N1 mode is disabled due to no available network slices, respectively. As an implementation option, the UE may start a timer TNSU for enabling the N1 mode capability that was disabled due to no available network slices for the 3GPP access. The value of timer TNSU is UE implementation specific. The UE should remove the memorized identity of the PLMNs or SNPNs where N1 mode is disabled due to no available network slice upon: - the expiry of the timer TNSU; or - receiving REGISTRATION ACCEPT message containing the Network slicing indication IE with the Network slicing subscription change indication set to “Network slicing subscription changed”. If the UE receives ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message provided with S-NSSAI and the PLMN ID in the Protocol configuration options IE or Extended protocol configuration options IE (see subclause 6.5.1.3 of 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]), the UE may remove the PLMN ID from the memorized identity of the PLMNs where N1 mode is disabled due to no available network slices. If the UE attempts to establish an emergency PDU session in a PLMN where N1 mode capability was disabled due to the UE's registration attempt counter have reached 5, the UE may enable N1 mode capability for that PLMN memorized by the UE. NOTE 2: If N1 mode capability is disabled due to the UE's registration attempt counter reaches 5, the value of the timer for re-enabling N1 mode capability is recommended to be the same as the value of T3502 which follows the handling specified in subclause 5.3.8. If the value of T3502 is indicated as zero by the network, an implementation specific non-zero value can be used for the timer for re-enabling N1 mode capability. | 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.9.2 |
1,777 | 10.5.6.3.3 Additional APN rate control parameters for exception data | The purpose of the Additional APN rate control parameters for exception data container contents is to indicate the additional APN rate control parameters for exception data. The Additional APN rate control parameters for exception data container contents are coded as shown in figure 10.5.6.3.3-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.6.3.3-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The Additional APN rate control parameters for exception data container contents can be 1 octet long or 3 octets long. If the Additional APN rate control parameters for exception data container contents is longer than 3 octets, the 4th octet and later octets are ignored. Figure 10.5.6.3.3-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Additional APN rate control parameters for exception data Table 10.5.6.3.3-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Additional APN rate control parameters for exception data | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.6.3.3 |
1,778 | 6.7.1B Minimum requirement for UL-MIMO | For UE supporting UL-MIMO, the transmit intermodulation requirements are specified at each transmit antenna connector and the wanted signal is defined as the sum of output power at each transmit antenna connector. For UEs with two transmit antenna connectors in closed-loop spatial multiplexing scheme, the requirements in subclause 6.7.1 apply to each transmit antenna connector. The requirements shall be met with the UL-MIMO configurations specified in Table 6.2.2B-2. If UE is configured for transmission on single-antenna port, the requirements in subclause 6.7.1 apply. | 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.1B |
1,779 | 16.3a.3 AAA-Initiated Bearer termination | RADIUS is used as the protocol between the P-GW and the AAA server or proxy for applications (e.g. MMS) to deliver information related to EPS user session. However some IP applications could need to interwork with the P-GW to release the corresponding resource (e.g. terminate a particular bearer or Resource Allocation Deactivation procedures as defined in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [78]). For this purpose, the AAA server or proxy may send a RADIUS Disconnect Request to the P-GW. On receipt of the Disconnect-Request from the AAA server, the P-GW shall release the corresponding resources and reply with a Disconnect-ACK. If the P-GW is unable to release the corresponding resources, it shall reply to the AAA server with a Disconnect-NAK. For more information on RADIUS Disconnect, see IETF RFC 3576 [41]. If the P-GW deletes the corresponding bearer, it need not wait for the response from the S-GW or non-3GPP IP access or ePDG before sending the RADIUS DisconnectResponse to the AAA server. The Teardown-Indicator in the RADIUS Disconnect Request message indicates to the P-GW that all IP-CAN bearers for this particular user and sharing the same user session shall be deleted. The IP-CAN bearers that belong to the same IP-CAN session are identified by the Acct-Session-Id. The Charging-Id contained in the Acct-Session-Id can be of any IP-CAN bearer of the user. The P-GW is able to find out all the related IP-CAN bearers sharing the same user session once it has found the exact IP-CAN bearer from the Acct-Session-Id. If a user has the same user IP address for different sets of IP-CAN bearers towards different networks, only the IP-CAN bearers linked to the one identified by the Acct-Session-Id shall be deleted. If the value of Teardown-Indicator is set to "0" or if TI is missing, and if the Acct-Session-Id identifies the default bearer, the P-GW shall tear-down all the IP-CAN bearers that share the same user session identified by the Acct-Session-Id. The following Figure 25a.3 is an example message flow to show the procedure of RADIUS AAA-Initiated Bearer termination, which applicable for GTP based S5/S8: NOTE: As shown on figure 25a.3, the P-GW need not wait for the Delete Bearer Response from the S-GW to send the RADIUS DisconnectResponse to the AAA server. Figure 25a.3: AAA-initiated bearer termination with RADIUS | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 16.3a.3 |
1,780 | 6.12.4 Subscription identification procedure | The subscriber identification mechanism may be invoked by the serving network when the UE cannot be identified by means of a temporary identity (5G-GUTI). In particular, it should be used when the serving network cannot retrieve the SUPI based on the 5G-GUTI by which the subscriber identifies itself on the radio path. The mechanism described in figure 6.12.4-1 allows the identification of a UE on the radio path by means of the SUCI. Figure 6.12.4-1: Subscription identifier query The mechanism is initiated by the AMF that requests the UE to send its SUCI. The UE shall calculate a fresh SUCI from SUPI using the Home Network Public Key, and respond with Identity Response carrying the SUCI. The UE shall implement a mechanism to limit the frequency at which the UE responds with a fresh SUCI to an Identity Request for a given 5G-GUTI. NOTE 1: If the UE is using any other scheme than the null-scheme, the SUCI does not reveal the SUPI. AMF may initiate authentication with AUSF to receive SUPI as specified in clause 6.1.3. In case the UE registers for Emergency Services and receives an Identity Request, the UE shall use the null-scheme for generating the SUCI in the Identity Response. NOTE 2: Registration for Emergency does not provide subscription identifier confidentiality. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.12.4 |
1,781 | Annex D (normative): UE requirements on ASN.1 comprehension | This clause specifies UE requirements regarding the ASN.1 transfer syntax support, i.e. the ASN.1 definitions to be comprehended by the UE. A UE that indicates release X in field accessStratumRelease shall comprehend the entire transfer syntax (ASN.1) of release X, in particular at least the first version upon ASN.1 freeze. The UE is however not required to support dedicated signalling related transfer syntax associated with optional features it does not support. In case a UE that indicates release X in field accessStratumRelease supports a feature specified in release Y, which is later than release X, (i.e. early UE implementation) additional requirements apply. The UE obviously also has to support the ASN.1 parts related to indicating support of the feature (in UE capabilities). Critical extensions (dedicated signaling) If the early implemented feature involves one or more critical extensions in dedicated signalling, the UE shall comprehend the parts of the transfer syntax (ASN.1) of release Y that are related to the feature implemented early. This, in particular, concerns the ASN.1 parts related to configuration of the feature. If configuration of an early implemented feature introduced in release Y involves a message or field that has been critically extended, the UE shall support configuration of all features supported by the UE that are associated with sub-fields of this critical extension. Apart from the early implemented feature(s), the UE needs, however, not to support functionality beyond what is defined in the release the UE indicates in access stratum release. Let's consider the example of a UE indicating value X in field accessStratumRelease that supports the features A1, A3, and A5, associated with fields fieldA1, fieldA3 and fieldA5 of InformationElementA (see ASN.1 below). The feature A5 implemented early is associated with fieldA5, and can only be configured by the –rY version of InformationElementA. In such case, the UE should support configuration of all the features A1, A3 and A5 associated with fields fieldA1, fieldA3 and fieldA5 by the –rY version of InformationElementA. If, however, one of the features was modified, e.g. the feature A3 associated with fieldA3, the network should assume the UE only supports the feature A3 according to the release it indicated in field accessStratumRelease (i.e. X). The UE is neither required to support the additional code-point (n80-vY0) nor the additional sub-field (fieldA3c-rY). InformationElementA-rX ::= SEQUENCE { fieldA1-rX InformationElementA1-rX OPTIONAL, -- Need N fieldA2-rX InformationElementA2-rX OPTIONAL, -- Need R fieldA3-rX InformationElementA3-rX OPTIONAL -- Need R } InformationElementA-rY ::= SEQUENCE { fieldA1-rY InformationElementA1-rX OPTIONAL, -- Need N fieldA2-rY InformationElementA2-rX OPTIONAL, -- Need R fieldA3-rY InformationElementA3-rY OPTIONAL, -- Need R fieldA4-rY InformationElementA4-rY OPTIONAL, -- Need R fieldA5-rY InformationElementA5-rY OPTIONAL -- Need R } InformationElementA3-rX ::= SEQUENCE { fieldA3a-rX InformationElementA3a-rX OPTIONAL, -- Need N fieldA3b-rX ENUMERATED {n10, n20, n40} OPTIONAL -- Need R } InformationElementA3-rY ::= SEQUENCE { fieldA3a-rY InformationElementA3a-rX OPTIONAL, -- Need N fieldA3b-rY ENUMERATED {n10, n20, n40, n80-vY0} OPTIONAL, -- Need R fieldA3c-rY InformationElementA3c-rY OPTIONAL -- Need R } Non-critical extensions (dedicated and broadcast signaling) If the early implemented feature involves one or more non-critical extensions, the UE shall comprehend the parts of the transfer syntax (ASN.1) of release Y that are related to the feature implemented early. If the early implemented feature involves one or more non-critical extensions in dedicated signaling, the network does not include extensions introduced after the release X that are not the parts related to the feature which the UE indicates early support of in UE capabilities. The UE shall anyway comprehend the parts of the transfer syntax (ASN.1) which indicate absence of such extensions. If the early implemented feature involves one or more non-critical extensions in system information, the SIB(s) containing the release Y fields related to the early implemented features may also include other extensions introduced after the release X that are not the parts related to the feature which the UE supports. The UE shall comprehend such intermediate fields (but again is not required to support the functionality associated with these intermediate fields, in case this concerns optional features not supported by the UE). | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | Annex |
1,782 | 5.9.2.2 Initiation | A UE shall apply the MCCH information acquisition procedure upon becoming interested to receive MBS broadcast services. A UE interested to receive MBS broadcast services shall apply the MCCH information acquisition procedure upon entering the cell providing SIB20 (e.g. upon power on, following UE mobility), upon receiving SIB20 of an SCell via dedicated signalling and upon receiving a notification that the MCCH information has changed due to the start of new MBS service(s). A UE that is receiving data via broadcast MRB shall apply the MCCH information acquisition procedure upon receiving a notification that the MCCH information has changed due to MCCH information modification other than the change caused by the start of new MBS service(s). NOTE 1: It is up to UE implementation how to address a possibility of the UE missing an MCCH change notification. NOTE 2: It is up to UE implementation to use the cell/tracking area list in the USD to avoid acquiring the MCCH when the UE is outside the MBS service area of the MBS broadcast service. Unless explicitly stated otherwise in the procedural specification, the MCCH information acquisition procedure overwrites any stored MCCH information, i.e. delta configuration is not applicable for MCCH information and the UE discontinues using a field if it is absent in MCCH information. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.9.2.2 |
1,783 | 6.3.4D.2 PSSS/SSSS time mask | The PSSS time mask / SSSS time mask defines the observation period between the Transmit OFF and ON power and between Transmit ON and OFF power for PSSS/SSSS transmissions in a subframe when not multiplexed with PSBCH in that subframe. There are no additional requirements on UE transmit power beyond that which is required in subclause 6.2.2 and subclause 6.6.2.3. Figure 6.3.4D.2-1: PSSS time mask for normal CP transmission (when not time-multiplexed with PSBCH) Figure 6.3.4D.2-2: PSSS time mask for extended CP transmission (when not time-multiplexed with PSBCH) Figure 6.3.4D.2-3: SSSS time mask (when not time-multiplexed with PSBCH) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.3.4D.2 |
1,784 | 8.3 Authentication | The 5G system shall support an efficient means to authenticate a user to an IoT device (e.g. biometrics). The 5G system shall be able to support authentication over a non-3GPP access technology using 3GPP credentials. The 5G system shall support operator-controlled alternative authentication methods (i.e. alternative to AKA) with different types of credentials for network access for IoT devices in isolated deployment scenarios (e.g. for industrial automation). The 5G system shall support a suitable framework (e.g. EAP) allowing alternative (e.g. to AKA) authentication methods with non-3GPP identities and credentials to be used for UE network access authentication in non-public networks. NOTE: Non-public networks can use 3GPP authentication methods, identities, and credentials for a UE to access network. Non-public networks are also allowed to utilize non-AKA based authentication methods such as provided by the EAP framework, for which the credentials can be stored in the ME. Subject to an agreement between an MNO and a 3rd party, the 5G system shall support a mechanism for the PLMN to authenticate and authorize UEs for access to both a hosted non-public network and private slice(s) of the PLMN associated with the hosted non-public network. The 5G network shall support a 3GPP supported mechanism to authenticate legacy non-3GPP devices for 5G LAN-VN access. The 5G system shall support a mechanism for the non-public network to authenticate and authorize UEs for access to network slices of that non-public network. The 5G system shall enable an NPN to be able to request a third-party service provider to perform NPN access network authentication of a UE based on non-3GPP identities and credentials supplied by the third-party service provider. The 5G system shall enable an NPN to be able to request a PLMN to perform NPN access network authentication of a UE based on 3GPP identities and credentials supplied by the PLMN. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 8.3 |
1,785 | A.4 Extension of the PDU specifications A.4.1 General principles to ensure compatibility | It is essential that extension of the protocol does not affect interoperability i.e. it is essential that implementations based on different versions of the RRC protocol are able to interoperate. In particular, this requirement applies for the following kind of protocol extensions: - Introduction of new PDU types (i.e. these should not cause unexpected behaviour or damage). - Introduction of additional fields in an extensible PDUs (i.e. it should be possible to ignore uncomprehended extensions without affecting the handling of the other parts of the message). - Introduction of additional values of an extensible field of PDUs. If used, the behaviour upon reception of an uncomprehended value should be defined. It should be noted that the PDU extension mechanism may depend on the logical channel used to transfer the message e.g. for some PDUs an implementation may be aware of the protocol version of the peer in which case selective ignoring of extensions may not be required. The non-critical extension mechanism is the primary mechanism for introducing protocol extensions i.e. the critical extension mechanism is used merely when there is a need to introduce a 'clean' message version. Such a need appears when the last message version includes a large number of non-critical extensions, which results in issues like readability, overhead associated with the extension markers. The critical extension mechanism may also be considered when it is complicated to accommodate the extensions by means of non-critical extension mechanisms. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | A.4 |
1,786 | 6.2.6.3 SCP profile | SCP profile maintained in an NRF includes the following information: - SCP ID. - FQDN or IP address of SCP. - Indication that the profile is of an SCP (e.g. NF type parameter set to type SCP). - SCP capacity information. - SCP load information. - SCP priority. - Location information for the SCP (see locality in clause 6.1.6.2.2 of TS 29.510[ 5G System; Network function repository services; Stage 3 ] [58]). - Served Location(s) (see servingScope in clause 6.1.6.2.2 of TS 29.510[ 5G System; Network function repository services; Stage 3 ] [58]). - Network Slice related Identifier(s) e.g. S-NSSAI, NSI ID. - Remote PLMNs reachable through SCP. - Endpoint addresses accessible via the SCP. - NF sets of NFs served by the SCP. - SCP Domain the SCP belongs to. If an SCP belongs to more than one SCP Domain, the SCP will be able bridge these domains, i.e. sending messages between these domains. NOTE: Service definition defines optional and mandatory parameters, see 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") | 6.2.6.3 |
1,787 | 4.16.15.2.1 Procedures for negotiation of planned data transfer with QoS requirements | This clause describes the PDTQ procedures to negotiate viable time window for the planned application data transfer via the support of the NEF. Figure 4.16.15.2.1-1: Negotiation for planned data transfer with QoS requirements Prior to the transmission of the Application AI/ML data, the AF negotiates with the 5G Core for the PDTQ policies that provide assistance for the application data transfer. The AF discovers its serving NEF, if it has not done so before, by using the mechanism described in clause 6.3.14 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 1a. The AF invokes the Nnef_PDTQPolicyNegotiation_Create Request (ASP Identifier, Number of UEs, list of Desired time windows, QoS Reference or individual QoS parameters, Alternative Service Requirements (optional), Network Area Information, Request for notification, Application Identifier). The Request for notification is an indication that PDTQ warning notification can be sent to the AF. NOTE 1: Based on AF's internal logic (policy), the AF may determine the minimum QoS requirements by considering the UEs expected to participate in the Desired time windows, the network input data and the trigger conditions for group application data transfer. 1b-1c. The NEF may authenticate the AF and authorize the PDTQ request from the AF. If the authentication/authorization of the AF's request has failed, the NEF will respond to the AF's request through the Nnef_PDTQPolicyNegotiation_Create Response with a failure result and the following steps are skipped. The NEF may map the ASP ID into DNN and S-NSSAI to be used in step 2. NOTE 2: The Application ID provided by the AF and the Application ID provided to NWDAF can be different, and in such a case, a mapping is performed by the PCF. 2. Based on an AF request, the NEF may translate the information provided by the AF (e.g. Network Area Information, etc.) based on the local policy and invokes the Npcf_PDTQPolicyControl_Create (ASP Identifier, Number of UEs, list of Desired time windows, QoS Reference or individual QoS parameters, Alternative Service Requirements (optional), Network Area Information, Request for notification, Application Identifier) with the H-PCF to authorize the creation of the policy regarding the PDTQ. If the PCF was provided with Request for notification, then PCF will send PDTQ warning notification to the AF as specified in clause 4.16.15.2.2 to notify the AF when the network performance or DN Performance in the area of interest reaches the Reporting Threshold set by the PCF based on operator configuration or the PCF determines to update the previously selected PDTQ policy based on the latest periodic reported network performance or DN Performance analytics as described in clause 6.1.2.7 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. The PCF may be configured to map the ASP identifier to a target DNN and S-NSSAI if the NEF did not provide the DNN, S-NSSAI to the PCF. 3. H-PCF queries the UDR to retrieve all existing PDTQ polices for all the ASPs using Nudr_DM_Query (Policy Data, Planned Data Transfer with QoS requirements) service operation. 4. The UDR provides all the stored PDTQ policies and corresponding related information (e.g. the Number of UEs, the list of Desired time windows) to the H-PCF. 5. Based on information provided by the AF and other available information, the H-PCF queries or/and subscribes to the NWDAF as defined in clause 6.6.4 or clause 6.14.4 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50] to request the Network Performance analytics or the DN Performance analytics. When requesting the Network Performance analytics or the DN performance analytics, if "any UE" is used, then the AoI information is used to identify the target gNB(s) for the prediction of the availability of the network resources. The DNN, S-NSSAI and Application ID may be provided by H-PCF as Analytics Filter Information when requesting or subscribing to the relevant Analytic ID. 6. By referring to the outcome of the analytics report as described in clause 6.1.2.7 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20], H-PCF determines one or more PDTQ policies. Each PDTQ policy includes a recommended time window for the traffic transfer for each of the AF sessions for each of the UEs involved. 7. The PCF sends one or more PDTQ policies to NEF in Npcf_PDTQPolicyControl_Create Response including the PDTQ Reference ID. 8. The NEF sends a Nnef_PDTQPolicyNegotiation_Create response to the AF to provide one or more PDTQ policies together with the PDTQ Reference ID. If the NEF received only one PDTQ policy from the PCF, steps 9-12 are not executed and the flow proceeds to step 13. Otherwise, the flow proceeds to step 9. 9. If more than one PDTQ policies were provided to the AF, the AF selects one of the PDTQ policies and notifies NEF for the selected PDTQ policy via Nnef_PDTQPolicyNegotiation_Update request together with the PDTQ Reference ID. The AF stores the PDTQ Reference ID for the future interaction with the PCF. 10-12. The NEF notifies H-PCF about the selected PDTQ policy by the AF. The H-PCF acknowledges NEF. The NEF responds to the AF request with a Nnef_PDTQPolicyNegotiation_Update Response. 13-14. The H-PCF stores the PDTQ Reference ID together with the new PDTQ policy in the UDR by invoking Nudr_DM_Update (PDTQ Reference ID, Policy Data, Planned Data Transfer with QoS requirements). The UDR sends a response to the H-PCF as acknowledgement. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.16.15.2.1 |
1,788 | 4.3.2.6 Abnormal cases | (a) RR connection failure: Upon detection of a RR connection failure before the AUTHENTICATION RESPONSE message is received, the network shall release all MM connections (if any) and abort any ongoing MM specific procedure. (b) Expiry of timer T3260: The authentication procedure is supervised on the network side by the timer T3260. At expiry of this timer the network may release the RR connection. In this case the network shall abort the authentication procedure and any ongoing MM specific procedure, release all MM connections if any, and initiate the RR connection release procedure described in subclause 3.5 of 3GPP TS 44.018[ None ] [84] (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). (c) Authentication failure (reject cause "MAC failure" or "GSM authentication unacceptable"): The MS shall send an AUTHENTICATION FAILURE message, with reject cause "MAC failure" or "GSM authentication unacceptable" according to subclause 4.3.2.5.1, to the network and start timer T3214. Furthermore, the MS shall stop any of the retransmission timers that are running (e.g. T3210, T3220 or T3230). Upon the first receipt of an AUTHENTICATION FAILURE message from the MS with reject cause "MAC failure" or "GSM authentication unacceptable", the network may initiate the identification procedure described in subclause 4.3.3. This is to allow the network to obtain the IMSI from the MS. The network may then check that the TMSI originally used in the authentication challenge corresponded to the correct IMSI. Upon receipt of the IDENTITY REQUEST message from the network, the MS shall send the IDENTITY RESPONSE message. NOTE: Upon receipt of an AUTHENTICATION FAILURE message from the MS with reject cause "MAC failure" or "GSM authentication unacceptable", the network may also terminate the authentication procedure (see subclause 4.3.2.5). If the TMSI/IMSI mapping in the network was incorrect, the network should respond by sending a new AUTHENTICATION REQUEST message to the MS. Upon receiving the new AUTHENTICATION REQUEST message from the network, the MS shall stop the timer T3214, if running, and then process the challenge information as normal. If theTMSI/IMSI mapping in the network was correct, the network should terminate the authentication procedure by sending an AUTHENTICATION REJECT message. If the network is validated successfully (an AUTHENTICATION REQUEST message that contains a valid SQN and MAC is received), the MS shall send the AUTHENTICATION RESPONSE message to the network and shall start any retransmission timers (e.g. T3210, T3220 or T3230), if they were running and stopped when the MS received the first failed AUTHENTICATION REQUEST message. If the MS receives the second AUTHENTICATION REQUEST message while T3214 is running, and the MAC value cannot be resolved or the message contains a GSM authentication challenge, the MS shall follow the procedure specified in this subclause (c), starting again from the beginning. If the SQN is invalid, the MS shall proceed as specified in (d). It can be assumed that the source of the authentication challenge is not genuine (authentication not accepted by the MS) if any of the following occur: - the timer T3214 expires; - the MS detects any combination of the authentication failures: "MAC failure", "invalid SQN", and "GSM authentication unacceptable", during three consecutive authentication challenges. The authentication challenges shall be considered as consecutive only, if the authentication challenges causing the second and third authentication failure are received by the MS, while the timer T3214 or T3216 started after the previous authentication failure is running. The MS shall stop timer T3214, if the timer is running and the MS detects an RR connection failure or the network releases the RR connection. When it has been deemed by the MS that the source of the authentication challenge is not genuine (i.e. authentication not accepted by the MS), the MS shall behave as described in subclause 4.3.2.6.1. Figure 4.2/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Authentication Failure Procedure (reject cause "MAC failure" or "GSM authentication unacceptable") (d) Authentication failure (reject cause "synch failure"): The MS shall send an AUTHENTICATION FAILURE message, with reject cause "synch failure", to the network and start the timer T3216. Furthermore, the MS shall stop any of the retransmission timers that are running (e.g. T3210, T3220 or T3230). Upon the first receipt of an AUTHENTICATION FAILURE message from the MS with the reject cause "synch failure", the network shall use the returned AUTS parameter from the authentication failure parameter IE in the AUTHENTICATION FAILURE message, to re-synchronise. The re-synchronisation procedure requires the VLR/MSC to delete all unused authentication vectors for that IMSI and obtain new vectors from the HLR. When re-synchronisation is complete, the network shall initiate the authentication procedure. Upon receipt of the AUTHENTICATION REQUEST message, the MS shall stop the timer T3216, if running. NOTE: Upon receipt of two consecutive AUTHENTICATION FAILURE messages from the MS with reject cause "synch failure", the network may terminate the authentication procedure by sending an AUTHENTICATION REJECT message. If the network is validated successfully (a new AUTHENTICATION REQUEST message is received which contains a valid SQN and MAC) while T3216 is running, the MS shall send the AUTHENTICATION RESPONSE message to the network and shall start any retransmission timers (e.g. T3210, T3220 or T3230), if they were running and stopped when the MS received the first failed AUTHENTICATION REQUEST message. If the MS receives the second AUTHENTICATION REQUEST message while T3216 is running, and the MAC value cannot be resolved or the message contains a GSM authentication challenge, the MS shall proceed as specified in (c); if the SQN is invalid, the MS shall follow the procedure specified in this subclause (d), starting again fom the beginning. The MS shall deem that the network has failed the authentication check and behave as described in subclause 4.3.2.6.1, if any of the following occurs: - the timer T3216 expires; - the MS detects any combination of the authentication failures: "MAC failure", "invalid SQN", and "GSM authentication unacceptable", during three consecutive authentication challenges. The authentication challenges shall be considered as consecutive only, if the authentication challenges causing the second and third authentication failure are received by the MS, while the timer T3214 or T3216 started after the previous authentication failure is running. The MS shall stop timer T3216, if the timer is running and the MS detects an RR connection failure or the network releases the RR connection. When it has been deemed by the MS that the source of the authentication challenge is not genuine (i.e. authentication not accepted by the MS), the MS shall behave as described in subclause 4.3.2.6.1. Figure 4.2a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Authentication Failure Procedure (reject cause "Synch failure") Upon receipt of an AUTHENTICATION REJECT message, the mobile station shall perform the actions as specified in subclause 4.3.2.5. If an MS has an MM connection for an emergency call established or is establishing an MM connection for an emergency call when timer T3214 or T3216 expires, the MS shall not deem that the network has failed the authentication check and not behave as described in subclause 4.3.2.6.1. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.3.2.6 |
1,789 | – SDAP-Config | The IE SDAP-Config is used to set the configurable SDAP parameters for a data radio bearer. All configured instances of SDAP-Config with the same value of pdu-Session correspond to the same SDAP entity as specified in TS 37.324[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Service Data Adaptation Protocol (SDAP) specification ] [24]. SDAP-Config information element -- ASN1START -- TAG-SDAP-CONFIG-START SDAP-Config ::= SEQUENCE { pdu-Session PDU-SessionID, sdap-HeaderDL ENUMERATED {present, absent}, sdap-HeaderUL ENUMERATED {present, absent}, defaultDRB BOOLEAN, mappedQoS-FlowsToAdd SEQUENCE (SIZE (1..maxNrofQFIs)) OF QFI OPTIONAL, -- Need N mappedQoS-FlowsToRelease SEQUENCE (SIZE (1..maxNrofQFIs)) OF QFI OPTIONAL, -- Need N ... } QFI ::= INTEGER (0..maxQFI) -- TAG-SDAP-CONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
1,790 | 4.11.1 Attempted PUCCH allocations for SCell scheduling in Carrier Aggregation | a) This measurement provides the number of attempted PUCCH allocations in the PCell for SCell scheduling in Carrier Aggregation. This measurement is split into subcounters for the PUCCH format 3 and PUCCH format 1bwcs. b) CC c) On allocation of PUCCH resources in the Pcell for Scell scheduling in Carrier Aggregation. d) Each measurement is an integer value. e) DRB.PucchAllocNbrAtt.PUCCHFormat where PUCCHFormat identifies the PUCCH format, which is either “format3” or “format1bwcs”. f) EUtranCellFDD EUtranCellTDD g) Valid for packet switched traffic h) EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.11.1 |
1,791 | 16.9.2.6 RRC | The RRC sublayer provides the following services and functions over the PC5 interface: - Transfer of a PC5-RRC message between peer UEs; - Maintenance and release of a PC5-RRC connection between two UEs; - Detection of sidelink radio link failure for a PC5-RRC connection; - Measurement configuration and reporting related to sidelink. A PC5-RRC connection is a logical connection between two UEs for a pair of Source and Destination Layer-2 IDs which is considered to be established after a corresponding PC5 unicast link is established as specified in TS 23.287[ Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services ] [40]. There is one-to-one correspondence between the PC5-RRC connection and the PC5 unicast link. A UE may have multiple PC5-RRC connections with one or more UEs for different pairs of Source and Destination Layer-2 IDs. Separate PC5-RRC procedures and messages are used for a UE to transfer UE capability and sidelink configuration to the peer UE, as specified in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [3]. Both peer UEs can exchange their own UE capability and sidelink configuration using separate bi-directional procedures in both sidelink directions. If it is not interested in sidelink transmission, if sidelink RLF on the PC5-RRC connection is declared, or if the Layer-2 link release procedure is completed as specified in TS 23.287[ Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services ] [40], UE releases the PC5-RRC connection. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.9.2.6 |
1,792 | 8.2.3.1 Intra-CU topology adaptation procedure in SA | During the intra-CU topology adaptation in SA, both the source and the target parent node are served by the same IAB-donor-CU. The target parent node may use a different IAB-donor-DU than the source parent node. The source path may have common nodes with the target path. Figure 8.2.3.1-1 shows an example of the topology adaptation procedure, where the target parent node uses a different IAB-donor-DU than the one used by the source parent node. Figure 8.2.3.1-1: IAB intra-CU topology adaptation procedure 1. The migrating IAB-MT sends a MeasurementReport message to the source parent node IAB-DU. This report is based on a Measurement Configuration the migrating IAB-MT received from the IAB-donor-CU before. 2. The source parent node IAB-DU sends an UL RRC MESSAGE TRANSFER message to the IAB-donor-CU to convey the received MeasurementReport. 3. The IAB-donor-CU sends a UE CONTEXT SETUP REQUEST message to the target parent node IAB-DU to create the UE context for the migrating IAB-MT and set up one or more bearers. These bearers can be used by the migrating IAB-MT for its own signalling, and, optionally, data traffic. 4. The target parent node IAB-DU responds to the IAB-donor-CU with a UE CONTEXT SETUP RESPONSE message. 5. The IAB-donor-CU sends a UE CONTEXT MODIFICATION REQUEST message to the source parent node IAB-DU, which includes a generated RRCReconfiguration message. The RRCReconfiguration message includes a default BH RLC channel and a default BAP Routing ID configuration for UL F1-C/non-F1 traffic mapping on the target path. It may include additional BH RLC channels. This step may also include allocation of TNL address(es) that is (are) routable via the target IAB-donor-DU. The new TNL address(es) may be included in the RRCReconfiguration message as a replacement for the TNL address(es) that is (are) routable via the source IAB-donor-DU. In case IPsec tunnel mode is used to protect the F1 and non-F1 traffic, the allocated TNL address is outer IP address. The TNL address replacement is not necessary if the source and target paths use the same IAB-donor-DU. The Transmission Action Indicator in the UE CONTEXT MODIFICATION REQUEST message indicates to stop the data transmission to the migrating IAB-node. 6. The source parent node IAB-DU forwards the received RRCReconfiguration message to the migrating IAB-MT. 7. The source parent node IAB-DU responds to the IAB-donor-CU with the UE CONTEXT MODIFICATION RESPONSE message. 8. A Random Access procedure is performed at the target parent node IAB-DU. 9. The migrating IAB-MT responds to the target parent node IAB-DU with an RRCReconfigurationComplete message. 10. The target parent node IAB-DU sends an UL RRC MESSAGE TRANSFER message to the IAB-donor-CU to convey the received RRCReconfigurationComplete message. Also, uplink packets can be sent from the migrating IAB-MT, which are forwarded to the IAB-donor-CU through the target parent node IAB-DU. These UL packets belong to the IAB-MT’s own signalling and, optionally, data traffic. 11. The IAB-donor-CU configures BH RLC channels and BAP-sublayer routing entries on the target path between the target parent IAB-node and target IAB-donor-DU as well as DL mappings on the target IAB-donor-DU for the migrating IAB-node’s target path. These configurations may be performed at an earlier stage, e.g. immediately after step 3, or before step 3. The IAB-donor-CU may establish additional BH RLC channels to the migrating IAB-MT via RRC message. 12. The F1-C connections are switched to use the migrating IAB-node’s new TNL address(es), IAB-donor-CU updates the UL BH information associated to each GTP-tunnel to migrating IAB-node. This step may also update UL FTEID and DL FTEID associated to each GTP-tunnel. All F1-U tunnels are switched to use the migrating IAB-node’s new TNL address(es). This step may use non-UE associated signaling in E1 and/or F1 interface to provide updated UP configuration for F1-U tunnels of multiple connected UEs or child IAB-MTs. The IAB-donor-CU may also update the UL BH information associated with non-UP traffic. Implementation must ensure the avoidance of potential race conditions, i.e. no conflicting configurations are concurrently performed using UE-associated and non-UE-associated procedures. In case IPsec tunnel mode is used for TNL protection, the IAB-node may use MOBIKE (IETF RFC 4555 [29]) to migrate the IPsec tunnel to the new IP outer addresses. After the completion of the MOBIKE procedure, the IAB-DU initiates an F1AP gNB-DU Configuration Update procedure from which the IAB-donor-CU can conclude whether the existing inner IP address(es) (e.g. for SCTP association) and the DL F-TEID can be reused. If new TNL addresses for F1-C traffic are configured, new SCTP association(s) between the migrating IAB-node and the IAB-donor-CU may be established using the new TNL address information of the migrating IAB-node. The migrating IAB-node sends an F1AP gNB-DU CONFIGURATION UPDATE message to the IAB-donor-CU, which may include new (outer) IP addresses and corresponding new (inner) IP address for the F1-U traffic to be switched to the target path. 13. The IAB-donor-CU sends a UE CONTEXT RELEASE COMMAND message to the source parent node IAB-DU. 14. The source parent node IAB-DU releases the migrating IAB-MT’s context and responds to the IAB-donor-CU with a UE CONTEXT RELEASE COMPLETE message. 15. The IAB-donor-CU releases BH RLC channels and BAP-sublayer routing entries on the source path between source parent IAB-node and source IAB-donor-DU. NOTE: In case that the source path and target path have common nodes, the BH RLC channels and BAP-sublayer routing entries of those nodes may not need to be released in Step 15. Steps 11, 12 and 15 should also be performed for the migrating IAB-node’s descendant nodes, as follows: The IAB-donor-CU may allocate new TNL address(es) that is (are) routable via the target IAB-donor-DU to the descendent nodes via RRCReconfiguration message. If needed, the IAB-donor-CU may also provide a new default UL mapping which includes a default BH RLC channel and a default BAP Routing ID for UL F1-C/non-F1 traffic on the target path, to the descendant nodes via RRCReconfiguration message. If needed, the IAB-donor-CU configures BH RLC channels, BAP-sublayer routing entries and BH RLC channel mappings on the target path for the descendant nodes in the same manner as described for the migrating IAB-node in step 11. The descendant nodes switch their F1-C connections and F1-U tunnels to new TNL addresses that are anchored at the new IAB-donor-DU, in the same manner as described for the migrating IAB-node in step 12. Based on implementation, these steps can be performed after or in parallel with the handover of the migrating IAB-node. To enable performing these steps in parallel, the IAB-donor-CU sends the RRCReconfiguration message with the new TNL address(es) and the new default BAP configuration to the descendent node while the migrating IAB-MT is still connected with source parent node, for example, before Step 5. In this case, the UE CONTEXT MODIFICATION REQUEST message carrying this RRCReconfiguration message includes a conditional delivery indication for the descendent node’s parent IAB-DU. Based on this indication, the parent IAB-DU retains the RRCReconfiguration message until the conditions for delivery are met, as specified in TS 38.473[ NG-RAN; F1 Application Protocol (F1AP) ] [4]. The IAB-donor-CU may further configure the BAP-sublayer routing entries on the migrating IAB-node and the descendant nodes while the migrating IAB-MT is still connected with the source parent node. NOTE: In upstream direction, in-flight packets between the source parent node and the IAB-donor-CU can be delivered even after the target path is established. NOTE: In-flight downlink data in the source path may be discarded, up to implementation via the NR user plane protocol (TS 38.425[ NG-RAN; NR user plane protocol ] [24]). NOTE: The IAB-donor-CU can determine the unsuccessfully transmitted downlink data over the backhaul link by implementation. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.2.3.1 |
1,793 | 15.3.2.3 Application layer initialization | Once SCTP connectivity has been established, the NG-RAN node and its candidate peer NG-RAN node are in a position to exchange application level configuration data over XnAP needed for the two nodes to interwork correctly on the Xn interface: - The NG-RAN node provides the relevant configuration information to the candidate NG-RAN node, which includes served cell information; - The candidate NG-RAN node provides the relevant configuration information to the initiating NG-RAN node, which includes served cell information; - When the application layer initialization is successfully concluded, the dynamic configuration procedure is completed and the Xn interface is operational; - The NG-RAN node shall keep neighbouring NG-RAN nodes updated with the complete list of served cells, or, if requested by the peer NG-RAN node, by a limited list of served cells, while the Xn interface is operational. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 15.3.2.3 |
1,794 | 7.5.1D Minimum requirements for ProSe | The UE shall fulfil the minimum requirement specified in Table 7.5.1D-1 for all values of an adjacent channel interferer up to –25 dBm. However it is not possible to directly measure the ACS, instead the lower and upper range of test parameters are chosen in Table 7.5.1D-2 and Table 7.5.1D-3 where the throughput shall be ≥ 95% of the maximum throughput of the reference measurement channels as specified in Annex A.6.2. Table 7.5.1D-1: Adjacent channel selectivity for ProSe Table 7.5.1D-2: Test parameters for Adjacent channel selectivity for ProSe, Case 1 Table 7.5.1D-3: Test parameters for Adjacent channel selectivity for ProSe, Case 2 | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 7.5.1D |
1,795 | 6.9.2.2 Key derivations for context modification procedure | As outlined in clause 6.9.2.1, whenever a fresh KgNB is calculated from the KAMF, the AMF shall transfer the KgNB to the serving ng-eNB/gNB in a message modifying the security context in the ng-eNB/gNB. The AMF and the UE shall compute the fresh KgNB as defined in Annex A.9 according to the rules in clause 6.9.6.4. An NCC value 0 is associated with the fresh KgNB. From the fresh KgNB, the ng-eNB/gNB and the UE shall compute the KNG-RAN* as described in Annex A.11 and A.12 and then use the computed KNG-RAN* as the KgNB/KeNB as described in clause 6.9.4.4. NOTE 1: Unlike EPS, in 5GS the NAS and the AS security contexts are synchronized as a part of handover procedure, if a handover is occurring. See sub-clauses under the clause 6.9.2.3 (key derivations during handover) of the present document. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.9.2.2 |
1,796 | 7.6.2 Out-of-band blocking | Out-of-band band blocking is defined for an unwanted CW interfering signal falling more than 15 MHz below or above the UE receive band. For the first 15 MHz below or above the UE receive band the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.1 and subclause 7.6.1 shall be applied. For CA configurations including Band 46 or Band 49, out-of-band band blocking is defined for an unwanted CW interfering signal falling more than 60 MHz below or above the UE receive band (see Table 7.6.2.1A-0a). For the first 60 MHz below or above the UE receive band the appropriate in-band blocking or adjacent channel selectivity in subclause 7.5.1A and subclause 7.6.1A shall be applied. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 7.6.2 |
1,797 | 4.4.2 Periodic updating | Periodic updating may be used to notify periodically the availability of the mobile station to the network. Periodic updating is performed by using the location updating procedure. The location updating type information element in the LOCATION UPDATING REQUEST message shall indicate periodic updating. The procedure is controlled by the timer T3212 in the mobile station. The MS indicates in the MS network feature support IE whether it supports the extended value for timer T3212. If the MS receives the Per MS T3212 IE in the LOCATION UPDATING ACCEPT message, the MS shall use this IE to determine the value of T3212 instead of the value of T3212 that is broadcast. If the MS does not receive the Per MS T3212 IE in the LOCATION UPDATING ACCEPT message, the MS shall use the value of T3212 that is broadcast . If the timer is not already started, the timer is started each time the mobile station enters the MM IDLE substate NORMAL SERVICE or ATTEMPTing TO UPDATE. When the MS leaves the MM Idle State the timer T3212 shall continue running until explicitly stopped. The timer is stopped (shall be set to its initial value for the next start) when: - a LOCATION UPDATING ACCEPT or LOCATION UPDATING REJECT message is received; - an AUTHENTICATION REJECT message is received; - the first MM message is received, or security mode setting is completed in the case of MM connection establishment, except when the most recent service state is LIMITED SERVICE; - the mobile station has responded to paging and thereafter has received the first correct layer 3 message except RR message; - the mobile station is deactivated (i.e. equipment powered down or SIM/USIM removed). When the timer T3212 expires, the location updating procedure is started and the timer shall be set to its initial value for the next start. If the mobile station is in other state than MM Idle when the timer expires the location updating procedure is delayed until the MM Idle State is entered. The conditions under which the periodic location updating procedure is used by a mobile station in the MM IDLE state are defined for each service state in subclause 4.2.2. If the mobile station is in service state NO CELL AVAILABLE, LIMITED SERVICE, PLMN SEARCH or PLMN SEARCH-NORMAL SERVICE when the timer expires the location updating procedure is delayed until this service state is left. In A/Gb mode and GERAN Iu mode, the (periodic) location updating procedure is not started if the BCCH information at the time the procedure is triggered indicates that periodic location shall not be used. The timeout value is broadcasted in the L3-RR SYSTEM INFORMATION TYPE 3 message on the BCCH, in the Control channel description IE, see 3GPP TS 44.018[ None ] [84] subclause 10.5.2.11. In UTRAN Iu mode, the (periodic) location updating procedure is not started if the information on BCCH or in the last received dedicated system information at the time the procedure is triggered indicates that periodic location shall not be used. The timeout value is included in the CS domain specific system information element. The T3212 timeout value shall not be changed in the NO CELL AVAILABLE, LIMITED SERVICE, PLMN SEARCH and PLMN SEARCH-NORMAL SERVICE states. If the MS, configured to use CS fallback and SMS over SGs, or SMS over SGs only, enters a GERAN or UTRAN cell after intersystem change from S1 mode to Iu or A/Gb mode in NMO II, the TIN indicates "GUTI", and the location area of the current cell is the same as the stored location area, the MS shall start timer T3212, with a value set to the shorter of the values of the remaining value of timer T3412, and the broadcast T3212 timeout value. When the MS supporting N1 mode in MS operation modes A or B moves from NG-RAN coverage to GERAN coverage, or from NG-RAN coverage to UTRAN coverage, the network operates in network operation mode II, the location area of the current cell is the same as the stored location area, the broadcast value of T3212 does not indicate "deactivated" and the T3212 has expired, the MS may intiate the periodic location updating procedure. When a change of the broadcast T3212 timeout value has to be taken into account and the timer is running (at change of the serving cell or, change of the broadcast value of T3212), the MS shall behave as follows: let t1 be the new T3212 timeout value and let t be the current timer value at the moment of the change to the new T3212 timeout value; then the timer shall be restarted with the value t modulo t1. When the mobile station is activated, or when a change of the broadcast T3212 timeout value has to be taken into account and the timer is not running, the mobile station shall behave as follows: let t1 be the new T3212 timeout value, the new timer shall be started at a value randomly, uniformly drawn between 0 and t1. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.4.2 |
1,798 | – PDSCH-TimeDomainResourceAllocationList | The IE PDSCH-TimeDomainResourceAllocation is used to configure a time domain relation between PDCCH and PDSCH. The PDSCH-TimeDomainResourceAllocationList contains one or more of such PDSCH-TimeDomainResourceAllocations. The network indicates in the DL assignment which of the configured time domain allocations the UE shall apply for that DL assignment. The UE determines the bit width of the DCI field based on the number of entries in the PDSCH-TimeDomainResourceAllocationList. Value 0 in the DCI field refers to the first element in this list, value 1 in the DCI field refers to the second element in this list, and so on. PDSCH-TimeDomainResourceAllocationList information element -- ASN1START -- TAG-PDSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-START PDSCH-TimeDomainResourceAllocationList ::= SEQUENCE (SIZE(1..maxNrofDL-Allocations)) OF PDSCH-TimeDomainResourceAllocation PDSCH-TimeDomainResourceAllocation ::= SEQUENCE { k0 INTEGER(0..32) OPTIONAL, -- Need S mappingType ENUMERATED {typeA, typeB}, startSymbolAndLength INTEGER (0..127) } PDSCH-TimeDomainResourceAllocationList-r16 ::= SEQUENCE (SIZE(1..maxNrofDL-Allocations)) OF PDSCH-TimeDomainResourceAllocation-r16 PDSCH-TimeDomainResourceAllocation-r16 ::= SEQUENCE { k0-r16 INTEGER(0..32) OPTIONAL, -- Need S mappingType-r16 ENUMERATED {typeA, typeB}, startSymbolAndLength-r16 INTEGER (0..127), repetitionNumber-r16 ENUMERATED {n2, n3, n4, n5, n6, n7, n8, n16} OPTIONAL, -- Cond Formats1-0_1-1_4-0_4-1_4-2 ..., [[ k0-v1710 INTEGER(33..128) OPTIONAL -- Need S ]], [[ repetitionNumber-v1730 ENUMERATED {n2, n3, n4, n5, n6, n7, n8, n16} OPTIONAL -- Cond Format1-2 ]] } Dummy-TDRA-List ::= SEQUENCE (SIZE(1.. maxNrofDL-Allocations)) OF MultiPDSCH-TDRA-r17 MultiPDSCH-TDRA-List-r17 ::= SEQUENCE (SIZE(1.. maxNrofDL-AllocationsExt-r17)) OF MultiPDSCH-TDRA-r17 MultiPDSCH-TDRA-r17 ::= SEQUENCE { pdsch-TDRA-List-r17 SEQUENCE (SIZE(1..maxNrofMultiplePDSCHs-r17)) OF PDSCH-TimeDomainResourceAllocation-r16, ... } -- TAG-PDSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
1,799 | 5.4.4.1 PDN GW initiated bearer deactivation | The bearer deactivation procedure for a GTP based S5/S8 is depicted in figure 5.4.4.1-1. This procedure can be used to deactivate a dedicated bearer or deactivate all bearers belonging to a PDN address. If the default bearer belonging to a PDN connection is deactivated, the PDN GW deactivates all bearers belonging to the PDN connection. When the last bearer belonging to the last PDN connection of a given APN is released, the PGW may forward to the MME the APN Rate Control Status for storing it in the MM context according to clause 4.7.7.3. Figure 5.4.4.1-1: PDN GW Initiated Bearer Deactivation NOTE 1: Steps 3-8 are common for architecture variants with GTP based S5/S8 and PMIP-based S5/S8. For an PMIP-based S5/S8, procedure steps (A) and (B) are defined in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [2]. Steps 1, 2, 9 and 10 concern GTP-based S5/S8. 1. If dynamic PCC is not deployed, the PDN GW is triggered to initiate the Bearer Deactivation procedure due either a QoS policy or on request from the MME (as outlined in clause 5.4.4.2) or on intra-node signalling request from the HeNB to release the LIPA PDN Connection. Optionally, the PCRF sends QoS policy to the PDN GW. This corresponds to the initial steps of the PCRF-initiated IP-CAN Session Modification procedure or the response to the PCEF initiated IP-CAN Session Modification procedure as defined in TS 23.203[ Policy and charging control architecture ] [6], up to the point that the PDN GW requests IP-CAN Bearer Signalling. The PCC decision provision message may indicate that User Location Information and/or UE Time Zone Information is to be provided to the PCRF as defined in TS 23.203[ Policy and charging control architecture ] [6]. If dynamic PCC is not deployed, the PDN GW may apply local QoS policy. The PDN GW initiated Bearer deactivation is also performed when handovers occur from 3GPP to non-3GPP, in which case, the default bearer and all the dedicated bearers associated with the PDN address are released, but the PDN address is kept in the PDN GW. For an emergency PDN connection the PDN GW initiates the deactivation of all bearers of that emergency PDN connection when the PDN connection is inactive (i.e. not transferring any packets) for a configured period of time or when triggered by dynamic PCC. For an PDN connection established towards the APN dedicated for Restricted Local Operator Services, the PDN GW initiates the deactivation of all bearers of the PDN connection per local operator policy e.g. when the duration of such PDN connection reaches a pre-configured period of time. 2. The PDN GW sends a Delete Bearer Request (PTI, EPS Bearer Identity, Causes and, optionally, APN Rate Control Status according to clause 4.7.7.3) message to the Serving GW. The Procedure Transaction Id (PTI) parameter in this step and in the following steps is only used when the procedure was initiated by a UE Requested Bearer Resource Modification Procedure - see clause 5.4.5. This message can include an indication that all bearers belonging to that PDN connection shall be released. The PDN GW includes 'Cause' IE in the Delete Bearer Request message and sets the IE to 'RAT changed from 3GPP to Non-3GPP' if the Delete Bearer Request message is caused by a handover from 3GPP to non-3GPP. 3a. The Serving GW sends the Delete Bearer Request (PTI, EPS Bearer Identity, Cause and, optionally, APN Rate Control Status) message to the MME. This message can include an indication that all bearers belonging to that PDN connection shall be released. 3b. If ISR is activated, the Serving GW sends the Delete Bearer Request (PTI, EPS Bearer Identity, Cause) message to the SGSN. This message can include an indication that all bearers belonging to that PDN connection shall be released, and the SGSN releases all bearer resources of the PDN connection. NOTE 2: If all the bearers belonging to a UE are released due to a handover from 3GPP to non-3GPP, the SGSN changes the MM state of the UE to IDLE (GERAN network) or PMM-DETACHED (UTRAN network). If ISR is activated, upon receiving Delete Bearer Request from SGW for the last PDN connection for a given UE, MME shall locally de-activate ISR. NOTE 3: In this case, SGSN locally de-activates ISR as well (see TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7]). If received, the MME stores the APN Rate Control Status in the MM context. Steps 4 to 7 are not performed if at least one of the following three conditions is fulfilled: (i) The UE is in ECM-IDLE and the last PDN connection of the UE is not being deleted and the Delete Bearer Request received from the Serving GW does not contain the cause "reactivation requested", which has been sent from the PDN GW; (ii) UE is in ECM-IDLE and the last PDN connection is deleted due to ISR deactivation; (iii) UE is in ECM-IDLE and the last PDN connection is deleted in 3GPP due to handover to non-3GPP access. When steps 4 to 7 are not performed, the EPS bearer state is synchronized between the UE and the network at the next ECM-IDLE to ECM-CONNECTED transition (e.g. Service Request or TAU procedure). 4a. If the last PDN connection of a UE that does not support "Attach without PDN connectivity" is being released and the bearer deletion is neither due to ISR deactivation nor due to handover to non-3GPP accesses, the MME explicitly detaches the UE by sending a Detach Request message to the UE. If the UE is in ECM-IDLE state the MME initiates paging via Network Triggered Service Request procedure in clause 5.3.4.3 from step 3a onwards in order to inform UE of the request. Steps 4b to 7b are skipped in this case, and the procedure continues from step 7c. 4b. If the UE is in ECM-IDLE state and the reason for releasing PDN connection is "reactivation requested", the MME initiates paging via Network Triggered Service Request procedure in clause 5.3.4.3 from step 3a onwards in order to inform UE of the request and step 4c is performed after completion of the paging. 4c. If the release of the bearer in E-UTRAN has already been signalled to the MME, steps 4c to 7 are omitted. Otherwise, if this is not the last PDN connection for the UE which is being released, the MME sends the S1-AP Deactivate Bearer Request (EPS Bearer Identity) message to the eNodeB. The MME builds a NAS Deactivate EPS Bearer Context Request message including the EPS Bearer Identity and a WLAN offloadability indication, and includes it in the S1-AP Deactivate Bearer Request message. When the bearer deactivation procedure was originally triggered by a UE request, the NAS Deactivate EPS Bearer Context Request message includes the PTI. The MME may include an indication whether the traffic of this PDN Connection is allowed to be offloaded to WLAN as described in clause 4.3.23 if the PDN connection is not released. 5. The eNodeB sends the RRC Connection Reconfiguration message including the EPS Radio Bearer Identity to release and the NAS Deactivate EPS Bearer Context Request message to the UE. 6a. The UE RRC releases the radio bearers indicated in the RRC message in step 5, and indicates the radio bearer status to the UE NAS. Then the UE NAS removes the UL TFTs and EPS Bearer Identity according to the radio bearer status indication from the UE RRC. The UE responds to the RRC Connection Reconfiguration Complete message to the eNodeB. 6b. The eNodeB acknowledges the bearer deactivation to the MME with a Deactivate Bearer Response (EPS Bearer Identity, ECGI, TAI, PSCell ID, Secondary RAT usage data) message. If the PLMN has configured secondary RAT usage reporting and the eNodeB has Secondary RAT usage data to report, the Secondary RAT usage data is included. The PSCell ID is included if Dual Connectivity is active for the UE in the RAN. The MME shall be prepared to receive this message either before or after the Session Management Response message sent in step 7b, and before or after, any Detach Request message sent in step 7c. 7a The UE NAS layer builds a Deactivate EPS Bearer Context Accept message including EPS Bearer Identity. The UE then sends a Direct Transfer (Deactivate EPS Bearer Context Accept) message to the eNodeB. 7b. The eNodeB sends an Uplink NAS Transport (Deactivate EPS Bearer Context Accept) message to the MME. 7c. If the UE receives the Detach Request message from the MME in the step 4a, the UE sends a Detach Accept message to the MME any time after step 4a. The eNodeB forwards this NAS message to the MME along with the TAI+ECGI of the cell which the UE is using. NOTE 4: The UE may not be able to send this message, e.g. when the UE is out of coverage of E-UTRAN due to mobility to non-3GPP access. 7a,b,c If Dual Connectivity is active for the UE, the PSCell ID shall be included in the Uplink NAS Transport sent by the eNodeB. 8a. After reception of both the Deactivate Bearer Response message in step 6b and the Deactivate EPS Bearer Context Accept message in step 7b, the MME deletes the bearer context related to the deactivated EPS bearer and acknowledges the bearer deactivation to the Serving GW by sending a Delete Bearer Response (EPS Bearer Identity, User Location Information (ECGI), RAN/NAS Release Cause, Secondary RAT usage data, PSCell ID) message. If the MME received Secondary RAT usage data in step 6b, the MME shall include it in this message. If the MME received PSCell ID in step 6b, the MME shall include it in this message. If extended idle mode DRX is enabled, then the MME acknowledges the bearer deactivation to the Serving GW and at the same time the MME initiates the deactivation towards the UE. If the S1 connection had already been released by the eNodeB due to radio link failure and the MME receives a Delete Bearer Request while it is still deferring the sending of the S1 release (see clause 5.3.5), the MME shall include in the Delete Bearer Response the RAN/NAS Cause received in the S1 Release due to radio link failure procedure. 8b The SGSN deletes PDP Context related to the deactivated EPS bearer and acknowledges the bearer deactivation to the Serving GW by sending a Delete Bearer Response (EPS Bearer Identity, User Location Information (CGI/SAI)) message. If extended idle mode DRX is enabled, then the SGSN acknowledges the bearer deactivation to the Serving GW and at the same time the SGSN initiates the deactivation towards the UE. 9. If ISR is activated, after receiving the two Delete Bearer Response messages from the MME and the SGSN, or if ISR is not activated, after receiving the Delete Bearer Response messages from the MME, the Serving GW deletes the bearer context related to the deactivated EPS bearer acknowledges the bearer deactivation to the PDN GW by sending a Delete Bearer Response (EPS Bearer Identity, User Location Information (ECGI or CGI/SAI), Secondary RAT usage data) message. If the MME and/or SGSN sent UE's Location Information and/or UE Time Zone in step 8a and/or step 8b, the Serving GW includes the User Location Information and/or UE Time Zone Information with the least age in this message. The Serving GW includes the Secondary RAT usage data if it was received in step 8a and if PGW secondary RAT usage data reporting is active. 10. The PDN GW deletes the bearer context related to the deactivated EPS bearer. If the dedicated bearer deactivation procedure was triggered by receiving a PCC decision message from the PCRF, the PDN GW indicates to the PCRF whether the requested PCC decision was successfully enforced by completing the PCRF-initiated IP-CAN Session Modification procedure or the PCEF initiated IP-CAN Session Modification procedure as defined in TS 23.203[ Policy and charging control architecture ] [6], proceeding after the completion of IP-CAN bearer signalling. If requested by the PCRF the PDN GW indicates User Location Information and/or UE Time Zone Information to the PCRF as defined in TS 23.203[ Policy and charging control architecture ] [6]. If available, the PDN GW shall send RAN/NAS Release Cause to the PCRF as defined in TS 23.203[ Policy and charging control architecture ] [6]. 11. If the UE is being explicitly detached, the MME releases the S1-MME signalling connection for the UE by sending an S1 Release Command (Cause) message to the eNodeB. The details of this step are covered in the "S1 Release Procedure", as described in clause 5.3.5 by step 4 to step 6. NOTE 5: In the "S1 Release Procedure", if Dual Connectivity was active at the time of the release, the eNodeB includes the PSCell ID. NOTE 6: The exact signalling of step 1 and 10 (e.g. for local break-out) is outside the scope of this specification. This signalling and its interaction with the dedicated bearer activation procedure are to be specified in TS 23.203[ Policy and charging control architecture ] [6]. Steps 1 and 10 are included here only for completeness. If all the bearers belonging to a UE that does not support "Attach without PDN connectivity" are released, the MME shall change the MM state of the UE to EMM-DEREGISTERED and the MME sends the S1 Release Command to the eNodeB, which initiates the release of the RRC connection for the given UE if it is not released yet, and returns an S1 Release Complete message to the MME. If all bearers of an emergency attached or RLOS attached UE are deactivated the MME may initiate the explicit MME-Initiated Detach procedure. Regardless of the outcome of any explicit Detach procedure the MME changes the EMM state of the UE to EMM-DEREGISTERED and the MME sends the S1 Release Command to the eNodeB if it is not yet released. If the default bearer belonging to a PDN connection is deactivated, the MME determines the Maximum APN Restriction for the remaining PDN connections and stores this new value for the Maximum APN Restriction. In addition if ISR is activated the SGSN determines the Maximum APN Restriction for the remaining bearer contexts and stores this new value for the Maximum APN Restriction. | 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.4.4.1 |
1,800 | 5.5.1.2.2 Attach procedure initiation | In state EMM-DEREGISTERED, the UE initiates the attach procedure by sending an ATTACH REQUEST message to the MME, starting timer T3410 and entering state EMM-REGISTERED-INITIATED (see example in figure 5.5.1.2.2.1). If timer T3402 is currently running, the UE shall stop timer T3402. If timer T3411 is currently running, the UE shall stop timer T3411. The UE shall include the IMSI in the EPS mobile identity IE in the ATTACH REQUEST message if the selected PLMN is neither the registered PLMN nor in the list of equivalent PLMNs and: a) the UE is configured for "AttachWithIMSI" as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]; or b) the UE is in NB-S1 mode. For all other cases, the UE shall handle the EPS mobile identity IE in the ATTACH REQUEST message as follows: a) if the UE operating in the single-registration mode is performing an inter-system change from N1 mode to S1 mode or the UE was previously registered in N1 mode before entering state 5GMM-DEREGISTERED and: 1) the UE has received the interworking without N26 interface indicator set to "interworking without N26 interface supported" from the network and: i) if the UE holds a valid GUTI, the UE shall include the valid GUTI into the EPS mobile identity IE, include Old GUTI type IE with GUTI type set to "Native GUTI" and include the UE status IE with a 5GMM registration status set to "UE is not in 5GMM-REGISTERED state". NOTE 1:Since MM context transfer is not possible between MME and AMF in a network that indicates "interworking without N26 interface supported", it is up to the UE implementation as to how to keep the 5GMM and EMM states in the UE in sync. ii) if the UE does not hold a valid GUTI, the UE shall include the IMSI in the EPS mobile identity IE; or 2) the UE has received the interworking without N26 interface indicator set to "interworking without N26 interface not supported" from the network and: i) if the UE holds a valid native 5G-GUTI, the UE shall include a GUTI, mapped from the 5G-GUTI into the EPS mobile identity IE, include Old GUTI type IE with GUTI type set to "Native GUTI" and include the UE status IE with a 5GMM registration status set to "UE is not in 5GMM-REGISTERED state"; ii) if the UE holds a valid GUTI and does not hold a valid 5G-GUTI, the UE shall indicate the GUTI in the EPS mobile identity IE and include Old GUTI type IE with GUTI type set to "Native GUTI"; or iii) if the UE holds neither a valid GUTI nor a valid 5G-GUTI, the UE shall include the IMSI in the EPS mobile identity IE; or NOTE 2: The value of the EMM registration status included by the UE in the UE status IE is not used by the MME. b) otherwise: 1) if the UE supports neither A/Gb mode nor Iu mode, the UE shall include in the ATTACH REQUEST message a valid GUTI together with the last visited registered TAI, if available. In addition, the UE shall include Old GUTI type IE with GUTI type set to "Native GUTI". If there is no valid GUTI available, the UE shall include the IMSI in the ATTACH REQUEST message; or 2) If the UE supports A/Gb mode or Iu mode or both and: i) if the TIN indicates "P-TMSI" and the UE holds a valid native P-TMSI and RAI, the UE shall map the P-TMSI and RAI into the EPS mobile identity IE, and include Old GUTI type IE with GUTI type set to "Mapped GUTI". If a P-TMSI signature is associated with the P-TMSI, the UE shall include it in the Old P-TMSI signature IE. Additionally, if the UE holds a valid GUTI, the UE shall indicate the GUTI in the Additional GUTI IE; NOTE 3: The mapping of the P-TMSI and the RAI to the GUTI is specified in 3GPP TS 23.003[ Numbering, addressing and identification ] [2]. ii) if the TIN indicates "GUTI" or "RAT-related TMSI" and the UE holds a valid GUTI, the UE shall indicate the GUTI in the EPS mobile identity IE, and include Old GUTI type IE with GUTI type set to "Native GUTI"; iii) if the TIN is deleted and: - the UE holds a valid GUTI, the UE shall indicate the GUTI in the EPS mobile identity IE, and include Old GUTI type IE with GUTI type set to "Native GUTI"; - the UE does not hold a valid GUTI but holds a valid native P-TMSI and RAI, the UE shall map the P-TMSI and RAI into the EPS mobile identity IE, and include Old GUTI type IE with GUTI type set to "Mapped GUTI". If a P-TMSI signature is associated with the P-TMSI, the UE shall include it in the Old P-TMSI signature IE; or - the UE does not hold a valid GUTI, P-TMSI or RAI, the UE shall include the IMSI in the EPS mobile identity IE; or iv) otherwise the UE shall include the in the EPS mobile identity IE. If the UE is operating in the dual-registration mode and it is in 5GMM state 5GMM-REGISTERED, the UE shall include the UE status IE with the 5GMM registration status set to "UE is in 5GMM-REGISTERED state". NOTE 4: The value of the EMM registration status included by the UE in the UE status IE is not used by the MME. If the UE is attaching for emergency bearer services and does not hold a valid GUTI, P-TMSI or IMSI as described above, the IMEI shall be included in the EPS mobile identity IE. If the UE in limited service state is attaching for access to RLOS and does not hold a valid GUTI, P-TMSI or IMSI as described above, the IMEI shall be included in the EPS mobile identity IE. If the UE supports A/Gb mode or Iu mode or if the UE needs to indicate its UE specific DRX parameter to the network, the UE shall include the UE specific DRX parameter in the DRX parameter IE in the ATTACH REQUEST message. If the UE in NB-S1 mode needs to indicate the UE specific DRX parameter in NB-S1 mode to the network, it shall include the UE specific DRX parameter in NB-S1 mode in the DRX parameter in NB-S1 mode IE in the ATTACH REQUEST message. If the UE supports eDRX and requests the use of eDRX, the UE shall include the extended DRX parameters IE in the ATTACH REQUEST message. If the UE supports WUS assistance, then the UE shall set the WUSA bit to "WUS assistance supported" in the UE network capability IE, and if the UE is not attaching for emergency bearer services, the UE may include its UE paging probability information in the Requested WUS assistance information IE of the ATTACH REQUEST message. If the UE supports SRVCC to GERAN/UTRAN, the UE shall set the SRVCC to GERAN/UTRAN capability bit to "SRVCC from UTRAN HSPA or E-UTRAN to GERAN/UTRAN supported". If the UE supports vSRVCC from S1 mode to Iu mode, then the UE shall set the H.245 after handover capability bit to "H.245 after SRVCC handover capability supported" and additionally set the SRVCC to GERAN/UTRAN capability bit to "SRVCC from UTRAN HSPA or E-UTRAN to GERAN/UTRAN supported" in the ATTACH REQUEST message. If the UE supports PSM and requests the use of PSM, then the UE shall include the T3324 value IE with a requested timer value in the ATTACH REQUEST message. When the UE includes the T3324 value IE and the UE indicates support for extended periodic timer value in the MS network feature support IE, it may also include the T3412 extended value IE to request a particular T3412 value to be allocated. If the UE supports ProSe direct discovery, then the UE shall set the ProSe bit to "ProSe supported" and set the ProSe direct discovery bit to "ProSe direct discovery supported" in the UE network capability IE of the ATTACH REQUEST message. If the UE supports ProSe direct communication, then the UE shall set the ProSe bit to "ProSe supported" and set the ProSe direct communication bit to "ProSe direct communication supported" in the UE network capability IE of the ATTACH REQUEST message. If the UE supports acting as a ProSe UE-to-network relay, then the UE shall set the ProSe bit to "ProSe supported" and set the ProSe UE-to-network relay bit to "acting as a ProSe UE-to-network relay supported" in the UE network capability IE of the ATTACH REQUEST message. If the UE supports NB-S1 mode, Non-IP or Ethernet PDN type, N1 mode, UAS services, URSP provisioning in EPS or if the UE supports DNS over (D)TLS (see 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]), then the UE shall support the Extended protocol configuration options IE. NOTE 5: Support of DNS over (D)TLS is based on the informative requirements as specified in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. If the UE supports the Extended protocol configuration options IE, then the UE shall set the ePCO bit to "extended protocol configuration options supported" in the UE network capability IE of the ATTACH REQUEST message. If the UE supports providing PDU session ID in the Protocol configuration options IE or the Extended protocol configuration options IE when its N1 mode capability is disabled, then the UE shall set the ePCO bit to "extended protocol configuration options supported" in the UE network capability IE of the ATTACH REQUEST message. If the UE supports the restriction on use of enhanced coverage, then the UE shall set the RestrictEC bit to "Restriction on use of enhanced coverage supported" in the UE network capability IE of the ATTACH REQUEST message. If the UE supports the control plane data back-off timer T3448, the UE shall set the CP backoff bit to "back-off timer for transport of user data via the control plane supported" in the UE network capability IE of the ATTACH REQUEST message. If the UE supports EPS-UPIP, the UE shall set the EPS-UPIP bit to "EPS-UPIP supported" in the UE network capability IE of the ATTACH REQUEST message. If the UE is in NB-S1 mode, then the UE shall set the Control plane CIoT EPS optimization bit to "Control plane CIoT EPS optimization supported" in the UE network capability IE of the ATTACH REQUEST message. If the UE is capable of NB-N1 mode, then the UE shall set the Control plane CIoT 5GS optimization bit to "Control plane CIoT 5GS optimization supported" in the N1 UE network capability IE of the ATTACH REQUEST message. If the UE is in NB-S1 mode, supports NB-S1 mode only, and requests to attach for EPS services and "SMS only", the UE shall indicate the SMS only requested bit to "SMS only" in the additional update type IE and shall set the EPS attach type IE to "EPS attach" in the ATTACH REQUEST message. If the UE supports CIoT EPS optimizations, it shall indicate in the UE network capability IE of the ATTACH REQUEST message whether it supports EMM-REGISTERED without PDN connection. If the UE supports enhanced discontinuous coverage, then the UE shall set the EDC bit to "Enhanced discontinuous coverage supported" in the UE network capability IE of the ATTACH REQUEST message. If the UE supports S1-U data transfer and multiple user plane radio bearers (see 3GPP TS 36.306[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio access capabilities ] [44], 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]) in NB-S1 mode, then the UE shall set the Multiple DRB support bit to "Multiple DRB supported" in the UE network capability IE of the ATTACH REQUEST message. If the UE supports control plane MT-EDT, then the UE shall set the CP-MT-EDT bit to "Control plane Mobile Terminated-Early Data Transmission supported" in the UE network capability IE of the ATTACH REQUEST message. If the UE supports user plane MT-EDT, then the UE shall set the UP-MT-EDT bit to "User plane Mobile Terminated-Early Data Transmission supported" in the UE network capability IE of the ATTACH REQUEST message. If the UE supports V2X communication over E-UTRA-PC5, then the UE shall set the V2X PC5 bit to "V2X communication over E-UTRA-PC5 supported" in the UE network capability IE of the ATTACH REQUEST message. If the UE supports V2X communication over NR-PC5, then the UE shall set the V2X NR-PC5 bit to "V2X communication over NR-PC5 supported" in the UE network capability IE of the ATTACH REQUEST message. If the UE supports service gap control, then the UE shall set the SGC bit to "service gap control supported" in the UE network capability IE of the ATTACH REQUEST message. If the UE supports dual connectivity with New Radio (NR), then the UE shall set the DCNR bit to "dual connectivity with NR supported" in the UE network capability IE of the ATTACH REQUEST message and shall include the UE additional security capability IE in the ATTACH REQUEST message. If the UE supports N1 mode for 3GPP access, the UE shall set the N1mode bit to "N1 mode for 3GPP access supported" in the UE network capability IE of the ATTACH REQUEST message and shall include the UE additional security capability IE in the ATTACH REQUEST message. If the UE supports signalling for a maximum number of 15 EPS bearer contexts, then the UE shall set the 15 bearers bit to "Signalling for a maximum number of 15 EPS bearer contexts supported" in the UE network capability IE of the ATTACH REQUEST message. If the MUSIM UE supports the NAS signalling connection release, then the UE shall set the NAS signalling connection release bit to "NAS signalling connection release supported" in the UE network capability IE of the ATTACH REQUEST message otherwise the UE shall not set the NAS signalling connection release bit to "NAS signalling connection release supported" in the UE network capability IE of the ATTACH REQUEST message. If the MUSIM UE supports the paging indication for voice services, then the UE shall set the paging indication for voice services bit to "paging indication for voice services supported" in the UE network capability IE of the ATTACH REQUEST message otherwise the UE shall not set the paging indication for voice services bit to "paging indication for voice services supported" in the UE network capability IE of the ATTACH REQUEST message. If the MUSIM UE supports the reject paging request, then the UE shall set the reject paging request bit to "reject paging request supported" in the UE network capability IE of the ATTACH REQUEST message otherwise the UE shall not set the reject paging request bit to "reject paging request supported" in the UE network capability IE of the ATTACH REQUEST message. If the MUSIM UE sets: - the reject paging request bit to "reject paging request supported"; - the NAS signalling connection release bit to "NAS signalling connection release supported"; or - both of them; and supports the paging restriction, then the UE shall set the paging restriction bit to "paging restriction supported" in the UE network capability IE of the ATTACH REQUEST message otherwise the UE shall not set the paging restriction bit to "paging restriction supported" in the UE network capability IE of the ATTACH REQUEST message. If the MUSIM UE supports the paging timing collision control, then the UE shall set the paging timing collision control bit to "paging timing collision control supported" in the UE network capability IE of the ATTACH REQUEST message otherwise the UE shall not set the paging timing collision control bit to "paging timing collision control supported" in the UE network capability IE of the ATTACH REQUEST message. If the UE supports ciphered broadcast assistance data and needs to obtain new ciphering keys, the UE shall include the Additional information requested IE with the CipherKey bit set to "ciphering keys for ciphered broadcast assistance data requested" in the ATTACH REQUEST message. For MUSIM UE if the UE needs to indicate an IMSI offset value to the network, the UE shall include the IMSI offset value in the Requested IMSI offset IE in the ATTACH REQUEST message. If EMM-REGISTERED without PDN connection is not supported by the UE or the MME, or if the UE wants to request PDN connection with the attach procedure, the UE shall send the ATTACH REQUEST message together with a PDN CONNECTIVITY REQUEST message contained in the ESM message container IE. If EMM-REGISTERED without PDN connection is supported by the UE and the MME, and the UE does not want to request PDN connection with the attach procedure, the UE shall send the ATTACH REQUEST message together with an ESM DUMMY MESSAGE contained in the ESM message container information element. In WB-S1 mode, if the UE supports RACS, the UE shall: a) set the RACS bit to "RACS supported" in the UE network capability IE of the ATTACH REQUEST message; and b) if the UE has an applicable UE radio capability ID for the current UE radio configuration in the selected PLMN, set the URCIDA bit to "UE radio capability ID available" in the UE radio capability ID availability IE of the ATTACH REQUEST message. If the attach procedure is initiated following an inter-system change from N1 mode to S1 mode in EMM-IDLE mode or the UE which was previously registered in N1 mode before entering state 5GMM-DEREGISTERED initiates the attach procedure: a) if the UE has received an "interworking without N26 interface not supported" indication from the network and a valid 5G NAS security context exists in the UE, the UE shall integrity protect the ATTACH REQUEST message combined with the message included in the ESM message container IE using the 5G NAS security context; b) otherwise: 1) if a valid EPS security context exists, the UE shall integrity protect the ATTACH REQUEST message combined with the message included in the ESM message container IE using the EPS security context; or 2) if the UE does not have a valid EPS security context, the ATTACH REQUEST message combined with the message included in the ESM message container IE is not integrity protected. Figure 5.5.1.2.2.1: Attach procedure and combined attach procedure | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.1.2.2 |
Subsets and Splits
No saved queries yet
Save your SQL queries to embed, download, and access them later. Queries will appear here once saved.