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
⌀ |
|---|---|---|---|---|---|---|---|
2,701 | 4.15.3.2.3b Specific NEF service operations information flow for loss of connectivity and UE reachability | The procedure is used by the AF to subscribe to notifications and to explicitly cancel a previous subscription for loss of connectivity and UE reachability. Figure 4.15.3.2.3b-1: Nnef_EventExposure_Subscribe, Unsubscribe and Notify operations or loss of connectivity and UE reachability 1. Step 1 to step 3b of Figure 4.15.3.2.3-1 are performed with the following differences: - For Loss of Connectivity, the subscription request may include Maximum Detection Time (see Table 4.15.3.1-1). - For UE reachability, the subscription request may include Maximum Latency, Maximum Response Time and/or Suggested number of downlink packets (see Table 4.15.3.1-1). In step 3a of Figure 4.15.3.2.3-1, the UDM may include Maximum Response Time in the subscription request to the AMF. NOTE 1: It is expected that Maximum Latency, Maximum Response Time and/or Suggested number of downlink packets included in the subscription request is only used by the AF that does not support Parameter Provisioning procedure specified in clause 4.15.6.3a. - For UE reachability, the AF may include Idle Status Indication request. If Idle Status Indication request is included, the NEF includes it in Nudm_EventExposure_Subscribe message. If the UDM receives Idle Status Indication request, it includes it in Namf_EventExposure_Subscribe message. If the NEF does not support the requested Idle Status Indication, then depending on operator policies, the NEF rejects the request. 2. [Conditional] If the subscribed periodic registration timer has not been set according to any subscription request, or a Network Configuration as defined in clause 4.15.6.3a the UDM shall set the subscribed periodic registration timer using the Maximum Detection Time or Maximum Latency; otherwise if the subscribed periodic registration timer was previously set by a different subscription identified by a different Notification Target Address (+ Notification Correlation ID), or set by a different Network Configuration identified by a different NEF reference ID for the same UE and if the newly received Maximum Detection Time or Maximum Latency is lower than the provided subscribed periodic registration timer, the UDM shall set the subscribed periodic registration timer using the newly received Maximum Detection Time or Maximum Latency. If Nudm_EventExposure_Unsubscribe request is performed in step 1, the UDM shall recalculate the subscribed periodic registration timer based on the remaining event subscriptions and/or Network Configurations. In addition for UE reachability subscription, if the newly received Maximum Response Time is longer than the provided subscribed Active Time (i.e. previously provided Maximum Response Time), the UDM shall set the subscribed Active Time using the newly received Maximum Response Time. If the suggested number of downlink packets is newly received, the UDM shall add the newly received suggested number of downlink packets to the currently used value of suggested number of downlink packets if the aggregated value is within the operator defined range. If Nudm_EventExposure_Unsubscribe request is performed in step 1, the UDM shall recalculate the subscribed Active Time and/or Suggested Number of Downlink Packets based on the remaining event subscriptions and/or Network Configurations. If the subscribed periodic registration timer or the subscribed Active Time are set or modified, the UDM sends the Nudm_SDM_Notification request to related serving AMF(s). If the AMF receives a subscribed periodic registration timer value from the UDM, it allocates the received value to the UE as the periodic registration timer at subsequent Registration procedure. The AMF starts monitoring of the expiration of the mobile reachable timer for Loss of Connectivity (if required) and starts monitoring of the UE entering connected mode for UE reachability (if required). If the suggested number of downlink packets are set or modified, the UDM sends the Nudm_SDM_Notification request to related serving SMF(s). The SMF configures the data buffer at the SMF/UPF according the suggested number of downlink packets. If the provided value is updated by the UDM, the UDM may notify the NEF (which then notifies the AF) of the actual value that is being applied in the 3GPP network. 3. Step 4 to step 5 of Figure 4.15.3.2.3-1 are performed. 4. Step 6c to step 6d of Figure 4.15.3.2.3-1 are performed with the following differences: - For Loss of Connectivity, the event is detected when the mobile reachability timer expires or when the UE has provided Unavailability Period Duration during the Registration procedure without including Start of Unavailability Period or when unavailability period starts based on Start of Unavailability Period stored in UE context at AMF or Deregistration procedure as described in clause 5.4.1.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. - For UE reachability, the event is detected when the UE changes to connected mode or when the UE will become reachable for paging. - For UE reachability, if Idle Status Indication request was included in step 1 and the AMF supports Idle Status Indication, the AMF includes also the Idle Status Indication. 5. Step 8 of Figure 4.15.3.2.3-1 is performed. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.3.2.3b |
2,702 | 4.2.7.2.5 NGAP UE-TNLA-binding per UE Release procedure | At any time the AMF may decide to release the NGAP UE-TNLA binding while keeping the UE in CM-CONNECTED state while keeping the corresponding N3 interface. The AMF releases the NGAP UE-TNLA binding by sending a UE-specific NGAP UE-TNLA binding release message on the current TNL association. If the AMF releases the NGAP UE-TNLA-binding without sending AMF unavailable status indication, then the AN may immediately trigger creation of a new NGAP-UE-TNLA-binding with the same AMF for subsequent N2 messages or may leave the NGAP UE association without NGAP UE-TNLA-binding. In the latter case the new NGAP UE-TNLA-binding is re-created upon the subsequent AN-initiated or AMF-initiated UE-specific N2 signalling as specified in clause 4.2.7.2.3. If the AMF releases the NGAP UE-TNLA-binding after AMF unavailable status indication, then the AN has to re-create the NGAP-UE-TNLA-binding with a different AMF. The 5G-AN re-creates N2AP UE-TNLA-binding for subsequent N2 messages for the given UE as specified in clause 4.2.7.2.3. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2.7.2.5 |
2,703 | 5.15.9 Operator-controlled inclusion of NSSAI in Access Stratum Connection Establishment | The Serving PLMN can control per Access Type which (if any) NSSAI the UE includes in the Access Stratum when establishing a connection caused by Service Request, Periodic Registration Update or Registration procedure used to update the UE capabilities. In addition, the Home and Visited PLMNs can also instruct the UE to never include NSSAI in the Access Stratum, regardless of the procedure that causes a RRC Connection to be established, i.e. to always enable privacy for the NSSAI). During the Registration procedure, the AMF may provide to the UE in the Registration Accept message, an Access Stratum Connection Establishment NSSAI Inclusion Mode parameter, indicating whether and when the UE shall include NSSAI information in the Access Stratum Connection Establishment (e.g. an RRC connection Establishment defined in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [28]) according to one of these modes: a) The UE shall include an NSSAI set to the Allowed NSSAI, if available, in the Access Stratum Connection Establishment caused by a Service Request, Periodic Registration Update or Registration procedure used to update the UE capabilities; b) The UE shall include a NSSAI with the following content: - for the case of Access Stratum Connection Establishment caused by a Service Request: an NSSAI including the S-NSSAI(s) of the Network Slice(s) that trigger the Access Stratum Connection Establishment; i.e. all the S-NSSAIs of the PDU sessions that have the User Plane reactivated by the Service Request, or the S-NSSAIs of the Network Slices a Control Plane interaction triggering the Service Request is related to, e.g. for SM it would be the S-NSSAI of the PDU Session the SM message is about; - for the case of Access Stratum Connection Establishment caused by a Periodic Registration Update or Registration procedure used to update the UE capabilities, an NSSAI set to the Allowed NSSAI; c) The UE shall not include any NSSAI in the Access Stratum Connection Establishment caused by Service Request, Periodic Registration Update or Registration procedure used to update the UE capabilities; or d) The UE shall not provide NSSAI in the Access stratum. For the case of Access Stratum Connection Establishment caused by Mobility Registration Update or Initial Registration in modes a), b) or c) the UE shall include the Requested NSSAI provided by the NAS layer and defined in clause 5.15.5.2.1. For all UEs that are allowed to use modes a), b) or c), the Access Stratum Connection Establishment NSSAI Inclusion Mode should be the same over the same Registration Areas.The UE shall store and comply to the required behaviour for a PLMN per Access Type as part of the network slicing configuration. The Serving PLMN AMF shall not instruct the UE to operate in any other mode than mode d) in 3GPP Access Type unless the HPLMN provides an indication that it is allowed to do so (i.e. if a PLMN allows behaviours a,b,c, then its UDM sends to the serving AMF an explicit indication that the NSSAI can be included in RRC as part of the subscription data). The UE default mode of operation is the following: - For 3GPP access the UE shall by default operate in mode d) unless it has been provided with an indication to operate in mode a), b) or c). - For untrusted non-3GPP access the UE shall operate by default in mode b) unless it has been provided with an indication to operate in mode a), c) or d). - For trusted non-3GPP access the UE shall operate by default in mode d) unless it has been provided with an indication to operate in mode a), b) or c). - For W-5GAN access the 5G-RG shall operate by default in mode b) unless it has been provided with an indication to operate in mode a), c) or d). An operator may pre-configure the UE to operate by default according to mode c) in the HPLMN (i.e. the UE by default includes NSSAI in the access stratum when it performs an Initial Registration and Mobility Registration Update with the HPLMN until the HPLMN changes the mode as described above). | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.15.9 |
2,704 | – RRCReconfigurationComplete | The RRCReconfigurationComplete message is used to confirm the successful completion of an RRC connection reconfiguration. Signalling radio bearer: SRB1 or SRB3 RLC-SAP: AM Logical channel: DCCH Direction: UE to Network RRCReconfigurationComplete message -- ASN1START -- TAG-RRCRECONFIGURATIONCOMPLETE-START RRCReconfigurationComplete ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { rrcReconfigurationComplete RRCReconfigurationComplete-IEs, criticalExtensionsFuture SEQUENCE {} } } RRCReconfigurationComplete-IEs ::= SEQUENCE { lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension RRCReconfigurationComplete-v1530-IEs OPTIONAL } RRCReconfigurationComplete-v1530-IEs ::= SEQUENCE { uplinkTxDirectCurrentList UplinkTxDirectCurrentList OPTIONAL, nonCriticalExtension RRCReconfigurationComplete-v1560-IEs OPTIONAL } RRCReconfigurationComplete-v1560-IEs ::= SEQUENCE { scg-Response CHOICE { nr-SCG-Response OCTET STRING (CONTAINING RRCReconfigurationComplete), eutra-SCG-Response OCTET STRING } OPTIONAL, nonCriticalExtension RRCReconfigurationComplete-v1610-IEs OPTIONAL } RRCReconfigurationComplete-v1610-IEs ::= SEQUENCE { ue-MeasurementsAvailable-r16 UE-MeasurementsAvailable-r16 OPTIONAL, needForGapsInfoNR-r16 NeedForGapsInfoNR-r16 OPTIONAL, nonCriticalExtension RRCReconfigurationComplete-v1640-IEs OPTIONAL } RRCReconfigurationComplete-v1640-IEs ::= SEQUENCE { uplinkTxDirectCurrentTwoCarrierList-r16 UplinkTxDirectCurrentTwoCarrierList-r16 OPTIONAL, nonCriticalExtension RRCReconfigurationComplete-v1700-IEs OPTIONAL } RRCReconfigurationComplete-v1700-IEs ::= SEQUENCE { needForGapNCSG-InfoNR-r17 NeedForGapNCSG-InfoNR-r17 OPTIONAL, needForGapNCSG-InfoEUTRA-r17 NeedForGapNCSG-InfoEUTRA-r17 OPTIONAL, selectedCondRRCReconfig-r17 CondReconfigId-r16 OPTIONAL, nonCriticalExtension RRCReconfigurationComplete-v1720-IEs OPTIONAL } RRCReconfigurationComplete-v1720-IEs ::= SEQUENCE { uplinkTxDirectCurrentMoreCarrierList-r17 UplinkTxDirectCurrentMoreCarrierList-r17 OPTIONAL, nonCriticalExtension RRCReconfigurationComplete-v1800-IEs OPTIONAL } RRCReconfigurationComplete-v1800-IEs ::= SEQUENCE { needForInterruptionInfoNR-r18 NeedForInterruptionInfoNR-r18 OPTIONAL, flightPathInfoAvailable-r18 ENUMERATED {true} OPTIONAL, selectedPSCellForCHO-WithSCG-r18 SelectedPSCellForCHO-WithSCG-r18 OPTIONAL, selectedSK-Counter-r18 SK-Counter OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } -- TAG-RRCRECONFIGURATIONCOMPLETE-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,705 | 10.2 Timers of 5GS mobility management | Timers of 5GS mobility management are shown in table 10.2.1 and table 10.2.2. NOTE: Timers T3324, T3346, T3245 and T3247 are defined in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [12]. Timers T3444, T3445, T3447 and T3448 are defined in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]. Table 10.2.1: Timers of 5GS mobility management – UE side Table 10.2.2: Timers of 5GS mobility management – AMF side | 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 | 10.2 |
2,706 | 4.4.9 HeNB subsystem | A HeNB subsystem consists of a HeNB, optionally a HeNB GW and optionally a Local GW. The Local IP Access and SIPTO at the Local Network with L-GW function collocated with the HeNB functions are achieved using a Local GW (L-GW) collocated with the HeNB. Figure 4.4.9-1 illustrates the architecture for LIPA and/or SIPTO at the Local Network with L-GW function collocated with the HeNB. Figure 4.4.9-1: Architecture for LIPA or SIPTO at the Local Network with L-GW collocated with the HeNB NOTE 1: The optional HeNB GW is not shown in the figure for simplicity. The HeNB subsystem is connected by means of the standard S1 interface to the EPC (Evolved Packet Core), more specifically to the MME (Mobility Management Entity) by means of the S1-MME interface and to the Serving Gateway (S-GW) by means of the S1-U interface. When LIPA or SIPTO at the Local Network with L-GW function collocated with the HeNB is activated, the L-GW has a S5 interface with the S-GW. NOTE 2: In this specification and for simplification the term eNodeB refers to the HeNB subsystem if the UE accesses the network via a HeNB unless stated otherwise. NOTE 3: Detailed functions of HeNB and HeNB GW are described in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]. NOTE 4: An L-GW collocated with a HeNB may support LIPA, or SIPTO@LN, or both. The Local GW is the gateway towards the IP networks (e.g. residential/enterprise networks, Internet) associated with the HeNB. The Local GW has the following PDN GW functions: - UE IP address allocation; - DHCPv4 (server and client) and DHCPv6 (client and server) functions; - Packet screening; - Functionality as defined in RFC 4861 [32]. Additionally, the Local GW has the following functions: - ECM-IDLE mode downlink packet buffering; - ECM-CONNECTED mode direct tunnelling towards the HeNB. NOTE 5: The architecture for SIPTO at the Local Network with L-GW function collocated with a HeNB depicted in Figure 4.4.9-1 also applies to SIPTO at the Local Network with L-GW function collocated with an eNodeB. | 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.9 |
2,707 | 5.2.5.4.2 Npcf_SMPolicyControl_Create service operation | Service operation name: Npcf_SMPolicyControl_Create. Description: The NF Service Consumer can request the creation of a SM Policy Association and provides relevant parameters about the PDU Session to the PCF. Inputs, Required: SUPI (or PEI in the case of emergency PDU Session without SUPI), PDU Session id, DNN, S-NSSAI and RAT Type. Inputs, Optional: Information provided by the SMF, such as PDU Session Type, Request Type, Access Type, the IPv4 address and/or IPv6 prefix, PEI, GPSI, User Location Information, UE Time Zone, Serving Network identifier (PLMN ID, or PLMN ID and NID, see clause 5.34 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]), Charging Characteristics information, Session-AMBR, subscribed default QoS information (5QI, 5QI Priority Level, ARP), UE support of reflective QoS (see TS 23.501[ System architecture for the 5G System (5GS) ] [2], clause 5.7.5.1), Number of supported packet filters for signalled QoS rules for the PDU Session (see TS 23.501[ System architecture for the 5G System (5GS) ] [2], clause 5.7.1.4), 3GPP PS Data Off status, Trace Requirements and Internal Group Identifier (see clause 5.9.7 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]), DN Authorization Profile Index, DN authorized Session AMBR, Framed Route information (as defined in Table 5.2.3.3.1-1), MA PDU Request indication, MA PDU Network-Upgrade Allowed indication, ATSSS capabilities of the MA PDU Session, QoS constraints from the VPLMN (as defined in clause 5.7.1.11 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]), Satellite Backhaul Category information, list of NWDAF instance Ids (used by AMF, SMF, UPF) and corresponding Analytics ID(s), PVS IP address(es) and/or PVS FQDN(s) and Onboarding Indication in the case of ON-SNPN (see clause 5.30.2.10.4.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]), URSP rule enforcement that including Connection Capability, HR-SBO support indication (see clause 6.2.1.2 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]), Alternative S-NSSAI (see clause 5.15.19 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]), URSP delivery in EPS support indication. NOTE 1: If SMF receives the DN authorized Session AMBR from the DN-AAA at PDU Session establishment, it includes the DN authorized Session AMBR within the Session-AMBR, instead of the subscribed Session-AMBR received from the UDM, in the request. NOTE 2: It is up to stage 3 to determine whether the corresponding supportedFeature in Npcf_SMPolicyControl can be reused as URSP delivery in EPS support indication. W-5GAN specific PDU Session information provided by the SMF is specified in TS 23.316[ Wireless and wireline convergence access support for the 5G System (5GS) ] [53]. Outputs, Required: SM Policy Association ID defined in TS 29.512[ 5G System; Session Management Policy Control Service; Stage 3 ] [57]. Success or Failure. Outputs, Optional: Policy information for the PDU Session as defined in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20] and Policy Control Request Trigger(s) of SM Policy Association as defined in clause 6.1.3.5 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. See clause 5.8.2.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] for allocation of IPv4 address and IPv6 prefix. The IPv6 prefix length is /64, or is shorter than /64 when Prefix Delegation applies. See clause 4.16.4 for the detail usage of this service operation. See clauses 4.22.2.1 and 4.22.3 for detailed usage of this service operation for ATSSS. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.5.4.2 |
2,708 | 4.7.1.2a.3 Integrity checking of layer 3 signalling messages in the network | Except the messages listed below, no GMM signalling messages shall be processed by the receiving GMM entity in the network or forwarded to the SM entity, unless integrity protection has been successfully negotiated: - GMM messages: - ATTACH REQUEST; - IDENTITY RESPONSE (if requested identification parameter is IMSI); - AUTHENTICATION AND CIPHERING FAILURE; - DETACH REQUEST; - DETACH ACCEPT. All SM messages are integrity protected. Once a valid UMTS security context exists, until integrity protection has been successfully negotiated, the receiving GMM entity in the network shall process the following GMM signalling messages, even if the MAC included in the LLC frame carrying the GMM message fails the integrity check or cannot be verified in the LLC layer, as the UMTS security context is not available in the network: - ATTACH REQUEST; - IDENTITY RESPONSE (if requested identification parameter is IMSI); - AUTHENTICATION AND CIPHERING FAILURE; - DETACH REQUEST (if sent before integrity protection has been activated); - DETACH ACCEPT; - ROUTING AREA UPDATE REQUEST; NOTE: These messages are processed by the GMM layer even when the MAC fails the integrity check or cannot be verified, as in certain situations they can be sent by the MS protected with an UMTS security context that is no longer available in the network. If an ATTACH REQUEST message fails the integrity check, the network shall authenticate the subscriber before processing the attach request any further. If a ROUTING AREA UPDATE REQUEST message fails the integrity check, the network shall initiate an re-authentication of the subscriber by initiating an authentication and ciphering procedure. Once integrity protection has been successfully negotiated, the receiving GMM or SM entity in the network shall not process any GMM or SM signalling messages unless they have been successfully integrity checked by the LLC layer. If any GMM or SM signalling message, having not successfully passed the integrity check, is received, then the LLC layer in the network discards that message. The processing of the AUTHENTICATION AND CIPHERING RESPONSE message when authentication is taking place, that has not successfully passed the integrity check at GMM layer is specified in subclause 4.7.7.3. If any GMM or SM signalling message is received, as not integrity protected even though integrity protection has been successfully negotiated, then the GMM layer shall discard this message. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.1.2a.3 |
2,709 | 5.8.18.2 NR sidelink positioning reception | A UE capable of NR sidelink positioning that is configured by upper layers for reception of SL-PRS: 1> if the conditions for NR sidelink positioning operation as defined in 5.8.2 are met: 2> if the frequency used for NR sidelink positioning is included in sl-FreqInfoToAddModList in RRCReconfiguration message or sl-FreqInfoList included in SIB23: 3> if the UE is configured with sl-RxPool and/or sl-PRS-RxPool included in RRCReconfiguration message with reconfigurationWithSync (i.e. handover): 4> configure lower layers to monitor sidelink control information and the corresponding SL-PRS using the pool(s) of resources indicated by sl-RxPool and/or sl-PRS-RxPool; 3> else if the cell chosen for NR sidelink positioning provides SIB23: 4> configure lower layers to monitor sidelink control information and the corresponding SL-PRS using the pool(s) of resources indicated by sl-RxPool and/or sl-PRS-RxPool in SIB23; 2> else: 3> configure lower layers to monitor sidelink control information and the corresponding SL-PRS using the pool(s) of resources that were preconfigured by sl-RxPool and/or sl-PRS-RxPool in SL-PreconfigurationNR, as defined in clause 9.3. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.18.2 |
2,710 | 9.2.1.6 TDD (CSI measurements in case two CSI subframe sets are configured and with CRS assistance information) | The following requirements apply to UE Category ≥2. For the parameters specified in Table 9.2.1.6-1, and using the downlink physical channels specified in tables C.3.2-1 for Cell 1, C3.3-2 for Cell 2 and Cell 3, and C.3.2-2, the reported CQI value according to RC.2 TDD in Table A.4-1 in subframes overlapping with aggressor cell ABS and non-ABS subframes shall be in the range of ±1 of the reported median more than 90% of the time. For test 1 and test 2, if the PDSCH BLER in ABS subframes using the transport format indicated by median CQI obtained by reports in CSI subframe sets CCSI,0 is less than or equal to 0.1, the BLER in ABS subframes using the transport format indicated by the (median CQI + 1) shall be greater than 0.1. If the PDSCH BLER in ABS subframes using the transport format indicated by the median CQI is greater than 0.1, the BLER in ABS subframes using transport format indicated by (median CQI – 1) shall be less than or equal to 0.1. For test 2, if the PDSCH BLER in non-ABS subframes using the transport format indicated by median CQI obtained by reports in CSI subframe sets CCSI,1 is less than or equal to 0.1, the BLER in non-ABS subframes using the transport format indicated by the (median CQI + 2) shall be greater than 0.1. If the PDSCH BLER in non-ABS subframes using the transport format indicated by the median CQI is greater than 0.1, the BLER in non-ABS subframes using transport format indicated by (median CQI – 1) shall be less than or equal to 0.1. Table 9.2.1.6-1: PUCCH 1-0 static test (TDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.2.1.6 |
2,711 | 4.12a.2 Registration via Trusted non-3GPP Access 4.12a.2.1 General | Clause 4.12a.2 specifies how a UE can register to 5GC via a trusted non-3GPP Access Network. The utilized procedure is very similar with the 5GC registration procedure over untrusted non-3GPP access in clause 4.12.2.2 and it is based on the Registration procedure specified in clause 4.2.2.2.2. It uses the same vendor-specific EAP method (called "EAP-5G") as the one specified in clause 4.12.2.1. In this case, the "EAP-5G" method is used between the UE and the TNGF and is utilized for encapsulating NAS messages. In Registration and subsequent Registration procedures via trusted non-3GPP access, the NAS messages are always exchanged between the UE and the AMF. When possible, the UE can be authenticated by reusing the existing UE security context in AMF. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.12a.2 |
2,712 | – UuMessageTransferSidelink | The UuMessageTransferSidelink message is used for the sidelink transfer of Paging message and System Information messages. Signalling radio bearer: SL-SRB3 RLC-SAP: AM Logical channel: SCCH Direction: L2 U2N Relay UE to L2 U2N Remote UE UuMessageTransferSidelink message -- ASN1START -- TAG-UUMESSAGETRANSFERSIDELINK-START UuMessageTransferSidelink-r17 ::= SEQUENCE { criticalExtensions CHOICE { uuMessageTransferSidelink-r17 UuMessageTransferSidelink-r17-IEs, criticalExtensionsFuture SEQUENCE {} } } UuMessageTransferSidelink-r17-IEs ::= SEQUENCE { sl-PagingDelivery-r17 OCTET STRING (CONTAINING PagingRecord) OPTIONAL, -- Need N sl-SIB1-Delivery-r17 OCTET STRING (CONTAINING SIB1) OPTIONAL, -- Need N sl-SystemInformationDelivery-r17 OCTET STRING (CONTAINING SystemInformation) OPTIONAL, -- Need N lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension UuMessageTransferSidelink-v1800-IEs OPTIONAL } UuMessageTransferSidelink-v1800-IEs ::= SEQUENCE { sl-PagingDelivery-r18 OCTET STRING (CONTAINING PagingRecord-v1700) OPTIONAL, -- Need N nonCriticalExtension SEQUENCE {} OPTIONAL } -- TAG-UUMESSAGETRANSFERSIDELINK-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,713 | 9.11.3.30 LADN information | The purpose of the LADN information information element is to provide the UE with the LADN service area for each available LADN in the current registration area or to delete the LADN information at the UE. The LADN information information element is coded as shown in figure 9.11.3.30.1, figure 9.11.3.30.2 and table 9.11.3.30.1. The LADN information is a type 6 information element with a minimum length of 3 octets and a maximum length of 1715 octets. The LADN information information element can contain a minimum of 0 and a maximum of 8 different LADNs each including a DNN and a 5GS tracking area identity list. Figure 9.11.3.30.1: LADN information information element Figure 9.11.3.30.2: LADN Table 9.11.3.30.1: LADN information 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.30 |
2,714 | 9.5.5 Activate Secondary PDP Context Accept | This message is sent by the network to the MS to acknowledge activation of an additional PDP context associated with the same PDP address and APN as an already active PDP context. See Table 9.5.5/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Message type: activate SECONDARY PDP context accept Significance: global Direction: network to MS Table 9.5.5/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Activate secondary PDP context Accept message content | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.5.5 |
2,715 | 6.3.2.3 Network-requested PDU session modification procedure accepted by the UE | Upon receipt of the PDU SESSION MODIFICATION COMMAND message, if the UE provided a DNN during the PDU session establishment, the UE shall stop timer T3396, if it is running for the DNN provided by the UE. If the UE did not provide a DNN during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session", the UE shall stop the timer T3396 associated with no DNN if it is running. If the PDU SESSION MODIFICATION COMMAND message was received for an emergency PDU session, the UE shall not stop the timer T3396 associated with no DNN if it is running. In an SNPN, the timer T3396 to be stopped includes: b) the timer T3396 applied for all the equivalent SNPNs, associated with the RSNPN or an equivalent SNPN, and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and a) the timer T3396 applied for the registered SNPN, associated with the RSNPN, and, if the UE supports access to an SNPN using credentials from a credentials holder, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running. Upon receipt of the PDU SESSION MODIFICATION COMMAND message, if the UE provided an S-NSSAI and a DNN during the PDU session establishment, the UE shall stop timer T3584, if it is running for the [S-NSSAI of the PDU session, DNN] combination provided by the UE. If the UE provided a DNN and did not provide an S-NSSAI during the PDU session establishment, the UE shall stop timer T3584, if it is running for the same [no S-NSSAI, DNN] combination provided by the UE. If the UE provided an S-NSSAI and did not provide a DNN during the PDU session establishment, the UE shall stop timer T3584, if it is running for the same [S-NSSAI, no DNN] combination provided by the UE. If the UE provided neither a DNN nor an S-NSSAI during the PDU session establishment, the UE shall stop timer T3584, if it is running for the same [no S-NSSAI, no DNN] combination provided by the UE. The timer T3584 to be stopped includes: a) in a PLMN: 1) the timer T3584 applied for all the PLMNs, if running; and 2) the timer T3584 applied for the registered PLMN, if running; or b) in an SNPN: 1) the timer T3584 applied for all the equivalent SNPNs, and associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and 2) the timer T3584 applied for the registered SNPN, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running. Upon receipt of the PDU SESSION MODIFICATION COMMAND message, if the UE provided an S-NSSAI during the PDU session establishment, the UE shall stop timer T3585, if it is running for the S-NSSAI of the PDU session. If the UE did not provide an S-NSSAI during the PDU session establishment and the request type was different from "initial emergency request" and different from "existing emergency PDU session", the UE shall stop the timer T3585 associated with no S-NSSAI if it is running. The timer T3585 to be stopped includes: a) in a PLMN: 1) the timer T3585 applied for all the PLMNs and for the access over which the PDU SESSION MODIFICATION COMMAND is received, if running; 2) the timer T3585 applied for all the PLMNs and for both 3GPP access type and non-3GPP access type, if running; 3) the timer T3585 applied for the registered PLMN and for the access over which the PDU SESSION MODIFICATION COMMAND is received, if running; and 4) the timer T3585 applied for the registered PLMN and for both 3GPP access type and non-3GPP access type, if running; or b) in an SNPN: 1) the timer T3585 applied for all the equivalent SNPNs and for the access over which the PDU SESSION AUTHENTICATION COMMAND message is received, associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; 2) the timer T3585 applied for all the equivalent SNPNs and for both 3GPP access type and non-3GPP access type, associated with the RSNPN or an equivalent SNPN and with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; 3) the timer T3585 applied for the registered SNPN and for the access over which the PDU SESSION AUTHENTICATION COMMAND message is received, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running; and 4) the timer T3585 applied for the registered PLMN and for both 3GPP access type and non-3GPP access type, associated with the RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if running. If the PDU SESSION MODIFICATION COMMAND message was received for an emergency PDU session, the UE shall not stop the timer T3585 associated with no S-NSSAI if it is running. NOTE 1: Upon receipt of the PDU SESSION MODIFICATION COMMAND message for a PDU session, if the UE provided a DNN (or no DNN) and an S-NSSAI (or no S-NSSAI) when the PDU session is established, timer T3396 associated with the DNN (or no DNN, if no DNN was provided by the UE) is running, and timer T3584 associated with the DNN (or no DNN, if no DNN was provided by the UE) and the S-NSSAI of the PDU session (or no S-NSSAI, if no S-NSSAI was provided by the UE) is running, then the UE stops both the timer T3396 and the timer T3584. NOTE 2: Upon receipt of the PDU SESSION MODIFICATION COMMAND message for a PDU session, if the UE provided a DNN (or no DNN) and an S-NSSAI (or no S-NSSAI) when the PDU session is established, timer T3585 associated with the S-NSSAI of the PDU session (or no S-NSSAI, if no S-NSSAI was provided by the UE) is running, and timer T3584 associated with the DNN (or no DNN, if no DNN was provided by the UE) and the S-NSSAI of the PDU session (or no S-NSSAI, if no S-NSSAI was provided by the UE) is running, then the UE stops both the timer T3585 and the timer T3584. If the PDU SESSION MODIFICATION COMMAND message includes the Authorized QoS rules IE, the UE shall process the QoS rules sequentially starting with the first QoS rule. If the PDU SESSION MODIFICATION COMMAND message includes the Mapped EPS bearer contexts IE, the UE shall process the mapped EPS bearer contexts sequentially starting with the first mapped EPS bearer context. If the PDU SESSION MODIFICATION COMMAND message includes the Authorized QoS flow descriptions IE, the UE shall process the QoS flow descriptions sequentially starting with the first QoS flow description. The UE shall replace the stored authorized QoS rules, authorized QoS flow descriptions and session-AMBR of the PDU session with the received value(s), if any, in the PDU SESSION MODIFICATION COMMAND message. If the PDU SESSION MODIFICATION COMMAND message includes a Mapped EPS bearer contexts IE, the UE shall check each mapped EPS bearer context for different types of errors as follows: NOTE 3: An error detected in a mapped EPS bearer context does not cause the UE to discard the Authorized QoS rules IE and Authorized QoS flow descriptions IE included in the PDU SESSION MODICATION COMMAND message, if any. a) Semantic error in the mapped EPS bearer operation: 1) operation code = "Create new EPS bearer" and there is already an existing mapped EPS bearer context with the same EPS bearer identity associated with any PDU session. 2) operation code = "Delete existing EPS bearer" and there is no existing mapped EPS bearer context with the same EPS bearer identity associated with the PDU session that is being modified. 3) operation code = "Modify existing EPS bearer" and there is no existing mapped EPS bearer context with the same EPS bearer identity associated with the PDU session that is being modified. 4) operation code = "Create new EPS bearer" or "Modify existing EPS bearer" and the resulting mapped EPS bearer context has invalid mandatory parameters or missing mandatory parameters (e.g., mapped EPS QoS parameters or traffic flow template for a dedicated EPS bearer context). In case 1, if the existing mapped EPS bearer context is associated with the PDU session that is being modified, the UE shall not diagnose an error, further process the create request and, if it was process successfully, delete the old EPS bearer context. In case 2, the UE shall not diagnose an error, further process the delete request and, if it was processed successfully, consider the mapped EPS bearer context as successfully deleted. Otherwise, after sending the PDU SESSION MODIFICATION COMPLETE for the ongoing PDU session modification procedure, the UE shall initiate a PDU session modification procedure by sending a PDU SESSION MODIFICATION REQUEST message to delete the mapped EPS bearer context with 5GSM cause #85 "Invalid mapped EPS bearer identity". b) if the mapped EPS bearer context includes a traffic flow template, the UE shall check the traffic flow template for different types of TFT IE errors as follows: 1) Semantic errors in TFT operations: i) TFT operation = "Create new TFT" when there is already an existing TFT for the EPS bearer context. ii) When the TFT operation is an operation other than "Create a new TFT" and there is no TFT for the EPS bearer context. iii) TFT operation = "Delete packet filters from existing TFT" when it would render the TFT empty. iv) TFT operation = "Delete existing TFT" for a dedicated EPS bearer context. In case iv, after sending the PDU SESSION MODIFICATION COMPLETE for the ongoing PDU session modification procedure, the UE shall initiate a PDU session modification procedure by sending a PDU SESSION MODIFICATION REQUEST message to delete the mapped EPS bearer context with 5GSM cause #41 "semantic error in the TFT operation". In the other cases the UE shall not diagnose an error and perform the following actions to resolve the inconsistency: In case i, the UE shall further process the new activation request to create a new TFT and, if it was processed successfully, delete the old TFT. In case ii, the UE shall: - process the new request and if the TFT operation is "Delete existing TFT" or "Delete packet filters from existing TFT", and if no error according to items 2, 3, and 4 was detected, consider the TFT as successfully deleted; - process the new request as an activation request, if the TFT operation is "Add packet filters in existing TFT" or "Replace packet filters in existing TFT". In case iii, if the packet filters belong to a dedicated EPS bearer context, the UE shall process the new deletion request and, if no error according to items 2, 3, and 4 was detected, after sending the PDU SESSION MODIFICATION COMPLETE for the ongoing PDU session modification procedure, the UE shall initiate a PDU session modification procedure by sending a PDU SESSION MODIFICATION REQUEST message to delete the mapped EPS bearer context with 5GSM cause #41 "semantic error in the TFT operation". In case iii, if the packet filters belong to the default EPS bearer context, the UE shall process the new deletion request and if no error according to items 2, 3, and 4 was detected then delete the existing TFT, this corresponds to using match-all packet filter for the default EPS bearer context. 2) Syntactical errors in TFT operations: i) When the TFT operation = "Create new TFT", "Add packet filters in existing TFT", "Replace packet filters in existing TFT" or "Delete packet filters from existing TFT" and the packet filter list in the TFT IE is empty. ii) TFT operation = "Delete existing TFT" or "No TFT operation" with a non-empty packet filter list in the TFT IE. iii) TFT operation = "Replace packet filters in existing TFT" when the packet filter to be replaced does not exist in the original TFT. iv) TFT operation = "Delete packet filters from existing TFT" when the packet filter to be deleted does not exist in the original TFT. v) Void. vi) When there are other types of syntactical errors in the coding of the TFT IE, such as a mismatch between the number of packet filters subfield, and the number of packet filters in the packet filter list. In case iii, the UE shall not diagnose an error, further process the replace request and, if no error according to items 3 and 4 was detected, include the packet filters received to the existing TFT. In case iv, the UE shall not diagnose an error, further process the deletion request and, if no error according to items 3 and 4 was detected, consider the respective packet filter as successfully deleted. Otherwise, after sending the PDU SESSION MODIFICATION COMPLETE for the ongoing PDU session modification procedure, the UE shall initiate a PDU session modification procedure by sending a PDU SESSION MODIFICATION REQUEST message to delete the mapped EPS bearer context with 5GSM cause #42 "syntactical error in the TFT operation". NOTE 3a: An implementation that strictly follows packet filter list as defined in subclause 10.5.6.12 in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [12] might not detect case 2) ii). 3) Semantic errors in packet filters: i) When a packet filter consists of conflicting packet filter components which would render the packet filter ineffective, i.e. no IP packet will ever fit this packet filter. How the UE determines a semantic error in a packet filter is outside the scope of the present document. ii) When the resulting TFT, which is assigned to a dedicated EPS bearer context, does not contain any packet filter applicable for the uplink direction among the packet filters created on request from the network. After sending the PDU SESSION MODIFICATION COMPLETE for the ongoing PDU session modification procedure, the UE shall initiate a PDU session modification procedure by sending a PDU SESSION MODIFICATION REQUEST message to delete the mapped EPS bearer context with 5GSM cause #44 "semantic errors in packet filter(s)". 4) Syntactical errors in packet filters: i) When the TFT operation = "Create new TFT", "Add packet filters to existing TFT", or "Replace packet filters in existing TFT" and two or more packet filters in the resultant TFT would have identical packet filter identifiers. ii) When the TFT operation = "Create new TFT", "Add packet filters to existing TFT" or "Replace packet filters in existing TFT", and two or more packet filters among all TFTs associated with this PDN connection would have identical packet filter precedence values. iii) When there are other types of syntactical errors in the coding of packet filters, such as the use of a reserved value for a packet filter component identifier. In case i, if two or more packet filters with identical packet filter identifiers are contained in the new request, after sending the PDU SESSION MODIFICATION COMPLETE for the ongoing PDU session modification procedure, the UE shall initiate a PDU session modification procedure by sending a PDU SESSION MODIFICATION REQUEST message to delete the mapped EPS bearer context with 5GSM cause #45 "syntactical error in packet filter(s)". Otherwise, the UE shall not diagnose an error, further process the new request and, if it was processed successfully, delete the old packet filters which have the identical packet filter identifiers. In case ii, if the old packet filters do not belong to the default EPS bearer context, the UE shall not diagnose an error, shall further process the new request and, if it was processed successfully, shall delete the old packet filters which have identical filter precedence values. In case ii, if one or more old packet filters belong to the default EPS bearer context, after sending the PDU SESSION MODIFICATION COMPLETE for the ongoing PDU session modification procedure, the UE shall initiate a PDU session modification procedure by sending a PDU SESSION MODIFICATION REQUEST message to delete the mapped EPS bearer context with 5GSM cause #45 "syntactical errors in packet filter(s)". Otherwise, after sending the PDU SESSION MODIFICATION COMPLETE for the ongoing PDU session modification procedure, the UE shall initiate a PDU session modification procedure by sending a PDU SESSION MODIFICATION REQUEST message to delete the mapped EPS bearer context with 5GSM cause #45 "syntactical error in packet filter(s)". And if a new EPS bearer identity parameter in Authorized QoS flow descriptions IE is received for a QoS flow which can be transferred to EPS, the UE shall update the association between the QoS flow and the mapped EPS bearer context, based on the new EPS bearer identity and the mapped EPS bearer contexts. If the "Delete existing EPS bearer" operation code in the Mapped EPS bearer contexts IE was received, the UE shall discard the association between the QoS flow and the corresponding mapped EPS bearer context and delete the corresponding mapped EPS bearer context. If: a) the UE detects different errors in the mapped EPS bearer contexts as described above which requires sending a PDU SESSION MODIFICATION REQUEST message to delete the erroneous mapped EPS bearer contexts; and b) optionally, if the UE detects errors in QoS rules that require to delete at least one QoS rule as described in subclause 6.3.2.4 which requires sending a PDU SESSION MODIFICATION REQUEST message to delete the erroneous QoS rules; the UE, after sending the PDU SESSION MODIFICATION COMPLETE message for the ongoing PDU session modification procedure, may send a single PDU SESSION MODIFICATION REQUEST message to delete the erroneous mapped EPS bearer contexts, and optionally to delete the erroneous QoS rules. The UE shall include a 5GSM cause IE in the PDU SESSION MODIFICATION REQUEST message. NOTE 4: The 5GSM cause to use cannot be different from #41 "semantic error in the TFT operation", #42 "syntactical error in the TFT operation", #44 "semantic error in packet filter(s)", #45 "syntactical errors in packet filter(s)", #83 "semantic error in the QoS operation", #84 "syntactical error in the QoS operation", or #85 "Invalid mapped EPS bearer identity". The selection of a 5GSM cause is up to UE implementation. Upon receipt of a PDU SESSION MODIFICATION COMMAND message and a PDU session ID, using the NAS transport procedure as specified in subclause 5.4.5, if the UE accepts the PDU SESSION MODIFICATION COMMAND message, the UE considers the PDU session as modified and the UE shall create a PDU SESSION MODIFICATION COMPLETE message. If the PDU SESSION MODIFICATION COMMAND message contains the PTI value allocated in the UE-requested PDU session modification procedure, the UE shall stop the timer T3581. The UE should ensure that the PTI value assigned to this procedure is not released immediately. NOTE 5: The way to achieve this is implementation dependent. For example, the UE can ensure that the PTI value assigned to this procedure is not released during the time equal to or greater than the default value of timer T3591. While the PTI value is not released, the UE regards any received PDU SESSION MODIFICATION COMMAND message with the same PTI value as a network retransmission (see subclause 7.3.1). If the selected SSC mode of the PDU session is "SSC mode 3" and the PDU SESSION MODIFICATION COMMAND message includes 5GSM cause #39 "reactivation requested", the UE can provide to the upper layers the PDU session address lifetime if received in the PDU session address lifetime parameter of the Extended protocol configuration options IE of the PDU SESSION MODIFICATION COMMAND message. After the completion of the network-requested PDU session modification procedure: a) if the PDU session is an MA PDU session: 1) established over both 3GPP access and non-3GPP access, and: - the UE is registered over both 3GPP access and non-3GPP access in the same PLMN: - the UE should re-initiate a UE-requested PDU session establishment procedure as specified in subclause 6.4.1 over the access the PDU SESSION MODIFICATION COMMAND message is received; or - the UE is registered over both 3GPP access and non-3GPP access in different PLMNs: - the UE should re-initiate UE-requested PDU session establishment procedures as specified in subclause 6.4.1 over both accesses. The UE should re-initiate the UE-requested PDU session establishment procedure over the access the PDU SESSION MODIFICATION COMMAND message is received first; or 2) established over only single access: - the UE should re-initiate a UE-requested PDU session establishment procedure as specified in subclause 6.4.1 over the access the user plane resources were established; or b) if the PDU session is a single access PDU session: - the UE should re-initiate a UE-requested PDU session establishment procedure as specified in subclause 6.4.1 over the access the PDU session was associated with; and for the re-initiated UE-requested PDU session establishment procedure(s) the UE should set a new PDU session ID different from the PDU session ID associated with the present PDU session and should set: a) the PDU session type to the PDU session type associated with the present PDU session; b) the SSC mode to the SSC mode associated with the present PDU session; c) the DNN to the DNN associated with the present PDU session; d) the S-NSSAI to: 1) the S-NSSAI associated with (if available in roaming scenarios) a mapped S-NSSAI if provided in the UE-requested PDU session establishment procedure of the present PDU session; or 2) the S-NSSAI received in the PDU SESSION ESTABLISHMENT ACCEPT message of the existing PDU session if the UE received the Alternative S-NSSAI IE in the PDU SESSION MODIFICATION COMMAND message; and e) the alternative S-NSSAI to the S-NSSAI associated with (if available in roaming scenarios) a mapped S-NSSAI if received in the Alternative S-NSSAI IE of the PDU SESSION MODIFICATION COMMAND message. If the UE has indicated support for CIoT 5GS optimizations and receives a small data rate control parameters container in the Extended protocol configuration options IE in the PDU SESSION MODIFICATION COMMAND 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 PDU session in accordance with 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]. If the UE has a previously stored small data rate control parameter value for the PDU session, the UE shall replace the stored small data rate control parameters value for the PDU session with the received small data rate control parameters value in the Extended protocol configuration options IE in the PDU SESSION MODIFICATION COMMAND message. If the UE has indicated support for CIoT 5GS optimizations and receives an additional small data rate control parameters for exception data container in the Extended protocol configuration options IE in the PDU SESSION MODIFICATION COMMAND 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 PDU session in accordance with 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]. If the UE has a previously stored additional small data rate control parameters for exception data value for the PDU session, the UE shall replace the stored additional small data rate control parameters for exception data value for the PDU session with the received additional small data rate control parameters for exception data value in the Extended protocol configuration options IE in the PDU SESSION MODIFICATION COMMAND message. The UE shall include the PDU session ID of the old PDU session which is about to get released in the old PDU session ID IE of the UL NAS TRANSPORT message that transports the PDU SESSION ESTABLISHMENT REQUEST message. NOTE 6: The UE is expected to maintain the PDU session for which the PDU SESSION MODIFICATION COMMAND message including 5GSM cause #39 "reactivation requested" is received during the time indicated by the PDU session address lifetime value or until receiving an indication from upper layers (e.g. that the old PDU session is no more needed). If the selected PDU session type of the PDU session is "Unstructured", the UE supports inter-system change from N1 mode to S1 mode, the UE does not support establishment of a PDN connection for the PDN type set to "non-IP" in S1 mode, and the parameters list field of one or more authorized QoS flow descriptions received in the Authorized QoS flow descriptions IE of the PDU SESSION MODIFICATION COMMAND message contains an EPS bearer identity (EBI), then the UE shall locally remove the EPS bearer identity (EBI) from the parameters list field of such one or more authorized QoS flow descriptions. After sending the PDU SESSION MODIFICATION COMPLETE message for the ongoing PDU session modification procedure, the UE shall initiate a PDU session modification procedure by sending a PDU SESSION MODIFICATION REQUEST message to delete the mapped EPS bearer context with 5GSM cause #85 "Invalid mapped EPS bearer identity". If the selected PDU session type of the PDU session is "Ethernet", the UE supports inter-system change from N1 mode to S1 mode, the UE does not support establishment of a PDN connection for the PDN type set to "non-IP" in S1 mode, the UE, the network or both of them do not support Ethernet PDN type in S1 mode, and the parameters list field of one or more authorized QoS flow descriptions received in the Authorized QoS flow descriptions IE of the PDU SESSION MODIFICATION COMMAND message contains an EPS bearer identity (EBI), the UE shall locally remove the EPS bearer identity (EBI) from the parameters list field of such one or more authorized QoS flow descriptions. After sending the PDU SESSION MODIFICATION COMPLETE message for the ongoing PDU session modification procedure, the UE shall initiate a PDU session modification procedure by sending a PDU SESSION MODIFICATION REQUEST message to delete the mapped EPS bearer context with 5GSM cause #85 "Invalid mapped EPS bearer identity". For a UE which is registered for disaster roaming services and for a PDU session which is not a PDU session for emergency services: a) if the parameters list field of one or more authorized QoS flow descriptions received in the Authorized QoS flow descriptions IE of the PDU SESSION MODIFICATION COMMAND message contains an EPS bearer identity (EBI), then the UE shall locally remove the EPS bearer identity (EBI) from the parameters list field of such one or more authorized QoS flow descriptions; and b) the UE shall locally delete the contents of the Mapped EPS bearer contexts IE if it is received in the PDU SESSION MODIFICATION COMMAND message. If the Always-on PDU session indication IE is included in the PDU SESSION MODIFICATION COMMAND message and: a) the value of the IE is set to "Always-on PDU session required", the UE shall consider the established PDU session as an always-on PDU session; or b) the value of the IE is set to "Always-on PDU session not allowed", the UE shall not consider the established PDU session as an always-on PDU session. If the UE does not receive the Always-on PDU session indication IE in the PDU SESSION MODIFICATION COMMAND message: a) if the network-requested PDU session modification procedure is triggered by a UE-requested PDU session modification procedure upon an inter-system change from S1 mode to N1 mode for a PDN connection established when in S1 mode, the UE shall not consider the modified PDU session as an always-on PDU session; or b) otherwise: 1) if the UE has received the Always-on PDU session indication IE with the value set to "Always-on PDU session required" for this PDU session, the UE shall consider the PDU session as an always-on PDU session; or 2) otherwise the UE shall not consider the PDU session as an always-on PDU session. If the PDU SESSION MODIFICATION COMMAND message contains a Port management information container IE, the UE shall forward the contents of the Port management information container IE to the DS-TT (see 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8] and 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9]). If the UE receives a Serving PLMN rate control IE in the PDU SESSION MODIFICATION COMMAND message, the UE shall store the Serving PLMN rate control IE value, replacing any existing value, and use the stored serving PLMN rate control value as the maximum allowed limit of uplink control plane user data for the corresponding PDU session in accordance with 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]. If the PDU SESSION MODIFICATION COMMAND message includes the Received MBS container IE, for each of the Received MBS informations: a) if MBS decision is set to "MBS join is accepted", the UE shall consider that it has successfully joined the multicast MBS session. The UE shall store the received TMGI and shall use it for any further operation on that multicast MBS session. The UE shall store the received MBS service area associated with the received TMGI, if any, and provide the received TMGI to lower layers. The UE may provide the MBS start time if it is included in the Received MBS information to upper layers; b) if MBS decision is set to "MBS join is rejected", the UE shall consider the requested join as rejected. The UE shall store the received MBS service area associated with the received TMGI, if any. If the received Rejection cause is set to "User is outside of local MBS service area", the UE shall not request to join the same multicast MBS session if neither current TAI nor CGI of the current cell is part of the received MBS service area. If the received Rejection cause is set to "multicast MBS session has not started or will not start soon" and an MBS back-off timer value is included with value that indicates neither zero nor deactivated, the UE shall start a back-off timer T3587 with the value provided in the MBS back-off timer value for the received TMGI, and shall not attempt to join the multicast MBS session with the same TMGI, the Source IP address information of the TMGI, or the Destination IP address information of the TMGI until the expiry of T3587. If the MBS back-off timer value indicates that this timer is deactivated, the UE shall not attempt to join the multicast MBS session with the same TMGI until the UE is switched off, the USIM is removed, or the entry in the "list of subscriber data" for the current SNPN is updated. If the MBS back-off timer value indicates zero, the UE may attempt to join the MBS session with the same TMGI; c) if the MBS decision is set to "Remove UE from multicast MBS session", the UE shall consider that it has successfully left the multicast MBS session, and if the received Rejection cause is set to "multicast MBS session is released", the UE shall consider the multicast MBS session as released. Then the UE shall indicate to lower layers to delete the stored TMGI; d) if the MBS decision is set to "MBS service area update", the UE shall store the received MBS service area associated with the received TMGI and replace the current MBS service area with the received one. or e) if the MBS decision is set to "MBS security information update", the UE shall replace the current MBS security information with the MBS security information received in the MBS security container associated with the received TMGI. If the UE has indicated support for ECS configuration information provisioning in the SESSION ESTABLISHMENT REQUEST message or while in S1 mode, then upon receiving - one or more ECS IPv4 address(es), ECS IPv6 address(es), ECS FQDN(s); - one or more associated ECSP identifier(s);and - optionally spatial validity conditions associated with the ECS address in the Extended protocol configuration options IE of the PDU SESSION MODIFICATION COMMAND message, then the UE shall pass them to the upper layers. If the UE supports receiving DNS server addresses in protocol configuration options and receives one or more DNS server IPv4 address(es), one or more DNS server IPv6 address(es) or both of them, in the Extended protocol configuration options IE of the PDU SESSION MODIFICATION COMMAND message, then the UE shall pass the received DNS server IPv4 address(es), if any, and the received DNS server IPv6 address(es), if any, to upper layers. NOTE 7: The received DNS server address(es) replace previously provided DNS server address(es), if any. If the UE supports the EAS rediscovery and receives: a) the EAS rediscovery indication without indicated impact; or b) the following: 1) one or more EAS rediscovery indication(s) with impacted EAS IPv4 address range, if supported by the UE; 2) one or more EAS rediscovery indication(s) with impacted EAS IPv6 address range, if supported by the UE; 3) one or more EAS rediscovery indication(s) with impacted EAS FQDN, if supported by the UE; or 4) any combination of the above; in the Extended protocol configuration options IE of the PDU SESSION MODIFICATION COMMAND message, then the UE shall pass the EAS rediscovery indication and the received impacted EAS IPv4 address range(s), if supported and included, the received EAS IPv6 address range(s), if supported and included, and the received EAS FQDN(s), if supported and included, to upper layers. NOTE 8: The upper layers handle the EAS rediscovery indication and the impacted EAS IPv4 address range(s), if any, the impacted EAS IPv6 address range(s), if any, and the received EAS FQDN(s), if any, according to 3GPP TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [10A]. Upon receipt of PDU SESSION MODIFICATION COMMAND message, if the network-requested PDU session modification procedure is triggered by a UE-requested PDU session modification procedure, the Service-level-AA container IE is included, then the UE shall forward the service-level-AA contents of the Service-level-AA container IE to the upper layers. If the UE supports EDC and receives the EDC usage allowed indicator in the Extended protocol configuration options IE of the PDU SESSION MODIFICATION COMMAND message, the UE shall indicate to upper layers that network allows the use of EDC. If the UE supports EDC and receives the EDC usage required indicator in the Extended protocol configuration options IE of the PDU SESSION MODIFICATION COMMAND message, the UE shall indicate to upper layers that network requires the use of EDC. NOTE 9: Handling of indication that network allows the use of EDC or that network requires the use of EDC is specified in 3GPP TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [182]. If the Alternative S-NSSAI IE is included in the PDU SESSION MODIFICATION COMMAND message, the UE shall replace the S-NSSAI or the mapped S-NSSAI associated with the PDU session according to the Alternative S-NSSAI IE. The UE shall transport the PDU SESSION MODIFICATION COMPLETE message and the PDU session ID, using the NAS transport procedure as specified in subclause 5.4.5. After sending the PDU SESSION MODIFICATION COMPLETE message, if the "Create new EPS bearer" operation code in the Mapped EPS bearer contexts IE was received in the PDU SESSION MODIFICATION COMMAND message and there is neither a corresponding Authorized QoS flow descriptions IE in the PDU SESSION MODIFICATION COMMAND message nor an existing QoS flow description corresponding to the EPS bearer identity included in the mapped EPS bearer context, the UE shall send a PDU SESSION MODIFICATION REQUEST message including a Mapped EPS bearer contexts IE to delete the mapped EPS bearer context. After sending the PDU SESSION MODIFICATION COMPLETE message, if for the PDU session being modified, there are mapped EPS bearer context(s) but none of them is associated with the default QoS rule, the UE shall locally delete the mapped EPS bearer context(s) and shall locally delete the stored EPS bearer identity (EBI) in all the QoS flow descriptions of the PDU session, if any. If a port management information container needs to be delivered (see 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8] and 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9]), the UE shall include a Port management information container IE in the PDU SESSION MODIFICATION COMPLETE message. Upon receipt of a PDU SESSION MODIFICATION COMPLETE message, the SMF shall stop timer T3591 and shall consider the PDU session as modified. If the selected SSC mode of the PDU session is "SSC mode 3" and the PDU SESSION MODIFICATION COMMAND message included 5GSM cause #39 "reactivation requested", the SMF shall start timer T3593. If the PDU Session Address Lifetime value is sent to the UE in the PDU SESSION MODIFICATION COMMAND message then timer T3593 shall be started with the same value, otherwise it shall use a default value. If the PDU SESSION MODIFICATION COMPLETE message contains a Port management information container IE, the SMF shall handle the contents of the Port management information container IE as specified in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8] and 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9]. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.3.2.3 |
2,716 | 9.9.4.5 ESM information transfer flag | The purpose of the ESM information transfer flag information element is to indicate whether ESM information, i.e. protocol configuration options or APN or both, is to be transferred security protected. The ESM information transfer flag information element is coded as shown in figure 9.9.4.5.1 and table 9.9.4.5.1. The ESM information transfer flag is a type 1 information element. Figure 9.9.4.5.1: ESM information transfer flag information element Table 9.9.4.5.1: ESM information transfer flag information element | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.9.4.5 |
2,717 | Annex J (informative): Store and Forward Satellite operation | The Store and Forward Satellite operation in a 5G system with satellite access is intended to provide some level of communication service for UEs under satellite coverage with intermittent/temporary satellite connectivity (e.g. when the satellite is not connected via a feeder link or via ISL to the ground network) for delay-tolerant communication service. An example of “S&F Satellite operation” is illustrated in Figure J-1, in contrast to what could be considered the current assumption for the “normal/default Satellite operation” of a 5G system with satellite access. As shown in Figure J-1: Under “normal/default Satellite operation” mode, signalling and data traffic exchange between a UE with satellite access and the remote ground network requires the service and feeder links to be active simultaneously, so that, at the time that the UE interacts over the service link with the satellite, there is a continuous end-to-end connectivity path between the UE, the satellite and the ground network. - In contrast, under “S&F Satellite operation” mode, the end-to-end exchange of signalling/data traffic is now handled as a combination of two steps not concurrent in time (Step A and B in Figure J-1). In Step A, signalling/data exchange between the UE and the satellite takes place, without the satellite being simultaneously connected to the ground network (i.e. the satellite is able to operate the service link without an active feeder link connection). In Step B, connectivity between the satellite and the ground network is established so that communication between the satellite and the ground network can take place. So, the satellite moves from being connected to the UE in step A to being connected to the ground network in step B. Figure J-1: Illustration of “normal/default operation” and “S&F Satellite operation” modes in a 5G system with satellite access. The concept of “S&F” service is widely used in the fields of delay-tolerant networking and disruption-tolerant networking. In 3GPP context, a service that could be assimilated to an S&F service is SMS, for which there is no need to have an end-to-end connectivity between the end-points (e.g. an end-point can be a UE and the other an application server) but only between the end-points and the SMSC which acts as an intermediate node in charge of storing and relying. The support of S&F Satellite operation is especially suited for the delivery of delay-tolerant/non-real-time IoT satellite services with NGSO satellites. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | Annex |
2,718 | 6.1.3.22 GNSS Measurement Command MAC Control Element | The GNSS Measurement Command MAC Control Element is identified by a MAC PDU subheader with LCID as specified in table 6.2.1-1. It has a fixed size and consists of a single octet defined as follow (Figure 6.1.3.22-1): - T: The Type field is a flag indicating UE is triggered by network to perform GNSS measurement or just a GNSS measurement gap length is provided for UE-autonomous measurement. The T field set to "0" indicates UE needs to perform GNSS measurement with the GNSS measurement gap length configured in this MAC CE. The T field set to "1" indicates the GNSS measurement gap length configured in this MAC CE needs to be stored and used for the subsequent UE-autonomous GNSS measurement; - R: Reserved bit, set to 0; - GNSS Measurement Gap Length: the field corresponds to the configuration of GNSS measurement gap length as shown in Table 6.1.3.22-1. The length of the field is 4 bits. Figure 6.1.3.22-1: GNSS Measurement Command MAC control element Table 6.1.3.22-1: Values of GNSS Measurement Gap Length field | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.1.3.22 |
2,719 | 8.10.1.1.1A Transmit diversity performance wit Enhanced Performance Requirement Type A - 2 Tx Antenna Ports with TM3 interference model | The requirements are specified in Table 8.10.1.1.1A-2, with the addition of parameters in Table 8.10.1.1.1A-1 and the downlink physical channel setup according to Annex C.3.2. The purpose is to verify the performance of transmit diversity (SFBC) with 2 transmit antennas when the PDSCH transmission in the serving cell is interfered by PDSCH of one dominant interfering cells applying transmission mode 3 interference model defined in clause B.5.2. In Table 8.10.1.1.1A-1, Cell 1 is the serving cell, and Cell 2 is an interfering cell. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1 and Cell 2, respectively. Table 8.10.1.1.1A-1: Test Parameters for Transmit diversity Performance (FRC) with TM3 interference model Table 8.10.1.1.1A-2: Enhanced Performance Requirement Type A, Transmit Diversity (FRC) with TM3 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.10.1.1.1A |
2,720 | 5.5.1.2.6 Initial registration for emergency services not accepted by the network | Upon receiving the REGISTRATION REJECT message including 5GMM cause #5 "PEI not accepted", the UE shall enter the state 5GMM-DEREGISTERED.NO-SUPI. If the REGISTRATION REJECT message is received, - over 3GPP access; or - over non-3GPP access and is integrity protected; and the UE also supports the registration procedure over the other access, the UE shall in addition handle 5GMM parameters and 5GMM state for this access, as described for this 5GMM cause value. Upon receiving the REGISTRATION REJECT message including 5GMM cause value which is not #5 "PEI not accepted", the UE shall perform the actions as described in subclause 5.5.1.2.5 with the following addition: the UE shall inform the upper layers of the failure of the procedure. NOTE 1: This can result in the upper layers requesting implementation specific mechanisms, e.g. procedures specified in 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [14] can result in the emergency call being attempted to another IP-CAN. If the initial registration request for emergency services fails due to abnormal cases, the UE shall perform the actions as described in subclause 5.5.1.2.7 and inform the upper layers of the failure to access the network or the failure of the procedure. NOTE 2: This can result in the upper layers requesting other implementation specific mechanisms, e.g. procedures specified in 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [14] can result in the emergency call being attempted to another IP-CAN. In a shared network, upon receiving the REGISTRATION REJECT message, the UE shall perform the actions as described in subclause 5.5.1.2.5, and shall: a) inform the upper layers of the failure of the procedure; or NOTE 3: The upper layers can request implementation specific mechanisms, e.g. procedures specified in 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [14] that can result in the emergency call being attempted to another IP-CAN. b) attempt to perform a PLMN or SNPN selection in the shared network and, if an initial registration for emergency services was not already attempted with the selected PLMN or SNPN and the REGISTRATION REQUEST message, for which the REGISTRATION REJECT message was received, is: - not for sending a PDU SESSION ESTABLISHMENT REQUEST message with request type set to "existing emergency PDU session", initiate an initial registration for emergency services with the selected PLMN or SNPN; or - for sending a PDU SESSION ESTABLISHMENT REQUEST message with request type set to "existing emergency PDU session", and: i) the selected PLMN is an equivalent PLMN or the selected SNPN is an equivalent SNPN, initiate an initial registration for emergency services with the selected PLMN or SNPN; and ii) the selected PLMN is not an equivalent PLMN or the selected SNPN is not an equivalent SNPN, perform a PLMN or SNPN selection and initiate an initial registration for emergency services with the selected PLMN or SNPN if an initial registration for emergency services was not already attempted with the selected PLMN or SNPN. In a shared network, if the initial registration request for emergency services fails due to abnormal cases, the UE shall perform the actions as described in subclause 5.5.1.2.7 and shall: a) inform the upper layers of the failure of the procedure; or NOTE 4: The upper layers can request implementation specific mechanisms, e.g. procedures specified in 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [14] that can result in the emergency call being attempted to another IP-CAN. b) attempt to perform a PLMN or SNPN selection in the shared network and, if an initial registration for emergency services was not already attempted with the selected PLMN or SNPN and the REGISTRATION REQUEST message is: - not for sending a PDU SESSION ESTABLISHMENT REQUEST message with request type set to "existing emergency PDU session", initiate an initial registration for emergency services with the selected PLMN or SNPN; or - for sending a PDU SESSION ESTABLISHMENT REQUEST message with request type set to "existing emergency PDU session", and: i) the selected PLMN is an equivalent PLMN or the selected SNPN is an equivalent SNPN, initiate an initial registration for emergency services with the selected PLMN or SNPN; and ii) the selected PLMN is not an equivalent PLMN or the selected SNPN is not an equivalent SNPN, perform a PLMN or SNPN selection and initiate an initial registration for emergency services with the selected PLMN or SNPN if an initial registration for emergency services was not already attempted with the selected PLMN or SNPN. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.1.2.6 |
2,721 | 5.8.5a.2 Initiation | A UE capable of V2X sidelink communication initiates the transmission of SLSS and MasterInformationBlock-SL-V2X according to the conditions and the procedures specified for V2X sidelink communication in clause 5.10.7 of TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10]. NOTE 1: When applying the procedure in this clause, SIB13 and SIB14 correspond to SystemInformationBlockType21 and SystemInformationBlockType26 specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10] respectively. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.5a.2 |
2,722 | 6.6.2.2A.2 Minimum requirement CA_66B (network signalled value "CA_NS_09") | Additional spectrum emission requirements are signalled by the network to indicate that the UE shall meet an additional requirement for a specific deployment scenario as part of the cell handover/broadcast message. When "CA_NS_09" is indicated in the cell, the power of any UE emission shall not exceed the levels specified in Table 6.6.2.2A.2-1. Table 6.6.2.2A.2-1: Additional requirements NOTE: As a general rule, the resolution bandwidth of the measuring equipment should be equal to the measurement bandwidth. However, to improve measurement accuracy, sensitivity and efficiency, the resolution bandwidth may be smaller than the measurement bandwidth. When the resolution bandwidth is smaller than the measurement bandwidth, the result should be integrated over the measurement bandwidth in order to obtain the equivalent noise bandwidth of the measurement bandwidth. | 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.2.2A.2 |
2,723 | 1.4 Conventions on bit ordering | The following conventions hold for the coding of the different identities appearing in the present document and in other GSM Technical Specifications if not indicated otherwise: - the different parts of an identity are shown in the figures in order of significance; - the most significant part of an identity is on the left part of the figure and the least significant on the right. When an identity appears in other Technical Specifications, the following conventions hold if not indicated otherwise: - digits are numbered by order of significance, with digit 1 being the most significant; - bits are numbered by order of significance, with the lowest bit number corresponding to the least significant bit. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 1.4 |
2,724 | 16.3.3 Resource Isolation and Management 16.3.3.1 General | Resource isolation enables specialized customization and avoids one slice affecting another slice. Hardware/software resource isolation is up to implementation. Each slice may be assigned with either shared, prioritized or dedicated radio resource up to RRM implementation and SLA as in TS 28.541[ Management and orchestration; 5G Network Resource Model (NRM); Stage 2 and stage 3 ] [49]. To enable differentiated handling of traffic for network slices with different SLA: - NG-RAN is configured with a set of different configurations for different network slices by OAM; - To select the appropriate configuration for the traffic for each network slice, NG-RAN receives relevant information indicating which of the configurations applies for this specific network slice. Slice-based RACH configuration for RA isolation and prioritization can be included in SIB1 messages. The slice-based RACH configurations are associated to specific NSAG(s), and if not provided for a NSAG that UE considers for selecting the RACH configuration, then the UE does not consider the NSAG for selecting the slice-based RACH configuration. The UE determines the NSAG to be considered during RA as specified in TS 23.501[ System architecture for the 5G System (5GS) ] [3]. When the UE AS does not receive any NSAG information from NAS for Random Access, the UE does not apply the slice-based RACH configuration. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.3.3 |
2,725 | 5.2.6.25.7 Nnef_TimeSynchronization_CapsUnsubscribe operation | Service operation name: Nnef_TimeSynchronization_CapsUnsubscribe Description: The AF requests to unsubscribe from receiving notifications about time synchronization capabilities for a list of UE(s) or a group of UEs or any UE using a DNN/S-NSSAI combination, for which the NEF authorizes the request and invokes the corresponding service operation with TSCTSF (clause 5.2.27.2.7). Inputs, Required: As specified in clause 5.2.27.2.7. Inputs, Optional: None. Outputs, Required: Operation execution result indication and in the case of successful operation, any outputs as specified in clause 5.2.27.2.7. Outputs, Optional: As specified in clause 5.2.27.2.7. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.6.25.7 |
2,726 | 5.3.13 RRC connection resume 5.3.13.1 General | Figure 5.3.13.1-1: RRC connection resume, successful Figure 5.3.13.1-2: RRC connection resume fallback to RRC connection establishment, successful Figure 5.3.13.1-3: RRC connection resume followed by network release, successful Figure 5.3.13.1-4: RRC connection resume followed by network suspend, successful Figure 5.3.13.1-5: RRC connection resume, network reject The purpose of this procedure is to resume a suspended RRC connection, including resuming SRB(s), DRB(s) and multicast MRB(s) or perform an RNA update. This procedure is also used to initiate SDT in RRC_INACTIVE. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.13 |
2,727 | 6.14.2.2 Procedure for steering of UE in VPLMN or HPLMN after registration | The security procedure for the steering of UE in VPLMN after registration is described below in figure 6.14.2.2-1: Figure 6.14.2.2-1: Procedure for providing list of preferred PLMN/access technology combinations after registration 1) The UDM decides to notify the UE of the changes to the Steering of Roaming Information by the means of invoking Nudm_SDM_Notification service operation. 2-3) The UDM shall invoke Nausf_SoRProtection service operation message by including the ACK Indication and optionally the list of preferred PLMN/access technology combinations or secured packet or SoR transparent container (only if transparent container is supported by the AMF) to the AUSF to get SoR-MAC-IAUSF and CounterSoR as specified in sub-clause 14.1.3 of this document. The UDM shall select the AUSF that holds the latest KAUSF of the UE. If the HPLMN decided that the UE is to acknowledge the successful security check of the received Steering of Roaming Information, then the UDM shall set accordingly the ACK Indication included in the Nausf_SoRProtection service operation message to signal that it also needs the expected SoR-XMAC-IUE, as specified in sub-clause 14.1.3 of this document. NOTE: At reception of Nausf_SoRProtection_Protect request from the UDM, if the SoR header is not included in the request, the AUSF constructs the SOR header, as described in clause 9.11.3.51 of TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [35], based on the information received from the UDM, i.e. ACK Indication and optionally the list of preferred PLMN/access technology combinations or secured packet; otherwise, if the SoR header in contained in the request, the AUSF uses the received SoR header in the calculation of SoR-MAC-IAUSF.. The details of the CounterSoR are specified in sub-clause 6.14.2.3 of this document. The inclusion of the Steering List and the SOR header in the calculation of SoR-MAC-IAUSF allows the UE to verify that the Steering of Roaming Information received is not tampered with or removed by the VPLMN. The inclusion of these information in the calculation of the expected SoR-XMAC-IUE allows the UDM to verify that the UE received the Steering of Roaming Information. 4) The UDM shall invoke Nudm_SDM_Notification service operation, which contains the SoR transaprent container as specified in clause 6.1.6.3.2 of TS 29.503[ 5G System; Unified Data Management Services; Stage 3 ] [93] if the VPMN AMF support SOR transparent container, or contains individual IEs including an optional the list of preferred PLMN/access technology combinations or secured packet, the ACK Indication, SoR-MAC-IAUSF, and CounterSoR within the Access and Mobility Subscription data. If the UDM requests an acknowledgement, it shall temporarily store the expected SoR-XMAC-IUE. 5) Upon receiving the Nudm_SDM_Notification message, if the SoR transparent container is included in the message, the AMF shall send a DL NAS Transport message to the served UE. including the received SoR transparent container; otherwise, the AMF shall construct the SOR transparent container (including the SOR header) as specified in clause 9.11.3.51 of 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [35] based on the ACK Indication, the Steering List, SoR-MAC-IAUSF and CounterSoR received from the UDM, and send the constructed SoR transparent container included to the served UE in a DL NAS Transport message. 6) On receiving the DL NAS Transport message, the UE shall calculate the SoR-MAC-IAUSF in the same way as the AUSF (as specified in Annex A.17) on the received SoR transparent container, including the CounterSoR and the SoR header and verify whether it matches the SoR-MAC-IAUSF value received in the DL NAS Transport message. 7) If the UDM has requested an acknowledgement from the UE and the UE verified that the Steering Information has been provided by the HPLMN, then the UE shall send the UL NAS Transport message to the serving AMF. The UE shall generate the SoR-MAC-IUE as specified in Annex A.18 and includes the generated SoR-MAC-IUE in a SOR transparent container in the UL NAS Transport message. 8) The AMF shall send a Nudm_SDM_Info request message to the UDM. If a SOR transparent container with the SoR-MAC-IUE was received in the UL NAS Transport message, the AMF shall include the received SoR transparent container in the Nudm_SDM_Info request message if the AMF supports SoR transparent container, otherwise, the AMF shall include the SoR-MAC-IUE in the Nudm_SDM_Info request message. 9) If the HPLMN indicated that the UE is to acknowledge the successful security check of the received Steering of Roaming Information, then the UDM shall compare the received SoR-MAC-IUE with the expected SoR-XMAC-IUE that the UDM stored temporarily in step 4. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.14.2.2 |
2,728 | A.8 Algorithm key derivation functions | When deriving keys for NAS integrity and NAS encryption algorithms from KAMF in the AMF and UE or ciphering and integrity keys from KgNB/ KSN in the gNB and UE, the following parameters shall be used to form the string S. - FC = 0x69 - P0 = algorithm type distinguisher - L0 = length of algorithm type distinguisher (i.e. 0x00 0x01) - P1 = algorithm identity - L1 = length of algorithm identity (i.e. 0x00 0x01) The algorithm type distinguisher shall be N-NAS-enc-alg for NAS encryption algorithms and N-NAS-int-alg for NAS integrity protection algorithms. The algorithm type distinguisher shall be N-RRC-enc-alg for RRC encryption algorithms, N-RRC-int-alg for RRC integrity protection algorithms, N-UP-enc-alg for UP encryption algorithms and N-UP-int-alg for UP integrity protection algorithms (see table A.8-1). The values 0x00 and 0x07 to 0xf0 are reserved for future use, and the values 0xf1 to 0xff are reserved for private use. Table A.8-1: Algorithm type distinguishers The algorithm identity (as specified in clause 5) shall be put in the four least significant bits of the octet. The two least significant bits of the four most significant bits are reserved for future use, and the two most significant bits of the most significant nibble are reserved for private use. The entire four most significant bits shall be set to all zeros. For the derivation of integrity and ciphering keys used between the UE and gNB, the input key shall be the 256-bit KgNB// KSN. For the derivation of integrity and ciphering keys used between the UE and AMF, the input key shall be the 256-bit KAMF. For an algorithm key of length n bits, where n is less or equal to 256, the n least significant bits of the 256 bits of the KDF output shall be used as the algorithm key. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | A.8 |
2,729 | 5.2.2.4.10 Actions upon reception of SIB9 | Upon receiving SIB9 with referenceTimeInfo, the UE may perform the related actions except for the action of ignoring all further referenceTimeInfo received in SIB9 as specified in clause 5.7.1.3. Upon receiving SIB9 with eventID-TSS, the UE shall perform the related actions if requested by upper layers: 1> if VarEventID has an entry with a storedEventID value: 2> if the storedEventID value within VarEventID is different from the eventID-TSS value received within SIB9: 3> consider that the content of clockQualityDetailsLevel may have changed; 3> notify upper layers that clockQualityDetailsLevel may have changed; 3> replace the storedEventID value within VarEventID with the eventID-TSS value received within SIB9; 3> replace the storedGnbID value within VarGnbID with the gNB identity value received within SIB1; 2> else: 3> if the VarGnbID has an entry with a storedGnbID value: 4> if the storedGnbID value within VarGnbID is different from the gNB identity value received within SIB1: 5> consider that the content of clockQualityDetailsLevel may have changed; 5> notify upper layers that clockQualityDetailsLevel may have changed; 5> replace the storedGnbID value within VarGnbID with the gNB identity value received within SIB1; NOTE: The UE should calculate the value of the gNB identity as the value of gNB-ID-Length leftmost bits of the 36-bit long cellIdentity in the first PLMN-IdentityInfo IE of PLMN-IdentityInfoList in SIB1. 1> else: 2> add a new entry of storedEventID within the VarEventID with the eventID-TSS value received within SIB9; 2> add a new entry of storedGnbID within the VarGnbID with the gNB identity value received within SIB1; 2> notify upper layers that clockQualityDetailsLevel may have changed; | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.2.2.4.10 |
2,730 | 10.2.2 Unauthenticated IMS Emergency Sessions 10.2.2.1 General | There are many scenarios when an unauthenticated Emergency Session may be established without the network having to authenticate the UE or apply ciphering or integrity protection for either AS or NAS. For example: a) UEs that are in Limited service state UEs, as specified in clause 3.5 in TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] b) UEs that have valid subscription but SN cannot complete authentication because of network failure or other reasons TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] clause 4.3.12.1 identifies four possible network behaviours of emergency bearer support. Amongst these, the following two cases are applicable for unauthenticated emergency sessions: a. IMSI required, authentication optional. These UEs shall have a SUPI. If authentication fails, the UE is granted access and the unauthenticated SUPI retained in the network for recording purposes. The PEI is used in the network as the UE identifier. PEI only UEs will be rejected (e.g. UICCless UEs). b. All UEs are allowed. Along with authenticated UEs, this includes UEs with a SUPI that cannot be authenticated and UEs with only an PEI. If an unauthenticated SUPI is provided by the UE, the unauthenticated SUPI is retained in the network for recording purposes. The PEI is used in the network to identify the UE. The network policy is configured to one of the above, and accordingly determine how emergency requests from the UE are treated. If the ME receives a NAS SMC selecting NIA0 (NULL integrity) for integrity protection, and NEA0 (NULL ciphering) for encryption protection, then: - the ME shall mark any stored native 5G NAS security context on the USIM /non-volatile ME memory as invalid; and - the ME shall not update the USIM/non-volatile ME memory with the current 5G NAS security context. These two rules override all other rules regarding updating the 5G NAS security context on the USIM/non-volatile ME memory, in the present document. If NIA0 is used, and the NAS COUNT values wrap around, and a new KAMF has not been established before the NAS COUNT wrap around, the NAS connection shall be kept. NOTE: For unauthenticated IMS emergency sessions, NIA0, i.e., null integrity algorithm, is used for integrity protection. Additionally, as the NAS COUNT values can wrap around, the initialization of the NAS COUNT values are not crucial. Uplink and downlink NAS COUNT are incremented for NAS message that use NIA0, as for any other NAS messages. A UE without a valid 5G subscription shall at an IRAT handover to 5G, when an IMS Emergency Service is active, be considered by the AMF to be unauthenticated. In such a scenario, EIA0 shall be used in 5G after handover if the target network policy allows unauthenticated IMS Emergency Sessions. A handover from 5G to another RAT, of an unauthenticated IMS Emergency Session, shall result in an unauthenticated IMS Emergency Session in the other RAT. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 10.2.2 |
2,731 | 5.2.5.7.4 Npcf_EventExposure_Notify service operation | Service operation name: Npcf_EventExposure_Notify. Description: This service operation reports the event to the consumer that has previously subscribed either using Npcf_EventExposure_Subscribe service operation or provided as part of the Data Set Application Data and Data Subset Service Parameters stored in UDR. Inputs, Required: Event ID, corresponding UE IDs (GPSI(s), SUPI), Notification Correlation Information, time stamp. The PCF reports the SUPI and if available GPSI(s) for each of the events. The PCF may report the reports multiple events when those happen at the same time and as indicated in the time stamp. Inputs, Optional: Internal-Group-Id, Event specific information. Outputs, Required: None. When the PCF detects the event subscribed by the NF consumer, the PCF reports the subscribed event together with the Notification Target Address (+ Notification Correlation ID) to the Event Receiving NF. The optional event specific parameter list provides the values that matched for generating the event notification. The parameter values to match are specified during the event subscription (see clause 6.1.3.18 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20] and clauses 5.2.5.7.2 and 5.2.5.7.1). See clause 4.15.6.7 and 4.1.5.6.10 for details on usage of this service operation toward Application Function. The PCF provides, in addition to the SUPI and if available GPSI(s), the Internal-Group-Id if provided as Target UE in the Service Parameters stored in UDR. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.5.7.4 |
2,732 | 8.9.2 Bearer context setup over F1-U | Figure 8.9.2-1 shows the procedure used to setup the bearer context in the gNB-CU-UP. Figure 8.9.2-1: Bearer context setup over F1-U 0. Bearer context setup (e.g., following an SGNB ADDITION REQUEST message from the MeNB) is triggered in gNB-CU-CP. 1. The gNB-CU-CP sends a BEARER CONTEXT SETUP REQUEST message containing UL TNL address information for S1-U or NG-U, and if required, DL TNL address information for X2-U to setup the bearer context in the gNB-CU-UP. For NG-RAN, the gNB-CU-CP decides flow-to-DRB mapping and sends the generated SDAP and PDCP configuration to the gNB-CU-UP. NOTE: In case of Conditional Handover or Conditional PSCell Addition/Change, the BEARER CONTEXT SETUP REQUEST message indicates to ignore the included security context and not to initiate sending downlink packets until the UE successfully accesses. Up to implementation, the gNB-CU-CP may request to establish bearer context as if a regular HO was requested. 2. The gNB-CU-UP responds with a BEARER CONTEXT SETUP RESPONSE message containing the UL TNL address information for F1-U, and DL TNL address information for S1-U or NG-U, and if required, UL TNL address information for X2-U or Xn-U. NOTE: The indirect data transmission for split bearer through the gNB-CU-UP is not precluded. 3. F1 UE context setup procedure is performed to setup one or more bearers in the gNB-DU. 4. The gNB-CU-CP sends a BEARER CONTEXT MODIFICATION REQUEST message containing the DL TNL address information for F1-U or Xn-U, and PDCP status. NOTE: In case the indirect path indication is received in step 4, the gNB-CU-UP may not discard the DL data based on the Downlink Data Delivery Status frame received from the gNB-DU. During the inter-gNB indirect-to-direct or indirect-to-indirect path switching, the source gNB-CU-UP forwards the buffered DL data to the target gNB as specified in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [2]. 5. The gNB-CU-UP responds with a BEARER CONTEXT MODIFICATION RESPONSE message. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.9.2 |
2,733 | 5.15.6 Network Slicing Support for Roaming | For roaming scenarios: - If the UE only uses standard S-NSSAI values, then the same S-NSSAI values can be used in VPLMN as in the HPLMN. - If the VPLMN and HPLMN have an SLA to support non-standard S-NSSAI values in the VPLMN, the NSSF of the VPLMN maps the Subscribed S-NSSAIs values to the respective S-NSSAI values to be used in the VPLMN. The S-NSSAI values to be used in the VPLMN are determined by the NSSF of the VPLMN based on the SLA. The NSSF of the VPLMN need not inform the HPLMN of which values are used in the VPLMN. Depending on operator's policy and the configuration in the AMF, the AMF may decide the S-NSSAI values to be used in the VPLMN and the mapping to the Subscribed S-NSSAIs. For the home routed case, the AMF or NSSF may select an S-NSSAI (if the UE does not provide an S-NSSAI for the PDU session establishment) and a Network Slice instance, based on load level and/or Observe Service Experience and/or Dispersion analytics of the VPLMN and/or that of the HPLMN from NWDAF as described in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [86]. - The UE constructs Requested NSSAI and provides the mapping of S-NSSAIs of the Requested NSSAI to HPLMN S-NSSAIs if the mapping is stored in the UE, as described in clause 5.15.5.2.1. - The NSSF in the VPLMN determines the Allowed NSSAI without interacting with the HPLMN. - the HPLMN may provide NSSRG Information as part of the Subscription information as described in clause 5.15.12. - The Allowed NSSAI in the Registration Accept includes S-NSSAI values used in the VPLMN. The mapping information described above is also provided to the UE with the Allowed NSSAI as described in clause 5.15.4. - If the S-NSSAI values are subject to NSAC, depending on operator's policy, a roaming agreement or an SLA between VPLMN and HPLMN, the AMF or SMF in VPLMN triggers a request for NSAC for these S-NSSAI values as described in clause 5.15.11.3. - In PDU Session Establishment procedure, the UE includes both: (a) the S-NSSAI that matches the application (that is triggering the PDU Session Request) within the NSSP in the URSP rules or within the UE Local Configuration as defined in clause 6.1.2.2.1 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]; the value of this S NSSAI is used in the HPLMN; and (b) an S-NSSAI belonging to the Allowed NSSAI that maps to (a) using the mapping of the Allowed NSSAI to HPLMN S-NSSAIs; the value of this S-NSSAI is used in the VPLMN. For the home routed case, the AMF may select the V-SMF and the H-SMF based on network data analytics (NF load, etc.) of the VPLMN and that of the HPLMN from the NWDAF as described in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [86]. The V-SMF sends the PDU Session Establishment Request message to the H-SMF along with the S-NSSAI with the value used in the HPLMN (a). If the S-NSSAI values are subject to NSAC, the V-SMF or H-SMF triggers a request for NSAC for these S-NSSAI values as described in clause 5.15.11.3. - When a PDU Session is established, the CN provides to the AN the S-NSSAI with the value from the VPLMN corresponding to this PDU Session, as described in clause 5.15.5.3. - The Network Slice instance specific network functions in the VPLMN are selected by the VPLMN by using the S-NSSAI with the value used in the VPLMN and querying an NRF that has either been pre-configured, or provided by the NSSF in the VPLMN. The Network Slice specific functions of the HPLMN (if applicable) are selected by the VPLMN by using the related S-NSSAI with the value used in the HPLMN via the support from an appropriate NRF in the HPLMN, identified as specified in clause 4.17.5 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] and, for SMF in clause 4.3.2.2.3.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. - If the serving AMF supports the Network Slice Replacement feature and is configured to use the NSSF for Network Slice Replacement triggering, the AMF subscribes with the NSSF of the VPLMN for notifications when an HPLMN S-NSSAI needs to be replaced with an Alternative S-NSSAI, in addition to notifications for the Serving PLMN S-NSSAIs. The NSSF of the VPLMN shall subscribe with the NSSF of the HPLMN for notifications when an HPLMN S-NSSAI needs to be replaced with an Alternative S-NSSAI. - If the serving AMF support the Network Slice Instance Replacement and configured to use Network Slice Instance Replacement, the AMF subscribes with the NSSF of the VPLMN for notifications when a Network Slice instance is congested or no longer available as described in clause 5.15.19. The NSSF of the VPLMN shall subscribe with the NSSF of the HPLMN for notifications when the Network Slice instance is congested or no longer available. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.15.6 |
2,734 | – BetaOffsets | The IE BetaOffsets is used to configure beta-offset values, see TS 38.213[ NR; Physical layer procedures for control ] [13], clause 9.3. BetaOffsets information element -- ASN1START -- TAG-BETAOFFSETS-START BetaOffsets ::= SEQUENCE { betaOffsetACK-Index1 INTEGER(0..31) OPTIONAL, -- Need S betaOffsetACK-Index2 INTEGER(0..31) OPTIONAL, -- Need S betaOffsetACK-Index3 INTEGER(0..31) OPTIONAL, -- Need S betaOffsetCSI-Part1-Index1 INTEGER(0..31) OPTIONAL, -- Need S betaOffsetCSI-Part1-Index2 INTEGER(0..31) OPTIONAL, -- Need S betaOffsetCSI-Part2-Index1 INTEGER(0..31) OPTIONAL, -- Need S betaOffsetCSI-Part2-Index2 INTEGER(0..31) OPTIONAL -- Need S } -- TAG-BETAOFFSETS-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,735 | 10.5.7.5 Radio priority 2 | The purpose of the radio priority 2 information element is to specify the priority level that the MS shall use at the lower layers for transmission of mobile originated TOM8 transmission. The radio priority 2 information element is coded as shown in figure 10.5.7.5-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.7.5-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The radio priority is a type 1 information element. Figure 10.5. 7.5-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Radio priority 2 information element Table 10.5. 7.5-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Radio priority 2 information element | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.7.5 |
2,736 | 6.22.2 Requirements 6.22.2.1 General | Based on operator policy, the 5G system shall be able to prevent UEs from accessing the network using relevant barring parameters that vary depending on Access Identity and Access Category. Access Identities are configured at the UE as listed in Table 6.22.2.2-1. Access Categories are defined by the combination of conditions related to UE and the type of access attempt as listed in Table 6.22.2.3-1. One or more Access Identities and only one Access Category are selected and tested for an access attempt. The 5G network shall be able to broadcast barring control information (i.e. a list of barring parameters associated with an Access Identity and an Access Category) in one or more areas of the RAN. The UE shall be able to determine whether or not a particular new access attempt is allowed based on barring parameters that the UE receives from the broadcast barring control information and the configuration in the UE. In the case of multiple core networks sharing the same RAN, the RAN shall be able to apply access control for the different core networks individually. The unified access control framework shall be applicable both to UEs accessing the 5G CN using E-UTRA and to UEs accessing the 5G CN using NR. The unified access control framework shall be applicable to UEs in RRC Idle, RRC Inactive, and RRC Connected at the time of initiating a new access attempt (e.g. new session request). NOTE 1: "new session request" in RRC Connected refers to events, e.g. new MMTEL voice or video session, sending of SMS (SMS over IP, or SMS over NAS), sending of IMS registration related signalling, new PDU session establishment, existing PDU session modification, and service request to re-establish the user plane for an existing PDU session. The 5G system shall support means by which the operator can define operator-defined Access Categories to be mutually exclusive. NOTE 2: Examples of criterion of operator-defined Access Categories are network slicing, application, and application server. The unified access control framework shall be applicable to inbound roamers to a PLMN. The serving PLMN should be able to provide the definition of operator-defined Access Categories to the UE. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.22.2 |
2,737 | 4.15.9 Time Synchronization exposure 4.15.9.1 General | Time synchronization exposure allows an AF to configure time synchronization in 5GS. For (g)PTP operation, the Time synchronization service allows an AF to subscribe to the UE and 5GC capabilities and availability for time synchronization service (as described in clause 4.15.9.2), to configure the (g)PTP instance in 5GS as described in clause 4.15.9.3 and monitor service status as described in clause 4.15.9.5. For 5G access stratum based time distribution, the AF can influence the 5G access stratum time distribution as described in clause 4.15.9.4 and monitor service status as described in clause 4.15.9.5. The time synchronization exposure is provided by NEF that uses the service provided by TSCTSF. The AF that is part of operator's trust domain may invoke the services directly with TSCTSF and TSCTSF responds/notifies directly to the AF, accordingly. NOTE: The AF can use either the procedure for configuring the (g)PTP instance in 5GS as described in clause 4.15.9.3 or the procedure for controlling the 5G access stratum time distribution as described in clause 4.15.9.4 for a particular UE. The procedures are not intended to be used in conjunction with each other by the AF. However, the (g)PTP instance activation, modification and deactivation can influence the 5G AS time distribution for the UEs that are part of the impacted PTP instance. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.9 |
2,738 | 9.3.5.1.1 FDD | For the parameters specified in Table 9.3.5.1.1-1, and using the downlink physical channels specified in Annex C, the minimum requirements are specified in Table 9.3.5.1.1-2 and by the following a) the ratio of the throughput obtained when transmitting the transport format indicated by each reported wideband CQI index subject to an interference source with specified DIP and that obtained when transmitting the transport format indicated by each reported wideband CQI index subject to a white Gaussian noise source shall be ≥ ; b) when transmitting the transport format indicated by each reported wideband CQI index subject to an interference source with specified DIP, the average BLER for the indicated transport formats shall be greater than or equal to 2%. Table 9.3.5.1.1-1 Fading test for single antenna (FDD) Table 9.3.5.1.1-2 Minimum requirement (FDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.3.5.1.1 |
2,739 | 5.3.4.3 Reception of the SecurityModeCommand by the UE | The UE shall: 1> derive the KgNB key, as specified in TS 33.501[ Security architecture and procedures for 5G System ] [11]; 1> derive the KRRCint key associated with the integrityProtAlgorithm indicated in the SecurityModeCommand message, as specified in TS 33.501[ Security architecture and procedures for 5G System ] [11]; 1> request lower layers to verify the integrity protection of the SecurityModeCommand message, using the algorithm indicated by the integrityProtAlgorithm as included in the SecurityModeCommand message and the KRRCint key; 1> if the SecurityModeCommand message passes the integrity protection check: 2> derive the KRRCenc key and the KUPenc key associated with the cipheringAlgorithm indicated in the SecurityModeCommand message, as specified in TS 33.501[ Security architecture and procedures for 5G System ] [11]; 2> derive the KUPint key associated with the integrityProtAlgorithm indicated in the SecurityModeCommand message, as specified in TS 33.501[ Security architecture and procedures for 5G System ] [11]; 2> configure lower layers to apply SRB integrity protection using the indicated algorithm and the KRRCint key immediately, i.e. integrity protection shall be applied to all subsequent messages received and sent by the UE, including the SecurityModeComplete message; 2> configure lower layers to apply SRB ciphering using the indicated algorithm, the KRRCenc keyafter completing the procedure, i.e. ciphering shall be applied to all subsequent messages received and sent by the UE, except for the SecurityModeComplete message which is sent unciphered; 2> consider AS security to be activated; 2> submit the SecurityModeComplete message to lower layers for transmission, upon which the procedure ends; 1> else: 2> continue using the configuration used prior to the reception of the SecurityModeCommand message, i.e. neither apply integrity protection nor ciphering. 2> submit the SecurityModeFailure message to lower layers for transmission, upon which the procedure ends. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.4.3 |
2,740 | 5.7.4.3a Setting the contents of OverheatingAssistance IE | The UE shall set the contents of OverheatingAssistance IE if initiated to provide overheating assistance indication for SCG in (NG)EN-DC according to clause 5.6.10.3 as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10]: 1> if the UE prefers to temporarily reduce the number of maximum secondary component carriers for SCG: 2> include reducedMaxCCs in the OverheatingAssistance IE; 2> set reducedCCsDL to the number of maximum SCells of the SCG the UE prefers to be temporarily configured in downlink; 2> set reducedCCsUL to the number of maximum SCells of the SCG the UE prefers to be temporarily configured in uplink; 1> if the UE prefers to temporarily reduce maximum aggregated bandwidth of FR1 for SCG: 2> include reducedMaxBW-FR1 in the OverheatingAssistance IE; 2> set reducedBW-FR1-DL to the maximum aggregated bandwidth the UE prefers to be temporarily configured across all downlink carriers of FR1 of the SCG; 2> set reducedBW-FR1-UL to the maximum aggregated bandwidth the UE prefers to be temporarily configured across all uplink carriers of FR1 of the SCG; 1> if the UE prefers to temporarily reduce maximum aggregated bandwidth of FR2-1 for SCG: 2> include reducedMaxBW-FR2 in the OverheatingAssistance IE; 2> set reducedBW-FR2-DL to the maximum aggregated bandwidth the UE prefers to be temporarily configured across all downlink carriers of FR2-1 of the SCG; 2> set reducedBW-FR2-UL to the maximum aggregated bandwidth the UE prefers to be temporarily configured across all uplink carriers of FR2-1 of the SCG; 1> if the UE prefers to temporarily reduce maximum aggregated bandwidth of FR2-2 for SCG: 2> include reducedMaxBW-FR2-2 in the OverheatingAssistance IE; 2> set reducedBW-FR2-2-DL to the maximum aggregated bandwidth the UE prefers to be temporarily configured across all downlink carriers of FR2-2 of the SCG; 2> set reducedBW-FR2-2-UL to the maximum aggregated bandwidth the UE prefers to be temporarily configured across all uplink carriers of FR2-2 of the SCG; 1> if the UE prefers to temporarily reduce the number of maximum MIMO layers of each serving cell operating on FR1 for SCG: 2> include reducedMaxMIMO-LayersFR1 in the OverheatingAssistance IE; 2> set reducedMIMO-LayersFR1-DL to the number of maximum MIMO layers of each serving cell operating on FR1 of the SCG the UE prefers to be temporarily configured in downlink; 2> set reducedMIMO-LayersFR1-UL to the number of maximum MIMO layers of each serving cell operating on FR1 of the SCG the UE prefers to be temporarily configured in uplink; 1> if the UE prefers to temporarily reduce the number of maximum MIMO layers of each serving cell operating on FR2-1 for SCG: 2> include reducedMaxMIMO-LayersFR2 in the OverheatingAssistance IE; 2> set reducedMIMO-LayersFR2-DL to the number of maximum MIMO layers of each serving cell operating on FR2-1 of the SCG the UE prefers to be temporarily configured in downlink; 2> set reducedMIMO-LayersFR2-UL to the number of maximum MIMO layers of each serving cell operating on FR2-1 of the SCG the UE prefers to be temporarily configured in uplink; 1> if the UE prefers to temporarily reduce the number of maximum MIMO layers of each serving cell operating on FR2-2 for SCG: 2> include reducedMaxMIMO-LayersFR2-2 in the OverheatingAssistance IE; 2> set reducedMIMO-LayersFR2-2-DL to the number of maximum MIMO layers of each serving cell operating on FR2-2 of the SCG the UE prefers to be temporarily configured in downlink; 2> set reducedMIMO-LayersFR2-2-UL to the number of maximum MIMO layers of each serving cell operating on FR2-2 of the SCG the UE prefers to be temporarily configured in uplink; | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.7.4.3a |
2,741 | 10.3.2 Transaction identifier | Bits 5 to 8 of the first octet of every message belonging to the protocols "Call Control; call related SS messages" and "Session Management"contain the transaction identifier (TI). The transaction identifier and its use are defined in 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [20]. For the session management protocol, the extended TI mechanism may be used (see 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [20]). For the call control protocol, the extended TI mechanism shall be supported for the purpose of protocol error handling as specified in subclause 8.3.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 | 10.3.2 |
2,742 | 8.3.10.7 Header compression configuration | This IE is included in the message if: a) the UE wishes to re-negotiate header compression configuration associated to an EPS bearer context and both the UE and the network supports Control plane CIoT EPS optimization and header compression; or b) to negotiate header compression configuration associated to an EPS bearer context after an inter-system change from N1 mode to S1 mode when both the UE and the network support control plane CIoT EPS optimization and header compression, and the UE is operating in single-registration mode and has received the interworking without N26 interface indicator set to "interworking without N26 interface not supported" from the network. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 8.3.10.7 |
2,743 | 4.3.2.11.1 PDN connection with integrity protection | At PS to CS domain change from Iu mode to Iu mode due to SRVCC handover of a PDN connection for which integrity protection has been activated, ciphering and integrity may be started (see 3GPP TS 25.331[ None ] [23c]) without any new authentication procedure. Deduction of the appropriate security keys for ciphering and integrity check in Iu mode, depends on the current GSM or UMTS security context for the PS domain stored in the MS and the network. The ME shall handle the UMTS ciphering key and the UMTS integrity key according to table 4.3.2.11.1. Table 4.3.2.11.1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : SRVCC handover from Iu mode to Iu mode NOTE 1: For the case of an established UMTS security context for the PS domain, because of deriving a new UMTS security context for the CS domain, a new GSM ciphering key needs to be derived from the new derived UMTS security keys (i.e. CK' and IK'). Note that the new GSM ciphering key is also part of the new UMTS security context for the CS domain, and therefore any old GSM ciphering key stored in the USIM and in the ME belongs to an old UMTS security context for the CS domain and can no longer be taken into use. The network shall replace an already established GSM or UMTS security context for the CS domain, if any, when the SRVCC handover from Iu mode to Iu mode has been completed successfully. If the SRVCC handover from Iu mode to Iu mode has not been completed successfully, the MS and the network shall delete the new derived GSM or UMTS security context for the CS domain. Additionally, the network shall delete the already established GSM or UMTS security context for the CS domain, if the CKSN of the already established GSM or UMTS security context is equal to the CKSN of the new derived GSM or UMTS security context for the CS domain. | 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.11.1 |
2,744 | 15.5.2.2.2 Connection failure due to intra-system mobility | One of the functions of Mobility Robustness Optimization is to detect connection failures that occur due to Too Early or Too Late Handovers, or Handover to Wrong Cell. These problems are defined as follows: - Intra-system Too Late Handover: an RLF occurs after the UE has stayed for a long period of time in the cell; the UE attempts to re-establish the radio link connection in a different cell. - Intra-system Too Early Handover: an RLF occurs shortly after a successful handover from a source cell to a target cell or a handover failure occurs during the handover procedure; the UE attempts to re-establish the radio link connection in the source cell. - Intra-system Handover to Wrong Cell: an RLF occurs shortly after a successful handover from a source cell to a target cell or a handover failure occurs during the handover procedure; the UE attempts to re-establish the radio link connection in a cell other than the source cell and the target cell. In the definition above, the "successful handover" refers to the UE state, namely the successful completion of the RA procedure. In case of CHO, the Too Late Handover, Too Early Handover and Handover to Wrong Cell in the definition above means Too Late CHO Execution, Too Early CHO Execution and CHO Execution to Wrong Cell. Detection mechanism A failure indication may be initiated after a UE attempts to re-establish the radio link connection at NG-RAN node B after a failure at NG-RAN node A. NG-RAN node B may initiate the Failure Indication procedure towards multiple NG-RAN nodes if they control cells which use the PCI signalled by the UE during the re-establishment procedure. The NG-RAN node receiving this selects the UE context that matches the received Failure Cell ID and C-RNTI, and, if available, uses the shortMAC-I to confirm this identification, by calculating the shortMAC-I and comparing it to the received IE. A failure indication may also be sent to the node last serving the UE when the NG-RAN node fetches the RLF REPORT from UE by triggering: - The Failure Indication procedure over Xn; - The Uplink RAN configuration transfer procedure and Downlink RAN configuration transfer procedure over NG. The detailed detection mechanisms for too late handover, too early handover and handover to wrong cell are carried out through the following in the NG-RAN node that served the UE before the reported connection failure: - Intra-system Too Late Handover: there is no recent handover for the UE prior to the connection failure e.g. the UE reported timer is absent or larger than the configured threshold (e.g. Tstore_UE_cntxt), or if CHO is configured but the CHO execution is not initiated for the UE prior to the connection failure, e.g. the UE reported timer is absent or larger than the configured threshold (e.g. Tstore_UE_cntxt). - Intra-system Too Early Handover: there is a recent handover for the UE prior to the connection failure e.g. the UE reported timer is smaller than the configured threshold (e.g. Tstore_UE_cntxt), and the first re-establishment attempt cell/the successful re-connect cell is the cell that served the UE at the last handover initialisation or fall back to the source cell configuration in case of DAPS HO. - Intra-system Handover to Wrong Cell: there is a recent handover for the UE prior to the connection failure e.g. the UE reported timer is smaller than the configured threshold (e.g. Tstore_UE_cntxt), and the first re-establishment attempt cell/ the cell UE attempts to re-connect/the cell UE attempts CHO recovery is neither the cell that served the UE at the last handover initialisation nor the cell that served the UE where the RLF happened or the cell that the handover was initialized toward. The "UE reported timer" above indicates the time elapsed since the last handover initialisation until connection failure or the time elapsed since the CHO execution until connection failure. In case of Too Early Handover or Handover to Wrong Cell, the NG-RAN node receiving the failure indication may inform the NG-RAN node controlling the cell where the mobility configuration caused the failure by means of the Handover Report procedure over Xn or the Uplink RAN Configuration Transfer procedure over NG. This may include the RLF report. For MRO analysis, a gNB may take into account the information regarding the LBT failures occurred during the handover execution for a specific UE, as detected by the UE for UL, and by the target gNB for DL. Retrieval of information needed for problem analysis In order to retrieve relevant information collected at the network side as part of the UE context, the UE provides C-RNTI used in the last serving cell. If the cause for the failure is identified as a "Too Early HO" or a "HO to Wrong Cell", the NG-RAN node controlling the last serving cell shall, include in the HANDOVER REPORT message the C-RNTI used in the source cell of the last completed handover before the failure. If the NG RAN node controlling that source cell provided the Mobility Information, it is also included in the HANDOVER REPORT message. If used, the Mobility Information is prepared at the source NG RAN node of a handover and may refer to or identify any handover-related data at this NG RAN node. In the Handover Preparation procedure, the source gNB can request the target gNB to provide information on DL LBT failures at the target gNB during handover execution. Handling multiple reports from a single failure event In case the RRC re-establishment fails and the RRC connection setup succeeds, MRO evaluation of intra-RAT mobility connection failures may be triggered twice for the same failure event. In this case, only one failure event should be counted. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 15.5.2.2.2 |
2,745 | 4.1.3.3.1 Main States | 4.1.3.3.1.1 GMM-DEREGISTERED The network has no GMM context or the GMM context is marked as detached, the MS is detached. In this state, the network may answer to a GPRS attach or combined GPRS attach procedure initiated by the MS. 4.1.3.3.1.2 GMM-COMMON-PROCEDURE-INITIATED A common GMM procedure, as defined in subclause 4.1.1, has been started. The network is awaiting the answer from the MS. 4.1.3.3.1.3 GMM-REGISTERED The GMM context has been established and the GPRS attach procedure has been successfully performed. 4.1.3.3.1.4 GMM-DEREGISTERED-INITIATED The network has started a GPRS detach procedure and is awaiting the answer from the MS. Figure 4.1c/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : GMM main states on the network side | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.1.3.3.1 |
2,746 | 10.5.6.4 Packet data protocol address | The purpose of the packet data protocol address information element is to identify an address associated with a PDP. The packet data protocol address is a type 4 information element with minimum length of 4 octets and a maximum length of 24 octets. The packet data protocol address information element is coded as shown in figure 10.5.137/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.155/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.137/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Packet data protocol address information element Table 10.5.155/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Packet data protocol address information element If PDP type number indicates IPv4, the Address information in octet 5 to octet 8 contains the IPv4 address. Bit 8 of octet 5 represents the most significant bit of the IP address and bit 1 of octet 8 the least significant bit. If PDP type number indicates IPv6, the Address information in octet 5 to octet 20 contains the IPv6 address. Bit 8 of octet 5 represents the most significant bit of the IP address and bit 1 of octet 20 the least significant bit. If PDP type number indicates IPv4v6: The Address information in octet 5 to octet 8 contains the IPv4 address. Bit 8 of octet 5 represents the most significant bit of the IP address and bit 1 of octet 8 the least significant bit. The Address information in octet 9 to octet 24 contains the IPv6 address. Bit 8 of octet 9 represents the most significant bit of the IP address and bit 1 of octet 24 the least significant bit. If PDP type number indicates IPv4 or IPv4v6 and DHCPv4 is to be used to allocate the IPv4 address, the IPv4 address shall be coded as 0.0.0.0. | 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.4 |
2,747 | 6.3.5 AMF discovery and selection | The AMF discovery and selection functionality is applicable to both 3GPP access and non-3GPP access. The AMF selection functionality can be supported by the 5G-AN (e.g. RAN, N3IWF) and is used to select an AMF instance for a given UE. An AMF supports the AMF selection functionality to select an AMF for relocation or because the initially selected AMF was not an appropriate AMF to serve the UE (e.g. due to change of Allowed NSSAI). Other CP NF(s), e.g. SMF, supports the AMF selection functionality to select an AMF from the AMF set when the original AMF serving a UE is unavailable. The TSCTSF shall use the AMF discovery functionality to determine the AMFs serving the TAs in the spatial validity condition provided by the AF. 5G-AN selects an AMF Set and an AMF from the AMF Set under the following circumstances: 1) When the UE provides no 5G-S-TMSI nor the GUAMI to the 5G-AN. 2) When the UE provides 5G-S-TMSI or GUAMI but the routing information (i.e. AMF identified based on AMF Set ID, AMF pointer) present in the 5G-S-TMSI or GUAMI is not sufficient and/or not usable (e.g. UE provides GUAMI with an AMF region ID from a different region). 3) AMF has instructed AN that the AMF (identified by GUAMI(s)) is unavailable and no target AMF is identified and/or AN has detected that the AMF has failed. 4) When the UE attempts to establish a signalling connection, and the following conditions are met: - the 5G-AN knows in what country the UE is located; and - the 5G-AN is connected to AMFs serving different PLMNs of different countries; and - the UE provides a 5G-S-TMSI or GUAMI, which indicates an AMF serving a different country to where the UE is currently located; and - the 5G-AN is configured to enforce selection of the AMF based on the country the UE is currently located. Then the 5G-AN shall select an AMF serving a PLMN corresponding to the UE's current location. How 5G-AN selects the AMF in this case is defined in TS 38.410[ NG-RAN; NG general aspects and principles ] [125]. NOTE: AMF selection case 4) does not apply if 5G-AN nodes serves one country only. In the case of NF Service Consumer based discovery and selection, the CP NF selects an AMF from the AMF Set under the following circumstances: - When the AMF has instructed CP NF that a certain AMF identified by GUAMI(s) is unavailable and the CP NF was not notified of target AMF; and/or - CP NF has detected that the AMF has failed; and/or - When the selected AMF does not support the UE's Preferred Network Behaviour; and/or - When the selected AMF does not support the High Latency communication for NR RedCap UE. In the case of delegated discovery and associated selection, the SCP selects an AMF from the corresponding AMF Set under the following circumstances: - The SCP gets an indication "select new AMF within SET" from the CP NF; and/or - SCP has detected that the AMF has failed. The AMF selection functionality in the 5G-AN may consider the following factors for selecting the AMF Set: - AMF Region ID and AMF Set ID derived from GUAMI; - Requested NSSAI; - Local operator policies; - 5G CIoT features indicated in RRC signalling by the UE; - IAB-indication; - NB-IoT RAT Type; - Category M Indication; - NR RedCap Indication; - SNPN Onboarding indication as indicated in 5G-AN signalling by the UE. AMF selection functionality in the 5G-AN or CP NFs or SCP considers the following factors for selecting an AMF from AMF Set: - Availability of candidate AMF(s). - Load balancing across candidate AMF(s) (e.g. considering weight factors of candidate AMFs in the AMF Set). - In 5G-AN, 5G CIoT features indicated in RRC signalling by the UE. - In 5G-AN, SNPN Onboarding indication as indicated in 5G-AN signalling by the UE. When the UE accesses the 5G-AN with a 5G-S-TMSI or GUAMI that identifies more than one AMF (as configured during N2 setup procedure), the 5G-AN selects the AMF considering the weight factors. When 5G-S-TMSI or GUAMI provided by the UE to the 5G-AN contains an AMF Set ID that is usable, and the AMF identified by AMF pointer that is not usable (e.g. AN detects that the AMF has failed) or the corresponding AMF indicates it is unavailable (e.g. out of operation) then the 5G-AN uses the AMF Set ID for selecting another AMF from the AMF set considering the factors above. The discovery and selection of AMF in the CP NFs or SCP follows the principle in clause 6.3.1 In the case of NF Service Consumer based discovery and selection, the AMF or other CP NFs shall utilize the NRF to discover the AMF instance(s) unless AMF information is available by other means, e.g. locally configured on AMF or other CP NFs. The NRF provides the NF profile(s) of AMF instance(s) to the AMF or other CP NFs. The AMF selection function in the AMF or other CP NFs selects an AMF instance as described below: When NF Service Consumer performs discovery and selection the following applies: - In the case of AMF discovery and selection functionality in AMF or other CP NFs use GUAMI (in the SNPN case, along with NID of the SNPN that owns the AMF instances to be discovered and selected) or TAI to discover the AMF instance(s), the NRF provides the NF profile of the associated AMF instance(s). If an associated AMF is unavailable due to AMF planned removal, the NF profile of the backup AMF used for planned removal is provided by the NRF. If an associated AMF is unavailable due to AMF failure, the NF profile of the backup AMF used for failure is provided by the NRF. If AMF pointer value in the GUAMI is associated with more than one AMF, the NRF provides all the AMFs associated with this AMF pointer value. If no AMF instances related to the indicated GUAMI can be found, the NRF may provide a list of NF profiles of candidate AMF instances in the same AMF Set. The other CP NF or AMF may select any AMF instance from the list of candidate AMF instances. If no NF profiles of AMF is returned in the discovery result, the other CP NF or AMF may discover an AMF using the AMF Set as below. - In the case of AMF discovery and selection functionality in AMF use AMF Set to discover AMF instance(s), the NRF provides a list of NF profiles of AMF instances in the same AMF Set. - At intra-PLMN mobility, the AMF discovery and selection functionality in AMF may use AMF Set ID, AMF Region ID, the target location information, S-NSSAI(s) of Allowed NSSAI to discover target AMF instance(s). The NRF provides the target NF profiles matching the discovery. - At intra-SNPN mobility, the AMF discovery and selection functionality in AMF may use AMF Set ID, AMF Region ID (along with NID of the SNPN that owns the AMF instances to be discovered and selected), the target location information, S-NSSAI(s) of Allowed NSSAI, AMF support of SNPN Onboarding (if the UE is registered for SNPN Onboarding) to discover target AMF instance(s). The NRF provides the target NF profiles matching the discovery. - At inter PLMN mobility, the source AMF selects an AMF instance(s) in the target PLMN by querying target PLMN level NRF via the source PLMN level NRF with target PLMN ID. The target PLMN level NRF returns an AMF instance address based on the target operator configuration. After the Handover procedure the AMF may select a different AMF instance as specified in clause 4.2.2.2.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. In the context of Network Slicing, the AMF selection is described in clause 5.15.5.2.1. When delegated discovery and associated selection is used, the following applies: - If the CP NF includes GUAMI or TAI in the request, the SCP selects an AMF instance associated with the GUAMI or TAI and sends the request to a selected AMF service instance if it is available. The following also applies: - If none of the associated AMF service instances are available due to AMF planned removal, an AMF service instance from the backup AMF used for planned removal is selected by the SCP; - If none of the associated AMF service instances are available due to AMF failure, an AMF service instance from the backup AMF used for failure is selected by the SCP; - If no AMF service instances related to the indicated GUAMI (in the SNPN case, along with NID of the SNPN that owns the AMF instances to be discovered and selected) can be found the SCP selects an AMF instance from the AMF Set; or - AMF Pointer value used by more than one AMF, SCP selects one of the AMF instances associated with the AMF Pointer. - If the CP NF includes AMF Set ID in the request, the SCP selects AMF/AMF service instances in the provided AMF Set. - At intra-PLMN mobility, if a target AMF instance needs to be selected, the AMF may provide AMF Set ID, AMF Region ID, and the target location information, S-NSSAI(s) of Allowed NSSAI in the request, optionally NRF to use. The SCP will select a target AMF instance matching the discovery. - At intra-SNPN mobility, if a target AMF instance needs to be selected, the AMF may provide AMF Set ID, AMF Region ID along with NID of the SNPN that owns the AMF instances to be discovered and selected, and the target location information, S-NSSAI(s) of Allowed NSSAI, AMF support of SNPN Onboarding in the request (if the UE is registered for SNPN Onboarding), optionally NRF to use. The SCP will select a target AMF instance matching the discovery. - At inter PLMN mobility, the source AMF selects indicates "roaming" to the SCP. The SCP interacts with the NRF in source PLMN so that the NRF in source PLMN can discover an AMF in the target PLMN via target PLMN NRF. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.3.5 |
2,748 | 6.44.2.1 Welcome SMS | The 5G system shall be able to support mechanisms for the HPLMN to provide a notification, including equipment and subscription identifiers, to a trusted application server when a UE successfully registers in a VPLMN. In response to the notification, the trusted application server can indicate specific actions to the HPLMN (e.g., send an SMS to the UE). NOTE: The trusted application server can be hosted by the home operator or a trusted 3rd party and is out of 3GPP scope. 6.44.2.2 Steering of Roaming (SoR) during the registration procedure The 5G system shall be able to support mechanisms enabling the HPLMN to: - provide a notification, including subscription and equipment identifiers, to a trusted application server when a UE tries to register in a VPLMN. - receive a notification reply from the trusted application server indicating specific actions to the HPLMN, e.g., reject UE registration (with a specific cause), trigger a SoR command. NOTE: The trusted application server can be hosted by the home operator or a trusted 3rd party and is out of 3GPP scope. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.44.2.1 |
2,749 | 5.8.9.10.4 Actions related to reception of NotificationMessageSidelink message | Upon receiving the NotificationMessageSidelink, the Remote UE shall: 1> if the UE is acting as U2N Remote UE: 2> if the indicationType is included: 3> if the UE is L2 U2N Remote UE in RRC_CONNECTED: 4> if MP is configured and MCG transmission (i.e. direct path) is not suspended; 5> initiate the indirect path failure information procedure as specified in 5. 7. 3c to report indirect path failure; 4> else if T301 is not running, initiate the RRC connection re-establishment procedure as specified in 5.3.7; 3> else (the UE is L3 U2N Remote UE, or L2 U2N Remote UE in RRC_IDLE or RRC_INACTIVE): 4> if the PC5-RRC connection with the U2N Relay UE is determined to be released: 5> indicate upper layers to trigger PC5 unicast link release; 4> else (i.e., maintain the PC5 RRC connection): 5> if the UE is L2 U2N Remote UE and the indicationType is relayUE-HO or relayUE-CellReselection: 6> consider cell re-selection occurs; NOTE 1: For L3 U2N Remote UE, or L2 U2N Remote UE in RRC_IDLE or RRC_INACTIVE, it is up to Remote UE implementation whether to release or keep the PC5 unicast link. NOTE 2: The L2 U2N Remote UE may ignore the NotificationMessageSidelink if it does not release the PC5 unicast link in source side yet during an indirect-to-direct path switch, i.e. T304 is running. 1> if the UE is acting as L2 U2U Remote UE: 2> if sl-IndicationType is relayUE-PC5-RLF: 3> indicate PC5 RLF received from L2 U2U Relay UE to the upper layers for the indicated L2 U2U Remote UE based on the received sl-DestinationIdentityRemoteUE; 3> perform PC5 RLF related actions as specified in 5.8.9.3, for the indicated L2 U2U Remote UE based on the received sl-DestinationIdentityRemoteUE; NOTE 3: It is up to the upper layers on whether to trigger U2U Relay reselection and whether to keep or release the PC5 link with the U2U Relay UE after the PC5 RLF indication received from U2U Relay UE. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.9.10.4 |
2,750 | 13.2.1 Address allocation by the Intranet or ISP | The MS is given an address belonging to the Intranet/ISP addressing space. The address is given dynamically immediately after the PDP context activation. This address is used for packet forwarding between the Intranet/ISP and the GGSN and within the GGSN. The MS may authenticate itself to the Intranet/ISP by means of the relevant DHCP procedures (see RFC 3118 [45]). The protocol configuration options are retrieved from the DHCP server belonging to the Intranet/ISP. Figure 16c: Protocol stack for access with DHCP end-to-end | 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 | 13.2.1 |
2,751 | 5.2.2.2.16 Namf_Communication_AMFStatusChangeNotify service operation | Service operation name: Namf_Communication_AMFStatusChangeNotify Description: Report AMF Status change (e.g. AMF unavailable) notification to subscribed NFs. Input, Required: GUAMI(s). Input, Optional: Target AMF(s) Name associated with the indicated GUAMI. Output, Required: None. Output, Optional: None. See clause 5.21.2.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] for the example usage of this service operation. The GUAMI(s) is used to identify the AMF. For network deployment without UDSF case, the target AMF Name which is to serve the user of the indicated GUAMI is also included. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.2.2.16 |
2,752 | 10.2.6B.2 Mapping to resource elements | The same antenna port shall be used for all symbols of the NWUS within a subframe. The UE shall not assume that the NWUS is transmitted on the same antenna port as any of the downlink reference signals or synchronization signals. If only one NRS port is configured by the eNB, the UE may assume the transmission of all NWUS subframes is using the same antenna port; otherwise, the UE may assume the same antenna port is used for NWUS transmission in DL subframes w0+2n and w0+2n+1, where w0 is the first DL subframe of the NWUS transmission as specified in [4], and n=0,1,…. The NWUS sequence is mapped to the set of subframes in the actual NWUS duration as defined in [4], where in a subframe #4 in which SystemInformationBlockType1-NB is transmitted or a subframe in which an SI message is transmitted, the subframe is counted in the NWUS mapping but not used for transmission of NWUS.On an NB-IoT carrier for which a UE receives higher-layer parameter operationModeInfo indicating inband-SamePCI, inband-DifferentPCI, guardband or standalone or on an NB-IoT carrier for which DL-CarrierConfigCommon-NB is present, the NWUS sequence shall be mapped to resource elements in sequence, starting with in increasing order of first the index over the 12 assigned subcarriers and then the index in each subframe in which NWUS is transmitted. Additionally, on an NB-IoT carrier for which a UE receives higher-layer parameter operationModeInfo indicating guardband or standalone, or on an NB-IoT carrier for which DL-CarrierConfigCommon-NB is present and no inbandCarrierInfo is present, the resource mapping for the first three OFDM symbols in the subframe is performed as follows: - The resource element (k,7) is mapped to resource element (k,0) of every index k over 12 assigned subcarriers - The resource element (k,8) is mapped to resource element (k,1) of every index k over 12 assigned subcarriers - The resource element (k,9) is mapped to resource element (k,2) of every index k over 12 assigned subcarriers A resource element overlapping with resource elements where cell-specific reference signals according to clause 6.10 are transmitted or NRSs according to clause 10.2.6 are transmitted shall not be used for NWUS transmission but is counted in the mapping process. | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 10.2.6B.2 |
2,753 | 6.5.2G.1 Error Vector Magnitude | For V2X physical channels PSCCH, PSSCH and PSBCH, the Error Vector Magnitude requirements shall be as specified for PUSCH in subclause 6.5.2.1 for the corresponding modulation and transmission bandwidth. For V2X sidelink physical channels PSCCH, PSSCH and PSBCH, the Error Vector Magnitude requirements shall be as specified separately for PSSCH and PSCCH for the corresponding modulation and transmission bandwidth. The measurement period for EVM of PSSCH and PSCCH is 15 subframes. The measurement period for reference signal EVM is 30 subframes. When V2X transmissions are shortened due to transmission gap of 1 symbol at the end of the subframe, the EVM measurement interval is reduced by one symbol, accordingly. For PSBCH the duration over which EVM is averaged shall be 24 subframes. For intra-band contiguous multi-carrier operation the EVM requirement shall apply for each component carrier. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.5.2G.1 |
2,754 | 9.1 Structure of APN | The APN is composed of two parts as follows: - The APN Network Identifier; this defines to which external network the GGSN/PGW is connected and optionally a requested service by the MS. This part of the APN is mandatory. - The APN Operator Identifier; this defines in which PLMN GPRS/EPS backbone the GGSN/PGW is located. This part of the APN is optional. NOTE 1: The APN Operator Identifier is mandatory on certain interfaces, see the relevant stage 3 specifications. The APN Operator Identifier is placed after the APN Network Identifier. An APN consisting of both the Network Identifier and Operator Identifier corresponds to a DNS name of a GGSN/PGW; the APN has, after encoding as defined in the paragraph below, a maximum length of 100 octets. The encoding of the APN shall follow the Name Syntax defined in RFC 2181 [18], RFC 1035 [19] and RFC 1123 [20]. The APN consists of one or more labels. Each label is coded as a one octet length field followed by that number of octets coded as 8 bit ASCII characters. Following RFC 1035 [19] the labels shall consist only of the alphabetic characters (A-Z and a-z), digits (0-9) and the hyphen (-). Following RFC 1123 [20], the label shall begin and end with either an alphabetic character or a digit. The case of alphabetic characters is not significant. The APN is not terminated by a length byte of zero. NOTE 2: A length byte of zero is added by the SGSN/MME at the end of the APN before interrogating a DNS server. For the purpose of presentation, an APN is usually displayed as a string in which the labels are separated by dots (e.g. "Label1.Label2.Label3"). | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 9.1 |
2,755 | 5.3.7 Handling of the periodic registration update timer and mobile reachable timer | The periodic registration update procedure is used over 3GPP access to periodically notify the availability of the UE to the network. The procedure is controlled in the UE by the periodic registration update timer, T3512. If the UE is registered over the 3GPP access, the AMF maintains an implicit de-registration timer to control when the UE is considered implicitly de-registered over the 3GPP access. If the UE is registered over the non-3GPP access, the AMF also maintains a non-3GPP implicit de-registration timer to control when the UE is considered implicitly de-registered over the non-3GPP access. The UE registered over the non-3GPP access maintains a non-3GPP de-registration timer to control when the UE is considered implicitly de-registered for the non-3GPP access. The AMF shall start a non-3GPP implicit de-registration timer for the UE registered over non-3GPP access when the N1 NAS signalling connection over non-3GPP access is released. The UE registered over non-3GPP access shall reset and start a non-3GPP de-registration timer when the N1 NAS signalling connection over non-3GPP access is released. The non-3GPP de-registration timer is stopped when the UE enters 5GMM-CONNECTED mode over non-3GPP access or the 5GMM-DEREGISTERED state over non-3GPP access. The non-3GPP implicit de-registration timer shall be longer than the non-3GPP de-registration timer. The value of timer T3512 is sent by the network to the UE in the REGISTRATION ACCEPT message. The UE shall apply this value in all tracking areas of the list of tracking areas assigned to the UE until a new value is received. The periodic registration update timer only applies to the UE registered to the 5GS services over 3GPP access. If timer T3512 received by the UE in a REGISTRATION ACCEPT message contains an indication that the timer is deactivated or the timer value is zero, then timer T3512 is deactivated and the UE shall not perform the periodic registration update procedure. NOTE 1: The UE does not perform the periodic registration update procedure for non-3GPP access. If during the registration procedure, the AMF does not indicate "strictly periodic registration timer supported" in the MICO indication IE to the UE, timer T3512 is reset and started with its initial value, when the UE changes from 5GMM-CONNECTED over 3GPP access to 5GMM-IDLE mode over 3GPP access. Timer T3512 is stopped when the UE enters 5GMM-CONNECTED mode over 3GPP access or the 5GMM-DEREGISTERED state over 3GPP access. If during the registration procedure, the AMF indicates "strictly periodic registration timer supported" in the MICO indication IE to the UE, timer T3512 is started with its initial value after the completion of the registration procedure. The UE shall neither stop nor reset the timer T3512 when the UE enters 5GMM-CONNECTED or when changing from 5GMM-CONNECTED mode to 5GMM-IDLE mode. If the timer T3512 expires, a) the UE in 5GMM-CONNECTED mode over 3GPP access shall reset and start the timer T3512 with its initial value; or b) the UE in 5GMM-IDLE mode over 3GPP access shall perform the periodic registration procedure. If the UE is registered for emergency services, and timer T3512 expires, the UE shall not initiate a periodic registration update procedure, but shall locally de-register from the network. When the UE is camping on a suitable cell, it may re-register to regain normal service. When a UE is not registered for emergency services, and timer T3512 expires when the UE is in 5GMM-IDLE mode, the periodic registration update procedure shall be started. If the UE is not registered for emergency services, and is in a state other than 5GMM-REGISTERED.NORMAL-SERVICE or 5GMM-REGISTERED.NON-ALLOWED-SERVICE over 3GPP access when timer T3512 expires, the periodic registration update procedure is delayed until the UE returns to 5GMM-REGISTERED.NORMAL-SERVICE or 5GMM-REGISTERED.NON-ALLOWED-SERVICE over 3GPP access. NOTE 2: When the UE returns to 5GMM-REGISTERED.NORMAL-SERVICE or 5GMM-REGISTERED.NON-ALLOWED-SERVICE and it needs to initiate other 5GMM procedure than the periodic registration update procedure then, based on UE implementation, the 5GMM procedure can take precedence. The network supervises the periodic registration update procedure of the UE by means of the mobile reachable timer. If the UE is not registered for emergency services, the mobile reachable timer shall be longer than the value of timer T3512. In this case, by default, the mobile reachable timer is 4 minutes greater than the value of timer T3512. The network behaviour upon expiry of the mobile reachable timer is network dependent, but typically the network stops sending paging messages to the UE on the first expiry, and may take other appropriate actions. If the UE is registered for emergency services, the AMF shall set the mobile reachable timer with a value equal to timer T3512. When the mobile reachable timer expires, the AMF shall locally de-register the UE. The mobile reachable timer shall be reset and started with the value as indicated above, when the AMF releases the NAS signalling connection for the UE. The mobile reachable timer shall be stopped when a NAS signalling connection is established for the UE. Upon expiry of the mobile reachable timer the network shall start the implicit de-registration timer over 3GPP access. The value of the implicit de-registration timer over 3GPP access is network dependent. If MICO mode is activated, the network shall start the implicit de-registration timer over 3GPP access when the UE enters 5GMM-IDLE mode at the AMF over 3GPP access. The default value of the implicit de-registration timer over 3GPP access is 4 minutes greater than the value of timer T3512. If the implicit de-registration timer expires before the UE contacts the network, the network shall implicitly de-register the UE. The implicit de-registration timer shall be stopped when a NAS signalling connection is established for the UE. If the non-3GPP implicit de-registration timer expires before the UE contacts the network over the non-3GPP access, the network shall implicitly de-register the UE and enter the state 5GMM-DEREGISTERED over non-3GPP access for the UE. The non-3GPP implicit de-registration timer shall be stopped when a NAS signalling connection over non-3GPP access is established for the UE. If the non-3GPP de-registration timer expires before the UE contacts the network over the non-3GPP access, the UE shall enter the state 5GMM-DEREGISTERED over non-3GPP access. The non-3GPP de-registration timer shall be stopped when a NAS signalling connection over non-3GPP access is established for the UE. If the AMF provides T3346 value IE in the DEREGISTRATION REQUEST message with Access type set to "Non-3GPP access" in Deregistration type IE, REGISTRATION REJECT message during a registration procedure for mobility and periodic registration update or SERVICE REJECT message and the value of timer T3346 is greater than the value of timer T3512, the AMF sets the mobile reachable timer and the implicit de-registration timer such that the sum of the timer values is greater than the value of timer T3346. If the AMF provides T3346 value IE in the DEREGISTRATION REQUEST message with Access type set to "3GPP access" in Deregistration type IE, REGISTRATION REJECT message during a registration procedure for mobility and periodic registration update or SERVICE REJECT message and the value of timer T3346 is greater than the value of the non-3GPP de-registration timer, the AMF sets the non-3GPP implicit de-registration timer value to be 8 minutes greater than the value of timer T3346. If the UE receives T3346 value IE in the DEREGISTRATION REQUEST message with Access type set to "3GPP access" in Deregistration type IE, REGISTRATION REJECT message during a registration procedure for mobility and periodic registration update or SERVICE REJECT message and the value of timer T3346 is greater than the value of the non-3GPP de-registration timer, the UE sets the non-3GPP de-registration timer value to be 4 minutes greater than the value of timer T3346. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.3.7 |
2,756 | – UAC-BarringPerPLMN-List | The IE UAC-BarringPerPLMN-List provides access category specific access control parameters, which are configured per PLMN/SNPN. UAC-BarringPerPLMN-List information element -- ASN1START -- TAG-UAC-BARRINGPERPLMN-LIST-START UAC-BarringPerPLMN-List ::= SEQUENCE (SIZE (1.. maxPLMN)) OF UAC-BarringPerPLMN UAC-BarringPerPLMN ::= SEQUENCE { plmn-IdentityIndex INTEGER (1..maxPLMN), uac-ACBarringListType CHOICE{ uac-ImplicitACBarringList SEQUENCE (SIZE(maxAccessCat-1)) OF UAC-BarringInfoSetIndex, uac-ExplicitACBarringList UAC-BarringPerCatList } OPTIONAL -- Need S } -- TAG-UAC-BARRINGPERPLMN-LIST-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,757 | 4.5.1 DL PRB Usage for traffic | This measurement provides the usage (in percentage) of physical resource blocks (PRBs) on the downlink for DTCH traffic. The measurement is split into subcounters per E-RAB QoS level (QCI). If there is one or more RNs served in a cell, for that cell the eNodeB performs PRB usage measurements separately for all traffic (including transmissions to/from RNs and UEs directly connected to the eNodeB) and for RN traffic. The measurement is also applicable to RNs. SI This measurement is obtained according to the definition in 3GPP TS 36.314[ Evolved Universal Terrestrial Radio Access (E-UTRA); Layer 2 - Measurements ] [11]. Separate counters are maintained for each QCI. The sum of all supported per QCI measurements shall equal the total PRB usage for DTCH. In case only a subset of per QCI measurements is supported, a sum subcounter will be provided first. Each measurement is an integer value from 0 to 100. The number of measurements is equal to the number of QCIs plus a possible sum value identified by the .sum suffix. The measurement name has the form RRU.PrbDl.QCI, which indicats the DL PRB Usage for all traffic RRU.PrbDlRN.QCI, which indicates the DL PRB Usage for the RN traffic where QCI identifies the E-RAB level quality of service class. 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.1 |
2,758 | 10.5.5.31 Network resource identifier container | The purpose of the Network resource identifier container information element is to provide a part of the allocated TMSI that the network will use to determine the actual NRI. The Network resource identifier container is a type 4 information element with a length of 4 octets. The Network resource identifier container information element is coded as shown in figure 10.5.5.31/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.5.31/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.5.31/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Network resource identifier container information element Table 10.5.5.31/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Network resource identifier container information element | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.5.31 |
2,759 | – UE-TimersAndConstants | The IE UE-TimersAndConstants contains timers and constants used by the UE in RRC_CONNECTED, RRC_INACTIVE and RRC_IDLE. UE-TimersAndConstants information element -- ASN1START -- TAG-UE-TIMERSANDCONSTANTS-START UE-TimersAndConstants ::= SEQUENCE { t300 ENUMERATED {ms100, ms200, ms300, ms400, ms600, ms1000, ms1500, ms2000}, t301 ENUMERATED {ms100, ms200, ms300, ms400, ms600, ms1000, ms1500, ms2000}, t310 ENUMERATED {ms0, ms50, ms100, ms200, ms500, ms1000, ms2000}, n310 ENUMERATED {n1, n2, n3, n4, n6, n8, n10, n20}, t311 ENUMERATED {ms1000, ms3000, ms5000, ms10000, ms15000, ms20000, ms30000}, n311 ENUMERATED {n1, n2, n3, n4, n5, n6, n8, n10}, t319 ENUMERATED {ms100, ms200, ms300, ms400, ms600, ms1000, ms1500, ms2000}, ... } -- TAG-UE-TIMERSANDCONSTANTS-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,760 | 6.6.4.3 UP integrity mechanisms between the UE and the ng-eNB | If the UE supports E-UTRA connected to 5GC, the UE shall indicate support of integrity protection by setting the EIA7 algorithm bit in 5G UE Security Capability IE (see clause 9.11.3.54 of TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [35]) to indicate that the UE supports user plane integrity protection with an ng-eNB. If the 128-NIA algorithm is signalled by the ng-eNB to the UE, clause 6.6.4.2 applies. If the 128-EIA algorithm is signalled by the ng-eNB to the UE, the following applies: - The use and mode of operation of the 128-EIA algorithms are specified in Annex B of TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [10]. - The input parameters to the 128-bit EIA algorithms as described in Annex B of TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [10] are, the message packet, a 128-bit integrity key KUPint as KEY, a 5-bit bearer identity BEARER value of which is assigned as specified by TS 38.323[ NR; Packet Data Convergence Protocol (PDCP) specification ] [23], the 1-bit direction of transmission DIRECTION, and a bearer specific, time and direction dependent 32-bit input COUNT which corresponds to the 32-bit PDCP COUNT. NOTE: The ng-eNB decides whether to signal 128-NIA or 128-EIA algorithm (cf. clause 5.3.1.2 of TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [69]). If the ng-eNB or the UE receives a PDCP PDU which fails integrity check with faulty or missing MAC-I after the start of integrity protection, the PDU shall be discarded. UE and the ng-eNB (or the ng-eNB acting as the MN) shall derive UP integrity key as specified in Annex A.7 of TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [10], with the KeNB set to KgNB. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.6.4.3 |
2,761 | 9.11.3.97 Alternative NSSAI | The purpose of the Alternative NSSAI information element is to identify a list of mapping information between the S-NSSAI to be replaced and the alternative S-NSSAI. The Alternative NSSAI information element is coded as shown in figure 9.11.3.97.1, figure 9.11.3.97.2 and table 9.11.3.97.1. The Alternative NSSAI is a type 4 information element with minimum length of 2 octets and maximum length of 146 octets. Figure 9.11.3.97.1: Alternative NSSAI information element Figure 9.11.3.97.2: Entry Table 9.11.3.97.1: Alternative NSSAI 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.97 |
2,762 | – CounterCheckResponse | The CounterCheckResponse message is used by the UE to respond to a CounterCheck message. Signalling radio bearer: SRB1 RLC-SAP: AM Logical channel: DCCH Direction: UE to Network CounterCheckResponse message -- ASN1START -- TAG-COUNTERCHECKRESPONSE-START CounterCheckResponse ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { counterCheckResponse CounterCheckResponse-IEs, criticalExtensionsFuture SEQUENCE {} } } CounterCheckResponse-IEs ::= SEQUENCE { drb-CountInfoList DRB-CountInfoList, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } DRB-CountInfoList ::= SEQUENCE (SIZE (0..maxDRB)) OF DRB-CountInfo DRB-CountInfo ::= SEQUENCE { drb-Identity DRB-Identity, count-Uplink INTEGER(0..4294967295), count-Downlink INTEGER(0..4294967295) } -- TAG-COUNTERCHECKRESPONSE-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,763 | 4.7.2 5GS mobility management aspects 4.7.2.1 General | The mobility management procedures defined over 3GPP access are re-used over non-3GPP access with the following exceptions: a) the registration status, and the 5GMM parameters of the UE's 3GPP access and non-3GPP access 5GMM state machine instances are independent in each of these accesses and can be different; b) single-registration mode and dual-registration mode do not apply for 5GMM over non-3GPP access; c) the RPLMN over non-3GPP access can be different from the RPLMN over 3GPP access. The MCC of the RPLMN over 3GPP access and the MCC of the RPLMN over the non-3GPP access can also be different; d) the registration for 3GPP access and for non-3GPP access are performed separately. Like for 3GPP access, an access stratum connection exists before the UE can perform the registration procedure for non-3GPP access. As at registration over non-3GPP access the UE is allocated a registration area, which is associated with a single TAI, list management of registration areas is not required, and registration updating due to registration area change with the registered PLMN is not performed. Furthermore, the periodic registration update procedure is also not performed. New registration at change of PLMN is required; e) the 5GMM over non-3GPP access in the UE considers that the N1 NAS signalling connection is established when the lower layers indicate that the access stratum connection is established succcessfully; f) the UE-initiated service request procedure via non-3GPP access is supported. Upon indication from the lower layers of non-3GPP access, that the access stratum connection is established between the UE and the network, the UE in 5GMM-REGISTERED state and in 5GMM-IDLE mode over non-3GPP access shall initiate the service request procedure via non-3GPP access. The UE may indicate with the service request message the PDU session(s) associated with non-3GPP access to re-establish user-plane resources for which the UE has pending user data to be sent; g) paging procedure is not performed via non-3GPP access; h) service area restrictions do not apply for non-3GPP access other than the wireline access; i) the establishment cause for non-3GPP access is determined according to subclause 4.7.2.2; j) eCall inactivity procedure is not performed via non-3GPP access; k) local area data network (LADN) does not apply for non-3GPP access; l) the Allowed PDU session IE shall not be included in the REGISTRATION REQUEST message or the SERVICE REQUEST message sent over non-3GPP access; m) DRX parameters do not apply for non-3GPP access; n) Mobile initiated connection only mode (MICO) does not apply for non-3GPP access; o) CIoT 5GS optimizations do not apply for non-3GPP access; p) unified access control does not apply for non-3GPP access; q) UE radio capability signalling optimisation (RACS) does not apply for non-3GPP access; r) Closed access group (CAG) does not apply for non-3GPP access; s) the N1 NAS signalling connection release, the paging indication for voice services and reject the paging request do not apply for non-3GPP access. The Paging restriction IE shall not be included in the REGISTRATION REQUEST message, the SERVICE REQUEST message or the CONTROL PLANE SERVICE REQUEST message sent over non-3GPP access. The AMF shall not delete any stored paging restriction preferences for the UE and shall not stop restricting paging when receiving REGISTRATION REQUEST message, SERVICE REQUEST message or CONTROL PLANE SERVICE REQUEST message over non-3GPP access; t) the partially allowed NSSAI and the partially rejected NSSAI do not apply for non-3GPP access; and u) support for unavailability period (see subclause 5.3.26) does not apply for non-3GPP access. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.2 |
2,764 | 18.2 SDT with UE context relocation | The overall procedure for SDT procedure over RACH with UE context relocation is illustrated in the figure 18.2-1. Figure 18.2-1. RA-based SDT with UE context relocation 1. The UE sends an RRCResumeRequest as well as UL SDT data and/or UL SDT signalling to the Receiving gNB. 2. The Receiving gNB identifies the Last Serving gNB using the I-RNTI and retrieves the UE context by means of Xn-AP Retrieve UE Context procedure. The Receiving gNB indicates that the UE request is for an SDT and may also provide SDT assistance information (e.g., single packet, multiple packets). 3. The Last Serving gNB decides to relocate UE context and responds with the RETRIEVE UE CONTEXT RESPONSE message. The UL SDT data, if any, is delivered from the Receiving gNB to the UPF. 4-6. The Receiving gNB decides to keep UE in RRC_INACTIVE state for SDT. If loss of DL user data buffered in the Last Serving gNB shall be prevented, the Receiving gNB provides forwarding addresses via the Xn-U ADDRESS INDICATION message. The Receiving gNB also initiates NGAP Path Switch Request procedure to establish a NG UE-associated signalling connection to the AMF. After the Path Switch Request procedure, the buffered UL NAS PDU, if any, is delivered from the Receiving gNB to the AMF. And then, the subsequent UL/DL SDT data and/or signalling are transferred between UE and core network via the Receiving gNB. NOTE 1: If the UP policy received from the Last Serving gNB is different from that received in the PATH SWITCH REQUEST ACKNOWLEDGE message, the Receiving gNB may either send the UE back to RRC_IDLE or move the UE to RRC_CONNECTED to update the security configuration. 7. After the SDT transmission is terminated, the Receiving gNB generates and sends the RRCRelease message including the suspend indication to the UE to terminate the SDT procedure and continue in RRC_INACTIVE state. NOTE 2: In case DL non-SDT data or DL non-SDT signalling arrives, or the UE assistance information (i.e. UL non-SDT data arrival indication) is received from the UE, the Receiving gNB may decide to directly send the UE to RRC_CONNECTED state by sending the RRCResume message. NOTE 3: The Receiving gNB may decide to directly send the UE to RRC_CONNECTED state by sending the RRCResume message based on (e.g. large size of) DL SDT data or DL SDT signalling. NOTE 4: The Receiving gNB may decide to directly send the UE to RRC_CONNECTED state by sending the RRCResume message based on the BSR received from the UE in case of uplink SDT data exceeding the data size threshold. 8. The Receiving gNB indicates to the Last Serving gNB to remove the UE context by sending the XnAP UE CONTEXT RELEASE message. The XnAP UE CONTEXT RELEASE message can be sent after step 6. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 18.2 |
2,765 | 6.12 Multiple Transmit/Receive Point Operation | In Multiple Transmit/Receive Point (multi-TRP) operation, a serving cell can schedule the UE from two TRPs, providing better coverage, reliability and/or data rates for PDSCH, PDCCH, PUSCH, and PUCCH. There are two different operation modes to schedule multi-TRP PDSCH transmissions: single-DCI and multi-DCI. For both modes, control of uplink and downlink operation can be done by physical layer and MAC layer, within the configuration provided by the RRC layer. In single-DCI mode, the UE is scheduled by the same DCI for both TRPs and in multi-DCI mode, the UE is scheduled by independent DCIs from each TRP. There are two different operation modes for multi-TRP PDCCH: PDCCH repetition as in Clause 5.2.3 and Single Frequency Network (SFN) based PDCCH transmission. In both modes, the UE can receive two PDCCH transmissions, one from each TRP, carrying the same DCI. In PDCCH repetition mode, the UE can receive the two PDCCH transmissions carrying the same DCI from two linked search spaces each associated with a different CORESET. In SFN based PDCCH transmission mode, the UE can receive the two PDCCH transmissions carrying the same DCI from a single search space/CORESET using different TCI states. For multi-TRP PUSCH repetition, according to indications in a single DCI or in a semi-static configured grant provided over RRC, the UE performs PUSCH transmission of the same contents toward two TRPs with corresponding beam directions associated with different spatial relations. For multi-TRP PUCCH repetition, the UE performs PUCCH transmission of the same contents toward two TRPs with corresponding beam directions associated with different spatial relations. For inter-cell multi-TRP operation, for multi-DCI PDSCH transmission, one or more TCI states can be associated with SSB with a PCI different from the serving cell PCI. The activated TCI states can be associated with at most one PCI different from the serving cell PCI at a time. For inter-cell and intra-cell multi-DCI multi-TRP operation, up to two TAGs with associated TAG IDs can be configured per serving cell. Each UL/Joint TCI state is associated with a TAG ID and the UE applies the timing advance of the TAG ID associated with the UL/joint TCI state utilized for UL transmission. For single-DCI multi-TRP Simultaneous Transmission with Multi-Panel (STxMP) Spatial Domain Multiplexing (SDM) PUSCH transmission, different layers of one PUSCH are separately transmitted towards two TRPs. For single-DCI multi-TRP STxMP SFN PUSCH transmission, same layers of one PUSCH are transmitted towards two TRPs. For multi-DCI based multi-TRP STxMP PUSCH+PUSCH transmission, two PUSCHs are transmitted towards two TRPs. For single-DCI multi-TRP STxMP SFN PUCCH transmission, one PUCCH is transmitted towards two TRPs. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 6.12 |
2,766 | 4.26.2 NF/NF Service Context Transfer Push Procedure | Figure 4.26.2-1: NF/NF Service Context Push procedure 1. When triggered, the Source NF/NF Service acting as NF Service Consumer sends its Context (e.g. UE Context or SM context) to the Target NF/NF Service acting as NF Service producer. This may trigger several other procedures that ensure all necessary NF/NF Services are being updated and set up with necessary information about the new context location. 2. The NF Service Consumer receives the response indicating the result of the operation (successful or not successful). When all procedures have been executed successfully the Target NF/NF Service can continue to serve the original NF Service Consumers of the Source NF/NF Service, which e.g. can be shut down gracefully. NOTE: After resumption of a new service transaction, it may be necessary to contact the UE using existing procedures. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.26.2 |
2,767 | 9.4.9 Authentication and ciphering request | This message is sent by the network to the MS to initiate authentication of the MS identity. Additionally, the ciphering mode is set, indicating whether ciphering will be performed or not. See table 9.4.9/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Message type: AUTHENTICATION AND CIPHERING REQUEST Significance: dual Direction: network to MS Table 9.4.9/TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : AUTHENTICATION AND CIPHERING REQUEST message content | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.4.9 |
2,768 | 6.9.4.2 NAS key re-keying | After a primary authentication has taken place, new NAS keys from a new KAMF shall be derived, according to Annex A.8. To re-activate a non-current full native 5G security context after handover from E-UTRAN the UE and the AMF take the NAS keys into use by running a NAS SMC procedure according to clause 6.7.2. AMF shall activate fresh NAS keys from a primary authentication run or activate native security context, which has a sufficiently low NAS COUNT values, before the NAS uplink or downlink COUNT wraps around with the current security context. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.9.4.2 |
2,769 | 20.3.4 MBMS session termination (MBMS GW initiated) | Figure 20.3.4.1: MBMS session termination 1. In exceptional cases (e.g. resource pre-emption or timeout of the MBMS session), the MBMS GW may send an STR command to the BM-SC to initiate the termination of the Diameter session related to an MBMS bearer service. If a bearer plane had been established over SGi-mb for this MBMS bearer service, the bearer plane is released. If the MBMS GW detects the SGi-mb path failure as specified in subclause 20.3.2.1 of 3GPP TS 23.007[ Restoration procedures ] [104], the MBMS GW shall set the Termination-Cause to "DIAMETER_LINK_BROKEN" (see IETF RFC 6733 [111]) and shall include the Diagnostic-Info AVP set to "User Plane Failure" if it tears down the MBMS session as a result of detecting an SGi-mb path failure. 2. The BM-SC removes the Diameter session and confirms the operation by sending an STA message to the MBMS GW. | 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.4 |
2,770 | 16.8.2.3 Network timing synchronization monitoring towards UE | The gNB may receive clock quality reporting control information for a UE from the AMF, see TS 23.501[ System architecture for the 5G System (5GS) ] [3]. The clock quality reporting control information contains the clock quality detail level (i.e., "metrics" or "acceptable/not acceptable indication") and clock quality acceptance criteria for the UE (if the clock quality detail level equals "acceptable/not acceptable indication"). Based on the clock quality reporting control information, the gNB determines how to provision clock quality information to the UE: - If the clock quality detail level equals "clock quality metrics", the gNB provides clock quality metrics supported by the gNB to the UE, i.e., one or more of the following information elements: synchronization state, traceability to UTC, traceability to GNSS, clock frequency stability, clock accuracy, parent time source, as defined in Table 5.27.1.12-1 in TS 23.501[ System architecture for the 5G System (5GS) ] [3]. - If the clock quality detail level equals "acceptable/not acceptable indication", the gNB indicates "acceptable" to the UE if the gNB's timing synchronization status matches the acceptance criteria received from the AMF; otherwise, the gNB indicates "not acceptable" to the UE. Clock quality acceptance criteria can be defined based on one or more information elements listed in Table 5.27.1.12-1 in TS 23.501[ System architecture for the 5G System (5GS) ] [3]. To provision clock quality information to the UEs: - For UEs in the RRC CONNECTED state, the gNB uses unicast RRC signalling. The RRC signalling includes Event ID and clock quality information. - For UEs that are not in the RRC_CONNECTED state, the UE first needs to establish or resume the RRC connection to receive the gNB timing synchronization status information from the gNB via unicast RRC signalling. The gNB broadcasts Event ID in SIB9 to notify its timing synchronization status. Event ID or gNB ID change serves as a notification for the UEs reading the SIB information that there is new RAN timing synchronization status information available. The following figure describes the signalling procedure of gNB reporting clock quality information to a UE: Figure 16.8.2-1: Signalling procedure of gNB reporting clock quality information to a UE 0. The gNB node is pre-configured for the thresholds for each timing synchronization status attribute as described in clause 5.27.1.12 in TS 23.501[ System architecture for the 5G System (5GS) ] [3]. If there is a change on its primary source so that the thresholds are exceeded or met again, the NG-RAN node detects a change on its timing synchronization state (e.g., degradation, failure, recovery). 1. The gNB notifies a change on its timing synchronization operation using Event ID in SIB9. The Event ID scope is local to gNB. 2. The UE in RRC_INACTIVE or RRC_IDLE determines if there is clock quality information update available at the gNB based on SIB9 information. For a UE in RRC_CONNECTED state, steps 2-3 can be skipped. 3. If there is a RAN timing synchronization status update available, the UE's RRC layer indicates this to the NAS layer which may request the RRC layer to initiate RRC Setup or RRC Resume procedure. 4. The gNB determines clock quality information reporting to the UE (e.g., metrics or "acceptable/not acceptable"). 5. The gNB sends the clock quality information to the UE via unicast RRC signalling. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.8.2.3 |
2,771 | 8.2.7.26 Non-3GPP NW policies | The AMF shall not include this IE during a registration procedure over non-3GPP access. This IE is included if the network needs to indicate whether emergency numbers provided via non-3GPP access can be used to initiate UE detected emergency calls (see 3GPP TS 24.302[ Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networks; Stage 3 ] [16]). If this IE is not included then the UE shall interpret this as a receipt of an information element with all bits of the value part coded as zero. NOTE: In this version of the specification, this IE is applicable in case the UE is connected to a PLMN using an ePDG as specified in 3GPP TS 24.302[ Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networks; Stage 3 ] [16]. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 8.2.7.26 |
2,772 | 9.11.3.12 Additional 5G security information | The purpose of the Additional 5G security information information element is to provide the UE with additional security parameters (e.g. horizontal derivation parameter) or to request the UE to retransmit an initial NAS message during a security mode control procedure as defined in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. The UE uses these parameters for completion of security mode control procedure. The Additional 5G security information information element is coded as shown in figure 9.11.3.12.1 and table 9.11.3.12.1. The Additional 5G security information is a type 4 information element with a length of 3 octets. Figure 9.11.3.12.1: Additional 5G security information information element Table 9.11.3.12.1: Additional 5G security information 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.12 |
2,773 | – MeasObjectNR-SL | The IE MeasObjectNR-SL concerns a measurement object including a list of transmission resource pool(s) for which CBR measurement is performed for NR sidelink communication/discovery. MeasObjectNR-SL information element -- ASN1START -- TAG-MEASOBJECTNR-SL-START MeasObjectNR-SL-r16 ::= SEQUENCE { tx-PoolMeasToRemoveList-r16 Tx-PoolMeasList-r16 OPTIONAL, -- Need N tx-PoolMeasToAddModList-r16 Tx-PoolMeasList-r16 OPTIONAL -- Need N } MeasObjectNR-SL-v1800 ::= SEQUENCE { sl-Frequency INTEGER (1..maxNrofFreqSL-r16), tx-PoolMeasToRemoveList-r16 Tx-PoolMeasList-r16 OPTIONAL, -- Need N tx-PoolMeasToAddModList-r16 Tx-PoolMeasList-r16 OPTIONAL -- Need N } Tx-PoolMeasList-r16 ::= SEQUENCE (SIZE (1..maxNrofSL-PoolToMeasureNR-r16)) OF SL-ResourcePoolID-r16 -- TAG-MEASOBJECTNR-SL-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,774 | 16.9.3.3 UE Autonomous Resource Selection | The UE autonomously selects sidelink resource(s) from resource pool(s) provided by broadcast system information or dedicated signalling while inside NG-RAN coverage or by pre-configuration while outside NG-RAN coverage. For NR sidelink communication, the resource pool(s) can be provided for a given validity area where the UE does not need to acquire a new pool of resources while moving within the validity area, at least when this pool is provided by SIB. The NR SIB area scope mechanism as specified in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12] is reused to enable validity area for SL resource pool configured via broadcasted system information. The UE is allowed to temporarily use UE autonomous resource selection with random selection for sidelink transmission based on configuration of the exceptional transmission resource pool as specified in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12]. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.9.3.3 |
2,775 | 5.5.2.1A.3 Group hopping | For the reference signal for PUSCH transmission using sub-PRB allocations for BL/CE UEs, sequence-group hopping can be enabled where the sequence-group number in slot of a radio frame is defined by a group hopping pattern and a sequence-shift pattern according to where the number of reference signal sequences available for each resource unit size, is given by Table 5.5.2.1A.3-1. Table 5.5.2.1A.3-1: Definition of Sequence-group hopping can be enabled or disabled as described in clause 5.5.1.3. The group-hopping pattern is given by where for using QPSK modulation scheme. When using π/2-BPSK modulation scheme, for frame structure type 1, is the slot number of the first slot of the resource unit, and for frame structure type 2, is the frame number of the first slot of the resource unit. The pseudo-random sequence is defined by clause 7.2. The pseudo-random sequence generator shall be initialized with at the beginning of the resource unit for using π/2-BPSK modulation scheme and in every even slot for using QPSK modulation scheme. The sequence-shift pattern is given by where . | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.5.2.1A.3 |
2,776 | 5.2.2.3 Namf_EventExposure service 5.2.2.3.1 General | Service description: This service enables an NF to subscribe and get notified about an Event ID. Following UE access and mobility information event are considered (Event ID is defined in clause 4.15.1 and Table 4.15.3.1-1): - Location Report (TAI, Cell ID, N3IWF/TNGF node, UE local IP address and optionally UDP source port number); - UE moving in or out of a subscribed "Area Of Interest" as described in clauses 5.3.4.4 and 5.6.11 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]; - Number of UEs served by the AMF and located in "Area Of Interest"; - Time zone changes (UE Time zone); - Access Type changes (3GPP access or non-3GPP access); - Registration state changes (Registered or Deregistered); - Connectivity state changes (IDLE or CONNECTED); - UE loss of communication; - UE reachability status; - UE indication of switching off SMS over NAS service; - Subscription Correlation ID change (implicit subscription); - UE Type Allocation code (TAC); - Frequent mobility re-registration; - Subscription Correlation ID addition (implicit subscription); - User State Information in 5GS, as described in clause 5.4.4 of TS 23.632[ User data interworking, coexistence and migration; Stage 2 ] [68]; - UE access behaviour trends (see clause 4.15.4.2); - UE location trends (see clause 4.15.4.2); and - Total number of Mobility Management transactions: - The Total number of Mobility Management transactions is used to collect the number of MM transactions of a SUPI or Internal Group ID, for example Dispersion Analytics as specified in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]. The Total number of transactions is incremented when the NAS signalling transactions from Authentication, Registration, De-Registration, Service Request and UE Configuration Update procedures is completed. Only the periodic reporting mode applies. In addition to UE access and mobility information event, AMF exposes the "S-NSSAIs per TAI mapping" event providing, per TAI, the related access type and list of supported S-NSSAIs (including indication of S-NSSAIs restricted by AMF). The Event Consumer may use as target of event reporting a list of TAIs, or "any TAI" and may use event filter information including a list of "S-NSSAIs". Whenever there is a change in supported S-NSSAIs (including indication of S-NSSAIs restricted by AMF) for a TAI, the event notification is generated with the updated information. Event Filters are used to specify the conditions to match for notifying the event (i.e. "List of Parameter values to match"). If there are no conditions to match for a specific Event ID, then the Event Filter is not provided. The following table provides some examples on how the conditions to match for event reporting can be specified for various Event IDs for AMF exposure. NOTE: The conditions to match can be set based on AMF-associated expected UE Behaviour parameter(s) to only notify the event when the UE's behaviour deviates from its expected UE behaviour as described in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]. Table 5.2.2.3.1-1: Example of Event Filters for AMF exposure events The following service operations are defined for the Namf_EventExposure service: - Namf_EventExposure_Subscribe. - Namf_EventExposure_UnSubscribe. - Namf_EventExposure_Notify. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.2.3 |
2,777 | 5.17.3 Interworking with EPC in presence of Non-3GPP PDU Sessions | When a UE is simultaneously connected to the 5GC over a 3GPP access and a non-3GPP access, it may have PDU Sessions associated with 3GPP access and PDU Sessions associated with non-3GPP access. When inter-system handover from 5GS to EPS is performed for PDU Sessions associated with 3GPP access, the PDU Sessions associated with non-3GPP access are kept anchored by the network in 5GC and the UE may either: - keep PDU Sessions associated with non-3GPP access in 5GS (5GC+N3IWF or TNGF) (i.e. the UE is then registered both in EPS and, for non-3GPP access, in 5GS); or - locally or explicitly release PDU Sessions associated with non-3GPP access; or - once in EPS, transfer PDU Sessions associated with non-3GPP access to E-UTRAN by triggering PDN connection establishment with Request Type "Handover", as specified in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [26]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.17.3 |
2,778 | 9.3.5.1.2 TDD | For the parameters specified in Table 9.3.5.1.2-1, and using the downlink physical channels specified in Annex C, the minimum requirements are specified in 9.3.5.1.2-2 and by the following a) the ratio of the throughput obtained when transmitting the transport format indicated by each reported wideband CQI index subject to an interference source with specified DIP and that obtained when transmitting the transport format indicated by each reported wideband CQI index subject to a white Gaussian noise source shall be ≥ ; b) when transmitting the transport format indicated by each reported wideband CQI index subject to an interference source with specified DIP, the average BLER for the indicated transport formats shall be greater than or equal to 2%. Table 9.3.5.1.2-1 Fading test for single antenna (TDD) Table 9.3.5.1.2-2 Minimum requirement (TDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.3.5.1.2 |
2,779 | 4.2.8.4 Architecture Reference Model for Wireline Access network | Figure 4.2.8.4-1: Non- roaming architecture for 5G Core Network for 5G-RG with Wireline 5G Access network and NG RAN The 5G-RG can be connected to 5GC via W-5GAN, NG RAN or via both accesses. NOTE 1: The reference architecture in figure 4.2.8.4-1 only shows the architecture and the network functions directly connected to Wireline 5G Access Network, and other parts of the architecture are the same as defined in clause 4.2. NOTE 2: The reference architecture in figure 4.2.8.4-1 supports service based interfaces for AMF, SMF and other NFs not represented in the figure. NOTE 3: The two N2 instances in Figure 4.2.8.4-1 apply to a single AMF for a 5G-RG which is simultaneously connected to the same 5G Core Network over 3GPP access and Wireline 5G Access Network. NOTE 4 The two N3 instances in Figure 4.2.8. 4-1 may apply to different UPFs when different PDU Sessions are established over 3GPP access and Wireline 5G Access Network. Figure 4.2.8.4-2: Non- roaming architecture for 5G Core Network for FN-RG with Wireline 5G Access network and NG RAN The N1 for the FN-RG, which is not 5G capable, is terminated on W-AGF which acts on behalf of the FN-RG. The FN-RG can only be connected to 5GC via W-5GAN. NOTE 5: The reference architecture in figure 4.2.8.4-2 only shows the architecture and the network functions directly connected to Wireline 5G Access Network, and other parts of the architecture are the same as defined in clause 4.2. NOTE 6: The reference architecture in figure 4.2.8.4-1 supports service based interfaces for AMF, SMF and other NFs not represented in the figure. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2.8.4 |
2,780 | 5.11.1.2 Integrity algorithm identifier values | All identifiers and names specified in the present sub-clause are for 5G NAS and New Radio. In relation to AS capabilities, the identifiers and names for E-UTRAN connected to 5GC are specified in TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [10]. Each integrity algorithm used for 5G will be assigned a 4-bit identifier. The following values for integrity algorithms are defined: "00002" NIA0 Null Integrity Protection algorithm; "00012" 128-NIA1 128-bit SNOW 3G based algorithm; "00102" 128-NIA2 128-bit AES based algorithm; and "00112" 128-NIA3 128-bit ZUC based algorithm. 128-NIA1 is based on SNOW 3G (see TS 35.215[ Specification of the 3GPP Confidentiality and Integrity Algorithms UEA2 & UIA2; Document 1: UEA2 and UIA2 specifications ] [14]). 128-NIA2 is based on 128-bit AES [15] in CMAC mode [17]. 128-NIA3 is based on 128-bit ZUC (see TS 35.221[ Specification of the 3GPP Confidentiality and Integrity Algorithms EEA3 & EIA3; Document 1: EEA3 and EIA3 specifications ] [18]). Full details of the algorithms are specified in Annex D. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 5.11.1.2 |
2,781 | 4.9.3 Disabling and re-enabling of UE's N1 mode capability for non-3GPP access | When the UE disables the N1 mode capability for non-3GPP access, the UE NAS layer shall not initiate any 5GS NAS procedures towards the network over non-3GPP access. When the UE supporting both N1 mode and S1 mode needs to stay in non-3GPP access 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 selection of a non-3GPP access network connected to 5GCN, the UE operating in single-registration mode shall not transfer any PDN connection to a non-3GPP access network connected to the 5GCN. If the disabling of N1 mode capability for non-3GPP access was due to IMS voice is not available over non-3GPP access in 5GS and the UE's usage setting is "voice centric", the UE shall re-enable the N1 mode capability for non-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 shall re-enable the N1 mode capability for non-3GPP access when a new PLMN or SNPN is selected over non-3GPP access. The UE may disable the N1 mode capability for the currently camped PLMN or SNPN over non-3GPP access if no network slice is available for the camped PLMN or SNPN. As an implementation option, the UE may start a timer for re-enabling the N1 mode capability for non-3GPP access, after the N1 mode capability for non-3GPP access was disabled. On the expiry of this timer, the UE should re-enable the N1 mode capability for non-3GPP access. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.9.3 |
2,782 | 28.9 Internal-Group Identifier | Internal-Group Identifier is a network internal globally unique ID which identifies a set of SUPIs (e.g. MTC devices) from a given network that are grouped together for one specific group related service (see 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [119] clause 5.9.7). An Internal-Group Identifier shall be composed in the same way as IMSI-Group Identifier (see clause 19.9). If a 5G subscriber's IMSI belongs to an IMSI-Group identified by a given IMSI-Group Identifier X, the IMSI shall also belong to the Internal-Group identified by the Internal-Group Identifier X. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 28.9 |
2,783 | 6.3.5G Power Control for V2X Communication | When UE is configured for E-UTRA V2X sidelink transmissions non-concurrent with E-UTRA uplink transmissions for E-UTRA V2X operating bands specified in Table Table 5.5G-1, the requirements in subclause 6.3.5G.1 apply for E-UTRA V2X sidelink transmission. When UE is configured for simultaneous E-UTRA V2X sidelink and E-UTRA uplink transmissions for inter-band E-UTRA V2X / E-UTRA bands specified in Table 5.5G-2, the requirements in subclause 6.3.5G.1 apply for V2X sidelink transmission and the requirements in subclause 6.3.5 apply for the E-UTRA uplink transmission. For V2X UE supporting Transmit Diversity, if the UE transmits on two antenna connectors at the same time, the power control tolerance for single carrier shall apply to the sum of output power at each transmit antenna connector. If the UE transmitson one -antenna connector at a time, the requirements for single carrier shall apply to the active antenna connector. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.3.5G |
2,784 | 9.11.3.44 PDU session status | The purpose of the PDU session status information element is to indicate the state of each PDU session that can be identified by a PDU session identity. The PDU session status information element is coded as shown in figure 9.11.3.44.1 and table 9.11.3.44.1. The PDU session status information element is a type 4 information element with minimum length of 4 octets and a maximum length of 34 octets. Figure 9.11.3.44.1: PDU session status information element Table 9.11.3.44.1: 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.44 |
2,785 | 6.1.1 Description | Network slicing allows the operator to provide customised networks. For example, there can be different requirements on functionality (e.g. priority, charging, policy control, security, and mobility), differences in performance requirements (e.g. latency, mobility, availability, reliability and data rates), or they can serve only specific users (e.g. MPS users, Public Safety users, corporate customers, roamers, or hosting an MVNO). A network slice can provide the functionality of a complete network, including radio access network functions, core network functions (e.g. potentially from different vendors) and IMS functions. One network can support one or several network slices. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.1.1 |
2,786 | 5.8.5.2 Initiation | A UE capable of NR sidelink communication/discovery and SLSS/PSBCH transmission shall, when transmitting NR sidelink communication/discovery/positioning, and if the conditions for NR sidelink communication/discovery/positioning operation are met and when the following conditions are met: 1> if in coverage on the frequency used for NR sidelink communication/discovery/positioning, as defined in TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [20]; and has selected GNSS or the cell as synchronization reference as defined in 5.8.6.3; or 1> if out of coverage on the frequency used for NR sidelink communication/discovery/positioning, and the frequency used to transmit NR sidelink communication/discovery is included in sl-FreqInfoToAddModList/sl-FreqInfoToAddModListExt in sl-ConfigDedicatedNR within RRCReconfiguration message or included in sl-FreqInfoList/sl-FreqInfoListSizeExt within SIB12 or SIB23 for NR sidelink positioning; and has selected GNSS or the cell as synchronization reference as defined in 5.8.6.3: 2> if sl-SyncFreqList is neither included in RRCReconfiguration nor in SIB12; or 2> if sl-SyncFreqList is included in RRCReconfiguration or in SIB12; and if none of the frequency(ies) selected as specified in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3] is included in the sl-SyncFreqList or the concerned frequency is selected as the synchronisation carrier frequency in accordance with 5.8.6.2; or 2> if sl-SyncFreqList and sl-SyncTxMultiFreq are included in RRCReconfiguration or in SIB12; and if the concerned frequency has been selected for NR sidelink communication transmission as specified in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3] and is included in sl-SyncFreqList; and if the UE has selected a frequency other than the concerned frequency as the synchronisation carrier frequency in accordance with 5.8.6.2; and if sl-SyncTxDisabled corresponding to the concerned frequency is not configured in RRCReconfiguration or in SIB12: 3> if in RRC_CONNECTED; and if networkControlledSyncTx is configured and set to on; or 3> if networkControlledSyncTx is not configured; and for the concerned frequency syncTxThreshIC is configured; and the RSRP measurement of the reference cell, selected as defined in 5.8.6.3, for NR sidelink communication/discovery transmission is below the value of syncTxThreshIC: 4> transmit sidelink SSB on the frequency used for NR sidelink communication/discovery in accordance with 5.8.5.3 and TS 38.211[ NR; Physical channels and modulation ] [16], including the transmission of SLSS as specified in 5.8.5.3 and transmission of MasterInformationBlockSidelink as specified in 5.8.9.4.3; 1> else: 2> if sl-SyncFreqList is not included in SL-PreconfigurationNR; or 2> if sl-SyncFreqList is included in SL-PreconfigurationNR, and if none of the frequency(ies) selected as specified in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3] is included in the sl-SyncFreqList or the concerned frequency is selected as the synchronisation carrier frequency in accordance with 5.8.6.2; or 2> if sl-SyncFreqList and sl-SyncTxMultiFreq are included in SL-PreconfigurationNR, and if the concerned frequency has been selected for NR sidelink communication transmission as specified in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3] and included in sl-SyncFreqList; and if the UE has selected a frequency other than the concerned frequency as the synchronisation carrier frequency in accordance with 5.8.6.2; and if sl-SyncTxDisabled corresponding to the concerned frequency is not configured in SL-PreconfigurationNR: 3> for the frequency used for NR sidelink communication/discovery, if syncTxThreshOoC is included in SidelinkPreconfigNR; and the UE is not directly synchronized to GNSS, and the UE has no selected SyncRef UE or the PSBCH-RSRP measurement result of the selected SyncRef UE is below the value of syncTxThreshOoC; or 3> for the frequency used for NR sidelink communication/discovery, if the UE selects GNSS as the synchronization reference source: 4> transmit sidelink SSB on the frequency used for NR sidelink communication/discovery in accordance with 5.8.5.3 and TS 38.211[ NR; Physical channels and modulation ] [16], including the transmission of SLSS as specified in 5.8.5.3 and transmission of MasterInformationBlockSidelink as specified in 5.8.9.4.3; | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.5.2 |
2,787 | 2.10.2.2.2 Mapping in the UE | When the UE moves from the E-UTRAN to 5GS, the UE needs to map the GUTI to a 5G-GUTI to be sent to the AMF. The mapping of the GUTI to a 5G-GUTI shall be performed as follows: E-UTRAN <MCC> maps to 5GS <MCC> E-UTRAN <MNC> maps to 5GS <MNC> E-UTRAN <MME Group ID> maps to 5GS <AMF Region ID> and part of 5GS <AMF Set ID> as follows: - 8 bits of the E-UTRAN <MME Group ID> starting at bit 15 and down to bit 8 are mapped into bit 7 and down to bit 0 of the 5GS <AMF Region ID>; - 8 bits of the E-UTRAN <MME Group ID> starting at bit 7 and down to bit 0 are mapped into bit 9 and down to bit 2 of the 5GS <AMF Set ID>;E-UTRAN <MME Code> maps to 5GS <AMF Set ID> and 5GS <AMF Pointer> as follows: - 2 bits of the E-UTRAN <MME Code> starting at bit 7 and down to bit 6 are mapped into bit 1 and down to bit 0 of the 5GS <AMF Set ID>; - 6 bits of the E-UTRAN <MMEC Code> starting at bit 5 and down to bit 0 are mapped into bit 5 and down to bit 0 of the 5GS <AMF Pointer >; E-UTRAN <M-TMSI> maps to 5GS <5G-TMSI> | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 2.10.2.2.2 |
2,788 | 14.2 Services provided by UDM 14.2.1 General | UDM provides within Nudm_UEAuthentication service all authentication-related service operations, which are Nudm_UEAuthentication_Get (clause 14.2.2) , Nudm_UEAuthentication_ResultConfirmation (clause 14.2.3), Nudm_UEAuthentication_GetProseAv (clause 14.2.4) and Nudm_UEAuthentication_GetGbaAv (clause 14.2.5). The complete list of UDM services is defined in TS 23.501[ System architecture for the 5G System (5GS) ] [2], clause 7.2.5, and further refined in TS 23.502[ Procedures for the 5G System (5GS) ] [8], clause 5.2.3.1. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 14.2 |
2,789 | – SIB21 | SIB21 contains the mapping between the current and/or neighbouring carrier frequencies and MBS Frequency Selection Area Identities (FSAI). SIB21 information element -- ASN1START -- TAG-SIB21-START SIB21-r17 ::= SEQUENCE { mbs-FSAI-IntraFreq-r17 MBS-FSAI-List-r17 OPTIONAL, -- Need R mbs-FSAI-InterFreqList-r17 MBS-FSAI-InterFreqList-r17 OPTIONAL, -- Need R lateNonCriticalExtension OCTET STRING OPTIONAL, ... } MBS-FSAI-List-r17 ::= SEQUENCE (SIZE (1..maxFSAI-MBS-r17)) OF MBS-FSAI-r17 MBS-FSAI-InterFreqList-r17 ::= SEQUENCE (SIZE (1..maxFreq)) OF MBS-FSAI-InterFreq-r17 MBS-FSAI-InterFreq-r17 ::= SEQUENCE { dl-CarrierFreq-r17 ARFCN-ValueNR, mbs-FSAI-List-r17 MBS-FSAI-List-r17 } MBS-FSAI-r17 ::= OCTET STRING (SIZE (3)) -- TAG-SIB21-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,790 | 5.44.3.1 PDU Session Establishment for PIN | When a PDU Session associated with a PIN is established by PEGC, an SMF is selected according to clause 4.3.2.2.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] based on S-NSSAI/DNN. The PEGC may use IP address allocation methods as specified in clause 5.8.2 (e.g. IPv6 Prefix Delegation feature). One PEGC may serve more than one PIN. The PEGC may use a single or multiple PDU sessions to serve multiple PINs. One PDU Session may be shared by more than one PIN served by the PEGC, if differentiation or isolation for the traffics to/from different PINs via PEGC is not required in 5GS. Otherwise, different DNNs and S-NSSAIs shall be applied to distinguish the PINs by different PDU sessions of the PEGC. One PIN can be served by only one PDU session in the PEGC. If there are multiple PDU sessions for a PIN from different PEGCs connecting to the same UPF, the same mechanism for local switching in the UPF as defined for 5G VN group communication, as described in clause 5.8.2.13, may be applied. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.44.3.1 |
2,791 | 6.6.3.2 Spurious emission band UE co-existence | This clause specifies the requirements for the specified E-UTRA band, for coexistence with protected bands. NOTE: For measurement conditions at the edge of each frequency range, the lowest frequency of the measurement position in each frequency range should be set at the lowest boundary of the frequency range plus MBW/2. The highest frequency of the measurement position in each frequency range should be set at the highest boundary of the frequency range minus MBW/2. MBW denotes the measurement bandwidth defined for the protected band. Table 6.6.3.2-1: Requirements NOTE: The restriction on the maximum uplink transmission to 54 RB in Notes 21, 22, and 27 of Table 6.6.3.2-1 and the restriction on the single-tone uplink transmission to sub-carrier index > 2 in Note 44 of Table 6.6.3.2-1 are intended for conformance testing and may be applied to network operation to facilitate coexistence when the aggressor and victim bands are deployed in the same geographical area. The applicable spurious emission requirement of -15.5 dBm/5MHz is a least restrictive technical condition for FDD/TDD coexistence and may have to be revised in the future. When "NS_33" or “NS 34” is configured from pre-configured radio parameters or the cell and the indication from upper layers has indicated that the UE is within the protection zone of CEN DSRC devices or HDR DSRC devices, the power of any V2X UE emission shall fulfil either one of the two set of conditions. | 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.2 |
2,792 | 9 Charging aspects 9.1 General | The following set of requirements complement the requirements listed in 3GPP TS 22.115[ Service aspects; Charging and billing ] [11]. The requirements apply for both home and roaming cases. The 5G core network shall support collection of all charging information on either a network or a slice basis. The 5G core network shall support collection of charging information for alternative authentication mechanisms. The 5G core network shall support collection of charging information associated with each serving MNO when multi-network connectivity is used under the control of the home operator. The 5G core network shall support charging for services/applications in an operator’s Service Hosting Environment. The 5G core network shall support charging for content delivered from a content caching application. The 5G core network shall support collection of charging information based on the access type (e.g. 3GPP, non-3GPP, satellite access). The 5G core network shall support collection of charging information based on the slice that the UE accesses. The 5G system shall be able to generate charging information regarding the used radio resources e.g. used frequency bands. The 5G core network shall support collection of charging information based on the capacity and performance metrics. The 5G system shall be able to support an indirect network connection even when the UE is in E-UTRAN or NG-RAN coverage. The 5G system shall be able to support mechanisms to differentiate charging information for traffic carried over satellite backhaul. For service function chaining (see clause 10) the collection of charging information associated to the use of service functions and the chain of service functions requested by third parties shall be supported. The 5G system shall be able to support collection of charging information for a group of UEs, e.g. UEs of a AI/ML FL group. The 5G system shall be able to support charging mechanism for multiple UE exchange data for the same service using the direct device connection. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 9 |
2,793 | 4.3.5.5 Removal of additional PDU Session Anchor and Branching Point or UL CL | Clause 4.3.5.5 describes a procedure to remove a PDU Session Anchor and (optionally) remove Branching Point or UL CL for an established PDU Session. Figure 4.3.5.5-1: Removal of additional PDU Session Anchor and Branching Point or UL CL 1. UE has an established PDU Session with a UPF including the Branching Point or UL CL, the PDU Session Anchor 1 (PSA1 in Figure 4.3.5.5-1) and the PDU Session Anchor 2 (PSA2 in Figure 4.3.5.5-1). At some point the SMF decides to remove the PDU Session Anchor 1 e.g. due to UE mobility, flow terminated. 2. In the case of IPv6 multi-homing, the SMF notifies the UE to stop using the IPv6 prefix corresponding to PSA1. This is performed by IPv6 Router Advertisement message (RFC 4861 [6] and RFC 4862 [8]). Also, the SMF sends IPv6 multi-homed routing rule along with the IPv6 prefix corresponding to PSA2 to the UE as described in clause 5.8.2.2.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. Based on the information provided in the Router Advertisement, the UE starts using the IPv6 prefix (corresponding to PSA2) for all the traffic. 4. If the Branching Point or UL CL is to be released, the SMF updates the (R)AN with the PSA2 CN Tunnel Info. In the case of UL CL, if there is an existing UPF between the (R)AN and the UL CL to be removed, the SMF updates the existing UPF via N4 instead of updating the (R)AN. 5. If the Branching Point or UL CL is to be released, the SMF updates via N4 the PSA2 providing the AN Tunnel Info. In the case of UL CL, if there is an existing UPF between the (R)AN and the UL CL to be removed, the SMF updates the PSA2 providing the UPF CN tunnel Info. 6. The SMF releases via N4 the PSA1. In the case of IPv6 multi-homing, the SMF also releases the corresponding IPv6 prefix and if the PCF has subscribed to the IP allocation/release event, the SMF performs the Session Management Policy Modification procedure as defined in clause 4.16.5 to notify the PCF of the IPv6 prefix release. 7. If steps 4 and 5 were executed, the SMF releases the Branching Point / UL CL. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3.5.5 |
2,794 | 5.2.4.3 Traffic channel assignment and user connection attachment | An appropriate traffic channel for the call is assigned in SRVCC handover, vSRVCC handover or 5G-SRVCC handover from NG-RAN to UTRAN. For SRVCC handover or 5G-SRVCC handover from NG-RAN to UTRAN, the mobile station shall attach the user connection: - when the call control entity enters the "active" state or the "call received" state; - when the call control entity enters the "call delivered" state, if prior to SRVCC the MS in the PS domain was receiving media for the session subjected to SRVCC handover or 5G-SRVCC handover from NG-RAN to UTRAN; and - when the call control entity enters the "mobile originating call proceeding" state, if prior to SRVCC the MS in the PS domain was receiving media for the session subjected to SRVCC handover5G-SRVCC handover from NG-RAN to UTRAN. NOTE: The attachment of the user connection prior to entering the "active" state allows the network to provide in-band tones and announcements to the UE. For vSRVCC handover, the mobile station shall attach the user connection when the call control entity enters the "active" state. For SRVCC or vSRVCC handover to a speech call, the principles of speech codec selection are described in subclause 5.2.1.11. For vSRVCC handover to a circuit-switched multimedia call, further requirements are specified in subclause 5.3.6.6. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.2.4.3 |
2,795 | 10.5.1.14 NAS container for PS HO | The purpose of the NAS container for PS HO information element is to indicate the NAS specific information for the PS handover to A/Gb mode. The NAS container for PS HO information element is included in the PS HO command message, see 3GPP TS 44.060[ None ] [76]. The coding of the information element identifier and length information is defined in 3GPP TS 44.060[ None ] [76]. The content of the NAS container for PS HO information element is coded as shown in figure 10.5.1.14/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.1.14/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The length of this information element is 5 octets. The MS shall ignore any additional octets received. Figure 10.5.1.14/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] NAS container for PS HO information element Table 10.5.1.14/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : NAS container for PS HO information element | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.1.14 |
2,796 | 5.4.7.2.1 Network slice-specific EAP message reliable transport procedure initiation | In order to initiate the network slice-specific EAP message reliable transport procedure, the AMF shall create a NETWORK SLICE-SPECIFIC AUTHENTICATION COMMAND message. The AMF shall set the EAP message IE of the NETWORK SLICE-SPECIFIC AUTHENTICATION COMMAND message to the EAP-request message which is generated by the AMF or provided by the AAA-S via the NSSAAF. The AMF shall set the S-NSSAI IE of the NETWORK SLICE-SPECIFIC AUTHENTICATION COMMAND message to the HPLMN S-NSSAI or the SNPN S-NSSAI to which the EAP-request message is related. The AMF shall send the NETWORK SLICE-SPECIFIC AUTHENTICATION COMMAND message and start timer T3575 per S-NSSAI (see example in figure 5.4.7.1.1). Upon receipt of a NETWORK SLICE-SPECIFIC AUTHENTICATION COMMAND message, the UE shall stop timer T3346 if running. The UE shall pass: a) the EAP-request message received in the EAP message IE; and b) the HPLMN S-NSSAI or the SNPN S-NSSAI in the S-NSSAI IE; to the upper layers. Apart from this action, the network slice-specific authentication and authorization procedure is transparent to the 5GMM layer of the UE. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.4.7.2.1 |
2,797 | 10.5.5.12 MS network capability | The purpose of the MS network capability information element is to provide the network with information concerning aspects of the mobile station related to GPRS. The contents might affect the manner in which the network handles the operation of the mobile station. The MS network capability information indicates general mobile station characteristics and it shall therefore, except for fields explicitly indicated, be independent of the frequency band of the channel it is sent on. The MS network capability is a type 4 information element with a maximum of 10 octets length. The value part of a MS network capabilityinformation element is coded as shown in figure 10.5.128/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.145/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . NOTE: The requirements for the support of the GEA algorithms in the MS are specified in 3GPP TS 43.020[ Security related network functions ] [13]. Figure 10.5.128/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] MS network capability information element Table 10.5.145/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] MS network capability information element | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.5.12 |
2,798 | 7.3.2 Requirements 7.3.2.1 General | The 5G System shall provide different 5G positioning services with configurable performances working points (e.g. accuracy, positioning service availability, positioning service latency, energy consumption, update rate, TTFF) according to the needs of users, operators and third parties. The 5G system shall support the combination of 3GPP and non-3GPP positioning technologies to achieve performances of the 5G positioning services better than those achieved using only 3GPP positioning technologies. NOTE 1: For instance, the combination of 3GPP positioning technologies with non-3GPP positioning technologies such as GNSS (e.g. Beidou, Galileo, GLONASS, and GPS), Terrestrial Beacon Systems (TBS), sensors (e.g. barometer, IMU), WLAN/Bluetooth-based positioning, can support the improvement of accuracy, positioning service availability, reliability and/or confidence level, the reduction of positioning service latency, the increase of the update rate of the position-related data, increase the coverage (service area). NOTE 2: The combination can vary over time to optimise the performances, and can be the combination of multiple positioning technologies at the same epoch and/or the combination of multiple positioning technologies at different epochs. The corresponding positioning information shall be acquired in a timely fashion, be reliable, and be available (e.g. it is possible to determine the position). UEs shall be able to share positioning information between each other e.g. to a controller if the location information cannot be processed or used locally. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 7.3.2 |
2,799 | 6.2.3 UPF | The User plane function (UPF) includes the following functionality. Some or all of the UPF functionalities may be supported in a single instance of a UPF: - Anchor point for Intra-/Inter-RAT mobility (when applicable). - Allocation of UE IP address/prefix (if supported) in response to SMF request. - External PDU Session point of interconnect to Data Network. - Packet routing & forwarding (e.g. support of Uplink classifier to route traffic flows to an instance of a data network, support of Branching point to support multi-homed PDU Session, support of traffic forwarding within a 5G VN group (UPF local switching, via N6, via N19)). - Packet inspection (e.g. Application detection based on service data flow template and the optional PFDs received from the SMF in addition). - User Plane part of policy rule enforcement, e.g. Gating, Redirection, Traffic steering). - Lawful intercept (UP collection). - Traffic usage reporting. - QoS handling for user plane, e.g. UL/DL rate enforcement, Reflective QoS marking in DL. - Uplink Traffic verification (SDF to QoS Flow mapping). - Transport level packet marking in the uplink and downlink. - Downlink packet buffering and downlink data notification triggering. - Sending and forwarding of one or more "end marker" to the source NG-RAN node. - Functionality to respond to Address Resolution Protocol (ARP) requests and / or IPv6 Neighbour Solicitation requests based on local cache information for the Ethernet PDUs. The UPF responds to the ARP and / or the IPv6 Neighbour Solicitation Request by providing the MAC address corresponding to the IP address sent in the request. - Packet duplication in downlink direction and elimination in uplink direction in GTP-U layer. - NW-TT functionality. - High latency communication, see clause 5.31.8. - ATSSS Steering functionality to steer the MA PDU Session traffic, refer to clause 5.32.6. NOTE: Not all of the UPF functionalities are required to be supported in an instance of user plane function of a Network Slice. - Inter PLMN UP Security (IPUPS) functionality, specified in clause 5.8.2.14. - Event exposure, including exposure of network information, i.e. the QoS monitoring information, as specified in clause 5.8.2.18, events as specified in clause 5.2.26.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3], exposure of data collected for analytics, as specified in clause 5.2.26.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] and exposure of the TSC management information as specified in clause 5.8.5.14. - Exposure of the UE information, e.g. UE IP address translation information as specified in clause 5.2.26.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] and clause 4.15.10 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] if Network address translation (i.e. NAT) functionality of the UE IP address is deployed within UPF. - Support PDU Set Handling as defined in clause 5.37.5. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.2.3 |
2,800 | 5.5.3.2 UE reachability in CM-CONNECTED | This clause applies to Non-3GPP access network corresponding to the Untrusted Non-3GPP access network, to the Trusted Non-3GPP access network and to the W-5GAN. In the case of W-5GAN the UE mentioned in this clause corresponds to 5G-RG and to W-AGF in the case of support of FN-RG. In the case of N5CW devices access 5GC via trusted WLAN access networks, the UE mentioned in this clause corresponds to TWIF. For a UE in CM-CONNECTED state: - the AMF knows the UE location on a N3IWF, TNGF, TWIF and W-AGF node granularity. - the N3IWF, TNGF, TWIF and W-AGF releases the N2 connection when UE becomes unreachable from N3IWF, TNGF, TWIF and W-AGF point of view, i.e. upon Non-3GPP Access Connection release. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.5.3.2 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.