Search is not available for this dataset
doc_id
int64 1
6.72k
⌀ | Section
stringlengths 5
247
⌀ | Content
stringlengths 501
147k
⌀ | Source
stringclasses 456
values | Document Title
stringclasses 22
values | Working Group
stringclasses 21
values | Series Subject
stringclasses 9
values | Subclause
stringlengths 1
13
⌀ |
|---|---|---|---|---|---|---|---|
5,401 | 10 Identification of the Cordless Telephony System entities 10.1 General description of CTS-MS and CTS-FP Identities | Every CTS-FP broadcasts a local identity - the Fixed Part Beacon Identity (FPBI) - which contains an Access Rights Identity. Every CTS-MS has both an Access Rights Key and a CTS Mobile Subscriber Identity (CTSMSI). These operate as a pair. A CTS-MS is allowed to access any CTS-FP which broadcasts an FPBI which can be identified by any of the CTS-MS Access Rights Keys of that CTS-MS. The CTS-MS Access Rights Key contains the FPBI and the FPBI Length Indicator (FLI) indicating the relevant part of the FPBI used to control access. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 10 |
5,402 | – EUTRA-Q-OffsetRange | The IE EUTRA-Q-OffsetRange is used to indicate a cell, or frequency specific offset to be applied when evaluating triggering conditions for measurement reporting. The value in dB. Value dB-24 corresponds to -24 dB, value dB-22 corresponds to -22 dB and so on. EUTRA-Q-OffsetRange information element -- ASN1START -- TAG-EUTRA-Q-OFFSETRANGE-START EUTRA-Q-OffsetRange ::= ENUMERATED { dB-24, dB-22, dB-20, dB-18, dB-16, dB-14, dB-12, dB-10, dB-8, dB-6, dB-5, dB-4, dB-3, dB-2, dB-1, dB0, dB1, dB2, dB3, dB4, dB5, dB6, dB8, dB10, dB12, dB14, dB16, dB18, dB20, dB22, dB24} -- TAG-EUTRA-Q-OFFSETRANGE-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,403 | – UE-MRDC-Capability | The IE UE-MRDC-Capability is used to convey the UE Radio Access Capability Parameters for MR-DC, see TS 38.306[ NR; User Equipment (UE) radio access capabilities ] [26]. UE-MRDC-Capability information element -- ASN1START -- TAG-UE-MRDC-CAPABILITY-START UE-MRDC-Capability ::= SEQUENCE { measAndMobParametersMRDC MeasAndMobParametersMRDC OPTIONAL, phy-ParametersMRDC-v1530 Phy-ParametersMRDC OPTIONAL, rf-ParametersMRDC RF-ParametersMRDC, generalParametersMRDC GeneralParametersMRDC-XDD-Diff OPTIONAL, fdd-Add-UE-MRDC-Capabilities UE-MRDC-CapabilityAddXDD-Mode OPTIONAL, tdd-Add-UE-MRDC-Capabilities UE-MRDC-CapabilityAddXDD-Mode OPTIONAL, fr1-Add-UE-MRDC-Capabilities UE-MRDC-CapabilityAddFRX-Mode OPTIONAL, fr2-Add-UE-MRDC-Capabilities UE-MRDC-CapabilityAddFRX-Mode OPTIONAL, featureSetCombinations SEQUENCE (SIZE (1..maxFeatureSetCombinations)) OF FeatureSetCombination OPTIONAL, pdcp-ParametersMRDC-v1530 PDCP-ParametersMRDC OPTIONAL, lateNonCriticalExtension OCTET STRING (CONTAINING UE-MRDC-Capability-v15g0) OPTIONAL, nonCriticalExtension UE-MRDC-Capability-v1560 OPTIONAL } -- Regular non-critical extensions: UE-MRDC-Capability-v1560 ::= SEQUENCE { receivedFilters OCTET STRING (CONTAINING UECapabilityEnquiry-v1560-IEs) OPTIONAL, measAndMobParametersMRDC-v1560 MeasAndMobParametersMRDC-v1560 OPTIONAL, fdd-Add-UE-MRDC-Capabilities-v1560 UE-MRDC-CapabilityAddXDD-Mode-v1560 OPTIONAL, tdd-Add-UE-MRDC-Capabilities-v1560 UE-MRDC-CapabilityAddXDD-Mode-v1560 OPTIONAL, nonCriticalExtension UE-MRDC-Capability-v1610 OPTIONAL } UE-MRDC-Capability-v1610 ::= SEQUENCE { measAndMobParametersMRDC-v1610 MeasAndMobParametersMRDC-v1610 OPTIONAL, generalParametersMRDC-v1610 GeneralParametersMRDC-v1610 OPTIONAL, pdcp-ParametersMRDC-v1610 PDCP-ParametersMRDC-v1610 OPTIONAL, nonCriticalExtension UE-MRDC-Capability-v1700 OPTIONAL } UE-MRDC-Capability-v1700 ::= SEQUENCE { measAndMobParametersMRDC-v1700 MeasAndMobParametersMRDC-v1700, nonCriticalExtension UE-MRDC-Capability-v1730 OPTIONAL } UE-MRDC-Capability-v1730 ::= SEQUENCE { measAndMobParametersMRDC-v1730 MeasAndMobParametersMRDC-v1730 OPTIONAL, nonCriticalExtension UE-MRDC-Capability-v1800 OPTIONAL } UE-MRDC-Capability-v1800 ::= SEQUENCE { -- R4 33-2: Support network control of requirementnetwork applicability for UE supporting interBandMRDC-WithOverlapDL-Bands-r16 requirementTypeIndication-r18 ENUMERATED {supported} OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } -- Late non-critical extensions: UE-MRDC-Capability-v15g0 ::= SEQUENCE { rf-ParametersMRDC-v15g0 RF-ParametersMRDC-v15g0 OPTIONAL, nonCriticalExtension UE-MRDC-Capability-v15n0 OPTIONAL } UE-MRDC-Capability-v15n0 ::= SEQUENCE { rf-ParametersMRDC-v15n0 RF-ParametersMRDC-v15n0 OPTIONAL, -- Following field is only for REL-15 late non-critical extensions lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension UE-MRDC-Capability-v16e0 OPTIONAL } UE-MRDC-Capability-v16e0 ::= SEQUENCE { rf-ParametersMRDC-v16e0 RF-ParametersMRDC-v16e0 OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } UE-MRDC-CapabilityAddXDD-Mode ::= SEQUENCE { measAndMobParametersMRDC-XDD-Diff MeasAndMobParametersMRDC-XDD-Diff OPTIONAL, generalParametersMRDC-XDD-Diff GeneralParametersMRDC-XDD-Diff OPTIONAL } UE-MRDC-CapabilityAddXDD-Mode-v1560 ::= SEQUENCE { measAndMobParametersMRDC-XDD-Diff-v1560 MeasAndMobParametersMRDC-XDD-Diff-v1560 OPTIONAL } UE-MRDC-CapabilityAddFRX-Mode ::= SEQUENCE { measAndMobParametersMRDC-FRX-Diff MeasAndMobParametersMRDC-FRX-Diff } GeneralParametersMRDC-XDD-Diff ::= SEQUENCE { splitSRB-WithOneUL-Path ENUMERATED {supported} OPTIONAL, splitDRB-withUL-Both-MCG-SCG ENUMERATED {supported} OPTIONAL, srb3 ENUMERATED {supported} OPTIONAL, dummy ENUMERATED {supported} OPTIONAL, ... } GeneralParametersMRDC-v1610 ::= SEQUENCE { f1c-OverEUTRA-r16 ENUMERATED {supported} OPTIONAL } -- TAG-UE-MRDC-CAPABILITY-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,404 | 8.7 Fraud protection | Subject to regional or national regulatory requirements, the 5G system shall support a secure mechanism for allowing an authorized entity to disable from normal operation of a UE reported as stolen. Subject to regional or national regulatory requirements, the 5G system shall support a secure mechanism for allowing an authorized entity to re-enable a recovered stolen UE to normal operation. The 5G system shall be able to protect user location information from passive attacks. Subject to regional or national regulatory requirements, the 5G system shall be able to protect user location information from active attacks. Subject to regional or national regulatory requirements, the 5G system shall support mechanisms to protect the production of the user location information and user positioning-related data against tampering and spoofing. Subject to regional or national regulatory requirements, the 5G system shall support mechanisms to detect tampering and spoofing attempts on the production of the user location information and the user position-related data. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 8.7 |
5,405 | 5.7.6 Packet Filter Set 5.7.6.1 General | The Packet Filter Set is used in the QoS rule and the PDR to identify one or more packet (IP or Ethernet) flow(s). NOTE 1: A QoS Flow is characterised by PDR(s) and QoS rule(s) as described in clause 5.7.1.1. NOTE 2: DL Packet Filter in a Packet Filter Set of a QoS rule may be needed by the UE e.g. for the purpose of IMS precondition. The Packet Filter Set may contain one or more Packet Filter(s). Every Packet Filter is applicable for the DL direction, the UL direction or both directions. NOTE 3: The Packet Filter in the Packet Filter Set of the default QoS rule that allows all UL traffic (also known as match-all Packet Filter) is described in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]. There are two types of Packet Filter Set, i.e. IP Packet Filter Set, and Ethernet Packet Filter Set, corresponding to those PDU Session Types. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.7.6 |
5,406 | 6.3.1.2 Location information | The location information describes the network location of the NF instance. It can consist of one or more levels. Each level describes one location aspect, such as geographic location, data centre, cluster, etc. An NF instance has only one location. The location information may be used to select the NF service instance or NF instance from a particular network location based on local configuration. NOTE: The location information in TS 29.510[ 5G System; Network function repository services; Stage 3 ] [58] specifies the granularity of location information. It is up to each deployment to determine the granularity of location information to be used. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.3.1.2 |
5,407 | 6.4.4.1 NAS input parameters to confidentiality algorithm | The input parameters for the NAS 128-bit ciphering algorithms shall be the same as the ones used for NAS integrity protection as described in clause 6.4.3, with the exception that a different key, KNASenc, is used as KEY, and there is an additional input parameter, namely the length of the key stream to be generated by the encryption algorithms. The use and mode of operation of the 128-bit ciphering algorithms are specified in Annex D. NOTE: In the context of the present subclause 6.4.4, a message is considered ciphered also when the NULL encryption algorithm NEA0 is applied. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.4.4.1 |
5,408 | 6.5.3.5 Abnormal cases in the UE | The following abnormal cases can be identified: a) Expiry of timer T3480: On the first expiry of the timer T3480, the UE shall resend the BEARER RESOURCE ALLOCATION REQUEST and shall reset and restart timer T3480. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3480, the UE shall abort the procedure, release the PTI allocated for this activation and enter the state PROCEDURE TRANSACTION INACTIVE. b) Unknown EPS bearer context Upon receipt of the BEARER RESOURCE ALLOCATION REJECT message including ESM cause #43 "invalid EPS bearer identity", the UE shall deactivate the existing default EPS bearer context locally without peer-to-peer signalling between the UE and the MME and shall stop the timer T3480. c) Collision of a UE requested bearer resource allocation procedure and an EPS bearer context deactivation procedure. When the UE receives a DEACTIVATE EPS BEARER CONTEXT REQUEST message for the default EPS bearer context related to the UE requested bearer resource allocation procedure, the UE shall abort the UE requested bearer resource allocation procedure and shall stop the timer T3480 and proceed with the EPS bearer context deactivation procedure. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.5.3.5 |
5,409 | 4.2.2.2 Registration procedures 4.2.2.2.1 General | A UE needs to register with the network to get authorized to receive services, to enable mobility tracking and to enable reachability. The UE initiates the Registration procedure using one of the following Registration types: - Initial Registration to the 5GS; - Mobility Registration Update upon changing to a new Tracking Area (TA) outside the UE's Registration Area in both CM-CONNECTED and CM-IDLE state, or when the UE needs to update its capabilities or protocol parameters that are negotiated in Registration procedure with or without changing to a new TA, or a change in the UE's Preferred Network Behaviour that would create an incompatibility with the Supported Network Behaviour provided by the serving AMF, or when the UE intends to retrieve LADN Information, or with NR satellite access upon changing to a suitable cell indicating multiple TAs for the RPLMN all of which are outside the UE's Registration Area in both CM-CONNECTED and CM-IDLE state, or when the Multi-USIM UE needs a new 5G-GUTI assignment, or when the UE needs to indicate or returns from an Unavailability Period (see clause 5.4.1.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]), or when the UE using a RAN that provides discontinuous coverage (e.g. for satellite access with discontinuous coverage) is about to leave the satellite network coverage as described in clause 5.4.13.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], or when the UE has informed the network it is unreachable and now returns to coverage using either satellite or terrestrial access as described in clause 5.4.1.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]; or - Periodic Registration Update (due to a predefined time period of inactivity); or - Emergency Registration; or - Disaster Roaming Initial Registration, as specified in clause 5.40 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]; or - Disaster Roaming Mobility Registration Update, as specified in clause 5.40 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]; or - SNPN Onboarding Registration allows the UE to access an ON-SNPN for the purpose of provisioning the UE with SO-SNPN credentials to enable SO-SNPN access. SNPN Onboarding Registration is only applicable for registration with ON-SNPN i.e. when the UE uses PLMN credentials for accessing an ONN the UE initiates an Initial Registration. The SNPN Onboarding Registration is specified in clause 4.2.2.2.4. NOTE 1: With NR satellite access, more than one TAC can be indicated to a UE for each PLMN in any cell. The General Registration call flow in clause 4.2.2.2.2 applies on all these Registration procedures, but the periodic registration need not include all parameters that are used in other registration cases. The following are the cleartext IEs, as defined in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [25] that can be sent by the UE in the Registration Request message if the UE has no NAS security context: - Registration type; - SUCI or 5G-GUTI or PEI; - Security parameters; - additional GUTI; - 4G Tracking Area Update; - the indication that the UE is moving from EPS; - PLMN with Disaster Condition; - if the UE is registering with an SNPN, the NID of the SNPN that assigned the 5G-GUTI. NOTE 2: The NID is provided when the 5G-GUTI is assigned by another SNPN than the selected SNPN. Aspects related to dual registration in 3GPP and non-3GPP access are described in clause 4.12. The general Registration call flow in clause 4.2.2.2.2 is also used for the case of registration in 3GPP access when the UE is already registered in a non-3GPP access and vice versa. Registration in 3GPP access when the UE is already registered in a non-3GPP access scenario may require an AMF change, as further detailed in clause 4.12.8. The general Registration call flow in clause 4.2.2.2.2 is also used by UEs in limited service state (see TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [22]) registering for emergency services only (referred to as Emergency Registration), see clause 5.16.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. During the initial registration the PEI is obtained from the UE. If the PEI is needed (e.g. for EIR check), the AMF shall retrieve the PEI when it establishes the NAS security context with a Security Mode Command during initial registration. The AMF operator may check the PEI with an EIR. If the PEI was retrieved by the AMF (either from the UE or another AMF), AMF shall provide it to the UDM using Nudm_UECM_Registration in order to ensure that the UDM always has the latest PEI available e.g. for reporting event Change of SUPI-PEI association. The AMF passes the PEI to the UDM, to the SMF and the PCF. The UDM may store this data in UDR by Nudr_SDM_Update. NOTE 3: The use of NSI ID in the 5GC is optional and depends on the deployment choices of the operator. During the registration the Home Network (or Credentials Holder in case of access to an SNPN) can provide Steering of Roaming information to the UE via the AMF (i.e. a list of preferred PLMN/access technology combinations and/or Credentials Holder controlled prioritized lists of preferred SNPNs and GINs and/or Credentials Holder controlled prioritized lists of preferred SNPNs and GINs for accessing Localized Services or HPLMN/Credentials Holder indication that 'no change of the above list(s) stored in the UE is needed'). The Home Network can include an indication for the UE to send an acknowledgement of the reception of this information. Details regarding the handling of Steering of Roaming information including how this information is managed between the AMF and the UE are defined in TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [22]. The AMF determines Access Type and RAT Type as defined in clause 5.3.2.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2.2.2 |
5,410 | 5.2.1.2 Receipt of a setup message | In the "null" or "recall present" states, upon receipt of a setup message (a SETUP message or an EMERGENCY SETUP message, see subclause 5.2.1.1), the call control entity of the network enters the "call initiated" state. It shall then analyse the call information contained in the setup message. In Iu mode, network shall include the SI received in the SETUP message into the RABid and send it back to the mobile station. For RABid see 3GPP TS 25.413[ UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling ] [19c] and 3GPP TS 44.118[ None ] [111]. If the network receives the SETUP message with no SI, the network shall set the SI value to 1. i) If, following the receipt of the setup message, the call control entity of the network determines that the call information received from the mobile station is invalid (e.g. invalid number), then the network shall initiate call clearing as defined in subclause 5.4 with one of the following cause values: # 1 "unassigned (unallocated) number", # 3 "no route to destination", # 22 "number changed", # 28 "invalid number format (incomplete number)". ii) If, following the receipt of the setup message, the call control entity of the network determines that a requested service is not authorized or is not available, it shall initiate call clearing in accordance with subclause 5.4.2 with one of the following cause values: # 8 "operator determined barring", # 57 "bearer capability not authorized", # 58 "bearer capability not presently available", # 63 "service or option not available, unspecified", or # 65 "bearer service not implemented". iii) Otherwise, the call control entity of the network shall either: - send a CALL PROCEEDING message to its peer entity to indicate that the call is being processed; and enter the "mobile originating call proceeding" state; - or: send an ALERTING message to its peer entity to indicate that alerting has been started at the called user side; and enter the "call received" state; - or: send a CONNECT message to its peer entity to indicate that the call has been accepted at the called user side; and enter the "connect request" state. The call control entity of the network may insert bearer capability information element(s) in the CALL PROCEEDING message to select options presented by the mobile station in the Bearer Capability information element(s) of the SETUP message. The bearer capability information element(s) shall contain the same parameters as received in the SETUP except those presenting a choice. Where choices were offered, appropriate parameters indicating the results of those choices shall be included. The CALL_PROCEEDING message shall also contain the priority of the call in the case where the network supports eMLPP. Mobile stations supporting eMLPP shall indicate this priority level to higher sublayers and store this information for the duration of the call for further action. Mobile stations not supporting eMLPP shall ignore this information element if provided in a CALL PROCEEDING message. NOTE: If the network supports only R98 or older versions of this protocol and the priority is not included in the CALL PROCEEDING message, this does not imply that the network does not support eMLPP. - The CALL_PROCEEDING message shall contain the multicall supported information in the network call control capabilities in the case where the network supports multicall and there are no other ongoing calls to the MS. Mobile stations supporting multicall shall store this information until the call control state for all calls returns to null. Mobile stations not supporting multicall shall ignore this information if provided in a CALL PROCEEDING message. If the multicall supported information is not sent in the CALL_PROCEEDING message, the mobile station supporting multicall shall regard that the network doesn't support multicall. The call control entity of the network having entered the "mobile originating call proceeding" state, the network may initiate the assignment of a traffic channel according to subclause 5.2.1.9 (early assignment). For speech calls, if the SETUP message or EMERGENCY SETUP message contains a Supported Codec List information element, the network shall use this list to select the codec for UTRAN. If no Supported Codec List information element is received, then for UTRAN the network shall select the default UMTS speech codec according to subclause 5.2.1.11. Codecs for GERAN shall be selected from the codecs indicated in the Supported Codec List information element or in the Bearer Capability information element. If neither a Supported Codec List information element nor a Bearer Capability information element is received, then for GERAN the network shall select GSM full rate speech version 1. Codec information that does not apply to the currently serving radio access shall be used by the network if an inter-system change occurs. Figure 5.2/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Mobile originated call initiation and possible subsequent responses. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.2.1.2 |
5,411 | 4.2.1.1 Selection of the Service State after Power On. | For an eCall only mobile station (as determined by information configured in the USIM), Timers T3242 and T3243 are considered to have expired at power-on. When mobility management is activated after power-on, the service state is 19.7 PLMN SEARCH. The detailed processing in this state is described in detail in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14], 3GPP TS 43.022[ None ] [82], 3GPP TS 45.008[ None ] [34] and 3GPP TS 25.304[ None ] [98], where procedures for power on and selection of PLMN is described in detail. If the "Location update status" stored on the SIM/USIM is different from "updated", then the mobile shall act as if the "Location update status" stored on the SIM/USIM is "not updated". The service state when the PLMN SEARCH state is left depends on the outcome of the search and on the presence of the SIM/USIM: - if no cell has been found, the state is NO CELL AVAILABLE, until a cell is found; - if no SIM/USIM is present the state is NO IMSI; - for an eCall only mobile station (as determined by information configured in USIM), the state is eCALL INACTIVE. - if the mobile station has been continuously activated since loosing coverage and then returns to coverage, and if the selected cell is in the location area where the mobile station is registered and the timer T3212 has not expired, then the state is NORMAL SERVICE; - if the selected cell is in the location area where the mobile station is registered and IMSI ATTACH is not required and timer T3212 has not expired, then the state is NORMAL SERVICE; - if the mobile station is in automatic network selection mode and the selected cell is in a forbidden PLMN, is in a forbidden LA, or is a CSG cell whose CSG ID and associated PLMN identity are not in the Allowed CSG list or in the Operator CSG list stored in the MS, then the mobile station enters the LIMITED SERVICE state; - if the mobile station is in manual network selection mode and no cell of the selected PLMN has been found, or the cell that is found in the selected PLMN is a CSG cell whose CSG ID and associated PLMN identity are not in the Allowed CSG list or in the Operator CSG list stored in the MS, then the mobile station enters the LIMITED SERVICE state; - otherwise, the mobile station enters the LOCATION UPDATE NEEDED state. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.2.1.1 |
5,412 | 10.5.5.5 Detach type | The purpose of the detach type information element is to indicate which type of detach is requested by the MS. In the network to MS direction the detach type information element is used to indicate the reason why a detach request is sent. The detach type is a type 1 information element. The detach type information element is coded as shown in figure 10.5.121/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.138/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.121/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Detach type information element Table 10.5.138/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Detach type 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.5 |
5,413 | 5.5.1.2 Registration procedure for initial registration 5.5.1.2.1 General | This procedure can be used by a UE for initial registration for 5GS services. When the UE initiates the registration procedure for initial registration, the UE shall indicate "initial registration" in the 5GS registration type IE. When the UE initiates the registration procedure for emergency services, the UE shall indicate "emergency registration" in the 5GS registration type IE. When the UE initiates the initial registration for onboarding services in SNPN, the UE shall indicate "SNPN onboarding registration" in the 5GS registration type IE. When the UE initiates the initial registration procedure for disaster roaming services, the UE shall indicate "disaster roaming initial registration" in the 5GS registration type IE. If the MUSIM UE initiates the registration procedure for initial registration and indicates "emergency registration" in the 5GS registration type IE in the REGISTRATION REQUEST message, the network shall not indicate the support of: - the N1 NAS signalling connection release; - the paging indication for voice services; - the reject paging request; or - the paging restriction; in the REGISTRATION ACCEPT message. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.1.2 |
5,414 | – FreqPriorityListSlicing | The IE FreqPriorityListSlicing indicates cell reselection priorities for slicing in SIB16. FreqPriorityListSlicing information element -- ASN1START -- TAG-FREQPRIORITYLISTSLICING-START FreqPriorityListSlicing-r17 ::= SEQUENCE (SIZE (1..maxFreqPlus1)) OF FreqPrioritySlicing-r17 FreqPrioritySlicing-r17 ::= SEQUENCE { dl-ImplicitCarrierFreq-r17 INTEGER (0..maxFreq), sliceInfoList-r17 SliceInfoList-r17 OPTIONAL -- Cond Mandatory } SliceInfoList-r17 ::= SEQUENCE (SIZE (1..maxSliceInfo-r17)) OF SliceInfo-r17 SliceInfo-r17 ::= SEQUENCE { nsag-IdentityInfo-r17 NSAG-IdentityInfo-r17, nsag-CellReselectionPriority-r17 CellReselectionPriority OPTIONAL, -- Need R nsag-CellReselectionSubPriority-r17 CellReselectionSubPriority OPTIONAL, -- Need R sliceCellListNR-r17 CHOICE { sliceAllowedCellListNR-r17 SliceCellListNR-r17, sliceExcludedCellListNR-r17 SliceCellListNR-r17 } OPTIONAL -- Need R } SliceCellListNR-r17 ::= SEQUENCE (SIZE (1..maxCellSlice-r17)) OF PCI-Range -- TAG-FREQPRIORITYLISTSLICING-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,415 | 5.32.2 Multi Access PDU Sessions | A Multi-Access PDU (MA PDU) Session is managed by using the session management functionality specified in clause 5.6, with the following additions and modifications: - When the UE wants to request a new MA PDU Session: - If the UE is registered to the same PLMN over 3GPP and non-3GPP accesses, then the UE shall send a PDU Session Establishment Request over any of the two accesses. The UE also provides Request Type as "MA PDU Request" in the UL NAS Transport message. The AMF informs the SMF that the UE is registered over both accesses and this triggers the establishment of user-plane resources on both accesses and two N3/N9 tunnels between PSA and the RAN/AN. - If the UE is registered to different PLMNs over 3GPP and non-3GPP accesses, then the UE shall send a PDU Session Establishment Request over one access. The UE also provides Request Type as "MA PDU Request" in the UL NAS Transport message. After this PDU Session is established with one N3/N9 tunnel between the PSA and (R)AN established, the UE shall send another PDU Session Establishment Request over the other access. The UE also provides the same PDU Session ID and Request Type as "MA PDU Request" in the UL NAS Transport message. Two N3/N9 tunnels and User-plane resources on both accesses are established. - If the UE is registered over one access only, then the UE shall send a PDU Session Establishment Request over this access. The UE also provides Request Type as "MA PDU Request" in the UL NAS Transport message. One N3/N9 tunnel between the PSA and (R)AN and User-plane resources on this access only are established. After the UE is registered over the second access, the UE shall establish user-plane resources on the second access. - In the PDU Session Establishment Request that is sent to request a new MA PDU Session, the UE shall provide also its ATSSS capabilities, which indicate the steering functionalities and the steering modes supported in the UE. These functionalities are defined in clause 5.32.6. - If the UE indicates it is capable of supporting: - the ATSSS-LL functionality with any steering mode (as specified in clause 5.32.6.1); and the network accepts to activate this functionality, then the network may provide to UE Measurement Assistance Information (see details in clause 5.32.5) and shall provide to UE one or more ATSSS rules. NOTE 1: As specified in Table 5.32.8-1 and in Table 5.8.5.8-1, the ATSSS-LL functionality cannot be used together with the Redundant steering mode. When the UE indicates it is capable of supporting the ATSSS-LL functionality with any steering mode, it is implied that the UE can support the ATSSS-LL functionality with any steering mode except the Redundant steering mode. - If the UE indicates it is capable of supporting: - the MPTCP functionality with any steering mode and the ATSSS-LL functionality with only the Active-Standby steering mode (as specified in clause 5.32.6.1); or - the MPTCP functionality with any steering mode and the ATSSS-LL functionality with any steering mode (as specified in clause 5.32.6.1); and the network accepts to activate these functionalities, then the network provides MPTCP proxy information to UE, and allocates to UE (a) one IP address/prefix for the MA PDU session (as defined in clause 5.8.2.2) and (b) two additional IP addresses/prefixes, called "MPTCP link-specific multipath" addresses. Further details are provided in clause 5.32.6.2.1. In addition, the network may provide to UE Measurement Assistance Information and shall provide to UE one or more ATSSS rules. If the UE supports the ATSSS-LL functionality with only the Active-Standby steering mode, the network shall provide to UE an ATSSS rule for non-MPTCP traffic. The ATSSS rule for non-MPTCP traffic shall use the ATSSS-LL functionality and the Active-Standby Steering Mode to indicate how the non-MPTCP traffic shall be transferred across the 3GPP access and the non-3GPP access in the uplink direction. - If the UE indicates it is capable of supporting - the MPQUIC functionality with any steering mode and the ATSSS-LL functionality with only the Active-Standby steering mode (as specified in clause 5.32.6.1); or - the MPQUIC functionality with any steering mode and the ATSSS-LL functionality with any steering mode (as specified in clause 5.32.6.1); and the network accepts to activate these functionalities, then the network provides MPQUIC proxy information to UE, and allocates to UE (a) one IP address/prefix for the MA PDU session (as defined in clause 5.8.2.2) and (b) two additional IP addresses/prefixes, called "MPQUIC link-specific multipath" addresses. Further details are provided in clause 5.32.6.2.2. In addition, the network may provide to UE Measurement Assistance Information and shall provide to UE one or more ATSSS rules. If the UE supports the ATSSS-LL functionality with only the Active-Standby steering mode, the network shall provide to UE an ATSSS rule for non-MPQUIC traffic. The ATSSS rule for non-MPQUIC traffic shall use the ATSSS-LL functionality and the Active-Standby Steering Mode to indicate how the non-MPQUIC traffic shall be transferred across the 3GPP access and the non-3GPP access in the uplink direction. - If the UE indicates it is capable of supporting - the MPTCP functionality with any steering mode, and the MPQUIC functionality with any steering mode, and the ATSSS-LL functionality with only the Active-Standby steering mode (as specified in clause 5.32.6.1); or - the MPTCP functionality with any steering mode, and the MPQUIC functionality with any steering mode, and the ATSSS-LL functionality with any steering mode (as specified in clause 5.32.6.1); and the network accepts to activate these functionalities, then the network provides MPTCP proxy information and MPQUIC proxy information to UE and allocates to UE (a) one IP address/prefix for the MA PDU session (as defined in clause 5.8.2.2), (b) two additional IP addresses/prefixes, called "MPTCP link-specific multipath" addresses, and (c) two additional IP addresses/prefixes, called "MPQUIC link-specific multipath" addresses. Further details are provided in clause 5.32.6.2.1 and in clause 5.32.6.2.2. In addition, the network may provide to UE Measurement Assistance Information and shall provide to UE one or more ATSSS rules. If the UE supports the ATSSS-LL functionality with only the Active-Standby steering mode, the network shall provide to UE an ATSSS rule for non-MPTCP and non-MPQUIC traffic (i.e. the traffic for which neither the MPTCP nor the MPQUIC functionalities are applied). The ATSSS rule for non-MPTCP and non-MPQUIC traffic shall use the ATSSS-LL functionality and the Active-Standby Steering Mode to indicate how the non-MPTCP and non-MPQUIC traffic shall be transferred across the 3GPP access and the non-3GPP access in the uplink direction. NOTE 2: The "MPTCP link-specific multipath" addresses and the "MPQUIC link-specific multipath" addresses can be the same. - If the UE requests an S-NSSAI, this S-NSSAI should be allowed on both accesses. Otherwise, the MA PDU Session shall not be established. - The SMF determines the ATSSS capabilities supported for the MA PDU Session based on the ATSSS capabilities provided by the UE and per DNN configuration on SMF, as follows: a) If the UE includes in its ATSSS capabilities "MPTCP functionality with any steering mode and ATSSS-LL functionality with only Active-Standby steering mode" (as specified in clause 5.32.6.1), then: i) If the DNN configuration allows MPTCP and ATSSS-LL with any steering mode (i.e. any Steering Mode allowed for ATSSS-LL), including RTT measurement without using PMF protocol, the MA PDU Session is capable of (1) MPTCP and ATSSS-LL with any steering mode (i.e. any Steering Mode allowed for ATSSS-LL) in the downlink, and (2) MPTCP and ATSSS-LL with Active-Standby mode in the uplink. NOTE 3: In this case, it is assumed that ATSSS-LL with "Smallest Delay" steering mode is selected for the downlink only when the UPF can measure RTT without using the PMF protocol, e.g. by using other means not defined by 3GPP such as using the RTT measurements of MPTCP. ii) If the DNN configuration allows MPTCP and ATSSS-LL with any steering mode (i.e. any Steering Mode allowed for ATSSS-LL), but not RTT measurement without using PMF protocol, the MA PDU Session is capable of (1) MPTCP in the downlink (2) ATSSS-LL with any steering mode (i.e. any Steering Mode allowed for ATSSS-LL) in the downlink, and (3) MPTCP and ATSSS-LL with Active-Standby mode in the uplink. iii) If the DNN configuration allows MPTCP with any steering mode and ATSSS-LL with only Active-Standby steering mode, the MA PDU Session is capable of MPTCP and ATSSS-LL with Active-Standby mode in the uplink and in the downlink. b) If the UE includes in its ATSSS capabilities "MPQUIC functionality with any steering mode and ATSSS-LL functionality with only Active-Standby steering mode" (as specified in clause 5.32.6.1), then: i) If the DNN configuration allows MPQUIC and ATSSS-LL with any steering mode (i.e. any Steering Mode allowed for ATSSS-LL), including RTT measurement without using PMF protocol, the MA PDU Session is capable of (1) MPQUIC and ATSSS-LL with any steering mode (i.e. any Steering Mode allowed for ATSSS-LL) in the downlink, and (2) MPQUIC and ATSSS-LL with Active-Standby mode in the uplink. NOTE 4: In this case, it is assumed that ATSSS-LL with "Smallest Delay" steering mode is selected for the downlink only when the UPF can measure RTT without using the PMF protocol, e.g. by using other means not defined by 3GPP such as using the RTT measurements of MPQUIC. ii) If the DNN configuration allows MPQUIC and ATSSS-LL with any steering mode (i.e. any Steering Mode allowed for ATSSS-LL), but not RTT measurement without using PMF protocol, the MA PDU Session is capable of (1) MPQUIC in the downlink (2) ATSSS-LL with any steering mode (i.e. any Steering Mode allowed for ATSSS-LL) in the downlink, and (3) MPQUIC and ATSSS-LL with Active-Standby mode in the uplink. iii) If the DNN configuration allows MPQUIC with any steering mode and ATSSS-LL with only Active-Standby steering mode, the MA PDU Session is capable of MPQUIC and ATSSS-LL with Active-Standby mode in the uplink and in the downlink. c) If the UE includes in its ATSSS capabilities "MPQUIC functionality with any steering mode and ATSSS-LL functionality with any steering mode" (as specified in clause 5.32.6.1), and the DNN configuration allows MPQUIC and ATSSS-LL with any steering mode (i.e. any Steering Mode allowed for ATSSS-LL), the MA PDU Session is capable of MPQUIC and ATSSS-LL with any steering mode (i.e. any Steering Mode allowed for ATSSS-LL) in the uplink and in the downlink. d) If the UE includes in its ATSSS capabilities "ATSSS-LL functionality with any steering mode" (as specified in clause 5.32.6.1) and the DNN configuration allows ATSSS-LL with any steering mode allowed for ATSSS-LL, the MA PDU Session is capable of ATSSS-LL with any steering mode allowed for ATSSS-LL in the uplink and in the downlink. e) If the UE includes in its ATSSS capabilities "MPTCP functionality with any steering mode and ATSSS-LL functionality with any steering mode" (as specified in clause 5.32.6.1), and the DNN configuration allows MPTCP and ATSSS-LL with any steering mode (i.e. any Steering Mode allowed for ATSSS-LL), the MA PDU Session is capable of MPTCP and ATSSS-LL with any steering mode (i.e. any Steering Mode allowed for ATSSS-LL) in the uplink and in the downlink. f) If the UE includes in its ATSSS capabilities "MPTCP functionality with any steering mode, and the MPQUIC functionality with any steering mode, and the ATSSS-LL functionality with any steering mode" (as specified in clause 5.32.6.1), and the DNN configuration allows MPTCP and MPQUIC and ATSSS-LL with any steering mode (i.e. any Steering Mode allowed for ATSSS-LL), the MA PDU Session is capable of MPTCP and MPQUIC and ATSSS-LL with any steering mode (i.e. any Steering Mode allowed for ATSSS-LL) in the uplink and in the downlink. g) If the UE includes in its ATSSS capabilities "MPTCP functionality with any steering mode, and the MPQUIC functionality with any steering mode, and the ATSSS-LL functionality with only the Active-Standby steering mode" (as specified in clause 5.32.6.1), then: i) If the DNN configuration allows MPTCP and MPQUIC and ATSSS-LL with any steering mode (i.e. any Steering Mode allowed for ATSSS-LL), including RTT measurement without using PMF protocol, the MA PDU Session is capable of (1) MPTCP and MPQUIC and ATSSS-LL with any steering mode (i.e. any Steering Mode allowed for ATSSS-LL) in the downlink, and (2) MPTCP and MPQUIC and ATSSS-LL with Active-Standby mode in the uplink. NOTE 5: In this case, it is assumed that ATSSS-LL with "Smallest Delay" steering mode is selected for the downlink only when the UPF can measure RTT without using the PMF protocol, e.g. by using other means not defined by 3GPP such as using the RTT measurements of MPTCP or MPQUIC. ii) If the DNN configuration allows MPTCP and MPQUIC and ATSSS-LL with any steering mode (i.e. any Steering Mode allowed for ATSSS-LL), but not RTT measurement without using PMF protocol, the MA PDU Session is capable of (1) MPTCP and MPQUIC in the downlink (2) ATSSS-LL with any steering mode (i.e. any Steering Mode allowed for ATSSS-LL) in the downlink, and (3) MPTCP and MPQUIC and ATSSS-LL with Active-Standby mode in the uplink. iii) If the DNN configuration allows MPTCP and MPQUIC with any steering mode and ATSSS-LL with only Active-Standby steering mode, the MA PDU Session is capable of MPTCP and MPQUIC and ATSSS-LL with Active-Standby mode in the uplink and in the downlink. The SMF provides the ATSSS capabilities of the MA PDU Session to the PCF during PDU Session Establishment. - The PCC rules provided by PCF include MA PDU Session Control information (see TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]). They are used by SMF to derive ATSSS rules for the UE and N4 rules for the UPF. When dynamic PCC is not used for the MA PDU Session, the SMF shall provide ATSSS rules and N4 rules based on local configuration (e.g. based on DNN or S-NSSAI). - The UE receives ATSSS rules from SMF, which indicate how the uplink traffic should be routed across 3GPP access and non-3GPP access. Similarly, the UPF receives N4 rules from SMF, which indicate how the downlink traffic should be routed across 3GPP access and non-3GPP access. - When the SMF receives a PDU Session Establishment Request and a "MA PDU Request" indication and determines that UP security protection (see clause 5.10.3) is required for the PDU Session, the SMF shall only confirm the establishment of the MA PDU session if the 3GPP access network can enforce the required UP security protection. The SMF needs not confirm whether the non-3GPP access can enforce the required UP security protection. - The UE indicates during MA PDU Session Establishment to the AMF whether it supports non-3GPP access path switching, i.e. whether the UE can transfer the non-3GPP access path of the MA PDU Session from a source non-3GPP access (N3IWF/TNGF) to a target non-3GPP access (a different N3IWF/TNGF). If the UE has indicated support for non-3GPP access path switching and the AMF supports non-3GPP access path switching, the AMF selects an SMF that supports non-3GPP access path switching, if such an SMF is available. If the AMF supports to maintain two N2 connections for non-3GPP access during the Registration procedure and the selected SMF supports non-3GPP path switching, the AMF indicates whether the UE supports non-3GPP path switching to the SMF. The SMF indicates support for non-3GPP path switching to the UE in the PDU Session Establishment Accept message. NOTE 6: If the AMF selects an SMF not supporting non-3GPP access path switching, the non-3GPP access path switching can still be performed with the AMF triggering release of the old user plane resources before new user plane resources are established. - After the MA PDU Session establishment: - At any given time, the MA PDU session may have user-plane resources on both 3GPP and non-3GPP accesses, or on one access only, or may have no user-plane resources on any access. - The AMF, SMF, PCF and UPF maintain their MA PDU Session contexts, even when the UE deregisters from one access (but remains registered on the other access). - When the UE deregisters from one access (but remains registered on the other access), the AMF informs the SMF to release the resource of this access type in the UPF for the MA PDU Session. Subsequently, the SMF notifies the UPF that the access type has become unavailable and the N3/N9 tunnel for the access type are released. - If the UE wants to add user-plane resources on one access of the MA PDU Session, e.g. based on access network performance measurement and/or ATSSS rules, then the UE shall send a PDU Session Establishment Request over this access containing PDU Session ID of the MA PDU Session. The UE also provides Request Type as "MA PDU Request" and the same PDU Session ID in the UL NAS Transport message. If there is no N3/N9 tunnel for this access, the N3/N9 tunnel for this access is established. - If the UE wants to re-activate user-plane resources on one access of the MA PDU Session, e.g. based on access network performance measurement and/or ATSSS rules, then the UE shall initiate the UE Triggered Service Request procedure over this access. - If the network wants to re-activate the user-plane resources over 3GPP access or non-3GPP access of the MA PDU Session, the network shall initiate the Network Triggered Service Request procedure, as specified in clause 4.22.7 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. - If the UE wants to move the non-3GPP user-plane resources of the MA PDU Session from a source non-3GPP access (e.g. source N3IWF or TNGF) to a target non-3GPP access (e.g. target N3IWF or TNGF), the UE initiates a Mobility Registration Update via the target non-3GPP access as described in TS 23.502[ Procedures for the 5G System (5GS) ] [3], clause 4.22.9.5. This procedure may also be used to move the non-3GPP user-plane resources of single access PDU Session(s). NOTE 7: The UE can request activation of single access PDU Session(s) over the target non-3GPP access while performing Mobility Registration Update procedure according to the existing procedure. - The SMF may add, remove or update one or more individual ATSSS rules of the UE by sending new or updated ATSSS rules with the corresponding Rule IDs to the UE. A MA PDU Session may be established either: a) when it is explicitly requested by an ATSSS-capable UE; or b) when an ATSSS-capable UE requests a single-access PDU Session but the network decides to establish a MA PDU Session instead. This is an optional scenario specified in clause 4.22.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3], which may occur when the UE requests a single-access PDU Session but no policy (e.g. no URSP rule) and no local restrictions in the UE mandate a single access for the PDU Session. A MA PDU Session may be established during a PDU Session modification procedure when the UE moves from EPS to 5GS, as specified in clause 4.22.6.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. The AMF indicates as part of the Registration procedure whether ATSSS is supported or not. When ATSSS is not supported, the UE shall not - request establishment of a MA PDU Session (as described in clause 4.22.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]); or - request addition of User Plane resources for an existing MA PDU Session (as described in clause 4.22.7 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]); or - request establishment of a PDU Session with "MA PDU Network-Upgrade Allowed" indication (as described in clause 4.22.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]); or - request PDU Session Modification with Request Type of "MA PDU request" or with "MA PDU Network-Upgrade Allowed" indication after moving from EPC to 5GC (as described in clause 4.22.6.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]). The AMF indicates as part of the Registration procedure whether it supports non-3GPP access path switching. When the AMF does not indicate support of non-3GPP access path switching, the UE shall not perform the Mobility Registration Update procedure for non-3GPP access path switching, i.e. to switch traffic from a source non-3GPP access to a target non-3GPP access. The SMF indicates as part of the PDU Session Establishment procedure whether it supports non-3GPP access path switching. If the UE has more than one PDU session and at least one serving SMF for the PDU Sessions supports non-3GPP access path switching, the UE may include ("Non-3GPP path switching while using old AN resources") indication when the UE performs the Mobility Registration Update procedure for non-3GPP access path switching. If the UE is registered to different PLMNs over 3GPP and non-3GPP accesses, the UE shall use the capability received over non-3GPP access to determine whether to perform the Mobility Registration Update procedure for non-3GPP path switching and whether to include ("Non-3GPP access path switching while using old AN resources") indication. NOTE 8: If the AMF receives ("Non-3GPP path switching while using old AN resources") indication from Mobility Registration Update procedure, and the serving SMF(s) for PDU Session(s) is not supporting non-3GPP access path switching, the non-3GPP access path switching can still be performed with the AMF triggering for each PDU Session the release of the old user plane resources before new user plane resources are established. An ATSSS-capable UE may decide to request a MA PDU Session based on the provisioned URSP rules. In particular, the UE should request a MA PDU Session when the UE applies a URSP rule, which triggers the UE to establish a new PDU Session and the Access Type Preference component of the URSP rule indicates "Multi-Access" (see TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]). | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.32.2 |
5,416 | 5.5.4.21 Event H1 (The Aerial UE altitude becomes higher than a threshold) | The UE shall: 1> consider the entering condition for this event to be satisfied when condition H1-1, as specified below, is fulfilled; 1> consider the leaving condition for this event to be satisfied when condition H1-2, as specified below, is fulfilled; Inequality H1-1 (Entering condition) Ms – Hys > Thresh Inequality H1-2 (Leaving condition) Ms + Hys < Thresh The variables in the formula are defined as follows: Ms is the Aerial UE altitude relative to the sea level. Hys is the hysteresis parameter for this event (i.e. h1-Hysteresis as defined within reportConfigNR for this event). Thresh is the threshold parameter for this event (i.e. h1-Threshold as defined within reportConfigNR for this event). Ms, Hys, Thresh are expressed in meters. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.5.4.21 |
5,417 | 6.4.2.6 Abnormal cases on the network side | The following abnormal cases can be identified: a) If the PDU session is an emergency PDU session and the 5GSM cause IE is not included in the PDU SESSION MODIFICATION REQUEST message which is not triggered according to subclause 6.4.2.1, item e), or is set to a 5GSM cause other than the 5GSM causes #41, #42, #44, #45, #83, #84, and #85, the SMF shall reject the PDU SESSION MODIFICATION REQUEST message with 5GSM cause #31 "request rejected, unspecified". b) PDU session inactive for the received PDU session identity. If the PDU session ID in the PDU SESSION MODIFICATION REQUEST message belongs to any PDU session in state PDU SESSION INACTIVE in the SMF, the SMF shall set the 5GSM cause IE to #43 "Invalid PDU session identity" in the PDU SESSION MODIFICATION REJECT message. c) Collision of network-requested PDU session modification procedure and UE-requested PDU session modification procedure. The handling of the same abnormal case as described in subclause 6.3.2.5 applies. d) AMF provides a "message was exempted from the DNN based congestion activated in the AMF" but the UE-requested PDU session modification procedure is not exempt from DNN based congestion control. If the SMF receives an exemptionInd attribute indicating "message was exempted from the DNN based congestion activated in the AMF" as specified in 3GPP TS 29.502[ 5G System; Session Management Services; Stage 3 ] [20A], and the Extended protocol configuration options IE of the PDU SESSION MODIFICATION REQUEST message does not indicate 3GPP PS data off UE status, then the SMF shall set the 5GSM cause #26 "insufficient resources" in the PDU SESSION MODIFICATION REJECT message. e) AMF provides a "message was exempted from the S-NSSAI and DNN based congestion activated in the AMF" but the UE-requested PDU session modification procedure is not exempt from S-NSSAI only based congestion control. If the SMF receives an exemptionInd attribute indicating "message was exempted from the S-NSSAI and DNN based congestion activated in the AMF" as specified in 3GPP TS 29.502[ 5G System; Session Management Services; Stage 3 ] [20A], and the Extended protocol configuration options IE of the PDU SESSION MODIFICATION REQUEST message does not indicate 3GPP PS data off UE status, then the SMF shall set the 5GSM cause #67 "insufficient resources for specific slice and DNN" in the PDU SESSION MODIFICATION REJECT message. f) AMF provides a "message was exempted from the S-NSSAI only based congestion activated in the AMF" but the UE-requested PDU session modification procedure is not exempt from S-NSSAI only based congestion control. If the SMF receives an exemptionInd attribute indicating "message was exempted from the S-NSSAI only based congestion activated in the AMF" as specified in 3GPP TS 29.502[ 5G System; Session Management Services; Stage 3 ] [20A], and the Extended protocol configuration options IE of the PDU SESSION MODIFICATION REQUEST message does not indicate 3GPP PS data off UE status, then the SMF shall set the 5GSM cause #69 "insufficient resources for specific slice" in the PDU SESSION MODIFICATION REJECT message. g) 5G access network cannot forward the message. If the SMF determines based on content of the n2SmInfo attribute specified in 3GPP TS 29.502[ 5G System; Session Management Services; Stage 3 ] [20A] that the DL NAS TRANSPORT message carrying the PDU SESSION MODIFICATION COMMAND message was not forwarded to the UE by the 5G access network due to a cause other than handover procedure in progress, then the SMF shall reject the UE-requested PDU session modification procedure with an appropriate 5GSM cause value in the PDU SESSION MODIFICATION REJECT message. NOTE: The use of an appropriate 5GSM cause value is implementation specific. | 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.4.2.6 |
5,418 | 12.7.2 NID of assignment mode 0 | The NID value of a NID of the assignment mode 0 consists of a NID PEN and a NID code, as shown in figure 12.7.2-1. The NID PEN is a private enterprise number issued to service provider of the SNPN by Internet Assigned Numbers Authority (IANA) in its capacity as the private enterprise number administrator, as maintained at https://www.iana.org/assignments/enterprise-numbers/enterprise-numbers Note: The private enterprise number issued by IANA is a decimal number that needs to be converted to a fixed length 8 digit hexadecimal number when used within the NID. E.g. 32473 is converted to 00007ed9. The NID code identifies the SNPN within the service provider identified by the NID PEN. Figure 12.7.2-1: NID of assignment mode 0 | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 12.7.2 |
5,419 | 10.5.5.4 TMSI status | The purpose of the TMSI status information element is to indicate whether a valid TMSI is available in the MS or not. The TMSI status is a type 1 information element. The TMSI status information element is coded as shown in figure 10.5.120/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.137/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.120/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : TMSI status information element Table 10.5.137/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : TMSI status 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.4 |
5,420 | 6.3.6.3 Combined N3IWF/ePDG Selection | When the UE wants to select a non-3GPP access node (either an N3IWF or an ePDG), the UE shall perform the following procedure: 1) The UE shall attempt to determine the country it is located in. This is determined by implementation-specific methods not defined in this specification. If the UE cannot determine the country it is located in, the UE shall stop the non-3GPP access node selection. 2) If the UE determines to be located in its home country, then: a) The UE shall select the HPLMN. If the UE fails to connect to an ePDG/N3IWF in the HPLMN, then the UE shall stop the non-3GPP access node selection. 3) If the UE determines to be located in a country other than its home country (called the visited country), then: a) If the UE is registered via 3GPP access to a PLMN and this PLMN is included in the Non-3GPP access node selection information, then the UE shall select this PLMN. If the UE fails to connect to an ePDG/N3IWF in this PLMN, the UE shall select another PLMN by performing the DNS procedure specified in bullet 3c) below. b) In all other cases, (e.g. when the UE is not configured with the Non-3GPP access node selection information, or the UE is registered via 3GPP access to a PLMN but this PLMN is not included in the Non-3GPP access node selection information, or the UE is not registered via 3GPP access to any PLMN), the UE shall select a PLMN by performing the DNS procedure specified in bullet 3c) below. c) The UE shall select a PLMN as follows: i) The UE shall determine if the non-3GPP access node selection is required for an IMS service or for a non-IMS service. The means of that determination are implementation specific. ii) If the UE determines that the non-3GPP access node selection is required for a non-IMS service, the UE shall select a PLMN as specified in clause 6.3.6.2. As defined below, if the UE fails to connect to an N3IWF in any PLMN, the UE may attempt to select an ePDG according to the procedure specified in clause 4.5.4.5 of TS 23.402[ Architecture enhancements for non-3GPP accesses ] [43]. iii) If the UE determines that the non-3GPP access node selection is required for an IMS service, the UE shall select a PLMN as follows: - First, the UE shall perform a DNS query using the Visited Country FQDN for N3IWF, as specified in TS 23.003[ Numbering, addressing and identification ] [19] to determine if the visited country mandates the selection of N3IWF in this country. The DNS response received by the UE may be empty or may contain the identities of one or more PLMNs in the visited country, which may be used for N3IWF selection, if the UE decides to select an N3IWF, as specified below. For example, the DNS response may contain the identity of PLMN-1 and the identity of PLMN-2. - Then, the UE shall perform a DNS query using the Visited Country FQDN for ePDG, as specified in TS 23.003[ Numbering, addressing and identification ] [19] to determine if the visited country mandates the selection of ePDG in this country. The DNS response received by the UE may be empty or may contain the identities of one or more PLMNs in the visited country, which may be used for ePDG selection, if the UE decides to select an ePDG, as specified below. For example, the DNS response may contain the identity of PLMN-1 and the identity of PLMN-3. - If the UE does not receive a DNS response in none of the above two DNS queries, then the UE shall stop the non-3GPP access node selection. Otherwise, the next steps are executed. - The UE shall consolidate the PLMN identities received in the above two DNS responses and shall construct a candidate list of PLMNs. For example, the candidate list of PLMNs may contain the identities of PLMN-1, PLMN-2, PLMN-3. - If the candidate list of PLMNs is empty, then: - If the Non-3GPP access node selection information contains one or more PLMNs in the visited country, the UE shall select one of these PLMNs based on their priorities in the Non-3GPP access node selection information. If the UE fails to connect to a non-3GPP access node in any of these PLMNs, the UE shall select the HPLMN. - Otherwise, the UE shall select the HPLMN. - If the candidate list of PLMNs is not empty, then: - If the UE is registered via 3GPP access to a PLMN which is included in the candidate list of PLMNs, then the UE shall select this PLMN. If the UE fails to connect to a non-3GPP access node in this PLMN, then the UE shall select a different PLMN included in the candidate list of PLMNs as specified in the next bullet. - If the UE is registered via 3GPP access to a PLMN which is not included in the candidate list of PLMNs, or the UE is not registered via 3GPP access to any PLMN, or the UE fails to connect to a non-3GPP access node according to the previous bullet, then the UE shall select one of the PLMNs included in the candidate list of PLMNs based on the prioritized list of PLMNs in the Non-3GPP access node selection information (i.e. the UE shall select first the highest priority PLMN in the Non-3GPP access node selection information that is contained in the candidate list of PLMNs). If the Non-3GPP access node selection information does not contain any of the PLMNs in the candidate list of PLMNs, or the UE is not configured with the Non-3GPP access node selection information, or the UE was not able to connect to a non-3GPP access node in any of the PLMNs included in the Non-3GPP access node selection information and in the candidate list of PLMN, then the UE shall select a PLMN included in the candidate list of PLMNs based on its own implementation means. - If the UE cannot select a non-3GPP access node in any of the PLMNs included in the candidate list of PLMNs, then the UE shall stop the non-3GPP access node selection. In the selected PLMN the UE shall attempt to select a non-3GPP access node as follows: 1. The UE shall determine if the non-3GPP access node selection is required for an IMS service or for a non-IMS service. The means of that determination are implementation-specific. 2. When the selection is required for an IMS service, the UE shall choose a non-3GPP access node type (i.e. ePDG or N3IWF) based on the "Preference" parameter specified in clause 6.3.6.1, unless the UE has its 5GS capability disabled in which case it shall choose an ePDG independent of the "Preference" parameter setting. If the "Preference" parameter for the selected PLMN indicates that ePDG is preferred, the UE shall attempt to select an ePDG. If the "Preference" parameter for the selected PLMN indicates that N3IWF is preferred, the UE shall attempt to select an N3IWF. If the selection fails, including the case when, during the registration performed over either 3GPP or non-3GPP access, the UE receives the IMS Voice over PS session Not Supported over Non-3GPP Access indication (specified in clause 5.16.3.2a), the UE shall attempt selecting the other non-3GPP access node type in the selected PLMN, if any. If that selection fails too, or it is not possible, then the UE shall select another PLMN, according to the procedure specified bullet 3c) above. 3. When the selection is required for a non-IMS service, the UE shall perform the selection by giving preference to the N3IWF independent of the "Preference" parameter setting. If the N3IWF selection fails, or it is not possible, the UE should select another PLMN based on the procedure specified in clause 4.5.4.4 of TS 23.402[ Architecture enhancements for non-3GPP accesses ] [43], and shall attempt to select an N3IWF in this PLMN. If the UE fails to select an N3IWF in any PLMN, the UE may attempt to select an ePDG according to the procedure specified in clause 4.5.4.5 of TS 23.402[ Architecture enhancements for non-3GPP accesses ] [43]. In the above procedure, when the UE attempts to construct a Tracking/Location Area Identifier FQDN either for ePDG selection or for N3IWF selection, the UE shall use the Tracking Area wherein the UE is located and shall construct either: - an ePDG or N3IWF TAI FQDN based on the 5GS TAI, when the UE is registered to the 5GS; or - an ePDG or N3IWF TAI FQDN based on the EPS TAI, when the UE is registered to EPS. NOTE: A UE performing both a selection for an IMS service and a selection for a non-IMS service could get simultaneously attached to a N3IWF and to an ePDG in the same PLMN or in different PLMNs. If the UE is configured with Slice-specific N3IWF prefix configuration, then the UE shall construct the Prefixed N3IWF OI FQDN or the Prefixed N3IWF TA FQDN as specified in TS 23.003[ Numbering, addressing and identification ] [19] instead of the N3IWF OI FQDN and the N3IWF TA FQDN, respectively. Further details on constructing the Prefixed N3IWF OI and TA FQDN are described in clause 6.3.6.2. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.3.6.3 |
5,421 | 6.1.3.6a Extended Power Headroom Report MAC Control Elements | For extendedPHR, the Extended Power Headroom Report (PHR) MAC control element is identified by a MAC PDU subheader with LCID as specified in table 6.2.1-2. It has a variable size and is defined in Figure 6.1.3.6a-2. When Type 2 PH is reported, the octet containing the Type 2 PH field is included first after the octet indicating the presence of PH per SCell and followed by an octet containing the associated PCMAX,c field (if reported). Then follows an octet with the Type 1 PH field and an octet with the associated PCMAX,c field (if reported), for the PCell. If SRS-ConfigAdd-r16 is configured for the PCell then follows an octet with the Type 3 PH field and an octet with the associated PCMAX,c field (if reported), for the PCell. And then follows in ascending order based on the ServCellIndex, as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8] an octet with the Type x PH field, wherein x is equal to 3 when the ul-Configuration-r14 or SRS-ConfigAdd-r16 is configured for this SCell, x is equal to 1 otherwise, and an octet with the associated PCMAX,c field (if reported), for each SCell indicated in the bitmap. For extendedPHR2, the Extended Power Headroom Report (PHR) MAC control elements are identified by a MAC PDU subheader with LCID as specified in table 6.2.1-2. They have variable sizes and are defined in Figure 6.1.3.6a1-3, Figure 6.1.3.6a2-4 and Figure 6.1.3.6a3-5. One octet with C fields is used for indicating the presence of PH per SCell when the highest SCellIndex of SCell with configured uplink is less than 8, otherwise four octets are used. When Type 2 PH is reported for the PCell, the octet containing the Type 2 PH field is included first after the octet(s) indicating the presence of PH per SCell and followed by an octet containing the associated PCMAX,c field (if reported). Then follows the Type 2 PH field for the PUCCH SCell (if PUCCH on SCell is configured and Type 2 PH is reported for the PUCCH SCell), followed by an octet containing the associated PCMAX,c field (if reported). Then follows an octet with the Type 1 PH field and an octet with the associated PCMAX,c field (if reported), for the PCell. If SRS-ConfigAdd-r16 is configured for the PCell then follows an octet with the Type 3 PH field and an octet with the associated PCMAX,c field (if reported), for the PCell. Then follows in ascending order based on the ServCellIndex, as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8] an octet with the Type x PH field, wherein, x is equal to 3 when the ul-Configuration-r14 or SRS-ConfigAdd-r16 is configured for this SCell, x is equal to 1 otherwise, and an octet with the associated PCMAX,c field (if reported), for each SCell indicated in the bitmap. The Extended PHR MAC Control Elements are defined as follows: - Ci: this field indicates the presence of a PH field for the SCell with SCellIndex i as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]. The Ci field set to "1" indicates that a PH field for the SCell with SCellIndex i is reported. The Ci field set to "0" indicates that a PH field for the SCell with SCellIndex i is not reported; - R: reserved bit, set to "0"; - V: this field indicates if the PH value is based on a real transmission or a reference format. For Type 1 PH, V=0 indicates real transmission on PUSCH and V=1 indicates that a PUSCH reference format is used. For Type 2 PH, V=0 indicates real transmission on PUCCH/SPUCCH and V=1 indicates that a PUCCH/SPUCCH reference format is used. For Type 3 PH, V=0 indicates real transmission on SRS and V=1 indicates that an SRS reference format is used. Furthermore, for Type 1, Type 2 and Type 3 PH, V=0 indicates the presence of the octet containing the associated PCMAX,c field, and V=1 indicates that the octet containing the associated PCMAX,c field is omitted; - Power Headroom (PH): this field indicates the power headroom level. The length of the field is 6 bits. The reported PH and the corresponding power headroom levels are shown in Table 6.1.3.6-1 (the corresponding measured values in dB can be found in clause 9.1.8.4 of TS 36.133[ Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for support of radio resource management ] [9]); - P: this field indicates whether the MAC entity applies power backoff due to power management (as allowed by P-MPRc, see TS 36.101[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception ] [10]). The MAC entity shall set P=1 if the corresponding PCMAX,c field would have had a different value if no power backoff due to power management had been applied; - PCMAX,c: if present, this field indicates the PCMAX,c or , as specified in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2] used for calculation of the preceding PH field. The reported PCMAX,c and the corresponding nominal UE transmit power levels are shown in Table .6a-1 (the corresponding measured values in dBm can be found in clause of TS 36.133[ Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for support of radio resource management ] [9]). Figure 6.1.3.6a-1: Void Figure 6.1.3.6a-2: Extended PHR MAC Control Element Figure 6.1.3.6a1-3: Extended PHR MAC Control Element supporting PUCCH on SCell Figure 6.1.3.6a2-4: Extended PHR MAC Control Element supporting 32 serving cells with configured uplink Figure 6.1.3.6a3-5: Extended PHR MAC Control Element supporting 32 serving cells with configured uplink and PUCCH on SCell Table .6a-1: Nominal UE transmit power level for Extended PHR and for Dual Connectivity PHR | 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.6a |
5,422 | N.5 Support for leaving network that provides access to Localized Services | When Localized Services in a network are completed, all UEs that are registered with the network are expected to be transferred to other network or to other network resources (e.g. other cells) within the same network, potentially within a relatively short timeframe. The other network can be HPLMN, VPLMN or another SNPN. UE can stop using the network resources for Localized Services for numerous reasons, e.g. when one or more of the following conditions apply: - Localized Services in a network are completed. - Validity conditions of network selection information are no longer met. - The user decides to stop using the Localized Services before they are completed. - A policy decision is taken by the network, with the effect that the UE is deregistered before the Localized Services are completed. NOTE: The list is not an exhaustive list and UE can stop using the network resources for Localized Services due to other reasons e.g. UE loses coverage, power off. When large number of UEs move to other network (i.e. HPLMN, VPLMN or another SNPN) or other network resources within a relatively short timeframe, the total signalling involved can cause signalling overload in the target network. Existing mechanisms for Control Plane Load Control, Congestion and Overload Control described in clause 5.19 and access control and barring described in clause 5.2.5 can be used to mitigate the signalling overload caused by returning UEs. For further enhancement of mitigation of signalling overload, additional mechanisms can be implemented to ensure spreading of the load that returning UEs cause. Such mechanisms are implementation-specific, but some guidelines that can be considered are described below: - The time validity of the network selection information given to a UE can be set somewhat longer than the actual duration of the service, e.g. users will by themselves disable Localized Service and the UE then stops using the connectivity to access the Localized Service, thus causing the UE to be moved, e.g. by performing normal network selection. - The time validity of the network selection information given to a UE can be different for each UE so that each UE performs network selection at a different time to distribute returning UEs. - When the AMF after end of Localized Services triggers deregistration of UEs, the deregistration requests can be sent at a certain rate in an adaptive and distributed manner, with the effect that the signalling load on both the source network and the target network is limited. - When the AMF after end of Localized Services triggers UE configuration update procedure, e.g. to remove S-NSSAI from the Allowed NSSAI (if dedicated S-NSSAI is used for the Localized Service), the requests can be sent at a certain rate, with the effect that the signalling load in the network is limited. When the NAS level congestion control is activated at AMF as specified in clause 5.19.7.2, to prevent a UE staying in an SNPN for accessing for Localized Services but not able to get services from the SNPN due to the congestion, additional mechanism can be implemented. Such mechanisms are implementation-specific but some guidelines that can be considered are described below: - the AMF can determine whether to reject the UE with a proper cause without Mobility Management back-off timer to allow the UE to reselect another SNPN for Localized Services. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | N.5 |
5,423 | 5.18 HPLMN Notification with specific indication due to MME initiated Bearer removal | When initiating a Delete Session Request procedure, the MME shall add an appropriate cause code facilitating the operator of the P-GW to take appropriate action (e.g. Alarm, O&M action by operator's management network) if needed. NOTE: This is for the HPLMN operator to be able to differentiate Delete Session Request procedures due to a failure case (e.g. due to a QoS parameter mismatch at Initial Attach) from Delete Session Request procedures that are executed in cases not related to any failure conditions (e.g. due to a Tracking Area Update). Action taken by the HPLMN operator is outside the scope of 3GPP specification. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.18 |
5,424 | 4.3.6.4 Transferring an AF request targeting an individual UE address to the relevant PCF | Figure 4.3.6.4-1: Handling an AF request targeting an individual UE address to the relevant PCF Depending on the AF deployment (see clause 6.2.10 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]), the AF may send the AF request to PCF directly, in which case step 1 is skipped, or via the NEF. 1. [Conditional] If the AF sends the AF request via NEF, the AF sends Nnef_TrafficInfluenceCreate/Update/Delete Request targeting an individual UE address to the NEF. This request corresponds to an AF request to influence traffic routing to a local network and/or to a service function chain that targets an individual UE address. When NEF receives an AF request from AF, the NEF ensures the necessary authorization control and as described in clause 4.3.6.1, mapping from the information provided by the AF into information needed by the 5GC. The NEF responds to the AF. 2. [Conditional] AF/NEF consumes Nbsf_Management_Discovery service operation (providing at least the UE address) to find out the address of the relevant PCF if the PCF address is not available on the NEF based on local configuration, otherwise step 1 is skipped. NOTE 1: The AF/NEF finds the BSF based on local configuration or using the NRF. 3. BSF provides the PCF address in the Nbsf_Management_Discovery response to AF/NEF. 4. If step 1 was performed, NEF invokes the Npcf_PolicyAuthorization service to the PCF to transfer the AF request. If an AF sends the AF request directly to the PCF, AF invokes Npcf_PolicyAuthorization service and the PCF responds to the AF. To support the AF instance change, the Npcf_PolicyAuthorization_Create (initiated by target AF) or Npcf_PolicyAuthorization_Update (initiated by source AF or target AF) service operation may be used. NOTE 2: If the source AF transfers the application context to the target AF, then target AF may create new subscription via Npcf_PolicyAuthorization_Create or update existing subscription via Npcf_PolicyAuthorization_Update. However, whether and how the application context transfer is done is out of this specification. 5. The PCF authorizes the AF request. If the PCF determines that the requirements can't be authorized, it rejects the AF request. Once the PCF authorizes the AF request, the PCF updates the SMF with corresponding new PCC rule(s) with PCF initiated SM Policy Association Modification procedure as described in clause 4.16.5.2. The PCF includes the Traffic Steering Policy ID(s) for AF influence on traffic routing Enforcement Control information and/or N6-LAN Traffic Steering Enforcement Control information in the relevant PCC rule as defined in clause 6.3.1 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. The PCF may, optionally, use service experience analytics per UP path, as defined in clause 6.4.3 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50], to provide a an updated list of DNAI(s) to the SMF. If Npcf_PolicyAuthorization_Update service operation is invoked, the PCF is required to update the subscription resource. The Npcf_PolicyAuthorization_Update service operation may include an updated notification target address. The updated subscription resource is used by the target AF. When a PCC rule is received from the PCF, the SMF may take appropriate actions, when applicable, to reconfigure the User plane of the PDU Session. In the case of AF influence on traffic routing, examples of actions are: - The SMF may consider service experience analytics and/or DN Performance analytics per UP path (i.e. including UPF and/or DNAI and/or AS instance) as defined in clauses 6.4.3 and 6.14.3, respectively, of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50] before taking any actions. - Determining a target DNAI and adding, replacing or removing UPF(s) in the data path, e.g. to act as UL CL, Branching Point and/or PDU Session Anchor e.g. as described in clause 4.3.5. - Allocate a new Prefix to the UE (when IPv6 multi-Homing applies). - Updating the UPF regarding the target DNAI with AF influence on traffic routing control parameters as described in clause 5.6.7.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. - Subscribe to notifications from the AMF for an Area of Interest via Namf_EventExposure_Subscribe service operation. - Determining whether to relocate PSA UPF considering the user plane latency requirements provided by the AF (see clause 6.3.6 of TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [74]). In the case of AF influence on Service Function Chaining, the SMF may take appropriate actions to enforce the N6-LAN traffic steering control: - Provide N6-LAN traffic steering control parameters to UPF as described in clause 5.6.16 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3.6.4 |
5,425 | 8.2.2.3 Inter-gNB-DU Conditional PSCell Change using MCG SRB without MN negotiation | This procedure is used for the case where the UE moves from one gNB-DU to another gNB-DU within the same gNB-CU when only MCG SRB is available and the MN’s configuration is not changed during EN-DC operation for conditional PSCell change. Figure 8.2.2.3-1 shows the inter-gNB-DU conditional PSCell change procedure using MCG SRB in EN-DC. Figure 8.2.2.3-1: Inter-gNB-DU Conditional PSCell Change using MCG SRB without MN negotiation in EN-DC 1-4. The steps 1-4 are as defined in clause 8.2.2.1. 5. The gNB-CU sends an UE CONTEXT SETUP REQUEST message to the candidate gNB-DU to create an UE context and setup one or more data bearers. The UE CONTEXT SETUP REQUEST message is sent for each candidate cell and includes a CG-ConfigInfo. 6. The candidate gNB-DU responds the gNB-CU with an UE CONTEXT SETUP RESPONSE message including the target cell ID that was requested from the gNB-CU. The response message is sent for each requested candidate cell. 7. The gNB-CU sends an SGNB MODIFICATION REQUIRED message to the MeNB, which includes a generated RRCReconfiguration message. 8. The MeNB and the UE perform RRC Connection Reconfiguration/Complete procedure. 9. The MeNB sends an SGNB MODIFICATION CONFIRM message to the gNB-CU, to convey the received RRCReconfigurationComplete message at step 8. 10. An execution condition to trigger initiation of conditional PSCell change is fulfilled. 11. Random Access procedure is performed at the candidate gNB-DU, which becomes the target gNB-DU if successful. The target gNB-DU sends a Downlink Data Delivery Status frame to inform the gNB-CU. The target gNB-DU also sends an ACCESS SUCCESS message to inform the gNB-CU of which cell the UE has successfully accessed. 12-13. The UE responds with an RRCReconfigurationComplete message (embedded in an ULInformationTransferMRDC message), which the MeNB forwards to the gNB-CU via an RRC TRANSFER message. 14. The gNB-CU sends a UE CONTEXT MODIFICATION REQUEST message to the source gNB-DU and indicates to stop the data transmission for the UE. The source gNB-DU sends a Downlink Data Delivery Status frame to inform the gNB-CU about the unsuccessfully transmitted downlink data to the UE. Downlink packets, which may include PDCP PDUs not successfully transmitted in the source gNB-DU, are sent from the gNB-CU to the target gNB-DU. Downlink packets are sent to the UE. Also, uplink packets are sent from the UE, which are forwarded to the gNB-CU through the target gNB-DU. NOTE: The step 14 may happen before step 13, as soon as the gNB-CU knows which cell the UE has successfully accessed. NOTE: The gNB-CU may initiate UE Context Release procedure toward the other signalling connections or other candidate target gNB-DUs, if any, to cancel conditional PSCell change for the UE. 15. The source gNB-DU responds to the gNB-CU with the UE CONTEXT MODIFICATION RESPONSE message. 16-17. The steps 16-17 are as defined in steps 11-12 in clause 8.2.1.1. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.2.2.3 |
5,426 | 4.12a.2.2 Registration procedure for trusted non-3GPP access | The UE connects to a trusted non-3GPP Access Network (TNAN) and it also registers to 5GC over via this TNAN, by using the EAP-based procedure shown in the figure 4.12a.2.2. This procedure is very similar with the 5GC registration procedure over untrusted non-3GPP access in clause 4.12.2.2. The link between the UE and the TNAN can be any data link (L2) that supports EAP encapsulation, e.g. PPP, PANA, Ethernet, IEEE 802.3, IEEE 802.11, etc. The interface between the TNAP and TNGF is an AAA interface. Figure 4.12a.2.2-1: Registration via trusted non-3GPP access 0. The UE which is not operating in SNPN access mode for Yt interface selects a PLMN and a TNAN for connecting to this PLMN by using the Trusted Non-3GPP Access Network selection procedure specified in clause 6.3.12 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. During this procedure, the UE discovers the PLMNs with which the TNAN supports trusted connectivity (e.g. "5G connectivity"). The UE operating in SNPN access mode for Yt interface selects an SNPN and a TNAN for connecting to this SNPN by using the Trusted Non-3GPP Access Network selection procedure specified in clause 5.30.2.13 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. During this procedure, the UE discovers the SNPNs with which the TNAN supports trusted connectivity (e.g. "5G connectivity"). NOTE 1: In this Release, it is assumed that when the trusted non-3GPP access is a trusted WLAN access, the UE is configured (e.g. with the WLANSP rules defined in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]) to select an TNAN(SSID and TNGF) associated with a non-3GPP Tracking Area, which supports one or more of the UE's subscribed S-NSSAIs. 1. A layer-2 connection is established between the UE and the TNAP. In the case of IEEE Std 802.11 [48], this step corresponds to an 802.11 Association. In the case of PPP, this step corresponds to a PPP LCP negotiation. In other types of non-3GPP access (e.g. Ethernet), this step may not be required. 2-3. An EAP procedure is initiated. EAP messages are encapsulated into layer-2 packets, e.g. into IEEE 802.3/802.1x packets, into IEEE 802.11/802.1x packets, into PPP packets, etc. The NAI provided by the UE not operating in SNPN access mode for Yt interface indicates that the UE requests "5G connectivity" to a specific PLMN (e.g. NAI = "<any_username>@nai.5gc. mnc<MNC>.mcc<MCC>.3gppnetwork.org"). In the case of WLAN access, if the UE has an MPS subscription, the UE shall also include an indication of its MPS subscription in the username part of the NAI as per TS 23.003[ Numbering, addressing and identification ] [33]. The NAI provided by the UE operating in SNPN access mode for Yt interface indicates that the UE request "5G connectivity" to a specific SNPN (e.g. NAI = "<any_username>@nai.5gc. nid<NID>.mnc<MNC>.mcc<MCC>.3gppnetwork.org"). If the WLANSP rule contains information including TNGF ID to use for specific slices and the UE supports such information, the UE builds the realm of NAI taking the TNGF ID into account (e.g. NAI = "<any_username>@ tngfid<TNGF ID>. nai.5gc. mnc<MNC>.mcc<MCC>.3gppnetwork.org"). This NAI triggers the TNAP to send an AAA request to a TNGF, which operates as an AAA proxy. Between the TNAP and TNGF the EAP packets are encapsulated into AAA messages. The AAA request also include the TNAP identifier, which can be treated as the User Location Information defined in clause 5.6.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. In order to support usage of the TNAP identifier defined in TS 23.316[ Wireless and wireline convergence access support for the 5G System (5GS) ] [53], when a 5G-RG acts as a TNAP , the W-5GAN may, as defined in clause 5.6.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], provide the 5G RG civic address information in the TNAP identifier. NOTE 2: In this Release, it is assumed that when the trusted non-3GPP access is a trusted WLAN access, the TNAP selects a TNGF based on the realm (e.g. MCC, MNC and TNGF ID) provided by the UE and also based on the SSID selected by the UE. In a deployment a TNGF may be reached over different SSID(s) where the TNGF supports a Tracking Area and be associated with a set of slices, or an SSID may provide access to one or more TNGF(s), where each of these TNGF(s) can support a different Tracking Area and a different set of slices. NOTE 3: Based on operator policy, after receiving the indication of MPS subscription from the UE, the TNAN can treat this UE with priority. 4-10. An EAP-5G procedure is executed as the one specified in clause 4.12.2.2 for the untrusted non-3GPP access with the following modifications: - The registration request may contain an indication that the UE supports TNGF selection based on the slices the UE wishes to use over trusted non-3GPP access (i.e. that the UE supports Extended WLANSP rule). - A TNGF key (instead of an N3IWF key) is created in the UE and in the AMF after the successful authentication. The TNGF key is transferred from the AMF to TNGF in step 10a (within the N2 Initial Context Setup Request). The TNGF derives a TNAP key, which is provided to the TNAP. The TNAP key depends on the non-3GPP access technology (e.g. it is a Pairwise Master Key in the case of IEEE Std 802.11 [48]). How these security keys are created, it is specified in TS 33.501[ Security architecture and procedures for 5G System ] [15]. - In step 5 the UE shall include the Requested NSSAI in the AN parameters only if allowed, according to the conditions defined in clause 5.15.9 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], for the trusted non-3GPP access. The UE shall also include a UE Id in the AN parameters, e.g. a 5G-GUTI if available from a prior registration to the same PLMN or SNPN. If the UE in SNPN access mode for Yt interface performs the Registration procedure for UE onboarding, the UE shall include an indication in the AN parameters that the connection request is for onboarding. - In the N2 message sent in step 6b, the TNGF includes a UE Location Information (ULI)including the TNAP ID and the UE IP address based on information received in step 3. If the ULI includes the IP address, this is set to a "null" IP address (e.g. 0.0.0.0) because the UE is not yet assigned an IP address. If the TNGF has received the the TNAP ID in step 3 over Ta, the TNGF includes the TNAP ID within UE Location Information (ULI) sent to AMF. After the UE is assigned an IP address, the TNGF includes this address in subsequent N2 messages. This N2 message also includes the Selected PLMN ID and optionally the Selected NID and the Establishment cause. NOTE 4: The Selected NID is present when the UE connects to an SNPN via Trusted non-3GPP access. - If the UE in SNPN access mode for Yt interface performs the Registration procedure for UE onboarding, the interaction between AMF and AUSF (step 8a and step 8c in Figure 4.12a.2.2-1) is replaced with step 9-1 or step 9-2 or step 9-3 in Figure 4.2.2.2.4-1, depending on the 5GC architecture that is used for UE onboarding. - After receiving the TNGF key from AMF in step 10a, the TNGF shall send to UE an EAP-Request/5G-Notification packet containing the "TNGF Contact Info", which includes the IP address of TNGF. After receiving an EAP-Response/5G-Notification packet from the UE in step 10c, the TNGF shall send message 10d containing the EAP-Success packet. 11. The TNAP key is used to establish layer-2 security between the UE and TNAP. In the case of IEEE Std 802.11 [48], a 4-way handshake is executed, which establishes a security context between the WLAN AP and the UE that is used to protect unicast and multicast traffic over the air. 12. The UE receives IP configuration from the TNAN, e.g. with DHCP. 13. At this point, the UE has successfully connected to the TNAN and has obtained IP configuration. The UE sets up a secure NWt connection with the TNGF as follows: The UE initiates an IKE_INIT exchange using the IP address of TNGF received during the EAP-5G signalling, in step 10b. Subsequently, the UE initiates an IKE_AUTH exchange and provides its identity. The identity provided by the UE in the IKEv2 signalling should be the same as the UE Id included in the AN parameters in step 5. This enables the TNGF to locate the TNGF key that was created before for this UE, during the authentication in step 8. The TNGF key is used for mutual authentication. NULL encryption is negotiated between the UE and the TNGF, as specified in RFC 2410 [49]. In step 13c, the TNGF provides to UE (a) an "inner" IP address, (b) a NAS_IP_ADDRESS and a TCP port number and (c) a DSCP value. After this step, an IPsec SA is established between the UE and TNGF. This is referred to as the "signalling IPsec SA" and operates in Tunnel mode. Operation in Tunnel mode enables the use of MOBIKE [40] for re-establishing the IPsec SAs when the IP address of the UE changes during mobility events. All IP packets exchanged between the UE and TNGF via the "signalling IPsec SA" shall be marked with the above DSCP value. The UE and the TNAP may map the DSCP value to a QoS level (e.g. to an EDCA Access Class [48]) supported by the underlying non-3GPP Access Network. The mapping of a DSCP value to a QoS level of the non-3GPP Access Network is outside the scope of 3GPP. Right after the establishment of the "signalling IPsec SA", the UE shall setup a TCP connection with the TNGF by using the NAS_IP_ADDRESS and the TCP port number received in step 13c. The UE shall send NAS messages within TCP/IP packets with source address the "inner" IP address of the UE and destination address the NAS_IP_ADDRESS. The TNGF shall send NAS messages within TCP/IP packets with source address the NAS_IP_ADDRESS and destination address the "inner" IP address of the UE. This concludes the setup of the NWt connection between the UE and the TNGF. All subsequent NAS messages between UE and TNGF are carried over this NWt connection (i.e. encapsulated in TCP/IP/ESP). 14. After the NWt connection is successfully established, the TNGF responds to AMF with an N2 Initial Context Setup Response message. 15. The AMF determines the allowed subset of the Requested NSSAI that is allowed by the Subscribed S-NSSAI(s); the AMF may detect that the TNGF used by the UE is not compatible with this allowed subset and based on operator's policy configured in the AMF, the AMF determines whether a different TNGF should be used. If the UE supports slice-based TNGF selection and the AMF determines to use a different TNGF, then the AMF proceeds with steps 17-21. Otherwise, i.e. if the AMF determines to use the selected TNGF that supports part of allowed the subset, the AMF proceeds with step 16. In this case, steps 17-21 are skipped. NOTE 5: The criteria for the AMF to determine that the TNGF used by the UE is not compatible with the subset of the requested NSSAI that is allowed by the subscribed S-NSSAI(s) is based on local AMF policies. For example the AMF can determine that the TNGF used by the UE is compatible as soon as there is one supported slice in common. 16. The NAS Registration Accept message is sent by the AMF and is forwarded to UE via the established NWt connection. Now the UE can use the TNAN (a) to transfer non-seamless offload traffic and (b) to establish one or more PDU Sessions. Steps 17 to 21 correspond to the case where the AMF has detected that TNGF used by the UE is not compatible with the subset of the requested NSSAI that is allowed by the subscribed S-NSSAI(s). 17. If the UE Registration Request contains an indication that the UE supports TNGF selection based on the slices the UE wishes to use over trusted non-3GPP access and AMF is able to select a UE PCF that supports UE policies for slice specific trusted access selection, the AMF may trigger UE policy association establishment if a suitable UE policy association does not exist yet. Then the AMF triggers the UE PCF to update the UE policies for slice specific trusted access selection by either indicating the request in Npcf_UEPolicyControl_Create or, if a UE policy already exists, by issuing a Npcf_UEPolicyControl_Update. The AMF requests the PCF to receive a notification when the PCF has completed the update of these UE policies. NOTE 6: The UE is assumed to inform PCF whether the UE supports Extended WLANSP or ANDSP as part of the UE policy update procedure. Details will be specified by CT WG1. 18. The PCF updates the UE policies for slice specific trusted access selection according to the procedure defined in figure 4.2.4.3-1. 19. When the update of these policies is completed, the PCF notifies the AMF by invoking Npcf_UEPolicyControl_UpdateNotify. 20. The AMF sends via the TNGF a UE Registration Reject indicating that the selected TNGF was not appropriate for the requested slices that the UE is allowed to access to. The AMF may provide target TNAN information (SSID, TNGF ID) to the UE within the Registration Reject message indicating the UE to build the NAI based on the TNGF ID. NOTE 7: The AMF may determine a target TNGF that supports the subset of the requested NSSAI that is allowed by the subscribed S-NSSAI(s) based on the list of supported TAs and the corresponding list of supported slices for each TA obtained in N2 interface management procedures as specified in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [10] and considering UE location. 21. If supported by the UE and if the UE received target TNAN information in step 20, the UE connects to the target TNAN, otherwise the UE may perform TNAN selection again using the updated WLANSP rule received in step 18. If the target TNAN information includes TNGF ID, the UE shall build the NAI based on TNGF ID. The UE uses the target TNAN information in the Registration Reject only for the TNAN selection directly following the rejected registration and UE shall not store it for future use. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.12a.2.2 |
5,427 | 11.8.2 Gi/SGi PtP tunnelling based on UDP/IP | Gi/SGi PtP tunnelling based on UDP/IP may be used to deliver Non-IP data to an AS via Gi/SGi. The PtP tunnel is set up by configuration of tunnel parameters in both end of the tunnel. The following parameters are pre-configured in the GGSN/P-GW per APN; - the UDP destination port number to use when sending Non-IP data; - the UDP port number it wants to receive Non-IP data; - the destination IP address to be used for sending Non-IP data. NOTE 1: Many APNs can resolve to the same P-GW, but each APN can be unique to a particular AS. The following is pre-configured in the AS; - the UDP destination port number to use when sending Non-IP data; - the UDP port number it wants to receive Non-IP data. NOTE 2: The GGSN/P-GW as well as the AS can use any UDP port numbers not assigned by IANA. The port numbers used need to be aligned between peers. IP address allocation procedures for the UE (i.e. PDN connection) are performed by the GGSN/P-GW as described in subclause 11.2.2. The UE IP address for the PDN connection or IPv6 prefix allocated for the PDN connection+suffix assigned for the PtP tunnel end point in the GGSN/P-GW is used as source address in the GGSN/P-GW and as destination address in the AS for the PtP tunnel. During the PDP context/PDN connection establishment, the GGSN/P-GW associates the GTP-U tunnel for the PDP context/PDN connection with the Gi/SGi PtP tunnel. The GTP-U tunnel with PDP/PDN type “Non-IP” is used. The GGSN/P-GW acts as a transparent forwarding node between the UE used for CIoT and the AS. NOTE 3: The UE can include application level identity to AS, what kind of identity is out of scope of this specification. For uplink delivery, if the uplink data is received from the GTP-U tunnel the GGSN/P-GW shall forward the received data to the AS over the Gi/SGi PtP tunnel associated with the GTP-U tunnel using UDP/IP encapsulation with the destination address of the AS and the configured UDP destination port number for “Non-IP” data as described above. For downlink delivery, the AS shall send the data using UDP/IP encapsulation with the IP address or IPv6 prefix+suffix of the UE as destination address and the configured UDP destination port number for “Non-IP” data as described above. NOTE 3: The UDP source port number to use for both uplink and downlink Non-IP data transfer can be a pre-configured or a locally allocated port number in the GGSN/P-GW and AS respectively. NOTE 4: For downlink delivery, the GGSN/P-GW decapsulates the received data (i.e. removes the UDP/IP headers) and forwards the data to SGSN/S-GW on the GTP-U tunnel identified by the IP address or the IPv6 prefix of the UE (i.e. PDN connection) for delivery to the UE. Figure 11.8: Protocol configuration for Non-IP data (user plane) using SGiPtP tunneling Figure 11.9: Protocol configuration for Non-IP data (user plane) using Gi PtP tunneling. | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 11.8.2 |
5,428 | – SL-RBSetConfig | The IE SL-RBSetConfig specifies the configuration information for RB set for NR Sidelink Communication. SL-RBSetConfig information element -- ASN1START -- TAG-SL-RBSETCONFIG-START SL-RBSetConfig-r18 ::= SEQUENCE { sl-RBSetIndex-r18 INTEGER (0..4), sl-NumOfSSSBRepetition-r18 INTEGER (2..9) OPTIONAL, -- Need M sl-GapBetweenSSSBRepetition-r18 INTEGER (1..84) OPTIONAL -- Need M } -- TAG-SL-RBSETCONFIG-STOP -- ASN1STOP – SL-RelayUE-Config The IE SL-RelayUE-Config specifies the configuration information for NR sidelink U2N Relay UE. SL-RelayUE-Config information element -- ASN1START -- TAG-SL-RELAYUE-CONFIG-START SL-RelayUE-Config-r17::= SEQUENCE { threshHighRelay-r17 RSRP-Range OPTIONAL, -- Need R threshLowRelay-r17 RSRP-Range OPTIONAL, -- Need R hystMaxRelay-r17 Hysteresis OPTIONAL, -- Cond ThreshHighRelay hystMinRelay-r17 Hysteresis OPTIONAL -- Cond ThreshLowRelay } -- TAG-SL-RELAYUE-CONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,429 | 5.7.1 Description | From the MNO’s point of view, an MNO may want to differentiate the UE which is specific for UAS use (UAS-capable) with the regular ground based UEs, as well as to identify the different class of UAV (e.g. small/big UAVs) for the following reasons: (1) To provide better service to the UAVs. As we know, airborne UAV may receive more DL signal interference from more RANs because UAVs can see more cells/RANs in the air (described in TR 36.777). If airborne status can be identified, MNO can use differentiated/optimized power control methods. Moreover, if UAV’s type can be identified, an MNO can translate the UAV class to mobility parameters (e.g. Time to Trigger used for handover), which can be used for mobility enhancements. (2) To protect the network. The airborne UAV may produce higher UL signal interference to the UEs on the ground (Described in TR 36.777), if the UAS-capable UE can be identified, suitable mechanisms or procedures can be used to migrate interference. (3) To differentiate charging rules. MNOs may want to charge different subscription fees for airborne UAV with UAS-capable UE vs. regular UEs. Also from the regulatory point of view, only certain type of UAV with certain 3GPP communication capabilities may be allowed to be operated in certain areas, and the MNOs may have the responsibility to identify the unauthorized airborne UAV that may because that type or communication capability of UAV is not allowed (e.g. UAV attached with a regular cell phone) in that area, and report to UTM or law enforcement. Some UAS may seek to operate without initial authorization from the UTM. In addition, they may attempt to avoid detection from the 3GPP system and being identified as UAS-capable UE. For instance, they may embed a terrestrial 3GPP UE and identify as a regular 3GPP UE. These UAS may hinder network performance and represent a breach of regulation in some airspaces. However, even in the absence of an explicit identification as a UAS-capable UE, the 3GPP system may detect, based on implicit information such as mobility pattern history and other RAN airborne UE detection mechanism, that the 3GPP UE is actually a UAS-capable UE in flying mode. In that case, an MNO may notify the UTM that a specific UE is believed to be in flying mode, to provide live positioning information into the UTM | 3GPP TS 22.825 | Study on Remote Identification of Unmanned Aerial Systems (UAS) | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 5.7.1 |
5,430 | 5.3.14.5 Access barring check | The UE shall: 1> if one or more Access Identities equal to 1, 2, 11, 12, 13, 14, or 15 are indicated according to TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [23], and 1> if for at least one of these Access Identities the corresponding bit in the uac-BarringForAccessIdentity contained in "UAC barring parameter" is set to zero: 2> consider the access attempt as allowed; 1> else: 2> if the establishment of the RRC connection is the result of release with redirect with mpsPriorityIndication (either in NR or E-UTRAN); and 2> if the bit corresponding to Access Identity 1 in the uac-BarringForAccessIdentity contained in the "UAC barring parameter" is set to zero: 3> consider the access attempt as allowed; 2> else if Access Identity 3 is indicated: 3> draw a random number 'rand' uniformly distributed in the range: 0 ≤ rand < 1; 3> if 'rand' is lower than the value indicated by uac-BarringFactorForAI3 included in "UAC barring parameter": 4> consider the access attempt as allowed; 3> else: 4> consider the access attempt as barred; 2> else: 3> draw a random number 'rand' uniformly distributed in the range: 0 ≤ rand < 1; 3> if 'rand' is lower than the value indicated by uac-BarringFactor included in "UAC barring parameter": 4> consider the access attempt as allowed; 3> else: 4> consider the access attempt as barred; 1> if the access attempt is considered as barred: 2> draw a random number 'rand' that is uniformly distributed in the range 0 ≤ rand < 1; 2> start timer T390 for the Access Category with the timer value calculated as follows, using the uac-BarringTime included in "UAC barring parameter": T390 = (0.7+ 0.6 * rand) * uac-BarringTime. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.14.5 |
5,431 | 9.3.2.2 Bearer capability 1 and bearer capability 2 | The bearer capability 1 information element shall be included if and only if at least one of the following six cases holds: - the mobile station wishes another bearer capability than that given by the bearer capability 1 information element of the incoming SETUP message; - the bearer capability 1 information element is missing or not fully specified in the SETUP message; - the bearer capability 1 information element received in the SETUP message is accepted and the "radio channel requirement" of the mobile station is other than "full rate support only mobile station"; - the bearer capability 1 information element received in the SETUP message indicates speech and is accepted and the mobile station supports CTM text telephony; - the bearer capability 1 information element received in the SETUP message indicates speech and is accepted and the mobile station supports other codecs for GERAN than GSM speech version 1; - the bearer capability 1 information element received in the SETUP message included the "fixed network user rate" parameter. When the bearer capability 1 information element is followed by the bearer capability 2 IE in the SETUP, the above rules apply to both bearer capability 1 IE and bearer capability 2 IE. Except those cases identified in 3GPP TS 27.001[ General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS) ] [36], if either bearer capability needs to be included, both shall be included. Furthermore, both bearer capability information elements may be present if the mobile station wishes to reverse the order of occurrence of the bearer capability information elements (which is referred to in the repeat indicator information element, see subclause 10.5.4.22) in cases identified in 3GPP TS 27.001[ General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS) ] [36]. If the mobile station wishes to indicate capability for an alternative call mode, which can be entered during the call through in-call modification, this is indicated by adding a bearer capability information element (bearer capability 2 information element, see subclause 5.3.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 | 9.3.2.2 |
5,432 | 6.16.2 Requirements | In constrained circumstances (e.g. reduced power supply), the 5G system shall be able to support a minimal user experience (e.g. user experienced data rate of [100] kbit/s, E2E latency of 50 ms, lower availability of the network of 95%). The 5G system shall support centralized automation and management of the network in order to reduce local management tasks. The 5G system shall support a mechanism to reduce data transfer rate at the cell edge for very large coverage area (e.g. 100 kbit/s for more than 100 km cell coverage, 1 Mbit/s for 100 km cell coverage). The 5G system shall be able to give priority to services (e.g. e-Health) when resources are limited. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.16.2 |
5,433 | 5.3.10.2 Recovery of physical layer problems | Upon receiving N311 consecutive "in-sync" indications for the SpCell from lower layers while T310 is running, the UE shall: 1> stop timer T310 for the corresponding SpCell. 1> stop timer T312 for the corresponding SpCell, if running. NOTE 1: In this case, the UE maintains the RRC connection without explicit signalling, i.e. the UE maintains the entire radio resource configuration. NOTE 2: Periods in time where neither "in-sync" nor "out-of-sync" is reported by L1 do not affect the evaluation of the number of consecutive "in-sync" or "out-of-sync" indications. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.10.2 |
5,434 | – MobilityFromNRCommand | The MobilityFromNRCommand message is used to command handover from NR to E-UTRA/EPC, E-UTRA/5GC or UTRA-FDD. Signalling radio bearer: SRB1 RLC-SAP: AM Logical channel: DCCH Direction: Network to UE MobilityFromNRCommand message -- ASN1START -- TAG-MOBILITYFROMNRCOMMAND-START MobilityFromNRCommand ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { mobilityFromNRCommand MobilityFromNRCommand-IEs, criticalExtensionsFuture SEQUENCE {} } } MobilityFromNRCommand-IEs ::= SEQUENCE { targetRAT-Type ENUMERATED { eutra, utra-fdd-v1610, spare2, spare1, ...}, targetRAT-MessageContainer OCTET STRING, nas-SecurityParamFromNR OCTET STRING OPTIONAL, -- Cond HO-ToEPCUTRAN lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension MobilityFromNRCommand-v1610-IEs OPTIONAL } MobilityFromNRCommand-v1610-IEs ::= SEQUENCE { voiceFallbackIndication-r16 ENUMERATED {true} OPTIONAL, -- Need N nonCriticalExtension MobilityFromNRCommand-v1800-IEs OPTIONAL } MobilityFromNRCommand-v1800-IEs ::= SEQUENCE { successHO-Config-r18 SetupRelease {SuccessHO-Config-r17} OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } -- TAG-MOBILITYFROMNRCOMMAND-STOP -- ASN1STOP NOTE 1: The correspondence between the value of the targetRAT-Type, the standard to apply, and the message contained within the targetRAT-MessageContainer is shown in the table below: | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,435 | 4.2.4.1 In-session activity time for UE | a) This measurement provides the aggregated active session time for UEs in a cell. b) CC c) Number of session seconds aggregated for UEs in a cell. For E-RABs with bursty flow, a UE is said to be “in session” if any E-RAB data on a Data Radio Bearer (UL or DL) has been transferred during the last 100 ms. For E-RABs with continuous flow, the E-RAB (and the UE) is always seen as being “in session” in the context of this measurement, and the session time is increased from the first data transmission on the E-RAB until 100 ms after the last data transmission on the E-RAB. d) Each measurement is an integer value. e) ERAB.SessionTimeUE f) EUtranCellFDD EUtranCellTDD g) Valid for packet switched traffic h) EPS i) This measurement is to support the Retainability KPI “E-RAB Retainability” defined in [13]. | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.2.4.1 |
5,436 | 5.21.2.2.1 AMF planned removal procedure with UDSF deployed | An AMF can be taken graciously out of service as follows: - If an UDSF is deployed in the network, then the AMF stores the context for registered UE(s) in the UDSF. The UE context includes the AMF UE NGAP ID that is unique per AMF set. In order for the AMF planned removal procedure to work graciously, 5G-S-TMSI shall be unique per AMF Set. If there are ongoing transactions (e.g. N1 procedure) for certain UE(s), AMF stores the UE context(s) in the UDSF upon completion of an ongoing transaction. - The AMF deregister itself from NRF indicating due to AMF planned removal. NOTE 1: It is assumed that the UE contexts from the old AMF include all event subscriptions with peer CP NFs. NOTE 2: Before removal of AMF the overload control mechanism can be used to reduce the amount of ongoing transaction. An AMF identified by GUAMI(s) shall be able to notify the 5G-AN that it will be unavailable for processing transactions by including GUAMI(s) configured on this AMF. Upon receipt of the indication that an AMF(identified by GUAMI(s)) is unavailable, 5G-AN shall take the following action: - 5G-AN should mark this AMF as unavailable and not consider the AMF for selection for subsequent N2 transactions until 5G-AN learns that it is available (e.g. as part of discovery results or by configuration). - During NGAP Setup procedure, the AMF may include an additional indicator that the AMF will rebind or release the NGAP UE-TNLA-binding on a per UE-basis for UE(s) in CM-CONNECTED state. If that indicator is included and the 5G-AN supports timer mechanism, the 5G-AN starts a timer to control the release of NGAP UE-TNLA-binding. For the duration of the timer or until the AMF releases or re-binds the NGAP UE-TNLA-binding the AN does not select a new AMF for subsequent UE transactions. Upon timer expiry, the 5G-AN releases the NGAP UE UE-TNLA-binding(s) with the corresponding AMF for the respective UE(s), for subsequent N2 message, the 5G-AN should select a different AMF from the same AMF set when the subsequent N2 message needs to be sent. NOTE 3: For UE(s) in CM-CONNECTED state, after indicating that the AMF is unavailable for processing UE transactions and including an indicator that the AMF releases the NGAP UE-TNLA-binding(s) on a per UE-basis, the AMF can either trigger a re-binding of the NGAP UE associations to an available TNLA on a different AMF in the same AMF set or use the NGAP UE-TNLA-binding per UE release procedure defined in TS 23.502[ Procedures for the 5G System (5GS) ] [3] to release the NGAP UE-TNLA-binding on a per UE-basis while requesting the AN to maintain N3 (user plane connectivity) and UE context information. NOTE 4: The support and the use of timer mechanism in 5G-AN is up to implementation. - If the instruction does not include the indicator, for UE(s) in CM-CONNECTED state, 5G-AN considers this as a request to release the NGAP UE-TNLA-binding with the corresponding AMF for the respective UE(s) while maintaining N3 (user plane connectivity) and UE context information. For subsequent N2 message, the 5G-AN should select a different AMF from the same AMF set when the subsequent N2 message needs to be sent. - For UE(s) in CM-IDLE state, when it subsequently returns from CM-IDLE state and the 5G-AN receives an initial NAS message with a 5G S-TMSI or GUAMI pointing to an AMF that is marked unavailable, the 5G-AN should select a different AMF from the same AMF set and forward the initial NAS message. If the 5G-AN can't select an AMF from the same AMF set, the 5G-AN selects another new AMF as described in clause 6.3.5. An AMF identified by GUAMI(s) shall be able to instruct other peer CP NFs, subscribed to receive such a notification, that it will be unavailable for processing transactions by including GUAMI(s) configured on this AMF. If the CP NFs register with NRF for AMF unavailable notification, then the NRF shall be able to notify the subscribed NFs to receive such a notification that AMF identified by GUAMI(s) will be unavailable for processing transactions. Upon receipt of the notification that an AMF (GUAMI(s)) is unavailable, the other CP NFs shall take the following actions: - CP NF should mark this AMF (identified by GUAMI(s)) as unavailable and not consider the AMF for selection for subsequent MT transactions until the CP NF learns that it is available (e.g. as part of NF discovery results or via NF status notification from NRF). - Mark this AMF as unavailable while not changing the status of UE(s) associated to this AMF (UE(s) previously served by the corresponding AMF still remain registered in the network), and AMF Set information. - For the UE(s) that were associated to the corresponding AMF, when the peer CP NF needs to initiate a transaction towards the AMF that is marked unavailable, CP NF should select another AMF from the same AMF set (as in clause 6.3.5) and forward the transaction together with the old GUAMI. The new AMF retrieves UE context from the UDSF. If CP NF needs to send a notification to new AMF which is associated with a subscription from the old AMF, the CP NF shall exchange the old AMF information embedded in the Notification Address with the new AMF information, and use that Notification Address for subsequent communication. NOTE 5: If the CP NF does not subscribe to receive AMF unavailable notification (either directly from the AMF or via NRF), the CP NF may attempt forwarding the transaction towards the old AMF and detect that the AMF is unavailable after certain number of attempts. When it detects unavailable, it marks the AMF and its associated GUAMI(s) as unavailable. CP NF should select another AMF from the same AMF set (as in clause 6.3.5) and forward the transaction together with the old GUAMI. The new AMF retrieves UE context from the UDSF and process the transaction. Following actions should be performed by the newly selected AMF: - When there is a transaction with the UE the newly selected AMF retrieves the UE context from the UDSF based on SUPI, 5G-GUTI or AMF UE NGAP ID and processes the UE message accordingly and updates the 5G-GUTI towards the UE, if necessary. For UE(s) in CM-CONNECTED state, it may also update the NGAP UE association with a new AMF UE NGAP ID towards the 5G-AN and replace the GUAMI in the UE context stored at the 5G-AN with the new GUAMI associated with the newly selected AMF if the 5G-GUTI has been updated. The AMF also informs the NG-RAN of the new UE Identity Index Value (derived from the new 5G-GUTI). - When there is a transaction with the UE, the new selected AMF updates the peer NFs (that subscribed to receive AMF unavailability notification from old AMF), with the new selected AMF information. - If the new AMF is aware of a different AMF serving the UE (by implementation specific means) it forwards the uplink N2 signalling of the UE to that AMF directly if necessary, the 5G-AN shall be able to receive the message from a different AMF, or it rejects the transaction from the peer CP NFs with a cause to indicate that new AMF has been selected, the peer CP NFs resend the transaction to the new AMF. NOTE 6: This bullet above addresses situations where 5G-AN node selects an AMF and CP NFs select another AMF for the UE concurrently. It also addresses the situation where CP NFs select an AMF for the UE concurrently - If the UE is in CM-IDLE state and the new AMF does not have access to the UE context, the new AMF selects one available AMF from the old AMF set as described in clause 6.3.5. The selected AMF retrieves the UE context from the UDSF and provides the UE context to the new AMF. If the new AMF doesn't receive the UE context then the AMF may force the UE to perform Initial Registration. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.21.2.2.1 |
5,437 | 6.3.1.1 NF Discovery and Selection aspects relevant with indirect communication | For indirect communication shown in Annex E, the SCP performs the following functionalities regarding Network Function and Network Function Service discovery and selection: - If the request includes a Routing Binding Indication, the SCP shall route the service request to the requested target as specified in Table 6.3.1.0-1. If the Routing Binding Indication does not exist, the SCP may get the NF Set ID from the NRF or local configuration (if available). - If the request recipient had previously provided a Binding Indication, then the request sender shall include a Routing Binding Indication with the same contents in subsequent related requests. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.3.1.1 |
5,438 | 4.7.1.6.4 Change of network mode of operation at A/Gb mode to Iu mode inter-system change | Whenever an MS moves to a new RA supporting the Iu mode radio interface, the procedures executed by the MS depend on the network mode of operation in the old and new routing area. In case the MS is in state GMM-REGISTERED or GMM-ROUTING-AREA-UPDATING-INITIATED and is in operation mode: a) A or B in A/Gb mode, the MS shall change to operation mode A in Iu mode and shall execute: Table 4.7.1.6.8/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Mode A or B in A/Gb mode changing to mode A in Iu mode b) C in A/Gb mode, an MS that changes to operation mode C in Iu mode shall execute a Normal Routing Area Update. (*) Intended to remove the Gs association in the MSC/VLR. (**) Intended to establish the Gs association in the MSC/VLR. (***) If the MS that needs only GPRS services and "SMS-only service" moves to a new routing area, see subclause 4.1.1.2.2. Further details are implementation issues. | 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.6.4 |
5,439 | 8.13.2.1.1 Minimum Requirement Multi-Layer Spatial Multiplexing 4 Tx Antenna Port | For CA with 2 DL CCs, the requirements are specified in Table 8.13.2.1.1-2A, based on single carrier requirement specified in Table 8.13.2.1.1-2, with the addition of the parameters in Table 8.13.2.1.1-1 and the downlink physical channel setup according to Annex C.3.2. For CA with 3 DL CCs, the requirements are specified in Table 8.13.2.1.1-3, based on single carrier requirement specified in Table 8.13.2.1.1-2, with the addition of the parameters in Table 8.13.2.1.1-1 and the downlink physical channel setup according to Annex C.3.2. For CA with 4 DL CCs, the requirements are specified in Table 8.13.2.1.1-4, based on single carrier requirement specified in Table 8.13.2.1.1-2, with the addition of the parameters in Table 8.13.2.1.1-1 and the downlink physical channel setup according to Annex C.3.2. For CA with 5 DL CCs, the requirements are specified in Table 8.13.2.1.1-5, based on single carrier requirement specified in Table 8.13.2.1.1-2, with the addition of the parameters in Table 8.13.2.1.1-1 and the downlink physical channel setup according to Annex C.3.2. The test coverage for different number of component carriers is defined in 8.1.2.4. Table 8.13.2.1.1-1: Test Parameters for Multi-Layer Spatial Multiplexing (FRC) for CA Table 8.13.2.1.1-2: Single carrier performance for multiple CA configurations Table 8.13.2.1.1-2A: Minimum performance (FRC) based on single carrier performance for CA with 2 DL CCs Table 8.13.2.1.1-3: Minimum performance (FRC) based on single carrier performance for CA with 3 DL CCs Table 8.13.2.1.1-4: Minimum performance (FRC) based on single carrier performance for CA with 4 DL CCs Table 8.13.2.1.1-5: Minimum performance (FRC) based on single carrier performance for CA with 5 DL CCs | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.13.2.1.1 |
5,440 | 16.6.2.3 Connected Mode | The NG-RAN node is aware of the SNPN ID(s) supported by neighbour cells. At the time of handover, cells that do not support the serving SNPN ID or the SNPN ID of an equivalent SNPN within the mobility restrictions received in the UE context are not considered as candidate target cells by the source NG-RAN node. The target NG-RAN node performs access control. In case it cannot accept the handover for the serving SNPN the target NG-RAN node fails the handover including an appropriate cause value. 16.6.3 Self-Configuration for SNPN Self-configuration is described in clause 15. In addition, on NG, the NG-RAN node signals the SNPN ID(s) supported per tracking area and the AMF signals the SNPN ID(s) supported per node; on Xn, NG-RAN nodes exchange SNPN ID(s) supported per cell. 16.6.4 Access Control During the establishment of the UE-associated logical NG-connection towards the 5GC, the AMF checks whether the UE is allowed to access the cell for the signalled SNPN ID as specified in TS 23.501[ System architecture for the 5G System (5GS) ] [3]. If the check is successful, the AMF sets up the UE-associated logical NG-connection and provides the NG-RAN node with the mobility restrictions applicable for the SNPN. If the check is not successful, the AMF shall reject setting up the UE-associated NG connection and inform the NG-RAN node with an appropriate cause value as specified in TS 23.501[ System architecture for the 5G System (5GS) ] [3]. 16.6.5 Access with subscription/credentials owned by a Credentials Holder An SNPN may allow access to UEs being authorized using credentials or subscription owned by a separate Credentials Holder (CH). The support of this feature is uniform across the SNPN as specified in TS 23.501[ System architecture for the 5G System (5GS) ] [3]. The following information is broadcast to support SNPN access with subscription of a Credentials Holder: - an indication per SNPN in SIB1 that access using credentials from a Credentials Holder is supported; - optionally a list of supported GINs in SIB18 (each GIN may be assigned to one or more SNPNs); - an optional indication per SNPN in SIB1 that the SNPN allows registration attempts from UEs that are not explicitly configured to select the SNPN. The above listed items are forwarded to the UE NAS layer that uses them for SNPN selection. 16.6.6 Support of UE onboarding and remote provisioning An SNPN may offer support for restricted 3GPP connectivity for remote provisioning of credentials. The feature is enabled/disabled per cell. The following information is broadcast to support UE onboarding and remote provisioning: - an indication per onboarding SNPN in SIB1 that UE onboarding is enabled; - optionally a list of supported GINs in SIB18 (each GIN may be assigned to one or more onboarding SNPNs). The above listed items are forwarded to the UE NAS layer that uses them for onboarding SNPN selection. When a UE intends to perform onboarding, it sends the onboarding request indication to the gNB during RRC connection establishment. The NG-RAN nodes receive information about onboarding support capabilities of the AMF(s). This information is used by the NG-RAN node to select a suitable AMF when receiving the onboarding request indication from the UE. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.6.2.3 |
5,441 | 6.3.3.5 Abnormal cases on the network side | The following abnormal cases can be identified: a) Expiry of timer T3592. The SMF shall, on the first expiry of the timer T3592, retransmit the PDU SESSION RELEASE COMMAND message and shall reset and start timer T3592. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3592, the SMF shall abort the procedure. b) Collision of network-requested PDU session release procedure and UE-requested PDU session modification procedure. When the SMF receives a PDU SESSION MODIFICATION REQUEST message during the network-requested PDU session release procedure, and the PDU session indicated in PDU SESSION MODIFICATION REQUEST message is the PDU session that the SMF had requested to release, the SMF shall ignore the PDU SESSION MODIFICATION REQUEST message and proceed with the PDU session release procedure. c) Collision of network-requested PDU session release procedure and UE-requested PDU session release procedure. If the SMF receives a PDU SESSION RELEASE REQUEST message after sending a PDU SESSION RELEASE COMMAND message with the PTI IE set to "No procedure transaction identity assigned" to the UE, and the PDU session ID in the PDU SESSION RELEASE REQUEST message is the same as the PDU session ID in the PDU SESSION RELEASE COMMAND message: - if the Access type IE is included in the PDU SESSION RELEASE COMMAND message and the PDU session is an MA PDU session and having user-plane resources established on the access different from the access indicated in the Access type IE in the PDU SESSION RELEASE COMMAND message, the SMF shall proceed both the UE-requested PDU session release procedure and network-requested PDU session release procedure; - otherwise, the SMF shall ignore the PDU SESSION RELEASE REQUEST message and proceed with the network-requested PDU session release procedure. d) Collision of re-establishment of the user-plane resources and network-requested PDU session release procedure for the same PDU session. If the SMF receives an indication from the AMF to re-establish the user-plane resources during the network-requested PDU session release procedure for the same PDU session, the SMF shall not re-establish the user-plane resources for the PDU session as specified in 3GPP TS 29.502[ 5G System; Session Management Services; Stage 3 ] [20A] subclause 5.2.2.3.2.2 and proceed with the network-requested PDU session release procedure. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.3.3.5 |
5,442 | 10.18.4 Successful PSCell Change Report | The objective of Successful PSCell change Report (SPR) is to detect sub-optimal successful PSCell change/CPC or successful PSCell addition/CPA. For analysis of such sub-optimal successful PSCell change/CPC and successful PSCell addition/CPA, the UE may collect SPR based on the triggers configured by the network, if received, and makes the SPR available to the network as specified in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [4]. For PSCell addition/CPA and PSCell change/CPC (MN or SN initiated), the target SN always decides the T304 trigger for SPR and performs root cause analysis. For SN-initiated PSCell change/CPC, the source SN decides the T310/T312 triggers for SPR and is responsible for SPR related optimizations e.g., to optimize PSCell change/CPC configuration or associated mobility thresholds or adjust T310/T312 timer values. For MN-initiated PSCell change/CPC, the MN decides the T310/T312 triggers for SPR. MN may optimize PSCell change/CPC configuration or associated mobility thresholds or both. Source SN may optimize lower layer issues e.g., adjust T310/T312 timer values. The SPR can be fetched from the UE by the MN only while the UE is still connected to the MN, or by a node different from the MN that sent the SPR configuration to the UE if the UE is not connected to the MN anymore. In case the SPR is retrieved in a node different from the MN that sent the SPR configuration to the UE, the SPR is first forwarded to that MN, which then forwards it to the respective SN(s) which should perform the SPR optimization. | 3GPP TS 37.340 | Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 | RAN2 | 3GPP Series : 37 , Multiple radio access technology aspects | 10.18.4 |
5,443 | 5.3.4.3.1 Initiation of in-call modification | The procedure is initiated by the requesting originating side in the "active" state of the call. It shall send a MODIFY message including the new mode to be changed to. The requesting originating side shall also start timer T323 and enter the "mobile originating modify" state (mobile station side) or the "mobile terminating modify" state (network side). The new mode given in the MODIFY message shall be one of those already negotiated and agreed during the establishment phase of the call. If the data call direction is different from the direction of the call setup a reverse call setup direction IE shall be included in the MODIFY message; otherwise this IE shall not be included. If the in-call modification is originated by the mobile station, the mobile station shall reserve any internal resources necessary to support the next call mode, stop sending Bm-channel information; and stop interpreting received Bm-channel information according to the old call mode. If the in-call modification is originated by the network, the network may reserve any internal resources necessary to support the next call mode. The network shall stop sending Bm-channel information and stop interpreting received Bm-channel information according to the old call mode at the latest when it changes the channel configuration. Upon receipt of the MODIFY message, the destination side shall check to ensure that the requested call mode can still be supported and if so, it shall initiate the reservation of any resources necessary to support the next call mode; start T324 (mobile station side only) if the in-call modification procedure is triggered as a result of a service change from speech to UDI/RDI multimedia modes; and enter the "mobile originating modify" (network side) or "mobile terminating modify" state (mobile station 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 | 5.3.4.3.1 |
5,444 | 6.7.3.6 Algorithm negotiation for unauthenticated UEs in LSM | UEs that are in limited service mode (LSM) and that cannot be authenticated by the AMF/SEAF (for whatever reason) may still be allowed to establish emergency session by sending the emergency registration request message. It shall be possible to configure whether the AMF allows unauthenticated UEs in LSM to establish bearers for emergency session or not. If an AMF allows unauthenticated UEs in LSM to establish bearers for an emergency session, then for the NAS protocol, the AMF shall use NIA0 and NEA0 as the integrity and ciphering algorithm respectively. If the AMF allows an unauthenticated UE in LSM to establish bearers for emergency session after it has received the emergency registration request message from the UE, the AMF shall: - Select NIA0 and NEA0, regardless of the supported algorithms announced previously by the UE as the NAS algorithms and signal this to the UE via the NAS security mode command procedure when activating the 5G NAS security context. - Set the UE 5G security capabilities to only contain EIA0, EEA0, NIA0 and NEA0 when sending these to the gNB/ng-eNB in the following messages: - NGAP UE INITIAL CONTEXT SETUP - NGAP UE CONTEXT MODIFICATION REQUEST - NGAP HANDOVER REQUEST NOTE: As a result of that the AMF only sending a UE 5G security capability containing EIA0, EEA0, NIA0 and NEA0 to the gNB/ng-eNB , the gNB/ng-eNB is only able of selecting a null integrity protection for AS integrity protection and a null ciphering algorithm for AS confidentiality protection. That is, if NIA0 is used for NAS integrity protection, then NIA0 or EIA0 will always be used for AS integrity protection. If NIA0 is disabled at the gNB for regulatory requirements and the gNB receives the UE 5G security capabilities to only contain NIA0 for integrity protection algorithms from the AMF in one of the above messages, the gNB shall reject the session. The rules for when the AMF shall select NIA0 for NAS integrity protection, and when the UE shall accept a NAS security mode command selecting NIA0 for NAS integrity protection depends on whether the UE and AMF can be certain that no 5G NAS security context can be established. The rules for determining this is defined in clause 10 of this specification. If the AMF has selected NIA0 as the NAS integrity protection algorithm, the UE shall accept selection of NIA0 or EIA0 as the AS integrity protection algorithm. Selection of AS integrity protection algorithm happens via the AS security mode command procedure or via a handover command. The UE shall under no other circumstances accept selection of null integrity algorithm as the AS integrity protection algorithm. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.7.3.6 |
5,445 | 8.90 Additional MM context for SRVCC | The additional MM Context for SRVCC information element contains mobile station classmarks, supported codec list that are necessary for the AMF/MME/S4-SGSN to perform SRVCC as defined in 3GPP TS 23.216[ Single Radio Voice Call Continuity (SRVCC); Stage 2 ] [43]. The coding of Mobile Station Classmarks and Supported Codec List fields include the IE value part as it is specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [5]. Figure 8.90-1: Additional MM context for SRVCC For each of the Mobile Station Classmark 2, Mobile Station Classmark 3 and Supported Codec List parameters, if they are not available, then the associated length field shall be set to zero, and the particular parameter field shall not be present. | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 8.90 |
5,446 | – DRX-Config | The IE DRX-Config is used to configure DRX related parameters. DRX-Config information element -- ASN1START -- TAG-DRX-CONFIG-START DRX-Config ::= SEQUENCE { drx-onDurationTimer CHOICE { subMilliSeconds INTEGER (1..31), milliSeconds ENUMERATED { ms1, ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30, ms40, ms50, ms60, ms80, ms100, ms200, ms300, ms400, ms500, ms600, ms800, ms1000, ms1200, ms1600, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1 } }, drx-InactivityTimer ENUMERATED { ms0, ms1, ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30, ms40, ms50, ms60, ms80, ms100, ms200, ms300, ms500, ms750, ms1280, ms1920, ms2560, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1}, drx-HARQ-RTT-TimerDL INTEGER (0..56), drx-HARQ-RTT-TimerUL INTEGER (0..56), drx-RetransmissionTimerDL ENUMERATED { sl0, sl1, sl2, sl4, sl6, sl8, sl16, sl24, sl33, sl40, sl64, sl80, sl96, sl112, sl128, sl160, sl320, spare15, spare14, spare13, spare12, spare11, spare10, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1}, drx-RetransmissionTimerUL ENUMERATED { sl0, sl1, sl2, sl4, sl6, sl8, sl16, sl24, sl33, sl40, sl64, sl80, sl96, sl112, sl128, sl160, sl320, spare15, spare14, spare13, spare12, spare11, spare10, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1 }, drx-LongCycleStartOffset CHOICE { ms10 INTEGER(0..9), ms20 INTEGER(0..19), ms32 INTEGER(0..31), ms40 INTEGER(0..39), ms60 INTEGER(0..59), ms64 INTEGER(0..63), ms70 INTEGER(0..69), ms80 INTEGER(0..79), ms128 INTEGER(0..127), ms160 INTEGER(0..159), ms256 INTEGER(0..255), ms320 INTEGER(0..319), ms512 INTEGER(0..511), ms640 INTEGER(0..639), ms1024 INTEGER(0..1023), ms1280 INTEGER(0..1279), ms2048 INTEGER(0..2047), ms2560 INTEGER(0..2559), ms5120 INTEGER(0..5119), ms10240 INTEGER(0..10239) }, shortDRX SEQUENCE { drx-ShortCycle ENUMERATED { ms2, ms3, ms4, ms5, ms6, ms7, ms8, ms10, ms14, ms16, ms20, ms30, ms32, ms35, ms40, ms64, ms80, ms128, ms160, ms256, ms320, ms512, ms640, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1 }, drx-ShortCycleTimer INTEGER (1..16) } OPTIONAL, -- Need R drx-SlotOffset INTEGER (0..31) } DRX-ConfigExt-v1700 ::= SEQUENCE { drx-HARQ-RTT-TimerDL-r17 INTEGER (0..448), drx-HARQ-RTT-TimerUL-r17 INTEGER (0..448) } DRX-ConfigExt2-v1800 ::= SEQUENCE { drx-NonIntegerLongCycleStartOffset-r18 CHOICE { ms1001over240 INTEGER(0..3), ms25over6 INTEGER(0..3), ms25over3 INTEGER(0..7), ms1001over120 INTEGER(0..7), ms100over9 INTEGER(0..10), ms25over2 INTEGER(0..11), ms40over3 INTEGER(0..12), ms125over9 INTEGER(0..12), ms50over3 INTEGER(0..15), ms1001over60 INTEGER(0..15), ms125over6 INTEGER(0..19), ms200over9 INTEGER(0..21), ms250over9 INTEGER(0..26), ms100over3 INTEGER(0..32), ms1001over30 INTEGER(0..32), ms125over3 INTEGER(0..40), ms1001over24 INTEGER(0..40), ms200over3 INTEGER(0..65), ms1001over15 INTEGER(0..65), ms250over3 INTEGER(0..82), ms1001over12 INTEGER(0..82), ms400over3 INTEGER(0..132) }, shortDRX-r18 SEQUENCE { drx-NonIntegerShortCycle-r18 ENUMERATED {ms1001over240, ms25over6, ms25over3, ms1001over120, ms100over9, ms25over2, ms40over3, ms125over9, ms50over3, ms1001over60, ms125over6, ms200over9, ms100over3, ms1001over30, ms125over3, ms1001over24, ms200over3, spare15, spare14, spare13, spare12, spare11, spare10, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1}, drx-ShortCycleTimer-r18 INTEGER (1..16) } OPTIONAL, -- Need R drx-TimeReferenceSFN-r18 ENUMERATED {sfn512} OPTIONAL -- Need S } -- TAG-DRX-CONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,447 | 4.2.1.3 Number of initial E-RABs failed to setup | a) This measurement provides the number of initial E-RABs failed to setup. The measurement is split into subcounters per failure cause. b) CC c) On transmission by the eNodeB/RN of an INITIAL CONTEXT SETUP RESPONSE, or INITIAL CONTEXT SETUP FAILURE message, each E-RAB failed to establish is added to the relevant measurement per cause, the possible causes are included in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [9]. The sum of all supported per cause measurements shall equal the total number of E-RABs failed to setup. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first. d) Each measurement is an integer value. The number of measurements is equal to the number of causes plus a possible sum value identified by the .sum suffix. e) The measurement name has the form ERAB.EstabInitFailNbr.Cause where Cause identifies the cause resulting in the initial E-RAB setup failure. f) EUtranCellFDD EUtranCellTDD g) Valid for packet switched traffic h) EPS i) One usage of this measurement is to support the coverage ratio (CR) calculation for EE coverage area determination in [21]. | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.2.1.3 |
5,448 | 8.9.1.2.2 Closed-loop spatial multiplexing performance (Cell-Specific Reference Symbols) | 8.9.1.2.2.1 Minimum Requirement Single-Layer Spatial Multiplexing 2 Tx Antenna Port The requirements are specified in Table 8.9.1.2.2.1-2, with the addition of the parameters in Table 8.9.1.2.2.1-1 and the downlink physical channel setup according to Annex C.3.2. The purpose of these tests is to verify the closed loop rank-one performance with frequency selective precoding. Table 8.9.1.2.2.1-1: Test Parameters for Single-Layer Spatial Multiplexing (FRC) Table8.9.1.2.2.1-2: Minimum performance Single-Layer Spatial Multiplexing (FRC) 8.9.1.2.2.2 Minimum Requirement Single-Layer Spatial Multiplexing 4 Tx Antenna Port The requirements are specified in Table 8.9.1.2.2.2-2, with the addition of the parameters in Table 8.9.1.2.2.2-1 and the downlink physical channel setup according to Annex C.3.2. The purpose of these tests is to verify the closed loop rank-one performance with frequency selective precoding. Table 8.9.1.2.2.2-1: Test Parameters for Single-Layer Spatial Multiplexing (FRC( Table 8.9.1.2.2.2-2: Minimum performance Single-Layer Spatial Multiplexing (FRC) 8.9.1.2.2.3 Minimum Requirement Single-Layer Spatial Multiplexing 4 Tx Antenna Ports with CRS assistance information The requirements are specified in Table 8.9.1.2.2.3-2, with the addition of parameters in Table 8.9.1.2.2.3-1. In Table 8.9.1.2.2.3-1, Cell 1 is the serving cell, and Cell 2 and Cell 3 are the aggressor cells. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1, Cell 2 and Cell 3, respectively. The CRS assistance information [7] is provided to the UE and includes information on Cell 2 and Cell 3. The purpose of the test is to verify the closed loop single layer TM4 performance under assumption that UE applies CRS interference mitigation in the scenario with 4 CRS antenna ports in the serving and aggressor cells. Table 8.9.1.2.2.3-1: Test Parameters Table 8.9.1.2.2.3-2: Minimum performance for PDSCH | 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.9.1.2.2 |
5,449 | 4.16.15 Negotiations for planned data transfer with QoS requirements 4.16.15.1 General | The intent of this clause is to specify generic service procedures to enable the AF to negotiate viable time window for the planned application data transfer with specific QoS requirements and operational conditions via the support of the NEF. The PDTQ policies are defined for a specific ASP and each PDTQ policy includes a recommended time window for the traffic transfer for each of the AF sessions involved. The Network Performance analytics or DN Performance analytics for NWDAF as described in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50] will be subscribed by the PCF in order to assist its decision to derive the PDTQ policies. One or more negotiated PDTQ policies could be provided by PCF to AF via NEF together with the PDTQ Reference ID. If the AF receives more than one PDTQ policies from the PCF, the AF will select one of them and inform the PCF about the selected PDTQ policy which will then be stored in the UDR. The selected PDTQ policy might be renegotiated, i.e. due to the degradation of the network performance. In this case, the PCF may determine a new list of candidate PDTQ policies and notify the AF via NEF. The AF may select one of the new PDTQ polices or not accept any of the PDTQ policies, it then notifies the PCF of the corresponding decision. Prior to the start of the selected time window for the planned data transfer, the AF requests the PCF to set up the AF session with required QoS. The PCF will then determine the appropriate PCC rules according to the AF request. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.16.15 |
5,450 | 4.16.7.3 Procedure for BDT warning notification | Figure 4.16.7.3-1: The procedure for BDT warning notification 1. The negotiation for Background Data Transfer (BDT) described in clause 4.16.7.2 is completed. In addition, the PCF has subscribed to analytics on "Network Performance" from NWDAF for the area of interest and time window of a background data transfer policy following the procedure and services described in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50], including a Reporting Threshold in the Analytics Reporting information. The value for Reporting Threshold is set by the PCF based on operator configuration. 2. The PCF is notified with the network performance analytics in the area of interest from the NWDAF when the NWDAF determines that the network performance goes below the threshold as described for the Network Performance analytics in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]. 3. The H-PCF may request from the UDR the stored BDT policies using Nudr_DM_Query (Policy Data, Background Data Transfer) service operation. 4. The UDR provides all the Background Transfer Policies together with the relevant information received from the AF (as defined in clause 6.1.2.4 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]) to the H-PCF. 5. The H-PCF identifies the BDT policies affected by the notification received from NWDAF. For each of them, the H-PCF determines the ASP of which the background traffic will be influenced by the degradation of network performance and which requested the H-PCF to send the notification. The PCF then performs the following steps for each of the determined ASPs, i.e. Steps 6 - 16 can occur multiple times (i.e. once per ASP). 6. The PCF decides based on operator policies, whether a new list of candidate Background Data Transfer policies can be calculated for the ASP. If the PCF does not find any new candidate BDT policy, the previously negotiated BDT policy shall be kept, no interaction with that ASP shall occur and the procedure stops for that BDT policy. NOTE 1: The BDT policies of an ASP which did not request to be notified are kept and no interaction with this ASP occurs. 7. The PCF sets the no longer valid BDT policy in the UDR as invalidated by invoking Nudr_DM_Update (Background Data Transfer Reference ID, invalidation flag) service. NOTE 2: The BDT policies that are applicable for future sessions are checked by the PCF in step 6. 8. The UDR sends a response to the H-PCF as acknowledgement. 9. The PCF sends the notification to the NEF by invoking Npcf_PolicyControl_Notify (Background Data Transfer Reference ID, list of candidate Background Data Transfer policies) service operation. 10. The NEF sends the BDT warning notification to the AF by invoking Nnef_BDTPNegotiation_Notify (Background Data Transfer Reference ID, list of candidate Background Data Transfer policies) service operation. 11. The AF checks the new Background Data Transfer policies included in the candidate list in the BDT warning notification. 12. If the AF selects any of the new Background Data Transfer policies, the steps 8-13 from clause 4.16.7.2 are executed. 13. If the AF doesn't select any of the new Background Data Transfer policies, the steps 8-11 from clause 4.16.7.2 are executed, with the AF indicating that none of the candidate Background Data Transfer policies is acceptable. 14.-15. If the step 13 is executed, the PCF removes the no longer valid BDT policy from UDR for the corresponding Background Data Transfer Reference ID. NOTE 3: The PCF can also remove the no longer valid BDT policy after an operator configurable time for the case that the AF does not respond. 16. If there is a new Background Data Transfer policy stored in the UDR or a BDT policy removed from the UDR, the PCFs are notified by the UDR accordingly. The PCFs check if the corresponding URSP rules need to be updated or removed and if so, use the procedure defined in clause 4.16.12.2 to update URSP rules for the relevant UEs. The AF can send a Stop notification by invoking Nnef_BDTPNegotiation_Update service, when the AF requests not to receive the BDT warning notification anymore. Then, the NEF invokes Npcf_BDTPolicyControl_Update service in order to provide this information for the H-PCF. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.16.7.3 |
5,451 | 5.3.9.3 Purge function | The Purge function allows an MME to inform the HSS that it has deleted the subscription data and MM context of a detached UE. The MME may, as an implementation option, delete the subscription data and MM context of an UE immediately after the implicit or explicit detach of the UE. Alternatively the MME may keep for some time the subscription data and the MM context of the detached UE, so that the data can be reused at a later attach without accessing the HSS. Figure 5.3.9.3-1: Purge Procedure 1. After deleting the Subscription data and MM contexts of a detached UE, the MME sends Purge UE (IMSI) message to the HSS. 2. The HSS sets the UE Purged for E-UTRAN flag and acknowledges with a Purge UE Ack message. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.3.9.3 |
5,452 | 5.1.3.2.2 5GS update status in the UE | In order to describe the detailed UE behaviour, the 5GS update (5U) status pertaining to a specific subscriber is defined. If the UE is not operating in SNPN access operation mode (see 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]), the 5GS update status is stored in a non-volatile memory in the USIM if the corresponding file is present in the USIM, else in the non-volatile memory in the ME, as described in annex C. If the UE is operating in SNPN access operation mode, the 5GS update status for each SNPN whose SNPN identity is included in the "list of subscriber data" configured in the ME (see 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]) is stored in the non-volatile memory in the ME as described in annex C. The 5GS update status value is changed only after the execution of a registration, network-initiated de-registration, 5GS based primary authentication and key agreement, service request, paging procedure or due to change in the current TAI which does not belong to the current registration area while T3346 is running. 5U1: UPDATED The last registration attempt was successful. 5U2: NOT UPDATED The last registration or service request attempt failed procedurally, e.g. no response or reject message was received from the AMF. 5U3: ROAMING NOT ALLOWED The last registration, service request, or registration for mobility or periodic registration update attempt was correctly performed, but the answer from the AMF was negative (because of roaming or subscription restrictions). | 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.1.3.2.2 |
5,453 | 9.3.1.1.1 FDD | For the parameters specified in Table 9.3.1.1.1-1, and using the downlink physical channels specified in Annex C.3.2, the minimum requirements are specified in Table 9.3.1.1.1-2 and by the following a) a sub-band differential CQI offset level of 0 shall be reported at least % of the time but less than % for each sub-band; b) the ratio of the throughput obtained when transmitting on a randomly selected sub-band among the sub-bands with the highest differential CQI offset level the corresponding TBS and that obtained when transmitting the TBS indicated by the reported wideband CQI median on a randomly selected sub-band in set S shall be ≥ ; c) when transmitting on a randomly selected sub-band among the sub-bands with the highest differential CQI offset level the corresponding TBS, the average BLER for the indicated transport formats shall be greater or equal to 0.05. The requirements only apply for sub-bands of full size and the random scheduling across the sub-bands is done by selecting a new sub-band in each TTI for FDD, each available downlink transmission instance for TDD. Table 9.3.1.1.1-1 Sub-band test for single antenna transmission (FDD) Table 9.3.1.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.1.1.1 |
5,454 | 5.3.5.13.8 Subsequent CPAC execution | Upon the conditional reconfiguration execution for subsequent CPAC, the UE shall: 1> if the selected subsequent CPAC candidate configuration is stored in MCG VarConditionalReconfig: 2> release/clear all current dedicated radio configuration except for the following: - the MCG C-RNTI; - the AS security configurations associated with the master key and the secondary key; - for each SRB/DRB in current UE configuration: - keep the associated RLC, PDCP and SDAP entities, their state variables, buffers and timers; - release all fields related to the SRB/DRB configuration except for srb-Identity and drb-Identity; - the UE variables VarConditionalReconfig and VarServingSecurityCellSetID. 2> release/clear all current common radio configuration; 1> else: 2> release/clear all current dedicated radio configuration associated with the SCG except for the following: - the AS security configurations associated with the secondary key; - for each SRB/DRB in current UE configuration which is using the secondary key: - keep the associated RLC, PDCP and SDAP entities, their state variables, buffers and timers; - release all fields related to the SRB/DRB configuration except for srb-Identity and drb-Identity; - the UE variables VarConditionalReconfig. 2> release/clear all current common radio configuration associated with the SCG; 1> use the default values specified in 9.2.3 for timers T310, T311 and constants N310, N311 for the cell group for which the subsequent CPAC cell switch procedure is triggered; 1> if the securityCellSetId is included in the entry in VarConditionalReconfig containing the RRCReconfiguration message: 2> if servingSecurityCellSetId is not included within VarServingSecurityCellSetID; or 2> if the value of the securityCellSetId is not equal to the value of servingSecurityCellSetId within VarServingSecurityCellSetID: 3> consider the first sk-Counter value in the sk-CounterList associated with the securityCellSetId within the VarConditionalReconfig as the selected sk-Counter value, and perform security key update procedure as specified in 5.3.5.7; 3> remove the selected sk-Counter value from the sk-CounterList associated with the securityCellSetId within the VarConditionalReconfig; 3> if the current VarServingSecurityCellSetID includes servingSecurityCellSetId: 4> replace the value of servingSecurityCellSetId within VarServingSecurityCellSetID with the value of securityCellSetId associated with the selected cell; 3> else: 4> store the servingSecurityCellSetId within VarServingSecurityCellSetID with the value of securityCellSetId associated with the selected cell; 1> if the selected subsequent CPAC candidate configuration is stored in the SCG VarConditionalReconfig: 2> for each drb-Identity value included in RadioBearerConfig associated with the secondary key (S-KgNB) as indicated by keyToUse that is part of the current UE configuration: 3> trigger the PDCP entity of the AM DRB to perform PDCP data recovery as specified in TS 38.323[ NR; Packet Data Convergence Protocol (PDCP) specification ] [5]; 3> re-establish the corresponding RLC entity as specified in TS 38.322[ NR; Radio Link Control (RLC) protocol specification ] [4]; Editor's Note: FFS how the L2 reset (PDCP re-establishment, PDCP recovery, and RLC re-establishment) is indicated by the network in case of subsequent CPAC. 1> else: 2> for each drb-Identity value included in RadioBearerConfig that is part of the current UE configuration: 3> if a different keyToUse value is configured; or 3> if a new sk-Counter value has been selected due to the conditional reconfiguration execution for subsequent CPAC: 4> trigger the PDCP entity of the bearer to perform PDCP reestablishment as specified in TS 38.323[ NR; Packet Data Convergence Protocol (PDCP) specification ] [5]; 3> else: 4> trigger the PDCP entity of the AM DRB to perform PDCP data recovery as specified in TS 38.323[ NR; Packet Data Convergence Protocol (PDCP) specification ] [5]; 4> re-establish the corresponding RLC entity as specified in TS 38.322[ NR; Radio Link Control (RLC) protocol specification ] [4]; 1> if scpac-ConfigComplete is not included within the VarConditionalReconfig for the selected cell: 2> if the subsequent CPAC candidate cell configuration is stored in MCG VarConditionalReconfig: 3> consider scpac-ReferenceConfiguration in MCG VarConditionalReconfig to be the current UE configuration; 2> else: 3> consider scpac-ReferenceConfiguration in SCG VarConditionalReconfig to be the current SCG configuration; NOTE 1: When the UE considers the reference configuration to be the current UE configuration, the UE should store fields and configurations that are part of the reference configuration but should not execute any actions or procedures triggered by the reception of an RRCReconfiguration message which are described in clause 5.3.5.3. 1> apply the stored condRRCReconfig of the selected cell(s) and perform the actions as specified in 5.3.5.3; 1> release the radio bearer(s) and the associated logical channel(s) that are part of the current UE configuration but not part of the subsequent CPAC candidate configuration for the selected cell, or the subsequent CPAC reference configuration (in case the subsequent CPAC candidate configuration does not include scpac-ConfigComplete). NOTE 2: When scpac-ConfigComplete is not included for the selected cell, before a subsequent CPAC execution, a UE implementation may generate and store an RRC reconfiguration message by applying the received subsequent CPAC candidate configuration on top of the subsequent CPAC reference configuration, and the stored RRC reconfiguration message is applied for subsequent CPAC execution. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.5.13.8 |
5,455 | 4.1.1.4.2 Control of Network Mode of Operation I | The behaviour of the MS with respect to NMO I is determined by the combination of PS domain specific system information IE as defined in subclause 10.5.1.12.3 and the setting of the parameter "NMO_I_Behaviour" in the NAS configuration Management Object as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [135] or in USIM file NASCONFIG as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [112]: - if the parameter "NMO_I_Behaviour" in the NAS configuration Management Object is set to the value of "1", the bit 2 "NMO I" of system information as described in figure 10.5.1.12.3/table 10.5.1.12.3 is applied; or - if the parameter "NMO_I_Behaviour" in the NAS configuration Management Object is set to the value of zero or is not provisioned, the bit 1 "NMO" of system information as described in figure 10.5.1.12.3/table 10.5.1.12.3 is applied. | 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.1.4.2 |
5,456 | 4.8.3 Dual-registration mode | If both 5GMM and EMM are enabled, a UE, operating in the dual-registration mode shall maintain independent contexts for 5GMM and EMM and this includes independent lists of equivalent PLMNs. Coordination between 5GMM and EMM is not needed, except as specified in the present subclause, subclause 5.1.5 and 5.3.13A. For dual-registration mode the following applies: a) a UE operating in the dual-registration mode may register to N1 mode only, S1 mode only, or to both N1 mode and S1 mode; b) when the UE decides to operate in dual-registration mode (see subclause 5.5.1.2.4), NAS informs the lower layers about this; c) if a UE is registered in N1 mode only, then for registration in S1 mode the UE shall use: 1) the same PLMN to which it is registered in N1 mode; or 2) an equivalent PLMN; and d) if a UE is registered in S1 mode only, then for registration in N1 mode the UE shall use: 1) the same PLMN to which it is registered in S1 mode; or 2) an equivalent PLMN. NOTE 1: It is up to UE implementation how to handle the case when the UE is registered in both N1 mode and S1 mode and the PLMNs to which the UE is registered, are not equivalent, e.g. search for a PLMN which is the same or equivalent to any of the registered ones. When no PDU session is active and the UE has not registered to S1 mode yet, the UE may initiate the EPS attach procedure with PDN connection establishment if EMM-REGISTERED without PDN connection is not supported by the MME. If EMM-REGISTERED without PDN connection is supported by the MME, the UE may initiate either the EPS attach procedure without PDN connection establishment or the attach procedure with PDN connection establishment. When at least one PDU session is active and the UE has not registered to S1 mode yet, the UE may initiate the EPS attach procedure. If necessary, the UE may transfer an active PDU session from N1 mode to S1 mode by initiating the EPS attach procedure with request type set to "handover" in the PDN CONNECTIVITY REQUEST message. After successfully attached in S1 mode, if necessary, the UE may transfer other active PDU sessions from N1 mode to S1 mode by initiating the PDN connectivity procedure with request type set to "handover" in the PDN CONNECTIVITY REQUEST message. NOTE 2: It is up to UE implementation to determine which active PDU session is transferred from N1 mode to S1 mode. When the UE has not registered to N1 mode, the UE may initiate the initial registration procedure. After successfully registered in N1 mode, if necessary, the UE may transfer one or more active PDN connections from S1 mode to N1 mode by initiating the PDU session establishment procedure with request type set to "existing PDU session". NOTE 3: It is up to UE implementation to determine which active PDN connection is transferred from S1 mode to N1 mode. If the MME supports EMM-REGISTERED without PDN connection, the UE that transferred all PDN connections to the 5GS, may stay in state EMM-REGISTERED. Otherwise, the UE shall enter state EMM-DEREGISTERED upon transferring all PDN connection to the 5GS. NOTE 4: When the UE has registered in both N1 mode and S1 mode, it is up to UE implementation to maintain the registration update to date in both N1 mode and S1 mode. See subclause 6.1.4 for coordination between 5GSM and ESM. See subclause 4.8.2.3.2 for interworking between TNGF or N3IWF connected to 5GCN and E-UTRAN. | 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.8.3 |
5,457 | 6.9.2 Resource group alignment, layer mapping and precoding | The block of symbols should be first aligned with resource element group size, resulting in a block of symbols , where for normal cyclic prefix; and for extended cyclic prefix. For normal cyclic prefix, , for . For extended cyclic prefix, for . The block of symbols shall be mapped to layers and precoded, resulting in a block of vectors , , where represents the signal for antenna port , and the number of cell-specific reference signals . The layer mapping and precoding operation depends on the cyclic prefix length and the number of antenna ports used for transmission of the PHICH. The PHICH shall be transmitted on the same set of antenna ports as the PBCH. For transmission on a single antenna port, , layer mapping and precoding are defined by clauses 6.3.3.1 and 6.3.4.1, respectively, with . For transmission on two antenna ports, , layer mapping and precoding are defined by clauses 6.3.3.3 and 6.3.4.3, respectively, with . For transmission on four antenna ports, , layer mapping is defined by clause 6.3.3.3 with and precoding by if for normal cyclic prefix, or for extended cyclic prefix, where is the PHICH group number and , and by otherwise for . | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.9.2 |
5,458 | 12.1.3 Load & overload control concepts | Load control refers to "GTP-C signalling based Load Control" as defined in clause 4.3.7.1a.1 of 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [3] and clause 5.3.6.1a of 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [35]. Overload control refers to "GTP-C signaling based Overload Control" as defined in clause 4.3.7.1a.2 of 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [3] and clause 5.3.6.1a of 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [35]. Load control and overload control are two distinct but complementary concepts: - load control enables a GTP-C entity (e.g. an SGW/PGW) to send its load information to a GTP-C peer (e.g. an MME/SGSN, ePDG, TWAN) to adaptively balance the session load across entities supporting the same function (e.g. an SGW cluster) according to their effective load. The load information reflects the operating status of the resources of the GTP-C entity. - overload control enables a GTP-C entity becoming or being overloaded to gracefully reduce its incoming signalling load by instructing its GTP-C peers to reduce sending traffic according to its available signalling capacity to successfully process the traffic. A GTP-C entity is in overload when it operates over its signalling capacity which results in diminished performance (including impacts to handling of incoming and outgoing traffic). Load control allows for better balancing of the session load, so as to attempt to prevent overload in the first place (preventive action). Overload control aims at shedding the incoming traffic as close to the traffic source as possible generally when an overload has occurred (reactive action), so to avoid spreading the problem inside the network and to avoid using resources of intermediate nodes in the network for signalling that would anyhow be discarded by the overloaded node. Load control does not trigger overload mitigation actions even if the GTP-C entity reports a high load. Load control and overload control may be supported and activated independently in the network. | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 12.1.3 |
5,459 | 8.2.1.1.1 Minimum Requirement | For single carrier, the requirements are specified in Table 8.2.1.1.1-2, with the addition of the parameters in Table 8.2.1.1.1-1 and the downlink physical channel setup according to Annex C.3.2. For CA with 2 DL CCs, the requirements are specified in Table 8.2.1.1.1-4, with the addition of the parameters in Table 8.2.1.1.1-3 and the downlink physical channel setup according to Annex C.3.2. For CA with 3 DL CCs, the requirements are speicifed in Table 8.2.1.1.1-6, based on single carrier requirement speicified in Table 8.2.1.1.1-5, with the addition of the parameters in Table 8.2.1.1.1-3 and the downlink physical channel setup according to Annex C.3.2. For CA with 4 DL CCs, the requirements are speicifed in Table 8.2.1.1.1-7, based on single carrier requirement speicified in Table 8.2.1.1.1-5, with the addition of the parameters in Table 8.2.1.1.1-3 and the downlink physical channel setup according to Annex C.3.2. For CA with 5 DL CCs, the requirements are speicifed in Table 8.2.1.1.1-8, based on single carrier requirement speicified in Table 8.2.1.1.1-5, with the addition of the parameters in Table 8.2.1.1.1-3 and the downlink physical channel setup according to Annex C.3.2. For CA with 6 DL CCs, the requirements are speicifed in Table 8.2.1.1.1-9, based on single carrier requirement speicified in Table 8.2.1.1.1-5, with the addition of the parameters in Table 8.2.1.1.1-3 and the downlink physical channel setup according to Annex C.3.2. For CA with 7 DL CCs, the requirements are speicifed in Table 8.2.1.1.1-10, based on single carrier requirement speicified in Table 8.2.1.1.1-5, with the addition of the parameters in Table 8.2.1.1.1-3 and the downlink physical channel setup according to Annex C.3.2. The test coverage for different number of component carriers is defined in 8.1.2.4. Table 8.2.1.1.1-1: Test Parameters Table 8.2.1.1.1-2: Minimum performance (FRC) Table 8.2.1.1.1-3: Test Parameters for CA Table 8.2.1.1.1-4: Minimum performance (FRC) for CA with 2DL CCs Table 8.2.1.1.1-5: Single carrier performance for multiple CA configurations Table 8.2.1.1.1-6: Minimum performance (FRC) based on single carrier performance for CA with 3DL CCs Table 8.2.1.1.1-7: Minimum performance (FRC) based on single carrier performance for CA with 4DL CCs Table 8.2.1.1.1-8: Minimum performance (FRC) based on single carrier performance for CA with 5DL CCs Table 8.2.1.1.1-9: Minimum performance (FRC) based on single carrier performance for CA with 6DL CCs Table 8.2.1.1.1-10: Minimum performance (FRC) based on single carrier performance for CA with 7DL CCs | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.2.1.1.1 |
5,460 | 5.7.3.2 Initiation | A UE initiates the procedure to report SCG failures when neither MCG nor SCG transmission is suspended and when one of the following conditions is met: 1> upon detecting radio link failure for the SCG, in accordance with clause 5.3.10.3; 1> upon detecting beam failure of the PSCell while the SCG is deactivated, in accordance with TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3]; 1> upon reconfiguration with sync failure of the SCG, in accordance with clause 5.3.5.8.3; 1> upon SCG configuration failure, in accordance with clause 5.3.5.8.2; 1> upon integrity check failure indication from SCG lower layers concerning SRB3. Upon initiating the procedure, the UE shall: 1> if the procedure was not initiated due to beam failure of the PSCell while the SCG is deactivated: 2> suspend SCG transmission for all SRBs, DRBs and, if any, BH RLC channels; 2> reset SCG MAC; 1> stop T304 for the SCG, if running; 1> stop conditional reconfiguration evaluation for CPC, CPA, or subsequent CPAC, if configured; 1> stop conditional reconfiguration evaluation for each CHO configuration that includes condExecutionCondPSCell, if configured; 1> if the UE is in (NG)EN-DC: 2> initiate transmission of the SCGFailureInformationNR message as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10], clause 5.6.13a. 1> else: 2> initiate transmission of the SCGFailureInformation message in accordance with 5.7.3.5. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.7.3.2 |
5,461 | 5.7.3c.4 Actions related to transmission of IndirectPathFailureInformation message | The UE shall set the contents of the IndirectPathFailureInformation message as follows: 1> set the failureTypeIndirectPath in accordance with 5.7.3c.3; 1> if the procedure was initiated to report SL indirect path failure: 2> set the sl-MeasResultServingRelay to include the measurement result for serving L2 U2N Relay UE if available; 2> for each measObjectRelay included MeasConfig, and for which measurement results are available: 3> include an entry in sl-MeasResultsCandRelay; 1> else if the procedure was initiated to report N3C indirect path failure; 2> include n3c-relayUE-InfoList to report relay UE information with non-3GPP connection(s) if available; 1> submit the IndirectPathFailureInformation message to lower layers for transmission. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.7.3c.4 |
5,462 | 7.4 Unknown or unforeseen message type | If UE receives an EMM message or ESM message with message type not defined for the protocol discriminator (PD) or not implemented by the receiver, it shall return a status message (EMM STATUS or ESM STATUS depending on the PD) with cause #97 "message type non-existent or not implemented". If the network receives an EMM or ESM message with message type not defined for the PD or not implemented by the receiver in a protocol state where reception of an unsolicited message with the given PD from the UE is not foreseen in the protocol, the network actions are implementation dependent. Otherwise, if the network receives a message with message type not defined for the PD or not implemented by the receiver, it shall ignore the message except that it should return a status message (EMM STATUS or ESM STATUS depending on the PD) with cause #97 "message type non-existent or not implemented". NOTE: A message type not defined for the PD in the given direction is regarded by the receiver as a message type not defined for the PD, see 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [12]. If the UE receives a message not compatible with the protocol state, the UE shall return a status message (EMM STATUS or ESM STATUS depending on the PD) with cause #98 "message type not compatible with protocol state". If the network receives a message not compatible with the protocol state, the network actions are implementation dependent. | 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 | 7.4 |
5,463 | 5.3.16 Extended DRX cycle for UEs in 5GMM-IDLE and 5GMM-CONNECTED mode with RRC inactive indication | Extended DRX (eDRX) cycle is supported for a UE in N1 mode. When eDRX is requested by the UE and accepted by the network: - if the UE is not in NB-N1 mode, eDRX is used when the UE is in 5GMM-IDLE mode or in 5GMM-CONNECTED mode with RRC inactive indication; or - if the UE is in NB-N1 mode, eDRX is used when the UE is in 5GMM-IDLE mode. The UE may request the use of eDRX cycle during a registration procedure by including the Requested extended DRX parameters IE (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 not request the use of eDRX during a registration procedure for emergency services. The UE may use the extended idle mode DRX cycle length stored in the USIM (see 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [22]) when requesting the use of eDRX. The UE and the network may negotiate eDRX parameters during a registration procedure when the UE has an emergency PDU session. The network accepts the request to use the eDRX by providing the Negotiated extended DRX parameters IE when accepting the registration procedure. The UE shall use eDRX only if it received the Negotiated extended DRX parameters IE during the last registration procedure and the UE does not have an emergency PDU session. NOTE 1: If the UE wants to keep using eDRX, the UE includes the Extended DRX parameters IE in each registration procedure. If the UE received the Negotiated extended DRX parameters IE during the last registration procedure, upon successful completion of the PDU session release procedure of the emergency PDU session, the UE shall resume eDRX. If the network has provided the Negotiated extended DRX parameters IE during the last registration procedure, upon successful completion of the PDU session release procedure of the emergency PDU session, the network shall resume eDRX. If the UE or the network locally releases an emergency PDU session, the UE or the network shall not use eDRX until the UE receives eDRX parameters during a registration procedure with PDU session context synchronization or upon successful completion of a service request procedure with PDU session context synchronization. If the UE did not receive the Negotiated extended DRX parameters IE, or if the UE has an emergency PDU session, the UE shall use the stored UE specific DRX parameter, if available. If the network did not accept the request to use eDRX, or if the UE has an emergency PDU session, the network shall use the stored UE specific DRX parameter, if available. If the network provided the Negotiated extended DRX parameters IE and also assigned a new 5G-GUTI for the UE as described in subclause 5.5.1.3.4 during the last registration procedure, the network shall use the stored UE specific DRX parameter, if available, with the old 5G-GUTI and use the eDRX provided by the network with the new 5G-GUTI until the old 5G-GUTI can be considered as invalid by the network (see subclauses 5.4.4.4 and 5.5.1.3.4). NOTE 2: If the UE using eDRX has joined one or more multicast MBS sessions or wants to receive the traffic of broadcast MBS sessions, the upper layers of the UE provide the lower layers with the MBS start time and the scheduled activation times of the respective MBS session if any of those times are obtained via the service announcement as specified in 3GPP TS 23.247[ Architectural enhancements for 5G multicast-broadcast services ] [53]. This interaction between the upper layers and the lower layers is out of scope of the present document. | 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.16 |
5,464 | 5.15.15.3 Network-based per UE Network Slice usage behaviour control | The 5GC performs Network Slice usage monitoring to be able to enforce the release of inactive PDU Sessions, and deregistering of UEs from Network Slices with no PDU Sessions on them according to its own policies. In order to support usage monitoring for a Network Slice: - the AMF runs a slice deregistration inactivity timer per S-NSSAI and access type to deregister the Network Slice which is started when the Network Slice is not used by any PDU Session over the corresponding access type. The slice deregistration inactivity timer is stopped and reset when at least a PDU Session associated with the Network Slice is successfully established or the Network Slice is removed form the Allowed NSSAI. When the slice deregistration inactivity timer for a Network Slice over an access type expires, the AMF removes the Network Slice from the Allowed NSSAI over the access type by sending the UE Configuration Update Command to impacted UE(s). - the SMFs provide to UPFs that handle the PDU sessions in the Network Slice a PDU Session inactivity timer. The PDU Session inactivity timer is started after no data packet is transmitted or received and runs until the next data packet is transmitted or received which restarts the timer again. If the PDU Session inactivity timer expires before any packet is received or transmitted, the UPF reports this PDU Session inactivity event to the SMF to cause the SMF to release the PDU Session. While releasing the PDU session the SMF may indicate the release cause because of slice inactivity. When the AMF receives the notification of PDU Session release and it includes the release cause of slice inactivity and if the Network Slice of the released PDU Session is not used by other PDU Sessions (i.e. the last PDU Session using the Network Slice is released) over the corresponding access type, the AMF may trigger the UE Configuration Update procedure to remove the Network Slice from the Allowed NSSAI over that corresponding access type or start slice deregistration inactivity timer for the Network Slice. If the PDU Session inactivity timer value is updated, the SMF provides the updated PDU Session inactivity timer value to the UPF. The UPF uses the updated PDU Session inactivity timer value immediately or next time the PDU Session inactivity timer starts. NOTE: For MA PDU Session, the PDU Session inactivity timer is independent of Access Type. If an S-NSSAI is dedicated for a single AF, and if authorized by operator policy to provide deregistration inactivity/PDU Session inactivity timer values for the S-NSSAI, the AF uses external parameter provisioning procedure to provide deregistration inactivity and PDU session inactivity timer values as described in clause 4.15.6.3g of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. In this case, the AF provided timer values are stored in the UDM and provided to the AMF/SMF as part of subscription data for the corresponding S-NSSAI. If no AF is authorized to provide deregistration inactivity/PDU Session inactivity timer values for the S-NSSAI, i.e. no timer value received from UDM, the slice deregistration inactivity timer value and PDU Session inactivity timer value are either pre-configured in the AMF/SMF or received by the AMF/SMF during the AM Policy Association / SM Policy Association procedure respectively. To enable a serving network to direct UEs to a preferred Network Slice, the AMF may request the UE to transfer a PDU Session from one S-NSSAI to another S-NSSAI as described in clause 5.15.19. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.15.15.3 |
5,465 | 6.5.1E Frequency error for UE category M1 and M2 | For category M1 and M2 TDD UEs and FD-FDD UEs, the frequency error requirements in Clause 6.5.1 apply. For category M1 and M2 HD-FDD UEs and for continuous uplink transmissions of duration ≤ 64 ms, the frequency error requirements in Clause 6.5.1 apply. For category M1 and M2 HD-FDD UEs and for continuous uplink transmissions of duration > 64 ms, the UE modulated carrier frequency shall be accurate to within the limits in Table 6.5.1E-1 observed over a period of one time slot (0.5 ms) compared to the carrier frequency received from the E-UTRA Node B. Table 6.5.1E-1: Frequency error requirement for HD-FDD UE category M1 and M2 | 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.1E |
5,466 | 6.2.3G.2 MPR for Power class 2 V2X UE | For contiguous allocation of PSCCH and PSSCH simultaneous transmission, the allowed MPR for the maximum output power for V2X physical channels PSCCH and PSSCH shall be as specified in Table 6.2.3G.2-1 for power class 2. Table 6.2.3G.2-1: Maximum Power Reduction (MPR) for power class 2 V2X Communication (Contiguous PSCCH and PSSCH transmission) For non-contiguous allocation of PSCCH and PSSCH simultaneous transmission, the allowed MPR for the maximum output power for V2X physical channels PSCCH and PSSCH shall be as specified as follows: MPR = CEIL {MA, 0.5} Where MA is defined as follows For 10MHz channel bandwidth MA = 4.5 ; 0.0< A ≤ 0.2 8.5 – 20.0A ; 0.2< A ≤0.3 2.5 ; 0.3< A ≤1.00 For 20MHz channel bandwidth MA = 9.0 ; 0.0< A ≤ 0.1 12.0 – 30.0A ; 0.1< A ≤0.3 3.0 ; 0.3< A ≤1.00 Where A = NRB_alloc / NRB. CEIL{MA, 0.5} means rounding upwards to closest 0.5dB. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.2.3G.2 |
5,467 | – SIB22 | SIB22 contains ATG assistant information. SIB22 information element -- ASN1START -- TAG-SIB22-START SIB22-r18 ::= SEQUENCE { atg-Config-r18 ATG-Config-r18 OPTIONAL, -- Need R hs-ATG-cellReselectionSet-r18 ENUMERATED {true} OPTIONAL, -- Need R atg-NeighCellConfigList-r18 ATG-NeighCellConfigList-r18 OPTIONAL, -- Need R lateNonCriticalExtension OCTET STRING OPTIONAL, ... } ATG-NeighCellConfigList-r18 ::= SEQUENCE (SIZE(1..maxCellATG-r18)) OF ATG-NeighCellConfig-r18 ATG-NeighCellConfig-r18 ::= SEQUENCE { atg-gNB-Location-r18 ReferenceLocation-r17 OPTIONAL, -- Need R heightgNB-r18 INTEGER (-16384..16383) OPTIONAL, -- Need R carrierFreq-r18 ARFCN-ValueNR OPTIONAL, -- Need R physCellId-r18 PhysCellId OPTIONAL, -- Need R ... } -- TAG-SIB22-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,468 | 5.2.3.2.3 Nudm_UECM_Deregistration service operation | Service operation name: Nudm_UECM_Deregistration. Description: The NF consumer requests the UDM to delete the information related to the NF in the UE context. When the consumer is AMF, this implies that the subscriptions to be notified when the NF is deregistered in UDM (i.e. Nudm_UECM_DeregistrationNotification) are also removed. Inputs, Required: SUPI, NF type, Access Type, PDU Session Id (if NF Type is SMF), Analytics ID(s) (if NF Type is NWDAF). - Access Type is included only when the NF type indicates AMF or SMSF. Inputs, Optional: None. Outputs, Required: Result Indication. Outputs, Optional: None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.3.2.3 |
5,469 | 6.10.3.1 Sequence generation | For antenna port 5, the UE-specific reference-signal sequence is defined by where denotes the assigned bandwidth in resource blocks of the corresponding PDSCH transmission. The pseudo-random sequence is defined in clause 7.2. The pseudo-random sequence generator shall be initialised with at the start of each subframe where is as described in clause 7.1 TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4]. For any of the antenna ports , the reference-signal sequence is defined by . The pseudo-random sequence is defined in clause 7.2. The pseudo-random sequence generator shall be initialised with at the start of each subframe. For BL/CE UEs, the same scrambling sequence is applied per subframe to the UE-specific reference-signal sequence for a given block of subframes. The subframe number of the first subframe in each block of consecutive subframes, denoted as , satisfies . For the block of subframes, the scrambling sequence generator shall be initialised with where and is the absolute subframe number of the first downlink subframe intended for PDSCH. The PDSCH transmissions span consecutive subframes, including subframes that are not BL/CE DL subframes where the PDSCH transmission is postponed. For a BL/CE UE configured in CEModeA, . For a BL/CE UE configured with CEModeB, for frame structure type 1 and for frame structure type 2. The quantities , , are given by - if no value for is provided by higher layers or if DCI format 1A, 2B or 2C is used for the DCI associated with the PDSCH transmission - otherwise The value of is zero unless specified otherwise. For a PDSCH transmission on ports 7 or 8, is given by the DCI format 2B, 2C, 2D, 6-1A, 7-1E, 7-1F and 7-1G in TS 36.212[ Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and channel coding ] [3] associated with the PDSCH transmission. In the case of DCI format 2B or 7-1E, is indicated by the scrambling identity field according to Table 6.10.3.1-1. In the case of DCI format 2C or 2D, is given by Table 5.3.3.1.5C-1, Table 5.3.3.1.5C-2 or Table 5.3.3.1.5C-6 in TS 36.212[ Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and channel coding ] [3]. In the case of DCI format 7-1F or 7-1G, is given by Table 5.3.3.1.22-1, Table 5.3.3.1.22-2, Table 5.3.3.1.22-3 or Table 5.3.3.1.5C-6 in TS 36.212[ Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and channel coding ] [3]. For a PDSCH transmission on ports 11 or 13, is given by the DCI format 2C or 2D in TS 36.212[ Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and channel coding ] [3] associated with the PDSCH transmission where is given by Table 5.3.3.1.5C-2 in TS 36.212[ Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and channel coding ] [3]. Table 6.10.3.1-1: Mapping of scrambling identity field in DCI format 2B to values for antenna ports 7 and 8 | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.10.3.1 |
5,470 | 5.2.8.2.3 Nsmf_PDUSession_Update service operation | Service operation name: Nsmf_PDUSession_Update. Description: Update the established PDU Session. This service operation is invoked by the V-SMF towards the H-SMF in the case of UE or serving network requested PDU Session Modification in order for the V-SMF to transfer the PDU Session Modification request. It can also be invoked by the V-SMF to indicate to the H-SMF that the access type of the PDU session can be changed. This service operation is also invoked by the V-SMF to insert or remove UL CL or BP controlled by the V-SMF. This service operation is invoked by the I-SMF towards the SMF in the case of UE or serving network requested PDU Session Modification in order for the I-SMF to transfer the PDU Session Modification request. It can also be invoked by the I-SMF to indicate to the SMF that the access type of the PDU session can be changed. This service operation is also invoked by the I-SMF towards the SMF to insert or remove ULCL or BP controlled by the I-SMF or to report usage offloaded via UL CL or BP controlled by I-SMF. This service operation is invoked by the H-SMF towards the V-SMF for both UE initiated and HPLMN initiated PDU Session Modification and PDU Session Release cases in order to have the SM PDU Session Modification request or SM PDU Session Release request sent to the UE. It can also be invoked by the H-SMF towards the V-SMF to release the 5GC and 5G-AN resources in e.g. handover from 5GC-N3IWF to EPS and from 5GS to EPC/ePDG, wherein the UE is not notified. This service operation is invoked by the SMF towards the I-SMF for both UE initiated and SMF/PCF initiated PDU Session Modification and PDU Session Release cases in order to have the SM PDU Session Modification request or SM PDU Session Release request sent to the UE. It can also be invoked by the SMF towards the I-SMF to release the 5GC and 5G-AN resources in e.g. handover from 5GC-N3IWF to EPS and from 5GS to EPC/ePDG, wherein the UE is not notified. This service operation is also invoked by the SMF towards the I-SMF to provide updated N4 information or updated DNAI list of interest for this PDU Session when SMF receives updated PCC rules. This service operation is invoked by the V-SMF or I-SMF and the H-SMF or SMF in the case of PDU Session Establishment authentication/authorization by a DN-AAA Server defined in clause 4.3.2.3: it is used to carry DN Request Container information between the DN-AAA Server and the UE. Input, Required: SM Context ID. Input, Optional: UE location information (ULI), UE Time Zone, AN type, indication of PDU Session Release, H-SMF SM Context ID (from H-SMF to V-SMF) or SMF SM Context ID (from SMF to I-SMF), QoS Rule and QoS Flow level QoS parameters if any for the QoS Flow associated with the QoS rule (from H-SMF to V-SMF or from SMF to I-SMF), EPS bearer context(s) and Linked EBI (from H-SMF to V-SMF or from SMF to I-SMF), N9 Tunnel Info (from V-SMF to H-SMF or from I-SMF to SMF), Information requested by UE for e.g. QoS (from V-SMF to H-SMF or from I-SMF to SMF), 5GSM Core Network Capability, Information necessary for V-SMF or I-SMF to build SM Message towards the UE (from H-SMF to V-SMF or from SMF to I-SMF), Trigger PDU release indication (V-SMF to H-SMF or from I-SMF to SMF), Start Pause of Charging indication, Stop Pause of Charging indication, DN Request Container information, indication that the UE shall not be notified, EBI Allocation Parameters (ARP list), Secondary RAT usage data, indication that the access type of the PDU session can be changed (V-SMF to H-SMF or from I-SMF to SMF) or from SMF to I-SMF), extended NAS-SM timer indication, DNAI list supported by I-SMF (from I-SMF to SMF), indication of multi-homing support (from SMF to I-SMF), indication of ULCL or BP insertion (from I-SMF to SMF), indication of ULCL or BP removal (from I-SMF to SMF), IPv6 prefix @local PSA (from I-SMF to SMF), DNAI(s) supported by local PSA (from I-SMF to SMF), Tunnel info of ULCL or BP (from I-SMF to SMF), N4 information (from I-SMF to SMF or from SMF to I-SMF), Handover Complete Indication, Relocation Cancel Indication. MA PDU request indication, MA PDU Network-Upgrade Allowed indication, Indication on whether the UE is registered in both accesses, MA PDU session Accepted indication, access for MA PDU Session Release, access type for GBR QoS flow, Indication of access unavailability (with access type), QoS Monitoring Indication (from SMF to I-SMF), QoS Monitoring reporting frequency(from SMF to I-SMF), QoS monitoring policy (from SMF to I-SMF), QoS Monitoring Result from (I-SMF to SMF), Notification of the SM Policy Association Establishment and Termination, PCF binding information, Satellite backhaul category, N9 forwarding tunnel to support the EAS session continuity required (from SMF to I-SMF), traffic filter for N9 forwarding (from SMF to I-SMF), value of the timer to detect the end of activity on the N9 forwarding tunnel to support the EAS session continuity (from SMF to I-SMF), EAS rediscovery indication, EAS information to be refreshed for EAS re-discovery, IP address of V-EASDF, ECS Address Configuration Information, Alternative HPLMN S-NSSAI, HR-SBO authorization result, VPLMN Specific Offloading Information for HR-SBO, HPLMN address information, DNS Server address provided by HPLMN, Indication of UE supports non-3GPP access path switching. Output, Required: Result indication, <ARP, Cause> pair. Output, Optional: UE location information, AN Type, SM information from UE (from V-SMF to H-SMF or from I-SMF to SMF), list of Rejected QoS Flows (from V-SMF to H-SMF or from I-SMF to SMF), a list of <ARP, EBI> pair, Secondary RAT Usage Data, DNAI(s) of interest for this PDU Session (from SMF to I-SMF), N4 Information (from SMF to I-SMF), QFI(s), QoS Profile(s), Session-AMBR, QoS Rule(s), QoS Flow level QoS parameters if any for the QoS Flow(s) associated with the QoS rule(s), EPS bearer context(s), linked EBI, DNAI(s) of interest for this PDU Session, HR-SBO authorization result, VPLMN Specific Offloading Information for HR-SBO, HPLMN address information, DNS Server address provided by HPLMN, Internal Group Identifier(s). The H-SMF SM Context ID in the Input provides addressing information allocated by the H-SMF (to be used for service operations towards the H-SMF for this PDU Session). The SMF SM Context ID in the Input provides addressing information allocated by the SMF (to be used for service operations towards the SMF for this PDU Session). See clause 4.3.3.3 for an example usage of this service operation. See clauses 4.22.6.3, 4.22.7, 4.22.8.3 and 4.22.10.3 for detailed usage of this service operation for ATSSS. See clause 6.7.3 of TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [74] for detailed usage of this service for EAS re-discovery. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.8.2.3 |
5,471 | 8.22 Fully Qualified TEID (F-TEID) | Fully Qualified Tunnel Endpoint Identifier (F-TEID) is coded as depicted in Figure 8.22-1. Figure 8.22-1: Fully Qualified Tunnel Endpoint Identifier (F-TEID) The following flags are coded within Octet 5: - Bit 8 – V4: If this bit is set to "1", then IPv4 address field exists in the F-TEID, otherwise the IPv4 address field is not present at all. - Bit 7 – V6: If this bit is set to "1", then IPv6 address field exists in the F-TEID, otherwise the IPv6 address field is not present at all. At least one of V4 and V6 shall be set to "1", and both may be set to "1". - Bit 6 to Bit 1 – Interface Type: This 6 bit wide integer can take the following values representing interface type and endpoint: 0: S1-U eNodeB GTP-U interface 1: S1-U SGW GTP-U interface 2: S12 RNC GTP-U interface 3: S12 SGW GTP-U interface 4: S5/S8 SGW GTP-U interface 5: S5/S8 PGW GTP-U interface 6: S5/S8 SGW GTP-C interface 7: S5/S8 PGW GTP-C interface 8: S5/S8 SGW PMIPv6 interface (the 32 bit GRE key is encoded in 32 bit TEID field) 9: S5/S8 PGW PMIPv6 interface (the 32 bit GRE key is encoded in the 32 bit TEID field, see clause 6.3 in 3GPP TS 29.275[ Proxy Mobile IPv6 (PMIPv6) based Mobility and Tunnelling protocols; Stage 3 ] [26]) 10: S11 MME GTP-C interface 11: S11/S4 SGW GTP-C interface 12: S10/N26 MME GTP-C interface 13: S3 MME GTP-C interface 14: S3 SGSN GTP-C interface 15: S4 SGSN GTP-U interface 16: S4 SGW GTP-U interface 17: S4 SGSN GTP-C interface 18: S16 SGSN GTP-C interface 19: eNodeB/gNodeB GTP-U interface for DL data forwarding 20: eNodeB GTP-U interface for UL data forwarding 21: RNC GTP-U interface for data forwarding 22: SGSN GTP-U interface for data forwarding 23: SGW/UPF GTP-U interface for DL data forwarding 24: Sm MBMS GW GTP-C interface 25: Sn MBMS GW GTP-C interface 26: Sm MME GTP-C interface 27: Sn SGSN GTP-C interface 28: SGW GTP-U interface for UL data forwarding 29: Sn SGSN GTP-U interface 30: S2b ePDG GTP-C interface 31: S2b-U ePDG GTP-U interface 32: S2b PGW GTP-C interface 33: S2b-U PGW GTP-U interface 34: S2a TWAN GTP-U interface 35: S2a TWAN GTP-C interface 36: S2a PGW GTP-C interface 37: S2a PGW GTP-U interface 38: S11 MME GTP-U interface 39: S11 SGW GTP-U interface 40: N26 AMF GTP-C interface 41: N19mb UPF GTP-U interface Other values of "Interface Type" are spare and reserved for future use. "Interface type" values with bit "6" set to 1 shall only be used between Rel-10 onwards GTPv2-C nodes. NOTE 1: "Interface type" IE is defined with 5 bits only in the earlier releases of this specification, thus pre-Rel-10 GTPv2-C nodes can ignore bit "6" which is marked as "Spare" in earlier releases, allowing backward compatibility. NOTE 2: Interface Type 8 is not used in this Release and in earlier Releases. Octet 6 to 9 (TEID/GRE field) represent either a TEID or a GRE key. If both IPv4 and IPv6 addresses are present in F-TEID IE, then the TEID value shall be shared by both addresses. Octets "m to (m+3)" and/or "p to (p+15)" (IPv4 address / IPv6 address fields), if present, contain respective address values. | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 8.22 |
5,472 | 9.3.6 Connect acknowledge | This message is sent by the network to the called mobile station to indicate that the mobile station has been awarded the call. It shall also be sent by the calling mobile station to the network to acknowledge the offered connection. See table 9.60/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Message type: CONNECT ACKNOWLEDGE Significance: local Direction: both Table 9.60/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : CONNECT ACKNOWLEDGE message content | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.3.6 |
5,473 | 9.8.3 Security mechanisms for the E1 interface | The E1 interface connects the gNB-CU-CP to the gNB-CU-UP. It is only used for the transport of signalling data. In order to protect the traffic on the E1 interface, IPsec ESP and IKEv2 certificates-based authentication shall be supported as specified in sub-clause 9.1.2 of the present document with confidentiality, integrity and replay protection. In addition to IPsec, DTLS shall be supported as specified in RFC 6083 [58] to provide mutual authentication, integrity protection, replay protection and confidentiality protection. Security profiles for DTLS implementation and usage shall follow the TLS profile given in clause 6.2 of TS 33.210[ Network Domain Security (NDS); IP network layer security ] [3] and the certificate profile given in clause 6.1.3a of TS 33.310[ Network Domain Security (NDS); Authentication Framework (AF) ] [5]. The identities in the end entity certificates shall be used for authentication and policy checks. Mutual authentication shall be supported over the E1interface between the gNB-CU-CP and the gNB-CU-UP using DTLS and/or IKEv2. IPsec is mandatory to support on the gNB-CU-UP and the gNB-CU-CP. Observe that on both the gNB-CU-CP and the gNB-CU-UP sides, a SEG may be used to terminate the IPsec tunnel. NOTE 1: The use of transport layer security, via DTLS, does not rule out the use of network layer protection according to NDS/IP as specified in TS 33.210[ Network Domain Security (NDS); IP network layer security ] [3]. In fact, IPsec has the advantage of providing topology hiding. NOTE 2: The use of cryptographic solutions to protect E1 is an operator's decision. In case the gNB has been placed in a physically secured environment then the 'secure environment' includes other nodes and links beside the gNB. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 9.8.3 |
5,474 | 10.5.4.19 More data | The more data information element is sent by the mobile station to the network or to the network to the mobile station in a USER INFORMATION message. The presence of the more data information element indicates to the destination remote user/mobile station that another USER INFORMATION message will follow containing information belonging to the same block. The use of the more data information element is not supervised by the network. The more data information element is coded as shown in figure 10.5.105/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The more data is a type 2 information element. Figure 10.5.105/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] More data information element | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.4.19 |
5,475 | 4.5.2.3 Abnormal cases | RR connection failure: If the RR connection failure occurs during a RR or MM common procedure, the consequent actions are described together with that procedure. In other cases, the following applies: - Mobile station: The MM sublayer shall indicate to all CM entities associated with active MM connections that the MM connection is interrupted, the subsequent action of the MM sublayer (call re-establishment, see 4.5.1.6, or local release) will then depend on the decisions by the CM entities. - Network: The MM sublayer shall locally release all active MM connections. As an option the network may delay the release of all or some of the MM connections to allow the mobile station to initiate call re-establishment. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.5.2.3 |
5,476 | 4.3 UE mode of operation 4.3.1 General | A UE attached for EPS services shall operate in one of the following operation modes: - PS mode 1 of operation: the UE registers only to EPS services, and UE's usage setting is "voice centric"; - PS mode 2 of operation: the UE registers only to EPS services, and UE's usage setting is "data centric"; - CS/PS mode 1 of operation: the UE registers to both EPS and non-EPS services, and UE's usage setting is "voice centric"; and - CS/PS mode 2 of operation: the UE registers to both EPS and non-EPS services, and UE's usage setting is "data centric". A UE configured to use CS fallback, shall operate in CS/PS mode 1 or CS/PS mode 2. Such UE may also be configured to use IMS, in which case the voice domain preference for E-UTRAN as defined in 3GPP TS 24.167[ 3GPP IMS Management Object (MO); Stage 3 ] [13B] shall be used for the selection of the domain for originating voice communication services. NOTE 1: The domain selected for originating voice communication services can be ignored by attempting a CS emergency call. Upon request from upper layers to establish a CS emergency call: - if the UE needs to initiate a CS fallback emergency call but it is unable to perform CS fallback, the UE shall attempt to select GERAN or UTRAN radio access technology, and a UE with "IMS voice not available" should disable the E-UTRA capability (see clause 4.5) to allow a potential callback, and then progress the CS emergency call establishment; - if the UE needs to initiate a 1xCS fallback emergency call but it is unable to perform 1xCS fallback, the UE shall attempt to select cdma2000® 1x radio access technology to establish the call. NOTE 2: Unable to perform CS fallback or 1xCS fallback means that either the UE was not allowed to attempt CS fallback or 1xCS fallback, or CS fallback or 1xCS fallback attempt failed. A UE configured to use SMS over SGs shall operate in CS/PS mode 1 or CS/PS mode 2. The behaviour of the UE in CS/PS mode 1 of operation, upon failure to access the CS domain or upon reception of a "CS fallback not preferred" or "SMS only" indication, will depend on the availability of voice over IMS. In the present document, "IMS voice not available" refers to one of the following conditions: a) the UE is not configured to use IMS; b) the UE is not configured to use IMS voice, i.e. when the voice domain preference for E-UTRAN, as defined in 3GPP TS 24.167[ 3GPP IMS Management Object (MO); Stage 3 ] [13B], indicates that voice communication services are allowed to be invoked only over the CS domain; c) the UE is configured to use IMS voice, but the network indicates in the ATTACH ACCEPT message or the TRACKING AREA UPDATE ACCEPT message that IMS voice over PS sessions are not supported; or d) the UE is configured to use IMS voice, the network indicates in the ATTACH ACCEPT message or the TRACKING AREA UPDATE ACCEPT message that IMS voice over PS sessions are supported, but the upper layers: - provide no indication that the UE is available for voice call in the IMS within a manufacturer determined period of time; or - indicate that the UE is not available for voice calls in the IMS. NOTE 3: If conditions a, b and c evaluate to false, the upper layers need time to attempt IMS registration. In the event an indication from the upper layers that the UE is available for voice calls in the IMS takes longer than the manufacturer determined period of time (e.g. due to delay when attempting IMS registration or due to delay obtaining an EPS bearer context for SIP signalling), the NAS layer assumes the UE is not available for voice calls in the IMS. Other conditions may exist but these are implementation specific. In the present document, "IMS voice available" refers to the conditions a, b, c and d, and other implementation specific conditions for "IMS voice not available" evaluate to false. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.3 |
5,477 | 4.2.1.8 Maximum E-RAB Setup time | This measurement provides the maximum time per QCI it takes to establish an E-RAB. GAUGE This measurement is obtained by monitoring the time intervals for every successfully established E-RAB between the receipt of an E-RAB SETUP REQUEST or INITIAL CONTEXT SETUP REQUEST message and the transmission of the corresponding E-RAB SETUP RESPONSE or INITIAL CONTEXT SETUP RESPONSE message by the eNodeB over the granularity period. The high tide mark of this time will be stored in a gauge, the gauge shall be reinitialised at the beginning of each granularity period.. The measurement is split into subcounters per QCI, and the possible QCIs are included in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [9]. Each measurement is an integer value (in milliseconds). The measurement name has the form ERAB.EstabTimeMax.QCI where QCI identifies the E-RAB level quality of service class. EUtranCellFDD EUtranCellTDD Valid for packet switching. EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.2.1.8 |
5,478 | 5.5.4.5 Event A4 (Neighbour becomes better than threshold) | The UE shall: 1> consider the entering condition for this event to be satisfied when condition A4-1, as specified below, is fulfilled; 1> consider the leaving condition for this event to be satisfied when condition A4-2, as specified below, is fulfilled. Inequality A4-1 (Entering condition) Mn + Ofn + Ocn – Hys > Thresh Inequality A4-2 (Leaving condition) Mn + Ofn + Ocn + Hys < Thresh The variables in the formula are defined as follows: Mn is the measurement result of the neighbouring cell or the measurement result of serving PSCell (i.e., in case it is configured as candidate PSCell for CondEvent A4 evaluation) for CHO with candidate SCG(s) case, not taking into account any offsets. Ofn is the measurement object specific offset of the neighbour cell (i.e. offsetMO as defined within measObjectNR corresponding to the neighbour cell). Ocn is the measurement object specific offset of the neighbour cell (i.e. cellIndividualOffset as defined within measObjectNR corresponding to the neighbour cell, or cellIndividualOffset as defined within reportConfigNR), and set to zero if not configured for the neighbour cell. Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigNR for this event). Thresh is the threshold parameter for this event (i.e. a4-Threshold as defined within reportConfigNR for this event). Mn is expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR. Ofn, Ocn, Hys are expressed in dB. Thresh is expressed in the same unit as Mn. NOTE: The definition of Event A4 also applies to CondEvent A4. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.5.4.5 |
5,479 | 10.2.6A Narrowband positioning reference signal (NPRS) | Narrowband positioning reference signals (NPRSs) shall only be transmitted in resource blocks in NB-IoT carriers configured for NPRS transmission. In a subframe configured for NPRS transmission, the starting positions of the OFDM symbols configured for NPRS transmission shall be identical to those in a subframe in which all OFDM symbols have the same cyclic prefix length as the OFDM symbols configured for NPRS transmission. NPRS are defined for and normal CP only. NPRSs are transmitted on antenna port 2006. | 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.6A |
5,480 | 6.1.3.1.2 Successful PDP context activation requested by the network | In order to request a PDP context activation, the network sends a REQUEST PDP CONTEXT ACTIVATION message to the MS and starts timer T3385. The message contains an offered PDP address. If available, the APN shall be included in the REQUEST PDP CONTEXT ACTIVATION message. Upon receipt of a REQUEST PDP CONTEXT ACTIVATION message if an APN is indicated in the message and the timer T3396 is running for the APN, the MS shall stop the timer T3396, and then either initiate the PDP context activation procedure as described in the previous subclause or reject the activation request by sending a REQUEST PDP CONTEXT ACTIVATION REJECT message as described in subclause 6.1.3.1.4. If the REQUEST PDP CONTEXT ACTIVATION message did not contain an APN, then the MS shall stop the timer T3396 associated with no APN. The value of the reject cause IE of the REQUEST PDP CONTEXT ACTIVATION REJECT message shall indicate the reason for rejection, e.g. "insufficient resources to activate another context". The ACTIVATE PDP CONTEXT REQUEST message sent by the MS in order to initiate the PDP context activation procedure shall contain the PDP address, PDP Type and APN requested by the network in the REQUEST PDP CONTEXT ACTIVATION message. Upon receipt of the ACTIVATE PDP CONTEXT REQUEST message, the network shall stop timer T3385. The same procedures then apply as described for MS initiated PDP context activation. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.1.3.1.2 |
5,481 | 6.4.1.3 Default EPS bearer context activation accepted by the UE | Upon receipt of the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message, if the UE provided an APN for the establishment of the PDN connection, the UE shall stop timer T3396 if it is running for the APN provided by the UE. If the UE did not provide an APN for the establishment of the PDN connection and the request type was different from "emergency" and from "handover of emergency bearer services", the UE shall stop the timer T3396 associated with no APN if it is running. If the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message was received in response to a request for an emergency PDN connection, the UE shall not stop the timer T3396 associated with no APN if it is running. For any case, the UE shall then send an ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message and enter the state BEARER CONTEXT ACTIVE. When the default bearer is activated as part of the attach procedure, the UE shall send the ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message together with ATTACH COMPLETE message. When the default bearer is activated as the response to the stand-alone PDN CONNECTIVITY REQUEST message, the UE shall send the ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message alone. If a WLAN offload indication information element is included in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message, the UE shall store the WLAN offload acceptability values for this PDN connection and use the E-UTRAN offload acceptability value to determine whether this PDN connection is offloadable to WLAN or not. The UE checks the PTI in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message to identify the UE requested PDN connectivity procedure to which the default bearer context activation is related (see clause 6.5.1). If the UE receives a serving PLMN rate control IE in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message, the UE shall store the serving PLMN rate control IE value and use the stored serving PLMN rate control value as the maximum allowed limit of uplink User data container IEs included in ESM DATA TRANSPORT messages for the corresponding PDN connection in accordance with 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10]. If the UE receives an APN rate control parameters container in the Protocol configuration options IE or Extended protocol configuration options IE in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message, the UE shall store the APN rate control parameters value and use the stored APN rate control parameters value as the maximum allowed limit of uplink user data related to the APN indicated in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message in accordance with 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10]. If the UE has a previously stored APN rate control parameters value for this APN, the UE shall replace the stored APN rate control parameters value for this APN with the received APN rate control parameters value. If the UE receives an additional APN rate control parameters for exception data container in the Protocol configuration options IE or Extended protocol configuration options IE in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message, the UE shall store the additional APN rate control parameters for exception data value and use the stored additional APN rate control parameters for exception data value as the maximum allowed limit of uplink exception data related to the APN indicated in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message in accordance with 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10]. If the UE has a previously stored additional APN rate control parameters for exception data value for this APN, the UE shall replace the stored additional APN rate control parameters for exception data value for this APN with the received additional APN rate control parameters for exception data value. If the UE receives a small data rate control parameters container in the Protocol configuration options IE or the Extended protocol configuration options IE in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message, the UE shall store the small data rate control parameters value and use the stored small data rate control parameters value as the maximum allowed limit of uplink user data for the corresponding PDU session that becomes transferred after inter-system change from S1 mode to N1 mode in accordance with 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [58]. If the UE receives an additional small data rate control parameters for exception data container in the Protocol configuration options IE or the Extended protocol configuration options IE in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message, the UE shall store the additional small data rate control parameters for exception data value and use the stored additional small data rate control parameters for exception data value as the maximum allowed limit of uplink exception data for the corresponding PDU session that becomes transferred after inter-system change from S1 mode to N1 mode in accordance with 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [58]. If the UE receives non-IP Link MTU parameter, Ethernet Frame Payload MTU parameter, IPv4 Link MTU parameter, or Unstructured Link MTU parameter of the Protocol configuration options IE or of the Extended protocol configuration options IE in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message, the UE shall pass the received Non-IP Link MTU size, Ethernet Frame Payload MTU size, or IPv4 Link MTU size, or Unstructured Link MTU size to the upper layer. NOTE 1: The Non-IP Link MTU and the IPv4 Link MTU size correspond to the maximum length of user data that can be sent either in the user data container in the ESM DATA TRANSPORT message or via S1-U interface. NOTE 2: The Ethernet frame payload MTU size corresponds to the maximum length of a payload of an Ethernet frame that can be sent either in the user data container in the ESM DATA TRANSPORT message or via S1-U interface. NOTE 3: A PDN connection of non-IP PDN type can be transferred to a PDU session of "Unstructured" PDU session type, thus the UE can request the unstructured link MTU parameter in the default EPS bearer context activation procedure. The unstructured link MTU size correspond to the maximum length of user data packet that can be sent either via the control plane or via N3 interface for a PDU session of the "Unstructured" PDU session type as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54]. If the UE receives the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message containing the Uplink data not allowed parameter in the Extended protocol configuration options IE, then the UE shall not send any uplink user data over EPS bearer context(s) of the corresponding PDN connection. Upon receiving the DNS server security information, the UE shall pass it to the upper layer. The UE shall use this information to send the DNS over (D)TLS (See 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]). NOTE 4: Support of DNS over (D)TLS is based on the informative requirements as specified in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. If the UE supports provisioning of ECS configuration information to the EEC in the UE, then upon receiving: - at least one of ECS IPv4 address(es), ECS IPv6 address(es), ECS FQDN(s); - at least one associated ECSP identifier; and - optionally spatial validity conditions associated with the ECS address in the Extended protocol configuration options IE of the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message, the UE shall pass them to the upper layers. NOTE 5: The IP address(es) and/or FQDN(s) are associated with the ECSP identifier and replace previously provided ECS configuration information associated with the same ECSP identifier, if any. Upon receipt of the ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message, the MME shall enter the state BEARER CONTEXT ACTIVE and stop the timer T3485, if the timer is running. If the PDN CONNECTIVITY REQUEST message included a low priority indicator set to "MS is configured for NAS signalling low priority", the MME shall store the NAS signalling low priority indication within the default EPS bearer context. If the UE indicated the URSP provisioning in EPS support indicator as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] in the UE requested PDN connectivity procedure establishing the PDN connection, and the Extended protocol configuration options IE of the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message contains the URSP provisioning in EPS support indicator, then the UE shall perform the UE requested bearer resource modification procedure to provide a UE policy container with the length of two octets containing the UE STATE INDICATION message (see 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] annex D), otherwise the UE shall not perform the UE requested bearer resource modification procedure to provide a UE policy container with the length of two octets containing the UE STATE INDICATION message (see 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] annex D). | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.4.1.3 |
5,482 | 5.2.3.2.3 ATTEMPTING-REGISTRATION-UPDATE | The UE in 3GPP access: a) shall not send any user data; b) shall initiate a registration procedure for mobility and periodic registration update on the expiry of timers T3502, T3511, T3346 or discontinuous coverage maximum time offset timer; c) shall initiate a registration procedure for mobility and periodic registration update when entering a new PLMN or SNPN, if timer T3346 is running and the new PLMN or SNPN is not equivalent to the PLMN or SNPN where the UE started timer T3346, the PLMN identity of the new cell is not in the forbidden PLMN lists, and the current TAI is not in one of the lists of 5GS forbidden tracking areas; d) shall initiate a registration procedure for mobility and periodic registration update when the current TAI has changed, if timer T3346 is not running: i) the PLMN identity of the new cell is not in one of the forbidden PLMN lists; ii) if the SNPN is not an SNPN selected for localized services in SNPN (see 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]), the SNPN identity of the new cell is in neither the "permanently forbidden SNPNs" list nor the "temporarily forbidden SNPNs" list which are, 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 or iii) if the SNPN is an SNPN selected for localized services in SNPN (see 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]), the SNPN identity of the new cell is in neither the "permanently forbidden SNPNs for access for localized services in SNPN" list nor the "temporarily forbidden SNPNs for access for localized services in SNPN" list, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription; and the current TAI is not in one of the lists of 5GS forbidden tracking areas; e) may initiate a registration procedure for mobility and periodic registration update upon request of the upper layers to establish an emergency PDU session or perform emergency service fallback; e1) may initiate a registration procedure for mobility and periodic registration update upon request of the upper layers to establish a PDU session, even if timer T3502, T3346 or T3447 is running, if the UE is a UE configured for high priority access in the selected PLMN; e2) may initiate a registration procedure for mobility and periodic registration update upon request of the upper layers to establish a PDU session, even if timer T3502, T3346 is running, if the UE is a UE configured for high priority access in selected SNPN; f) may perform de-registration locally and initiate a registration procedure for initial registration for emergency services even if timer T3346 is running; g) shall initiate registration procedure for mobility and periodic registration update upon reception of paging, or upon reception of NOTIFICATION message with access type indicating 3GPP access; NOTE: As an implementation option, the MUSIM UE is allowed to not respond to paging based on the information available in the paging message, e.g. voice service indication. h) may initiate a registration procedure for mobility and periodic registration update upon request for an MMTEL voice call, MMTEL video call, or an MO IMS registration related signalling from the upper layers, and none of the following conditions is met: 1) timer T3346 is running; 2) the UE has stored a list of "non-allowed tracking areas" and the current TAI is in the list of "non-allowed tracking areas"; or 3) the UE has stored a list of "allowed tracking areas", the UE is camped on a cell which is in the registered PLMN, a PLMN from the list of equivalent PLMNs, or the registered SNPN, and the current TAI is not in the list of "allowed tracking areas"; i) shall initiate a registration procedure for mobility and periodic registration update if the 5GS update status is set to 5U2 NOT UPDATED, and timers T3511, T3502 and T3346 are not running; j) if configured for eCall only mode as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [22], shall perform the eCall inactivity procedure at expiry of timer T3444 or timer T3445 (see subclause 5.5.3); k) may initiate a registration procedure for mobility and periodic registration update for UE in NB-N1 mode upon receiving a request from upper layers to transmit user data related to an exceptional event and the UE is allowed to use exception data reporting (see the ExceptionDataReportingAllowed leaf of the NAS configuration MO in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [17]) or the USIM file EFNASCONFIG in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [22]) if timer T3346 is not already running for "MO exception data" and even if timer T3502 or timer T3511 is running; l) shall not initiate the de-registration signalling procedure unless the current TAI is part of the TAI list ; and m) shall initiate a registration procedure for mobility and periodic registration update if the UE supports the reconnection to the network due to RAN timing synchronization status change and receives an indication of a change in the RAN timing synchronization status, even if timer T3502 is running. The UE in non-3GPP access: a) shall not send any user data; b) shall initiate the registration procedure for mobility and periodic registration update on the expiry of timers T3502, T3511 or T3346; c) may initiate a registration procedure for mobility registration update upon request of the upper layers to establish an emergency PDU session; c1) may initiate a registration procedure for mobility and periodic registration update upon request of the upper layers to establish a PDU session, if the UE is a UE configured for high priority access in selected PLMN even if timer T3346 or T3502 is running; d) may perform de-registration locally and initiate a registration procedure for initial registration for emergency services even if timer T3346 is running; e) may initiate a registration procedure for mobility and periodic registration update upon request for an MMTEL voice call, MMTEL video call, or an MO IMS registration related signalling from the upper layers, if timer T3346 is not running; f) shall initiate a registration procedure for mobility and periodic registration update if the 5GS update status is set to 5U2 NOT UPDATED, and timers T3511, T3502 and T3346 are not running; and g) shall not initiate the de-registration signalling procedure unless timer T3346 is running. | 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.2.3.2.3 |
5,483 | 4.7.9.2 Paging for non-GPRS services | The network may initiate the paging procedure for non-GPRS services when the MS is IMSI attached for non-GPRS services. In Iu mode, to initiate the procedure the GMM entity requests the lower layer to start paging (see 3GPP TS 25.331[ None ] [23c] and 3GPP TS 25.413[ UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling ] [19c]) for non-GPRS services. In A/Gb mode, to initiate the procedure the GMM entity requests the RR sublayer to start paging (see 3GPP TS 44.018[ None ] [84] and 3GPP TS 44.060[ None ] [76] for non-GPRS services). The MS identity used for paging shall be the allocated TMSI if acknowledged by the MS, otherwise the IMSI. | 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.9.2 |
5,484 | 6.8.10.1 SRVCC from HSPA to circuit switched UTRAN/GERAN | HSPA SRVCC to UTRAN/GERAN is described in TS 23.216[ Single Radio Voice Call Continuity (SRVCC); Stage 2 ] [37]. Case 1: UMTS subscribers: Case 1.1: HO to UTRAN When the SRNC decides to start a SRVCC from HSPA to UTRAN, it shall initiate the SRVCC Preparation procedure described in TS 25.413[ UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling ] [31]. The source SGSN shall generate a NONCE and derive CK'CS||IK'CS from the NONCE and the CKPS||IKPS generated during the latest UMTS AKA procedure. In case the current UMTS security context is mapped from an EPS security context and there has been no UMTS AKA run since the current UMTS security context was mapped, the CKPS, IKPS and GPRS Kc belonging to the mapped UMTS security context shall be considered to be the keys from the latest UMTS AKA. The source SGSN shall transfer CK’CS, IK’CS, KSI’CS (=KSIPS) and the NONCE to the SRNC and transfer CK’CS, IK’CS and KSI’CS (=KSIPS) to the MSC server enhanced for SRVCC. The SRNC shall transfer the NONCE to the target RNC. The target RNC shall include the NONCE in the handover command to be sent to the UE. The SRNC shall also transfer the security context, including CK’CS, IK’CS, KSI’CS and START CS (which is received by the SRNC during RRC connection establishment), to the target RNC. Upon reception of the handover command, the ME shall derive CK'CS||IK'CS from CKPS||IKPS and the NONCE, and set KSI’CS to KSIPS. The ME shall convert GSM ciphering key Kc’ from CK’CS||IK’CS, and set GSM CKSN’ CS equal to KSI’CS. For the definition of the Key Derivation Function and its inputs see Annex B.3. NOTE 1: Due to replacing all the UTRAN CS key parameters CK, IK, KSI with CK'CS, IK'CS and KSI’CS on USIM and in ME, a new GSM ciphering key Kc’ needs to be derived from the new UTRAN CS key parameters CK and IK (i.e. CK’CS and IK’CS), which is part of the new UMTS security context as well, as any old GSM ciphering key Kc stored on USIM and in ME, belongs to an old UMTS security context and can no longer be taken into use. Case 1.2: HO to GERAN When the SRVCC is from HSPA to GERAN, the source SGSN shall generate a NONCE and derive CK’CS, and IK’CS from the NONCE and the CKPS||IKPS generated during the latest UMTS AKA procedure. In case the current UMTS security context is mapped from an EPS security context and there has been no UMTS AKA run since the current UMTS security context was mapped, the CKPS, IKPS and GPRS Kc belonging to the mapped UMTS security context shall be considered to be the keys from the latest UMTS AKA. The source SGSN shall append the NONCE to the GSM HO command, received from the target BSS, when forwarding the command to the SRNC. The SRNC shall forward the NONCE together with the GSM HO command to the UE. The source SGSN shall transfer the security context, including CK’CS, IK’CS and KSI’CS (=KSIPS) to the MSC server enhanced for SRVCC. The MSC server enhanced for SRVCC and the ME shall convert CK’CS||IK’CS to GSM ciphering key Kc’, and set GSM CKSN’ CS to KSI’CS. Upon reception of the handover command, the ME shall derive CK’CS, and IK’CS from CKPS||IKPS and the NONCE, convert GSM ciphering key Kc’ from CK’CS||IK’CS, and set GSM CKSN’ CS to KSI’CS. For the definition of the Key Derivation Function and its inputs see Annex B.3. NOTE 2: See note 1. If a 128-bit GSM ciphering algorithm is taken into use, the target MSC server enhanced for SRVCC and UE shall derive the GSM ciphering key Kc128 key derived from CK'CS||IK'CS as described in annex B.5. For both cases 1.1 and 1.2: The MSC server enhanced for SRVCC shall overwrite the stored parameters CKCS, IKCS and KSICS if any, with the parameters CK’CS, IK’CS and KSI’CS received from the source SGSN when the SRVCC handover has been completed successfully. The ME shall overwrite the stored parameters CKCS, IKCS , KSICS , GSM ciphering key Kc and GSM CKSN CS if any, with the derived parameters CK’CS, IK’CS, KSI’CS, GSM ciphering key Kc’ and GSM CKSN’ CS in both ME and USIM when the SRVCC handover has been completed successfully. If the SRVCC handover isn’t completed successfully, the MSC server enhanced for SRVCC and the UE shall discard CK’CS, IK’CS and KSI’CS. NOTE 1: The new derived security context overwriting the stored values in the USIM is for allowing reusing the derived security context without invoking the authentication procedure in the subsequent connection set-ups, and also for avoiding that one KSI value indicates to two different key sets and consequently leads to security context desynchronization. NOTE 2: An operator concerned about the security of keys received from an UTRAN of another operator may want to enforce a policy in the MSC server to run an AKA as soon as possible after the handover. One example of ensuring this is the deletion of the derived security context in the MSC server after the UE has left active state. The MSC server enhanced for SRVCC shall delete the stored parameters CKCS and IKCS if the SRVCC handover is not completed successfully. Case 2: GSM subscribers Case 2.1: HO to UTRAN When the SRNC decides to start a SRVCC from HSPA to UTRAN, it shall initiate the SRVCC Preparation procedure (see TS 25.413[ UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling ] ). The source SGSN shall generate a NONCE and derive GSM ciphering key Kc’ from the NONCE and the GPRS Kc generated in the latest successful GSM AKA. The source SGSN shall set GSM CKSN’CS and KSI’CS to GPRS CKSNPS. . The source SGSN shall compute CK’CS, IK’CS from GSM ciphering key Kc’, using the conversion functions c4 and c5, and transfer CK’CS, IK’CS and KSI’CS to the SRNC. The SRNC shall transfer the NONCE to the target RNC. The target RNC shall include the NONCE in the handover command to be sent to the UE. The SRNC shall transfer the security context, including CK’CS, IK’CS, KSI’CS and START CS (which is received by the SRNC during RRC connection establishment), to the target RNC. The source SGSN shall also transfer GSM ciphering key Kc’ and GSM CKSN’ CS to the MSC server enhanced for SRVCC. Upon reception of the handover command, the UE shall derive GSM ciphering key Kc’ from the GPRS Kc generated in the latest successful GSM AKA and the NONCE. The UE shall set GSM CKSN’CS and KSI’CS to GPRS CKSNPS. The UE shall compute CK’CS, IK’CS from GSM ciphering key Kc’, using the conversion functions c4 and c5. For the definition of the Key Derivation Functions see Annex B.4. Case 2.2: HO to GERAN When the SRVCC is from HSPA to GERAN, the source SGSN shall generate a NONCE and derive GSM ciphering key Kc’ from the NONCE and the 64-bit GPRS Kc generated in the latest successful GSM AKA. The source SGSN shall append the NONCE to the GSM HO command, received from the target BSS, when forwarding the command to the SRNC. The SRNC shall forward the NONCE together with the GSM HO command to the UE. The source SGSN shall set GSM CKSN’CS to GPRS CKSNPS and transfer GSM ciphering key Kc’ and GSM CKSN’CS to the MSC server enhanced for SRVCC. Upon reception of the handover command, the UE shall derive GSM ciphering key Kc’ from the GPRS Kc generated in the latest successful GSM AKA and the NONCE, and set GSM CKSN’CS to GPRS CKSNPS. For the definition of the Key Derivation Functions see Annex B.4. For both cases 2.1 and 2.2: The MSC server enhanced for SRVCC shall overwrite the stored parameters 64-bit GSM ciphering key Kc and GSM CKSNCS, if any, with the parameters GSM ciphering key Kc’ and GSM CKSN’CS received from the source SGSN when the SRVCC handover has been completed successfully. The UE shall overwrite the stored parameters 64-bit GSM ciphering key Kc and GSM CKSNCS, if any, with the derived parameters GSM ciphering key Kc’ and GSM CKSN’CS in both ME and SIM when the SRVCC handover has been completed successfully. If the SRVCC handover isn’t completed successfully, the MSC server enhanced for SRVCC and the UE shall discard GSM ciphering key Kc’ and GSM CKSN’CS. NOTE 3: The new derived security context overwriting the stored values in the SIM is for allowing reusing the derived security context without invoking the authentication procedure in the subsequent connection set-ups, and also for avoiding that one CKSN value indicates to two different key sets and consequently leads to security context desynchronization. If the SRVCC is for an emergency call and the session in HSPA complies with clause 6.4.9.1, the security procedure in this subclause shall be applied. If the SRVCC is for an emergency call and the session in HSPA complies with clause 6.4.9.2, the security procedure in this subclause shall not be applied, i.e., no key derivation is needed. The MSC server enhanced for SRVCC shall delete the stored parameters CKCS and IKCS if the SRVCC handover isn’t completed successfully, so for any subsequent CS connection a new CS key-set is generated. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 6.8.10.1 |
5,485 | 5.13 Discontinuous Reception and UE Specific DRX Parameter handling | During the Attach and Tracking/Routing Area Update procedures in E-UTRAN, UTRAN and/or GERAN, the UE can signal its UE Specific DRX Parameters to the Core Network (MME in the E-UTRAN case and SGSN in UTRAN/GERAN case). In E-UTRAN and UTRAN, the UE may signal that it wishes to use the DRX cycle length broadcast in the RAN's System Information. Alternatively, the UE can propose a DRX cycle length separately for WB-EUTRA and NB-IoT. For NB-IoT, the cell broadcasts an indication of support of UE specific DRX for NB-IoT in that cell, and the UE can request UE specific DRX for NB-IoT during Attach and Tracking Area Update procedures irrespective of whether the cell broadcasts that support indication. The MME shall accept the value proposed by the UE for WB-E-UTRAN. For NB-IoT the MME should accept the UE requested value, but subject to operator policy the MME may change the UE requested values. The MME shall respond to the UE with the Accepted DRX parameter for NB-IoT. In each S1 interface Page Request message, the MME shall send the UE Specific DRX Parameters for the UE's current RAT (to help determine the DRX cycle length) and information derived from the IMSI (which defines when the UE will be awake from its sleep mode). Details are specified in TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [34]. NOTE 1: To ease backward compatibility with Pre-Release 8 SGSNs, the UTRAN and E-UTRAN DRX cycle lengths are encoded in the same field within the TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [47] DRX parameter information element. At MME to MME, MME to SGSN and SGSN to MME mobility, the UE Specific DRX Parameters for RATs other than NB-IoT are sent from the old CN node to the new CN node as part of the MM context information and (except for NB-IoT) should not be sent by the UE in the Tracking Area Update message. NOTE 2: it is assumed that all SGSNs are Release 99 or newer and hence support storage of the Release '99 encoding of the TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [47] DRX parameter information element. During Attach and non-periodic Tracking Area Update procedures on NB-IoT cells, the UE shall ensure that it has provided the MME with any UE Specific DRX parameter that applies to NB-IoT and optionally UE specific DRX parameter that applies for WB-E-UTRAN. If a CN node receives UE Specific DRX Parameters in a dedicated message from the UE (e.g. in a Tracking Area Update or Attach message), then the CN node updates any stored information with the information supplied by the UE and uses the UE provided information in preference to any information that might be received from another CN node during the same procedure. If the UE wishes to alter its GERAN or UTRAN/WB-E-UTRAN/NB-IoT UE Specific DRX Parameters while in E-UTRAN, then it shall send a Tracking Area Update Request message to the MME containing its new UE Specific DRX Parameters. If ISR had been activated for the UE, then the UE shall deactivate ISR by setting its TIN to "GUTI" so that the UE performs a Routing Area Update when it next enters GERAN/UTRAN coverage. When the UE performs that Routing Area Update, the SGSN will receive the updated DRX parameters within the MM context information sent by the MME and hence the UE should not include them again in the Routing Area Update Request message. If the UE wishes to alter its WB-E-UTRAN/UTRAN or GERAN DRX Parameters while in GERAN or UTRAN coverage, then the UE shall send a Routing Area Update Request message to the SGSN containing its new UE DRX Parameters. If ISR has been activated, the UE shall deactivate ISR by setting its TIN to "P-TMSI" so that the UE performs a Tracking Area Update when it next returns to E-UTRAN coverage. When the UE performs that Tracking Area Update, the MME will receive the updated DRX parameters (excluding the one for NB-IoT) within the MM context information sent by the SGSN and hence the UE should not include them again in the Tracking Area Update message. For NB-IoT, the UE shall apply the DRX cycle broadcast in the cell by the RAN unless it has received Accepted DRX parameters for NB-IoT from the MME and the cell supports UE specific DRX for NB-IoT, in which case the UE shall apply either the DRX cycle broadcast in the cell or the Accepted DRX parameters for NB-IoT, as defined in TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [34]. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.13 |
5,486 | 6.1.5 Coordination between ESM and EMM for supporting ISR | The UE with its TIN set as "RAT-related TMSI" for which ISR is activated shall change its TIN to "GUTI" to locally deactivate ISR and stop the periodic routing area update timer T3312 or T3323, if running: - upon modification of any EPS bearer context which was activated before the ISR is activated in the UE; - at the time when the UE changes from S1 mode to A/Gb mode or Iu mode not due to PS handover procedure (see 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13]), if any EPS bearer context activated after the ISR was activated in the UE exists; or - upon deactivation of the last non-emergency EPS bearer context in the UE, if the UE has only a PDN connection for emergency bearer services remaining. ISR remains activated on the network side in the above cases. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.1.5 |
5,487 | B.3.2 Network-to-MS compatibility checking | When the network is providing a basic service at the called side, the MS shall check that the basic service(s) offered by the network in the Bearer Capability information element(s) match(es) the basic services that the MS is able to support. If a mismatch is detected, then the MS shall proceed as follows: - if the SETUP message contained two bearer capability information elements for only one of which a mismatch is detected, the MS shall either: - under the conditions specified in 3GPP TS 27.001[ General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS) ] [36] (e.g. TS 61 and TS 62), accept the SETUP message with a CALL CONFIRMED message containing the, possibly negotiated, bearer capability information element for which no mismatch is detected, or - reject the call using cause No. 88 "incompatible destination". - otherwise the MS shall reject the offered call using a RELEASE COMPLETE message with cause No. 88 "incompatible destination". NOTE: The backup bearer capability IE is not subject to compatibility checking. When interworking with existing networks, limitations in network or distant user signalling (e.g. in the case of an incoming call from a PSTN or a call from an analogue terminal) may restrict the information available to the called MS in the incoming SETUP message (e.g. missing Bearer Capability Information Element or missing High Layer Compatibility Information Element). For compatibility checking, and handling of such calls see 3GPP TS 27.001[ General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS) ] [36]. | 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 | B.3.2 |
5,488 | 5.4.1 PUCCH formats 1, 1a and 1b | For PUCCH format 1, information is carried by the presence/absence of transmission of PUCCH from the UE. In the remainder of this clause, shall be assumed for PUCCH format 1. For PUCCH formats 1a and 1b, one or two explicit bits are transmitted, respectively. The block of bits shall be modulated as described in Table 5.4.1-1, resulting in a complex-valued symbol. The modulation schemes for the different PUCCH formats are given by Table 5.4-1. The complex-valued symbol shall be multiplied with a cyclically shifted length sequence for each of the antenna ports used for PUCCH transmission according to where is defined by clause 5.5.1 with and . The antenna-port specific cyclic shift varies between symbols and slots as defined below. The block of complex-valued symbols shall be scrambled by and block-wise spread with the antenna-port specific orthogonal sequence according to where and with for the two slots in a subframe given by Table 5.4.1-1a. The sequence is given by Table 5.4.1-2 and Table 5.4.1-3 and is defined below. Resources used for transmission of PUCCH format 1, 1a and 1b are identified by a resource index from which the orthogonal sequence index and the cyclic shift are determined according to where The resource indices within the two resource blocks in the two slots of a subframe to which the PUCCH is mapped are given by for and by for , where , with for normal CP and for extended CP. The parameter deltaPUCCH-Shift is provided by higher layers. Table 5.4.1-1: Modulation symbol for PUCCH formats 1a and 1b Table 5.4.1-1a: The quantity for PUCCH formats 1a and 1b Table 5.4.1-2: Orthogonal sequences for Table 5.4.1-3: Orthogonal sequences for | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.4.1 |
5,489 | J.4 Downlink data transfer | Figure J.4-1 shows a downlink data transfer to an idle state UE when ISR is activated. The Serving GW receives downlink data. Because of activated ISR, the Serving GW has control connections with both MME and SGSN and sends therefore downlink data notifications to both nodes. MME and SGSN start their paging procedures, which results in paging of the UE in the registered RA and TA(s) in parallel. In the example illustrated in Figure J.4-1 it is assumed that the UE camps on E-UTRAN. So the UE responds to paging as usual with Service Request. This triggers the MME to setup the user plane connection between eNodeB and Serving GW. The downlink data are transferred to the UE. When the UE camps on UTRAN/GERAN it performs the paging response as specified for these access systems without any required update or other signalling before. The downlink data are then transferred via UTRAN/GERAN to the UE. Figure J.4-1: Downlink data transfer with ISR active | 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") | J.4 |
5,490 | 5.27.2.5.2 Proactive RAN feedback for adaptation of Burst Arrival Time and Periodicity | If the NG-RAN receives a Burst Arrival Time and Burst Arrival Time Window in the TSCAI for a QoS Flow, the 5GS will perform the following actions: - The NG-RAN can determine a BAT offset in order to align the expected arrival of the traffic bursts (as indicated in the BAT) with the time when the next transmission over the air interface in each direction (i.e. DL or UL) is expected. The BAT offset shall always be provided by NG-RAN and it shall be within the BAT Window. The BAT offset is calculated with reference to the BAT. - If the BAT offset is provided from NG-RAN to the SMF in the response to the QoS Flow establishment or modification request, the SMF provides the BAT offset to the PCF and the PCF notifies the AF as described in clause 6.1.3.23a of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. - The SMF may adjust the BAT offset received from NG-RAN based on the clock drifting report from UPF as specified in clause 4.4.3.4 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. NOTE: The feedback from RAN implies that the RAN accepts the BAT offset. If the AF requested BAT is acceptable for NG-RAN, the NG-RAN provides a BAT offset of zero. - If the RAN also receives a Periodicity Range along with the Periodicity in the TSCAI for a QoS flow, the 5GS will further perform the following actions: - The RAN may determine an adjusted periodicity in order to align the periodicity of the traffic bursts with the expected time interval between subsequent transmission opportunities over the air interface in each direction (i.e. DL or UL). If the RAN determines an adjusted periodicity, the RAN provides it together with a BAT offset mentioned above. The adjusted periodicity shall be within the Periodicity Range and the BAT offset is based on the adjusted periodicity. - The adjusted periodicity is forwarded to the AF via the SMF and the PCF together with a BAT offset in the same way it is described above. - If interworking with a TSN network deployed in the transport network is supported, the SMF/CUC uses the adjusted periodicity (if provided) and BAT offset accepted by the RAN to adjust the EarliestTransmitOffset and LatestTransmitOffset in the Talker/Listener Group in IEEE Std 801.Q [98] as described in Annex M, clause M.1. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.27.2.5.2 |
5,491 | 4.7.2.2 The EPS bearer with GTP-based S5/S8 | Figure 4.7.2.2-1: Two Unicast EPS bearers (GTP-based S5/S8) An EPS bearer is realized by the following elements: - In the UE, the UL TFT maps a traffic flow aggregate to an EPS bearer in the uplink direction; - In the PDN GW, the DL TFT maps a traffic flow aggregate to an EPS bearer in the downlink direction; - A radio bearer (defined 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]) transports the packets of an EPS bearer between a UE and an eNodeB. If a radio bearer exists, there is a one-to-one mapping between an EPS bearer and this radio bearer; - An S1 bearer transports the packets of an EPS bearer between an eNodeB and a Serving GW; - An E-RAB (E-UTRAN Radio Access Bearer) refers to the concatenation of an S1 bearer and the corresponding radio bearer, as defined 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]. - An S5/S8 bearer transports the packets of an EPS bearer between a Serving GW and a PDN GW; - A UE stores a mapping between an uplink packet filter and a radio bearer to create the mapping between a traffic flow aggregate and a radio bearer in the uplink; - A PDN GW stores a mapping between a downlink packet filter and an S5/S8 bearer to create the mapping between a traffic flow aggregate and an S5/S8 bearer in the downlink; - An eNodeB stores a one-to-one mapping between a radio bearer and an S1 Bearer to create the mapping between a radio bearer and an S1 bearer in both the uplink and downlink; - A Serving GW stores a one-to-one mapping between an S1 Bearer and an S5/S8 bearer to create the mapping between an S1 bearer and an S5/S8 bearer in both the uplink and downlink. The PDN GW routes downlink packets to the different EPS bearers based on the downlink packet filters in the TFTs assigned to the EPS bearers in the PDN connection. Upon reception of a downlink data packet, the PDN GW evaluates for a match, first the downlink packet filter that has the lowest evaluation precedence index and, if no match is found, proceeds with the evaluation of downlink packet filters in increasing order of their evaluation precedence index. This procedure shall be executed until a match is found, in which case the downlink data packet is tunnelled to the Serving GW on the EPS bearer that is associated with the TFT of the matching downlink packet filter. If no match is found, the downlink data packet shall be sent via the EPS bearer that does not have any TFT assigned. If all EPS bearers (including the default EPS bearer for that PDN) have been assigned a TFT, the PDN GW shall discard the downlink data packet. | 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.7.2.2 |
5,492 | 8.12.3 Demodulation of NPBCH | The receiver characteristics of the NPBCH are determined by the probability of miss-detection of the NPBCH (Pm-bch), which is defined as For the performance with single a NPBCH TTI decoding, A is the number of correctly decoded MIB-NB PDUs and B is the number of transmitted MIB-NB PDUs. For the performance with multiple NPBCH TTIs decoding, A is the number of 5120ms durations consisting of contiguous NPBCH TTIs where there is at least one correctly decoded MIB-NB PDU, and B is the number of 5120ms durations consisting of contiguous NPBCH TTIs during the test. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.12.3 |
5,493 | 10.5.1.4 Mobile Identity | The purpose of the Mobile Identity information element is to provide either the international mobile subscriber identity, IMSI, the temporary mobile subscriber identity, TMSI/P-TMSI/M-TMSI, the international mobile equipment identity, IMEI, the international mobile equipment identity together with the software version number, IMEISV, or the temporary mobile group identity (TMGI), associated with the optional MBMS Session Identity. The IMSI shall not exceed 15 digits, the TMSI/P-TMSI/M-TMSI is 4 octets long, and the IMEI is composed of 15 digits, the IMEISV is 16 digits (see 3GPP TS 23.003[ Numbering, addressing and identification ] [10]). The TMGI is at maximum 6 octets long and is defined in subclause 10.5.6.13. The MBMS Session Identity, if included, is 1 octet long (see 3GPP TS 48.018[ None ] [86]). For packet paging the network shall select the mobile identity type with the following priority: 1- P-TMSI: The P-TMSI shall be used if it is available. 2- IMSI: The IMSI shall be used in cases where no P-TMSI is available. For MBMS (pre-)notification (see 3GPP TS 44.018[ None ] [84] and 3GPP TS 44.060[ None ] [76]) the network shall select the mobile identity type "TMGI and optional MBMS Session Identity". NOTE 1: The type of identity "TMGI and optional MBMS Session Identity" is only used by the MBMS (pre-)notification procedure in of A/Gb mode. For all other transactions with the following exceptions: - emergency call establishment, emergency call re-establishment, mobile terminated call establishment, the identification procedure, the GMM identification procedure, the GMM authentication, GPRS attach, routing area updating, and ciphering procedure and the ciphering mode setting procedure; and - location updating when the MS is configured for "AttachWithIMSI" as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [135] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [112] and the selected PLMN is neither the registered PLMN nor in the list of equivalent PLMNs; the mobile station and the network shall select the mobile identity type with the following priority: 1- TMSI: The TMSI shall be used if it is available. 2- IMSI: The IMSI shall be used in cases where no TMSI is available. For mobile terminated call establishment the mobile station shall select the same mobile identity type as received from the network in the PAGING REQUEST message. In case of enhanced DTM CS establishment (see 3GPP TS 44.018[ None ] [84]) the mobile station shall select the mobile identity type with the following priority in the PAGING RESPONSE message: 1- TMSI: The TMSI shall be used if it is available. 2- IMSI: The IMSI shall be used in cases where no TMSI is available. For the PAGING RESPONSE message sent as a response to a paging for CS fallback, the MS shall: - select the TMSI as mobile identity type if the network has, in E-UTRAN, - paged the MS for CS fallback using the S-TMSI; or - indicated TMSI in the CS SERVICE NOTIFICATION message (see 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120]); - select the IMSI as mobile identity type if the network has, in E-UTRAN, - paged the MS for CS fallback using the IMSI; or - indicated IMSI in the CS SERVICE NOTIFICATION message (see 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120]). For emergency call establishment and re-establishment the mobile station shall select the mobile identity type with the following priority: 1- TMSI: The TMSI shall be used if it is available and if the location update status is UPDATED, and the stored LAI is equal to the one received on the BCCH from the current serving cell. 2- IMSI: The IMSI shall be used in cases where no TMSI is available or TMSI is available but either the update status is different from UPDATED, or the stored LAI is different from the one received on the BCCH from the current serving cell. 3- IMEI: The IMEI shall be used in cases where no SIM/USIM is available or the SIM/USIM is considered as not valid by the mobile station or no IMSI or TMSI is available. In the identification procedure and in the GMM identification procedure the mobile station shall select the mobile identity type which was requested by the network, if available. If the requested identity is not available, then the mobile station shall indicate the identity type "No Identity". In the ciphering mode setting procedure and in the GMM authentication and ciphering procedure the mobile shall select the IMEISV. The Mobile Identity information element is coded as shown in figure 10.5.4/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.4/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The Mobile Identity is a type 4 information element with a minimum length of 3 octet and 11 octets length maximal. Further restriction on the length may be applied, e.g. number plans. Figure 10.5.4/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Mobile Identity information element Figure 10.5.4a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Mobile Identity information element for type of identity "TMGI and optional MBMS Session Identity" Table 10.5.4/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Mobile Identity 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.4 |
5,494 | – RLC-Parameters | The IE RLC-Parameters is used to convey capabilities related to RLC. RLC-Parameters information element -- ASN1START -- TAG-RLC-PARAMETERS-START RLC-Parameters ::= SEQUENCE { am-WithShortSN ENUMERATED {supported} OPTIONAL, um-WithShortSN ENUMERATED {supported} OPTIONAL, um-WithLongSN ENUMERATED {supported} OPTIONAL, ..., [[ extendedT-PollRetransmit-r16 ENUMERATED {supported} OPTIONAL, extendedT-StatusProhibit-r16 ENUMERATED {supported} OPTIONAL ]], [[ am-WithLongSN-RedCap-r17 ENUMERATED {supported} OPTIONAL ]], [[ am-WithLongSN-NCR-r18 ENUMERATED {supported} OPTIONAL ]] } -- TAG-RLC-PARAMETERS-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,495 | 4.7.3.1.4a GPRS attach for emergency bearer services not accepted by the network (UTRAN Iu mode only) | If the attach request for emergency bearer services cannot be accepted by the network, an ATTACH REJECT message is transferred to the MS. The ATTACH REJECT message includes GMM cause #5 "IMEI not accepted" or one of the GMM cause values as described in subclause 4.7.3.1.4. NOTE 1: If GMM cause #11 is sent to a MS of a roaming subscriber attaching for emergency bearer services and the MS is in automatic network selection mode, it cannot obtain normal service provided by this PLMN. Upon receiving the ATTACH REJECT message including GMM cause #5, the MS shall enter the state GMM-DEREGISTERED.NO-IMSI. Upon receiving the ATTACH REJECT message including one of the other GMM cause values, the MS shall perform the actions as described in subclause 4.7.3.1.4 with the following addition: the MS shall inform the upper layers of the failure of the procedure. NOTE 2: This can result in the upper layers requesting establishment of a CS emergency call (if not already attempted in the CS domain), or 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 ] [13D] can result in the emergency call being attempted to another IP-CAN. If the attach request for emergency bearer services fails due to abnormal case a) in subclause 4.7.3.1.5, the MS shall perform the actions as described in subclause 4.7.3.1.5 and inform the upper layers of the failure to access the network. NOTE 3: This can result in the upper layers requesting establishment of a CS emergency call (if not already attempted in the CS domain), or 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 ] [13D] can result in the emergency call being attempted to another IP-CAN. If the attach request for emergency bearer services fails due to abnormal cases b), c) or d) in subclause .1.5, the MS shall perform the actions as described in subclause 4.7.3.1.5 with the following addition: the MS shall inform the upper layers of the failure of the procedure. NOTE 4: This can result in the upper layers requesting establishment of a CS emergency call (if not already attempted in the CS domain), or 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 ] [13D] can result in the emergency call being attempted to another IP-CAN. In a shared network, upon receiving the ATTACH REJECT message, the MS shall perform the actions as described in subclause 4.7.3.1.4, and shall: a) inform the upper layers of the failure of the procedure; or NOTE 5: This can result in the upper layers requesting establishment of a CS emergency call (if not already attempted in the CS domain), or 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 ] [13D] can result in the emergency call being attempted to another IP-CAN. b) attempt the attach for emergency bearer services to another PLMN in the shared network. In a shared network, if the attach request for emergency bearer services fails due to abnormal case a) in subclause 4.7.3.1.5, the MS shall perform the actions as described in subclause 4.7.3.1.5 and shall: a) inform the upper layers of the failure to access the network; or NOTE 6: This can result in the upper layers requesting establishment of a CS emergency call (if not already attempted in the CS domain), or 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 ] [13D] can result in the emergency call being attempted to another IP-CAN. b) attempt the attach for emergency bearer services to another PLMN in the shared network. In a shared network, if the attach request for emergency bearer services fails due to abnormal cases b), c) or d) in subclause .1.5, the MS shall perform the actions as described in subclause .1.5, and shall: a) inform the upper layers of the failure of the procedure; or NOTE 7: This can result in the upper layers requesting establishment of a CS emergency call (if not already attempted in the CS domain), or 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 ] [13D] can result in the emergency call being attempted to another IP-CAN. b) attempt the attach for emergency bearer services to another PLMN in the shared network. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.3.1.4a |
5,496 | 6.8.1.1.2.2 Full native 5G NAS security context available | The UE shall transmit a NAS Registration Request message. This message is integrity protected using the distinct NAS COUNT values and the NAS connection identifier associated with this access. For the case that the 5G NAS security context used by the UE is non-current in the AMF, the AMF shall delete any existing current 5G security context and make the used 5G security context the current 5G security contex. Furthermore, provided that the NAS Registration Request was with "PDU session(s) to be re-activated" and there is no NAS SMC procedure before the AS SMC the NAS COUNT of the Registration Request message shall be used to derive the KgNB/KeNB with the KDF as specified in Annex A. As a result of the NAS Registration Request with "PDU session(s) to be re-activated", the gNB/ng-eNB shall send an AS SMC to the UE to activate AS security. The KgNB/KeNB used, is derived in the current 5G NAS security context. When the UE receives the AS SMC without having received a NAS Security Mode Command after the Registration Request with "PDU session(s) to be re-activated", it shall use the uplink NAS COUNT of the Registration Request message that triggered the AS SMC to be sent as freshness parameter in the derivation of the initial KgNB/KeNB. From this initial KgNB/KeNB the RRC protection keys and the UP protection keys shall be derived as described in sub-clause 6.2.3.1. The same procedure for generating initial KgNB/KeNB can be used regardless of the fact if the UE is connecting to the same AMF to which it was connected previously or to a different AMF. In case UE connects to a different AMF and this AMF selects different NAS algorithms, the NAS keys have to be re-derived in the AMF with the new algorithm IDs as input using the KDF as specified in Annex A. In addition, there is a need for the AMF to send a NAS SMC to the UE to indicate the change of NAS algorithms and to take the re-derived NAS keys into use. The UE shall assure that the NAS keys used to verify the integrity of the NAS SMC are derived using the algorithm ID specified in the NAS SMC. The NAS SMC Command and NAS SMC Complete messages are protected with the new NAS keys. If there is a NAS Security Mode Command after the Registration Request with "PDU session(s) to be re-activated" but before the AS SMC, the UE and AMF use the uplink NAS COUNT of the most recent NAS Security Mode Complete and the related KAMF as the parameter in the derivation of the KgNB/KeNB. From this KgNB/KeNB the RRC protection keys and the UP protection keys are derived as described in sub-clause 6.2.3.1. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.8.1.1.2.2 |
5,497 | 7.8 Bandwidth Adaptation | To enable BA on the PCell, the gNB configures the UE with UL and DL BWP(s). To enable BA on SCells in case of CA, the gNB configures the UE with DL BWP(s) at least (i.e. there may be none in the UL). For the PCell, the BWP used for initial access is configured via system information. For the SCell(s), the BWP used after initial activation is configured via dedicated RRC signalling. In paired spectrum, DL and UL can switch BWP independently. In unpaired spectrum, DL and UL switch BWP simultaneously. Switching between configured BWPs happens by means of RRC signalling, DCI, inactivity timer or upon initiation of random access. When an inactivity timer is configured for a serving cell, the expiry of the inactivity timer associated to that cell switches the active BWP to a default BWP configured by the network. There can be at most one active BWP per cell, except when the serving cell is configured with SUL, in which case there can be at most one on each UL carrier. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 7.8 |
5,498 | 8.2 National network subsystem numbers used for GSM/UMTS | The following national network subsystem numbers have been allocated for use within GSM/UMTS networks: 1111 1000 CSS (MAP); 1111 1001 PCAP; 1111 1010 BSC (BSSAP-LE); 1111 1011 MSC (BSSAP-LE); 1111 1100 SMLC (BSSAP-LE); 1111 1101 BSS O&M (A interface); 1111 1110 BSSAP (A interface). The following national network subsystem numbers have been allocated for use within and between GSM/UMTS networks: 1000 1110 RANAP; 1000 1111 RNSAP; 1001 0001 GMLC (MAP); 1001 0010 CAP; 1001 0011 gsmSCF (MAP) or IM-SSF (MAP) or Presence Network Agent; 1001 0100 SIWF (MAP); 1001 0101 SGSN (MAP); 1001 0110 GGSN (MAP). | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 8.2 |
5,499 | 5.28.5 Support of integration with IETF Deterministic Networking 5.28.5.1 General | 5GS acts as a DetNet Router according to the architecture defined in clause 4.4.8.4. When integrated with an IETF Deterministic Network, 5GS acts as one or more routers. A 5GS router is composed of the ports on a single UPF (i.e. PSA) network side, the user plane tunnel between the UE and UPF, and the ports on the device side. For each 5GS router of a deterministic network, the ports on the network side and the ports on device side that are associated to the PDU Sessions support connectivity to the deterministic network. The granularity of the 5GS DetNet node is per UPF for each network instance or DNN/S-NSSAI. The TSCTSF stores the binding relationship between a device side port and a PDU Session identified by the UE address. The TSCTSF also stores information about ports on the UPF/NW-TT side. The integration with IETF Deterministic Networking assumes the following. - The existing 3GPP routing mechanisms are re-used for DetNet. - The existing multicast capabilities can be re-used for DetNet communications. - The 5GS integration to IETF DetNet is based on DetNet for IP; DetNet for MPLS is not supported. - IPbased DetNet traffic is carried in IPtype PDU Sessions. - 5GS functions realize the DetNet forwarding sub-layer. For the IP case, according to clause 1 of IETF RFC 8939 [157], no service sub-layer function needs to be defined. The 5GS DetNet Router acts as a DetNet transit node as defined in IETF RFC 8655 [150]. The interface between the TSCTSF and the DetNet controller uses protocols defined in IETF. The DetNet configuration is carried in the YANG model [154] over Netconf [155] or Restconf [156]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.28.5 |
5,500 | 4.1.3.3 RRC connection usage per UE multi-RAT capability | a) This measurement provides RRC connection usage per UE multi-RAT capability. The measurement is split into subcounters per UE multi-RAT capability. b) DER (n=1) c) This measurement is obtained by accumulating successful RRC connections per UE multi-RAT capability after the receipt of a RRC CONNECTION SETUP COMPLETE message by the eNodeB/RN. The possible UE multi-RAT capabilities are included in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]. One or more subcounters are stepped based on received UE multi-RAT capabilities. d) Each measurement is an integer value. e) RRC.ConnUsage.geranCs RRC.ConnUsage.geranPs RRC.ConnUsage.cdma20001xRTT RRC.ConnUsage.utra RRC.ConnUsage.eutra RRC.ConnUsage.eutra-nr RRC.ConnUsage.nr f) EUtranCellFDD EUtranCellTDD g) Valid for packet switching. h) EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.1.3.3 |
Subsets and Splits
No saved queries yet
Save your SQL queries to embed, download, and access them later. Queries will appear here once saved.