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
⌀ |
|---|---|---|---|---|---|---|---|
4,501 | – VarMeasReportList | The UE variable VarMeasReportList includes information about the measurements for which the triggering conditions have been met. VarMeasReportList UE variable -- ASN1START -- TAG-VARMEASREPORTLIST-START VarMeasReportList ::= SEQUENCE (SIZE (1..maxNrofMeasId)) OF VarMeasReport VarMeasReport ::= SEQUENCE { -- List of measurement that have been triggered measId MeasId, cellsTriggeredList CellsTriggeredList OPTIONAL, numberOfReportsSent INTEGER, cli-TriggeredList-r16 CLI-TriggeredList-r16 OPTIONAL, tx-PoolMeasToAddModListNR-r16 Tx-PoolMeasList-r16 OPTIONAL, relaysTriggeredList-r17 RelaysTriggeredList-r17 OPTIONAL } CellsTriggeredList ::= SEQUENCE (SIZE (1..maxNrofCellMeas)) OF CHOICE { physCellId PhysCellId, physCellIdEUTRA EUTRA-PhysCellId, physCellIdUTRA-FDD-r16 PhysCellIdUTRA-FDD-r16 } CLI-TriggeredList-r16 ::= CHOICE { srs-RSRP-TriggeredList-r16 SRS-RSRP-TriggeredList-r16, cli-RSSI-TriggeredList-r16 CLI-RSSI-TriggeredList-r16 } SRS-RSRP-TriggeredList-r16 ::= SEQUENCE (SIZE (1.. maxNrofCLI-SRS-Resources-r16)) OF SRS-ResourceId CLI-RSSI-TriggeredList-r16 ::= SEQUENCE (SIZE (1.. maxNrofCLI-RSSI-Resources-r16)) OF RSSI-ResourceId-r16 RelaysTriggeredList-r17 ::= SEQUENCE (SIZE (1.. maxNrofRelayMeas-r17)) OF SL-SourceIdentity-r17 -- TAG-VARMEASREPORTLIST-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,502 | 8.14.1.2 Signalling of RACH information from gNB-CU to gNB-DU | The signalling flow for signalling of RACH information from gNB-CU to gNB-DU is shown in Figure 8.14.1.2-1, where the example where NG-RAN nodes exchange the RACH Report via the Xn: ACCESS AND MOBILITY INDICATION message has been considered. Figure 8.14.1.2-1 Example of signalling of RACH information from gNB-CU to gNB-DU in NG-RAN 1. A UE with a RACH Report concerning cells of gNB1 connects to a cell in gNB2 and it signals the RACH Report to gNB2 by means of the RRC UE Information Request/Response procedures. 2. GNB2 sends an Xn: Access and Mobility Indication message to gNB1-CU where the UE may have previously been connected. This includes also the RACH Report. 3. GNB1-CU sends the F1: Access and Mobility Indication message to the gNB1-DU, including the RACH Report. It is also possible for the gNB-CU receiving the RACH Report from the UE to signal it directly to the gNB-DU by means of the F1: Access and Mobility Indication procedure. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.14.1.2 |
4,503 | A.3.8 Guidelines on use of parameterised SetupRelease type | The usage of the parameterised SetupRelease type is like a function call in programming languages where the element type parameter is passed as a parameter. The parameterised type only implies a textual change in abstract syntax where all references to the parameterised type are replaced by the compiler with the release/setup choice. Two examples of the usage are shown below: -- /example/ ASN1START RRCMessage-rX-IEs ::= SEQUENCE { field-rX SetupRelease { IE-rX } OPTIONAL, -- Need M ... } RRCMessage-rX-IEs ::= SEQUENCE { field-rX SetupRelease { Element-rX } } OPTIONAL, -- Need M Element-rX ::= SEQUENCE { field1-rX IE1-rX, field2-rX IE2-rX OPTIONAL -- Need N } OPTIONAL, -- Need M -- /example/ ASN1STOP The SetupRelease is always be used with only named IEs, i.e. the example below is not allowed: -- /example/ ASN1START RRCMessage-rX-IEs ::= SEQUENCE { field-rX SetupRelease { SEQUENCE { -- Unnamed SEQUENCEs are not allowed! field1-rX IE1-rX, field2-rX IE2-rX OPTIONAL -- Need N } } OPTIONAL, -- Need M } -- /example/ ASN1STOP If a field defined using the parameterized SetupRelease type requires procedural text, the field is referred to using the values defined for the type itself, namely, "setup" and "release". For example, procedural text for field-rX above could be as follows: 1> if field-rX is set to "setup": 2> do something; 1> else (field-rX is set to "release"): 2> release field-rX (if appropriate). | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | A.3.8 |
4,504 | 20.4.3 Session-Termination-Request Command | A DIAMETER session may be terminated by the MBMS GW in exceptional cases. The relevant AVPs that are of use for the SGmb interface are detailed in the ABNF description below. Other valid AVPs for this command are not used for SGmb purposes and should be ignored by the receiver or processed according to the relevant specifications. Message Format: <ST-Request> ::= < Diameter Header: 275, REQ, PXY > < Session-Id > { Origin-Host } { Origin-Realm } { Destination-Realm } { Auth-Application-Id } { Termination-Cause } [ Destination-Host ] * [ Class ] [ Origin-State-Id ] * [ Proxy-Info ] * [ Route-Record ] [ Diagnostic-Info ] [ Restart-Counter ] | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 20.4.3 |
4,505 | T.2 Security of network exposure to edge application server | It is defined in the TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [98] clause 6.4 that the network could expose network information to the local AF with two scenarios, i.e. - Case 1: L-PSA UPF may expose the network information to local AF via Local NEF, - Case 2: or L-PSA UPF may expose the network information to local AF directly. However, How to deliver the information on N6 is out of scope. For the Case 1, the Security aspects of Network Exposure Function specified in clause 12 shall be used for the network information exposure. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | T.2 |
4,506 | G.4.2 Overview of Deployment Scenario | Figure G.4.2-1 shows an overview of this deployment scenario. For SBI-based interactions with other 5GC functionalities, a consumer entity (e.g. 5GC functionality B in the cluster on the left side) communicates through the cluster's Service Router with other entities in other clusters (e.g. 5GC Functionality D in the cluster on the right side). The target selection is performed through the platform's Discovery Service. From the client's perspective, the Service Router is the first and only contact point to the SCP. The platform resolves the requested Service identifier and aligns the results with the platform's policies. The Path Computation Element calculates a path between the consumer and the producer (e.g. the shortest path between the nodes). Figure G.4.2-1: (NbR-) SCP interconnects multiple deployment clusters with external NRF | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | G.4.2 |
4,507 | 4.3A Applicability of minimum requirements (CA, UL-MIMO, ProSe, Dual Connectivity, UE category 0, UE category M1, UE category M2, UE category 1bis, UE category NB1 and NB2, V2X Communication, MBMS UE, LTE based 5G terrestrial broadcast, Aerial UE) | The feature-specific requirements in clauses 5, 6 and 7 related to CA, UL-MIMO, ProSe, Dual Connectivity, UE category 0, UE category M1, UE category M2, UE category 1bis, UE category NB1 and NB2, V2X Communication, and LTE based 5G terrestrial broadcast and Aerial UE are specified as suffix A, B, C, D, E, F, G,H and K where; a) Suffix A additional requirements need to support CA b) Suffix B additional requirements need to support UL-MIMO c) Suffix C additional requirements need to support Dual Connectivity d) Suffix D additional requirements need to support ProSe e) Suffix E additional requirements need to support UE category 0, category M1, category M2, and category 1bis f) Suffix F additional requirements need to support UE category NB1 and NB2 g) Suffix G additional requirements need to support V2X Communication h) Suffix H additional requirements needed to support LTE based 5G terrestrial broadcasth) Suffix H additional requirements needed to support LTE based 5G terrestrial broadcast i) Suffix K additional requirements needed to support Aerial UEs (UAV) A terminal which supports the above features needs to meet both the general requirements and the additional requirement applicable to the additional subclause (suffix A, B, C, D, E, F, G, H and K) in clauses 5, 6 and 7. Where there is a difference in requirement between the general requirements and the additional subclause requirements (suffix A, B, C, D, E, F, G, H and K) in clauses 5, 6 and 7, the tighter requirements are applicable unless stated otherwise in the additional subclause. A terminal which supports more than one of above features in clauses 5, 6 and 7 shall meet all of the separate corresponding requirements. For a terminal supporting CA, compliance with minimum requirements for non-contiguous intra-band carrier aggregation in any given operating band does not imply compliance with minimum requirements for contiguous intra-band carrier aggregation in the same operating band. For a terminal supporting CA, compliance with minimum requirements for contiguous intra-band carrier aggregation in any given operating band does not imply compliance with minimum requirements for non- contiguous intra-band carrier aggregation in the same operating band. A terminal which supports a DL CA configuration shall support all the lower order fallback DL CA combinations and it shall support at least one bandwidth combination set for each of the constituent lower order DL combinations containing all the bandwidths specified within each specific combination set of the upper order DL combination. A terminal which supports CA, for each supported CA configuration, shall support Pcell transmissions in each of the aggregated Component Carriers unless indicated otherwise in clause 5.6A.1. Terminal supporting Dual Connectivity configuration shall meet the minimum requirements for corresponding CA configuration (suffix A), unless otherwise specified. For a terminal that supports ProSe Direct Communication and/or ProSe Direct Discovery, the minimum requirements are applicable when - the UE is associated with a serving cell on the ProSe carrier, or - the UE is not associated with a serving cell on the ProSe carrier and is provisioned with the preconfigured radio parameters for ProSe Direct Communications and/or ProSe Direct Discovery that are associated with known Geographical Area, or - the UE is associated with a serving cell on a carrier different than the ProSe carrier, and the radio parameters for ProSe Direct Discovery on the ProSe carrier are provided by the serving cell, or - the UE is associated with a serving cell on a carrier different than the ProSe carrier, and has a non-serving cell selected on the ProSe carrier that supports ProSe Direct Discovery and/or ProSe Direct Communication. When the ProSe UE is not associated with a serving cell on the ProSe carrier, and the UE does not have knowledge of its geographical area, or is provisioned with preconfigured radio parameters that are not associated with any Geographical Area, ProSe transmissions are not allowed, and the requirements in Section 6.3.3D apply. A terminal that supports simultaneous E-UTRA ProSe sidelink transmissions and E-UTRA uplink transmissions for the inter-band E-UTRA ProSe/E-UTRA bands specified in Table 5.5D-2, shall meet the minimum requirements for the corresponding inter-band UL CA configuration (suffix A), unless otherwise specified. For transmitter characteristics specified in clause 6, the terminal is required to meet the conformance tests for the corresponding inter-band UL CA configuration and is not required to be retested with simultaneous E-UTRA ProSe sidelink and E-UTRA uplink transmissions. A terminal that supports E-UTRA V2X intra-band multi-carrier operation including carrier aggregation for the band specified in Table 5.5G-3, shall meet the corresponding transmitter characteristics requirements (in subclauses with suffix G in Section 6) only when there are multiple active transmissions on all of the configured carrier components. When there is only one active transmission on one of the configured carrier components, the corresponding requirements for V2X single carrier operation apply for the corresponding active carrier component. A terminal which supports MBMS (including 15 kHz, 7.5 kHz ,1.25 kHz, 2.5 kHz and 0.37 kHz subcarrier spacing), shall meet the minimum requirements in clauses 5 and 7. A terminal which supports MBMS is not required to support all kinds of subcarrier spacing. A terminal that supports multiple TTI patterns in different carriers, different TTI patterns can only be used when the carriers are aggregated in inter-band manner. For intra-band carrier aggregation, only same TTI patterns and same TAG are allowed in aggregated carriers. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 4.3A |
4,508 | 5.5.2.2.4 UE-initiated de-registration procedure completion for 5GS services over non-3GPP access | If the access type in the DEREGISTRATION REQUEST indicates that the de-registration procedure is for non-3GPP access, the AMF shall trigger SMF to perform a local release of the PDU session(s) established over non-3GPP access, if any, for this UE. The UE shall perform a local release of the PDU session(s) established over non-3GPP access, if any. If there is an MA PDU session with user plane resources established on both 3GPP access and non-3GPP access in the same PLMN or in different PLMNs, the AMF shall trigger SMF to perform release of user plane resources on non-3GPP access, and the UE shall consider the user plane resources on non-3GPP access as released. If there is an MA PDU session with a PDN connection as a user-plane resource and user plane resources established on non-3GPP access, the AMF shall trigger SMF to perform release of user plane resources on non-3GPP access, and the UE shall consider the user plane resources on non-3GPP access as released. If the UE has an MA PDU session with user plane resources established on non-3GPP access only, the AMF shall trigger the SMF to perform a local release of the MA PDU session, and the UE shall perform a local release of the MA PDU session. The UE is marked as inactive in the AMF for 5GS services for non-3GPP access. The AMF shall enter the state 5GMM-DEREGISTERED over non-3GPP access. If the de-registration request is not due to switch off, the UE shall: a) if the de-registration procedure was performed due to disabling of 5GS services, enter the 5GMM-NULL state for non-3GPP access; b) otherwise, enter the 5GMM-DEREGISTERED state for non-3GPP access. NOTE: Case b) is applicable when the UE is also registered over 3GPP access. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.2.2.4 |
4,509 | 4.23.4 Service Request procedures 4.23.4.1 General | The following two scenarios are considered: - The I-SMF is available for the PDU Session and I-SMF is not changed or removed during the service request procedure. The procedure to support this scenario is described in clause 4.23.4.2. - The I-SMF is inserted, changed or removed during service request procedure. The procedure to support this scenario is described in clause 4.23.4.3. When the AMF receives the service request message, for each PDU Session to be activated based on the service area information of SMF and the location where the UE camped the AMF determines which procedure is used. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.23.4 |
4,510 | 6.8.1 PDCCH formats | The physical downlink control channel carries scheduling assignments and other control information. A physical control channel is transmitted on an aggregation of one or several consecutive control channel elements (CCEs), where a control channel element corresponds to 9 resource element groups. The number of resource-element groups not assigned to PCFICH or PHICH is . The CCEs available in the system are numbered from 0 to, where . The PDCCH supports multiple formats as listed in Table 6.8.1-1 where PDCCH format 4 is supported only for non-MBSFN subframes in an MBMS-dedicated cell. A PDCCH consisting of consecutive CCEs may only start on a CCE fulfilling, where is the CCE number. Multiple PDCCHs can be transmitted in a subframe. Table 6.8.1-1: Supported PDCCH formats | 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.8.1 |
4,511 | 8.9.4.1.1 Enhanced Downlink Control Channel Performance Requirement Type A - 2 Tx Antenna Port with Non-Colliding CRS Dominant Interferer | The purpose of this test is to verify the Enhanced Downlink Control Channel Performance Requirement Type A for PDCCH/PCFICH with 2 transmit antennas for the case of dominant interferer with the non-colliding CRS pattern and applying interference model defined in clause B.7.1. For the parameters specified in Table 8.4.1-1 and Table 8.9.4.1.1-1, the average probability of a missed downlink scheduling grant (Pm-dsg) shall be below the specified value in Table 8.9.4.1.1-2. In Table 8.9.4.1.1-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.9.4.1.1-1: Test Parameters for PDCCH/PCFICH Table 8.9.4.1.1-2: Minimum Performance for PDCCH/PCFICH for Enhanced Downlink Control Channel Performance Requirement Type A | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.9.4.1.1 |
4,512 | 4.4.2.2 Establishment of a mapped EPS security context during intersystem handover | In order for the UE to derive a mapped EPS security context for an inter-system change from A/Gb mode or Iu mode to S1 mode in EMM-CONNECTED mode, the MME shall generate a KSISGSN, create a nonceMME and generate the K'ASME using the created nonceMME as indicated in 3GPP TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [19]. The MME shall include the selected NAS algorithms, nonceMME and generated KSISGSN (associated with the K'ASME) in the NAS security transparent container for handover to E-UTRAN. The MME shall derive the EPS NAS keys from K'ASME. When the UE receives the command to perform handover to E-UTRAN, the UE shall derive K'ASME, as indicated in 3GPP TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [19], using the nonceMME received in the NAS security transparent container. Furthermore, the UE shall associate the derived K'ASME with the received KSISGSN and derive the EPS NAS keys from K'ASME. When the UE has a PDN connection for emergency bearer services and has no current UMTS security context, the MME shall set EIA0 and EEA0 as the selected NAS security algorithms in the NAS security transparent container for handover to E-UTRAN. The MME shall create a locally generated K'ASME. The MME shall set the KSI value of the associated security context to "000" and the type of security context flag to "mapped security context" in the NAS security transparent container for handover to E-UTRAN. When the UE receives the command to perform handover to E-UTRAN and has a PDN connection for emergency bearer services, if EIA0 and EEA0 as the selected NAS security algorithms are included in the NAS security transparent container for handover to E-UTRAN, the UE shall create a locally generated K'ASME. The UE shall set the KSI value of the associated security context to the KSI value received. If the inter-system change from A/Gb mode or Iu mode to S1 mode in EMM-CONNECTED mode is not completed successfully, the MME and the UE shall delete the new mapped EPS security context. The establishment of a mapped EPS security context during inter-system change from N1 mode to S1 mode in EMM-CONNECTED mode is specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] clause 4.4.2.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.4.2.2 |
4,513 | 8.12.3 Mobile IAB-node integration | During the integration, the mobile IAB-MT and the mobile IAB-DU can connect to the same IAB-donor or to different IAB-donors. The procedure for the latter case is shown in Figure 8.12.3-1. Figure 8.12.3-1: Decoupled mobile IAB-node integration procedure Phase 1: Equivalent procedure to Phase 1 of the IAB-node integration in SA mode in clause 8.12.1, where the mobile IAB-node and the RRC-terminating IAB-donor correspond to IAB-node 2 and the IAB-donor, respectively. The mobile IAB-node selects the parent node based on a mobile-IAB-specific over-the-air indication (transmitted in SIB1). The mobile IAB-MT includes a mobile-IAB-node-specific indication in the RRCSetupComplete message to assist the RRC-terminating IAB-donor in selecting an AMF supporting mobile IAB. Phase 2-1: Same as Phase 2-1 of procedure in clause 8.12.1. Phase 2-2: Same as Phase 2-2 of procedure in clause 8.12.1. Phase 3: Mobile IAB-DU part setup. In this phase, the mobile IAB-DU is configured via OAM. The configured information includes, e.g., the information of the F1-terminating IAB-donor-CU, to enable the mobile IAB-DU to initiate the establishment of F1-C to the F1-terminating IAB-donor-CU. The mobile IAB-DU initiates the TNL establishment, and F1 setup (as defined in clause 8.5) with the F1-terminating IAB-donor-CU using the default BAP routing ID and default BH RLC channel configured by the RRC-terminating IAB-donor-CU in Phase 2-1 for upstream traffic. During the F1 setup, the mobile IAB-DU includes the gNB ID of the RRC-terminating IAB-donor-CU and the BAP address of the co-located mobile IAB-MT in the F1 SETUP REQUEST message. The mobile IAB-node determines this gNB ID based on the over-the-air broadcast (SIB1) by the RRC-terminating IAB-donor. After the F1 is set up, the mobile IAB-node can start serving UEs. The F1-terminating IAB-donor-CU can initiate the IAB Transport Migration Management procedure towards the RRC-terminating IAB-donor-CU as defined in clause 8.17.3.1. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.12.3 |
4,514 | 10.5.4.27 Allowed actions $(CCBS)$ | The purpose of the Allowed actions information element is to provide the mobile station with information about further allowed procedures. The Allowed actions information element is coded as shown in figure 10.5.116/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.133/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The Allowed actions is a type 4 information element with 3 octets length. Figure 10.5.116/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Allowed actions information element Table 10.5.133/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Allowed actions 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.27 |
4,515 | 5.3.4.1 UE triggered Service Request | Figure 5.3.4.1-1: UE triggered Service Request procedure The Service Request procedure in this clause is triggered by the UE in: a) ECM-IDLE state to establish user plane radio bearers for the UE; b) ECM-IDLE state to establish user plane radio bearers even if the UE applies Control Plane CIoT EPS Optimisation, when the UE and MME supports S1-U data transfer or User Plane EPS Optimisation in addition to Control Plane CIoT EPS Optimisation; c) ECM-CONNECTED state to request, if the UE is a Multi-USIM UE and wants to release of the UE connection, stop of any data transmission, discard of any pending data and, optionally, Paging Restriction Information; or d) ECM-IDLE state to request, if the UE is a Multi-USIM UE wants to remove the Paging Restriction Information. e) ECM-IDLE state, if the UE is a Multi-USIM UE and wants to respond to paging with a Reject Paging Indication that indicates that S1 connection shall be released and no user plane radio bearers shall be established, unless it is unable to do so, e.g. due to UE implementation constraints. The UE optionally provides the Paging Restriction Information. NOTE 1: It is not expected that a Multi-USIM UE will execute UE triggered service request procedure with Release Request indication if regulatory prioritized services (e.g. emergency service, emergency callback waiting) are ongoing. NOTE 2: For a PMIP-based S5/S8, procedure steps (A) are defined in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [2]. Steps 9 and 11 concern GTP-based S5/S8. 1. The UE sends NAS message Service Request towards the MME encapsulated in an RRC message to the eNodeB. The RRC message(s) that can be used to carry the S-TMSI and this NAS message are described in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]. The Multi-USIM UE in ECM-CONNECTED state may include the Release Request indication and optionally Paging Restriction Information in the Service Request message, if the UE intends to return to ECM-IDLE state. 2. The eNodeB forwards NAS message to MME. NAS message is encapsulated in either an S1-AP: Initial UE Message (NAS message, TAI+ECGI of the serving cell, S-TMSI, CSG ID, CSG access Mode, RRC establishment cause), or another S1-AP message (e.g. Uplink NAS Transport Message) used for the UE in ECM-CONNECTED. Details of this step are described in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]. If the MME can't handle the Service Request it will reject it. CSG ID is provided if the UE sends the Service Request message via a CSG cell or a hybrid cell. CSG access mode is provided if the UE sends the Service Request message via a hybrid cell. If the CSG access mode is not provided but the CSG ID is provided, the MME shall consider the cell as a CSG cell. If a CSG ID is indicated and CSG access mode is not provided, and there is no subscription data for this CSG ID and associated PLMN or the CSG subscription is expired, the MME rejects the Service Request with an appropriate cause. The UE shall remove the CSG ID and associated PLMN of the cell where the UE has initiated the service request procedure from the Allowed CSG list, if present. For UEs with emergency EPS bearers, i.e. at least one EPS bearer has an ARP value reserved for emergency services, if CSG access restrictions do not allow the UE to get normal services the MME shall deactivate all non-emergency bearers and accept the Service Request. If LIPA is active for a PDN connection and if the cell accessed by the UE does not link to the L-GW where the UE initiated the LIPA PDN Connection, the MME shall not request the establishment of the bearers of the LIPA PDN connection from the eNodeB in step 4 and shall request disconnection of the LIPA PDN connection according to clause 5.10.3. If the UE has no other PDN connection then the MME shall reject the Service Request with an appropriate cause value resulting in the UE detaching, skip the following steps of the procedure and initiate the release of the core network resources with the implicit MME-initiated Detach procedure according to clause 5.3.8.3. If there is a "Availability after DDN Failure" monitoring event or a "UE Reachability" monitoring event configured for the UE in the MME, the MME sends an event notification (see TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [74] for further information). To assist Location Services, the eNodeB indicates the UE's Coverage Level to the MME. If the MME supports RACS, and the MME detects that the selected PLMN is different from the currently registered PLMN for the UE, the MME provides the UE Radio Capability ID of the newly selected PLMN in the UE context to the eNodeB as described in clause 5.11.3a. If the Service Request message is received from a UE in ECM-IDLE state without a Release Request indication, the MME shall delete any stored Paging Restriction Information for this UE and stop restricting paging accordingly and the procedure continues form the next step 3. If the Service Request message includes a Release Request indication or Reject Paging Indication, then: - If the Service Request message includes Paging Restriction Information, the MME may accept or reject the Paging Restriction Information requested by the UE based on operator policy. If the MME rejects the Paging Restriction Information, the MME removes any stored Paging Restriction Information from the UE context and discards the UE requested Paging Restriction Information. If the MME accepts the Paging Restriction Information from the UE, the MME stores the received Paging Restriction Information from the UE in the UE context. The MME informs the UE about the acceptance/rejection of the requested Paging Restriction Information in the Service Accept message. If no Paging Restriction Information is provided, no paging restrictions apply; - no S1 bearer is established (steps 4-7 are skipped); - the MME Triggers the S1 release procedure as described in clause 5.3.5 and no further steps of this procedure are executed. The MME may however trigger the NAS Authentication/Security in step 3 before releasing the UE. In the case of satellite access for Cellular IoT, the MME may verify the UE location and determine whether the PLMN is allowed to operate at the UE location, as described in clause 4.13.4. If the UE receives a Service Reject message with cause value indicating that the selected PLMN is not allowed to operate at the present UE location, the UE shall attempt to select a PLMN as specified in TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [10]. 3. NAS authentication/security procedures as defined in clause 5.3.10 on "Security function" may be performed. If the MME is configured to support RLOS and the UE indicated Attach Type "RLOS", based on local regulation and operator policy, the MME may skip the authentication and security setup, or the MME may perform authentication if security information is available or obtainable from a HSS, and continue the Service Request procedure regardless of the authentication result. 4. If there is a Service Gap timer running in the MME MM Context for the UE and the MME is not waiting for a MT paging response from the UE, the MME rejects the Service Request with an appropriate cause. In addition, MME may also provide a UE with a Mobility Management Back-off timer set to the remaining value of the Service Gap timer. The MME deletes S11-U related information in UE context if there is any, including TEID(DL) for the S11-U for Control Plane CIoT EPS Optimisation if data buffering is in the MME, ROHC context for Control Plane CIoT EPS Optimisation, etc, but not the Header Compression Configuration. The MME sends S1-AP Initial Context Setup Request (Serving GW address, S1-TEID(s) (UL), EPS Bearer QoS(s), Security Context, MME Signalling Connection Id, Handover Restriction List, CSG Membership Indication) message to the eNodeB. If there is a PDN connection established for Local IP Access, this message includes a Correlation ID for enabling the direct user plane path between the HeNB and the L-GW. If there is a PDN connection established for SIPTO at the Local Network with L-GW function collocated with the (H)eNB, this message includes a SIPTO Correlation ID for enabling the direct user plane path between the (H)eNB and the L-GW. This step activates the radio and S1 bearers for all the active EPS Bearers. The eNodeB stores the Security Context, MME Signalling Connection Id, EPS Bearer QoS(s) and S1-TEID(s) in the UE RAN context. The step is described in detail in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]. Handover Restriction List is described in clause 4.3.5.7 "Mobility Restrictions". NOTE 3: In this release of the 3GPP specification the Correlation ID and SIPTO Correlation ID is set equal to the user plane PDN GW TEID (GTP-based S5) or GRE key (PMIP-based S5) which is specified in clause 5.3.2.1 and clause 5.10.2. If the UE included support for restriction of use of Enhanced Coverage, the MME sends Enhanced Coverage Restricted parameter to the eNodeB in the S1-AP message. The MME shall only request to establish Emergency EPS Bearer if the UE is not allowed to access the cell where the UE initiated the service request procedure due to CSG access restriction. If the MME receives multiple TAIs from E-UTRAN in step 2 and determines that some, but not all, TAIs in the received list of TAIs are forbidden by subscription or by operator policy, the MME shall include the forbidden TAI(s) as in the Service Reject message. If the Service Request is performed via a hybrid cell, CSG Membership Indication indicating whether the UE is a CSG member shall be included in the S1-AP message from the MME to the RAN. Based on this information, the RAN can perform differentiated treatment for CSG and non-CSG members. If RACS is supported and MME has UE Radio Capability ID in UE context, valid for the PLMN the UE is currently in, it signals the UE Radio Capability ID to the eNodeB as defined in clause 5.11.3a. If the eNodeB does not have mapping between the specific UE Radio Capability ID and the UE radio capabilities, it shall use the procedure described in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36] to retrieve the mapping from the Core Network. 5. The eNodeB performs the radio bearer establishment procedure. The user plane security is established at this step, which is described in detail in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]. When the user plane radio bearers are setup. EPS bearer state synchronization is performed between the UE and the network, i.e. the UE shall locally remove any EPS bearer for which no radio bearers are setup and, if the radio bearer for a default EPS bearer is not established, the UE shall locally deactivate all EPS bearers associated to that default EPS bearer. 6. The uplink data from the UE can now be forwarded by eNodeB to the Serving GW. The eNodeB sends the uplink data to the Serving GW address and TEID provided in the step 4. The Serving GW forwards the uplink data to the PDN GW. 7. The eNodeB sends an S1-AP message Initial Context Setup Complete (eNodeB address, List of accepted EPS bearers, List of rejected EPS bearers, S1 TEID(s) (DL)) to the MME. This step is described in detail in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]. If the Correlation ID or SIPTO Correlation ID is included in step 4, the eNodeB shall use the included information to establish a direct user plane path to the L-GW and forward uplink data for Local IP Access or SIPTO at the Local Network with L-GW function collocated with the (H)eNB accordingly. 8. The MME sends a Modify Bearer Request message (eNodeB address, S1 TEID(s) (DL) for the accepted EPS bearers, Delay Downlink Packet Notification Request, RAT Type, MO Exception data counter) per PDN connection to the Serving GW. If the Serving GW supports Modify Access Bearers Request procedure and if there is no need for the Serving GW to send the signalling to the PDN GW, the MME may send Modify Access Bearers Request (eNodeB address(es) and TEIDs for downlink user plane for the accepted EPS bearers, Delay Downlink Packet Notification Request) per UE to the Serving GW to optimise the signalling. The Serving GW is now able to transmit downlink data towards the UE. The usage of the Delay Downlink Packet Notification Request Information Element is specified in clause 5.3.4.2 below. If the PDN GW requested UE's location and/or User CSG information and the UE's location and/or User CSG information has changed, the MME also includes the User Location Information IE and/or User CSG Information IE in this message. If ISR is activated or if the Serving Network IE has changed compared to the last reported Serving Network IE then the MME also includes the Serving Network IE in this message. If the UE Time Zone has changed compared to the last reported UE Time Zone then the MME shall include the UE Time Zone IE in this message. If the internal flag Pending Network Initiated PDN Connection Signalling is set, the MME indicates UE available for end to end signalling in the Modify Bearer Request message and reset the flag. The MME only includes the MO Exception data counter if the RRC establishment cause is set to "MO exception data" and the UE is accessing via the NB-IoT RAT. The MME maintains the MO Exception Data Counter for Serving PLMN Rate Control purposes (see clause 4.7.7.2). The MME may immediately send the MO Exception Data Counter to the Serving GW. Alternatively, in order to reduce signalling, the MME may send the MO Exception Data Counter to the Serving GW as described in TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [43]. The MME and the Serving GW clears the DL Data Buffer Expiration Time in their UE contexts if it was set, to remember that any DL data buffered for a UE using power saving functions has been delivered and to avoid any unnecessary user plane setup in conjunction with a later TAU. If a default EPS bearer is not accepted by the eNodeB, all the EPS bearers associated to that default bearer shall be treated as non-accepted bearers. The MME releases the non-accepted bearers by triggering the bearer release procedure as specified in clause 5.4.4.2. If the Serving GW receives a DL packet for a non-accepted bearer, the Serving GW drops the DL packet and does not send a Downlink Data Notification to the MME. 9. If the RAT Type has changed compared to the last reported RAT Type or if the UE's Location and/or Info IEs and/or UE Time Zone and/or if ISR is not activated and Serving Network id and/or the indication UE available for end to end signalling are present in step 8, the Serving GW shall send the Modify Bearer Request message (RAT Type, MO Exception data counter) per PDN connection to the PDN GW. User Location Information IE and/or User CSG Information IE and/or Serving Network IE and/or UE Time Zone and/or the indication UE available for end to end signalling are also included if they are present in step 8. If the Modify Bearer Request message is not sent because of above reasons and the PDN GW charging is paused, then the SGW shall send a Modify Bearer Request message with PDN Charging Pause Stop Indication to inform the PDN GW that the charging is no longer paused. Other IEs are not included in this message. If the Modify Bearer Request message is not sent because of above reasons but the MME indicated the MO Exception data counter, then the Serving Gateway should notify the PDN GW that this RRC establishment cause has been used by the MO Exception Data Counter (see TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [43]). The Serving GW indicates each use of this RRC establishment cause by the related counter on its CDR. 10. If dynamic PCC is deployed, the PDN GW interacts with the PCRF to get the PCC rule(s) according to the RAT Type by means of a PCEF initiated IP-CAN Session Modification procedure as defined in TS 23.203[ Policy and charging control architecture ] [6]. If dynamic PCC is not deployed, the PDN GW may apply local QoS policy. The PDN GW indicates each use of the RRC establishment cause "MO Exception Data" by the related counter on its CDR. 11. The PDN GW sends the Modify Bearer Response to the Serving GW. 12. The Serving GW shall return a Modify Bearer Response (Serving GW address and TEID for uplink traffic) to the MME as a response to a Modify Bearer Request message, or a Modify Access Bearers Response (Serving GW address and TEID for uplink traffic) as a response to a Modify Access Bearers Request message. If the Serving GW cannot serve the MME Request in the Modify Access Bearers Request message without S5/S8 signalling other than to unpause charging in the PDN GW or without corresponding Gxc signalling when PMIP is used over the S5/S8 interface, it shall respond to the MME with indicating that the modifications are not limited to S1-U bearers, and the MME shall repeat its request using a Modify Bearer Request message per PDN connection. If SIPTO at the Local Network is active for a PDN connection with stand-alone GW deployment and the Local Home Network ID for stand-alone accessed by the UE differs from the Local Home Network ID where the UE initiated the SIPTO@LN PDN Connection, the MME shall request disconnection of the SIPTO at the local network PDN connection(s) with the "reactivation requested" cause value according to clause 5.10.3. If the UE has no other PDN connection, the MME initiated "explicit detach with reattach required" procedure according to clause 5.3.8.3. If SIPTO at the Local Network is active for a PDN connection with collocated LGW deployment and the L-GW CN address of the cell accessed by the UE differs from the L-GW CN address of the cell where the UE initiated the SIPTO at the Local Network PDN Connection, the MME shall request disconnection of the SIPTO at the local network PDN connection(s) with the "reactivation requested" cause value according to clause 5.10.3. If the UE has no other PDN connection, the MME initiated "explicit detach with reattach required" procedure according to clause 5.3.8.3. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.3.4.1 |
4,516 | 5.33.2.1 Dual Connectivity based end to end Redundant User Plane Paths | In order to support highly reliable URLLC services, a UE may set up two redundant PDU Sessions over the 5G network, such that the 5GS sets up the user plane paths of the two redundant PDU Sessions to be disjoint. The user's subscription indicates if user is allowed to have redundant PDU Sessions and this indication is provided to SMF from UDM. NOTE 1: It is out of scope of 3GPP how to make use of the duplicate paths for redundant traffic delivery end-to-end. It is possible to rely on upper layer protocols, such as the IEEE 802.1 TSN (Time Sensitive Networking) FRER (Frame Replication and Elimination for Reliability) [83], to manage the replication and elimination of redundant packets/frames over the duplicate paths which can span both the 3GPP segments and possibly fixed network segments as well. NOTE 2: The following redundant network deployment aspects are within the responsibility of the operator and are not subject to 3GPP standardization: - RAN supports dual connectivity, and there is sufficient RAN coverage for dual connectivity in the target area. - UEs support dual connectivity. - The core network UPF deployment is aligned with RAN deployment and supports redundant user plane paths. - The underlying transport topology is aligned with the RAN and UPF deployment and supports redundant user plane paths. - The physical network topology and geographical distribution of functions also supports the redundant user plane paths to the extent deemed necessary by the operator. - The operation of the redundant user plane paths is made sufficiently independent, to the extent deemed necessary by the operator, e.g. independent power supplies. Figure 5.33.2.1-1 illustrates an example user plane resource configuration of dual PDU Sessions when redundancy is applied. One PDU Session spans from the UE via Master RAN node to UPF1 acting as the PDU Session Anchor, and the other PDU Session spans from the UE via Secondary RAN node to UPF2 acting as the PDU Session Anchor. As described in TS 37.340[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 ] [31], NG-RAN may realize redundant user plane resources for the two PDU Sessions with two NG-RAN nodes (i.e. Master RAN node and Secondary RAN node as shown in Figure 5.33.2.1-1) or a single NG-RAN node. In both cases, there is a single N1 interface towards AMF. Based on these two PDU Sessions, two independent user plane paths are set up. UPF1 and UPF2 connect to the same Data Network (DN), even though the traffic via UPF1 and UPF2 may be routed via different user plane nodes within the DN. In order to establish two redundant PDU Sessions and associate the duplicated traffic coming from the same application to these PDU Sessions, URSP as specified in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45] may be used, or alternatively the UE may perform this task independently from URSP. When URSP is used to establish two redundant PDU Sessions, duplicated traffic from the application, associated to the redundant PDU Sessions, is differentiated by two distinct traffic descriptors, each in a distinct URSP rule. These traffic descriptors need to have different DNNs, IP descriptors or non-IP descriptors (e.g. MAC address, VLAN ID), so that the two redundant PDU Sessions are matched to the Route Selection Descriptors of distinct URSP rules. These Route Selection Descriptors of distinct URSP rules may include corresponding RSNs and PDU Session Pair IDs. The Route Selection Descriptors share same PDU Session Pair ID, if included, to denote the two traffic are redundant with each other. How does UE determines the PDU Session Pair ID and/or RSN from the matched URSP rules is described in clause 6.6.2 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. When the UE performs the establishment of two redundant PDU Sessions and the duplication of traffic independently from URSP, the UE may establish two redundant PDU Sessions even when the application does not duplicate the traffic and the application does not provide two distinct traffic descriptors. In this case the UE may set the RSN and PDU Session Pair ID in the PDU Session Establishment Request message based on UE implementation. NOTE 3: As an example, the UE may use the implementation of FRER (Frame Replication and Elimination for Reliability), IEEE Std 802.1CB-2017 [83], in the UE's operating system. If the operator decides to allow UE to use its own mechanisms to determine PDU Session Pair ID and RSN (where such UE capability is known based on local PCF configuration based on e.g. deployment, terminal implementation or policies per group of UE(s)), then the PCF shall not include PDU Session Pair ID and RSN in URSP rule. The redundant user plane set up applies to both IP and Ethernet PDU Sessions. Figure 5.33.2.1-1: Example scenario for end to end redundant User Plane paths using Dual Connectivity Support of redundant PDU Sessions include: - UE initiates two redundant PDU Sessions and may provide PDU Session Pair ID (optional) and the RSN (optional). Different combinations of RSN, DNN and S-NSSAI are used for each PDU Session within a given pair of redundant PDU Sessions. Different combinations of PDU Session Pair ID, DNN and S-NSSAI are used between the different pairs of redundant PDU Session. - The UE may include a PDU Session Pair ID and/or RSN in each of the PDU Session establishment Request when it establishes redundant PDU Sessions. UE determines the PDU Session Pair ID and/or RSN based on UE local mechanism or the matched URSP rules. - The SMF determines whether the PDU Session is to be handled redundantly. The determination is based on the presence of the PDU Session Pair ID and/or RSN in the PDU Session Establishment Request or the determination is based on an indication that redundant PDU Session is required provided by PCF for the PDU Session, if dynamic PCC applies for the PDU Session or the combination of the S-NSSAI, DNN, user subscription and local policy configuration in the SMF if dynamic PCC is not used for the PDU Session. If the PDU session is to be handled redundantly and the PDU Session Pair ID was not included in the PDU Session Establishment request, the SMF uses S-NSSAI, DNN and local configuration to determine the PDU Session Pair ID. If the PDU session is to be handled redundantly and RSN was not included in the PDU Session Establishment request, the SMF uses S-NSSAI, DNN to determine the RSN value. The RSN differentiates the PDU Sessions that are handled redundantly and indicates redundant user plane requirements for the PDU Sessions in NG-RAN. - The SMF shall provide the RSN and PDU Session Pair ID to the NG-RAN for a redundant PDU Session. - Operator configuration of UPF selection ensures the appropriate UPF selection for disjoint paths. - At establishment of the PDU Sessions or at transitions to CM-CONNECTED state, the RSN parameter indicates to NG-RAN that redundant user plane resources shall be provided for the given PDU Sessions by means of dual connectivity. The PDU Session Pair ID identifies the two redundant PDU Sessions that belong together. The value of the RSN parameter and the PDU Session Pair ID indicates redundant user plane requirements for the PDU Sessions. This request for redundant handling is made by indicating the RSN to the NG-RAN node on a per PDU Session granularity. PDU Sessions associated with different RSN values shall be realized by different, redundant UP resources. Based on the RSN, the PDU Session Pair ID and RAN configuration, the NG-RAN sets up dual connectivity as defined in TS 37.340[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 ] [31] so that the sessions have end to end redundant paths. When there are multiple PDU Sessions with the RSN parameter set, of different values of RSN and the same PDU Session Pair ID, this indicates to NG-RAN that CN is requesting dual connectivity to be set up and the user plane shall be handled as indicated by the RSN parameter, the PDU Session Pair ID and the associated RAN configuration. If the RSN value and PDU Session Pair ID are provided to the NG-RAN, NG-RAN shall consider the RSN value and PDU Session Pair ID when it associates the PDU Sessions with NG-RAN UP. NOTE 4: The decision to set up dual connectivity remains in NG-RAN as defined today. NG-RAN takes into account the additional request for the dual connectivity setup provided by the CN. - Using NG-RAN local configuration, NG-RAN determines whether the request to establish RAN resources for a PDU Session is fulfilled or not considering user plane requirements indicated by the RSN parameter and the PDU Session Pair ID by means of dual connectivity. If the request to establish RAN resources for PDU Session can be fulfilled by the RAN, the PDU Session is established even if the user plane requirements indicated by RSN cannot be satisfied. The decision for each PDU Session is taken independently (i.e. rejection of a PDU Session request shall not release the previously established PDU Session). The RAN shall determine whether to notify the SMF if the RAN resources indicated by the RSN parameter and the PDU Session Pair ID can no longer be maintained and SMF can use that to determine if the PDU Session should be released. - In the case of Ethernet PDU Sessions, the SMF has the possibility to change the UPF (acting as the PSA) and select a new UPF based on the identity of the Secondary RAN node for the second PDU Session if the Secondary RAN node is modified (or added/released), using the Ethernet PDU Session Anchor Relocation procedure described in clause 4.3.5.8 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. - The SMF's charging record may reflect the RSN information. - The RSN parameter and the PDU Session Pair ID, if available, is transferred from Source NG-RAN to Target NG-RAN in the case of handover. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.33.2.1 |
4,517 | 4.16.1.4 Number of Secondary Node Additions with SN terminated bearers | a) This measurement provides the number of Secondary Node Addition attempts with SN terminated bearers. b) CC c) On transmission by the MN of an SgNB Addition Request message to SN,the request include SN terminated bearers. SGNB Addition Trigger Indication (TS 36.423[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 Application Protocol (X2AP) ] [10]) excludes SN change, inter-eNB HO, intra-eNB HO. d) Each measurement is an integer value. e) The measurement name has the form ENDC.SNAdditionAttWithSnErab. 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.4 |
4,518 | 9.11.4.14 Session-AMBR | The purpose of the Session-AMBR information element is to indicate the initial subscribed PDU session aggregate maximum bit rate when the UE establishes a PDU session or to indicate the new subscribed PDU session aggregate maximum bit rate if it is changed by the network. The Session-AMBR information element is coded as shown in figure 9.11.4.14.1 and table 9.11.4.14.1. The Session-AMBR is a type 4 information element with a length of 8 octets. Figure 9.11.4.14.1: Session-AMBR information element Table 9.11.4.14.1: Session-AMBR information element | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.11.4.14 |
4,519 | 10.5.6.3.10 PVS IPv4 Address | The purpose of the PVS IPv4 Address container contents is to indicate the PVS IPv4 Address and, optionally, the related DNN and S-NSSAI. The PVS IPv4 Address container contents are coded as shown in figure 10.5.6.3.10-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.6.3.10-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.6.3.10-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : PVS IPv4 Address Table 10.5.6.3.10-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : PVS IPv4 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.10 |
4,520 | 5.19.7.4 S-NSSAI based congestion control | S-NSSAI based congestion control is designed for the purpose of avoiding and handling of NAS signalling congestion for the UEs with back-off timer associated with or without an S-NSSAI regardless of the presence of a DNN. The UE associates the received back-off time with the S-NSSAI and DNN (i.e. no S-NSSAI and no DNN, no S-NSSAI, S-NSSAI only, an S-NSSAI and a DNN) which was included in the uplink NAS MM message carrying the corresponding NAS SM request message for the PLMN which is under congestion. S-NSSAI based congestion control is applied as follows: - If an S-NSSAI is determined as congested, then the SMF may apply S-NSSAI based congestion control towards the UE for SM requests except for those sent for the purpose of reporting 3GPP PS Data Off status change for a specific S-NSSAI and provides a back-off time and an indication of HPLMN congestion; - If the UE receives an S-NSSAI based back-off time without an indication of HPLMN congestion, the UE shall apply the S-NSSAI back-off timer only in the PLMN in which the back-off time was received. If the UE receives S-NSSAI based back-off time with an indication of HPLMN congestion, the UE shall apply the S-NSSAI based back-off timer in the PLMN in which the back-off time was received and in any other PLMN; - The SMF may release PDU Sessions belonging to a congested S-NSSAI by sending a PDU Session Release Request message towards the UE with a back-off time associated either to the S-NSSAI only (i.e. with no specific DNN) or a combination of the S-NSSAI and a specific DNN. If NWDAF is deployed, the SMF may make use of Session Management Congestion Control Experience analytics provided by NWDAF, as defined in clause 6.12 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [86], to determine back-off timer provided to UEs; NOTE: For example, the SMF can apply a short back-off timer to the UEs in the list of high-experienced UEs while the SMF can apply a long back-off timer to the UEs in the list of low-experienced UEs. - If S-NSSAI based congestion control is activated at AMF e.g. configured by OAM and an S-NSSAI is determined as congested, then the AMF applies S-NSSAI based congestion control towards the UE for UE-initiated Session Management requests. In this case, the AMF provides a NAS Transport Error message for the NAS Transport message carrying the SM message, and in the NAS Transport Error message it includes a back-off timer; If NWDAF is deployed, the AMF may determine that S-NSSAI is congested based on the network slice load level analytics defined in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [86]. - The UE behaves as follows in the PLMN where the S-NSSAI based congestion control applies when the back-off timer is running: - If the back-off timer was associated with an S-NSSAI only (i.e. not associated with an S-NSSAI and a DNN), the UE shall not initiate any Session Management procedures for the congested S-NSSAI; - If the back-off timer was associated with an S-NSSAI and a DNN, then the UE shall not initiate any Session Management procedures for that combination of S-NSSAI and DNN; - If the UE receives a network-initiated Session Management message other than PDU Session Release Command for the congested S-NSSAI, the UE shall stop this back-off timer and respond to the 5GC; - If the UE receives a PDU Session Release Command message for the congested S-NSSAI, it shall stop the back-off timer unless it receives a new back-off time from SMF; - Upon Cell/TA/PLMN/RAT change, change of untrusted non-3GPP access network or change of Access Type, the UE shall not stop the back-off timer for any S-NSSAI or any combination of S-NSSAI and DNN; - The UE is allowed to initiate the Session Management procedures for high priority access and emergency services for the S-NSSAI; - The UE is allowed to initiate the Session Management procedure for reporting Data Off status change for the S-NSSAI or the combination of S-NSSAI and DNN. - If the back-off timer is not associated to any S-NSSAI, the UE may only initiate Session Management procedures for specific S-NSSAI; - If the back-off timer is not associated to any S-NSSAI and DNN, the UE may only initiate Session Management procedures for specific S-NSSAI and DNN; - The UE is allowed to initiate PDU Session Release procedure (e.g. sending PDU Session Release Request message). The UE shall not stop the back-off timer when the related PDU Session is released; - The list above is not an exhaustive list, i.e. more details of the above actions and further conditions, if any, are specified in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]. The UE shall maintain a separate back-off timer for each S-NSSAI and for each combination of S-NSSAI and DNN that the UE may use. If UE initiates one of the Session Management procedure that are exempt from NAS congestion control, the UE indicates that the carried NAS SM message is exempted from NAS congestion control in the UL NAS Transport message as described in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]. When the S-NSSAI based congestion control is activated at AMF, if the UE indicates that the NAS SM message in the UL NAS Transport message is exempted from NAS congestion control, the AMF shall not apply S-NSSAI based congestion control on the UL NAS Transport message and shall forward the NAS SM message to the corresponding SMF with an indication that the message was received with exemption indication. The SMF evaluates whether that the NAS SM message is allowed to be exempted from S-NSSAI based congestion control. If it is not, the SMF rejects the message, e.g. the SMF shall reject PDU Session Modification received if it is not for Data Off status reporting. The back-off timer associated with an S-NSSAI or a combination of an S-NSSAI and a DNN shall only apply to congestion control for Session Management procedures when UE is in 5GS. To avoid that large amounts of UEs initiate deferred requests (almost) simultaneously, the 5GC should select the value of the back-off timer for the S-NSSAI based congestion control so that deferred requests are not synchronized. If the UE required to report 5GSM Core Network Capability change, or the Always-on PDU Session Requested indication while S-NSSAI based congestion control timer was running and was unable to initiate SM signalling, the UE defers the related SM signalling until the S-NSSAI based congestion control timer expires and initiates the necessary SM signalling after the expiry of the timer. The S-NSSAI based congestion control does not prevent the UE from sending and receiving data or initiating Service Request procedure for activating User Plane connection for a PDU Session associated to the S-NSSAI that is under the congestion control. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.19.7.4 |
4,521 | – PTRS-DownlinkConfig | The IE PTRS-DownlinkConfig is used to configure downlink phase tracking reference signals (PTRS) (see TS 38.214[ NR; Physical layer procedures for data ] [19] clause 5.1.6.3) PTRS-DownlinkConfig information element -- ASN1START -- TAG-PTRS-DOWNLINKCONFIG-START PTRS-DownlinkConfig ::= SEQUENCE { frequencyDensity SEQUENCE (SIZE (2)) OF INTEGER (1..276) OPTIONAL, -- Need S timeDensity SEQUENCE (SIZE (3)) OF INTEGER (0..29) OPTIONAL, -- Need S epre-Ratio INTEGER (0..3) OPTIONAL, -- Need S resourceElementOffset ENUMERATED { offset01, offset10, offset11 } OPTIONAL, -- Need S ..., [[ maxNrofPorts-r16 ENUMERATED {n1, n2} OPTIONAL -- Need R ]] } -- TAG-PTRS-DOWNLINKCONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,522 | 9.2.1.5 FDD (CSI measurements in case two CSI subframe sets are configured and with CRS assistance information) | The following requirements apply to UE Category ≥2. For the parameters specified in Table 9.2.1.5-1, and using the downlink physical channels specified in tables C.3.2-1 for Cell 1, C.3.3-2 for Cell 2 and Cell 3, and C.3.2-2, the reported CQI value according to RC.2 FDD in Table A.4-1 in subframes overlapping with aggressor cell ABS and non-ABS subframes shall be in the range of ±1 of the reported median more than 90% of the time. For test 1 and test 2, if the PDSCH BLER in ABS subframes using the transport format indicated by median CQI obtained by reports in CSI subframe sets CCSI,0 is less than or equal to 0.1, the BLER in ABS subframes using the transport format indicated by the (median CQI + 1) shall be greater than 0.1. If the PDSCH BLER in ABS subframes using the transport format indicated by the median CQI is greater than 0.1, the BLER in ABS subframes using transport format indicated by (median CQI – 1) shall be less than or equal to 0.1. For test 2, if the PDSCH BLER in non-ABS subframes using the transport format indicated by median CQI obtained by reports in CSI subframe sets CCSI,1 is less than or equal to 0.1, the BLER in non-ABS subframes using the transport format indicated by the (median CQI + 2) shall be greater than 0.1. If the PDSCH BLER in non-ABS subframes using the transport format indicated by the median CQI is greater than 0.1, the BLER in non-ABS subframes using transport format indicated by (median CQI – 1) shall be less than or equal to 0.1. Table 9.2.1.5-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.2.1.5 |
4,523 | 10.1 Basic Scheduler Operation | In order to utilise radio resources efficiently, MAC in gNB includes dynamic resource schedulers that allocate physical layer resources for the downlink and the uplink. In this clause, an overview of the scheduler is given in terms of scheduler operation, signalling of scheduler decisions, and measurements. Scheduler Operation: - Taking into account the UE buffer status and the QoS requirements of each UE and associated radio bearers, schedulers assign resources between UEs; - Schedulers may assign resources taking account the radio conditions at the UE identified through measurements made at the gNB and/or reported by the UE; - Resource assignment consists of radio resources (resource blocks). Signalling of Scheduler Decisions: - UEs identify the resources by receiving a scheduling (resource assignment) channel. Measurements to Support Scheduler Operation: - Uplink buffer status reports (measuring the data that is buffered in the logical channel queues in the UE) are used to provide support for QoS-aware packet scheduling; - Power headroom reports (measuring the difference between the nominal UE maximum transmit power and the estimated power for uplink transmission) are used to provide support for power aware packet scheduling. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 10.1 |
4,524 | 5.5b.1.2 Initiation | While in RRC_INACTIVE and RRC_IDLE state, the UE shall: 1> store any previously or subsequently received application layer measurement report containers associated with the measConfigAppLayerId for which no segment, or full message, has been submitted to lower layers for transmission; 1> if the memory reserved for storing application layer measurement report containers becomes full: 2> if the UE is configured with appLayerMeasPriority: 3> discard reports in priority order where reports with the lowest priority are discarded first; 2> else if no appLayerMeasPriority is configured: 3> discard reports in the order they were received, where older reports may be discarded first; 1> if the current cell when the UE transits from RRC_CONNECTED state to RRC_INACTIVE or RRC_IDLE state is part of the area indicated by qoe-AreaScope: 2> inform upper layers of being inside the area; 1> if the current cell when the UE transits from RRC_CONNECTED state to RRC_INACTIVE or RRC_IDLE state is not part of the area indicated by qoe-AreaScope: 2> inform upper layers of being outside the area. 1> if a new current cell is part of the area indicated by qoe-AreaScope and the previous cell was not part of the area indicated by qoe-AreaScope: 2> inform upper layers of being inside the area; 1> if a new current cell is not part of the area indicated by qoe-AreaScope and the previous cell was part of the area indicated by qoe-AreaScope: 2> inform upper layers of being outside the area. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.5b.1.2 |
4,525 | – MRDC-Parameters | The IE MRDC-Parameters contains the band combination parameters specific to MR-DC for a given MR-DC band combination. MRDC-Parameters information element -- ASN1START -- TAG-MRDC-PARAMETERS-START MRDC-Parameters ::= SEQUENCE { singleUL-Transmission ENUMERATED {supported} OPTIONAL, dynamicPowerSharingENDC ENUMERATED {supported} OPTIONAL, tdm-Pattern ENUMERATED {supported} OPTIONAL, ul-SharingEUTRA-NR ENUMERATED {tdm, fdm, both} OPTIONAL, ul-SwitchingTimeEUTRA-NR ENUMERATED {type1, type2} OPTIONAL, simultaneousRxTxInterBandENDC ENUMERATED {supported} OPTIONAL, asyncIntraBandENDC ENUMERATED {supported} OPTIONAL, ..., [[ dualPA-Architecture ENUMERATED {supported} OPTIONAL, intraBandENDC-Support ENUMERATED {non-contiguous, both} OPTIONAL, ul-TimingAlignmentEUTRA-NR ENUMERATED {required} OPTIONAL ]] } MRDC-Parameters-v1580 ::= SEQUENCE { dynamicPowerSharingNEDC ENUMERATED {supported} OPTIONAL } MRDC-Parameters-v1590 ::= SEQUENCE { interBandContiguousMRDC ENUMERATED {supported} OPTIONAL } MRDC-Parameters-v15g0 ::= SEQUENCE { simultaneousRxTxInterBandENDCPerBandPair SimultaneousRxTxPerBandPair OPTIONAL } MRDC-Parameters-v15n0 ::= SEQUENCE { intraBandENDC-Support-UL ENUMERATED {non-contiguous, both} OPTIONAL } MRDC-Parameters-v1620 ::= SEQUENCE { maxUplinkDutyCycle-interBandENDC-TDD-PC2-r16 SEQUENCE{ eutra-TDD-Config0-r16 ENUMERATED {n20, n40, n50, n60, n70, n80, n90, n100} OPTIONAL, eutra-TDD-Config1-r16 ENUMERATED {n20, n40, n50, n60, n70, n80, n90, n100} OPTIONAL, eutra-TDD-Config2-r16 ENUMERATED {n20, n40, n50, n60, n70, n80, n90, n100} OPTIONAL, eutra-TDD-Config3-r16 ENUMERATED {n20, n40, n50, n60, n70, n80, n90, n100} OPTIONAL, eutra-TDD-Config4-r16 ENUMERATED {n20, n40, n50, n60, n70, n80, n90, n100} OPTIONAL, eutra-TDD-Config5-r16 ENUMERATED {n20, n40, n50, n60, n70, n80, n90, n100} OPTIONAL, eutra-TDD-Config6-r16 ENUMERATED {n20, n40, n50, n60, n70, n80, n90, n100} OPTIONAL } OPTIONAL, -- R1 18-2 Single UL TX operation for TDD PCell in EN-DC tdm-restrictionTDD-endc-r16 ENUMERATED {supported} OPTIONAL, -- R1 18-2a Single UL TX operation for FDD PCell in EN-DC tdm-restrictionFDD-endc-r16 ENUMERATED {supported} OPTIONAL, -- R1 18-2b Support of HARQ-offset for SUO case1 in EN-DC with LTE TDD PCell for type 1 UE singleUL-HARQ-offsetTDD-PCell-r16 ENUMERATED {supported} OPTIONAL, -- R1 18-3 Dual Tx transmission for EN-DC with FDD PCell(TDM pattern for dual Tx UE) tdm-restrictionDualTX-FDD-endc-r16 ENUMERATED {supported} OPTIONAL } MRDC-Parameters-v1630 ::= SEQUENCE { -- R4 2-20 Maximum uplink duty cycle for FDD+TDD EN-DC power class 2 maxUplinkDutyCycle-interBandENDC-FDD-TDD-PC2-r16 SEQUENCE { maxUplinkDutyCycle-FDD-TDD-EN-DC1-r16 ENUMERATED {n30, n40, n50, n60, n70, n80, n90, n100} OPTIONAL, maxUplinkDutyCycle-FDD-TDD-EN-DC2-r16 ENUMERATED {n30, n40, n50, n60, n70, n80, n90, n100} OPTIONAL } OPTIONAL, -- R4 2-19 FDD-FDD or TDD-TDD inter-band MR-DC with overlapping or partially overlapping DL spectrum interBandMRDC-WithOverlapDL-Bands-r16 ENUMERATED {supported} OPTIONAL } MRDC-Parameters-v1700 ::= SEQUENCE { condPSCellAdditionENDC-r17 ENUMERATED {supported} OPTIONAL, scg-ActivationDeactivationENDC-r17 ENUMERATED {supported} OPTIONAL, scg-ActivationDeactivationResumeENDC-r17 ENUMERATED {supported} OPTIONAL } MRDC-Parameters-v1770 ::= SEQUENCE { -- R4 26-1: Higher Power Limit CA DC higherPowerLimitMRDC-r17 ENUMERATED {supported} OPTIONAL } -- TAG-MRDC-PARAMETERS-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,526 | 8.3.1.3.6 Minimum requirements for QCL Type C and 2 Layers Spatial Multiplexing | The requirements are specified in Table 8.3.1.3.6-3, with the additional parameters in Table 8.3.1.3.6-1 and Table 8.3.1.3.6-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 with non-coherent joint transmission from two transmission points. The test verifies that the UE configured with quasi co-location type C performs correct tracking and compensation of the frequency and time difference between two transmission points, channel parameters estimation, channel estimation and rate matching behaviour according to the ‘PDSCH RE Mapping and Quasi-Co-Location Indicator’ signalling defined in [6]. In Table 8.3.1.3.6-1, transmission point 1 (TP 1) is the serving cell transmitting PDCCH, synchronization signals, PBCH and PDSCH, and transmission point 2 (TP 2) has different Cell ID and transmits PDSCH. In the test the PDSCH is transmitted from TP1 and TP2. The downlink physical channel setup for TP 1 is according to Annex C.3.2 and for TP 2 according to Annex C.3.2. Table 8.3.1.3.6-1: Test Parameters Table 8.3.1.3.6-2: Configurations of PQI and DL transmission hypothesis for each PQI set Table 8.3.1.3.6-3: Performance Requirements | 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.3.6 |
4,527 | – CandidateTCI-State | The IE CandidateTCI-State defines a TCI states configuration which associate one or more reference signal with a corresponding quasi-colocation (QCL) type. CandidateTCI-State information element -- ASN1START -- TAG-CANDIDATETCI-STATE-START CandidateTCI-State-r18 ::= SEQUENCE { tci-StateId-r18 TCI-StateId, qcl-Type1-r18 LTM-QCL-Info-r18, qcl-Type2-r18 LTM-QCL-Info-r18 OPTIONAL, -- Need R pathlossReferenceRS-Id-r18 PathlossReferenceRS-Id-r17 OPTIONAL, -- Need R ... } LTM-QCL-Info-r18 ::= SEQUENCE { referenceSignal-r18 CHOICE { ssb-Index SSB-Index, csi-RS-Index NZP-CSI-RS-ResourceId }, qcl-Type-r18 ENUMERATED {typeA, typeB, typeC, typeD}, ... } -- TAG-CANDIDATETCI-STATE-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,528 | 13.2.2.3 Procedure for error detection and handling in SEPP | Errors can occur on an active N32-c connection or on one or more N32-f connections between two SEPPs. When an error is detected, the SEPP shall map the error to an appropriate cause code. The SEPP shall create a signalling message to inform the peer SEPP, with cause code as one of its parameters. The SEPP shall use the N32-c connection to send the signalling message to the peer SEPP. If the old N32-c connection has been terminated, it uses a new N32-c connection instead. If the error occurred in the processing of the one or more N32-f message(s), the SEPP shall include the corresponding message ID (s), obtained from the metadata section of the N32-f message, as a parameter in the signalling message. This allows the peer SEPP to identify the source message(s) (HTTP Request or Response) on which the other SEPP found the error. NOTE: Local action taken by either SEPP is out of 3GPP scope. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 13.2.2.3 |
4,529 | 6.38.2.4 Discovery | The 5G system shall enable a UE or non-3GPP device in a CPN or PIN to discover other UEs or non-3GPP devices within the same CPN or PIN subject to acess rights. The 5G system shall efficiently support service discovery mechanisms where a UE or non-3GPP device in a CPN or PIN can discover, subject to access rights: - availability and reachability of other entities (e.g. other UEs or non-3GPP devices) on the CPN or PIN; - capabilities of other entities on the CPN (e.g. PRAS, eRG) or PIN (e.g. relay UE, connection types) and/or; - services provided by other entities on the CPN or PIN (e.g. the entity is a printer).The 5G system shall support a mechanism for an Authorised Administrator to indicate whether a PIN element is discoverable by other PIN elements of the same PIN. The 5G system shall support a mechanism for an Authorised Administrator to indicate whether a PIN element is discoverable by UEs that are not members of the PIN. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.38.2.4 |
4,530 | 4.23.7.3.4 Handover Cancel | Figure 4.23.7.3.4-1: Handover Cancel procedure 1. Step 1~3 in clause 4.11.1.2.3 are performed. Case: I-SMF Change, step 4~9 are skipped for I-SMF Insertion case and I-SMF Removal case. 4. T-AMF to Target I-SMF: Nsmf_PDUSession_UpdateSMContext Request (Relocation Cancel Indication). The target AMF invokes Nsmf_PDUSession_UpdateSMContext Request (Relocation Cancel Indication) to the target I-SMF to release the SM Context and all resources allocated on the target I-SMF during preparation phase. 5a. Target I-SMF to Target I-UPF: N4 Session Release Request. The target I-SMF invokes N4 Session Release Request to target I-UPF, to release all resources allocated for the N4 session. 5b. Target I-UPF to Target I-SMF: N4 Session Release Response. 6. [Conditional] Target I-SMF to Source I-SMF: Nsmf_PDUSession_UpdateSMContext Request (Relocation Cancel Indication). If indirect forwarding tunnel is setup during preparation phase, the target I-SMF initiates Nsmf_PDUSession_UpdateSMContext Request to the source I-SMF, indicating the source I-SMF to delete the resources temporarily allocated for indirect forwarding tunnel. 7a. [Conditional] Source I-SMF to Source I-UPF: N4 Session Modification Request. The source I-SMF invokes N4 Session Modification Request to source I-UPF, to delete all resources allocated for indirect forwarding tunnel. 7b. [Conditional] Source I-UPF to Source I-SMF: N4 Session Modification Response. 8. [Conditional] Source I-SMF to Target I-SMF: Nsmf_PDUSession_UpdateSMContext Response. 9. Target I-SMF to T-AMF: Nsmf_PDUSession_UpdateSMContext Response. Case: I-SMF Insertion, step 10~18 are skipped for I-SMF Change case and I-SMF Removal case. 10. T-AMF to Target I-SMF: Nsmf_PDUSession_UpdateSMContext Request (Relocation Cancel Indication). The target AMF invokes Nsmf_PDUSession_UpdateSMContext Request (Relocation Cancel Indication) to the target I-SMF to release the SM Context and all resources allocated on the target I-SMF during preparation phase. 11a. Target I-SMF to Target I-UPF: N4 Session Release Request. The target I-SMF invokes N4 Session Release Request to target I-UPF, to release all resources allocated for the N4 session. 11b. Target I-UPF to Target I-SMF: N4 Session Release Response. 12. Target I-SMF to SMF: Nsmf_PDUSession_Update Request (PDU Session ID, Relocation Cancel Indication). The target I-SMF invokes Nsmf_PDUSession_Update Request (PDU Session ID, Relocation Cancel Indication) to the SMF, to release the PDU Session resources allocated during preparation phase, e.g. CN Tunnel for N9. 13a. [Conditional] SMF to UPF (PSA): N4 Session Modification Request. If CN Tunnel for N9 is allocated during preparation phase, i.e. the CN Tunnel for N3 and N9 are different, the SMF asks UPF (PSA) to release the CN Tunnel on N9. 13b. [Conditional] UPF(PSA) to SMF: N4 Session Modification Response. 14. SMF to Target I-SMF: Nsmf_PDUSession_Update Response. 15. [Conditional] Target I-SMF to SMF: Nsmf_PDUSession_UpdateSMContext Request (Operation Type). If indirect forwarding tunnel is setup during preparation phase, the target I-SMF initiates Nsmf_PDUSession_UpdateSMContext Request (Operation Type) to the SMF, indicating the SMF to delete the resources temporarily allocated for indirect forwarding tunnel. 16a. [Conditional] SMF to UPF (PSA): N4 Session Modification Request. The SMF invokes N4 Session Modification Request to UPF (PSA), to delete all resources allocated for indirect forwarding tunnel. 16b. [Conditional] UPF (PSA) to SMF: N4 Session Modification Response. 17. [Conditional] SMF to Target I-SMF: Nsmf_PDUSession_UpdateSMContext Response. 18. Target I-SMF to T-AMF: Nsmf_PDUSession_UpdateSMContext Response. Case: I-SMF Removal, step 19~24 are skipped for I-SMF Insertion case and I-SMF Change case. 19. T-AMF to SMF: Nsmf_PDUSession_UpdateSMContext Request (Relocation Cancel Indication). The target AMF invokes Nsmf_PDUSession_UpdateSMContext Request (Relocation Cancel Indication) to the SMF to release the SM Context and all resources allocated on the SMF during preparation phase. 20a. [Conditional] SMF to UPF (PSA): N4 Session Modification Request. If CN Tunnel for N3 is allocated during preparation phase, i.e. the CN Tunnel for N3 and N9 are different, the SMF asks UPF (PSA) to release the CN Tunnel on N3. 20b. [Conditional] UPF (PSA) to SMF: N4 Session Modification Response. 21. [Conditional] SMF to Source I-SMF: Nsmf_PDUSession_UpdateSMContext Request (Operation Type). If indirect forwarding tunnel is setup during preparation phase, the SMF initiates Nsmf_PDUSession_UpdateSMContext Request (Operation Type) to the source I-SMF, indicating the source I-SMF to delete the resources temporarily allocated for indirect forwarding tunnel. 22a. [Conditional] Source I-SMF to Source I-UPF: N4 Session Modification Request. The source I-SMF invokes N4 Session Modification Request to source I-UPF, to delete all resources allocated for indirect forwarding tunnel. 22. [Conditional] Source I-UPF to SMF: N4 Session Modification Response. 23. [Conditional] Source I-SMF to SMF: Nsmf_PDUSession_UpdateSMContext Response. 24. SMF to T-AMF: Nsmf_PDUSession_UpdateSMContext Response. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.23.7.3.4 |
4,531 | 5.2.2.4.24 Actions upon reception of SIB22 | No UE requirements related to the contents of SIB22 apply other than those specified elsewhere e.g. within procedures using the concerned system information, and/or within the corresponding field descriptions. 5.2.2.4.25 Actions upon reception of SIB23 Upon receiving SIB23, the UE shall: 1> if sl-FreqInfoList is included in sl-PosConfigCommonNR: 2> if configured to receive sidelink control information for SL-PRS measurement: 3> use the resource pool(s) indicated by sl-RxPool and/or sl-PRS-RxPool for sidelink control information reception for SL-PRS , as specified in 5.8.18.2; 2> if configured to transmit SL-PRS: 3> use the resource pool(s) indicated by sl-TxPoolSelectedNormal, sl-TxPoolExceptional, sl-PRS-TxPoolSelectedNormal or sl-PRS-TxPoolExceptional for SL-PRS transmission, as specified in 5.8.18.3; 3> perform CBR measurement on the transmission resource pool(s) indicated by sl-TxPoolSelectedNormal, sl-TxPoolExceptional, sl-PRS-TxPoolSelectedNormal or sl-PRS-TxPoolExceptional for SL-PRS transmission, as specified in 5.5.3.1; 3> use the synchronization configuration parameters for NR sidelink positioning on frequencies included in sl-FreqInfoList, as specified in 5.8.5; The UE should discard any stored segments for SIB23 if the complete SIB23 has not been assembled within a period of 3 hours. The UE shall discard any stored segments for SIB23 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.24 |
4,532 | 5.3.3.3.2 NAS signalling connection establishment | NAS signalling connection establishment function is provided by the UE and the AMF to establish a NAS signalling connection for a UE in CM-IDLE state. The AMF shall provide the list of recommended cells/ TAs / NG-RAN node identifiers for paging, if the NG-RAN had provided that information in an earlier AN Release Procedure in the AN (see clause 4.2.6 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]). When the UE in CM-IDLE state needs to transmit an NAS message, the UE shall initiate a Service Request, a Registration or a Deregistration procedure to establish a NAS signalling connection to the AMF as specified in clauses 4.2.2 and 4.2.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. If the NAS signalling connection is to be established via an NG-RAN node, but the AMF detects that this UE has already established a NAS signalling connection via old NG-RAN node, the AMF shall release the old established NAS signalling connection by triggering AN Release Procedure. Based on UE preferences, UE subscription, Mobility Pattern and network configuration, the AMF may keep the NAS signalling connection until the UE de-registers from the network. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.3.3.3.2 |
4,533 | 6.5 Access link data integrity 6.5.1 General | Most control signalling information elements that are sent between the MS and the network are considered sensitive and must be integrity protected. A message authentication function shall be applied on these signalling information elements transmitted between the ME and the RNC. After the RRC connection establishment and execution of the security mode set-up procedure, all dedicated MS <–> network control signalling messages (e.g. RRC, MM, CC, GMM, and SM messages) shall be integrity protected. The Mobility Management layer in the MS supervises that the integrity protection is started (see section 6.4.5). All signalling messages except the following ones shall then be integrity protected: HANDOVER TO UTRAN COMPLETE Paging Type 1 PUSCH CAPACITY REQUEST PHYSICAL SHARED CHANNEL ALLOCATION RRC Connection Request RRC Connection Setup RRC Connection Setup Complete RRC Connection Reject RRC CONNECTION RELEASE (CCCH only) SYSTEM INFORMATION (BROADCAST INFORMATION) SYSTEM INFORMATION CHANGE INDICATION TRANSPORT FORMAT COMBINATION CONTROL (TM DCCH only) | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 6.5 |
4,534 | 9.2.3.2 TDD | The following requirements apply to UE Category ≥2. For the parameters specified in table 9.2.3.2-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.2.3.2-1: PUCCH 1-1 submode 1 static test (TDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.2.3.2 |
4,535 | 4.2.1.1 Number of initial E-RABs attempted to setup | a) This measurement provides the number of initial E-RABs attempted to setup. The measurement is split into subcounters per E-RAB QoS level (QCI). b) CC c) On receipt by the eNodeB/RN of an INITIAL CONTEXT SETUP REQUEST message, each requested E-RAB in the message is added to the relevant measurement per QCI, the possible QCIs are included in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [9]. The sum of all supported per QCI measurements shall equal the total number of E-RABs attempted to setup. In case only a subset of per QCI measurements is supported, a sum subcounter will be provided first. d) Each measurement is an integer value. The number of measurements is equal to the number of QCIs plus a possible sum value identified by the .sum suffix. e) The measurement name has the form ERAB.EstabInitAttNbr.QCI where QCI identifies the E-RAB level quality of service class. f) EUtranCellFDD EUtranCellTDD g) Valid for packet switched traffic h) EPS i) One usage of this measurement is to support the coverage ratio (CR) calculation for EE coverage area determination in [21]. | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.2.1.1 |
4,536 | 7.2 Centralised UAV traffic management | The UTM shall be able to coordinate the route data provided in the authorisation to operate and change it if needed. The 3GPP system shall enable a UTM to send route modification information to a UAS with a latency of less than [500ms]. The 3GPP system shall enable a UTM to send a notification to a UAV controller with a latency of less than [500ms]. The 3GPP system shall be able to enforce the authorisation for an in-flight UAS to operate basing on UAS subscription information or under the instructions from UTM (e.g. by enabling dedicated control channel between UAS and UTM or by enabling or disabling communication between the UAV and UAV controller). | 3GPP TS 22.825 | Study on Remote Identification of Unmanned Aerial Systems (UAS) | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 7.2 |
4,537 | 9.3.1.2.1 FDD | For the parameters specified in Table 9.3.1.2.1-1, and using the downlink physical channels specified in Annex C.3.2, the minimum requirements are specified in Table 9.3.1.2.1-2 and by the following a) a sub-band differential CQI offset level of 0 shall be reported at least % of the time but less than % for each sub-band; b) the ratio of the throughput obtained when transmitting on a randomly selected sub-band among the sub-bands with the highest differential CQI offset level the corresponding TBS and that obtained when transmitting the TBS indicated by the reported wideband CQI median on a randomly selected sub-band in set S shall be ≥ ; c) when transmitting on a randomly selected sub-band among the sub-bands with the highest differential CQI offset level the corresponding TBS, the average BLER for the indicated transport formats shall be greater or equal to 0.05. The requirements only apply for sub-bands of full size and the random scheduling across the sub-bands is done by selecting a new sub-band in each TTI for FDD, each available downlink transmission instance for TDD. Sub-bands of a size smaller than full size are excluded from the test. Table 9.3.1.2.1-1 Sub-band test for FDD Table 9.3.1.2.1-2 Minimum requirement (FDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.3.1.2.1 |
4,538 | 16.9.8 Inter-UE Coordination (IUC) | The SL UE can support inter-UE coordination (IUC) in Mode 2, whereby a UE sends information about resources to a peer UE, which the peer UE then uses for resource (re)selection. The following schemes of inter-UE coordination are supported: - IUC scheme 1, where the IUC information sent from a UE to a peer UE is the preferred or non-preferred resources for the peer UE's transmission, and - IUC scheme 2, where the IUC information sent from a UE to a peer UE is the presence of expected/potential resource conflict on the resources indicated by the peer UE's SCI. In scheme 1, the transmission of IUC information from a UE can be triggered by a condition at this UE, or by an explicit request from a peer UE. The UE determines the set of resources reserved by other UEs or slots where the UE, when it is the intended receiver of the peer UE, does not expect to perform SL reception from the peer UE due to half-duplex operation. The UE uses these resources as the set of non-preferred resources, or excludes these resources to determine a set of preferred resources and sends the preferred/non-preferred resources to the peer UE. Regarding the IUC information received from the UE, the peer UE's resources for resource (re)selection can be based on both the peer UE's sensing results (if available) and the IUC information, or it can be based only on the IUC information. For scheme 1, MAC CE and second-stage SCI or MAC CE only can be used to send IUC information. For IUC information transmission triggered by an explicit request, both the explicit request and the IUC information are transmitted in unicast manner. For IUC information transmission triggered by a condition other than the explicit request, the IUC information indicating preferred resource set is transmitted in unicast manner, and the IUC information indicating non-preferred resource set is transmitted in unicast, groupcast or broadcast manner. In scheme 2, a UE determines the expected/potential resource conflict within the resources indicated by a peer UE's SCI as either resources reserved by other UEs and identified by the UE as fully/partially overlapping with the resources indicated by the peer UE's SCI, or as slots where the UE is the intended receiver of the peer UE and does not expect to perform SL reception on those slots due to half-duplex operation. The peer UE uses the conflicting resources to determine the resources to be reselected and exclude the conflicting resources from the reselected resources. For scheme 2, PSFCH is used to send IUC information. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.9.8 |
4,539 | 5.4.11.7 Tracking Area handling for NR satellite access | In the case of NR satellite access with moving cells, in order to ensure that each TA is Earth-stationary even if the radio cells are moving across the Earth's surface, the NG-RAN may change the TAC values that are broadcast in a cell's system information as the cell moves, as described in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27] and TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [28]. NG-RAN may broadcast in a cell a single TAC per PLMN and change that TAC value as the cell moves. Alternatively, the NG-RAN may broadcast in a cell more than one TAC for a PLMN and add or remove TAC values as the cell moves. The NG-RAN provides either the single broadcast TAI or all broadcast TAIs corresponding to the Selected PLMN as described in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [34] to the AMF as part of the ULI, whenever the ULI is included in the NGAP message as described in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [34]. The NG-RAN indicates, if known, also the TAI where the UE is geographically located. NOTE: The AMF may take the TAI where the UE is geographically located into account to generate a suitable Registration Area for the UE. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.4.11.7 |
4,540 | E.1 Delegated SMF discovery in the Home Routed scenario | Figure E.1: Delegated Discovery of SMF in the Home Routed Scenario 1. The AMF sends Nnrf_NFDiscovery Request to the V-NRF. The AMF may indicate the maximum number of H-SMF instances to be returned by the NRF. 2. The NRF in VPLMN and NRF in HPLMN interact using the Nnrf_NFDiscovery service. See step 2 in clause 4.17.5. 3. The AMF gets Nnrf_NFDiscovery service response with one or more profile(s) of SMF(s) in HPLMN. 4. The AMF selects an SMF instance in HPLMN (H-SMF endpoint). 5. The AMF builds a Nsmf_PDUSession_CreateSMContext Request that includes the endpoint (e.g. URI) of the selected H-SMF in the body of the request. If the AMF supports delegated SMF discovery and is configured to apply it, the AMF sends the Nsmf_PDUSession_CreateSMContext Request with Discovery & Selection parameters to the selected SCP in the VPLMN. Discovery & Selection parameters include S-NSSAI, UE location (TAI), i.e. parameter for V-SMF selection. 6. [Optional] The SCP in VPLMN sends Nnrf_NFDiscovery Request to the V-NRF using Discovery & Selection parameters received from AMF. 7. [Optional] The SCP in VPLMN gets Nnrf_NFDiscovery service response with profile(s) of SMF(s) in VPLMN. 8. The SCP in VPLMN selects an SMF instance in VPLMN (V-SMF), which supports the Discovery & Selection parameters received earlier from the AMF. 9. The SCP in VPLMN forwards the Nsmf_PDUSession_CreateSMContext Request received from the AMF to the selected SMF instance in VPLMN. 10. If the V-SMF does not support delegated SMF discovery or is not configured to apply it (Case A), the V-SMF sends Nsmf_PDUSession_Create Request directly to the H-SMF. Otherwise (Case B), the V-SMF sends the Nsmf_PDUSession_Create Request to the SCP in VPLMN but adds Discovery & Selection parameter set to H-SMF endpoint received from the AMF. In both cases, the V-SMF uses the received endpoint (e.g. URI) of the selected H-SMF to construct the target destination to be addressed. NOTE: The Nsmf_PDUSession_Create Request sent by the V-SMF in Case A and in Case B is the same apart from the Discovery & Selection parameter. The Nsmf_PDUSession_Create Request received by the H-SMF in Case A and in Case B is the same. 11. The SCP in VPLMN sends a Nsmf_PDUSession_Create Request to the selected SMF instance in HPLMN indicated in step 10. When the V-SMF responds to AMF with Nsmf_PDUSession_CreateSMContext Response as in clause 4.3.2.2.2 in step 3b, if the AMF has not stored the SMF Service Area for the V-SMF, the AMF shall obtain the SMF Service Area for the concerned V-SMF from the NRF using the Nnrf_NFManagement_NFStatusSubscribe service operation. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | E.1 |
4,541 | 8.9.4.2.2 Enhanced Downlink Control Channel Performance Requirement Type A - 4 Tx Antenna Port with Non-Colliding CRS Dominant Interferer | The purpose of this test is to verify the Enhanced Downlink Control Channel Performance Requirement Type A for PDCCH/PCFICH with 4 transmit antennas for the case of dominant interferer with the non-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.9.4.2.2-1, the average probability of a missed downlink scheduling grant (Pm-dsg) shall be below the specified value in Table 8.9.4.2.2-2. In Table 8.9.4.2.2-1, Cell 1 is the serving cell, and Cell 2 and Cell 3 are the aggressor cells. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1, Cell 2 and Cell 3, respectively. The CRS assistance information [7] is provided and includes information on Cell 2 and Cell 3. Table 8.9.4.2.2-1: Test Parameters for PDCCH/PCFICH Table 8.9.4.2.2-2: Minimum Performance for PDCCH/PCFICH for Enhanced Downlink Control Channel Performance Requirement Type A | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.9.4.2.2 |
4,542 | – ConfiguredGrantConfig | The IE ConfiguredGrantConfig is used to configure uplink transmission without dynamic grant according to two possible schemes. The actual uplink grant may either be configured via RRC (type1) or provided via the PDCCH (addressed to CS-RNTI) (type2). Multiple Configured Grant configurations may be configured in one BWP of a serving cell. ConfiguredGrantConfig information element -- ASN1START -- TAG-CONFIGUREDGRANTCONFIG-START ConfiguredGrantConfig ::= SEQUENCE { frequencyHopping ENUMERATED {intraSlot, interSlot} OPTIONAL, -- Need S cg-DMRS-Configuration DMRS-UplinkConfig, mcs-Table ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need S mcs-TableTransformPrecoder ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need S uci-OnPUSCH SetupRelease { CG-UCI-OnPUSCH } OPTIONAL, -- Need M resourceAllocation ENUMERATED { resourceAllocationType0, resourceAllocationType1, dynamicSwitch }, rbg-Size ENUMERATED {config2} OPTIONAL, -- Need S powerControlLoopToUse ENUMERATED {n0, n1}, p0-PUSCH-Alpha P0-PUSCH-AlphaSetId, transformPrecoder ENUMERATED {enabled, disabled} OPTIONAL, -- Need S nrofHARQ-Processes INTEGER(1..16), repK ENUMERATED {n1, n2, n4, n8}, repK-RV ENUMERATED {s1-0231, s2-0303, s3-0000} OPTIONAL, -- Need R periodicity ENUMERATED { sym2, sym7, sym1x14, sym2x14, sym4x14, sym5x14, sym8x14, sym10x14, sym16x14, sym20x14, sym32x14, sym40x14, sym64x14, sym80x14, sym128x14, sym160x14, sym256x14, sym320x14, sym512x14, sym640x14, sym1024x14, sym1280x14, sym2560x14, sym5120x14, sym6, sym1x12, sym2x12, sym4x12, sym5x12, sym8x12, sym10x12, sym16x12, sym20x12, sym32x12, sym40x12, sym64x12, sym80x12, sym128x12, sym160x12, sym256x12, sym320x12, sym512x12, sym640x12, sym1280x12, sym2560x12 }, configuredGrantTimer INTEGER (1..64) OPTIONAL, -- Need R rrc-ConfiguredUplinkGrant SEQUENCE { timeDomainOffset INTEGER (0..5119), timeDomainAllocation INTEGER (0..15), frequencyDomainAllocation BIT STRING (SIZE(18)), antennaPort INTEGER (0..31), dmrs-SeqInitialization INTEGER (0..1) OPTIONAL, -- Need R precodingAndNumberOfLayers INTEGER (0..63), srs-ResourceIndicator INTEGER (0..15) OPTIONAL, -- Need R mcsAndTBS INTEGER (0..31), frequencyHoppingOffset INTEGER (1.. maxNrofPhysicalResourceBlocks-1) OPTIONAL, -- Need R pathlossReferenceIndex INTEGER (0..maxNrofPUSCH-PathlossReferenceRSs-1), ..., [[ pusch-RepTypeIndicator-r16 ENUMERATED {pusch-RepTypeA,pusch-RepTypeB} OPTIONAL, -- Need M frequencyHoppingPUSCH-RepTypeB-r16 ENUMERATED {interRepetition, interSlot} OPTIONAL, -- Cond RepTypeB timeReferenceSFN-r16 ENUMERATED {sfn512} OPTIONAL -- Need S ]], [[ pathlossReferenceIndex2-r17 INTEGER (0..maxNrofPUSCH-PathlossReferenceRSs-1) OPTIONAL, -- Need R srs-ResourceIndicator2-r17 INTEGER (0..15) OPTIONAL, -- Need R precodingAndNumberOfLayers2-r17 INTEGER (0..63) OPTIONAL, -- Need R timeDomainAllocation-v1710 INTEGER (16..63) OPTIONAL, -- Need M timeDomainOffset-r17 INTEGER (0..40959) OPTIONAL, -- Need R cg-SDT-Configuration-r17 CG-SDT-Configuration-r17 OPTIONAL -- Need M ]], [[ srs-ResourceSetId-r18 SRS-ResourceSetId OPTIONAL, -- Need R cg-mIAB-Configuration-r18 CG-mIAB-Configuration-r18 OPTIONAL, -- Cond RACHlessHO cg-LTM-Configuration-r18 CG-LTM-Configuration-r18 OPTIONAL, -- Cond LTM cg-SDT-PeriodicityExt-r18 ENUMERATED { sym1x14x1280, sym2x14x1280, sym4x14x1280 , sym8x14x1280, sym16x14x1280, sym32x14x1280, sym48x14x1280, sym64x14x1280, sym96x14x1280, sym128x14x1280, sym192x14x1280, sym240x14x1280, sym256x14x1280, sym384x14x1280, sym472x14x1280, sym480x14x1280, sym512x14x1280, sym768x14x1280, sym944x14x1280, sym960x14x1280, sym1408x14x1280, sym1536x14x1280, sym1888x14x1280, sym1920x14x1280, sym2816x14x1280, sym3072x14x1280, sym3776x14x1280, sym5632x14x1280, sym6144x14x1280, sym7552x14x1280, sym7680x14x1280, sym11264x14x1280, sym15104x14x1280, sym15360x14x1280, sym22528x14x1280, sym30208x14x1280, sym45056x14x1280, sym60416x14x1280, sym90112x14x1280, sym180224x14x1280, sym4x12x1280, sym8x12x1280, sym16x12x1280, sym32x12x1280, sym192x12x1280, sym384x12x1280, sym960x12x1280, sym1888x12x1280, sym3776x12x1280, sym5632x12x1280, sym11264x12x1280 } OPTIONAL, -- Need R timeReferenceHyperSFN-r18 INTEGER (0..1023) OPTIONAL, -- Need R cg-NTN-RACH-Less-Configuration-r18 CG-NTN-RACH-Less-Configuration-r18 OPTIONAL -- Cond RACH-lessHO ]] } OPTIONAL, -- Need R ..., [[ cg-RetransmissionTimer-r16 INTEGER (1..64) OPTIONAL, -- Need R cg-minDFI-Delay-r16 ENUMERATED {sym7, sym1x14, sym2x14, sym3x14, sym4x14, sym5x14, sym6x14, sym7x14, sym8x14, sym9x14, sym10x14, sym11x14, sym12x14, sym13x14, sym14x14,sym15x14, sym16x14 } OPTIONAL, -- Need R cg-nrofPUSCH-InSlot-r16 INTEGER (1..7) OPTIONAL, -- Need R cg-nrofSlots-r16 INTEGER (1..40) OPTIONAL, -- Need R cg-StartingOffsets-r16 CG-StartingOffsets-r16 OPTIONAL, -- Need R cg-UCI-Multiplexing-r16 ENUMERATED {enabled} OPTIONAL, -- Need R cg-COT-SharingOffset-r16 INTEGER (1..39) OPTIONAL, -- Need R betaOffsetCG-UCI-r16 INTEGER (0..31) OPTIONAL, -- Need R cg-COT-SharingList-r16 SEQUENCE (SIZE (1..1709)) OF CG-COT-Sharing-r16 OPTIONAL, -- Need R harq-ProcID-Offset-r16 INTEGER (0..15) OPTIONAL, -- Need M harq-ProcID-Offset2-r16 INTEGER (0..15) OPTIONAL, -- Need M configuredGrantConfigIndex-r16 ConfiguredGrantConfigIndex-r16 OPTIONAL, -- Cond CG-List configuredGrantConfigIndexMAC-r16 ConfiguredGrantConfigIndexMAC-r16 OPTIONAL, -- Cond CG-IndexMAC periodicityExt-r16 INTEGER (1..5120) OPTIONAL, -- Need R startingFromRV0-r16 ENUMERATED {on, off} OPTIONAL, -- Need R phy-PriorityIndex-r16 ENUMERATED {p0, p1} OPTIONAL, -- Need R autonomousTx-r16 ENUMERATED {enabled} OPTIONAL -- Cond LCH-BasedPrioritization ]], [[ cg-betaOffsetsCrossPri0-r17 SetupRelease { BetaOffsetsCrossPriSelCG-r17 } OPTIONAL, -- Need M cg-betaOffsetsCrossPri1-r17 SetupRelease { BetaOffsetsCrossPriSelCG-r17 } OPTIONAL, -- Need M mappingPattern-r17 ENUMERATED {cyclicMapping, sequentialMapping} OPTIONAL, -- Cond SRSsets sequenceOffsetForRV-r17 INTEGER (0..3) OPTIONAL, -- Need R p0-PUSCH-Alpha2-r17 P0-PUSCH-AlphaSetId OPTIONAL, -- Need R powerControlLoopToUse2-r17 ENUMERATED {n0, n1} OPTIONAL, -- Need R cg-COT-SharingList-r17 SEQUENCE (SIZE (1..50722)) OF CG-COT-Sharing-r17 OPTIONAL, -- Need R periodicityExt-r17 INTEGER (1..40960) OPTIONAL, -- Need R repK-v1710 ENUMERATED {n12, n16, n24, n32} OPTIONAL, -- Need R nrofHARQ-Processes-v1700 INTEGER(17..32) OPTIONAL, -- Need M harq-ProcID-Offset2-v1700 INTEGER (16..31) OPTIONAL, -- Need R configuredGrantTimer-v1700 INTEGER(33..288) OPTIONAL, -- Need R cg-minDFI-Delay-v1710 INTEGER (238..3584) OPTIONAL -- Need R ]], [[ harq-ProcID-Offset-v1730 INTEGER (16..31) OPTIONAL, -- Need R cg-nrofSlots-r17 INTEGER (1..320) OPTIONAL -- Need R ]], [[ applyIndicatedTCI-State-r18 ENUMERATED {first, second, both} OPTIONAL, -- Need R disableCG-RetransmissionMonitoring-r18 ENUMERATED {true} OPTIONAL, -- Need R nrofSlotsInCG-Period-r18 INTEGER (2..32) OPTIONAL, -- Need R nrofBitsInUTO-UCI-r18 INTEGER (3..8) OPTIONAL, -- Need R betaOffsetUTO-UCI-r18 INTEGER (0..31) OPTIONAL -- Need R ]] } CG-UCI-OnPUSCH ::= CHOICE { dynamic SEQUENCE (SIZE (1..4)) OF BetaOffsets, semiStatic BetaOffsets } CG-COT-Sharing-r16 ::= CHOICE { noCOT-Sharing-r16 NULL, cot-Sharing-r16 SEQUENCE { duration-r16 INTEGER (1..39), offset-r16 INTEGER (1..39), channelAccessPriority-r16 INTEGER (1..4) } } CG-COT-Sharing-r17 ::= CHOICE { noCOT-Sharing-r17 NULL, cot-Sharing-r17 SEQUENCE { duration-r17 INTEGER (1..319), offset-r17 INTEGER (1..319) } } CG-StartingOffsets-r16 ::= SEQUENCE { cg-StartingFullBW-InsideCOT-r16 SEQUENCE (SIZE (1..7)) OF INTEGER (0..6) OPTIONAL, -- Need R cg-StartingFullBW-OutsideCOT-r16 SEQUENCE (SIZE (1..7)) OF INTEGER (0..6) OPTIONAL, -- Need R cg-StartingPartialBW-InsideCOT-r16 INTEGER (0..6) OPTIONAL, -- Need R cg-StartingPartialBW-OutsideCOT-r16 INTEGER (0..6) OPTIONAL -- Need R } BetaOffsetsCrossPriSelCG-r17 ::= CHOICE { dynamic-r17 SEQUENCE (SIZE (1..4)) OF BetaOffsetsCrossPri-r17, semiStatic-r17 BetaOffsetsCrossPri-r17 } CG-SDT-Configuration-r17 ::= SEQUENCE { cg-SDT-RetransmissionTimer INTEGER (1..64) OPTIONAL, -- Need R sdt-SSB-Subset-r17 CHOICE { shortBitmap-r17 BIT STRING (SIZE (4)), mediumBitmap-r17 BIT STRING (SIZE (8)), longBitmap-r17 BIT STRING (SIZE (64)) } OPTIONAL, -- Need S sdt-SSB-PerCG-PUSCH-r17 ENUMERATED {oneEighth, oneFourth, half, one, two, four, eight, sixteen} OPTIONAL, -- Need M sdt-P0-PUSCH-r17 INTEGER (-16..15) OPTIONAL, -- Need M sdt-Alpha-r17 ENUMERATED {alpha0, alpha04, alpha05, alpha06, alpha07, alpha08, alpha09, alpha1} OPTIONAL, -- Need M sdt-DMRS-Ports-r17 CHOICE { dmrsType1-r17 BIT STRING (SIZE (8)), dmrsType2-r17 BIT STRING (SIZE (12)) } OPTIONAL, -- Need M sdt-NrofDMRS-Sequences-r17 INTEGER (1..2) OPTIONAL -- Need M } CG-mIAB-Configuration-r18 ::= SEQUENCE { mIAB-RSRP-ThresholdSSB-r18 RSRP-Range, mIAB-SSB-PerCG-PUSCH-r18 ENUMERATED {oneEighth, oneFourth, half, one, two, four, eight, sixteen}, mIAB-SSB-Subset-r18 CHOICE { shortBitmap-r18 BIT STRING (SIZE (4)), mediumBitmap-r18 BIT STRING (SIZE (8)), longBitmap-r18 BIT STRING (SIZE (64)) }, mIAB-DMRS-Ports-r18 CHOICE { dmrsType1-r18 BIT STRING (SIZE (8)), dmrsType2-r18 BIT STRING (SIZE (12)) } OPTIONAL, -- Need R mIAB-NrofDMRS-Sequences-r18 INTEGER (1..2) OPTIONAL -- Need R } CG-LTM-Configuration-r18 ::= SEQUENCE { cg-LTM-RetransmissionTimer-r18 INTEGER (1..64) OPTIONAL, -- Need R ltm-SSB-Subset-r18 CHOICE { shortBitmap-r18 BIT STRING (SIZE (4)), mediumBitmap-r18 BIT STRING (SIZE (8)), longBitmap-r18 BIT STRING (SIZE (64)) } OPTIONAL, -- Need S ltm-SSB-PerCG-PUSCH-r18 ENUMERATED {oneEighth, oneFourth, half, one, two, four, eight, sixteen} OPTIONAL, -- Need M sdt-P0-PUSCH-r18 INTEGER (-16..15) OPTIONAL, -- Need M sdt-Alpha-r18 ENUMERATED {alpha0, alpha04, alpha05, alpha06, alpha07, alpha08, alpha09, alpha1} OPTIONAL, -- Need M ltm-DMRS-Ports-r18 CHOICE { dmrsType1-r18 BIT STRING (SIZE (8)), dmrsType2-r18 BIT STRING (SIZE (12)) } OPTIONAL, -- Need M ltm-NrofDMRS-Sequences-r18 INTEGER (1..2) OPTIONAL -- Need M } CG-NTN-RACH-Less-Configuration-r18 ::= SEQUENCE { ntn-cg-RACH-less-RetransmissionTimer INTEGER (1..64) OPTIONAL, -- Need R ntn-RSRP-ThresholdSSB-r18 RSRP-Range, ntn-SSB-PerCG-PUSCH-r18 ENUMERATED {oneEighth, oneFourth, half, one, two, four, eight, sixteen}, ntn-SSB-Subset-r18 CHOICE { shortBitmap-r18 BIT STRING (SIZE (4)), mediumBitmap-r18 BIT STRING (SIZE (8)), longBitmap-r18 BIT STRING (SIZE (64)) } OPTIONAL, -- Need R ntn-DMRS-Ports-r18 CHOICE { dmrsType1-r18 BIT STRING (SIZE (8)), dmrsType2-r18 BIT STRING (SIZE (12)) } OPTIONAL, -- Need R ntn-NrofDMRS-Sequences-r18 INTEGER (1..2) OPTIONAL -- Need R } -- TAG-CONFIGUREDGRANTCONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,543 | 5.33 Support for Ultra Reliable Low Latency Communication 5.33.1 General | The following features described in 5.33 may be used to enhance 5GS to support Ultra Reliable Low Latency Communication (URLLC): - Redundant transmission for high reliability communication. In this Release, URLLC applies to 3GPP access only. When a PDU Session is to serve URLLC QoS Flow, the UE and SMF should establish the PDU Session as always-on PDU Session as described in clause 5.6.13. NOTE 1: How the UE knows whether a PDU Session is to serve a URLLC QoS Flow when triggering PDU Session establishment is up to UE implementation. NOTE 2: No additional functionality is specified for URLLC in order to support Home Routed roaming scenario in this Release. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.33 |
4,544 | K.3 Mobility management information elements. | For the mobility management information elements listed below, the default coding of the information element identifier bits is summarized in table K.3/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Table K.3/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Default information element identifier coding for mobility management information elements NOTE: These values were allocated but never used in earlier versions of the protocol | 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 | K.3 |
4,545 | 10.5.6.3 Protocol configuration options 10.5.6.3.1 General | The purpose of the protocol configuration options information element is to: - transfer external network protocol options associated with a PDP context activation, and - transfer additional (protocol) data (e.g. configuration parameters, error codes or messages/events) associated with an external protocol or an application. The protocol configuration options is a type 4 information element with a minimum length of 3 octets and a maximum length of 253 octets. The protocol configuration options information element is coded as shown in figure 10.5.136/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.154/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.136/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Protocol configuration options information element Table 10.5.154/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Protocol configuration options 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.6.3 |
4,546 | 5.15.11.3.3 HPLMN NSAC Admission Mode | In this admission mode the AMF or SMF in VPLMN interacts with HPLMN for admission, both for number of registered UEs or the number of LBO PDU sessions respectively. For each S-NSSAI of the HPLMN that is subject to NSAC and mapped to a corresponding S-NSSAI of the VPLMN, AMF performs NSAC admission for the number of registered UEs with the HPLMN central or primary NSACF for all inbound roamers from that HPLMN when they register in this VPLMN. The AMF discovers the HPLMN primary or central NSACF or be configured with the needed information. For each S-NSSAI of the HPLMN that is subject to NSAC and mapped to a corresponding S-NSSAI of the VPLMN, every SMF in this VPLMN performs NSAC admission for the number of LBO PDU sessions with the HPLMN central or primary NSACF for all inbound roamers from that HPLMN when they initiate an LBO PDU session. The SMFs discover the HPLMN primary or central NSACF or be configured with the needed information. For each S-NSSAI of the HPLMN that is subject to NSAC, the SMF performs NSAC according to the principles described in clause 5.15.11.2 for home routed PDU sessions. In the HPLMN NSAC admission mode, the primary NSACF or central NSACF in HPLMN determines whether the NSAC admission request for a roaming UE is accepted or rejected. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.15.11.3.3 |
4,547 | 5.34.2.2 Non-roaming architecture | Figure 5.34.2.2-1 depicts the non-roaming architecture with an I-SMF insertion to the PDU Session without UL-CL/BP, using reference point representation. NOTE 1: N16a is the interface between SMF and I-SMF. NOTE 2: N38 is the interface between I-SMFs. Figure 5.34.2.2-1: Non-roaming architecture with I-SMF insertion to the PDU Session in reference point representation, with no UL-CL/BP Figure 5.34.2.2-2 depicts the non-roaming architecture for an I-SMF insertion to the PDU Session with UL-CL/BP, using reference point representation. Figure 5.34.2.2-2: Non-roaming architecture with I-SMF insertion to the PDU Session in reference point representation, with UL-CL/BP | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.34.2.2 |
4,548 | 4.5 Connection management sublayer service provision | The concept of MM connection is introduced in this subclause. This concept is mainly a descriptive tool: The establishment of an MM connection by the network can be local (i.e. it is achieved by the transmission of the first CM layer message and without the transmission of any MM layer messages) or can be achieved by the transmission of a CM SERVICE PROMPT message (eg. in the case of certain ring back services). The release of an MM connection by the network or by the mobile station is always local, i.e. these purposes can be achieved without sending any MM messages over the radio interface. (On the contrary, establishment of an MM connection by the mobile station requires the sending of MM messages over the radio interface. An exception is VGCS, where an MM connection will be established as result of an uplink access procedure (see subclause 3.7.2.1.1in 3GPP TS 44.018[ None ] [84]).) The Mobility Management (MM) sublayer is providing connection management services to the different entities of the upper Connection management (CM) sublayer (see 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [20]). It offers to a CM entity the possibility to use an MM connection for the exchange of information with its peer entity. An MM connection is established and released on request from a CM entity. Different CM entities communicate with their peer entity using different MM connections. Several MM connections may be active at the same time. An MM connection requires an RR connection. All simultaneous MM connections for a given mobile station use the same RR connection. In the following subclauses, the procedures for establishing, re-establishing, maintaining, and releasing an MM connection are described, usually separately for the mobile station and the network side. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.5 |
4,549 | 5.5.3.2.4 Normal and periodic tracking area updating procedure accepted by the network | If the tracking area update request has been accepted by the network, the MME shall send a TRACKING AREA UPDATE ACCEPT message to the UE. If the MME assigns a new GUTI for the UE, a GUTI shall be included in the TRACKING AREA UPDATE ACCEPT message. If the MME includes the GUTI IE in the TRACKING AREA UPDATE ACCEPT message, the MME shall start timer T3450 and enter state EMM-COMMON-PROCEDURE-INITIATED as described in clause 5.4.1. The MME may include a new TAI list for the UE in the TRACKING AREA UPDATE ACCEPT message. The MME shall not assign a TAI list containing both tracking areas in NB-S1 mode and tracking areas in WB-S1 mode. NOTE 1: When assigning the TAI list, the MME can take into account the eNodeB's capability of support of CIoT EPS optimization. If the UE has included the UE network capability IE or the MS network capability IE or both in the TRACKING AREA UPDATE REQUEST message, the MME shall store all octets received from the UE, up to the maximum length defined for the respective information element. NOTE 2: This information is forwarded to the new MME during inter-MME handover or to the new SGSN during inter-system handover to A/Gb mode or Iu mode. NOTE 3: For further details concerning the handling of the MS network capability and UE network capability in the MME see also 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10]. In NB-S1 mode, if the tracking area update request is accepted by the network, the MME shall set the EMC BS bit to zero in the EPS network feature support IE included in the TRACKING AREA UPDATE ACCEPT message to indicate that support of emergency bearer services in NB-S1 mode is not available. If a UE radio capability information update needed IE is included in the TRACKING AREA UPDATE REQUEST message, the MME shall delete the stored UE radio capability information or the UE radio capability ID, if any. If the UE specific DRX parameter was included in the DRX Parameter IE in the TRACKING AREA UPDATE REQUEST message, the network shall replace any stored UE specific DRX parameter with the received parameter and use it for the downlink transfer of signalling and user data in WB-S1 mode. In NB-S1 mode, if the DRX parameter in NB-S1 mode IE was included in the TRACKING AREA UPDATE REQUEST message, the MME shall provide to the UE the Negotiated DRX parameter in NB-S1 mode IE in the TRACKING AREA UPDATE ACCEPT message. The MME shall replace any stored UE specific DRX parameter in NB-S1 mode with the negotiated DRX parameter and use it for the downlink transfer of signalling and user data in NB-S1 mode. NOTE 4: In NB-S1 mode, if a DRX parameter was included in the Negotiated DRX parameter in NB-S1 mode IE in the TRACKING AREA UPDATE ACCEPT message, then the UE stores and uses the received DRX parameter in NB-S1 mode (see 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [21]). If the UE has included the DRX parameter in NB-S1 mode IE in the TRACKING AREA UPDATE REQUEST message, but did not receive a DRX parameter in the Negotiated DRX parameter in NB-S1 mode IE, or if the Negotiated DRX parameter in NB-S1 mode IE was not included in the TRACKING AREA UPDATE ACCEPT message, then the UE uses the cell specific DRX value in NB-S1 mode (see 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [21]).If the UE requests "control plane CIoT EPS optimization" in the Additional update type IE, indicates support of control plane CIoT EPS optimization in the UE network capability IE and the MME decides to accept the requested CIoT EPS optimization and the tracking area update request, the MME shall indicate "control plane CIoT EPS optimization supported" in the EPS network feature support IE. In NB-S1 mode, if the UE requested "SMS only" in the Additional update type IE, supports NB-S1 mode only and the MME decides to accept the tracking area update request for EPS services and "SMS only", the MME shall indicate "SMS only" in the Additional update result IE and shall set the EPS update type IE to "TA updating" in the TRACKING AREA UPDATE ACCEPT message. The MME shall include the extended DRX parameters IE in the TRACKING AREA UPDATE ACCEPT message only if the extended DRX parameters IE was included in the TRACKING AREA UPDATE REQUEST message, and the MME supports and accepts the use of eDRX. If: - the UE supports WUS assistance; and - the MME supports and accepts the use of WUS assistance, then the MME shall determine the negotiated UE paging probability information for the UE, store it in the EMM context of the UE, and if the UE is not attaching for emergency bearer services, the MME shall include it in the Negotiated WUS assistance information IE and assign a new GUTI in the TRACKING AREA UPDATE ACCEPT message. The MME may take into account the UE paging probability information received in the Requested WUS assistance information IE when determining the negotiated UE paging probability information for the UE. If the UE has not included Requested WUS assistance information IE in the TRACKING AREA UPDATE REQUEST message and the MME has stored a negotiated UE paging probability information for that UE, the MME shall erase the negotiated UE paging probability information and assign a new GUTI in the TRACKING AREA UPDATE ACCEPT message. NOTE 5: Besides the UE paging probability information requested by the UE, the MME can take local configuration or previous statistical information for the UE into account when determining the negotiated UE paging probability information for the UE (see 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10]). If the UE indicates support for EMM-REGISTERED without PDN connection in the TRACKING AREA UPDATE REQUEST message and the MME supports EMM-REGISTERED without PDN connection, the MME shall indicate this in the EPS network feature support IE of the TRACKING AREA UPDATE ACCEPT message. The UE and the MME shall use the information whether the peer entity supports EMM-REGISTERED without PDN connection as specified in the present clause 5 and in clause 6. If the UE indicates support for enhanced discontinuous coverage in the TRACKING AREA UPDATE REQUEST message and the MME supports enhanced discontinuous coverage, the MME shall indicate "Enhanced discontinuous coverage supported" in the EPS network feature support IE of the TRACKING AREA UPDATE ACCEPT message. If the UE provided the Unavailability information IE in the TRACKING AREA UPDATE REQUEST message, then: a) the MME shall determine the unavailability period duration value as: - a value that was provided by the UE; or - a value that was determined by the MME based on satellite coverage availability information; and the MME shall store the determined unavailability period duration and provide the determined unavailability period duration to the UE by including the Unavailability period duration IE in the TRACKING AREA UPDATE ACCEPT message; b) the MME shall store the start of unavailability period value. If the UE did not include a start of the unavailability period, the MME shall consider the start of unavailability period to be the time at which MME received the TRACKING AREA UPDATE REQUEST message from the UE. The MME shall consider the UE as unreachable until the UE initiates the tracking area updating procedure for normal service again without providing an unavailability information; and c) release the NAS signalling connection immediately after the completion of the tracking area updating procedure in which the UE provided unavailability information without providing the start of the unavailability period. The MME should determine the periodic tracking area update timer, mobile reachable timer and implicit detach timer value based on: a) the stored value of the received unavailability period duration or based on a network determined unavailability period duration when the unavailability period duration is not provided by the UE; b) the stored value of the received start of unavailability period or based on a network determined start of unavailability period when the start of unavailability period is not provided by the UE; or c) any combination of the above. If the UE does not provide the Unavailability information IE in the TRACKING AREA UPDATE REQUEST message, the MME shall delete any stored value of the Unavailability information IE if exists. If an EPS bearer context status IE is included in the TRACKING AREA UPDATE REQUEST message, the MME shall deactivate all those EPS bearer contexts locally (without peer-to-peer signalling between the MME and the UE) which are in ESM state BEARER CONTEXT ACTIVE or BEARER CONTEXT MODIFY PENDING on the network side, but are indicated by the UE as being in ESM state BEARER CONTEXT INACTIVE. If a default EPS bearer context is marked as inactive in the EPS bearer context status IE included in the TRACKING AREA UPDATE REQUEST message, and this default bearer is not associated with the last remaining PDN connection of the UE in the MME, the MME shall locally deactivate all EPS bearer contexts associated to the PDN connection with the default EPS bearer context without peer-to-peer ESM signalling to the UE. If the default bearer is associated with the last remaining PDN connection of the UE in the MME, and EMM-REGISTERED without PDN connection is supported by the UE and the MME, the MME shall locally deactivate all EPS bearer contexts associated to the PDN connection with the default EPS bearer context without peer-to-peer ESM signalling to the UE. If the default EPS bearer context of a PDN connection established as a user-plane resource of an MA PDU session as specified in clause 5.3 of 3GPP TS 24.193[ 5G System;Access Traffic Steering, Switching and Splitting (ATSSS); Stage 3 ] [61] is deactivated locally and the MA PDU session does not have user plane resources established on non-3GPP access in N1 mode, the network shall perform a local release of the MA PDU session. If the EPS bearer context status IE is included in the TRACKING AREA UPDATE REQUEST, the MME shall include an EPS bearer context status IE in the TRACKING AREA UPDATE ACCEPT message, indicating which EPS bearer contexts are active in the MME except for the case no EPS bearer context exists on the network side. If the EPS update type IE included in the TRACKING AREA UPDATE REQUEST message indicates "periodic updating", and the UE was previously successfully attached for EPS and non-EPS services, subject to operator policies the MME should allocate a TAI list that does not span more than one location area. The MME shall indicate "combined TA/LA updated" or "combined TA/LA updated and ISR activated" in the EPS update result IE in the TRACKING AREA UPDATE ACCEPT message, if the following conditions apply: - the EPS update type IE included in the TRACKING AREA UPDATE REQUEST message indicates "periodic updating" and the UE was previously successfully attached for EPS and non-EPS services; and - location area updating for non-EPS services as specified in 3GPP TS 29.118[ Mobility Management Entity (MME) - Visitor Location Register (VLR) SGs interface specification ] [] is successful. The MME may include T3412 extended value IE in the TRACKING AREA UPDATE ACCEPT message only if the UE indicates support of the extended periodic timer T3412 in the MS network feature support IE in the TRACKING AREA UPDATE REQUEST message. The MME shall include the T3324 value IE in the TRACKING AREA UPDATE ACCEPT message only if the T3324 value IE was included in the TRACKING AREA UPDATE REQUEST message, and the MME supports and accepts the use of PSM. If the MME supports and accepts the use of PSM, and the UE included the T3412extended value IE in the TRACKING AREA UPDATE REQUEST message, then the MME shall take into account the T3412 value requested when providing the T3412 value IE and the T3412 extended value IE in the TRACKING AREA UPDATE ACCEPT message. NOTE 6: Besides the value requested by the MS, the MME can take local configuration or subscription data provided by the HSS into account when selecting a value for T3412 (see 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10] clause 4.3.17.3). If the MME includes the T3324 value IE indicating a value other than deactivated in the TRACKING AREA UPDATE ACCEPT message, then the MME shall indicate in the EPS update result IE in the TRACKING AREA UPDATE ACCEPT message that ISR is not activated. Also, during the tracking area updating procedure without the "active" flag set, if the MME has deactivated EPS bearer context(s) locally for any reason, the MME shall inform the UE of the deactivated EPS bearer context(s) by including the EPS bearer context status IE in the TRACKING AREA UPDATE ACCEPT message. Also, during the tracking area updating procedure with the "active" flag set, if the MME has deactivated EPS bearer context(s) associated with control plane only indication locally for any reason, the MME shall inform the UE of the deactivated EPS bearer context(s) by including the EPS bearer context status IE in the TRACKING AREA UPDATE ACCEPT message. If the TRACKING AREA UPDATE ACCEPT message contains the DCN-ID IE, then the UE shall store the included DCN-ID value together with the PLMN code of the registered PLMN in a DCN-ID list in a non-volatile memory in the ME as specified in annex C. If due to regional subscription restrictions or access restrictions the UE is not allowed to access the TA, but it has a PDN connection for emergency bearer services established, the MME may accept the TRACKING AREA UPDATE REQUEST message and deactivate all non-emergency EPS bearer contexts by initiating an EPS bearer context deactivation procedure when the tracking area updating procedure is initiated in EMM-CONNECTED mode. When the tracking area updating procedure is initiated in EMM-IDLE mode, the MME locally deactivates all non-emergency EPS bearer contexts and informs the UE via the EPS bearer context status IE in the TRACKING AREA UPDATE ACCEPT message. The MME shall not deactivate the emergency EPS bearer contexts. The network shall consider the UE to be attached for emergency bearer services only and shall indicate in the EPS update result IE in the TRACKING AREA UPDATE ACCEPT message that ISR is not activated. If a TRACKING AREA UPDATE REQUEST message is received from a UE with a LIPA PDN connection, and if: - a GW Transport Layer Address IE value identifying a L-GW is provided by the lower layer together with the TRACKING AREA UPDATE REQUEST message, and the P-GW address included in the EPS bearer context of the LIPA PDN Connection is different from the provided GW Transport Layer Address IE value (see 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [23]); or - no GW Transport Layer Address is provided together with the TRACKING AREA UPDATE REQUEST message by the lower layer, then the MME locally deactivates all EPS bearer contexts associated with the LIPA PDN connection. Furthermore, the MME takes one of the following actions: - if no active EPS bearer contexts remain for the UE, the MME shall not accept the tracking area update request as specified in clause 5.5.3.2.5; - if active EPS bearer contexts remain for the UE and the TRACKING AREA UPDATE REQUEST message is accepted, the MME informs the UE via the EPS bearer context status IE in the TRACKING AREA UPDATE ACCEPT message that EPS bearer contexts were locally deactivated. If a TRACKING AREA UPDATE REQUEST message is received from a UE with a SIPTO at the local network PDN connection, is accepted by the network, the following different cases can be distinguished: 1) If the PDN connection is a SIPTO at the local network PDN connection with collocated L-GW and if: - a SIPTO L-GW Transport Layer Address IE value identifying a L-GW is provided by the lower layer together with the TRACKING AREA UPDATE REQUEST message, and the P-GW address included in the EPS bearer context of the SIPTO at the local network PDN connection is different from the provided SIPTO L-GW Transport Layer Address IE value (see 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [23]); or - no SIPTO L-GW Transport Layer Address is provided together with the TRACKING AREA UPDATE REQUEST message by the lower layer, 2) If the PDN connection is a SIPTO at the local network PDN connection with stand-alone GW and if: - a LHN-ID value is provided by the lower layer together with the TRACKING AREA UPDATE REQUEST message, and the LHN-ID stored in the EPS bearer context of the SIPTO at the local network PDN connection is different from the provided LHN-ID value (see 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [23]); or - no LHN-ID value is provided together with the TRACKING AREA UPDATE REQUEST message by the lower layer, then the MME takes one of the following actions: - if the SIPTO at the local network PDN connection is the last remaining PDN connection for the UE, and EMM-REGISTERED without PDN connection is not supported by the UE or the MME, then the MME shall upon completion of the tracking area updating procedure detach the UE by using detach type "re-attach required" (see clause 5.5.2.3.1); - if the SIPTO at the local network PDN connection is the last remaining PDN connection for the UE, and EMM-REGISTERED without PDN connection is supported by the UE and the MME, then the MME shall upon completion of the tracking area updating procedure initiate an EPS bearer context deactivation procedure with ESM cause #39 "reactivation requested" for the default EPS bearer context of the SIPTO at the local network PDN connection (see clause 6.4.4.2); and - if a PDN connection remains that is not SIPTO at the local network PDN connection, the MME shall upon completion of the tracking area updating procedure initiate an EPS bearer context deactivation procedure with ESM cause #39 "reactivation requested" for the default EPS bearer context of each SIPTO at the local network PDN connection (see clause 6.4.4.2); For a SIPTO at the local network PDN connection with stand-alone GW, the conditions to deactivate ISR are specified in 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10], clause 4.3.5.6. For a shared network, the TAIs included in the TAI list can contain different PLMN identities. The MME indicates the selected core network operator PLMN identity to the UE in the GUTI (see 3GPP TS 23.251[ Network sharing; Architecture and functional description ] [8B]). If the "active" flag is set in the TRACKING AREA UPDATE REQUEST message and control plane CIoT EPS optimization is not used by the MME, the MME shall re-establish the radio and S1 bearers for all active EPS bearer contexts. If the "active" flag is set in the TRACKING AREA UPDATE REQUEST message and control plane CIoT EPS optimization is used by the MME, the MME shall re-establish the radio and S1 bearers for all active EPS bearer contexts associated with PDN connections established without Control plane only indication. If the "signalling active" flag is set in the TRACKING AREA UPDATE REQUEST message and control plane CIoT EPS optimization is used by the MME, the MME shall not immediately release the NAS signalling connection after the completion of the tracking area updating procedure. If the "active" flag is not set in the TRACKING AREA UPDATE REQUEST message and control plane CIoT EPS optimization is not used by the MME, the MME may also re-establish the radio and S1 bearers for all active EPS bearer contexts due to downlink pending data or downlink pending signalling, except for the case when the TRACKING AREA UPDATE REQUEST message includes the UE request type IE and the Request type is set to "NAS signalling connection release". If the "active" flag is not set in the TRACKING AREA UPDATE REQUEST message and control plane CIoT EPS optimization is used by the MME, the MME may also re-establish the radio and S1 bearers for all active EPS bearer contexts associated with PDN connections established without Control plane only indication due to downlink pending data or downlink pending signalling, except for the case when the TRACKING AREA UPDATE REQUEST message includes the UE request type IE and the Request type is set to "NAS signalling connection release". If the MME supports NB-S1 mode, non-IP or Ethernet PDN type, inter-system change with 5GS, UAS services or the network wants to enforce the use of DNS over (D)TLS (see 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]), then the MME shall support the Extended protocol configuration options IE. NOTE 7: Support of DNS over (D)TLS is based on the informative requirements as specified in 3GPP TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [19] and it is implemented based on the operator requirement. If the MME supports the Extended protocol configuration options IE and the UE indicated support of the Extended protocol configuration options IE, then the MME shall set the ePCO bit to "extended protocol configuration options supported" in the EPS network feature support IE of the TRACKING AREA UPDATE ACCEPT message. If the UE indicates support for restriction on use of enhanced coverage in the TRACKING AREA UPDATE REQUEST message, and the network decides to restrict the use of enhanced coverage for the UE, then the MME shall set the RestrictEC bit to "Use of enhanced coverage is restricted" in the EPS network feature support IE of the TRACKING AREA UPDATE ACCEPT message. The MME may indicate the header compression configuration status IE in the TRACKING AREA UPDATE ACCEPT message for each established EPS bearer context using control plane CIoT EPS optimisation. If the UE has indicated support for the control plane data back-off timer, and the MME decides to activate the congestion control for transport of user data via the control plane, then the MME shall include the T3448 value IE in the TRACKING AREA UPDATE ACCEPT message. If the UE indicates support for dual connectivity with NR in the TRACKING AREA UPDATE REQUEST message, and the MME decides to restrict the use of dual connectivity with NR for the UE, then the MME shall set the RestrictDCNR bit to "Use of dual connectivity with NR is restricted" in the EPS network feature support IE of the TRACKING AREA UPDATE ACCEPT message. If the UE indicates support for N1 mode in the TRACKING AREA UPDATE REQUEST message and the MME supports inter-system interworking with 5GS, the MME may set the IWK N26 bit to either: - "interworking without N26 interface not supported" if the MME supports N26 interface; or - "interworking without N26 interface supported" if the MME does not support N26 interface in the EPS network feature support IE in the TRACKING AREA UPDATE ACCEPT message. If the MME determines the UE's N1 mode capability for 3GPP access changes from " N1 mode for 3GPP access not supported " to " N1 mode for 3GPP access supported " and the network decides to enable the transfer of a PDN connection not supporting interworking to 5GS from S1 mode to N1 mode, the MME may upon completion of the tracking area updating procedure initiate an EPS bearer context deactivation procedure to deactivate the default EPS bearer context of the PDN connection by including ESM cause #39 "reactivation requested" in the DEACTIVATE EPS BEARER CONTEXT REQUEST message (see clause 6.4.4.2). The MME shall set the redir-policy bit to "Unsecured redirection to GERAN or UTRAN not allowed" in the Network policy IE of the TRACKING AREA UPDATE ACCEPT message if unsecured redirection to a GERAN or UTRAN cell is not allowed in the current PLMN. Otherwise, the redir-policy bit shall be set to "Unsecured redirection to GERAN or UTRAN allowed". If the UE has indicated support for service gap control, a service gap time value is available in the EMM context, the MME may include the T3447 value IE set to the service gap time value in the TRACKING AREA UPDATE ACCEPT message. If the network supports signalling for a maximum number of 15 EPS bearer contexts and the UE indicated support of signalling for a maximum number of 15 EPS bearer contexts in the TRACKING AREA UPDATE REQUEST message, then the MME shall set the 15 bearers bit to "Signalling for a maximum number of 15 EPS bearer contexts supported" in the EPS network feature support IE of the TRACKING AREA UPDATE ACCEPT message. If the UE indicates support of the NAS signalling connection release in the TRACKING AREA UPDATE REQUEST message and the network decides to accept the NAS signalling connection release, then the MME shall set the NAS signalling connection release bit to "NAS signalling connection release supported" in the EPS network feature support IE of the TRACKING AREA UPDATE ACCEPT message. If the UE indicates support of the paging indication for voice services in the TRACKING AREA UPDATE REQUEST message and the network decides to accept the paging indication for voice services, then the MME shall set the paging indication for voice services bit to "paging indication for voice services supported" in the EPS network feature support IE of the TRACKING AREA UPDATE ACCEPT message. If the UE receives the TRACKING AREA UPDATE ACCEPT message with the paging indication for voice services bit set to "paging indication for voice services supported", the UE NAS layer informs the lower layers that paging indication for voice services is supported. Otherwise, the UE NAS layer informs the lower layers that paging indication for voice services is not supported. If the UE indicates support of the reject paging request in the TRACKING AREA UPDATE REQUEST message and the network decides to accept the reject paging request, then the MME shall set the reject paging request bit to "reject paging request supported" in the EPS network feature support IE of the TRACKING AREA UPDATE ACCEPT message. If the UE indicates support of the paging restriction in the TRACKING AREA UPDATE REQUEST message, and the MME sets: - the reject paging request bit to "reject paging request supported"; - the NAS signalling connection release bit to "NAS signalling connection release supported"; or - both of them; in the EPS network feature support IE of the TRACKING AREA UPDATE ACCEPT message, and the network decides to accept the paging restriction, then the MME shall set the paging restriction bit to "paging restriction supported" in the EPS network feature support IE of the TRACKING AREA UPDATE ACCEPT message. If the UE indicates support of the paging timing collision control in the TRACKING AREA UPDATE REQUEST message and the network decides to accept the paging timing collision control, then the MME shall set the paging timing collision control bit to "paging timing collision control supported" in the EPS network feature support IE of the TRACKING AREA UPDATE ACCEPT message. If the UE requests ciphering keys for ciphered broadcast assistance data in the TRACKING AREA UPDATE REQUEST message and the MME has valid ciphering key data applicable to the UE's subscription, then the MME shall include the ciphering key data in the Ciphering key data IE of the TRACKING AREA UPDATE ACCEPT message. If the MUSIM UE does not include the Paging restriction IE in the TRACKING AREA UPDATE REQUEST message, the MME shall delete any stored paging restriction for the UE and stop restricting paging. If the MUSIM UE has included a Requested IMSI offset IE in the TRACKING AREA UPDATE REQUEST message with the EPS update type IE not indicating "periodic updating" and if the MME supports paging timing collision control, the MME shall include the Negotiated IMSI offset IE and assign a new GUTI in the TRACKING AREA UPDATE ACCEPT message, and the MME shall set the IMSI offset value to: - A value that is different than what the UE has provided, if the MME has a different value; or - A value that is same as what the UE has provided, if the MME does not have a different value; and the MME shall calculate an alternative IMSI value using the IMSI offset value and store it in the UE context as specified in 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10]. The alternative IMSI value is used for deriving the paging occasion as specified in 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [21]. If the MUSIM UE has not included a Requested IMSI offset IE in the TRACKING AREA UPDATE REQUEST message with the EPS update type IE not indicating "periodic updating" and the MME has stored an alternative IMSI value for that UE, the MME shall erase the alternative IMSI value and assign a new GUTI in the TRACKING AREA UPDATE ACCEPT message. If the MUSIM UE requests the release of the NAS signalling connection, by setting Request type to "NAS signalling connection release" in the UE request type IE in the TRACKING AREA UPDATE REQUEST message, and the MME supports the NAS signalling connection release, the MME shall initiate the release of the NAS signalling connection after the completion of the tracking area updating procedure. If the UE requests restriction of paging by including the Paging restriction IE in the TRACKING AREA UPDATE REQUEST message and the MME supports the paging restriction, the MME: - if accepts the paging restriction, shall include the EPS additional request result IE in the TRACKING AREA UPDATE ACCEPT message and set the Paging restriction decision to "paging restriction is accepted". The MME shall store the paging restriction of the UE and enforce these restrictions in the paging procedure as described in clause 5.6.2; or - if rejects the paging restriction, shall include the EPS additional request result IE in the TRACKING AREA UPDATE ACCEPT message and set the Paging restriction decision to "paging restriction is rejected", and shall discard the received paging restriction. The MME shall delete any stored paging restriction for the UE and stop restricting paging. Upon receiving a TRACKING AREA UPDATE ACCEPT message, the UE shall stop timer T3430, reset the service request attempt counter, tracking area updating attempt counter, enter state EMM-REGISTERED and set the EPS update status to EU1 UPDATED. If the message contains a GUTI, the UE shall use this GUTI as new temporary identity for EPS services and shall store the new GUTI. If no GUTI was included by the MME in the TRACKING AREA UPDATE ACCEPT message, the old GUTI shall be used. If the UE receives a new TAI list in the TRACKING AREA UPDATE ACCEPT message, the UE shall consider the new TAI list as valid and the old TAI list as invalid; otherwise, the UE shall consider the old TAI list as valid. If the UE receives the TRACKING AREA UPDATE ACCEPT message from a PLMN for which a PLMN-specific attempt counter or PLMN-specific PS-attempt counter is maintained (see clause 5.3.7b), then the UE shall reset these counters. If the UE maintains a counter for "SIM/USIM considered invalid for GPRS services", then the UE shall reset this counter. If the TRACKING AREA UPDATE ACCEPT message contains the T3412 extended value IE, then the UE shall use the T3412 extended value IE as periodic tracking area update timer (T3412). If the TRACKING AREA UPDATE ACCEPT contains T3412 value IE, but not T3412 extended value IE, then the UE shall use value in T3412 value IE as periodic tracking area update timer (T3412). If neither T3412 value IE nor T3412 extended value IE is included, the UE shall use the value currently stored, e.g. from a prior ATTACH ACCEPT or TRACKING AREA UPDATE ACCEPT message. If the TRACKING AREA UPDATE ACCEPT message contains the T3324 value IE, then the UE shall use the timer value for T3324 as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13], clause 4.7.2.8. If the UE had initiated the tracking area updating procedure in EMM-IDLE mode to perform an inter-system change from A/Gb mode or Iu mode to S1 mode and the nonceUE was included in the TRACKING AREA UPDATE REQUEST message, the UE shall delete the nonceUE upon receipt of the TRACKING AREA UPDATE ACCEPT message. If an EPS bearer context status IE is included in the TRACKING AREA UPDATE ACCEPT message, the UE shall deactivate all those EPS bearers contexts locally (without peer-to-peer signalling between the UE and the MME) which are active in the UE, but are indicated by the MME as being inactive. If a default EPS bearer context is marked as inactive in the EPS bearer context status IE included in the TRACKING AREA UPDATE ACCEPT message, and this default bearer is not associated with the last remaining PDN connection in the UE, the UE shall locally deactivate all EPS bearer contexts associated to the PDN connection with the default EPS bearer context without peer-to-peer ESM signalling to the MME. If only the PDN connection for emergency bearer services remains established, the UE shall consider itself attached for emergency bearer services only. If the default bearer is associated with the last remaining PDN connection of the UE in the MME, and EMM-REGISTERED without PDN connection is supported by the UE and the MME, the UE shall locally deactivate all EPS bearer contexts associated to the PDN connection with the default EPS bearer context without peer-to-peer ESM signalling to the UE. If the default EPS bearer context of a PDN connection established as a user-plane resource of an MA PDU session as specified in clause 5.3 of 3GPP TS 24.193[ 5G System;Access Traffic Steering, Switching and Splitting (ATSSS); Stage 3 ] [61] is deactivated locally and the MA PDU session does not have user plane resources established on non-3GPP access in N1 mode, the UE shall perform a local release of the MA PDU session. If an EPS bearer context status IE is included in the TRACKING AREA UPDATE ACCEPT message, the UE may choose to ignore all those EPS bearers which are indicated by the MME as being active but are inactive at the UE. If the tracking area updating procedure is initiated following an inter-system change from N1 mode to S1 mode and only the PDN connection for emergency bearer services is established, the UE should consider itself attached for emergency bearer services only. If a Negotiated IMSI offset IE is included in the TRACKING AREA UPDATE ACCEPT message, the MUSIM UE shall forward the IMSI offset value to lower layers. If a Negotiated IMSI offset IE is not included in the TRACKING AREA UPDATE ACCEPT message and the EPS update type IE included in the TRACKING AREA UPDATE REQUEST message does not indicate "periodic updating", the MUSIM UE shall indicate to lower layers to erase any IMSI offset value, if available. The MME may also include a list of equivalent PLMNs in the TRACKING AREA UPDATE ACCEPT message. Each entry in the list contains a PLMN code (MCC+MNC). The UE shall store the list as provided by the network, and if there is no PDN connection for emergency bearer services or PDN connection for RLOS established, the UE shall remove from the list any PLMN code that is already in the list of "forbidden PLMNs" or in the list of "forbidden PLMNs for GPRS service". If the UE is not attached for emergency bearer services and there is a PDN connection for emergency bearer services established, the UE shall remove from the list of equivalent PLMNs any PLMN code present in the list of forbidden PLMNs or in the list of "forbidden PLMNs for GPRS service" when the PDN connection for emergency bearer services is released. In addition, the UE shall add to the stored list the PLMN code of the registered PLMN that sent the list. The UE shall replace the stored list on each receipt of the TRACKING AREA UPDATE ACCEPT message. If the TRACKING AREA UPDATE ACCEPT message does not contain a list, then the UE shall delete the stored list. If the UE is neither attached for emergency bearer services nor attached for access to RLOS, and if the PLMN identity of the registered PLMN is a member of the list of "forbidden PLMNs" or the list of "forbidden PLMNs for GPRS service", any such PLMN identity shall be deleted from the corresponding list(s). The network may also indicate in the EPS update result IE in the TRACKING AREA UPDATE ACCEPT message that ISR is active. If the UE is attached for emergency bearer services, the network shall indicate in the EPS update result IE in the TRACKING AREA UPDATE ACCEPT message that ISR is not activated. If the TRACKING AREA UPDATE ACCEPT message contains: i) no indication that ISR is activated, the UE shall set the TIN to "GUTI" and shall stop the periodic routing area update timer T3312 or T3323, if running; ii) an indication that ISR is activated, then: - if the UE is required to perform routing area updating for IMS voice termination as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13], annex P.5, the UE shall set the TIN to "GUTI" and shall stop the periodic routing area update timer T3312 or T3323, if running; - if the UE had initiated the tracking area updating procedure due to a change in UE network capability or change in DRX parameters, the UE shall set the TIN to "GUTI" and shall stop the periodic routing area update timer T3312 or T3323, if running; - if the UE had initiated the tracking area updating procedure due to a change in the UE's usage setting or the voice domain preference for E-UTRAN, the UE shall set the TIN to "GUTI" and shall stop the periodic routing area update timer T3312 or T3323, if running; or - the UE shall regard a previously assigned P-TMSI and RAI as valid and registered with the network. If the TIN currently indicates "P-TMSI" and the periodic routing area update timer T3312 is running or is deactivated, the UE shall set the TIN to "RAT-related TMSI". If the TIN currently indicates "P-TMSI" and the periodic routing area update timer T3312 has already expired, the UE shall set the TIN to "GUTI". The network informs the UE about the support of specific features, such as IMS voice over PS session, location services (EPC-LCS, CS-LCS), emergency bearer services, or CIoT EPS optimizations, in the EPS network feature support information element. In a UE with IMS voice over PS capability, the IMS voice over PS session indicator and the emergency bearer services indicator shall be provided to the upper layers. The upper layers take the IMS voice over PS session indicator into account as specified in 3GPP TS 23.221[ Architectural requirements ] [8A], clause 7.2a and clause 7.2b, when selecting the access domain for voice sessions or calls. When initiating an emergency call, the upper layers also take both the IMS voice over PS session indicator and the emergency bearer services indicator into account for the access domain selection. When the UE determines via the IMS voice over PS session indicator that the network does not support IMS voice over PS sessions in S1 mode, then the UE shall not locally release any persistent EPS bearer context. When the UE determines via the emergency bearer services indicator that the network does not support emergency bearer services in S1 mode, then the UE shall not locally release any emergency EPS bearer context if there is a radio bearer associated with that context. In a UE with LCS capability, location services indicators (EPC-LCS, CS-LCS) shall be provided to the upper layers. When MO-LR procedure is triggered by the UE's application, those indicators are taken into account as specified in 3GPP TS 24.171[ Control Plane Location Services (LCS) procedures in the Evolved Packet System (EPS) ] [13C]. If the MME received the list of TAIs from the satellite E-UTRAN as described in 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10], and determines that, by UE subscription and operator's preferences, any but not all TAIs in the received list of TAIs is forbidden for roaming or for regional provision of service as per operator's choice, the MME shall include the TAI(s) in: a) the Forbidden TAI(s) for the list of "forbidden tracking areas for roaming" IE; b) the Forbidden TAI(s) for the list of "forbidden tracking areas for regional provision of service" IE; or c) both, in the TRACKING AREA UPDATE ACCEPT message. NOTE 8: Void. If the RestrictDCNR bit is set to "Use of dual connectivity with NR is restricted" in the EPS network feature support IE of the TRACKING AREA UPDATE ACCEPT message, the UE shall provide the indication that dual connectivity with NR is restricted to the upper layers. The UE supporting N1 mode shall operate in the mode for inter-system interworking with 5GS as follows: - if the IWK N26 bit in the EPS network feature support IE is set to "interworking without N26 interface not supported", the UE shall operate in single-registration mode; - if the IWK N26 bit in the EPS network feature support IE is set to "interworking without N26 interface supported" and the UE supports dual-registration mode, the UE may operate in dual-registration mode; or NOTE 9: The registration mode used by the UE is implementation dependent. - if the IWK N26 bit in the EPS network feature support IE is set to "interworking without N26 interface supported" and the UE only supports single-registration mode, the UE shall operate in single-registration mode. The UE shall treat the interworking without N26 interface indicator as valid in the entire PLMN and equivalent PLMNs. The interworking procedures required for coordination between 5GMM and EMM without N26 interface are specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54]. If the redir-policy bit is set to "Unsecured redirection to GERAN or UTRAN not allowed" in the Network policy IE of the TRACKING AREA UPDATE ACCEPT message, the UE shall set the network policy on unsecured redirection to GERAN for the current PLMN to "Unsecured redirection to GERAN or UTRAN not allowed" and indicate to the lower layers that unsecured redirection to a GERAN or UTRAN cell is not allowed. If the redir-policy bit is set to "Unsecured redirection to GERAN or UTRAN allowed" or if the Network policy IE is not included in the TRACKING AREA UPDATE ACCEPT message, the UE shall set the network policy on unsecured redirection to GERAN or UTRAN for the current PLMN to "Unsecured redirection to GERAN or UTRAN allowed" and indicate to the lower layers that unsecured redirection to a GERAN or UTRAN cell is allowed. The UE shall set the network policy on unsecured redirection to GERAN or UTRAN to "Unsecured redirection to GERAN or UTRAN not allowed" and indicate this to the lower layers when any of the following events occurs: - the UE initiates an EPS attach or tracking area updating procedure in a PLMN different from the PLMN where the UE performed the last successful EPS attach or tracking area updating procedure; - the UE is switched on; or - the UICC containing the USIM is removed. If the UE has initiated the tracking area updating procedure due to manual CSG selection and receives a TRACKING AREA UPDATE ACCEPT message, and the UE sent the TRACKING AREA UPDATE REQUEST message in a CSG cell, the UE shall check if the CSG ID and associated PLMN identity of the cell where the UE has sent the TRACKING AREA UPDATE REQUEST message are contained in the Allowed CSG list. If not, the UE shall add that CSG ID and associated PLMN identity to the Allowed CSG list and the UE may add the HNB Name (if provided by lower layers) to the Allowed CSG list if the HNB Name is present in neither the Operator CSG list nor the Allowed CSG list. If the TRACKING AREA UPDATE ACCEPT message contained a GUTI, the UE shall return a TRACKING AREA UPDATE COMPLETE message to the MME to acknowledge the received GUTI or the received Negotiated IMSI offset IE. If the UE has a negotiated IMSI offset value stored at the lower layers and the TRACKING AREA UPDATE ACCEPT message does not contain the Negotiated IMSI offset IE, the UE shall return a TRACKING AREA UPDATE COMPLETE message to the MME, and the MME shall erase the stored alternative IMSI value for the UE upon receiving the TRACKING AREA UPDATE COMPLETE message. If the UE which was previously successfully attached for EPS and non-EPS services receives the TRACKING AREA UPDATE ACCEPT message with EPS update result IE indicating "combined TA/LA updated" or "combined TA/LA updated and ISR activated" as the response of the TRACKING AREA UPDATE REQUEST message with EPS update type IE indicating "periodic updating", the UE shall behave as follows: - If the TRACKING AREA UPDATE ACCEPT message contains an IMSI, the UE is not allocated any TMSI, and shall delete any old TMSI accordingly. - If the TRACKING AREA UPDATE ACCEPT message contains a TMSI, the UE shall use this TMSI as new temporary identity. The UE shall delete its old TMSI and shall store the new TMSI. In this case, a TRACKING AREA UPDATE COMPLETE message is returned to the network to confirm the received TMSI. - If neither a TMSI nor an IMSI has been included by the network in the TRACKING AREA UPDATE ACCEPT message, the old TMSI, if any is available, shall be kept. If the header compression configuration status is included in the TRACKING AREA UPDATE ACCEPT message, the UE shall stop using header compression and decompression for those EPS bearers using Control plane CIoT EPS optimisation for which the MME indicated that the header compression configuration is not used. If the T3448 value IE is present in the received TRACKING AREA UPDATE ACCEPT message, the UE shall: - stop timer T3448 if it is running; and - start timer T3448 with the value provided in the T3448 value IE. If the UE is using EPS services with control plane CIoT EPS optimization, the T3448 value IE is present in the TRACKING AREA UPDATE ACCEPT message and the value indicates that this timer is either zero or deactivated, the UE shall consider this case as an abnormal case and proceed as if the T3448 value IE is not present. If the UE in EMM-IDLE mode initiated the tracking area updating procedure and the TRACKING AREA UPDATE ACCEPT message does not include the T3448 value IE and if timer T3448 is running, then the UE shall stop timer T3448. If the UE has indicated "service gap control supported" in the TRACKING AREA UPDATE REQUEST message and: - the TRACKING AREA UPDATE ACCEPT message contains the T3447 value IE, then the UE shall store the new T3447 value, erase any previous stored T3447 value if exists and use the new T3447 value with the T3447 timer next time it is started; or - the TRACKING AREA UPDATE ACCEPT message does not contain the T3447 value IE, then the UE shall erase any previous stored T3447 value if exists and stop the T3447 timer if running. Upon receiving a TRACKING AREA UPDATE COMPLETE message, the MME shall stop timer T3450 and change to state EMM-REGISTERED. The GUTI, the Negotiated IMSI offset, or both, if sent in the TRACKING AREA UPDATE ACCEPT message, shall be considered as valid. NOTE 10: Upon receiving a TRACKING AREA UPDATE COMPLETE message, if a new TMSI was included in the TRACKING AREA UPDATE ACCEPT message, the MME sends an SGsAP-TMSI-REALLOCATION-COMPLETE message as specified in 3GPP TS 29.118[ Mobility Management Entity (MME) - Visitor Location Register (VLR) SGs interface specification ] [16A]. For inter-system change from A/Gb mode to S1 mode or Iu mode to S1 mode in EMM-IDLE mode, if the UE has included an eKSI in the NAS Key Set Identifier IE indicating a current EPS security context in the TRACKING AREA UPDATE REQUEST message by which the TRACKING AREA UPDATE REQUEST message is integrity protected, the MME shall take one of the following actions: - if the MME retrieves the current EPS security context as indicated by the eKSI and GUTI sent by the UE, the MME shall integrity check the TRACKING AREA UPDATE REQUEST message using the current EPS security context and integrity protect the TRACKING AREA UPDATE ACCEPT message using the current EPS security context; - if the MME cannot retrieve the current EPS security context as indicated by the eKSI and GUTI sent by the UE, and if the UE has included a valid GPRS ciphering key sequence number, the MME shall create a new mapped EPS security context as specified in 3GPP TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [19], and then perform a security mode control procedure to indicate the use of the new mapped EPS security context to the UE (see clause 5.4.3.2); or - if the UE has not included an Additional GUTI IE, the MME may treat the TRACKING AREA UPDATE REQUEST message as in the previous item, i.e. as if it cannot retrieve the current EPS security context. NOTE 11: The handling described above at failure to retrieve the current EPS security context or if no Additional GUTI IE was provided does not preclude the option for the MME to perform an EPS authentication procedure and create a new native EPS security context. For inter-system change from A/Gb mode to S1 mode or Iu mode to S1 mode in EMM-IDLE mode, if the UE has not included a valid eKSI in the NAS Key Set Identifier IE and has included a valid GPRS ciphering key sequence number in the TRACKING AREA UPDATE REQUEST message, the MME shall create a new mapped EPS security context as specified in 3GPP TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [19], and then perform a security mode control procedure to indicate the use of the new mapped EPS security context to the UE (see clause 5.4.3.2). NOTE 12: This does not preclude the option for the MME to perform an EPS authentication procedure and create a new native EPS security context. For inter-system change from N1 mode to S1 mode in EMM-IDLE mode, if the UE has included an eKSI in the NAS Key Set Identifier IE indicating a 5G NAS security context in the TRACKING AREA UPDATE REQUEST message by which the TRACKING AREA UPDATE REQUEST message is integrity protected, the MME shall take actions as specified in clause 4.4.2.3. For inter-system change from A/Gb mode to S1 mode or Iu mode to S1 mode in EMM-CONNECTED mode, the MME shall integrity check TRACKING AREA UPDATE REQUEST message using the current K'ASME as derived when triggering the handover to E-UTRAN (see clause 4.4.2.2). The MME shall verify the received UE security capabilities in the TRACKING AREA UPDATE REQUEST message. The MME shall then take one of the following actions: - if the TRACKING AREA UPDATE REQUEST does not contain a valid KSIASME in the Non-current native NAS key set identifier IE, the MME shall remove the non-current native EPS security context, if any, for any GUTI for this UE. The MME shall then integrity protect and cipher the TRACKING AREA UPDATE ACCEPT message using the security context based on K'ASME and take the mapped EPS security context into use; or - if the TRACKING AREA UPDATE REQUEST contains a valid KSIASME in the Non-current native NAS key set identifier IE, the MME may initiate a security mode control procedure to take the corresponding native EPS security context into use. For inter-system change from N1 mode to S1 mode in EMM-CONNECTED mode, the MME shall integrity check TRACKING AREA UPDATE REQUEST message using the current K'ASME as derived when triggering the handover to E-UTRAN (see clause 4.4.2.2). The MME shall verify the received UE security capabilities in the TRACKING AREA UPDATE REQUEST message. The MME shall then take one of the following actions: - if the TRACKING AREA UPDATE REQUEST does not contain a valid KSIASME in the Non-current native NAS key set identifier IE, the MME shall remove the non-current native EPS security context, if any, for any GUTI for this UE. The MME shall then integrity protect and cipher the TRACKING AREA UPDATE ACCEPT message using the security context based on K'ASME and take the mapped EPS security context into use; or - if the TRACKING AREA UPDATE REQUEST contains a valid KSIASME in the Non-current native NAS key set identifier IE, the MME may initiate a security mode control procedure to take the corresponding native EPS security context into use. In WB-S1 mode, if the UE has set the RACS bit to "RACS supported" in the UE network capability IE of the TRACKING AREA UPDATE REQUEST message, the MME may include a UE radio capability ID IE or a UE radio capability ID deletion indication IE in the TRACKING AREA UPDATE ACCEPT message. In this case the MME shall enter state EMM-COMMON-PROCEDURE-INITIATED as described in clause 5.4.1. In WB-S1 mode, if the UE has set the RACS bit to "RACS supported" in the UE network capability IE of the TRACKING AREA UPDATE REQUEST message and the TRACKING AREA UPDATE ACCEPT message includes: - a UE radio capability ID deletion indication IE set to "Network-assigned UE radio capability IDs deletion requested", the UE shall: a) delete any network-assigned UE radio capability IDs associated with the registered PLMN stored at the UE; b) send a TRACKING AREA UPDATE COMPLETE message to the network to acknowledge the received UE radio capability ID deletion indication IE; and c) after the completion of the ongoing tracking area updating procedure, initiate a tracking area updating procedure as specified in clause 5.5.3 over the existing NAS signalling connection except if there is a pending service request procedure as response to paging for CS fallback; or - a UE radio capability ID IE, the UE shall: a) store the UE radio capability ID as specified in annex C; and b) send a TRACKING AREA UPDATE COMPLETE message to the network to acknowledge the received UE radio capability ID IE. If the UE receives the Forbidden TAI(s) for the list of "forbidden tracking areas for roaming" IE in the TRACKING ARE UPDATE ACCEPT message and the TAI(s) included in the IE is not part of the list of "forbidden tracking areas for roaming", the UE shall store the TAI(s) included in the IE which are belonging to the serving PLMN or equivalent PLMN(s) into the list of "forbidden tracking areas for roaming", ignore the TAI(s) which do not belong to the serving PLMN or equivalent PLMN(s) and remove the TAI(s) from the stored TAI list if present. If the UE receives the Forbidden TAI(s) for the list of "forbidden tracking areas for regional provision of service" IE in the TRACKING AREA UPDATE ACCEPT message and the TAI(s) included in the IE is not part of the list of "forbidden tracking areas for regional provision of service", the UE shall store the TAI(s) included in the IE which are belonging to the serving PLMN or equivalent PLMN(s) into the list of "forbidden tracking areas for regional provision of service", ignore the TAI(s) which do not belong to the serving PLMN or equivalent PLMN(s) and remove the TAI(s) from the stored TAI list if present. NOTE 13: For the UE supporting non-IP or Ethernet PDN type or UAS services, if the UE receives the TRACKING AREA UPDATE ACCEPT message and the ePCO bit in the EPS network feature support IE is not set to "extended protocol configuration options supported", the UE can perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6] with the current PLMN considered as the lowest priority after the completion of the tracking area update procedure. If for discontinuous coverage, the UE receives the Unavailability configuration IE in the TRACKING AREA UPDATE ACCEPT message and the End of unavailability report bit is set to "UE does not need to report end of unavailability", the UE is not required to trigger tracking area update procedure when the unavailability period duration has ended. If the UE does not receive the Unavailability configuration IE, or the End of unavailability report bit is set to "UE needs to report end of unavailability", the UE should trigger tracking area update procedure when the unavailability period duration has ended. If the UE supports enhanced discontinuous coverage, the MME may include the Discontinuous coverage maximum time offset IE in the TRACKING ARE UPDATE ACCEPT message. If the UE receives, the Discontinuous coverage maximum time offset IE in the TRACKING ARE UPDATE ACCEPT message, the UE shall replace any previously received discontinuous coverage maximum time offset value on the same satellite E-UTRAN access and PLMN with the latest received timer value. | 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.3.2.4 |
4,550 | 5.5.3.2.5 Normal and periodic tracking area updating procedure not accepted by the network | If the tracking area updating cannot be accepted by the network, the MME sends a TRACKING AREA UPDATE REJECT message to the UE including an appropriate EMM cause value. If a tracking area update request from a UE with a LIPA PDN connection is not accepted due to the reasons specified in clause 5.5.3.2.4, the MME shall send the TRACKING AREA UPDATE REJECT message with EMM cause value #10 "Implicitly detached". If the tracking area update request is rejected due to general NAS level mobility management congestion control, the network shall set the EMM cause value to #22 "congestion" and assign a value for back-off timer T3346. In NB-S1 mode, if the tracking area update request is rejected due to operator determined barring (see 3GPP TS 29.272[ Evolved Packet System (EPS); Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol ] [16C]), the network shall set the EMM cause value to #22 "congestion" and assign a value for back-off timer T3346. If the tracking area request is rejected due to service gap control as specified in clause 5.3.17 i.e. the T3447 timer is running, the network shall set the EMM cause value to #22 "congestion" and may assign a back-off timer T3346 with the remaining time of the running T3447 timer. If the tracking area update request is rejected due to incompatibility between the CIoT EPS optimizations supported by the UE and what the network supports and the network sets the EMM cause value to #15 "no suitable cells in tracking area", the network may additionally include the Extended EMM cause IE with value "requested EPS optimization not supported". NOTE 1: How the UE uses the Extended EMM cause IE with value "requested EPS optimization not supported" is implementation specific. The UE still behaves according to the EMM cause value #15. Based on operator policy, if the tracking area update request is rejected due to core network redirection for CIoT optimizations, the network shall set the EMM cause value to #31 "Redirection to 5GCN required". NOTE 2: The network can take into account the UE's N1 mode capability, the 5GS CIoT network behaviour supported by the UE or the 5GS CIoT network behaviour supported by the 5GCN to determine the rejection with the EMM cause value #31 "Redirection to 5GCN required". If the UE initiated the tracking area updating procedure due to inter-system change from N1 mode to S1 mode, and the MME does not support N26 interface, the MME shall send a TRACKING AREA UPDATE REJECT message with EMM cause value #9 "UE identity cannot be derived by the network". When the UE performs inter-system change from N1 mode to S1 mode, if the MME is informed that verification of the integrity protection of the TRACKING AREA UPDATE REQUEST message has failed in the AMF, then: a) If the MME can retrieve the current EPS security context as indicated by the eKSI and GUTI sent by the UE, the MME shall proceed as specified in clause 5.5.3.2.4; b) if the MME cannot retrieve the current EPS security context as indicated by the eKSI and GUTI sent by the UE, or the eKSI or GUTI was not sent by the UE, the MME may initiate the identification procedure by sending the IDENTITY REQUEST message with the "Type of identity" of the Identity type IE set to "IMSI" before taking actions as specified in clause 4.4.4.3; or c) If the MME needs to reject the tracking area updating procedure, the MME shall send a TRACKING AREA UPDATE REJECT message with EMM cause value #9 "UE identity cannot be derived by the network". In NB-S1 mode or WB-S1 mode via satellite E-UTRAN access, if the tracking area updating request is from a UE via a satellite E-UTRA cell and the network using the User Location Information provided by the eNodeB (see 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [23]), is able to determine that the UE is in a location where the network is not allowed to operate, the network shall set the EMM cause value in the TRACKING AREA UPDATE REJECT message to #78 "PLMN not allowed to operate at the present UE location". Upon receiving the TRACKING AREA UPDATE REJECT message, if the message is integrity protected or contains a reject cause other than EMM cause value #25, the UE shall stop timer T3430 and stop any transmission of user data. If the TRACKING AREA UPDATE REJECT message with EMM cause #25 or #78 was received without integrity protection, then the UE shall discard the message. If the MME received multiple TAIs from the satellite E-UTRAN as described in 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10], and determines that, by UE subscription and operator's preferences, all of the received TAIs are forbidden for roaming or for regional provision of service, the MME shall include the TAI(s) in: a) the Forbidden TAI(s) for the list of "forbidden tracking areas for roaming" IE; b) the Forbidden TAI(s) for the list of "forbidden tracking areas for regional provision of service" IE; or c) both, in the TRACKING AREA UPDATE REJECT message. Regardless of the EMM cause value received in the TRACKING AREA UPDATE REJECT message via satellite E-UTRAN, - if the UE receives the Forbidden TAI(s) for the list of "forbidden tracking areas for roaming" IE in the TRACKING AREA UPDATE REJECT message, the UE shall store the TAI(s) included in the IE which are belonging to the serving PLMN or equivalent PLMN(s), if not already stored, into the list of "forbidden tracking areas for roaming" and ignore the TAI(s) which do not belong to the serving PLMN or equivalent PLMN(s); and - if the UE receives the Forbidden TAI(s) for the list of "forbidden tracking areas for regional provision of service" IE in the TRACKING AREA UPDATE REJECT message, the UE shall store the TAI(s) included in the IE which are belonging to the serving PLMN or equivalent PLMN(s), if not already stored, into the list of "forbidden tracking areas for regional provision of service" and ignore the TAI(s) which do not belong to the serving PLMN or equivalent PLMN(s) Furthermore. the UE shall take the following actions depending on the EMM cause value received in the TRACKING AREA UPDATE REJECT message. #3 (Illegal UE); #6 (Illegal ME); or #8 (EPS services and non-EPS services not allowed); The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and eKSI. The UE shall consider the USIM as invalid for EPS services until switching off or the UICC containing the USIM is removed or the timer T3245 expires as described in clause 5.3.7a. The UE shall delete the list of equivalent PLMNs and shall enter the state EMM-DEREGISTERED.NO-IMSI. If the message has been successfully integrity checked by the NAS and the UE maintains a counter for "SIM/USIM considered invalid for GPRS services", then the UE shall set this counter to UE implementation-specific maximum value. If A/Gb mode or Iu mode is supported by the UE, the UE shall handle the GMM parameters GMM state, GPRS update status, P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number and the MM parameters update status, TMSI, LAI and ciphering key sequence number as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the normal routing area updating procedure is rejected with the GMM cause with the same value. The USIM shall be considered as invalid also for non-EPS services until switching off or the UICC containing the USIM is removed or the timer T3245 expires as described in clause 5.3.7a. If the message has been successfully integrity checked by the NAS and the UE maintains a counter for "SIM/USIM considered invalid for non-GPRS services", then the UE shall set this counter to UE implementation-specific maximum value. For the EMM cause value #3 or #6, if the UE is operating in single-registration mode, the UE shall in addition handle the 5GMM parameters 5GMM state, 5GS update status, 5G-GUTI, last visited registered TAI, TAI list and ngKSI as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the registration procedure for mobility and periodic registration update performed over 3GPP access and indicating "mobility registration updating" in the 5GS registration type IE of the REGISTRATION REQUEST message is rejected with the 5GMM cause with the same value. For the EMM cause value #8, if the UE is operating in single-registration mode, the UE shall in addition set the 5GMM state to 5GMM-DEREGISTERED, 5GS update status to 5U3 ROAMING NOT ALLOWED, and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. NOTE 3: The possibility to configure a UE so that the radio transceiver for a specific radio access technology is not active, although it is implemented in the UE, is out of scope of the present specification. #7 (EPS services not allowed); The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and eKSI. The UE shall consider the USIM as invalid for EPS services until switching off or the UICC containing the USIM is removed or the timer T3245 expires as described in clause 5.3.7a. The UE shall enter the state EMM-DEREGISTERED. If the message has been successfully integrity checked by the NAS and the UE maintains a counter for "SIM/USIM considered invalid for GPRS services", then the UE shall set this counter to UE implementation-specific maximum value. If the EPS update type is "periodic updating", a UE operating in CS/PS mode 1 or CS/PS mode 2 of operation, which is IMSI attached for non-EPS services, is still IMSI attached for non-EPS services. The UE operating in CS/PS mode 1 or CS/PS mode 2 of operation shall set the update status to U2 NOT UPDATED, shall attempt to select GERAN or UTRAN radio access technology and shall proceed with appropriate MM specific procedure according to the MM service state. The UE shall not reselect E-UTRAN radio access technology until switching off or the UICC containing the USIM is removed. If A/Gb mode or Iu mode is supported by the UE, the UE shall handle the GMM parameters GMM state, GPRS update status, P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the normal routing area updating procedure is rejected with the GMM cause with the same value. If the UE is operating in single-registration mode, the UE shall in addition handle the 5GMM parameters 5GMM state, 5GS update status, 5G-GUTI, last visited registered TAI, TAI list and ngKSI as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the registration procedure for mobility and periodic registration update performed over 3GPP access and indicating "mobility registration updating" in the 5GS registration type IE of the REGISTRATION REQUEST message is rejected with the 5GMM cause with the same value. #9 (UE identity cannot be derived by the network); The UE shall set the EPS update status to EU2 NOT UPDATED (and shall store it according to clause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and eKSI. The UE shall enter the state EMM-DEREGISTERED.NORMAL-SERVICE. If the rejected request was not for initiating a PDN connection for emergency bearer services, the UE shall subsequently, automatically initiate the attach procedure. NOTE 4: User interaction is necessary in some cases when the UE cannot re-activate the EPS bearer(s) automatically. If A/Gb mode or Iu mode is supported by the UE, the UE shall handle the GMM parameters GMM state, GPRS update status, P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the normal routing area updating procedure is rejected with the GMM cause with the same value. If the UE is operating in the single-registration mode, the UE shall handle the 5GMM parameters 5GMM state, 5GS update status, 5G-GUTI, last visited registered TAI, TAI list and ngKSI as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the registration procedure for mobility and periodic registration update performed over 3GPP access and indicating "mobility registration updating" in the 5GS registration type IE of the REGISTRATION REQUEST message is rejected with the 5GMM cause with the same value. #10 (Implicitly detached); If the EPS update type is "periodic updating", a UE in CS/PS mode 1 or CS/PS mode 2 of operation is IMSI detached for both EPS services and non-EPS services. The UE shall enter the state EMM-DEREGISTERED.NORMAL-SERVICE. The UE shall delete any mapped EPS security context or partial native EPS security context. If the rejected request was not for initiating a PDN connection for emergency bearer services, the UE shall then perform a new attach procedure. NOTE 5: User interaction is necessary in some cases when the UE cannot re-activate the EPS bearer(s) automatically. If A/Gb mode or Iu mode is supported by the UE, the UE shall handle the GMM state as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the normal routing area updating procedure is rejected with the GMM cause with the same value. If the UE is operating in single-registration mode, the UE shall in addition handle the 5GMM state as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the registration procedure for mobility and periodic registration update performed over 3GPP access and indicating "mobility registration updating" in the 5GS registration type IE of the REGISTRATION REQUEST message is rejected with the 5GMM cause with the same value. #11 (PLMN not allowed); or #35 (Requested service option not authorized in this PLMN); The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and eKSI. The UE shall reset the tracking area updating attempt counter, delete the list of equivalent PLMNs and enter the state EMM-DEREGISTERED.PLMN-SEARCH. The UE shall store the PLMN identity in the "forbidden PLMN list" and if the UE is configured to use timer T3245 (see 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]) then the UE shall start timer T3245 and proceed as described in clause 5.3.7a. If the message has been successfully integrity checked by the NAS and the UE maintains a PLMN-specific attempt counter for that PLMN, then the UE shall set this counter to the UE implementation-specific maximum value. The UE shall perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. If A/Gb mode or Iu mode is supported by the UE, the UE shall handle the GMM parameters GMM state, GPRS update status, P-TMSI, P-TMSI signature, RAI, GPRS ciphering key sequence number and routing area updating attempt counter and the MM parameters update status, TMSI, LAI, ciphering key sequence number and the location update attempt counter as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the normal routing area updating procedure is rejected with the GMM cause value #11 and no RR connection exists. For the EMM cause value #11, if the UE is operating in single-registration mode, the UE shall in addition handle the 5GMM parameters 5GMM state, 5GS update status, 5G-GUTI, last visited registered TAI, TAI list, ngKSI and registration attempt counter as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the registration procedure for mobility and periodic registration update performed over 3GPP access and indicating "mobility registration updating" in the 5GS registration type IE of the REGISTRATION REQUEST message is rejected with the 5GMM cause with the same value. For the EMM cause value #35, if the UE is operating in single-registration mode, the UE shall in addition set the 5GMM state to 5GMM-DEREGISTERED, 5GS update status to 5U3 ROAMING NOT ALLOWED, and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. In addition, the UE shall reset the registration attempt counter. #12 (Tracking area not allowed); The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and eKSI. The UE shall reset the tracking area updating attempt counter and shall enter the state EMM-DEREGISTERED.LIMITED-SERVICE. The UE shall store the current TAI in the list of "forbidden tracking areas for regional provision of service". If the TRACKING AREA UPDATE REJECT message is not integrity protected, the UE shall memorize the current TAI was stored in the list of "forbidden tracking areas for regional provision of service" for non-integrity protected NAS reject message. If A/Gb mode or Iu mode is supported by the UE, the UE shall handle the GMM parameters GMM state, GPRS update status, P-TMSI, P-TMSI signature, RAI, GPRS ciphering key sequence number and routing area updating attempt counter as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the normal routing area updating procedure is rejected with the GMM cause with the same value. If the UE is operating in single-registration mode, the UE shall in addition handle the 5GMM parameters 5GMM state, 5GS update status, 5G-GUTI, last visited registered TAI, TAI list, ngKSI and registration attempt counter as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the registration procedure for mobility and periodic registration update performed over 3GPP access and indicating "mobility registration updating" in the 5GS registration type IE of the REGISTRATION REQUEST message is rejected with the 5GMM cause with the same value. #13 (Roaming not allowed in this tracking area); The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.3) and shall delete the list of equivalent PLMNs. The UE shall reset the tracking area updating attempt counter and shall change to state EMM-REGISTERED.PLMN-SEARCH. The UE shall store the current TAI in the list of "forbidden tracking areas for roaming" and shall remove the current TAI from the stored TAI list if present. If the TRACKING AREA UPDATE REJECT message is not integrity protected, the UE shall memorize the current TAI was stored in the list of "forbidden tracking areas for roaming" for non-integrity protected NAS reject message. If the UE is registered in N1 mode and operating in dual-registration mode, the PLMN that the UE chooses to register in is specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] clause 4.8.3. Otherwise the UE shall perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. If A/Gb mode or Iu mode is supported by the UE, the UE shall handle the GMM parameters GMM state, GPRS update status and routing area updating attempt counter as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the normal routing area updating procedure is rejected with the GMM cause with the same value. If the UE is operating in single-registration mode, the UE shall in addition handle the 5GMM parameters 5GMM state, 5GS update status, and registration attempt counter as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the registration procedure for mobility and periodic registration update performed over 3GPP access and indicating "mobility registration updating" in the 5GS registration type IE of the REGISTRATION REQUEST message is rejected with the 5GMM cause with the same value. #14 (EPS services not allowed in this PLMN); The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.3). Furthermore, the UE shall delete any GUTI, last visited registered TAI, TAI list and eKSI. The UE shall reset the tracking area updating attempt counter and shall enter the state EMM-DEREGISTERED.PLMN-SEARCH. The UE shall store the PLMN identity in the "forbidden PLMNs for GPRS service" list and if the UE is configured to use timer T3245 (see 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]) then the UE shall start timer T3245 and proceed as described in clause 5.3.7a. If the message has been successfully integrity checked by the NAS and the UE maintains a PLMN-specific PS-attempt counter for that PLMN, then the UE shall set this counter to the UE implementation-specific maximum value. If the EPS update type is "TA updating", or the EPS update type is "periodic updating" and the UE is in PS mode 1 or PS mode 2 of operation, the UE shall perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. In this case, the UE supporting S1 mode only shall delete the list of equivalent PLMNs before performing the procedure. If the EPS update type is "periodic updating", a UE operating in CS/PS mode 1 or CS/PS mode 2 of operation, which is IMSI attached for non-EPS services, is still IMSI attached for non-EPS services and shall proceed as follows: - a UE operating in CS/PS mode 1 or CS/PS mode 2 of operation shall set the update status to U2 NOT UPDATED; - a UE operating in CS/PS mode 1 of operation and supporting A/Gb mode or Iu mode may select GERAN or UTRAN radio access technology and proceed with the appropriate MM specific procedure according to the MM service state. In this case, the UE shall disable the E-UTRA capability (see clause 4.5); - a UE operating in CS/PS mode 1 of operation and supporting A/Gb mode or Iu mode may perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]; - a UE operating in CS/PS mode 1 of operation and supporting S1 mode only, or operating in CS/PS mode 2 of operation shall delete the list of equivalent PLMNs and shall perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. If A/Gb mode or Iu mode is supported by the UE, the UE shall handle the GMM parameters GMM state, GPRS update status, P-TMSI, P-TMSI signature, RAI, GPRS ciphering key sequence number and routing area updating attempt counter as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the normal routing area updating procedure is rejected with the GMM cause with the same value. If the UE is operating in single-registration mode, the UE shall in addition set the 5GMM state to 5GMM-DEREGISTERED, 5GS update status to 5U3 ROAMING NOT ALLOWED, and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. In addition, the UE shall reset the registration attempt counter. #15 (No suitable cells in tracking area); The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.3). The UE shall reset the tracking area updating attempt counter and shall enter the state EMM-REGISTERED.LIMITED-SERVICE. The UE shall store the current TAI in the list of "forbidden tracking areas for roaming". If the TRACKING AREA UPDATE REJECT message is not integrity protected, the UE shall memorize the current TAI was stored in the list of "forbidden tracking areas for roaming" for non-integrity protected NAS reject message. Additionally, the UE shall remove the current TAI from the stored TAI list if present and: - if the UE is in WB-S1 mode and the Extended EMM cause IE with value "E-UTRAN not allowed" is included in the TRACKING AREA UPDATE REJECT message, the UE supports "E-UTRA Disabling for EMM cause #15", and the "E-UTRA Disabling Allowed for EMM cause #15" parameter as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17] is present and set to enabled; then the UE shall disable the E-UTRA capability as specified in clause 4.5 and search for a suitable cell in another location area or 5GS tracking area; - if the UE is in NB-S1 mode and the Extended EMM cause IE with value "NB-IoT not allowed" is included in the TRACKING AREA UPDATE REJECT message, then the UE may disable the NB-IoT capability as specified in clause 4.9 and search for a suitable cell in E-UTRAN radio access technology; - otherwise, the UE shall search for a suitable cell in another tracking area or in another location area according to 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [21]. If A/Gb mode or Iu mode is supported by the UE, the UE shall handle the GMM parameters GMM state, GPRS update status and routing area updating attempt counter as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the normal routing area updating procedure is rejected with the GMM cause with the same value. If the UE is operating in single-registration mode, the UE shall in addition handle the 5GMM parameters 5GMM state, 5GS update status, and registration attempt counter as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the registration procedure for mobility and periodic registration update performed over 3GPP access and indicating "mobility registration updating" in the 5GS registration type IE of the REGISTRATION REQUEST message is rejected with the 5GMM cause with the same value. #22 (Congestion); If the T3346 value IE is present in the TRACKING AREA UPDATE REJECT message and the value indicates that this timer is neither zero nor deactivated, the UE shall proceed as described below, otherwise it shall be considered as an abnormal case and the behaviour of the UE for this case is specified in clause 5.5.3.2.6. The UE shall abort the tracking area updating procedure, reset the tracking area updating attempt counter and set the EPS update status to EU2 NOT UPDATED. If the rejected request was not for initiating a PDN connection for emergency bearer services, the UE shall change to state EMM-REGISTERED.ATTEMPTING-TO-UPDATE. The UE shall stop timer T3346 if it is running. If the TRACKING AREA UPDATE REJECT message is integrity protected, the UE shall start timer with the value provided in the T3346 value IE. If the TRACKING AREA UPDATE REJECT message is not integrity protected, the UE shall start timer T3346 with a random value from the default range specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13]. The UE stays in the current serving cell and applies the normal cell reselection process. The tracking area updating procedure is started, if still necessary, when timer T3346 expires or is stopped. If A/Gb mode or Iu mode is supported by the UE, the UE shall handle the GMM parameters GMM state, GPRS update status and routing area updating attempt counter as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the normal routing area updating procedure is rejected with the GMM cause with the same value. If the tracking area updating procedure was initiated for and MO MMTEL voice or MO MMTEL video call is started, then a notification that the request was not accepted due to network congestion shall be provided to upper layers. NOTE 6: This can result in the upper layers requesting establishment of the originating voice call on an alternative manner e.g. requesting establishment of a CS voice call (see 3GPP TS 24.173[ IMS Multimedia telephony communication service and supplementary services; Stage 3 ] [13E]). If the UE is operating in single-registration mode, the UE shall in addition handle the 5GMM parameters 5GMM state, 5GS update status and registration attempt counter as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the registration procedure for mobility and periodic registration update performed over 3GPP access and indicating "mobility registration updating" in the 5GS registration type IE of the REGISTRATION REQUEST message is rejected with the 5GMM cause with the same value. #25 (Not authorized for this CSG); EMM cause #25 is only applicable when received from a CSG cell. EMM cause #25 received from a non-CSG cell is considered as an abnormal case and the behaviour of the UE is specified in clause 5.5.3.2.6. The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and store it according to clause 5.1.3.3). The UE shall reset the tracking area updating attempt counter and shall enter the state EMM-REGISTERED.LIMITED-SERVICE. If the CSG ID and associated PLMN identity of the cell where the UE has sent the TRACKING AREA UPDATE REQUEST message are contained in the Allowed CSG list, the UE shall remove the entry corresponding to this CSG ID and associated PLMN identity from the Allowed CSG list. If the CSG ID and associated PLMN identity of the cell where the UE has sent the TRACKING AREA UPDATE REQUEST message are contained in the Operator CSG list, the UE shall apply the procedures defined in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6] clause 3.1A. The UE shall search for a suitable cell according to 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [21]. If A/Gb mode or Iu mode is supported by the UE, the UE shall handle the GMM parameters GMM state, GPRS update status and routing area updating attempt counter as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the normal routing area updating procedure is rejected with the GMM cause with the same value. If the UE is operating in single-registration mode, the UE shall in addition set the 5GMM state to 5GMM-REGISTERED and set the 5GS update status to 5U3 ROAMING NOT ALLOWED and reset the registration attempt counter. #31 (Redirection to 5GCN required); EMM cause #31 received by a UE that has not indicated support for CIoT optimizations or not indicated support for N1 mode is considered as an abnormal case and the behaviour of the UE is specified in clause 5.5.3.2.6. The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.3). The UE shall reset the tracking area updating attempt counter and shall enter the state EMM-REGISTERED.LIMITED-SERVICE. The UE shall enable N1 mode capability for 3GPP access if it was disabled and disable the E-UTRA capability (see clause 4.5). If the UE is operating in single-registration mode, the UE shall in addition handle the 5GMM parameters 5GMM state, 5GS update status, and registration attempt counter as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the registration procedure for mobility and periodic registration update performed over 3GPP access and indicating "mobility registration updating" in the 5GS registration type IE of the REGISTRATION REQUEST message is rejected with the 5GMM cause with the same value. #36 (IAB-node operation not authorized); The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and eKSI. The UE shall reset the tracking area updating attempt counter, delete the list of equivalent PLMNs and enter the state EMM-DEREGISTERED.PLMN-SEARCH. The UE shall store the PLMN identity in the "forbidden PLMN list" and if the UE is configured to use timer T3245 (see 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]) then the UE shall start timer T3245 and proceed as described in subclause 5.3.7a. If the message has been successfully integrity checked by the NAS and the UE maintains a PLMN-specific attempt counter for that PLMN, then the UE shall set this counter to the UE implementation-specific maximum value. The UE shall perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. If the UE is operating in single-registration mode, the UE shall in addition handle the 5GMM parameters 5GMM state, 5GS update status, 5G-GUTI, last visited registered TAI, TAI list and ngKSI as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the registration procedure for mobility and periodic registration update performed over 3GPP access and indicating "mobility registration updating" in the 5GS registration type IE of the REGISTRATION REQUEST message is rejected with the 5GMM cause with the same value. #40 (No EPS bearer context activated); The UE shall deactivate all the EPS bearer contexts locally, if any, and shall enter the state EMM-DEREGISTERED.NORMAL-SERVICE. If the rejected request was not for initiating a PDN connection for emergency bearer services, the UE shall perform a new attach procedure. NOTE 7: User interaction is necessary in some cases when the UE cannot re-activate the EPS bearer(s) automatically. If A/Gb mode or Iu mode is supported by the UE, the UE shall handle the GMM state as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the normal routing area updating procedure is rejected with the GMM cause value #10 "Implicitly detached". If the UE is operating in single-registration mode, the UE shall in addition set the 5GMM state to 5GMM-DEREGISTERED. #42 (Severe network failure); The UE shall set the EPS update status to EU2 NOT UPDATED, and shall delete any GUTI, last visited registered TAI, TAI list, eKSI, and list of equivalent PLMNs, and set the tracking area update counter to 5. The UE shall start an implementation specific timer, setting its value to 2 times the value of T as defined in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. While this timer is running, the UE shall not consider the PLMN + RAT combination that provided this reject cause as a candidate for PLMN selection. The UE then enters state EMM-DEREGISTERED.PLMN-SEARCH in order to perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. If A/Gb mode or Iu mode is supported by the UE, the UE shall in addition set the GMM state to GMM-DEREGISTERED, GPRS update status to GU2 NOT UPDATED, and shall delete the P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number. If the UE is operating in single-registration mode, the UE shall in addition set the 5GMM state to 5GMM-DEREGISTERED, 5GS update status to 5U2 NOT UPDATED, and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. #78 (PLMN not allowed to operate at the present UE location). This cause value received from a non-satellite E-UTRA cell is considered as an abnormal case and the behaviour of the UE is specified in clause 5.5.3.2.6. The UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and eKSI. Additionally, the UE shall reset the registration attempt counter. The UE shall store the PLMN identity and, if it is known, the current geographical location in the list of "PLMNs not allowed to operate at the present UE location", start a corresponding timer instance (see subclause 4.11.2), enter state EMM-DEREGISTERED.PLMN-SEARCH and perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. If the UE is operating in single-registration mode, the UE shall in addition handle the 5GMM parameters 5GMM state, 5GS update status, and registration attempt counter as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the registration procedure for mobility and periodic registration update performed over 3GPP access and indicating "mobility registration updating" in the 5GS registration type IE of the REGISTRATION REQUEST message is rejected with the 5GMM cause with the same value. Other values are considered as abnormal cases. The specification of the UE behaviour in those cases is described in clause 5.5.3.2.6. | 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.3.2.5 |
4,551 | 5.8.5.3 Transmission of SLSS | The UE shall select the SLSSID and the slot in which to transmit SLSS as follows: 1> if triggered by NR sidelink communication/discovery/positioning and in coverage on the frequency used for NR sidelink communication/discovery/positioning, as defined in TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [20]; or 1> if triggered by NR sidelink communication/discovery/positioning, and out of coverage on the frequency used for NR sidelink communication/discovery/positioning, and the concerned frequency is included in sl-FreqInfoToAddModList/sl-FreqInfoToAddModListExt in sl-ConfigDedicatedNR within RRCReconfiguration message or included in sl-FreqInfoList/sl-FreqInfoToAddModListExt within SIB12 or SIB23 for NR sidelink positioning: 2> if the UE has selected GNSS as synchronization reference in accordance with 5.8.6.2: 3> select SLSSID 0; 3> use sl-SSB-TimeAllocation1 included in the entry of configured sl-SyncConfigList corresponding to the concerned frequency, that includes txParameters and gnss-Sync; 3> select the slot(s) indicated by sl-SSB-TimeAllocation1; 2> if the UE has selected a cell as synchronization reference in accordance with 5.8.6.2: 3> select the SLSSID included in the entry of configured sl-SyncConfigList corresponding to the concerned frequency, that includes txParameters and does not include gnss-Sync; 3> select the slot(s) indicated by sl-SSB-TimeAllocation1; 1> else if triggered by NR sidelink communication/discovery and the UE has GNSS as the synchronization reference: 2> select SLSSID 0; 2> if sl-SSB-TimeAllocation3 is configured for the frequency used in SidelinkPreconfigNR: 3> select the slot(s) indicated by sl-SSB-TimeAllocation3; 2> else: 3> select the slot(s) indicated by sl-SSB-TimeAllocation1; 1> else: 2> select the synchronisation reference UE (i.e. SyncRef UE) as defined in 5.8.6; 2> if the UE has a selected SyncRef UE and inCoverage in the MasterInformationBlockSidelink message received from this UE is set to true; or 2> if the UE has a selected SyncRef UE and inCoverage in the MasterInformationBlockSidelink message received from this UE is set to false while the SLSS from this UE is part of the set defined for out of coverage, see TS 38.211[ NR; Physical channels and modulation ] [16]: 3> select the same SLSSID as the SLSSID of the selected SyncRef UE; 3> select the slot in which to transmit the SLSS according to the sl-SSB-TimeAllocation1 or sl-SSB-TimeAllocation2 included in the preconfigured sidelink parameters corresponding to the concerned frequency, such that the timing is different from the SLSS of the selected SyncRef UE; 2> else if the UE has a selected SyncRef UE and the SLSS from this UE was transmitted on the slot(s) indicated sl-SSB-TimeAllocation3, which is configured for the frequency used in SidelinkPreconfigNR: 3> select SLSSID 337; 3> select the slot(s) indicated by sl-SSB-TimeAllocation2; 2> else if the UE has a selected SyncRef UE: 3> select the SLSSID from the set defined for out of coverage having an index that is 336 more than the index of the SLSSID of the selected SyncRef UE, see TS 38.211[ NR; Physical channels and modulation ] [16]; 3> select the slot in which to transmit the SLSS according to sl-SSB-TimeAllocation1 or sl-SSB-TimeAllocation2 included in the preconfigured sidelink parameters corresponding to the concerned frequency, such that the timing is different from the SLSS of the selected SyncRef UE; 2> else (i.e. no SyncRef UE selected): 3> if the UE has not randomly selected an SLSSID: 4> randomly select, using a uniform distribution, an SLSSID from the set of sequences defined for out of coverage except SLSSID 336 and 337, see TS 38.211[ NR; Physical channels and modulation ] [16]; 4> select the slot in which to transmit the SLSS according to the sl-SSB-TimeAllocation1 or sl-SSB-TimeAllocation2 (arbitrary selection between these) included in the preconfigured sidelink parameters in SidelinkPreconfigNR corresponding to the concerned frequency; | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.5.3 |
4,552 | E.2 Examples of using measurement reports | The received-signal strength and location information in measurement reports can be used to detect a false base station which attract the UEs by transmitting signal with higher power. They can also be used to detect a false base station which replays the genuine MIB/SIB without modification. In order to detect a false base station which replays modified version of broadcast information to prevent victim UEs from switching back and forth between itself and genuine base stations (e.g. modifying neighbouring cells, cell reselection criteria, registration timers, etc. to avoid the so called ping-pong effect), information on broadcast information can be used to detect inconsistency from the deployment information. Further, a false base station which uses inconsistent cell identifier or operates in inconsistent frequency than the deployment of the genuine base stations, can be detected respectively by using the cell identifier or the frequency information in the measurement reports. Measurement reports collected from multiple UEs can be used to filter out incorrect reports sent by a potential rogue UE. Upon detection of the false base station, the operator can take further actions, e.g. informing legal authorities or contacting the victim UE. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | E.2 |
4,553 | 5.6.2 Interaction between AMF and SMF | The AMF and SMF are separate Network Functions. N1 related interaction with SMF is as follows: - The single N1 termination point is located in AMF. The AMF forwards SM related NAS information to the SMF based on the PDU Session ID in the NAS message. Further SM NAS exchanges (e.g. SM NAS message responses) for N1 NAS signalling received by the AMF over an access (e.g. 3GPP access or non-3GPP access) are transported over the same access. - The serving PLMN ensures that subsequent SM NAS exchanges (e.g. SM NAS message responses) for N1 NAS signalling received by the AMF over an access (e.g. 3GPP access or non-3GPP access) are transported over the same access. - SMF handles the Session management part of NAS signalling exchanged with the UE. - The UE shall only initiate PDU Session Establishment in RM-REGISTERED state. - When a SMF has been selected to serve a specific PDU Session, AMF has to ensure that all NAS signalling related with this PDU Session is handled by the same SMF instance. - Upon successful PDU Session Establishment, the AMF and SMF stores the Access Type that the PDU Session is associated. N11 related interaction with SMF is as follows: - The AMF reports the reachability of the UE based on a subscription from the SMF, including: - The UE location information with respect to the area of interest indicated by the SMF. - The SMF indicates to AMF when a PDU Session has been released. - Upon successful PDU Session Establishment, AMF stores the identification of serving SMF of UE and SMF stores the identification of serving AMF of UE including the AMF set. When trying to reach the AMF serving the UE, the SMF may need to apply the behaviour described for "the other CP NFs" in clause 5.21. N2 related interaction with SMF is as follows: - Some N2 signalling (such as handover related signalling) may require the action of both AMF and SMF. In such case, the AMF is responsible to ensure the coordination between AMF and SMF. The AMF may forward the SM N2 signalling towards the corresponding SMF based on the PDU Session ID in N2 signalling. - SMF shall provide PDU Session Type together with PDU Session ID to NG-RAN, in order to facilitate NG-RAN to apply suitable header compression mechanism to packet of different PDU type. Details refer to TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [34]. N3 related interaction with SMF is as follows: - Selective activation and deactivation of UP connection of existing PDU Session is defined in clause 5.6.8. N4 related interaction with SMF is as follows: - When it is made aware by the UPF that some DL data has arrived for a UE without downlink N3 tunnel information, the SMF interacts with the AMF to initiate Network Triggered Service Request procedure. In this case, if the SMF is aware that the UE is unreachable or if the UE is reachable only for regulatory prioritized service and the PDU Session is not for regulatory prioritized service, then the SMF shall not inform DL data notification to the AMF The AMF is responsible of selecting the SMF per procedures described in clause 6.3.2. For this purpose, it gets subscription data from the UDM that are defined in that clause. Furthermore, it retrieves the subscribed UE-AMBR from the UDM, and optionally dynamic serving network UE-AMBR from PCF based on operator local policy, and sends to the (R)AN as defined in clause 5.7.2 AMF-SMF interactions to support LADN or LADN per DNN and S-NSSAI are defined in clause 5.6.5 and in clause 5.6.5a. In order to support charging and to fulfil regulatory requirement (in order to provide NPLI (Network Provided Location Information) as defined in TS 23.228[ IP Multimedia Subsystem (IMS); Stage 2 ] [15]) related with the set-up, modification and release of IMS Voice calls or with SMS transfer the following applies - At the time of the PDU Session Establishment, the AMF provides the SMF with the PEI of the UE if the PEI is available at the AMF. - When it forwards UL NAS or N2 signalling to a peer NF (e.g. to SMF or to SMSF) or during the UP connection activation of a PDU Session, the AMF provides any User Location Information it has received from the 5G-AN as well as the Access Type (3GPP - Non 3GPP) of the AN over which it has received the UL NAS or N2 signalling. The AMF also provides the corresponding UE Time Zone. In addition, in order to fulfil regulatory requirement (i.e. providing Network Provided Location Information (NPLI), as defined in TS 23.228[ IP Multimedia Subsystem (IMS); Stage 2 ] [15]) when the access is non-3GPP, the AMF may also provide the last known 3GPP access User Location Information with its age, if the UE is still attached to the same AMF for 3GPP access (i.e. valid User Location Information). The User Location Information, the access type and the UE Time Zone may be further provided by SMF to PCF. The PCF may get this information from the SMF in order to provide NPLI to applications (such as IMS) that have requested it. The User Location Information may correspond to: - In the case of 3GPP access: TAI, Cell-Id. The AMF includes only the Primary Cell-Id even if it had received also the Cell-Id of the Primary cell in the Secondary RAN node from NG-RAN. - In the case of Untrusted non-3GPP access: TAI, the UE local IP address used to reach the N3IWF and optionally the UDP source port number if NAT is detected. - In the case of Trusted non-3GPP access: TAI, TNAP/TWAP Identifier, the UE/N5CW device local IP address used to reach the TNGF/TWIF and optionally the UDP source port number if NAT is detected. When the UE uses WLAN based on IEEE 802.11 technology to reach the TNGF, the TNAP Identifier shall include the SSID of the access point to which the UE is attached. The TNAP Identifier shall include at least one of the following elements, unless otherwise determined by the TWAN operator's policies: - the BSSID (see IEEE Std 802.11-2012 [106]); - civic address information of the TNAP to which the UE is attached. The TWAP Identifier shall include the SSID of the access point to which the NC5W is attached. The TWAP Identifier shall also include at least one of the following elements, unless otherwise determined by the TWAN operator's policies: - the BSSID (see IEEE Std 802.11-2012 [106]); - civic address information of the TWAP to which the UE is attached. NOTE 1: The SSID can be the same for several TNAPs/TWAPs and SSID only cannot provide a location, but it might be sufficient for charging. NOTE 2: the BSSID associated with a TNAP/TWAP is assumed to be static. - In the case of W-5GAN access: The User Location Information for W-5GAN is defined in TS 23.316[ Wireless and wireline convergence access support for the 5G System (5GS) ] [84]. When the SMF receives a request to provide Access Network Information reporting while there is no action to carry out towards the 5G-AN or the UE (e.g. no QoS Flow to create / Update / modify), the SMF may request User Location Information from the AMF. The interaction between AMF and SMF(s) for the case of a I-SMF insertion, relocation or removal for a PDU session is described in clause 5.34. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.6.2 |
4,554 | – PUSCH-PowerControl | The IE PUSCH-PowerControl is used to configure UE specific power control parameter for PUSCH. PUSCH-PowerControl information element -- ASN1START -- TAG-PUSCH-POWERCONTROL-START PUSCH-PowerControl ::= SEQUENCE { tpc-Accumulation ENUMERATED { disabled } OPTIONAL, -- Need S msg3-Alpha Alpha OPTIONAL, -- Need S p0-NominalWithoutGrant INTEGER (-202..24) OPTIONAL, -- Need M p0-AlphaSets SEQUENCE (SIZE (1..maxNrofP0-PUSCH-AlphaSets)) OF P0-PUSCH-AlphaSet OPTIONAL, -- Need M pathlossReferenceRSToAddModList SEQUENCE (SIZE (1..maxNrofPUSCH-PathlossReferenceRSs)) OF PUSCH-PathlossReferenceRS OPTIONAL, -- Need N pathlossReferenceRSToReleaseList SEQUENCE (SIZE (1..maxNrofPUSCH-PathlossReferenceRSs)) OF PUSCH-PathlossReferenceRS-Id OPTIONAL, -- Need N twoPUSCH-PC-AdjustmentStates ENUMERATED {twoStates} OPTIONAL, -- Need S deltaMCS ENUMERATED {enabled} OPTIONAL, -- Need S sri-PUSCH-MappingToAddModList SEQUENCE (SIZE (1..maxNrofSRI-PUSCH-Mappings)) OF SRI-PUSCH-PowerControl OPTIONAL, -- Need N sri-PUSCH-MappingToReleaseList SEQUENCE (SIZE (1..maxNrofSRI-PUSCH-Mappings)) OF SRI-PUSCH-PowerControlId OPTIONAL -- Need N } P0-PUSCH-AlphaSet ::= SEQUENCE { p0-PUSCH-AlphaSetId P0-PUSCH-AlphaSetId, p0 INTEGER (-16..15) OPTIONAL, -- Need S alpha Alpha OPTIONAL -- Need S } P0-PUSCH-AlphaSetId ::= INTEGER (0..maxNrofP0-PUSCH-AlphaSets-1) PUSCH-PathlossReferenceRS ::= SEQUENCE { pusch-PathlossReferenceRS-Id PUSCH-PathlossReferenceRS-Id, referenceSignal CHOICE { ssb-Index SSB-Index, csi-RS-Index NZP-CSI-RS-ResourceId } } PUSCH-PathlossReferenceRS-r16 ::= SEQUENCE { pusch-PathlossReferenceRS-Id-r16 PUSCH-PathlossReferenceRS-Id-v1610, referenceSignal-r16 CHOICE { ssb-Index-r16 SSB-Index, csi-RS-Index-r16 NZP-CSI-RS-ResourceId } } DummyPathlossReferenceRS-v1710 ::= SEQUENCE { pusch-PathlossReferenceRS-Id-r17 PUSCH-PathlossReferenceRS-Id-r17, additionalPCI-r17 AdditionalPCIIndex-r17 OPTIONAL -- Need R } PUSCH-PathlossReferenceRS-Id ::= INTEGER (0..maxNrofPUSCH-PathlossReferenceRSs-1) PUSCH-PathlossReferenceRS-Id-v1610 ::= INTEGER (maxNrofPUSCH-PathlossReferenceRSs..maxNrofPUSCH-PathlossReferenceRSs-1-r16) PUSCH-PathlossReferenceRS-Id-r17 ::= INTEGER (0..maxNrofPUSCH-PathlossReferenceRSs-1-r16) SRI-PUSCH-PowerControl ::= SEQUENCE { sri-PUSCH-PowerControlId SRI-PUSCH-PowerControlId, sri-PUSCH-PathlossReferenceRS-Id PUSCH-PathlossReferenceRS-Id, sri-P0-PUSCH-AlphaSetId P0-PUSCH-AlphaSetId, sri-PUSCH-ClosedLoopIndex ENUMERATED { i0, i1 } } SRI-PUSCH-PowerControlId ::= INTEGER (0..maxNrofSRI-PUSCH-Mappings-1) PUSCH-PowerControl-v1610 ::= SEQUENCE { pathlossReferenceRSToAddModListSizeExt-v1610 SEQUENCE (SIZE (1..maxNrofPUSCH-PathlossReferenceRSsDiff-r16)) OF PUSCH-PathlossReferenceRS-r16 OPTIONAL, -- Need N pathlossReferenceRSToReleaseListSizeExt-v1610 SEQUENCE (SIZE (1..maxNrofPUSCH-PathlossReferenceRSsDiff-r16)) OF PUSCH-PathlossReferenceRS-Id-v1610 OPTIONAL, -- Need N p0-PUSCH-SetList-r16 SEQUENCE (SIZE (1..maxNrofSRI-PUSCH-Mappings)) OF P0-PUSCH-Set-r16 OPTIONAL, -- Need R olpc-ParameterSet SEQUENCE { olpc-ParameterSetDCI-0-1-r16 INTEGER (1..2) OPTIONAL, -- Need R olpc-ParameterSetDCI-0-2-r16 INTEGER (1..2) OPTIONAL -- Need R } OPTIONAL, -- Need M ..., [[ sri-PUSCH-MappingToAddModList2-r17 SEQUENCE (SIZE (1..maxNrofSRI-PUSCH-Mappings)) OF SRI-PUSCH-PowerControl OPTIONAL, -- Need N sri-PUSCH-MappingToReleaseList2-r17 SEQUENCE (SIZE (1..maxNrofSRI-PUSCH-Mappings)) OF SRI-PUSCH-PowerControlId OPTIONAL, -- Need N p0-PUSCH-SetList2-r17 SEQUENCE (SIZE (1..maxNrofSRI-PUSCH-Mappings)) OF P0-PUSCH-Set-r16 OPTIONAL, -- Need R dummy SEQUENCE (SIZE (1..maxNrofPUSCH-PathlossReferenceRSs-r16)) OF DummyPathlossReferenceRS-v1710 OPTIONAL -- Need N ]] } P0-PUSCH-Set-r16 ::= SEQUENCE { p0-PUSCH-SetId-r16 P0-PUSCH-SetId-r16, p0-List-r16 SEQUENCE (SIZE (1..maxNrofP0-PUSCH-Set-r16)) OF P0-PUSCH-r16 OPTIONAL, -- Need R ... } P0-PUSCH-SetId-r16 ::= INTEGER (0..maxNrofSRI-PUSCH-Mappings-1) P0-PUSCH-r16 ::= INTEGER (-16..15) -- TAG-PUSCH-POWERCONTROL-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,555 | 5.8.2.3.3 Management of CN Tunnel Info in the UPF | The UPF shall manage the CN Tunnel Info space. When a new CN Tunnel Info is needed, the SMF shall request over N4 the UPF to allocate CN Tunnel Info for the applicable N3/N9 reference point. In response, the UPF provides CN Tunnel Info to the SMF. In the case of PDU Session Release or a UPF is removed from the user plane path of an existing PDU Session, the SMF shall request UPF to release CN Tunnel Info for the PDU Session. If the corresponding N4 Session is released the UPF releases the associated CN Tunnel Info. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.8.2.3.3 |
4,556 | J.1.2 Procedure | As described in TS 23.216[ Single Radio Voice Call Continuity (SRVCC); Stage 2 ] [72], there is no direct interface between the AMF in 5G and the MSC in UTRAN to support SRVCC, so the keys used to protect the SRVCC session once the UE is handed over to UTRAN are derived by MME based on security context mapping from 5G to E-UTRAN and then forwarded to the MSC during the HO procedure. The procedure is initiated when the gNB wants to trigger a 5G SRVCC handover to UTRAN. Figure J.1.2-1: Key derivation of 5G SRVCC from NR to UTRAN 1. The gNB sends Handover required message to the AMF. 2. The AMF shall derive a new KASME_SRVCC key using the KAMF key and the current downlink 5G NAS COUNT of the current 5G security context as described in clause A.21. The AMF increases the downlink 5G NAS COUNT by one. 3. The AMF shall assign the value of ngKSI to the eKSI (maps ngKSI to eKSI) and shall transfer the new KASME_SRVCC key and the UE security capability to the MME_SRVCC via Forward relocation request message. 4. The MME_SRVCC shall derive the CKSRVCC, IKSRVCC based on the new KASME_SRVCC key as in clause A.12 in TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [10] using a downlink NAS COUNT of zero. 5. The MME_SRVCC assigns the value of eKSI to KSISRVCC (maps eKSI to KSISRVCC) and transfers CKSRVCC, IKSRVCC with KSISRVCC and the UE security capability to the MSC server in PS to CS HO request message. 6. The MSC server sends the PS to CS HO response message to the MME_SRVCC. 7. The MME_SRVCC sends the Forward relocation response message to the AMF. 8. The AMF sends the HO command to the gNB, in which the AMF shall include the 4 LSBs of the downlink NAS COUNT used to calculate KASME_SRVCC. 9. The gNB sends the HO command to the UE, in which the gNB shall include the 4 LSB of the downlink NAS COUNT received from the AMF. 10. When the UE receives the message, the UE shall derive the new KASME_SRVCC key as described in Annex A.21 using the KAMF key and the downlink 5G NAS COUNT estimated from the 4 LSB received form the AMF. The UE shall further derive CKSRVCC, IKSRVCC based on the new KASME_SRVCC key as described in the clause A.12 in TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [10] using a downlink NAS COUNT of zero. The UE shall identify the CKSRVCC and IKSRVCC from eKSI (= ngKSI) as the MME_SRVCC does. If the SRVCC handover is not completed successfully, the new mapped CKSRVCC, IKSRVCC and KSISRVCC cannot be used. In this case, the MSC server enhanced for SRVCC shall delete the newly mapped SRVCC security context for the UE, including CKSRVCC, IKSRVCC and KSISRVCC. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | J.1.2 |
4,557 | A.4 Causes related to invalid messages | Cause #95 – Semantically incorrect message This 5GMM cause is used to report receipt of a message with semantically incorrect contents. Cause #96 – Invalid mandatory information This cause 5GMM indicates that the equipment sending this 5GMM cause has received a message with a non-semantical mandatory IE error. Cause #97 – Message type non-existent or not implemented This 5GMM cause indicates that the equipment sending this 5GMM cause has received a message with a message type it does not recognize either because this is a message not defined, or defined but not implemented by the equipment sending this 5GMM cause. Cause #98 – Message type not compatible with protocol state This 5GMM cause indicates that the equipment sending this 5GMM cause has received a message not compatible with the protocol state. Cause #99 – Information element non-existent or not implemented This 5GMM cause indicates that the equipment sending this 5GMM cause has received a message which includes information elements not recognized because the information element identifier is not defined or it is defined but not implemented by the equipment sending the 5GMM cause. However, the information element is not required to be present in the message in order for the equipment sending the 5GMM cause to process the message. Cause #100 – Conditional IE error This 5GMM cause indicates that the equipment sending this cause has received a message with conditional IE errors. Cause #101 – Message not compatible with protocol state This 5GMM cause indicates that a message has been received which is incompatible with the protocol state. Cause #111 – Protocol error, unspecified This 5GMM cause is used to report a protocol error event only when no other 5GMM cause in the protocol error class applies. | 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 | A.4 |
4,558 | 4.12a.5 UE Requested PDU Session Establishment via Trusted non-3GPP Access | After the UE registers to 5GC via trusted non-3GPP access, the UE may request a PDU Session establishment by using the same procedure as the one specified in clause 4.12.5 for untrusted non-3GPP access, with the following modifications: - The N3IWF in Figure 4.12.5-1 should be substituted with a TNGF and the Untrusted non-3GPP access should be substituted with a Trusted non-3GPP Access Point (TNAP). - The TNGF may send a TNGF Identities parameter to AMF inside an N2 Uplink NAS Transport message. The TNGF Identities parameter contains a list of identifiers (i.e. FQDNs or IP addresses) of N3 terminations supported by the TNGF. If received by the AMF, it shall forward it to the SMF, which may use it as input to UPF selection. The AMF provides ULI information received from TNGF to the SMF which then propagates it to the PCF. - The IKEv2 Create Child SA Request message that is sent by the TNGF to UE (in steps 4a and 4c), in order to establish a child SA for one or more QoS flows, shall also include Additional QoS Information. The Additional QoS Information shall contain: a) If the IPsec child SA carries a GBR flow: QoS Characteristics and GBR QoS Flow Information: - The QoS Characteristics are associated with the 5QI of the GBR flow and are defined in clause 5.7.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The TNGF either receives the QoS Characteristics via the N2 interface (in the case of a dynamically assigned 5QI), or is pre-configured with the QoS Characteristics (in the case of a standardized 5QI). - The GBR QoS Flow Information (defined in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [10]) is part of the QoS Profile received via the N2 interface and contains: MFBR, GFBR and optionally Maximum Packet Loss Rate. The Notification Control is not included in the QoS profile. b) If the IPsec child SA carries a non-GBR flow: QoS Characteristics: - The QoS Characteristics are defined in bullet a) above. The TNGF may aggregate multiple GBR flows or multiple non-GBR flows into the same IPsec child SA. In this case, the TNGF derives, in an implementation specific way, the QoS Characteristics of the aggregated flow by considering the QoS Characteristics of the individual flows. Similarly, the TNGF derives, in an implementation specific way, the GBR QoS Flow Information of an aggregated GBR flow by considering the GBR QoS Flow Information of the individual GBR flows. NOTE: The above behaviour of the TNGF does not create any impact on the N2 interface. - After receiving an IKEv2 Create Child SA Request message, the UE shall use the Additional QoS Information contained in this message to determine what QoS resources to reserve over the non-3GPP access, including e.g. guaranteed bit rates and delay bounds for UL/DL communication. How the UE determines what QoS resources to reserve over the non-3GPP access and how these QoS resources are reserved, is outside the scope of 3GPP specifications. - If the UE fails to reserve QoS resources over non-3GPP access for the QoS flows associated with the child SA (e.g. because the non-3GPP Access Network rejects the allocation of the requested bit rates), the UE shall reject the IKEv2 Child SA Request. Based on operator policy, the network may reattempt to establish the Child SA without the Additional QoS Information. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.12a.5 |
4,559 | 8.4.2.2.9 Enhanced Downlink Control Channel Performance Requirement Type A - 4 Tx Antenna Port with Non-Colliding CRS Dominant Interferer | The purpose of this test is to verify the Enhanced Downlink Control Channel Performance Requirement Type A for PDCCH/PCFICH with 4 transmit antennas for the case of dominant interferer with the non-colliding CRS pattern and applying interference model defined in clause B.7.1. For the parameters specified in Table 8.4.1-1 and Table 8.4.2.2.9-1, the average probability of a missed downlink scheduling grant (Pm-dsg) shall be below the specified value in Table 8.4.2.2.9-2. In Table 8.4.2.2.9-1, Cell 1 is the serving cell, and Cell 2 and Cell 3 are the aggressor cells. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1, Cell 2 and Cell 3, respectively. The CRS assistance information [7] is provided and includes information on Cell 2 and Cell 3. Table 8.4.2.2.9-1: Test Parameters for PDCCH/PCFICH Table 8.4.2.2.9-2: Minimum Performance for PDCCH/PCFICH for Enhanced Downlink Control Channel Performance Requirement Type A | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.4.2.2.9 |
4,560 | 5.8.8 Sidelink communication transmission | A UE capable of NR sidelink communication that is configured by upper layers to transmit NR sidelink communication and has related data to be transmitted shall: 1> if the conditions for NR sidelink communication operation as defined in 5.8.2 are met: 2> if the frequency used for NR sidelink communication is included in sl-FreqInfoToAddModList/sl-FreqInfoToAddModListExt in sl-ConfigDedicatedNR within RRCReconfiguration message or included in sl-ConfigCommonNR within SIB12: 3> if the UE is in RRC_CONNECTED and uses the frequency included in sl-ConfigDedicatedNR within RRCReconfiguration message: 4> if the UE acting as U2U Relay UE is performing U2U Relay Communication with integrated Discovery as specified in TS 23.304[ Proximity based Services (ProSe) in the 5G System (5GS) ] [65] and sl-DiscConfig is included in RRCReconfiguration, and if the NR sidelink U2U Relay UE threshold conditions as specified in 5.8.16.2 are met based on sl-RelayUE-ConfigU2U; or 4> if the UE is performing NR sidelink communication other than U2U Relay Communication with integrated Discovery: NOTE 0: For U2U Relay UE, it can be up to UE implementation on cross-layer interaction for the AS layer condition check for Direct Communication Request message with integrated discovery forwarding. 5> if the UE is configured with sl-ScheduledConfig: 6> if T310 for MCG or T311 is running; and if sl-TxPoolExceptional is included in sl-FreqInfoList/sl-FreqInfoListSizeExt for the concerned frequency in SIB12 or included in sl-ConfigDedicatedNR in RRCReconfiguration; or 6> if T301 is running and the cell on which the UE initiated RRC connection re-establishment provides SIB12 including sl-TxPoolExceptional for the concerned frequency; or 6> if T304 for MCG is running and the UE is configured with sl-TxPoolExceptional included in sl-ConfigDedicatedNR for the concerned frequency in RRCReconfiguration: 7> configure lower layers to perform the sidelink resource allocation mode 2 based on random selection using the pool of resources indicated by sl-TxPoolExceptional as defined in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3]; 6> else: 7> configure lower layers to perform the sidelink resource allocation mode 1 for NR sidelink communication; 6> if T311 is running, configure the lower layers to release the resources indicated by rrc-ConfiguredSidelinkGrant (if any); 5> if the UE is configured with sl-UE-SelectedConfig: 6> if a result of full/partial sensing, if selected and is allowed 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]; 7> if sl-TxPoolExceptional for the concerned frequency is included in RRCReconfiguration; or 7> if the PCell provides SIB12 including sl-TxPoolExceptional in sl-FreqInfoList/sl-FreqInfoListSizeExt for the concerned frequency: 8> configure lower layers to perform the sidelink resource allocation mode 2 based on random selection using the pool of resources indicated by sl-TxPoolExceptional as defined in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3]; 6> else, if the sl-TxPoolSelectedNormal for the concerned frequency is included in the sl-ConfigDedicatedNR within RRCReconfiguration: 7> configure lower layers to perform the sidelink resource allocation mode 2 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 communication transmission provides SIB12: 5> if the UE acting as U2U Relay UE is performing U2U Relay communication with integrated Discovery as specified in TS 23.304[ Proximity based Services (ProSe) in the 5G System (5GS) ] [65], and if the NR sidelink U2U Relay UE threshold conditions as specified in 5.8.16.2 are met based on sl-RelayUE-ConfigCommonU2U in SIB12; or 5> if the UE is performing NR sidelink communication other than U2U Relay Communication with integrated Discovery: 6> if SIB12 includes sl-TxPoolSelectedNormal for the concerned frequency, and a result of full/partial 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: 7> configure lower layers to perform the sidelink resource allocation mode 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]; 6> else if SIB12 includes sl-TxPoolExceptional for the concerned frequency: 7> 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 7> if a result of full/partial sensing, if selected and is allowed by sl-AllowedResourceSelectionConfig, on the resources configured in sl-TxPoolSelectedNormal for the concerned frequency in SIB12 is not available in accordance with TS 38.214[ NR; Physical layer procedures for data ] [19]: 8> configure lower layers to perform the sidelink resource allocation mode 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-TxPoolExceptional for the concerned frequency; 2> else: 3> if the UE acting as U2U Relay UE is performing U2U Relay communication with integrated Discovery as specified in TS 23.304[ Proximity based Services (ProSe) in the 5G System (5GS) ] [65], and if the NR sidelink U2U Relay UE threshold conditions as specified in 5.8.16.2 are met based on sl-RelayUE-PreconfigU2U in SidelinkPreconfigNR; or 3> if the UE is performing NR sidelink communication other than U2U Relay Communication with integrated Discovery: 4> configure lower layers to perform the sidelink resource allocation mode 2 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 in SidelinkPreconfigNR for the concerned frequency. NOTE 1: The UE continues to use resources configured in rrc-ConfiguredSidelinkGrant (while T310 is running) until it is released (i.e. until T310 has expired). The UE does not use sidelink configured grant type 2 resources while T310 is running. NOTE 2: In case of RRC reconfiguration with sync, the UE uses resources configured in rrc-ConfiguredSidelinkGrant (while T304 on the MCG is running) if provided by the target cell. NOTE 3: It is up to UE implementation to determine, in accordance with TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3], which resource pool to use if multiple resource pools are configured, and which resource allocation scheme is used in the AS based on UE capability (for a UE in RRC_IDLE/RRC_INACTIVE) and the allowed resource schemes sl-AllowedResourceSelectionConfig in the resource pool configuration. NOTE 4: In case that the network does not provide resource pools in SIB12, a UE which is out of coverage, will be unable to obtain sidelink resources to send the first UL RRC message. If configured to perform sidelink resource allocation mode 2, the UE capable of NR sidelink communication that is configured by upper layers to transmit NR sidelink communication shall perform resource selection operation according to sl-AllowedResourceSelectionConfig on all pools of resources which may be used for transmission of the sidelink control information and the corresponding data. The pools of resources are indicated by SidelinkPreconfigNR, sl-TxPoolSelectedNormal in sl-ConfigDedicatedNR, or sl-TxPoolSelectedNormal in SIB12 for the concerned frequency, as configured above. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.8 |
4,561 | 5.30.3.5 Support of emergency services in CAG cells | Emergency Services are supported in CAG cells, for UEs supporting CAG, whether normally registered or emergency registered as described in clause 5.16.4 and in clause 4.13.4 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. A UE may camp on an acceptable CAG cell in limited service state as specified in TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [17] and TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [50], based on operator policy defined in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27]. NOTE: Support for Emergency services requires each cell with a Cell Identity associated with PLMNs or PNI-NPNs to only be connected to AMFs that supports emergency services. The UE shall select a PLMN (of a CAG cell or non-CAG cell), as described in TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [17] and TS 23.167[ IP Multimedia Subsystem (IMS) emergency sessions ] [18], when initiating emergency services from limited service state. During handover to a CAG cell, if the UE is not authorized to access the target CAG cell as described in clause 5.30.3.4 and has emergency services, the target NG-RAN node only accepts the emergency PDU Session and the target AMF releases the non-emergency PDU Sessions that were not accepted by the NG-RAN node. Upon completion of handover the UE behave as emergency registered. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.30.3.5 |
4,562 | 9.1.1.4 SCCH configuration | Parameters that are specified for unicast of NR sidelink communication, which is used for the sidelink signalling radio bearer of PC5-RRC message. The SL-SRB using this SCCH configuration is named as SL-SRB3. Parameters that are specified of NR sidelink communication, which is used for the sidelink signalling radio bearer of unprotected PC5-S message (e.g. Direct Link Establishment Request, TS 24.587[ Vehicle-to-Everything (V2X) services in 5G System (5GS); Stage 3 ] [57] or Prose Direct Link Establishment Request, TS 24.554[ Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3 ] [72]). The SL-SRB using this SCCH configuration is named as SL-SRB0. Parameters that are specified for unicast of NR sidelink communication, which is used for the sidelink signalling radio bearer of PC5-S message establishing PC5-S security (e.g. Direct Link Security Mode Command and Direct Link Security Mode Complete, TS 24.587[ Vehicle-to-Everything (V2X) services in 5G System (5GS); Stage 3 ] [57] or ProSe Direct Link Security Mode Command and ProSe Direct Link Security Mode Complete, TS 24.554[ Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3 ] [72]). The SL-SRB using this SCCH configuration is named as SL-SRB1. Parameters that are specified for unicast of NR sidelink communication, which is used for the sidelink signalling radio bearer of protected PC5-S message except Direct Link Security Mode Complete, TS 24.587[ Vehicle-to-Everything (V2X) services in 5G System (5GS); Stage 3 ] [57] or Prose Direct Link Security Mode Complete, TS 24.554[ Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3 ] [72]. The SL-SRB using this SCCH configuration is named as SL-SRB2. Parameters that are specified for NR sidelink discovery, which is used for the sidelink signalling radio bearer of NR sidelink discovery messages (e.g., Announcement message, Solicitation message and Response message, see TS 23.304[ Proximity based Services (ProSe) in the 5G System (5GS) ] [65]). The SL-SRB using this SCCH configuration is named as SL-SRB4. Parameters that are specified for NR sidelink L2 U2N Relay operations, which is used for the PC5 Relay RLC channel for Remote UE's SRB0 message transmission/reception. The PC5 Relay RLC channel using this configuration is named as SL-RLC0. Parameters that are specified for NR sidelink L2 U2U Relay operations, which is used for the PC5 Relay RLC channel for U2U Remote UE's SL-SRB0/1/2/3 message transmission/reception with the peer U2U Remote UE. The PC5 Relay RLC channel using this configuration is named as SL-U2U-RLC. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 9.1.1.4 |
4,563 | 6.2.4 gNB-CU-UP ID | The gNB-CU-UP ID is configured at the gNB-CU-CP and used to uniquely identify the gNB-CU-UP at least within a gNB-CU-CP. The gNB-CU-UP provides its gNB-CU-UP ID to the gNB-CU-CP during the E1 Setup procedure. The gNB-CP-UP ID is used only within E1AP procedures. NOTE 1: This identity is also used to uniquely identify the ng-eNB-CU-UP at least within an ng-eNB-CU-CP in case CP/UP separation is implemented in ng-eNB. NOTE 2: This identity is also used to uniquely identify the eNB at least within an eNB-CP in case CP/UP separation is implemented in eNB. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 6.2.4 |
4,564 | 6.1 GPRS Session management 6.1.1 General | The main function of the session management (SM) is to support PDP context handling of the user terminal. Furthermore, the SM supports the MBMS context handling within the MS and the network, which allows the MS to receive data from a specific MBMS source. The SM comprises procedures for - identified PDP context activation, deactivation and modification; and - identified MBMS context activation and deactivation. SM procedures for identified access can only be performed if a GMM context has been established between the MS and the network. If no GMM context has been established, the MM sublayer has to initiate the establishment of a GMM context by use of the GMM procedures as described in chapter 4. After GMM context establishment, SM uses services offered by GMM (see 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [20]). Ongoing SM procedures are suspended during GMM procedure execution. The SM procedures for identified MBMS context activation and deactivation can only be performed, if in addition to the GMM context the MS has a PDP context activated. In Iu mode only, integrity protected signalling (see subclause 4.1.1.1.1 of the present document and in general, see 3GPP TS 33.102[ 3G security; Security architecture ] [5a]) is mandatory. In Iu mode only, all protocols shall use integrity protected signalling. Integrity protection of all SM signalling messages is the responsibility of lower layers. It is the network which activates integrity protection. This is done using the security mode control procedure (3GPP TS 25.331[ None ] [23c] and 3GPP TS 44.118[ None ] [111]). For the session management protocol, the extended TI mechanism may be used (see 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [20]). | 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 |
4,565 | – RACH-ConfigCommon | The IE RACH-ConfigCommon is used to specify the cell specific random-access parameters. RACH-ConfigCommon information element -- ASN1START -- TAG-RACH-CONFIGCOMMON-START RACH-ConfigCommon ::= SEQUENCE { rach-ConfigGeneric RACH-ConfigGeneric, totalNumberOfRA-Preambles INTEGER (1..63) OPTIONAL, -- Need S ssb-perRACH-OccasionAndCB-PreamblesPerSSB CHOICE { oneEighth ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64}, oneFourth ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64}, oneHalf ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64}, one ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64}, two ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32}, four INTEGER (1..16), eight INTEGER (1..8), sixteen INTEGER (1..4) } OPTIONAL, -- Need M groupBconfigured SEQUENCE { ra-Msg3SizeGroupA ENUMERATED {b56, b144, b208, b256, b282, b480, b640, b800, b1000, b72, spare6, spare5,spare4, spare3, spare2, spare1}, messagePowerOffsetGroupB ENUMERATED { minusinfinity, dB0, dB5, dB8, dB10, dB12, dB15, dB18}, numberOfRA-PreamblesGroupA INTEGER (1..64) } OPTIONAL, -- Need R ra-ContentionResolutionTimer ENUMERATED { sf8, sf16, sf24, sf32, sf40, sf48, sf56, sf64}, rsrp-ThresholdSSB RSRP-Range OPTIONAL, -- Need R rsrp-ThresholdSSB-SUL RSRP-Range OPTIONAL, -- Cond SUL prach-RootSequenceIndex CHOICE { l839 INTEGER (0..837), l139 INTEGER (0..137) }, msg1-SubcarrierSpacing SubcarrierSpacing OPTIONAL, -- Cond L139 restrictedSetConfig ENUMERATED {unrestrictedSet, restrictedSetTypeA, restrictedSetTypeB}, msg3-transformPrecoder ENUMERATED {enabled} OPTIONAL, -- Need R ..., [[ ra-PrioritizationForAccessIdentity-r16 SEQUENCE { ra-Prioritization-r16 RA-Prioritization, ra-PrioritizationForAI-r16 BIT STRING (SIZE (2)) } OPTIONAL, -- Cond InitialBWP-Only prach-RootSequenceIndex-r16 CHOICE { l571 INTEGER (0..569), l1151 INTEGER (0..1149) } OPTIONAL -- Need R ]], [[ ra-PrioritizationForSlicing-r17 RA-PrioritizationForSlicing-r17 OPTIONAL, -- Cond InitialBWP-Only featureCombinationPreamblesList-r17 SEQUENCE (SIZE(1..maxFeatureCombPreamblesPerRACHResource-r17)) OF FeatureCombinationPreambles-r17 OPTIONAL -- Cond AdditionalRACH ]] } -- TAG-RACH-CONFIGCOMMON-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,566 | 6.3.4.3 Precoding for transmit diversity | Precoding for transmit diversity is only used in combination with layer mapping for transmit diversity as described in clause 6.3.3.3. The precoding operation for transmit diversity is defined for two and four antenna ports. For transmission on two antenna ports, , the output , of the precoding operation is defined by for with . For rank=1 transmission on two antenna ports, , the output , of the precoding operation is defined by where . For transmission on four antenna ports,, the output , of the precoding operation is defined by for with . | 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.4.3 |
4,567 | – DMRS-BundlingPUCCH-Config | The IE DMRS-BundlingPUCCH-Config-r17 is used to configure DMRS bundling for PUCCH. DMRS-BundlingPUCCH-Config information element -- ASN1START -- TAG-DMRS-BUNDLINGPUCCH-CONFIG-START DMRS-BundlingPUCCH-Config-r17 ::= SEQUENCE { pucch-DMRS-Bundling-r17 ENUMERATED {enabled} OPTIONAL, -- Need R pucch-TimeDomainWindowLength-r17 INTEGER (2..8) OPTIONAL, -- Need S pucch-WindowRestart-r17 ENUMERATED {enabled} OPTIONAL, -- Need R pucch-FrequencyHoppingInterval-r17 ENUMERATED {s2, s4, s5, s10} OPTIONAL, -- Need S ... } -- TAG-DMRS-BUNDLINGPUCCH-CONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,568 | 4.2.4.1.1 Selection of the substate after power on or enabling the MS's GPRS capability | When the MS is switched on, the substate shall be PLMN-SEARCH in case the SIM/USIM is inserted and valid. See 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14] and 3GPP TS 45.008[ None ] [34] for further details. When the GPRS capability in an activated MS has been enabled, the selection of the GMM-DEREGISTERED substate depends on the MM state and the GPRS update status. The substate chosen after PLMN-SEARCH, in case of power on or after enabling of the GPRS capability is: - if the cell is not supporting GPRS, the substate shall be NO-CELL-AVAILABLE; - if no SIM/USIM is present the substate shall be NO-IMSI; - if a suitable cell supporting GPRS has been found and the PLMN or LA is not in the forbidden list, then the substate shall be NORMAL-SERVICE; - if the selected cell supporting GPRS is in a forbidden PLMN, is in a forbidden LA, or is a CSG cell with a CSG ID and associated PLMN identity that are not in Allowed CSG list or in the Operator CSG list stored in the MS , then the MS shall enter the substate LIMITED-SERVICE; - if the MS is in manual network selection mode and no cell supporting GPRS of the selected PLMN has been found, the MS shall enter the substate NO-CELL-AVAILABLE. | 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.4.1.1 |
4,569 | 5.3.3.7 T300 expiry | The UE shall: 1> if timer T300 expires: 2> reset MAC, release the MAC configuration and re-establish RLC for all RBs that are established (except broadcast MRBs); 2> if the UE supports RRC Connection Establishment failure with temporary offset and the T300 has expired a consecutive connEstFailCount times on the same cell for which connEstFailureControl is included in SIB1: 3> for a period as indicated by connEstFailOffsetValidity: 4> use connEstFailOffset for the parameter Qoffsettemp for the concerned cell when performing cell selection and reselection according to TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [20] and TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [27]; NOTE 1: When performing cell selection, if no suitable or acceptable cell can be found, it is up to UE implementation whether to stop using connEstFailOffset for the parameter Qoffsettemp during connEstFailOffsetValidity for the concerned cell. 2> if the UE supports multiple CEF report: 3> if the UE is not registered in SNPN and if the UE has connection establishment failure information or connection resume failure information available in VarConnEstFailReport and if the RPLMN is equal to plmn-identity in network-Identity stored in VarConnEstFailReport; or 3> if the UE is registered in SNPN and if the UE has connection establishment failure information or connection resume failure information available in VarConnEstFailReport and if the registered SNPN identity is not equal to snpn-identity in network-Identity stored in any entry of VarConnEstFailReportList: 4> if the cell identity of current cell is not equal to the cell identity stored in measResultFailedCell in VarConnEstFailReport and if the maxCEFReport-r17 has not been reached: 5> append the VarConnEstFailReport as a new entry in the VarConnEstFailReportList; 2> if the UE has connection establishment failure information or connection resume failure information available in VarConnEstFailReport and if the RPLMN is not equal to plmn-identity in network-Identity stored in VarConnEstFailReport; or 2> if the UE is registered in SNPN and if the UE has connection establishment failure information or connection resume failure information available in VarConnEstFailReport and if the registered SNPN identity is not equal to snpn-identity in network-Identity stored in any entry of VarConnEstFailReportList: 2> if the cell identity of current cell is not equal to the cell identity stored in measResultFailedCell in VarConnEstFailReport: 3> reset the numberOfConnFail to 0; 2> if the UE supports multiple CEF report and if the UE has connection establishment failure information or connection resume failure information available in VarConnEstFailReportList and if the RPLMN is not equal to plmn-identity in network-Identity stored in any entry of VarConnEstFailReportList;or 2> if the UE supports multiple CEF report and if the UE has connection establishment failure information or connection resume failure information available in VarConnEstFailReportList and if the registered SNPN identity is not equal to snpn-identity in network-Identity stored in any entry of VarConnEstFailReportList: 3> clear the content included in VarConnEstFailReportList; 2> clear the content included in VarConnEstFailReport except for the numberOfConnFail, if any; 2> store the following connection establishment failure information in the VarConnEstFailReport by setting its fields as follows: 3> if the UE is not in SNPN access mode: 4> set the plmn-Identity in network-Identity to the PLMN selected by upper layers (see TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [23]) from the PLMN(s) included in the plmn-IdentityInfoList in SIB1; 3> else if the UE is in SNPN access mode: 4> set the snpn-Identity in network-Identity to include the SNPN identity selected by upper layers (see TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [23]) from the list of SNPN(s) included in the npn-IdentityInfoList in SIB1; 3> set the measResultFailedCell to include the global cell identity, tracking area code, the cell level and SS/PBCH block level RSRP, and RSRQ, and SS/PBCH block indexes, of the failed cell based on the available SSB measurements collected up to the moment the UE detected connection establishment failure; 3> if available, set the measResultNeighCells, in order of decreasing ranking-criterion as used for cell re-selection, to include neighbouring cell measurements for at most the following number of neighbouring cells: 6 intra-frequency and 3 inter-frequency neighbours per frequency as well as 3 inter-RAT neighbours, per frequency/ set of frequencies per RAT and according to the following: 4> for each neighbour cell included, include the optional fields that are available; NOTE 2: The UE includes the latest results of the available measurements as used for cell reselection evaluation, which are performed in accordance with the performance requirements as specified in TS 38.133[ NR; Requirements for support of radio resource management ] [14]. 3> if available, set the locationInfo as follows: 4> if available, set the commonLocationInfo to include the detailed location information; 4> if available, set the bt-LocationInfo to include the Bluetooth measurement results, in order of decreasing RSSI for Bluetooth beacons; 4> if available, set the wlan-LocationInfo to include the WLAN measurement results, in order of decreasing RSSI for WLAN APs; 4> if available, set the sensor-LocationInfo to include the sensor measurement results as follows; 5> if available, include the sensor-MeasurementInformation; 5> if available, include the sensor-MotionInformation; NOTE 3: Which location information related configuration is used by the UE to make the locationInfo available for inclusion in the VarConnEstFailReport is left to UE implementation. 3> set perRAInfoList to indicate the performed random access procedure related information as specified in 5.7.10.5; 3> if the numberOfConnFail is smaller than 8: 4> increment the numberOfConnFail by 1; 2> inform upper layers about the failure to establish the RRC connection, upon which the procedure ends; The UE may discard the connection establishment failure or connection resume failure information, i.e. release the UE variable VarConnEstFailReport and the UE variable VarConnEstFailReportList, 48 hours after the last connection establishment failure is detected. The L2 U2N Relay UE either indicates to upper layers (to trigger PC5 unicast link release) or sends NotificationMessageSidelink message to the connected L2 U2N Remote UE(s) in accordance with 5.8.9.10. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.3.7 |
4,570 | 6.2.3.2 Virtual resource blocks of distributed type | Virtual resource blocks of distributed type are mapped to physical resource blocks as described below. Table 6.2.3.2-1: RB gap values The parameter is given by Table 6.2.3.2-1. For , only one gap value is defined and . For , two gap values and are defined. Whether or is signaled as part of the downlink scheduling assignment as described in TS 36.212[ Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and channel coding ] [3]. Virtual resource blocks of distributed type are numbered from 0 to, where for and for . Consecutive VRB numbers compose a unit of VRB number interleaving, where for and for . Interleaving of VRB numbers of each interleaving unit is performed with 4 columns and rows, where , and is RBG size as described in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4]. VRB numbers are written row by row in the rectangular matrix, and read out column by column. nulls are inserted in the last rows of the 2nd and 4th column, where . Nulls are ignored when reading out. The VRB numbers mapping to PRB numbers including interleaving is derived as follows: For even slot number ; , where , and , where and is obtained from the downlink scheduling assignment as described in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4]. For odd slot number ; Then, for all ; . Virtual resource blocks of distributed type are not applicable to BL/CE UEs. | 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.2.3.2 |
4,571 | 5.44.4 Identifiers for PIN | A PIN is managed at the PIN application layer. A unique PIN ID in a PLMN is designated to a PIN, e.g. by PIN application layer as specified in TS 23.542[ Application layer support for Personal IoT Network ] [181]. In 5GS the PIN ID is only used in the traffic descriptor of URSP rules, for routing traffic of specific PIN towards a dedicated (DNN, S-NSSAI) combination as specified in clause 6.6.2 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. If a PIN contains more than one PEGCs, the list of PEGCs may be grouped together following the 5G VN group management principles as specified in clause 5.29.2. Then the PEGCs of a PIN can be identified by an External Group ID by the AF for PIN. The AF for PIN may use the External Group ID to manage the list of PEGCs that are part of a PIN and for providing URSP guidance (as specified in clause 5.44.2) and/or QoS requests applicable to all the PEGCs (as specified in clause 5.44.3). NOTE: The PEMCs can also be grouped together with the PEGCs using the 5G VN group management functionality for enabling the PEMCs to communicate with PEGCs via UPF local switch in order to manage the PIN. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.44.4 |
4,572 | 6.10.4.3 Positioning reference signal subframe configuration | The subframe configuration period and the subframe offset for the transmission of positioning reference signals are listed in Table 6.10.4.3-1. The PRS configuration index is configured by higher layers. Positioning reference signals are transmitted only in configured DL subframes. Positioning reference signals shall not be transmitted in DwPTS. Positioning reference signals shall be transmitted in consecutive downlink subframes, where is configured by higher layers. The positioning reference signal instances, for the first subframe of the downlink subframes, shall satisfy . Table 6.10.4.3-1: Positioning reference signal subframe configuration | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.10.4.3 |
4,573 | 17.1 Remote Interference Management | The atmospheric ducting phenomenon, caused by lower densities at higher altitudes in the Earth's atmosphere, causes a reduced refractive index, causing the signals to bend back towards the Earth. A signal trapped in the atmospheric duct can reach distances far greater than normal. In TDD networks with the same UL/DL slot configuration, and in the absence of atmospheric ducting, a guard period is used to avoid the interference between UL and DL transmissions in different cells. However, when the atmospheric ducting phenomenon happens, radio signals can travel a relatively long distance, and the propagation delay exceeds the guard period. Consequently, the DL signals of an aggressor cell can interfere with the UL signals of a victim cell that is far away from the aggressor. Such interference is termed as remote interference. The further the aggressor is to the victim, the more UL symbols of the victim will be impacted. A remote interference scenario may involve a number of victim and aggressor cells, where the gNBs execute Remote Interference Management (RIM) coordination on behalf of their respective cells. Aggressor and victim gNBs can be grouped into semi-static sets, where each cell is assigned a set ID, and is configured with a RIM Reference Signal (RIM-RS) and the radio resources associated with the set ID. Each aggressor gNB can be configured with multiple set IDs and each victim gNB can be configured with multiple set IDs, whereas each cell can have at most one victim set ID and one aggressor set ID. Consequently, each gNB can be an aggressor and a victim at the same time. To mitigate remote interference, the network enables RIM frameworks for coordination between victim and aggressor gNBs. The coordination communication in RIM frameworks can be wireless- or backhaul-based. The backhaul-based RIM framework uses a combination of wireless and backhaul communication, while in the wireless framework, the communication is purely wireless. In both frameworks, all gNBs in a victim set simultaneously transmit an identical RIM reference signal carrying the victim set ID over the air. In the wireless framework, upon reception of the RIM reference signal from the victim set, aggressor gNBs undertake RIM measures, and send back a RIM reference signal carrying the aggressor set ID. The RIM reference signal sent by the aggressor is able to provide information whether the atmospheric ducting phenomenon exists. The victim gNBs realize the atmospheric ducting phenomenon have ceased upon not receiving any reference signal sent from aggressors. In the RIM backhaul framework, upon reception of the RIM reference signal from the victim set, aggressor gNBs undertake RIM measures, and establish backhaul coordination towards the victim gNB set. The backhaul messages are sent from individual aggressor gNBs to individual victim gNB, where the signalling is transparent to the core network. The RIM backhaul messages from aggressor to victim gNBs carry the indication about the detection or disappearance of RIM reference signal. Based on the indication from the backhaul message, the victim gNBs realize whether the atmospheric ducting and the consequent remote interference have ceased. In both frameworks, upon realizing that the atmospheric ducting has disappeared, the victim gNBs stop transmitting the RIM reference signal. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 17.1 |
4,574 | – MeasAndMobParametersMRDC | The IE MeasAndMobParametersMRDC is used to convey capability parameters related to RRM measurements and RRC mobility. MeasAndMobParametersMRDC information element -- ASN1START -- TAG-MEASANDMOBPARAMETERSMRDC-START MeasAndMobParametersMRDC ::= SEQUENCE { measAndMobParametersMRDC-Common MeasAndMobParametersMRDC-Common OPTIONAL, measAndMobParametersMRDC-XDD-Diff MeasAndMobParametersMRDC-XDD-Diff OPTIONAL, measAndMobParametersMRDC-FRX-Diff MeasAndMobParametersMRDC-FRX-Diff OPTIONAL } MeasAndMobParametersMRDC-v1560 ::= SEQUENCE { measAndMobParametersMRDC-XDD-Diff-v1560 MeasAndMobParametersMRDC-XDD-Diff-v1560 OPTIONAL } MeasAndMobParametersMRDC-v1610 ::= SEQUENCE { measAndMobParametersMRDC-Common-v1610 MeasAndMobParametersMRDC-Common-v1610 OPTIONAL, interNR-MeasEUTRA-IAB-r16 ENUMERATED {supported} OPTIONAL } MeasAndMobParametersMRDC-v1700 ::= SEQUENCE { measAndMobParametersMRDC-Common-v1700 MeasAndMobParametersMRDC-Common-v1700 OPTIONAL } MeasAndMobParametersMRDC-v1730 ::= SEQUENCE { measAndMobParametersMRDC-Common-v1730 MeasAndMobParametersMRDC-Common-v1730 OPTIONAL } MeasAndMobParametersMRDC-Common ::= SEQUENCE { independentGapConfig ENUMERATED {supported} OPTIONAL } MeasAndMobParametersMRDC-Common-v1610 ::= SEQUENCE { condPSCellChangeParametersCommon-r16 SEQUENCE { condPSCellChangeFDD-TDD-r16 ENUMERATED {supported} OPTIONAL, condPSCellChangeFR1-FR2-r16 ENUMERATED {supported} OPTIONAL } OPTIONAL, pscellT312-r16 ENUMERATED {supported} OPTIONAL } MeasAndMobParametersMRDC-Common-v1700 ::= SEQUENCE { condPSCellChangeParameters-r17 SEQUENCE { inter-SN-condPSCellChangeFDD-TDD-NRDC-r17 ENUMERATED {supported} OPTIONAL, inter-SN-condPSCellChangeFR1-FR2-NRDC-r17 ENUMERATED {supported} OPTIONAL, inter-SN-condPSCellChangeFDD-TDD-ENDC-r17 ENUMERATED {supported} OPTIONAL, inter-SN-condPSCellChangeFR1-FR2-ENDC-r17 ENUMERATED {supported} OPTIONAL, mn-InitiatedCondPSCellChange-FR1FDD-ENDC-r17 ENUMERATED {supported} OPTIONAL, mn-InitiatedCondPSCellChange-FR1TDD-ENDC-r17 ENUMERATED {supported} OPTIONAL, mn-InitiatedCondPSCellChange-FR2TDD-ENDC-r17 ENUMERATED {supported} OPTIONAL, sn-InitiatedCondPSCellChange-FR1FDD-ENDC-r17 ENUMERATED {supported} OPTIONAL, sn-InitiatedCondPSCellChange-FR1TDD-ENDC-r17 ENUMERATED {supported} OPTIONAL, sn-InitiatedCondPSCellChange-FR2TDD-ENDC-r17 ENUMERATED {supported} OPTIONAL } OPTIONAL, condHandoverWithSCG-ENDC-r17 ENUMERATED {supported} OPTIONAL, condHandoverWithSCG-NEDC-r17 ENUMERATED {supported} OPTIONAL } MeasAndMobParametersMRDC-Common-v1730 ::= SEQUENCE { independentGapConfig-maxCC-r17 SEQUENCE { fr1-Only-r17 INTEGER (1..32) OPTIONAL, fr2-Only-r17 INTEGER (1..32) OPTIONAL, fr1-AndFR2-r17 INTEGER (1..32) OPTIONAL } } MeasAndMobParametersMRDC-XDD-Diff ::= SEQUENCE { sftd-MeasPSCell ENUMERATED {supported} OPTIONAL, sftd-MeasNR-Cell ENUMERATED {supported} OPTIONAL } MeasAndMobParametersMRDC-XDD-Diff-v1560 ::= SEQUENCE { sftd-MeasPSCell-NEDC ENUMERATED {supported} OPTIONAL } MeasAndMobParametersMRDC-FRX-Diff ::= SEQUENCE { simultaneousRxDataSSB-DiffNumerology ENUMERATED {supported} OPTIONAL } -- TAG-MEASANDMOBPARAMETERSMRDC-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,575 | Annex C (informative): Generating EPS PDN Connection parameters from 5G PDU Session parameters | This annex specifies how to generate the EPS PDN connection parameters from the 5G PDU Session parameters in SMF+PGW-C. When the SMF+PGW-C is requested to set up/modify either a PDN connection or a PDU session supporting interworking between EPS and 5GS, the SMF+PGW-C generates the PDN Connection parameters from the PDU session parameters. When the SMF+PGW-C generates the PDN Connection parameters based on the PDU Session parameters, the following rules hold: - PDN type: the PDN type is set to IPv4, IPv6 or IPv4v6 if the PDU Session Type is IPv4, IPv6 or IPv4v6, respectively. The PDN Type is set to Ethernet if the MME, SGW and UE support Ethernet PDN Type, otherwsie the PDN type is set to Non-IP for Ethernet and Unstructured PDU Session Types - EPS bearer ID: the EBI is requested from the AMF during the establishment of a QoS Flow as described in clause 4.11.1.4.1 for PDU Sessions supporting interworking between EPS and 5GS. The EBI is obtained from MME during the establishment of an EPS Bearer (that is triggered by an establishment of a QoS Flow) as defined in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13] for PDN Connections hosted by SMF+PGW-C. The association between EBI and QoS Flow is stored by the SMF. - APN-AMBR: APN-AMBR is set according to operator policy (e.g. taking the Session AMBR into account). - EPS QoS parameters (including ARP, QCI, GBR and MBR): If QoS Flow is mapped to one EPS bearer, ARP, GBR and MBR of the EPS Bearer is set to the ARP, GFBR and MFBR of the corresponding QoS Flow, respectively. For standardized 5QIs, the QCI is one to one mapped to the 5QI. For non-standardized 5QIs, the SMF+PGW-C derives the QCI based on the 5QI and operator policy. A GBR QoS Flow is mapped 1 to 1 to a GBR dedicated EPS Bearer if an EBI has been assigned. After mobility to EPS traffic flows corresponding to GBR QoS Flow for which no EBI has been assigned will continue flowing on the default EPS bearer if it does not have assigned TFT. If multiple QoS Flows are mapped to one EPS bearer, the EPS bearer parameters are set based on operator policy, e.g. EPS bearer QoS parameters are set according to the highest QoS of all mapped QoS Flows. After mobility to EPS traffic flows corresponding to Non-GBR QoS Flows for which no EBI has been assigned will continue flowing on the default EPS Bearer if it does not have assigned TFT. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | Annex |
4,576 | C.3 Target ID | This clause describes a possible way to support SRNS relocation. In UMTS, when SRNS relocation is executed, a target ID which consists of MCC, MNC and RNC ID is used as routeing information to route to the target RNC via the new SGSN. An old SGSN shall resolve a new SGSN IP address by a target ID to send the Forward Relocation Request message to the new SGSN. It shall be possible to refer to a target ID by a logical name which shall be translated into an SGSN IP address to take into account inter-PLMN handover. The old SGSN transforms the target ID information into a logical name of the form: rncXXXX.mncYYY.mccZZZ.gprs X shall be Hex coded digits; Y and Z shall be encoded as single digits (in the range 0-9). If there are less than 4 significant digits in XXXX, one or more "0" digit(s) is/are inserted at the left side to fill the 4 digits coding. If there are only 2 significant digits in YYY, a "0" digit is inserted at the left side to fill the 3 digit coding. Then, for example, a DNS server is used to translate the logical name to an SGSN IP address. As an example, the logical name for RNC 1B34, MCC 167 and MNC 92 will be coded in the DNS server as: rnc1B34.mnc092.mcc167.gprs | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | C.3 |
4,577 | – VarLTM-Config | The IE VarLTM-Config is used to store the reference configuration and the LTM candidate configurations. VarLTM-Config UE variable -- ASN1START -- TAG-VARLTM-CONFIG-START VarLTM-Config-r18-IEs ::= SEQUENCE { ltm-ReferenceConfiguration-r18 ReferenceConfiguration-r18, ltm-CandidateList-r18 SEQUENCE (SIZE (1..maxNrofLTM-Configs-r18)) OF LTM-Candidate-r18, ltm-CSI-ResourceConfigList-r18 SEQUENCE (SIZE (1..maxNrofLTM-CSI-ResourceConfigurations-r18)) OF LTM-CSI-ResourceConfig-r18 } -- TAG-VARLTM-CONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,578 | – CounterCheck | The CounterCheck message is used by the network to indicate the current COUNT MSB values associated to each DRB and to request the UE to compare these to its COUNT MSB values and to report the comparison results to the network. Signalling radio bearer: SRB1 RLC-SAP: AM Logical channel: DCCH Direction: Network to UE CounterCheck message -- ASN1START -- TAG-COUNTERCHECK-START CounterCheck ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { counterCheck CounterCheck-IEs, criticalExtensionsFuture SEQUENCE {} } } CounterCheck-IEs ::= SEQUENCE { drb-CountMSB-InfoList DRB-CountMSB-InfoList, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } DRB-CountMSB-InfoList ::= SEQUENCE (SIZE (1..maxDRB)) OF DRB-CountMSB-Info DRB-CountMSB-Info ::= SEQUENCE { drb-Identity DRB-Identity, countMSB-Uplink INTEGER(0..33554431), countMSB-Downlink INTEGER(0..33554431) } -- TAG-COUNTERCHECK-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,579 | 5.28.3 Port and user plane node management information exchange in 5GS 5.28.3.1 General | Port number for the PDU Session is assigned by the UPF during PDU session establishment. The port number for a PDU Session shall be reported to the SMF from the UPF and further stored at the SMF. The SMF provides the port number via PCF to the TSN AF or TSCTSF. TSN AF or TSCTSF maintains an association between the port number for the PDU Session and the DS-TT port MAC address (with Ethernet type PDU session) or IP address (applicable for TSCTSF only, with IP type PDU Session) of the UE. If a PDU session for which SMF has reported a port number to TSN AF or TSCTSF is released, then SMF informs TSN AF or TSCTSF accordingly. The port number for the PDU Session corresponds to the device side port of the 5GS bridge/router. When the device supports the DS-TT functionality, the port number represents the DS-TT port number corresponding to the given PDU Session. NOTE 1: Port number can refer either to Ethernet port or PTP port. In Ethernet type PDU Sessions, it is assumed that the PTP port number is the same as the associated Ethernet port number. When the DS-TT or the NW-TT functions are used, the 5GS shall support transfer of standardized and deployment-specific port management information transparently between TSN AF or TSCTSF and DS-TT or NW-TT, respectively inside a Port Management Information Container. NW-TT may support one or more ports. In this case, each port uses separate Port Management Information Container. 5GS shall also support transfer of standardized and deployment-specific user plane node management information transparently between TSN AF or TSCTSF and NW-TT, respectively inside a User Plane Node Management Information Container. Clause K.1 lists standardized port management information and user plane node management information, respectively. If TSN AF is deployed, i.e. if 5GS is integrated with an IEEE TSN network, the port and user plane node management information is exchanged between CNC and TSN AF. The port management information is related to ports located in DS-TT or NW-TT. The user plane node management information container is related to 5GS bridge management. If TSN AF is not deployed, the port and user plane node management information is exchanged between TSCTSF and DS-TT/NW-TT. NOTE 2: The time synchronization parameters used in Port Management Information Container and User Plane Node Management Information Container are from IEEE Std 1588 [126], Edition 2019, and from IEEE Std 802.1AS [104]. Since the IEEE time synchronization data sets are not exposed, care needs to be taken when interoperating with devices supporting Edition 2008, IEEE Std 1588-2008 [107] (which can be the case when operating under the SMPTE profile, ST 2059-2:2015 [127]) and using a common management. Exchange of port and user plane node management information between TSN AF or TSCTSF and NW-TT or between TSN AF or TSCTSF and DS-TT allows TSN AF or TSCTSF to: 1) retrieve port management information for a DS-TT or NW-TT port or user plane node management information; 2) send port management information for a DS-TT or NW-TT port or user plane node management information; 3) subscribe to and receive notifications if specific port management information for a DS-TT or NW-TT port changes or user plane node management information changes. 4) delete selected entries in the following data structures: - "DS-TT port neighbour discovery configuration for DS-TT port" in UMIC using the DS-TT port number to reference the selected entry. - "Stream Filter Instance Table" in PMIC using the Stream Filter Instance ID to reference the selected entry. - "Stream Gate Instance Table" in PMIC using the Stream Gate Instance ID to reference the selected entry. - "Static Filtering Entries table" in UMIC using the (MAC address, VLAN ID) pair to reference the selected entry. 5) delete PTP Instances in a DS-TT port or NW-TT port using the PTP Instance ID to reference the selected entry as described in clause K.2.2.1. Exchange of port management information between TSN AF or TSCTSF and NW-TT or DS-TT is initiated by DS-TT or NW-TT to: - notify TSN AF or TSCTSF if port management information has changed that TSN AF or TSCTSF has subscribed for. Exchange of user plane node management information between TSN AF or TSCTSF and NW-TT is initiated by NW-TT to: - notify TSN AF or TSCTSF if user plane node management information has changed that TSN AF or TSCTSF has subscribed for. - notify TSCTSF if time synchronization status information of UPF has changed that the TSCTSF has subscribed for. Exchange of port management information is initiated by DS-TT to: - provide port management capabilities, i.e. provide information indicating which standardized and deployment-specific port management information is supported by DS-TT. TSN AF or TSCTSF indicates inside the Port Management Information Container or user plane node Management Information Container whether it wants to retrieve or send port or user plane node management information or intends to (un-)subscribe for notifications. If the TSN AF or TSCTSF has requested to receive notification of TSC management information and both SMF and UPF support direct reporting, the UPF may directly report TSC management information to the TSN AF or TSCTSF using Nupf_EventExposure_Notify. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.28.3 |
4,580 | 6.8.8.2 GSM security context | A GSM security context is only established for GSM subscribers. At the network side, two cases are distinguished: a) In case of a PS intra SGSN Handover, the SGSN starts to apply the 64-bit GSM cipher key Kc agreed during the latest GSM AKA procedure. b) In case of a PS inter SGSN Handover, the initial SGSN sends the 64-bit GSM cipher key Kc agreed during the latest GSM AKA procedure to the (new) SGSN. The new SGSN stores the key and applies it. The new SGSN becomes the new anchor point for the service. At the user side, in both cases, the ME applies the 64-bit GSM cipher key Kc received from the SIM during the latest GSM AKA procedure. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 6.8.8.2 |
4,581 | 6.6.2 UP security activation mechanism | AS UP integrity protection and ciphering activation shall be done as part of the DRB addition procedure using RRC Connection Reconfiguration procedure as described in this clause, see Figure 6.6.2-1. The SMF shall send the UP security policy to the gNB/ng-eNB as defined in Clause 6.6.1. Figure 6.6.2-1: User plane (UP) security activation mechanism 1a. This RRC Connection Reconfiguration procedure which is used to add DRBs shall be performed only after RRC security has been activated as part of the AS security mode command procedure defined in Clause 6.7.4. 1b. The gNB/ng-eNB shall send the RRC Connection Reconfiguration message to the UE for UP security activation containing indications for the activation of UP integrity protection and ciphering for each DRB according to the security policy. 1c. If UP integrity protection is activated for DRBs as indicated in the RRC Connection Reconfiguration message, and if the gNB/ng-eNB does not have KUPint, the gNB/ng-eNB shall generate KUPint and UP integrity protection for such DRBs shall start at the gNB/ng-eNB. Similarly, if UP ciphering is activated for DRBs as indicated in the RRC Connection Reconfiguration message, and if the gNB/ng-eNB does not have KUPenc, the gNB/ng-eNB shall generate KUPenc and UP ciphering for such DRBs shall start at the gNB/ng-eNB. 2a. UE shall verify the RRC Connection Reconfiguration message. If successful: 2a.1 If UP integrity protection is activated for DRBs as indicated in the RRC Connection Reconfiguration message, and if the UE does not have KUPint, the UE shall generate KUPint and UP integrity protection for such DRBs shall start at the UE. 2a.2 Similarly, if UP ciphering is activated for DRBs as indicated in the RRC Connection Reconfiguration message, and if the UE does not have KUPenc, the UE shall generate KUPenc and UP ciphering for such DRBs shall start at the UE 2b. If the UE successfully verifies integrity of the RRC Connection Reconfiguration message, the UE shall send the RRC Connection Reconfiguration Complete message to the gNB/ng-eNB. If UP integrity protection is not activated for DRBs, the gNB/ng-eNB and the UE shall not integrity protect the traffic of such DRB and shall not put MAC-I into PDCP packet. If UP ciphering is not activated for DRBs, the gNB/ng-eNB and the UE shall not cipher the traffic of such DRBs. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.6.2 |
4,582 | 5.15.2.1.1 Sidelink HARQ Entity | There is one Sidelink HARQ Entity at the MAC entity for reception on the SL-DCH which maintains a number of parallel Sidelink processes. The Sidelink HARQ Entity directs HARQ information and associated TBs received on the SL-DCH to the corresponding Sidelink processes. The number of receiving Sidelink processes per Sidelink HARQ Entity is specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]. For each subframe of the SL-DCH, the Sidelink HARQ Entity shall: - receive the TB and the associated HARQ information from the physical layer; - if this subframe corresponds to a new transmission opportunity: - allocate the received TB (if any) and the associated HARQ information to a non-running Sidelink process and consider this transmission to be a new transmission. - else, if this subframe corresponds to a retransmission opportunity: - allocate the received TB (if any) and the associated HARQ information to its Sidelink process and consider this transmission to be a retransmission. | 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.15.2.1.1 |
4,583 | – CSI-ReportConfig | The IE CSI-ReportConfig is used to configure a periodic or semi-persistent report sent on PUCCH on the cell in which the CSI-ReportConfig is included, or to configure a semi-persistent or aperiodic report sent on PUSCH triggered by DCI received on the cell in which the CSI-ReportConfig is included (in this case, the cell on which the report is sent is determined by the received DCI). See TS 38.214[ NR; Physical layer procedures for data ] [19], clause 5.2.1. CSI-ReportConfig information element -- ASN1START -- TAG-CSI-REPORTCONFIG-START CSI-ReportConfig ::= SEQUENCE { reportConfigId CSI-ReportConfigId, carrier ServCellIndex OPTIONAL, -- Need S resourcesForChannelMeasurement CSI-ResourceConfigId, csi-IM-ResourcesForInterference CSI-ResourceConfigId OPTIONAL, -- Need R nzp-CSI-RS-ResourcesForInterference CSI-ResourceConfigId OPTIONAL, -- Need R reportConfigType CHOICE { periodic SEQUENCE { reportSlotConfig CSI-ReportPeriodicityAndOffset, pucch-CSI-ResourceList SEQUENCE (SIZE (1..maxNrofBWPs)) OF PUCCH-CSI-Resource }, semiPersistentOnPUCCH SEQUENCE { reportSlotConfig CSI-ReportPeriodicityAndOffset, pucch-CSI-ResourceList SEQUENCE (SIZE (1..maxNrofBWPs)) OF PUCCH-CSI-Resource }, semiPersistentOnPUSCH SEQUENCE { reportSlotConfig ENUMERATED {sl5, sl10, sl20, sl40, sl80, sl160, sl320}, reportSlotOffsetList SEQUENCE (SIZE (1.. maxNrofUL-Allocations)) OF INTEGER(0..32), p0alpha P0-PUSCH-AlphaSetId }, aperiodic SEQUENCE { reportSlotOffsetList SEQUENCE (SIZE (1..maxNrofUL-Allocations)) OF INTEGER(0..32) } }, reportQuantity CHOICE { none NULL, cri-RI-PMI-CQI NULL, cri-RI-i1 NULL, cri-RI-i1-CQI SEQUENCE { pdsch-BundleSizeForCSI ENUMERATED {n2, n4} OPTIONAL -- Need S }, cri-RI-CQI NULL, cri-RSRP NULL, ssb-Index-RSRP NULL, cri-RI-LI-PMI-CQI NULL }, reportFreqConfiguration SEQUENCE { cqi-FormatIndicator ENUMERATED { widebandCQI, subbandCQI } OPTIONAL, -- Need R pmi-FormatIndicator ENUMERATED { widebandPMI, subbandPMI } OPTIONAL, -- Need R csi-ReportingBand CHOICE { subbands3 BIT STRING(SIZE(3)), subbands4 BIT STRING(SIZE(4)), subbands5 BIT STRING(SIZE(5)), subbands6 BIT STRING(SIZE(6)), subbands7 BIT STRING(SIZE(7)), subbands8 BIT STRING(SIZE(8)), subbands9 BIT STRING(SIZE(9)), subbands10 BIT STRING(SIZE(10)), subbands11 BIT STRING(SIZE(11)), subbands12 BIT STRING(SIZE(12)), subbands13 BIT STRING(SIZE(13)), subbands14 BIT STRING(SIZE(14)), subbands15 BIT STRING(SIZE(15)), subbands16 BIT STRING(SIZE(16)), subbands17 BIT STRING(SIZE(17)), subbands18 BIT STRING(SIZE(18)), ..., subbands19-v1530 BIT STRING(SIZE(19)) } OPTIONAL -- Need S } OPTIONAL, -- Need R timeRestrictionForChannelMeasurements ENUMERATED {configured, notConfigured}, timeRestrictionForInterferenceMeasurements ENUMERATED {configured, notConfigured}, codebookConfig CodebookConfig OPTIONAL, -- Need R dummy ENUMERATED {n1, n2} OPTIONAL, -- Need R groupBasedBeamReporting CHOICE { enabled NULL, disabled SEQUENCE { nrofReportedRS ENUMERATED {n1, n2, n3, n4} OPTIONAL -- Need S } }, cqi-Table ENUMERATED {table1, table2, table3, table4-r17} OPTIONAL, -- Need R subbandSize ENUMERATED {value1, value2}, non-PMI-PortIndication SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourcesPerConfig)) OF PortIndexFor8Ranks OPTIONAL, -- Need R ..., [[ semiPersistentOnPUSCH-v1530 SEQUENCE { reportSlotConfig-v1530 ENUMERATED {sl4, sl8, sl16} } OPTIONAL -- Need R ]], [[ semiPersistentOnPUSCH-v1610 SEQUENCE { reportSlotOffsetListDCI-0-2-r16 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..32) OPTIONAL, -- Need R reportSlotOffsetListDCI-0-1-r16 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..32) OPTIONAL -- Need R } OPTIONAL, -- Need R aperiodic-v1610 SEQUENCE { reportSlotOffsetListDCI-0-2-r16 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..32) OPTIONAL, -- Need R reportSlotOffsetListDCI-0-1-r16 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..32) OPTIONAL -- Need R } OPTIONAL, -- Need R reportQuantity-r16 CHOICE { cri-SINR-r16 NULL, ssb-Index-SINR-r16 NULL } OPTIONAL, -- Need R codebookConfig-r16 CodebookConfig-r16 OPTIONAL -- Need R ]], [[ cqi-BitsPerSubband-r17 ENUMERATED {bits4} OPTIONAL, -- Need R groupBasedBeamReporting-v1710 SEQUENCE { nrofReportedGroups-r17 ENUMERATED {n1, n2, n3, n4} } OPTIONAL, -- Need R codebookConfig-r17 CodebookConfig-r17 OPTIONAL, -- Need R sharedCMR-r17 ENUMERATED {enable} OPTIONAL, -- Need R csi-ReportMode-r17 ENUMERATED {mode1, mode2} OPTIONAL, -- Need R numberOfSingleTRP-CSI-Mode1-r17 ENUMERATED {n0, n1, n2} OPTIONAL, -- Need R reportQuantity-r17 CHOICE { cri-RSRP-Index-r17 NULL, ssb-Index-RSRP-Index-r17 NULL, cri-SINR-Index-r17 NULL, ssb-Index-SINR-Index-r17 NULL } OPTIONAL -- Need R ]], [[ semiPersistentOnPUSCH-v1720 SEQUENCE { reportSlotOffsetList-r17 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..128) OPTIONAL, -- Need R reportSlotOffsetListDCI-0-2-r17 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..128) OPTIONAL, -- Need R reportSlotOffsetListDCI-0-1-r17 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..128) OPTIONAL -- Need R } OPTIONAL, -- Need R aperiodic-v1720 SEQUENCE { reportSlotOffsetList-r17 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..128) OPTIONAL, -- Need R reportSlotOffsetListDCI-0-2-r17 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..128) OPTIONAL, -- Need R reportSlotOffsetListDCI-0-1-r17 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..128) OPTIONAL -- Need R } OPTIONAL -- Need R ]], [[ codebookConfig-v1730 CodebookConfig-v1730 OPTIONAL -- Need R ]], [[ groupBasedBeamReporting-v1800 SEQUENCE { reportingMode-r18 ENUMERATED {jointULDL, onlyUL} } OPTIONAL, -- Need R reportQuantity-r18 TDCP-r18 OPTIONAL, -- Need R codebookConfig-r18 CodebookConfig-r18 OPTIONAL, -- Need R csi-ReportSubConfigToAddModList-r18 SEQUENCE (SIZE (2..maxNrofCSI-ReportSubconfigPerCSI-ReportConfig-r18)) OF CSI-ReportSubConfig-r18 OPTIONAL, -- Need N csi-ReportSubConfigToReleaseList-r18 SEQUENCE (SIZE (2..maxNrofCSI-ReportSubconfigPerCSI-ReportConfig-r18)) OF CSI-ReportSubConfigId-r18 OPTIONAL -- Need N ]] } CSI-ReportPeriodicityAndOffset ::= CHOICE { slots4 INTEGER(0..3), slots5 INTEGER(0..4), slots8 INTEGER(0..7), slots10 INTEGER(0..9), slots16 INTEGER(0..15), slots20 INTEGER(0..19), slots40 INTEGER(0..39), slots80 INTEGER(0..79), slots160 INTEGER(0..159), slots320 INTEGER(0..319) } PortIndexFor8Ranks ::= CHOICE { portIndex8 SEQUENCE{ rank1-8 PortIndex8 OPTIONAL, -- Need R rank2-8 SEQUENCE(SIZE(2)) OF PortIndex8 OPTIONAL, -- Need R rank3-8 SEQUENCE(SIZE(3)) OF PortIndex8 OPTIONAL, -- Need R rank4-8 SEQUENCE(SIZE(4)) OF PortIndex8 OPTIONAL, -- Need R rank5-8 SEQUENCE(SIZE(5)) OF PortIndex8 OPTIONAL, -- Need R rank6-8 SEQUENCE(SIZE(6)) OF PortIndex8 OPTIONAL, -- Need R rank7-8 SEQUENCE(SIZE(7)) OF PortIndex8 OPTIONAL, -- Need R rank8-8 SEQUENCE(SIZE(8)) OF PortIndex8 OPTIONAL -- Need R }, portIndex4 SEQUENCE{ rank1-4 PortIndex4 OPTIONAL, -- Need R rank2-4 SEQUENCE(SIZE(2)) OF PortIndex4 OPTIONAL, -- Need R rank3-4 SEQUENCE(SIZE(3)) OF PortIndex4 OPTIONAL, -- Need R rank4-4 SEQUENCE(SIZE(4)) OF PortIndex4 OPTIONAL -- Need R }, portIndex2 SEQUENCE{ rank1-2 PortIndex2 OPTIONAL, -- Need R rank2-2 SEQUENCE(SIZE(2)) OF PortIndex2 OPTIONAL -- Need R }, portIndex1 NULL } PortIndex8::= INTEGER (0..7) PortIndex4::= INTEGER (0..3) PortIndex2::= INTEGER (0..1) TDCP-r18 ::= SEQUENCE { delayDSetofLengthY-r18 SEQUENCE (SIZE (1.. maxNrofdelayD-r18)) OF DelayD, phaseReporting-r18 ENUMERATED {enable} OPTIONAL -- Need R } DelayD ::= ENUMERATED { symb4, slot1, slot2, slot3, slot4, slot5, slot6, slot10 } -- TAG-CSI-REPORTCONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,584 | 5.6.9.3 SSC mode selection | SSC mode selection is done by the SMF based on the allowed SSC modes -including the default SSC mode) in the user subscription as well as the PDU Session type and if present, the SSC mode requested by the UE. The operator may provision a SSC mode selection policy (SSCMSP) to the UE as part of the URSP rule -see clause 6.6.2 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]). The UE shall use the SSCMSP to determine the type of session and service continuity mode associated with an application or group of applications for the UE as described in clause 6.6.2.3 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. If the UE does not have SSCMSP, the UE can select a SSC mode based on UE Local Configuration as described in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45], if applicable. If the UE cannot select a SSC mode, the UE requests the PDU Session without providing the SSC mode. NOTE 1: The UE can use the SSC Mode Selection component of the URSP rule with match-all traffic descriptor if there is no SSC mode in the UE local configuration. The SSC mode selection policy rules provided to the UE can be updated by the operator by updating the URSP rule. The SMF receives from the UDM the list of allowed SSC modes and the default SSC mode per DNN per S-NSSAI as part of the subscription information. If a UE provides an SSC mode when requesting a new PDU Session, the SMF selects the SSC mode by either accepting the requested SSC mode or rejecting the PDU Session Establishment Request message with the cause value and the SSC mode(s) allowed to be used back to UE based on the PDU Session type, subscription and/or local configuration. Based on that cause value and the SSC mode(s) allowed to be used, the UE may re-attempt to request the establishment of that PDU Session with the SSC mode allowed to be used or using another URSP rule. If a UE does not provide an SSC mode when requesting a new PDU Session, then the SMF selects the default SSC mode for the data network listed in the subscription or applies local configuration to select the SSC mode. SSC mode 1 shall be assigned to the PDU Session when static IP address/prefix is allocated to the PDU Session based on the static IP address/prefix subscription for the DNN and S-NSSAI. The SMF shall inform the UE of the selected SSC mode for a PDU Session. The UE shall not request and the network shall not assign SSC mode 3 for the PDU Session of Unstructured type or Ethernet type. NOTE 2: To avoid issues for UEs not supporting all SSC modes, the operator can, in the subscription data and local configuration, include at least SSC mode 1 in the allowed SSC modes, and set default SSC mode to 1 (since all UEs supporting PDU sessions are mandated to support SSC mode 1). Still the 5GC can trigger PDU session release with a cause code indicating reactivation due to, e.g. restoration or user plane path optimization purposes, though this may cause interruption of the service. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.6.9.3 |
4,585 | – SPS-Config | The IE SPS-Config is used to configure downlink semi-persistent transmission. Multiple Downlink SPS configurations may be configured in one BWP of a serving cell. SPS-Config information element -- ASN1START -- TAG-SPS-CONFIG-START SPS-Config ::= SEQUENCE { periodicity ENUMERATED {ms10, ms20, ms32, ms40, ms64, ms80, ms128, ms160, ms320, ms640, spare6, spare5, spare4, spare3, spare2, spare1}, nrofHARQ-Processes INTEGER (1..8), n1PUCCH-AN PUCCH-ResourceId OPTIONAL, -- Need M mcs-Table ENUMERATED {qam64LowSE} OPTIONAL, -- Need S ..., [[ sps-ConfigIndex-r16 SPS-ConfigIndex-r16 OPTIONAL, -- Cond SPS-List harq-ProcID-Offset-r16 INTEGER (0..15) OPTIONAL, -- Need R periodicityExt-r16 INTEGER (1..5120) OPTIONAL, -- Need R harq-CodebookID-r16 INTEGER (1..2) OPTIONAL, -- Need R pdsch-AggregationFactor-r16 ENUMERATED {n1, n2, n4, n8 } OPTIONAL -- Need S ]], [[ sps-HARQ-Deferral-r17 INTEGER (1..32) OPTIONAL, -- Need R n1PUCCH-AN-PUCCHsSCell-r17 PUCCH-ResourceId OPTIONAL, -- Need R periodicityExt-r17 INTEGER (1..40960) OPTIONAL, -- Need R nrofHARQ-Processes-v1710 INTEGER(9..32) OPTIONAL, -- Need R harq-ProcID-Offset-v1700 INTEGER (16..31) OPTIONAL -- Need R ]] } -- TAG-SPS-CONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,586 | Annex A (informative): Example of subaddress information element coding | This annex gives an example of how the Called Party Subaddress IE is encoded to carry subaddress digits that use IA5 characters. This example is also applicable to the Calling Party Subaddress IE. NOTE 1: The value of this bit has no significance when the type of subaddress is "NSAP". NOTE 2: These bits are spare. NOTE 3: The Authority and Format Identifier code 50 (in BCD) indicates that the subaddress consists of IA5 characters (see ISO standard 8348 AD2). NOTE 4: IA5 character as defined in ITU-T Recommendation T.50 [52]/ISO 646 and then encoded into two semi-octets according to the "preferred binary encoding" defined in X.213 [144]/ISO 8348 AD2. (Each character is converted into a number in the range 32 to 127 using the ISO 646 encoding with zero parity and the parity bit in the most significant position. This number is then reduced by 32 to give a new number in the range 0 to 95. The new number is then treated as a pair of decimal digits with the value of each digit being encoded in a semi-octet.) NOTE 5: the number of IA5 characters in the subaddress may vary, subject to an upper limit of 19 IA5 characters. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | Annex |
4,587 | 5.34.7.1 UE's Mobility Event Management | When an I-SMF is involved in a PDU Session, the SMF and I-SMF independently subscribe to "UE mobility event notification" service provided by AMF. The AMF treats the SMF's and I-SMF's subscription separately and notifies the event directly to the SMF or I-SMF. If the SMF does not know the serving AMF address, the SMF gets the serving AMF address from the UDM as described in clause 5.2.3.2.4, TS 23.502[ Procedures for the 5G System (5GS) ] [3] and subscribes directly with the serving AMF. In the case of AMF change (e.g. Inter NG-RAN node N2 based handover), the target AMF receives mobility event subscription information from the source AMF and updates the mobility event subscription information with the SMF and I-SMF independently (i.e. target AMF allocates the Subscription Correlation ID for each event and notifies the respective SMFs and I-SMF as described in clause 5.3.4.4). In the case of I-SMF change or I-SMF insertion (e.g. at Inter NG-RAN node N2 based handover), the subscription of mobility event (from AMF) is not transferred from the old I-SMF or SMF to the new I-SMF, the new I-SMF triggers a new subscription event if the new I-SMF wants to receive the corresponding mobility event. In the case of I-SMF removal, the subscription of mobility event at the AMF is not transferred from the old I-SMF to the SMF, the SMF triggers a new subscription event if the SMF wants to receive the corresponding mobility event. The subscription from the old SMF entity (old I-SMF, SMF) is removed via an explicitly request from this old SMF entity. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.34.7.1 |
4,588 | 8.51.8 Macro ng-eNodeB ID | The Target Type is Macro ng-eNodeB ID for an EPS to 5GS handover to a target Macro ng-eNodeB. In this case the coding of the Target ID field shall be coded as depicted in Figure 8.51.8-1. Figure 8.51.8-1: Target ID for Type Macro ng-eNodeB Octets 6 to 11 shall be encoded as specified for the Macro eNodeB (see Figure 8.51-2). The 5GS TAC consists of 3 octets. Bit 8 of Octet 12 is the most significant bit and bit 1 of octet 14 the least significant bit. The coding of the tracking area code is the responsibility of each administration. Coding using full hexadecimal representation (binary, not ASCII encoding) shall be used. | 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.51.8 |
4,589 | – SL-SyncConfig | The IE SL-SyncConfig specifies the configuration information concerning reception of synchronisation signals from neighbouring cells as well as concerning the transmission of synchronisation signals for sidelink communication. SL-SyncConfig information element -- ASN1START -- TAG-SL-SYNCCONFIG-START SL-SyncConfigList-r16 ::= SEQUENCE (SIZE (1..maxSL-SyncConfig-r16)) OF SL-SyncConfig-r16 SL-SyncConfig-r16 ::= SEQUENCE { sl-SyncRefMinHyst-r16 ENUMERATED {dB0, dB3, dB6, dB9, dB12} OPTIONAL, -- Need R sl-SyncRefDiffHyst-r16 ENUMERATED {dB0, dB3, dB6, dB9, dB12, dBinf} OPTIONAL, -- Need R sl-filterCoefficient-r16 FilterCoefficient OPTIONAL, -- Need R sl-SSB-TimeAllocation1-r16 SL-SSB-TimeAllocation-r16 OPTIONAL, -- Need R sl-SSB-TimeAllocation2-r16 SL-SSB-TimeAllocation-r16 OPTIONAL, -- Need R sl-SSB-TimeAllocation3-r16 SL-SSB-TimeAllocation-r16 OPTIONAL, -- Need R sl-SSID-r16 INTEGER (0..671) OPTIONAL, -- Need R txParameters-r16 SEQUENCE { syncTxThreshIC-r16 SL-RSRP-Range-r16 OPTIONAL, -- Need R syncTxThreshOoC-r16 SL-RSRP-Range-r16 OPTIONAL, -- Need R syncInfoReserved-r16 BIT STRING (SIZE (2)) OPTIONAL -- Need R }, gnss-Sync-r16 ENUMERATED {true} OPTIONAL, -- Need R ... } SL-RSRP-Range-r16 ::= INTEGER (0..13) SL-SSB-TimeAllocation-r16 ::= SEQUENCE { sl-NumSSB-WithinPeriod-r16 ENUMERATED {n1, n2, n4, n8, n16, n32, n64} OPTIONAL, -- Need R sl-TimeOffsetSSB-r16 INTEGER (0..1279) OPTIONAL, -- Need R sl-TimeInterval-r16 INTEGER (0..639) OPTIONAL -- Need R } -- TAG-SL-SYNCCONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,590 | 9.11.3.18A CAG information list | The purpose of the CAG information list information element is to provide "CAG information list" or to delete the "CAG information list" at the UE. The CAG information list information element is coded as shown in figures 9.11.3.18A.1 and 9.11.3.18A.2 and table 9.11.3.18A.1. The CAG information list is a type 6 information element, with a minimum length of 3 octets. Figure 9.11.3.18A.1: CAG information list information element Figure 9.11.3.18A.2: Entry n Table 9.11.3.18A.1: CAG information list information element | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.11.3.18A |
4,591 | 5.1 Overview 5.1.1 General | This subclause describes the call control (CC) protocol, which is one of the protocols of the Connection Management (CM) sublayer (see 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [20]). Every mobile station must support the call control protocol. If a mobile station does not support any bearer capability at all then it shall respond to a SETUP message with a RELEASE COMPLETE message as specified in subclause 5.2.2.2. In Iu mode only, integrity protected signalling (see subclause 4.1.1.1.1 of the present document and in general, see 3GPP TS 33.102[ 3G security; Security architecture ] [5a]) is mandatory. In Iu mode only, all protocols shall use integrity protected signalling. Integrity protection of all CC signalling messages is the responsibility of lower layers. It is the network which activates integrity protection. This is done using the security mode control procedure (3GPP TS 25.331[ None ] [23c] and 3GPP TS 44.118[ None ] [111]). In the call control protocol, more than one CC entity are defined. Each CC entity is independent from each other and shall communicate with the correspondent peer entity using its own MM connection. Different CC entities use different transaction identifiers. With a few exceptions the present document describes the call control protocol only with regard to two peer entities. The call control entities are described as communicating finite state machines which exchange messages across the radio interface and communicate internally with other protocol (sub)layers. This description is only normative as far as the consequential externally observable behaviour is concerned. Certain sequences of actions of the two peer entities compose "elementary procedures" which are used as a basis for the description in this subclause. These elementary procedures may be grouped into the following classes: - call establishment procedures; - call clearing procedures; - call information phase procedures; - miscellaneous procedures. The terms "mobile originating" or "mobile originated" (MO) are used to describe a call initiated by the mobile station. The terms "mobile terminating" or "mobile terminated" (MT) are used to describe a call initiated by the network. Figure 5.1a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] gives an overview of the main states and transitions on the mobile station side. The MS side extension figure 5.1a.1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] shows how for the Network Initiated MO call the MS reaches state U1.0 from state U0 $(CCBS)$. Figure 5.1a.2/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] illustrates the additional state transitions possible in the MS due to SRVCC handovers from PS to CS or 5G-SRVCC handover from NG-RAN to UTRAN. Figure 5.1a.3/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] illustrates the additional state transitions possible in the MS due to SRVCC handovers from CS to PS. Figure 5.1b/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] gives an overview of the main states and transitions on the network side. The Network side extension figure 5.1b.1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] shows for Network Initiated MO Calls the Network reaches state N1.0 from state N0 $(CCBS)$.Figure 5.1b.2/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] illustrates the additional state transitions possible in the network due to SRVCC handovers from PS to CS or 5G-SRVCC handover from NG-RAN to UTRAN. Figure 5.1b.3/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] illustrates the additional state transitions possible in the network due to SRVCC handovers from CS to PS. Figure 5.1a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Overview call control protocol/MS side Figure 5.1a.1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Overview call control protocol/MS side, extension Figure 5.1a.2/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Overview call control protocol/MS side, extension for SRVCC from PS to CS or 5G-SRVCC handover from NG-RAN to UTRAN Figure 5.1a.3/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Overview call control protocol/MS side, extension for SRVCC from CS to PS Figure 5.1b/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Overview call control protocol/Network side Figure 5.1b.1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Overview call control protocol/Network side, extension Figure 5.1b.2/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Overview call control protocol/Network side, extension for SRVCC from PS to CS or 5G-SRVCC handover from NG-RAN to UTRAN Figure 5.1b.3/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Overview call control protocol/Network side, extension for SRVCC from CS to PS | 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.1 |
4,592 | 5.2.3.2.7 UPDATE-NEEDED | The UE: a) shall not send any user data; b) shall not send signalling information, unless it is a service request as a response to paging or to initiate signalling for emergency services or emergency services fallback; c) shall perform cell selection/reselection; d) shall enter the appropriate new substate as soon as the lower layers indicate that the barring is alleviated for the access category with which the access attempt for the registration procedure for mobility and periodic registration update was associated; and e) if configured for eCall only mode as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [22], shall perform the eCall inactivity procedure at expiry of timer T3444 or T3445 (see subclause 5.5.3). | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.2.3.2.7 |
4,593 | 6.2.3B UE maximum output power for modulation / channel bandwidth for UL-MIMO | For UE with two transmit antenna connectors in closed-loop spatial multiplexing scheme, the allowed Maximum Power Reduction (MPR) for the maximum output power in Table 6.2.2B-1 is specified in Table 6.2.3-1. The requirements shall be met with UL-MIMO configurations defined in Table 6.2.2B-2. For UE supporting UL-MIMO, the maximum output power is measured as the sum of the maximum output power at each UE antenna connector. For the UE maximum output power modified by MPR, the power limits specified in subclause 6.2.5B apply. If UE is configured for transmission on single-antenna port, the requirements in subclause 6.2.3 apply. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.2.3B |
4,594 | 7.3.14 Change Notification Request | 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [3] and 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [4] specify that if PGW has requested ECGI/eNodeB ID/TAI/CGI/SAI/RAI Change Reporting or reporting of change of UE presence in Presence Reporting Area(s) or User CSG information Change Reporting and if MME/S4-SGSN supports the feature, then MME/S4-SGSN shall send the Change Notification Request message on the S11/S4 interface to the SGW. If SGW supports the feature, the SGW forwards the message on the GTP based S5/S8 interface to the PGW as part of location dependent charging related procedures. In this version of the specification, the sender shall set the header TEID value to that of the peer node's Control Plane TEID on S11/S4 interface or to the peer node's Control Plane TEID on S5/S8 interface. However a receiver shall be prepared to receive messages in which the header TEID value is set to zero from implementation conforming to earlier versions of this specification. When that is the case, the receiver identifies the subscriber context based on the included LBI, IMSI, and/or MEI IEs. The MME shall increment the "MO Exception Data Counter" by one each time the MME has received the RRC cause "MO Exception data". The MME may defer sending a Change Notification Request message to report a non-zero value for the "MO Exception Data Counter" based on local configuration. If the PLMN has configured secondary RAT usage reporting and if PDN GW Secondary RAT reporting is active, the MME shall send the Change Notification Request message and include "Secondary RAT Usage Data Report" on the S11 interface to the SGW when it has received Secondary RAT usage data from the eNodeB in the following procedures, regardless of whether ULI shall be reported or not: Connection Suspend eNodeB initiated S1 release E-UTRAN to UTRAN Iu mode Inter RAT handover E-UTRAN to GERAN A/Gb mode Inter RAT handover MME triggered Serving GW relocation MME to 3G SGSN combined hard handover and SRNS relocation The MME may also send the send the Change Notification Request message and include "Secondary RAT Usage Data Report" on the S11 interface to the SGW when it has received periodic reporting of Secondary RAT usage data from eNodeB or as part of an MME initiated S1 release from the eNodeB, as described in 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [3] clause 5.7A. The SGW shall forward the "Secondary RAT Usage Data Report" to the PGW if the IRPGW flag is set to "1". Table -1: Information Element in Change Notification Request | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 7.3.14 |
4,595 | 9.3 Security requirements and procedures on N3 | N3 is the reference point between the 5G-AN and UPF. It is used to carry user plane data from the UE to the UPF. The transport of user data over N3 shall be integrity, confidentiality and replay-protected. In order to protect the traffic on the N3 reference point, it is required to implement IPsec ESP and IKEv2 certificate-based authentication as specified in sub-clause 9.1.2 of the present document with confidentiality, integrity and replay protection. IPsec is mandatory to implement on the gNB and the ng-eNB. On the core network side, a SEG may be used to terminate the IPsec tunnel. NOTE: The use of cryptographic solutions to protect N3 is an operator's decision. In case the NG-RAN node (gNB or ng-eNB) has been placed in a physically secured environment then the 'secure environment' includes other nodes and links beside the NG-RAN node. QoS related aspects are further described in sub-clause 9.1.3 of the present document. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 9.3 |
4,596 | 9.2 Default radio configurations | The following clauses only list default values for REL-15 parameters included in protocol version v15.3.0. For all fields introduced in a later protocol version, the default value is "released" or "false" unless explicitly specified otherwise. If the UE is to apply default configuration while it is configured with some critically extended fields, the UE shall apply the original version of those fields with only default values. NOTE 1: In general, the signalling should preferably support a "release" option for fields introduced after v15.3.0. The "value not applicable" should be used restrictively, mainly limited to for fields which value is relevant only if another field is set to a value other than its default. NOTE 2: For parameters in ServingCellConfig, the default values are specified in the corresponding specification. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 9.2 |
4,597 | 9.2.3 Resource blocks | A physical resource block is defined as consecutive SC-FDMA symbols in the time domain and consecutive subcarriers in the frequency domain, where and are given by Table 9.2.3-1. A physical resource block in the sidelink thus consists of resource elements, corresponding to one slot in the time domain and 180 kHz in the frequency domain. Table 9.2.3-1: Resource block parameters The relation between the physical resource block number in the frequency domain and resource elements in a slot is given by | 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.2.3 |
4,598 | Annex E (normative): Mapping between EPS and Release 99 QoS parameters | This annex specifies how the QoS parameter values of an EPS bearer are mapped to/from the Release 99 QoS parameter values of a PDP context in PDN GW, S4-SGSN and MME. Within this specification, different names are used for the QoS parameters of a PDP context e.g. "R99 QoS profile" and "R99 QoS parameters", but nevertheless the whole QoS IE as described in TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [47] is referred to including the R99 and R97/98 QoS attributes. This means that the MME performs QoS mapping, populates and forwards both R99 and R97/98 QoS attributes towards the UE in S1 mode, if the UE supports A/Gb mode or Iu mode or both. The MME also performs QoS mapping, populates and forwards both R99 and R97/98 QoS attributes also on Gn when deployed in the interoperation scenarios as listed in Annex D, clause D.2. The S4-SGSN performs QoS mapping, populates and forwards either both R99 and R97/98 QoS attributes or only R97/98 QoS attributes towards the UE in Iu mode and A/Gb mode. The P-GW performs QoS mapping, populates and forwards both R99 and R97/98 QoS attributes over Gn/Gp when deployed in the interoperation scenarios as listed in Annex D, clause D.2. The following mapping rules hold: - There is a one-to-one mapping between an EPS bearer and a PDP context. - When EPS bearer QoS parameters are mapped to Release 99 QoS parameters the pre-emption capability and the pre-emption vulnerability information of the EPS bearer ARP are ignored and the priority of the EPS bearer parameter ARP is mapped to the Release 99 bearer parameter ARP, as described in table E.1. Table E.1: Mapping of EPS bearer ARP to Release 99 bearer parameter ARP When Release 99 QoS parameters are mapped to EPS bearer QoS parameters the pre-emption capability and the pre-emption vulnerability information of the EPS bearer ARP are set based on operator policy in the entity that performs the mapping. The Release 99 bearer parameter ARP is mapped to the priority level information of the EPS bearer parameter ARP as described in table E.2. Table E.2: Mapping of Release 99 bearer parameter ARP to EPS bearer ARP The values of H (high priority) and M (medium priority) can be set according to operator requirements to ensure proper treatment of users with higher priority level information. The minimum value of H is 1. The minimum value of M is H+1. From Release 9 onwards, the priority of the EPS bearer parameter ARP is mapped one-to-one to/from the Evolved ARP parameter of a PDP context, if the network supports this parameter. NOTE 1: The setting of the values for H and M may be based on the SGSN mapping from the Release 99 bearer parameter ARP to the ARP parameter that is used for UTRAN/GERAN. NOTE 2: After a handover from UTRAN/GERAN to E-UTRAN the ARP parameter of the EPS bearer can be modified by the P-GW to re-assign the appropriate priority level, pre-emption capability and pre-emption vulnerability setting. NOTE 3: A mapping from the EPS bearer parameter ARP to the Release 99 bearer parameter ARP is not required for a P-GW when connected to an SGSN via Gn/Gp as any change of the bearer ARP parameter may get overwritten by the SGSN due to subscription enforcement. However, the P-GW should not combine services with different EPS bearer ARP values onto the same PDP context to enable a modification of the bearer ARP without impacting the assignment of services to bearers after a handover to E-UTRAN. - The EPS bearer parameters GBR and MBR of a GBR EPS bearer are mapped one-to-one to/from the Release 99 bearer parameters GBR and MBR of a PDP context associated with Traffic class 'conversational' or 'streaming'. - When EPS bearer QoS parameters are mapped to Release 99 QoS parameters the Release 99 bearer parameter MBR of PDP contexts associated with Traffic Class 'interactive' or 'background' is set equal to the value of the authorized APN-AMBR. If the APN-AMBR is modified while the UE accesses the EPS through E-UTRAN, the UE shall also set the Release 99 bearer parameter MBR to the new APN-AMBR value for all non-GBR PDP contexts of this PDN connection. The P-GW shall enforce the APN-AMBR across all PDP contexts with Traffic Class 'interactive' and 'background' for that APN. The MME or S4-SGSN may attempt to transfer APN-AMBR and UE-AMBR to a Gn/Gp SGSN - When Release 99 QoS parameters are mapped to EPS bearer QoS parameters the AMBR for the corresponding APN shall be set equal to the MBR value of the subscribed QoS profile. At handover from a Gn/Gp SGSN the MME or S4-SGSN shall provide this APN-AMBR value, if not explicitly received from the Gn/Gp SGSN, to the Serving GW and the PDN GW for each PDN connection. It is required that the subscribed MBR in the HLR/HSS is set to the desired APN-AMBR value for all subscribed APNs which may lead to a selection of a P-GW. The UE derives the APN-AMBR from the value of the MBR of a PDP context created by the PDP Context Activation Procedure as described in TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7]. NOTE 5: If the pre-Rel-8 UE with the updated subscribed MBR is connected to a GGSN, the GGSN can downgrade the MBR of the PDP contexts based on either local policy or PCC (where the MBR per QCI information is provided to the PCEF). NOTE 6: From Release 9 onwards, the APN-AMBR is available on Gn/Gp. - For handover from a Gn/Gp SGSN and if the MME does not receive AMBR values from the Gn/Gp SGSN, the MME provides a local UE-AMBR to the eNodeB until MME gets the EPS subscribed UE-AMBR. When the MME gets the subscribed UE-AMBR value from the HSS, it calculates the UE-AMBR (UE-AMBR=MIN (subscribed UE-AMBR, sum APN-AMBR of all active APNs)). Then it compares this value with the local UE-AMBR and if the local UE-AMBR is different from the corresponding derived UE-AMBR, the MME initiates HSS Initiated Subscribed QoS Modification procedure to notify the derived UE-AMBR to the eNodeB. NOTE 7: The local UE-AMBR may be for example based on the summing up of the APN-AMBR values of all active APNs of the UE or on internal configuration. - A standardized value of the EPS bearer parameter QCI is mapped one-to-one to/from values of the Release 99 parameters Traffic Class, Traffic Handling Priority, Signalling Indication, and Source Statistics Descriptor as shown in Table E.3. NOTE 8: When mapping to QCI=2 or QCI=3, the Release 99 parameter Transfer Delay is used in addition to the four Release 99 parameters mentioned above. - When EPS bearer QoS parameters are mapped to Release 99 QoS parameters the setting of the values of the Release 99 parameters Transfer Delay and SDU Error Ratio is derived from the corresponding QCI's Packet Delay Budget and Packet Loss Rate, respectively. When Packet Loss Rate parameter is further mapped to Release 99 QoS parameter Reliability Class (TS 23.107[ Quality of Service (QoS) concept and architecture ] [59], table 7), the Residual BER is considered <= 2*10-4. Also when Release 99 QoS parameters are mapped to EPS bearer QoS parameters the values of the Release 99 parameter SDU Error Ratio are ignored. - The setting of the values of all other Release 99 QoS is based on operator policy pre-configured in the MME and S4-SGSN. - In networks that support mobility from E-UTRAN to UTRAN/GERAN, if the UE has indicated support of UTRAN or GERAN, the EPS network shall provide the UE with the Release 99 QoS parameters in addition to the EPS bearer QoS parameters within EPS bearer signalling. Table E.3: Mapping between standardized QCIs and Release 99 QoS parameter values | 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") | Annex |
4,599 | 11.1.2 Authentication | Figure 11.1.2-1: Initial EAP Authentication with an external AAA server This procedure concerns both roaming and non-roaming scenarios. In the non-roaming case, the V-SMF is not involved. In the HR roaming case, the V-SMF shall proxy the signalling between the AMF in the VPLMN and the H-SMF in the HPLMN. In the LBO roaming case, only one SMF in VPLMN is involved. The following procedure is based on sub-clauses 4.2.2.2.2, 4.3.2.2.1 and 4.3.2.3 in TS 23.502[ Procedures for the 5G System (5GS) ] [8]. NOTE 1: Steps 1-6 are borrowed from clause 4.2.2.2.2 and 4.3.2.2.1 TS 23.502[ Procedures for the 5G System (5GS) ] [8] and are for information only. Steps 7 to 15are related to authentication and are normative text. 1-3. The NG-UE registers with the network performing primary authentication with the AUSF/ARPF based on its network access credentials and establishes a NAS security context with the AMF. 4. The UE initiates establishment of a new PDU Session by sending a NAS message containing a PDU Session Establishment Request within the N1 SM container, slice information (identified by S-NSSAI) , PDU session ID and the PDN it would like to connect to (identified by DNN). The PDU Session Establishment Request may contain SM PDU DN Request Container IE containing information for the PDU session authorization by the external DN. 5a. The AMF selects a V-SMF and sends either Nsmf_PDUSession_CreateSMContext Request or Nsmf_PDUSession_UpdateSMContext Request with the N1 SM container as one of its payload. It also forwards SUPI PDU Session ID, the received S-NSSAI, and the DNN. 5b. The V-SMF sends an Nsmf_PDUSession_CreateSMContext Responseor Nsmf_PDUSession_UpdateSMContext Response correspondingly to the AMF. In case of a single SMF being involved in the PDU session setup, e.g. non-roaming or local breakout, that single SMF takes the role of both V-SMF and H-SMF. In this case, steps 6 and 17 are skipped. 6. The V-SMF sends an Nsmf_PDUSession_Create Request to the H-SMF. 7. The H-SMF obtains subscription data from the UDM for the given SUPI obtained from the AMF in step 5. The SMF checks the subscription data whether the secondary authentication is required and whether the UE request is allowed according to the user subscription and local policies. If not allowed, the H-SMF will reject UE's request via SM-NAS signalling and skip rest of the procedure. If secondary authentication is required, the SMF may also check whether the UE has been authenticated and/or authorized by the same DN, as indicated DNN in step 5, or the same AAA server in a previous PDU session establishment. The SMF may skip steps 8 to 15 if positive. Note 2: The information on a successful authentication/authorization between a UE and an SMF may be saved in SMF and/or UDM. 8. The H-SMF shall trigger EAP Authentication to obtain authorization from an external DN-AAA server. If there is no existing N4 session, the H-SMF selects a UPF and establishes an N4 Session with it. The H-SMF notifies the DN-AAA server with the GPSI, if available, and the IP address(es) of the UE allocated to the PDU Session if the PDU session is of IP PDU type or the MAC address if the PDU session is of Ethernet PDU type. 9. The H-SMF may send an EAP Request/Identity message to the UE. 10. The UE may send an EAP Response/Identity message contained within t a NAS message. The DN-specific identity shall comply with Network Access Identifier (NAI) format. To avoid the additional round-trip in steps 9 and 10, the secondary authentication DN-specific identity may be sent by the UE in step 4. In this case, H-SMF forms an EAP Response/Identity message that contains the identity. 11. If there is no existing N4 session, the H-SMF selects a UPF and establishes an N4 Session with it. 12. The DN-specific identity, if provided by the UE, is forwarded to the UPF. The H-SMF identifies the DN AAA server based on the DN-specific identity provided by the UE and on local configuration. The UPF shall forward the DN-specific identity within an EAP Response/Identity message to the DN AAA Server. 13. The DN AAA server and the UE shall exchange EAP messages, as required by the EAP method. In addition, it may send additional authorization information as defined in TS 23.501[ System architecture for the 5G System (5GS) ] clause 5.6.6. 14. After the successful completion of the authentication procedure, DN AAA server shall send EAP Success message to the H-SMF. 15. This completes the authentication procedure at the SMF. The SMF may save the DN-specific ID and DNN (or DN's AAA server ID if available) in a list for successful authentication/authorization between UE and an SMF. Alternatively, the SMF may update the list in UDM. If the authorization is successful, PDU Session Establishment proceeds further starting at step 7a of Figure 4.3.2.2.1-1 in TS 23.502[ Procedures for the 5G System (5GS) ] [8]. 16a-16b. The SMF initiates a N4 Session Modification procedure with the selected UPF as in steps 10a and 10b of Fig 4.3.2.2.1-1 in TS 23.502[ Procedures for the 5G System (5GS) ] [8]. 17. The H-SMF sends an Nsmf_PDUSession_Create Response to the V-SMF. This message shall include EAP Success to be sent to the UE to V-SMF. 18. The V-SMF sends Namf_Communication_N1N2MessageTransfer to the AMF as in step 11 of Figure 4.3.2.2.1-1 in TS 23.502[ Procedures for the 5G System (5GS) ] [8]. This message shall include EAP Success to be sent to the UE within the NAS SM PDU Session Establishment Accept message. 19. The AMF forwards NAS SM PDU Session Establishment Accept message along with EAP Success to the UE as described in steps 12 and step 13 of Figure 4.3.2.2.1-1 in TS 23.502[ Procedures for the 5G System (5GS) ] [8]. The UE-requested PDU Session Establishment authentication/authorization by a DN-AAA server proceeds further as described in sub-clause 4.3.2.3 in TS 23.502[ Procedures for the 5G System (5GS) ] [8]. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 11.1.2 |
4,600 | 6.8.4.1 UMTS security context | A UMTS security context in UTRAN is only established for a UMTS subscriber with a ME that is capable of UMTS AKA. At the network side, four cases are distinguished: a) In case of a handover to a GSM BSS controlled by the same MSC/VLR, the MSC/VLR derives the 64-bit GSM cipher key Kc from the UMTS cipher/integrity keys CK and IK used before the intersystem handover (using the conversion function c3) and sends the 64-bit Kc to the target BSC (which forwards it to the BTS). If the MSC/VLR is Rel-9+ and MSC/VLR has included a 128-bit GSM ciphering algorithms as a permitted ciphering algorithm, the MSC/VLR shall also derive the 128-bit ciphering key Kc128 and send also this to the target BSC (which forwards it to the BTS). b) In case of a handover to a GSM BSS controlled by another MSC/VLR, depending on the capability of the inter-MSC communication protocol version, the initial MSC/VLR sends to the target MSC/VLR the security keys associated with the allowed security algorithms. If the inter-MSC communication protocol version only allows inclusion of the 64-bit GSM security key Kc, and the initial MSC/VLR includes a 64-bit GSM A5 ciphering algorithm as allowed ciphering algorithm, the initial MSC/VLR derives the 64-bit Kc and sends it to the new MSC/VLR. Otherwise, if the inter-MSC communication protocol version allows inclusion of UMTS security keys, the initial MSC/VLR sends, in addition, the UMTS cipher/integrity keys CK and IK used before the intersystem handover to the new MSC/VLR. If the initial MSC/VLR includes a 128-bit GSM A5 ciphering algorithm as an allowed ciphering algorithm, the initial MSC/VLR shall also calculate a Kc128 from the CK/IK and forward this to the new MSC. The new MSC/VLR stores the key(s) and then forwards them to the target BSC (which forwards them to the BTS). The initial MSC/VLR remains the anchor point throughout the service. At the user side, in either case, the ME applies the derived 64-bit GSM cipher key Kc from the key set which was used before the intersystem handover if the selected GSM ciphering algorithm requires a 64-bit key. If the selected GSM A5 ciphering algorithm requires a 128-bit key, the ME shall apply the derived 128-bit GSM cipher key Kc128 from the key set which was used before the intersystem handover. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 6.8.4.1 |
Subsets and Splits
No saved queries yet
Save your SQL queries to embed, download, and access them later. Queries will appear here once saved.