Search is not available for this dataset
doc_id
int64 1
6.72k
⌀ | Section
stringlengths 5
247
⌀ | Content
stringlengths 501
147k
⌀ | Source
stringclasses 456
values | Document Title
stringclasses 22
values | Working Group
stringclasses 21
values | Series Subject
stringclasses 9
values | Subclause
stringlengths 1
13
⌀ |
|---|---|---|---|---|---|---|---|
5,501 | I.2.3 Key hierarchy, key derivation and key distribution I.2.3.1 General | The text in clauses 6.2.1 and 6.2.2 cannot apply directly for an EAP authentication method other than EAP-AKA' as these clauses assume that an AKA-based authentication method is used. The major differences are the way in which KAUSF is calculated and that the UDM/ARPF is not necessarily involved in the key derivation or distribution. Depending on the selected authentication method, the KAUSF is generated as follows: - For 5G AKA and EAP-AKA' refer to clause 6.2.1. - When using a key-generating EAP authentication method other than EAP-AKA', the key derivation of KAUSF is based on the EAP-method credentials in the UE and AUSF and shall be done as shown in Figure I.2.3-1. NOTE: For EAP authentication methods other than EAP-AKA', this key derivation replaces clauses 6.2.1 and 6.2.2 for the generation of KAUSF . Figure I.2.3.1-1: KAUSF derivation for key-generating EAP authentication methods other than EAP-AKA' KAUSF shall be derived by the AUSF and UE from the EMSK created by the EAP authentication as for EAP-AKA'. All of figures 6.2.1-1, 6.2.2.1-1 and 6.2.2.2.2-1 from the KAUSF downwards are used without modification. Similarly, text relating to the key hierarchy, key derivation and key distribution in clauses 6.2.1, 6.2.2.1 and 6.2.2.2 for keys derived from KAUSF (e.g. KSEAF, KAMF, KgNB etc) apply without modification. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | I.2.3 |
5,502 | P.2 Session management and traffic routing for PIN | The general session management principles as described in clause 5.6, the QoS model as defined in clause 5.7 and the User Plane management for 5GS as defined in clause 5.8 are applicable to PIN-DN communication and PIN-indirect communication. If a PIN has multiple PEGC UEs, 5G VN group communication mechanisms can be used for PIN indirect communication (i.e. communication between PIN Elements belonging to the same PIN but served by different PEGC UEs). In this case a dedicated SMF set is used for managing the PIN related PDU Sessions from all the PEGCs of that PIN and the PDU session management principles for 5G VN-LAN-type services as specified in clause 5.29.3 are applicable. The user plane handling for 5G LAN-type services as specified in 5.29.4 are applicable with following differences: - For PIN indirect communication N19-based traffic forwarding is not used i.e. the PIN traffic is forwarded using: - N6-based traffic forwarding method, where the UL/DL traffic for the PIN communication is forwarded to/from the DN; - local switching as depicted in Figure P.2-1 below, following the principles of local switching of traffic for 5G VN LAN-type service. Figure P.2-1: Local-switch based user plane architecture for PIN NOTE: Figure P.2-1 does not show traffic from a PEMC. The SMF configures the UPF(s) to apply N6-based traffic forwarding to route traffic between PDU Sessions of different PEGC UEs of a PIN as specified in clause 5.8.2.13. The SMF can apply local switching as specified in clause 5.8.2.13 in order to enable UPF locally forward uplink stream from one PDU session of one PEGC UE of a PIN as downlink stream of PDU session of one or more PEGC UE(s) of the same PIN. For local switching of PIN traffic between PIN related PDU sessions from different PEGC UEs of a single PIN, based on the DNN and S-NSSAI that is used for the PDU session related to PIN, the SMF provides a Network Instance to the UPF in FAR and/or PDR via N4 Session Establishment/Modification procedures. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | P.2 |
5,503 | 5.5.1.2.5A Attach for emergency bearer services not accepted by the network | If the attach request for emergency bearer services cannot be accepted by the network, the MME shall send an ATTACH REJECT message to the UE including EMM cause #5 "IMEI not accepted" or one of the EMM cause values as described in clause 5.5.1.2.5. NOTE 1: If EMM cause #11 is sent to a UE of a roaming subscriber attaching for emergency bearer services and the UE is in automatic network selection mode, it cannot obtain normal service provided by this PLMN. Upon receiving the ATTACH REJECT message including EMM cause #5, the UE shall enter the state EMM-DEREGISTERED.NO-IMSI. Upon receiving the ATTACH REJECT message including one of the other EMM cause values, the UE shall perform the actions as described in clause 5.5.1.2.5 with the following addition: the UE shall inform the upper layers of the failure of the procedure. NOTE 2: This can result in the upper layers requesting establishment of a CS emergency call (if not already attempted in the CS domain), or other implementation specific mechanisms, e.g. procedures specified in 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [13D] can result in the emergency call being attempted to another IP-CAN. If the attach request for emergency bearer services fails due to abnormal case a) in clause .2.6, the UE shall perform the actions as described in clause 5.5.1.2.6 and inform the upper layers of the failure to access the network. NOTE 3: This can result in the upper layers requesting establishment of a CS emergency call (if not already attempted in the CS domain), or other implementation specific mechanisms, e.g. procedures specified in 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [13D] can result in the emergency call being attempted to another IP-CAN. If the attach request for emergency bearer services fails due to abnormal cases b), c) or d) in clause .2.6, the UE shall perform the actions as described in clause 5.5.1.2.6 with the following addition: the UE shall inform the upper layers of the failure of the procedure. NOTE 4: This can result in the upper layers requesting establishment of a CS emergency call (if not already attempted in the CS domain), or other implementation specific mechanisms, e.g. procedures specified in 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [13D] can result in the emergency call being attempted to another IP-CAN. In a shared network, upon receiving the ATTACH REJECT message, the UE shall perform the actions as described in clause 5.5.1.2.5, and shall: a) inform the upper layers of the failure of the procedure; or NOTE 5: This can result in the upper layers requesting establishment of a CS emergency call (if not already attempted in the CS domain), or other implementation specific mechanisms, e.g. procedures specified in 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [13D] can result in the emergency call being attempted to another IP-CAN . b) attempt to perform a PLMN selection in the shared network and, if an attach for emergency bearer services was not already attempted with the selected PLMN and the ATTACH REQUEST message: - did not include a PDN CONNECTIVITY REQUEST message with request type set to "handover of emergency bearer services", initiate an attach for emergency bearer services to the selected PLMN; or - did include a PDN CONNECTIVITY REQUEST message with request type set to "handover of emergency bearer services" and: i) the selected PLMN is an equivalent PLMN, initiate an attach for emergency bearer services to the selected PLMN; and ii) the selected PLMN is not an equivalent PLMN, perform a PLMN selection and initiate an attach for emergency bearer services to the selected PLMN if an attach for emergency bearer services was not already attempted with the selected PLMN. In a shared network, if the attach request for emergency bearer services fails due to abnormal case a) in clause .2.6, the UE shall perform the actions as described in clause 5.5.1.2.6 and shall: a) inform the upper layers of the failure to access the network; or NOTE 6: This can result in the upper layers requesting establishment of a CS emergency call (if not already attempted in the CS domain), or other implementation specific mechanisms, e.g. procedures specified in 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [13D] can result in the emergency call being attempted to another IP-CAN . b) attempt to perform a PLMN selection in the shared network and, if an attach for emergency bearer services was not already attempted with the selected PLMN and the ATTACH REQUEST message: - did not include a PDN CONNECTIVITY REQUEST message with request type set to "handover of emergency bearer services", initiate an attach for emergency bearer services to the selected PLMN; or - did include a PDN CONNECTIVITY REQUEST message with request type set to "handover of emergency bearer services" and: i) the selected PLMN is an equivalent PLMN, initiate an attach for emergency bearer services to the selected PLMN; and ii) the selected PLMN is not an equivalent PLMN, perform a PLMN selection and initiate an attach for emergency bearer services to the selected PLMN if an attach for emergency bearer services was not already attempted with the selected PLMN. In a shared network, if the attach request for emergency bearer services fails due to abnormal cases b), c) or d) in clause .2.6, the UE shall perform the actions as described in clause 5.5.1.2.6, and shall: a) inform the upper layers of the failure of the procedure; or NOTE 7: This can result in the upper layers requesting establishment of a CS emergency call (if not already attempted in the CS domain), or other implementation specific mechanisms, e.g. procedures specified in 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [13D] can result in the emergency call being attempted to another IP-CAN . b) attempt to perform a PLMN selection in the shared network and, if an attach for emergency bearer services was not already attempted with the selected PLMN and the ATTACH REQUEST message - did not include a PDN CONNECTIVITY REQUEST message with request type set to "handover of emergency bearer services", initiate an attach for emergency bearer services to the selected PLMN; or - did include a PDN CONNECTIVITY REQUEST message with request type set to "handover of emergency bearer services" and: i) the selected PLMN is an equivalent PLMN, initiate an attach for emergency bearer services to the selected PLMN; and ii) the selected PLMN is not an equivalent PLMN, perform a PLMN selection and initiate an attach for emergency bearer services to the selected PLMN if an attach for emergency bearer services was not already attempted with the selected PLMN. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.1.2.5A |
5,504 | 5.2.2.4.19 Actions upon reception of SIB17 | Upon receiving SIB17, the UE shall: 1> if the UE has stored at least one segment of SIB17 and the value tag of SIB17 has changed since a previous segment was stored: 2> discard all stored segments; 1> store the segment; 1> if all segments have been received: 2> assemble SIB17-IEs from the received segments. The UE should discard any stored segments for SIB17 if the complete SIB17 has not been assembled within a period of 3 hours. The UE shall discard any stored segments for SIB17 upon cell (re-) selection. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.2.2.4.19 |
5,505 | 8.2.2.2.5 Minimum Requirement 2 Tx Antenna Port (when EIMTA-MainConfigServCell-r12 is configured) | The requirements are specified in Table 8.2.2.2.5-2 with the addition of the parameters in Table 8.2.2.2.5-1 and the downlink physical channel setup according to Annex C.3.2. The test purpose is to verify the performance of transmit diversity (SFBC) with 2 transmitter antennas in case of using eIMTA TDD UL-DL reconfiguration for TDD serving cell(s) via monitoring PDCCH with eIMTA-RNTI on a PCell. Table 8.2.2.2.5-1: Test Parameters for Transmit diversity Performance (FRC) when EIMTA-MainConfigServCell-r12 is configured Table 8.2.2.2.5-2: Minimum performance Transmit diversity when EIMTA-MainConfigServCell-r12 is configured | 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.2.2.5 |
5,506 | 5.2.13.2.4 Nbsf_Management_Discovery service operation | Service Operation name: Nbsf_Management discovery Description: Discovers the PCF and PCF set selected for a PDU Session identified by the tuple (UE address(es), SUPI, GPSI, DNN, S-NSSAI), or discovers the PCF and PCF set selected for the UE identified by the tuple (SUPI, GPSI). This operation may also be used to determine the SUPI from the tuple (UE address, DNN, S-NSSAI). Inputs, Required: UE address (i.e. IP address or MAC address), [Required, for a PDU Session and for a UE], DNN [Conditional], S-NSSAI [Conditional], if the target PCF is for a PDU Session, MBS session ID as defined in TS 23.247[ Architectural enhancements for 5G multicast-broadcast services ] [78], [Required, for an MBS Session]. SUPI and/or GPSI, if the target PCF is for a UE. NOTE: For support of time sensitive communication and time synchronization (as described in clause 5.28.3.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]) the UE address contains the DS-TT port MAC address for Ethernet type PDU Session. Inputs, Optional: If the target PCF is for a PDU Session, SUPI, GPSI. Outputs, Required: PCF address(es), PCF instance ID [Conditional, if available] and PCF Set ID [Conditional, if available], level of Binding [Conditional, if available] (see clause 6.3.1.0 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]). Outputs, Optional: SUPI, if available. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.13.2.4 |
5,507 | 25.2 Home network domain name | The home network domain name of the OCS shall be in the form of an Internet domain name, e.g. operator.com, as specified in IETF RFC 1035 [19] and IETF RFC 1123 [20]. The home network domain of the OCS consists of one or more labels. Each label shall consist of the alphabetic characters (A-Z and a-z), digits (0-9) and the hyphen (-) in accordance with IETF RFC 1035 [19]. Each label shall begin and end with either an alphabetic character or a digit in accordance with IETF RFC 1123 [20]. The case of alphabetic characters is not significant. If the home network domain of the OCS is not known (e.g. through an available static address or through its reception from another node), it shall be: - in the form of "ocs.mnc<MNC>.mcc<MCC>.3gppnetwork.org", where "<MNC>" and "<MCC>" fields correspond to the MNC and MCC of the operator's PLMN to which the OCS belongs. Both the "<MNC>" and "<MCC>" fields are 3 digits long. If the MNC of the PLMN is 2 digits, then a zero shall be added at the beginning; and - derived from the subscriber's IMSI, as described in the following steps: 1. take the first 5 or 6 digits, depending on whether a 2 or 3 digit MNC is used (see 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [27]) and separate them into MCC and MNC; if the MNC is 2 digits then a zero shall be added at the beginning; 2. use the MCC and MNC derived in step 1 to create the "mnc<MNC>.mcc<MCC>.3gppnetwork.org" domain name; 3. add the label "ocs" to the beginning of the domain name. An example of a home network domain name is: IMSI in use: 234150999999999; Where: MCC = 234; MNC = 15; MSIN = 0999999999; Which gives the home network domain name: ocs.mnc015.mcc234.3gppnetwork.org. NOTE: It is implementation dependent to determine that the length of the MNC is 2 or 3 digits. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 25.2 |
5,508 | 4.2.8 Support of non-3GPP access 4.2.8.1 General Concepts to Support Trusted and Untrusted Non-3GPP Access | The 5G Core Network supports connectivity of UEs via non-3GPP access networks, e.g. WLAN access networks. Only the support of non-3GPP access networks deployed outside the NG-RAN is described in this clause. The 5G Core Network supports both untrusted non-3GPP access networks and trusted non-3GPP access networks (TNANs). An untrusted non-3GPP access network shall be connected to the 5G Core Network via a Non-3GPP InterWorking Function (N3IWF), whereas a trusted non-3GPP access network shall be connected to the 5G Core Network via a Trusted Non-3GPP Gateway Function (TNGF). Both the N3IWF and the TNGF interface with the 5G Core Network CP and UP functions via the N2 and N3 interfaces, respectively. A non-3GPP access network may advertise the PLMNs or SNPNs for which it supports trusted connectivity and the type of supported trusted connectivity (e.g. "5G connectivity"). Therefore, the UEs can discover the non-3GPP access networks that can provide trusted connectivity to one or more PLMNs or SNPNs. This is further specified in clause 6.3.12 (Trusted Non-3GPP Access Network selection). The UE decides to use trusted or untrusted non-3GPP access for connecting to a 5G PLMN or SNPNs by using procedures not specified in this document. Examples of such procedures are defined in clause 6.3.12.1. When the UE decides to use untrusted non-3GPP access to connect to a 5G Core Network in a PLMN: - the UE first selects and connects with a non-3GPP access network; and then - the UE selects a PLMN/SNPN and an N3IWF in this PLMN/SNPN. The PLMN/SNPN/N3IWF selection and the non-3GPP access network selection are independent. The N3IWF selection is defined in clause 6.3.6. When the UE decides to use trusted non-3GPP access to connect to a 5G Core Network in a PLMN: - the UE first selects a PLMN/SNPN; and then - the UE selects a non-3GPP access network (a TNAN) that supports trusted connectivity to the selected PLMN/SNPN. In this case, the non-3GPP access network selection is affected by the PLMN/SNPN selection. A UE that accesses the 5G Core Network over a non-3GPP access shall, after UE registration, support NAS signalling with 5G Core Network control-plane functions using the N1 reference point. When a UE is connected via a NG-RAN and via a non-3GPP access, multiple N1 instances shall exist for the UE i.e. there shall be one N1 instance over NG-RAN and one N1 instance over non-3GPP access. A UE simultaneously connected to the same 5G Core Network of a PLMN/SNPN over a 3GPP access and a non-3GPP access shall be served by a single AMF in this 5G Core Network. When a UE is connected to a 3GPP access of a PLMN, if the UE selects a N3IWF and the N3IWF is located in a PLMN different from the PLMN of the 3GPP access, e.g. in a different VPLMN or in the HPLMN, the UE is served separately by the two PLMNs. The UE is registered with two separate AMFs. PDU Sessions over the 3GPP access are served by V-SMFs different from the V-SMF serving the PDU Sessions over the non-3GPP access. The same can be true when the UE uses trusted non-3GPP access, i.e. the UE may select one PLMN for 3GPP access and a different PLMN for trusted non-3GPP access. NOTE: The registrations with different PLMNs over different Access Types doesn't apply to UE registered for Disaster Roaming service as described in the clause 5.40. The PLMN selection for the 3GPP access does not depend on the PLMN that is used for non-3GPP access. In other words, if a UE is registered with a PLMN over a non-3GPP access, the UE performs PLMN selection for the 3GPP access independently of this PLMN. A UE shall establish an IPsec tunnel with the N3IWF or with the TNGF in order to register with the 5G Core Network over non-3GPP access. Further details about the UE registration to 5G Core Network over untrusted non-3GPP access and over trusted non-3GPP access are described in clause 4.12.2 and in clause 4.12.2a of TS 23.502[ Procedures for the 5G System (5GS) ] [3], respectively. It shall be possible to maintain the UE NAS signalling connection with the AMF over the non-3GPP access after all the PDU Sessions for the UE over that access have been released or handed over to 3GPP access. N1 NAS signalling over non-3GPP accesses shall be protected with the same security mechanism applied for N1 over a 3GPP access. User plane QoS differentiation between UE and N3IWF is supported as described in clause 5.7 and clause 4.12.5 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. QoS differentiation between UE and TNGF is supported as described in clause 5.7 and clause 4.12a.5 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") | 4.2.8 |
5,509 | – SRS-Config | The IE SRS-Config is used to configure sounding reference signal transmissions. The configuration defines a list of SRS-Resources, a list of SRS-PosResources, a list of SRS-PosResourceSets and a list of SRS-ResourceSets. Each resource set defines a set of SRS-Resources or SRS-PosResources. The network triggers the transmission of the set of SRS-Resources or SRS-PosResources using a configured aperiodicSRS-ResourceTrigger (L1 DCI). The network does not configure SRS specific power control parameters, alpha (without suffix), p0 (without suffix) or pathlossReferenceRS if unifiedTCI-StateType is configured for the serving cell. SRS-Config information element -- ASN1START -- TAG-SRS-CONFIG-START SRS-Config ::= SEQUENCE { srs-ResourceSetToReleaseList SEQUENCE (SIZE(1..maxNrofSRS-ResourceSets)) OF SRS-ResourceSetId OPTIONAL, -- Need N srs-ResourceSetToAddModList SEQUENCE (SIZE(1..maxNrofSRS-ResourceSets)) OF SRS-ResourceSet OPTIONAL, -- Need N srs-ResourceToReleaseList SEQUENCE (SIZE(1..maxNrofSRS-Resources)) OF SRS-ResourceId OPTIONAL, -- Need N srs-ResourceToAddModList SEQUENCE (SIZE(1..maxNrofSRS-Resources)) OF SRS-Resource OPTIONAL, -- Need N tpc-Accumulation ENUMERATED {disabled} OPTIONAL, -- Need S ..., [[ srs-RequestDCI-1-2-r16 INTEGER (1..2) OPTIONAL, -- Need S srs-RequestDCI-0-2-r16 INTEGER (1..2) OPTIONAL, -- Need S srs-ResourceSetToAddModListDCI-0-2-r16 SEQUENCE (SIZE(1..maxNrofSRS-ResourceSets)) OF SRS-ResourceSet OPTIONAL, -- Need N srs-ResourceSetToReleaseListDCI-0-2-r16 SEQUENCE (SIZE(1..maxNrofSRS-ResourceSets)) OF SRS-ResourceSetId OPTIONAL, -- Need N srs-PosResourceSetToReleaseList-r16 SEQUENCE (SIZE(1..maxNrofSRS-PosResourceSets-r16)) OF SRS-PosResourceSetId-r16 OPTIONAL, -- Need N srs-PosResourceSetToAddModList-r16 SEQUENCE (SIZE(1..maxNrofSRS-PosResourceSets-r16)) OF SRS-PosResourceSet-r16 OPTIONAL,-- Need N srs-PosResourceToReleaseList-r16 SEQUENCE (SIZE(1..maxNrofSRS-PosResources-r16)) OF SRS-PosResourceId-r16 OPTIONAL,-- Need N srs-PosResourceToAddModList-r16 SEQUENCE (SIZE(1..maxNrofSRS-PosResources-r16)) OF SRS-PosResource-r16 OPTIONAL -- Need N ]], [[ dci-TriggeringPosResourceSetLink-r18 ENUMERATED { enabled } OPTIONAL -- Need R ]] } SRS-ResourceSet ::= SEQUENCE { srs-ResourceSetId SRS-ResourceSetId, srs-ResourceIdList SEQUENCE (SIZE(1..maxNrofSRS-ResourcesPerSet)) OF SRS-ResourceId OPTIONAL, -- Cond Setup resourceType CHOICE { aperiodic SEQUENCE { aperiodicSRS-ResourceTrigger INTEGER (1..maxNrofSRS-TriggerStates-1), csi-RS NZP-CSI-RS-ResourceId OPTIONAL, -- Cond NonCodebook slotOffset INTEGER (1..32) OPTIONAL, -- Need S ..., [[ aperiodicSRS-ResourceTriggerList SEQUENCE (SIZE(1..maxNrofSRS-TriggerStates-2)) OF INTEGER (1..maxNrofSRS-TriggerStates-1) OPTIONAL -- Need M ]] }, semi-persistent SEQUENCE { associatedCSI-RS NZP-CSI-RS-ResourceId OPTIONAL, -- Cond NonCodebook ... }, periodic SEQUENCE { associatedCSI-RS NZP-CSI-RS-ResourceId OPTIONAL, -- Cond NonCodebook ... } }, usage ENUMERATED {beamManagement, codebook, nonCodebook, antennaSwitching}, alpha Alpha OPTIONAL, -- Need S p0 INTEGER (-202..24) OPTIONAL, -- Cond Setup pathlossReferenceRS PathlossReferenceRS-Config OPTIONAL, -- Need M srs-PowerControlAdjustmentStates ENUMERATED { sameAsFci2, separateClosedLoop} OPTIONAL, -- Need S ..., [[ pathlossReferenceRSList-r16 SetupRelease { PathlossReferenceRSList-r16} OPTIONAL -- Need M ]], [[ usagePDC-r17 ENUMERATED {true} OPTIONAL, -- Need R availableSlotOffsetList-r17 SEQUENCE (SIZE(1..4)) OF AvailableSlotOffset-r17 OPTIONAL, -- Need R followUnifiedTCI-StateSRS-r17 ENUMERATED {enabled} OPTIONAL -- Need R ]], [[ applyIndicatedTCI-State-r18 ENUMERATED {first, second} OPTIONAL -- Cond FollowUTCI ]] } AvailableSlotOffset-r17 ::= INTEGER (0..7) PathlossReferenceRS-Config ::= CHOICE { ssb-Index SSB-Index, csi-RS-Index NZP-CSI-RS-ResourceId } PathlossReferenceRSList-r16 ::= SEQUENCE (SIZE (1..maxNrofSRS-PathlossReferenceRS-r16)) OF PathlossReferenceRS-r16 PathlossReferenceRS-r16 ::= SEQUENCE { srs-PathlossReferenceRS-Id-r16 SRS-PathlossReferenceRS-Id-r16, pathlossReferenceRS-r16 PathlossReferenceRS-Config } SRS-PathlossReferenceRS-Id-r16 ::= INTEGER (0..maxNrofSRS-PathlossReferenceRS-1-r16) SRS-PosResourceSet-r16 ::= SEQUENCE { srs-PosResourceSetId-r16 SRS-PosResourceSetId-r16, srs-PosResourceIdList-r16 SEQUENCE (SIZE(1..maxNrofSRS-ResourcesPerSet)) OF SRS-PosResourceId-r16 OPTIONAL, -- Cond Setup resourceType-r16 CHOICE { aperiodic-r16 SEQUENCE { aperiodicSRS-ResourceTriggerList-r16 SEQUENCE (SIZE(1..maxNrofSRS-TriggerStates-1)) OF INTEGER (1..maxNrofSRS-TriggerStates-1) OPTIONAL, -- Need M ... }, semi-persistent-r16 SEQUENCE { ... }, periodic-r16 SEQUENCE { ... } }, alpha-r16 Alpha OPTIONAL, -- Need S p0-r16 INTEGER (-202..24) OPTIONAL, -- Cond Setup pathlossReferenceRS-Pos-r16 CHOICE { ssb-IndexServing-r16 SSB-Index, ssb-Ncell-r16 SSB-InfoNcell-r16, dl-PRS-r16 DL-PRS-Info-r16 } OPTIONAL, -- Need M ..., [[ srs-PosHyperSFN-Index-r18 ENUMERATED {even0, odd1} OPTIONAL -- Need S ]] } SRS-ResourceSetId ::= INTEGER (0..maxNrofSRS-ResourceSets-1) SRS-PosResourceSetId-r16 ::= INTEGER (0..maxNrofSRS-PosResourceSets-1-r16) SRS-Resource ::= SEQUENCE { srs-ResourceId SRS-ResourceId, nrofSRS-Ports ENUMERATED {port1, ports2, ports4}, ptrs-PortIndex ENUMERATED {n0, n1 } OPTIONAL, -- Need R transmissionComb CHOICE { n2 SEQUENCE { combOffset-n2 INTEGER (0..1), cyclicShift-n2 INTEGER (0..7) }, n4 SEQUENCE { combOffset-n4 INTEGER (0..3), cyclicShift-n4 INTEGER (0..11) } }, resourceMapping SEQUENCE { startPosition INTEGER (0..5), nrofSymbols ENUMERATED {n1, n2, n4}, repetitionFactor ENUMERATED {n1, n2, n4} }, freqDomainPosition INTEGER (0..67), freqDomainShift INTEGER (0..268), freqHopping SEQUENCE { c-SRS INTEGER (0..63), b-SRS INTEGER (0..3), b-hop INTEGER (0..3) }, groupOrSequenceHopping ENUMERATED { neither, groupHopping, sequenceHopping }, resourceType CHOICE { aperiodic SEQUENCE { ... }, semi-persistent SEQUENCE { periodicityAndOffset-sp SRS-PeriodicityAndOffset, ... }, periodic SEQUENCE { periodicityAndOffset-p SRS-PeriodicityAndOffset, ... } }, sequenceId INTEGER (0..1023), spatialRelationInfo SRS-SpatialRelationInfo OPTIONAL, -- Need R ..., [[ resourceMapping-r16 SEQUENCE { startPosition-r16 INTEGER (0..13), nrofSymbols-r16 ENUMERATED {n1, n2, n4}, repetitionFactor-r16 ENUMERATED {n1, n2, n4} } OPTIONAL -- Need R ]], [[ spatialRelationInfo-PDC-r17 SetupRelease { SpatialRelationInfo-PDC-r17 } OPTIONAL, -- Need M resourceMapping-r17 SEQUENCE { startPosition-r17 INTEGER (0..13), nrofSymbols-r17 ENUMERATED {n1, n2, n4, n8, n10, n12, n14}, repetitionFactor-r17 ENUMERATED {n1, n2, n4, n5, n6, n7, n8, n10, n12, n14} } OPTIONAL, -- Need R partialFreqSounding-r17 SEQUENCE { startRBIndexFScaling-r17 CHOICE{ startRBIndexAndFreqScalingFactor2-r17 INTEGER (0..1), startRBIndexAndFreqScalingFactor4-r17 INTEGER (0..3) }, enableStartRBHopping-r17 ENUMERATED {enable} OPTIONAL -- Need R } OPTIONAL, -- Need R transmissionComb-n8-r17 SEQUENCE { combOffset-n8-r17 INTEGER (0..7), cyclicShift-n8-r17 INTEGER (0..5) } OPTIONAL, -- Need R srs-TCI-State-r17 CHOICE { srs-UL-TCI-State TCI-UL-StateId-r17, srs-DLorJointTCI-State TCI-StateId } OPTIONAL -- Need R ]], [[ repetitionFactor-v1730 ENUMERATED {n3} OPTIONAL, -- Need R srs-DLorJointTCI-State-v1730 SEQUENCE { cellAndBWP-r17 ServingCellAndBWP-Id-r17 } OPTIONAL -- Cond DLorJointTCI-SRS ]], [[ nrofSRS-Ports-n8-r18 ENUMERATED {ports8, ports8tdm} OPTIONAL, -- Need R combOffsetHopping-r18 SEQUENCE { hoppingId-r18 INTEGER (0..1023) OPTIONAL, -- Need R hoppingSubset-r18 CHOICE { transmissionComb-n4 BIT STRING (SIZE (4)), transmissionComb-n8 BIT STRING (SIZE (8)) } OPTIONAL, -- Need R hoppingWithRepetition-r18 ENUMERATED {symbol, repetition} OPTIONAL -- Need R } OPTIONAL, -- Need R cyclicShiftHopping-r18 SEQUENCE { hoppingId-r18 INTEGER (0..1023) OPTIONAL, -- Need R hoppingSubset-r18 CHOICE { transmissionComb-n2 BIT STRING (SIZE (8)), transmissionComb-n4 BIT STRING (SIZE (12)), transmissionComb-n8 BIT STRING (SIZE (6)) } OPTIONAL, -- Need R hoppingFinerGranularity-r18 ENUMERATED {enable} OPTIONAL -- Need R } OPTIONAL -- Need R ]] } SRS-PosResource-r16::= SEQUENCE { srs-PosResourceId-r16 SRS-PosResourceId-r16, transmissionComb-r16 CHOICE { n2-r16 SEQUENCE { combOffset-n2-r16 INTEGER (0..1), cyclicShift-n2-r16 INTEGER (0..7) }, n4-r16 SEQUENCE { combOffset-n4-r16 INTEGER (0..3), cyclicShift-n4-r16 INTEGER (0..11) }, n8-r16 SEQUENCE { combOffset-n8-r16 INTEGER (0..7), cyclicShift-n8-r16 INTEGER (0..5) }, ... }, resourceMapping-r16 SEQUENCE { startPosition-r16 INTEGER (0..13), nrofSymbols-r16 ENUMERATED {n1, n2, n4, n8, n12} }, freqDomainShift-r16 INTEGER (0..268), freqHopping-r16 SEQUENCE { c-SRS-r16 INTEGER (0..63), ... }, groupOrSequenceHopping-r16 ENUMERATED { neither, groupHopping, sequenceHopping }, resourceType-r16 CHOICE { aperiodic-r16 SEQUENCE { slotOffset-r16 INTEGER (1..32) OPTIONAL, -- Need S ... }, semi-persistent-r16 SEQUENCE { periodicityAndOffset-sp-r16 SRS-PeriodicityAndOffset-r16, ..., [[ periodicityAndOffset-sp-Ext-r16 SRS-PeriodicityAndOffsetExt-r16 OPTIONAL -- Need R ]] }, periodic-r16 SEQUENCE { periodicityAndOffset-p-r16 SRS-PeriodicityAndOffset-r16, ..., [[ periodicityAndOffset-p-Ext-r16 SRS-PeriodicityAndOffsetExt-r16 OPTIONAL -- Need R ]] } }, sequenceId-r16 INTEGER (0..65535), spatialRelationInfoPos-r16 SRS-SpatialRelationInfoPos-r16 OPTIONAL, -- Need R ..., [[ srs-PosHyperSFN-Index-r18 ENUMERATED {even0, odd1} OPTIONAL, --Need S txHoppingConfig-r18 TxHoppingConfig-r18 OPTIONAL --Need R ]] } SRS-SpatialRelationInfo ::= SEQUENCE { servingCellId ServCellIndex OPTIONAL, -- Need S referenceSignal CHOICE { ssb-Index SSB-Index, csi-RS-Index NZP-CSI-RS-ResourceId, srs SEQUENCE { resourceId SRS-ResourceId, uplinkBWP BWP-Id } } } SRS-SpatialRelationInfoPos-r16 ::= CHOICE { servingRS-r16 SEQUENCE { servingCellId ServCellIndex OPTIONAL, -- Need S referenceSignal-r16 CHOICE { ssb-IndexServing-r16 SSB-Index, csi-RS-IndexServing-r16 NZP-CSI-RS-ResourceId, srs-SpatialRelation-r16 SEQUENCE { resourceSelection-r16 CHOICE { srs-ResourceId-r16 SRS-ResourceId, srs-PosResourceId-r16 SRS-PosResourceId-r16 }, uplinkBWP-r16 BWP-Id } } }, ssb-Ncell-r16 SSB-InfoNcell-r16, dl-PRS-r16 DL-PRS-Info-r16 } SSB-Configuration-r16 ::= SEQUENCE { ssb-Freq-r16 ARFCN-ValueNR, halfFrameIndex-r16 ENUMERATED {zero, one}, ssbSubcarrierSpacing-r16 SubcarrierSpacing, ssb-Periodicity-r16 ENUMERATED { ms5, ms10, ms20, ms40, ms80, ms160, spare2,spare1 } OPTIONAL, -- Need S sfn0-Offset-r16 SEQUENCE { sfn-Offset-r16 INTEGER (0..1023), integerSubframeOffset-r16 INTEGER (0..9) OPTIONAL -- Need R } OPTIONAL, -- Need R sfn-SSB-Offset-r16 INTEGER (0..15), ss-PBCH-BlockPower-r16 INTEGER (-60..50) OPTIONAL -- Cond Pathloss } SSB-InfoNcell-r16 ::= SEQUENCE { physicalCellId-r16 PhysCellId, ssb-IndexNcell-r16 SSB-Index OPTIONAL, -- Need S ssb-Configuration-r16 SSB-Configuration-r16 OPTIONAL -- Need S } DL-PRS-Info-r16 ::= SEQUENCE { dl-PRS-ID-r16 INTEGER (0..255), dl-PRS-ResourceSetId-r16 INTEGER (0..7), dl-PRS-ResourceId-r16 INTEGER (0..63) OPTIONAL -- Need S } SRS-ResourceId ::= INTEGER (0..maxNrofSRS-Resources-1) SRS-PosResourceId-r16 ::= INTEGER (0..maxNrofSRS-PosResources-1-r16) SRS-PeriodicityAndOffset ::= CHOICE { sl1 NULL, sl2 INTEGER(0..1), sl4 INTEGER(0..3), sl5 INTEGER(0..4), sl8 INTEGER(0..7), sl10 INTEGER(0..9), sl16 INTEGER(0..15), sl20 INTEGER(0..19), sl32 INTEGER(0..31), sl40 INTEGER(0..39), sl64 INTEGER(0..63), sl80 INTEGER(0..79), sl160 INTEGER(0..159), sl320 INTEGER(0..319), sl640 INTEGER(0..639), sl1280 INTEGER(0..1279), sl2560 INTEGER(0..2559) } SRS-PeriodicityAndOffset-r16 ::= CHOICE { sl1 NULL, sl2 INTEGER(0..1), sl4 INTEGER(0..3), sl5 INTEGER(0..4), sl8 INTEGER(0..7), sl10 INTEGER(0..9), sl16 INTEGER(0..15), sl20 INTEGER(0..19), sl32 INTEGER(0..31), sl40 INTEGER(0..39), sl64 INTEGER(0..63), sl80 INTEGER(0..79), sl160 INTEGER(0..159), sl320 INTEGER(0..319), sl640 INTEGER(0..639), sl1280 INTEGER(0..1279), sl2560 INTEGER(0..2559), sl5120 INTEGER(0..5119), sl10240 INTEGER(0..10239), sl40960 INTEGER(0..40959), sl81920 INTEGER(0..81919), ... } SRS-PeriodicityAndOffsetExt-r16 ::= CHOICE { sl128 INTEGER(0..127), sl256 INTEGER(0..255), sl512 INTEGER(0..511), sl20480 INTEGER(0..20479) } SpatialRelationInfo-PDC-r17 ::= SEQUENCE { referenceSignal CHOICE { ssb-Index SSB-Index, csi-RS-Index NZP-CSI-RS-ResourceId, dl-PRS-PDC NR-DL-PRS-ResourceID-r17, srs SEQUENCE { resourceId SRS-ResourceId, uplinkBWP BWP-Id }, ... }, ... } TxHoppingConfig-r18 ::= SEQUENCE { overlapValue-r18 ENUMERATED {zeroRB, oneRB, twoRB, fourRB}, numberOfHops INTEGER(1..6), slotOffsetForRemainingHopsList-r18 SEQUENCE (SIZE (1..maxNrofHops-r18-1) ) OF SlotOffsetForRemainingHops-r18, ... } SlotOffsetForRemainingHops-r18 ::= SEQUENCE { slotOffsetRemainingHops-r18 CHOICE { aperiodic-r18 SEQUENCE { slotOffset-r18 INTEGER (1..32) OPTIONAL, -- Need S startPosition-r18 INTEGER (0..13) OPTIONAL, -- Need S ... }, semi-persistent-r18 SEQUENCE { periodicityAndOffset-sp-r18 SRS-PeriodicityAndOffset-r16 OPTIONAL, -- Need R periodicityAndOffset-sp-Ext-r18 SRS-PeriodicityAndOffsetExt-r16 OPTIONAL, -- Need R ... }, periodic-r18 SEQUENCE { periodicityAndOffset-p-r18 SRS-PeriodicityAndOffset-r16 OPTIONAL, -- Need R periodicityAndOffset-p-Ext-r18 SRS-PeriodicityAndOffsetExt-r16 OPTIONAL, -- Need R ... }, ... } } -- TAG-SRS-CONFIG-STOP -- ASN1STOP Editor's Note: The ASN.1 SRS periodicity covering 2048 ms is FFS. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,510 | 5.8.2.8.1 Activation/Deactivation of predefined PCC rules | A predefined PCC rule is configured in the SMF. The traffic detection filters, e.g. IP Packet Filter, required in the UP function can be configured either in the SMF and provided to the UPF, as service data flow filter(s), or be configured in the UPF, as the application detection filter identified by an application identifier. For the latter case, the application identifier has to be configured in the SMF and the UPF. The traffic steering policy information can be only configured in the UPF, together with traffic steering policy identifier(s), while the SMF has to be configured with the traffic steering policy identifier(s). Policies for traffic handling in the UPF, which are referred by some identifiers corresponding to the parameters of a PCC rule, can be configured in the UPF. These traffic handling policies are configured as predefined QER(s), FAR(s) and URR(s). When a predefined PCC rule is activated/deactivated by the PCF, SMF shall decide what information has to be provided to the UPF to enforce the rule based on where the traffic detection filters (i.e. service data flow filter(s) or application detection filter), traffic steering policy information and the policies used for the traffic handling in the UPF are configured and where they are enforced: - If the predefined PCC rule contains an application identifier for which corresponding application detection filters are configured in the UPF, the SMF shall provide a corresponding application identifier to the UPF; - If the predefined PCC rule contains traffic steering policy identifier(s), the SMF shall provide a corresponding traffic steering policy identifier(s) to the UPF; - If the predefined PCC rule contains service data flow filter(s), the SMF shall provide them to the UPF; - If the predefined PCC rule contains some parameters for which corresponding policies for traffic handling in the UPF are configured in the UPF, the SMF shall activate those traffic handling policies via their rule ID(s). The SMF shall maintain the mapping between a PCC rule received over Npcf and the flow level PDR rule(s) used on N4 interface. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.8.2.8.1 |
5,511 | 5.2.21.2.6 Nnsacf_NSAC_LocalNumberUpdate service operation | Service Operation name: Nnsacf_NSAC_LocalNumberUpdate Description: The Primary NSACF uses this service operation to update local maximum number of registered UEs and/or number of PDU sessions of the network slice at NSACFs. Inputs, Required: S-NSSAI, Updated local number (s). Inputs, Optional: None. The S-NSSAI is the network slice for which the NSACF is applying the updated local number update. The updated local number indicates the updated local maximum number of registered UEs, or the updated local maximum number of PDU Sessions of the S-NSSAI. Output, Required: Result indication. Outputs, Optional: None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.21.2.6 |
5,512 | 8.4.2.2.7 Enhanced Downlink Control Channel Performance Requirement Type B - 2 Tx Antenna Port with Colliding CRS Dominant Interferer | The purpose of this test is to verify the Enhanced Downlink Control Channel Performance Requirement Type B for PDCCH/PCFICH with 2 transmit antennas for the case of dominant interferer with the colliding CRS pattern and applying interference model defined in clause B.7.1. For the parameters specified in Table 8.4.2-1 and Table 8.4.2.2.7-1, the average probability of a missed downlink scheduling grant (Pm-dsg) shall be below the specified value in Table 8.4.2.2.7-2. In Table 8.4.2.2.7-1, Cell 1 is the serving cell, and Cell 2 and Cell 3 are the agressor cells. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1, Cell 2 and Cell 3, respectively. The CRS assistance information [7] is provided and includes Cell 2 and Cell 3. Table 8.4.2.2.7-1: Test Parameters for PDCCH/PCFICH Table 8.4.2.2.7-2: Minimum Performance for PDCCH/PCFICH for Enhanced Downlink Control Channel Performance Requirement Type B | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.4.2.2.7 |
5,513 | 5.4 Charging data configuration | Charging interface applications are specified for Rf and Ro in TS 32.299[ Telecommunication management; Charging management; Diameter charging applications ] [50], for Nchf in TS 32.291[ Telecommunication management; Charging management; 5G system, charging service; Stage 3 ] [58], for Ga in TS 32.295[ Telecommunication management; Charging management; Charging Data Record (CDR) transfer ] [54], and for Bx in TS 32.297[ Telecommunication management; Charging management; Charging Data Record (CDR) file format and transfer ] [52] and TS 32.298[ Telecommunication management; Charging management; Charging Data Record (CDR) parameter description ] [51]. The middle tier TSs determine per domain / service /subsystem which of the reference points exist as open interfaces and which of them are internal to integrated NEs (see charging architecture mapping discussion in clause 4.5). In accordance with these prerequisites, the content of charging events, i.e.Information Element (IE), and CDRs, i.e. CDR parameter, is also specified in the middle tier TSs on all the open network interfaces that exist in the respective domain / subsystem / service. The rules governing the presence of IEs or CDR parameters on these interfaces are summarized in this clause. A logical diagram illustrating the possible presence requirements for IEs / CDR parameters ("field categories") is shown in figure 5.4.1. Figure 5.4.1: Logical diagram illustrating the different parameter categories The IE and CDR parameter description tables in the middle tier TSs specify the Mandatory (M), Conditional (C) and Operator provisionable (OC or OM) designations. The category of an IE or CDR parameter can have one of two primary values: M This parameter is Mandatory and shall always be present in the event / CDR. C This parameter shall be present in the event / CDR only when certain Conditions are met. These Conditions are specified as part of the parameter definition. All other parameters are designated as Operator provisionable (O). Using network management functions or specific tools provided by an equipment vendor, operators may choose if they wish to include or omit the parameter from the charging event / CDR. Once omitted, this parameter is not generated in an event / a CDR. To avoid any potential ambiguity, the CTF / CDF / CGF shall be able to provide all these parameters. Only an operator can choose whether or not these parameters should be generated in their system, i.e. included in the charging event / CDR. Those parameters that the operator configures to be present are further divided into mandatory and conditional categories: OM This is a parameter that, if provisioned by the operator to be present, shall always be included in the events / CDRs. In other words, an OM parameter that is provisioned to be present is a mandatory parameter. OC This is a parameter that, if provisioned by the operator to be present, shall be included in the events / CDRs when the specified conditions are met. If provisioned by the operator not to be present, shall not be included in the events / CDRs even the specified conditions are met. In other words, an OC parameter that is configured to be present is a conditional parameter. The IE and CDR parameter tables provide a brief description of each charging event / CDR in the corresponding middle tier TSs. The full definitions of the CDR parameters, sorted by the CDR parameter name in alphabetical order, are provided in TS 32.298[ Telecommunication management; Charging management; Charging Data Record (CDR) parameter description ] [51]. The following principles apply for Information Element (IE) and CDR parameter category across the specifications: - Category for IEs common between the middle tier TSs (stage 2) and TS 32.290[ Telecommunication management; Charging management; 5G system; Services, operations and procedures of charging using Service Based Interface (SBI) ] [57]: IE category in the middle tier TSs takes precedence; - IE category in the middle tier TSs takes precedence over the corresponding IE stage 3 category and syntax in TS 32.291[ Telecommunication management; Charging management; 5G system, charging service; Stage 3 ] [58] and TS 32.299[ Telecommunication management; Charging management; Diameter charging applications ] [50]. - CDR parameter category in the middle tier TSs takes precedence over the corresponding ASN.1 field syntax in TS 32.298[ Telecommunication management; Charging management; Charging Data Record (CDR) parameter description ] [51]. | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 5.4 |
5,514 | 6.10.4 Protection of traffic between UE and SN | This subclause provides the details of the needed SN RRC and UP keys and the algorithms used to protect the traffic whose PDCP terminates on the SN. The UE and SN may either calculate all the SN RRC and UP keys at once or as there are required to be used. The RRC and UP keys are KRRCenc and KRRCint for the SRB whose PDCP terminates on the SN and KUPenc for the DRBs whose PDCP terminate on the SN. When the SN is a gNB, the RRC traffic protection directly between the UE and SN is done using the mechanism described in subclause 6.5 of the present document with the algorithms specified in Annex D of the present document. When the SN is a gNB, the UP traffic protection and activation is done using the mechanism described in subclauses 6.6 of the present document using the algorithms specified in Annex D of the present document. The UP security activation procedure for MR-DC (meaning NR-DC, NE-DC and NGEN-DC) scenarios use the mechanism described in sublcause 6.10.2.1 with the following additional procedures: In the case of split PDU session where some of the DRB(s) is terminated at the MN and some DRB(s) is terminated at the SN, the MN shall ensure that all DRBs which belong to the same PDU session have the same UP integrity protection and ciphering activation. To achieve this, the MN shall inform the SN with its UP integrity protection and ciphering activation decision of any DRB that is offloaded and to be terminated at the SN. The SN shall activate the UP integrity protection and ciphering based on the MN decision. For UP Integrity Protection, if the UE does not indicate that it supports the use of integrity protection with ng-eNB: Case 1: UP security policy indicates UP Integrity Protection "required": In NGEN-DC scenario, the MN shall reject the PDU session. In NE-DC scenario, if the MN decides to activate the UP integrity protection for this PDU session, the MN shall not offload any DRB of the PDU session to the SN. In NR-DC scenario, the MN makes the decision for PDU sessions that are terminated at the MN while the SN makes the decision for PDU sessions that are terminated at the SN. Case 2: UP security policy indicates UP Integrity Protection "preferred": In NGEN-DC scenario, the MN shall always deactivate UP integrity protection. In this case, the SN shall always deactivate the UP integrity protection of any PDU session terminated at the SN. In NE-DC scenario, if the MN has activated any of this PDU session DRBs with UP integrity protection "on", the MN shall not offload any DRB of this PDU session to the SN. However, if the MN has activated all DRBs of this PDU session with integrity protection "off", the MN may offload DRBs of this PDU session to the SN. In this case, the SN shall not activate the UP integrity protection and shall always set the UP integrity protection indication to "off". In NR-DC scenario, the MN makes the decision for PDU sessions that are terminated at the MN while the SN makes the decision for PDU sessions that are terminated at the SN. Case 3: UP security policy indicates UP Integrity Protection "not needed": In all MR-DC scenarios, the MN and SN shall always deactivate UP integrity protection. For UP integrity protection, if the UE indicates that it supports use of integrity protection with ng-eNB, in all 5GC-based MR-DC scenarios, the MN and SN shall make a decision on UP integrity protection according to the UP security policy for PDU sessions which terminate at the MN and SN, respectively, where all DRBs belonging to the same PDU session shall have the integrity protection either "on" or "off". For UP Ciphering Protection: In all MR-DC scenario, the MN and SN shall make a decision on UP ciphering protection according to the UP security policy for PDU sessions which terminate at the MN and SN, respectively, where all DRBs belonging to the same PDU session shall have the ciphering protection either "on" or "off". NOTE 1: A UE that is Rel-16 or prior does not support UP integrity protection with ng-eNB. Therefore, explicit indication, as specified in clause 6.6.4.3, that the UE supports use of UP integrity protection with ng-eNB is required. In all scenarios of MR-DC, the SN shall send the UP integrity protection and encryption indications to the MN in the SN Addition/Modification Request Acknowledgement message. The MN shall forward the UP integrity protection and encryption indications to the UE in RRC Connection Reconfiguration message. The UE activate the UP security protection with the SN based on the UP integrity protection and encryption indications using the scheme described in subclause 6.6.2. If the MN has not activated the RRC security before sending the RRC Connection Reconfiguration message, the MN shall perform AS SMC procedure first. When the SN is a ng-eNB, the RRC and UP traffic is protected using the mechanism described in subclauses 7.4 and 7.3 respectively of TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [10] with the algorithms specified in Annex C of TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [10]. Additionally, the UP traffic is integrity protected based on the UP security policy and the indication that the UE supports the use of UP integrity protection with ng-eNB. NOTE: Void. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.10.4 |
5,515 | 5.4.1.3.7 Abnormal cases | a) Lower layer failure. Upon detection of lower layer failure before the AUTHENTICATION RESPONSE message is received, the network shall abort the procedure. b) Expiry of timer T3560. The network shall, on the first expiry of the timer T3560, retransmit the AUTHENTICATION REQUEST message and shall reset and start timer T3560. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3560, the network shall abort the 5G AKA based primary authentication and key agreement procedure and any ongoing 5GMM specific procedure and release the N1 NAS signalling connection. c) Authentication failure (5GMM cause #20 "MAC failure"). The UE shall send an AUTHENTICATION FAILURE message, with 5GMM cause #20 "MAC failure" according to subclause 5.4.1.3.6, to the network and start timer T3520 (see example in figure 5.4.1.3.7.1). Furthermore, the UE shall stop any of the retransmission timers that are running (e.g. T3510, T3517 or T3521). Upon the first receipt of an AUTHENTICATION FAILURE message from the UE with 5GMM cause #20 "MAC failure", the network may initiate the identification procedure described in subclause 5.4.3. This is to allow the network to obtain the SUCI from the UE. The network may then check that the 5G-GUTI originally used in the 5G authentication challenge corresponded to the correct SUPI. Upon receipt of the IDENTITY REQUEST message from the network, the UE shall proceed as specified in subclause 5.4.3.3. NOTE 1: Upon receipt of an AUTHENTICATION FAILURE message from the UE with 5GMM cause #20 "MAC failure", the network may also terminate the 5G AKA based primary authentication and key agreement procedure (see subclause 5.4.1.3.5). If the mapping of 5G-GUTI to SUPI in the network was incorrect, the network should respond by sending a new AUTHENTICATION REQUEST message to the UE. Upon receiving the new AUTHENTICATION REQUEST message from the network, the UE shall stop the timer T3520, if running, and then process the 5G challenge information as normal. If the mapping of 5G-GUTI to SUPI in the network was correct, the network should terminate the 5G AKA based primary authentication and key agreement procedure by sending an AUTHENTICATION REJECT message (see subclause 5.4.1.3.5). If the network is validated successfully (an AUTHENTICATION REQUEST message that contains a valid SQN and MAC is received), the UE shall send the AUTHENTICATION RESPONSE message to the network and shall start any retransmission timers (e.g. T3510, T3517 or T3521) if they were running and stopped when the UE received the first failed AUTHENTICATION REQUEST message. If the UE receives the second AUTHENTICATION REQUEST message, and the MAC value cannot be resolved, the UE shall follow the procedure specified in this subclause, item c, starting again from the beginning, or if the message contains a UMTS authentication challenge, the UE shall follow the procedure specified in item d. If the SQN is invalid, the UE shall proceed as specified in item f. Figure 5.4.1.3.7.1: Authentication failure during 5G AKA based primary authentication and key agreement procedure d) Authentication failure (5GMM cause #26 "non-5G authentication unacceptable"). The UE shall send an AUTHENTICATION FAILURE message, with 5GMM cause #26 "non-5G authentication unacceptable", to the network and start the timer T3520 (see example in figure 5.4.1.3.7.1). Furthermore, the UE shall stop any of the retransmission timers that are running (e.g. T3510, T3517 or T3521). Upon the first receipt of an AUTHENTICATION FAILURE message from the UE with 5GMM cause #26 "non-5G authentication unacceptable", the network may initiate the identification procedure described in subclause 5.4.3. This is to allow the network to obtain the SUCI from the UE. The network may then check that the 5G-GUTI originally used in the 5G authentication challenge corresponded to the correct SUPI. Upon receipt of the IDENTITY REQUEST message from the network, the UE shall proceed as specified in subclause 5.4.3.3. NOTE 2: Upon receipt of an AUTHENTICATION FAILURE message from the UE with 5GMM cause #26 "non-5G authentication unacceptable", the network may also terminate the 5G AKA based primary authentication and key agreement procedure (see subclause 5.4.1.3.5). If the mapping of 5G-GUTI to SUPI in the network was incorrect, the network should respond by sending a new AUTHENTICATION REQUEST message to the UE. Upon receiving the new AUTHENTICATION REQUEST message from the network, the UE shall stop the timer T3520, if running, and then process the 5G challenge information as normal. If the mapping of 5G-GUTI to SUPI in the network was correct, the network should terminate the 5G AKA based primary authentication and key agreement authentication procedure by sending an AUTHENTICATION REJECT message (see subclause 5.4.1.3.5). If the network is validated successfully (an AUTHENTICATION REQUEST message that contains a valid 5G authentication challenge is received), the UE shall send the AUTHENTICATION RESPONSE message to the network and shall start any retransmission timers (e.g. T3510, T3517 or T3521) if they were running and stopped when the UE received the first failed AUTHENTICATION REQUEST message. e) Authentication failure (5GMM cause #71 "ngKSI already in use"). The UE shall send an AUTHENTICATION FAILURE message, with 5GMM cause #71 "ngKSI already in use", to the network and start the timer T3520 (see example in figure 5.4.1.3.7.1). Furthermore, the UE shall stop any of the retransmission timers that are running (e.g. T3510, T3517 or T3521). Upon the first receipt of an AUTHENTICATION FAILURE message from the UE with 5GMM cause #71 "ngKSI already in use", the network performs necessary actions to select a new ngKSI and send the same 5G authentication challenge to the UE. NOTE 3: Upon receipt of an AUTHENTICATION FAILURE message from the UE with 5GMM cause #71 "ngKSI already in use", the network may also re-initiate the 5G AKA based primary authentication and key agreement procedure (see subclause 5.4.1.3.2). Upon receiving the new AUTHENTICATION REQUEST message from the network, the UE shall stop the timer T3520, if running, and then process the 5G challenge information as normal. If the network is validated successfully (an AUTHENTICATION REQUEST message that contains a valid ngKSI, SQN and MAC is received), the UE shall send the AUTHENTICATION RESPONSE message to the network and shall start any retransmission timers (e.g. T3510, T3517 or T3521) if they were running and stopped when the UE received the first failed AUTHENTICATION REQUEST message. f) Authentication failure (5GMM cause #21 "synch failure"). The UE shall send an AUTHENTICATION FAILURE message, with 5GMM cause #21 "synch failure", to the network and start the timer T3520 (see example in figure 5.4.1.3.7.1). Furthermore, the UE shall stop any of the retransmission timers that are running (e.g. T3510, T3517 or T3521). Upon the first receipt of an AUTHENTICATION FAILURE message from the UE with the 5GMM cause #21 "synch failure", the network shall use the returned AUTS parameter from the authentication failure parameter IE in the AUTHENTICATION FAILURE message, to re-synchronise. The re-synchronisation procedure requires the AMF to delete all unused authentication vectors for that SUPI and obtain new vectors from the UDM/AUSF. When re-synchronisation is complete, the network shall initiate the 5G AKA based primary authentication and key agreement procedure. Upon receipt of the AUTHENTICATION REQUEST message, the UE shall stop the timer T3520, if running. NOTE 4: Upon receipt of two consecutive AUTHENTICATION FAILURE messages from the UE with 5GMM cause #21 "synch failure", the network may terminate the 5G AKA based primary authentication and key agreement procedure by sending an AUTHENTICATION REJECT message. If the network is validated successfully (a new AUTHENTICATION REQUEST message is received which contains a valid SQN and MAC) while T3520 is running, the UE shall send the AUTHENTICATION RESPONSE message to the network and shall start any retransmission timers (e.g. T3510, T3517 or T3521), if they were running and stopped when the UE received the first failed AUTHENTICATION REQUEST message. Upon receipt of an AUTHENTICATION REJECT message, the UE shall perform the actions as specified in subclause 5.4.1.3.5. g) Network failing the authentication check. If the UE deems that the network has failed the authentication check, then it shall request RRC to locally release the RRC connection and treat the active cell as barred (see 3GPP TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [28] or 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [25C]). The UE shall start any retransmission timers (e.g. T3510, T3517 or T3521), if they were running and stopped when the UE received the first AUTHENTICATION REQUEST message containing an incorrect authentication challenge data causing authentication failure. h) Transmission failure of AUTHENTICATION RESPONSE message or AUTHENTICATION FAILURE message indication from lower layers (if the 5G AKA based primary authentication and key agreement procedure is triggered by a registration procedure). The UE shall stop the timer T3520, if running, and re-initiate the registration procedure. i) Transmission failure of AUTHENTICATION RESPONSE message or AUTHENTICATION FAILURE message indication with change in the current TAI (if the 5G AKA based primary authentication and key agreement procedure is triggered by a service request procedure). The UE shall stop the timer T3520, if running. If the current TAI is not in the TAI list, the 5G AKA based primary authentication and key agreement procedure shall be aborted and a registration procedure for mobility and periodic registration update shall be initiated. If the current TAI is still part of the TAI list, it is up to the UE implementation how to re-run the ongoing procedure that triggered the 5G AKA based primary authentication and key agreement procedure. j) Transmission failure of AUTHENTICATION RESPONSE message or AUTHENTICATION FAILURE message indication without change in the current TAI (if the authentication procedure is triggered by a service request procedure). The UE shall stop the timer T3520, if running. It is up to the UE implementation how to re-run the ongoing procedure that triggered the 5G AKA based primary authentication and key agreement procedure. k) Lower layers indication of non-delivered NAS PDU due to handover. If the AUTHENTICATION REQUEST message could not be delivered due to an intra AMF handover and the target TA is included in the TAI list, then upon successful completion of the intra AMF handover the AMF shall retransmit the AUTHENTICATION REQUEST message. If a failure of handover procedure is reported by the lower layer and the N1 NAS signalling connection exists, the AMF shall retransmit the AUTHENTICATION REQUEST message. l) Change in the current TAI. If the current TAI is not in the TAI list before the AUTHENTICATION RESPONSE message is sent, the UE may discard sending the AUTHENTICATION RESPONSE message to the network and continue with the initiation of the registration procedure for mobility and periodic registration update as described in subclause 5.5.1.3.2. m) AUTHENTICATION REJECT message is received without integrity protection and neither timer T3516 nor T3520 is running. If an AUTHENTICATION REJECT message is received without integrity protection and if neither timer T3516 nor T3520 is running, then the UE shall discard the AUTHENTICATION REJECT message. Additionally, the UE may request RRC to locally release the RRC connection and treat the active cell as barred (see 3GPP TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [28] or 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [25C]). For items c, d, e, and f if no emergency service is started or is ongoing: The UE shall stop timer T3520, if the timer is running and the UE enters 5GMM-IDLE mode, e.g. upon detection of a lower layer failure, release of the N1 NAS signalling connection, or as the result of an inter-system change in 5GMM-CONNECTED mode from N1 mode to S1 mode. The UE shall deem that the network has failed the authentication check or assume that the authentication is not genuine and proceed as described in item g above if any of the following occurs: - the timer T3520 expires; - the UE detects any combination of the 5G authentication failures: 5GMM causes #20 "MAC failure", #21 "synch failure", #26 "non-5G authentication unacceptable" or #71 "ngKSI already in use", during three consecutive authentication challenges. The 5G authentication challenges shall be considered as consecutive only, if the 5G authentication challenges causing the second and third 5G authentication failure are received by the UE, while the timer T3520 started after the previous 5G authentication failure is running. For items c, d, e, and f if there is an emergency service started or is ongoing: The UE shall stop timer T3520, if the timer is running and the UE enters 5GMM-IDLE mode, e.g. upon detection of a lower layer failure, release of the N1 NAS signalling connection, or as the result of an inter-system change in 5GMM-CONNECTED mode from N1 mode to S1 mode. If there is an ongoing: - service request procedure for emergency services fallback the UE shall abort the service request procedure, stop timer T3517 and locally release any resources allocated for the service request procedure and enter state 5GMM-REGISTERED; or - registration procedure for mobility and periodic registration update triggered upon a request from the upper layers to perform an emergency services fallback procedure the UE shall abort the registration procedure for mobility and periodic registration update, stop timer T3510 and locally release any resources allocated for the registration procedure for mobility and periodic registration update and enter the state 5GMM-REGISTERED; and the UE shall attempt to select an E-UTRA cell connected to EPC or 5GCN according to the domain priority and selection rules specified in 3GPP TS 23.167[ IP Multimedia Subsystem (IMS) emergency sessions ] [6]. If the UE finds a suitable E-UTRA cell, it proceeds with the appropriate EMM or 5GMM procedures. If the UE operating in single-registration mode has changed to S1 mode, it shall disable the N1 mode capability for 3GPP access. Depending on local requirements or operator preference for emergency services, if the UE has an emergency PDU session established or is establishing an emergency PDU session, the AMF need not follow the procedures specified for the authentication failure specified in the present subclause. The AMF may respond to the AUTHENTICATION FAILURE message by initiating the security mode control procedure selecting the "null integrity protection algorithm" 5G-IA0, "null ciphering algorithm" 5G-EA0 or may abort the 5G AKA based primary authentication and key agreement procedure and continue using the current security context, if any. The AMF shall indicate to the SMF to perform the release of all non-emergency PDU sessions, if any. If there is an ongoing PDU session establishment procedure, the AMF shall indicate to the SMF to perform the release of all non-emergency PDU sessions upon completion of the PDU session establishment procedure. The network shall behave as if the UE is registered for emergency services. If a UE has an emergency PDU session established or is establishing an emergency PDU session and sends an AUTHENTICATION FAILURE message to the AMF with the 5GMM cause appropriate for these cases (#20, #21, #26, or #71 respectively) and receives the SECURITY MODE COMMAND message before the timeout of timer T3520, the UE shall deem that the network has passed the authentication check successfully, stop timer T3520, respectively, and execute the security mode control procedure. If a UE has an emergency PDU session established or is establishing an emergency PDU session when timer T3520 expires, the UE shall not deem that the network has failed the authentication check and not behave as described in item g. Instead the UE shall continue using the current security context, if any, release all non-emergency PDU sessions, if any, by initiating UE-requested PDU session release procedure. If there is an ongoing PDU session establishment procedure, the UE shall release all non-emergency PDU sessions upon completion of the PDU session establishment procedure. The UE shall start any retransmission timers (e.g. T3510, T3517 or T3521) if: - they were running and stopped when the UE received the AUTHENTICATION REQUEST message and detected an authentication failure; and - the procedures associated with these timers have not yet been completed. The UE shall behave as if the UE is registered for emergency services. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.4.1.3.7 |
5,516 | 5.4.3.5 Mobility from NR failure | The UE shall: 1> if the UE does not succeed in establishing the connection to the target radio access technology: 2> if the targetRAT-Type in the received MobilityFromNRCommand is set to eutra and the UE supports Radio Link Failure Report for Inter-RAT MRO EUTRA: 3> store handover failure information in VarRLF-Report according to 5.3.10.5; 2> if voiceFallbackIndication is included in the MobilityFromNRCommand message; or 2> if the mobility from NR procedure is for emergency services fallback as specified in TS 23.502[ Procedures for the 5G System (5GS) ] [43]: 3> attempt to select an E-UTRA cell: 4> if a suitable E-UTRA cell is selected; or 4> if no suitable E-UTRA cell is available and an acceptable E-UTRA cell supporting emergency call is selected when the UE has an ongoing emergency call: 5> perform the actions upon going to RRC_IDLE as specified in 5.3.11, with release cause 'RRC connection failure'; 4> else: 5> revert back to the configuration used in the source PCell; 5> initiate the connection re-establishment procedure as specified in clause 5.3.7; NOTE: It is left to UE implementation to determine whether the mobility from NR procedure is for emergency services fallback as specified in TS 23.502[ Procedures for the 5G System (5GS) ] [43]. 2> else: 3> revert back to the configuration used in the source PCell; 3> initiate the connection re-establishment procedure as specified in clause 5.3.7; 1> else if the UE is unable to comply with any part of the configuration included in the MobilityFromNRCommand message; or 1> if there is a protocol error in the inter RAT information included in the MobilityFromNRCommand message, causing the UE to fail the procedure according to the specifications applicable for the target RAT: 2> if the targetRAT-Type in the received MobilityFromNRCommand is set to eutra and the UE supports Radio Link Failure Report for Inter-RAT MRO EUTRA: 3> store handover failure information in VarRLF-Report according to 5.3.10.5; 2> revert back to the configuration used in the source PCell; 2> initiate the connection re-establishment procedure as specified in clause 5.3.7. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.4.3.5 |
5,517 | 5.8.18.3 NR sidelink positioning transmission | A UE capable of NR sidelink positioning that is configured by upper layers to transmit SL-PRS shall: 1> if the conditions for NR sidelink positioning operation as defined in 5.8.2 are met: 2> if the frequency used for NR sidelink positioning is included in sl-FreqInfoToAddModList in sl-ConfigDedicatedNR within RRCReconfiguration message or included in sl-PosConfigCommonNR within SIB23: 3> if the UE is in RRC_CONNECTED and uses the frequency included in sl-ConfigDedicatedNR within RRCReconfiguration message: 4> if the UE is configured with sl-ScheduledConfig: 5> if T310 for MCG or T311 is running; and if sl-PRS-TxPoolExceptional or sl-TxPoolExceptional is included in sl-FreqInfoList for the concerned frequency in SIB23 or included in sl-ConfigDedicatedNR in RRCReconfiguration; or 5> if T301 is running and the cell on which the UE initiated RRC connection re-establishment provides SIB23 including sl-PRS-TxPoolExceptional or sl-TxPoolExceptional for the concerned frequency; or 5> if T304 for MCG is running and the UE is configured with sl-PRS-TxPoolExceptional or sl-TxPoolExceptional included in sl-ConfigDedicatedNR for the concerned frequency in RRCReconfiguration: 6> configure lower layers to perform the sidelink resource allocation scheme 2 based on random selection using the resource pool indicated by sl-PRS-TxPoolExceptional or sl-TxPoolExceptional as defined in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3]; 5> else: 6> configure lower layers to perform the sidelink resource allocation scheme 1 for NR sidelink positioning; 5> if T311 is running, configure the lower layers to release the resources indicated by rrc-ConfiguredSidelinkGrant (if any); 4> if the UE is configured with sl-UE-SelectedConfig: 5> if a result of full sensing, if selected and is allowed by sl-PosAllowedResourceSelectionConfig, on the resources configured in sl-PRS-TxPoolSelectedNormal or by sl-AllowedResourceSelectionConfig, on the resources configured in sl-TxPoolSelectedNormal for the concerned frequency included in sl-ConfigDedicatedNR within RRCReconfiguration is not available in accordance with TS 38.214[ NR; Physical layer procedures for data ] [19]; 6> if sl-TxPoolExceptional or sl-PRS-TxPoolExceptional for the concerned frequency is included in RRCReconfiguration; or 6> if the PCell provides SIB25 including sl-TxPoolExceptional or sl-PRS-TxPoolExceptional in sl-FreqInfoList for the concerned frequency: 7> configure lower layers to perform the sidelink resource allocation scheme 2 based on random selection using the pool of resources indicated by sl-TxPoolExceptional or sl-PRS-TxPoolExceptional as defined in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3]; 5> else, if the sl-PRS-TxPoolSelectedNormal or sl-TxPoolSelectedNormal for the concerned frequency is included in the sl-ConfigDedicatedNR within RRCReconfiguration: 6> configure lower layers to perform the sidelink resource allocation scheme 2 based on resource selection operation according to sl-PosAllowedResourceSelectionConfig (as defined in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3] and TS 38.214[ NR; Physical layer procedures for data ] [19]) using the pools of resources indicated by sl-PRS-TxPoolSelectedNormalNormal for the concerned frequency, or based on resource selection operation according to sl-AllowedResourceSelectionConfig (as defined in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3] and TS 38.214[ NR; Physical layer procedures for data ] [19]) using the pools of resources indicated by sl-TxPoolSelectedNormal for the concerned frequency; 3> else: 4> if the cell chosen for NR sidelink positioning transmission provides SIB23: 5> if SIB23 includes sl-PosTxPoolSelectedNormal for the concerned frequency, and a result of full sensing, if selected and is allowed by sl-PosAllowedResourceSelectionConfig, on the resources configured in the sl-PRS-TxPoolSelectedNormal is available in accordance with TS 38.214[ NR; Physical layer procedures for data ] [19] or random selection, if allowed by sl-PosAllowedResourceSelectionConfig, is selected: 6> configure lower layers to perform the sidelink resource allocation scheme 2 based on resource selection operation according to sl-PosAllowedResourceSelectionConfig using the pools of resources indicated by sl-PosTxPoolSelectedNormal for the concerned frequency as defined in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3]; 5> if SIB23 includes sl-TxPoolSelectedNormal for the concerned frequency, and a result of full sensing, if selected and is allowed by sl-AllowedResourceSelectionConfig, on the resources configured in the sl-TxPoolSelectedNormal is available in accordance with TS 38.214[ NR; Physical layer procedures for data ] [19] or random selection, if allowed by sl-AllowedResourceSelectionConfig, is selected: 6> configure lower layers to perform the sidelink resource allocation scheme 2 based on resource selection operation according to sl-AllowedResourceSelectionConfig using the pools of resources indicated by sl-TxPoolSelectedNormal for the concerned frequency as defined in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3]; 5> else if SIB23 includes sl-PRS-TxPoolExceptional or sl-TxPoolExceptional for the concerned frequency: 6> from the moment the UE initiates RRC connection establishment or RRC connection resume, until receiving an RRCReconfiguration including sl-ConfigDedicatedNR, or receiving an RRCRelease or an RRCReject; or 6> if a result of full sensing, if selected and is allowed by sl-PosAllowedResourceSelectionConfig, on the resources configured in sl-PRS-TxPoolSelectedNormal or if selected and is allowed by sl-AllowedResourceSelectionConfig, on the resources configured in sl-TxPoolSelectedNormal for the concerned frequency in SIB23 is not available in accordance with TS 38.214[ NR; Physical layer procedures for data ] [19]: 7> configure lower layers to perform the sidelink resource allocation scheme 2 based on random selection (as defined in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3]) using the pool of resources indicated by sl-PRS-TxPoolExceptional or sl-TxPoolExceptional for the concerned frequency; 2> else: 3> configure lower layers to perform the sidelink resource allocation scheme 2 based on resource selection operation according to sl-PosAllowedResourceSelectionConfig (as defined in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3] and TS 38.214[ NR; Physical layer procedures for data ] [19]) using the pools of resources indicated by sl-PRS-TxPoolSelectedNormal in SL-PosPreconfigurationNR for the concerned frequency or based on sl-AllowedResourceSelectionConfig (as defined in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3] and TS 38.214[ NR; Physical layer procedures for data ] [19]) using the pools of resources indicated by sl-TxPoolSelectedNormal in SidelinkPreconfigNR for the concerned frequency.. NOTE: The same Notes as in clause 5.8.8 are applicable for this clause unless otherwise stated. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.18.3 |
5,518 | 16.4.7.2 Coding 3GPP Vendor-Specific RADIUS attributes | In this subclause the provisions of IETF RFC 2865 [38] apply, which in particular specify the following: - the Length field of an attribute is one octet, and it indicates the length of this Attribute including the Type, Length and Value fields. - type String may be 1-253 octets long and it contains binary data (values 0 through 255 decimal, inclusive). Strings of length zero (0) shall not be sent, but the entire attribute shall be omitted. A NULL terminating character shall not be appended to an attribute of type String. - type Text may be 1-253 octets long and it contains UTF-8 encoded characters. Text of length zero (0) shall not be sent, but the entire attribute shall be omitted. A NULL terminating character shall not be appended to an attribute of type Text. - type Address is 32 bit value and most significant octet is the first one. - type Integer is 32 bit unsigned value and most significant octet is the first one. The RADIUS vendor Attribute is encoded as follows (as per IETF RFC 2865 [38]) n 7 3GPP Vendor Id = 10415 The string part is encoded as follows: m 2 and m 248 The 3GPP specific attributes encoding is clarified below. NOTE 1: Unless otherwise stated, the encoding of the value field of a 3GPP vendor-specific attribute is identical for Gi and Sgi. 1 – 3GPP-IMSI 3GPP Type: 1 n 15 Length: m 17 IMSI value: Text type: A GGSN (or a P-GW) receives IMSI that is encoded according to 3GPP TS 29.060[ General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface ] [24] (or 3GPP TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [81]) and converts IMSI into the UTF-8 characters, which are encoded as defined in 3GPP TS 23.003[ Numbering, addressing and identification ] [40]. There shall be no padding characters between the MCC and MNC, and between the MNC and MSIN. If the IMSI is less than 15 digits, the padding in the GTP information element shall be removed by the GGSN (or the P-GW) and not encoded in this sub-attribute. 2 – 3GPP-Charging ID 3GPP Type: 2 Length: 6 Charging ID value: 32 bits unsigned integer 3 – 3GPP-PDP type 3GPP Type: 3 Length: 6 PDP type value: Unsigned 32 bits integer type PDP type may have the following values: 0 = IPv4 1 = PPP 2 = IPv6 3 = IPv4v6 4 = Non-IP 5 = Unstructured 6 = Ethernet For P-GW, this sub-attribute represents PDN Type and therefore only the values "0", "2", "3" and "4" are applicable. The value 5 Unstructured and 6 Ethernet of PDP type does not apply for the present specification. For specifications referencing the present RADIUS VSA, those values shall only apply if it is explicitely endorsed within the referencing specification. 4 – 3GPP-Charging Gateway address 3GPP Type: 4 Length: 6 Charging GW address value: Address type. 5 – 3GPP-GPRS Negotiated QoS profile 3GPP Type: 5 Length: For GGSN, L 37 (release 7 or higher) or L 33 (release 6 or release 5) or L 27 (release 4 or release 99) or L = 11 (release 98). For P-GW, the length varies depending on the value of QCI. See below for details. QoS profile value: Text type UTF-8 encoded QoS profile syntax: "<Release indicator> – <release specific QoS IE UTF-8 encoding>" <Release indicator> = UTF-8 encoded number (two characters) : For GGSN: "98" = Release 98 "99"= Release 99 or release 4 "05"= Release 5 or release 6 "07"= Release 7 or higher For P-GW: "08"= Release 8 or higher For SMF: "15"= Release 15 or higher <release specific QoS profile UTF-8 encoding> = UTF-8 encoded QoS profile for the release indicated by the release indicator. The UTF-8 encoding of a QoS IE is defined as follows: each octet is described by 2 UTF-8 encoded characters, defining its hexadecimal representation. For GGSN: The QoS profile definition is in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [54]. The release 98 QoS profile data is 3 octets long, which then results in a 6 octets UTF-8 encoded string. The release 99 and release 4 QoS profile data is 11 octets long, which results in a 22 octets UTF-8 encoded string. The release 5 and release 6 QoS profile data is 14 octets long, which results in a 28 octets UTF-8 encoded string. The release 7 (and higher) QoS profile data is 16 octets long, which results in a 32 octets UTF-8 encoded string. For P-GW: It contains the following QoS parameters associated with the EPS bearer: - QCI - ARP - GBR QoS information (UL/DL MBR, UL/DL GBR) or UL/DL APN-AMBR. In other words if the value of QCI indicates a GBR bearer, the GBR QoS information shall be present. If the value of QCI indicates a non-GBR bearer, the APN-AMBR information shall be present. The encoding of the EPS bearer QoS profile parameters is specified in 3GPP TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [81]: ARP is specified in Bearer QoS IE; QCI, UL MBR, DL MBR, UL MBR and DL MBR are specified in Flow QoS IE; UL APN-AMBR and DL APN-AMBR are specified in AMBR IE. For GBR QCIs, the encoding of UTF-8 encoded QoS Profile field shall be as follows: For non-GBR QCIs, the UL/DL MBR and UL/DL GBR fields shall not be present; UL APN-AMBR and DL APN-AMBR fields shall be encoded (in UTF-8 encoded format) respectively after the QCI field. For SMF: It contains the following QoS parameters associated with the QoS flow: - 5QI - ARP - GBR QoS information (UL/DL MFBR, UL/DL GFBR) or UL/DL Session-AMBR. In other words if the value of 5QI indicates a GBR QoS flow, the GBR QoS information shall be present. If the value of 5QI indicates a non-GBR QoS flow, the Session-AMBR information shall be present. 5QI value range is 0-255. ARP shall be encoded as Allocation/Retention Priority IE defined in 3GPP TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [81]. The UTF-8 encoded UL/DL MFBR, UL/DL GFBR and UL/DL Session-AMBR has the following pattern: '^\d+(\.\d+)? (bps|Kbps|Mbps|Gbps|Tbps)$' Examples: "125 Mbps", "0.125 Gbps", "125000 Kbps" For GBR 5QIs, the encoding of UTF-8 encoded QoS Profile field shall be as follows: For non-GBR 5QIs, the encoding of UTF-8 encoded QoS Profile field shall be as follows: The above structures for encoding the QoS profile of Release indicator "15" do not apply for the present specification. For specifications referencing the present VSA, those formats shall only apply if it is explicitely endorsed within the referencing specification. 6 – 3GPP-SGSN address 3GPP Type: 6 Length: 6 SGSN address value: Address type. 7 – 3GPP-GGSN address 3GPP Type: 7 Length: 6 GGSN address value: Address type. 8 – 3GPP-IMSI MCC-MNC 3GPP Type: 8 Length: n shall be 7 or 8 octets depending on the presence of MNC digit 3 IMSI MCC-MNC address value: Text type. This is the UTF-8 encoded characters representing the IMSI MCC-MNC numerical values. In accordance with 3GPP TS 29.060[ General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface ] [24] (for GGSN), 3GPP TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [81] (for P-GW) and 3GPP TS 23.003[ Numbering, addressing and identification ] [40], the MCC shall be 3 digits and the MNC shall be either 2 or 3 digits. There shall be no padding characters between the MCC and MNC. 9 – 3GPP-GGSN MCC-MNC 3GPP Type: 9 Length: n shall be 7 or 8 octets depending on the presence of MNC digit 3 GGSN address value: Text type. This is the UTF-8 encoding of the GGSN MCC-MNC values. In accordance with 3GPP TS 23.003[ Numbering, addressing and identification ] [40] and 3GPP TS 29.060[ General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface ] [24] the MCC shall be 3 digits and the MNC shall be either 2 or 3 digits. There shall be no padding characters between the MCC and MNC. 10 – 3GPP-NSAPI 3GPP Type: 10 Length: 3 NSAPI value: Text Type. It is the value of the NSAPI of the PDP context the RADIUS message is related to. It is encoded as its hexadecimal representation, using one UTF-8 encoded character. The GGSN should receive NSAPI values in the following hexadecimal range 05 – 0F. The GGSN shall discard digit 0 and convert the remaining digit into one UTF-8 coded character. For P-GW, the value of this sub-attribute represents the EPS Bearer ID as specified in 3GPP TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [81]. 11 – 3GPP-Session Stop Indicator 3GPP Type: 11 Length: 3 Value is set to all 1. 3GPP-Session Stop Indicator value: Bit String type. 12 – 3GPP-Selection-Mode 3GPP Type: 12 Length: 3 Selection mode value: Text type. The format of this sub-attribute shall be a character that represents a single digit, mapping from the binary value of the selection mode in the Create PDP Context message (3GPP TS 29.060[ General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface ] [24]) for the GGSN, and the Create Session Request message (3GPP TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [81]) for the P-GW. Where 3GPP TS 29.060[ General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface ] [24] provides for interpretation of the value, e.g. map ‘3’ to ‘2’, this shall be done by the GGSN. 13 – 3GPP-Charging-Characteristics 3GPP Type: 13 Length: 6 Charging characteristics value: Text type. The charging characteristics is value of the 2 octets. The value field is taken from the GTP IE described in 3GPP TS 29.060[ General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface ] [24], subclause 7.7.23 for the GGSN and 3GPP TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [81] for the P-GW. Each octet of this IE field value is represented via 2 UTF-8 encoded character, defining its hexadecimal representation. 14 – 3GPP-Charging Gateway IPv6 address 3GPP Type: 14 Length: 18 Charging GW IPv6 address value: IPv6 Address. Charging GW IPv6 address is Octet String type. 15 – 3GPP-SGSN IPv6 address 3GPP Type: 15 Length: 18 SGSN IPv6 address value: IPv6 Address. SGSN IPv6 address is Octet String type. 16 – 3GPP-GGSN IPv6 address 3GPP Type: 16 Length: 18 GGSN IPv6 address value: IPv6 Address. SGSN IPv6 address is Octet String type. 17 – 3GPP-IPv6-DNS-Servers 3GPP Type: 17 Length: m = n × 16 + 2; n 1 and n 15; k = m-15 IPv6 DNS Server value: IPv6 Address. IPv6 DNS Server address is Octet String type. The 3GPP- IPv6-DNS-Servers sub-attribute provides a list of one or more (‘n’) IPv6 addresses of Domain Name Server (DNS) servers for an APN. The DNS servers are listed in the order of preference for use by a client resolver, i.e. the first is ‘Primary DNS Server’, the second is ‘Secondary DNS Server’ etc. The sub-attribute may be included in Access-Accept packets. 18 – 3GPP-SGSN MCC-MNC 3GPP Type: 18 Length: n shall be 7 or 8 octets depending on the presence of MNC digit 3 SGSN MCC-MNC address value: Text type. This is the UTF-8 encoding of the MCC-MNC values extracted from the RAI or from the Serving Network. In accordance with 3GPP TS 23.003[ Numbering, addressing and identification ] [40] and 3GPP TS 29.060[ General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface ] [24] (for the GGSN and P-GW connected to a Gn/Gp SGSN) and 3GPP TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [81] (for the P-GW in GTP/PMIP S5/S8, S2a, S2b), the MCC shall be 3 digits and the MNC shall be either 2 or 3 digits. There shall be no padding characters between the MCC and MNC. 19 – 3GPP-Teardown Indicator 3GPP Type: 19 Length: 3 Octet 3 is Octet String type. For GGSN, if the value of TI is set to "1", then all PDP contexts that share the same user session with the PDP context identified by the Acct-Session-Id shall be torn down. Only the PDP context identified by the Acct-Session-Id shall be torn down if the value of TI is "0" (see subclause 16.3.4 "AAA-Initiated PDP context termination"), or if TI is missing. For P-GW, the usage of Teardown-Indicator is as follows (see subclause 16.3a.3 for more deails): - if the value of TI is set to "1", then all IP-CAN bearers that share the same user session with the IP-CAN bearer identified by the Acct-Session-Id shall be torn down. - if the value of TI is "0", or if TI is missing, only the IP-CAN bearer identified by the Acct-Session-Id shall be torn down. If the Acct-Session-Id identifies the default bearer, the P-GW shall tear down all the IP-CAN bearers that share the same user session identified by the Acct-Session-Id. 20 -3GGP- IMEISV 3GPP Type: 20 IMEISV value: Text type. A GGSN receives IMEI(SV) that is encoded according to 3GPP TS 29.060[ General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface ] [24]. A P-GW receives IMEI(SV) that is encoded in ME Identity IE specified in 3GPP TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [81]. The GGSN or the P-GW converts IMEI(SV) into a sequence of UTF-8 characters.IMEI(SV) shall be encoded as defined in 3GPP TS 23.003[ Numbering, addressing and identification ] [40]. 14 n 16 n = 16 for IMEISV, where TAC = 8 digits SNR = 6 digits & SVN = 2 digits; n = 15 for IMEI, where TAC = 8 digits SNR = 6 digits & Spare = 1 digit; n = 14 for IMEI, where TAC = 8 digits SNR = 6 digits (Spare digit is not sent) 21 – 3GPP-RAT-Type 3GPP Type: 21 The 3GPP-RAT-Type sub-attribute indicates which Radio Access Technology is currently serving the UE. RAT field: Radio Access Technology type values. RAT field is Octet String type. For GGSN, it shall be coded as specified in 3GPP TS 29.060[ General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface ] [24]. For P-GW, it shall be coded as follows: 0-9 As specified in 3GPP TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [81] 10-50 Spare for future use 51 NR 52 NR in unlicensed bands 53 Trusted WLAN 54 Trusted Non-3GPP access 55 Wireline access 56 Wireline Cable access 57 Wireline BBF access 58 NR RedCap 59-100 Spare for future use 101 IEEE 802.16e 102 3GPP2 eHRPD 103 3GPP2 HRPD 104 3GPP2 1xRTT 105 3GPP2 UMB 106-255 Spare for future use The value 51-58 does not apply for the present specification. For specifications referencing the present RADIUS VSA, the value shall only apply if it is explicitely endorsed within the referencing specification. 22 – 3GPP-User-Location-Info 3GPP Type: 22 Length=m, where m depends on the Geographic Location Type For example, m= 10 in the CGI and SAI types. Geographic Location Type field is used to convey what type of location information is present in the ‘Geographic Location’ field. For GGSN, the Geographic Location Type values and coding are as defined in 3GPP TS 29.060[ General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface ] [24]. For P-GW, the Geographic Location Type values and coding are defined as follows: 0 CGI 1 SAI 2 RAI 3-127 Spare for future use 128 TAI 129 ECGI 130 TAI and ECGI 131 eNodeB ID 132 TAI and eNodeB ID 133 extended eNodeB ID 134 TAI and extended eNodeB ID 135 NCGI 136 5GS TAI 137 5GS TAI and NCGI 138 NG-RAN Node ID 139 5GS TAI and NG-RAN Node ID 140-255 Spare for future use Geographic Location field is used to convey the actual geographic information as indicated in the Geographic Location Type. For GGSN, the coding of this field is as specified in 3GPP TS 29.060[ General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface ] [24]. For P-GW, the coding of this field shall be as follows: - If the Geographic Location Type has a value indicating CGI, SAI, RAI, TAI or ECGI (i.e. the value field is equal to 0, 1, 2, 128, or 129), the coding of the Geographic Location field shall be as per clauses 8.21.1 to 8.21.5, respectively, in 3GPP TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [81], - If the Geographic Location Type has a value indicating TAI and ECGI (i.e. the value field is equal to 130), in Geographic Location field both TAI and ECGI shall be encoded one after another as per clauses 8.21.4 and 8.21.5 in 3GPP TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [81]. TAI information shall be encoded first starting with Octet 4 of 3GPP-User-Location-Info. - If the Geographic Location Type has a value indicating eNodeB ID (i.e. the value field is equal to 131), the coding of the Geographic Location field shall be as defined in subclause 8.21.7 in 3GPP TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [81]. - If the Geographic Location Type has a value indicating TAI and eNodeB ID (i.e. the value field is equal to 132), in Geographic Location field both TAI and eNodeB ID shall be encoded one after another as per subclauses 8.21.4 and 8.21.7 in 3GPP TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [81]. - If the Geographic Location Type has a value indicating extended eNodeB ID (i.e. the value field is equal to 133), the coding of the Geographic Location field shall be as defined in subclause 8.21.8 in 3GPP TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [81]. - If the Geographic Location Type has a value indicating TAI and extended eNodeB ID (i.e. the value field is equal to 134), in Geographic Location field both TAI and extended eNodeB ID shall be encoded one after another as per subclauses 8.21.4 and 8.21.8 in 3GPP TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [81]. NOTE 1: The Geographic Location Type values "TAI and ECGI" is used only in 5GC-EPC interworking e.g in 3GPP TS 29.214[ Policy and charging control over Rx reference point ] [121]. The Geographic Location Type values "NCGI", "5GS TAI", "5GS TAI and NCGI", "NG-RAN Node ID" and "5GS TAI and NG-RAN Node ID" are only introduced to extend the 3GPP-User-Location-Info AVP derived from the 3GPP Vendor-Specific RADIUS attributes and shall not apply for the present specification. For specifications referencing the present data type, those values shall only apply if they are explicitely endorsed within the referencing specification. For those values, the Geographic Location field shall be coded as follows: NOTE 2: The Geographic Location Type values "NCGI", "NG-RAN Node ID" and "5GS TAI and NG-RAN Node ID" are not used in 5G till current releases, while the value "5GS TAI and NCGI" is used only in 5GC e.g in 3GPP TS 29.214[ Policy and charging control over Rx reference point ] [121]. - If the Geographic Location Type has a value indicating NCGI (i.e. the value field is equal to 135), the coding of the Geographic Location field shall be as per subclause 9.3.1.7 in 3GPP TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [115]. Spare bits shall be placed just after the PLMN Identity and shall be set to zero. - If the Geographic Location Type has a value indicating 5GS TAI (i.e. the value field is equal to 136), the coding of the Geographic Location field shall be as per subclause 9.3.3.11 in 3GPP TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [115]. - If the Geographic Location Type has a value indicating 5GS TAI and NCGI (i.e. the value field is equal to 137), in Geographic Location field both 5GS TAI and NCGI shall be encoded one after another as per subclause 9.3.3.11 in 3GPP TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [115] and per subclause 9.3.1.7 in 3GPP TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [115]. Spare bits for the NCGI shall be placed just after the PLMN Identity and shall be set to zero. - If the Geographic Location Type has a value indicating NG-RAN Node ID (i.e. the value field is equal to 138), the first octet of the Geographic Location field shall be length of the NG-RAN Node ID in unit of bit, and it also indicates the type of NG-RAN node as follows: 1. length value = 18, short ng-eNodeB ID 2. length value = 20, ng-eNodeB ID 3. length value = 21, long ng-eNodeB ID 4. length value = 22-32, gNodeB ID Starting from the second octet of the Geographic Location field, the coding shall be as per subclause 9.3.1.5 in 3GPP TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [115], i.e. first PLMN information then NG-RAN Node ID. Spare bits shall be set to zero. - If the Geographic Location Type has a value indicating 5GS TAI and NG-RAN Node ID (i.e. the value field is equal to 139), in Geographic Location field both 5GS TAI and NG-RAN Node ID shall be encoded one after another as per subclause 9.3.3.11 in 3GPP TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [115] and as described for NG-RAN Node ID (i.e. the value field is equal to 138). Spare bits shall be set to zero. Geographic Location Type and Geographic Location fields are Octet String type. 23 – 3GPP-MS-TimeZone 3GPP Type: 23 Length=4 The Time Zone field and the Daylight Saving Time fields are used to indicate the offset between universal time and local time in steps of 15 minutes of where the MS/UE currently resides. For GGSN, both fields are coded as specified in 3GPP TS 29.060[ General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface ] [24] and represented as Octet String type. For, P-GW, both fields are coded as specified in 3GPP TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [81] in UE-Time Zone IE and represented as Octet String type. 24 – 3GPP-Camel-Charging-Info 3GPP Type: 24 Length=m m depends on the size of the CAMELInformationPDP IE. The CAMEL Charging Information Container field is used to copy the CAMELInformationPDP IE including Tag and Length from the SGSN’s CDR (S-CDR). The coding of this field is as specified in 3GPP TS 29.060[ General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface ] [24] and represented as Octet String type. 25 – 3GPP-Packet-Filter 3GPP Type: 25 Length: n Each 3GPP-Packet-Filter sub-attribute contains only one packet filter. Multiple 3GPP-Packet-Filter sub-attributes can be sent in one RADIUS Accounting Request message. When the GGSN/P-GW sends the packet filter information, the RADIUS message shall carry ALL (or none) of the packet filters. Packet Filter Value: Direction Value: 00000000: Downlink 00000001: Uplink 00000010: Bidirectional The packet filter content is represented as Octet String type. The packet filter content is defined below: NOTE 3: The sending of this sub-attribute is not recommended for an inter-operator interface for security reason. 26 – 3GPP-Negotiated-DSCP 3GPP Type: 26 Length: 3 Negotiated DSCP value: Octet String DSCP value: Octet String type. 27 – 3GPP-Allocate-IP-Type 3GPP Type: 27 If multiple Access-Request signalling towards a AAA server is needed during the lifetime of a PDN connection (e.g. for PDN/PDP type IPv4v6 and deferred IPv4 addressing), this sub-attribute shall be included in the Access-Request message to indicate how the AAA server needs to treat the request. The P-GW/GGSN may also use this sub-attribute if the AAA server is configured to allocate both IPv4 address and IPv6 prefix but the P-GW/GGSN requires assignment of only one IP type or both IP types (e.g. because the UE supports single IP stack and it has requested PDN/PDP type of IPv4 or IPv6). If this sub-attribute does not exist in Access-Request from P-GW/GGSN to the AAA server, the IP address allocation shall be based on the IP address allocation policy configured in the the AAA server. IP Type field: It is encoded in Octet String type and the following decimal equivalent values apply: 0 Do not allocate IPv4 address or IPv6 prefix. The typical use case is for PDN/PDP type IPv4v6 and deferred IPv4 addressing and only IPv4 address is allocated by the AAA server but IPv6 prefix is allocated by some other means, e.g. local pool in the P-GW/GGSN. The Access-Request from the P-GW/GGSN to the AAA server during the UE’s initial access to the network shall set the value of this sub-attribute to 0. 1 Allocate IPv4 address The typical use case is for PDN/PDP type IPv4v6 and deferred IPv4 addressing and the IPv4 address (and/or IPv6 prefix) is allocated by the AAA server. The Access-Request from the P-GW/GGSN to the AAA server when the P-GW/GGSN receives UE-initiated IPv4 address allocation signalling (e.g. DHCPv4) after UE’s successful initial access to the PDN shall set the value of this attribute to 1. In this case, if the AAA server had allocated an IPv6 prefix earlier during UE’s initial access to the network, same IPv6 prefix shall be kept allocated. 2 Allocate IPv6 prefix The typical use case is for PDN/PDP type IPv4v6 and deferred IPv4 addressing and both IPv4 address and IPv6 prefix are allocated by the AAA server. The Access-Request from the P-GW/GGSN to the AAA server during the UE’s initial access to the network shall set the value of this sub-attribute to 2. 3 Allocate IPv4 address and IPv6 prefix Currently there is no use case identified to use this specific value for PDN/PDP tpe IPv4v6 and deferred IPv4 addressing. One potential use case is for PDN/PDP type IPv4v6 and non-deferred IPv4 addressing and both IPv4 address and IPv6 prefix are allocated by the AAA server. The Accesss-Request from the P-GW/GGSN to the AAA server may use this value to have both IPv4 address and IPv6 prefix assigned to the UE. 4-255 Reserved for future use 28 – External-Identifier 3GPP Type: 28 n 72 / 253 (n 72 octets shall be supported, n 253 octets recommended, refer to 3GPP TS 29.336[ Home Subscriber Server (HSS) diameter interfaces for interworking with packet data networks and applications ] [101] and IETF RFC 4282 [102]) Length: m 74 / 255 (m 74 octets shall be supported, m 255 octets recommended, refer to 3GPP TS 29.336[ Home Subscriber Server (HSS) diameter interfaces for interworking with packet data networks and applications ] [101] and IETF RFC 4282 [102]) External-Identifier value: Text type. A globally unique identifier of a UE used towards external server instead of IMSI and MSISDN, refer to 3GPP TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [100] and 3GPP TS 23.003[ Numbering, addressing and identification ] [40]. 29 – TWAN-Identifier 3GPP Type: 29 Length=m, where m depends on the type of location that is present as described in 3GPP TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [81]. TWAN Identifier field is used to convey the location information in a Trusted WLAN Access Network (TWAN). The coding of this field shall be the same as for the GTP TWAN Identifier starting with Octet 5, as per clause 8.100 in 3GPP TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [81]. TWAN Identifier field is Octet String type. 30 – 3GPP-User-Location-Info-Time 3GPP Type: 30 Length=6 User Location Info time field is Unsigned32 type, it indicates the NTP time at which the UE was last known to be in the location which is reported during bearer deactivation or UE detach procedure. 31 – 3GPP-Secondary-RAT-Usage 3GPP Type: 31 Length=28 Multiple 3GPP-Secondary-RAT-Usage sub-attributes can be sent in one RADIUS Accounting Request Interim-Update/STOP message. Octet 3 is Octet String type. The encoding of RAT field (bit 1 to bit 4) is: 0 – NR 1 – NR-U 2 – EUTRA 3 – EUTRA-U 4 – Unlicensed Spectrum 5-15 – spare, reserved for future use SESS (bit 5): If it is set to 1, it indicates the secondary RAT usage of the PDU session. The values 1, 2 and 3 of RAT field and SESS field do not apply for the present specification. For specifications referencing the present RADIUS VSA, they shall only apply if it is explicitely endorsed within the referencing specification. Bit 6 to bit 8 of octet 3 is spare and reserved for future use. The encoding of octets 4 to 28 is specified in Secondary RAT Usage Data Report IE of 3GPP TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [81]. 32 – 3GPP-UE-Local-IP-Address 3GPP Type: 32 Length=7 or 19 IP Type field: It is encoded in Octet String type and the following decimal equivalent values apply: 1 UE local IPv4 address 2 UE local IPv6 address UE local IP address field: It is encoded in Octet String type, with 4 octets when the IP Type is UE local IPv4 address, or with 16 octets when the IP Type is UE local IPv6 address. 33 – 3GPP-UE-Source-Port 3GPP Type: 33 Length=5 Source Port Type field: It is encoded in Octet String type and the following decimal equivalent values apply: 1 UDP Source Port 2 TCP Source Port Port Number field: It is encoded in Octet String type, with bit 8 of Octet 4 represents the most significant bit of the port number and bit 1 of Octet 5 represents the least significant bit. | 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.4.7.2 |
5,519 | 7.8 PCI Optimisation Function | The PCI Optimization Function in non-split gNB case is specified in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [2]. In split gNB architecture, the OAM configures a PCI for each NR cell to the gNB-DU. For centralized PCI assignment in split gNB architecture, the gNB-CU detects PCI conflict of NR cells and reports the NR cells suffering PCI conflict to OAM directly. The OAM is in charge of reassigning a new PCI for the NR cell subject to PCI conflict. For distributed PCI assignment in split gNB architecture, the OAM assigns a list of PCIs for each NR cell and sends the configured PCI list to the gNB-CU. If the gNB-CU detects PCI conflict, the gNB-CU may select a new PCI value from the preconfigured PCI list for the NR cell and send it to the gNB-DU by either F1 Setup procedure or gNB-CU configuration update procedure. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 7.8 |
5,520 | 4.16.4 SM Policy Association Establishment | Figure 4.16.4-1: SM Policy Association Establishment This procedure concerns both roaming and non-roaming scenarios. In the non-roaming case the V-PCF is not involved. In the local breakout roaming case, the H-PCF is not involved. In the home routed roaming case, the V-PCF is not involved and the H-PCF interacts with the H-SMF. This procedure is used in UE requests a PDU Session Establishment as explained in clause 4.3.2.2.1, for non-roaming and local breakout roaming. For home-routed roaming, as explained in clause 4.3.2.2.2. For local breakout roaming, the interaction with HPLMN (e.g. step 3) is not used. In local breakout roaming, the V-PCF interacts with the UDR of the VPLMN. 1. The SMF determines that the PCC authorization is required and requests to establish an SM Policy Association with the PCF by invoking Npcf_SMPolicyControl_Create operation, including information about the PDU Session as specified in clause 5.2.5.4.2. The SMF provides Trace Requirements to the PCF when it has received Trace Requirements and it has selected a different PCF than the one received from the AMF. If the DNN Selection Mode indicates that the DNN is not explicitly subscribed, the PCF may use the local configuration instead of PDU Session policy control data in UDR. The QoS constraints from the VPLMN are provided by the H-SMF to the H-PCF in the home routed roaming scenario as defined in clause 4.3.2.2.2. If the SMF utilizes an NWDAF or in case the SMF has received information from AMF or UPF that are consumer of analytic services, the SMF includes the IDs of each of these NWDAFs serving the UE (for SMF, AMF and UPF), identified by the NWDAF instance Id. The Analytics ID(s) are also included per NWDAF service instance. The SMF provides the request for notification of SM Policy Association establishment and termination to a DNN, S-NSSAI together with PCF for the UE binding information to the PCF if received from the AMF. 2. If the PCF does not have the subscriber's subscription related information, it sends a request to the UDR by invoking Nudr_DM_Query (SUPI, DNN, S-NSSAI, Policy Data, PDU Session policy control data, Remaining allowed Usage data) service in order to receive the information related to the PDU Session. The PCF may request notifications from the UDR on changes in the subscription information by invoking Nudr_DM_Subscribe (Policy Data, SUPI, DNN, S-NSSAI, Notification Target Address (+ Notification Correlation Id), Event Reporting Information (continuous reporting), PDU Session policy control data, Remaining allowed Usage data) service. If the PCF does not have the 5G VN group data for the group identified by Internal Group Identifier as indicated by SMF in Npcf_SMPolicyControl_Create, the PCF retrieves the 5G VN group data from UDR and subscribes to changes on the 5G VN group data, see similar way to how the PCF does it during UE Policy Association establishment as described in clause 4.16.11. If the PCF receives the Maximum Group Data Rate in 5G VN group data, the PCF performs the group related policy control as described in clauses 6.1.5 and 6.2.1.11 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. NOTE 1: For local breakout roaming, PDU Session policy control subscription information and Remaining allowed usage subscription information for monitoring control as defined in clause 6.2.1.3 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20] are not available in V-UDR and V-PCF uses locally configured information according to the roaming agreement with the HPLMN operator. 3. If the PCF determines that the policy decision depends on the status of the policy counters available at the CHF and such reporting is not established for the subscriber, the PCF initiates an Initial Spending Limit Report Retrieval as defined in clause 4.16.8.2. If policy counter status reporting is already established for the subscriber and the PCF determines that the status of additional policy counters are required, the PCF initiates an Intermediate Spending Limit Report Retrieval as defined in clause 4.16.8.3. 4. The PCF makes the authorization and the policy decision. The PCF may reject Npcf_SMPolicyControl_Create request when Validation condition is not satisfied. (see clause 6.1.2.4 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]). The PCF may invoke Nbsf_Management_Register service operation to create the binding information in BSF. The PCF may report that a SM Policy Association is established as described in clause 4.16.14.2. In the non-roaming case, the PCF may subscribe to Analytics from NWDAF as defined in clause 6.1.1.3 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. In the home-routed roaming scenario, the H-PCF ensures that the QoS constraints provided by the VPLMN are taken into account as described in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. 5. The PCF answers with a Npcf_SMPolicyControl_Create response; in its response the PCF may provide policy information defined in clause 5.2.5.4 (and in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]). The SMF enforces the decision. The SMF implicitly subscribes to changes in the policy decisions. NOTE 2: After this step the PCF can subscribe to SMF events associated with the PDU Session. If the PCF determines based on a local policy, that the PDU Session is potentially impacted by (g)PTP time synchronization service, or the PDU Session belongs to a 5GS DetNet router, the PCF can include a subscription for SMF event for "5GS Bridge/Router information" associated with the PDU Session into the Npcf_SMPolicyControl_Create response. In this case, if the SMF has stored the 5GS Bridge/Router information and has not reported the event to the PCF, the SMF initiates an SM Policy Association Modification procedure and notifies the PCF for the event of "5GS Bridge/Router information Notification". | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.16.4 |
5,521 | 10.16.3 Inter-system handover from 5GS to EPS with the Source Node used as target Secondary Node | Inter-system handover from 5GS to EPS with the Source Node used as target Secondary Node refers to a deployment scenario where the source gNB and the target en-gNB are realised within the same network entity. Figure 10.16.3-1: Inter-system handover from 5GS to EPS with the Source Node used as target Secondary Node 1. The (source) gNB triggers handover preparation phase including in the Source eNB to Target eNB Transparent Container the Source NG-RAN node ID and the RAN UE NGAP ID. 2. The target eNB receives the Source NG-RAN node ID and the RAN UE NGAP ID in the Source eNB to Target eNB Transparent Container. 3.-4. The X2AP SgNB Addition procedure is performed towards the (target) en-gNB indicated in the Source NG-RAN node ID received in step 2. The eNB includes the RAN UE NGAP ID received in step 2 in the X2 SgNB Addition Request message. 5.-8. Handover proceeds. 9. DL UP data is forwarded in a node-internal way for the SN terminated bearers. | 3GPP TS 37.340 | Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 | RAN2 | 3GPP Series : 37 , Multiple radio access technology aspects | 10.16.3 |
5,522 | 5.5.7.3 Stop DTMF request by the mobile station | When the user indicates that the DTMF sending should cease e.g. by releasing the key the mobile station will send a STOP DTMF message to the network. On sending a STOP DTMF message the MS shall start timer T337. The MS shall only send a STOP DTMF message if a START DTMF ACKNOWLEDGE message has been received from the network (see subclause 5.5.7.2). If timer T337 expires, the MS shall terminate the ongoing DTMF procedure without any retransmissions, and is free to begin another DTMF procedure. (e.g. another START DTMF message). | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.7.3 |
5,523 | 5.3.4 Requirements for the gNB setup and configuration | Setting up and configuring gNBs by O&M systems shall be authenticated and authorized by gNB so that attackers shall not be able to modify the gNB settings and software configurations via local or remote access. - The certificate enrolment mechanism specified in TS 33.310[ Network Domain Security (NDS); Authentication Framework (AF) ] [5] for base station should be supported for gNBs. The decision on whether to use the enrolment mechanism is left to operators. - Communication between the O&M systems and the gNB shall be confidentiality, integrity and replay protected from unauthorized parties. The security associations between the gNB and an entity in the 5G Core or in an O&M domain trusted by the operator shall be supported. These security association establishments shall be mutually authenticated. The security associations shall be realized according to TS 33.210[ Network Domain Security (NDS); IP network layer security ] [3] and TS 33.310[ Network Domain Security (NDS); Authentication Framework (AF) ] [5]. - The gNB shall be able to ensure that software/data change attempts are authorized. - The gNB shall use authorized data/software. - Sensitive parts of the boot-up process shall be executed with the help of the secure environment. - Confidentiality of software transfer towards the gNB shall be ensured. - Integrity protection of software transfer towards the gNB shall be ensured. - The gNB software update shall be verified before its installation (cf. sub-clause 4.2.3.3.5 of TS 33.117[ Catalogue of general security assurance requirements ] [24]). | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 5.3.4 |
5,524 | 5.27.1.12 Support for network timing synchronization status monitoring | While the time synchronization service is offered by the 5GS, based on 5G access stratum-based time distribution or (g)PTP-based time distribution, the network timing synchronization status of the nodes involved in the operation (e.g. gNBs and/or UPF/NW-TTs) may change. gNBs and UPF/NW-TT can detect timing synchronization degradation or improvement locally. The support for network timing synchronization status monitoring enables the 5GS to modify time synchronization service for a UE or a group of UEs depending on the current synchronization status and notify service updates. There may be three consumers of this information: - TSCTSF may receive node-level information about timing synchronization status from gNB and/or UPF/NW-TT directly from OAM or alternatively, if supported by a node, using control plane signalling at node level. Node level signalling uses UMIC for UPF/NW-TT case and an AMF service to report N2 node level information for the gNB case. In the latter case, the AMF controls the gNB node level reporting and subscription using NGAP messages (see TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [34]). - AF may subscribe to time synchronization status notifications for a UE or group of UEs for which the AF requests or has requested time synchronization service (for 5G access stratum time distribution or (g)PTP services). - For 5G access stratum time synchronization service, the UE may receive clock quality information from the gNB based on UE subscription data stored in the UDM (see clause 5.27.1.11) or AF request for clock quality reporting to the UE. When activating time synchronization for a UE, TSCTSF forwards the clock quality detail level (if available) to the AMF (via PCF using AM policy). The AMF instructs the UE to transition to the RRC_CONNECTED state in the case when the UE later detects that the gNB timing synchronization status has changed while the UE is in the RRC_INACTIVE or RRC_IDLE state. When the UE wants to access the 5GS, the UE shall perform Unified Access Control as defined in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [28]. gNBs may be pre-configured with thresholds for each Timing Synchronization Status (TSS) attribute, if supported, that is described in Table 5.27.1.12-1. gNBs may include a reference report ID in SIB information, if supported. A reference report ID consists of a scope of the TSS and an Event ID. A scope of the TSS supports providing TSS information for all cells or a group of cells within a single gNB. Event ID is an integer indicating that the gNB's clock quality has changed, resulting in at least one TSS attribute exceeding or meeting again the pre-configured threshold. Uniqueness of Event ID value is ensured by combining it with a gNB ID as specified in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27]. When the network TSS attribute exceeds the thresholds (i.e. status degradation), or the network TSS attribute meets the thresholds again (i.e. status improvement), the gNB notifies the TSCTSF (either using N2 node level signalling via AMF, or via OAM) with the scope of the timing synchronization status (i.e. gNB ID or a list of Cell IDs within a single gNB) and the corresponding network timing synchronization status attributes as described in Table 5.27.1.12-1. The gNB indicates the status change to the UEs via the reference report ID change in SIB information: - When the network timing synchronization status exceeds any of the pre-configured thresholds (i.e. status degradation) or meets the threshold again (i.e. status, improvement), the gNB changes the reference report ID in SIB information. Either event serves as a notification for the UEs reading the SIB information that there is new TSS information available. NOTE 1: NG-RAN is assumed not to provide clock quality metrics better than the pre-configured threshold, i.e. if a clock quality metric is better than the corresponding threshold, the NG-RAN reports the threshold value to the UE in an RRC message instead. NOTE 2: It is assumed the pre-configured thresholds in the gNB(s) are sufficient to meet UE time sync performance requirement which are configured by the operator. - If supported, the UE in the RRC_INACTIVE or RRC_IDLE state compares the reference report ID in SIB information with its locally stored reference report ID to determine whether it has the latest available clock quality information already or it needs to transit to the RRC_CONNECTED state to retrieve it. - If the UE is instructed by AMF (via the Registration procedure, or the UE Configuration Update procedure) to reconnect to the network in the case when the UE determines that the reference report ID has changed, the UE in the RRC_INACTIVE or RRC_IDLE state, if supported by the UE, reconnects to the network. RAN may delay or prioritize UE's transition to the RRC_CONNECTED state using the UAC framework [28], i.e. UEs are not expected to transition to the RRC_CONNECTED state immediately after determining that the clock quality information has changed and receiving instructions from the AMF. After the UE has reconnected to the network, the gNB uses unicast RRC signalling to provision the clock quality information to the UEs. The network timing synchronization status information from gNB or UPF/NW-TT to the TSCTSF may contain the following information as described in the Table 5.27.1.12-1. The details for gNB timing synchronization status information are specified in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [34]. However, it is up to gNB to determine whether to provide its timing synchronization status reporting and which of the information elements to include in the TSS report to the TSCTSF, i.e. based on the implementation gNB may report all, some, or none of the information elements from Table 5.27.1.12-1. Table 5.27.1.12-1: Information elements that gNB or UPF/NW-TT timing synchronization status information may contain (all optional) The TSCTSF determines the UEs impacted by gNB's timing synchronization status change (i.e. degradation, failure or improvement) or UPF timing synchronization status change (only for the case when UPF/NW-TT is involved in providing time information to DS-TT). - For the gNB case, when the TSCTSF receives information about timing synchronization status change, the TSCTSF uses the NRF to discover the AMFs serving the impacted gNBs and subscribes to receive notifications for UE's presence in Area of Interest information from AMF as described in clause 5.3.4.4. The Area of Interest is set to the scope of the timing synchronization status (i.e. gNB ID or a group of cells within the gNB specified with a list of Cell IDs that has reported status degradation (i.e. the pre-configured thresholds are exceeded in the gNB). The subscription is targeted to any UE in the AMF, the TSCTSF may provide additional filtering information as specified in clause 5.3.4.4 (e.g., List of UE IDs, DNN(s)/S-NNSAI(s)) to limit the subscription to the indicated UE identities, UEs having a PDU Session with the given DNN(s)/S-NSSAI(s). The TSCTSF correlates information about impacted gNBs and the UE location information received from the AMF. If the gNB notifies the TSCTSF for the status improvement (i.e. the pre-configured thresholds are met in the gNB), the TSCTSF modifies the subscription to remove the corresponding Area of Interest from the subscription. - For UPF case, the TSCTSF determines the UEs for which the impacted UPF/NW-TT is configured to send (g)PTP messages on behalf of DS-TT (see clause 5.27.1.7). If the gNB's or UPF's timing synchronization status change, the TSCTSF may perform the following: - For AFs that subscribe for 5G access stratum time synchronization service or (g)PTP time synchronization service status update (i.e. change in support status of the clock quality acceptance criteria provided by the AF and specified using TSS attributes from Table 5.27.1.12-1), the TSCTSF may provide notification towards the AF when there is a change in support status for a UE or group of UEs. - Deactivating/reactivating/updating time synchronization services: - (g)PTP time synchronization service case: For UEs that are part of a PTP instance and which are impacted by NG-RAN or UPF time synchronization status degradation or improvement: - If TSCTSF determines that the clock quality acceptance criteria provided by AF can still be met, then TSCTSF may update the clock quality information sent in Announce messages (see clause 7.6.2 of IEEE 1588 [8]) for the PTP instance using existing procedures and existing PMIC/UMIC information. The handling of Announce messages follows existing procedures as described in clause 5.27.1.6. - If TSCTSF determines that the clock quality acceptance criteria provided by AF cannot be met, then TSCTSF informs the AF for the corresponding PTP ports being inactive due to the result of fulfilling the clock quality acceptance criteria; and the TSCTSF temporarily removes the UE/DS-TT from the PTP instance using the procedure in clause K.2.2.1 and clause K.2.2.4. The AF may send a service update or delete request (see clause 4.15.9.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]). - If TSCTSF determines that the clock quality acceptance criteria provided by AF can be met again then TSCTSF informs the AF about the result, adds the DS-TT PTP port to the PTP instance again and re-activates the Grandmaster functionality. For 5G access stratum time synchronization service, clock quality reporting control information manages the gNBs timing synchronization status reporting to the UE. When AMF provides the 5G access stratum time distribution indication and the Uu time synchronization error budget to gNB, the AMF also includes the clock quality reporting control information (CQRCI) provided by the TSCTSF or retrieved from UDM. CQRCI may be a part of Access and Mobility Subscription data at the UDM, or AF may include CQRCI in its request. CQRCI contains the following fields: - Clock quality detail level. It indicates whether and which clock quality information to provide to the UE and can take one of the following values: "clock quality metrics" or "acceptable/not acceptable indication". - If the clock quality detail level equals "clock quality metrics", the NG-RAN provides clock quality metrics to the UE that reflect its current timing synchronization status. i.e. one or more of the following information elements: clock accuracy, traceability to UTC, traceability to GNSS, frequency stability, parent time source, synchronization state as defined in Table 5.27.1.12-1. NG-RAN is locally configured which of the clock quality metrics supported by NG-RAN are provided to UE(s). - If the clock quality detail level equals "acceptable/not acceptable indication", NG-RAN provides clock quality acceptance criteria for the UE. The gNB provides an acceptable indication to the UE if the gNB's timing synchronization status matches the acceptance criteria received from the AMF; otherwise, the gNB indicates "not acceptable" to the UE. Clock quality acceptance criteria can be defined based on one or more information elements listed in Table 5.27.1.12-1. If AF includes clock quality acceptance criteria in its request towards TSCTSF, the AF shall be notified about the result once TSCTSF determines whether the clock quality acceptance criteria can be met or not. Based on the notification, the AF may decide to modify the service if preferred (e.g., disable the service upon status degradation or enable it again upon status improvement). When determining the clock quality metrics for a UE and when determining whether clock quality is acceptable or not acceptable for a UE, the gNB considers whether propagation delay compensation is performed. NOTE 3: In this Release, UE capabilities and internal inaccuracies are assumed to be budgeted by the client network operator when agreeing the required clock accuracy with the 5G network operator. To provision clock quality information to the UEs, a gNB uses unicast RRC signalling: - For UEs in the RRC_CONNECTED state, the gNB uses unicast RRC signalling. - UEs that are not in the RRC_CONNECTED state first need to establish or resume the RRC connection to receive the clock quality information from the gNB via unicast RRC signalling. During N2 Handover and Xn handover, Service Request, mobility registration and AM policy modification procedure, the AMF may provide the CQRCI to NG-RAN. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.27.1.12 |
5,525 | 5.3.2 Permanent identifiers | A globally unique permanent identity, the 5G subscription permanent identifier (SUPI), is allocated to each subscriber for 5GS-based services. The IMSI, the network specific identifier, the GCI and the GLI are valid SUPI types. When the SUPI contains a network specific identifier, a GCI or a GLI, it shall take the form of a network access identifier (NAI). When the UE performs initial registration for onboarding services in SNPN or is registered for onboarding services in SNPN, the SUPI contains the onboarding SUPI derived from the default UE credentials for primary authentication. The UE derives the onboarding SUPI before or during the initial registration for onboarding services in SNPN and uses the derived onboarding SUPI in the initial registration for onboarding services in SNPN and while registered for onboarding services in SNPN. The structure of the SUPI and its derivatives are specified in 3GPP TS 23.003[ Numbering, addressing and identification ] [4]. The UE provides the SUPI to the network in concealed form. The SUCI is a privacy preserving identifier containing the concealed SUPI. When the SUPI contains a network specific identifier, a GCI or a GLI, the SUCI shall take the form of a NAI as specified in 3GPP TS 23.003[ Numbering, addressing and identification ] [4]. A UE supporting N1 mode includes a SUCI: a) in the REGISTRATION REQUEST message when the UE is attempting initial registration procedure and a valid 5G-GUTI is not available; b) in the IDENTITY RESPONSE message, if the SUCI is requested by the network during the identification procedure; and c) in the DEREGISTRATION REQUEST message when the UE initiates a de-registration procedure and a valid 5G-GUTI is not available. If the UE uses the "null-scheme" as specified in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24] to generate a SUCI, the SUCI contains the unconcealed SUPI. When: - not operating in SNPN access operation mode; or - operating in SNPN access operation mode but not performing initial registration for onboarding services and not registered for onboarding services; the UE shall use the "null-scheme" if: a) the home network has not provisioned the public key needed to generate a SUCI; b) the home network has configured "null-scheme" to be used for the UE; c) the UE needs to perform a registration procedure for emergency services and the USIM is still considered as valid after the failure of authentication procedure or after reception of a REGISTRATION REJECT message with the 5GMM cause #3 "Illegal UE", #6 "Illegal ME" or #7 "5GS services not allowed", or to initiate a de-registration procedure before the registration procedure for emergency services was completed successfully, and the UE does not have a valid 5G-GUTI for the selected PLMN; or d) the UE receives an identity request for SUCI during a registration procedure for emergency services or during a de-registration procedure that was initiated before the registration procedure for emergency services was completed successfully. When operating in SNPN access operation mode and: - performing initial registration for onboarding services; or - registered for onboarding services; the UE shall use the "null-scheme" if: a) the public key needed to generate a SUCI is not configured as part of the default UE credentials for primary authentication; or b) "null-scheme" usage is configured as part of the default UE credentials for primary authentication. If: a) the UE uses the "null-scheme" as specified in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24] to generate a SUCI; b) the UE operates in SNPN access operation mode and: 1) an indication to use anonymous SUCI which is associated with the selected entry of the "list of subscriber data", is configured in the ME, if the UE is not registering or registered for onboarding services in SNPN; or 2) an indication to use anonymous SUCI which is associated with the default UE credentials for primary authentication, is configured in the ME, if the UE is registering or registered for onboarding services in SNPN; NOTE 1: The ME can be configured with an indication to use anonymous SUCI associated with an entry of "list of subscriber data" when the EAP method associated with the credentials of the entry supports SUPI privacy at the EAP layer, or can be configured with an indication to use anonymous SUCI associated with the default UE credentials for primary authentication when the EAP method associated with the default UE credentials for primary authentication supports SUPI privacy at the EAP layer, or both. c) the UE does not need to perform a registration procedure for emergency services, or to initiate a de-registration procedure before the registration procedure for emergency services was completed successfully; and d) the UE does not receive an identity request for SUCI during a registration procedure for emergency services or during a de-registration procedure that was initiated before the registration procedure for emergency services was completed successfully; then the UE shall use anonymous SUCI as specified in 3GPP TS 23.003[ Numbering, addressing and identification ] [4]. A W-AGF acting on behalf of an FN-RG shall use the "null-scheme" as specified in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24] to generate a SUCI. A W-AGF acting on behalf of an N5GC device shall use the "null-scheme" as specified in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24] to generate a SUCI. If the 5G-RG acting on behalf of the AUN3 device has not obtained a SUCI from the AUN3 device, the 5G-RG acting on behalf of the AUN3 device shall use the "null-scheme" as specified in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24] to generate a SUCI for the AUN3 device. If a UE is a MUSIM UE, the UE shall use a separate permanent equipment identifier (PEI) for each USIM, if any, and each entry of "list of subscriber data", if any, the UE operates for accessing 5GS-based services; otherwise, a UE contains and uses a permanent equipment identifier (PEI) for accessing 5GS-based services. When the UE is registered with a network by using a USIM or an entry of "list of subscriber data", and has provided a PEI, then until the UE is de-registered from the network using the USIM or the entry of "list of subscriber data", the UE shall keep using that PEI in the registration using the USIM or the entry of "list of subscriber data" and shall not provide that PEI in registration using another USIM or another entry of "list of subscriber data". In this release of the specification, the IMEI, the IMEISV, the MAC address together with the MAC address usage restriction indication and the EUI-64 are the only PEI formats supported by 5GS. The structure of the PEI and its formats are specified in 3GPP TS 23.003[ Numbering, addressing and identification ] [4]. Each UE supporting at least one 3GPP access technology (i.e. satellite NG-RAN, NG-RAN, satellite E-UTRAN, E-UTRAN, UTRAN or GERAN) contains a PEI in the IMEI format and shall be able to provide an IMEI and an IMEISV upon request from the network. Each UE not supporting any 3GPP access technologies and supporting NAS over untrusted or trusted non-3GPP access shall have a PEI in the form of the Extended Unique Identifier EUI-64 [48] of the access technology the UE uses to connect to the 5GC. A UE supporting N1 mode includes a PEI: a) when neither SUPI nor valid 5G-GUTI is available to use for emergency services in the REGISTRATION REQUEST message with 5GS registration type IE set to "emergency registration"; b) when the network requests the PEI by using the identification procedure, in the IDENTITY RESPONSE message; and c) when the network requests the IMEISV by using the security mode control procedure, in the SECURITY MODE COMPLETE message. Each 5G-RG supporting only wireline access and each FN-RG shall have a permanent MAC address configured by the manufacturer. For 5G-CRG, the permanent MAC address configured by the manufacturer shall be a cable modem MAC address. When the 5G-RG contains neither an IMEI nor an IMEISV, the 5G-RG shall use as a PEI the 5G-RG's permanent MAC address configured by the manufacturer and the MAC address usage restriction indication set to "no restrictions". The W-AGF acting on behalf of the FN-RG shall use as a PEI the MAC address provided by the FN-RG and if the MAC address provided by the FN-RG is not unique or does not correspond to the FN-RG's permanent MAC address according to W-AGF's configuration, the MAC address usage restriction indication set to "MAC address is not usable as an equipment identifier" otherwise the MAC address usage restriction indication set to "no restrictions". The 5G-RG, when acting on behalf of an AUN3 device, shall use the MAC address provided by the AUN3 device as a PEI. The 5G-RG containing neither an IMEI nor an IMEISV or the 5G-RG acting on behalf of the AUN3 device shall include the PEI containing the MAC address together with the MAC address usage restriction indication: a) when neither SUPI nor valid 5G-GUTI is available to use for emergency services in the REGISTRATION REQUEST message with 5GS registration type IE set to "emergency registration"; b) when the network requests the PEI by using the identification procedure, in the IDENTIFICATION RESPONSE message; and c) when the network requests the IMEISV by using the security mode control procedure, in the SECURITY MODE COMPLETE message. NOTE 2: In case c) above, the MAC address is provided even though AMF requests the IMEISV. The W-AGF acting on behalf of the FN-RG shall include the PEI containing the MAC address together with the MAC address usage restriction indication: a) when the network requests the PEI by using the identification procedure, in the IDENTIFICATION RESPONSE message; and b) when the network requests the IMEISV by using the security mode control procedure, in the SECURITY MODE COMPLETE message. NOTE 3: In case b) above, the MAC address is provided even though AMF requests the IMEISV. The W-AGF acting on behalf of the N5GC device shall use as a PEI the MAC address provided by the N5GC device and the MAC address usage restriction indication set to "no restrictions". Based on operator policy, the W-AGF acting on behalf of the N5GC device may encode the MAC address of the N5GC device using the EUI-64 format as specified in [48] and use as a PEI the derived EUI-64. NOTE 4: The MAC address of an N5GC device is universally/globally unique. The AMF can request the PEI at any time by using the identification procedure. If the TWIF acting on behalf of the N5CW device receives the decorated NAI for N5CW device as defined in subclause 28.7.7.1 or 28.7.7.2 of 3GPP TS 23.003[ Numbering, addressing and identification ] [4] from the N5CW device, the TWIF shall first convert the decorated NAI into an NAI as specified in TS 23.502[ Procedures for the 5G System (5GS) ] [9], i.e., for decorated NAI taking the form "homerealm!username@otherrealm": a) replace the 'otherrealm' part with the 'homerealm' part; and b) remove 'homerealm!'. As a result of specified above, the converted NAI takes the form "username@homerealm". The TWIF shall include the converted NAI as a SUPI with SUPI format "network specific identifier" in the REGISTRATION REQUEST message. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.3.2 |
5,526 | 6.4 MSISDN notification procedure | The MSISDN notification procedure allows the MS to query the network for its MSISDN for the purpose of user information. In order to request the MSISDN, the MS shall encode the protocol configuration options information element (subclause 10.5.6.3) in the MS to network direction to indicate MSISDN query. The network shall then provide the MSISDN, if available, in the protocol configuration options information element in the network to MS direction. Querying the network and handling of the provided MSISDN by the MS is implementation dependent, in a similar way to the USSD notification or application mode defined in 3GPP TS 23.090[ Unstructured Supplementary Service Data (USSD); Stage 2 ] [132]. NOTE: The MS might store the provided MSISDN in the corresponding USIM file (see 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [112] subclause 4.2.26) and such an MS could check this USIM file to determine whether to query the network. The network shall provide only one MSISDN. As a result, a provided MSISDN shall supercede any MSISDN that was previously provided in the protocol configuration options information element. The MSISDN provided is for user information only, and the MS shall not use the MSISDN in any NAS signalling procedure. If the MSISDN is stored in the ME, the ME shall retain the MSISDN at power off. The MSISDN stored in the ME, if any, can only be used if the IMSI from the USIM matches the IMSI stored in non-volatile memory, else the MS shall delete the MSISDN. | 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.4 |
5,527 | 4.17.4 NF/NF service discovery by NF service consumer in the same PLMN | Figure 4.17.4-1: NF/NF service discovery in the same PLMN 1. The NF service consumer intends to discover services available in the network based on service name and target NF type. The NF service consumer invokes Nnrf_NFDiscovery_Request (Expected NF service Name, NF Type of the expected NF instance, NF type of the NF consumer) from an appropriate configured NRF in the same PLMN. The parameter may include optionally producer NF Set ID, NF Service Set ID, SUPI, Data Set Identifier(s), External Group ID (for UDM, UDR discovery), UE's Routing Indicator and Home Network Public Key identifier (for UDM and AUSF discovery), S-NSSAI, NSI ID if available and other service related parameters. In addition, for AMF discovery, the parameters may include AMF Region ID, AMF Set ID, TAI. The NF service consumer may indicate a preference for target NF location in the Nnrf_NFDiscovery_Request. A complete list of parameters is provided in service definition in clause 5.2.7.3.2. NOTE 1: The NF service consumer indicates its NF location for preference for target NF location. NOTE 2: The use of NSI ID within a PLMN depends on the network deployment. NOTE 3: The need for other service related parameters depends on the NF type of the expected NF instance(s) and refer to the clause 6.3 " Principles for Network function and Network Function Service discovery and selection" in TS 23.501[ System architecture for the 5G System (5GS) ] [2]. It is up to NF implementation whether one or multiple NF service instances are registered in the NRF. 2. The NRF authorizes the Nnrf_NFDiscovery_Request. Based on the profile of the expected NF/NF service and the type of the NF service consumer, the NRF determines whether the NF service consumer is allowed to discover the expected NF instance(s). If the expected NF instance(s) or NF service instance(s) are deployed in a certain network slice, NRF authorizes the discovery request according to the discovery configuration of the Network Slice, e.g. the expected NF instance(s) are only discoverable by the NF in the same network slice. 3. If allowed, the NRF determines a set of NF instance(s) matching the Nnrf_NFDiscovery_Request and internal policies of the NRF and sends the NF profile(s) of the determined NF instances. Each NF profile containing at least the output required parameters (see clause 5.2.7.3.2) to the NF service consumer via Nnrf_NFDiscovery_Request Response message. If the target NF is UDR, UDM or AUSF, if SUPI was used as optional input parameter in the request, the NRF shall provide the corresponding UDR, UDM or AUSF instance(s) that matches the optional input SUPI. Otherwise, if SUPI is not provided in the request, the NRF shall return all applicable UDR instance(s) (e.g. based on the Data Set Id, NF type), UDM instance(s) or AUSF instance(s) (e.g. based on NF type) and if applicable, the information of the range of SUPI(s) and/or Data Set Id each UDR instance is supporting. If the target NF is CHF, if SUPI, GPSI or PLMN ID was used as optional input parameter in the request, the NRF shall provide the corresponding CHF instance(s) that matches the optional input SUPI, GPSI or PLMN ID. The NRF shall provide the primary CHF instance and the secondary CHF instance pair(s) together, if configured in CHF instance profile. Otherwise, if neither SUPI/PLMN ID nor GPSI is provided in the request, the NRF shall return all applicable CHF instance(s) and if applicable, the information of the range of SUPI(s), GPSI(s) or PLMN ID(s). If the NF service consumer provided a preferred target NF location, the NRF shall not limit the set of discovered NF instances or NF service instance(s) to the target NF location, e.g. the NRF may provide NF instance(s) or NF service instance(s) for which location is not the preferred target NF location if no NF instance or NF service instance could be found for the preferred target NF location. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.17.4 |
5,528 | 7.2.25 Modify Access Bearers Response | If an SGW supports the MABR feature (see clause 8.83), the SGW shall send a Modify Access Bearers Response message on the S11 interface to an MME as a response to a Modify Access Bearers Request message. If handling of all default bearers to be modified fails, then Cause at the message level shall be a failure cause. Possible Cause values are specified in Table 8.4-1. Message specific cause values are: - "Request accepted". - "Request accepted partially". - "Context not found". - "Service not supported". - "Modifications not limited to S1-U bearers" The SGW shall send the cause value "Modifications not limited to S1-U bearers" if - it can not serve the MME Request without corresponding S5/S8 signalling other than to unpause charging in the PGW, or without corresponding Gxc signalling when PMIP is used over the S5/S8 interface, or - if there are suspended non-GBR bearers for that UE in the SGW (NOTE 3). Upon receipt of that cause value, the MME shall repeat its request using Modify Bearer Request message per PDN connection. NOTE 1: This cause value is introduced for forward compatibility between an MME implementing this version of the specification and an SGW implementing a more recent version requiring the SGW to send S5/S8 signalling. NOTE 2: During an Inter-MME Intra-SGW handover/TAU, if the SGW, PGW and the old MME support the partial failure handling feature but the new MME doesn't, the SGW needs to inform the PGW about the change of FQ-CSID (see clause 16.2.5 of 3GPP TS 23.007[ Restoration procedures ] [17]). If the SGW receives a Modify Access Bearers Request from the new MME, it can force the MME to send individual Modify Bearer Request message per PDN connection by returning the cause value "Modifications not limited to S1-U bearers". NOTE 3: There may be some suspended non-GBR bearers in the SGW during an Inter-MME Intra-SGW Tracking Area Update without SGW Change when the UE is coming back to E-UTRAN via a different MME than the MME serving the UE before the CSFB or SRVCC call. Table 7.2.25-1: Information Elements in a Modify Access Bearers Response Table 7.2.25-2: Bearer Context modified within Modify Access Bearers Response Table 7.2.25-3: Bearer Context marked for removal within Modify Access Bearers Response Table 7.2.25-4: Load Control Information within Modify Access Bearers Response Table 7.2.25-5: Overload Control Information within Modify Access Bearers 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.2.25 |
5,529 | 9.3.3.2 Data Forwarding for the User Plane | In case of indirect data forwarding, user plane handling for inter-System data forwarding from EPS to 5GS follows the following key principles: - For each E-RAB accepted for data forwarding, the source eNB forwards data to the SGW in the corresponding E-RAB tunnel and the SGW forwards the received data to the UPF in the E-RAB tunnel. - The UPF maps the forwarded data received from an E-RAB tunnel to the corresponding mapped PDU session tunnel, adding a QFI value (by means of the PDU Session User Plane protocol TS 38.415[ NG-RAN; PDU session user plane protocol ] [30]). - The target NG-RAN node maps a forwarded packet to the corresponding DRB based on the received QFI value. It prioritizes the forwarded packets over the fresh packets for those QoS flows. - Handling of end marker packets: - The UPF/PGW-U sends one or several end marker packets to the SGW per EPS bearer. The SGW forwards the received end markers per EPS bearer to the source eNB. When there are no more data packets to be forwarded for an E-RAB, the source eNB forwards the received end markers in the EPS bearer tunnel to the SGW and the SGW forwards them to the UPF. The UPF adds one QFI (by means of the PDU Session User Plane protocol TS 38.415[ NG-RAN; PDU session user plane protocol ] [30]) among the QoS flows mapped to that E-RAB to the end markers and sends those end markers to the target NG-RAN node in the per PDU session tunnel. When the target NG-RAN node receives an end marker with a QFI added, the target NG-RAN node starts to transmit the data packets of all QoS flows mapped to the corresponding E-RAB received from the core network towards the UE. In case of direct data forwarding, user plane handling for inter-System data forwarding from EPS to 5GS follows the following key principles: - For each E-RAB accepted for data forwarding, the source node forwards data to the target NG-RAN node in the corresponding E-RAB data forwarding tunnel. - Until a GTP-U end marker packet is received, the target NG-RAN node prioritizes the forwarded packets over the fresh packets for those QoS flows which are involved in the accepted data forwarding. NOTE: The target NG-RAN node should remove the forwarded PDCP SNs if received in the forwarded GTP-U packets, and deliver the forwarded PDCP SDUs to the UE. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 9.3.3.2 |
5,530 | 4.1 Overview | The non-access stratum (NAS) described in the present document forms the highest stratum of the control plane between UE and MME at the radio interface (reference point "LTE-Uu"; see 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10]). Main functions of the protocols that are part of the NAS are: - the support of mobility of the user equipment (UE); and - the support of session management procedures to establish and maintain IP connectivity between the UE and a packet data network gateway (PDN GW). NAS security is an additional function of the NAS providing services to the NAS protocols, e.g. integrity protection and ciphering of NAS signalling messages. For the support of the above functions, the following procedures are supplied within this specification: - elementary procedures for EPS mobility management in clause 5; and - elementary procedures for EPS session management in clause 6. Complete NAS transactions consist of specific sequences of elementary procedures. Examples of such specific sequences can be found in 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10]. The NAS for EPS follows the protocol architecture model for layer 3 as described in 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [12]; however, due to the objective of EPS to provide the subscriber with a "ready-to-use" IP connectivity and an "always-on" experience, the protocol supports a linkage between mobility management and session management procedures during the attach procedure (see clause 4.2). Signalling procedures for the control of NAS security are described as part of the EPS mobility management in clause 5. In addition to that, principles for the handing of EPS security contexts and for the activation of ciphering and integrity protection, when a NAS signalling connection is established, are provided in clause 4.4. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.1 |
5,531 | 10.5.4.32 Supported codec list | The purpose of the Supported Codec List information element is to provide the network with information about the speech codecs supported by the mobile. The Supported Codec List information element is coded as shown in figure 10.5.118c/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The Supported Codec List information element is a type 4 information element with a minimum length of 5 octets and a maximum length of m+3 octets. Speech codec information belonging to GERAN and UTRAN shall be conveyed by this information element. Figure 10.5.118c/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Supported codec list information element Table 10.5.4.135c/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Supported Codec List information element | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.4.32 |
5,532 | 9.9.3.51 Replayed NAS message container | The purpose of the Replayed NAS message container IE is to, during an ongoing attach or tracking area updating procedure, re-send the ATTACH REQUEST or TRACKING AREA UPDATE REQUEST message with which the UE had initiated the procedure, if the MME has included a HASHMME in the SECURITY MODE COMMAND message and the HASHMME is different from the hash value locally calculated at the UE as described in 3GPP TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [19]. If an ATTACH REQUEST message is included in this IE, the ATTACH REQUEST message shall be coded as specified in clause 8.2.4, i.e. without NAS security header. If a TRACKING AREA UPDATE REQUEST message is included in this IE, the TRACKING AREA UPDATE REQUEST message shall be coded as specified in clause 8.2.29, i.e. without NAS security header The Replayed NAS message container information element is coded as shown in figure 9.9.3.51.1 and table 9.9.3.51.1. The Replayed NAS message container is a type 6 information element. Figure 9.9.3.51.1: Replayed NAS message container information element Table 9.9.3.51.1: Replayed NAS message container 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.51 |
5,533 | 5.2.6.28.5 Nnef_ASTI_Get operation | Service operation name: Nnef_ASTI_Get Description: The consumer makes a query about the status of the access stratum time distribution, for which the NEF authorizes the request and invokes the corresponding service operation with TSCTSF (clause 5.2.27.4.5). Inputs, Required: As specified in clause 5.2.27.4.5. Inputs, Optional: As specified in clause 5.2.27.4.5. Outputs, Required: Operation execution result indication and in the case of successful operation, any outputs as specified in clause 5.2.27.4.5. Outputs, Optional: As specified in clause 5.2.27.4.5. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.6.28.5 |
5,534 | 7.6.3 Repeated IEs | If an information element with format T, TV, TLV, or TLV-E is repeated in a message in which repetition of the information element is not specified in clause 8 and clause 9 of the present document, the UE shall handle only the contents of the information element appearing first and shall ignore all subsequent repetitions of the information element. When repetition of information elements is specified, the UE shall handle only the contents of specified repeated information elements. If the limit on repetition of information elements is exceeded, the UE shall handle the contents of information elements appearing first up to the limit of repetitions and shall ignore all subsequent repetitions of the information element. The network should follow the same procedures. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 7.6.3 |
5,535 | 7.6.2.1G Minimum requirements for V2X | The throughput shall be ≥ 95% of the maximum throughput of the reference measurement channels as specified in Annex A.8.2 with parameters specified in Tables 7.6.2.1G-1, 7.6.2.1G-2. For Table 7.6.2.1G-2 in frequency range 1, 2 and 3, up to exceptions are allowed for spurious response frequencies in each assigned frequency channel when measured using a 1MHz step size, where is the number of resource blocks in the downlink transmission bandwidth configuration (see Figure 5.6-1). For these exceptions the requirements of subclause 7.7 spurious response are applicable. Table 7.6.2.1G-1: Out-of-band blocking parameters Table 7.6.2.1G-2: Out of band blocking When UE is configured for simultaneous E-UTRA V2X sidelink and E-UTRA downlink reception for inter-band E-UTRA V2X / E-UTRA bands specified in Table 5.5G-2, the requirements in subclause 7.6.2.1G apply for the E-UTRA V2X sidelink reception and the requirements in subclause 7.6.2.1 apply for the E-UTRA downlink reception while all downlink carriers are active. For intra-band contiguous multi-carrier operation, the V2X UE throughput shall be ≥ 95% of the maximum throughput of the reference measurement channels as specified in Annex A.8.2 with parameters specified in Tables 7.6.2.1G-3 and 7.6.2.1G-4. For Table .1G-4 in frequency range 1, 2 and 3, up to exceptions are allowed for spurious response frequencies in each assigned frequency channel when measured using a 1MHz step size. For these exceptions the requirements of subclause 7.7 spurious response are applicable. Table .1G-3: Out-of-band blocking parameters for intra-band contiguous multi-carrier for V2X UE Table .1G-4: Out of band blocking for intra-band contiguous multi-carrier for V2X UE | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 7.6.2.1G |
5,536 | 5.38.2 Connection Release | A Multi-USIM UE may request the network to release the UE from RRC_CONNECTED state in 3GPP access for a USIM due to activity on another USIM in 3GPP access, if both UE and network indicate the Connection Release feature is supported to each other. In the case of NAS connection release procedure, the UE indicates that it requests to be released from RRC_CONNECTED state, by initiating either a Service Request procedure over 3GPP access or a Registration procedure over 3GPP access (if case the UE needs to perform Registration Update at the same time with this network, including the case where the Registration Request is sent due to mobility outside the Registration Area, i.e. before detecting whether the network supports the feature in the new Tracking Area, provided that the network has already indicated support for Connection Release feature in the current stored Registration Area), by including a Release Request Indication. If supported by the UE and network, the UE may also provide, only together with the Release Request Indication, Paging Restriction Information, as specified in clause 5.38.5, which requests the network to restrict paging. If the UE is performing an Emergency Registration then it shall not include a Release Request Indication. For NR/5G access, an AS method for the UE to request the network to release the UE from RRC_CONNECTED state is specified in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27]. This mechanism does not allow the UE to indicate Paging Restrictions. NOTE 1: When both the access stratum and NAS based approaches for requesting the connection release are supported by the UE and the network, it depends on the UE implementation which of the two to use (for example: based on the preferred end state (RRC_INACTIVE or RRC_IDLE) and whether Paging Restriction Information is to be provided). NOTE 2: When there is no PLMN-wide support for the Connection Release feature, it can occur that upon Mobility Registration Update with Release Request indication the UE is not released by the network. The UE behaviour, when it detects that the network does not support the feature in a new RA, is outside the scope of this specification. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.38.2 |
5,537 | 5.2.2.4.2 Namf_MT_EnableUEReachability service operation | Service operation name: Namf_MT_EnableUEReachability. Description: The consumer NF uses this service operation to request enabling UE reachability. Inputs, Required: NF ID, UE ID. Inputs, Optional: Extended Buffering Support, PPI, ARP, 5QI, QFI, PDU Session ID. Outputs, Required: Result indication. Outputs, Optional: Redirection information, Estimated Maximum wait time. See clause 4.13.3.6 and clause 4.24.2 for details on the usage of this service operation. The consumer NF does not need to know UE state. The AMF accepts the request and respond the consumer NF immediately if UE is in CM-CONNECTED state. If the UE is in CM-IDLE state, the AMF may page the UE and respond to the consumer NF after the UE enters CM-CONNECTED state. If the result of the service operation fails, the AMF shall set the corresponding cause value in the result indication which can be used by the NF consumer for further action. If the related UE is not served by the AMF and the AMF knows which AMF is serving the UE, the AMF provides redirection information which can be used by the NF consumer to resend UE related message to the AMF that serves the UE. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.2.4.2 |
5,538 | 4.16.12.2 UE Policy Association Modification initiated by the PCF | This procedure is used to update UE policy and/or UE policy triggers. In the non-roaming case, the H-PCF may interact with the CHF in HPLMN to make a decision about UE Policies based on spending limits. Figure 4.16.12.2-1: UE Policy Association Modification initiated by the PCF This procedure concerns both roaming and non-roaming scenarios. In the non-roaming case the V-PCF is not involved and the role of the H-PCF is performed by the PCF. In the roaming case, the H-PCF provides UE policy decision and provides the policy to the AMF via V-PCF. 1a and 1b. If (H-)PCF subscribed to notification of subscriber´s policy data change or 5G VN Group Configuration (5G VN group data, 5G VN group membership) change and a change is detected, the UDR notifies that the subscriber´s policy data of a UE or 5G VN Group Configuration (5G VN group data, 5G VN group membership) has been changed. The UDR notifies the (H-)PCF of the updated policy control subscription information profile via Nudr_DM_Notify (Notification correlation Id, Policy Data, either UE context policy control data or Policy Set Entry data or both, SUPI), or The UDR notifies the (H-)PCF of the updated 5G VN Group Configuration (5G VN group data, 5G VN group membership) via Nudr_DM_Notify (Notification correlation Id, 5G VN Group Configuration, Internal-Group-Identifier), or The (V-)UDR notifies the (V-)PCF of the updated policy control subscription information profile via Nudr_DM_Notify (Notification correlation Id, Policy Data, PolicySetEntry Data. PLMN ID). The (V-)UDR notifies the (V-)PCF of the updated Service Parameters via Nudr_DM_Notify. 1c and 1d. PCF determines locally that UE policy information needs to be sent to the UE. 1e The CHF notifies the (H-)PCF about the change of the status of the subscribed policy counters available at the CHF for that subscriber. 2a and 2b. The PCF makes the policy decision. If the group data is updated, the (H-) PCF checks the UE Policy Associations for those SUPIs within the Internal-Group-Id and may need to perform step 3 to step 9 for each UE Policy Association that needs to be updated with new UE Policies sent to each UE. In the non-roaming case, the PCF may subscribe to Analytics from NWDAF as defined in clause 6.1.1.3 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. 2c and 2d. In the roaming case, the V-PCF may provide the updated Service Parameters received from the V-UDR as specified in clause 4.15.6.10 to the H-PCF using the Npcf_UEPolicyControl_Update Request. The H-PCF sends a response to the V-PCF. 3. The (H-)PCF may create the UE policy container including UE policy information as defined in clause 6.1.2.2.2 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. In the case of roaming, the H-PCF may send the UE policy container in the Npcf_UEPolicyControl UpdateNotify Request. The H-PCF may provide updated policy control triggers for the UE policy association. If there is the received Service Parameters from the V-PCF in step 2, the H-PCF may take the Service Parameters obtained from V-PCF to generate URSP rules applicable in the VPLMN as specified in clause 4.15.6.10. 4. The V-PCF sends a response to H-PCF using Npcf_UEPolicyControl UpdateNotify Response. 5. The (V-)PCF provides the Policy Control Request Trigger parameters in the Npcf_UEPolicyControl UpdateNotify Request to the AMF. In the case of roaming, the V-PCF may also provide UE policy information to the UE. The V-PCF may also provide updated policy control triggers for the UE policy association to the AMF. 6. The AMF sends a response to (V-)PCF. Steps 7, 8 and 9 are the same as steps 8, 9 and 10 of procedure UE Policy Association Establishment in clause 4.16.11. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.16.12.2 |
5,539 | 5.2.2.1 Call indication | After the arrival of a call from a remote user, the corresponding call control entity in the network shall: initiate the MM connection establishment according to clause 4 and enter the "MM connection pending" state. The request to establish the MM connection is passed from the CM sublayer to the MM sublayer. It contains the necessary routing information derived from the SETUP message. Upon completion of the MM connection, the call control entity of the network shall: send the SETUP message to its peer entity at the mobile station, start timer T303 and enter the "call present" state. The SETUP message shall contain the multicall supported information in the network call control capabilities in the case where the network supports multicall and there are no other ongoing calls to the MS. Mobile stations supporting multicall shall store this information until the call control state for all calls returns to null. Mobile stations not supporting multicall shall ignore this information if provided in a SETUP message. If the multicall supported information is not sent in the SETUP message, the mobile station supporting multicall shall regard that the network does not support multicall. Upon receipt of a SETUP message, the mobile station shall perform compatibility checking as described in subclause 5.2.2.2. If the result of the compatibility checking was compatibility, the call control entity of the mobile station shall enter the "call present" state. An incompatible mobile station shall respond with a RELEASE COMPLETE message in accordance with subclause 5.2.2.3.4. If there are no bearer capability IEs in the SETUP message, the network may provide information about the requested service in the backup bearer capability IE. If no response to the SETUP message is received by the call control entity of the network before the expiry of timer T303, the procedures described in subclause 5.2.2.3.3 shall apply. Figure 5.6/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Mobile terminating call initiation and possible subsequent responses. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.2.2.1 |
5,540 | 6.1.2 MAC PDU (DL-SCH and UL-SCH except transparent MAC and Random Access Response, MCH) | A MAC PDU consists of a MAC header, zero or more MAC Service Data Units (MAC SDU), zero, or more MAC control elements, and optionally padding; as described in Figure 6.1.2-3. Both the MAC header and the MAC SDUs are of variable sizes. A MAC PDU header consists of one or more MAC PDU subheaders; each subheader corresponds to either a MAC SDU, a MAC control element or padding. A MAC PDU subheader consists of the header fields R/F2/E/LCID/(R/R/eLCID)/(F)/(L). The L field is present in the MAC PDU subheader except for the last subheader in the MAC PDU and fixed sized MAC control elements. The last subheader in the MAC PDU and subheaders for fixed sized MAC control elements consist of the header fields R/F2/E/LCID/(R/R/eLCID). A MAC PDU subheader corresponding to padding consists of the four header fields R/F2/E/LCID. Figure 6.1.2-1: R/F2/E/LCID/(R/R/eLCID)/F/L MAC subheader with 7-bits and 15-bits L field Figure 6.1.2-1a: R/F2/E/LCID/(R/R/eLCID)/L MAC subheader with 16-bits L field Figure 6.1.2-2: R/F2/E/LCID/(R/R/eLCID) MAC subheader MAC PDU subheaders have the same order as the corresponding MAC SDUs, MAC control elements and padding. MAC control elements are always placed before any MAC SDU. Padding occurs at the end of the MAC PDU, except when single-byte or two-byte padding is required. Padding may have any value and the MAC entity shall ignore it. When padding is performed at the end of the MAC PDU, zero or more padding bytes are allowed. When single-byte or two-byte padding is required, one or two MAC PDU subheaders corresponding to padding are placed at the beginning of the MAC PDU before any other MAC PDU subheader. A maximum of one MAC PDU can be transmitted per TB per MAC entity. A maximum of one MCH MAC PDU can be transmitted per TTI. Figure 6.1.2-3: Example of MAC PDU consisting of MAC header, MAC control elements, MAC SDUs and padding | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.1.2 |
5,541 | 19.4.2.9A.3 Tracking/Location Area Identity based Emergency ePDG FQDN | There are two Tracking Area Identity based Emergency ePDG FQDNs defined: one based on a TAI with a 2 octet TAC and a 5GS one based on a 3 octet TAC. 1) The Tracking Area Identity based Emergency ePDG FQDN using a 2 octet TAC and the Location Area Identity based Emergency ePDG FQDN shall be constructed as specified for the Tracking Area Identity based ePDG FQDN and the Location Area Identity based ePDG FQDN in clause 19.4.2.9.3, with the addition of the label "sos" before the labels "epdg.epc". The Tracking Area Identity based Emergency ePDG FQDN and the Location Area Identity based Emergency ePDG FQDN shall be constructed as follows: "tac-lb<TAC-low-byte>.tac-hb<TAC-high-byte>.tac.sos.epdg.epc.mnc<MNC>.mcc<MCC>.pub.3gppnetwork.org" and "lac<LAC>.sos.epdg.epc.mnc<MNC>.mcc<MCC>.pub.3gppnetwork.org" As examples, - the Tracking Area Identity based Emergency ePDG FQDN for the TAC H'0B21, MCC 345 and MNC 12 is coded in the DNS as: " tac-lb21.tac-hb0b.tac.sos.epdg.epc.mnc012.mcc345.pub.3gppnetwork.org" - the Location Area Identity based Emergency ePDG FQDN for the LAC H'0B21, MCC 345 and MNC 12 is coded in the DNS as: " lac0b21.sos.epdg.epc.mnc012.mcc345.pub.3gppnetwork.org" 2) The 5GS Tracking Area Identity based Emergency ePDG FQDN using a 3 octet TAC shall be constructed as specified for the 5GS Tracking Area Identity based ePDG FQDN in clause 19.4.2.9.3, with the addition of the label "sos" before the labels "epdg.epc". The 5GS Tracking Area Identity based Emergency ePDG FQDN shall be constructed as follows: "tac-lb<TAC-low-byte>.tac-mb<TAC-middle-byte>.tac-hb<TAC-high-byte>.5gstac.sos. epdg.epc.mnc<MNC>.mcc<MCC>.pub.3gppnetwork.org " As examples, - the 5GS Tracking Area Identity based Emergency ePDG FQDN for the 5GS TAC H'0B1A21, MCC 345 and MNC 12 is coded in the DNS as: "tac-lb21.tac-mb1a.tac-hb0b.5gstac.sos.epdg.epc.mnc012.mcc345.pub.3gppnetwork.org" | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 19.4.2.9A.3 |
5,542 | 10.2.6B.1 Sequence generation | The NWUS sequence in subframe is defined by where is the actual duration of NWUS as defined in [4]. For a UE not configured with group NWUS, . For a UE configured with group NWUS, for , where is determined by the UE group to which the UE is associated as determined by higher layers [10]. In a resource that is not shared with non-group NWUS, the common NWUS sequence shall be determined by . In a resource that is shared with non-group NWUS, the common NWUS sequence is determined by higher layers [9]. The scrambling sequence is given by clause 7.2, and shall be initialized at the start of the NWUS with where is the first frame of the first PO to which the NWUS is associated, is the first slot of the first PO to which the NWUS is associated and indicates the group NWUS resource to which the UE is associated. For a UE not configured with group NWUS, , whereas for a UE configured with group NWUS, is determined by higher layers [10]. | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 10.2.6B.1 |
5,543 | 4.2.5 Behaviour in state GMM-REGISTERED | The state GMM-REGISTERED is entered when: - a GMM context is established, i.e. the MS is IMSI attached for GPRS services only or for GPRS and non-GPRS services. The specific behaviour of the MS in state GMM-REGISTERED is described in subclause 4.2.5.1. The primary substate when entering the state GMM-REGISTERED is always NORMAL-SERVICE. It should be noted that transitions between the various substates of GMM-REGISTERED are caused by (e.g.): - cell selection/reselection (see also 3GPP TS 43.022[ None ] [82] and 3GPP TS 25.304[ None ] [98]); - change of RA; - loss/regain of coverage. How various GMM procedures affect the GMM-REGISTERED substates is described in the detailed description of the procedures in subclause 4.7. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.2.5 |
5,544 | 5.31.7.5 MICO mode and Periodic Registration Timer Control | If the Expected UE Behaviour indicates the absence of DL communication, the AMF may allow MICO mode for the UE and allocate a large periodic registration timer value based on e.g. Network Configuration parameters to the UE so that the UE can maximise power saving between Periodic Registration Updates. If the Expected UE Behaviour indicates scheduled DL communication the AMF should allow MICO mode for the UE and allocate a periodic registration timer value such that the UE performs Periodic Registration Update to renegotiate MICO mode before or at the scheduled DL communication time, if the AMF decides to allow MICO mode for the UE. When UE requests the MICO mode with active time, the UE may also request a periodic registration timer value suitable for the latency/responsiveness of the DL communication service known to UE. If the UE wants to change the periodic registration timer value, e.g. when the conditions are changed in the UE, the UE consequently requests the value it wants in the registration procedure. The AMF takes the UE requested periodic registration time value into consideration when providing the periodic registration timer to UE during Registration procedure as specified in clause 4.2.2.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. If the UE supports 'Strictly Periodic Registration Timer Indication', the UE indicates its capability of supporting 'Strictly Periodic Registration Timer Indication' in the Registration Request message. If the UE indicates its support of 'Strictly Periodic Registration Timer Indication' in the Registration Request message, the AMF may provide a Strictly Periodic Registration Timer Indication to the UE together with the periodic registration timer value, e.g. based on Expected UE Behaviour. If the indication is provided by the AMF, the UE and the AMF shall start the periodic registration timer after completion of the Registration procedure. The UE and the AMF shall neither stop nor restart the periodic registration timer when the UE enters CM-CONNECTED, and shall keep it running while in CM-CONNECTED state and after returning to CM-IDLE state. If and only when the timer expires and the UE is in CM-IDLE, the UE shall perform a Periodic Registration Update. If the timer expires and the UE is in CM-CONNECTED state, the AMF and the UE restart the periodic registration timer while still applying 'Strictly Periodic Registration Timer Indication'. The AMF may use the UE Configuration Update procedure to trigger the UE to perform Registration procedure, in which the periodic registration timer value and 'Strictly Periodic Registration Timer Indication' can be renegotiated. When the UE and the AMF locally disable MICO mode (e.g. when an emergency service is initiated), the UE and the AMF shall not apply 'Strictly Periodic Registration Timer Indication'. If the periodic registration timer is renegotiated during a Registration procedure, e.g. triggered by UE Configuration Update, and if the periodic registration timer is running, then the periodic registration timer is stopped and restarted using the renegotiated value even when the Strictly Periodic Registration Timer Indication was provided to the UE. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.31.7.5 |
5,545 | 6.6.4.2 UP integrity mechanisms between the UE and the gNB | The use and mode of operation of the 128-bit NIA algorithms are specified in Annex D. The input parameters to the 128-bit NIA algorithms as described in Annex D are, the message packet, a 128-bit integrity key KUPint as KEY, a 5-bit bearer identity BEARER value of which is assigned as specified by TS 38.323[ NR; Packet Data Convergence Protocol (PDCP) specification ] [23], the 1-bit direction of transmission DIRECTION, and a bearer specific, and direction dependent 32-bit input COUNT which corresponds to the 32-bit PDCP COUNT. If the gNB or the UE receives a PDCP PDU which fails integrity check with faulty or missing MAC-I after the start of integrity protection, the PDU shall be discarded. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.6.4.2 |
5,546 | – RRCReconfiguration | The RRCReconfiguration message is the command to modify an RRC connection. It may convey information for measurement configuration, mobility control, radio resource configuration (including RBs, MAC main configuration and physical channel configuration) and AS security configuration. Signalling radio bearer: SRB1 or SRB3 RLC-SAP: AM Logical channel: DCCH Direction: Network to UE RRCReconfiguration message -- ASN1START -- TAG-RRCRECONFIGURATION-START RRCReconfiguration ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { rrcReconfiguration RRCReconfiguration-IEs, criticalExtensionsFuture SEQUENCE {} } } RRCReconfiguration-IEs ::= SEQUENCE { radioBearerConfig RadioBearerConfig OPTIONAL, -- Need M secondaryCellGroup OCTET STRING (CONTAINING CellGroupConfig) OPTIONAL, -- Cond SCG measConfig MeasConfig OPTIONAL, -- Need M lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension RRCReconfiguration-v1530-IEs OPTIONAL } RRCReconfiguration-v1530-IEs ::= SEQUENCE { masterCellGroup OCTET STRING (CONTAINING CellGroupConfig) OPTIONAL, -- Need M fullConfig ENUMERATED {true} OPTIONAL, -- Cond FullConfig dedicatedNAS-MessageList SEQUENCE (SIZE(1..maxDRB)) OF DedicatedNAS-Message OPTIONAL, -- Cond nonHO masterKeyUpdate MasterKeyUpdate OPTIONAL, -- Cond MasterKeyChange dedicatedSIB1-Delivery OCTET STRING (CONTAINING SIB1) OPTIONAL, -- Need N dedicatedSystemInformationDelivery OCTET STRING (CONTAINING SystemInformation) OPTIONAL, -- Need N otherConfig OtherConfig OPTIONAL, -- Need M nonCriticalExtension RRCReconfiguration-v1540-IEs OPTIONAL } RRCReconfiguration-v1540-IEs ::= SEQUENCE { otherConfig-v1540 OtherConfig-v1540 OPTIONAL, -- Need M nonCriticalExtension RRCReconfiguration-v1560-IEs OPTIONAL } RRCReconfiguration-v1560-IEs ::= SEQUENCE { mrdc-SecondaryCellGroupConfig SetupRelease { MRDC-SecondaryCellGroupConfig } OPTIONAL, -- Need M radioBearerConfig2 OCTET STRING (CONTAINING RadioBearerConfig) OPTIONAL, -- Need M sk-Counter SK-Counter OPTIONAL, -- Need N nonCriticalExtension RRCReconfiguration-v1610-IEs OPTIONAL } RRCReconfiguration-v1610-IEs ::= SEQUENCE { otherConfig-v1610 OtherConfig-v1610 OPTIONAL, -- Need M bap-Config-r16 SetupRelease { BAP-Config-r16 } OPTIONAL, -- Need M iab-IP-AddressConfigurationList-r16 IAB-IP-AddressConfigurationList-r16 OPTIONAL, -- Need M conditionalReconfiguration-r16 ConditionalReconfiguration-r16 OPTIONAL, -- Need M daps-SourceRelease-r16 ENUMERATED{true} OPTIONAL, -- Need N t316-r16 SetupRelease {T316-r16} OPTIONAL, -- Need M needForGapsConfigNR-r16 SetupRelease {NeedForGapsConfigNR-r16} OPTIONAL, -- Need M onDemandSIB-Request-r16 SetupRelease { OnDemandSIB-Request-r16 } OPTIONAL, -- Need M dedicatedPosSysInfoDelivery-r16 OCTET STRING (CONTAINING PosSystemInformation-r16-IEs) OPTIONAL, -- Need N sl-ConfigDedicatedNR-r16 SetupRelease {SL-ConfigDedicatedNR-r16} OPTIONAL, -- Need M sl-ConfigDedicatedEUTRA-Info-r16 SetupRelease {SL-ConfigDedicatedEUTRA-Info-r16} OPTIONAL, -- Need M targetCellSMTC-SCG-r16 SSB-MTC OPTIONAL, -- Need S nonCriticalExtension RRCReconfiguration-v1700-IEs OPTIONAL } RRCReconfiguration-v1700-IEs ::= SEQUENCE { otherConfig-v1700 OtherConfig-v1700 OPTIONAL, -- Need M sl-L2RelayUE-Config-r17 SetupRelease { SL-L2RelayUE-Config-r17 } OPTIONAL, -- Need M sl-L2RemoteUE-Config-r17 SetupRelease { SL-L2RemoteUE-Config-r17 } OPTIONAL, -- Need M dedicatedPagingDelivery-r17 OCTET STRING (CONTAINING Paging) OPTIONAL, -- Cond PagingRelay needForGapNCSG-ConfigNR-r17 SetupRelease {NeedForGapNCSG-ConfigNR-r17} OPTIONAL, -- Need M needForGapNCSG-ConfigEUTRA-r17 SetupRelease {NeedForGapNCSG-ConfigEUTRA-r17} OPTIONAL, -- Need M musim-GapConfig-r17 SetupRelease {MUSIM-GapConfig-r17} OPTIONAL, -- Need M ul-GapFR2-Config-r17 SetupRelease { UL-GapFR2-Config-r17 } OPTIONAL, -- Need M scg-State-r17 ENUMERATED { deactivated } OPTIONAL, -- Need N appLayerMeasConfig-r17 AppLayerMeasConfig-r17 OPTIONAL, -- Need M ue-TxTEG-RequestUL-TDOA-Config-r17 SetupRelease {UE-TxTEG-RequestUL-TDOA-Config-r17} OPTIONAL, -- Need M nonCriticalExtension RRCReconfiguration-v1800-IEs OPTIONAL } RRCReconfiguration-v1800-IEs ::= SEQUENCE { needForInterruptionConfigNR-r18 ENUMERATED { enabled, disabled } OPTIONAL, -- Need M uav-Config-r18 SetupRelease { UAV-Config-r18 } OPTIONAL, -- Need M sl-IndirectPathAddChange-r18 SetupRelease { SL-IndirectPathAddChange-r18 } OPTIONAL, -- Need M n3c-IndirectPathAddChange-r18 SetupRelease { N3C-IndirectPathAddChange-r18 } OPTIONAL, -- Need M n3c-IndirectPathConfigRelay-r18 SetupRelease { N3C-IndirectPathConfigRelay-r18 } OPTIONAL, -- Need M otherConfig-v1800 OtherConfig-v1800 OPTIONAL, -- Need M srs-PosResourceSetLinkedForAggBWList-r18 SetupRelease { SRS-PosResourceSetLinkedForAggBWList-r18 } OPTIONAL, -- Need M ltm-Config-r18 SetupRelease {LTM-Config-r18} OPTIONAL, -- Need M nonCriticalExtension SEQUENCE {} OPTIONAL } MRDC-SecondaryCellGroupConfig ::= SEQUENCE { mrdc-ReleaseAndAdd ENUMERATED {true} OPTIONAL, -- Need N mrdc-SecondaryCellGroup CHOICE { nr-SCG OCTET STRING (CONTAINING RRCReconfiguration), eutra-SCG OCTET STRING } } BAP-Config-r16 ::= SEQUENCE { bap-Address-r16 BIT STRING (SIZE (10)) OPTIONAL, -- Need M defaultUL-BAP-RoutingID-r16 BAP-RoutingID-r16 OPTIONAL, -- Need M defaultUL-BH-RLC-Channel-r16 BH-RLC-ChannelID-r16 OPTIONAL, -- Need M flowControlFeedbackType-r16 ENUMERATED {perBH-RLC-Channel, perRoutingID, both} OPTIONAL, -- Need R ... } MasterKeyUpdate ::= SEQUENCE { keySetChangeIndicator BOOLEAN, nextHopChainingCount NextHopChainingCount, nas-Container OCTET STRING OPTIONAL, -- Cond securityNASC ... } OnDemandSIB-Request-r16 ::= SEQUENCE { onDemandSIB-RequestProhibitTimer-r16 ENUMERATED {s0, s0dot5, s1, s2, s5, s10, s20, s30} } T316-r16 ::= ENUMERATED {ms50, ms100, ms200, ms300, ms400, ms500, ms600, ms1000, ms1500, ms2000} IAB-IP-AddressConfigurationList-r16 ::= SEQUENCE { iab-IP-AddressToAddModList-r16 SEQUENCE (SIZE(1..maxIAB-IP-Address-r16)) OF IAB-IP-AddressConfiguration-r16 OPTIONAL, -- Need N iab-IP-AddressToReleaseList-r16 SEQUENCE (SIZE(1..maxIAB-IP-Address-r16)) OF IAB-IP-AddressIndex-r16 OPTIONAL, -- Need N ... } IAB-IP-AddressConfiguration-r16 ::= SEQUENCE { iab-IP-AddressIndex-r16 IAB-IP-AddressIndex-r16, iab-IP-Address-r16 IAB-IP-Address-r16 OPTIONAL, -- Need M iab-IP-Usage-r16 IAB-IP-Usage-r16 OPTIONAL, -- Need M iab-donor-DU-BAP-Address-r16 BIT STRING (SIZE(10)) OPTIONAL, -- Need M ... } SL-ConfigDedicatedEUTRA-Info-r16 ::= SEQUENCE { sl-ConfigDedicatedEUTRA-r16 OCTET STRING OPTIONAL, -- Need M sl-TimeOffsetEUTRA-List-r16 SEQUENCE (SIZE (8)) OF SL-TimeOffsetEUTRA-r16 OPTIONAL -- Need M } SL-TimeOffsetEUTRA-r16 ::= ENUMERATED {ms0, ms0dot25, ms0dot5, ms0dot625, ms0dot75, ms1, ms1dot25, ms1dot5, ms1dot75, ms2, ms2dot5, ms3, ms4, ms5, ms6, ms8, ms10, ms20} UE-TxTEG-RequestUL-TDOA-Config-r17 ::= CHOICE { oneShot-r17 NULL, periodicReporting-r17 ENUMERATED { ms160, ms320, ms1280, ms2560, ms61440, ms81920, ms368640, ms737280 } } SRS-PosResourceSetLinkedForAggBWList-r18 ::= SEQUENCE (SIZE(1..maxNrOfLinkedSRS-PosResourceSet-r18)) OF SRS-PosResourceSetLinkedForAggBW-r18 -- TAG-RRCRECONFIGURATION-STOP -- ASN1STOP Editor's Note: FFS whether/how to indicate PC5 release/maintain for indirect path add/modify/release. And for indirect path release, FFS whether to include an explicit "directPathRelease" flag in the reconfiguration procedure so that the UE can apply a simpler behaviour. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,547 | 16.5.3 eCall over IMS | NG-RAN broadcast an indication to indicate support of eCall over IMS (eCallOverIMS-Support). UEs that are in limited service state need to consider both eCallOverIMS-Support and ims-EmergencySupport to determine if eCall over IMS is possible. UEs that are not in limited service state need to only consider eCallOverIMS-Support to determine if eCall over IMS is possible. The broadcast indicator is set to "support" if the PLMN in a non-shared environment, or all PLMNs in a shared environment, supports eCall over IMS. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.5.3 |
5,548 | 8.2.9.1 Message definition | The REGISTRATION REJECT message is sent by the AMF to the UE. See table 8.2.9.1.1. Message type: REGISTRATION REJECT Significance: dual Direction: network to UE Table 8.2.9.1.1: REGISTRATION REJECT message content NOTE: It is possible for AMFs compliant with version 17.7.0 or 17.8.0 of this specification to send the Forbidden TAI(s) for the list of "5GS forbidden tracking areas for roaming" IE with IEI of value "3B" for this message or the Forbidden TAI(s) for the list of "5GS forbidden tracking areas for regional provision of service" IE with IEI of value "3C" for this message. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 8.2.9.1 |
5,549 | 6.14.1 Description | With the Internet of Things, it is expected that the diversity of IoT devices (e.g. sensors, UAVs, smart flower pots) and the usage models will largely vary. Moreover, when the IoT device is manufactured, the deployment location and specific usage might not be known. Sometimes the IoT devices will be added to existing subscriptions, other times they can be part of a new subscription for the user. Sometimes the IoT devices can be leased. During their life cycle these IoT devices go through different stages, involving the change in ownership when the IoT device is deployed and possibly afterwards, the activation of the IoT device by the preferred operator, a possible change of operators, etc. These stages need to be managed securely and efficiently. A method of dynamic subscription generation and management is needed in addition to statically provisioned subscription. Once the subscription is established, subscription management becomes necessary, for example, to modify the subscription when the ownership of the IoT device changes, to update or refresh credentials due to suspected leakage or theft of security keys or as a preventive measure. The Internet of Things will also support various connectivity models: The IoT devices can connect with the network directly or connect with the network using another IoT device as a relay UE, or they can be capable of using both types of connections. The direct device connection between the IoT device and the relay UE can be using 3GPP or non-3GPP RAT. The relay UE can access the network also using 3GPP or non-3GPP access networks (e.g. WLAN, fixed broadband access network). In order to identify and manage the IoT devices, a subscription with the 5G network is needed, even if the access is done via non-3GPP access. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.14.1 |
5,550 | 8.17.3.2 IAB inter-CU topology adaptation procedure with descendant IAB-node | Figure 8.17.3.2-1 shows an example of the topology adaptation procedure where the migrating IAB-MT is migrated from a source IAB-donor-CU to a target IAB-donor-CU, and where the migrating IAB-node has a descendant IAB-node which retains both its RRC connection and F1 connection with the source IAB-donor-CU. Figure 8.17.3.2-1: IAB inter-CU topology adaptation procedure with descendant IAB-node 0. The topology adaptation procedure of clause 8.17.3.1 is performed for the migrating IAB-node. 1. The source IAB-donor-CU sends an IAB TRANSPORT MIGRATION MANAGEMENT REQUEST message to the target IAB-donor-CU to provide the context of the descendant IAB-node’s traffic to be offloaded. The message may include a request for new TNL address(es) for the descendant IAB-node(s), anchored at a target IAB-donor-DU. The source IAB-donor-CU includes an identifier of the migrating IAB-node in the request message. This could be performed in parallel with step 0 after the source IAB-donor-CU receives HANDOVER REQUEST ACKNOWLEDGE message, e.g., the context of the traffic to be offloaded for the migrating/descendant nodes and IP address request information could be contained in the same IAB TRANSPORT MIGRATION MANAGEMENT REQUEST message. 2. The target IAB-donor-CU determines the target IAB-donor-DU, based on the identifier of the migrating IAB-node. The target IAB-donor-CU may configure or modify BH RLC channels and BAP-sublayer routing entries on the target path between the boundary IAB-node and target IAB-donor-DU, as well as DL mappings on the target IAB-donor-DU for the migrating IAB-node’s target path. These configurations may support the transport of UP and non-UP traffic on the target path. 3. The target IAB-donor-CU may obtain new TNL address(es) from the target IAB-donor-DU, based on the request for TNL address(es) received in step 1. 4. The target IAB-donor-CU responds with an IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE message to the source IAB-donor-CU, to provide the mapping information for the traffic to be offloaded. The message includes the L2 info from the target IAB-donor-CU topology that is necessary to configure the migrating IAB-node with the BAP-sublayer routing, header-rewriting and BH RLC CH mapping entries of traffic indicated in step 1. The message includes the DSCP/IPv6 Flow Label values to be used for the DL traffic to be offloaded as indicated in step 1. The message may include the new TNL address(es) obtained in step 3, if any. NOTE 1: The target IAB-donor-CU should select the same IAB-donor-DU in its IAB topology for all to-be-offloaded traffic, whose UL BH mappings received from the source IAB-donor-CU in step 1 share the same BAP address. NOTE 2: The target IAB-donor-CU should provide the same Egress BAP Routing ID for all to-be-offloaded uplink traffic, whose UL BH mappings received from the source IAB-donor-CU in step 1 share the same Ingress BAP Routing ID. 5. The source IAB-donor-CU configures the migrating IAB-node’s IAB-DU with the BAP-sublayer routing, header-rewriting and BH RLC CH mapping entries of the migrating IAB-node. 6. The source IAB-donor-CU sends a DL RRC MESSAGE TRANSFER message to the descendant IAB-node’s parent IAB-DU, which includes an RRCReconfiguration message for the descendant IAB-MT. The RRC configuration may include the new TNL addresses received in step 4. If needed, the source IAB-donor-CU may also provide a new default UL mapping which includes a default BH RLC channel and a default BAP Routing ID on the target path, to the descendant nodes via RRCReconfiguration message. 7. The descendant IAB-node’s parent IAB-DU forwards the received RRCReconfiguration message to the descendant IAB-MT. 8. The descendant IAB-MT responds to the migrating IAB-node’s IAB-DU with an RRCReconfigurationComplete message. 9. The migrating IAB-node’s IAB-DU sends an UL RRC MESSAGE TRANSFER message to the source IAB-donor-CU, to convey the received RRCReconfigurationComplete message. 10. If needed, the source IAB-donor-CU configures UL BH mappings on the descendant node and BAP-sublayer routing entries between the descendant node and the migrating IAB-node. This step may be performed at an earlier stage, e.g., immediately after step 4. 11. The F1-C connections and F1-U tunnels are switched to use the descendant IAB-node’s new TNL address(es), if any, as described in Steps 15 and 19 of the inter-CU topology adaptation procedure in clause 8.17.3.1. NOTE: The IP address selected by the descendant IAB-node for an offloaded traffic needs to be anchored at the IAB-donor-DU whose BAP address is contained in the BAP routing ID of the UL mapping for this traffic, and obtained in step 7. 12. The source IAB-donor-CU sends an IAB TRANSPORT MIGRATION MANAGEMENT REQUEST message to the target IAB-donor-CU, to modify the context of the descendant IAB-node’s offloaded traffic. The message may include the DL TNL address information received in step 11 that is necessary for the target IAB-donor-CU to configure or modify DL mappings on the target IAB-donor-DU. 13. The target IAB-donor-CU responds with an IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE message to the source IAB-donor-CU. 14. The of steps above may be repeated, if needed, for the source IAB-donor-CU to request addition, modification or release of the offloaded traffic pertaining to the descendant IAB-node. The target IAB-donor-CU can fully or partially reject addition or modification requests by the source IAB-donor-CU. The target IAB-donor-CU may trigger the modification of the L2 transport of the offloaded traffic in the target IAB-donor-CU’s topology using the IAB TRANSPORT MIGRATION MODIFICATION REQUEST message. Based on this message, the source IAB-donor-CU may reconfigure the UL BH mappings on the descendant nodes, the routing entries and BH RLC channel mappings on the migrating node and the descendant nodes, and the BAP header rewriting entries on the migrating node, and acknowledges the modification via the IAB TRANSPORT MIGRATION MODIFICATION RESPONSE message. The target IAB-donor-CU may further provide updated TNL address information for the descendant IAB-node to the source IAB-donor-CU. The full or partial release or revoking of traffic offload pertaining to the descendant IAB-nodes and their served UEs follows the same procedure as defined for the partial migration in clause 8.17.3.1. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.17.3.2 |
5,551 | 5.20 Preallocated uplink grant | When the preallocated uplink grant is configured by RRC, the following information is provided in ul-ConfigInfo: - Uplink Scheduling interval ul-SchedInterval, starting subframe ul-StartSubframe of the preallocated uplink grant, the uplink grant ul-Grant and the number of HARQ process for the preallocated uplink grant numberOfConfUL-Processes. When the preallocated uplink grant configuration is released by RRC, the corresponding preallocated uplink grant shall be discarded. NOTE 1: When eIMTA is configured for the SpCell, if a preallocated grant occurs in a subframe that can be reconfigured through eIMTA L1 signalling, then the UE behaviour is left unspecified. If ul-ConfigInfo is configured, the MAC entity shall: - consider sequentially that the Nth grant occurs in the subframe for which: - subframe = [N * ul-SchedInterval + ul-StartSubframe] modulo 10. For TDD, the MAC entity is configured with ul-SchedInterval shorter than 10 subframes, the Nth grant shall be ignored if it occurs in a downlink subframe or a special subframe. NOTE 2: Retransmissions for uplink transmissions using the preallocated uplink grant can continue after clearing the preallocated uplink grant. | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.20 |
5,552 | 9.2.4.1A FDD (With interferenceMeasRestriction configured) | The following requirements apply to UE Category ≥2. For the parameters specified in table 9.2.4.1A-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.1A-1: PUCCH 1-1 static test (FDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.2.4.1A |
5,553 | 6.6.3K Spurious emission for Aerial UE | When "NS_UAV_70" is indicated in the cell, the power of any UE emission shall not exceed the levels specified in Table 6.6.3K-1. This requirement also applies for the frequency ranges that are less than FOOB (MHz) in Table 6.6.3.1-1 from the edge of the channel bandwidth. Table 6.6.3K-1: Additional requirements for "NS_UAV_70" When "NS_UAV_44" is indicated in the cell, the power of any UE emission shall not exceed the levels specified in Table 6.6.3K-2. This requirement also applies for the frequency ranges that are less than FOOB (MHz) in Table 6.6.3.1-1 from the edge of the channel bandwidth. Table 6.6.3K-2: Additional requirements for "NS_UAV_44" When "NS_UAV_46" is indicated in the cell, the power of any UE emission shall not exceed the levels specified in Table 6.6.3K-3. This requirement also applies for the frequency ranges that are less than FOOB (MHz) in Table 6.6.3.1-1 from the edge of the channel bandwidth. Table 6.6.3K-3: Additional requirements for "NS_UAV_46" | 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.3K |
5,554 | 9.9.1.2.1 FDD | The following requirements apply to UE Category ≥2. For the parameters specified in table 9.9.1.2.1-1, and using the downlink physical channels specified in tables C.3.2-1 and C.3.2-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.9.1.2.1-1: PUCCH 1-1 static test (FDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.9.1.2.1 |
5,555 | 13.3.4 Authentication and authorization between SEPPs | Authentication and authorization between SEPPs in different PLMNs is defined in clause 13.2. 13.3.5 Authentication between SEPP and SCP Authentication between SEPP and SCP within one PLMN shall use one of the following methods: - If the PLMN uses protection at the transport layer, authentication provided by the transport layer protection solution shall be used for authentication between SEPP and SCP. - If the PLMN does not use protection at the transport layer, authentication between SEPP and SCP within one PLMN may be implicit by NDS/IP or physical security (see clause 13.1). A SCP and the SEPP shall mutually authenticate before forwarding incoming or outgoing requests. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 13.3.4 |
5,556 | 6.10.2 Requirements | The following set of requirements complement the requirements listed in 3GPP TS 22.101[ Service aspects; Service principles ] [6], clause 29. Based on operator policy, a 5G network shall provide suitable APIs to allow a trusted third-party to create, modify, and delete network slices used for the third-party. Based on operator policy, the 5G network shall provide suitable APIs to allow a trusted third-party to monitor the network slice used for the third-party. Based on operator policy, the 5G network shall provide suitable APIs to allow a trusted third-party to define and update the set of services and capabilities supported in a network slice used for the third-party. Based on operator policy, the 5G network shall provide suitable APIs to allow a trusted third-party to configure the information which associates a UE to a network slice used for the third-party. Based on operator policy, the 5G network shall provide suitable APIs to allow a trusted third-party to configure the information which associates a service to a network slice used for the third-party. Based on operator policy, the 5G network shall provide suitable APIs to allow a trusted third-party to assign a UE to a network slice used for the third-party, to move a UE from one network slice used for the third-party to another network slice used for the third-party, and to remove a UE from a network slice used for the third-party based on subscription, UE capabilities, and services provided by the network slice. The 3GPP network shall be able to provide suitable and secure means to enable an authorized third-party to provide the 3GPP network via encrypted connection with the expected communication behaviour of UE(s). NOTE 1: The expected communication behaviour is, for instance, the application servers a UE is allowed to communicate with, the time a UE is allowed to communicate, or the allowed geographic area of a UE. The 3GPP network shall be able to provide suitable and secure means to enable an authorized third-party to provide via encrypted connection the 3GPP network with the actions expected from the 3GPP network when detecting behaviour that falls outside the expected communication behaviour. NOTE 2: Such actions can be, for instance, to terminate the UE's communication, to block the transferred data between the UE and the not allowed application. The 5G network shall be able to provide secure means for providing communication scheduling information (i.e. the time period the UE(s) will use a communication service) to an NPN via encrypted connection. This communication scheduling information is used by the 5G network to perform network energy saving and network resource optimization. The 5G network shall provide a mechanism to expose broadcasting capabilities to trusted third-party broadcasters' management systems. Based on operator policy, a 5G network shall provide suitable APIs to allow a trusted third-party to manage this trusted third-party owned application(s) in the operator's Service Hosting Environment. Based on operator policy, the 5G network shall provide suitable APIs to allow a third-party to monitor this trusted third-party owned application(s) in the operator's Service Hosting Environment. Based on operator policy, the 5G network shall provide suitable APIs to allow a trusted third-party to scale a network slice used for the third-party, i.e. to adapt its capacity. Based on operator policy, a 5G network shall provide suitable APIs to allow one type of traffic (from trusted third-party owned applications in the operator's Service Hosting Environment) to/from a UE to be offloaded to a Service Hosting Environment close to the UE's location. Based on operator policy, the 5G network shall provide suitable APIs to allow a trusted third-party application to request appropriate QoE from the network. Based on operator policy, the 5G network shall expose a suitable API to an authorized third-party to provide the information regarding the availability status of a geographic location that is associated with that third-party. Based on operator policy, the 5G network shall expose a suitable API to allow an authorized third-party to monitor the resource utilisation of the network service (radio access point and the transport network (front, backhaul)) that are associated with the third-party. Based on operator policy, the 5G network shall expose a suitable API to allow an authorized third-party to define and reconfigure the properties of the communication services offered to the third-party. The 5G system shall support the means for disengagement (tear down) of communication services by an authorized third-party. Based on operator policy, the 5G network shall expose a suitable API to provide the security logging information of UEs, for example, the active 3GPP security mechanisms (e.g. data privacy, authentication, integrity protection) to an authorized third-party. Based on operator policy, the 5G system shall provide suitable means to allow a trusted and authorized third-party to consult security related logging information for the network slices dedicated to that third-party. Based on operator policy, the 5G network shall be able to acknowledge within 100 ms a communication service request from an authorized third-party via a suitable API. The 5G network shall provide suitable APIs to allow a trusted third-party to monitor the status (e.g. locations, lifecycle, registration status) of its own UEs. NOTE 3: The number of UEs could be in the range from single digit to tens of thousands. The 5G network shall provide suitable APIs to allow a trusted third-party to get the network status information of a private slice dedicated for the third-party, e.g. the network communication status between the slice and a specific UE. The 5G system shall support APIs to allow the non-public network to be managed by the MNO's Operations System. The 5G system shall provide suitable APIs to allow third-party infrastructure (i.e. physical/virtual network entities at RAN/core level) to be used in a private slice. A 5G system shall provide suitable APIs to enable a third-party to manage its own non-public network and its private slice(s) in the PLMN in a combined manner. The 5G system shall support suitable APIs to allow an MNO to offer automatic configuration services (for instance, interference management) to non-public networks deployed by third parties and connected to the MNO's Operations System through standardized interfaces. The 5G system shall be able to: - provide a third-party with secure access to APIs (e.g. triggered by an application that is visible to the 5G system), by authenticating and authorizing both the third-party and the UE using the third-party's service. - provide a UE with secure access to APIs (e.g. triggered by an application that is not visible to the 5G system), by authenticating and authorizing the UE. - allow the UE to provide/revoke consent for information (e.g., location, presence) to be shared with the third-party. - preserve the confidentiality of the UE's external identity (e.g. MSISDN) against the third-party. - provide a third-party with information to identify networks and APIs on those networks. Based on operator policy, the 5G system shall provide means by which an MNO informs a third party of changes in UE subscription information. The 5G system shall also provide a means for an authorised third party to request this information at any time from the MNO. NOTE 4: Examples of UE subscription information include IP address, 5G LAN-VN membership, and configuration parameters for data network access. NOTE 5: These changes can have strong impacts in the stability of the third-party service. The 5G system shall provide a means by which an MNO can inform authorised 3rd parties of changes in the - RAT type that is serving a UE; - cell ID; - RAN quality of signal information; - assigned frequency band. This information listed above shall be provided with a suitable frequency via OAM and/or 5G core network. NOTE 6: The information aids the third party user to take proactive actions so that it can achieve high service availability in delivery of its services. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.10.2 |
5,557 | 10.5.6.3.11 PVS IPv6 Address | The purpose of the PVS IPv6 Address container contents is to indicate the PVS IPv6 Address and, optionally, the related DNN and S-NSSAI. The PVS IPv6 Address container contents are coded as shown in figure 10.5.6.3.11-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.6.3.11-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.6.3.11-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : PVS IPv6 Address Table 10.5.6.3.11-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : PVS IPv6 Address | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.6.3.11 |
5,558 | 6.1.3.8.2 Unsuccessful MBMS context activation requested by the MS 6.1.3.8.2.1 General | Upon receipt of an ACTIVATE MBMS CONTEXT REQUEST message the network may reject the MS initiated MBMS context activation by sending an ACTIVATE MBMS CONTEXT REJECT message to the MS. The sender of the message shall include the same TI as included in the ACTIVATE MBMS CONTEX REQUEST and an additional cause code that typically indicates one of the following causes: # 8: Operator Determined Barring; # 24: MBMS bearer capabilities insufficient for the service; # 26: insufficient resources; # 27: missing or unknown APN; # 29: user authentication failed; # 30: activation rejected by GGSN, Serving GW or PDN GW; # 31: activation rejected, unspecified; # 32: service option not supported; # 33: requested service option not subscribed; # 34: service option temporarily out of order; or # 95 - # 111: protocol errors. The network may include a Back-off timer value IE in the ACTIVATE MBMS CONTEXT REJECT message. If the Back-off timer value IE is included and the SM cause value is different from #26 "insufficient resources", the network may include the Re-attempt indicator IE to indicate whether the MS is allowed to attempt an MBMS context activation procedure in an equivalent PLMN. Upon receipt of an ACTIVATE MBMS CONTEXT REJECT message, the MS shall stop timer T3380 and enter/remain in state PDP-INACTIVE. | 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.8.2 |
5,559 | 5.8.2.16 Support for L2TP tunnelling on N6 | If requested by the SMF during N4 Session Establishment, the UPF (PSA) may setup L2TP towards an L2TP network server (LNS) in the DN and tunnel the PDU Session user plane traffic in this L2TP tunnel. In this case the UPF acts as a L2TP access concentrator (LAC). To enable this, the SMF may provide L2TP information to the UPF, such as LNS IP address and/or LNS host name, as described in TS 29.244[ Interface between the Control Plane and the User Plane nodes ] [65]. This L2TP information may be configured on the SMF as part of the DNN configuration or received from the DN-AAA Server during secondary authentication/authorization, as described in clause 5.6.6. Alternatively, the L2TP tunnel parameters may be configured in the UPF Function. The L2TP tunnel parameters include necessary parameters for setting up L2TP tunnel towards the LNS (e.g. LNS address, tunnel password, etc.). In addition, the SMF may provide PAP/CHAP authentication information to the UPF, for use in L2TP session establishment, in case it was received from the UE in the PDU Session Establishment Request. When L2TP is to be used for a PDU Session, the SMF may select a UPF based upon support of this feature. The SMF determines whether the UPF supports this feature via N4 capability negotiation during N4 Association Setup or via NRF discovery. If SMF requests the UPF to allocate UE IP address, as described in clause 5.8.2.2.1, the UPF (LAC) may retrieve this IP address from the LNS. In addition, if the SMF requests the UPF to provide DNS address(es), the UPF (LAC) may request the LNS to provide DNS address(es) and report such DNS address(es) to the SMF. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.8.2.16 |
5,560 | 5.15.11.5 Support of Network Slice Admission Control and Interworking with EPC | This clause describes the NSAC for maximum number of registered UEs and for maximum number of PDU Sessions for network slice subjected to EPS interworking. The NSAC for maximum number of UE with at least one PDU Session/PDN Connection is described in clause 5.15.11.5a. A network slice subject to both NSAC and EPS counting shall be configured with only one of the options: - Maximum number of registered UEs and/or maximum number of PDU Session; or - Maximum number of UEs with at least one PDU Session/PDN Connection and/or maximum number of PDU Session. If EPS counting is required for a network slice, the NSAC for maximum number of UEs and/or for maximum number of PDU Sessions per network slice is performed at the time of PDN connection establishment in case of EPC interworking. To support the NSAC for maximum number of UEs and/or for maximum number of PDU Sessions per network slice in EPC, the SMF+PGW-C is configured with the information indicating which network slice is subject to NSAC. During PDN connection establishment in EPC, the SMF+PGW-C selects an S-NSSAI associated with the PDN connection as described in clause 5.15.7.1. If the selected S-NSSAI by the SMF+PGW-C is subject to the NSAC, the SMF+PGW-C triggers interaction with NSACF to check the availability of the network slice by invoking separate NSAC procedures for number of UE and number of PDU Session (as described in clause 4.11.5.9 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]), before the SMF+PGW-C provides the selected S-NSSAI to the UE. If the network slice is available, the SMF+PGW-C continues to proceed with the PDN connection establishment procedure. The NSACF performs the following for checking network slice availability prior to returning a response to the SMF+PGW-C: - For NSAC for number of UEs, if the UE identity is already included in the list of UE IDs registered with a network slice, or the UE identity is not included in the list of UE IDs registered with a network slice and the current number of UE registration did not reach the maximum number, the NSACF responds to the SMF+PGW-C with the information that the network slice is available. The NSACF includes the UE identity in the list of UE IDs if not already on the list and increases the current number of UE registration. Otherwise, the NSACF returns a response indicating that the maximum number with the network slice has been reached. If hierarchical NSAC architecture is deployed, when the local maximum number or local threshold is reached the NSACF 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. - For NSAC for number of PDU Sessions, if the current number of PDU sessions is below the maximum number, the NSACF responds to the SMF+PGW-C with the information that the network slice is available. The NSACF increases the current number of PDU sessions. Otherwise, the NSACF returns the response indicating that the maximum number with the network slice has been reached. If hierarchical NSAC architecture is deployed, when the local maximum number is reached the NSACF 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.2.2. If the maximum number of UEs and/or the maximum number of PDU sessions has already been reached, unless operator policy implements a different action, the SMF+PGW-C rejects the PDN connection. NOTE 1: As an implementation option, if the APN is mapped to more than one S-NSSAI and the first selected S-NSSAI is not available (e.g. either current number of UE registration reached maximum or current number of PDU sessions reached maximum), then based on the operator policy the PGW-C+SMF can try another mapped S-NSSAI for the PDN connection establishment procedure. If the establishment of a new PDN Connections is with a different SMF+PGW-C from the SMF+PGW-C used for already existing PDN connection associated with the same S-NSSAI, each SMF+PGW-C will send a request for update (e.g. increase or decrease) to the NSACF. The NSACF may maintain a registration entry per SMF+PGW-C for the same UE ID. The SMF+PGW-C provides the Access Type to the NSACF when triggering a request to increase or decrease the number of UEs and/or the number of PDU Sessions for an S-NSSAI. NOTE 2: The SMF+PGW-C determines the Access Type based on the RAT type parameter in the PMIP or GTP message received from the ePDG; or alternatively it can internally determine the Access Type based on the source node (e.g. SGW) sending the request for the PDN Connection establishment. When the UE with ongoing PDN connection(s) moves from EPC to 5GC, the SMF+PGW-C triggers a request to decrease the number of the UE registration in NSACF and the AMF triggers a request to increase the number of the UE registration in NSACF when the UE is registered in the new AMF. If there are more than one PDN connections associated with the S-NSSAI, the NSACF may receive multiple requests for the same S-NSSAI from different SMF+PGW-Cs. When the UE with ongoing PDU session(s) moves from 5GC to EPC, the SMF+PGW-C triggers a request to increase the number of the UE registration in NSACF and the old AMF triggers a request to decrease the number of the UE registration in NSACF when the UE is deregistered in old AMF. If there are more than one PDU sessions associated with the S-NSSAI, the NSACF may receive multiple requests for the same S-NSSAI from different SMF+PGW-Cs. The NSACF maintains a list of UE IDs based on the requests from SMF+PGW-C(s) and AMF, and adjusts the current number of registrations accordingly. When EPS counting is performed for a network slice, and the UE with ongoing PDN connection(s) moves from EPC to 5GC, session continuity is guaranteed from NSAC standpoint, as the admission was granted at the time of PDN connection establishment, i.e. the number of PDU session is not counted again in 5GC. Similarly, when the UE with ongoing PDU session(s) moves from 5GC to EPC, session continuity is guaranteed from NSAC standpoint as the admission of the PDN Connection(s) to the network slice was already granted at the time of PDU Session establishment in 5GC. If the PDN connection associated with S-NSSAI is released in EPC, the SMF+PGW-C triggers a request (i.e. decrease) to NSACF for maximum number of UEs and/or maximum number of PDU sessions per network slice control. The NSACF decreases the current number of registrations and removes the UE identity from the list of UE IDs if the PDN connection(s) associated with the S-NSSAI are all released in EPC. NOTE 3: NSAC in EPC is not performed for the attachment without PDN connectivity. If EPS counting is not required for a network slice, the NSAC for maximum number of UEs and/or for maximum number of PDU Sessions per network slice is performed when the UE moves from EPC to 5GC, i.e. when the UE performs mobility Registration procedure from EPC to 5GC (NSAC for maximum number of UEs per network slice) and/or when the PDN connections are handed over from EPC to 5GC (NSAC for maximum number of PDU Sessions per network slice). The SMF+PGW-C is configured with the information indicating the network slice is subject to NSAC only in 5GS. The PDN connection interworking procedure is performed as described in clause 5.15.7.1. Mobility from EPC to 5GC does not guarantee all active PDU Session(s) can be transferred to the 5GC in certain circumstances when either the current number of UE registration or the current number of PDU sessions would exceed the maximum number when the UE moves from EPC to 5GC. When the UE with ongoing PDU session(s) moves from 5GC to EPC, the SMF+PGW-C triggers a request to decrease the number of PDU Session to NSACF. If there are more than one PDU sessions associated with the S-NSSAI, the NSACF may receive multiple requests for the same S-NSSAI from different SMF+PGW-Cs and NSACF removes the PDU Session ID(s) while decreasing the number of PDU Session(s). NOTE 4: Given that session continuity is not guaranteed when EPS counting is not required, it is recommended for services which require the session continuity to support EPS counting. NOTE 5: When multiple NSACFs are deployed and if the number of UE in target NSACF has reached the maximum number, whether session continuity can be guaranteed is left to implementation. NOTE 6: When a centralized architecture is deployed, UE admission is guaranteed at inter-system and inter-AMF mobility if the same NSACF is selected. This is the case for non-roaming scenarios and for roaming scenarios with HPLMN NSAC Admission Mode described in clause 5.15.11.3. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.15.11.5 |
5,561 | 8.3.2.4.5 Minimum requirements with different Cell ID and non-colliding CRS (with multiple NZP CSI-RS resources and CRS assistance information is configured) | The requirements are specified in Table 8.3.2.4.5-3, with the additional parameters in Tables 8.3.2.4.5-1 and 8.3.2.4.5-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 three transmission point have the different Cell ID and non-colliding CRS. In particular the test verifies that the UE, configured with quasi co-location type B, performs correct tracking and compensation of the frequency difference and 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]. Further, the test verifies that the UE, configured with the CRS assistance information [7], can mitigate interference from CRS for demodulation. The CRS assistance information [7] includes TP 3. In Tables 8.3.2.4.5-1 and 8.3.2.4.5-2, transmission point 1 (TP 1) is the serving cell transmitting PDCCH, synchronization signals and PBCH, Transmission point 2 (TP 2) has different Cell ID as TP 1, and Transmission point 3 (TP3) is the aggressor transmission point. Multiple NZP CSI-RS resources and ZP CSI-RS resources are configured. In each sub-frame, DL PDSCH transmission is dynamically switched between TP 1 and TP 2 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.5-2. The downlink physical channel setup for TP 1 is according to Table C.3.4-1, for TP 2 is according to Table C.3.4-2, and for TP 3 is according to Annex C.3.2 Table 8.3.2.4.5-1: Test Parameters for DPS transmission with CRS assistance information Table 8.3.2.4.5-2: Configurations of PQI and DL transmission hypothesis for each PQI set Table 8.3.2.4.5-3: Performance Requirements for DPS transmission with CRS assistance information | 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.5 |
5,562 | 6.15 UE parameters update via UDM control plane procedure security mechanism 6.15.1 General | This clause describes the security functions necessary to update the UE parameters using the UDM control plane procedure specified in TS 23.502[ Procedures for the 5G System (5GS) ] [8]. The security functions are described in the context of the functions supporting the delivery of UE Parameters Update Data from the UDM to the UE after the UE has successfully registered to the 5G network. If the control plane procedure for UE parameters update is supported by the UDM, the AUSF shall store the latest KAUSF after the completion of the latest primary authentication. The content of UE Parameters Update Data and the conditions for sending it to the UE as well as how it is handled at the UE are specified in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [35]. NOTE : The home network relies on the serving network to deliver the UE parameters update. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.15 |
5,563 | 4.23.12.2A 5GS to EPS Idle mode mobility using N26 interface with Data forwarding and I-SMF removal | For 5GS to EPS Idle mode mobility using N26 with data forwarding and I-SMF removal, the procedure "5GS to EPS Idle mode mobility using N26 interface with data forwarding" defined in clause 4.11.1.3.2A for the home-routed roaming case is re-used, with the following change: - The V-SMF is replaced by I-SMF, V-UPF is replaced by I-UPF and H-SMF is replaced by SMF. - Data forwarding tunnel resource is established and the tunnel information is exchanged through N26 interface. Data buffered in I-SMF/I-UPF is forwarded to UE via Serving GW. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.23.12.2A |
5,564 | 5.3.5.17.3 Configuration of N3C indirect path 5.3.5.17.3.1 General | For N3C indirect path, - the N3C remote UE is provided with N3C indirect path configuration including relay UE identification as specified in 5.3.5.17.3.2; - the N3C relay UE is provided with N3C indirect path configuration including bearer mapping configurations as specified in 5.3.5.17.3.4, as well as Uu Relay RLC channel configuration as specified in 5.3.5.5.12 and 5.3.5.5.13. NOTE: The data transmission/reception between the N3C remote UE and the N3C relay UE via the non-3GPP connection is outside the scope of 3GPP. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.5.17.3 |
5,565 | – PLMN-IdentityInfoList | The IE PLMN-IdentityInfoList includes a list of PLMN identity information. PLMN-IdentityInfoList information element -- ASN1START -- TAG-PLMN-IDENTITYINFOLIST-START PLMN-IdentityInfoList ::= SEQUENCE (SIZE (1..maxPLMN)) OF PLMN-IdentityInfo PLMN-IdentityInfo ::= SEQUENCE { plmn-IdentityList SEQUENCE (SIZE (1..maxPLMN)) OF PLMN-Identity, trackingAreaCode TrackingAreaCode OPTIONAL, -- Need R ranac RAN-AreaCode OPTIONAL, -- Need R cellIdentity CellIdentity, cellReservedForOperatorUse ENUMERATED {reserved, notReserved}, ..., [[ iab-Support-r16 ENUMERATED {true} OPTIONAL -- Need S ]], [[ trackingAreaList-r17 SEQUENCE (SIZE (1..maxTAC-r17)) OF TrackingAreaCode OPTIONAL, -- Need R gNB-ID-Length-r17 INTEGER (22..32) OPTIONAL -- Cond eventID-TSS ]], [[ mobileIAB-Support-r18 ENUMERATED {true} OPTIONAL -- Need S ]] } -- TAG-PLMN-IDENTITYINFOLIST-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,566 | 8.3.2.1H Single-layer Spatial Multiplexing (CRS assistance information is configured) | The requirements are specified in Table 8.3.2.1H-2, with the addition of parameters in Table 8.3.2.1H-1. The purpose is to verify the performance of the antenna ports 7 or 8 without a simultaneous transmission on the other antenna port in the serving cell with CRS assistance information. In Table 8.3.2.1H-1, Cell 1 is the serving cell, and Cell 2 and Cell 3 are the aggressor cells. The downlink physical channel setup for Cell 1, Cell 2 and Cell 3 is according to Annex C.3.2. The CRS assistance information [7] includes Cell 2 and Cell 3. Table 8.3.2.1H-1: Test parameters of TM9-Single-Layer (2 CSI-RS ports) Table 8.3.2.1H-2: Minimum Performance of TM9-Single-Layer (2 CSI-RS ports) | 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.1H |
5,567 | – SL-PreconfigurationNR | The IE SL-PreconfigurationNR includes the sidelink pre-configured parameters used for NR sidelink communication. Need codes or conditions specified for subfields in SL-PreconfigurationNR do not apply. SL-PreconfigurationNR information elements -- ASN1START -- TAG-SL-PRECONFIGURATIONNR-START SL-PreconfigurationNR-r16 ::= SEQUENCE { sidelinkPreconfigNR-r16 SidelinkPreconfigNR-r16, ... } SidelinkPreconfigNR-r16 ::= SEQUENCE { sl-PreconfigFreqInfoList-r16 SEQUENCE (SIZE (1..maxNrofFreqSL-r16)) OF SL-FreqConfigCommon-r16 OPTIONAL, sl-PreconfigNR-AnchorCarrierFreqList-r16 SL-NR-AnchorCarrierFreqList-r16 OPTIONAL, sl-PreconfigEUTRA-AnchorCarrierFreqList-r16 SL-EUTRA-AnchorCarrierFreqList-r16 OPTIONAL, sl-RadioBearerPreConfigList-r16 SEQUENCE (SIZE (1..maxNrofSLRB-r16)) OF SL-RadioBearerConfig-r16 OPTIONAL, sl-RLC-BearerPreConfigList-r16 SEQUENCE (SIZE (1..maxSL-LCID-r16)) OF SL-RLC-BearerConfig-r16 OPTIONAL, sl-MeasPreConfig-r16 SL-MeasConfigCommon-r16 OPTIONAL, sl-OffsetDFN-r16 INTEGER (1..1000) OPTIONAL, t400-r16 ENUMERATED{ms100, ms200, ms300, ms400, ms600, ms1000, ms1500, ms2000} OPTIONAL, sl-MaxNumConsecutiveDTX-r16 ENUMERATED {n1, n2, n3, n4, n6, n8, n16, n32} OPTIONAL, sl-SSB-PriorityNR-r16 INTEGER (1..8) OPTIONAL, sl-PreconfigGeneral-r16 SL-PreconfigGeneral-r16 OPTIONAL, sl-UE-SelectedPreConfig-r16 SL-UE-SelectedConfig-r16 OPTIONAL, sl-CSI-Acquisition-r16 ENUMERATED {enabled} OPTIONAL, sl-RoHC-Profiles-r16 SL-RoHC-Profiles-r16 OPTIONAL, sl-MaxCID-r16 INTEGER (1..16383) DEFAULT 15, ..., [[ sl-DRX-PreConfigGC-BC-r17 SL-DRX-ConfigGC-BC-r17 OPTIONAL, sl-TxProfileList-r17 SL-TxProfileList-r17 OPTIONAL, sl-PreconfigDiscConfig-r17 SL-RemoteUE-Config-r17 OPTIONAL ]], [[ sl-PreconfigFreqInfoListSizeExt-v1800 SEQUENCE (SIZE (1..maxNrofFreqSL-1-r18)) OF SL-FreqConfigCommon-r16 OPTIONAL, sl-RLC-BearerConfigListSizeExt-v1800 SEQUENCE (SIZE (1..maxSL-LCID-r16)) OF SL-RLC-BearerConfig-r16 OPTIONAL, sl-SyncFreqList-r18 SEQUENCE (SIZE (1..maxNrofFreqSL-r16)) OF SL-Freq-Id-r16 OPTIONAL, sl-SyncTxMultiFreq-r18 ENUMERATED {true} OPTIONAL, sl-PreconfigDiscConfig-v1800 SL-PreconfigDiscConfig-v1800 OPTIONAL ]] } SL-TxProfileList-r17 ::= SEQUENCE (SIZE (1..256)) OF SL-TxProfile-r17 SL-TxProfile-r17 ::= ENUMERATED {drx-Compatible, drx-Incompatible, spare6, spare5, spare4, spare3,spare2, spare1} SL-PreconfigGeneral-r16 ::= SEQUENCE { sl-TDD-Configuration-r16 TDD-UL-DL-ConfigCommon OPTIONAL, reservedBits-r16 BIT STRING (SIZE (2)) OPTIONAL, ... } SL-RoHC-Profiles-r16 ::= SEQUENCE { profile0x0001-r16 BOOLEAN, profile0x0002-r16 BOOLEAN, profile0x0003-r16 BOOLEAN, profile0x0004-r16 BOOLEAN, profile0x0006-r16 BOOLEAN, profile0x0101-r16 BOOLEAN, profile0x0102-r16 BOOLEAN, profile0x0103-r16 BOOLEAN, profile0x0104-r16 BOOLEAN } SL-PreconfigDiscConfig-v1800 ::= SEQUENCE { sl-RelayUE-PreconfigU2U-r18 SL-RelayUE-ConfigU2U-r18, sl-RemoteUE-PreconfigU2U-r18 SL-RemoteUE-ConfigU2U-r18 } -- TAG-SL-PRECONFIGURATIONNR-STOP -- ASN1STOP Editor's Note: The mapping configuration (from e2e SLRB to RLC channel) is needed in pre-configuration. The existing table format is used as a baseline, subject to discussion during maintenance. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,568 | 5.5.3.3a Derivation of layer 3 beam filtered measurement | The UE shall: 1> for each layer 3 beam filtered measurement quantity to be derived based on SS/PBCH block; 2> derive each configured beam measurement quantity based on SS/PBCH block as described in TS 38.215[ NR; Physical layer measurements ] [9], and apply layer 3 beam filtering as described in 5.5.3.2; 1> for each layer 3 beam filtered measurement quantity to be derived based on CSI-RS; 2> derive each configured beam measurement quantity based on CSI-RS as described in TS 38.215[ NR; Physical layer measurements ] [9], and apply layer 3 beam filtering as described in 5.5.3.2. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.5.3.3a |
5,569 | – SL-PBPS-CPS-Config | The IE SL-PBPS-CPS-Config specifies the operation information for a resource pool which can be (pre-)configured to enable full sensing only, partial sensing only, random resource selection only, or any combination(s) thereof. SL-PBPS-CPS-Config information element -- ASN1START -- TAG-SL-PBPS-CPS-CONFIG-START SL-PBPS-CPS-Config-r17 ::= SEQUENCE { sl-AllowedResourceSelectionConfig-r17 ENUMERATED {c1, c2, c3, c4, c5, c6, c7} OPTIONAL, -- Need M sl-MinNumCandidateSlotsPeriodic-r17 INTEGER (1..32) OPTIONAL, -- Need M sl-PBPS-OccasionReservePeriodList-r17 SEQUENCE (SIZE (1..16)) OF INTEGER (1..16) OPTIONAL, -- Need M sl-Additional-PBPS-Occasion-r17 ENUMERATED { monitored } OPTIONAL, -- Need M sl-CPS-WindowPeriodic-r17 INTEGER (5..30) OPTIONAL, -- Need M sl-MinNumCandidateSlotsAperiodic-r17 INTEGER (1..32) OPTIONAL, -- Need M sl-MinNumRssiMeasurementSlots-r17 INTEGER (1..800) OPTIONAL, -- Need M sl-DefaultCBR-RandomSelection-r17 INTEGER (0..100) OPTIONAL, -- Need M sl-DefaultCBR-PartialSensing-r17 INTEGER (0..100) OPTIONAL, -- Need M sl-CPS-WindowAperiodic-r17 INTEGER (0..30) OPTIONAL, -- Need M sl-PartialSensingInactiveTime-r17 ENUMERATED { enabled, disabled } OPTIONAL, -- Need M ... } -- TAG-SL-PBPS-CPS-CONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,570 | 5.25 Transmission of Downlink Channel Quality Report | The MAC entity of a BL UE or UE in enhanced coverage may be configured by upper layers to report DL channel quality in Msg3. DL channel quality in Msg3 in RRC_CONNECTED is not reported. If the UE is a BL UE or UE in enhanced coverage or an NB-IoT UE, a Downlink Channel Quality Report (DCQR) shall be triggered if any of the following events occur: - DCQR Command MAC control element is received, in which case the DCQR is referred below to as "Regular DCQR"; - for BL UE or UE in enhanced coverage, transmission of DCQR in Msg3 is configured by upper layers in mpdcch-CQI-Reporting, in which case DCQR is referred below to as "Msg3 DCQR". If any type of DCQR has been triggered: - start performing DL channel quality measurements according to TS 36.133[ Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for support of radio resource management ] [9]. If "Regular DCQR" has been triggered: - if an uplink grant has been received on the PDCCH for MAC entity's C-RNTI: - instruct the Multiplexing and Assembly procedure to generate a DCQR and AS RAI MAC control element as defined in clause 6.1.3.19; - cancel the triggered "Regular DCQR". If "Msg3 DCQR" has been triggered: - if an uplink grant has been received on the PDCCH for MAC entity's RA-RNTI: - if the allocated resources can accommodate a DCQR and AS RAI MAC control element plus its subheader as a result of logical channel prioritization: - instruct the Multiplexing and Assembly procedure to generate a DCQR and AS RAI MAC control element as defined in clause 6.1.3.19; - else if the uplink grant is not for EDT: - if configured by upper layers in mpdcch-CQI-Reporting, use R and F2 fields in the MAC PDU subheader, to transmit the measurement outcome, as defined in clause 6.2.1; - cancel the triggered "Msg3 DCQR". | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.25 |
5,571 | 6.2.4A.7 A-MPR for CA_NS_07 | If the UE is configured to CA_39C or any uplink inter-band CA configuration containing CA_39C and it receives IE CA_NS_07 the allowed maximum output power reduction applied to transmission on two component carriers for contiguously aggregated signals is specified in Table 6.2.4A.7-1. Table 6.2.4A.7-1: Contiguous Allocation A-MPR for CA_NS_07 If the UE is configured to CA_39C or any uplink inter-band CA configuration containing CA_39C and it receives IE CA_NS_07 the allowed maximum output power reduction applied to transmissions on two serving cells assigned to Band 39 with non-contiguous resource allocation is defined as follows A-MPR = CEIL {MA, 0.5} Where MA is defined as follows MA = -16. 25A + 21 ; 0 ≤ A < 0. 80 -2.50 A + 10.00 ; 0.80 ≤ A ≤ 1 Where A = NRB_alloc / NRB_agg | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.2.4A.7 |
5,572 | 5.8.2.18 QoS Flow related QoS monitoring and reporting | The SMF may configure the UPF to perform QoS monitoring for a QoS Flow and to report the monitoring results with the help of the following parameters provided in the Session Reporting Rule (SRR) described in clause 5.8.5.11: - QoS monitoring parameter(s) indicating the subject of the QoS monitoring as defined in clause 5.45; - Reporting period indicating the time interval in which a new measurement result and a potential report has to be available. Generally, if no measurement result is available to the UPF within the Reporting period, the UPF shall report a measurement failure; however, for some QoS monitoring parameters (e.g. congestion information, PDV and data rate), the measurement failure report is not applicable. - Reporting frequency indicating the type of the reporting as "periodic" or "event triggered": - If the Reporting frequency indicates "periodic", the UPF shall send a report each time the reporting period is over. - If the Reporting frequency indicates "event triggered", a Reporting threshold for each parameter in the QoS monitoring parameter(s) and a Minimum waiting time are provided as well. The UPF shall send a report when the measurement result matches or exceeds the indicated Reporting threshold. Subsequent reports shall not be sent by the UPF during the Minimum waiting time. If measurement results are received during the Minimum waiting time, the UPF shall report the minimum and the maximum measurement result when the Minimum waiting time is over. - (Optional) Target of the reporting and Indication of direct event notification indicating that the UPF shall send the reports to a different NF than the SMF (e.g. to the NEF/AF or the NWDAF/DCCF/MFAF). The NF is identified by a Notification Target Address and a Notification Correlation ID. The SMF can also indicate that the UPF shall send the reports to both, the NF indicated by the Target of reporting and to the SMF. If so, the UPF shall send the reports to the SMF as well. If the Indication of direct event notification is not provided, the UPF shall send the reports to the SMF. - (Optional) Reporting suggestion information as defined in clause 5.8.2.17 applicable to Target of the reporting to reduce the UPF performance impacts. - (Optional) Indication of QoS Flow associated with the default QoS Rule (see clause 4.15.4.5.1 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]). The UPF shall forward this indication, that the QoS monitoring report is for the QoS Flow associated with the default QoS Rule, in the Nupf_EventExposure_Notify service operation when sending reports. The UPF shall send the QoS Monitoring Report as follows: - when the UPF sends reports to the SMF, the UPF shall use QoS Monitoring Reports as described in clause 5.8.5.12; and/or - When the UPF sends reports to a different NF than the SMF (e.g. the NEF/AF or the NWDAF/DCCF/MFAF), the UPF shall use the Nupf_EventExposure_Notify service operation described in clause 5.2.26.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.8.2.18 |
5,573 | 9.2.5 Paging | Paging allows the network to reach UEs in RRC_IDLE and in RRC_INACTIVE state through Paging messages, and to notify UEs in RRC_IDLE, RRC_INACTIVE and RRC_CONNECTED state of system information change (see clause 7.3.3) and ETWS/CMAS indications (see clause 16.4) through Short Messages. Both Paging messages and Short Messages are addressed with P-RNTI on PDCCH, but while the former is sent on PCCH, the latter is sent over PDCCH directly (see clause 6.5 of TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12]). While in RRC_IDLE the UE monitors the paging channels for CN-initiated paging. While in RRC_INACTIVE with no ongoing SDT procedure (see clause 18.0) the UE monitors paging channels for RAN-initiated paging and CN-initiated paging. A UE need not monitor paging channels continuously though; Paging DRX is defined where the UE in RRC_IDLE or RRC_INACTIVE is only required to monitor paging channels during one Paging Occasion (PO) per DRX cycle (see TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [10]). The Paging DRX cycles are configured by the network: 1) For CN-initiated paging, a default cycle is broadcast in system information; 2) For CN-initiated paging, a UE specific cycle can be configured via NAS signalling; 3) For RAN-initiated paging, a UE-specific cycle is configured via RRC signalling; - The UE uses the shortest of the DRX cycles applicable i.e. a UE in RRC_IDLE uses the shortest of the first two cycles above, while a UE in RRC_INACTIVE uses the shortest of the three. The POs of a UE for CN-initiated and RAN-initiated paging are based on the same UE ID, resulting in overlapping POs for both. The number of different POs in a DRX cycle is configurable via system information and a network may distribute UEs to those POs based on their IDs. While in RRC_CONNECTED and while in RRC_INACTIVE with ongoing SDT procedure, the UE monitors the paging channels in any PO signalled in system information for SI change indication and PWS notification. In case of BA, a UE in RRC_CONNECTED only monitors paging channels on the active BWP with common search space configured. For operation with shared spectrum channel access, a UE can be configured for an additional number of PDCCH monitoring occasions in its PO to monitor for paging. However, when the UE detects a PDCCH transmission within the UE's PO addressed with P-RNTI, the UE is not required to monitor the subsequent PDCCH monitoring occasions within this PO. If Paging Cause is included in the Paging message, a UE in RRC_IDLE or RRC_INACTIVE state may use the Paging Cause as per TS 23.501[ System architecture for the 5G System (5GS) ] [3]. Paging optimization for UEs in CM_IDLE: at UE context release, the NG-RAN node may provide the AMF with a list of recommended cells and NG-RAN nodes as assistance info for subsequent paging. The AMF may also provide Paging Attempt Information consisting of a Paging Attempt Count and the Intended Number of Paging Attempts and may include the Next Paging Area Scope. If Paging Attempt Information is included in the Paging message, each paged NG-RAN node receives the same information during a paging attempt. The Paging Attempt Count shall be increased by one at each new paging attempt. The Next Paging Area Scope, when present, indicates whether the AMF plans to modify the paging area currently selected at next paging attempt. If the UE has changed its state to CM CONNECTED the Paging Attempt Count is reset. Paging optimization for UEs in RRC_INACTIVE: at RAN Paging, the serving NG-RAN node provides RAN Paging area information. The serving NG-RAN node may also provide RAN Paging attempt information. Each paged NG-RAN node receives the same RAN Paging attempt information during a paging attempt with the following content: Paging Attempt Count, the intended number of paging attempts and the Next Paging Area Scope. The Paging Attempt Count shall be increased by one at each new paging attempt. The Next Paging Area Scope, when present, indicates whether the serving NG_RAN node plans to modify the RAN Paging Area currently selected at next paging attempt. If the UE leaves RRC_INACTIVE state the Paging Attempt Count is reset. UE power saving for paging monitoring: in order to reduce UE power consumption due to false paging alarms, the group of UEs monitoring the same PO can be further divided into multiple subgroups. With subgrouping, a UE shall monitor PDCCH in its PO for paging if the subgroup to which the UE belongs is paged as indicated via associated PEI. If a UE cannot find its subgroup ID with the PEI configurations in a cell or if the UE is unable to monitor the associated PEI occasion corresponding to its PO, it shall monitor the paging in its PO. These subgroups have the following characteristics: - They are formed based on either CN controlled subgrouping or UE ID based subgrouping; - If CN controlled subgroup ID is not provided from AMF, UE ID based subgrouping is used if supported by the UE and network; - The RRC state (RRC_IDLE or RRC_INACTIVE state) does not impact which subgroup the UE belongs to; - Subgrouping support for a cell is broadcast in the system information as one of the following: Only CN controlled subgrouping supported, only UE ID based subgrouping supported, or both CN controlled subgrouping and UE ID based subgrouping supported; - Total number of subgroups allowed in a cell is up to 8 and represents the sum of CN controlled and UE ID based subgrouping configured by the network; - A UE configured with CN controlled subgroup ID applies CN controlled subgroup ID if the cell supports CN controlled subgrouping; otherwise, it derives UE ID based subgroup ID if the cell supports only UE ID based subgrouping. PEI associated with subgroups has the following characteristics: - If the PEI is supported by the UE, it shall at least support UE ID based subgrouping method; - PEI monitoring can be limited via system information to the last used cell (i.e., the cell in which the UE most recently received RRCRelease without indicating that the last used cell for PEI shall not be updated); - A PEI-capable UE shall store its last used cell information; - gNBs supporting the PEI monitoring to the last used cell function provide the UE's last used cell information to the AMF in the NG-AP UE Context Release Complete message for PEI capable UEs, as described in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [26]; - UE that expects MBS group notification shall ignore the PEI and shall monitor paging in its PO. CN controlled subgrouping: For CN controlled subgrouping, AMF is responsible for assigning subgroup ID to the UE. The total number of subgroups for CN controlled subgrouping which can be configured, e.g. by OAM is up to 8. It is assumed that CN controlled subgrouping support is homogeneous within an RNA. The following figure describes the procedure for CN controlled subgrouping: Figure 9.2.5-1: Procedure for CN controlled subgrouping 1. The UE indicates its support of CN controlled subgrouping via NAS signalling. 2. If the UE supports CN controlled subgrouping, the AMF determines the subgroup ID assignment for the UE. 3. The AMF sends subgroup ID to the UE via NAS signalling. 4. The AMF informs the gNB about the CN assigned subgroup ID for paging the UE in RRC_IDLE/ RRC_INACTIVE state. 5. When the paging message for the UE is received from the CN or is generated by the gNB, the gNB determines the PO and the associated PEI occasion for the UE. 6. Before the UE is paged in the PO, the gNB transmits the associated PEI and indicates the corresponding CN controlled subgroup of the UE that is to be paged in the PEI. UE ID based subgrouping: For UE ID based subgrouping, the gNB and UE can determine the subgroup ID based on the UE ID and the total number of subgroups for UE ID based subgrouping in the cell. The total number of subgroups for UE ID based subgrouping is decided by the gNB for each cell and can be different in different cells. The following figure describes the procedure for UE ID based subgrouping: Figure 9.2.5-2: Procedure for UE ID based subgrouping 1. The gNB determines the total number of subgroups for UE ID based subgrouping in a cell. 2. The gNB broadcasts the total number of subgroups for UE ID based subgrouping in a cell. 3. UE determines its subgroup in a cell. 4. When paging message for the PEI capable UE is received from the CN at the gNB or is generated by the gNB, the gNB determines the PO and the associated PEI occasion for the UE. 5. Before the UE is paged in the PO, the gNB transmits the associated PEI and indicates the corresponding subgroup derived based on UE ID of the UE that is paged in the PEI. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 9.2.5 |
5,574 | D.7.2 UE initiated QoS | When UE is accessing an overlay network via an underlay network as described in clause D.3, if UE-initiated QoS modification in clause 5.30.2.7 and clause 5.30.2.8 is used, the following principles can be considered to enable consistent QoS for User Plane IPsec Child SAs between the two networks: - UE registers and establishes PDU Session in the overlay network via the User Plane connectivity established in the underlay network. When UE is accessing a specific service of overlay network, a QoS Flow in overlay network can be created according to clause 4.3.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. UE receives the QoS Flow level QoS parameters (e.g. 5QI, GFBR, MFBR, as specified in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]) from SMF/PCF in overlay network for the QoS Flow which is created for the specific overlay network service. - N3IWF in overlay network creates dedicated User Plane IPsec Child SA for each overlay network QoS Flow that requires underlay network QoS support. - In order to ensure the traffic of the overlay network service is handled with the desired QoS in underlay network, UE can request new QoS Flow for the PDU session in the underlay network, by PDU Session Modification procedure described in clause 4.3.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. The requested QoS can be derived from the QoS Flow level QoS parameters which the UE has received from the overlay network. The Packet Filter in the QoS rule of the request includes overlay network N3IWF IP address and SPI associated with the User Plane IPsec Child SA. - SMF in the underlay network notifies the PCF that the UE has initiated resource modification, after receiving the PDU Session Modification Request. PCF in the underlay network determines if the request can be authorized based on UE subscription and local policy which can take into account the SLA between overlay network and underlay network. If the request is authorized, PCF generates new PCC rule and installs on SMF in order to create new QoS Flow in underlay network using the QoS Flow level QoS parameters from the overlay network. The PDR/FAR generated refers to the N3IWF IP address and the SPI (provided by the UE in Traffic filter in PDU Session Modification request) to enable filtering and mapping of DL traffic towards the right PDU Session/QoS Flow within the underlay network. - If SLA exists, it can include a mapping between the DSCP values of the User Plane IPsec Child SAs and the QoS requirement of the overlay network services. The SLA is configured at N3IWF in overlay network and at SMF/PCF in underlay network. N3IWF can provide DSCP value to UE for the User Plane IPsec Child SA at PDU Session Establishment (clause 4.12.5, step 4a and 4c of TS 23.502[ Procedures for the 5G System (5GS) ] [3]). UE can include the DSCP value as an addition in the Packet Filter by initiating the PDU Session Modification procedure in the underlay network. PCF in the underlay network performs QoS authorization of UE QoS request considering the UE subscription and local configuration which takes into account the mapping in the SLA. Details of the mapping between DSCP values of the User Plane IPSec Child SAs and QoS requirement of the overlay network services is described in TS 29.513[ 5G System; Policy and Charging Control signalling flows and QoS parameter mapping; Stage 3 ] [133]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | D.7.2 |
5,575 | 8.3.1.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.3.1.1-1 and 8.3.1.1-2, with the addition of the parameters in Table 8.3.1.1-3 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 with and without a simultaneous transmission on the other antenna port, and to verify rate matching with multiple CSI reference symbol configurations with non-zero and zero transmission power. Table 8.3.1.1-1: Test Parameters for Testing CDM-multiplexed DM RS (single layer) with multiple CSI-RS configurations Table 8.3.1.1-2: Minimum performance for CDM-multiplexed DM RS without simultaneous transmission (FRC) with multiple CSI-RS configurations Table 8.3.1.1-3: Minimum performance for CDM-multiplexed DM RS with interfering simultaneous transmission (FRC) with multiple CSI-RS configurations | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.3.1.1 |
5,576 | 5.7.15 Void | 5.7.16 Application layer measurement reporting 5.7.16.1 General Figure 5.7.16.1-1: Application layer measurement reporting The purpose of this procedure is to send application layer measurement reports to the network. 5.7.16.2 Initiation A UE capable of application layer measurement reporting in RRC_CONNECTED may initiate the procedure when configured with application layer measurement, i.e. when appLayerMeasConfig and SRB4 and/or SRB5 have been configured by the network. Upon initiating the procedure, the UE shall: 1> for each measConfigAppLayerId received from upper layers: 2> if the UE AS has received application layer measurement report container from upper layers which has not been transmitted; and 2> if the application layer measurement reporting has not been suspended for the measConfigAppLayerId associated with the application layer measurement report container according to clause 5.3.5.13d: 3> set the measReportAppLayerContainer in the MeasurementReportAppLayer message to the received value in the application layer measurement report container; 2> set the measConfigAppLayerId in the MeasurementReportAppLayer message to the value of the measConfigAppLayerId received together with application layer measurement report information; 2> if session start or stop information has been received from upper layers for the measConfigAppLayerId: 3> set the appLayerSessionStatus in the MeasurementReportAppLayer message to the received value of session start or stop information; 2> if reportingSRB and ran-VisibleReportingSRB are different for the measConfigAppLayerId: 3> include measReportAppLayerContainer and appLayerSessionStatus in a different MeasurementReportAppLayer message than ran-VisibleMeasurements; 2> if RAN visible application layer measurement report has been received from upper layers: 3> for each appLayerBufferLevel value in the received RAN visible application layer measurement report: 4> set the appLayerBufferLevel values in the appLayerBufferLevelList in the MeasurementReportAppLayer message to the buffer level values received from the upper layer in the order with the first appLayerBufferLevel value set to the newest received buffer level value, the second appLayerBufferLevel value set to the second newest received buffer level value, and so on until all the buffer level values received from the upper layer have been assigned or the maximum number of values have been set according to appLayerBufferLevel, if configured; 3> set the playoutDelayForMediaStartup in the MeasurementReportAppLayer message to the received value of playout delay for media startup in the RAN visible application layer measurement report, if any; 3> for each PDU session ID value indicated in the received RAN visible application layer measurement report, if any: 4> set the PDU-SessionID in the pdu-SessionIdList in the MeasurementReportAppLayer message to the indicated PDU session ID value; 4> for each QoS Flow ID value indicated in the received RAN visible application layer measurement report associated with the PDU Session ID, if any: 5> set the QFI associated with the PDU session ID to the indicated QoS Flow ID value. 1> for each stored application layer measurement configuration with configforRRC-IdleInactive set to true and for which appLayerIdleInactiveConfig has not been transmitted since the UE entered RRC_CONNECTED: 2> set the parameters in appLayerIdleInactiveConfig in the MeasurementReportAppLayer message to the values stored in the UE variable VarAppLayerIdleConfig; 1> for each encoded MeasurementReportAppLayer message generated above: 2> if reportingSRB or ran-VisibleReportingSRB are not configured: 3> if the encoded RRC message is larger than the maximum supported size of one PDCP SDU specified in TS 38.323[ NR; Packet Data Convergence Protocol (PDCP) specification ] [5]: 4> if the RRC message segmentation is enabled based on the field rrc-SegAllowed received in appLayerMeasConfig: 5> initiate the UL message segment transfer procedure as specified in clause 5.7.7; 4> else: 5> discard the RRC message; 3> else: 4> submit the MeasurementReportAppLayer message to lower layers for transmission. 2> else if reportingSRB or ran-VisibleReportingSRB are configured: 3> if the encoded RRC message is larger than the maximum supported size of one PDCP SDU specified in TS 38.323[ NR; Packet Data Convergence Protocol (PDCP) specification ] [5]: 4> if the RRC message segmentation is enabled based on the field rrc-SegAllowedSRB4 received in appLayerMeasConfig and the reportingSRB is SRB4; or 4> if the RRC message segmentation is enabled based on the field rrc-SegAllowedSRB5 received in appLayerMeasConfig and the reportingSRB is SRB5: 5> initiate the UL message segment transfer procedure as specified in clause 5.7.7 via the SRB indicated in the field reportingSRB in MeasConfigAppLayer; 4> else: 5> discard the RRC message; 3> else: 4> submit the MeasurementReportAppLayer message to lower layers for transmission via the SRB indicated in the field reportingSRB or, if different from reportingSRB, ran-VisibleReportingSRB in MeasConfigAppLayer upon which the procedure ends. Editor's Note: FFS on if it needs to be specified what the UE transmits when returning to RRC_CONNECTED. NOTE 1: If the SRB indicated by reportingSRB is not available, the UE may store application layer measurement report containers until the SRB is available. The UE may discard reports when the memory reserved for storing application layer measurement report containers becomes full. Reports with lower appLayerMeasPriority are discarded first. If no appLayerMeasPriority is configured, older reports may be discarded first. NOTE 2: If the SRB indicated by ran-VisibleReportingSRB is not available, the UE discards RAN visible application layer measurement reports. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.7.15 |
5,577 | 5.2.7.2.2 Nnrf_NFManagement_NFRegister service operation | Service Operation name: Nnrf_NFManagement_NFRegister. Description: Registers the consumer NF in the NRF by providing the NF profile of the consumer NF to NRF and NRF marks the consumer NF available. Inputs, Required: NF type, NF instance ID, FQDN or IP address of NF, Names of supported NF services (if applicable) and PLMN ID e.g. if NF needs to be discovered by other PLMNs/SNPNs. NOTE 1: for the UPF, the addressing information within the NF profile corresponds to the N4 interface. NOTE 2: For the purpose of the Nnrf_NFManagement service, the SCP is treated by the NRF in the same way as NFs. Specifically, the SCP is designated with a specific NF type and NF instance ID. However, the SCP does not support services and related NF profile parameters do not apply (e.g. NF Set ID, NF service set ID, Endpoint Address(es) of instance(s) of supported service(s)), see clause 6.2.6.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. Inputs, Optional: - If the consumer NF stores Data Set(s) (e.g. UDR): Range(s) of SUPIs, range(s) of GPSIs, range(s) of external group identifiers, Data Set Identifier(s). - If the consumer is BSF: Range(s) of SUPIs, range(s) of GPSIs, Range(s) of (UE) IPv4 addresses or Range(s) of (UE) IPv6 prefixes, IP domain list as described in clause 6.1.6.2.21 of TS 29.510[ 5G System; Network function repository services; Stage 3 ] [37], Range(s) of SUPIs, range(s) of GPSIs. NOTE 3: Range of SUPI(s) is limited in this release to a SUPI type of IMSI as defined in TS 23.003[ Numbering, addressing and identification ] [33]. - If the consumer is UDM, UDR, PCF, BSF or AUSF, they can include UDM Group ID, UDR Group ID, PCF Group ID, BSF Group ID, AUSF Group ID respectively. - For UDM and AUSF, Routing Indicator, or Routing Indicator and Home Network Public Key identifier; Home Network Identifier: PLMN ID in the case of PLMN, PLMN ID + NID in the case of SNPN. Optionally, some NFs may additionally include a Home Network Identifier (including the identification of the CH with AAA Server or DCS with AAA Server) in the form of a realm e.g. in the case of access to an SNPN using credentials owned by CH with AAA Server or in the case of SNPN Onboarding using a DCS with AAA Server. - For NSSAAF, Home Network Identifier in the form of a realm e.g. in the case of access to an SNPN using credentials owned by CH with AAA Server or in the case of SNPN Onboarding using credentials from a DCS with AAA Server. - If the consumer is AMF, it includes list of GUAMI(s). In addition, AMF may include list of GUAMI(s) for which it can serve as backup for failure/maintenance. - If the consumer is CHF, it may include Range(s) of SUPIs, Range(s) of GPSIs, or Range(s) of PLMNs as defined in TS 32.290[ Telecommunication management; Charging management; 5G system; Services, operations and procedures of charging using Service Based Interface (SBI) ] [42]. - If the consumer is CHF, primary CHF instance and the secondary CHF instance pair. If the CHF does not provide NF set ID or NF Service Set ID, it shall provide a primary CHF instance and the secondary CHF instance pair and otherwise it may do so. - If the consumer is P-CSCF, the P-CSCF IP address(es) to be provided to the UE by SMF. - If the consumer is HSS, IMPI range, IMPU range, HSS Group ID (as defined in TS 23.228[ IP Multimedia Subsystem (IMS); Stage 2 ] [55]) can be used as optional input parameters. - For the UPF Management: UPF Provisioning Information as defined in clause 4.17.6. - S-NSSAI(s) and the associated NSI ID(s) (if available). - DNN(s) if the consumer is PCF or BSF. DNN(s) per S-NSSAI if the consumer is SMF, UPF or TSCTSF. - If the consumer is a trusted AF it may include one or multiple combination(s) of S-NSSAI and DNN corresponding to the AF. In addition, it may include supported Application Id(s), Event ID(s) and Internal-Group Identifier. It may include an indication whether it supports mapping between UE IP address (IPv4 address or IPv6 prefix) and UE ID (i.e. SUPI). - Information about the location of the NF consumer (operator specific information, e.g. geographical location, data centre). - TAI(s). - NF Set ID. - NF Service Set ID. - If the consumer is PCF or SMF, it includes the MA PDU Session capability to indicate if the NF instance supports MA PDU session or not. - If the consumer is PCF, it includes the DNN replacement capability to indicate if the NF instance supports DNN replacement or not. - If the consumer is PCF or SMF, it includes the slice replacement capability to indicate if the NF instance supports slice replacement or not. - If the consumer is PCF, it may include the 5G ProSe Capability as specified in TS 23.304[ Proximity based Services (ProSe) in the 5G System (5GS) ] [77]. - If the consumer is PCF, it may include the V2X capability as specified in TS 23.287[ Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services ] [73]. - If the consumer is PCF, it may include the A2X capability as specified in TS 23.256[ Support of Uncrewed Aerial Systems (UAS) connectivity, identification and tracking; Stage 2 ] [80]. - If the consumer is PCF, it may include the indication of PCF support of URSP delivery in EPS. - If the consumer is PCF, it may include the indication of PCF support of VPLMN specific rules. - If the consumer is PCF, it may include the indication of PCF support of URSP rule enforcement. - If the consumer is NWDAF, it may include: - Analytics ID(s) (possibly per service). - NWDAF Serving Area information and Supported Analytics Delay per Analytics ID(s) (if available). - Analytics aggregation capability and/ or Analytics metadata provisioning capability if such capability is provided by the NWDAF. - Roaming exchange capability if such capability is provided by NWDAF. - If the consumer NWDAF contains MTLF, it may also include the ML model Filter information parameters S-NSSAI(s) and Area(s) of Interest for the trained ML model(s) per Analytics ID(s) and ML Model Interoperability indicator per Analytics ID(s), if available (see clause 5.2 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]). - If the consumer is NWDAF containing MTLF with Federated Learning (FL) capability, it includes FL capability information per analytics ID containing FL capability type (i.e. FL client, FL server, if available) and Time interval supporting FL, if available (see clause 5.2 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]). - If the consumer is NWDAF containing MTLF with ML Model Accuracy checking capability, it includes ML Model Accuracy checking capability for ML model accuracy monitoring (see clause 5.2 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]). - If the consumer is NWDAF containing AnLF with Analytics Accuracy checking capability, it includes Analytics Accuracy checking capability for Analytics Accuracy Monitoring (see clause 5.2 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]). - It may also include NF Set ID and NF Type of the NF data sources, if data management service is available. Details about NWDAF specific information are described in clause 6.3.13 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. - If the consumer is ADRF, it may include: - Data and analytics storage and retrieval capability if available. - ML model storage and retrieval capability if available. Details about ADRF specific information are described in clause 6.3.20 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. - If the consumer is NEF, it may include Event ID(s) supported by AFs, the S-NSSAI and DNN corresponding to the untrusted AF served by the NEF, Application Identifier(s) supported by AFs, range(s) of External Identifiers, or range(s) of External Group Identifiers, or the domain names served by the NEF. It may also include an indication whether the untrusted AF supports mapping between UE IP address (IPv4 address or IPv6 prefix) and external UE ID (i.e. GPSI). If the consumer is local NEF, it may include parameters of list of supported TAI or list of supported DNAI additionally. - If the consumer is a NSACF, it includes the S-NSSAI(s) of the PLMN or SNPN where the NSACF is located, the NSAC Service Area Identifier(s) n and NSACF service capabilities. Details about NSAC Service Area Identifier and NSACF service capabilities are described in clause 6.3.22 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. - Notification endpoint for default subscription for each type of notification that the NF is interested in receiving. - Endpoint Address(es) of instance(s) of supported service(s). - NF capacity information. - NF priority information. - If consumer is NF, SCP domain the NF belongs to. - If the consumer is SCP, it may include: - SCP domain(s) the SCP belongs to. - Remote PLMNs reachable through SCP. - Endpoint addresses or Address Domain(s) (e.g. IP Address or FQDN ranges) accessible via the SCP. - NF sets of NFs served by the SCP. - If the consumer NF is MB-SMF, it may include MB-SMF service area and the MBS Session ID(s), Area Session ID(s), the corresponding MBS service area(s) if available, as specified in TS 23.247[ Architectural enhancements for 5G multicast-broadcast services ] [78]. - If the consumer is DCCF, the request may include DCCF Serving Area information, NF type of the NF data source, NF Set ID of the NF data sources, support for relocation of data subscription. Details about DCCF discovery and selection are described in clause 6.3.19 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. - If the consumer is EASDF, it may include S-NSSAI, DNN, N6 IP address of the PSA UPF, location as per NF profile and DNAI (if exists). - For ON-SNPN, if the consumer is AMF, Capability to support SNPN Onboarding, or, if the consumer is SMF, Capability to support User Plane Remote Provisioning. - If the consumer is NEF, it may include the support for UAS NF functionality, the capability to support Multi-member AF session with required QoS and the capability to support member UE selection assistance functionality. - If the consumer is UPF and UPF can expose NAT information, it may include the range of IP addresses the NAT uses towards the DN (e.g. public IP addresses). This IP address range may be on a per IP domain, DNN and S-NSSAI. - If the consumer is DCSF, it may include an IMS domain name or a list of IMS domain names it serves, IMPU range of calling identity or called identity it serves, or IMPI range it serves. - If the consumer is MF, it includes the data channel media capabilities it supports. It may also include MF location information as specified in TS 23.228[ IP Multimedia Subsystem (IMS); Stage 2 ] [55]. - If the consumer is MRF or MRFP, it includes the list of supported IMS media services (as defined in TS 23.228[ IP Multimedia Subsystem (IMS); Stage 2 ] [55]). Outputs, Required: Result indication. Outputs, Optional: None. See clause 5.21.2.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], the AMF registers itself to NRF. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.7.2.2 |
5,578 | 4.23.12.8.6 Xn based handover with insertion of I-SMF | The following impact is applicable Xn based handover with insertion of I-SMF in clause 4.23.11.2: - In step 6, at I-SMF insertion, if EBI(s) have been allocated before but the SMF+PGW-C has not prepared the CN Tunnel Info for each EPS bearer, the SMF+PGW-C requests the PGW-U+UPF to allocate the CN Tunnel for each EPS bearer for PDU Session(s). PGW-U+UPF allocates the PGW-U tunnel info for the EPS bearer and sends it to the SMF+PGW-C. - In step 9, the SMF+PGW-C provides also the CN Tunnel Info for each EPS bearer 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.8.6 |
5,579 | 6.1.3 Information Element instance | Every GTPv2 message and grouped IE within a message in this specification has a column documenting the instance value of each IE. When a GTPv2 message is encoded for use the instance value of each included IE is encoded in the Instance field of the IE for the message scope. See clause 7 and clause 8.2 for details of that encoding. An Information Element in an encoded GTPv2 message or encoded grouped IE is identified by the pair of IE Type and Instance values and described by a specific row in the corresponding tables in clauses of 7 in the present document. If several Information Elements with the same Type and Instance values are included in an encoded GTPv2 message, they represent a list for the corresponding IE name and row identified in the message grammar in clauses of clause 7. If several Information Elements with the same Type and Instance values are included in an encoded grouped IE, they represent a list for the corresponding IE name and row identified in the grouped IE grammar in clauses of clause 7. In tables in this document the instance value for "Private Extension" is marked as VS (Vendor Specific). While an instance value must be encoded by the sender the value can be Vendor and even Private Extension specific. The same IE name might be used in different messages (on the top level or within grouped IEs) in this specification. The instance value and name of an IE is only meaningful within the scope of the message definition . The combination of Type value and Instance value uniquely identifies a specific row in a message description table. | 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 | 6.1.3 |
5,580 | 4.6.2.5 Mobility management based network slice admission control | A serving PLMN or SNPN can perform network slice admission control for the S-NSSAI(s) subject to NSAC to monitor and control the number of registered UEs per network slice. The timing of the network slice admission control is managed by the EAC mode per network slice, which can be either activated or deactivated for the network performing network slice admission control. The EAC mode is activated when the number of UEs associated with the S-NSSAI reaches a certain threshold (see 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9]) If the EAC mode is activated for an S-NSSAI, the AMF performs network slice admission control before the S-NSSAI subject to NSAC is included in the allowed NSSAI or the partially allowed NSSAI sent to the UE. During a registration procedure (including initial registration or mobility registration updating from another AMF), if the AMF determines that the maximum number of UEs has been reached for: a) one or more S-NSSAIs but not all S-NSSAIs in the requested NSSAI, then the AMF includes the allowed NSSAI or the partially allowed NSSAI and the rejected NSSAI accordingly in the REGISTRATION ACCEPT message as specified in the subclauses 5.5.1.2.4 and 5.5.1.3.4; b) all S-NSSAIs in the requested NSSAI but there are one or more default S-NSSAIs which can be allowed to the UE, then the AMF includes the allowed NSSAI or the partially allowed NSSAI containing these default S-NSSAIs and the rejected NSSAI accordingly in the REGISTRATION ACCEPT message as specified in the subclauses 5.5.1.2.4 and 5.5.1.3.4; or c) all S-NSSAIs in the requested NSSAI and there are no default S-NSSAIs which can be allowed to the UE, then the AMF includes the rejected NSSAI accordingly in the REGISTRATION REJECT message as specified in the subclauses 5.5.1.2.5 and 5.5.1.3.5. If the EAC mode is deactivated for an S-NSSAI, the AMF performs network slice admission control after the S-NSSAI subject to NSAC is included in the allowed NSSAI or the partially allowed NSSAI sent to the UE. While the AMF is waiting for response from the NSACF for the S-NSSAI, the AMF processes the NAS signalling message related to the S-NSSAI as usual i.e. like S-NSSAI in the allowed NSSAI or the partially allowed NSSAI. After the network performs the network slice admission control, if the AMF determines that the maximum number of UEs has been reached for: a) one or more S-NSSAIs but not all S-NSSAIs in the allowed NSSAI or the partially allowed NSSAI, then the AMF updates the allowed NSSAI or the partially allowed NSSAI and the rejected NSSAI accordingly using the generic UE configuration update procedure as specified in the subclause 5.4.4; b) for all S-NSSAIs in the allowed NSSAI or the partially allowed NSSAI but there are one or more default S-NSSAIs which can be allowed to the UE, then the AMF updates the allowed NSSAI or the partially allowed NSSAI containing these default S-NSSAIs and the rejected NSSAI accordingly using the generic UE configuration update procedure as specified in the subclause 5.4.4; or c) for all S-NSSAIs in the allowed NSSAI or the partially allowed NSSAI and there are no default S-NSSAIs which can be allowed to the UE, then the AMF performs the network-initiated de-registration procedure and includes the rejected NSSAI in the DEREGISTRATION REQUEST message as specified in the subclause 5.5.2.3 except when the UE has an emergency PDU session established or the UE is establishing an emergency PDU session. When the UE has an emergency PDU session established or the UE is establishing an emergency PDU session, the AMF updates the rejected NSSAI using the generic UE configuration update procedure as specified in the subclause 5.4.4 and informs the SMF to release all PDU sessions associated with the S-NSSAI. During the generic UE configuration update procedure, the AMF includes the 5GS registration result IE in the CONFIGURATION UPDATE COMMAND message and sets the Emergency registered bit of the 5GS registration result IE to "Registered for emergency services". After the emergency PDU session is released, the AMF performs the network-initiated de-registration procedure as specified in the subclause 5.5.2.3. Based on operator policy, the mobility management based network slice admission control is not applicable for the S-NSSAI used for emergency services, or the mobility management based network slice admission control result is ignored for the S-NSSAI used for emergency services. Based on operator policy, the mobility management based network slice admission control is not applicable for the UEs configured for priority services, or the mobility management based network slice admission control result is ignored for the UEs configured for priority services. NOTE: A UE configured for priority services can be identified based on the RRC establishment cause received from the NG-RAN or based on the MPS priority information in the user's subscription context obtained from the UDM. The mobility management based network slice admission control is not applicable to a UE that is registering or registered for onboarding services in SNPN. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.6.2.5 |
5,581 | 2.4 Structure of TMSI | Since the TMSI has only local significance (i.e. within a VLR and the area controlled by a VLR, or within an SGSN and the area controlled by an SGSN, or within an MME and the area controlled by an MME), the structure and coding of it can be chosen by agreement between operator and manufacturer in order to meet local needs. The TMSI consists of 4 octets. It can be coded using a full hexadecimal representation. In order to avoid double allocation of TMSIs after a restart of an allocating node, some part of the TMSI may be related to the time when it was allocated or contain a bit field which is changed when the allocating node has recovered from the restart. In areas where both MSC-based services and SGSN-based services are provided, some discrimination is needed between the allocation of TMSIs for MSC-based services and the allocation of TMSIs for SGSN-based services. The discrimination shall be done on the 2 most significant bits, with values 00, 01, and 10 being used by the VLR, and 11 being used by the SGSN. If intra domain connection of RAN nodes to multiple CN nodes as described in 3GPP TS 23.236[ Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes ] [23] is applied in the MSC/VLR or SGSN, then the NRI shall be part of the TMSI. The NRI has a configurable length of 0 to 10 bits. A configurable length of 0 bits indicates that the NRI is not used and this feature is not applied in the MSC/VLR or SGSN. The NRI shall be coded in bits 23 to 14. An NRI shorter than 10 bits shall be encoded with the most significant bit of the NRI field in bit 23. The TMSI shall be allocated only in ciphered form. See also 3GPP TS 43.020[ Security related network functions ] [7] and 3GPP TS 33.102[ 3G security; Security architecture ] [42]. The network shall not allocate a TMSI with all 32 bits equal to 1 (this is because the TMSI must be stored in the SIM, and the SIM uses 4 octets with all bits equal to 1 to indicate that no valid TMSI is available). To allow for eventual modifications of the management of the TMSI code space management, MSs shall not check if an allocated TMSI belongs to the range allocated to the allocating node. MSs shall use an allocated TMSI according to the specifications, whatever its value. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 2.4 |
5,582 | – NeedForInterruptionInfoNR | The IE NeedForInterruptionInfoNR indicates whether interruption is needed for the UE to perform SSB based measurements on an NR target band without measurement gap while NR-DC or NE-DC is not configured. NeedForInterruptionInfoNR information element -- ASN1START -- TAG-NeedForInterruptionInfoNR-START NeedForInterruptionInfoNR-r18 ::= SEQUENCE { intraFreq-needForInterruption-r18 NeedForInterruptionIntraFreqList-r18, interFreq-needForInterruption-r18 NeedForInterruptionBandListNR-r18 } NeedForInterruptionIntraFreqList-r18 ::= SEQUENCE (SIZE (1.. maxNrofServingCells)) OF NeedForInterruptionNR-r18 NeedForInterruptionBandListNR-r18 ::= SEQUENCE (SIZE (1..maxBands)) OF NeedForInterruptionNR-r18 NeedForInterruptionNR-r18 ::= SEQUENCE { interruptionIndication-r18 ENUMERATED {no-gap-with-interruption, no-gap-no-interruption} OPTIONAL } -- TAG-NeedForInterruptionInfoNR-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,583 | 6.3.3 Layer mapping | The complex-valued modulation symbols for each of the codewords to be transmitted are mapped onto one or several layers. Complex-valued modulation symbols for codeword shall be mapped onto the layers , where is the number of layers and is the number of modulation symbols per layer, unless and "MUST interference presence and power ratio (MUSTIdx)" signalled in the associated DCI is '00' for only one codeword in which case , where for the layer for which MUSTIdx is '00', and for the layer for which MUSTIdx is not '00'. The value of is determined from Table 6.3.3-1 using MUSTIdx and the modulation order of the codeword for which MUSTIdx is not '00'. Table 6.3.3-1: Values for | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.3.3 |
5,584 | Annex C (informative): Intended UE behaviour for DRX Timers | When a DRX timer is set to a value of X, and n denotes the subframe in which the related event is triggered according to the clause 5.7, the intended behaviours of each DRX timer are presented in the Table C-1 below: Table C-1: Intended UE behaviour for DRX timers For drx-InactivityTimerSCPTM, drx-InactivityTimer, drx-RetransmissionTimer and drx-ULRetransmissionTimer, if X=0, the timer does not make the MAC entity to monitor the PDCCH. The intended UE behaviours in Table C-1 are not applicable for NB-IoT. For NB-IoT, the intended UE behaviour regarding setting the HARQ RTT Timer is shown in Figure C-1 and for the UL HARQ RTT Timer is shown in Figure C-2. Figure C-1: Setting the HARQ RTT Timer for NB-IoT Figure C-2: Setting the UL HARQ RTT Timer for NB-IoT | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | Annex |
5,585 | 5.2.9.2.2 Nsmsf_SMService_Activate service operation | Service operation name: Nsmsf_SMService_Activate. Description: Authorize whether the specified UE is allowed to activate SMS service, or add connectivity for SMS over new Access Type. Concurrent use: None. Inputs, Required: SUPI, NF ID, RAT Type. Inputs, Optional: GPSI, Time Zone, one or more Access Type(s), GUAMI, backup AMF(s) (if NF Type is AMF). Backup AMF(s) sent only once by the AMF to the SMSF in its first interaction with the SMSF, UE's Routing Indicator optionally with Home Network Public Key identifier or UDM Group ID for the UE. Outputs, Required: SMS service activation result. Outputs, Optional: None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.9.2.2 |
5,586 | 8.6.2.2.3 Minimum Requirement 2 Tx Antenna Port under Time Domain Measurement Resource Restriction with CRS Assistance Information | For the parameters specified in Table 8.6.2.2.3-1 and Table 8.6.2.2.3-2, the averaged probability of a miss-detected PBCH (Pm-bch) shall be below the specified value in Table 8.6.2.2.3-2. Cell 1 is the serving cell, and Cell 2 and Cell 3 are the aggressor cells. The downlink physical channel setup for Cell 1 is according to Annex C.3.2 and for Cell 2 and Cell 3 is according to Annex C3.3, respectively. The CRS assistance information [7] including Cell 2 and Cell 3 is provided. Table 8.6.2.2.3-1: Test Parameters for PBCH Table 8.6.2.2.3-2: Minimum performance PBCH | 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.6.2.2.3 |
5,587 | 9.7.1.3 FDD (Category 1bis UE) | The following requirements apply to UE DL Category 1bis. For the parameters specified in Table 9.7.1.3-1, and using the downlink physical channels specified in tables C.3.2-1 and C.3.2-2, the reported CQI value according to RC.4 FDD in Table A.4-1 shall be in the range of ±1 of the reported median more than 90% of the time. If the PDSCH BLER using the transport format indicated by median CQI is less than or equal to 0.1, the BLER using the transport format indicated by the (median CQI + 1) shall be greater than 0.1. If the PDSCH BLER using the transport format indicated by the median CQI is greater than 0.1, the BLER using transport format indicated by (median CQI – 1) shall be less than or equal to 0.1. Table 9.7.1.3-1: PUCCH 1-0 static test (FDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.7.1.3 |
5,588 | 8.138 Additional RRM Policy Index | Additional RRM Policy Index (ARPI) is coded as depicted in Figure 8.138-1 and contains a non-transparent copy of the corresponding IE (see clause 8.2.2), "Additional RRM Policy Index" as specified in 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [10]. The ARPI is encoded as Unsigned32 binary integer values. Figure 8.138-1. Additional RRM Policy Index Editor' Note: The IE name for "Additional RRM Policy Index" in S1AP is to be confirmed. | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 8.138 |
5,589 | 6.3.6.2 Stand-alone N3IWF selection | The UE performs N3IWF selection based on the ePDG selection procedure as specified in clause 4.5.4 of TS 23.402[ Architecture enhancements for non-3GPP accesses ] [43] except for the following differences: - The Tracking/Location Area Identifier FQDN shall be constructed by the UE based only on the Tracking Area wherein the UE is located. The N3IWF Tracking/Location Area Identifier FQDN may use the 5GS TAI when the UE is registered to the 5GS, or the EPS TAI when the UE is registered to EPS. The Location Area is not applicable on the 3GPP access. - The ePDG Operator Identifier (OI) FQDN format is substituted by with N3IWF OI FQDN format as specified in TS 23.003[ Numbering, addressing and identification ] [19]. - If the UE is configured with Slice-specific N3IWF prefix configuration, then the UE shall construct the Prefixed N3IWF OI FQDN or the Prefixed N3IWF TA FQDN as specified in TS 23.003[ Numbering, addressing and identification ] [19] instead of the N3IWF OI FQDN and the N3IWF TA FQDN, respectively. To determine the prefix, the UE selects the Slice-specific N3IWF prefix configuration for the selected PLMN that contains S-NSSAIs that match all (or most, in case there is no full match) of the S-NSSAIs that the UE is going to include in the Requested NSSAI in the subsequent Registration procedure. Editor's note: The Prefixed N3IWF OI FQDN is assumed to take the form: <Prefix>.tac-lb<TAC-low-byte>.tac-hb<TAC-high-byte>.tac.n3iwf.5gc.mnc<MNC>.mcc<MCC>.pub.3gppnetwork.org. The Prefixed N3IWF TA FQDN is assumed to take the form <Prefix>.n3iwf.5gc.mnc<MNC>.mcc<MCC>.pub.3gppnetwork.org. Once these FQDNs have been added to TS 23.003[ Numbering, addressing and identification ] , this Editor's note will be removed. - The ePDG identifier configuration is substituted by the N3IWF identifier configuration and the Extended Home N3IWF identifier configuration. The Extended Home N3IWF identifier configuration takes precedence over the N3IWF identifier configuration. If the UE is located in the home country and the UE is configured with Extended Home N3IWF identifier configuration, then the UE uses the Extended Home N3IWF identifier configuration to select an N3IWF: - The UE uses the FQDN or IP address from the Extended Home N3IWF identifier configuration that matches all (or most, if there is no full match) of the S-NSSAIs that the UE is going to request in the subsequent Registration. - The ePDG selection information is substituted by the Non-3GPP access node selection information and slice-specific N3IWF prefix information. The UE shall give preference to the N3IWF in all PLMNs in the Non-3GPP access node selection information independent of the "Preference" parameter. - If the UE determines to be located in a country other than its home country (called the visited country), then instead of clause 4.5.4.4, bullet 3 of TS 23.402[ Architecture enhancements for non-3GPP accesses ] [43], the following applies: a) If the UE is registered via 3GPP access to a PLMN and this PLMN is included in the Non-3GPP access node selection information, then the UE shall select an N3IWF in this PLMN. If the UE fails to connect to an N3IWF in this PLMN, the UE shall select an N3IWF by performing the DNS procedure specified in clause 4.5.4.5 of TS 23.402[ Architecture enhancements for non-3GPP accesses ] [43]. b) In all other cases, (e.g. when the UE is not configured with the Non-3GPP access node selection information, or the UE is registered via 3GPP access to a PLMN but this PLMN is not included in the Non-3GPP access node selection information, or the UE is not registered via 3GPP access to any PLMN), the UE shall select an N3IWF by performing the DNS procedure specified in clause 4.5.4.5 of TS 23.402[ Architecture enhancements for non-3GPP accesses ] [43] with the difference that the UE shall construct the Prefixed N3IWF OI FQDN if the UE is configured with Slice-specific N3IWF prefix configuration for the selected PLMN. If the UE is accessing PLMN services via SNPN, the UE uses the procedure defined in this clause to select an N3IWF deployed in the PLMN. If the UE is accessing standalone non-public network service via a PLMN (see supported cases in clause 5.30.2.0), the UE uses the procedure defined in clause 6.3.6.2a. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.3.6.2 |
5,590 | 6.5.2.4 UE requested PDN disconnection procedure not accepted by the network | Upon receipt of the PDN DISCONNECT REQUEST message, if it is not accepted by the network, the MME shall send a PDN DISCONNECT REJECT message to the UE. The PDN DISCONNECT REJECT message shall contain the PTI and an ESM cause IE that typically indicates one of the following ESM cause values: #35: PTI already in use; #43: invalid EPS bearer identity; #49: last PDN disconnection not allowed; #95 – 111: protocol errors. If EMM-REGISTERED without PDN connection is supported by the UE and the MME, then ESM cause #49 "last PDN disconnection not allowed" is not applicable. Upon receipt of the PDN DISCONNECT REJECT message, the UE shall stop the timer T3492, enter the state PROCEDURE TRANSACTION INACTIVE and abort the PDN disconnection procedure. Additionally, in all cases with the exception of the UE having received ESM cause #49 "last PDN disconnection not allowed" if EMM-REGISTERED without PDN connection is not supported by the UE or the MME, the UE shall deactivate all EPS bearer contexts for this PDN connection locally without peer-to-peer signalling between the UE and the MME. If the UE receives ESM cause #49 "last PDN disconnection not allowed" and the UE has any other PDN connections established, the UE may locally deactivate, without peer-to-peer signalling between the UE and the MME, all EPS bearer contexts associated with those other PDN connections. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.5.2.4 |
5,591 | 19.4.2.9.3 Tracking/Location Area Identity based ePDG FQDN | The Tracking/Location Area Identity based ePDG FQDN is used to support location based ePDG selection within a PLMN. There are two Tracking Area Identity based ePDG FQDNs defined: one based on a TAI with a 2 octet TAC and a 5GS one based on a 3 octet TAC. 1) The Tracking Area Identity based ePDG FQDN using a 2 octet TAC and the Location Area Identity based ePDG FQDN shall be constructed respectively as: "tac-lb<TAC-low-byte>.tac-hb<TAC-high-byte>.tac.epdg.epc.mnc<MNC>.mcc<MCC>.pub.3gppnetwork.org" and "lac<LAC>.epdg.epc.mnc<MNC>.mcc<MCC>.pub.3gppnetwork.org" where - the <MNC> and <MCC> shall identify the PLMN where the ePDG is located and shall be encoded as - <MNC> = 3 digits - <MCC> = 3 digits If there are only 2 significant digits in the MNC, one "0" digit shall be inserted at the left side to fill the 3 digits coding of MNC in the ePDG FQDN. - the <TAC>, together with the <MCC> and <MNC> shall identify the Tracking Area Identity the UE is located in. The TAC is a 16-bit integer. The <TAC-high-byte> is the hexadecimal string of the most significant byte in the TAC and the <TAC-low-byte > is the hexadecimal string of the least significant byte. If there are less than 2 significant digits in <TAC-high-byte> or <TAC-low-byte >, "0" digit(s) shall be inserted at the left side to fill the 2 digit coding; - the <LAC>, together with the <MCC> and <MNC> shall identify the Location Area Identity the UE is located in. The LAC> shall be hexadecimal coded digits representing the LAC; if there are less than 4 significant digits in <LAC>, one or more "0" digit(s) is/are inserted at the left side to fill the 4 digit coding; As examples, - the Tracking Area Identity based ePDG FQDN for the TAC H'0B21, MCC 345 and MNC 12 is coded in the DNS as: " tac-lb21.tac-hb0b.tac.epdg.epc.mnc012.mcc345.pub.3gppnetwork.org" - the Location Area Identity based ePDG FQDN for the LAC H'0B21, MCC 345 and MNC 12 is coded in the DNS as: " lac0b21.epdg.epc.mnc012.mcc345.pub.3gppnetwork.org" 2) The 5GS Tracking Area Identity based ePDG FQDN using a 3 octet TAC shall be constructed respectively as: "tac-lb<TAC-low-byte>.tac-mb<TAC-middle-byte>.tac-hb<TAC-high-byte>.5gstac. epdg.epc.mnc<MNC>.mcc<MCC>.pub.3gppnetwork.org" where - the <MNC> and <MCC> shall identify the PLMN where the ePDG is located and shall be encoded as - <MNC> = 3 digits - <MCC> = 3 digits If there are only 2 significant digits in the MNC, one "0" digit shall be inserted at the left side to fill the 3 digits coding of MNC in the ePDG FQDN. - the <TAC>, together with the <MCC> and <MNC> shall identify the 5GS Tracking Area Identity the UE is located in. The 5GS TAC is a 24-bit integer. The <TAC-high-byte> is the hexadecimal string of the most significant byte in the TAC and the <TAC-low-byte > is the hexadecimal string of the least significant byte. If there are less than 2 significant digits in <TAC-low-byte>, <TAC-middle-byte> or <TAC-high-byte >, "0" digit(s) shall be inserted at the left side to fill the 2 digits coding; As examples, - the 5GS Tracking Area Identity based ePDG FQDN for the 5GS TAC H'0B1A21, MCC 345 and MNC 12 is coded in the DNS as: "tac-lb21.tac-mb1a.tac-hb0b.5gstac.epdg.epc.mnc012.mcc345.pub.3gppnetwork.org" | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 19.4.2.9.3 |
5,592 | 9.4.6 Mapping to physical resources | The block of complex-valued symbols shall be multiplied with the amplitude scaling factor in order to conform to the transmit power specified in [4], and mapped in sequence starting with to physical resource blocks on antenna port and assigned for transmission of PSCCH. The mapping to resource elements corresponding to the physical resource blocks assigned for transmission and not used for transmission of reference signals shall be in increasing order of first the index , then the index, starting with the first slot in the subframe. Resource elements in the last SC-FDMA symbol within a subframe shall be counted in the mapping process but not transmitted. | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.4.6 |
5,593 | 6.1.3.8.1 Successful MBMS context activation | In order to request an MBMS context activation, the network sends a REQUEST MBMS CONTEXT ACTIVATION message to the MS, enters the state MBMS-ACTIVE-PENDING and starts timer T3385. The message shall contain the IP multicast address, the APN and the Linked NSAPI. Upon receipt of a REQUEST MBMS CONTEXT ACTIVATION message, the MS shall validate the message by verifying the NSAPI given in the Linked NSAPI IE to be one of the active PDP context(s), stop the timer T3396 if it is running for the APN indicated in the message and send an ACTIVATE MBMS CONTEXT REQUEST, enter state MBMS-ACTIVE-PENDING and start timer T3380. The message shall contain an IP multicast address and an APN, which shall be the same as the IP multicast address and the APN requested by the network in the REQUEST MBMS CONTEXT ACTIVATION message. Furthermore, the MS shall include the Supported MBMS bearer capabilities, i.e. the maximum downlink bit rate the MS can handle. Upon receipt of the ACTIVATE MBMS CONTEXT REQUEST message, the network shall stop timer T3385. If the network accepts the request, it shall reply with an ACTIVATE MBMS CONTEXT ACCEPT message. Upon receipt of the message ACTIVATE MBMS CONTEXT ACCEPT the MS shall stop timer T3380 and shall enter the state MBMS-ACTIVE. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.1.3.8.1 |
5,594 | B.3 Key derivation | When EAP methods are used with 5G system, the serving network name is always bound to the anchor key derivation as required in clause 6.1.1.3. When SEAF acts as a pass-through EAP authenticator, it always includes the serving network name (constructed as specified in clause 6.1.1.4) into the authentication request to the AUSFduring the initial authentication procedure as specified in clause 6.1.2. The AUSF verifies that the SEAF is authorized to use the serving network name, before it uses the serving network name to calculate the KSEAF from the KAUSF as described in Annex A.6. The AUSF always uses the most significant 256 bits of EMSK as the KAUSF. When EAP-TLS as specified in RFC 5216 [38] and draft-ietf-emu-eap-tls13 [76] is used for authentication, key materials are derived during authentication and key agreement procedure, which are further split into MSK and EMSK. Both UE and AUSF share a 512 bits EMSK key and use the most significant 256 bits of the EMSK as the KAUSF. The KSEAF is derived based on the rules specified in Annex A.6. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | B.3 |
5,595 | 5.24 Activation/Deactivation of PDCP duplication | If one or more DRBs are configured with PDCP duplication, the network may activate and deactivate the PDCP duplication for the configured DRB(s) by sending the PDCP Duplication Activation/Deactivation MAC CE described in clause 6.1.3.17. In addition, PDCP duplication for DRB(s) may be activated upon configuration by upper layers (TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]). Upon reception of a PDCP Duplication Activation/Deactivation MAC CE, the MAC entity shall for each DRB configured with duplication: - if the MAC CE indicates that PDCP duplication for the DRB shall be activated: - indicate the activation of PDCP duplication for the DRB to upper layers. - if the MAC CE indicates that PDCP duplication for the DRB shall be deactivated: - indicate the deactivation of PDCP duplication for the DRB to upper layers. | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.24 |
5,596 | 4.3.33.6 Paging Restriction | A Multi-USIM UE and the network may support Paging Restriction. A Multi-USIM UE, if the MME indicates that the network supports Paging Restriction feature, may indicate Paging Restriction Information in an Extended Service Request or a Tracking Area Update Request (including the case where the Tracking Area Update is performed due to mobility to a Tracking Area outside the current Tracking Area List, i.e. before detecting whether the network supports the feature in the new Tracking Area, provided that the network has already indicated support for Paging Restrictions in the current Tracking Area List), as specified in clauses 4.3.33.2 and 4.3.33.4. The MME may accept or reject the Paging Restriction Information requested by the UE. If the MME accepts the Paging Restriction Information from the UE, the MME stores the Paging Restriction Information from the UE in the UE context. If the MME rejects the Paging Restriction Information the MME removes any stored Paging Restriction Information from the UE context and discards the UEs requested Paging Restriction Information. The MME informs the UE about the acceptance/rejection of the requested Paging Restriction Information in the Tracking Area Update Accept or Service Accept message. If the UE does not provide Paging Restriction Information in the Extended Service Request message or the Tracking Area Update Request message, or if the UE initiates the Service Request procedure, the MME removes any stored Paging Restriction Information from the UE context. The Paging Restriction Information may indicate any of the following: a) all paging is restricted, or b) all paging is restricted, except paging for voice service (MMTel voice or CS domain voice), or c) all paging is restricted, except for certain PDN Connection(s), or d) all paging is restricted, except for certain PDN Connection(s) and voice service (MMTel voice or CS domain voice). NOTE 1: The UE expects not to be paged for any purpose in case a). The UE expects to be paged only for voice service in case b). The UE expects to be paged only for certain PDN Connection(s) in case c). The UE expects be paged for voice service and certain PDN Connection(s) in case d). The MME can page the UE for mobile terminated signalling based on local policy considering the stored Paging Restriction Information, except for case a). In this case, to comply with UE provided Paging Restriction Information, the MME can trigger S1 release procedure as soon as possible after the mobile terminated signalling procedure is executed. NOTE 2: In the case of roaming, the paging restrictions for voice service implied by bullet b) and d) depends on the existence of an agreement with the HPLMN to support voice service via IMS. Hence the support of paging restrictions in bullets b) and d) takes the IMS voice service agreement into consideration. NOTE 3: When there is no PLMN-wide support for the Paging Restriction feature, it can occur that upon Tracking Area Update due to mobility with Paging Restriction Information the UE detects the network does not support the feature. If so, the UE assumes that no Paging Restriction is applied. | 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.33.6 |
5,597 | 4.16.1.2 Successful Secondary Node Additions without SN terminated bearers | a) This measurement provides the number of successful Secondary Node Additions without SN terminated bearers. b) CC c) On transmission by the MN of an SgNB reconfiguration complete message to SN (after MN receives RRCConnectionReconfigurationComplete message) from UE when without SN terminated bearers. SGNB Addition Trigger Indication (TS 36.423[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 Application Protocol (X2AP) ] ) excludes SN change, inter-eNB HO, intra-eNB HO. d) Each measurement is an integer value. e) The measurement name has the form ENDC.SNAdditionSuccWoSnErab. f) EUtranCellFDD EUtranCellTDD g) Valid for packet switched traffic h) EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.16.1.2 |
5,598 | 5.14.2.2.2 Sidelink process | For each subframe where a transmission takes place for the Sidelink process, one TB and the associated HARQ information is received from the Sidelink HARQ Entity. The sequence of redundancy versions is 0, 2, 3, 1. The variable CURRENT_IRV is an index into the sequence of redundancy versions. This variable is updated modulo 4. For each received TB and associated HARQ information, the Sidelink process shall: - if this is a new transmission: - set CURRENT_IRV to 0; - store the received data in the soft buffer and optionally attempt to decode the received data according to CURRENT_IRV. - else if this is a retransmission: - if the data for this TB has not yet been successfully decoded: - increment CURRENT_IRV by 1; - combine the received data with the data currently in the soft buffer for this TB and optionally attempt to decode the combined data according to the CURRENT_IRV. - if the data which the MAC entity attempted to decode was successfully decoded for this TB: - if this is the first successful decoding of the data for this TB: - if the DST field of the decoded MAC PDU subheader is equal to the 16 MSB of any of the Destination Layer-2 ID(s) of the UE for which the 8 LSB are equal to the Group Destination ID in the corresponding SCI: - deliver the decoded MAC PDU to the disassembly and demultiplexing entity. - else if the DST field of the decoded MAC PDU subheader is equal to any of the Destination Layer-2 ID(s) of the UE: - deliver the decoded MAC PDU to the disassembly and demultiplexing entity. | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.14.2.2.2 |
5,599 | – UE-NR-Capability | The IE UE-NR-Capability is used to convey the NR UE Radio Access Capability Parameters, see TS 38.306[ NR; User Equipment (UE) radio access capabilities ] [26]. UE-NR-Capability information element -- ASN1START -- TAG-UE-NR-CAPABILITY-START UE-NR-Capability ::= SEQUENCE { accessStratumRelease AccessStratumRelease, pdcp-Parameters PDCP-Parameters, rlc-Parameters RLC-Parameters OPTIONAL, mac-Parameters MAC-Parameters OPTIONAL, phy-Parameters Phy-Parameters, rf-Parameters RF-Parameters, measAndMobParameters MeasAndMobParameters OPTIONAL, fdd-Add-UE-NR-Capabilities UE-NR-CapabilityAddXDD-Mode OPTIONAL, tdd-Add-UE-NR-Capabilities UE-NR-CapabilityAddXDD-Mode OPTIONAL, fr1-Add-UE-NR-Capabilities UE-NR-CapabilityAddFRX-Mode OPTIONAL, fr2-Add-UE-NR-Capabilities UE-NR-CapabilityAddFRX-Mode OPTIONAL, featureSets FeatureSets OPTIONAL, featureSetCombinations SEQUENCE (SIZE (1..maxFeatureSetCombinations)) OF FeatureSetCombination OPTIONAL, lateNonCriticalExtension OCTET STRING (CONTAINING UE-NR-Capability-v15c0) OPTIONAL, nonCriticalExtension UE-NR-Capability-v1530 OPTIONAL } -- Regular non-critical Rel-15 extensions: UE-NR-Capability-v1530 ::= SEQUENCE { fdd-Add-UE-NR-Capabilities-v1530 UE-NR-CapabilityAddXDD-Mode-v1530 OPTIONAL, tdd-Add-UE-NR-Capabilities-v1530 UE-NR-CapabilityAddXDD-Mode-v1530 OPTIONAL, dummy ENUMERATED {supported} OPTIONAL, interRAT-Parameters InterRAT-Parameters OPTIONAL, inactiveState ENUMERATED {supported} OPTIONAL, delayBudgetReporting ENUMERATED {supported} OPTIONAL, nonCriticalExtension UE-NR-Capability-v1540 OPTIONAL } UE-NR-Capability-v1540 ::= SEQUENCE { sdap-Parameters SDAP-Parameters OPTIONAL, overheatingInd ENUMERATED {supported} OPTIONAL, ims-Parameters IMS-Parameters OPTIONAL, fr1-Add-UE-NR-Capabilities-v1540 UE-NR-CapabilityAddFRX-Mode-v1540 OPTIONAL, fr2-Add-UE-NR-Capabilities-v1540 UE-NR-CapabilityAddFRX-Mode-v1540 OPTIONAL, fr1-fr2-Add-UE-NR-Capabilities UE-NR-CapabilityAddFRX-Mode OPTIONAL, nonCriticalExtension UE-NR-Capability-v1550 OPTIONAL } UE-NR-Capability-v1550 ::= SEQUENCE { reducedCP-Latency ENUMERATED {supported} OPTIONAL, nonCriticalExtension UE-NR-Capability-v1560 OPTIONAL } UE-NR-Capability-v1560 ::= SEQUENCE { nrdc-Parameters NRDC-Parameters OPTIONAL, receivedFilters OCTET STRING (CONTAINING UECapabilityEnquiry-v1560-IEs) OPTIONAL, nonCriticalExtension UE-NR-Capability-v1570 OPTIONAL } UE-NR-Capability-v1570 ::= SEQUENCE { nrdc-Parameters-v1570 NRDC-Parameters-v1570 OPTIONAL, nonCriticalExtension UE-NR-Capability-v1610 OPTIONAL } -- Late non-critical Rel-15 extensions: UE-NR-Capability-v15c0 ::= SEQUENCE { nrdc-Parameters-v15c0 NRDC-Parameters-v15c0 OPTIONAL, partialFR2-FallbackRX-Req ENUMERATED {true} OPTIONAL, nonCriticalExtension UE-NR-Capability-v15g0 OPTIONAL } UE-NR-Capability-v15g0 ::= SEQUENCE { rf-Parameters-v15g0 RF-Parameters-v15g0 OPTIONAL, nonCriticalExtension UE-NR-Capability-v15j0 OPTIONAL } UE-NR-Capability-v15j0 ::= SEQUENCE { -- Following field is only for REL-15 late non-critical extensions lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension UE-NR-Capability-v16a0 OPTIONAL } -- Regular non-critical Rel-16 extensions: UE-NR-Capability-v1610 ::= SEQUENCE { inDeviceCoexInd-r16 ENUMERATED {supported} OPTIONAL, dl-DedicatedMessageSegmentation-r16 ENUMERATED {supported} OPTIONAL, nrdc-Parameters-v1610 NRDC-Parameters-v1610 OPTIONAL, powSav-Parameters-r16 PowSav-Parameters-r16 OPTIONAL, fr1-Add-UE-NR-Capabilities-v1610 UE-NR-CapabilityAddFRX-Mode-v1610 OPTIONAL, fr2-Add-UE-NR-Capabilities-v1610 UE-NR-CapabilityAddFRX-Mode-v1610 OPTIONAL, bh-RLF-Indication-r16 ENUMERATED {supported} OPTIONAL, directSN-AdditionFirstRRC-IAB-r16 ENUMERATED {supported} OPTIONAL, bap-Parameters-r16 BAP-Parameters-r16 OPTIONAL, referenceTimeProvision-r16 ENUMERATED {supported} OPTIONAL, sidelinkParameters-r16 SidelinkParameters-r16 OPTIONAL, highSpeedParameters-r16 HighSpeedParameters-r16 OPTIONAL, mac-Parameters-v1610 MAC-Parameters-v1610 OPTIONAL, mcgRLF-RecoveryViaSCG-r16 ENUMERATED {supported} OPTIONAL, resumeWithStoredMCG-SCells-r16 ENUMERATED {supported} OPTIONAL, resumeWithStoredSCG-r16 ENUMERATED {supported} OPTIONAL, resumeWithSCG-Config-r16 ENUMERATED {supported} OPTIONAL, ue-BasedPerfMeas-Parameters-r16 UE-BasedPerfMeas-Parameters-r16 OPTIONAL, son-Parameters-r16 SON-Parameters-r16 OPTIONAL, onDemandSIB-Connected-r16 ENUMERATED {supported} OPTIONAL, nonCriticalExtension UE-NR-Capability-v1640 OPTIONAL } UE-NR-Capability-v1640 ::= SEQUENCE { redirectAtResumeByNAS-r16 ENUMERATED {supported} OPTIONAL, phy-ParametersSharedSpectrumChAccess-r16 Phy-ParametersSharedSpectrumChAccess-r16 OPTIONAL, nonCriticalExtension UE-NR-Capability-v1650 OPTIONAL } UE-NR-Capability-v1650 ::= SEQUENCE { mpsPriorityIndication-r16 ENUMERATED {supported} OPTIONAL, highSpeedParameters-v1650 HighSpeedParameters-v1650 OPTIONAL, nonCriticalExtension UE-NR-Capability-v1690 OPTIONAL } UE-NR-Capability-v1690 ::= SEQUENCE { ul-RRC-Segmentation-r16 ENUMERATED {supported} OPTIONAL, nonCriticalExtension UE-NR-Capability-v1700 OPTIONAL } -- Late non-critical extensions from Rel-16 onwards: UE-NR-Capability-v16a0 ::= SEQUENCE { phy-Parameters-v16a0 Phy-Parameters-v16a0 OPTIONAL, rf-Parameters-v16a0 RF-Parameters-v16a0 OPTIONAL, nonCriticalExtension UE-NR-Capability-v16c0 OPTIONAL } UE-NR-Capability-v16c0 ::= SEQUENCE { rf-Parameters-v16c0 RF-Parameters-v16c0 OPTIONAL, nonCriticalExtension UE-NR-Capability-v16d0 OPTIONAL } UE-NR-Capability-v16d0 ::= SEQUENCE { featureSets-v16d0 FeatureSets-v16d0 OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } -- Regular non-critical Rel-17 extensions: UE-NR-Capability-v1700 ::= SEQUENCE { inactiveStatePO-Determination-r17 ENUMERATED {supported} OPTIONAL, highSpeedParameters-v1700 HighSpeedParameters-v1700 OPTIONAL, powSav-Parameters-v1700 PowSav-Parameters-v1700 OPTIONAL, mac-Parameters-v1700 MAC-Parameters-v1700 OPTIONAL, ims-Parameters-v1700 IMS-Parameters-v1700 OPTIONAL, measAndMobParameters-v1700 MeasAndMobParameters-v1700, appLayerMeasParameters-r17 AppLayerMeasParameters-r17 OPTIONAL, redCapParameters-r17 RedCapParameters-r17 OPTIONAL, ra-SDT-r17 ENUMERATED {supported} OPTIONAL, srb-SDT-r17 ENUMERATED {supported} OPTIONAL, gNB-SideRTT-BasedPDC-r17 ENUMERATED {supported} OPTIONAL, bh-RLF-DetectionRecovery-Indication-r17 ENUMERATED {supported} OPTIONAL, nrdc-Parameters-v1700 NRDC-Parameters-v1700 OPTIONAL, bap-Parameters-v1700 BAP-Parameters-v1700 OPTIONAL, musim-GapPreference-r17 ENUMERATED {supported} OPTIONAL, musimLeaveConnected-r17 ENUMERATED {supported} OPTIONAL, mbs-Parameters-r17 MBS-Parameters-r17, nonTerrestrialNetwork-r17 ENUMERATED {supported} OPTIONAL, ntn-ScenarioSupport-r17 ENUMERATED {gso, ngso} OPTIONAL, sliceInfoforCellReselection-r17 ENUMERATED {supported} OPTIONAL, ue-RadioPagingInfo-r17 UE-RadioPagingInfo-r17 OPTIONAL, -- R4 17-2 UL gap pattern for Tx power management ul-GapFR2-Pattern-r17 BIT STRING (SIZE (4)) OPTIONAL, ntn-Parameters-r17 NTN-Parameters-r17 OPTIONAL, nonCriticalExtension UE-NR-Capability-v1740 OPTIONAL } UE-NR-Capability-v1740 ::= SEQUENCE { redCapParameters-v1740 RedCapParameters-v1740, nonCriticalExtension UE-NR-Capability-v1750 OPTIONAL } UE-NR-Capability-v1750 ::= SEQUENCE { crossCarrierSchedulingConfigurationRelease-r17 ENUMERATED {supported} OPTIONAL, nonCriticalExtension UE-NR-Capability-v1800 OPTIONAL } -- Regular non-critical Rel-18 extensions: UE-NR-Capability-v1800 ::= SEQUENCE { airToGroundNetwork-r18 ENUMERATED {supported} OPTIONAL, eRedCapParameters-r18 ERedCapParameters-r18 OPTIONAL, ncr-Parameters-r18 NCR-Parameters-r18 OPTIONAL, softSatelliteSwitchResyncNTN-r18 ENUMERATED {supported} OPTIONAL, hardSatelliteSwitchResyncNTN-r18 ENUMERATED {supported} OPTIONAL, mt-SDT-r18 ENUMERATED {supported} OPTIONAL, mt-SDT-NTN-r18 ENUMERATED {supported} OPTIONAL, inDeviceCoexIndAutonomousDenial-r18 ENUMERATED {supported} OPTIONAL, inDeviceCoexIndFDM-r18 ENUMERATED {supported} OPTIONAL, inDeviceCoexIndTDM-r18 ENUMERATED {supported} OPTIONAL, musim-GapPriorityPreference-r18 ENUMERATED {supported} OPTIONAL, musim-CapabilityRestriction-r18 ENUMERATED {supported} OPTIONAL, multiRx-FR2-Preference-r18 ENUMERATED {supported} OPTIONAL, ra-InsteadCG-SDT-r18 ENUMERATED {supported} OPTIONAL, resumeAfterSDT-Release-r18 ENUMERATED {supported} OPTIONAL, additionalBSR-Table-r18 ENUMERATED {supported} OPTIONAL, delayStatusReport-r18 ENUMERATED {supported} OPTIONAL, disableCG-RetransmissionMonitoring-r18 ENUMERATED {supported} OPTIONAL, enhancedDRX-r18 ENUMERATED {supported} OPTIONAL, pdu-SetDiscard-r18 ENUMERATED {supported} OPTIONAL, psi-BasedDiscard-r18 ENUMERATED {supported} OPTIONAL, ul-TrafficInfo-r18 ENUMERATED {supported} OPTIONAL, aerialParameters-r18 AerialParameters-r18 OPTIONAL, nonCriticalExtension SEQUENCE{} OPTIONAL } UE-NR-CapabilityAddXDD-Mode ::= SEQUENCE { phy-ParametersXDD-Diff Phy-ParametersXDD-Diff OPTIONAL, mac-ParametersXDD-Diff MAC-ParametersXDD-Diff OPTIONAL, measAndMobParametersXDD-Diff MeasAndMobParametersXDD-Diff OPTIONAL } UE-NR-CapabilityAddXDD-Mode-v1530 ::= SEQUENCE { eutra-ParametersXDD-Diff EUTRA-ParametersXDD-Diff } UE-NR-CapabilityAddFRX-Mode ::= SEQUENCE { phy-ParametersFRX-Diff Phy-ParametersFRX-Diff OPTIONAL, measAndMobParametersFRX-Diff MeasAndMobParametersFRX-Diff OPTIONAL } UE-NR-CapabilityAddFRX-Mode-v1540 ::= SEQUENCE { ims-ParametersFRX-Diff IMS-ParametersFRX-Diff OPTIONAL } UE-NR-CapabilityAddFRX-Mode-v1610 ::= SEQUENCE { powSav-ParametersFRX-Diff-r16 PowSav-ParametersFRX-Diff-r16 OPTIONAL, mac-ParametersFRX-Diff-r16 MAC-ParametersFRX-Diff-r16 OPTIONAL } BAP-Parameters-r16 ::= SEQUENCE { flowControlBH-RLC-ChannelBased-r16 ENUMERATED {supported} OPTIONAL, flowControlRouting-ID-Based-r16 ENUMERATED {supported} OPTIONAL } BAP-Parameters-v1700 ::= SEQUENCE { bapHeaderRewriting-Rerouting-r17 ENUMERATED {supported} OPTIONAL, bapHeaderRewriting-Routing-r17 ENUMERATED {supported} OPTIONAL } MBS-Parameters-r17 ::= SEQUENCE { maxMRB-Add-r17 INTEGER (1..16) OPTIONAL } -- TAG-UE-NR-CAPABILITY-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,600 | 5.3.5.17.2.2 SL indirect path specific configuration | The L2 U2N Remote UE shall: 1> if sl-IndirectPathAddChange is set to setup: 2> consider the UE indicated by the sl-IndirectPathRelayUE-Identity to be the (target) L2 U2N Relay UE and indicate to upper layer to trigger the PC5 unicast link establishment with the L2 U2N Relay UE; 2> start timer T421 for the corresponding L2 U2N Relay UE with the timer value set to T421; 2> indicate to upper layer (to trigger the PC5 unicast link release) with the source L2 U2N Relay UE in case of SL indirect path change (i.e. a new L2 U2N Relay UE is indicated via sl-IndirectPathRelayUE-Identity); 1> else if sl-IndirectPathAddChange is set to release: 2> consider the SL indirect path is released and release the corresponding configurations; 2> indicate to upper layer (to trigger the PC5 unicast link release) with the L2 U2N Relay UE. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.5.17.2.2 |
Subsets and Splits
No saved queries yet
Save your SQL queries to embed, download, and access them later. Queries will appear here once saved.