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
⌀ |
|---|---|---|---|---|---|---|---|
3,601 | 12.3.10.4.1 Description | For messages destined to a remote GTP-C entity (i.e. a GTP-C entity not in direct contact but reached via an intermediate GTP-C entity), the source GTP-C entity shall enforce the overload control based on the overload information of the target of the message, as well as the overload information of the intermediate GTP-C entity, e.g. the MME applies the overload control for messages targeted for the PGW based on the overload information of the SGW and PGW. For the received messages, the intermediate GTP-C entity shall not further enforce any overload control and hence, shall not reject any message towards the source GTP-C entity. Annex D.4.1 provides an (informative) example of a possible implementation. NOTE 1: This approach ensures the overload protection of the Target as well as Intermediate GTP-C entities. NOTE 2: The source GTP-C entity may be connected to the same Target GTP-C entity via multiple different Intermediate GTP-C entities. The exact algorithm used at the source GTP-C entity to enforce the overload control, as per the aforementioned requirements, is implementation specific. | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 12.3.10.4.1 |
3,602 | 10.5.3.9 Time Zone and Time | The purpose of the timezone part of this information element is to encode the offset between universal time and local time in steps of 15 minutes. The purpose of the time part of this information element is to encode the universal time at which this information element may have been sent by the network. The Time Zone and Time information element is coded as shown in figure 10.5.84/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.97/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The Time Zone and Time is a type 3 information element with a length of 8 octets. Figure 10.5.84/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Time Zone and Time information element Table 10.5.97/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Timezone and Time information element NOTE: Due to ambiguities in earlier versions of the protocol specifications, some mobile stations may interpret the received NITZ time as local time. This may result in incorrect time settings in the mobile. | 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.3.9 |
3,603 | 9.3.5.2.2 TDD | For the parameters specified in Table 9.3.5.2.2-1, and using the downlink physical channels specified in Annex C, the minimum requirements are specified in 9.3.5.2.2-2 and by the following a) the ratio of the throughput obtained when transmitting the transport format indicated by each reported wideband CQI index subject to an interference source with specified DIP and that obtained when transmitting the transport format indicated by each reported wideband CQI index subject to a white Gaussian noise source shall be ≥ ; b) when transmitting the transport format indicated by each reported wideband CQI index subject to an interference source with specified DIP, the average BLER for the indicated transport formats shall be greater than or equal to 2%. Table 9.3.5.2.2-1 Fading test for single antenna (TDD) Table 9.3.5.2.2-2 Minimum requirement (TDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.3.5.2.2 |
3,604 | 6.4 5GS TSN services charging | The corresponding description to support of integration with TSN and enablers for Time Sensitive Communications and Time Synchronization are specified TS 23.501[ System architecture for the 5G System (5GS) ] [3] clauses 5.27 and 5.28. - 5GS acts as a Layer 2 Ethernet Bridge. When integrated with IEEE TSN network, 5GS functions acts as one or more TSN Bridges of the TSN network. The configuration of the 5GS Bridge can be provided by TSN AF and CNC. - 5G System features that can be used independently or in combination to enable time-sensitive communication and time synchronization. | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 6.4 |
3,605 | – CrossCarrierSchedulingConfig | The IE CrossCarrierSchedulingConfig is used to specify the configuration when the cross-carrier scheduling is used in a cell. CrossCarrierSchedulingConfig information element -- ASN1START -- TAG-CROSSCARRIERSCHEDULINGCONFIG-START CrossCarrierSchedulingConfig ::= SEQUENCE { schedulingCellInfo CHOICE { own SEQUENCE { -- Cross carrier scheduling: scheduling cell cif-Presence BOOLEAN }, other SEQUENCE { -- Cross carrier scheduling: scheduled cell schedulingCellId ServCellIndex, cif-InSchedulingCell INTEGER (1..7) } }, ..., [[ carrierIndicatorSize-r16 SEQUENCE { carrierIndicatorSizeDCI-1-2-r16 INTEGER (0..3), carrierIndicatorSizeDCI-0-2-r16 INTEGER (0..3) } OPTIONAL, -- Cond CIF-PRESENCE enableDefaultBeamForCCS-r16 ENUMERATED {enabled} OPTIONAL -- Need S ]], [[ ccs-BlindDetectionSplit-r17 ENUMERATED {oneSeventh, threeFourteenth, twoSeventh, threeSeventh, oneHalf, fourSeventh, fiveSeventh, spare1} OPTIONAL -- Need R ]] } -- TAG-CROSSCARRIERSCHEDULINGCONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,606 | 10.5.5.7 Force to standby | The purpose of the force to standby information element is to force the MS to stop the READY timer in order to prevent the MS to perform cell updates. In Iu mode, the network shall always indicate force to standby not indicated in the force to standby information element. The force to standby is a type 1 information element. The force to standby information element is coded as shown in figure 10.5.123/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.140/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.123/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Force to standby information element Table 10.5.140/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Force to standby 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.7 |
3,607 | – CodebookConfig | The IE CodebookConfig is used to configure codebooks of Type-I and Type-II (see TS 38.214[ NR; Physical layer procedures for data ] [19], clause 5.2.2.2) CodebookConfig information element -- ASN1START -- TAG-CODEBOOKCONFIG-START CodebookConfig ::= SEQUENCE { codebookType CHOICE { type1 SEQUENCE { subType CHOICE { typeI-SinglePanel SEQUENCE { nrOfAntennaPorts CHOICE { two SEQUENCE { twoTX-CodebookSubsetRestriction BIT STRING (SIZE (6)) }, moreThanTwo SEQUENCE { n1-n2 CHOICE { two-one-TypeI-SinglePanel-Restriction BIT STRING (SIZE (8)), two-two-TypeI-SinglePanel-Restriction BIT STRING (SIZE (64)), four-one-TypeI-SinglePanel-Restriction BIT STRING (SIZE (16)), three-two-TypeI-SinglePanel-Restriction BIT STRING (SIZE (96)), six-one-TypeI-SinglePanel-Restriction BIT STRING (SIZE (24)), four-two-TypeI-SinglePanel-Restriction BIT STRING (SIZE (128)), eight-one-TypeI-SinglePanel-Restriction BIT STRING (SIZE (32)), four-three-TypeI-SinglePanel-Restriction BIT STRING (SIZE (192)), six-two-TypeI-SinglePanel-Restriction BIT STRING (SIZE (192)), twelve-one-TypeI-SinglePanel-Restriction BIT STRING (SIZE (48)), four-four-TypeI-SinglePanel-Restriction BIT STRING (SIZE (256)), eight-two-TypeI-SinglePanel-Restriction BIT STRING (SIZE (256)), sixteen-one-TypeI-SinglePanel-Restriction BIT STRING (SIZE (64)) }, typeI-SinglePanel-codebookSubsetRestriction-i2 BIT STRING (SIZE (16)) OPTIONAL -- Need R } }, typeI-SinglePanel-ri-Restriction BIT STRING (SIZE (8)) }, typeI-MultiPanel SEQUENCE { ng-n1-n2 CHOICE { two-two-one-TypeI-MultiPanel-Restriction BIT STRING (SIZE (8)), two-four-one-TypeI-MultiPanel-Restriction BIT STRING (SIZE (16)), four-two-one-TypeI-MultiPanel-Restriction BIT STRING (SIZE (8)), two-two-two-TypeI-MultiPanel-Restriction BIT STRING (SIZE (64)), two-eight-one-TypeI-MultiPanel-Restriction BIT STRING (SIZE (32)), four-four-one-TypeI-MultiPanel-Restriction BIT STRING (SIZE (16)), two-four-two-TypeI-MultiPanel-Restriction BIT STRING (SIZE (128)), four-two-two-TypeI-MultiPanel-Restriction BIT STRING (SIZE (64)) }, ri-Restriction BIT STRING (SIZE (4)) } }, codebookMode INTEGER (1..2) }, type2 SEQUENCE { subType CHOICE { typeII SEQUENCE { n1-n2-codebookSubsetRestriction CHOICE { two-one BIT STRING (SIZE (16)), two-two BIT STRING (SIZE (43)), four-one BIT STRING (SIZE (32)), three-two BIT STRING (SIZE (59)), six-one BIT STRING (SIZE (48)), four-two BIT STRING (SIZE (75)), eight-one BIT STRING (SIZE (64)), four-three BIT STRING (SIZE (107)), six-two BIT STRING (SIZE (107)), twelve-one BIT STRING (SIZE (96)), four-four BIT STRING (SIZE (139)), eight-two BIT STRING (SIZE (139)), sixteen-one BIT STRING (SIZE (128)) }, typeII-RI-Restriction BIT STRING (SIZE (2)) }, typeII-PortSelection SEQUENCE { portSelectionSamplingSize ENUMERATED {n1, n2, n3, n4} OPTIONAL, -- Need R typeII-PortSelectionRI-Restriction BIT STRING (SIZE (2)) } }, phaseAlphabetSize ENUMERATED {n4, n8}, subbandAmplitude BOOLEAN, numberOfBeams ENUMERATED {two, three, four} } } } CodebookConfig-r16 ::= SEQUENCE { codebookType CHOICE { type2 SEQUENCE { subType CHOICE { typeII-r16 SEQUENCE { n1-n2-codebookSubsetRestriction-r16 CHOICE { two-one BIT STRING (SIZE (16)), two-two BIT STRING (SIZE (43)), four-one BIT STRING (SIZE (32)), three-two BIT STRING (SIZE (59)), six-one BIT STRING (SIZE (48)), four-two BIT STRING (SIZE (75)), eight-one BIT STRING (SIZE (64)), four-three BIT STRING (SIZE (107)), six-two BIT STRING (SIZE (107)), twelve-one BIT STRING (SIZE (96)), four-four BIT STRING (SIZE (139)), eight-two BIT STRING (SIZE (139)), sixteen-one BIT STRING (SIZE (128)) }, typeII-RI-Restriction-r16 BIT STRING (SIZE(4)) }, typeII-PortSelection-r16 SEQUENCE { portSelectionSamplingSize-r16 ENUMERATED {n1, n2, n3, n4}, typeII-PortSelectionRI-Restriction-r16 BIT STRING (SIZE (4)) } }, numberOfPMI-SubbandsPerCQI-Subband-r16 INTEGER (1..2), paramCombination-r16 INTEGER (1..8) } } } CodebookConfig-r17 ::= SEQUENCE { codebookType CHOICE { type1 SEQUENCE { typeI-SinglePanel-Group1-r17 SEQUENCE { nrOfAntennaPorts CHOICE { two SEQUENCE { twoTX-CodebookSubsetRestriction1-r17 BIT STRING (SIZE (6)) }, moreThanTwo SEQUENCE { n1-n2 CHOICE { two-one-TypeI-SinglePanel-Restriction1-r17 BIT STRING (SIZE (8)), two-two-TypeI-SinglePanel-Restriction1-r17 BIT STRING (SIZE (64)), four-one-TypeI-SinglePanel-Restriction1-r17 BIT STRING (SIZE (16)), three-two-TypeI-SinglePanel-Restriction1-r17 BIT STRING (SIZE (96)), six-one-TypeI-SinglePanel-Restriction1-r17 BIT STRING (SIZE (24)), four-two-TypeI-SinglePanel-Restriction1-r17 BIT STRING (SIZE (128)), eight-one-TypeI-SinglePanel-Restriction1-r17 BIT STRING (SIZE (32)), four-three-TypeI-SinglePanel-Restriction1-r17 BIT STRING (SIZE (192)), six-two-TypeI-SinglePanel-Restriction1-r17 BIT STRING (SIZE (192)), twelve-one-TypeI-SinglePanel-Restriction1-r17 BIT STRING (SIZE (48)), four-four-TypeI-SinglePanel-Restriction1-r17 BIT STRING (SIZE (256)), eight-two-TypeI-SinglePanel-Restriction1-r17 BIT STRING (SIZE (256)), sixteen-one-TypeI-SinglePanel-Restriction1-r17 BIT STRING (SIZE (64)) } } } } OPTIONAL, -- Need R typeI-SinglePanel-Group2-r17 SEQUENCE { nrOfAntennaPorts CHOICE { two SEQUENCE { twoTX-CodebookSubsetRestriction2-r17 BIT STRING (SIZE (6)) }, moreThanTwo SEQUENCE { n1-n2 CHOICE { two-one-TypeI-SinglePanel-Restriction2-r17 BIT STRING (SIZE (8)), two-two-TypeI-SinglePanel-Restriction2-r17 BIT STRING (SIZE (64)), four-one-TypeI-SinglePanel-Restriction2-r17 BIT STRING (SIZE (16)), three-two-TypeI-SinglePanel-Restriction2-r17 BIT STRING (SIZE (96)), six-one-TypeI-SinglePanel-Restriction2-r17 BIT STRING (SIZE (24)), four-two-TypeI-SinglePanel-Restriction2-r17 BIT STRING (SIZE (128)), eight-one-TypeI-SinglePanel-Restriction2-r17 BIT STRING (SIZE (32)), four-three-TypeI-SinglePanel-Restriction2-r17 BIT STRING (SIZE (192)), six-two-TypeI-SinglePanel-Restriction2-r17 BIT STRING (SIZE (192)), twelve-one-TypeI-SinglePanel-Restriction2-r17 BIT STRING (SIZE (48)), four-four-TypeI-SinglePanel-Restriction2-r17 BIT STRING (SIZE (256)), eight-two-TypeI-SinglePanel-Restriction2-r17 BIT STRING (SIZE (256)), sixteen-one-TypeI-SinglePanel-Restriction2-r17 BIT STRING (SIZE (64)) } } } } OPTIONAL, -- Need R typeI-SinglePanel-ri-RestrictionSTRP-r17 BIT STRING (SIZE (8)) OPTIONAL, -- Need R typeI-SinglePanel-ri-RestrictionSDM-r17 BIT STRING (SIZE (4)) OPTIONAL -- Need R }, type2 SEQUENCE { typeII-PortSelection-r17 SEQUENCE { paramCombination-r17 INTEGER (1..8), valueOfN-r17 ENUMERATED {n2, n4} OPTIONAL, -- Need R numberOfPMI-SubbandsPerCQI-Subband-r17 INTEGER(1..2) OPTIONAL, -- Need R typeII-PortSelectionRI-Restriction-r17 BIT STRING (SIZE (4)) } } } } CodebookConfig-v1730 ::= SEQUENCE { codebookType CHOICE { type1 SEQUENCE { codebookMode INTEGER (1..2) OPTIONAL -- Need R } } } CodebookConfig-r18 ::= SEQUENCE { codebookType CHOICE { type2 SEQUENCE { typeII-CJT-r18 SEQUENCE { n1-n2-codebookSubsetRestrictionList-r18 SEQUENCE (SIZE (1..4)) OF CBSR-r18, paramCombination-CJT-r18 INTEGER (1..7), paramCombination-CJT-L-r18 SEQUENCE (SIZE (1..4)) OF INTEGER (1..5) OPTIONAL, -- Need R restrictedCMR-Selection-r18 ENUMERATED {enable} OPTIONAL, -- Need R valueOfO3-r18 ENUMERATED {n1, n4} OPTIONAL, -- Need R numberOfPMI-SubbandsPerCQI-Subband-r18 INTEGER(1..2) OPTIONAL, -- Need R typeII-RI-Restriction-r18 BIT STRING (SIZE (4)), codebookMode-r18 INTEGER (1..2) OPTIONAL -- Need R }, typeII-CJT-PortSelection-r18 SEQUENCE { paramCombination-CJT-PS-r18 INTEGER (1..5), paramCombination-CJT-PS-alpha-r18 SEQUENCE (SIZE (1..4)) OF INTEGER (1..8) OPTIONAL, -- Need R restrictedCMR-Selection-r18 ENUMERATED {enable} OPTIONAL, -- Need R valueOfO3-r18 ENUMERATED {n1, n4} OPTIONAL, -- Need R valueOfN-CJT-r18 ENUMERATED {n2, n4} OPTIONAL, -- Need R numberOfPMI-SubbandsPerCQI-Subband-r18 INTEGER(1..2) OPTIONAL, -- Need R typeII-PortSelectionRI-Restriction-r18 BIT STRING (SIZE (4)), codebookMode-r18 INTEGER (1..2) OPTIONAL -- Need R }, typeII-Doppler-r18 SEQUENCE { n1-n2-codebookSubsetRestriction-r18 CBSR-r18, paramCombination-Doppler-r18 INTEGER (1..9), td-dd-config-r18 TD-DD-Config-r18 OPTIONAL, -- Need R numberOfPMI-SubbandsPerCQI-Subband-r18 INTEGER(1..2) OPTIONAL, -- Need R predictionDelay-r18 ENUMERATED {m0,n0,n1,n2 } OPTIONAL, -- Need R typeII-RI-Restriction-r18 BIT STRING (SIZE (4)) }, typeII-DopplerPortSelection-r18 SEQUENCE { paramCombinationDoppler-PS-r18 INTEGER (1..8), td-dd-config-r18 TD-DD-Config-r18 OPTIONAL, -- Need R valueOfN-Doppler-r18 ENUMERATED {n2, n4} OPTIONAL, -- Need R numberOfPMI-SubbandsPerCQI-Subband-r18 INTEGER(1..2) OPTIONAL, -- Need R predictionDelay-r18 ENUMERATED {m0,n0,n1,n2 } OPTIONAL, -- Need R typeII-PortSelectionRI-Restriction-r18 BIT STRING (SIZE (4)) } } } } CBSR-r18 ::= CHOICE { two-one BIT STRING (SIZE (8)), two-two BIT STRING (SIZE (27)), four-one BIT STRING (SIZE (16)), three-two BIT STRING (SIZE (35)), six-one BIT STRING (SIZE (24)), four-two BIT STRING (SIZE (43)), eight-one BIT STRING (SIZE (32)), four-three BIT STRING (SIZE (59)), six-two BIT STRING (SIZE (59)), twelve-one BIT STRING (SIZE (48)), four-four BIT STRING (SIZE (75)), eight-two BIT STRING (SIZE (75)), sixteen-one BIT STRING (SIZE (64)) } TD-DD-Config-r18 ::= SEQUENCE { vectorLengthDD-r18 ENUMERATED {n1,n2,n4,n8 }, unitDurationDD-r18 ENUMERATED {m1,m2} OPTIONAL, -- Need R aperiodicResourceOffset-r18 INTEGER(1..2) OPTIONAL, -- Need R tdCQI-r18 ENUMERATED {n11,n12,n2 } OPTIONAL -- Need R } -- TAG-CODEBOOKCONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,608 | 16.9.9.4 COT Sharing | UE to UE COT sharing is supported in NR sidelink operation for SL-U. When performing SL-SSB transmission(s), a responding UE can utilize a COT shared by a COT initiating UE when the responding UE intends to transmit SL-SSB in the shared COT. When performing PSFCH transmissions, a responding UE can utilize a COT shared by a COT initiating UE when at least one of the responding UE's PSFCH transmissions is intended for the COT initiating UE. When performing PSSCH/PSCCH transmissions, a responding UE can utilize a COT shared by a COT initiating UE when the responding UE's transmission(s) is intended for the COT initiating UE. In unicast, the destination/source ID of the responding UE's transmission should match the source/destination ID of the initiator UE's transmission for the same unicast link. In groupcast/broadcast, destination ID of the responding UE's transmission should match the initiator's destination ID. In addition, a COT initiating UE may transmit an additional pair of source/destination ID in either unicast, groupcast, or broadcast. In this case, the responding UE can utilize a COT shared by a COT initiating UE if the destination/source (for unicast) or destination (for groupcast/broadcast) of the responding UE transmission match what is carried in the additional ID(s). In all cases, a UE's transmissions in a shared COT should have SL-CAPC value that is equal to or smaller than the SL-CAPC value indicated in the COT sharing information. In order to satisfy the COT sharing requirements, a responding UE may perform an enhanced LCP procedure as specified in 38.321 [6]. When receiving multiple COT sharing indications from different COT initiators, it is up to UE implementation which shared COT is used. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.9.9.4 |
3,609 | 6.6.4.2 CK | The cipher key CK is 128 bits long. There may be one CK for CS connections (CKCS), established between the CS service domain and the user and one CK for PS connections (CKPS) established between the PS service domain and the user. The CK to use for a particular radio bearer is described in 6.6.5. For UMTS subscribers, CK is established during UMTS AKA, as the output of the cipher key derivation function f3, available in the USIM and in HLR/AuC. For GSM subscribers that access the UTRAN, CK is established following GSM AKA and is derived from the GSM cipher key Kc, as described in 8.2. CK is stored in the USIM and a copy is stored in the ME. CK is sent from the USIM to the ME upon request of the ME. The USIM shall send CK under the condition that a valid CK is available. The ME shall trigger a new authentication procedure if the current value of STARTCS or STARTPS in the USIM have reached THRESHOLD. The ME shall delete CK from memory after power-off as well as after removal of the USIM. CK is sent from the HLR/AuC to the VLR/SGSN and stored in the VLR/SGSN as part of the quintet. It is sent from the VLR/SGSN to the RNC in the (RANAP) security mode command. At handover, the CK is transmitted within the network infrastructure from the old RNC to the new RNC, to enable the communication to proceed. The cipher CK remains unchanged at handover, with the exception of SRVCC handover and reverse SRVCC handover. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 6.6.4.2 |
3,610 | 4.3.27a Restriction of use of Enhanced Coverage for voice centric UE | Support of UEs in Enhanced Coverage is specified 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]. If the UE's usage setting is "voice centric" as defined in TS 23.221[ Architectural requirements ] [27], it shall not operate in CE mode B. If the UE supports CE mode B and UE's usage setting is set to "voice centric" in the Attach or TAU request message then the MME shall indicate to eNodeB that CE mode B is restricted. If the UE supports CE mode B and UE's usage setting is set to "data centric" in the Attach or TAU request message then, based on operator's policy and the Enhanced Coverage Restricted parameter (see clause 4.3.28), the MME shall indicate to eNodeB that CE mode B is not restricted. The MME keeps the CE mode B Restricted parameter in the MM Context. The MME shall send the CE mode B Restricted parameter to the eNodeB via S1 signalling indicating whether the UE is "restricted" or "not restricted" for the use of CE mode B, e.g. in PAGING, INITIAL CONTEXT SETUP REQUEST, HANDOVER REQUEST, PATH SWITCH REQUEST ACKNOWLEDGE, CONNECTION ESTABLISHMENT INDICATION, and DOWNLINK NAS TRANSPORT message carrying the TAU ACCEPT message. If the UE supports CE mode B and the CE mode B Restricted parameter stored in the MME's MM context is set to "not restricted", the MME shall use the extended NAS timer settings for the UE as specified in TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [46]. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3.27a |
3,611 | 5.2.1.5 Alerting | Having entered the "mobile originating call proceeding" state, upon receiving an indication that user alerting has been initiated at the called address, the call control entity of the network shall: send an ALERTING message to its peer entity at the calling mobile station and enter the "call delivered" state. When the call control entity of the mobile station in the "call initiated" state or "mobile originating call proceeding" state receives an ALERTING message then, the call control entity of the mobile station shall stop timer T303 and T310 (if running) and shall enter the "call delivered" state. In this state: - for speech calls: an alerting indication should be given to the user. If the mobile station has not attached the user connection then the mobile station shall internally generate an alerting indication. If the mobile station has attached the user connection then the network is responsible for generating the alerting indication and the mobile station need not generate one; and - for multimedia calls: if the mobile station has not attached the user connection then the mobile station may internally generate an alerting indication. If the mobile station supports multimedia CAT during the alerting phase of a mobile originated multimedia call establishment, the network may request the mobile station to attach the user connection and setup a H.324 call and generate multimedia CAT as specified in subclause 5.3.6.4, in which case the mobile station need not generatean alerting tone. Abnormal cases: On the mobile station side, if timer T303 or T310 expires, the call control entity of the mobile station shall initiate call clearing as described in subclause 5.4. Figure 5.4/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Call confirmation at mobile originating call 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 | 5.2.1.5 |
3,612 | 6.2.3.1 Key setting | Key setting happens at the end of successful authentication procedure. Authentication and key setting may be initiated by the network as often as the network operator wishes when an active NAS connection exists. Key setting can occur as soon as the identity of the mobile subscriber (i.e. 5G-GUTI or SUPI) is known by the AMF. A successful run of 5G AKA or EAP AKA' results in a new KAMF that is stored in the UE and the AMF with a new partial, non-current security context. NAS keys (i.e. KNASint and KNASenc) and AS keys (i.e. KgNB, KRRCenc, KRRCint, KUPenc, KUPint) are derived from KAMF using the KDFs specified in Annex A. The NAS keys derived from the new KAMF are taken in use in the AMF and the UE by means of the NAS security mode command procedure (see sub-clause 6.7.2). The AS keys are taken into use with the AS security mode command procedure (see sub-clause 6.7.4) or with the key change on the fly procedure (see sub-clause 6.9.6). For the non-3GPP access, the key KN3IWF is derived from the KAMF. KN3IWF is stored in the UE and the N3IWF as specified in subclause 7.2.1. This key KN3IWF and the IPsec SA cryptographic keys are taken into use with the establishment of IPsec Security Association (SA) between the UE and the N3IWF. NOTE: For mapped security contexts, the KAMF is derived from EPS keys during interworking with EPS (see clause 8). | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.2.3.1 |
3,613 | 6.5.1.2 UE requested PDN connectivity procedure initiation | In order to request connectivity to a PDN, the UE shall send a PDN CONNECTIVITY REQUEST message to the MME, start timer T3482 and enter the state PROCEDURE TRANSACTION PENDING (see example in figure 6.5.1.2.1). When the PDN CONNECTIVITY REQUEST message is sent together with an ATTACH REQUEST message, the UE shall not start timer T3482 and shall not include the APN. NOTE 1: If the UE needs to provide protocol configuration options which require ciphering or provide an APN, or both, during the attach procedure, the ESM information transfer flag is included in the PDN CONNECTIVITY REQUEST. The MME then at a later stage in the PDN connectivity procedure initiates the ESM information request procedure in which the UE can provide the MME with protocol configuration options or APN or both. In order to request a PDN connection for emergency bearer services or for access to RLOS, the UE shall not include an APN in the PDN CONNECTIVITY REQUEST message or, when applicable, in the ESM INFORMATION RESPONSE message. In order to request connectivity to a PDN using the default APN, the UE includes the access point name IE in the PDN CONNECTIVITY REQUEST message or, when applicable, in the ESM INFORMATION RESPONSE message, according to the following conditions: - if use of a PDN using the default APN requires PAP/CHAP, then the UE should include the Access point name IE; and - in all other conditions, the UE need not include the Access point name IE. In order to request connectivity to an additional PDN using a specific APN, the UE shall include the requested APN in the PDN CONNECTIVITY REQUEST message or, when applicable, in the ESM INFORMATION RESPONSE message. NOTE 2: The requested APN in the PDN CONNECTIVITY REQUEST or ESM INFORMATION RESPONSE message is for UAS services when the request to establish a PDN connection for UAS services is requested by the upper layers. NOTE 3: By configuration provided by the operator, the UE supporting UAS services knows that an APN is for UAS services when the request to establish a PDN connection for UAS services is requested by the upper layers and how this UE configuration is achieved is implementation specific. In the PDN type IE the UE shall either indicate the IP version capability of the IP stack associated with the UE or non IP or Ethernet as specified in clause 6.2.2. If the PDN type value of the PDN type IE is set to IPv4 or IPv6 or IPv4v6 and the UE indicates "Control plane CIoT EPS optimization supported" in the UE network capability IE of the ATTACH REQUEST message, the UE may include the Header compression configuration IE in the PDN CONNECTIVITY REQUEST message. When the connectivity to a PDN is to be transferred from a non-3GPP access network to the 3GPP access network, the UE shall set the PDN type value of the PDN type IE to: - IPv4, if the previously allocated home address information consists of an IPv4 address only; - IPv6, if the previously allocated home address information consists of an IPv6 prefix only; or - IPv4v6, if the previously allocated home address information consists of both an IPv4 address and an IPv6 prefix. The UE shall set the request type to "initial request" when the UE is establishing a new PDN connectivity to a PDN in an attach procedure or in a stand-alone PDN connectivity procedure or when the UE requests establishment of a PDN connection as a user-plane resource of an MA PDU session to be established. The UE shall set the request type to "emergency" when the UE is requesting a new PDN connectivity for emergency bearer services. The UE shall set the request type to "handover" when the connectivity to a PDN is to be transferred from a non-3GPP access network to the 3GPP access network, when the UE initiates the procedure to add 3GPP access to the PDN connection which is already established over WLAN, when the UE supporting N1 mode requests transfer of an existing non-emergency PDU session in 5GS or when the UE requests establishment of a PDN connection as a user-plane resource of an already established MA PDU session. The UE shall set the request type to "handover of emergency bearer services" when a PDN connection for emergency bearer services is to be transferred from a WLAN to the 3GPP access network or when the UE supporting N1 mode requests transfer of an existing emergency PDU session in 5GS. The UE shall set the request type to "RLOS" when the UE is requesting a new PDN connection for RLOS. If the UE supports DSMIPv6, the UE may include a request for obtaining the IPv6 address and optionally the IPv4 address of the home agent in the Protocol configuration options IE in the PDN CONNECTIVITY REQUEST message. The UE may also include a request for obtaining the IPv6 Home Network Prefix. The UE shall request the IPv6 Home Network Prefix only if the UE has requested the home agent IPv6 address. The requested home agent address(es) and the Home Network Prefix are related to the APN the UE requested connectivity for. The UE may set the ESM information transfer flag in the PDN CONNECTIVITY REQUEST message to indicate that it has ESM information, i.e. protocol configuration options, APN, or both, that needs to be sent after the NAS signalling security has been activated between the UE and the MME. If the UE supports A/Gb mode or Iu mode or both, the UE shall indicate the support of the network requested bearer control procedures (see 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13]) in A/Gb mode or Iu mode in the Protocol configuration options IE. If the UE supports N1 mode and the request type is: a) "initial request" or "emergency", the UE shall generate a PDU session ID, associate the PDU session ID with the PDN connection that is being established, and include the PDU session ID in the Protocol configuration options IE or the Extended protocol configuration options IE; b) "handover" or "handover of emergency bearer services", and the UE requests: 1) transfer of an existing PDU session in 5GS or establishment of a PDN connection as a user-plane resource of an already established MA PDU session, the UE shall associate the PDU session ID of the PDU session with the PDN connection that is being established for the existing PDU session and include the PDU session ID in the Protocol configuration options IE or the Extended protocol configuration options IE; or 2) transfer of an existing PDN connection in a non-3GPP access connected to the EPC and a PDU session ID is associated with the existing PDN connection, the UE shall include the PDU session ID in the Protocol configuration options IE or the Extended protocol configuration options IE and associate the PDU session ID with the PDN connection that is being established. If the existing PDN connection is a non-emergency PDN connection and an S-NSSAI and a related PLMN ID are associated with the existing PDN connection, the UE shall in addition associate the S-NSSAI and the related PLMN ID with the PDN connection that is being established. NOTE 4: The UE can also have an S-NSSAI and the related PLMN ID associated with the PDN connection, if the S-NSSAI and the related PLMN ID was associated with the existing PDN connection in a non-3GPP access connected to the EPC as specified in 3GPP TS 24.302[ Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networks; Stage 3 ] [48]. The UE stores this S-NSSAI and the related PLMN ID for later use during inter-system change from S1 mode to N1 mode. If the N1 mode capability is disabled, the UE may apply a) and b.2) above for service continuity support at inter-system change from S1 mode to N1 mode once its N1 mode capability is enabled again. If the UE supporting N1 mode supports receiving QoS rules with the length of two octets or QoS flow descriptions with the length of two octets via the Extended protocol configuration options IE, the UE shall include the QoS rules with the length of two octets support indicator or the QoS flow descriptions with the length of two octets support indicator, respectively, in the Protocol configuration options IE or the Extended protocol configuration options IE. If the UE supports providing PDU session ID in the Protocol configuration options IE or the Extended protocol configuration options IE when its N1 mode capability is disabled, the UE shall include the QoS rules with the length of two octets support indicator or the QoS flow descriptions with the length of two octets support indicator, respectively, in the Protocol configuration options IE or the Extended protocol configuration options IE. Protocol configuration options provided in the ESM INFORMATION RESPONSE message replace any protocol configuration options provided in the PDN CONNECTIVITY REQUEST message. When the UE initiates the procedure to add 3GPP access to the PDN connection that is already established over WLAN, the UE shall provide the same APN as that of the PDN connection established over WLAN in the PDN connectivity procedure as specified in the clause 6.2.2 of 3GPP TS 23.161[ Network-Based IP Flow Mobility (NBIFOM); Stage 2 ] [34]. If the UE supports APN rate control, the UE shall include an APN rate control support indicator and an additional APN rate control for exception data support indicator in the Protocol configuration options IE or Extended protocol configuration options IE. If the UE supports DNS over (D)TLS (see 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]), the UE shall include the Protocol configuration options IE or the Extended protocol configuration options IE in the PDN CONNECTIVITY REQUEST or ESM INFORMATION RESPONSE message and include the DNS server security information indicator and optionally, if the UE wishes to indicate which security protocol type(s) are supported by the UE, it may include the DNS server security protocol support. NOTE 5: Support of DNS over (D)TLS is based on the informative requirements as specified in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. When the UE supporting UAS services initiates a UE requested PDN connectivity procedure for UAS services during an attach procedure, the UE: a) shall create the service-level-AA container with the length of two octets. In the service-level-AA container with the length of two octets, the UE: 1) shall include the service-level device ID parameter set to the UE's CAA-level UAV ID; 2) shall include the service-level-AA server address parameter set to the USS address, if it is provided by the upper layers; 3) shall include the service-level-AA payload parameter set to the UUAA payload and the service-level-AA payload type parameter set to "UUAA payload", if the UUAA payload is provided by the upper layer; and 4) shall include the service-level-AA payload parameter set to the C2 authorization payload and the service-level-AA payload type parameter set to "C2 authorization payload", if the C2 authorization procedure is requested; and NOTE 6: The C2 authorization payload in the service-level-AA payload parameter can include one, some or all of the pairing information for C2 communication, an indication of the request for direct C2 communication, pairing information for direct C2 communication and the flight authorization information. b) shall include the created service-level-AA container with the length of two octets in the Extended protocol configuration options IE of the PDN CONNECTIVITY REQUEST or ESM INFORMATION RESPONSE message. When the UE supporting UAS services initiates a UE requested PDN connectivity procedure for C2 communication after the completion of the attach procedure, the UE: a) shall create the service-level-AA container with the length of two octets. In the service-level-AA container with the length of two octets, the UE: 1) shall include the service-level device ID parameter set to the UE's CAA-level UAV ID; and 2) shall include the service-level-AA payload parameter set to the C2 authorization payload and the service-level-AA payload type parameter set to "C2 authorization payload"; and NOTE 7: The C2 authorization payload in the service-level-AA payload parameter can include one, some or all of the pairing information for C2 communication, an indication of the request for direct C2 communication, pairing information for direct C2 communication and the flight authorization information. b) shall include the created service-level-AA container with the length of two octets in the Extended protocol configuration options IE of the PDN CONNECTIVITY REQUEST message. If the UE supports provisioning of ECS configuration information to the EEC in the UE, then the UE may include the ECS configuration information provisioning support indicator in the Protocol configuration options IE or the Extended protocol configuration options IE in the PDN CONNECTIVITY REQUEST message. If the UE supports secondary DN authentication and authorization over EPC and has included the PDU session ID in the Protocol configuration options IE or the Extended protocol configuration options IE, the UE shall include the SDNAEPC support indicator in the Protocol configuration options IE or the Extended protocol configuration options IE in the PDN CONNECTIVITY REQUEST message, and if the UE requests to establish a new non-emergency PDN connection with a DN, the UE may include the SDNAEPC DN-specific identity set to DN-specific identity of the UE complying with network access identifier (NAI) format as specified in IETF RFC 7542 [62] in the Protocol configuration options IE or the Extended protocol configuration options IE in the PDN CONNECTIVITY REQUEST message. NOTE 8: The UE can avoid including both the SDNAEPC DN-specific identity and the protocol configuration option parameters with PAP/CHAP protocol identifiers in the PDN CONNECTIVITY REQUEST message. The way to achieve this is implementation dependent. If the UE supports URSP provisioning in EPS and the PDN CONNECTIVITY REQUEST message is sent together with an ATTACH REQUEST message, then the UE shall include the Protocol configuration options IE or the Extended protocol configuration options IE according to subclause 6.6.1.1 in the PDN CONNECTIVITY REQUEST or ESM INFORMATION RESPONSE message and shall include the URSP provisioning in EPS support indicator. If the UE supports URSP provisioning in EPS, the PDN CONNECTIVITY REQUEST message was not sent together with an ATTACH REQUEST message, the UE requested PDN connectivity procedure is performed for the first PDN connection, and the MME supports the Extended protocol configuration options IE then the UE shall include the Protocol configuration options IE or the Extended protocol configuration options IE according to subclause 6.6.1.1 in the PDN CONNECTIVITY REQUEST message and shall include the URSP provisioning in EPS support indicator. Figure 6.5.1.2.1: UE requested PDN connectivity 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.1.2 |
3,614 | – LocationInfo | The IE LocationInfo is used to transfer available detailed location information, Bluetooth, WLAN and sensor available measurement results at the UE. LocationInfo information element -- ASN1START -- TAG-LOCATIONINFO-START LocationInfo-r16 ::= SEQUENCE { commonLocationInfo-r16 CommonLocationInfo-r16 OPTIONAL, bt-LocationInfo-r16 LogMeasResultListBT-r16 OPTIONAL, wlan-LocationInfo-r16 LogMeasResultListWLAN-r16 OPTIONAL, sensor-LocationInfo-r16 Sensor-LocationInfo-r16 OPTIONAL, ... } -- TAG-LOCATIONINFO-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,615 | – SL-FreqConfig | The IE SL-FreqConfig specifies the dedicated configuration information on one particular carrier frequency for NR sidelink communication. SL-FreqConfig information element -- ASN1START -- TAG-SL-FREQCONFIG-START SL-FreqConfig-r16 ::= SEQUENCE { sl-Freq-Id-r16 SL-Freq-Id-r16, sl-SCS-SpecificCarrierList-r16 SEQUENCE (SIZE (1..maxSCSs)) OF SCS-SpecificCarrier, sl-AbsoluteFrequencyPointA-r16 ARFCN-ValueNR OPTIONAL, -- Need M sl-AbsoluteFrequencySSB-r16 ARFCN-ValueNR OPTIONAL, -- Need R frequencyShift7p5khzSL-r16 ENUMERATED {true} OPTIONAL, -- Cond V2X-SL-Shared valueN-r16 INTEGER (-1..1), sl-BWP-ToReleaseList-r16 SEQUENCE (SIZE (1..maxNrofSL-BWPs-r16)) OF BWP-Id OPTIONAL, -- Need N sl-BWP-ToAddModList-r16 SEQUENCE (SIZE (1..maxNrofSL-BWPs-r16)) OF SL-BWP-Config-r16 OPTIONAL, -- Need N sl-SyncConfigList-r16 SL-SyncConfigList-r16 OPTIONAL, -- Need M sl-SyncPriority-r16 ENUMERATED {gnss, gnbEnb} OPTIONAL -- Need M } SL-Freq-Id-r16 ::= INTEGER (1.. maxNrofFreqSL-r16) SL-FreqConfigExt-v1800 ::= SEQUENCE { absenceOfAnyOtherTechnology-r18 ENUMERATED {true} OPTIONAL, -- Need M sl-FreqSelectionConfig-r18 SL-FreqSelectionConfig-r18 OPTIONAL, -- Need M sl-SyncTxDisabled-r18 ENUMERATED {true} OPTIONAL, -- Need M sl-EnergyDetectionConfig-r18 CHOICE { sl-MaxEnergyDetectionThreshold-r18 INTEGER (-85..-52), sl-EnergyDetectionThresholdOffset-r18 INTEGER (-13..20) } OPTIONAL, -- Need M ue-ToUE-COT-SharingED-Threshold-r18 INTEGER (-85..-52) OPTIONAL, -- Need M harq-ACKFeedbackRatioforCW-AdjustmentGC-Option2-r18 INTEGER (10..100) OPTIONAL, -- Need M ... } -- TAG-SL-FREQCONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,616 | 5.4.4b UE 5GSM Core Network Capability handling | The UE 5GSM Core Network Capability is included in PDU Session Establishment/Modification Request. The UE shall indicate in the UE 5GSM Core Network Capability whether the UE supports: - "Ethernet" PDU Session Type supported in EPC as PDN Type "Ethernet"; - Reflective QoS; - Multi-homed IPv6 PDU Session (only if the Requested PDU Type was set to "IPv6" or "IPv4v6"); - ATSSS capability (as referred to clause 5.32.2); - Transfer of Port Management Information containers; - Support for secondary DN authentication and authorization over EPC (as referred to clause 5.17.2.5). The 5GSM Core Network Capability is transferred, if needed, from V-SMF to H-SMF during PDU Session Establishment/Modification procedure. After the first inter-system change from EPS to 5GS for a PDU session established in EPS, the 5GSM Core Network Capability is also included in the PDU Session Modification if the Reflective QoS and/or Multi-homed IPv6 PDU Session is present. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.4.4b |
3,617 | 5.8.10.2 Sidelink measurement configuration 5.8.10.2.1 General | The UE shall: 1> if the received sl-MeasConfig includes the sl-MeasObjectToRemoveList in the RRCReconfigurationSidelink: 2> perform the sidelink measurement object removal procedure as specified in 5.8.10.2.4; 1> if the received sl-MeasConfig includes the sl-MeasObjectToAddModList in the RRCReconfigurationSidelink: 2> perform the sidelink measurement object addition/modification procedure as specified in 5.8.10.2.5; 1> if the received sl-MeasConfig includes the sl-ReportConfigToRemoveList in the RRCReconfigurationSidelink: 2> perform the sidelink reporting configuration removal procedure as specified in 5.8.10.2.6; 1> if the received sl-MeasConfig includes the sl-ReportConfigToAddModList in the RRCReconfigurationSidelink: 2> perform the sidelink reporting configuration addition/modification procedure as specified in 5.8.10.2.7; 1> if the received sl-MeasConfig includes the sl-QuantityConfig in the RRCReconfigurationSidelink: 2> perform the sidelink quantity configuration procedure as specified in 5.8.10.2.8; 1> if the received sl-MeasConfig includes the sl-MeasIdToRemoveList in the RRCReconfigurationSidelink: 2> perform the sidelink measurement identity removal procedure as specified in 5.8.10.2.2; 1> if the received sl-MeasConfig includes the sl-MeasIdToAddModList in the RRCReconfigurationSidelink: 2> perform the sidelink measurement identity addition/modification procedure as specified in 5.8.10.2.3; | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.10.2 |
3,618 | 7.3.22 UE Registration Query Response | The UE Registration Query Response message shall be sent as a response to a UE Registration Query Request, to report whether the inquired UE is registered in the MME and if so, with which Core Network Operator, as specified in the clause 7.1.6 of 3GPP TS 23.251[ Network sharing; Architecture and functional description ] [55]. Possible Cause values are specified in Table 8.4-1. Message specific cause values are: - "Request accepted", to be used when the UE is registered in the MME - "IMSI/IMEI not known", to be used when the UE is not registered in the MME. The IMSI received in the UE Registration Query Request message shall be included in the response, to allow correlation in the SGSN. The Selected Core Network Operator Identifier identifies the core network operator currently serving the UE, and shall be included if the inquired UE is registered in the MME. Table 7.3.22-1 specifies the presence of IEs in this message. Table 7.3.22-1: Information Elements in UE Registration Query Response | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 7.3.22 |
3,619 | 4.6.2.7 Mobility management based network slice replacement | The support for network slice replacement by a UE or network is optional. If the UE and network support network slice replacement, and the AMF determines that an S-NSSAI included in the allowed NSSAI needs to be replaced with an alternative S-NSSAI, the AMF provides: a) the alternative S-NSSAI in the allowed NSSAI, if not included yet; b) the alternative S-NSSAI in the configured NSSAI, if not included yet; c) the alternative S-NSSAI in the NSAG information, if not included yet and the UE supports NSAG; and d) the mapping information between the S-NSSAI to be replaced and the alternative S-NSSAI, to the UE during the UE configuration update procedure or during the registration procedure as follows: a) for non-roaming UE, the AMF provides the mapping information between the S-NSSAI included in the allowed NSSAI and the alternative S-NSSAI to the UE; and NOTE 1: In non-roaming scenarios, the alternative S-NSSAI does not have to be part of the subscribed S-NSSAI(s) in the UE subscription. b) for roaming UE: 1) if the S-NSSAI included in the allowed NSSAI needs to be replaced (i.e. the S-NSSAI to be replaced is part of the VPLMN S-NSSAIs), the AMF provides the mapping information between the S-NSSAI included in the allowed NSSAI and the alternative S-NSSAI to the UE; and 2) if the S-NSSAI included in the mapped S-NSSAI(s) for the allowed NSSAI needs to be replaced (i.e. the S-NSSAI to be replaced is part of the HPLMN S-NSSAIs), the AMF provides the mapping information between the S-NSSAI and the alternative S-NSSAI to the UE. NOTE 1A: In roaming scenarios, the alternative S-NSSAI part of the HPLMN S-NSSAIs does not have to be part of the subscribed S-NSSAI(s) in the UE subscription. NOTE 2: It is up to AMF local policy to determine when to provide the mapping information between the S-NSSAI to be replaced and the alternative S-NSSAI to the UE, e.g. when the alternative S-NSSAI is available and there is no PDU session associated with the S-NSSAI to be replaced, or wait until the UE establishes the first PDU session associated with the S-NSSAI to be replaced. If the AMF determines that the S-NSSAI which has been replaced is available, the AMF provides the updated alternative NSSAI excluding the S-NSSAI which has been replaced and the corresponding alternative S-NSSAI to the UE during the UE configuration update procedure or during the registration procedure. If all the S-NSSAI(s) that were replaced in alternative NSSAI are available, the AMF provides the alternative NSSAI with Length of Alternative NSSAI contents set to 0 in the UE configuration update procedure or registration procedure. The AMF also provides the updated allowed NSSAI and configured NSSAI to the UE. NOTE 3: If there is S-NSSAI location validity information for both the S-NSSAI to be replaced and the alternative S-NSSAI, the NS-AoS of the alternative S-NSSAI is the same as or larger than the NS-AoS of the S-NSSAI to be replaced. If the NS-AoS of the alternative S-NSSAI is larger than the NS-AoS of the S-NSSAI to be replaced, the UE can request the establishment of user plane resources of PDU session(s) associated with the alternative S-NSSAI in the cell(s) outside the NS-AoS of the S-NSSAI to be replaced but within the NS-AoS of the alternative S-NSSAI. | 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.6.2.7 |
3,620 | 14.1.3 Nausf_SoRProtection service | The following table illustrates the security related services for SoR that AUSF provides. Table 14.1.3-1: NF services for SoR provided by AUSF Service operation name: Nausf_SoRProtection. Description: The AUSF calculates the SoR-MAC-IAUSF as specified in the Annex A.17 of this document using UE specific home key (KAUSF), the Steering Information List and ACK Indication received from the requester NF and delivers the SoR-MAC-IAUSF and CounterSoR to the requester NF. If the ACK Indication input is set to indicate that the acknowledgement is requested, then the AUSF shall compute the SoR-XMAC-IUE as specified in Annex A.18 of the present document, and return it in the response. NOTE: At reception of Nausf_SoRProtection_Protect request from the UDM, the AUSF constructs the SOR header, as described in clause 9.11.3.51 of TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [35], based on the information received from the requester NF, i.e. ACK Indication and list of preferred PLMN/access technology combinations or a secured packet (if provided). Input, Required: Requester ID, SUPI, service name, ACK Indication. Input, Optional: list of preferred PLMN/access technology combinations or secured packet or SoR transparent container. Output, Required: SoR-MAC-IAUSF, CounterSoR or error (counter_wrap). Output, Optional: SoR-XMAC-IUE (if the ACK Indication input is set to indicate that the acknowledgement is requested, then the SoR-XMAC-IUE shall be computed and returned). | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 14.1.3 |
3,621 | 6.4.3.5 Abnormal cases in the UE | Apart from the case described in clause 6.3.3, the following abnormal cases can be identified: a) Collision of UE requested bearer resource modification procedure and EPS bearer context modification procedure: If the UE receives a MODIFY EPS BEARER CONTEXT REQUEST message during the UE requested bearer resource modification procedure, the Procedure transaction identity IE of the MODIFY EPS BEARER CONTEXT REQUEST message is set to "No procedure transaction identity assigned" and the EPS bearer indicated in the MODIFY EPS BEARER CONTEXT REQUEST message is the EPS bearer that the UE had requested to modify, the UE shall abort internally the UE requested bearer resource modification procedure, and: - if the UE had initiated resource release for all the traffic flows for the bearer and the UE still needs to release the bearer (e.g. the TFT is empty due to error cases described in subclause 6.4.2.4 or subclause 6.4.3.4), the UE may proceed with the EPS bearer context modification procedure (i.e. respond with a MODIFY EPS BEARER CONTEXT ACCEPT message or a MODIFY EPS BEARER CONTEXT REJECT message) and deactivate the EPS bearer context locally without peer-to-peer signalling between the UE and the MME. In order to synchronize the EPS bearer context status with the MME, the UE may send a TRACKING AREA UPDATE REQUEST message that includes the EPS bearer context status IE to the MME; or - otherwise, the UE shall enter the state BEARER CONTEXT ACTIVE and proceed with the EPS bearer context modification 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.4.3.5 |
3,622 | 5.31.12 Restriction of use of Enhanced Coverage | Support of UEs in E-UTRA Enhanced Coverage is specified in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [30]. The usage of Enhanced Coverage requires use of extensive resources (e.g. radio and signalling resources). Specific subscribers can be restricted to use the Enhanced Coverage feature through Enhanced Coverage Restricted information that is stored in the UDM as part of subscription data and specifies per PLMN whether the Enhanced Coverage functionality is restricted or not for the UE. For eMTC, the Enhanced Coverage Restricted information indicates whether CE mode B is restricted for the UE, or both CE mode A and CE mode B are restricted for the UE, or both CE mode A and CE mode B are not restricted for the UE. For NB-IoT, the NB-IoT Enhanced Coverage Restricted information indicates whether the Enhanced Coverage is restricted or not for the UE. The AMF receives Enhanced Coverage Restricted information from the UDM during the Registration procedure. If the UE includes the support for restriction of use of Enhanced Coverage in the Registration Request message, the AMF based on local configuration, UE Usage setting, UE subscription information and network policies, or any combination of them, determines whether Enhanced Coverage is restricted for the UE and stores updated Enhanced Coverage Restriction information in the UE context in the AMF. If the UE usage setting indicated that UE is "voice centric", then the AMF shall set CE mode B restricted for the UE in Enhanced Coverage Restriction information. The AMF sends Enhanced Coverage Restricted information to the UE in the Registration Accept message. The UE shall use the value of Enhanced Coverage Restricted information to determine if enhanced coverage feature is restricted or not. The AMF provides an Enhanced Coverage Restricted information to the RAN via N2 signalling whenever the UE context is established in the RAN, e.g. during N2 Paging procedure, Service Request procedure, Initial Registration and Periodic Registration procedure. For roaming UEs, if the UDM doesn't provide any Enhanced Coverage Restricted information or the provided Enhanced Coverage Restricted information is in conflict with the roaming agreement, the AMF uses default Enhanced Coverage Restricted information locally configured in the VPLMN based on the roaming agreement with the subscriber's HPLMN. The UE indicates its capability of support for restriction of use of Enhanced Coverage to the AMF in the Registration procedure for the RAT it is camping on. A UE that supports Enhanced Coverage shall also support restriction of the Enhanced Coverage. The UE shall assume that restriction for use of Enhanced Coverage indicated by Enhanced Coverage Restricted information is the same in the equivalent PLMNs. NB-IoT cells also broadcast the support of restriction of use of Enhanced Coverage as defined in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [51]. If the UE supports CE mode B and use of CE mode B is not restricted according to the Enhanced Coverage Restriction information in the UE context in the AMF, then the AMF shall use the extended NAS-MM timer setting for the UE as specified in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47] and shall send the extended NAS-SM timer indication during PDU session establishment to the SMF. If the UE supports CE mode B and use of CE mode B changes from restricted to unrestricted or vice versa in the Enhanced Coverage Restriction information in the UE context in the AMF (e.g. due to a subscription change) then: - The AMF determines when to enforce the change of restriction of use of Enhanced Coverage. - When the UE is in CM-CONNECTED mode, the AMF can use the UE Configuration Update procedure, as specified in step 3a of clause 4.2.4.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3], to trigger a mobility registration update procedure in CM-CONNECTED mode for the AMF to inform the change of restriction of Enhanced Coverage towards the UE. - If the UE has already established PDU sessions, then the AMF shall trigger a PDU session modification to the SMFs serving the UE's PDU sessions to update the use of the extended NAS-SM timer setting as described in step 1f of clause 4.3.3.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] when the AMF determines that NAS-SM timer shall be updated due to the change of Enhanced Coverage Restriction. - The UE and network applies the new Enhanced Coverage Restriction information after mobility registration procedure is completed. Based on the extended NAS-SM timer indication, the SMF shall use the extended NAS-SM timer setting for the UE as specified in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]. The support for Enhanced Coverage Restriction Control via NEF enables AF to query status of Enhanced Coverage Restriction or enable/disable Enhanced Coverage Restriction per individual UEs. The procedure for Enhanced Coverage Restriction Control via NEF is described in clause 4.27 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.31.12 |
3,623 | 8.9.1.2.3 Closed-loop spatial multiplexing performance (User-Specific Reference Symbols) | 8.9.1.2.3.1 Single-layer Spatial Multiplexing For single-layer transmission on antenna ports 7 or 8 upon detection of a PDCCH with DCI format 2C, the requirements are specified in Table 8.9.1.2.3.1-2 with the addition of the parameters in Table 8.9.1.2.3.1-1 and the downlink physical channel setup according to Annex C.3.2. The purpose of these tests is to verify rank-1 performance on one of the antenna ports 7 or 8, and to verify rate matching with multiple CSI reference symbol configurations with non-zero and zero transmission power. Table 8.9.1.2.3.1-1: Test Parameters for Testing CDM-multiplexed DM RS (single layer) with multiple CSI-RS configurations Table 8.9.1.2.3.1-2: Minimum performance for CDM-multiplexed DM RS without simultaneous transmission (FRC) with multiple CSI-RS configurations 8.9.1.2.3.2 Single-layer Spatial Multiplexing with CRS assistance information The requirements are specified in Table 8.9.1.2.3.2-2, with the addition of parameters in Table 8.9.1.2.3.2-1. In Table 8.9.1.2.3.2-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 single-layer spatial multiplexing TM9 performance under assumption that UE applies CRS interference mitigation in the scenario with 2 CRS antenna ports in the serving and aggressor cells. Table 8.9.1.2.3.2-1: Test Parameters Table 8.9.1.2.3.2-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.3 |
3,624 | 5.3.5.12 BAP configuration | The IAB-MT shall: 1> if the bap-Config is set to setup: 2> if no BAP entity is established: 3> establish a BAP entity as specified in TS 38.340[ NR; Backhaul Adaptation Protocol (BAP) specification ] [47]; 2> if bap-Address is included: 3> configure the BAP entity to use the bap-Address as this node's BAP address; 2> if defaultUL-BAP-RoutingID is included: 3> configure the BAP entity to apply the default UL BAP routing ID according to the configuration; 2> if defaultUL-BH-RLC-Channel is included 3> configure the BAP entity to apply the default UL BH RLC channel according to the configuration; 2> if flowControlFeedbackType is included: 3> configure the BAP entity to apply the flow control feedback according to the configuration; 1> if the bap-Config is set to release: 2> release the concerned bap-Config; 2> if there is no other configured bap-Config for the MCG or for the SCG 3> release the BAP entity as specified in TS 38.340[ NR; Backhaul Adaptation Protocol (BAP) specification ] [47]. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.5.12 |
3,625 | 5.2.2.2.9 Namf_Communication_N2InfoUnsubscribe service operation | Service operation name: Namf_Communication_N2InfoUnSubscribe. Description: An NF can invoke this service operation to unsubscribe for the delivery of information contained in a specific N2 message type. Input, Required: CN NF ID, N2 information type to unsubscribe. Input, Optional: None. Output, Required: None. Output, Optional: None. The consumer NF invokes the Namf_Communication_N2InfoUnSubscribe service operation (CN NF ID, N2 information type to unsubscribe) on the AMF. The AMF deletes the binding for the consumer NF to for the requested information to unsubscribe. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.2.2.9 |
3,626 | 28.7.9.2 Decorated NAI used for 5G NSWO | The result is a decorated NAI of the form: 5gc-nswo.mnc<homeMNC>.mcc<homeMCC>.3gppnetwork.org!<username of SUCI in NAI format>@5gc-nswo.mnc<visitedMNC>.mcc<visitedMCC>.3gppnetwork.org For the SNPN scenarios where the credential holder is a subscribed SNPN, the decorated NAI should have the form as mentioned below: 5g-nswo.nid<subscribedSNPNNID>.mnc<subscribedSNPNMNC>.mcc<subscribedSNPNMCC>.3gppnetwork.org!<username of SUCI in NAI format>@5g-nswo.nid<nonsubscribedSNPNNID>.mnc<nonsubscribedSNPNMNC>.mcc<nonsubscribedSNPNMCC>.3gppnetwork.org For the SNPN scenarios where the credential holder is an HPLMN, the decorated NAI should have the form as mentioned below: 5g-nswo.mnc<homeMNC >.mcc<homeMCC>.3gppnetwork.org!<username of SUCI in NAI format>@5g-nswo.nid<nonsubscribedSNPNNID>.mnc<nonsubscribedSNPNMNC>.mcc<nonsubscribedSNPNMCC>.3gppnetwork.org EXAMPLE: Assuming the IMSI 234150999999999, where MCC=234, MNC=15 and MSISN=0999999999, the Routing Indicator 678, a Home Network Public Key Identifier of 27, the null-scheme, and the Visited PLMN ID (MCC = 610, MNC = 71): - the NAI format for the SUCI for 5G NSWO takes the form: type0.rid678.schid0.userid0999999999@5gc-nswo.mnc015.mcc234.3gppnetwork.org - the Decorated NAI format for the SUCI for 5G NSWO roaming takes the form: 5gc-nswo.mnc015.mcc234.3gppnetwork.org!type0.rid678.schid0.userid0999999999@5gc-nswo.mnc071.mcc610.3gppnetwork.org For SNPN scenarios, decorated NAI format for SUCI for 5G-NSWO roaming shall take the following form: Assuming the IMSI 234150999999999, where the subscribed SNPN that has MCC 234, MNC 015, and NID 345678ABCD and the non-subscribed SNPN (MCC =999, MNC =012, and NID 45678ABCDE).5gc-nswo.nid345678ABCD.mnc015.mcc234.3gppnetwork.org!type0.rid678.schid0.userid0999999999@5gc-nswo.nid45678ABCDE.mnc012.mcc999.3gppnetwork.org Assuming the IMSI 234150999999999, where the HPLMN that has MCC 234 and MNC 015 and the non-subscribed SNPN (MCC =999, MNC =012, and NID 45678ABCDE). 5gc-nswo.nid345678ABCD.mnc015.mcc234.3gppnetwork.org!type0.rid678.schid0.userid0999999999@5gc-nswo.nid45678ABCDE.mnc012.mcc999.3gppnetwork.org | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 28.7.9.2 |
3,627 | 16.15.5 Non-Homogeneous support of PDU set based handling in NG-RAN | During a handover from a gNB supporting PDU Set based handling to another gNB, the source gNB signals the PDU Set Information over Xn-U if the target node has signalled the support of PDU Set based handling in the Xn Handover Request Acknowledge message. During a handover from a gNB not supporting PDU Set based handling to a gNB supporting PDU Set based handling, the target gNB may indicate the support of PDU Set based handling to the SMF during the Path Switch Request procedure (in case of Xn handover) or Handover Resource Allocation procedure (in case of NG handover), the SMF will act as specified in TS 23.501[ System architecture for the 5G System (5GS) ] [3]. If the indication is absent, the SMF infers that PDU Set based handling is not supported by the target NG-RAN node, then the SMF will act as specified in TS 23.501[ System architecture for the 5G System (5GS) ] [3]. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.15.5 |
3,628 | 4.12b Procedures for devices that do not support 5GC NAS over WLAN access 4.12b.1 General | As specified in clause 4.2.8.5 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], devices that do not support 5GC NAS signalling over WLAN access (referred to as "Non-5G-Capable over WLAN" devices, or N5CW devices for short), may access 5GC in a PLMN or an SNPN via a trusted WLAN Access Network that supports a Trusted WLAN Interworking Function (TWIF). The following clause specifies how a N5CW device can be registered to 5GC and how it can send data via a PDU Session. A N5CW device may be 5G-capable over 3GPP access, in which case it is also a 5G UE over 3GPP access. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.12b |
3,629 | – SRS-RSRP-Range | The IE SRS-RSRP-Range specifies the value range used in SRS-RSRP measurements and thresholds. The integer value for SRS-RSRP measurements is according to Table 10.1.22.1.2-1 in TS 38.133[ NR; Requirements for support of radio resource management ] [14]. For thresholds, the actual value is (IE value –140) dBm, except for the IE value 98, in which case the actual value is infinity. SRS-RSRP-Range information element -- ASN1START -- TAG-SRS-RSRP-RANGE-START SRS-RSRP-Range-r16 ::= INTEGER(0..98) -- TAG-SRS-RSRP-RANGE-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,630 | 6.2.29 TSCTSF | The Time Sensitive Communication and Time Synchronization Function (TSCTSF) supports the following functionality: - Associating the time synchronization service request (see clause 5.27.1.8) from the NF consumer to the AF sessions with the PCF (the session between the PCF and TSCTSF). - Controlling time synchronization service request from the NF consumer, (g)PTP-based time distribution and ASTI-based time distribution based on subscription data. The TSCTSF may be pre-configured with one or several PTP instance configurations. For each PTP instance configuration, it may contain: - a reference to the PTP instance configuration. - PTP profile. - PTP domain. - Detecting and reporting time synchronization service status based on NG-RAN and UPF/NW-TT timing synchronization status information and reporting status updates. - Managing the DS-TT and NW-TT via exchange of PMIC and UMIC as described in Annex K. - Detecting availability of 5GS Bridge/Router information (including user plane node ID that applies also for IP type PDU Sessions) as reported by PCF for both Ethernet and IP type PDU Sessions (including the need to (un)subscribe 5GS Bridge/Router information Notification from PCF). - Creating the TSC Assistance Container based on individual traffic pattern parameters from the NEF/AF or DetNet controller and providing it to the PCF. - Determining the Requested PDB by subtracting the UE-DS-TT Residence Time from the Requested 5GS Delay provided by the NEF/AF or DetNet controller and providing the determined Requested PDB to the PCF. - Discovering the AMFs serving the list of TA(s) that comprise the spatial validity condition from the NRF or AMFs serving the UE(s) from the UDM and subscribing to the discovered AMF(s) to receive notifications about presence of the UE in an Area of Interes. - Discovering the AMF(s) serving a UE or a list of TA(s) and subscribing to gNB's node-level timing synchronization status. - Obtaining gNB's and UPF's node-level timing synchronization status information as defined in clause 5.27.1.12. - Determining the spatial validity condition from the requested coverage area by the NEF/AF and enforcing time synchronization service for the requested coverage area. - Support for RAN feedback for BAT offset and adjusted periodicity as defined in clause 5.27.2.5. - In the case of support of integration with IETF Deterministic Networking (as depicted in clauses 4.4.8.4 and 5.28.5), acting as a stateful translator function between a DetNet controller and 5G System Network Functions and Procedures, including the NW-TT. This includes exposing the information about the 5GS router to the DetNet controller and mapping 5GS router configuration parameters provided by the DetNet controller to 5G System parameters. The details are defined in clause 5.28.5. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.2.29 |
3,631 | 6.6.2.2.3 Minimum requirement (network signalled value "NS_06" or “NS_07”) | Additional spectrum emission requirements are signalled by the network to indicate that the UE shall meet an additional requirement for a specific deployment scenario as part of the cell handover/broadcast message. When "NS_06" or “NS_07” is indicated in the cell, the power of any UE emission shall not exceed the levels specified in Table 6.6.2.2.3-1. Table 6.6.2.2.3-1: Additional requirements NOTE: As a general rule, the resolution bandwidth of the measuring equipment should be equal to the measurement bandwidth. However, to improve measurement accuracy, sensitivity and efficiency, the resolution bandwidth may be smaller than the measurement bandwidth. When the resolution bandwidth is smaller than the measurement bandwidth, the result should be integrated over the measurement bandwidth in order to obtain the equivalent noise bandwidth of the measurement bandwidth. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.6.2.2.3 |
3,632 | L.1 Mapping of NAS procedure to RRC establishment cause(Iu mode only) | When MM requests the establishment of an RR connection, the RRC establishment cause used by the MS shall be selected according to the CS NAS procedure as specified in table L.1.1. Table L.1.1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Mapping of CS NAS procedure to establishment cause When MM requests the establishment of an RR connection, if the MS is configured for EAB (see the "ExtendedAccessBarring" leaf of the NAS configuration MO 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]), the MS is not an MS configured to use AC11 – 15 in selected PLMN, the MS is not answering to paging and the RRC Establishment cause is not set to "Emergency call", then the MM shall indicate to the lower layer for the purpose of access control that EAB applies for this request. NOTE 1: void. NOTE 2: EAB override is not supported in the CS domain. When GMM requests the establishment of a PS signalling connection, the RRC establishment cause used by the MS shall be selected according to the PS NAS procedure as specified in Table L.1.2. Table L.1.2/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Mapping of PS NAS procedure to establishment cause NOTE 3: The RRC establishment cause can be used by the network to prioritise the connection establishment request from the MS at high load situations in the network. When GMM requests the establishment of a PS signalling connection, if the MS is configured for EAB (see the "ExtendedAccessBarring" leaf of the NAS configuration MO 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]), the GMM shall indicate to the lower layer for the purpose of access control that EAB applies for this request except for the following cases: - the MS is an MS configured to use AC11 – 15 in selected PLMN; - the MS is answering to paging or a "call-pull-initiated" indication is received from the upper layer (see 3GPP TS 24.174[ Support of multi-device and multi-identity in the IP Multimedia Subsystem (IMS); Stage 3 ] [185]); - the RRC Establishment cause is set to "Emergency call"; - the MS is configured to allow overriding EAB (see the "Override_ExtendedAccessBarring" leaf of the NAS configuration MO 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 receives an indication from the upper layers to override EAB; or - the MS is configured to allow overriding EAB (see the "Override_ExtendedAccessBarring" leaf of the NAS configuration MO 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 already has a PDN connection that was established with EAB override. NOTE 4: void. | 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 | L.1 |
3,633 | 10.5.4.2 Locking shift procedure | The locking shift procedure employs an information element to indicate the new active codeset. The specified codeset remains active until another locking shift information element is encountered which specifies the use of another codeset. For example, codeset 0 is active at the start of message content analysis. If a locking shift to codeset 5 is encountered, the next information elements will be interpreted according to the information element identifiers assigned in codeset 5, until another shift information element is encountered. This procedure is used only to shift to a higher order codeset than the one being left. The locking shift is valid only within that message which contains the locking shift information element. At the start of every message content analysis, the active codeset is codeset 0. The locking shift information element uses the type 1 information element format and coding shown in figure 10.5.85/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.98/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.85/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Locking shift element Table 10.5.98/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Locking shift 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.2 |
3,634 | 5.5.2.1A.1 Reference signal sequence using modulation schemes other than π/2-BPSK | The reference signal sequence for is defined by a cyclic shift of a base sequence according to , where is given by Tables 5.5.2.1A.1-1 and 5.5.2.1A.1-2 for and , respectively. The cyclic shift is derived from higher layer parameters threeTone-CyclicShift and sixTone-CyclicShift, respectively, as defined in Table 5.5.2.1A.1-3. If group hopping is enabled, the base sequence index is given by clause 5.5.2.1A.3. If group hopping is not enabled, the base sequence index is given by - for - for Table 5.5.2.1A.1-1: Definition of for Table 5.5.2.1A.1-2: Definition of for Table 5.5.2.1A.1-3: Definition of | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.5.2.1A.1 |
3,635 | 5.3.4B Data Transport in Control Plane CIoT EPS Optimisation 5.3.4B.1 General | If the UE and MME use the Control Plane CIoT EPS Optimisation, they can transfer data in NAS PDUs including the EPS Bearer Identity of the PDN connection they relate to, for which there is no S1-U bearers established (i.e. when an S1-U bearer is established the UE shall use S1-U to transfer data PDUs). All PDN types are supported. If the UE and the MME support Control Plane CIoT EPS Optimisation, then for SMS transfer and EPC Mobile Originated Location Request (EPC-MO-LR) or EPC Mobile Terminated Location Request (EPC-MT-LR) the Service Request procedures defined in clause 5.3.4 are not used for MO and MT SMS or for EPC-MO-LR and EPC-MT-LR, but instead UE and MME shall be using the Data Transport in Control Plane CIoT EPS Optimisation. This is accomplished by using the NAS transport capabilities of RRC and S1-AP protocols and the data transport of GTP-u tunnels between MME and S-GW and between S-GW and P-GW, or if a Non-IP connection is provided by via the MME with the SCEF, then data transfer occurs as indicated in TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [74]. For IP data, the UE and MME may perform header compression based on ROHC framework IETF RFC 5795 [77]. For uplink IP data, UE implements ROHC compressor, and MME implements the decompressor. For downlink IP data, MME implements the ROHC compressor, and UE implements the decompressor. The uplink and downlink ROHC channels are bound by UE and MME to support feedback. The configurations for the header compression are established during the PDN connection establishment procedure. To minimise potential conflicts between NAS signalling PDUs and NAS Data PDUs, the MME should complete any security related procedures (e.g. Authentication, Security Mode Command, GUTI reallocation) before alerting the HSS, MSC or SGW of the UE's entry into ECM-CONNECTED state, and before commencing downlink transfer of NAS Data PDUs. The priority handling between the EMM/ESM NAS signalling PDUs and NAS Data PDUs is specified in TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [46]. | 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.4B |
3,636 | 8.3.2.4.2 Minimum requirements with Same Cell ID (with multiple NZP CSI-RS resources) | The requirements are specified in Table 8.3.2.4.2-3, with the additional parameters in Tables 8.3.2.4.2-1 and 8.3.2.4.2-2. The purpose of this test is to verify the UE capability of supporting non quasi-colocated antenna ports when the UE receives DCI format 2D in a scenario where the two transmission point share the same Cell ID. In particular the test verifies that the UE, configured with quasi co-location type B, performs correct tracking and compensation of the timing difference between two transmission points, channel parameters estimation and rate matching according to the ‘PDSCH RE Mapping and Quasi-Co-Location Indicator’ (PQI) signalling defined in [6]. In Tables 8.3.2.4.2-1 and 8.3.2.4.2-2, transmission point 1 (TP 1) is the serving cell transmitting PDCCH, synchronization signals and PBCH, and transmission point 2 (TP 2) has same Cell ID as TP 1. Multiple NZP CSI-RS resources and ZP CSI-RS resources are configured. In each sub-frame, DL PDSCH transmission is dynamically switched between 2 TPs with multiple PDSCH RE Mapping and Quasi-Co-Location Indicator configuration (PQI). Configurations of PDSCH RE Mapping and Quasi-Co-Location Indicator and downlink transmission hypothesis are defined in Table 8.3.2.4.2-2. The downlink physical channel setup for TP 1 is according to Table C.3.4-1 and for TP 2 according to Table C.3.4-2. Table 8.3.2.4.2-1: Test Parameters for timing offset compensation with DPS transmission Table 8.3.2.4.2-2: Configurations of PQI and DL transmission hypothesis for each PQI set Table 8.3.2.4.2-3: Performance Requirements for timing offset compensation with DPS transmission | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.3.2.4.2 |
3,637 | 7.6 Split SRB | Split SRB is supported for both SRB1 and SRB2 (split SRB is not supported for SRB0, SRB3, SRB4 and SRB5) in all MR-DC cases. RRC PDUs on split SRB are ciphered and integrity protected using NR PDCP. Split SRB can be configured by the MN in Secondary Node Addition and/or Modification procedure, with SN configuration part provided by the SN. A UE can be configured with both split SRB and SRB3 simultaneously. SRB3 and the SCG leg of split SRB can be independently configured. For the split SRB, the selection of transmission path in downlink depends on network implementation. For uplink, the UE is configured via MN RRC signalling whether to use MCG path or duplicate the transmission on both MCG and SCG. | 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 | 7.6 |
3,638 | 8.9.9.1 Traffic Mapping from IP-layer to Layer-2 | When forwarding IP packets, the IAB-donor-DU performs the traffic mapping from IP-layer to layer-2 as defined in TS 38.340[ NR; Backhaul Adaptation Protocol (BAP) specification ] [22]. The traffic mapping information is configured by the IAB-donor-CU, which contains the IP header information, and the BH information including the BAP routing ID and a list of egress link and BH RLC channel pairs. Multiple traffic mappings can contain the same BAP routing ID and/or list of egress link and BH RLC channel pairs. The traffic mappings can be configured as part of the UE Context Setup or UE Context Modification procedures. They may also be configured via the non-UE-associated BAP Mapping Configuration procedure. NOTE: Implementation must ensure the avoidance of potential race conditions, i.e. no conflicting configurations are concurrently performed using UE-associated and non-UE-associated procedures. The traffic mapping from IP-layer to layer-2 may include IPv6 Flow Label information. For DL F1 or X2 traffic, the IPv6 Flow Label information is set by the IAB-donor-CU or MeNB, respectively. When this traffic is protected via IPsec tunnel mode, the IPv6 Flow Label is set on the inner header by the IAB-donor-CU or MeNB, and the security gateway shall copy the IPv6 Flow Label from the inner IP header to the outer IP header to ensure that the IAB-donor-DU can perform the traffic mapping considering the IPv6 Flow Label. NOTE: Implementation must ensure that IPv6 Flow Label collisions are avoided on the IP backhaul network between security gateway and IAB-donor-DU. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.9.9.1 |
3,639 | 4.23.2 I-SMF selection | For non-roaming or LBO roaming case, the AMF selects an SMF serving the PDU Session as described in clause 4.3.2.2.3. If the service area of the selected SMF does not control UPF that can serve the UE location, the AMF selects an I-SMF as described in clause 5.34.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. After the PDU Session is established, if the selected SMF cannot serve the target DNAI requested by the PCC rule, the SMF issues Nsmf_PDUSession_SMContextStatusNotify to provide the target DNAI information to the AMF. Then AMF selects an I-SMF that serves this target DNAI as described in clause 5.34.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. For home routed roaming case, the AMF selects V-SMF as described in clause 4.3.2.2.3.2 and reselects V-SMF as described in clause 5.34.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. When the delegated discovery is used, the SCP selects the SMF as described in clause 5.34.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] and in Annex E. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.23.2 |
3,640 | 4.22.2.3.3 QoS Support | The general principles for QoS support with ATSSS as described in clause 5.32.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], apply, with the clarifications provided in this clause. With an MA PDU Session associated to a PDN Connection on EPS there may be separate user-plane tunnels between the AN and the PGW-U+UPF, one associated with 3GPP access in EPC and one associated with non-3GPP access in 5GS. As described in clause 4.11.1.1, the PGW-C+SMF maps the 5G QoS information received from PCC to EPS QoS parameters. This mapping is e.g. based on operator configuration and may result in that multiple QoS flows are mapped to a single EPS bearer. The PGW-C+SMF applies the appropriate QoS signalling in each access, e.g. to manage dedicated bearers in the access associated with EPC and QoS flows in the access associated with 5GC. The PGW-C+SMF also provides N4 rules to UPF for performing QoS enforcement and for mapping downlink traffic to appropriate GTP-U tunnels. As described in clause 5.32.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], for a GBR QoS flow, the QoS profile is provided to a single access network at a given time. GBR QoS flows (and associated MBR, GBR) are thus only enforced in either the access associated to EPC or the access associated to 5GC. In order to maintain consistency between QoS information received via AS and NAS layers in each system, the PGW-C+SMF only provides the GBR QoS information to the UE for the access where the GBR traffic is enforced. The UE shall treat the uplink traffic sent via EPC according to the EPS QoS information received in EPC (e.g. UL TFTs) and the uplink traffic sent via 5GC according to the 5G QoS rules received in 5GS. The UE thus need to determine what access to use (3GPP and Non-3GPP) before applying the uplink QoS treatment. The UPF shall treat the downlink traffic according to the N4 rules (QER, etc.) received from PGW-C+SMF. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.22.2.3.3 |
3,641 | 9.9.3.64 IMSI offset | The purpose of the IMSI offset information element is to indicate an IMSI offset value that is used for calculating an alternative IMSI value as specified in 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10] that is used for deriving the paging occasion as specified in 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [21]. The IMSI offset information element is coded as shown in figure 9.9.3.64.1 and table 9.9.3.64.1. The IMSI offset is a type 4 information element with a length of 4 octets. Figure 9.9.3.64.1: IMSI offset information element Table 9.9.3.64.1: IMSI offset information element | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.9.3.64 |
3,642 | 4.23.12.4 Procedures for EPS bearer ID allocation | The EPS Bearer ID allocation procedure, EPS Bearer ID transfer procedure and EPS Bearer ID revocation procedure are perfomed as described for the home-routed roaming case in clause 4.11.1.4, with the following differences: - H-SMF is replaced by SMF. - V-SMF is replaced by I-SMF. - In step 8 of clause 4.11.1.4.1, in addition to home routing roaming scenario, for scenario of deployments topologies with specific SMF Service Areas, if EBI is assigned successfully, the SMF+PGW-C also prepares CN Tunnel Info for each EPS bearer and provides this information to the I-SMF. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.23.12.4 |
3,643 | 5.3.3.2.5 CM-CONNECTED with RRC_INACTIVE state | RRC_INACTIVE state applies to NG-RAN. UE support for RRC_INACTIVE state is defined in TS 38.306[ NR; User Equipment (UE) radio access capabilities ] [69] for NR and TS 36.306[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio access capabilities ] [70] for E-UTRA connected to 5GC. RRC_INACTIVE is not supported by NB-IoT connected to 5GC. The AMF shall provide assistance information to the NG-RAN, to assist the NG-RAN's decision whether the UE can be sent to RRC_INACTIVE state except due to some exceptional cases such as: - PLMN (or AMF set) does not support RRC_INACTIVE; - The UE needs to be kept in CM-CONNECTED State (e.g. for tracking). The "RRC Inactive Assistance Information" includes: - UE specific DRX values; - UE specific extended idle mode DRX values (cycle length and Paging Time Window length); - The Registration Area provided to the UE; - Periodic Registration Update timer; - If the AMF has enabled MICO mode for the UE, an indication that the UE is in MICO mode; - Information from the UE identifier, as defined in TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [50] for NR and TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [52] for E-UTRA connected to 5GC, that allows the RAN to calculate the UE's RAN paging occasions; - An indication that Paging Cause Indication for Voice Service is supported; - AMF PEIPS Assistance Information (see clause 5.4.12.2) for paging a UE in CM-CONNECTED with RRC_INACTIVE state over NR as defined in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27]; - CN based MT communication handling support indication for RRC_INACATIVE state (see clause 5.31.7.2.1). The RRC Inactive Assistance Information mentioned above is provided by the AMF during N2 activation with the (new) serving NG-RAN node (i.e. during Registration, Service Request, Handover) to assist the NG RAN's decision whether the UE can be sent to RRC_INACTIVE state. If the AMF allocates a new Registration Area to the UE, the AMF should update the NG-RAN with the new Registration Area by sending the RRC Inactive Assistance Information accordingly. The Paging Cause Indication for Voice Service is used to assist NG RAN to perform RAN based paging. RRC_INACTIVE state is part of RRC state machine, and it is up to the RAN to determine the conditions to enter RRC_INACTIVE state. If any of the parameters included in the RRC Inactive Assistance Information changes as the result of NAS procedure, the AMF shall update the RRC Inactive Assistance Information to the NG-RAN node. When the UE is in CM-CONNECTED state, if the AMF has provided RRC Inactive assistance information, the RAN node may decide to move a UE to CM-CONNECTED with RRC_INACTIVE state. The state and "endpoints" (in the case of Dual Connectivity configuration) of the N2 and N3 reference points are not changed by the UE entering CM-CONNECTED with RRC_INACTIVE state. A UE in RRC_INACTIVE state is aware of the RAN Notification area and periodic RAN Notification Area Update timer. The 5GC network is not aware of the UE transitions between CM-CONNECTED with RRC_CONNECTED and CM-CONNECTED with RRC_INACTIVE state, unless the 5GC network is notified via N2 notification procedure in clause 4.8.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. At transition into CM-CONNECTED with RRC_INACTIVE state, the NG-RAN configures the UE with a periodic RAN Notification Area Update timer taking into account the value of the Periodic Registration Update timer value indicated in the RRC Inactive Assistance Information, and uses a guard timer with a value longer than the RAN Notification Area Update timer value provided to the UE. If the periodic RAN Notification Area Update guard timer expires in NG-RAN, the NG-RAN shall initiate AN Release procedure as specified in clause 4.2.6 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. When the UE is in CM-CONNECTED with RRC_INACTIVE state, the UE performs PLMN selection procedures as defined in TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [17] and TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]. When the UE is CM-CONNECTED with RRC_INACTIVE state, the UE may resume the RRC Connection due to: - Uplink data pending; - Mobile initiated NAS signalling procedure; - As a response to RAN paging; - Notifying the network that it has left the RAN Notification Area; - Upon periodic RAN Notification Area Update timer expiration. If the UE resumes the connection in a different NG-RAN node within the same PLMN or equivalent PLMN or within the same SNPN or equivalent SNPN, the UE AS context is retrieved from the old NG-RAN node and a procedure is triggered towards the CN (see clause 4.8.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]). NOTE 1: With Dual Connectivity configuration if the UE resumes the RRC connection in the Master RAN node, the Secondary RAN node configuration is defined in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27]. If the RAN paging procedure applying DRX or eDRX value no longer than 10.24s, as defined in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27], is not successful in establishing contact with the UE the procedure shall be handled by the network as follows: - If NG-RAN has at least one pending NAS PDU for transmission, the RAN node shall initiate the AN Release procedure (see clause 4.2.6 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]) to move the UE CM state in the AMF to CM-IDLE state and indicate to the AMF the NAS non-delivery. - If NG RAN has only pending user plane data for transmission, the NG-RAN node may keep the N2 connection active or initiate the AN Release procedure (see clause 4.2.6 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]) based on local configuration in NG-RAN. NOTE 2: The user plane data which triggers the RAN paging can be lost, e.g. in the case of RAN paging failure. If the RAN paging procedure applying eDRX value longer than 10.24s, as defined in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27], has not requested the CN based mobile terminated (MT) communication handling as described in clause 5.31.7.2.1 and is not successful in establishing contact with the UE after paging the UE, the procedure shall be handled by network as follows: - If NG-RAN has at least one pending NAS PDU for transmission, the RAN node shall initiate the AN Release procedure (see clause 4.2.6 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]) to move the UE CM state in the AMF to CM-IDLE state and indicate to the AMF the NAS non-delivery. - If NG-RAN has only pending user plane data for transmission, the NG-RAN node may keep the N2 connection active and based on implementation send indication to the CN requesting the CN based mobile terminated (MT) communication handling as described in clause 5.31.7.2.1, or initiate the AN Release procedure (see clause 4.2.6 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]) based on local configuration in NG-RAN. NOTE 3: The user plane data which triggers the RAN paging can be lost, e.g. in the case of RAN paging failure. If a UE in CM-CONNECTED with RRC_INACTIVE state performs cell selection to GERAN/UTRAN/E-UTRAN, it shall follow idle mode procedures of the selected RAT as specified in clause 5.17. In addition, a UE in CM-CONNECTED state with RRC_INACTIVE state shall enter CM-IDLE state and initiates the NAS signalling recovery (see TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]) in the following cases: - If RRC resume procedure fails, If the UE receives Core Network paging, - If the periodic RAN Notification Area Update timer expires and the UE cannot successfully resume the RRC Connection, - In any other failure scenario that cannot be resolved in RRC_INACTIVE state and requires the UE to move to CM-IDLE state. When a UE is in CM-CONNECTED with RRC_INACTIVE state, and a trigger to change the UE's NG-RAN or E-UTRAN UE Radio Capability information happens, the UE shall move to CM-IDLE state and initiate the procedure for updating UE Radio Capability defined in clause 5.4.4.1. (For specific requirements for a UE operating in dual-registration mode see clause 5.17.2.1) When UE is in CM-CONNECTED with RRC_INACTIVE state, if RAN has received Location Reporting Control message from AMF with the Reporting Type indicating single stand-alone report or continuously reporting whenever the UE changes the cell, the RAN shall perform location reporting as specified in clause 4.10 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. When the UE is CM-CONNECTED with RRC_INACTIVE state. If the AMF receives Nudm_UECM_DeregistrationNotification from UDM, the AMF shall initiate AN Release procedure as specified in clause 4.2.6 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. When UE is in CM-CONNECTED with RRC_INACTIVE state, if RAN has received Location Reporting Control message from AMF with the Reporting Type of the Area Of Interest based reporting, the RAN shall send a Location Report message to AMF including UE presence in the Area Of Interest (i.e. IN, OUT, or UNKNOWN) and the UE's last known location with time stamp. When the UE is in CM-CONNECTED with RRC_INACTIVE state, if the old NG-RAN node that sends the UE into RRC_INACTIVE state receives the downlink N2 signalling, it initiates the RAN paging as defined in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27]. If the UE resumes the RRC Connection towards a different NG-RAN node, the old NG-RAN node includes the "UE Context Transfer" indication into a response container to the NF (e.g. AMF or SMF) that generates such N2 downlink signalling. Then the NF shall reattempt the same procedure when the path switch from the old NG-RAN node to the new NG-RAN node is complete. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.3.3.2.5 |
3,644 | 10.4 Message Type | The message type IE and its use are defined in 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [20]. Tables 10.3/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] , 10.4/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] , and 10.4a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] define the value part of the message type IE used in the Mobility Management protocol, the Call Control protocol, and Session management protocol. Table 10.2/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Message types for Mobility Management NOTE: This value was allocated but never used in earlier phases of the protocol. When the radio connection started with a core network node of earlier than R99, bit 8 shall be set to 0 and bit 7 is reserved for the send sequence number in messages sent from the mobile station. In messages sent from the network, bits 7 and 8 are coded with a "0". See 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [20]. When the radio connection started with a core network node of R'99 or later, bits 7 and 8 are reserved for the send sequence number in messages sent from the mobile station. In messages sent from the network, bits 7 and 8 are coded with a "0". See 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [20]. Table 10.3/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Message types for Call Control and call related SS messages 1): When used, the message type is defined in the following octet(s), according to the national specification. When the radio connection started with a core network node of earlier than R99, bit 8 shall be set to 0 and bit 7 is reserved for the send sequence number in messages sent from the mobile station. In messages sent from the network, bits 7 and 8 are coded with a "0". See 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [20]. When the radio connection started with a core network node of R'99 or later, bits 7 and 8 are reserved for the send sequence number in messages sent from the mobile station. In messages sent from the network, bits 7 and 8 are coded with a "0". See 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [20]. Table 10.4/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Message types for GPRS mobility management Table 10.4a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Message types for GPRS session management | 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.4 |
3,645 | 8.2.1.3 Inter-gNB-DU Conditional Handover or Conditional PSCell Change or subsequent CPAC | This procedure is used for the case when the UE moves from one gNB-DU to another gNB-DU within the same gNB-CU during NR operation for conditional handover or conditional PSCell change or subsequent CPAC. Figure 8.2.1.3-1 shows the inter-gNB-DU conditional mobility procedure for intra-NR. Figure 8.2.1.3-1: Inter-gNB-DU Conditional Handover or Conditional PSCell Change or subsequent CPAC for intra-NR 1-2. The steps 1-2 are as defined in clause 8.2.1.1. 3. 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 HandoverPreparationInformation (conditional handover) or a CG-ConfigInfo (conditional PSCell change or subsequent CPAC). 4. The candidate gNB-DU responds to 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. 5. The gNB-CU sends a DL RRC MESSAGE TRANSFER message to the source gNB-DU, which includes a generated RRCReconfiguration message. 6. The step 6 is as defined in clause 8.2.1.1. 7-8. The UE responds to the source gNB-DU with an RRCReconfigurationComplete message, for which the source gNB-DU forwards to the gNB-CU via an UL RRC MESSAGE TRANSFER message. 9. An execution condition to trigger initiation of conditional handover or conditional PSCell change or subsequent CPAC is fulfilled. 10. A 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. 11-12. The steps 11-12 are as defined in steps 9-10 in clause 8.2.1.1. 13. 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 also 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. NOTE: The step 13 may happen before step 12, 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 handover or conditional PSCell change for the UE. 14. The source gNB-DU responds to the gNB-CU with the UE CONTEXT MODIFICATION RESPONSE message. 15 -16. The steps 15-16 are as defined in steps 11-12 in clause 8.2.1.1. The step 15~16 shall not happen if all of the PSCells in the source gNB-DU remain configured as the candidate PSCell(s) in the subsequent CPAC. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.2.1.3 |
3,646 | 6.3.5A.3.1 Minimum requirements | For inter-band carrier aggregation with uplink assigned to two E-UTRA bands, the aggregate power tolerance is specified on each component carrier exceed the minimum output power as defined in subclause 6.3.2A and the total power is limited by maximum output power as defined in subclause 6.2.2A. The requirements defined in Table 6.3.5.3.1-1 shall apply on each component carrier with all component carriers active. The requirements can be tested by time aligning any transmission gaps on both the component carriers. For intra-band contiguous carrier aggregation bandwidth class B, C and D and intra-band non-contiguous carrier aggregation, the aggregate power tolerance per component carrier is given in Table 6.3.5.3.1-1 with either simultaneous PUSCH or simultaneous PUCCH-PUSCH (if supported by the UE) configured. The average power per PRB shall be aligned across both assigned carriers before the start of the test. The requirement can be tested with the transmission gaps time aligned between component carriers. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.3.5A.3.1 |
3,647 | 15.2 Mutual authentication | If a management service consumer resides outside the 3GPP operator’s trust domain, mutual authentication shall be performed between the management service consumer and the management service producer using TLS. TLS shall follow, the profile given in TS 33.210[ Network Domain Security (NDS); IP network layer security ] [3], clause 6.2 and either 1) the client and server certificates with the profiles given in 3GPP TS 33.310[ Network Domain Security (NDS); Authentication Framework (AF) ] [5], clause 6.1.3a or 2) pre-shared keys following RFC 5489for TLS 1.2 and RFC 8446 [60] for TLS 1.3. The structure of the PKI used for the certificates is out of scope of the present document. The identities in the end entity certificates shall be used for authentication and policy checks. The key distribution of pre-shared keys for TLS is up to the operator’s security policy and out of scope of the present document. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 15.2 |
3,648 | 5.2.27.3.6 Ntsctsf_QoSandTSCAssistance_Subscribe operation | Service operation name: Ntsctsf_QoSandTSCAssistance_Subscribe Description: The consumer requests the network to subscribe to receive an event about the AF session with requested QoS or the AF session with requested QoS including Alternative Service Requirements. Inputs, Required: Notification Target Address, Notification Correlation ID, (Set of) Event ID(s) as specified in clause 6.1.3.18 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. Inputs, Optional: None. Outputs, Required: Subscription Correlation Id, result. Output (optional): None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.27.3.6 |
3,649 | 5.15.11.5a Support of Network Slice Admission Control in 5GS for maximum number of UEs with at least one PDU Session/PDN Connection | When EPS counting is required for a network slice and NSACF is configured with maximum number of UEs with at least one PDU Session/PDN Connection, the NSACF keeps track of the current number of UEs with at least one PDU session/PDN connection established on a network slice to ensure it does not exceed the maximum configured number. To support the NSAC for maximum number of UEs with at least one PDU Session/PDN Connection, the SMF+PGW-C may be configured with one of the following options: - Option 1: Triggering an Nnsacf_NSAC_NumOfUEsUpdate_Request to NSACF for NSAC for maximum number of UEs when the UE establishes first PDU Session/PDN connection associated with the network slice in the SMF+PGW-C, or when the last PDU Session/PDN connection associated with the network slice is released. The NSACF performs admission control as described in clause 5.15.11.5 and the number of registered UE is replaced with number of UE with at least one PDU session/PDN connection. Also, if the maximum number of UEs with at least one PDU Session/PDN connection has already been reached and SMF+PGW-C receives the rejection from NSACF, unless operator policy implements a different action, the SMF+PGW-C rejects the PDU Session/PDN connection indicating the cause being the number of UEs in the network slice has been exceeded. The AMF is not configured for this S-NSSAI to be subject to NSAC; or - Option 2: Triggering an Nnsacf_NSAC_NumOfPDUsUpdate_Request as described in clause 5.15.11.5 to NSACF and the NSACF performs admission control for the number of UEs with at least one PDU Session/PDN connection as follows: - The NSACF supports handling both for the number of UEs with at least one PDU Session/PDN Connection and number of PDU session for the S-NSSAI that is subject to EPC interworking and NSAC. In this case the AMF is not configured for this S-NSSAI to be subject to NSAC. As an optimization option, the SMF+PGW-C can be configured not to trigger the Nnsacf_NSAC_NumOfUEsUpdate_Request to NSACF. - When the NSACF receives request to increase the current number of PDU Session/PDN Connection established for the network slice, the NSACF checks whether this is the first PDU Session/PDN Connection associated with the network slice. If this is the first PDU Session/PDN Connection associated with the network slice the NSACF checks whether the maximum number of UEs with at least one PDU Session/PDN Connection has been reached. If the maximum number has not been reached then the NSACF increases the number of UE with at least one PDU session/PDN connection and add an entry for UE ID. If the maximum number of UEs has already been reached, unless operator policy implements a different action, the SMF+PGW-C rejects the PDU Session/PDN connection indicating the cause being the number of UEs in the network slice has been exceeded. - When the NSACF receives request to decrease the current number of PDU Session/PDN Connection established for the network slice, the NSACF locates the UE entry, checks whether this is the last PDU Session/PDN Connection associated with the network slice for the UE. If it is the last PDU Session/PDN Connection the NSACF decreases the number of UE with at least one PDU session/PDN connection and remove the associated UE entry. NOTE 1: A PLMN can deploy one of the above two options for a slice when EPS counting is required for a network slice and NSACF is configured with maximum number of UEs with at least one PDU Session/PDN Connection. NSACF is configured with the information of whether the NSAC for number of UEs with at least one PDU session/PDN connection is based on Option1 or Option 2. In both options, the SMF+PGW-C provides the Access Type to the NSACF when triggering a request to increase or decrease or update the number of UEs with at least one PDU Session/PDN Connection and/or the number of PDU Sessions for an S-NSSAI. In the case of roaming, same mechanisms in clause 5.15.11.3 are used and number of registered UE is replaced with number of UE with at least one PDU Session/PDN Connection. For home routed PDU Session/PDN Connection only HPLMN admission mode can be used in this case. If hierarchical NSAC architecture is deployed, when the local maximum number or local threshold is reached the NSAC may interact with the Primary NSACF before it returns the response back to the SMF+PGW-C. For more details on handling at the NSACF and Primary NSACF see clause 5.15.11.1.2. NOTE 2: When NSAC for number of UEs with at least one PDU session or one PDN connection is used, the session continuity is guaranteed at inter-system mobility as the admission is granted during the establishment of the PDU Session/PDN Connection. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.15.11.5a |
3,650 | 5.10.2 Scenario | The UAV controller and UAV have been switched on to serve remote inspection mission for power line infrastructure. The MNO initiates network assisted UAS discovery procedure. After successful Network assisted UAS discovery, the UTM can then start to track the UAS and the 3GPP network enables the 3GPP connectivity to assist the UAS operation. The UAV controller requests the 3GPP network to establish a data connection which can provide low latency and reliable connectivity for transporting UAV commands and receiving UAV responses. The 3GPP network establishes a route via control plane path or data plane for the UAV and the UAV controller, which can be anchored in the same RAN node, routed between two different RAN nodes that serve UAV and UAV controller, respectively, control plane or user plane gateway function, or a local DN at the edge. The UAV starts to record the real-time video and transport it to the UAV controller using the 3GPP connectivity via 3GPP network. | 3GPP TS 22.825 | Study on Remote Identification of Unmanned Aerial Systems (UAS) | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 5.10.2 |
3,651 | 8.2.1.4.3A Minimum Requirement Multi-Layer Spatial Multiplexing 4 Tx Antenna Port for dual connectivity | For dual connectivity the requirements are specified in Table 8.2.1.4.3A-3 for 2DL CCs and Table 8.2.1.4.3A-4 for 3DL CCs, based on single carrier requirement specified in Table 8.2.1.4.3A-2, with the addition of the parameters in Table 8.2.1.4.3A-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-two performance with wideband and frequency selective precoding by using dual connectivity transmission. Table 8.2.1.4.3A-1: Test Parameters for Multi-Layer Spatial Multiplexing (FRC) for dual connectivity Table 8.2.1.4.3A-2: Single carrier performance for multiple dual connectivity configurations Table 8.2.1.4.3A-3: Minimum performance Multi-Layer Spatial Multiplexing (FRC) for dual connectivity with 2 DL CCs Table 8.2.1.4.3A-4: Minimum performance Multi-Layer Spatial Multiplexing (FRC) for dual connectivity with 3DL 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.4.3A |
3,652 | O.4.3 UE capability version | The purpose of the UE capability version is to inform the receiving MS that the capability of the sending MS has changed since the last UE capability exchange (see 3GPP TS 24.279[ Combining Circuit Switched (CS) and IP Multimedia Subsystem (IMS) services; Stage 3 ] [116]). The UE capability version information element is coded as shown in figure O.4/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table O.4/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The UE capability version has the form UCV-XX, where XX is a 2-digit hexadecimal number. Only the hexadecimal number XX is coded in the UE capability version information element. The UE capability version information element is coded as shown in figure O.4/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table O.4/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The UE capability version is a type 3 information element with 2 octets length. Figure O.4/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : UE capability version Table O.4/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : UE capability version | 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 | O.4.3 |
3,653 | 6.6.3 Spurious emissions | Spurious emissions are emissions which are caused by unwanted transmitter effects such as harmonics emission, parasitic emissions, intermodulation products and frequency conversion products, but exclude out of band emissions unless otherwise stated. The spurious emission limits are specified in terms of general requirements inline with SM.329 [2] and E-UTRA operating band requirement to address UE co-existence. To improve measurement accuracy, sensitivity and efficiency, the resolution bandwidth may be smaller than the measurement bandwidth. When the resolution bandwidth is smaller than the measurement bandwidth, the result should be integrated over the measurement bandwidth in order to obtain the equivalent noise bandwidth of the measurement bandwidth. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.6.3 |
3,654 | 7.3.1 Minimum requirements (QPSK) | The throughput shall be ≥ 95% of the maximum throughput of the reference measurement channels as specified in Annexes A.2.2, A.2.3 and A.3.2 (with one sided dynamic OCNG Pattern OP.1 FDD/TDD for the DL-signal as described in Annex A.5.1.1/A.5.2.1) with parameters specified in Table 7.3.1-1 and Table 7.3.1-2 Table 7.3.1-1: Reference sensitivity QPSK PREFSENS For UE(s) equipped with 4 antenna ports, the minimum requirement for reference sensitivity in Table 7.3.1-1 shall be modified by the amount given in ΔRIB,4R in Table 7.3.1-1a for the applicable E-UTRA bands. Table 7.3.1-1a: ΔRIB,4R For UE(s) equipped with 8 antenna ports, the minimum requirement for reference sensitivity in Table 7.3.1-1 shall be modified by the amount given in ΔRIB,8R in Table 7.3.1-1aa for the applicable E-UTRA bands. Table 7.3.1-1aa: ΔRIB,8R For UE(s) supporting power class 1 in any of the E-UTRA bands given in table 7.3.1-1b, the following exceptions due to the high power leakage or blocking issue shall apply. The throughput shall be ≥ 95% of the maximum throughput of the reference measurement channels as specified in Annexes A.2.2, A.2.3 and A.3.2 (with one sided dynamic OCNG Pattern OP.1 FDD/TDD for the DL-signal as described in Annex A.5.1.1/A.5.2.1) with parameters specified in Table 7.3.1-1b and Table 7.3.1-2. Table 7.3.1-1b: Reference sensitivity for power class 1 QPSK PREFSENS (Exception due to high power issue) The reference receive sensitivity (REFSENS) requirement specified in Table 7.3.1-1 (two antenna ports) and Table 7.3.1-1a (four antenna ports) shall be met for an uplink transmission bandwidth less than or equal to that specified in Table 7.3.1-2. NOTE: Table 7.3.1-2 is intended for conformance tests and does not necessarily reflect the operational conditions of the network, where the number of uplink and downlink allocated resource blocks will be practically constrained by other factors. Typical receiver sensitivity performance with HARQ retransmission enabled and using a residual BLER metric relevant for e.g. Speech Services is given in the Annex G (informative).For the UE which supports inter-band carrier aggregation configuration with the uplink in one or two E-UTRA bands, the minimum requirement for reference sensitivity in Table 7.3.1-1 and Table 7.3.1-1a shall be increased by the amount given in ΔRIB,c in Table 7.3.1-1A, Table 7.3.1-1B and Table 7.3.1-1C for the applicable E-UTRA bands where unless otherwise stated, the same ΔRIB,c is applicable to E-UTRA band(s) part for CA configurations which have the same E-UTRA operating band combination. Table 7.3.1-1A: ΔRIB,c (two bands) NOTE: To meet the RIB,c requirements for CA_20A-28A state-of-the-art filter combiner technology is needed. Table 7.3.1-1B: ΔRIB,c (three bands) Table 7.3.1-1C: ΔRIB,c (four bands) Table 7.3.1-1D: ΔRIB,c (five bands) NOTE : The above additional tolerances do not apply to supported UTRA operating bands with frequency range below 1 GHz that correspond to the E-UTRA operating bands that belong to the supported inter-band carrier aggregation configurations when such bands are belonging only to band combination(s) where one band is <1GHz and other bands are >1.7GHz and there is no harmonic relationship between the low band UL and high band DL. Otherwise the above additional tolerances also apply to supported UTRA operating bands that correspond to the E-UTRA operating bands that belong to the supported inter-band carrier aggregation configurations. Table 7.3.1-1E: ΔRIB,c (six bands) Table 7.3.1-2: Uplink configuration for reference sensitivity Unless given by Table 7.3.1-3, the minimum requirements specified in Tables 7.3.1-1, 7.3.1-1a and 7.3.1-2 shall be verified with the network signalling value NS_01 (Table 6.2.4-1) configured. Table 7.3.1-3: Network signalling value for reference sensitivity | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 7.3.1 |
3,655 | 4.12 Access traffic steering, switching and splitting (ATSSS) | The ATSSS feature is an optional feature that may be supported by the UE and the 5GCN. The ATSSS feature enables a multi-access PDU connectivity service, which can exchange PDUs between the UE and a data network by simultaneously using one 3GPP access network and one non-3GPP access network. The multi-access PDU connectivity service is realized by establishing a multi-access PDU session, i.e. a PDU session that can have user-plane resources on two access networks. NOTE: MA PDU session is not applicable for CIoT 5GS optimization in this release of specification. The UE can request an MA PDU session when the UE is registered via both 3GPP and non-3GPP accesses, or when the UE is registered via one access only. The MA PDU session management is performed based on the PDU session management procedures. The detailed description of the procedures for ATSSS between the UE and the network across one 3GPP access network and one non-3GPP access network are specified in 3GPP TS 24.193[ 5G System;Access Traffic Steering, Switching and Splitting (ATSSS); Stage 3 ] [13B]. | 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.12 |
3,656 | 4.23.5.2 PDU Session Release procedure | For the non roaming or LBO roaming case, the procedure defined in clause 4.3.4.3 (UE or network requested PDU Session Release for Home-routed Roaming) is used to release the PDU Session, with the V-SMF and V-UPF are replaced by I-SMF and I-UPF and H-SMF and H-UPF are replaced by SMF and UPF(PSA) respectively. Also if the ULCL/BP is included in the data path, in step 1 the I-SMF releases the local UPF (PSA) and includes N4 information in the Nsmf_PDUSession_Release or Nsmf_PDUSession_Update Request request respectively. For AMF triggers PDU Session Release procedure in Registration procedure (see step 17 of clause 4.2.2.2.2) and Deregistration procedure (see step 2 of clause 4.2.2.3.2), if I-SMF is used for the session, the AMF invokes PDU Session Release operation towards the I-SMF, then I-SMF releases the PDU Session towards SMF. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.23.5.2 |
3,657 | – ClockQualityMetrics | The IE ClockQualityMetrics is used to configure RAN timing synchronisation status information as specified in TS 38.473[ NG-RAN; F1 Application Protocol (F1AP) ] [36] ClockQualityMetrics information element -- ASN1START -- TAG-CLOCKQUALITYMETRICS-START ClockQualityMetrics-r18 ::= SEQUENCE { synchronisationState-r18 ENUMERATED {locked, holdover, freerun, spare1} OPTIONAL, -- Need N tracebilityToUTC-r18 ENUMERATED {true, false} OPTIONAL, -- Need N tracebilityToGNSS-r18 ENUMERATED {true, false} OPTIONAL, -- Need N clockFrequencyStability-r18 BIT STRING (SIZE(16)) OPTIONAL, -- Need N clockAccuracy-r18 CHOICE { value INTEGER (1..40000000), index INTEGER (32..47) } OPTIONAL, -- Need N parentTimeSource-r18 ENUMERATED {syncE, pTP, gNSS,atomicClock, terrestialRadio, serialTimeCode, nTP, handset, other, spare7, spare6, spare5, spare4, spare3, spare2, spare1} OPTIONAL, -- Need N ... } -- TAG-CLOCKQUALITYMETRICS-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,658 | 6.1.3.2.0 5G AKA | 5G AKA enhances EPS AKA [10] by providing the home network with proof of successful authentication of the UE from the visited network. The proof is sent by the visited network in an Authentication Confirmation message. The selection of using 5G AKA is described in sub-clause 6.1.2 of the present document. NOTE 1: 5G AKA does not support requesting multiple 5G AVs, neither the SEAF pre-fetching 5G AVs from the home network for future use. Figure 6.1.3.2-1: Authentication procedure for 5G AKA The authentication procedure for 5G AKA works as follows, cf. also Figure 6.1.3.2-1: 1. For each Nudm_Authenticate_Get Request, the UDM/ARPF shall create a 5G HE AV. The UDM/ARPF does this by generating an AV with the Authentication Management Field (AMF) separation bit set to "1" as defined in TS 33.102[ 3G security; Security architecture ] [9]. The UDM/ARPF shall then derive KAUSF (as per Annex A.2) and calculate XRES* (as per Annex A.4). Finally, the UDM/ARPF shall create a 5G HE AV from RAND, AUTN, XRES*, and KAUSF. 2. The UDM shall then return the 5G HE AV to the AUSF together with an indication that the 5G HE AV is to be used for 5G AKA in a Nudm_UEAuthentication_Get Response. In case SUCI was included in the Nudm_UEAuthentication_Get Request, UDM will include the SUPI in the Nudm_UEAuthentication_Get Response after deconcealment of SUCI by SIDF. If a subscriber has an AKMA subscription, the UDM shall include the AKMA indication and Routing indicator in the Nudm_UEAuthentication_Get Response. 3. The AUSF shall store the XRES* temporarily together with the received SUCI or SUPI. 4. The AUSF shall then generate the 5G AV from the 5G HE AV received from the UDM/ARPF by computing the HXRES* from XRES* (according to Annex A.5) and KSEAF from KAUSF (according to Annex A.6), and replacing the XRES* with the HXRES* and KAUSF with KSEAF in the 5G HE AV. 5. The AUSF shall then remove the KSEAF and return the 5G SE AV (RAND, AUTN, HXRES*) to the SEAF in a Nausf_UEAuthentication_UEAuthentication Response. 6. The SEAF shall send RAND, AUTN to the UE in a NAS message Authentication Request. This message shall also include the ngKSI that will be used by the UE and AMF to identify the KAMF and the partial native security context that is created if the authentication is successful. This message shall also include the ABBA parameter. The SEAF shall set the ABBA parameter as defined in Annex A.7.1. The ME shall forward the RAND and AUTN received in NAS message Authentication Request to the USIM. NOTE 2: The ABBA parameter is included to enable the bidding down protection of security features. 7. At receipt of the RAND and AUTN, the USIM shall verify the freshness of the received values by checking whether AUTN can be accepted as described in TS 33.102[ 3G security; Security architecture ] [9]. If so, the USIM computes a response RES. The USIM shall return RES, CK, IK to the ME. If the USIM computes a Kc (i.e. GPRS Kc) from CK and IK using conversion function c3 as described in TS 33.102[ 3G security; Security architecture ] [9], and sends it to the ME, then the ME shall ignore such GPRS Kc and not store the GPRS Kc on USIM or in ME. The ME then shall compute RES* from RES according to Annex A.4. The ME shall calculate KAUSF from CK||IK according to clause A.2. The ME shall calculate KSEAF from KAUSF according to clause A.6. An ME accessing 5G shall check during authentication that the "separation bit" in the AMF field of AUTN is set to 1. The "separation bit" is bit 0 of the AMF field of AUTN. NOTE 3: This separation bit in the AMF field of AUTN cannot be used anymore for operator specific purposes as described by TS 33.102[ 3G security; Security architecture ] [9], Annex F. 8. The UE shall return RES* to the SEAF in a NAS message Authentication Response. 9. The SEAF shall then compute HRES* from RES* according to Annex A.5, and the SEAF shall compare HRES* and HXRES*. If they coincide, the SEAF shall consider the authentication successful from the serving network point of view. If not, the SEAF proceed as described in sub-clause 6.1.3.2.2. If the UE is not reached, and the RES* is never received by the SEAF, the SEAF shall consider authentication as failed, and indicate a failure to the AUSF. 10. The SEAF shall send RES*, as received from the UE, in a Nausf_UEAuthentication_Authenticate Request message to the AUSF. 11. When the AUSF receives as authentication confirmation the Nausf_UEAuthentication_Authenticate Request message including a RES* it may verify whether the 5G AV has expired. If the 5G AV has expired, the AUSF may consider the authentication as unsuccessful from the home network point of view. Upon successful authentication, the AUSF stores the KAUSF based on the home network operator's policy according to clause 6.1.1.1. AUSF shall compare the received RES* with the stored XRES*. If the RES* and XRES* are equal, the AUSF shall consider the authentication as successful from the home network point of view. AUSF shall inform UDM about the authentication result (see sub-clause 6.1.4 of the present document for linking with the authentication confirmation). NOTE 4: It is left to implementation to temporarily store the KAUSF received in step 2 in AUSF until the RES* verification is done successfully (i.e., at step 11). 12. The AUSF shall indicate to the SEAF in the Nausf_UEAuthentication_Authenticate Response whether the authentication was successful or not from the home network point of view. If the authentication was successful, the KSEAF shall be sent to the SEAF in the Nausf_UEAuthentication_Authenticate Response. In case the AUSF received a SUCI from the SEAF in the authentication request (see sub-clause 6.1.2 of the present document), and if the authentication was successful, then the AUSF shall also include the SUPI in the Nausf_UEAuthentication_Authenticate Response message. If the authentication was successful, the key KSEAF received in the Nausf_UEAuthentication_Authenticate Response message shall become the anchor key in the sense of the key hierarchy as specified in sub-clause 6.2 of the present document. Then the SEAF shall derive the KAMF from the KSEAF, the ABBA parameter and the SUPI according to Annex A.7. The SEAF shall provide the ngKSI and the KAMF to the AMF. If the AUSF indicates that the authentication was successful from the home network point of view, then the AMF shall initiate NAS security mode command procedure (see clause 6.7.2) with the UE, to take the newly generated partial native 5G NAS security context into use. Upon receiving the valid NAS Security Mode Command message from the AMF, the UE shall consider the performed primary authentication as successful. If a SUCI was used for this authentication, then the SEAF shall only provide ngKSI and KAMF to the AMF after it has received the Nausf_UEAuthentication_Authenticate Response message containing KSEAF and SUPI; no communication services will be provided to the UE until the SUPI is known to the serving network. The further steps taken by the AUSF after the authentication procedure are described in sub-clause 6.1.4 of the present document. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.1.3.2.0 |
3,659 | 5.4.5.2.5 Abnormal cases on the network side | The following abnormal cases in AMF are identified: a) If the Payload container type IE is set to "N1 SM information" and: 1) if the Old PDU session ID IE is not included in the UL NAS TRANSPORT message, the AMF does not have a PDU session routing context for the PDU session ID and the UE, the Request type IE is set to "initial request" or "MA PDU request", and the SMF selection fails, then the AMF shall send back to the UE the 5GSM message which was not forwarded as specified in subclause 5.4.5.3.1 case e) or case f); 2) if the Old PDU session ID IE is included in the UL NAS TRANSPORT message, the AMF has a PDU session routing context for the old PDU session ID and the UE and does not have a PDU session routing context for the PDU session ID and the UE, the Request type IE is set to "initial request", the AMF received a reallocation requested indication from the SMF indicating that the SMF is to be reallocated, and the SMF selection fails, then the AMF shall send back to the UE the 5GSM message which was not forwarded as specified in subclause 5.4.5.3.1 case e) or case f); 3) if the AMF does not have a PDU session routing context for the PDU session ID and the UE, the Request type IE is set to "existing PDU session" or "MA PDU request", and the user's subscription context obtained from the UDM does not contain an SMF ID for the PDU session ID matching the PDU session ID received from the UE or for the DNN matching the DNN received from the UE such that the SMF ID includes a PLMN identity corresponding to the UE's HPLMN or the current PLMN or the PLMN ID part of the current SNPN, then the AMF may send back to the UE the 5GSM message which was not forwarded as specified in subclause 5.4.5.3.1 case e) or case f). 4) if the Old PDU session ID IE is included in the UL NAS TRANSPORT message, and the AMF has a PDU session routing context for the old PDU session ID and the UE and does not have a PDU session routing context for the PDU session ID and the UE, the Request type IE is set to "initial request" and the AMF has not received a reallocation requested indication, the AMF should select an SMF with following handlings: i) if the S-NSSAI IE is not included and the allowed NSSAI contains: A) one S-NSSAI, the AMF shall use the S-NSSAI in the allowed NSSAI as the S-NSSAI; B) two or more S-NSSAIs and the user's subscription context obtained from UDM contains only one default S-NSSAI that is included in the allowed NSSAI, the AMF shall use the S-NSSAI in the allowed NSSAI as the S-NSSAI; or C) two or more S-NSSAIs and the user's subscription context obtained from UDM contains two or more default S-NSSAI(s) included in the allowed NSSAI, the AMF shall use an S-NSSAI in the allowed NSSAI selected based on operator policy as the S-NSSAI; ii) if the DNN IE is not included, and the user's subscription context obtained from UDM: A) contains the default DNN for the S-NSSAI, the AMF shall use the default DNN as the DNN; and B) does not contain the default DNN for the S-NSSAI, the AMF shall use a locally configured DNN as the DNN; iii) if the DNN selected by the network is a LADN DNN, the AMF shall determine the UE presence in LADN service area (see subclause 6.2.6); iv) if the SMF selection is successful, the AMF should store a PDU session routing context for the PDU session ID and the UE, set the SMF ID in the stored PDU session routing context to the selected SMF ID, and forward the 5GSM message, the PDU session ID, the old PDU session ID, the S-NSSAI, the mapped S-NSSAI (in roaming scenarios), the DNN determined by the AMF, DNN selected by the network (if different from DNN determined by the AMF), the request type and UE presence in LADN service area (if DNN selected by the network corresponds to an LADN DNN) towards the SMF ID of the PDU session routing context; and v) if the SMF selection fails, then the AMF shall send back to the UE the 5GSM message which was not forwarded as specified in subclause 5.4.5.3.1 case e) or case f); 5) if the AMF has a PDU session routing context for the PDU session ID and the UE, the PDU session routing context indicates that the PDU session is an emergency PDU session, the Request type IE is set to "initial emergency request", the AMF should forward the 5GSM message, the PDU session ID, the S-NSSAI (if configured in the AMF emergency configuration data), the DNN (if configured in the AMF emergency configuration data) and the request type towards the SMF ID of the PDU session routing context; 6) if the Request type IE is set to "initial emergency request" and the S-NSSAI or the DNN is received, the AMF ignores the received S-NSSAI or the DNN and uses the emergency DNN from the AMF emergency configuration data, if any; 7) if the AMF does not have a PDU session routing context for the PDU session ID and the UE, and the Request type IE of the UL NAS TRANSPORT message is either not provided or is provided but set to other value than "initial request", "existing PDU session", "initial emergency request", "existing emergency PDU session" and "MA PDU request", then the AMF may send back to the UE the 5GSM message which was not forwarded as specified in subclause 5.4.5.3.1 case e) or case f); 8) if the AMF unsuccessfully attempted to forward the 5GSM message, the PDU session ID, the S-NSSAI, the mapped S-NSSAI (in roaming scenarios), the DNN and the request type (if received) towards a SMF ID, then the AMF may send back to the UE the 5GSM message which was not forwarded as specified in subclause 5.4.5.3.1 case e) or case f). 9) if the Old PDU session ID IE is included in the UL NAS TRANSPORT message, the AMF does not have a PDU session routing context for the old PDU session ID and the UE, the AMF does not have a PDU session routing context for the PDU session ID and the UE, the Request type IE is set to "initial request", the AMF should select an SMF with following handlings: i) if the S-NSSAI IE is not included and the allowed NSSAI contains: A) one S-NSSAI, the AMF shall use the S-NSSAI in the allowed NSSAI as the S-NSSAI; B) two or more S-NSSAIs and the user's subscription context obtained from UDM contains only one default S-NSSAI that is included in the allowed NSSAI, the AMF shall use the default S-NSSAI in the allowed NSSAI as the S-NSSAI; or C) two or more S-NSSAIs and the user's subscription context obtained from UDM contains two or more default S-NSSAI(s) included in the allowed NSSAI, the AMF shall use an S-NSSAI in the allowed NSSAI selected based on operator policy as the S-NSSAI. ii) if the DNN IE is not included, and the user's subscription context obtained from UDM: A) contains the default DNN for the S-NSSAI, the AMF shall use the default DNN as the DNN; and B) does not contain the default DNN for the S-NSSAI, the AMF shall use a locally configured DNN as the DNN; iii) if the DNN selected by the network is a LADN DNN, the AMF shall determine the UE presence in LADN service area (see subclause 6.2.6); iv) if the SMF selection is successful, the AMF should store a PDU session routing context for the PDU session ID and the UE, set the SMF ID in the stored PDU session routing context to the selected SMF ID, and forward the 5GSM message, the PDU session ID, the old PDU session ID, the S-NSSAI, the mapped S-NSSAI (in roaming scenarios), the DNN determined by the AMF, DNN selected by the network (if different from DNN determined by the AMF), the request type and UE presence in LADN service area (if DNN selected by the network corresponds to an LADN DNN) towards the SMF ID of the PDU session routing context; and v) if the SMF selection fails, then the AMF shall send back to the UE the 5GSM message which was not forwarded as specified in subclause 5.4.5.3.1 case e) or case f); 10) if the AMF has a PDU session routing context for the PDU session ID and the UE, the PDU session routing context indicates that the PDU session is not an emergency PDU session, and the Request type IE is included and is set to "existing emergency PDU session", the AMF may send back to the UE the 5GSM message which was not forwarded as specified in subclause 5.4.5.3.1 case e) or case f); 11) if the AMF has a PDU session routing context for the PDU session ID and the UE, the PDU session routing context indicates that the PDU session is an emergency PDU session, and the Request type IE is included and is set to "existing PDU session", the AMF may forward the 5GSM message, the PDU session ID, the S-NSSAI (if configured in the AMF emergency configuration data), the DNN (if configured in the AMF emergency configuration data), and the request type towards the SMF identified by the SMF ID of the PDU session routing context; 12) if the AMF has a PDU session routing context for the PDU session ID and the UE, the Request type IE is set to "initial request", then the AMF shall perform a local release of the PDU session identified by the PDU session ID and shall request the SMF to perform a local release of the PDU session, and proceed as specified in subclause 5.4.5.2.3; 13) if the Request type IE is set to "initial request" or "modification request", and the S-NSSAI IE contains an S-NSSAI that is not allowed by the network, then the AMF shall send back to the UE the 5GSM message which was not forwarded as specified in subclause 5.4.5.3.1 case e), case f) or h4); 14) if the Request type IE is set to "existing PDU session", the AMF has a PDU session routing context for the PDU session ID and the UE, the PDU session routing context indicates that the PDU session is not an emergency PDU session, and the S-NSSAI associated with the PDU session identified by the PDU session ID is not allowed for the target access type, the AMF shall send back to the UE the 5GSM message which was not forwarded as specified in subclause 5.4.5.3.1 case e), case f) or h4); 15) if the Request type IE is set to "initial request", "existing PDU session", "modification request" or "MA PDU request", the UE is not configured for high priority access in selected PLMN or SNPN, and the UE is in non-allowed area or is not in allowed area, the AMF shall send back to the UE the 5GSM message which was not forwarded, and 5GMM cause #28 "Restricted service area" as specified in subclause 5.4.5.3.1 case i); 15a) if the Request type IE is set to "initial request" or "initial emergency request" and the AMF determines that the UE has registered to a PLMN via a satellite NG-RAN cell that is not allowed to operate at the present UE location, then the AMF may send back to the UE the 5GSM message which was not forwarded as specified in subclause 5.4.5.3.1 case i1); and 16) if the Request type IE is set to "initial request" or "MA PDU request", the AMF is pending the receipt of a REGISTRATION REQUEST message indicating "mobility registration updating" in the 5GS registration type IE, and an emergency PDU session exists for the UE (see subclause 5.4.4.3), the AMF shall send back to the UE the 5GSM message which was not forwarded as specified in subclause 5.4.5.3.1 case e) or case f); 17) if the timer T3447 is running and the UE supports service gap control and: i) the Request type IE: A) is set to "initial request"; B) is set to "existing PDU session"; or C is set to "modification request" and the PDU session being modified is a non-emergency PDU session; ii) the UE is not configured for high priority access in selected PLMN; iii) the current NAS signalling connection was not triggered by paging; and iv) mobile terminated signalling has not been sent or no user-plane resources have been established for any PDU session after the establishment of the current NAS signalling connection, then the AMF shall send back to the UE the 5GSM message which was not forwarded as specified in subclause 5.4.5.3.1 case e) or case f); 18) if the AMF has a PDU session routing context for the PDU session ID and the UE, the Request type IE is not included, the UE is not configured for high priority access in selected PLMN or SNPN, and the PDU session is not an emergency PDU session, then the AMF shall forward the 5GSM message, and the PDU session ID IE towards the SMF identified by the SMF ID of the PDU session routing context with: i) 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], if DNN based congestion control is activated for the selected DNN; ii) 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], if S-NSSAI and DNN based congestion control is activated for the selected S-NSSAI and the selected DNN; or iii) 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], if S-NSSAI only based congestion control is activated for the selected S-NSSAI; 19) if the Request type IE is set to "MA PDU request" and the S-NSSAI IE contains an S-NSSAI that is not allowed by the network on neither access, then the AMF shall send to the UE the 5GSM message which was not forwarded as specified in subclause 5.4.5.3.1 case e) or case f); 20) if the Request type IE is set to "initial request" and the UE is registered for emergency services over the current access, then the AMF may send back to the UE the 5GSM message which was not forwarded as specified in subclause 5.4.5.3.1 case e) or case f); and 21) if the Request type IE is set to "existing PDU session", the UE is attempting to transfer a PDU session from 3GPP access to non-3GPP access, and the PDU session is associated with control plane only indication then the AMF shall send back to the UE the 5GSM message which was not forwarded as specified in subclause 5.4.5.3.1 case e). 22) if the Request type IE is set to "MA PDU request" and the UE requested DNN corresponds to an LADN DNN, the AMF shall send back to the UE the 5GSM message which was not forwarded and 5GMM cause #90 "payload was not forwarded" as specified in subclause 5.4.5.3.1 case hx). 23) if the Request type IE is set to "initial request", the UE requested DNN corresponds to an LADN DNN, and the MA PDU session information IE is included, the AMF shall not forward the MA PDU session information towards the SMF. 24) if the Request type IE is set to "modification request", the DNN associated with the PDU session corresponds to an LADN DNN, and MA PDU session information IE is included, the AMF shall not forward the MA PDU session information towards the SMF. b) If the Payload container type IE is set to "SMS" and: 1) the AMF does not have an SMSF address associated with the UE; 2) the AMF cannot forward the content of the Payload container IE to the SMSF associated with the SMSF address available in the AMF; or 3) the AMF determines that the UE has registered to a PLMN via a satellite NG-RAN cell that is not allowed to operate at the present UE location; then the AMF shall abort the procedure. c) If the Payload container type IE is set to "LTE Positioning Protocol (LPP) message container" or "SLPP message container" and: 1) if the Additional information IE is not included in the UL NAS TRANSPORT message; 2) the AMF cannot forward the content of the Payload container IE to the LMF associated with the routing information included in the Additional information IE; or 3) the AMF determines that the UE has registered to a PLMN via a satellite NG-RAN cell that is not allowed to operate at the present UE location; then the AMF shall abort the procedure. d) If the Payload container type IE is set to "UE policy container" and: 1) the AMF does not have a PCF address associated with the UE; 2) the AMF cannot forward the content of the Payload container IE to the PCF associated with the PCF address available in the AMF; or 3) the AMF determines that the UE has registered to a PLMN via a satellite NG-RAN cell that is not allowed to operate at the present UE location; then the AMF shall abort the procedure. e) If the Payload container type IE is set to "Location services message container" and: 1) if the Additional information IE is included in the UL NAS TRANSPORT message and the AMF cannot forward the content of the Payload container IE to an LMF associated with the routing information included in the Additional information IE; 2) the AMF determines that the UE has registered to a PLMN via a satellite NG-RAN cell that is not allowed to operate at the present UE location; 3) the AMF determines that the payload container content is related to PRU and the UE has not a valid PRU subscription information; or 4) any combination of bullets 1 to 3, then the AMF shall abort the procedure. f) If the Payload container type IE is set to "SMS" or "LTE Positioning Protocol (LPP) message container" or "SLPP message container": 1) the timer T3447 is running and the UE supports service gap control; 2) the UE is not configured for high priority access in selected PLMN; 3) the current NAS signalling connection was not triggered by paging; and 4) mobile terminated signalling has not been sent or no user-plane resources have been established for any PDU session after the establishment of the current NAS signalling connection, the AMF shall abort the procedure. NOTE: In this state the N1 NAS signalling connection can be released by the network. g) If the Payload container type IE is set to "CIoT user data container" and: 1) if the AMF does not have a PDU session routing context for the PDU session ID and the UE; or 2) if the AMF unsuccessfully attempted to forward the user data container and the PDU session ID, then the AMF may send back to the UE the CIoT user data container which was not forwarded as specified in subclause 5.4.5.3.1 case l1). h) If the Payload container type IE is set to "CIoT user data container": 1) if the timer T3447 is running and the UE supports service gap control; 2) the UE is not configured for high priority access in selected PLMN; 3) the current N1 NAS signalling connection was not triggered by paging; and 4) mobile terminated signalling has not been sent or no user-plane resources have been established for any PDU session after the establishment of the current NAS signalling connection, then the AMF shall send back to the UE the CIoT user data container which was not forwarded as specified in subclause 5.4.5.3.1 case l1). i) If the Payload container type IE is set to "SOR transparent container", "UE prameters update transparent container", or "Service-level-AA container", and the AMF determines that the UE has registered to a PLMN via a satellite NG-RAN cell that is not allowed to operate at the present UE location, then the AMF shall abort the procedure. j) If the Payload container type IE is set to "UPP-CMI container" and: 1) if the Additional information IE is not included in the UL NAS TRANSPORT message; 2) the AMF cannot forward the content of the Payload container IE to the LMF associated with the routing information included in the Additional information IE; or 3) the AMF determines that the UE has registered to a PLMN via a satellite NG-RAN cell that is not allowed to operate at the present UE location; then the AMF shall abort the procedure. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.4.5.2.5 |
3,660 | 5.2.2 Scenario | Several UAVs are making deliveries to an office block simultaneously. They are each registered with the UTM. Each UAS is transmitting accurate positional information, which may be supplemented by the service MNO, to the UTM. The UTM has agreed their route data with the authorization to operate. The UTM offers a UCAS service. The UAS provides the UTM with its live location. The UTM may receive location information related to manned air traffic. When the UTM detects that there is a danger of loss of separation between a UAS under its control and a manned aircraft the UTM may issue a course change commend to the appropriate UAS. As the UTM notices that the multiple UAVs pass some metric of proximity defined by speed of aircraft, density of airspace, etc. and decided to intervene to help prevent any collision. The UTM sends a notification message towards UAV controller to warn for possible collision. If after notification message there is no change of behaviour of UAV the UTM may send route change data to the UAS. The route modifications are transmitted to each UAS and are incorporated into the planned routes of each UAS. | 3GPP TS 22.825 | Study on Remote Identification of Unmanned Aerial Systems (UAS) | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 5.2.2 |
3,661 | 5.13 Requirements on NSSAAF | The Network slice specific and SNPN authentication and authorization function (NSSAAF) shall handle the Network Slice Specific Authentication requests from the serving AMF as specified in clause 16.The NSSAAF shall also support functionality for access to SNPN using credentials from Credentials Holder using AAA Server as specified in clause I.2.2.2. The NSSAAF is responsible to send the NSSAA requests to the appropriate AAA-S. The NSSAAF shall support AAA-S triggered Network Slice-Specific Re-authentication and Re-authorization and Slice-Specific Authorization Revocation and translate any AAA protocol into a Service Based format. NSSAAF shall translate the Service based messages from the serving AMF or AUSF to AAA protocols towards AAA-P/AAA-S. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 5.13 |
3,662 | – ServingCellConfig | The IE ServingCellConfig is used to configure (add or modify) the UE with a serving cell, which may be the SpCell or an SCell of an MCG or SCG. The parameters herein are mostly UE specific but partly also cell specific (e.g. in additionally configured bandwidth parts). Reconfiguration between a PUCCH and PUCCHless SCell is only supported using an SCell release and add. ServingCellConfig information element -- ASN1START -- TAG-SERVINGCELLCONFIG-START ServingCellConfig ::= SEQUENCE { tdd-UL-DL-ConfigurationDedicated TDD-UL-DL-ConfigDedicated OPTIONAL, -- Cond TDD initialDownlinkBWP BWP-DownlinkDedicated OPTIONAL, -- Need M downlinkBWP-ToReleaseList SEQUENCE (SIZE (1..maxNrofBWPs)) OF BWP-Id OPTIONAL, -- Need N downlinkBWP-ToAddModList SEQUENCE (SIZE (1..maxNrofBWPs)) OF BWP-Downlink OPTIONAL, -- Need N firstActiveDownlinkBWP-Id BWP-Id OPTIONAL, -- Cond SyncAndCellAdd bwp-InactivityTimer ENUMERATED {ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30, ms40,ms50, ms60, ms80,ms100, ms200,ms300, ms500, ms750, ms1280, ms1920, ms2560, spare10, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1 } OPTIONAL, --Need R defaultDownlinkBWP-Id BWP-Id OPTIONAL, -- Need S uplinkConfig UplinkConfig OPTIONAL, -- Need M supplementaryUplink UplinkConfig OPTIONAL, -- Need M pdcch-ServingCellConfig SetupRelease { PDCCH-ServingCellConfig } OPTIONAL, -- Need M pdsch-ServingCellConfig SetupRelease { PDSCH-ServingCellConfig } OPTIONAL, -- Need M csi-MeasConfig SetupRelease { CSI-MeasConfig } OPTIONAL, -- Need M sCellDeactivationTimer ENUMERATED {ms20, ms40, ms80, ms160, ms200, ms240, ms320, ms400, ms480, ms520, ms640, ms720, ms840, ms1280, spare2,spare1} OPTIONAL, -- Cond ServingCellWithoutPUCCH crossCarrierSchedulingConfig CrossCarrierSchedulingConfig OPTIONAL, -- Need M tag-Id TAG-Id, dummy1 ENUMERATED {enabled} OPTIONAL, -- Need R pathlossReferenceLinking ENUMERATED {spCell, sCell} OPTIONAL, -- Cond SCellOnly servingCellMO MeasObjectId OPTIONAL, -- Cond MeasObject ..., [[ lte-CRS-ToMatchAround SetupRelease { RateMatchPatternLTE-CRS } OPTIONAL, -- Need M rateMatchPatternToAddModList SEQUENCE (SIZE (1..maxNrofRateMatchPatterns)) OF RateMatchPattern OPTIONAL, -- Need N rateMatchPatternToReleaseList SEQUENCE (SIZE (1..maxNrofRateMatchPatterns)) OF RateMatchPatternId OPTIONAL, -- Need N downlinkChannelBW-PerSCS-List SEQUENCE (SIZE (1..maxSCSs)) OF SCS-SpecificCarrier OPTIONAL -- Need S ]], [[ supplementaryUplinkRelease-r16 ENUMERATED {true} OPTIONAL, -- Need N tdd-UL-DL-ConfigurationDedicated-IAB-MT-r16 TDD-UL-DL-ConfigDedicated-IAB-MT-r16 OPTIONAL, -- Cond TDD_IAB dormantBWP-Config-r16 SetupRelease { DormantBWP-Config-r16 } OPTIONAL, -- Need M ca-SlotOffset-r16 CHOICE { refSCS15kHz INTEGER (-2..2), refSCS30KHz INTEGER (-5..5), refSCS60KHz INTEGER (-10..10), refSCS120KHz INTEGER (-20..20) } OPTIONAL, -- Cond AsyncCA dummy2 SetupRelease { DummyJ } OPTIONAL, -- Need M intraCellGuardBandsDL-List-r16 SEQUENCE (SIZE (1..maxSCSs)) OF IntraCellGuardBandsPerSCS-r16 OPTIONAL, -- Need S intraCellGuardBandsUL-List-r16 SEQUENCE (SIZE (1..maxSCSs)) OF IntraCellGuardBandsPerSCS-r16 OPTIONAL, -- Need S csi-RS-ValidationWithDCI-r16 ENUMERATED {enabled} OPTIONAL, -- Need R lte-CRS-PatternList1-r16 SetupRelease { LTE-CRS-PatternList-r16 } OPTIONAL, -- Need M lte-CRS-PatternList2-r16 SetupRelease { LTE-CRS-PatternList-r16 } OPTIONAL, -- Need M crs-RateMatch-PerCORESETPoolIndex-r16 ENUMERATED {enabled} OPTIONAL, -- Need R enableTwoDefaultTCI-States-r16 ENUMERATED {enabled} OPTIONAL, -- Need R enableDefaultTCI-StatePerCoresetPoolIndex-r16 ENUMERATED {enabled} OPTIONAL, -- Need R enableBeamSwitchTiming-r16 ENUMERATED {true} OPTIONAL, -- Need R cbg-TxDiffTBsProcessingType1-r16 ENUMERATED {enabled} OPTIONAL, -- Need R cbg-TxDiffTBsProcessingType2-r16 ENUMERATED {enabled} OPTIONAL -- Need R ]], [[ directionalCollisionHandling-r16 ENUMERATED {enabled} OPTIONAL, -- Need R channelAccessConfig-r16 SetupRelease { ChannelAccessConfig-r16 } OPTIONAL -- Need M ]], [[ nr-dl-PRS-PDC-Info-r17 SetupRelease {NR-DL-PRS-PDC-Info-r17} OPTIONAL, -- Need M semiStaticChannelAccessConfigUE-r17 SetupRelease {SemiStaticChannelAccessConfigUE-r17} OPTIONAL, -- Need M mimoParam-r17 SetupRelease {MIMOParam-r17} OPTIONAL, -- Need M channelAccessMode2-r17 ENUMERATED {enabled} OPTIONAL, -- Need R timeDomainHARQ-BundlingType1-r17 ENUMERATED {enabled} OPTIONAL, -- Need R nrofHARQ-BundlingGroups-r17 ENUMERATED {n1, n2, n4} OPTIONAL, -- Need R fdmed-ReceptionMulticast-r17 ENUMERATED {true} OPTIONAL, -- Need R moreThanOneNackOnlyMode-r17 ENUMERATED {mode2} OPTIONAL, -- Need S tci-ActivatedConfig-r17 TCI-ActivatedConfig-r17 OPTIONAL, -- Cond TCI_ActivatedConfig directionalCollisionHandling-DC-r17 ENUMERATED {enabled} OPTIONAL, -- Need R lte-NeighCellsCRS-AssistInfoList-r17 SetupRelease { LTE-NeighCellsCRS-AssistInfoList-r17 } OPTIONAL -- Need M ]], [[ lte-NeighCellsCRS-Assumptions-r17 ENUMERATED {false} OPTIONAL -- Need R ]], [[ crossCarrierSchedulingConfigRelease-r17 ENUMERATED {true} OPTIONAL -- Need N ]], [[ multiPDSCH-PerSlotType1-CB-r17 ENUMERATED {enabled, disabled} OPTIONAL -- Need R ]], [[ lte-CRS-PatternList3-r18 SetupRelease { LTE-CRS-PatternList-r16 } OPTIONAL, -- Need M lte-CRS-PatternList4-r18 SetupRelease { LTE-CRS-PatternList-r16 } OPTIONAL, -- Need M pdcch-CandidateReceptionWith-CRS-Overlap-r18 ENUMERATED {enabled} OPTIONAL, -- Need R cjt-Scheme-PDSCH-r18 ENUMERATED {cjtSchemeA, cjtSchemeB} OPTIONAL, -- Need R tag2-r18 SEQUENCE { tag2-Id TAG-Id, tag2-flag BOOLEAN } OPTIONAL, -- Need R n-TimingAdvanceOffset2-r18 ENUMERATED { n0, n25600, n39936 } OPTIONAL, -- Cond Tag2 cellDTXDRX-Config-r18 SetupRelease { CellDTXDRX-Config-r18 } OPTIONAL, -- Need M positionInDCI-cellDTRX-r18 INTEGER (0..maxDCI-2-9-Size-1-r18) OPTIONAL, -- Need R mc-DCI-SetOfCellsToAddModList-r18 SEQUENCE (SIZE (1..maxNrofSetsOfCells-r18)) OF MC-DCI-SetOfCells-r18 OPTIONAL, -- Need N mc-DCI-SetOfCellsToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofSetsOfCells-r18)) OF SetOfCellsId-r18 OPTIONAL -- Need N ]] } UplinkConfig ::= SEQUENCE { initialUplinkBWP BWP-UplinkDedicated OPTIONAL, -- Need M uplinkBWP-ToReleaseList SEQUENCE (SIZE (1..maxNrofBWPs)) OF BWP-Id OPTIONAL, -- Need N uplinkBWP-ToAddModList SEQUENCE (SIZE (1..maxNrofBWPs)) OF BWP-Uplink OPTIONAL, -- Need N firstActiveUplinkBWP-Id BWP-Id OPTIONAL, -- Cond SyncAndCellAdd pusch-ServingCellConfig SetupRelease { PUSCH-ServingCellConfig } OPTIONAL, -- Need M carrierSwitching SetupRelease { SRS-CarrierSwitching } OPTIONAL, -- Need M ..., [[ powerBoostPi2BPSK BOOLEAN OPTIONAL, -- Need M uplinkChannelBW-PerSCS-List SEQUENCE (SIZE (1..maxSCSs)) OF SCS-SpecificCarrier OPTIONAL -- Need S ]], [[ enablePL-RS-UpdateForPUSCH-SRS-r16 ENUMERATED {enabled} OPTIONAL, -- Need R enableDefaultBeamPL-ForPUSCH0-0-r16 ENUMERATED {enabled} OPTIONAL, -- Need R enableDefaultBeamPL-ForPUCCH-r16 ENUMERATED {enabled} OPTIONAL, -- Need R enableDefaultBeamPL-ForSRS-r16 ENUMERATED {enabled} OPTIONAL, -- Need R uplinkTxSwitching-r16 SetupRelease { UplinkTxSwitching-r16 } OPTIONAL, -- Need M mpr-PowerBoost-FR2-r16 ENUMERATED {true} OPTIONAL -- Need R ]], [[ srs-PosTx-Hopping-r18 SetupRelease { SRS-PosTx-Hopping-r18 } OPTIONAL -- Need M ]] } DummyJ ::= SEQUENCE { maxEnergyDetectionThreshold-r16 INTEGER(-85..-52), energyDetectionThresholdOffset-r16 INTEGER (-20..-13), ul-toDL-COT-SharingED-Threshold-r16 INTEGER (-85..-52) OPTIONAL, -- Need R absenceOfAnyOtherTechnology-r16 ENUMERATED {true} OPTIONAL -- Need R } ChannelAccessConfig-r16 ::= SEQUENCE { energyDetectionConfig-r16 CHOICE { maxEnergyDetectionThreshold-r16 INTEGER (-85..-52), energyDetectionThresholdOffset-r16 INTEGER (-13..20) } OPTIONAL, -- Need R ul-toDL-COT-SharingED-Threshold-r16 INTEGER (-85..-52) OPTIONAL, -- Need R absenceOfAnyOtherTechnology-r16 ENUMERATED {true} OPTIONAL -- Need R } IntraCellGuardBandsPerSCS-r16 ::= SEQUENCE { guardBandSCS-r16 SubcarrierSpacing, intraCellGuardBands-r16 SEQUENCE (SIZE (1..4)) OF GuardBand-r16 } GuardBand-r16 ::= SEQUENCE { startCRB-r16 INTEGER (0..274), nrofCRBs-r16 INTEGER (0..15) } DormancyGroupID-r16 ::= INTEGER (0..4) DormantBWP-Config-r16::= SEQUENCE { dormantBWP-Id-r16 BWP-Id OPTIONAL, -- Need M withinActiveTimeConfig-r16 SetupRelease { WithinActiveTimeConfig-r16 } OPTIONAL, -- Need M outsideActiveTimeConfig-r16 SetupRelease { OutsideActiveTimeConfig-r16 } OPTIONAL -- Need M } WithinActiveTimeConfig-r16 ::= SEQUENCE { firstWithinActiveTimeBWP-Id-r16 BWP-Id OPTIONAL, -- Need M dormancyGroupWithinActiveTime-r16 DormancyGroupID-r16 OPTIONAL -- Need R } OutsideActiveTimeConfig-r16 ::= SEQUENCE { firstOutsideActiveTimeBWP-Id-r16 BWP-Id OPTIONAL, -- Need M dormancyGroupOutsideActiveTime-r16 DormancyGroupID-r16 OPTIONAL -- Need R } UplinkTxSwitching-r16 ::= SEQUENCE { uplinkTxSwitchingPeriodLocation-r16 BOOLEAN, uplinkTxSwitchingCarrier-r16 ENUMERATED {carrier1, carrier2} } MIMOParam-r17 ::= SEQUENCE { additionalPCI-ToAddModList-r17 SEQUENCE (SIZE(1..maxNrofAdditionalPCI-r17)) OF SSB-MTC-AdditionalPCI-r17 OPTIONAL, -- Need N additionalPCI-ToReleaseList-r17 SEQUENCE (SIZE(1..maxNrofAdditionalPCI-r17)) OF AdditionalPCIIndex-r17 OPTIONAL, -- Need N unifiedTCI-StateType-r17 ENUMERATED {separate, joint} OPTIONAL, -- Need R uplink-PowerControlToAddModList-r17 SEQUENCE (SIZE (1..maxUL-TCI-r17)) OF Uplink-powerControl-r17 OPTIONAL, -- Need N uplink-PowerControlToReleaseList-r17 SEQUENCE (SIZE (1..maxUL-TCI-r17)) OF Uplink-powerControlId-r17 OPTIONAL, -- Need N sfnSchemePDCCH-r17 ENUMERATED {sfnSchemeA,sfnSchemeB} OPTIONAL, -- Need R sfnSchemePDSCH-r17 ENUMERATED {sfnSchemeA,sfnSchemeB} OPTIONAL -- Need R } MC-DCI-SetOfCells-r18 ::= SEQUENCE { setOfCellsId-r18 SetOfCellsId-r18, nCI-Value-r18 INTEGER (0..7), scheduledCellListDCI-1-3-r18 SEQUENCE (SIZE (2..maxNrofCellsInSet-r18)) OF ServCellIndex OPTIONAL, -- Need R scheduledCellListDCI-0-3-r18 SEQUENCE (SIZE (2..maxNrofCellsInSet-r18)) OF ServCellIndex OPTIONAL, -- Need R scheduledCellComboListDCI-1-3-r18 SEQUENCE (SIZE (1..maxNrofCellCombos-r18)) OF ScheduledCellCombo-r18 OPTIONAL, -- Need R scheduledCellComboListDCI-0-3-r18 SEQUENCE (SIZE (1..maxNrofCellCombos-r18)) OF ScheduledCellCombo-r18 OPTIONAL, -- Need R antennaPortsDCI1-3-r18 ENUMERATED {type1a, type2} OPTIONAL, -- Cond TypeDCI1-3 antennaPortsDCI0-3-r18 ENUMERATED {type1a, type2} OPTIONAL, -- Cond TypeDCI0-3 tpmi-DCI0-3-r18 ENUMERATED {type1a, type2} OPTIONAL, -- Cond TypeDCI0-3 sri-DCI0-3-r18 ENUMERATED {type1a, type2} OPTIONAL, -- Cond TypeDCI0-3 priorityIndicatorDCI-1-3-r18 ENUMERATED {enabled} OPTIONAL, -- Need R priorityIndicatorDCI-0-3-r18 ENUMERATED {enabled} OPTIONAL, -- Need R dormancyDCI-1-3-r18 ENUMERATED {enabled} OPTIONAL, -- Need R dormancyDCI-0-3-r18 ENUMERATED {enabled} OPTIONAL, -- Need R pdcchMonAdaptDCI-1-3-r18 ENUMERATED {enabled} OPTIONAL, -- Need R pdcchMonAdaptDCI-0-3-r18 ENUMERATED {enabled} OPTIONAL, -- Need R minimumSchedulingOffsetK0DCI-1-3-r18 ENUMERATED {enabled} OPTIONAL, -- Need R minimumSchedulingOffsetK0DCI-0-3-r18 ENUMERATED {enabled} OPTIONAL, -- Need R pdsch-HARQ-ACK-OneShotFeedbackDCI-1-3-r18 ENUMERATED {enabled} OPTIONAL, -- Need R pdsch-HARQ-ACK-enhType3DCI-1-3-r18 ENUMERATED {enabled} OPTIONAL, -- Need R pdsch-HARQ-ACK-enhType3DCIfieldDCI-1-3-r18 ENUMERATED {enabled} OPTIONAL, -- Need R pdsch-HARQ-ACK-retxDCI-1-3-r18 ENUMERATED {enabled} OPTIONAL, -- Need R pucch-sSCellDynDCI-1-3-r18 ENUMERATED {enabled} OPTIONAL, -- Need R tdra-FieldIndexListDCI-1-3-r18 SEQUENCE (SIZE (1..32)) OF TDRA-FieldIndexDCI-1-3-r18 OPTIONAL, -- Need R tdra-FieldIndexListDCI-0-3-r18 SEQUENCE (SIZE (1..64)) OF TDRA-FieldIndexDCI-0-3-r18 OPTIONAL, -- Need R rateMatchListDCI-1-3-r18 SEQUENCE (SIZE (1..16)) OF RateMatchDCI-1-3-r18 OPTIONAL, -- Need R zp-CSI-RSListDCI-1-3-r18 SEQUENCE (SIZE (1..8)) OF ZP-CSI-DCI-1-3-r18 OPTIONAL, -- Need R tci-ListDCI-1-3-r18 SEQUENCE (SIZE (1..16)) OF TCI-DCI-1-3-r18 OPTIONAL, -- Need R srs-RequestListDCI-1-3-r18 SEQUENCE (SIZE (1..16)) OF SRS-RequestCombo-r18 OPTIONAL, -- Need R srs-OffsetListDCI-1-3-r18 SEQUENCE (SIZE (1..8)) OF SRS-OffsetCombo-r18 OPTIONAL, -- Need R srs-RequestListDCI-0-3-r18 SEQUENCE (SIZE (1..16)) OF SRS-RequestCombo-r18 OPTIONAL, -- Need R srs-OffsetListDCI-0-3-r18 SEQUENCE (SIZE (1..8)) OF SRS-OffsetCombo-r18 OPTIONAL -- Need R } SetOfCellsId-r18 ::= INTEGER (0..maxNrofSetsOfCells-1-r18) ScheduledCellCombo-r18 ::= SEQUENCE (SIZE (1..maxNrofCellsInSet-r18)) OF INTEGER (0..maxNrofCellsInSet-1-r18) RateMatchDCI-1-3-r18 ::= SEQUENCE (SIZE (1..maxNrofCellsInSet-r18)) OF BIT STRING (SIZE (1..2)) ZP-CSI-DCI-1-3-r18 ::= SEQUENCE (SIZE (1.. maxNrofCellsInSet-r18)) OF BIT STRING (SIZE (1..2)) TCI-DCI-1-3-r18 ::= SEQUENCE (SIZE (2.. maxNrofCellsInSet-r18)) OF BIT STRING (SIZE (3)) SRS-RequestCombo-r18 ::= SEQUENCE (SIZE (1.. maxNrofCellsInSet-r18)) OF BIT STRING (SIZE (2..3)) SRS-OffsetCombo-r18 ::= SEQUENCE (SIZE (1.. maxNrofCellsInSet-r18)) OF INTEGER (0..3) TDRA-FieldIndexDCI-1-3-r18 ::= SEQUENCE (SIZE (2.. maxNrofBWPsInSetOfCells-r18)) OF INTEGER (0..maxNrofDL-Allocations-1-r18) TDRA-FieldIndexDCI-0-3-r18 ::= SEQUENCE (SIZE (2.. maxNrofBWPsInSetOfCells-r18)) OF INTEGER (0..maxNrofUL-Allocations-1-r18) -- TAG-SERVINGCELLCONFIG-STOP -- ASN1STOP NOTE 1: If the dedicated part of initial UL/DL BWP configuration is absent, the initial BWP can be used but with some limitations. For example, changing to another BWP requires RRCReconfiguration since DCI format 1_0 doesn't support DCI-based switching. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,663 | 28.13 NF Service Set Identifier (NF Service Set ID) | A NF Service Set Identifier is a globally unique identifier of a set of equivalent and interchangeable CP NF service instances within a NF instance from a given network that provide distribution, redundancy and scalability (see clause 5.21.3 of 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [119]). An NF Service Set Identifier shall be constructed from the MCC, MNC, NID (for SNPN), NF instance Identifier, service name and a Set ID. A NF Service Set Identifier shall be formatted as the following string: set<Set ID>.sn<Service Name>.nfi<NF Instance ID>.5gc.mnc<MNC>.mcc<MCC> for a NF Service Set in a PLMN, or set<Set ID>.sn<Service Name>.nfi<NF Instance ID>.5gc.nid<NID>.mnc<MNC>.mcc<MCC> for a NF Service Set in a SNPN. where: - the <MCC> and <MNC> shall identify the PLMN of the NF Service Set and shall be encoded as follows: - <MCC> = 3 digits - <MNC> = 3 digits If there are only 2 significant digits in the MNC, one "0" digit shall be inserted at the left side to fill the 3 digits coding of MNC. - the Network Identifier (NID) shall be encoded as hexadecimal digits as specified in clause 12.7. - the NFInstanceID shall identify the NF instance of the NF Service set, as defined by 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [119] and 3GPP TS 29.510[ 5G System; Network function repository services; Stage 3 ] [130]; - the ServiceName shall identify the NF service of the NF Service set, as defined by 3GPP TS 29.510[ 5G System; Network function repository services; Stage 3 ] [130]; - the Set ID shall be a service specific Set ID within the NF instance, chosen by the operator that shall consist of alphabetic characters (A-Z and a-z), digits (0-9) and/or the hyphen (-) and that shall end with either an alphabetic character or a digit; - the case of alphabetic characters is not significant (i.e. two NF Service Set IDs with the same characters but using different lower and upper cases identify the same NF Service Set). EXAMPLE 1: setxyz.snnsmf-pdusession.nfi54804518-4191-46b3-955c-ac631f953ed8.5gc.mnc012.mcc345 EXAMPLE 2: set2.snnpcf-smpolicycontrol.nfi54804518-4191-46b3-955c-ac631f953ed8.5gc.mnc012.mcc345 EXAMPLE 3: setxyz.snnsmf-pdusession.nfi54804518-4191-46b3-955c-ac631f953ed8.5gc.nid000007ed9d5.mnc012.mcc345 for a SNPN with the NID 000007ed9d5 (hexadecimal). NF service instances from different NF instances are equivalent NF service instances if they share the same MCC, MNC, NID (for SNPN), ServiceName and Set ID. NF Service Sets belonging to different NF Instances are said to be equivalent, if they share the same MCC, MNC, NID (for SNPN), ServiceName and Set ID. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 28.13 |
3,664 | W.4.1 Key derivation, management and distribution W.4.1.1 General | If the security protection of MBS traffic is required, confidentiality and integrity protection as specified in clause 5.3 of TS 33.246[ 3G Security; Security of Multimedia Broadcast/Multicast Service (MBMS) ] [102] apply. The control-plane procedure and user-plane procedure are optionally supported in service layer. The control-plane procedure is only applicable for multicast sessions, while the user-plane procedure is applicable for both multicast sessions and broadcast sessions. The user plane security between UE and RAN shall be deactivated when 5GC shared MBS traffic delivery method for MBS data transmission is used to avoid redundant protection. The MBS Security Function (MBSSF) is a logical function, which needs to be collocated with either MBSF or MBSTF and the according interfaces are up to the implementation of the deployment options. In case of the control-plane procedure, the key derivation, management and distribution in MBSF and MBSTF can be achieved in MBSSF. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | W.4.1 |
3,665 | 5.5.2.1.3 Execution phase | Figure 5.5.2.1.3-1: E-UTRAN to UTRAN Iu mode Inter RAT HO, execution phase NOTE: For a PMIP-based S5/S8, procedure steps (A) and (B) are defined in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [2]. Step (B) shows PCRF interaction in the case of PMIP-based S5/S8. Steps 8 and 8a concern GTP based S5/S8 The source eNodeB continues to receive downlink and uplink user plane PDUs. 1. The source MME completes the preparation phase towards source eNodeB by sending the message Handover Command (Target to Source Transparent Container, E-RABs to Release List, Bearers Subject to Data Forwarding List). The "Bearers Subject to Data forwarding list" IE may be included in the message and it shall be a list of 'Address(es) and TEID(s) for user traffic data forwarding' received from target side in the preparation phase (Step 7 of the preparation phase) when 'Direct Forwarding' applies, or the parameters received in Step 8a of the preparation phase when 'Indirect Forwarding' applies. The source eNodeB initiates data forwarding for bearers specified in the "Bearers Subject to Data Forwarding List". The data forwarding may go directly to target RNC or alternatively go via the Serving GW if so decided by source MME and or/ target SGSN in the preparation phase. 2. The source eNodeB will give a command to the UE to handover to the target access network via the message HO from E-UTRAN Command. This message includes a transparent container including radio aspect parameters that the target RNC has set-up in the preparation phase. The details of this E-UTRAN specific signalling are described in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]. Upon the reception of the HO from E-UTRAN Command message containing the Handover Command message, the UE shall associate its bearer IDs to the respective RABs based on the relation with the NSAPI and shall suspend the uplink transmission of the user plane data. 3. If the PLMN has configured Secondary RAT usage data reporting and the source eNodeB has Secondary RAT usage data to report, the eNodeB sends the RAN Usage data report message (Secondary RAT usage data) to the MME. Since the handover is an inter-RAT handover, the MME continues with the Secondary RAT usage data reporting procedure as in clause 5.7A.3. The reporting procedure in clause 5.7A.3 is only performed if PGW secondary RAT usage reporting is active. 4. The UE moves to the target UTRAN Iu (3G) system and executes the handover according to the parameters provided in the message delivered in step 2. The procedure is the same as in step 6 and 8 in clause 5.2.2.2 in TS 43.129[ None ] [8] with the additional function of association of the received RABs and existing Bearer Id related to the particular NSAPI. The UE may resume the user data transfer only for those NSAPIs for which there are radio resources allocated in the target RNC. 5. When the new source RNC-ID + S-RNTI are successfully exchanged with the UE, the target RNC shall send the Relocation Complete message to the target SGSN. The purpose of the Relocation Complete procedure is to indicate by the target RNC the completion of the relocation from the source E-UTRAN to the RNC. After the reception of the Relocation Complete message the target SGSN shall be prepared to receive data from the target RNC. Each uplink N-PDU received by the target SGSN is forwarded directly to the Serving GW. For SIPTO at the Local Network with stand-alone GW architecture, the target RNC shall include the Local Home Network ID of the target cell in the Relocation Complete message. 6. Then the target SGSN knows that the UE has arrived to the target side and target SGSN informs the source MME by sending the Forward Relocation Complete Notification (ISR Activated, Serving GW change) message. If indicated, ISR Activated indicates to the source MME that it shall maintain the UE's context and that it shall activate ISR, which is only possible when the S-GW is not changed. The source MME will also acknowledge that information. A timer in source MME is started to supervise when resources in Source eNodeB and Source Serving GW (for Serving GW relocation) shall be released. When the timer expires and ISR Activated is not indicated by the target SGSN the source MME releases all bearer resources of the UE. If Serving GW change is indicated and this timer expires the source MME deletes the EPS bearer resources by sending Delete Session Request (Cause, Operation Indication) messages to the Source Serving GW. The operation Indication flag is not set, that indicates to the Source Serving GW that the Source Serving GW shall not initiate a delete procedure towards the PDN GW. If ISR has been activated before this procedure, the cause indicates to the Source S-GW that the Source S-GW shall delete the bearer resources on the other old CN node by sending Delete Bearer Request message(s) to that CN node. Upon receipt of the Forward Relocation Complete Acknowledge message the target SGSN starts a timer if the target SGSN allocated S-GW resources for indirect forwarding. For all bearers that were not included in the Forward Relocation Request message sent in step 3, the MME now releases them by sending a Delete Bearer Command to the SGW, or, the appropriate message to the SCEF. 7. The target SGSN will now complete the Handover procedure by informing the Serving GW (for Serving GW relocation this will be the Target Serving GW) that the target SGSN is now responsible for all the EPS Bearer Contexts the UE has established. This is performed in the message Modify Bearer Request (SGSN Tunnel Endpoint Identifier for Control Plane, NSAPI(s), SGSN Address for Control Plane, SGSN Address(es) and TEID(s) for User Traffic for the accepted EPS bearers (if Direct Tunnel is not used) or RNC Address(es) and TEID(s) for User Traffic for the accepted EPS bearers (if Direct Tunnel is used) and RAT type, ISR Activated) per PDN connection. As it is a mobility from E-UTRAN, if the target SGSN supports location information change reporting, the target SGSN shall include the User Location Information (according to the supported granularity) in the Modify Bearer Request, regardless of whether location information change reporting had been requested in the previous RAT by the PDN GW. If the PDN GW requested User CSG information (determined from the UE context), the SGSN also includes the User CSG Information IE in this message. If the UE Time Zone has changed, the SGSN includes the UE Time Zone IE in this message. If Serving GW is not relocated but the Serving Network has changed or if the SGSN has not received any old Serving Network information from the old MME, the SGSN includes the new Serving Network IE in this message. In network sharing scenarios Serving Network denotes the serving core network. If indicated, the information ISR Activated indicates that ISR is activated, which is only possible when the S-GW is not changed. When the Modify Bearer Request does not indicate ISR Activated and S-GW is not changed, the S-GW deletes any ISR resources by sending a Delete Bearer Request to the other CN node that has bearer resources on the S-GW reserved. The SGSN releases the non-accepted EPS Bearer contexts by triggering the Bearer Context deactivation procedure. If the Serving GW receives a DL packet for a non-accepted bearer, the Serving GW drops the DL packet and does not send a Downlink Data Notification to the SGSN. 8. The Serving GW (for Serving GW relocation this will be the Target Serving GW) may inform the PDN GW(s) the change of for example for Serving GW relocation or the RAT type that e.g. can be used for charging, by sending the message Modify Bearer Request per PDN connection. The S-GW also includes User Location Information IE and/or UE Time Zone IE and/or User CSG Information IE if they are present in step 7. Serving Network should be included if it is received in step 7 or in step 4 in clause 5.5.2.1.2. For Serving GW relocation, the Serving GW allocates DL TEIDs on S5/S8 even for non-accepted bearers and may include the PDN Charging Pause Support Indication. The PDN GW must acknowledge the request with the message Modify Bearer Response. In the case of Serving GW relocation, the PDN GW updates its context field and returns a Modify Bearer Response (Charging Id, MSISDN, PDN Charging Pause Enabled Indication (if PDN GW has chosen to enable the function), etc.) message to the Serving GW. The MSISDN is included if the PDN GW has it stored in its UE context. If location information change reporting is required and supported in the target SGSN, the PDN GW shall provide MS Info Change Reporting Action in the Modify Bearer Response. If PCC infrastructure is used, the PDN GW informs the PCRF about the change of, for example, the RAT type. If the Serving GW is relocated, the PDN GW shall send one or more "end marker" packets on the old path immediately after switching the path. The source Serving GW shall forwards the "end marker" packets to the source eNodeB. 9. The Serving GW (for Serving GW relocation this will be the Target Serving GW) acknowledges the user plane switch to the target SGSN via the message Modify Bearer Response (Cause, Serving GW Tunnel Endpoint Identifier for Control Plane, Serving GW Address for Control Plane, Protocol Configuration Options, MS Info Change Reporting Action). At this stage the user plane path is established for all EPS Bearer contexts between the UE, target RNC, target SGSN if Direct Tunnel is not used, Serving GW (for Serving GW relocation this will be the Target Serving GW) and PDN GW. If the Serving GW does not change, the Serving GW shall send one or more "end marker" packets on the old path immediately after switching the path. 10. When the UE recognises that its current Routing Area is not registered with the network, or when the UE's TIN indicates "GUTI", the UE initiates a Routing Area Update procedure with the target SGSN informing it that the UE is located in a new routing area. It is RAN functionality to provide the PMM-CONNECTED UE with Routing Area information. The target SGSN knows that an IRAT Handover has been performed for this UE as it received the bearer context(s) by handover messages and therefore the target SGSN performs only a subset of the RAU procedure, specifically it excludes the context transfer procedures between source MME and target SGSN. For a UE supporting CIoT EPS Optimisations, the UE uses the bearer status information in the RAU Accept to identify any non-transferred bearers that it shall locally release. 11. When the timer started at step 6 expires, the source MME sends a Release Resources message to the Source eNodeB. The Source eNodeB releases its resources related to the UE. When the timer started in step 6 expires and if the source MME received the Serving GW change indication in the Forward Relocation Response message, it deletes the EPS bearer resources by sending Delete Session Request (Cause, Operation Indication, Secondary RAT usage data) messages to the Source Serving GW. The operation indication flag is not set, that indicates to the Source Serving GW that the Source Serving GW shall not initiate a delete procedure towards the PDN GW. Secondary RAT usage data is included if it was received in step 3. The Source Serving GW acknowledges with Delete Session Response (Cause) messages. If ISR has been activated before this procedure, the cause indicates to the Source S-GW that the Source S-GW shall delete the bearer resources on the other old CN node by sending Delete Bearer Request message(s) to that CN node. 12. If indirect forwarding was used then the expiry of the timer at source MME started at step 6 triggers the source MME to send a Delete Indirect Data Forwarding Tunnel Request message to the S-GW to release the temporary resources used for indirect forwarding. 13. If indirect forwarding was used and the Serving GW is relocated, then the expiry of the timer at target SGSN started at step 6 triggers the target SGSN to send a Delete Indirect Data Forwarding Tunnel Request message to the target S-GW to release temporary resources used for indirect forwarding. | 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.5.2.1.3 |
3,666 | 6.38.2.3 Operation without 5G core network connectivity | The 5G system shall allow PIN Elements to communicate when there is no connectivity between a PIN Element with Gateway Capability and a 5G network. For a Public Safety PIN licensed spectrum may be used for PIN direct communications otherwise unlicensed spectrum shall be used. When a CPN has lost connectivity with the 5G network, the 5G system shall provide an operator-controlled mechanism to enable: - in the default configuration, or under certain conditions configured by the operator, the PRAS radio interface shall be deactivated; and - under certain other conditions configured by the operator, the CPN shall continue existing intra-CPN communication, as long as no interaction with the 5G network is needed (e.g. refreshing security keys). NOTE 1: The requirement above relates to intra-CPN operations and is subject to operator policy and control, under certain situations. NOTE 2: Setting up new intra-CPN or intra-PIN communication sessions without connection to the 5G network is only possible with non-3GPP provided credentials. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.38.2.3 |
3,667 | 12.1.2 Scenarios leading to overload | Reasons for these temporary overload cases can be many and various in an operational network, such as insufficient internal resource capacity of a GTP-C entity faced with a sudden burst of requests, e.g. after network failure/restart procedures affecting a large number of users, deficiency of a GTP-C entity component leading to a drastic reduction of the overall performances of the GTP-C entity. Examples of GTP-C signalling based scenarios which can cause GTP-C overload are: - a traffic flood resulting from the failure of a network element, inducing a signalling spike, e.g. when the network needs to re-establish the PDN connections affected by the failure of an EPC node; - a traffic flood resulting from a large number of users performing TAU/RAU or from frequent transitions between idle and connected mode; - an exceptional event locally generating a traffic spike, e.g. a large amount of calls (and dedicated bearers) being setup almost simultaneously upon a catastrophic event or an exceptional but predictable event (e.g. Christmas, New year) via a 3GPP access or a WLAN access; - Frequent RAT-reselection due to scattered non-3GPP (e.g. WiFi) coverage or massive mobility between 3GPP and non-3GPP coverage may potentially cause frequent or massive intersystem change activities, i.e. UEs trying to either create PDN connections over the new access or moving PDN connections between 3GPP and non-3GPP coverage. Besides, GTP-C load balancing based only on semi-static DNS weights can lead to a load imbalance and thus GTP-C signalling scenarios, such as those mentioned above, may result in an overload of the SGWs or PGWs with the highest load while there is still remaining capacity on other SGWs or PGWs. | 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.2 |
3,668 | 6.1.3.13 Handling of network rejection not due to based congestion control | The network may include a back-off timer value in a session management reject message to regulate the time interval at which the MS may retry the same procedure. For SM cause values other than #26 "insufficient resources", the network may also include the re-attempt indicator to indicate whether the MS is allowed to re-attempt the corresponding EPS session management procedure for the same in S1 mode after inter-system change. NOTE 1: If the network includes this back-off timer value, then the MS is blocked from sending another SM request for the same procedure for the same PLMN and combination for the specified duration. Therefore, the operator needs to exercise caution in determining the use of this timer value. NOTE 2: If the re-attempt indicator is not provided by the network, an MS registered in its HPLMN or in an EHPLMN (if the EHPLMN list is present) can use the configured SM_RetryAtRATChange value specified in the NAS configuration MO or in the USIM NASCONFIG file to derive the re-attempt indicator as specified in subclauses 6.1.3.1.3.3, 6.1.3.2.2.3, and 6.1.3.3.3.3. If re-attempt in S1 mode is allowed, the MS shall consider the back-off timer to be applicable only to the GPRS session management in A/Gb and Iu mode for the rejected session management procedure and the given PLMN and combination. If re-attempt in S1 mode is not allowed, the MS shall consider the back-off timer to be applicable to both NAS protocols, i.e. applicable to the GPRS session management in A/Gb and Iu mode for the rejected session management procedure and to the EPS session management in S1 mode for the corresponding EPS session management procedure and the given PLMN and combination. The APN of the PLMN and APN combination associated with the back-off timer is the APN sent by the MS when the PDN connection is established. If no APN is included in the ACTIVATE PDP CONTEXT REQUEST message, then the back-off timer is associated with the combination of the PLMN and no APN. For this purpose the MS shall memorize the APN provided to the network during the PDP context activation. The back-off timer associated with the combination of a PLMN with no APN will never be started due to any SM procedure related to an emergency PDN connection. If the back-off timer associated with the combination of a PLMN with no APN is running, it does not affect the ability of the MS to request an emergency PDN connection. The network may additionally indicate in the re-attempt indicator that a command to back-off is applicable not only for the PLMN in which the MS received the session management reject message, but for each PLMN included in the equivalent PLMN list at the time when the session management reject message was received. If the back-off timer is running or is deactivated for a given PLMN and APN combination, and the MS is an MS configured to use AC11 – 15 in selected PLMN, then the MS is allowed to initiate any GPRS session management procedure for this PLMN and APN combination. | 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.13 |
3,669 | 4.2.5a Radio Capabilities Signalling optimisation | Figure 4.2.5a-1 depicts the AMF to UCMF reference point and interface. Figure 4.2.5a-2 depicts the related interfaces in AMF and UCMF for the Radio Capabilities Signalling optimisation in the roaming architecture. Figure 4.2.5a-1: Radio Capability Signalling optimisation architecture NOTE: The AF in the VPLMN (i.e. the one having a relationship with the VPLMN NEF) is the one which provisions Manufacturer Assigned UE radio capability IDs in the VPLMN UCMF. RACS is a serving PLMN only feature (it requires no specific support in the roaming agreement with the UE HPLMN to operate). Figure 4.2.5a-2: Roaming architecture for Radio Capability Signalling optimisation | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2.5a |
3,670 | 16.3.4 AAA-Initiated PDP context termination | RADIUS is used as the protocol between the GGSN and an AAA server or proxy for applications (e.g. MMS) to deliver information related to GPRS user session. However some IP applications could need to interwork with the GGSN to terminate a particular PDP context. For this purpose, the AAA server or proxy may send a RADIUS Disconnect Request to the GGSN. As depicted in figure 25, the GGSN may react by deleting the corresponding PDP context or silently discard the Disconnect Request message. For more information on RADIUS Disconnect, see RFC 3576 [41]. If the GGSN deletes the corresponding PDP context, it need not wait for the DeletePDPContextResponse from the SGSN before sending the RADIUS DisconnectResponse to the AAA server. The Teardown-Indicator in the RADIUS Disconnect Request message indicates to the GGSN that all PDP contexts for this particular user and sharing the same user session shall be deleted. The PDP contexts belong to the same IP-CAN session are identified by the Acct-Session-Id. The Charging-Id contained in the Acct-Session-Id can be of any PDP context of the user. The GGSN is able to find out all the related PDP contexts sharing the same user session once it has found the exact PDP context from the Acct-Session-Id. If a user has the same user IP address for different sets of PDP contexts towards different networks, only the PDP contexts linked to the one identified by the Acct-Session-Id shall be deleted. Since the Charging-Id contained in the Acct-Session-Id is already sufficient to uniquely identify PDP context(s) for a user session on a GGSN, it has no impact if the user IP address is not known by the GGSN (e.g. in the case of transparent PPP IP-CAN sessions). In this case the user IP address in the Disconnect message should be set to zero (e.g. 0.0.0.0 for IPv4). NOTE: As showed on figure 25, the GGSN need not wait for the DeletePDPContextResponse from the SGSN to send the RADIUS DisconnectResponse to the AAA server. Figure 25: PDP Context deletion with RADIUS | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 16.3.4 |
3,671 | 16.7.5 Paging | The NG-RAN node may receive a paging message including the list of CAGs allowed for the UE, and whether the UE is allowed to access non-CAG cells. The NG-RAN node may use this information to avoid paging in cells on which the UE is not allowed to camp. For UEs in RRC_INACTIVE state, the NG-RAN node may page a neighbour NG-RAN node including the list of CAGs allowed for the UE, and whether the UE is allowed to access non-CAG cells. The neighbour NG-RAN node may use this information to avoid paging in cells on which the UE is not allowed to camp. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.7.5 |
3,672 | 6.1.3.1.1 Successful PDP context activation initiated by the mobile station | In order to request a PDP context activation, the MS sends an ACTIVATE PDP CONTEXT REQUEST message to the network, enters the state PDP-ACTIVE-PENDING and starts timer T3380. The message contains the selected NSAPI, PDP type number and requested QoS. The MS shall ensure that the selected NSAPI is not currently being used by another Session Management entity in the MS. The MS may indicate the support of Network Requested Bearer Control procedures, the support of local IP address in TFTs or the 3GPP PS data off UE status in the protocol configuration options information element. The MS supporting S1 mode shall indicate subscribed, interactive or background traffic class in the QoS requested. The MS not supporting S1 mode should indicate subscribed, interactive or background traffic class in the QoS requested. If there is a subscribed QoS profile available for the MS, the network may ignore the requested QoS and apply the subscribed QoS profile (see 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [74]). The MS shall set the request type to "initial request" when the MS is establishing connectivity to an additional PDN for the first time, i.e. when it is an initial attach to that PDN. The MS shall set the request type to "handover" when the connectivity to a PDN is established upon handover from a non-3GPP access network and the MS was connected to that PDN before the handover to the 3GPP access network. If the MS is establishing connectivity for emergency bearer services it shall set the request type to "emergency" and not include an APN in the ACTIVATE PDP CONTEXT REQUEST message. Upon receipt of the ACTIVATE PDP CONTEXT REQUEST message with request type set to "emergency" the network shall use the APN or the GGSN/PDN GW configured for emergency bearer services. Upon receipt of an ACTIVATE PDP CONTEXT REQUEST message with a PDP type number "IPv4v6 address" in the Requested PDP address information element, the network shall on sending the ACTIVATE PDP CONTEXT ACCEPT message: - include the SM cause information element with cause #50 "PDP type IPv4 only allowed", if the requested PDN connectivity is accepted with the restriction that only PDP type IPv4 is allowed; or - include the SM cause information element with cause #51 "PDP type IPv6 only allowed", if the requested PDN connectivity is accepted with the restriction that only PDP type IPv6 is allowed; or - include the SM cause information element with cause #52 "single address bearers only allowed", if the requested PDN connectivity is accepted with the restriction that only single IP version bearers are allowed. If the MS receives the SM cause value #50 "PDP type IPv4 only allowed" or #51 "PDP type IPv6 only allowed" in the ACTIVATE PDP CONTEXT ACCEPT message, the MS shall not subsequently request another PDP context to get a PDP Type different from the one allowed by the network, until: - all PDP contexts to the given APN are deactivated either explicitly between the MS and the network, i.e. PDP context deactivation procedure, or implicitly (without peer to peer signalling between the MS and the network) as a result of: i) PDP context synchronization during routing area updating or service request procedure; ii) PDP context deactivation initiated by the network, iii) detach from GPRS services; or; iv) a service request procedure is rejected with a cause which results in the MS entering state GMM-DEREGISTERED; or - the PDP type which is used to access to the APN is changed. NOTE 1: Request to send another ACTIVATE PDP CONTEXT REQUEST message with a specific PDP type comes from upper layers. If the MS receives the SM cause value #52 "single address bearers only allowed" in the ACTIVATE PDP CONTEXT ACCEPT message, the MS should subsequently request another PDP context for the other PDP type to the same APN with a single address PDP type (IPv4 or IPv6) other than the one already activated. NOTE 2: If the MT and TE are separated, the MS might not be able to use SM cause #52 "single address bearers only allowed" as a trigger for activating a second single-IP-stack PDP context. Upon receipt of an ACTIVATE PDP CONTEXT REQUEST message, the network selects a radio priority level based on the QoS negotiated and may reply with an ACTIVATE PDP CONTEXT ACCEPT message. If the ACTIVATE PDP CONTEXT REQUEST message included a low priority indicator set to "MS is configured for NAS signalling low priority", the network shall store the NAS signalling low priority indication within the default PDP context. If the network receives an ACTIVATE PDP CONTEXT REQUEST message with the same combination of APN and PDP type as an already existing PDN connection, and multiple PDN connections for a given APN are allowed, the network may retain the existing PDP contexts and proceed with the requested PDP context activation procedure. Upon receipt of the message ACTIVATE PDP CONTEXT ACCEPT the MS shall stop timer T3380, shall enter the state PDP-ACTIVE. If the protocol configuration options information element is present, the network may indicate the Bearer Control Mode that shall be used, the network support of local IP address in TFTs, or the 3GPP PS data off support indication. If the protocol configuration options information element is not present or the Selected Bearer Control Mode parameter is not present in the protocol configuration options information element, the MS shall apply Bearer Control Mode 'MS only' for all active PDP contexts sharing the same PDP Address and APN. If the 3GPP PS data off UE status is "activated", the MS behaves as described in subclause 4.7.1.10. If the offered QoS parameters received from the network differ from the QoS requested by the MS, the MS shall either accept the negotiated QoS or initiate the PDP context deactivation procedure. If the Request type information element is not present, the network shall assume that the request type is "initial request". NOTE 3: If the MS requested a value for a QoS parameter that is not within the range specified by 3GPP TS 23.107[ Quality of Service (QoS) concept and architecture ] [81], the network should negotiate the parameter to a value that lies within the specified range. If the lower layers provide a L-GW Transport Layer Address value together with the ACTIVATE PDP CONTEXT REQUEST message and a PDN connection is established as a LIPA PDN connection due to the ACTIVATE PDP CONTEXT REQUEST message, then the SGSN shall store the L-GW Transport Layer Address value as the GGSN address in the PDP context of the LIPA PDN connection. If connectivity with the requested APN is accepted and the network considers this PDN connection a LIPA PDN connection, then subject to operator policy the SGSN shall include in the ACTIVATE PDP CONTEXT ACCEPT message the Connectivity type IE indicating "the PDN connection is considered a LIPA PDN connection". If the lower layers provide a SIPTO L-GW Transport Layer Address value identifying a L-GW together with the ACTIVATE PDP CONTEXT REQUEST message and a PDN connection is established as a SIPTO at the local network PDN connection due to the ACTIVATE PDP CONTEXT REQUEST message, then the SGSN shall store the SIPTO L-GW Transport Layer Address value as the P-GW address in the PDP context of the SIPTO at the local network PDN connection. If the lower layers provide a LHN-ID value together with the ACTIVATE PDP CONTEXT REQUEST message and a PDN connection is established as a SIPTO at the local network PDN connection due to the ACTIVATE PDP CONTEXT REQUEST message, then the SGSN shall store the LHN-ID value in the PDP context of the SIPTO at the local network PDN connection. NOTE 4: The receipt of a LHN-ID value during the establishment of the PDN connection, during routing area updating procedure or during inter-SGSN handover can be used as an indication by the SGSN that the SIPTO at the local network PDN connection is established to a stand-alone GW (see 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [74]). In A/Gb mode, the MS shall initiate establishment of the logical link for the LLC SAPI indicated by the network with the offered QoS and selected radio priority level if no logical link has been already established for that SAPI. If the offered QoS parameters received from the network differ from the QoS requested by the MS, the MS shall either accept the negotiated QoS or initiate the PDP context deactivation procedure. If the LLC SAPI indicated by the network can not be supported by the MS, the MS shall initiate the PDP context deactivation procedure. In Iu mode, both the network and the MS shall store the LLC SAPI and the radio priority in the PDP context. If a Iu mode to A/Gb mode system change is performed, the new SGSN shall initiate establishment of the logical link using the negotiated QoS profile, the negotiated LLC SAPI, and selected radio priority level stored in the PDP context as in a A/Gb mode to A/Gb mode Routing Area Update. An MS, which is capable of operating in A/Gb mode, shall use a valid LLC SAPI, while an MS which is not capable of operating in A/Gb mode shall indicate the LLC SAPI value as "LLC SAPI not assigned" in order to avoid unnecessary value range checking and any other possible confusion in the network. When the MS uses a valid LLC SAPI, the network shall return a valid LLC SAPI. The network shall return the "LLC SAPI not assigned" value only when the MS uses the "LLC SAPI not assigned" value. NOTE 5: The radio priority level and the LLC SAPI parameters, though not used in Iu mode, shall be included in the messages, in order to support handover between Iu mode and A/Gb mode networks. If a WLAN offload indication information element is included in the ACTIVATE PDP CONTEXT ACCEPT message, the MS shall store the WLAN offload acceptability values for this PDN connection and use the UTRAN offload acceptability value to determine whether this PDN connection is offloadable to WLAN or not. At inter-system change from Iu mode to A/Gb mode, SM shall locally deactivate the active PDP context(s) if SM does not have the following parameters: - LLC SAPI; and - radio priority. Upon receipt of the ACTIVATE PDP CONTEXT ACCEPT message with the Connectivity type IE indicating "the PDN connection is considered a LIPA PDN connection", the MS provides an indication to the upper layers that the connectivity is provided by a LIPA PDN connection. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.1.3.1.1 |
3,673 | I.9.2.1 Requirements | The primary authentication shall be performed before UE onboarding is allowed. For primary authentication, the UE shall use Default UE credentials for primary authentication. Credentials or means used to authenticate the UE based on Default UE credentials for primary authentication may be stored within the ON-SNPN or in a Default Credentials Server (DCS) that is external to the ON-SNPN. The UE shall use Onboarding SUPI and Onboarding SUCI as specified in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [35] during Onboarding Registration. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | I.9.2.1 |
3,674 | 17.2 MBMS service registration / de-registration | The MBMS service registration of the GGSN at the BM-SC shall be performed after authorisation of the first user on a particular GGSN, for a particular multicast MBMS Bearer service. The MBMS service de-registration of the GGSN shall be performed when the last user leaves a particular GGSN, for a particular multicast MBMS bearer service. The MBMS de-registration procedure shall be initiated by BM-SC when the specific multicast MBMS service is terminated. The GGSN shall support pre-configuration of a BM-SC or Gmb proxy server for registration/de-registration purposes. The GGSN may support a list of pre-configured BM-SC servers based on the MBMS bearer service requested for bearer registration purposes. | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 17.2 |
3,675 | 5.3.5.18.3 LTM candidate configuration addition/modification | The UE shall: 1> for each ltm-CandidateId value in the ltm-CandidateToAddModList: 2> if the current VarLTM-Config includes an LTM-Candidate with the ltm-CandidateId value: 3> replace the LTM-Candidate within VarLTM-Config in accordance with the received LTM-Candidate; 2> else: 3> add the received LTM-Candidate to VarLTM-Config; 2> if the received LTM-Candidate includes ltm-DL-OrJointTCI-StateToReleaseList: 3> for each tci-StateId in the ltm-DL-OrJointTCI-StateToReleaseList: 4> if the current VarLTM-Config includes a CandidateTCI-State within an LTM-Candidate with the ltm-CandidateId value that is associated with the tci-StateId value: 5> remove the entry related to CandidateTCI-State within the LTM-Candidate from VarLTM-Config. 2> if the received LTM-Candidate includes ltm-DL-OrJointTCI-StateToAddModList: 3> for each tci-StateId in the ltm-DL-OrJointTCI-StateToAddModList: 4> if the current VarLTM-Config includes a CandidateTCI-State within an LTM-Candidate with the ltm-CandidateId value that is associated with the tci-StateId value: 5> replace the entry related to CandidateTCI-State within the LTM-Candidate from VarLTM-Config. 4> else: 5> add the received CandidateTCI-State within LTM-Candidate to VarLTM-Config; 2> if the received LTM-Candidate includes ltm-UL-TCI-StatesToReleaseList: 3> for each tci-StateId in the ltm-UL-TCI-StatesToReleaseList: 4> if the current VarLTM-Config includes an CandidateTCI-UL-State within an LTM-Candidate with the ltm-CandidateId value that is associated with the tci-StateId value: 5> remove the entry related to CandidateTCI-UL-State within the LTM-Candidate from VarLTM-Config. 2> if the received LTM-Candidate includes ltm-UL-TCI-StatesToAddModList: 3> for each tci-StateId in the ltm-UL-TCI-StatesToAddModList: 4> if the current VarLTM-Config includes an CandidateTCI-UL-State within an LTM-Candidate with the ltm-CandidateId value that is associated with the tci-StateId value: 5> replace the entry related to CandidateTCI-UL-State within the LTM-Candidate from VarLTM-Config. 4> else: 5> add the received CandidateTCI-UL-State within LTM-Candidate to VarLTM-Config. 2> if the received LTM-Candidate includes ltm-nzp-CSI-RS-ResourceToReleaseList: 3> for each nzp-CSI-RS-ResourceId in the ltm-nzp-CSI-RS-ResourceToReleaseList: 4> if the current VarLTM-Config includes an NZP-CSI-RS-Resource within an LTM-Candidate with the ltm-CandidateId value that is associated with the nzp-CSI-RS-ResourceId value: 5> remove the entry related to NZP-CSI-RS-Resource within the LTM-Candidate from VarLTM-Config. 2> if the received LTM-Candidate includes ltm-nzp-CSI-RS-ResourceToAddModList: 3> for each nzp-CSI-RS-ResourceId in the ltm-nzp-CSI-RS-ResourceToReleaseList: 4> if the current VarLTM-Config includes an NZP-CSI-RS-Resource within an LTM-Candidate with the ltm-CandidateId value that is associated with the nzp-CSI-RS-ResourceId value: 5> replace the entry related to NZP-CSI-RS-Resource within the LTM-Candidate from VarLTM-Config. 4> else: 5> add the received NZP-CSI-RS-Resource within LTM-Candidate to VarLTM-Config. 2> if the received LTM-Candidate includes ltm-nzp-CSI-RS-ResourceSetToReleaseList: 3> for each nzp-CSI-RS-ResourceSetId in the ltm-nzp-CSI-RS-ResourceSetToReleaseList: 4> if the current VarLTM-Config includes an NZP-CSI-RS-ResourceSet within an LTM-Candidate with the ltm-CandidateId value that is associated with the nzp-CSI-RS-ResourceSetId value: 5> remove the entry related to NZP-CSI-RS-ResourceSet within the LTM-Candidate from VarLTM-Config. 2> if the received LTM-Candidate includes ltm-nzp-CSI-RS-ResourceSetToAddModList: 3> for each nzp-CSI-RS-ResourceSetId in the ltm-nzp-CSI-RS-ResourceSetToReleaseList: 4> if the current VarLTM-Config includes an NZP-CSI-RS-ResourceSet within an LTM-Candidate with the ltm-CandidateId value that is associated with the nzp-CSI-RS-ResourceSetId value: 5> replace the entry related to NZP-CSI-RS-ResourceSet within the LTM-Candidate from VarLTM-Config. 4> else: 5> add the received NZP-CSI-RS-ResourceSet within LTM-Candidate to VarLTM-Config. 2> if the received LTM-Candidate includes pathlossReferenceRS-ToReleaseList: 3> for each pathlossReferenceRS-Id in the pathlossReferenceRS-ToReleaseList: 4> if the current VarLTM-Config includes an PathlossReferenceRS within an LTM-Candidate with the ltm-CandidateId value that is associated with the pathlossReferenceRS-Id value: 5> remove the entry related to PathlossReferenceRS within the LTM-Candidate from VarLTM-Config. 2> if the received LTM-Candidate includes pathlossReferenceRS-ToAddModList: 3> for each pathlossReferenceRS-Id in the pathlossReferenceRS-ToAddModList: 4> if the current VarLTM-Config includes an PathlossReferenceRS within an LTM-Candidate with the ltm-CandidateId value that is associated with the pathlossReferenceRS-Id value: 5> replace the entry related to PathlossReferenceRS within the LTM-Candidate from VarLTM-Config. 4> else: 5> add the received PathlossReferenceRS within LTM-Candidate to VarLTM-Config. 2> if the LTM-Candidate with the received ltm-CandidateId value includes ltm-UE-MeasuredTA-ID: 3> if the value of ltm-UE-MeasuredTA-ID is equal to the value of ltm-ServingCellUE-MeasuredTA-ID within VarLTM-ServingCellUE-MeasuredTA-ID: 4> inform lower layers that UE is configured with UE-based TA measurements if an LTM cell switch is executed for this LTM candidate configuration; | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.5.18.3 |
3,676 | 6.3.2D UE Minimum output power for ProSe | When UE is configured for E-UTRA ProSe sidelink transmissions non-concurrent with E-UTRA uplink transmissions for E-UTRA ProSe operating bands specified in Table 5.5D-1, the requirements in subclause 6.3.2 apply for ProSe transmission. When UE is configured for simultaneous E-UTRA ProSe sidelink and E-UTRA uplink transmissions for inter-band E-UTRA ProSe / E-UTRA bands specified in Table 5.5D-2, the requirements in subclause 6.3.2A apply as specified for the corresponding inter-band aggregation with uplink assigned to two bands. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.3.2D |
3,677 | 16.3.4.2 AMF and NW Slice Selection | RAN selects the AMF based on a Temp ID or NSSAI provided by the UE. Figure 16.3.4.2-1: AMF selection In case a Temp ID is not available, the NG-RAN uses the NSSAI provided by the UE at RRC connection establishment to select the appropriate AMF (the information is provided after MSG3 of the random access procedure). If such information is also not available, the NG-RAN routes the UE to one of the configured default AMF(s). The NG-RAN uses the list of supported S-NSSAI(s) previously received in the NG Setup Response message when selecting the AMF with the NSSAI. This list may be updated via the AMF Configuration Update message. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.3.4.2 |
3,678 | 4.7.3.1.4 GPRS attach not accepted by the network | If the attach request cannot be accepted by the network, an ATTACH REJECT message is transferred to the MS. The MS receiving the ATTACH REJECT message containing a reject cause other than GMM cause value #25 or the message is integrity protected, shall stop the timer T3310 and for all causes except #7, #12, #14, #15, #22 and #25 deletes the list of "equivalent PLMNs". If the ATTACH REJECT message containing GMM cause value cause #25 was received without integrity protection, then the MS shall discard the message. If the attach request is rejected due to NAS level mobility management congestion control, the network shall set the GMM cause value to #22 "congestion" and assign a back-off timer T3346. The MS shall then take one of the following actions depending upon the reject cause: # 3 (Illegal MS); # 6 (Illegal ME); The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to subclause 4.1.3.2) and shall delete any P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number. The new GMM state is GMM-DEREGISTERED.NO-IMSI. The SIM/USIM shall be considered as invalid for GPRS services until switching off or the SIM/USIM is removed or the timer T3245 expires as described in subclause 4.1.1.6. If the message has been successfully integrity checked by the lower layers and the MS maintains a counter for "SIM/USIM considered invalid for GPRS services", then the MS shall set this counter to MS implementation-specific maximum value. If the MS is IMSI attached, the MS shall in addition set the update status to U3 ROAMING NOT ALLOWED, shall delete any TMSI, LAI and ciphering key sequence number. If the MS is operating in MS operation mode A and an RR connection exists, the MS shall abort the RR connection, unless an emergency call is ongoing. The SIM/USIM shall be considered as invalid also for non-GPRS services until switching off or the SIM/USIM is removed. If the message has been successfully integrity checked by the lower layers and the MS maintains a counter for "SIM/USIM considered invalid for non-GPRS services", then the MS shall set this counter to MS implementation-specific maximum value. If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, GUTI, last visited registered TAI, TAI list and KSI as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when the attach procedure is rejected with the EMM cause with the same value. # 7 (GPRS services not allowed); The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to subclause 4.1.3.2) and shall delete any P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number. The SIM/USIM shall be considered as invalid for GPRS services until switching off or the SIM/USIM is removed. The new state is GMM-DEREGISTERED. If the message has been successfully integrity checked by the lower layers and the MS maintains a counter for "SIM/USIM considered invalid for GPRS services", then the MS shall set this counter to MS implementation-specific maximum value. NOTE 1: Optionally the MS starts the timer T3340 as described in subclause 4.7.1.9 If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, GUTI, last visited registered TAI, TAI list and KSI as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when the attach procedure is rejected with the EMM cause with the same value. # 8 (GPRS services and non-GPRS services not allowed); The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to subclause 4.1.3.2) and shall delete any P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number. The new GMM state is GMM-DEREGISTERED.NO-IMSI. NOTE 2: Optionally the MS starts the timer T3340 as described in subclause 4.7.1.9. The MS shall set the update status to U3 ROAMING NOT ALLOWED, shall delete any TMSI, LAI and ciphering key sequence number. If the MS is operating in MS operation mode A and an RR connection exists, the MS shall abort the RR connection, unless an emergency call is ongoing. The SIM/USIM shall be considered as invalid for GPRS and non-GPRS services until switching off or the SIM/USIM is removed. If the message has been successfully integrity checked by the lower layers and the MS maintains a counter for "SIM/USIM considered invalid for GPRS services", then the MS shall set this counter to MS implementation-specific maximum value. If the message has been successfully integrity checked by the lower layers and the MS maintains a counter for "SIM/USIM considered invalid for non-GPRS services", then the MS shall set this counter to MS implementation-specific maximum value. If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, GUTI, last visited registered TAI, TAI list and KSI as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when the attach procedure is rejected with the EMM cause with the same value. # 11 (PLMN not allowed); The MS shall delete any RAI, P-TMSI, P-TMSI signature, and GPRS ciphering key sequence number stored, shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to subclause 4.1.3.2), shall reset the GPRS attach attempt counter and shall change to state GMM-DEREGISTERED. The MS shall store the PLMN identity in the "forbidden PLMN list" and if the MS is configured to use timer T3245 (see 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]) then the MS shall start timer T3245 and proceed as described in subclause 4.1.1.6. If the message has been successfully integrity checked by the lower layers and the MS maintains a PLMN-specific attempt counter for that PLMN, then the MS shall set this counter to the MS implementation-specific maximum value. The MS shall start timer T3340 as described in subclause 4.7.1.9. If no RR connection exists, the MS shall perform the following additional actions immediately. If the MS is operating in MS operation mode A and an RR connection exists, the MS shall perform these actions when the RR connection is subsequently released: - If the MS is IMSI attached, the MS shall set the update status to U3 ROAMING NOT ALLOWED, shall delete any TMSI, LAI and ciphering key sequence number and shall reset the location update attempt counter. The new MM state is MM IDLE. - The MS shall perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14]. An MS in GAN mode shall request a PLMN list in GAN (see 3GPP TS 44.318[ None ] [76b]) prior to perform a PLMN selection from this list according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14]. If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, GUTI, last visited registered TAI, TAI list, KSI and attach attempt counter as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when attach procedure is rejected with the EMM cause with the same value. # 12 (Location area not allowed); The MS shall delete any RAI, P-TMSI, P-TMSI signature and GPRS ciphering key sequence number, shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to clause 4.1.3.2) and shall reset the GPRS attach attempt counter. The state is changed to GMM-DEREGISTERED.LIMITED-SERVICE. The mobile station shall store the LAI in the list of "forbidden location areas for regional provision of service". The MS shall start timer T3340 as described in subclause 4.7.1.9. If no RR connection exists, the MS shall perform the following additional actions immediately. If the MS is operating in MS operation mode A and an RR connection exists, the MS shall perform these actions when the RR connection is subsequently released: - If the MS is IMSI attached, the MS shall set the update status to U3 ROAMING NOT ALLOWED, shall delete any TMSI, LAI and ciphering key sequence number and shall reset the location update attempt counter. The new MM state is MM IDLE. - The MS shall perform a cell selection according to 3GPP TS 43.022[ None ] [82] and 3GPP TS 25.304[ None ] [98]. NOTE 3: The cell selection procedure is not applicable for an MS in GAN mode. If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, GUTI, last visited registered TAI, TAI list, KSI and attach attempt counter as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when the attach procedure is rejected with the EMM cause with the same value. # 13 (Roaming not allowed in this location area); The MS shall delete any RAI, P-TMSI, P-TMSI signature and GPRS ciphering key sequence number, shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to clause 4.1.3.2) and shall reset the GPRS attach attempt counter. The state is changed to GMM-DEREGISTERED.LIMITED-SERVICE or optionally to GMM-DEREGISTERED.PLMN-SEARCH. The MS shall store the LAI in the list of "forbidden location areas for roaming". The MS shall start timer T3340 as described in subclause 4.7.1.9. If no RR connection exists, the MS shall perform the following additional actions immediately. If the MS is operating in MS operation mode A and an RR connection exists, the MS shall perform these actions when the RR connection is subsequently released: - If the MS is IMSI attached, the MS shall set the update status to U3 ROAMING NOT ALLOWED, shall delete any TMSI, LAI and ciphering key sequence number and shall reset the location update attempt counter. The new MM state is MM IDLE. - The MS shall perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14]. An MS in GAN mode shall request a PLMN list in GAN (see 3GPP TS 44.318[ None ] [76b]) prior to perform a PLMN selection from this list according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14]. If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, GUTI, last visited registered TAI, TAI list, KSI and attach attempt counter as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when the attach procedure is rejected with the EMM cause with the same value. # 14 (GPRS services not allowed in this PLMN); The MS shall delete any RAI, P-TMSI, P-TMSI signature, and GPRS ciphering key sequence number stored, shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to subclause 4.1.3.2) , shall reset the GPRS attach attempt counter and shall change to state GMM-DEREGISTERED. The MS shall store the PLMN identity in the "forbidden PLMNs for GPRS service" list and if the MS is configured to use timer T3245 (see 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]) then the MS shall start timer T3245 and proceed as described in subclause 4.1.1.6. A GPRS MS operating in MS operation mode C shall perform a PLMN selection instead of a cell selection. If the message has been successfully integrity checked by the lower layers and the MS maintains a PLMN-specific PS-attempt counter for that PLMN, then the MS shall set this counter to the MS implementation-specific maximum value. A GPRS MS operating in MS operation mode A or B in network operation mode II, is still IMSI attached for CS services in the network. As an implementation option, a GPRS MS operating in operation mode A or B may perform the following additional action. If no RR connection exists the MS may perform the action immediately. If the MS is operating in MS operation mode A and an RR connection exists, the MS may only perform the action when the RR connection is subsequently released: - The MS may perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14]. If an MS in GAN mode performs a PLMN selection, it shall request a PLMN list in GAN (see 3GPP TS 44.318[ None ] [76b]) prior to perform a PLMN selection from this list according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14]. The MS shall not perform the optional PLMN selection in the case where the PLMN providing this reject cause is: - On the "User Controlled PLMN Selector with Access Technology" list; - On the "Operator Controlled PLMN Selector with Access Technology" list; - On the "PLMN Selector" list for an MS using a SIM/USIM without access technology information storage (i.e. the "User Controlled PLMN Selector with Access Technology" and the "Operator Controlled PLMN Selector with Access Technology" data files are not present); or - A PLMN identified as equivalent to any PLMN, within the same country, contained in the lists above. If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, GUTI, last visited registered TAI, TAI list, KSI and attach attempt counter as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when the attach procedure is rejected with the EMM cause with the same value. # 15 (No Suitable Cells In Location Area); The MS shall delete any RAI, P-TMSI, P-TMSI signature and GPRS ciphering key sequence number, shall set the GPRS update status to GU3 ROAMING NOT ALLOWED(and shall store it according to clause 4.1.3.2) and shall reset the GPRS attach attempt counter. The state is changed to GMM-DEREGISTERED.LIMITED-SERVICE. The MS shall store the LAI in the list of "forbidden location areas for roaming". The MS shall start timer T3340 as described in subclause 4.7.1.9. If no RR connection exists, the MS shall perform the following additional actions immediately. If the MS is operating in MS operation mode A and an RR connection exists, the MS shall perform these actions when the RR connection is subsequently released: - If the MS is IMSI attached, the MS shall set the update status to U3 ROAMING NOT ALLOWED, shall delete any TMSI, LAI and ciphering key sequence number and shall reset the location update attempt counter. The new MM state is MM IDLE. - The MS shall search for a suitable cell in another location area or a tracking area according to 3GPP TS 43.022[ None ] [82] and 3GPP TS 25.304[ None ] [98] or 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [121]. NOTE 4: The cell selection procedure is not applicable for an MS in GAN mode. If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, GUTI, last visited registered TAI, TAI list, KSI and attach attempt counter as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when the attach procedure is rejected with the EMM cause with the same value. # 22 (Congestion); If the T3346 value IE is present in the ATTACH REJECT message and the value indicates that this timer is neither zero nor deactivated, the MS shall proceed as described below, otherwise it shall be considered as an abnormal case and the behaviour of the MS for this case is specified in subclause 4.7.3.1.5. The MS shall abort the attach procedure, reset the GPRS attach attempt counter, set the GPRS update status to GU2 NOT UPDATED and enter state GMM-DEREGISTERED.ATTEMPTING-TO-ATTACH. The MS shall stop timer T3346 if it is running. If the ATTACH REJECT message is integrity protected, the MS shall start timer T3346 with the value provided in the T3346 value IE. If the ATTACH REJECT message is not integrity protected, the MS shall start timer T3346 with a random value from the default range specified in table 11.3a. The MS stays in the current serving cell and applies the normal cell reselection process. The attach procedure is started if still needed when timer T3346 expires or is stopped. If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, and attach attempt counter as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when the attach procedure is rejected with the EMM cause with the same value. # 25 (Not authorized for this CSG); Cause #25 is only applicable in UTRAN Iu mode and when received from a CSG cell. Other cases are considered as abnormal cases and the specification of the mobile station behaviour is given in subclause 4.7.3.1.5. The MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED (and shall store it according to subclause 4.1.3.2), reset the GPRS attach attempt counter and enter the state GMM-DEREGISTERED.LIMITED-SERVICE. If the CSG ID and associated PLMN identity of the cell where the MS has sent the ATTACH REQUEST message are contained in the Allowed CSG list stored in the MS, the MS shall remove the entry corresponding to this CSG ID and associated PLMN identity from the Allowed CSG list. If the CSG ID and associated PLMN identity of the cell where the MS has sent the ATTACH REQUEST message are contained in the Operator CSG list stored in the MS, the MS shall proceed as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14] subclause 3.1A. The MS shall start timer T3340 as described in subclause 4.7.1.9. The MS shall search for a suitable cell according to 3GPP TS 43.022[ None ] [82] and 3GPP TS 25.304[ None ] [98]. If S1 mode is supported in the MS, the MS shall handle the EMM parameters EMM state, EPS update status, GUTI, last visited registered TAI, TAI list, KSI and attach attempt counter as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when the attach procedure is rejected with the EMM cause with the same value. Other values are considered as abnormal cases. The specification of the MS behaviour in those cases is specified in subclause 4.7.3.1.5. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.3.1.4 |
3,679 | 5.3.1.2.1 IPv4 address allocation via default bearer activation and release via PDN connection release | An IPv4 address may be provided to the UE as part of the default bearer activation and the IPv4 address is released when PDN connection associated with the IPv4 address is released. When the PLMN allocates an IPv4 address, it is the PDN GW responsibility to allocate and release the IPv4 address. The PDN GW may use an internal IPv4 address pool in this case. The PDN GW allocates an IPv4 address upon default bearer activation and it releases the IPv4 address upon PDN connection release associated with the IPv4 address for a given UE. NOTE: If the PDN type is IPv4v6, when the PDN Connection is released, the IPv6 address is also released. When an IPv4 address is allocated from an external PDN, it is the PDN GW responsibility to obtain the IPv4 address from the external PDN, and to allocate, renew and release the IPv4 address. The PDN GW may use DHCPv4 to obtain, renew and release the IPv4 address from the external PDN. If RADIUS or Diameter is used towards the external PDN, as described in TS 29.061[ Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) ] [38], the IP address can be obtained, renewed and released as part of these procedures. If DHCPv4 is used, the PDN GW functions as a DHCPv4 Client. If RADIUS is used, the PDN GW functions as a RADIUS Client. If Diameter is used, the PDN GW functions as a Diameter Client. After releasing the IPv4 address, the PDN GW should not assign that IPv4 address to other user immediately. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.3.1.2.1 |
3,680 | 16.10.6.7 Shared processing for MBS broadcast and unicast reception | If the UE in RRC_CONNECTED state is receiving or interested to receive an MBS broadcast service from a non-serving cell as described in TS 38.306[ NR; User Equipment (UE) radio access capabilities ] [11] , the UE may use MBS Interest Indication message to inform the serving gNB about the parameters used for the non-serving cell broadcast reception as described in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12]. The gNB may enable the sending of the MBS Interest Indication by including an indication in SIB1. The UE may indicate to the serving cell the UE capability for receiving MBS broadcast service from a non-serving cell. It is up to gNB implementation to consider the MBS Interest Indication and the UE capability for receiving MBS broadcast service from a non-serving cell, if indicated, when scheduling the UE. In case the UE only reports the frequency for broadcast service reception from the non-serving cell in MBS Interest Indication due to some parameters (e.g., SCS, bandwidth) not being available, the UE may transmit updated MBS Interest Indication once the parameters are available to the UE. It is up to network implementation on how to enable the UE to acquire these parameters from the non-serving cell. 16.10.6.8 Support of Resource Sharing across multiple Broadcast MBS sessions in RAN Sharing Scenario NGAP supports resource sharing efficient scheme for broadcast delivery in RAN sharing. Such scheme enables the gNB to identify broadcast MBS sessions from different PLMNs providing identical content. The identification is based on information provided by the involved 5GCs in the Associated Session ID as specified in TS 23.247[ Architectural enhancements for 5G multicast-broadcast services ] [45]. If in the MBS Broadcast Setup Request message an Associated Session ID is received from a 5GC participating in RAN sharing, the gNB uses it to determine whether MBS Session resources can be shared with a broadcast MBS session(s) associated with the same Associated Session ID requested from another 5GC participating in RAN sharing. The identification of MBS Broadcast Sessions providing identical content may also be based on implementation specific configuration as specified in TS 23.247[ Architectural enhancements for 5G multicast-broadcast services ] [45]. The gNB applying this resource efficiency scheme: - may decide whether NG-U resources are established towards all involved 5GCs or only some of them; - resolves different QoS requirements or different S-NSSAIs received from the participating 5GCs in an implementation specific way. The gNB may also trigger the NGAP Broadcast Session Transport procedure towards one 5GC participating in RAN sharing to set up NG-U resources to maintain NG-U connectivity as specified in TS 23.247[ Architectural enhancements for 5G multicast-broadcast services ] [45]. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.10.6.7 |
3,681 | 9.2.4.2 TDD | The following requirements apply to UE Category ≥2. For the parameters specified in table 9.2.4.2-1, and using the downlink physical channels specified in Tables C.3.4-1 and C.3.4-2, the reported offset level of the wideband spatial differential CQI for codeword #1 (Table 7.2-2 in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [6]) shall be used to determine the wideband CQI index for codeword #1 as wideband CQI1 = wideband CQI0 – Codeword 1 offset level The wideband CQI1 shall be within the set {median CQI1 -1, median CQI1, median CQI1 +1} for more than 90% of the time, where the resulting wideband values CQI1 shall be used to determine the median CQI values for codeword #1. For both codewords #0 and #1, the PDSCH BLER using the transport format indicated by the respective median CQI0 – 1 and median CQI1 – 1 shall be less than or equal to 0.1. Furthermore, for both codewords #0 and #1, the PDSCH BLER using the transport format indicated by the respective median CQI0 + 1 and median CQI1 + 1 shall be greater than or equal to 0.1. Table 9.2.4.2-1: PUCCH 1-1 static test (TDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.2.4.2 |
3,682 | 6.3.4 ON/OFF time mask 6.3.4.1 General ON/OFF time mask | The General ON/OFF time mask defines the observation period between Transmit OFF and ON power and between Transmit ON and OFF power. ON/OFF scenarios include; the beginning or end of DTX, measurement gap, contiguous, and non contiguous transmission The OFF power measurement period is defined in a duration of at least one subframe, or one slot or one subslot for sTTI, excluding any transient periods. The ON power is defined as the mean power over one subframe, or one slot or one subslot for sTTI, excluding any transient period. There are no additional requirements on UE transmit power beyond that which is required in subclause 6.2.2 and subclause 6.6.2.3 The transient period length shall be no longer than the specified value in Table 6.3.4.1-1. Table 6.3.4.1-1: Transient period length depending on transmission length Figure 6.3.4.1-1: General ON/OFF time mask for subframe TTI and for Frame Structure Type 1 and Frame Structure Type 2 For Frame Structure Type 3 the general ON/OFF mask is specified in 6.3.4.1-1A with the PUSCH starting position modified by relative to the start of the sub-frame as indicated in the associated DCI, where and the basic time unit are specified in [4]. At the end of the sub-frame and with denoting the duration of the last SC-FDMA symbol when the bit indicating the PUSCH ending symbol in the associated DCI has value ‘0’ and ‘1’ as specified in [5], respectively; the OFF power requirement applies 5 s after the end of the last symbol transmitted. Figure 6.3.4.1-1A: General ON/OFF time mask for subframe TTI and for Frame Structure Type 3 Figure 6.3.4.1-1B: General ON/OFF time mask for sTTI and for Frame Structure Type 1 and Frame Structure Type 2 | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.3.4 |
3,683 | 4.17.12.3 Binding created as part of service request | If the NF service consumer can also be as a NF service producer for later communication from the contacted producer, a service request sent to the producer may include binding indication. NOTE: This clause only applies to an AMF, V-SMF or I-SMF as NF service consumer sending requests to an SMF and to an AMF as NF service consumer sending requests to an I-SMF or V-SMF, in step 1 unless further usage has been defined in stage 3. Implicit subscriptions are not described in this clause. Figure 4.17.12.3-1: Binding created as part of service request 1. Instance A, as an NF service consumer sends a service request using either Direct Communication or Indirect communication via SCP and Instance B is selected as NF service producer. If Instance A can also be NF service producer for later communication for the concerned data context, it may include binding indication referring to NF service instance, NF service set, NF instance or NF Set as specified in Table 6.3.1.0-1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] in the request sent to the NF service producer; the binding indication shall be associated with an applicability indicating "other service" and include the service name. In this case, if indirect communication is used, the SCP sends to the Instance B the service request including the binding indication. 2. Instance B as the NF service producer sends a response to the NF service consumer. 3. When Instance B as NF service consumer needs to invoke the service provided by Instance A, Instance B sends a request using the binding indication received in step 1 as described in Steps 3-4 in Figure 4.17.12.2-1 with the following difference: - Based on the received binding indication, if delegated discovery is not used, the Instance B may need to discover the corresponding endpoint address of the Instance A. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.17.12.3 |
3,684 | 5.15.11.2.2 Hierarchical NSAC architecture | The main differences between the NSACFs deployed in a non-Hierarchical architecture and NSACFs deployed in a Hierarchical architecture is as follows: - The NSCAF is enhanced to support PDU session admission quota-based control. - When the local maximum number of PDU sessions is reached, the NSACF interacts with the Primary NSACF to handle the request. The Primary NSACF either return an increased local maximum number to the NSACF, or reject the local maximum number value update request if all the global maximum number are consumed based on the status of established PDU sessions to the network slice. NOTE: For Hierarchical NSAC architecture global maximum number used within this specification is synonymous with the maximum number of allowed registered UEs or established PDU Sessions for an S-NSSAI subject to Network Slice Admission Control (NSAC) for the entire PLMN and outbound roamers. - Based on the response from Primary NSACF, the NSACF updates the local maximum number if updated value is received from the Primary NSACF. The NSACF updates local maximum number value (if received) and determines whether to accept or reject the NSAC request for PDU session establishment based on the local maximum number value. - The update of local maximum number value by the Primary NSACF can also happen at any time through the Nnsacf_NSAC_LocalNumberUpdate service operation as described in clause 4.2.11.6 TS 23.502[ Procedures for the 5G System (5GS) ] [3]. The updated values provided from the Primary NSACF to NSACFs may directly apply to current NSAC pending request in NSACF and are used for all future requests. - The Primary NSACF subscribes with all NSACFs to obtain the number of currently established PDU sessions at all NSACFs. Based on the obtained information, the Primary NSACF can update the NSACF with local maximum number of established PDU sessions. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.15.11.2.2 |
3,685 | – DRX-ConfigSL | The IE DRX-ConfigSL is used to configure additional DRX parameters for the UE performing sidelink operation with resource allocation mode 1, as specified in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3]. DRX-ConfigSL information element -- ASN1START -- TAG-DRX-CONFIGSL-START DRX-ConfigSL-r17 ::= SEQUENCE { drx-HARQ-RTT-TimerSL-r17 INTEGER (0..56), drx-RetransmissionTimerSL-r17 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} } -- TAG-DRX-CONFIGSL-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,686 | 7.6 DELTA_PREAMBLE values | Except for NB-IoT, the DELTA_PREAMBLE preamble format based power offset values are presented in Table 7.6-1. Table 7.6-1: DELTA_PREAMBLE values. Where the Preamble Format is given by prach-ConfigIndex, as specified in TS 36.211[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation ] [7]. For NB-IoT, the DELTA_PREAMBLE preamble format based power offset values are presented in Table 7.6-2. Table 7.6-2: DELTA_PREAMBLE values for NB-IoT. Where Preamble Format is specified in TS 36.211[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation ] [7]. | 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 | 7.6 |
3,687 | 5.5.1 Visibility | Although in general the security features should be transparent to the user, for certain events and according to the user's concern, greater user visibility of the operation of security features should be provided. This yields to a number of features that inform the user of security-related events, such as: - indication of access network encryption: the property that the user is informed whether the confidentiality of user data is protected on the radio access link, in particular when non-ciphered calls are set-up; - indication of the level of security: the property that the user is informed on the level of security that is provided by the visited network, in particular when a user is handed over or roams into a network with lower security level (3G à 2G). The ciphering indicator feature is specified in 3GPP TS 22.101[ Service aspects; Service principles ] [ 21]. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 5.5.1 |
3,688 | 6.11.2.1 Sequence generation | The sequence used for the second synchronization signal is an interleaved concatenation of two length-31 binary sequences. The concatenated sequence is scrambled with a scrambling sequence given by the primary synchronization signal. The combination of two length-31 sequences defining the secondary synchronization signal differs between subframes according to where . The indices and are derived from the physical-layer cell-identity group according to where the output of the above expression is listed in Table 6.11.2.1-1. The two sequences and are defined as two different cyclic shifts of the m-sequence according to where, , is defined by with initial conditions. The two scrambling sequences and depend on the primary synchronization signal and are defined by two different cyclic shifts of the m-sequence according to where is the physical-layer identity within the physical-layer cell identity group and , , is defined by with initial conditions . The scrambling sequences and are defined by a cyclic shift of the m-sequence according to where and are obtained from Table 6.11.2.1-1 and , , is defined by with initial conditions . Table 6.11.2.1-1: Mapping between physical-layer cell-identity group and the indices and | 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.11.2.1 |
3,689 | 9.9.3.69 Unavailability information | The purpose of the Unavailability information information element is to provide the unavailability type, unavailability period duration and the start of unavailability period from the UE to the network. The Unavailability information information element is coded as shown in figure 9.9.3.69.1 and table 9.9.3.69.1. The Unavailability information is a type 4 information element with a minimum length of 3 octets and maximum length of 9 octets. Figure 9.9.3.69.1: Unavailability information information element Table 9.9.3.69.1: Unavailability information information element | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.9.3.69 |
3,690 | 5.3.8.2 Initiation | The network initiates the RRC connection release procedure to transit a UE in RRC_CONNECTED to RRC_IDLE; or to transit a UE in RRC_CONNECTED to RRC_INACTIVE only if SRB2 and at least one DRB or multicast MRB or, for IAB and NCR, SRB2, is setup in RRC_CONNECTED; or to transit a UE in RRC_INACTIVE back to RRC_INACTIVE when the UE tries to resume (for resuming a suspended RRC connection or for initiating SDT); or to transit a UE in RRC_INACTIVE to RRC_IDLE when the UE tries to resume (for resuming of a suspended RRC connection or for initiating SDT). The procedure can also be used to release and redirect a UE to another frequency. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.8.2 |
3,691 | 10.5.1.6 Mobile Station Classmark 2 | The purpose of the Mobile Station Classmark 2 information element is to provide the network with information concerning aspects of both high and low priority of the mobile station equipment. This affects the manner in which the network handles the operation of the mobile station. The Mobile Station Classmark information indicates general mobile station characteristics and it shall therefore, except for fields explicitly indicated, be independent of the frequency band of the channel it is sent on. The Mobile Station Classmark 2 information element is coded as shown in figure 10.5.6/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] , table 10.5.6a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.6b/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The Mobile Station Classmark 2 is a type 4 information element with 5 octets length. NOTE 1: Owing to backward compatibility problems, bit 8 of octet 4 should not be used unless it is also checked that the bits 8, 7 and 6 of octet 3 are not "0 0 0". Figure 10.5.6/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Mobile Station Classmark 2 information element NOTE 2: Additional mobile station capability information might be obtained by invoking the classmark interrogation procedure when GSM is used. | 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.6 |
3,692 | 5.6.14 Support of Framed Routing | Framed Routing is only defined for PDU Sessions of the IP type (IPv4, IPv6, IPv4v6) and allows to support an IP network behind a UE, such that a range of IPv4 addresses or IPv6 prefixes is reachable over a single PDU Session, e.g. for enterprise connectivity. Framed Routes are IP routes behind the UE. A PDU Session may be associated with multiple Framed Routes. Each Framed Route refers to a range of IPv4 addresses (i.e. an IPv4 address and an IPv4 address mask) or a range of IPv6 Prefixes (i.e. an IPv6 Prefix and an IPv6 Prefix length). The set of one or more Framed Routes associated to a PDU Session is contained in the Framed Route information. The network does not send Framed Route information to the UE: devices in the network(s) behind the UE get their IP address by mechanisms out of the scope of 3GPP specifications. See RFC 2865 [73], RFC 3162 [74]. Framed Route information is provided by the SMF to the UPF (acting as PSA) as part of Packet Detection Rule (PDR, see clause 5.8.5.3) related with the network side (N6) of the UPF. NOTE: SMF can take the UPF capabilities into account when selecting PSA UPF, to ensure that the SMF chooses PSA UPF(s) that support Framed Routing for PDU Sessions to DNN and/or slices deemed to support Framed Routing e.g. DNN and/or slices intended to support RG or if Framed Route information has been received as part of Session Management Subscription data. The Framed Route information may be provided to the SMF by: - the DN-AAA server as part of PDU Session Establishment authentication/authorization by a DN-AAA server (as defined in clause 5.6.6); or by - Session Management Subscription data associated with DNN and S-NSSAI sent by UDM (as defined in clause 5.2.3.3.1 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]). If the SMF receives Framed Route information both from DN-AAA and from UDM, the information received from DN-AAA takes precedence and supersedes the information received from UDM. The IPv4 address / IPv6 Prefix allocated to the UE as part of the PDU Session establishment (e.g. delivered in NAS PDU Session Establishment Accept) may belong to one of the Framed Routes associated with the PDU Session or may be dynamically allocated outside of such Framed Routes. If PCC applies to the PDU Session, at PDU Session establishment the SMF reports to the PCF the Framed Route information corresponding to the PDU Session (as described in clause 6.1.3.5 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]). In this case, in order to support session binding, the PCF may further report to the BSF the Framed Route information corresponding to the PDU Session (as described in clause 6.1.2.2 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]). If the UDM or DN-AAA updates the Framed Route information during the lifetime of the PDU Session, the SMF releases the PDU Session and may include in the release request an indication for the UE to re-establish the PDU Session. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.6.14 |
3,693 | F.2 Subscriber privacy | EAP-AKA' includes optional support for identity privacy mechanism that protects the privacy against passive eavesdropping. The mechanism is described in RFC 4187 [21] clause 4.1.1.2, and it uses pseudonyms that are delivered from the EAP server to the peer as part of an EAP-AKA exchange. The privacy mechanism described in [21] corresponds to the privacy provided by 5G-GUTI, however, assignment of 5G-GUTI is done outside the EAP framework in 5GS. TS 33.501[ Security architecture and procedures for 5G System ] assumes that the SUCI is sent outside the EAP messages, however, the peer may still receive EAP-Request/Identity or EAP-Request/AKA-Identity messages. Table F.2-1 specifies how the 5G UE shall behave when receiving such requests. Table F.2-1: 5G UE behaviour when receiving EAP identity requests 1) RFC 3748 [27] allows the peer to respond with abbreviated Identity Response where the peer-name portion of the NAI has been omitted. The 5G UE responds with SUCI in the same format as sent in the Registration Request, where the peer name has been encrypted. 2) RFC 4187 [21] allows the peer to respond with a pseudonym (cf. 5G-GUTI) or the permanent identity (i.e. SUPI). The 5G UE follows the "conservative" policy that has been described in RFC 4187 [21] clause 4.1.6 (Attacks against Identity Privacy) for the pseudonym based privacy, i.e. the peer shall not reveal its permanent identity. Instead, the peer shall send the EAP-Response/AKA-Client-Error packet with the error code "unable to process packet", and the authentication exchange terminates. The peer assumes that the EAP-Request/AKA-Identity originates from an attacker that impersonates the network, and for this reason refuses to send the cleartext SUPI. 3) RFC 4187 [21] allows the peer to respond with a pseudonym (cf. 5G-GUTI) or the permanent identity (i.e. SUPI). The 5G UE responds with SUCI. 4) RFC 4187 [21] allows the peer to respond with a fast re-authentication identity, pseudonym (cf. 5G-GUTI) or the permanent identity (i.e. SUPI). If the 5G UE supports fast re-authentication, it responds with the fast re-authentication identity, and if the 5G UE does not support fast re-authentication, it responds with SUCI. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | F.2 |
3,694 | 6.9.2.3.3 N2-Handover | Upon reception of the NGAP HANDOVER REQUIRED message, if the source AMF does not change the active KAMF (meaning no horizontal KAMF derivation) and if AS key re-keying is not required, the source AMF shall increment its locally kept NCC value by one and compute a fresh NH from its stored data using the function defined in Annex A.10. The source AMF shall use the KAMF from the currently active 5GS NAS security context for the computation of the fresh NH. The source AMF shall send the fresh {NH, NCC} pair to the target AMF in the Namf_Communication_CreateUEContext Request message. The Namf_Communication_CreateUEContext Request message shall in addition contain the KAMF that was used to compute the fresh {NH, NCC} pair and its corresponding ngKSI and corresponding uplink and downlink NAS COUNTs. If the source AMF had activated a new 5G NAS security context with a new KAMF, different from the 5G NAS security context on which the currently active 5G AS security context is based, but has not yet performed a UE Context Modification procedure, the Namf_Communication_CreateUEContext Request message shall in addition contain an indication that the KAMF sent by source AMF to target AMF is not in sync with the current KgNB used between the UE and the source gNB (i.e., keyAmfChangeInd) which means that AS key re-keying is required at the UE. Further, the source AMF shall derive a new KgNB associated with NCC=0 using the new KAMF and the uplink NAS COUNT from the last successful NAS SMC procedure with the UE and provide the {NH= newly derived KgNB, NCC=0} pair to the target AMF in the Namf_Communication_CreateUEContext Request message. The source AMF uses its local policy to determine whether to perform horizontal KAMF derivation on currently active KAMF. If horizontal KAMF derivation is performed, the Namf_Communication_CreateUEContext Request shall contain an indication (i.e., keyAmfHDerivationInd ) that the new KAMF has been calculated, an indication (i.e., keyAmfChangeInd) that AS key re-keying is required at the UE, and the downlink NAS COUNT used in the horizontal derivation of the sent KAMF. The ngKSI for the newly derived KAMF key has the same value and the same type as the ngKSI of the current KAMF. Further, the source AMF shall derive a new KgNB associated with NCC=0 using the newly derived KAMF and the uplink NAS COUNT value of 232-1 as defined in Annex A.9. The source AMF shall include the{NH=newly derived KgNB, NCC=0} pair and the ngKSI for the newly derived KAMF key in the Namf_Communication_CreateUEContext Request as well. NOTE a: The uplink NAS COUNT value for the initial KgNB derivation is set to 232-1. The reason for choosing such a value is to avoid any possibility that the value may be used to derive the same KgNB again. The source AMF shall always increment the downlink NAS COUNT by one after sending the Namf_Communication_CreateUEContext Request message to the target AMF. Unlike the S10 FORWARD RELOCATION REQUEST message in EPS, the Namf_Communication_CreateUEContext Request message in 5G shall not contain data and meta-data related to old 5G security context. NOTE 1: Void. If the target AMF receives the indication of horizontal KAMF derivation (i.e., keyAmfHDerivationInd), it shall derive the NAS keys from the received KAMF as specified in clause A.8 and set the NAS COUNTs to zero. The target AMF shall create a NASC (NAS Container) containing the K_AMF_change_flag, the received downlink NAS COUNT, ngKSI, selected NAS security algorithms, and NAS MAC. The K_AMF_change_flag is set to one when the target AMF receives keyAmfHDerivationInd_. Otherwise, the K_AMF_change_flag is set to zero. If the target AMF does not receive keyAmfHDerivationInd but wants to change the NAS algorithms, it shall create a NASC using the selected NAS security algorithms in the same manner as the case for the horizontal KAMF derivation. However, the target AMF shall not set the NAS COUNTs to zero. The target AMF shall calculate a 32-bit NAS MAC over the parameters included in the NASC using the KNASint key. The input parameters to the NAS 128-bit integrity algorithms as described in Annex D.3 shall be set as follows when calculating NAS MAC. The calculation of NAS MAC shall be the 32-bit output of the selected NIA and shall use the following inputs: - KEY : it shall be set to the corresponding KNASint; - COUNT : it shall be set to 232-1; - MESSAGE : it shall be set to the content of NAS Container as defined in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [35]; - DIRECTION : its bit shall be set to 1; and - BEARER : it shall be set to the value of the NAS connection identifier for 3GPP access. The use of the 232-1 as the value of the COUNT for the purpose of NAS MAC calculation/verification does not actually set the NAS COUNT to 232-1. The reason for choosing such a value not in the normal NAS COUNT range, i.e., [0, 224-1] is to avoid any possibility that the value may be reused for normal NAS messages. Replay protection is achieved by the UE checking if the downlink NAS COUNT included in the NAS Container is replayed or not. The UE shall not accept the same downlink NAS COUNT value twice before a newly derived KAMF is taken into use and the corresponding downlink NAS COUNT is set to zero. The target AMF shall increment the downlink NAS COUNT by one after creating a NASC. The NASC is included in the NGAP HANDOVER REQUEST message to the target ng-eNB/gNB. The purpose of this NASC could be compared to a NAS SMC message. If the target AMF receives the keyAmfChangeInd, it shall further send the received {NCC, NH} pair and the New Security Context Indicator (NSCI) to the target ng-eNB/gNB within the NGAP HANDOVER REQUEST message. The target AMF shall further set the NCC to one and shall further compute a NH as specified in Annex A.10. The target AMF shall further store the {NCC=1, NH} pair. NOTE 1a: VoidNOTE 2: The NAS Container (NASC) is defined as Intra N1 mode NAS transparent container in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [35]. NOTE 3: The downlink NAS COUNT is always included in the Namf_Communication_CreateUEContext Request and used by the target AMF for NAS MAC computation. This provides replay protection for NASC. If the target AMF does not receive the keyAmfChangeInd, it shall store locally the KAMF and {NH, NCC} pair received from the source AMF and then send the received {NH, NCC} pair to the target ng-eNB/gNB within the NGAP HANDOVER REQUEST message. Upon receipt of the NGAP HANDOVER REQUEST message from the target AMF, the target ng-eNB/gNB shall compute the KNG-RAN* to be used with the UE by performing the key derivation defined in Annex A.11 and A.12 with the {NH, NCC} pair received in the NGAP HANDOVER REQUEST message and the target PCI and its frequency ARFCN-DL/EARFCN-DL. The gNB uses the KNG-RAN* corresponding to the selected cell as KgNB. The ng-eNB uses the KNG-RAN* corresponding to the selected cell as KeNB. The target ng-eNB/gNB shall associate the NCC value received from AMF with the KgNB/KeNB. The target ng-eNB/gNB shall include the NCC value from the received {NH, NCC} pair, and the NASC if such was also received, into the HO Command message to the UE and remove any existing unused stored {NH, NCC} pairs. If the target ng-eNB/gNB had received the NSCI, it shall set the keySetChangeIndicator field in the HO Command message to true. NOTE 4: The source AMF may be the same as the target AMF in the description in this sub-clause. If so the single AMF performs the roles of both the source and target AMF. In this case, actions related to N14 messages are handled internally in the single AMF. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.9.2.3.3 |
3,695 | 16.9.4.3 Control of idle/inactive UEs | The UE in RRC_IDLE or RRC_INACTIVE performs NR sidelink communication and/or V2X sidelink communication, as configured by the upper layers. NG-RAN may provide common sidelink configuration to the UE in RRC_IDLE or RRC_INACTIVE via system information for NR sidelink communication and/or V2X sidelink communication. UE receives resource pool configuration and SL DRB configuration via SIB12 for NR sidelink communication as specified in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12], and/or resource pool configuration via SIB13 and SIB14 for V2X sidelink communication as specified in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12]. When the UE performs cell reselection, the UE interested in V2X service(s) considers at least whether NR sidelink communication and/or V2X sidelink communication are supported by the cell. The UE may consider the following carrier frequency as the highest priority frequency, except for the carrier only providing the anchor carrier: - the frequency providing both NR sidelink communication configuration and V2X sidelink communication configuration, if configured to perform both NR sidelink communication and V2X sidelink communication; - the frequency providing NR sidelink communication configuration, if configured to perform only NR sidelink communication. - the frequency providing V2X sidelink communication configuration, if configured to perform only V2X sidelink communication. When the UE performs cell reselection, the UE interested in ProSe service(s) considers at least whether NR sidelink communication/discovery is supported by the cell. The UE may consider the carrier frequency providing NR sidelink communication/discovery configuration as the highest priority frequency, except for the carrier only providing the anchor carrier. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.9.4.3 |
3,696 | C.4.3.1 IMSI-based SUPI | The following test data set corresponds to SUCI computation in the UE for IMSI-based SUPI and ECIES Profile A. IMSI consists of MCC|MNC: '274012' and MSIN: '001002086' ECIES test data The ECIES Scheme Output is computed in the UE as defined in Figure C.3.2-1 of clause C.3.2 with the following data Home Network Private Key: 'c53c22208b61860b06c62e5406a7b330c2b577aa5558981510d128247d38bd1d' Home Network Public Key: '5a8d38864820197c3394b92613b20b91633cbd897119273bf8e4a6f4eec0a650' Eph. Private Key: 'c80949f13ebe61af4ebdbd293ea4f942696b9e815d7e8f0096bbf6ed7de62256' Eph. Public Key: 'b2e92f836055a255837debf850b528997ce0201cb82adfe4be1f587d07d8457d' Eph. Shared Key: '028ddf890ec83cdf163947ce45f6ec1a0e3070ea5fe57e2b1f05139f3e82422a' Eph. Enc. Key: '2ba342cabd2b3b1e5e4e890da11b65f6' ICB: 'e2622cb0cdd08204e721c8ea9b95a7c6' Plaintext block: '00012080f6' Cipher-text vaue: 'cb02352410' Eph. mac key: 'd9846966fb7cf5fcf11266c5957dea60b83fff2b7c940690a4bfe57b1eb52bd2' MAC-tag value: 'cddd9e730ef3fa87' Scheme Output: 'b2e92f836055a255837debf850b528997ce0201cb82adfe4be1f587d07d8457dcb02352410cddd9e730ef3fa87’ | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | C.4.3.1 |
3,697 | 4.15.6.9.3 Processing AF requests to influence access and mobility management policies | With this procedure, the AF can provide its request to influence access and mobility management policies (for one or multiple UEs) at any time. Figure 4.15.6.9.3-1: Handling an AF request to influence access and mobility management policies Policy This procedure concerns non-roaming scenarios, i.e. to cases where the involved entities serving the UE (i.e. AF, NEF, PCF, BSF, UDR, AMF) belong to the home PLMN, or the AF belongs to a third party with which the home PLMN has an agreement. This procedure concerns also the local breakout roaming case where the involved entities (i.e. AF, NEF, PCF, BSF, UDR, AMF) serving the UE belong to the VPLMN or the AF belongs to a third party with which the VPLMN has an agreement. The PCF for the UE and the PCF for the PDU Session can be the same entity, then step 5 is not performed and the PCF itself determines the start/stop of application traffic or SM policy establishment/termination for a DNN, S-NSSAI and proceeds with step 6. 1. AM Policy Association establishment as described in clause 4.16.1. 2. The PCF for the UE may subscribe to policy data related to AM influence (Data Set = Application Data; Data Subset = AM influence information, Data Key = S-NSSAI and DNN and/or (Internal Group Identifier or SUPI or PLMN ID of inbound roamers)). 3a. To create a new request, the AF provides "AM influence information" data to the NEF using the Nnef_AMInfluence_Create service operation (together with the AF identifier and potentially further inputs as specified in clause 5.2.6.23.2), including a target (one UE identified by GPSI, a group of UEs identified by an External Group Identifier, or any UE (for non roaming case), or any inbound roaming UEs identified by their PLMN ID(s)), a list of (DNN, S-NSSAI)(s) and optionally a list of External Application Identifier(s) and requirements related to access and mobility management policies (e.g. service coverage requirements, throughput requirements). The AF request contains also an AF Transaction Id and may contain a timer on how long this policy shall last, in which case the system behaviour upon expiration of this timer is as specified in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. If with this request the AF subscribes to access and mobility management related events, the AF indicates also where it desires to receive the corresponding notifications. The target "any UE" is applicable if an External Application Identifier or list of (DNN, S-NSSAI) is also provided. The target "any inbound roaming UEs identified by their PLMN ID(s)" is applicable if an External Application Identifier or list of (DNN, S-NSSAI) is also provided. To update or remove an existing request, the AF invokes an Nnef_AMInfluence_Update or Nnef_AMInfluence_Delete service operation providing the corresponding AF Transaction Id. 3b. The NEF stores, updates, or removes the policy data of step 3a in the UDR, having translated any External Group Identifier to an Internal Group Identifier and any GPSI to a SUPI. 3c. The UDR informs the NEF about the result of the operation of step 3b. 3d. The NEF informs the AF about the result of the Nnef_AMInfluence operation performed in step 3a. NOTE 1: Steps 1, 2 and 3 can occur in any order. 4. The UDR notifies the PCF(s) that have a matching subscription (from step 2) about the data stored, updated, or removed in step 3. If matching entries already existed in the UDR when step 2 is performed, this shall be immediately reported to the PCF. The PCF may check that an SM Policy Association is established for the SUPI, DNN, S-NSSAI then subscribe to the SMF to Policy Control Request Trigger to detect the application traffic that triggers the allocation of a service area coverage or an allocation of RFSP index value, then step 6 follows. 5. Steps 2 to 10 in Figure 4.16.14.2.1-1 applies if access and mobility management policies depend on application in use, or steps 2 to 5 in Figure 4.16.14.2.2-1 applies if access and mobility management policies depend on SM Policy Association establishment and termination for a DNN, S-NSSAI combination 6. The PCF for the UE takes a policy decision and then it may initiate an AM Policy Association Modification procedure as described in clause 4.16.2.2. If the AF has subscribed to access and mobility management related events, i.e. request for service area coverage outcome in step 3, then the PCF reports the event (i.e. outcome of the request for service area coverage) to the AF as described in clause 4.16.2.2. NOTE 2: The PCF for the UE can subscribe to the "start/stop of application traffic detection" events for multiple applications with different application identifiers in the same Npcf_PolicyAuthorization_Subscribe request. When PCF receives the notifications for multiple applications, the PCF for the UE can determine which access and mobility management policy to apply based on local configuration and operator policy. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.6.9.3 |
3,698 | 5.27.2.5.1 Overview | If the NG-RAN receives a TSCAI containing a BAT Window or the Capability for BAT adaptation for a QoS Flow, the NG-RAN can determine a BAT offset in order to align the arrival of the traffic bursts with the next expected transmission opportunity over the air interface in each direction (i.e. DL or UL). The BAT offset can take a positive or a negative values. If the NG-RAN receives a TSCAI containing a Periodicity Range for a QoS Flow, the NG-RAN can determine an adjusted Periodicity along with above specified BAT offset, 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 TSCAI contained a value range, the adjusted Periodicity should be any value between the lower bound and upper bound. If the TSCAI contained a list of Periodicity value(s), the adjusted Periodicity should be one of these values. NG-RAN may support the following feedback mechanisms: - Proactive RAN feedback for adaptation of Burst Arrival Time and Periodicity: NG-RAN may provide a Burst Arrival Time offset and an adjusted Periodicity as part of QoS flow establishment or modification as illustrated in clause 5.27.2.5.2; - Reactive RAN feedback for Burst Arrival Time adaptation: NG-RAN may provide a Burst Arrival Time offset after QoS flow establishment as illustrated in clause 5.27.2.5.3. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.27.2.5.1 |
3,699 | 16.15.3 Power Saving | Most XR video frame rates (15, 30, 45, 60, 72, 90 and 120 fps) correspond to periodicities that are not an integer (66.66, 33.33, 22.22, 16.66, 13.88, 11.11 and 8.33 ms respectively). The gNB may configure a DRX cycle expressed in rational numbers so that the DRX cycle matches those periodicities, e.g. for the traffic with a frame rate of 60 fps, the network may configure the UE with a DRX cycle of 50/3 ms. Configured grants may be configured without the need for the UE to monitor possible UL retransmissions, thus increasing the number of power saving opportunities for the UE. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.15.3 |
3,700 | 4.3.2.4 Support of L2TP | L2TP may be used between UPF and the DN via N6 to carry traffic of a PDU Session, as defined in TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The corresponding high level end to end signalling flow is described in this clause and further refined in TS 29.561[ 5G System; Interworking between 5G Network and external Data Networks; Stage 3 ] [63]. For the procedure described below, it is a prerequisite that the UE is already registered to the 5GC and both SMF and UPF support the L2TP feature. NOTE 1: The scenario where the UE sends actual PPP frames/signalling towards the LAC, which involves back and forth message exchanges between the UE and LAC, for example for LCP Negotiation, is not in the scope of the present document. NOTE 2: The UE does not need to be aware of the L2TP procedure. Figure 4.3.2.4-1: Support of L2TP 1. This step is the same as step 1 in clause 4.3.2.2.1 or step 1 in clause 4.3.2.2.2. The PDU session establishment may include in the PCO information authentication information for PAP and/or CHAP. 2. The SMF may determine that an L2TP session is required for the PDU Session based on local configuration (e.g. related with DNN/S-NSSAI). The SMF may retrieve the L2TP Tunnel parameters from the DN-AAA Server, as described in clause 4.3.2.3, or be configured locally with L2TP Tunnel parameters. The L2TP Tunnel parameters may include information such as the LNS addressing information (e.g. IP address or hostname), as defined in TS 29.561[ 5G System; Interworking between 5G Network and external Data Networks; Stage 3 ] [63]. 3. This step is the same as step 8 in clause 4.3.2.2.1 with the following additions: If L2TP is required for the PDU Session, the SMF selects a UPF supporting L2TP. 4. This step is the same as step 10a in clause 4.3.2.2.1 with the following additions: The SMF requests the UPF to setup an L2TP Session towards the L2TP server (LNS). The SMF may send to the UPF as part of N4 signalling, L2TP Tunnel Information and L2TP Session Information to setup a L2TP session. The L2TP Session Information includes specific information related to the PDU Session, e.g. a Calling Number which may be set to UE's SUPI, the Called Number for the L2TP Session which may be configured to contain the DNN, PAP/CHAP related parameters if included by the UE in PCO in step 1 etc. This information is defined in TS 29.561[ 5G System; Interworking between 5G Network and external Data Networks; Stage 3 ] [63]. 5. If needed the UPF may decide to setup a new L2TP Tunnel, as described in TS 29.561[ 5G System; Interworking between 5G Network and external Data Networks; Stage 3 ] [63]. If the UPF decides to use an already existing L2TP Tunnel for the requested PDU Session from the SMF, it directly proceeds with step 6 below. 6. The UPF proceeds with L2TP Session setup towards the LNS, as described in TS 29.561[ 5G System; Interworking between 5G Network and external Data Networks; Stage 3 ] [63]. If the SMF has requested the UPF to allocate the UE IP address in step 4, the UPF may retrieve the UE IP address from the LNS. 7. This step is the same as step 10b in clause 4.3.2.2.1 with the following additions: The status of the L2TP Session setup is sent by the UPF to the SMF in a N4 Session Establishment Response. This may indicate information provided by the LNS Server for the UE such as the DNS server address, etc. 8. This step is the same as steps 11 - 13 in clause 4.3.2.2.1. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3.2.4 |
Subsets and Splits
No saved queries yet
Save your SQL queries to embed, download, and access them later. Queries will appear here once saved.