Search is not available for this dataset
doc_id
int64 1
6.72k
⌀ | Section
stringlengths 5
247
⌀ | Content
stringlengths 501
147k
⌀ | Source
stringclasses 456
values | Document Title
stringclasses 22
values | Working Group
stringclasses 21
values | Series Subject
stringclasses 9
values | Subclause
stringlengths 1
13
⌀ |
|---|---|---|---|---|---|---|---|
2,501 | 6.5.1.4C Handling the maximum number of active user plane radio bearers in NB-S1 mode | When the maximum number of active user plane radio bearers in NB-S1 mode is reached (see clause 6.5.0) and upper layers request for more DRBs for PDN connections other than PDN connections with those DRBs, the UE can choose to release one or more of the PDN connections to cater for the upper layer request. The choice of which PDN connection to be released is implementation specific. If the maximum number of active user plane radio bearers in NB-S1 mode is reached and the upper layers of the UE request user-plane resources for exception data reporting, the UE shall release a PDN connection that has user-plane resources to cater for the request for exception data reporting. The choice of which PDN connection to be released is implementation specific. If the UE needs to release a PDN connection for the reasons stated in this clause, a PDN connection that is used for exception data reporting shall not be released. If the UE releases a PDN connection to cater for the upper layer request, the UE shall release the PDN connection via explicit ESM signalling. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.5.1.4C |
2,502 | 24.2.3 Format of PLMN ID in ProSe Application ID | The PLMN ID shall uniquely identify the PLMN of the ProSe Function that has assigned the ProSe Application ID. The PLMN ID is composed of two labels which shall be separated by a dot as follows: "mcc<MCC>.mnc<MNC>" where: "mcc" and "mnc" serve as invariable identifiers for the following digits. <MCC> contains the MCC (Mobile Country Code) of the ProSe Function that has assigned the ProSe Application ID. <MNC> contains the MNC (Mobile Network Code) of the ProSe Function that has assigned the ProSe Application ID. In order to guarantee inter-PLMN operability, the <MCC> and the <MNC> shall be represented by 3 digits. If there are only 2 significant digits in the MNC, one "0" digit is inserted at the left side of the MNC to form the <MNC> in the "mnc<MNC>" label. EXAMPLE: The PLMN ID for MCC 345 and MNC 12 will be "mcc345.mnc012". | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 24.2.3 |
2,503 | 4.2.16 Architecture to support User Plane Information Exposure via a service-based interface | As depicted in Figure 4.2.16-1, the 5G System architecture allows user plane information exposure to some NFs via service-based interface in UPF. Figure 4.2.16-1: Architecture to support User Plane Information Exposure via a service-based interface NOTE 1: In this Release of the specification, only NWDAF/DCCF/MFAF, NEF/AF and TSNAF/TSCTSF are considered as the receiver of the UPF event notifications. NOTE 2: UPF information exposure is not restricted to SBI interface, i.e. reporting via PFCP over N4 to SMF is still applicable. Not all events can be subscribed to UPF directly. The details and constraints for the subscription to UPF event exposure service (i.e. direct vs. indirect) and the information exposed to certain NFs by UPF, as well as the information contained in the event notifications, are defined in clause 5.2.26.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] and clause 5.8.2.17. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2.16 |
2,504 | 4.15.6.4 Set a chargeable party at AF session setup | Figure 4.15.6.4-1: Set the chargeable party at AF session set-up 1. When setting up the connection between an ASP sponsoring a session and the UE, the ASP may communicate with the AF to request to become the chargeable party for the session to be set up by sending a Nnef_ChargeableParty_Create request message (AF Identifier, UE address, Flow description information or External Application Identifier, Sponsor Information, Sponsoring Status, Background Data Transfer Reference ID, DNN, S-NSSAI) to the NEF. The Sponsoring Status indicates whether sponsoring is started or stopped, i.e. whether the 3rd party service provider is the chargeable party or not. The Background Data Transfer Reference ID parameter identifies a previously negotiated transfer policy for background data transfer as defined in clause 4.16.7. The NEF assigns a Transaction Reference ID to the Nnef_ChargeableParty_Create request. 2. The NEF authorizes the AF request to sponsor the application traffic and stores the sponsor information together with the AF Identifier and the Transaction Reference ID. If the authorisation is not granted, step 2 is skipped and the NEF replies to the AF with a Result value indicating that the authorisation failed. NOTE: Based on operator configuration, the NEF may skip this step. In this case the authorization is performed by the PCF in step 3. 3. The NEF interacts with the PCF by triggering a Npcf_PolicyAuthorization_Create request message and provides IP filter information or Ethernet filter information, sponsored data connectivity information (as defined in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]), Background Data Transfer Reference ID (if received from the AF) and Sponsoring Status (if received from the AF) to the PCF. 4. The PCF determines whether the request is allowed and notifies the NEF if the request is not authorized. If the request is not authorized, NEF responds to the AF in step 5 with a Result value indicating that the authorization failed. 5. The NEF sends a Nnef_ChargeableParty_Create response message (Transaction Reference ID, Result) to the AF. Result indicates whether the request is granted or not. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.6.4 |
2,505 | 5.3.2 Lists of forbidden tracking areas | The UE shall store a list of "forbidden tracking areas for roaming", as well as a list of "forbidden tracking areas for regional provision of service". These lists shall be erased when the UE is switched off or when the UICC containing the USIM is removed, and periodically (with a period in the range 12 to 24 hours). When the lists are erased, the UE performs cell selection according to 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [21]. One or more tracking areas is removed from the list of "forbidden tracking areas for roaming" in the UE, as well as the list of "forbidden tracking areas for regional provision of service" if, after a subsequent procedure e.g. attach procedure, tracking area updating procedure and GUTI reallocation procedure, one or more tracking areas in the lists is received from the network. If the UE has only one PDN connection established which is for emergency bearer services, the tracking areas shall not be removed from these lists if one or more tracking areas in the lists are received from the network. In S1 mode, the UE shall update the suitable list whenever an ATTACH REJECT, TRACKING AREA UPDATE REJECT, SERVICE REJECT or DETACH REQUEST message is received with the EMM cause #12 "tracking area not allowed", #13 "roaming not allowed in this tracking area", or #15 "no suitable cells in tracking area" or an ATTACH ACCEPT or a TRACKING AREA UPDATE ACCEPT message is received with the forbidden TAI(s). In S1 mode, if the UE receives the "forbidden tracking areas for roaming" IE or the "forbidden tracking areas for regional provision of service" IE in the ATTACH REJECT, ATTACH ACCEPT, TRACKING AREA UPDATE REJECT, TRACKING AREA UPDATE ACCEPT , SERVICE REJECT or DETACH REQUEST message, the UE shall update the suitable list with the TAI(s) included in the IEs which are belonging to the serving PLMN or equivalent PLMN(s) and ignore the TAI(s) which do not belong to the serving PLMN or equivalent PLMN(s). Each list shall accommodate 40 or more TAIs. When the list is full and a new entry has to be inserted, the oldest entry shall be deleted. | 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.3.2 |
2,506 | 5.7 Reception of an EMM STATUS message by an EMM entity | The purpose of the sending of the EMM STATUS message is to report at any time certain error conditions detected upon receipt of EMM protocol data. The EMM STATUS message can be sent by both the MME and the UE (see example in figure 5.7.1). On receipt of an EMM STATUS message no state transition and no specific action shall be taken as seen from the radio interface, i.e. local actions are possible. The local actions to be taken by the MME or the UE on receipt of an EMM STATUS message are implementation dependent. Figure 5.7.1: EMM status procedure | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.7 |
2,507 | 14.11 PSCCH/PSSCH decoding capability test (CA) | The purpose of this test is to verify the maximum number of Sidelink processes and the maximum number of bits per TTI supported by the UE with UE SL-C-RX Category 4 for UEs supporting V2X CA. For CA with 2 SL CCs, the requirements are specified in Table 14.11-4 based on single carrier requirement specified in Table 14.11-3, with the test parameters specified in Table 14.11-1 and Table 14.11-2 according to UE capability. For CA with 3 SL CCs, the requirements are specified in Table 14.11-5 based on single carrier requirement specified in Table 14.11-3, with test parameters specified in Table 14.11-1 and Table 14.11-2 according to UE capability. Table 14.11-1: Test Parameters Table 14.11-2: Test Parameters Table 14.11-3: Single carrier performance with different bandwidths for multiple CA configurations Table 14.11-4: Minimum performance for CA configuration with 2 SL CCs Table 14.11-5: Minimum performance for CA configuration with 3 SL CCs | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 14.11 |
2,508 | 8.6.1 RRC connected to RRC inactive | This clause gives the RRC connected to RRC inactive state transition given that gNB consists of gNB-CU and gNB-DU(s), as shown in Figure 8.6.1-1. Figure 8.6.1-1: RRC connected to RRC inactive state transition procedure 0. At first, the gNB-CU determines the UE to enter into RRC inactive mode from connected mode. 1. The gNB-CU generates RRCRelease message which includes suspend configuration towards UE. The RRC message is encapsulated in UE CONTEXT RELEASE COMMAND message to the gNB-DU. 2. The gNB-DU forwards RRCRelease message to UE. 3. The gNB-DU responds with UE CONTEXT RELEASE COMPLETE message. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.6.1 |
2,509 | 9.3.20 Retrieve | This message is sent by the mobile user to request the retrieval of a held call. See table 9.69b/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] for the content of the RETRIEVE message. For the use of this message, see 3GPP TS 24.010[ Mobile radio interface layer 3; Supplementary services specification; General aspects ] [21]. Message type: RETRIEVE Significance: local Direction: mobile station to network Table 9.69b/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : RETRIEVE message content | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.3.20 |
2,510 | 6.1.3.4 UE Contention Resolution Identity MAC Control Element | The UE Contention Resolution Identity MAC control element is identified by MAC PDU subheader with LCID as specified in table 6.2.1-1. This control element has a fixed 48-bit size and consists of a single field defined as follows (figure 6.1.3.4-1) - UE Contention Resolution Identity: If this MAC control element is included in response to an uplink CCCH transmission, then this field contains the uplink CCCH SDU if the uplink CCCH SDU is 48 bits long. If the CCCH SDU is longer than 48 bits, this field contains the first 48 bits of the uplink CCCH SDU. If this MAC control element is included in response to an uplink DCCH transmission (i.e. the MAC entity is configured with rach-Skip or rach-SkipSCG), then the MAC entity shall ignore the contents of this field. Figure 6.1.3.4-1: UE Contention Resolution Identity MAC control element | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.1.3.4 |
2,511 | 6.6.2F.2.2 Minimum requirement (network signalled value "NS_03") | Additional spectrum emission requirements are signalled by the network to indicate that the UE shall meet an additional requirement for a specific deployment scenario as part of the cell broadcast message. When "NS_03" is indicated in the cell, the NB-IoT channel is deployed in the upper guard-band of a 10MHz E-UTRA channel and the separation between the two channel centres is equal to 4.695 MHz. The power of any UE emission shall not exceed the levels specified in Table 6.6.2.1.1-1 for the specified E-UTRA channel bandwidth and the levels specified in Table 6.6.2F.1-1 for the NB-IoT channel. Note: UEs that meet the above emission requirement would automatically meet the E-UTRA additional spectrum emission masks as defined in 6.6.2.2 for the applicable operating bands. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.6.2F.2.2 |
2,512 | 10.2.3.1 Scrambling | Scrambling shall be done according to clause 6.3.1. If the NPDSCH is carrying the BCCH, the scrambling sequence generator shall be initialised with . Otherwise, the scrambling sequence generator shall be initialised with whereis the first slot of the transmission of the codeword. In case of NPDSCH repetitions and the NPDSCH carrying the BCCH, the scrambling sequence generator shall be reinitialized according to the expression above for each repetition. In case of NPDSCH repetitions and the NPDSCH is not carrying the BCCH, the scrambling sequence generator shall be reinitialized according to the expression above after every transmission of the codeword withand set to the first slot and the frame, respectively, used for the transmission of the repetition. | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 10.2.3.1 |
2,513 | – DL-PPW-PreConfig | The IE DL-PPW-PreConfig provides configuration for a measurement window where a UE is expected to measure the DL PRS, if it is inside the active DL BWP and with the same numerology as the active DL BWP. Based upon the indication received in the configuration, the UE identifies whether the DL PRS priority is higher than that of the other DL signals or channels and accordingly determines, for example, the UE is expected to measure the DL PRS and is not expected to receive other DL signals and channels. DL-PPW-PreConfig information element -- ASN1START -- TAG-DL-PPW-PRECONFIG-START DL-PPW-PreConfig-r17 ::= SEQUENCE { dl-PPW-ID-r17 DL-PPW-ID-r17, dl-PPW-PeriodicityAndStartSlot-r17 DL-PPW-PeriodicityAndStartSlot-r17, length-r17 INTEGER (1..160), type-r17 ENUMERATED {type1A, type1B, type2} OPTIONAL, -- Cond MultiType priority-r17 ENUMERATED {st1, st2, st3} OPTIONAL -- Cond MultiState } DL-PPW-ID-r17 ::= INTEGER (0..maxNrofPPW-ID-1-r17) DL-PPW-PeriodicityAndStartSlot-r17 ::= CHOICE { scs15 CHOICE { n4 INTEGER (0..3), n5 INTEGER (0..4), n8 INTEGER (0..7), n10 INTEGER (0..9), n16 INTEGER (0..15), n20 INTEGER (0..19), n32 INTEGER (0..31), n40 INTEGER (0..39), n64 INTEGER (0..63), n80 INTEGER (0..79), n160 INTEGER (0..159), n320 INTEGER (0..319), n640 INTEGER (0..639), n1280 INTEGER (0..1279), n2560 INTEGER (0..2559), n5120 INTEGER (0..5119), n10240 INTEGER (0..10239), ... }, scs30 CHOICE { n8 INTEGER (0..7), n10 INTEGER (0..9), n16 INTEGER (0..15), n20 INTEGER (0..19), n32 INTEGER (0..31), n40 INTEGER (0..39), n64 INTEGER (0..63), n80 INTEGER (0..79), n128 INTEGER (0..127), n160 INTEGER (0..159), n320 INTEGER (0..319), n640 INTEGER (0..639), n1280 INTEGER (0..1279), n2560 INTEGER (0..2559), n5120 INTEGER (0..5119), n10240 INTEGER (0..10239), n20480 INTEGER (0..20479), ... }, scs60 CHOICE { n16 INTEGER (0..15), n20 INTEGER (0..19), n32 INTEGER (0..31), n40 INTEGER (0..39), n64 INTEGER (0..63), n80 INTEGER (0..79), n128 INTEGER (0..127), n160 INTEGER (0..159), n256 INTEGER (0..255), n320 INTEGER (0..319), n640 INTEGER (0..639), n1280 INTEGER (0..1279), n2560 INTEGER (0..2559), n5120 INTEGER (0..5119), n10240 INTEGER (0..10239), n20480 INTEGER (0..20479), n40960 INTEGER (0..40959), ... }, scs120 CHOICE { n32 INTEGER (0..31), n40 INTEGER (0..39), n64 INTEGER (0..63), n80 INTEGER (0..79), n128 INTEGER (0..127), n160 INTEGER (0..159), n256 INTEGER (0..255), n320 INTEGER (0..319), n512 INTEGER (0..511), n640 INTEGER (0..639), n1280 INTEGER (0..1279), n2560 INTEGER (0..2559), n5120 INTEGER (0..5119), n10240 INTEGER (0..10239), n20480 INTEGER (0..20479), n40960 INTEGER (0..40959), n81920 INTEGER (0..81919), ... }, ... } -- TAG-DL-PPW-PRECONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,514 | 4.4.1.4 Maximum UL cell PDCP SDU bit-rate | This measurement provides the maximum cell bit-rate of PDCP SDUs measured on the uplink. This represents successful transmissions of user plane traffic; control signalling and retransmissions are excluded from this measure. This is a sum counter measured across all QCIs. SI The measurement is obtained by sampling at pre-defined intervals the UL cell PDCP SDU bit-rate summed across all QCIs (see clause 4.4.1.2), and then taking the arithmetic maximum of these samples. A single integer value representing the maximum bit-rate measured in kbit/s. DRB.PdcpSduBitrateUlMax EUtranCellFDD EUtranCellTDD Valid for packet switched traffic EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.4.1.4 |
2,515 | I.2.1 Requirements for setup and configuration | Setting up and configuring RNCs in exposed locations shall be authenticated and authorized so that attackers shall not be able to modify the settings and software configurations of the RNCs in exposed locations via local or remote access. 1. The support of security associations is required between the 3G core network and the RNC in an exposed location and between adjacent RNCs in exposed locations. These security association establishments shall be mutually authenticated and used for user and control plane communication between the entities. The security associations shall be realized according to Annex I.3 of the present document. 2. Communication between the O&M systems and the RNC in an exposed location shall be confidentiality, integrity and replay protected from unauthorized parties. The support of security associations is required between the RNC in an exposed location and an entity in the 3G core network or in an O&M domain trusted by the operator. These security association establishments shall be mutually authenticated. 3. The RNC in an exposed location shall ensure that software/data change attempts are authorized. 4. The RNC in an exposed location shall use authorized data/software. 5. Sensitive parts of the boot-up process shall be executed with the help of the secure environment. 6. Confidentiality of software transfer towards the RNC in an exposed location shall be ensured. 7. Integrity protection of software transfer towards the RNC in an exposed location shall be ensured. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | I.2.1 |
2,516 | 9.11.3.42 PDU session reactivation result | The purpose of the PDU session reactivation result information element is to indicate the result of establishments of user-plane resources of PDU sessions. The PDU session reactivation result information element is coded as shown in figure 9.11.3.42.1 and table 9.11.3.42.1. The PDU session reactivation result is a type 4 information element with minimum length of 4 octets and maximum length of 34 octets. Figure 9.11.3.42.1: PDU session reactivation result information element Table 9.11.3.42.1: PDU session reactivation result 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.42 |
2,517 | 8.13.3.2.1 Minimum Requirement Dual-Layer Spatial Multiplexing 2 Tx Antenna Port for FDD PCell | The purpose of these tests is to verify dual-layer transmission on antenna ports 7 and 8 upon detection of a PDCCH with DCI format 2C. For TDD FDD CA with FDD PCell and 2DL CCs, the requirements are specified in Table 8.13.3.2.1-4 based on single carrier requirement specified in Table 8.13.3.2.1-2 and Table 8.13.3.2.1-3, with the addition of the parameters in Table 8.13.3.2.1-1 and the downlink physical channel setup according to Annex C.3.2. For TDD FDD CA with FDD PCell and 3DL CCs, the requirements are specified in Table 8.13.3.2.1-5 based on single carrier requirement specified in Table 8.13.3.2.1-2 and Table 8.13.3.2.1-3, with the addition of the parameters in Table 8.13.3.2.1-1 and the downlink physical channel setup according to Annex C.3.2 For TDD FDD CA with FDD PCell and 4DL CCs, the requirements are specified in Table 8.13.3.2.1-6 based on single carrier requirement specified in Table 8.13.3.2.1-2 and Table 8.13.3.2.1-3, with the addition of the parameters in Table 8.13.3.2.1-1 and the downlink physical channel setup according to Annex C.3.2. For TDD FDD CA with FDD PCell and 5DL CCs, the requirements are specified in Table 8.13.3.2.1-7 based on single carrier requirement specified in Table 8.13.3.2.1-2 and Table 8.13.3.2.1-3, with the addition of the parameters in Table 8.13.3.2.1-1 and the downlink physical channel setup according to Annex C.3.2. The test coverage for different number of component carriers is defined in 8.1.2.4. Table 8.13.3.2.1-1: Test Parameters for Multi-Layer Spatial Multiplexing (FRC) for CA Table 8.13.3.2.1-2: Single carrier performance with different bandwidths for multiple CA configurations for FDD PCell and SCell (FRC) Table 8.13.3.2.1-3: Single carrier performance with different bandwidths for multiple CA configurations for TDD SCell (FRC) Table 8.13.3.2.1-4: Minimum performance for multiple CA configurations with 2DL CCs (FRC) Table 8.13.3.2.1-5: Minimum performance for multiple CA configurations with 3DL CCs (FRC) Table 8.13.3.2.1-6: Minimum performance for multiple CA configurations with 4DL CCs (FRC) Table 8.13.3.2.1-7: Minimum performance for multiple CA configurations with 5DL CCs (FRC) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.13.3.2.1 |
2,518 | – MeasObjectUTRA-FDD | The IE MeasObjectUTRA-FDD specifies information applicable for inter-RAT UTRA-FDD neighbouring cells. MeasObjectUTRA-FDD information element -- ASN1START -- TAG-MEASOBJECTUTRA-FDD-START MeasObjectUTRA-FDD-r16 ::= SEQUENCE { carrierFreq-r16 ARFCN-ValueUTRA-FDD-r16, utra-FDD-Q-OffsetRange-r16 UTRA-FDD-Q-OffsetRange-r16 OPTIONAL, -- Need R cellsToRemoveList-r16 UTRA-FDD-CellIndexList-r16 OPTIONAL, -- Need N cellsToAddModList-r16 CellsToAddModListUTRA-FDD-r16 OPTIONAL, -- Need N ... } CellsToAddModListUTRA-FDD-r16 ::= SEQUENCE (SIZE (1..maxCellMeasUTRA-FDD-r16)) OF CellsToAddModUTRA-FDD-r16 CellsToAddModUTRA-FDD-r16 ::= SEQUENCE { cellIndexUTRA-FDD-r16 UTRA-FDD-CellIndex-r16, physCellId-r16 PhysCellIdUTRA-FDD-r16 } UTRA-FDD-CellIndexList-r16 ::= SEQUENCE (SIZE (1..maxCellMeasUTRA-FDD-r16)) OF UTRA-FDD-CellIndex-r16 UTRA-FDD-CellIndex-r16 ::= INTEGER (1..maxCellMeasUTRA-FDD-r16) -- TAG-MEASOBJECTUTRA-FDD-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,519 | – PUSCH-ConfigCommon | The IE PUSCH-ConfigCommon is used to configure the cell specific PUSCH parameters. PUSCH-ConfigCommon information element -- ASN1START -- TAG-PUSCH-CONFIGCOMMON-START PUSCH-ConfigCommon ::= SEQUENCE { groupHoppingEnabledTransformPrecoding ENUMERATED {enabled} OPTIONAL, -- Need R pusch-TimeDomainAllocationList PUSCH-TimeDomainResourceAllocationList OPTIONAL, -- Need R msg3-DeltaPreamble INTEGER (-1..6) OPTIONAL, -- Need R p0-NominalWithGrant INTEGER (-202..24) OPTIONAL, -- Need R ... } -- TAG-PUSCH-CONFIGCOMMON-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,520 | 5.44.3.2 Session management related policy control | For PIN indirect communication and PIN-DN communication via PEGC and5GC with PDU session, the 5GC supports the session policy control. The policy control is based on session management procedures as specified in TS 23.502[ Procedures for the 5G System (5GS) ] [3] and TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. An AF may provide QoS parameters for PIN traffic to 5GC as specified in clauses 4.15.6.6, 4.15.6.6a, and 4.15.6.14 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. An AF may influence traffic routing for PDU sessions for PIN-DN communication as specified in clause 5.6.7 and in clause 4.3.6 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.44.3.2 |
2,521 | 5.5.2.2.1 Reference signal sequence | The PUCCH demodulation reference signal sequence for PUCCH formats 1, 1a, 1b, 2, 2a, 2b, and 3 is defined by where and is the number of antenna ports used for PUCCH transmission. For PUCCH formats 2a and 2b, equals for , where is defined in clause 5.4.2. For all other cases, The sequence is given by clause 5.5.1 with and where the expression for the cyclic shift is determined by the PUCCH format. For PUCCH formats 1, 1a and 1b, is given by where , , and are defined by clause 5.4.1. The number of reference symbols per slot and the sequence are given by Table 5.5.2.2.1-1 and 5.5.2.2.1-2, respectively. For PUCCH formats 2, 2a and 2b, is defined by clause 5.4.2. The number of reference symbols per slot and the sequence are given by Table 5.5.2.2.1-1 and 5.5.2.2.1-3, respectively. For PUCCH format 3, is given by where is given by Table 5.5.2.2.1-4 and and for the first and second slot in a subframe, respectively, are obtained from clause 5.4.2A. The number of reference symbols per slot and the sequence are given by Table 5.5.2.2.1-1 and 5.5.2.2.1-3, respectively. Table 5.5.2.2.1-1: Number of PUCCH demodulation reference symbols per slot Table 5.5.2.2.1-2: Orthogonal sequences for PUCCH formats 1, 1a and 1b Table 5.5.2.2.1-3: Orthogonal sequences for PUCCH formats 2, 2a, 2b and 3. Table 5.5.2.2.1-4: Relation between and for PUCCH format 3. The PUCCH demodulation reference signal sequence for PUCCH formats 4 and 5 is defined by where and Clause 5.5.1 defines the sequence where . The cyclic shift in a slot is given as with where the values of and are given by Clause 5.5.2.1.1 and with obtained as described in clause 5.4.2C. | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.5.2.2.1 |
2,522 | – SL-RLC-ChannelConfig | The IE SL-RLC-ChannelConfig specifies the configuration information for PC5 Relay RLC channel between L2 U2N Relay UE and L2 U2N Remote UE, or between L2 U2U Remote UE and L2 U2U Relay UE. SL-RLC-ChannelConfig information element -- ASN1START -- TAG-SL-RLC-RLC-CHANNEL-CONFIG-START SL-RLC-ChannelConfig-r17 ::= SEQUENCE { sl-RLC-ChannelID-r17 SL-RLC-ChannelID-r17, sl-RLC-Config-r17 SL-RLC-Config-r16 OPTIONAL, -- Need M sl-MAC-LogicalChannelConfig-r17 SL-LogicalChannelConfig-r16 OPTIONAL, -- Need M sl-PacketDelayBudget-r17 INTEGER (0..1023) OPTIONAL, -- Need M ...} -- TAG-SL-RLC-CHANNEL-CONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,523 | 9.2.1.8 TDD (Modulation and TBS index Table 2 and 4-bit CQI Table 2 are used) | The following requirements apply to UE Category 11-12 and UE DL Category ≥11. For the parameters specified in Table 9.2.1.8-1, and using the downlink physical channels specified in tables C.3.2-1 and C.3.2-2, the reported CQI value according to RC.1A TDD in Table A.4-1 shall be in the range of ±1 of the reported median more than 90% of the time. If the PDSCH BLER using the transport format indicated by median CQI is less than or equal to 0.1, the BLER using the transport format indicated by the (median CQI + 1) shall be greater than 0.1, or the BLER using the transport format indicated by the (median CQI + 1) shall be less than or equal to 0.1 when the highest MCS value of the test case has reached. If the PDSCH BLER using the transport format indicated by the median CQI is greater than 0.1, the BLER using transport format indicated by (median CQI – 1) shall be less than or equal to 0.1. In this test, 4-bit CQI Table 2 in Table 7.2.3-2 in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [6], and Modulation and TBS index table 2 in Table 7.1.7.1-1A for PDSCH in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [6] are applied. Table 9.2.1.8-1: PUCCH 1-0 static test (TDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.2.1.8 |
2,524 | 10.5.5.11 Receive N-PDU Numbers list | The purpose of the Receive N-PDU Numbers list information element is to specify the current SNDCP Receive N-PDU Number values. The Receive N-PDU Number list is a type 4 information element with a length of 4 to 19 octets. The value part of a Receive N-PDU Number list information element is coded as shown in figure 10.5.127/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.144/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.127/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Receive N-PDU Number list information element Table 10.5.144/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Receive N-PDU Number list information element | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.5.11 |
2,525 | 5.8.9.2.3 Actions related to transmission of the UECapabilityEnquirySidelink by the UE | The initiating UE shall set the contents of UECapabilityEnquirySidelink message as follows: 1> include in UE radio access capabilities for sidelink within ue-CapabilityInformationSidelink, if needed; NOTE 1: It is up to initiating UE to decide whether ue-CapabilityInformationSidelink should be included. 1> set frequencyBandListFilterSidelink to include frequency bands for which the peer UE is requested to provide supported bands and band combinations; NOTE 2: The initiating UE is not allowed to send the UECapabilityEnquirySidelink message without including the field frequencyBandListFilterSidelink. 1> submit the UECapabilityEnquirySidelink message to lower layers for transmission. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.9.2.3 |
2,526 | 8.2 Information Element Format 8.2.1 General | Figure 8.2-1 depicts the format of an information element. Figure 8.2-1: Information Element Format An IE has the following mandatory fields: - Type field: This field indicates the type of Information Element. The valid values of the IE type are defined in clause 8.1. - Length: This field contains the length of the information element excluding the first four octets, which are common for all information elements (Type, Length and the contents of octet 4) and is denoted "n" in Figure 8.2-1. For all the length fields, bit 8 of the lowest numbered octet is the most significant bit and bit 1 of the highest numbered octet is the least significant bit. - Instance: This field shall be used to differentiate amongst different parameters in one specific message which use the same information element type (see also clause 6.1.3 "Information Element Instance"). An IE is said to be TLIV (Type, Length, Instance, Value) encoded. | 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.2 |
2,527 | 4.14.2.5 Number of attempted additions of LWIP DRB | a) This measurement provides the number of attempted additions of LWIP DRB. b) CC c) On transmission of RRCConnectionReconfiguration message which includes the drb-ToAddModList in the radioResourceConfigDedicated information element, and the drb-ToAddModList contains at least one drb-Identity that is not part of the current UE configuration and the drb-TypeLWIP of this DRB is included and not set to "eutran" (see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]). d) An integer value e) LWI.LwipDrbAddAtt f) WLANMobilitySet 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.14.2.5 |
2,528 | 5.18.3 Network selection by the UE | NOTE: This clause applies to UEs not operating in SNPN access mode. Network selection for UEs set to operate in SNPN access mode is described in clause 5.30.2.4. A UE that has a subscription to one of the sharing core network operators shall be able to select this core network operator while within the coverage area of the shared network and to receive subscribed services from that core network operator. Each cell in shared NG-RAN shall in the broadcast system information include the PLMN-IDs concerning available core network operators in the shared network. When a UE performs an Initial Registration to a network, one of available PLMNs shall be selected to serve the UE. UE uses all the received broadcast PLMN-IDs in its PLMN (re)selection processes which is specified in TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [17]. UE shall inform the NG-RAN of the selected PLMN so that the NG-RAN can route correctly. The NG-RAN shall inform the core network of the selected PLMN. As per any network, after Initial Registration to the shared network and while remaining served by the shared network, the network selection procedures specified in TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [17] may cause the UE to perform a reselection of another available PLMN. UE uses all of the received broadcast PLMN-IDs in its cell and PLMN (re)selection processes. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.18.3 |
2,529 | 5.5.3 Tracking area updating procedure (S1 mode only) 5.5.3.1 General | The tracking area updating procedure is always initiated by the UE and is used for the following purposes: - normal tracking area updating to update the registration of the actual tracking area of a UE in the network; - combined tracking area updating to update the registration of the actual tracking area for a UE in CS/PS mode 1 or CS/PS mode 2 of operation; - periodic tracking area updating to periodically notify the availability of the UE to the network; - IMSI attach for non-EPS services when the UE is attached for EPS services. This procedure is used by a UE in CS/PS mode 1 or CS/PS mode 2 of operation; - in various cases of inter-system change from Iu mode to S1 mode or from A/Gb mode to S1 mode; - in various cases of inter-system change from N1 mode to S1 mode if the UE operates in single-registration mode and as described in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54]; - S101 mode to S1 mode inter-system change; - MME load balancing; - to update certain UE specific parameters in the network; - recovery from certain error cases; - to indicate that the UE enters S1 mode after CS fallback or 1xCS fallback; - to indicate to the network that the UE has selected a CSG cell whose CSG identity and associated PLMN identity are not included in the UE's Allowed CSG list or in the UE's Operator CSG list; - to indicate the current radio access technology to the network for the support of terminating access domain selection for voice calls or voice sessions; - to indicate to the network that the UE has locally released EPS bearer context(s); - to indicate to the network that the MUSIM UE needs to use an IMSI Offset value as specified in 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10] that is used for deriving the paging occasion as specified in 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [21]; - to indicate to the network the unavailability information or a change in the unavailability information; and - to indicate to the network that the UE needs to come out of the unavailability period and resume normal services. Details on the conditions for the UE to initiate the tracking area updating procedure are specified in clause 5.5.3.2.2 and clause 5.5.3.3.2. If the MUSIM UE is attached for emergency bearer services and initiates a tracking area updating procedure, the network shall not indicate the support of: - the NAS signalling connection release; - the paging indication for voice services; - the reject paging request; - the paging restriction; or - the paging timing collision control; in the TRACKING AREA UPDATE ACCEPT message. While a UE has a PDN connection for emergency bearer services, the UE shall not perform manual CSG selection. If control plane CIoT EPS optimization is not used by the UE, a UE initiating the tracking area updating procedure in EMM-IDLE mode may request the network to re-establish the radio and S1 bearers for all active EPS bearer contexts during the procedure. If control plane CIoT EPS optimization is used by the UE, a UE initiating the tracking area updating procedure in EMM-IDLE mode may request the network to re-establish the radio and S1 bearers for all active EPS bearer contexts associated with PDN connections established without control plane only indication during the procedure. In a shared network, the UE shall choose one of the PLMN identities as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. The UE shall construct the TAI of the cell from this chosen PLMN identity and the TAC received for this PLMN identity on the broadcast system information. The chosen PLMN identity shall be indicated to the E-UTRAN (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]). Whenever a TRACKING AREA UPDATE REJECT message with the EMM cause #11 "PLMN not allowed" is received by the UE, the chosen PLMN identity shall be stored 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. Whenever a TRACKING AREA UPDATE REJECT message with the EMM cause #14 "EPS services not allowed in this PLMN" is received by the UE, the chosen PLMN identity shall be stored in the "forbidden PLMNs for GPRS service". Whenever a TRACKING AREA UPDATE REJECT message is received by the UE with the EMM cause #12 "tracking area not allowed", #13 "roaming not allowed in this tracking area", or #15 "no suitable cells in tracking Area", the constructed TAI shall be stored in the suitable list. In a shared network, if TRACKING AREA UPDATE REJECT is received as a response to a tracking area updating procedure initiated in EMM-CONNECTED mode, the UE need not update forbidden lists. A tracking area updating attempt counter is used to limit the number of subsequently rejected tracking area update attempts. The tracking area updating attempt counter shall be incremented as specified in clause 5.5.3.2.6. Depending on the value of the tracking area updating attempt counter, specific actions shall be performed. The tracking area updating attempt counter shall be reset when: - a normal or periodic tracking area updating or a combined tracking area updating procedure is successfully completed; - a normal or periodic tracking area updating or a combined tracking area updating procedure is rejected with EMM cause #11, #12, #13, #14, #15, #25 or #35: - a combined attach procedure or a combined tracking area updating procedure is completed for EPS services only with cause #2 or #18; or - a new PLMN is selected. Additionally the tracking area updating attempt counter shall be reset when the UE is in substate EMM-REGISTERED.ATTEMPTING-TO-UPDATE or EMM-REGISTERED.ATTEMPTING-TO-UPDATE-MM, and: - a new tracking area is entered; - timer T3402 expires; or - timer T3346 is started. | 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,530 | 5.3.3.2 E-UTRAN Tracking Area Update without S-GW Change | Figure 5.3.3.2-1: E-UTRAN Tracking Area Update without S-GW change NOTE 1: For a PMIP-based S5/S8, procedure steps (A) are defined in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [2]. Steps 12 and 14 concern GTP based S5/S8. NOTE 2: In the case of Tracking Area Update without MME change the signalling in steps 4, 5, 7 and steps 9-19 are skipped. A change of UE Time Zone, User CSG information or Serving Network is signalled in the next Service Request. If TAI change need to be reported to the PDN GW, location information change reporting procedure described in clause 5.9.2 is performed. NOTE 3: Deferred reporting of UE Time Zone, or Serving Network per NOTE 2 may fail when inter-MME/SGSN mobility occurs before a UE sends SERVICE REQUEST and the target MME/SGSN (e.g. pre-Release 10) does not support the "Change to Report" flag. 1. One of the triggers described in clause 5.3.3.0 for starting the TAU procedure occurs. 2. The UE initiates a TAU procedure by sending, to the eNodeB, a Tracking Area Update Request (UE Core Network Capability, MS Network Capability, Preferred Network behaviour, Support for restriction of use of Enhanced Coverage, active flag, signalling active flag, EPS bearer status, old GUTI, Old GUTI Type, last visited TAI, P-TMSI signature, additional GUTI, KSISGSN, KSIASME, NAS sequence number, NAS-MAC, Voice domain preference and UE's usage setting, UE has UE Radio Capability ID assigned for the selected PLMN, Requested IMSI Offset, Release Request indication, Paging Restriction Information, Unavailability Period Duration, Start of Unavailability Period) message together with RRC parameters indicating the Selected Network and the old GUMMEI. An exception is that, if the TAU was triggered for load re-balancing purposes (see clause 4.3.7.3), the old GUMMEI is not included in the RRC parameters. The UE shall set the Old GUTI Type to indicate whether the Old GUTI is a native GUTI or is mapped from a P-TMSI and RAI. If the UE's TIN indicates "GUTI" or "RAT-related TMSI" and the UE holds a valid GUTI then the old GUTI indicates this valid GUTI. If the UE's TIN indicates "P-TMSI" and the UE holds a valid P-TMSI and related RAI then these two elements are indicated as the old GUTI. Mapping a P-TMSI and RAI to a GUTI is specified in Annex H. When the UE is in connected mode (e.g. in URA_PCH) when it reselects to E-UTRAN, the UE shall set its TIN to "P-TMSI". If the UE holds a valid GUTI and the old GUTI indicates a GUTI mapped from a P-TMSI and RAI, then the UE indicates the GUTI as additional GUTI. If the old GUTI indicates a GUTI mapped from a P-TMSI and RAI, and the UE has a valid P-TMSI signature, the P-TMSI signature shall be included. The additional GUTI in the Tracking Area Update Request message allows the new MME to find any already existing UE context stored in the new MME when the old GUTI indicates a value mapped from a P-TMSI and RAI. Alternatively, when a UE only supports E-UTRAN, it identifies itself with the old GUTI and sets the Old GUTI Type to 'native'. The RRC parameter "old GUMMEI" takes its value from the identifier that is signalled as the old GUTI according to the rules above. For a combined MME/SGSN the eNodeB is configured to route the MME-code(s) of this combined node to the same combined node. This eNodeB is also configured to route MME-code(s) of GUTIs that are generated the UE's mapping of the P-TMSIs allocated by the combined node. Such an eNodeB configuration may also be used for separate nodes to avoid changing nodes in the pool caused by inter RAT mobility. The last visited TAI shall be included in order to help the MME produce a good list of TAIs for any subsequent TAU Accept message. Selected Network indicates the network that is selected. Active flag is a request by the UE to activate the radio and S1 bearers for all the active EPS Bearers by the TAU procedure. Signalling active flag is a request by UE using Control Plane CIoT EPS Optimisation to maintain the NAS signalling connection after Tracking Area Update Procedure is completed in order to transmit pending Data using the Data Transport in Control Plane CIoT EPS Optimisation or NAS signalling. The UE's ISR capability is included in the UE Core Network Capability element. The EPS bearer status indicates each EPS bearer that is active in the UE. The TAU Request message shall be integrity protected by the NAS-MAC as described in TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [41]. KSIASME is included if the UE has valid security parameters. NAS sequence number indicates the sequential number of the NAS message. In the RRC connection establishment signalling associated with the TAU Request, the UE indicates its support of the CIoT EPS Optimisations relevant for MME selection. For UE using CIoT EPS Optimisation without any activated PDN connection, there is no active flag or EPS bearer status included in the TAU Request message. For a UE with a running Service Gap timer in the UE the UE shall not set the active flag or the signalling active flag in the TAU request message (see clause 4.3.17.9) except for network access for regulatory prioritized services like Emergency services or exception reporting. If the UE has any PDN connection of PDN Type "non-IP" or "Ethernet", the UE shall send the EPS bearer status in the TAU Request message. KSISGSN is included if the UE indicates a GUTI mapped from a P-TMSI in the information element "old GUTI". The UE sets the voice domain preference and UE's usage setting according to its configuration, as described in clause 4.3.5.9. The UE includes extended idle mode DRX parameters information element if it needs to enable extended idle mode DRX, even if extended idle mode DRX parameters were already negotiated before. If a UE includes a Preferred Network Behaviour, this defines the Network Behaviour the UE is expecting to be available in the network as defined in clause 4.3.5.10. If the UE supports RACS as defined in clause 5.11.3a, and if the UE is provisioned with a UE Radio Capability ID for use in the selected PLMN (i.e. PLMN-assigned for the specific PLMN or manufacturer-assigned), the UE includes a flag that indicates it has an assigned UE Radio Capability ID for use in the selected PLMN but the actual UE Radio Capability is provided to MME after security context is established in step 6 (see below). If a Multi-USIM UE wants to enter ECM-IDLE state it includes the Release Request indication and optionally provides Paging Restriction Information. If a Multi-USIM UE needs to modify the Paging Occasions in order to avoid paging collisions, it sends a Requested IMSI Offset to the MME, in order to signal an alternative IMSI as described in clause 4.3.33. If the UE is using a eNodeB that provides discontinuous coverage (e.g. for satellite access with discontinuous coverage), the UE may include an Unavailability Period Duration and Start of Unavailability Period, see clause 4.13.8.2. 3. The eNodeB derives the MME address from the RRC parameters carrying the old GUMMEI, the indicated Selected Network and the RAT (NB-IoT or WB-E-UTRAN). If that GUMMEI is not associated with the eNodeB, or the GUMMEI is not available or the UE indicates that the TAU procedure was triggered by load re-balancing, the eNodeB selects the MME as described in clause 4.3.8.3 on "MME Selection Function". The eNodeB forwards the TAU Request message together with the CSG access mode, CSG ID, TAI+ECGI of the cell from where it received the message and with the Selected Network to the MME. CSG ID is provided by RAN if the UE sends the TAU Request message via a CSG cell or a hybrid cell. CSG access mode is provided if the UE sends the TAU 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. For SIPTO at the Local Network with stand-alone GW architecture the eNodeB includes the Local Home Network ID in the Initial UE Message and in Uplink NAS Transport message if the target cell is in a Local Home Network. 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. 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 TAU 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]. 4. The new MME differentiates the type of the old node, i.e. MME or SGSN, as specified in clause 4.3.19, uses the GUTI received from the UE to derive the old MME/S4 SGSN address and sends a Context Request (old GUTI, MME Address, UE Validated, complete TAU Request message, P-TMSI Signature, CIoT EPS Optimisation support inidication) message to the old MME/S4 SGSN to retrieve the user information. UE Validated indicates that the new MME has validated the integrity protection of the TAU message, e.g. based on native EPS security context for the UE. To validate the Context Request the old MME uses the complete TAU Request message and the old S4 SGSN uses the P-TMSI Signature and responds with an appropriate error if integrity check fails in old MME/S4 SGSN. This shall initiate the security functions in the new MME. If the security functions authenticate the UE correctly, the new MME shall send a Context Request (IMSI, complete TAU Request message, MME Address, UE Validated) message to the old MME/S4 SGSN with the UE Validated set. If the new MME indicates that it has authenticated the UE or if the old MME/old S4 SGSN authenticates the UE, the old MME/old S4 SGSN starts a timer. If the UE with emergency bearers is not authenticated in the old MME/old S4 SGSN (in a network supporting unauthenticated UEs) the old MME/old S4 SGSN continues the procedure with sending a Context Response and starting the timer also when it cannot validate the Context Request. If a RLOS attached UE is not successfully authenticated in the old MME and/or the Context Request cannot be validated, the old MME continues the procedure with sending a Context Response and starting the existing timer. If the new MME supports CIoT EPS Optimisation, CIoT EPS Optimisation support indication is included in the Context Request indicating support for various CIoT EPS Optimisations (e.g. support for header compression for CP CIoT EPS Optimisation, etc.). 5. If the Context Request is sent to an old MME the old MME responds with a Context Response (IMSI, ME Identity (IMEISV), unused EPS Authentication Vectors, KSIASME, KASME, EPS Bearer Context(s), Serving GW signalling Address and TEID(s), MS Info Change Reporting Action (if available), CSG Information Reporting Action (if available), UE Time Zone, UE Core Network Capability, UE Specific DRX Parameters, Change to Report (if present), Remaining Running Service Gap timer, LTE-M UE Indication) message. If the new MME supports CIoT EPS Optimisation and the use of header compression has been negotiated between the UE and old MME, the Context Response also includes the Header Compression Configuration which includes the information necessary for the ROHC channel setup but not the RoHC context itself. If the Context Request is sent to an old S4 SGSN the old S4 SGSN responds with a Context Response (IMSI, ME Identity (if available), unused Authentication Quintets, CK, IK, KSISGSN, EPS Bearer Context(s), Serving GW signalling Address and TEID(s), ISR Supported, MS Info Change Reporting Action (if available), CSG Information Reporting Action (if available), UE Time Zone, UE Core Network Capability, UE Specific DRX Parameters, Change to Report (if present)) message. The Authentication Quintets are maintained by the old S4 SGSN. TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [41] gives further details on the transfer of security related information. Change to Report flag is included by the old MME or the old S4 SGSN if reporting of change of UE Time Zone, or Serving Network, or both towards Serving GW / PDN GW was deferred by the old MME or old S4 SGSN. If the Context Response message did not include IMEISV and the MME does not already store the IMEISV of the UE, the MME shall retrieve the ME Identity (IMEISV) from the UE. The PDN GW Address and TEID(s) (for GTP-based S5/S8) or GRE Keys (PMIP-based S5/S8 at the PDN GW(s) for uplink traffic and the TI(s), is part of the EPS Bearer Context. ISR Supported is indicated if the old SGSN and associated Serving GW are capable to activate ISR for the UE. The new MME shall ignore the UE Core Network Capability contained in the Context Response only when it has previously received an UE Core Network Capability in the Tracking Area Update Request. If the UE is not known in the old MME/old S4 SGSN or if the integrity check for the TAU request message fails, the old MME/old S4 SGSN responds with an appropriate error cause. If the DL Data Buffer Expiration Time for the UE has not expired (see High latency communication in clause 4.3.17.7), the old MME/old S4-SGSN indicates Buffered DL Data Waiting in the Context Response. When this is indicated, the new MME shall setup the user plane in conjunction to the TAU procedure for delivery of the buffered DL data. If the UE receives emergency bearer services from the old MME/old S4 SGSN and the UE is UICCless, IMSI can not be included in the Context Response. For emergency attached UEs, if the IMSI cannot be authenticated, then the IMSI shall be marked as unauthenticated. Also, in this case, security parameters are included only if available. For a RLOS attached UE, the old MME includes an RLOS indication to the new MME. If the RLOS attached UE in the old MME does not have a USIM, IMSI can not be included in the Context Response. If the RLOS attached UE has USIM but the IMSI cannot be successfully authenticated, then the IMSI shall be marked as unauthenticated. Also, in this case, security parameters are included only if available. If SIPTO at the Local Network is active for a PDN connection in the architecture with stand-alone GW, the old MME/old S4 SGSN shall include the Local Home Network ID of the old cell in the EPS Bearer context corresponding to the SIPTO at the Local Network PDN connection. For UE using CIoT EPS Optimisation without any activated PDN connection, there is no EPS Bearer Context(s) included in the Context Response message. Based on the CIoT EPS Optimisation support indication, old MME only transfers the EPS Bearer Context(s) that the new MME supports. If the new MME does not support CIoT EPS Optimisation, EPS Bearer Context(s) of non-IP PDN connection are not transferred to the new MME. If the new MME does not support Ethernet PDN Type, EPS Bearer Context(s) of Ethernet PDN type are not transferred to the new MME. If the EPS Bearer Context(s) of a PDN connection has not been transferred, the old MME shall consider all bearers of that PDN connection as failed and release that PDN connection by triggering the MME requested PDN disconnection procedure specified in clause 5.10.3. The buffered data in the old MME is discarded after receipt of Context Acknowledgement. If the EPS Bearer Context(s) are to be transferred to the new MME, the old MME also includes the Serving GW IP address and TEID for both S1-U and S11-U, if available. If the Old MME is aware the UE is a LTE-M UE, it provides the LTE-M UE Indication to the new MME. 6. If the integrity check of TAU Request message (sent in step 2) failed, then authentication is mandatory. The authentication functions are defined in clause 5.3.10 on "Security Function". Ciphering procedures are described in clause 5.3.10 on "Security Function". If GUTI allocation is going to be done and the network supports ciphering, the NAS messages shall be ciphered. If this TAU request is received for a UE which is already in ECM_CONNECTED state and the PLMN-ID of the TAI sent by the eNodeB in Step 3 is different from that of the GUTI included in the TAU Request message, the MME shall delay authenticating the UE until after Step 21 (TAU Complete message). NOTE 4: The MME delays the authentication such that the UE first updates its registered PLMN-ID to the new PLMN-ID selected by the RAN during handover. The new PLMN-ID is provided by the MME to the UE as part of the GUTI in the TAU accept message in Step 20. Doing this ensures that the same PLMN-ID is used in the derivation of the Kasme key by both the network and the UE. If the new MME is configured to allow emergency bearer services for unauthenticated UE the new MME behave as follows: - where a UE has only emergency bearer services, the MME either skip the authentication and security procedure or accepts that the authentication may fail and continues the Tracking Area Update procedure; or - where a UE has both emergency and non-emergency bearer services and authentication fails, the MME continues the Tracking Area Update procedure and deactivates all the non-emergency PDN connections as specified in clause 5.10.3. If the new MME is configured to support Restricted Local Operator Services, the new MME, based on local regulation and operator policy, may skip the authentication and security procedure, or may perform authentication if security parameters are available or obtainable from HSS and continues the Tracking Area Update procedure regardless of the authentication result. If the UE indicated it has a UE Radio Capability ID assigned for use in the selected PLMN in step 2, the MME may request the UE to provide the UE Radio Capability ID in Security Mode Command, if the MME needs to get the UE Radio Capability ID from the UE e.g. at inter-PLMN mobility. If enquired by the MME the UE shall include the UE Radio Capability ID in Security Mode Command Accept for the supported UE radio capabilities. 7. If the old node is an old MME the new MME sends a Context Acknowledge message to the old MME. The old MME marks in its context that the information in the GW and the HSS are invalid. This ensures that the MME updates the GWs and the HSS if the UE initiates a TAU procedure back to the MME before completing the ongoing TAU procedure. NOTE 5: Updating the GWs refers to modification of session(s) on the Serving GW. This will result in successful re-establishment of the S11/S4 tunnel between the MME/SGSN and the Serving GW. If the old node is an old S4 SGSN the MME sends a Context Acknowledge (ISR Activated) message to the old SGSN. Unless ISR Activated is indicated by the MME, the old S4 SGSN marks in its context that the information in the GWs is invalid. This ensures that the old S4 SGSN updates the GWs if the UE initiates a RAU procedure back to the old S4 SGSN before completing the ongoing TAU procedure. If ISR Activated is indicated to the old S4 SGSN, this indicates that the old S4 SGSN shall maintain its UE context including authentication quintets and stop the timer started in step 4. In this case, if the Implicit Detach timer is running, the old S4 SGSN shall re-start it with a slightly larger value than the UE's GERAN/UTRAN Deactivate ISR timer. Also, in this case, if the old SGSN has maintained the Serving GW address for user plane and S4 GTP-U TEID, the old SGSN shall remove Serving GW address for user plane and S4 GTP-U TEID locally. When ISR Activated is not indicated and this timer expires the old SGSN deletes all bearer resources of that UE. As the Context Acknowledge from the MME does not include any S-GW change the S4 SGSN does not send any Delete Session Request message to the S-GW. The MME shall not activate ISR if the associated Serving GW does not support ISR. If the security functions do not authenticate the UE correctly, then the TAU shall be rejected, and the MME shall send a reject indication to the old MME/old S4 SGSN. The old MME/old S4 SGSN shall continue as if the Identification and Context Request was never received. For UE using CIoT EPS Optimisation without any activated PDN connection, the steps 9, 10, 11, 12 and 13 are skipped. 8. Void. 9. If the MME has changed the new MME adopts the bearer contexts received from the old MME/SGSN as the UE's EPS bearer contexts to be maintained by the new MME. The MME establishes the EPS bearer(s) in the indicated order. The MME deactivates the EPS bearers which cannot be established. The MME verifies the EPS bearer status received from the UE with the EPS bearer contexts it maintains and releases any network resources related to EPS bearers that are not active in the UE. If there is no bearer context at all, the MME rejects the TAU Request. If the MME has changed the new MME sends a Modify Bearer Request (new MME address and TEID, ISR Activated, RAT type, LTE-M RAT type reporting to PGW flag) message per PDN connection to the Serving GW. If there is no need for the SGW to send the signalling to the PDN GW, the MME may send Modify Access Bearers Request (new MME address and TEID) per UE to the Serving GW to optimise the signalling. The PDN GW address is indicated in the bearer contexts. If indicated, the information ISR Activated indicates that ISR is activated. If it is a mobility from a SGSN to a MME and if the MME supports location information change reporting, the MME shall include the User Location Information (according to the supported granularity) in the Modify Bearer Request, regardless of whether location information change reporting had been requested in the previous RAT by the PDN GW. If it is an inter MME mobility and if the PDN GW requested location information change reporting, the MME includes the User Location Information IE in this message if it is different compared to the previously sent information. If the PDN GW requested User CSG information, the MME also includes the User CSG Information IE in this message. If either the UE Time Zone has changed or Context Response message indicated pending UE Time Zone change reporting (via Change to Report flag), the MME includes the UE Time Zone IE in this message. If either the Serving Network has changed or Context Response message indicated pending Serving Network change reporting (via Change to Report flag) the MME includes the new Serving Network IE in this message. In network sharing scenarios Serving Network denotes the serving core network. If the old node is an old MME at a Tracking Area Update with a MME change ISR Activated shall not be indicated. NOTE 6: The User CSG Information IE is only sent in step 9 if the "Active flag" is set in the TAU Request message. When the Modify Access Bearers Request or Modify Bearer Request does not indicate ISR Activated the S-GW deletes any ISR resources by sending a Delete Bearer Request to the other CN node that has bearer resources on the S-GW reserved. If the new MME receives the EPS bearer context with SCEF, then the new MME updates the SCEF as defined in TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [74]. For Control Plane CIoT EPS Optimisation, if the DL data is buffered in the Serving GW, and if this is a Tracking Area Update without MME change and the DL Data Buffer Expiration Time in the MM context for the UE in the MME has not expired, or if this is a Tracking Area Update with MME change and the old MME/old S4-SGSN indicated Buffered DL Data Waiting in the Context Response in step 5, the MME shall also indicate S11-U tunnelling of NAS user data and include its own S11-U IP address and MME DL TEID for DL data forwarding by the SGW in the Modify Bearer Request. The MME may also do so without DL data buffered in the SGW. If the UE is using the LTE-M RAT type and the PDN GW expects the LTE-M RAT type reporting as specified in clause 5.11.5, the MME also includes the LTE-M RAT type reporting to PGW flag to indicate to the Serving GW to forward the LTE-M RAT type to the PDN GW. 10. If the RAT type has changed, or the Serving GW has received the User Location Information IE or the UE Time Zone IE or User CSG Information IE and/or the Serving Network IE from the MME in step 9, the Serving GW informs the PDN GW(s) about this information that e.g. can be used for charging, by sending the message Modify Bearer Request (RAT type) per PDN connection to the PDN GW(s) concerned. User Location Information IE and/or UE Time Zone IE and/or User CSG Information IE and/or Serving Network IE are also included if they are present in step 9. 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 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 LTE-M RAT type and the LTE-M RAT type reporting to PGW flag were received at step 9, the Serving GW shall include the LTE-M RAT type in the Modify Bearer Request message to the PGW. Otherwise the Serving GW includes RAT type WB-E-UTRAN. 11. If dynamic PCC is deployed, and RAT type information or UE location information needs to be conveyed from the PDN GW to the PCRF, then the PDN GW shall send this information to the PCRF by means of an IP-CAN Session Modification procedure as defined in TS 23.203[ Policy and charging control architecture ] [6]. NOTE 7: The PDN GW does not need to wait for the PCRF response, but continues in the next step. If the PCRF response leads to an EPS bearer modification the PDN GW should initiate a bearer update procedure. 12. The PDN GW updates its context field to allow DL PDUs to be routed to the correct Serving GW. PDN GW returns a Modify Bearer Response (MSISDN) to the Serving GW. The MSISDN is included if the PDN GW has it stored in its UE context. If there has been a RAT change towards E-UTRAN and location information change reporting is required and supported in the target MME, the PDN GW shall provide MS Info Change Reporting Action in the Modify Bearer Response. 13. The Serving GW updates its bearer context. If ISR Activated is indicated in step 9 and RAT Type received in step 9 indicates E-UTRAN, then the Serving GW only updates the MME Control Plane Address stored locally and keep the SGSN related information unchanged. Also, in this case, if the Serving GW has maintained the SGSN address for user plane and S4 GTP-U TEID, the Serving GW removes the SGSN address for user plane and S4 GTP-U TEID locally. Otherwise the Serving GW shall update all of the information stored locally for this UE with the related information received from the MME. This allows the Serving GW to route Bearer PDUs to the PDN GW when received from eNodeB. The Serving GW shall return a Modify Bearer Response (Serving GW address and TEID for uplink traffic, MS Info Change Reporting Action) message to the new 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 Modify Bearer Request message per PDN connection. When the MME receives the Modify Bearer Response or the Modify Access Bearers Response message, the MME checks if there is a "Availability after DDN Failure" monitoring event or a "UE Reachability" monitoring event configured for the UE in the MME and in such a case sends an event notification (see TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [74] for further information). For Control Plane CIoT EPS Optimisation, if the MME address and MME DL TEID are provided in step 9, the Serving GW includes Serving GW address and Serving GW UL TEID in the Modify Bearer Response message. The DL data is sent to the MME from the Serving GW. The buffered DL data is sent to the UE as described in steps 12-14 of clause 5.3.4B.3. 14. The new MME verifies whether it holds subscription data for the UE identified by the GUTI, the additional GUTI or by the IMSI received with the context data from the old CN node. If there are no subscription data in the new MME for this UE, or for some network sharing scenario (e.g. GWCN) if the PLMN-ID of the TAI supplied by the eNodeB is different from that of the GUTI in the UE's context, then the new MME informs the HSS of the change of MME by sending an Update Location Request (MME Id, IMSI, ULR-Flags, MME Capabilities, Homogenous Support of IMS Voice over PS Sessions, UE SRVCC capability, equivalent PLMN list, ME Identity (IMEISV)) message to the HSS. ULR-Flags indicates that update location is sent from an MME and the MME registration shall be updated in HSS. The HSS does not cancel any SGSN registration. The MME capabilities indicate the MME's support for regional access restrictions functionality. The inclusion of the equivalent PLMN list indicates that the MME supports the inter-PLMN handover to a CSG cell in an equivalent PLMN using the subscription information of the target PLMN. The "Homogenous Support of IMS Voice over PS Sessions" indication (see clause 4.3.5.8A) shall not be included unless the MME has completed its evaluation of the support of "IMS Voice over PS Session" as specified in clause 4.3.5.8. The ME Identity is included if step 5 caused the MME to retrieve the IMEISV from the UE. NOTE 8: At this step, the MME may not have all the information needed to determine the setting of the IMS voice over PS Session Supported indication for this UE (see clause 4.3.5.8). Hence the MME can send the "Homogenous Support of IMS Voice over PS Sessions" later on in this procedure. If the UE initiates the TAU procedure in a VPLMN supporting Autonomous CSG Roaming and the HPLMN has enabled Autonomous CSG Roaming in the VPLMN (via Service Level Agreement) and the MME needs to retrieve the CSG subscription information of the UE from the CSS, the MME initiates the Update CSG Location Procedure with CSS as described in clause 5.3.12. If the MME determines that only the UE SRVCC capability has changed, the MME sends a Notify Request to the HSS to inform about the changed UE SRVCC capability. If all the EPS bearers of the UE have emergency ARP value, the new MME may skip the update location procedure or proceed even if the update location fails. If the UE is RLOS attached, the new MME skips the update location procedure and the TAU procedure proceeds. 15. The HSS sends a Cancel Location (IMSI, Cancellation type) message to the old MME with a Cancellation Type set to Update Procedure. 16. When receiving a Cancel Location message and the timer started in step 4 is not running, the old MME removes the MM and bearer contexts. Otherwise, the contexts are removed when the timer expires. It also ensures that the MM context is kept in the old MME for the case the UE initiates another TAU procedure before completing the ongoing TAU procedure to the new MME. The old MME acknowledges with a Cancel Location Ack (IMSI) message. NOTE 9: ISR Activated is never indicated from new to old MME. So an old MME deletes all the bearer resources of the UE in any case when the timer started in step 4 expires, which is independent on receiving a Cancel Location message. 17. When receiving the Context Acknowledge message and if the UE is Iu Connected, the old SGSN sends an Iu Release Command message to the RNC after the timer started in step 4 has expired. 18. The RNC responds with an Iu Release Complete message. 19. The HSS acknowledges the Update Location Request by returning an Update Location Ack (IMSI, Subscription Data) message to the new MME after the cancelling of the old MME context is finished. If all checks are successful, the MME constructs an MM context for the UE. The Subscription Data may contain the CSG subscription data for the registered PLMN and for the equivalent PLMN list requested by MME in step 14. The subscription data may contain Enhanced Coverage Restricted parameter. If received from the HSS, MME stores this Enhanced Coverage Restricted parameter in the MME MM context. The subscription data may contain Service Gap Time. If received from the HSS, the MME stores this Service Gap Time in the MME MM context for the UE and passes it to the UE in the Tracking Area Update Accept message if the UE has indicated Service Gap Control capability. The subscription data may contain Subscribed Paging Time Window parameter that applies to the UEs on a specific RAT, e.g. NB-IoT. If received from the HSS, MME stores this Subscribed Paging Time Window parameter in the MME MM context. If the UE initiates the TAU procedure at a CSG cell, the new MME shall check whether the CSG ID and associated PLMN is contained in the CSG subscription and is not expired. If the CSG ID and associated PLMN is not present or expired, the MME shall send a Tracking Area Update reject message to the UE with an appropriate cause value. The UE shall remove the CSG ID and associated PLMN from its Allowed CSG list if present. If the Update Location is rejected by the HSS, the new MME rejects the TAU Request from the UE with an appropriate cause sent in the TAU Reject message to the UE. In such cases, the new MME releases any local MME EPS Bearer contexts for this particular UE. 20. If due to regional subscription restrictions or access restrictions (e.g. CSG restrictions) (received in update location procedure in step 19) the UE is not allowed to access the TA: - The MME rejects the Tracking Area Update Request with an appropriate cause to the UE. - For UEs with emergency EPS bearers, i.e. at least one EPS bearer has an ARP value reserved for emergency services, the new MME accepts the Tracking Area Update Request and deactivates all non-emergency PDN connections as specified in clause 5.10.3. If the Tracking Area Update procedure is initiated in ECM-IDLE state, all non-emergency EPS bearers are deactivated by the Tracking Area Update procedure without bearer deactivation signalling between the UE and the MME. If the TAU 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 Paging Restriction Information from the UE in the UE context and then enforces it in the Network Triggered Service Request procedure as described in clause 5.3.4.3. The MME informs the UE about the acceptance/rejection of the requested Paging Restriction Information in the TAU Accept message. If the TAU Request message does not include any Paging Restriction Information, the MME shall delete any stored Paging Restriction Information for this UE and stop restricting paging accordingly. If the TAU Request message includes a Release Request indication, the MME does not activate the user plane setup procedure in the subsequent steps and triggers the S1 release procedure as described in clause 5.3.5 after the completion of TAU procedure. The MME responds to the UE with a Tracking Area Update Accept (GUTI, TAI-list, EPS bearer status, NAS sequence number, NAS-MAC, ISR Activated, IMS Voice over PS session supported, Emergency Service Support indicator, LCS Support Indication, Supported Network Behaviour, Service Gap Time, Enhanced Coverage Restricted, Indication of support of 15 EPS bearers per UE, PLMN-assigned UE Radio Capability ID, Accepted IMSI Offset, Paging Restriction Information acceptance/rejection, Enhanced Discontinuous Coverage Support, Return To Coverage Notification Not Required, Unavailability Period Duration, the Start of Unavailability Period, Maximum Time Offset) message. If the active flag is set the Handover Restriction List may be sent to eNodeB as eNodeB handles the roaming restrictions and access restrictions in the Intra E-UTRAN case. If the active flag is set in the TAU Request message the user plane setup procedure is activated in conjunction with the TAU Accept message. If this is a Tracking Area Update without MME change and the DL Data Buffer Expiration Time in the MM context for the UE in the MME has not expired, or if this is a Tracking Area Update with MME change and the old MME/old S4-SGSN indicated Buffered DL Data Waiting in the Context Response in step 5, the user plane setup procedure is activated even if the MME did not receive the active flag in the TAU Request message. If the new MME receives the Downlink Data Notification message or any downlink signalling message while the UE is still connected, the user plane setup procedure may be activated even if the new MME did not receive the active flag in the TAU Request message. The procedure 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]. The message sequence should be the same as for the UE triggered Service Request procedure specified in clause 5.3.4.1 from the step when MME establish the bearers(s). The EPS bearer status indicates the active bearers in the network. The UE removes any internal resources related to bearers not marked active in the received EPS bearer status. If the EPS bearer status information was in the TAU Request, the MME shall indicate the EPS bearer status to the UE. If ISR Activated is indicated to the UE, this indicates that its P-TMSI and RAI shall remain registered with the network and shall remain valid in the UE. At a Tracking Area Update with an MME change ISR Activated shall not be indicated. At a Tracking Area Update without an MME change, if ISR is activated for the UE when the MME receives the Tracking Area Update Request, the MME should maintain ISR by indicating ISR Activated in the Tracking Area Update Accept message. Handover Restriction List is described in clause 4.3.5.7 "Mobility Restrictions". The MME sets the IMS Voice over PS session supported as described in clause 4.3.5.8. For UE using CIoT EPS Optimisation without any activated PDN connection, there is no EPS bearer status included in the TAU Accept message. The MME indicates the CIoT EPS Optimisations it supports and prefers in the Supported Network Behaviour information as defined in clause 4.3.5.10. If there is a Service Gap timer running for the UE in the MME, the MME shall ignore the active flag and signalling active flag and not perform any of the actions related to these flags except if the TAU Request message has been received when the UE has a PDN connection for emergency bearer services established or is establishing a PDN connection for emergency bearer services or if the UE is configured to use high priority access (AC 11-15) in selected PLMN. The MME shall include the Service Gap Time in the TAU Accept message if the UE has indicated Service Gap Control capability and either if Service Gap Time was received in step 19 from HSS in the subscription information or if the Service Gap Time in the subscription information has been updated by HSS User Profile management (i.e. the Insert Subscriber Data procedure in clause 5.3.9.2). If the UE included support for restriction of use of Enhanced Coverage in step 1, the MME sends Enhanced Coverage Restricted parameter to the eNodeB in the S1-AP message as defined in clause 4.3.28. The MME also sends the Enhanced Coverage Restricted parameter to the UE in the TAU Accept message. UE shall store Enhanced Coverage Restricted parameter and shall use the value of Enhanced Coverage Restricted parameter to determine if enhanced coverage feature should be used or not. If the MME successfully obtained Header Compression Configuration parameters in step 5 it indicates he continued use of previous negotiated configuration to the UE in the Header Compression Context Status for each EPS Bearer of the UE. When Header Compression Context Status indicates that the previous negotiated configuration can no longer be used for some EPS bearers, the UE shall stop performing header compression and decompression when sending or receiving data using Control Plane CIoT EPS Optimisation on these EPS bearers. The MME checks if there is a "Availability after DDN Failure" monitoring event or a "UE Reachability" monitoring event configured for the UE in the MME for which an event notification has not yet been sent. In such a case an event notification is sent (see TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [74] for further information). If the MME did not receive the Voice support match indicator in the MM Context, then the MME may send a UE Radio Capability Match Request to the eNodeB as described in clause 5.3.14. If the MME hasn't received Voice support match indicator from the eNodeB then based on implementation MME may set IMS Voice over PS session supported Indication and update it at a later stage. After step 14, and in parallel to any of the preceding steps, the MME shall send a Notify Request (Homogeneous Support of IMS Voice over PS Sessions) message to the HSS: - If the MME has evaluated the support of IMS Voice over PS Sessions, see clause 4.3.5.8, and - If the MME determines that it needs to update the Homogeneous Support of IMS Voice over PS Sessions, see clause 4.3.5.8A. The Emergency Service Support indicator informs the UE that Emergency bearer services are supported. LCS Support Indication indicates whether the network supports the EPC-MO-LR and/or CS-MO-LR as described in TS 23.271[ Functional stage 2 description of Location Services (LCS) ] [57]. Indication for support of 15 EPS bearers per UE indicates the network supports 15 EPS bearers as defined in clause 4.12. When receiving the TAU Accept message and there is no ISR Activated indication the UE shall set its TIN to "GUTI". When ISR Activated is indicated and the UE's TIN indicates "GUTI" the UE's TIN shall not be changed. When ISR Activated is indicated and the TIN is "P-TMSI" or "RAT-related TMSI" the UE shall set its TIN to "RAT-related TMSI". For an MME change ISR is not activated by the new MME to avoid context transfer procedures with two old CN nodes. For an emergency attached UE, emergency ISR is not activated. If the TAU procedure is initiated by manual CSG selection and occurs via a CSG cell, the UE upon receiving TAU Accept message shall add the CSG ID and associated PLMN to its Allowed CSG list if it is not already present. Manual CSG selection is not supported if the UE has emergency bearers established. If the UE included extended idle mode DRX parameters information element, the MME includes extended idle mode DRX parameters information element in the TAU accept if it decides to enable extended idle mode DRX with Paging Time Window length assigned considering Subscribed Paging Time Window (if available) and the local policy. Additionally, for a UE using an eNodeB that provides discontinuous coverage (e.g. for satellite access with discontinuous coverage), the MME may consider Unavailability Period Duration and/or Start of Unavailability Period as described in clause 4.13.8.2 when determining extended idle mode DRX parameters. If the user plane setup is performed in conjunction with the TAU Accept message and the TAU is performed via a hybrid cell, then the MME shall send an indication whether the UE is a CSG member to the RAN along with the S1-MME control message. Based on this information, the RAN may perform differentiated treatment for CSG and non-CSG members. NOTE 10: If the UE receives a TAU Accept message via a hybrid cell, the UE does not add the corresponding CSG ID and associated PLMN to its Allowed CSG list. Adding a CSG ID and associated PLMN to the UE's local Allowed CSG list for a hybrid cell is performed only by OTA or OMA DM procedures. If the UE receives a Service Gap Time in the TAU Accept message, the UE shall store this parameter and apply Service Gap Control (see clause 4.3.17.9). If the UE has indicated support for dual connectivity with NR in the TAU Request and the UE is not allowed to use NR as Secondary RAT, the MME indicates that to the UE in the TAU Accept message. If the user plane setup is performed and 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. When the UE supports RACS, and the MME needs to configure the UE with a UE Radio Capability ID, and the MME already has the UE radio capabilities for the UE, the MME may provide the UE with the UE Radio Capability ID for the UE radio capabilities the UCMF returns to the MME for this UE. If the UE had included a UE Specific DRX parameter for NB-IoT in the Tracking Area Update Request, the MME includes the Accepted NB-IoT DRX parameter. If the UE provided a Requested IMSI Offset in step 2, but the network prefers a different value, the MME provides the UE with an Accepted IMSI Offset different from the one provided in step 2. Otherwise the value of the Accepted IMSI Offset the MME sends is the value of the Requested IMSI Offset sent by the UE in step 2. The MME stores the value of the alternative IMSI derived (see clause 4.3.33) from the Accepted IMSI Offset provided to the UE in the UE context. If a Multi-USIM UE does not provide a Requested IMSI Offset in step 1, the MME erases any alternative IMSI value in the UE context. NOTE 11: The MME does not remove IMSI Offset value if the Tracking Area Update Request is for periodic Tracking Area Update. If the Multi-USIM UE has indicated one or more Multi-USIM specific Capabilities are supported in the UE Core Network Capability in step 2, the MME shall indicate whether the corresponding one or more Multi-USIM specific features described in clause 4.3.33 are supported based on network capability and preference by the network (based on local network policy) by providing one or more of the Connection Release Supported, Paging Cause Indication for Voice Service Supported, Reject Paging Request Supported, Paging Restriction Supported and Paging Timing Collision Control Supported indications. The MME shall only indicate Paging Restriction Supported together with either Connection Release Supported or Reject Paging Request Supported. The UE shall only use Multi-USIM specific features that the MME indicated as being supported. In case of Emergency attached UE, the MME shall not indicate support for any Multi-USIM feature to the UE. If both UE and network support discontinuous coverage, the MME provides the Enhanced Discontinuous Coverage Support indication as described in clause 4.13.8.1. For a UE using a eNodeB that provides discontinuous coverage (e.g. for satellite access with discontinuous coverage), the MME may provide Return To Coverage Notification Not Required, which requests the UE in ECM_IDLE state to not perform the TAU procedure when it returns to coverage, and/or provide the UE with an Unavailability Period Duration and/or Start of Unavailability Period if available, as described in clause 4.13.8.2. The MME may also provide a Maximum Time Offset as described in clause 4.13.8.6. 21. If the GUTI was changed, or the MME indicates an Accepted IMSI Offset to the UE in step 20, the UE acknowledges the new GUTI or the Accepted IMSI Offset value by returning a Tracking Area Update Complete message to the MME. When the "Active flag" is not set in the TAU Request message and the Tracking Area Update was not initiated in ECM-CONNECTED state, the MME releases the signalling connection with UE, according to clause 5.3.5. For a UE using Control Plane CIoT EPS Optimisation, when the "Signalling active flag" is set, the new MME shall not release the NAS signalling connection with the UE immediately after the TAU procedure is completed. NOTE 12: The new MME may initiate E-RAB establishment (see TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36]) after execution of the security functions, or wait until completion of the TA update procedure. For the UE, E-RAB establishment may occur any time after the TA update request is sent. In the case of a rejected tracking area update operation, due to regional subscription, roaming restrictions, or access restrictions (see TS 23.221[ Architectural requirements ] [27] and TS 23.008[ Organization of subscriber data ] [28]) the new MME should not construct an MM context for the UE. In the case of receiving the subscriber data from HSS, the new MME may construct an MM context and store the subscriber data for the UE to optimise signalling between the MME and the HSS. A reject shall be returned to the UE with an appropriate cause and the S1 connection shall be released. Upon return to idle, the UE shall act according to TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [10]. If the new MME is unable to update the bearer context in one or more P-GWs, the new MME shall deactivate the corresponding bearer contexts as described in clause "MME Initiated Dedicated Bearer Deactivation Procedure". This shall not cause the MME to reject the tracking area update. The new MME shall determine the Maximum APN restriction based on the received APN Restriction of each bearer context in the Context Response message and then store the new Maximum APN restriction value. The bearer contexts shall be prioritized by the new MME. If the new MME is unable to support the same number of active bearer contexts as received from old MME/SGSN, the prioritisation is used to decide which bearer contexts to maintain active and which ones to delete. In any case, the new MME shall first update all contexts in one or more P-GWs and then deactivate the context(s) that it cannot maintain as described in clause "MME Initiated Dedicated Bearer Deactivation Procedure". This shall not cause the MME to reject the tracking area update. The new MME shall not deactivate emergency service related EPS bearers, i.e. EPS bearers with ARP value reserved for emergency services. NOTE 13: If MS (UE) was in PMM-CONNECTED state the bearer contexts are sent already in the Forward Relocation Request message as described in clause "Serving RNS relocation procedures" of TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7]. If the tracking area update procedure fails a maximum allowable number of times, or if the MME returns a Tracking Area Update Reject (Cause) message, the UE shall enter EMM DEREGISTERED state. If the new MME identifies that the RAT type has changed, the MME checks the subscription information to identify for each APN whether to maintain the PDN connection, disconnect the PDN connection with a reactivation request, or, disconnect the PDN connection without reactivation request. If the MME decides to deactivate a PDN connection it performs MME-initiated PDN Connection Deactivation procedure after the tracking area update procedure is completed but before the S1/RRC interface connection is released. Existing ESM cause values as specified in TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [46] (e.g. #39, "reactivation requested"; #66 "Requested APN not supported in current RAT and PLMN combination"; and for a dedicated bearer, possibly #37 "EPS QoS not accepted") are used to cause predictable UE behaviour. If all the PDN connections are disconnected and the UE does not support "attach without PDN connectivity", the MME shall request the UE to detach and reattach. | 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.3.2 |
2,531 | 5.37.5 PDU Set based Handling 5.37.5.1 General | A PDU Set is comprised of one or more PDUs carrying an application layer payload such as a video frame or video slice. The PDU Set based QoS handling by the NG-RAN is determined by PDU Set QoS Parameters in the QoS profile of the QoS Flow (specified in clause 5.7.7) and PDU Set information provided by the PSA UPF via N3/N9 interface as described in clause 5.37.5.2. The PDU Set based QoS Handling can be applied for GBR and non-GBR QoS Flows. The AF should provide PDU Set related assistance information for dynamic PCC control. One or more of the following PDU Set related assistance information may be provided to the NEF/PCF using the AF session with required QoS procedures in clauses 4.15.6.6 and 4.15.6.6a of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. - PDU Set QoS Parameters as described in clause 5.7.7 - Protocol Description: Indicates the transport protocol used by the service data flow (e.g. RTP, SRTP) and information, e.g. the following: - RTP [185] or SRTP [186]; - RTP or SRTP with RTP Header Extensions, including: - RTP Header Extensions for PDU Set Marking as defined in TS 26.522[ 5G Real-time Media Transport Protocol Configurations ] [179]; - Other RTP Header Extensions as defined RFC 8285 [189]; - RTP or SRTP without RTP Header Extensions, but together with RTP Payload Format (e.g. H.264 [187] or H.265 [188]); - RTP or SRTP with RTP Header Extensions for PDU Set Marking as defined in TS 26.522[ 5G Real-time Media Transport Protocol Configurations ] [179], and together with RTP Payload Format (e.g. H.264 [187] or H.265 [188]); - RTP or SRTP with other RTP Header Extensions following RFC 8285 [189], and together with RTP Payload Format (e.g. H.264 [187] or H.265 [188]). When RTP Header Extensions for PDU Set Marking (as defined in TS 26.522[ 5G Real-time Media Transport Protocol Configurations ] [179] or other RTP header extensions as defined in RFC 8285 [189] is included, the differentiation between different RTP Header Extension Types should be supported. When RTP Payload Format is included, the differentiation between different RTP Payload Formats should be supported. NOTE 1: Multiplexing of different transport protocols and different media traffic for differentiated PDU Set QoS handling is not supported in the current Release. AF provided PDU Set QoS Parameters and Protocol Description may be used in determining the PCC Rule by the PCF as defined in clause 6.1.3.27.4 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45] and the Protocol Description may be used for identifying the PDU Set information by the PSA UPF. When the SMF receives the PCC rule, the SMF performs binding of the PCC rule to one QoS Flow as described in clause 6.1.3.2.4 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. If the PCC rule contains one or more PDU Set QoS Parameters (PSER, PSDB and PSIHI), the SMF adds these PDU Set QoS parameters to the QoS Profile of the QoS Flow as described in clause 6.2.2.4 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. Alternatively, the SMF may be configured to support PDU Set based QoS Handling without receiving PCC rules from a PCF. For the downlink direction, the PSA UPF identifies PDUs that belong to PDU Sets and marks them accordingly as described in clause 5.37.5.2. If the PSA UPF receives a PDU that does not belong to a PDU Set based on Protocol Description for PDU Set identification, then the PSA UPF still maps it to a PDU Set and determines the PDU Set Information as described in clause 5.37.5.2. NOTE 2: If the PSA UPF receives a PDU that does not belong to a PDU Set, then it is assumed that the UPF determines the PDU Set Importance value based on pre-configuration. For the uplink direction, the UE may identify PDU Sets, and how this is done is left up to UE implementation. The SMF may send Protocol Description associated with the QoS rule to UE. NOTE 3: Using the Protocol Description or not is left to UE implementation. The use of Protocol Description does not impact QoS Flow Mapping in the UE. In this Release, the PDU Set based QoS handling is supported in 5GS for UE registered in 3GPP access for single access PDU Session with IP PDU Session Type. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.37.5 |
2,532 | 10.5.5.2 Attach type | The purpose of the attach type information element is to indicate the type of the requested attach, i.e. whether the MS wants to perform a GPRS or combined GPRS attach. The attach type is a type 1 information element. The attach type information element is coded as shown in figure 10.5.117b/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.135b/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.117b/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Attach type information element Table 10.5.135b/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Attach type information element | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.5.2 |
2,533 | 8 Subscription checking | The subscription of an MS/UE is checked by the PLMN during IP-CAN session establishment procedure as described in 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [3], 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [77] and 3GPP TS 23.402[ Architecture enhancements for non-3GPP accesses ] [78]. The GGSN/P-GW implicitly checks its internal context related to the destination address for each mobile terminated packet. For PDN types other than Non-IP, if there is a context IP-CAN session associated with the IP address the packet shall be forwarded towards the MS/UE; otherwise the packet shall be discarded or rejected depending on the implemented protocol. For PDN type "Non-IP", the packet shall be forwarded towards the MS/UE, discarded or rejected depending on the implemented protocol. | 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 | 8 |
2,534 | 5.7.3.2 Resource Type | The resource type determines if dedicated network resources related to a QoS Flow-level Guaranteed Flow Bit Rate (GFBR) value are permanently allocated (e.g. by an admission control function in a radio base station). GBR QoS Flows are therefore typically authorized "on demand" which requires dynamic policy and charging control. A GBR QoS Flow uses either the GBR resource type or the Delay-critical GBR resource type. The definition of PDB and PER are different for GBR and Delay-critical GBR resource types, and the MDBV parameter applies only to the Delay-critical GBR resource type. A Non-GBR QoS Flow may be pre-authorized through static policy and charging control. A Non-GBR QoS Flow uses only the Non-GBR resource type. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.7.3.2 |
2,535 | 5.2.5.4 HARQ | Asynchronous Incremental Redundancy Hybrid ARQ is supported. The gNB provides the UE with the HARQ-ACK feedback timing either dynamically in the DCI or semi-statically in an RRC configuration. Retransmission of HARQ-ACK feedback is supported by using enhanced dynamic codebook and/or one-shot triggering of HARQ-ACK transmission for (i) all configured CCs and HARQ processes in the PUCCH group, (ii) a configured subset of CCs and/or HARQ processes in the PUCCH group, or (iii) a dynamically indicated HARQ-ACK feedback instance. For HARQ-ACK of SPS PDSCH without associated PDCCH, in case of HARQ-ACK dropping due to TDD specific collisions, the HARQ-ACK feedback can be deferred to a next available PUCCH transmission occasion. The UE may be configured to receive code block group based transmissions where retransmissions may be scheduled to carry a sub-set of all the code blocks of a TB. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.2.5.4 |
2,536 | 28.3.2.2.9 Prefixed Tracking Area Identity based N3IWF FQDN | The Prefixed Tracking Area Identity based N3IWF FQDN, used by a UE that is configured with Slice-specific N3IWF prefix configuration, shall be constructed as specified for the Tracking Area Identity based N3IWF FQDN in clause 28.3.2.2.3, with the addition of <Prefix> before the TAC. The <Prefix> is provided in the Slice-specific N3IWF prefix configuration for the selected PLMN that contains S-NSSAIs that match all (or most, in case there is no full match) of the S-NSSAIs that the UE is going to include in the Requested NSSAI in the subsequent Registration procedure, and is specified in 3GPP TS 24.526[ User Equipment (UE) policies for 5G System (5GS); Stage 3 ] [144]. There are two Prefixed Tracking Area Identity based N3IWF FQDNs defined: one based on a TAI with a 2 octet TAC and a 5GS one based on a 3 octet TAC. 1) The Prefixed Tracking Area Identity based N3IWF FQDN using a 2 octet TAC shall be constructed respectively as: "<Prefix>.tac-lb<TAC-low-byte>.tac-hb<TAC-high-byte>.tac.n3iwf.5gc.mnc<MNC>.mcc<MCC>.pub.3gppnetwork.org" The syntax and semantics of <TAC-high-byte>, <TAC-low-byte>, <MNC>, and <MCC> are specified in clause 28.3.2.2.3. As an example, the Prefixed Tracking Area Identity based N3IWF FQDN for the TAC H'0B21, MCC 345, MNC 12, and an example <Prefix> value "ssn3iwfprefix-Y" is coded in the DNS as: "ssn3iwfprefix-Y.tac-lb21.tac-hb0b.tac.n3iwf.5gc.mnc012.mcc345.pub.3gppnetwork.org" 2) The 5GS Prefixed Tracking Area Identity based N3IWF FQDN using a 3 octet TAC shall be constructed respectively as: "<Prefix>.tac-lb<TAC-low-byte>.tac-mb<TAC-middle-byte>.tac-hb<TAC-high-byte>.5gstac.n3iwf.5gc.mnc<MNC>.mcc<MCC>.pub.3gppnetwork.org" The syntax and semantics of <TAC-high-byte>, <TAC-middle-byte>, <TAC-low-byte>, <MNC>, and <MCC> are specified in clause 28.3.2.2.3. As an example, the 5GS Prefixed Tracking Area Identity based N3IWF FQDN for the 5GS TAC H'0B1A21, MCC 345, MNC 12, and an example <Prefix> value "ssn3iwfprefix-Y" is coded in the DNS as: "ssn3iwfprefix-Y.tac-lb21.tac-mb1a.tac-hb0b.5gstac.n3iwf.5gc.mnc012.mcc345.pub.3gppnetwork.org" | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 28.3.2.2.9 |
2,537 | – UECapabilityEnquirySidelink | The UECapabilityEnquirySidelink message is used to request UE sidelink capabilities. It is only applied to unicast of NR sidelink communication. Signalling radio bearer: SL-SRB3 RLC-SAP: AM Logical channel: SCCH Direction: UE to UE UECapabilityEnquirySidelink message -- ASN1START -- TAG-UECAPABILITYENQUIRYSIDELINK-START UECapabilityEnquirySidelink ::= SEQUENCE { rrc-TransactionIdentifier-r16 RRC-TransactionIdentifier, criticalExtensions CHOICE { ueCapabilityEnquirySidelink-r16 UECapabilityEnquirySidelink-r16-IEs, criticalExtensionsFuture SEQUENCE {} } } UECapabilityEnquirySidelink-r16-IEs ::= SEQUENCE { frequencyBandListFilterSidelink-r16 FreqBandList OPTIONAL, -- Need N ue-CapabilityInformationSidelink-r16 OCTET STRING OPTIONAL, -- Need N lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE{} OPTIONAL } -- TAG-UECAPABILITYENQUIRYSIDELINK-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,538 | 5.3.5.3 Wireline access service area restrictions | If: a) a SERVICE REJECT message with the 5GMM cause #28 "Restricted service area"; b) a DL NAS TRANSPORT message with the Payload container type IE set to "N1 SM information" and the 5GMM cause #28 "Restricted service area"; or c) a REGISTRATION ACCEPT message includes the PDU session reactivation result error cause IE with the 5GMM cause #28 "Restricted service area"; is received over wireline access then the 5G-RG or the W-AGF acting on behalf of the FN-CRG (or on behalf of the N5GC device) shall start enforcing the wireline access service area restrictions and shall enter the state 5GMM-REGISTERED.NON-ALLOWED-SERVICE. While in the state 5GMM-REGISTERED.NON-ALLOWED-SERVICE, the 5G-RG or the W-AGF acting on behalf of the FN-CRG (or on behalf of the N5GC device) shall: a) if in 5GMM-IDLE mode over wireline access: 1) shall not perform the registration procedure for mobility and periodic registration update with Uplink data status IE except for emergency services or for high priority access; and 2) shall not initiate a service request procedure except for: - emergency services, - emergency services fallback; or - high priority access; and b) if in 5GMM-CONNECTED mode over wireline access: 1) shall not perform the registration procedure for mobility and periodic registration update with Uplink data status IE except for: - emergency services; - emergency services fallback; or - high priority access; 2) shall not initiate a service request procedure except for emergency services, or high priority access; and 3) shall not initiate a 5GSM procedure except for emergency services or high priority access; over the wireline access. When the 5G-RG is switched off, the UICC containing the USIM is removed or the 5G-RG starts using another wireline access network, the 5G-RG shall stop enforcing the wireline access service area restrictions, if enforced. NOTE: When the 5G-RG acting on behalf of the AUN3 device determines that the AUN3 device is switched off or the UICC containing the USIM of AUN3 device is removed, the 5G-RG acting on behalf of the AUN3 device stops enforcing the wireline access service area restrictions, if enforced. When the W-AGF acting on behalf of the FN-CRG determines that the FN-CRG is switched off, the W-AGF acting on behalf of the FN-CRG stops enforcing the wireline access service area restrictions, if enforced. When the W-AGF acting on behalf of the N5GC device determines that the FN-CRG serving the N5GC device is switched off, the W-AGF acting on behalf of the N5GC device stops enforcing the wireline access service area restrictions, if enforced. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.3.5.3 |
2,539 | I.2 Causes related to invalid messages | Cause value = 81 Invalid transaction identifier value. See annex H, subclause H.5.1. Cause value = 95 Semantically incorrect message. See annex H, subclause H.5.5. Cause value = 96 Invalid mandatory information. See annex H, subclause H.6.1. Cause value = 97 Message type non-existent or not implemented. See annex H, subclause H.6.2. Cause value = 98 Message type not compatible with protocol state. See annex H, subclause H.6.3. Cause value = 99 Information element non-existent or not implemented. See annex H, subclause H.6.4. Cause value = 100 Conditional IE error. See annex H, subclause H.6.5. Cause value = 101 Message not compatible with protocol state. See annex H, subclause H.6.6. Cause value = 111 Protocol error, unspecified. See annex H, subclause H.6.8. | 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 | I.2 |
2,540 | 4.11.3 Handling multiple tracking area codes from the lower layers | When a UE camps on a satellite E-UTRAN cell, the UE may receive multiple TACs from the lower layers. The UE shall construct TAIs from the multiple TACs (i.e. concatenate the identity of the current PLMN and each of the TACs) and select a TAI as follows: a) if at least one TAI belongs to the TAI list of the UE, the UE shall select a TAI which belongs to the TAI list. If there are multiple TAIs which belong to the TAI list the UE shall consider each of these TAIs equal and: - if the UE can determine a TAI which represents the best the tracking area of the UE's geographical location, the UE shall select a TAI which represents the best the tracking area of the UE's geographical location; and - otherwise, the UE shall select a TAI in an implementation-specific way. b) if no TAI belongs to the TAI list of the UE and: 1) there is a TAI which belongs to neither the list of "forbidden tracking areas for roaming" nor the list of "forbidden tracking areas for regional provision of service", the UE shall select a TAI which belongs to neither the list of "forbidden tracking areas for roaming" nor the list of "forbidden tracking areas for regional provision of service". In this case, if there are multiple TAIs which belong to neither the list of "forbidden tracking areas for roaming" nor the list of "forbidden tracking areas for regional provision of service", then the UE shall consider each of these TAIs equal and: - if the UE can determine a TAI which represents the best the tracking area of the UE's geographical location, the UE shall select a TAI which represents the best the tracking area of the UE's geographical location; and - otherwise, the UE shall select a TAI in an implementation-specific way. 2) all TAIs belong to the list of "forbidden tracking areas for roaming" or the list of "forbidden tracking areas for regional provision of service", then the UE shall consider each of these TAIs equal and: - if the UE can determine a TAI which represents the best the tracking area of the UE's geographical location, the UE shall select a TAI which represents the best the tracking area of the UE's geographical location; and - otherwise, the UE shall select a TAI in an implementation-specific way. The UE shall consider the selected TAI as the current TAI. The UE shall select a TAI as described above when: a) the UE receives multiple TACs from the lower layers; or b) the UE has received multiple TACs from the lower layers upon starting to camping on the current cell and the TAI list, the list of "forbidden tracking areas for roaming", or the list of "forbidden tracking areas for regional provision of service" is updated. Handling of the list of "forbidden tracking areas for roaming" and the list of "forbidden tracking areas for regional provision of service" is specified in clause 5.3.2. | 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.11.3 |
2,541 | 4.4.7 MSISDN-less MO SMS Service | MSISDN-less MO SMS via T4 is subscription based. The subscription provides the information whether a UE is allowed to originate MSISDN-less MO SMS. The UE is pre-configured with the Service Centre address that points to SMS-SC that performs this MO SMS delivery via NEF delivery procedure. The recipient of this short message is set to the pre-configured address of the AF (i.e. Address of the destination SME). If UE has multiple GPSIs associated to the same IMSI, the GPSI that is associated with an SMS may be determined from the UE's IMSI and the Application Port ID value in the TP-User-Data field (see TS 23.040[ Technical realization of the Short Message Service (SMS) ] [5]). The NEF may obtain the GPSI by querying the UDM with the IMSI and application port ID. UE is aware whether the MO SMS delivery status (success or fail) based on the SMS delivery report from SMS-SC. The network does not perform any storing and forwarding functionality for MO SMS. See clause 5.2.6 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] for a description of NEF Services and Service Operations. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.4.7 |
2,542 | 14.5 Temporary identities | The Temporary identities (Pseudonyms and re-authentication identities) shall take the form of a NAI username as specified in clause 2.1 of the IETF RFC 4282 [53]. Temporary identity shall be generated as specified in clause 6.4.1 of 3GPP TS 33.234[ 3G security; Wireless Local Area Network (WLAN) interworking security ] [55]. This part of the temporary identity shall follow the UTF-8 transformation format specified in IETF RFC 2279 [54] except for the following reserved hexadecimal octet value: FF. When the temporary identity username is coded with FF, this reserved value is used to indicate the special case when no valid temporary identity exists in the WLAN UE (see 3GPP TS 24.234[ 3GPP system to Wireless Local Area Network (WLAN) interworking; WLAN User Equipment (WLAN UE) to network protocols; Stage 3 ] [48]). The network shall not allocate a temporary identity with the whole username coded with the reserved hexadecimal value FF. For EAP-AKA authentication, the username portion of the pseudonym identity shall be prepended with the single digit "2" and the username portion of the fast re-authentication identity shall be prepended with the single digit "4" as specified in clause 4.1.1.7 of IETF RFC 4187 [50]. For EAP-SIM authentication, the username portion of the pseudonym identity shall be prepended with the single digit "3" and the username portion of the fast re-authentication identity shall be prepended with the single digit "5" as specified in clause 4.2.1.7 of IETF RFC 4186 [51]. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 14.5 |
2,543 | 4.16.14.2.2 Management of access and mobility related policy information at SM Policy Association establishment and termination with the notification sent by the BSF | Figure 4.16.14.2.2-1: Management of access and mobility related policy information at SM Policy Association establishment and termination with the notification by the BSF 1. The AMF establishes an AM Policy Association for retrieving access and mobility related policy information, e.g. RFSP index value, as described in clause 4.16.1.2. 2. If the access and mobility related policy information depend on the SM Policy Association establishment and termination for a DNN, S-NSSAI combination, then depending on operator policies in the PCF, the PCF may subscribe to BSF and then step 3 follows, or the PCF may provide its PCF binding information to the AMF with the indication to be notified about the PCF for the PDU Session for a DNN, S-NSSAI and then step 4 follows. 3. The PCF for the UE determines that access and mobility related policy information (e.g. RFSP index value) depend on the detection of SM Policy Association establishment associated with the (DNN, S-NSSAI) combinations configured in the PCF or retrieved from the UDR as part of the Application Data Set. The PCF for the UE then subscribes to the BSF to be notified when a PCF for the PDU Session is registered for the first SM Policy Association establishment and the PCF for the PDU Session is deregistered for the last SM Policy Association termination to the same (DNN, S-NSSAI) combination in the BSF, by invoking Nbsf_Management_Subscribe (SUPI, list of (DNN, S-NSSAI)(s), indication of registration/deregistration per (DNN, S-NSSAI)). 4. The SMF establishes a SM Policy Association as described in clause 4.16.4. The allocated UE address/prefix, SUPI, DNN, S-NSSAI and the PCF address are registered in the BSF, as described in clause 6.1.1.2.2 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. 5. If the PCF for the UE subscribed to BSF, then the BSF notifies a PCF registration when the first SM Policy Association corresponding to the (DNN, S-NSSAI) combination is established, by invoking Nbsf_Management_Notify (DNN, S-NSSAI, notification of registration). 6. The PCF checks operator policies and then may change access and mobility related policy information (e.g. RFSP index value) based on the reporting of SM Policy Association establishment. 7. The SM Policy Association is terminated as described in clause 4.16.6 and the allocated UE address/prefix, SUPI, DNN, S-NSSAI and the PCF address are deregistered in the BSF. 8. If the PCF for the UE subscribed to BSF, then BSF notifies of a PCF deregistration when the last SM Policy Association corresponding to the (DNN, S-NSSAI) combination is terminated, by invoking Nbsf_Management_Notify (DNN, S-NSSAI, notification of deregistration). | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.16.14.2.2 |
2,544 | D.1 Mapping of NAS procedure to RRC establishment cause (S1 mode only) | When EMM requests the establishment of a NAS-signalling connection, or when EMM requests the lower layers to resume a NAS signalling connection, the RRC establishment cause used by the UE shall be selected according to the NAS procedure as specified in table D.1.1. The EMM shall also indicate to the lower layer for the purpose of access control, the call type associated with the RRC establishment cause as specified in table D.1.1. If the UE is configured for EAB (see the "ExtendedAccessBarring" leaf of NAS configuration MO 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]), the EMM shall indicate to the lower layer for the purpose of access control that EAB applies for this request except for the following cases: - the UE is a UE configured to use AC11 – 15 in selected PLMN; - the UE is answering to paging; - the RRC Establishment cause is set to "Emergency call"; - the UE is configured to allow overriding EAB (see the "Override_ExtendedAccessBarring" leaf of the NAS configuration MO as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]) and receives an indication from the upper layers to override EAB; or - the UE is configured to allow overriding EAB (see the "Override_ExtendedAccessBarring" leaf of the NAS configuration MO as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]) and already has a PDN connection that was established with EAB override. Table D.1.1: Mapping of NAS procedure to establishment cause and call type NOTE: The RRC establishment cause can be used by the network to prioritise the connection establishment request from the UE at high load situations in the network. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | D.1 |
2,545 | 4.4.4.2 UL PDCP SDU loss rate | This measurement provides the fraction of IP packets (PDCP SDUs) which are lost (not successfully received) on the uplink. Only user-plane traffic (DTCH) and only PDCP SDUs that have entered PDCP (and given a PDCP sequence number) are considered. The measurement is split into subcounters per E-RAB QoS level (QCI). The packets transmitted between the eNodeB and UEs and the packets transmitted between E-UTRAN and RN are counted seperately. The measurement is also applicable to RNs. SI This measurement is obtained according to the definition in 3GPP TS 36.314[ Evolved Universal Terrestrial Radio Access (E-UTRA); Layer 2 - Measurements ] [11]. Separate counters are maintained for each QCI. In case only a subset of per QCI measurements is supported, a loss rate subcounter calculated across all QCIs will be provided first. Each measurement is an integer value representing the loss rate multiplied by 1E6. The number of measurements is equal to the number of QCIs plus a possible sum value identified by the .sum suffix. The measurement name has the form DRB.PdcpSduLossRateUl.QCII, which indicates the UL PDCP SDU loss rate between the eNodeB (or RN) and UE DRB.PdcpSduLossRateUlRN.QCI, which indicates the UL PDCP SDU loss rate between the E-UTRAN and RN. where QCI identifies the target E-RAB level quality of service class. EUtranCellFDD EUtranCellTDD Valid for packet switched traffic EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.4.4.2 |
2,546 | 17.5.1 Service activation | The multicast MBMS bearer service activation procedure registers the user in the network to enable the reception of data from a specific multicast MBMS bearer service Figure 26; Activation of an MBMS multicast service 1. The GGSN receives an IGMP (IPv4) or MLD (IPv6) Join message from a UE, over the default PDP context to signal its interest in receiving a particular multicast MBMS bearer service identified by an IP multicast address. 2. The GGSN sends an AAR seeking authorization for the activating UE to receive data from a particular service. 3. The authorization decision is provided in the AAA together with the APN to be used for creation of the MBMS UE context. If the AAA indicates that the UE is not authorized to receive the MBMS data the process terminates with no additional message exchange. 4. The GGSN sends an MBMS Notification Request (IP multicast address, APN, Linked NSAPI) to the SGSN. Linked NSAPI is set equal to the NSAPI of the PDP context over which the Join request was received. The IP multicast address is the one requested by the UE in the Join request. The APN may be different from the APN to which the default PDP context has been activated. In any case, the APN may resolve to a GGSN that is different from the GGSN receiving the IGMP/MLD Join request. The GGSN starts a MBMS Activation Timer as GGSN may receive no response, e.g. in case SGSN or UE does not support MBMS. 5. The SGSN sends a MBMS Notification Response (Cause) to the GGSN that sent the MBMS Notification Request, where Cause shall indicate successful or unsuccessful MBMS context activation for the reason of SGSN or UE . Upon reception of the response message with Cause indicating unsuccessful operation or time-out of the MBMS Activation Timer in the GGSN, the GGSN may fallback to IP multicast access as defined in clause 11.7. 6. The SGSN creates an MBMS UE context and sends a Create MBMS Context Requests (IP multicast address, APN, RAI) to the GGSN. That GGSN may be different from the GGSN receiving the IGMP/MLD Join request. 7. The GGSN sends an AAR seeking authorization for the activating UE. 8. The authorization decision is provided in the AAA 9. If the GGSN does not have the MBMS Bearer Context information for this MBMS bearer service, i.e. the GGSN was not yet registered, the GGSN sends a AAR to the BM-SC. See subclause 17.5.4 "Registration Procedure". If no TMGI has been allocated for this MBMS bearer service, the BM-SC will allocate a new TMGI. This TMGI will be passed to GGSN via the AAA message. 10. The BM-SC responds with a AAA containing the MBMS Bearer Context information for this MBMS bearer service and adds the identifier of the GGSN to the "list of downstream nodes" parameter in its MBMS Bearer Context. See subclause 17.5.4 "Registration Procedure". 11. The GGSN creates an MBMS UE context and sends a Create MBMS Context Response to the SGSN | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 17.5.1 |
2,547 | 6.4.1.4 UE-requested PDU session establishment procedure not accepted by the network 6.4.1.4.1 General | If the connectivity with the requested DN is rejected by the network, the SMF shall create a PDU SESSION ESTABLISHMENT REJECT message. The SMF shall set the 5GSM cause IE of the PDU SESSION ESTABLISHMENT REJECT message to indicate the reason for rejecting the PDU session establishment. The 5GSM cause IE typically indicates one of the following SM cause values: #8 operator determined barring; #26 insufficient resources; #27 missing or unknown DNN; #28 unknown PDU session type; #29 user authentication or authorization failed; #31 request rejected, unspecified; #32 service option not supported; #33 requested service option not subscribed; #35 PTI already in use; #38 network failure; #39 reactivation requested; #46 out of LADN service area; #50 PDU session type IPv4 only allowed; #51 PDU session type IPv6 only allowed; #54 PDU session does not exist; #57: PDU session type IPv4v6 only allowed; #58: PDU session type Unstructured only allowed; #61: PDU session type Ethernet only allowed; #67 insufficient resources for specific slice and DNN; #68 not supported SSC mode; #69 insufficient resources for specific slice; #70 missing or unknown DNN in a slice; #82 maximum data rate per UE for user-plane integrity protection is too low; #86 UAS services not allowed; or #95 – 111 protocol errors. If the PDU SESSION ESTABLISHMENT REQUEST message includes a PDU session type IE set to "IPv6", and the subscription, the SMF configuration, or both, are limited to IPv4 only for the requested DNN, the SMF shall include the 5GSM cause value #50 "PDU session type IPv4 only allowed" in the 5GSM cause IE of the PDU SESSION ESTABLISHMENT REJECT message. If the PDU SESSION ESTABLISHMENT REQUEST message includes a PDU session type IE set to "IPv6", and the subscription, the SMF configuration, or both, support none of "IPv4" and "IPv6" PDU session types for the requested DNN, the SMF shall include the 5GSM cause value #28 "unknown PDU session type" in the 5GSM cause IE of the PDU SESSION ESTABLISHMENT REJECT message. If the PDU SESSION ESTABLISHMENT REQUEST message includes a PDU session type IE set to "IPv4", and the subscription, the SMF configuration, or both, are limited to IPv6 only for the requested DNN, the SMF shall include the 5GSM cause value #51 "PDU session type IPv6 only allowed" in the 5GSM cause IE of the PDU SESSION ESTABLISHMENT REJECT message. If the PDU SESSION ESTABLISHMENT REQUEST message includes a PDU session type IE set to "IPv4", and the subscription, the SMF configuration, or both, support none of "IPv4" and "IPv6" PDU session types for the requested DNN, the SMF shall include the 5GSM cause value #28 "unknown PDU session type" in the 5GSM cause IE of the PDU SESSION ESTABLISHMENT REJECT message. If the PDU SESSION ESTABLISHMENT REQUEST message includes a PDU session type IE set to "IPv4v6", and the subscription, the SMF configuration, or both, support none of "IPv4v6", "IPv4" and "IPv6" PDU session types for the requested DNN, the SMF shall include the 5GSM cause value #28 "unknown PDU session type" in the 5GSM cause IE of the PDU SESSION ESTABLISHMENT REJECT message. If the PDU SESSION ESTABLISHMENT REQUEST message includes a PDU session type IE set to "Unstructured" or "Ethernet", and the subscription, the SMF configuration, or both, do not support the PDU session type for the requested DNN, the SMF shall include the 5GSM cause value #28 "unknown PDU session type" in the 5GSM cause IE of the PDU SESSION ESTABLISHMENT REJECT message. If the PDU SESSION ESTABLISHMENT REQUEST message is to establish an MA PDU session and includes a PDU session type IE set to "Unstructured", and the SMF configuration does not support the PDU session type, the SMF shall include the 5GSM cause value #28 "unknown PDU session type" in the 5GSM cause IE of the PDU SESSION ESTABLISHMENT REJECT message. If the PDU SESSION ESTABLISHMENT REQUEST message contains the SSC mode IE indicating an SSC mode not supported by the subscription, the SMF configuration, or both of them, and the SMF decides to rejects the PDU session establishment, the SMF shall include the 5GSM cause value #68 "not supported SSC mode" in the 5GSM cause IE and the SSC modes allowed by SMF in the Allowed SSC mode IE of the PDU SESSION ESTABLISHMENT REJECT message. If the PDU SESSION ESTABLISHMENT REQUEST message is to establish an MA PDU session and MA PDU session is not allowed due to operator policy and subscription, and the SMF decides to reject the PDU session establishment, the SMF shall include the 5GSM cause value #33 "requested service option not subscribed" in the 5GSM cause IE of the PDU SESSION ESTABLISHMENT REJECT message. If the PDU SESSION ESTABLISHMENT REQUEST message is identified to be for C2 communication and: a) does not include the Service-level-AA container IE with the service-level device ID set to the CAA-level UAV ID; b) does not include the Service-level-AA container IE with the service-level-AA payload and the Service-level-AA payload type; or c) the SMF is informed by the UAS-NF that the UAS service is not allowed, the SMF shall reject the PDU SESSION ESTABLISHMENT REQUEST message by transmitting a PDU SESSION ESTABLISHMENT REJECT message with 5GSM cause IE set to 5GSM cause value #86 "UAS services not allowed". In 3GPP access, if the operator's configuration requires user-plane integrity protection for the PDU session and, the maximum data rate per UE for user-plane integrity protection supported by the UE for uplink or the maximum data rate per UE for user-plane integrity protection supported by the UE for downlink, or both, are lower than required by the operator's configuration, the SMF shall include the 5GSM cause value #82 "maximum data rate per UE for user-plane integrity protection is too low" in the 5GSM cause IE of the PDU SESSION ESTABLISHMENT REJECT message. If the UE requests a PDU session establishment for an LADN when the UE is located outside of the LADN service area, the SMF shall include the 5GSM cause value #46 "out of LADN service area" in the 5GSM cause IE of the PDU SESSION ESTABLISHMENT REJECT message. If the DN authentication of the UE was performed with the PDU session authentication and authorization procedure and completed unsuccessfully, the SMF shall include the 5GSM cause value #29 "user authentication or authorization failed" in the 5GSM cause IE of the PDU SESSION ESTABLISHMENT REJECT message and shall set the EAP message IE of the PDU SESSION ESTABLISHMENT REJECT message to an EAP-failure message as specified in IETF RFC 3748 [34], provided by the DN. If the DN authentication of the UE was performed with the service-level authentication and authorization procedure and completed unsuccessfully, the SMF shall include the 5GSM cause value #29 "user authentication or authorization failed" in the 5GSM cause IE of the PDU SESSION ESTABLISHMENT REJECT message and shall include the service-level-AA response provided by DN in the Service-level-AA container IE of the PDU SESSION ESTABLISHMENT REJECT message. Based on the local policy and user's subscription data, if a PDU session is being established with the request type set to "existing PDU session" and the SMF determines the UE has: a) moved between a tracking area in NB-N1 mode and a tracking area in WB-N1 mode; b) moved between a tracking area in NB-S1 mode and a tracking area in WB-N1 mode; or c) moved between a tracking area in WB-S1 mode and a tracking area in NB-N1 mode, the SMF may reject the PDU SESSION ESTABLISHMENT REQUEST message and: a) include the 5GSM cause value #39 "reactivation requested" in the 5GSM cause IE of the PDU SESSION ESTABLISHMENT REJECT message; or b) include a 5GSM cause value other than #39 "reactivation requested" in the 5GSM cause IE of the PDU SESSION ESTABLISHMENT REJECT message. NOTE 1: The included 5GSM cause value is up to the network implementation. If the PDU session cannot be established due to resource unavailability in the UPF, the SMF shall include the 5GSM cause value #26 "insufficient resources" in the 5GSM cause IE of the PDU SESSION ESTABLISHMENT REJECT message. Based on the user's subscription data and the operator policy, if the SMF determines that the UUAA-SM procedure needs to be performed for a UE but the SMF does not receives the service-level device ID set to the CAA-level UAV ID in the Service-level-AA container IE of the PDU SESSION ESTABLISHMENT REQUEST message from the UE, the SMF shall include the 5GSM cause value #86 "UAS services not allowed" in the 5GSM cause IE of the PDU SESSION ESTABLISHMENT REJECT message. The network may include a Back-off timer value IE in the PDU SESSION ESTABLISHMENT REJECT message. If the 5GSM cause value is #26 "insufficient resources", #67 "insufficient resources for specific slice and DNN", or #69 "insufficient resources for specific slice" and the PDU SESSION ESTABLISHMENT REQUEST message was received from a UE configured for high priority access in selected PLMN or SNPN or the request type provided during the PDU session establishment is set to "initial emergency request" or "existing emergency PDU session", the network shall not include a Back-off timer value IE. If the 5GSM cause value is #29 "user authentication or authorization failed ", the network should include a Back-off timer value IE. If the Back-off timer value IE is included and the 5GSM cause value is different from #26 "insufficient resources", #28 "unknown PDU session type", #46 "out of LADN service area", #50 "PDU session type IPv4 only allowed", #51 "PDU session type IPv6 only allowed", #54 "PDU session does not exist", #57 "PDU session type IPv4v6 only allowed", #58 "PDU session type Unstructured only allowed", #61 "PDU session type Ethernet only allowed", #67 "insufficient resources for specific slice and DNN", #68 "not supported SSC mode", and #69 "insufficient resources for specific slice", the network may include the Re-attempt indicator IE to indicate whether the UE is allowed to attempt a PDN connectivity procedure in the PLMN for the same DNN in S1 mode, whether another attempt in S1 mode or in N1 mode is allowed in an equivalent PLMN or whether another attempt in N1 mode is allowed in an equivalent SNPN. If the 5GSM cause value is #50 "PDU session type IPv4 only allowed", #51 "PDU session type IPv6 only allowed", #57 "PDU session type IPv4v6 only allowed", #58 "PDU session type Unstructured only allowed", or #61 "PDU session type Ethernet only allowed", the network may include the Re-attempt indicator IE without Back-off timer value IE to indicate whether the UE is allowed to attempt a PDU session establishment procedure in an equivalent PLMN or equivalent SNPN in N1 mode using the same PDU session type for the same DNN (or no DNN, if no DNN was indicated by the UE) and the same S-NSSAI (or no S-NSSAI, if no S-NSSAI was indicated by the UE). The SMF shall send the PDU SESSION ESTABLISHMENT REJECT message. Upon receipt of a PDU SESSION ESTABLISHMENT REJECT message and a PDU session ID, using the NAS transport procedure as specified in subclause 5.4.5, the UE shall stop timer T3580 shall release the allocated PTI value and shall consider that the PDU session was not established. If the PDU SESSION ESTABLISHMENT REQUEST message was sent with request type set to "initial emergency request" or "existing emergency PDU session" and the UE receives a PDU SESSION ESTABLISHMENT REJECT message, then the UE may: a) inform the upper layers of the failure of the procedure; or NOTE 2: This can result in the upper layers requesting another emergency call attempt using domain selection as specified in 3GPP TS 23.167[ IP Multimedia Subsystem (IMS) emergency sessions ] [6]. b) de-register locally, if not de-registered already, attempt initial registration for emergency services. If the PDU SESSION ESTABLISHMENT REJECT message includes 5GSM cause #39 "reactivation requested" and the PDU session is being transferred from EPS to 5GS and established with the request type set to "existing PDU session", the UE should re-initiate the UE-requested PDU session establishment procedure as specified in subclause 6.4.1 for: a) the PDU session type associated with the transferred PDU session; b) the SSC mode associated with the transferred PDU session; c) the DNN associated with the transferred PDU session; and d) the S-NSSAI associated with (if available in roaming scenarios) a mapped S-NSSAI if provided in the UE-requested PDU session establishment procedure of the transferred PDU session. If the PDU SESSION ESTABLISHMENT REJECT message includes 5GSM cause #86 "UAS services not allowed" and the UE has not included the service-level device ID in the Service-level-AA container IE of the PDU SESSION ESTABLISHMENT REQUEST message and set the value to the CAA-level UAV ID: a) the UE shall not send another PDU SESSION ESTABLISHMENT REQUEST message for UAS services without including the CAA-level UAV ID in the service-level device ID of the Service-level-AA container IE; and b) upon receipt of the request from the upper layers to establish a PDU session for UAS services, the UE shall initiate the UE-requested PDU session establishment procedure by including the service-level device ID in the Service-level-AA container IE of the PDU SESSION ESTABLISHMENT REQUEST message and set the value to the CAA-level UAV ID as specified in subclause 6.4.1.2. If the 5GSM cause value is different from #26 "insufficient resources", #28 "unknown PDU session type", #39 "reactivation requested", #46 "out of LADN service area", #50 "PDU session type IPv4 only allowed", #51 "PDU session type IPv6 only allowed", #54 "PDU session does not exist", #57 "PDU session type IPv4v6 only allowed", #58 "PDU session type Unstructured only allowed", #61 "PDU session type Ethernet only allowed", #67 "insufficient resources for specific slice and DNN", #68 "not supported SSC mode", and #69 "insufficient resources for specific slice", #86 "UAS services not allowed", and #33 "requested service option not subscribed" and the PDU SESSION ESTABLISHMENT REQUEST message was received from a UE configured for high priority access in selected PLMN, the network shall not include a Back-off timer value IE. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.4.1.4 |
2,548 | 5.14.1.3.1 Logical channel prioritization | The Logical Channel Prioritization procedure is applied when a new transmission is performed. Each sidelink logical channel has an associated priority which is the PPPP and optionally an associated PPPR. Multiple sidelink logical channels may have the same associated priority. The mapping between priority and LCID is left for UE implementation. If duplication is activated as specified in TS 36.323[ Evolved Universal Terrestrial Radio Access (E-UTRA); Packet Data Convergence Protocol (PDCP) specification ] [4], the MAC entity shall map different sidelink logical channels which correspond to the same PDCP entity onto different carriers in accordance with clause 5.14.1.5, or onto different carriers of different carrier sets (if configured in allowedCarrierFreqList for the corresponding destination). For a given sidelink logical channel, it is up to UE implementation which carrier set to select among the carrier sets configured in allowedCarrierFreqList (if configured) for the corresponding destination. The MAC entity shall perform the following Logical Channel Prioritization procedure either for each SCI transmitted in an SC period in sidelink communication, or for each SCI corresponding to a new transmission in V2X sidelink communication: - The MAC entity shall allocate resources to the sidelink logical channels in the following steps: - Only consider sidelink logical channels not previously selected for this SC period and the SC periods (if any) which are overlapping with this SC period, to have data available for transmission in sidelink communication; - Only consider sidelink logical channels which meet the following conditions: - allowed on the carrier where the SCI is transmitted for V2X sidelink communication, if the carrier is configured by upper layers according to TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8] and TS 24.386[ User Equipment (UE) to V2X control function; protocol aspects; Stage 3 ] [15]; - having a priority whose associated threshCBR-FreqReselection is no lower than the CBR of the carrier when the carrier is (re-)selected in accordance with 5.14.1.5; - Only consider one sidelink logical channel among sidelink logical channels corresponding to same PDCP entity, if duplication is activated as specified in TS 36.323[ Evolved Universal Terrestrial Radio Access (E-UTRA); Packet Data Convergence Protocol (PDCP) specification ] [4]. - Step 0: Select a ProSe Destination, having the sidelink logical channel with the highest priority, among the sidelink logical channels having data available for transmission and having the same transmission format as the one selected corresponding to the ProSe Destination; NOTE: The sidelink logical channels belonging to the same ProSe Destination have the same transmission format. - For each MAC PDU associated to the SCI: - Step 1: Among the sidelink logical channels belonging to the selected ProSe Destination and having data available for transmission, allocate resources to the sidelink logical channel with the highest priority; - Step 2: if any resources remain, sidelink logical channels belonging to the selected ProSe Destination are served in decreasing order of priority until either the data for the sidelink logical channel(s) or the SL grant is exhausted, whichever comes first. Sidelink logical channels configured with equal priority should be served equally. - The UE shall also follow the rules below during the scheduling procedures above: - the UE should not segment an RLC SDU (or partially transmitted SDU) if the whole SDU (or partially transmitted SDU) fits into the remaining resources; - if the UE segments an RLC SDU from the sidelink logical channel, it shall maximize the size of the segment to fill the grant as much as possible; - the UE should maximise the transmission of data; - if the MAC entity is given a sidelink grant size that is equal to or larger than 10 bytes (for sidelink communication) or 11 bytes (for V2X sidelink communication) while having data available for transmission, the MAC entity shall not transmit only padding. | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.14.1.3.1 |
2,549 | 5.32.3 Policy for ATSSS Control | If dynamic PCC is to be used for the MA PDU Session, the PCF may take ATSSS policy decisions and create PCC rules that contain MA PDU Session Control information, (as specified in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]), which determines how the uplink and the downlink traffic of the MA PDU Session should be distributed across the 3GPP and non-3GPP accesses. If dynamic PCC is not deployed, local policy in SMF is used. The SMF receives the PCC rules with MA PDU Session Control information and maps these rules into (a) ATSSS rules, which are sent to the UE, and (b) N4 rules, which are sent to the UPF. The ATSSS rules are provided as a prioritized list of rules (see clause 5.32.8), which are applied by the UE to enforce the ATSSS policy in the uplink direction and the N4 Rules are applied by the UPF to enforce the ATSSS policy in the downlink direction. The ATSSS rules are sent to UE with a NAS message when the MA PDU Session is created or updated by the SMF, e.g. after receiving updated/new PCC rules from the PCF. Similarly, the N4 rules are sent to UPF when the MA PDU Session is created or updated by the SMF. The details of the policy control related to ATSSS are specified in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.32.3 |
2,550 | Annex F (normative): Use and structure of the I-RNTI | The I-RNTI provides an NG-RAN node with a reference to the UE context and a reference to the NG-RAN node that allocated the UE context. To support an NG-RAN node in resolving the Local NG-RAN ID of the NG-RAN node that allocated the UE context, the I-RNTI structure is as follows: - the first part (starting from the MSB of the I-RNTI) identifies the I-RNTI profile. It is 2 bits long for a Full I-RNTI or 1 bit long for a short I-RNTI, and it indicates the length of a Local NG-RAN Node Identifier of the NG-RAN Node that allocated the I-RNTI; - the second part, immediately following the first part, is a Local NG-RAN Node Identifier; - the third part, immediately following the second part, identifies the UE context stored in the NG-RAN node that allocated the I-RNTI. In case a NG-RAN node takes an additional Local NG-RAN Node identifier into use or removes a Local NG-RAN Node identifier currently in use it informs its neighbour NG-RAN nodes about this change. The I-RNTI profiles for Full I-RNTI are described in table F-1. Table F-1: I-RNTI profiles for Full I-RNTI The I-RNTI profiles for Short I-RNTI are described in table F-2. Table F-2: I-RNTI profiles for Short I-RNTI | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | Annex |
2,551 | 6.5.1 UE requested PDN connectivity procedure 6.5.1.1 General | The purpose of the UE requested PDN connectivity procedure is for a UE to request the setup of a default EPS bearer to a PDN. The UE requests connectivity to a PDN by sending a PDN CONNECTIVITY REQUEST message to the network. If accepted by the network, this procedure initiates the establishment of a default EPS bearer context. If EMM-REGISTERED without PDN connection is not supported by the UE or the MME, the procedure is used either to establish the first default bearer by including the PDN CONNECTIVITY REQUEST message into the initial attach message, or to establish subsequent default bearers to additional PDNs in order to allow the UE simultaneous access to multiple PDNs by sending the message stand-alone. If EMM-REGISTERED without PDN connection is supported by the UE and the MME, the procedure is used to establish the first or subsequent default bearers to a PDN or additional PDNs by sending the PDN CONNECTIVITY REQUEST message stand-alone. If the UE requests PDN connectivity for emergency bearer services, the MME shall not check for regional restrictions or subscription restrictions when processing the PDN CONNECTIVITY REQUEST message. If there is already a PDN connection for emergency bearer services established, the UE shall not request an additional PDN connection for emergency bearer services. A UE attached for emergency bearer services shall not request a PDN connection to any other PDN. A UE attached for access to RLOS shall not request any additional PDN connection for RLOS nor any PDN connection to any other PDN. The UE may also initiate the UE requested PDN connectivity procedure to add 3GPP access to the PDN connection which is already established over WLAN as specified in the clause 6.2.2 of 3GPP TS 23.161[ Network-Based IP Flow Mobility (NBIFOM); Stage 2 ] [34]. The UE may also initiate the UE requested PDN connectivity procedure to transfer an existing PDU session in the 5GS to EPS as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54]. If the UE supports the device triggering short message as specified in 3GPP TS 23.040[ Technical realization of the Short Message Service (SMS) ] [57] and supports non-IP PDN type, then upon receiving from ESMS entity as specified in 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [12] an indication requesting establishment of a PDN connection for non-IP PDN type using the default APN as specified in 3GPP TS 24.011[ Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface ] [13A], the UE shall initiate the UE requested PDN connectivity procedure in order to request connectivity to a PDN using the default APN and non-IP PDN type. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.5.1 |
2,552 | 5.3.9 Handling of NAS level mobility management congestion control | The AMF may detect 5GMM signalling congestion and perform general NAS level congestion control. Under the 5GMM signalling congestion conditions the AMF may reject 5GMM signalling requests from UEs as specified in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]. The AMF should not reject the following: a) requests for emergency services; b) requests for emergency services fallback; c) requests from UEs configured for high priority access in selected PLMN or SNPN; d) DEREGISTRATION REQUEST message; e) requests for mobile terminated services, triggered by paging or a notification procedure; f) requests for initial registration or mobility and periodic registration update, when emergency is indicated by lower layers; and g) requests for mobility registration update when the UE is reporting unavailability information due to discontinuous coverage. When general NAS level congestion control is active, the AMF may include a value for the mobility management back-off timer T3346 in the reject messages. The UE starts the timer T3346 with the value received in the 5GMM reject messages. To avoid that large numbers of UEs simultaneously initiate deferred requests, the AMF should select the value for the timer T3346 for the rejected UEs so that timeouts are not synchronised. When general NAS level congestion control is active, if the current SNPN is an SNPN selected for localized services in SNPN, the AMF may include an appropriate cause value other than 5GMM cause #22 "congestion" (e.g., #74 "Temporarily not authorized for this SNPN") in the reject messages without including timer T3346 value, to allow the UE to enter state 5GMM-REGISTERED.PLMN-SEARCH or 5GMM-DEREGISTERED.PLMN-SEARCH and perform SNPN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]. If the UE is registered in the same PLMN over the 3GPP access and non-3GPP access, and the UE receives the timer T3346 from the AMF, the timer T3346 shall apply to both 3GPP access and non-3GPP access. If the UE receives the paging message or NOTIFICATION message when timer T3346 is running and the UE is registered to the same PLMN over 3GPP access and non-3GPP access, the UE shall stop the timer T3346 for both accesses and respond to the paging message or NOTIFICATION message as specified in subclause 5.6.2 and subclause 5.6.3. NOTE 1: As an implementation option, MUSIM UE is allowed to not respond to paging based on the information available in the paging message, e.g. voice service indication. If the timer T3346 is running when the UE enters state 5GMM-DEREGISTERED, the UE remains switched on, and the USIM in the UE remains the same, then the timer T3346 is kept running until it expires or it is stopped. If the UE is switched off when the timer T3346 is running, the UE shall behave as follows when the UE is switched on and the USIM in the UE remains the same: let t1 be the time remaining for T3346 timeout at switch off and let t be the time elapsed between switch off and switch on. If t1 is greater than t, then the timer shall be restarted with the value t1 – t. If t1 is equal to or less than t, then the timer need not be restarted. If the UE is not capable of determining t, then the UE shall restart the timer with the value t1. If the UE enters a new PLMN or SNPN while timer T3346 is running, and the new PLMN or SNPN is not equivalent to the PLMN or SNPN where the UE started timer T3346, the UE shall stop timer T3346 when initiating 5GMM procedures in the new PLMN or SNPN. After a change in registration area, if the timer T3346 is running and 5GS update status is 5U1 UPDATED then the UE shall set the 5GS update status to 5U2 NOT UPDATED and enter state 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE. If timer T3346 is running or is deactivated, and: a) the UE is a UE configured for high priority access in selected PLMN or SNPN; b) the UE needs to initiate signalling for emergency services or emergency services fallback; or c) the UE needs to report unavailability information due to discontinuous coverage, then the UE is allowed to initiate 5GMM procedures. NOTE 2: UE can, based on implementation, restrict lower layers of non-3GPP access from establishing access stratum connection on a registered PLMN when timer T3346 is running for the same PLMN. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.3.9 |
2,553 | 4.11.1.2.1 5GS to EPS handover using N26 interface | Figure 4.11.1.2.1-1 describes the handover procedure from 5GS to EPS when N26 is supported. In the case of handover to a shared EPS network, the source NG-RAN determines a PLMN to be used in the target network as specified by TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The source NG-RAN shall indicate the selected PLMN ID to be used in the target network to the AMF as part of the TAI sent in the HO Required message. In the case of handover from a shared NG-RAN, the AMF may provide the MME with an indication that the 5GS PLMN is a preferred PLMN at later change of the UE to a 5GS shared networks. During the handover procedure, as specified in clause 4.9.1.3.1, the source AMF shall reject any SMF+PGW-C initiated N2 request received since handover procedure started and shall include an indication that the request has been temporarily rejected due to handover procedure in progress. Upon reception of a rejection for an SMF+PGW-C initiated N2 request(s) with an indication that the request has been temporarily rejected due to handover procedure in progress, the SMF+PGW-C behaves as specified in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13]. Figure 4.11.1.2.1-1: 5GS to EPS handover for single-registration mode with N26 interface The procedure involves a handover to EPC and setup of default EPS bearer and dedicated bearers for QoS Flows that have EBI assigned, in EPC in steps 1-16 and re-activation, if required, of dedicated EPS bearers for non-GBR QoS Flows that have no EBI assigned, in step 19. This procedure can be triggered, for example, due to new radio conditions, load balancing or in the presence of QoS Flow for normal voice or IMS emergency voice, the source NG-RAN node may trigger handover to EPC. For Ethernet and Unstructured PDU Session Types, the PDN Type Ethernet and non-IP respectively are used, when supported, in EPS. When EPS supports PDN Type non-IP but not PDN type Ethernet, PDN type non-IP is used also for Ethernet PDU sessions. The SMF shall also set the PDN Type of the EPS Bearer Context to non-IP in this case. After the handover to EPS, the PDN Connection will have PDN Type non-IP, but it shall be locally associated in UE and SMF to PDU Session Type Ethernet or Unstructured respectively. In the roaming home routed case, the SMF+PGW-C always provides the EPS Bearer ID and the mapped QoS parameters to UE. The V-SMF caches the EPS Bearer ID and the mapped QoS parameters obtained from H-SMF for this PDU session. This also applies in the case that the HPLMN operates the interworking procedure without N26. NOTE 1: The IP address preservation cannot be supported, if SMF+PGW-C in the HPLMN doesn't provide the mapped QoS parameters. 1. NG-RAN decides that the UE should be handed over to the E-UTRAN. If NG-RAN is configured to perform Inter RAT mobility due to IMS voice fallback triggered by QoS flow setup and request to setup QoS flow for IMS voice was received, NG-RAN responds indicating rejection of the QoS flow establishment because of mobility due to fallback for IMS voice via N2 SM information and triggers handover to E-UTRAN. The NG-RAN sends a Handover Required (Target eNB ID, Direct Forwarding Path Availability, Source to Target Transparent Container, inter system handover indication) message to the AMF. NG-RAN indicates bearers corresponding to the 5G QoS Flows for data forwarding in Source to Target Transparent Container. If the source NG RAN and target E-UTRAN support RACS as defined in TS 23.501[ System architecture for the 5G System (5GS) ] [2], the Source to Target transparent container need not carry the UE radio access capabilities (instead the UE Radio Capability ID is supplied from the CN to the target E-UTRAN). However, if the source NG-RAN has knowledge that the target E-UTRAN might not have a local copy of the Radio Capability corresponding to the UE Radio Capability ID (i.e. because the source NG-RAN had itself to retrieve the UE's Radio Capability from the AMF) then the source NG-RAN may also send some (or all) of the UE's Radio Capability to the target E-UTRAN (the size limit based on configuration). In the case of inter-PLMN handover, when the source NG-RAN and target E-UTRAN support RACS as defined in TS 23.501[ System architecture for the 5G System (5GS) ] [2] and TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13] and the source NG-RAN determines that the target PLMN does not support the UE Radio Capability ID assigned by the source PLMN based on local configuration, then the source NG-RAN includes the UE radio access capabilities in the Source to Target transparent container. Direct Forwarding Path Availability indicates whether direct forwarding is available from the NG-RAN to the E-UTRAN. This indication from NG-RAN can be based on e.g. the presence of IP connectivity and security association(s) between the NG-RAN and the E-UTRAN. If the handover is triggered due to Emergency fallback, the NG-RAN may forward the Emergency indication to the target eNB in the Source to Target Transparent Container and the target eNB allocates radio bearer resources taking received indication into account. 2a-2c. The AMF determines from the 'Target eNB Identifier' IE that the type of handover is Handover to E-UTRAN. The AMF selects an MME as described in clause 4.3.8.3 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13]. The AMF determines for a PDU Session whether to retrieve context including mapped UE EPS PDN Connection from the V-SMF (in the case of HR roaming) or the SMF+PGW-C (in the case of non roaming or LBO roaming) as follows: - If the AMF determines that one or more of the EBI(s) can be transferred, the AMF sends Nsmf_PDUSession_ContextRequest to the V-SMF or SMF+PGW-C and includes in the message EBI value(s) if any that cannot be transferred. - The EBI values(s) that cannot be transferred is determined by the AMF if the target MME does not support 15 EPS bearers, i.e. the AMF determines the EBI values in range 1-4 as not to be transferred to EPS and if there are still more than 8 EBI values associated with PDU Sessions, the AMF then determines EBI value(s) not to be transferred to EPS based on S-NSSAI and ARP as specified in clause 5.17.2.2.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. - The AMF does not retrieve the context for a PDU Session that cannot be transferred to EPS due to no EBI allocated, or allocated EBIs not transferrable, or combination of the two. When the AMF sends Nsmf_PDUSession_ContextRequest the AMF provides also the target MME capability to the V-SMF or the SMF+PGW-C to allow it to determine whether to include EPS Bearer context for Ethernet PDN Type or non-IP PDN Type or not. When the AMF sends Nsmf_PDUSession_ContextRequest to the V-SMF or the SMF+PGW-C, the AMF indicates whether the target MME supports User Plane Integrity Protection with EPS. NOTE 2: The AMF knows the MME capability to support 15 EPS bearers, Ethernet PDN type and/or non-IP PDN type or not through local configuration. The AMF knows the MME capability to support User Plane integrity protection through local configuration but the actual EPS support may depend on the target E-UTRAN coverage (see step 14). When Nsmf_PDUSession_Context Request is received in the V-SMF or the SMF+PGW-C, the V-SMF or the SMF+PGW-C provides context that includes the mapped EPS PDN Connection as follows: - If there is EBI list not to be transferred and the EBI value of the QoS Flow associated with the default QoS Rule is included in that list, the V-SMF or the SMF+PGW-C shall not return the PDN Connection context (which implies the whole PDU Session is not transferred to EPS), otherwise if the EBI value of the QoS Flow associated with the default QoS Rule is not included in EBI list not to be transferred, the V-SMF or PGW C+SMF shall not provide the EPS bearer context(s) mapped from QoS Flow(s) associated with the EBI list not to be transferred. - For PDU Sessions with PDU Session Type Ethernet, if the UE and target MME supports Ethernet PDN type, the V-SMF or the PGW C+SMF provides Context for Ethernet PDN Type, otherwise if the target MME does not support Ethernet Type but support non-IP Type, the V-SMF or the PGW C+SMF provides Context for non-IP PDN Type. For PDU Sessions with PDU Session Type Unstructured, the V-SMF or the SMF+PGW-C provides Context for non-IP PDN Type. - If the UP integrity protection policy for the EPS bearer context is set to "Required", the V-SMF or the PGW C+SMF shall not provide the EPS bearer context unless the MME capability indicates support for User Plane Integrity Protection with EPS and the UE supports User Plane Integrity Protection with EPS. In the case of non roaming or LBO roaming, when Nsmf_PDUSession_ContextRequest is received in PGW C+SMF, if the SMF+PGW-C determines that EPS Bearer Context can be transferred to EPS and the CN Tunnel Info for EPS bearer(s) have not been allocated before, the SMF+PGW-C sends N4 Session modification to the PGW-U+UPF to establish the CN tunnel for each EPS bearer and provides EPS Bearer Contexts to AMF, as described in step 8 of clause 4.11.1.4.1. The PGW-U+UPF is ready to receive the uplink packet from E-UTRAN. This step is performed with all the SMF+PGW-Cs corresponding to PDU Sessions of the UE which are associated with 3GPP access and have at leaset one EBI(s) determined to be transferred to EPS. NOTE 2: The AMF knows the MME capability to support 15 EPS bearers, Ethernet PDN type and/or non-IP PDN type or not through local configuration. In home routed roaming scenario, the UE's EPS PDN Contexts are obtained from the V-SMF. If Small Data Rate Control applies on PDU Session, the V-SMF retrieves the SM Context, including Small Rate Control Status information from the H-SMF using Nsmf_PDUSession_Context Request. 3. The AMF sends a Forward Relocation Request as in step 3 in clause 5.5.1.2.2 (S1-based handover, normal) in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13], with the following modifications and clarifications: - Parameter "Return preferred" may be included. Return preferred is an optional indication by the MME of a preferred return of the UE to the 5GS PLMN at a later access change to a 5GS shared network. An MME may use this information as specified by TS 23.501[ System architecture for the 5G System (5GS) ] [2]. - The SGW address and TEID for both the control-plane or EPS bearers in the message are such that target MME selects a new SGW. - The AMF determines, based on configuration and the Direct Forwarding Path Availability, the Direct Forwarding Flag to inform the target MME whether direct data forwarding is applicable. - The AMF includes the mapped SM EPS UE Contexts for PDU Sessions with and without active UP connections. - Subject to operator policy if the secondary RAT access restriction condition is the same for EPS and 5GS, the AMF may set EPS secondary RAT access restriction condition based on the UE's subscription data. 4-5. Step 4 and 4a respectively in clause 5.5.1.2.2 (S1-based handover, normal) in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13]. 6. Step 5 (Handover Request) in clause 5.5.1.2.2 (S1-based handover, normal) in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13] with the following modification: - Handover Request may contain information Handover Restriction List with information about PLMN IDs as specified by clause 5.2a of TS 23.251[ Network sharing; Architecture and functional description ] [35] for eNodeB functions. - The target eNB should establish E-RABs indicated by the list of EPS bearer to be setup provided by the MME, even if they are not included in the source to target container. 7-9. Step 5a through 7 in clause 5.5.1.2.2 (S1-based handover, normal) in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13]. 10a. If data forwarding applies, the AMF sends the Nsmf_PDUSession_UpdateSMContext Request (data forwarding information) to the SMF+PGW-C. If multiple SMF+PGW-Cs serves the UE, the AMF maps the EPS bearers for Data forwarding to the SMF+PGW-C address(es) based on the association between the EPS bearer ID(s) and PDU Session ID(s). In home-routed roaming case, the AMF requests the V-SMF to create indirect forwarding tunnel if indirect forwarding applies. 10b. If indirect data forwarding applies, the SMF+PGW-C may select an intermediate PGW-U+UPF for data forwarding. The SMF+PGW-C maps the EPS bearers for Data forwarding to the 5G QoS flows based on the association between the EPS bearer ID(s) and QFI(s) for the QoS flow(s) in the SMF+PGW-C and then sends the QFIs, Serving GW Address(es) and TEID(s) for data forwarding to the PGW-U+UPF. The CN Tunnel Info is provided by the PGW-U+UPF to SMF+PGW-C in this response. In home-routed roaming case, the V-SMF selects the V-UPF for data forwarding. The SMF+PGW-C deactivates PDU Set based handling at PGW-U+UPF if it is activated during the UE was registered to 5GS as described in clause 5.37.5.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 10c. The SMF+PGW-C returns an Nsmf_PDUSession_UpdateSMContext Response (Cause, Data Forwarding tunnel Info, QoS flows for Data Forwarding). Based on the correlation between QFI(s) and Serving GW Address(es) and TEID(s) for data forwarding, the PGW-U+UPF maps the QoS flow(s) into the data forwarding tunnel(s) in EPC. 11. The AMF sends the Handover Command to the source NG-RAN (Transparent container (radio aspect parameters that the target eNB has set-up in the preparation phase), Data forwarding tunnel info, QoS flows for Data Forwarding). The source NG-RAN commands the UE to handover to the target Access Network by sending the HO Command. The UE correlates the ongoing QoS Flows with the indicated EPS Bearer IDs to be setup in the HO command. The UE locally deletes the PDU Session if the QoS Flow associated with the default QoS rule in the PDU Session does not have an EPS Bearer ID assigned. If the QoS Flow associated with the default QoS rule has an EPS Bearer ID assigned, the UE keeps the PDU Session (PDN connection) and for the remaining QoS Flow(s) that do not have EPS bearer ID(s) assigned, the UE locally deletes the QoS rule(s) and the QoS Flow level QoS parameters if any associated with those QoS Flow(s) and notifies the impacted applications that the dedicated QoS resource has been released. The UE deletes any UE derived QoS rules. The EPS Bearer ID that was assigned for the QoS flow of the default QoS rule in the PDU Session becomes the EPS Bearer ID of the default bearer in the corresponding PDN connection. If indirect data forwarding is applied, Data forwarding tunnel info includes CN tunnel info for data forwarding per PDU session. For the QoS Flows indicated in the "QoS Flows for Data Forwarding", NG-RAN initiate data forwarding via to the PGW-U+UPF based on the CN Tunnel Info for Data Forwarding per PDU Session. Then the PGW-U+UPF maps data received from the data forwarding tunnel(s) in the 5GS to the data forwarding tunnel(s) in EPS and sends the data to the target eNodeB via the Serving GW. If direct data forwarding is applied, Data forwarding tunnel info includes E-UTRAN tunnel info for data forwarding per EPS bearer. NG-RAN initiate data forwarding to the target E-UTRAN based on the Data Forwarding Tunnel Info for Data Forwarding per EPS bearer. 12-12c. Step 13 to step 14 from clause 5.5.1.2.2 (S1-based handover, normal) in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13] with the following clarification: - The AMF requests the release of the PDU Session which is associated with 3GPP access and not expected to be transferred to EPC, i.e. the AMF requests the release of: - PDU Session(s) whose corresponding SMF+PGW-C(s) are not contacted by AMF for SM context because the AMF determines that none of EBI(s) for the PDU Session can be transferred to EPS at step 2a; and - PDU Session(s) for which the SM context retrieval failed at step 2c. 12d. The AMF acknowledges MME with Relocation Complete Ack message. A timer in AMF is started to supervise when resource in NG-RAN shall be released. 12e. In the case of home routed roaming, the AMF invokes Nsmf_PDUSession_ReleaseSMContext Request (V-SMF only indication) to the V-SMF. This service operation request the V-SMF to remove only the SM context in V-SMF, i.e. not release PDU Session context in the SMF+PGW-C. If indirect forwarding tunnel(s) were previously established, the V-SMF starts a timer and releases the SM context on expiry of the timer. If no indirect forwarding tunnel has been established, the V-SMF immediately releases the SM context and its UP resources for this PDU Session in V-UPF locally. 13. Step 15 from clause 5.5.1.2.2 (S1-based handover, normal) in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13]. 14a. Step 16 (Modify Bearer Request) from clause 5.5.1.2.2 (S1-based handover, normal) in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13] with the following clarification: - If the PDU Session (PDN connection) has QoS Flows that do not have EPS bearer ID(s) assigned, or QoS Flow(s) for which the mapped EPS bearers are not included in Modify Bearer Request, the SMF+PGW-C deletes the PCC rule(s) associated with those QoS Flows and informs the PCF about the removed PCC rule(s). If there are QoS Flow(s) with PCC rule(s) that do not have allocated TFT packet filters, the SMF+PGW-C deletes those PCC rule(s) and informs the PCF about the removed PCC rule(s). NOTE 4: If the QoS flow is deleted, the IP flows of the deleted QoS rules will continue flowing on the default EPS bearer if it does not have an assigned TFT. If the default EPS bearer has an assigned TFT, the IP flows of the deleted QoS Flow may be interrupted until step 19 when dedicated bearer activation is triggered by a request from the PCF. The SMF+PGW-C may need to report some subscribed event to the PCF by performing an SMF initiated SM Policy Association Modification procedure as defined in clause 4.16.5. If the MME does not indicate support of User Plane integrity protection, or the new eNB does not support User Plane integrity protection, or the UE does not support User Plane Integrity Protection with EPS and the UP integrity protection policy is set to "Required" then the SMF+PGW-C releases the bearers associated with the PDN CONNECTION. 15. The SMF+PGW-C initiates a N4 Session Modification procedure towards the UPF+PGW-U to update the User Plane path, i.e. the downlink User Plane for the indicated PDU Session is switched to E-UTRAN. The SMF+PGW-C releases the resource of the CN tunnel for PDU Session in UPF+PGW-U. 16. Step 16a (Modify Bearer Response) from clause 5.5.1.2.2 (S1-based handover, normal) in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13]. At this stage the User Plane path is established for the default bearer and the dedicated EPS bearers between the UE, target eNodeB, Serving GW and the PGW-U+UPF. The SMF+PGW-C uses the EPS QoS parameters as assigned for the dedicated EPS bearers during the QoS Flow establishment. SMF+PGW-C maps all the other IP flows to the default EPS bearer (see NOTE 4). If indirect forwarding tunnel(s) were previously established, the SMF+PGW-C starts a timer, to be used to release the resource used for indirect data forwarding. 17. Step 17 from clause 5.5.1.2.2 (S1-based handover, normal) in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13]. 18. The UE initiates a Tracking Area Update procedure as specified in step 18 of clause 5.5.1.2.2 (S1-based handover, normal) in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13]. This includes the deregistration of the old AMF for 3GPP access from the HSS+UDM as specified in clause 4.11.1.5.3. Any registration associated with the non-3GPP access in the old AMF is not removed (i.e. an AMF that was serving the UE over both 3GPP and non-3GPP accesses does not consider the UE as deregistered over non 3GPP access and will remain registered and subscribed to subscription data updates in UDM). NOTE 5: The behaviour whereby the HSS+UDM cancels location of CN node of the another type, i.e. AMF, is similar to HSS behaviour for MME and Gn/Gp SGSN registration (see TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13]). The target AMF that receives the cancel location from the HSS+UDM is the one associated with 3GPP access. When the UE decides to deregister over non-3GPP access or the old AMF decides not to maintain a UE registration for non-3GPP access anymore, the old AMF then deregisters from UDM by sending a Nudm_UECM_Deregistration service operation, unsubscribes from Subscription Data updates by sending an Nudm_SDM_Unsubscribe service operation to UDM and releases all the AMF and AN resources related to the UE. 19. If PCC is deployed, the PCF may decide to provide the previously removed PCC rules to the SMF+PGW-C again thus triggering the SMF+PGW-C to initiate dedicated bearer activation procedure. This procedure is specified in clause 5.4.1 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13] with modification captured in clause 4.11.1.5.4. This step is applicable for PDN Type IP or Ethernet, but not for non-IP PDN Type. 20. Step 21 from clause 5.5.1.2.2 (S1-based handover, normal) in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13]. 21. In the case of home routed roaming, at the expiry of the timer at V-SMF started at step 12e, the V-SMF locally releases the SM context and the UP resource for the PDU Session including the resources used for indirect forwarding tunnel(s) that were allocated at step 10. In non-roaming or local breakout roaming, if SMF+PGW-C has started a timer in step 16, at the expiry of the timer, the SMF+PGW-C sends N4 Session Modification Request to PGW-U+UPF to release the resources used for the indirect forwarding tunnel(s) that were allocated at step 10. When the timer set in step 12d expires, AMF also sends a UE Context Release Command message to the source NG RAN. The source NG RAN releases its resources related to the UE and responds with a UE Context Release Complete message. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.11.1.2.1 |
2,554 | 8.4.1.2.6 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.4.1.2.6-1, the average probability of a missed downlink scheduling grant (Pm-dsg) shall be below the specified value in Table 8.4.1.2.6-2. In Table 8.4.1.2.6-1, Cell 1 is the serving cell, and Cell 2 and Cell 3 are the agressor cells. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1, Cell 2 and Cell 3, respectively. The CRS assistance information [7] is provided and includes Cell 2 and Cell 3. Table 8.4.1.2.6-1: Test Parameters for PDCCH/PCFICH Table 8.4.1.2.6-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.1.2.6 |
2,555 | 5.4.4.2 Generic UE configuration update procedure initiated by the network | The AMF shall initiate the generic UE configuration update procedure by sending the CONFIGURATION UPDATE COMMAND message to the UE. The AMF shall in the CONFIGURATION UPDATE COMMAND message either: a) include one or more of the following parameters: 5G-GUTI, TAI list, allowed NSSAI that may include the mapped S-NSSAI(s), LADN information, extended LADN information, service area list, MICO indication, NITZ information, configured NSSAI that may include the mapped S-NSSAI(s), NSSRG information, S-NSSAI location validity information, S-NSSAI time validity information, rejected S-NSSAI(s) in the Rejected NSSAI IE or in the Extended rejected NSSAI IE, network slicing subscription change indication, operator-defined access category definitions, SMS indication, "CAG information list", UE radio capability ID, 5GS registration result, UE radio capability ID deletion indication, truncated 5G-S-TMSI configuration, T3447 value, "list of PLMN(s) to be used in disaster condition", disaster roaming wait range, disaster return wait range, PEIPS assistance information, the priority indicator, the NSAG information, alternative NSSAI, partially allowed NSSAI, partially rejected NSSAI, on-demand NSSAI, feature authorization indication, or discontinuous coverage maximum time offset; b) include the Configuration update indication IE with the Registration requested bit set to "registration requested"; or c) include a combination of both a) and b). If the UE is registering or registered for onboarding services in SNPN, the serving SNPN shall not provide the configured NSSAI, the allowed NSSAI or the rejected NSSAI to the UE. If the UE supports extended rejected NSSAI, the rejected S-NSSAI(s) shall be included in the Extended rejected NSSAI IE. Otherwise, the rejected S-NSSAI(s) shall be included in the Rejected NSSAI IE. In roaming scenarios, if the Extended rejected NSSAI IE is included in the CONFIGURATION UPDATE COMMAND message, the AMF shall provide mapped S-NSSAI(s) for the rejected NSSAI. If an acknowledgement from the UE is requested, the AMF shall indicate "acknowledgement requested" in the Acknowledgement bit of the Configuration update indication IE in the CONFIGURATION UPDATE COMMAND message and shall start timer T3555. Acknowledgement shall be requested for all parameters except when only NITZ information is included. To initiate parameter re-negotiation between the UE and network, the AMF shall indicate "registration requested" in the Registration requested bit of the Configuration update indication IE in the CONFIGURATION UPDATE COMMAND message. NOTE 1: Generic UE configuration update procedure can be initiated by the AMF for updating the emergency number list, the extended emergency number list or both by indicating "registration requested" in the Registration requested bit of the Configuration update indication IE in the CONFIGURATION UPDATE COMMAND message to the UE. If a new allowed NSSAI information or AMF re-configuration of supported S-NSSAIs requires an AMF relocation, the AMF shall indicate "registration requested" in the Registration requested bit of the Configuration update indication IE and include the Allowed NSSAI IE in the CONFIGURATION UPDATE COMMAND message. If the AMF includes a new allowed NSSAI in the CONFIGURATION UPDATE COMMAND message and the subscription information includes the NSSRG information, then the S-NSSAIs of the allowed NSSAI shall be associated with at least one common NSSRG value. If the network has pending NSSAI, the S-NSSAIs in the pending NSSAI and allowed NSSAI shall be associated with at least one common NSSRG value. If the AMF includes a new partially allowed NSSAI and the new partially allowed NSSAI requires an AMF relocation, the AMF shall indicate "registration requested" in the Registration requested bit of the Configuration update indication IE and include the Partially allowed NSSAI IE in the CONFIGURATION UPDATE COMMAND message. If the AMF includes a new configured NSSAI in the CONFIGURATION UPDATE COMMAND message and the new configured NSSAI requires an AMF relocation as specified in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8], the AMF shall indicate "registration requested" in the Registration requested bit of the Configuration update indication IE in the message. If the AMF includes a new configured NSSAI in the CONFIGURATION UPDATE COMMAND message, the subscription information includes the NSSRG information, and the UE has set the NSSRG bit in the 5GMM capability IE of the REGISTRATION REQUEST message to: a) "NSSRG supported", then the AMF shall include the NSSRG information in the CONFIGURATION UPDATE COMMAND message; or b) "NSSRG not supported", then the configured NSSAI shall include one or more S-NSSAIs each of which is associated with all the NSSRG value(s) of the default S-NSSAI(s), or the configured NSSAI shall include, based on the indication received from the UDM as specified in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8], all subscribed S-NSSAIs even if these S-NSSAIs do not share any common NSSRG value. If the AMF needs to update the NSSRG information and the UE has set the NSSRG bit to "NSSRG supported" in the 5GMM capability IE of the REGISTRATION REQUEST message, then the AMF shall include the new NSSRG information in the CONFIGURATION UPDATE COMMAND message. If the AMF includes a new NSSRG information in the CONFIGURATION UPDATE COMMAND message and the AMF determines that the UE needs to provide a new requested NSSAI due to no NSSRG value common to all the S-NSSAI(s) of the allowed NSSAI based on the new NSSRG information, then the CONFIGURATION UPDATE COMMAND message shall indicate "registration requested" in the Registration requested bit of the Configuration update indication IE. If the UE supports S-NSSAI time validity information and the AMF needs to update the S-NSSAI time validity information, then the AMF shall include the new S-NSSAI time validity information in the CONFIGURATION UPDATE COMMAND message. If the AMF needs to update the S-NSSAI location validity information toward a UE which has set the NS-AoS bit to "S-NSSAI location validity information supported" in the 5GMM capability IE of the REGISTRATION REQUEST message, then the AMF shall include the new S-NSSAI location validity information in the CONFIGURATION UPDATE COMMAND message. If the CONFIGURATION UPDATE COMMAND message is initiated only due to changes to the allowed NSSAI and these changes require the UE to initiate a registration procedure, but the AMF is unable to determine an allowed NSSAI for the UE as specified in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8], then the CONFIGURATION UPDATE COMMAND message shall indicate "registration requested" in the Registration requested bit of the Configuration update indication IE, and shall not contain any other parameters. If the slice deregistration inactivity timer has expired, the UE does not support network slice usage control and the AMF removes the on-demand S-NSSAI from the allowed NSSAI over the current access type, the AMF shall include the new allowed NSSAI in the CONFIGURATION UPDATE COMMAND message. If: - the AMF needs to enforce a change in the restriction on the use of enhanced coverage or use of CE mode B as described in subclause 5.3.18; or - the AMF decides to inform a UE in 5GMM-CONNECTED mode and registered for disaster roaming services, that a disaster condition is no longer applicable; NOTE 1A: The case of the AMF triggering a generic UE configuration update procedure to inform a UE registered for disaster roaming services that a disaster condition is no longer applicable, is only applicable for a UE already in 5GMM-CONNECTED mode. the AMF shall indicate "registration requested" in the Registration requested bit of the Configuration update indication IE and "release of N1 NAS signalling connection not required" in the Signalling connection maintain request bit of the Additional configuration indication IE in the CONFIGURATION UPDATE COMMAND message. If a network slice-specific authentication and authorization procedure for an S-NSSAI is completed as a: a) success, the AMF shall include this S-NSSAI in the allowed NSSAI over the same access of the requested S-NSSAI or in the partially allowed NSSAI over 3GPP access; or b) failure, the AMF shall include this S-NSSAI in the rejected NSSAI for the failed or revoked NSSAA with the rejection cause "S-NSSAI not available due to the failed or revoked network slice-specific authentication and authorization" over either 3GPP access or non-3GPP access. If authorization is revoked for an S-NSSAI that is in the current allowed NSSAI for an access type, the AMF shall: a) provide a new allowed NSSAI to the UE, excluding the S-NSSAI for which authorization is revoked; and b) provide a new rejected NSSAI for the failed or revoked NSSAA, including the S-NSSAI in the rejected NSSAI for which the authorization is revoked, with the rejection cause "S-NSSAI not available due to the failed or revoked network slice-specific authentication and authorization". The allowed NSSAI, the partially allowed NSSAI and the rejected NSSAI shall be included in the CONFIGURATION UPDATE COMMAND message to reflect the result of the procedures subject to network slice-specific authentication and authorization. NOTE 2: If there are multiple S-NSSAIs subject to network slice-specific authentication and authorization, it is implementation specific if the AMF informs the UE about the outcome of the procedures in one or more CONFIGURATION UPDATE COMMAND messages. If the AMF includes the Network slicing indication IE in the CONFIGURATION UPDATE COMMAND message with the Network slicing subscription change indication set to "Network slicing subscription changed", and changes to the allowed NSSAI require the UE to initiate a registration procedure, but the AMF is unable to determine an allowed NSSAI for the UE as specified in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8], then the CONFIGURATION UPDATE COMMAND message shall additionally indicate "registration requested" in the Registration requested bit of the Configuration update indication IE and shall not include an allowed NSSAI. If EAC mode is activated for an S-NSSAI, the AMF shall perform NSAC for the S-NSSAI subject to NSAC before such S-NSSAI is included in the allowed NSSAI in the CONFIGURATION UPDATE COMMAND message. If EAC mode is deactivated for an S-NSSAI, the AMF shall perform NSAC for the S-NSSAI subject to NSAC after such S-NSSAI is included in the allowed NSSAI in the CONFIGURATION UPDATE COMMAND message. If the UE supports extended rejected NSSAI and the AMF determines that maximum number of UEs reached for one or more S-NSSAI(s) in the allowed NSSAI as specified in subclause 4.6.2.5, the AMF shall include the rejected NSSAI containing one or more S-NSSAIs with the rejection cause "S-NSSAI not available due to maximum number of UEs reached" in the Extended rejected NSSAI IE in the CONFIGURATION UPDATE COMMAND message. In addition, the AMF may include a back-off timer value for each S-NSSAI with the rejection cause "S-NSSAI not available due to maximum number of UEs reached" included in the Extended rejected NSSAI IE of the CONFIGURATION UPDATE COMMAND message. To avoid that large numbers of UEs simultaneously initiate deferred requests, the network should select the value for the backoff timer for each S-NSSAI for the informed UEs so that timeouts are not synchronised. If the UE does not indicate support for extended rejected NSSAI and the maximum number of UEs has been reached, the AMF should include the rejected NSSAI containing one or more S-NSSAIs with the rejection cause "S-NSSAI not available in the current registration area" in the Rejected NSSAI IE and should not include these S-NSSAIs in the allowed NSSAI in the CONFIGURATION UPDATE COMMAND message. In addition, the AMF may based on the network policies start a local implementation specific timer for the UE per rejected S-NSSAI and upon expiration of the local implementation specific timer, the AMF may remove the rejected S-NSSAI from the rejected NSSAI and update to the UE by initiating the generic UE configuration update procedure. NOTE 3: Based on network policies, the AMF can include the S-NSSAI(s) for which the maximum number of UEs has been reached in the rejected NSSAI with rejection causes other than "S-NSSAI not available in the current registration area". If the UE has set the NSAG bit to "NSAG supported" in the 5GMM capability IE of the REGISTRATION REQUEST message, the AMF may include the NSAG information IE in the CONFIGURATION UPDATE COMMAND message. Up to 4 NSAG entries are allowed to be associated with a TAI list in the NSAG information IE. NOTE 3a: How the AMF selects NSAG entries to be included in the NSAG information IE is implementation specific, e.g. take the NSAG priority and the current registration area into account. NOTE 3b: If the NSAG for the PLMN and its equivalent PLMN(s) have different associations with S-NSSAIs, then the AMF includes a TAI list for the NSAG entry in the NSAG information IE. If the UE supports network slice replacement and the AMF determines to provide the mapping information between the S-NSSAI to be replaced and the alternative S-NSSAI to the UE, then the AMF shall include the Alternative NSSAI IE, the Allowed NSSAI IE including the alternative S-NSSAI, if not included in the current allowed NSSAI, and the Configured NSSAI IE including the alternative S-NSSAI, if not included in the current configured NSSAI, in the CONFIGURATION UPDATE COMMAND message. If the AMF determines that the S-NSSAI which has been replaced is available, then the AMF shall provide the updated alternative NSSAI excluding the S-NSSAI which has been replaced and the corresponding alternative S-NSSAI in the Alternative NSSAI IE in the CONFIGURATION UPDATE COMMAND message. If the AMF determines that all the S-NSSAI(s) which have been replaced are available, then the AMF shall provide the Alternative NSSAI IE with Length of Alternative NSSAI contents set to 0 in the CONFIGURATION UPDATE COMMAND message. If the UE supports partial network slice and the AMF needs to update the partially allowed NSSAI, partially rejected NSSAI or both, then the AMF shall include the Partially allowed NSSAI IE, the Partially rejected NSSAI IE or both, in the CONFIGURATION UPDATE COMMAND message. If the UE indicates network slice usage control and the AMF needs to update the on-demand NSSAI, the AMF shall include the On-demand NSSAI IE in the CONFIGURATION UPDATE COMMAND message. If the AMF needs to update the LADN information, the AMF shall include the LADN information in the LADN information IE of the CONFIGURATION UPDATE COMMAND message. If the UE supports LADN per DNN and S-NSSAI and the AMF needs to update the extended LADN information, the AMF shall include the extended LADN information in the Extended LADN information IE of the CONFIGURATION UPDATE COMMAND message. If: - the UE does not support LADN per DNN and S-NSSAI; - the UE is subscribed to the LADN DNN for a single S-NSSAI only; and - the AMF only has the extended LADN information; the AMF may decide to provide the LADN service area for that LADN DNN of the extended LADN information as the LADN information and include the LADN information in the LADN information IE of the CONFIGURATION UPDATE COMMAND message. NOTE 3c: If the LADN service area is configured per DNN and S-NSSAI, in order to serve the UEs that do not support LADN per DNN and S-NSSAI, it is recommended that the LADN DNN is only served by a single S-NSSAI. NOTE 3d: In case of the UE is subscribed to the LADN DNN for multiple S-NSSAIs, the AMF can treat this as no extended LADN information is available. If the UE does not support LADN per DNN and S-NSSAI and the AMF has neither the LADN information nor the extended LADN information, the AMF shall not provide any LADN information to the UE. If the AMF needs to update the "CAG information list", the AMF shall include the CAG information list IE or the Extended CAG information list IE in the CONFIGURATION UPDATE COMMAND message. NOTE 4: If the UE supports extended CAG information list, the CAG information list can be included either in the CAG information list IE or Extended CAG information list IE. If the UE does not support extended CAG information list, the CAG information list shall not be included in the Extended CAG information list IE. If the AMF needs to update the "CAG information list", the UE has an emergency PDU session, and the AMF can determine that the UE is in a) a CAG cell and none of the CAG-ID(s) supported by the CAG cell is authorized based on the "allowed CAG list" for the current PLMN in the updated "CAG information list"; or b) a non-CAG cell and the entry for the current PLMN in the updated "CAG information list" includes an "indication that the UE is only allowed to access 5GS via CAG cells"; the AMF may indicate to the SMF to perform a local release of: a) all non-emergency single access PDU sessions associated with 3GPP access; b) all MA PDU sessions without a PDN connection established as a user-plane resource and without user plane resources established on non-3GPP access; and c) the 3GPP access user plane resources of all those MA PDU sessions with user plane resources established on both accesses. The AMF shall not indicate to the SMF to release the emergency PDU session. If the AMF indicated to the SMF to perform a local release of: a) all single access non-emergency PDU sessions associated with 3GPP access; b) all MA PDU sessions without a PDN connection established as a user-plane resource and without user plane resources established on non-3GPP access; and c) the 3GPP access user plane resources of all those MA PDU sessions with user plane resources established on both accesses; the network shall behave as if the UE is registered for emergency services over 3GPP access and shall set the emergency registered bit of the 5GS registration result IE to "Registered for emergency services" in the CONFIGURATION UPDATE COMMAND message. If the AMF is initiating the generic UE configuration update procedure to indicate to a UE which is registered for disaster roaming services, and which has an ongoing emergency PDU session, that the UE is registered for emergency services as described in subclause 4.24, the AMF shall set the emergency registered bit of the 5GS registration result IE to "Registered for emergency services" in the CONFIGURATION UPDATE COMMAND message. If the AMF: - updated the "CAG information list" to remove one or more CAG-ID(s) authorized based on the Allowed CAG list for the serving PLMN or an equivalent PLMN; or - updated the "CAG information list" to set the "indication that the UE is only allowed to access 5GS via CAG cells" for the serving PLMN or an equivalent PLMN which was not set before, then upon completion of the configuration update procedure and if the UE does not have an emergency PDU session, the AMF shall initiate the release of the N1 NAS signalling connection according to subclause 5.3.1.3. If the AMF needs to update the truncated 5G-S-TMSI configuration for a UE in NB-N1 mode using control plane CIoT 5GS optimization, the AMF shall include the Truncated 5G-S-TMSI configuration IE in the CONFIGURATION UPDATE COMMAND message. If the AMF includes a UE radio capability ID deletion indication IE in the CONFIGURATION UPDATE COMMAND message, the AMF shall indicate "registration requested" in the Registration requested bit of the Configuration update indication IE. If the AMF needs to redirect the UE to EPC as described in subclause 4.8.4A.2, the AMF shall indicate "registration requested" in the Registration requested bit of the Configuration update indication IE and "release of N1 NAS signalling connection not required" in the Signalling connection maintain request bit of the Additional configuration indication IE in the CONFIGURATION UPDATE COMMAND message. If the UE is not in NB-N1 mode and the UE supports RACS, the AMF may include either a UE radio capability ID IE or a UE radio capability ID deletion indication IE in the CONFIGURATION UPDATE COMMAND message. During an established 5GMM context, the network may send none, one, or more CONFIGURATION UPDATE COMMAND messages to the UE. If more than one CONFIGURATION UPDATE COMMAND message is sent, the messages need not have the same content. Upon receipt of the result of the UUAA-MM procedure from the UAS-NF, the AMF shall include: a) the service-level-AA response with the SLAR field set to: 1) "Service level authentication and authorization was successful" if the AMF detects the UUAA-MM procedure has succeeded; or 2) "Service level authentication and authorization was not successful or service level authorization is revoked" if the AMF detects the UUAA-MM procedure has failed; b) if the CAA-Level UAV ID is provided by the UAS-NF, the service-level device ID with the value set to the CAA-Level UAV ID; and; c) if a payload is received from the UAS-NF: 1) the service-level-AA payload with the value set to the payload; and 2) if a payload type associated with the payload is received, the service-level-AA payload type with the values set to the payload type; and 3) if the payload type associated with the payload is for C2 authorization payload, the service-level-AA response with C2AR field set to either "C2 authorization was successful" or "C2 authorization was not successful or C2 authorization is revoked" according to the authorization result received from the UAS-NF; in the Service-level-AA container IE of the CONFIGURATION UPDATE COMMAND message. NOTE 5: UAS security information can be included in the UUAA payload by the USS as specified in 3GPP TS 33.256[ Security aspects of Uncrewed Aerial Systems (UAS) ] [24B]. NOTE 5A: The service-level-AA payload associated with the payload type "C2 authorization payload" can include pairing information for the direct C2 communication, or the security information as specified in TS 33.256[ Security aspects of Uncrewed Aerial Systems (UAS) ] [24B], or both. NOTE 6: If the AMF receives the HTTP code set to "4xx" or "5xx" as specified in 3GPP TS 29.500[ 5G System; Technical Realization of Service Based Architecture; Stage 3 ] [20AA] or the AMF detects that the UUAA-MM failure as specified in 3GPP TS 29.256[ Uncrewed Aerial Systems Network Function (UAS-NF); Aerial Management Services; Stage 3 ] [21B], then the AMF considers the UUAA-MM procedure has failed. If the AMF needs to deliver to the UE the UUAA revocation notification received from the UAS-NF, the AMF shall include the service-level-AA response with SLAR set to "Service level authentication and authorization was not successful or service level authorization is revoked" in the Service-level-AA container IE of the CONFIGURATION UPDATE COMMAND message. If the UE supports UAS services and UAS services become enabled for the UE (e.g. because of the aerial subscription becomes a part of the UE subscription data retrieved from the UDM), the AMF may include the service-level-AA service status indication with UAS field set to "UAS services enabled" in the Service-level-AA container IE of the CONFIGURATION UPDATE COMMAND message. If the UE supports MINT, the AMF may include the List of PLMNs to be used in disaster condition IE in the CONFIGURATION UPDATE COMMAND message. If the UE supports MINT, the AMF may include the Disaster roaming wait range IE in the CONFIGURATION UPDATE COMMAND message. If the UE supports MINT, the AMF may include the Disaster return wait range IE in the CONFIGURATION UPDATE COMMAND message. NOTE 7: The AMF can determine the content of the "list of PLMN(s) to be used in disaster condition", the value of the disaster roaming wait range and the value of the disaster return wait range based on the network local configuration. If the UE supports discontinuous coverage, the AMF may include the Discontinuous coverage maximum time offset IE in the CONFIGURATION UPDATE COMMAND message. If the UE supports and the network supports and accepts the use of the PEIPS assistance information, and the AMF needs to update the PEIPS assistance information, the AMF may include the PEIPS assistance information in the Updated PEIPS assistance information IE of the CONFIGURATION UPDATE COMMAND message.If the AMF needs to inform the UE that the use of access identity 1 is valid or is no longer valid, then, 1) if the UE supports MPS indicator update via the UE configuration update procedure,the AMF: a) informs the UE by setting the MPS indicator bit of the Priority indicator IE to "Access identity 1 valid" or "Access identity 1 not valid" respectively, in the CONFIGURATION UPDATE COMMAND message. Based on operator policy, the AMF sets the MPS indicator bit in the CONFIGURATION UPDATE COMMAND message based on the MPS priority information in the user's subscription context obtained from the UDM; or b) indicates "registration requested" in the Registration requested bit of the Configuration update indication IE in the CONFIGURATION UPDATE COMMAND message; or 2) if the UE supports MCS indicator update via the UE configuration update procedure,the AMF: a) informs the UE by setting the MCS indicator bit of the Priority indicator IE to "Access identity 2 valid" or "Access identity 2 not valid" respectively, in the CONFIGURATION UPDATE COMMAND message. Based on operator policy, the AMF sets the MCS indicator bit in the CONFIGURATION UPDATE COMMAND message based on the MCS priority information in the user's subscription context obtained from the UDM; or b) indicates "registration requested" in the Registration requested bit of the Configuration update indication IE in the CONFIGURATION UPDATE COMMAND message; or 3) otherwise, the AMF shall indicate "registration requested" in the Registration requested bit of the Configuration update indication IE in the CONFIGURATION UPDATE COMMAND message. If the UE has set the Reconnection to the network due to RAN timing synchronization status change (RANtiming) bit to "Reconnection to the network due to RAN timing synchronization status change supported" in the 5GMM capability IE of the REGISTRATION REQUEST message, the AMF may include the RAN timing synchronization IE with the RecReq bit set to "Reconnection requested" in the CONFIGURATION UPDATE COMMAND message. When the UE is operating as an MBSR and its status of the MBSR authorization changes to not authorized for MBSR operation based on the UE subscription and local policy and the UE is allowed to operate as a UE, then the AMF shall include the Feature authorization indication IE in the CONFIGURATION UPDATE COMMAND message and shall set the MBSRAI field to "not authorized to operate as MBSR but allowed to operate as a UE". When the UE that was not allowed for MBSR operation becomes to be allowed for MBSR operation based on the UE subscription and local policy, then the AMF shall include the Feature authorization indication IE in the CONFIGURATION UPDATE COMMAND message and shall set the MBSRAI field to "authorized to operate as MBSR" | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.4.4.2 |
2,556 | 5.6.8 Selective activation and deactivation of UP connection of existing PDU Session | This clause applies to the case when a UE has established multiple PDU Sessions. The activation of a UP connection of an existing PDU Session causes the activation of its UE-CN User Plane connection (i.e. data radio bearer and N3 tunnel). For the activation of a UP connection the service area restrictions as specified in clause 5.3.4.1.1 apply. For the UE in the CM-IDLE state in 3GPP access, either UE or Network-Triggered Service Request procedure may support independent activation of UP connection of existing PDU Session. For the UE in the CM-IDLE state in non-3GPP access, UE-Triggered Service Request procedure allows the re-activation of UP connection of existing PDU Sessions, and may support independent activation of UP connection of existing PDU Session. A UE in the CM-CONNECTED state invokes a Service Request (see clause 4.2.3.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]) procedure to request the independent activation of the UP connection of existing PDU Sessions. Network Triggered re-activation of UP connection of existing PDU Sessions is handled as follows: - If the UE CM state in the AMF is already CM-CONNECTED on the access (3GPP, non-3GPP) associated to the PDU Session in the SMF, the network may re-activate the UP connection of a PDU Session using a Network Initiated Service Request procedure. Otherwise: - If the UE is registered in both 3GPP and non-3GPP accesses and the UE CM state in the AMF is CM-IDLE in non-3GPP access, the UE can be paged or notified through the 3GPP access for a PDU Session associated in the SMF (i.e. last routed) to the non-3GPP access: - If the UE CM state in the AMF is CM-IDLE in 3GPP access, the paging message may include the access type associated with the PDU Session in the SMF. The UE, upon reception of the paging message containing an access type, shall reply to the 5GC via the 3GPP access using the NAS Service Request message, which shall contain the list of PDU Sessions associated with the received access type and whose UP connections can be re-activated over 3GPP (i.e. the list does not contain the PDU Sessions whose UP connections cannot be re-activated on 3GPP based on UE policies and whether the S-NSSAIs of these PDU Sessions are within the Allowed NSSAI for 3GPP access). If the PDU Session for which the UE has been paged is in the list of the PDU Sessions provided in the NAS Service Request and the paging was triggered by pending DL data, the 5GC shall re-activate the PDU Session UP connection over 3GPP access. If the paging was triggered by pending DL signalling, the Service Request succeeds without re-activating the PDU session UP connection over the 3GPP access and the pending DL signalling is delivered to the UE over the 3GPP access; - If the UE CM state in the AMF is CM-CONNECTED in 3GPP access, the notification message shall include the non-3GPP Access Type. The UE, upon reception of the notification message, shall reply to the 5GC via the 3GPP access using the NAS Service Request message, which shall contain the List of Allowed PDU Sessions that can be re-activated over 3GPP or an empty List of Allowed PDU Sessions if no PDU Sessions are allowed to be re-activated over 3GPP access. NOTE: A UE that is in a coverage of a non-3GPP access and has PDU Session(s) that are associated in the UE (i.e. last routed) to non-3GPP access, is assumed to attempt to connect to it without the need to be paged. - If the UE is registered in both 3GPP and non-3GPP accesses served by the same AMF and the UE CM state in the AMF is CM-IDLE in 3GPP access and is in CM-CONNECTED in non 3GPP access, the UE can be notified through the non-3GPP for a PDU Session associated in the SMF (i.e. last routed) to the 3GPP access. The notification message shall include the 3GPP Access Type. Upon reception of the notification message, when 3GPP access is available, the UE shall reply to the 5GC via the 3GPP access using the NAS Service Request message. In addition to the above, a PDU Session may be established as an always-on PDU Session as described in clause 5.6.13. The deactivation of the UP connection of an existing PDU Session causes the corresponding data radio bearer and N3 tunnel to be deactivated. The UP connection of different PDU Sessions can be deactivated independently when a UE is in CM-CONNECTED state in 3GPP access or non-3GPP access. At the deactivation of the UP of a PDU Session using a N9 tunnel whose end-point is controlled by an I-SMF, the N9 tunnel is preserved. If a PDU Session is an always-on PDU Session, the SMF should not deactivate a UP connection of this PDU Session due to inactivity. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.6.8 |
2,557 | 8.1.2.2 Definition of CA capability | The definition with respect to CA capabilities for 2CCs is given as in Table 8.1.2.2-1. The definition with respect to CA capabilities for 3CCs is given in Table 8.1.2.2-3. Table 8.1.2.2-1: Definition of CA capability with 2DL CCs The supported testable aggregated CA bandwidth combinations for 2CCs for each CA capability are listed in Table 8.1.2.2-2. Table 8.1.2.2-2: Supported testable aggregated CA bandwidth combinations for different CA capability with 2DL CCs Table 8.1.2.2-3: Definition of CA capability with 3 DL CCs The supported testable largest aggregated CA bandwidth combinations for 3CCs for each CA capability are listed in Table 8.1.2.2-4. Table 8.1.2.2-4: Supported largest aggregated CA bandwidth combinations for different CA capability with 3 CCs Table 8.1.2.2-5: Definition of CA capability with 4 DL CCs The supported testable largest aggregated CA bandwidth combinations for 4CCs for each CA capability are listed in Table 8.1.2.2-6. Table 8.1.2.2-6: Supported largest aggregated CA bandwidth combinations for different CA capability with 4 CCs Table 8.1.2.2-7: Definition of CA capability with 5 DL CCs The supported testable largest aggregated CA bandwidth combinations for 5CCs for each CA capability are listed in Table 8.1.2.2-8. Table 8.1.2.2-8: Supported largest aggregated CA bandwidth combinations for different CA capability with 5 CCs Table 8.1.2.2-9: Definition of CA capability with 6 DL CCs The supported testable largest aggregated CA bandwidth combinations for 6CCs for each CA capability are listed in Table 8.1.2.2-10. Table 8.1.2.2-10: Supported largest aggregated CA bandwidth combinations for different CA capability with 6 CCs Table 8.1.2.2-11: Definition of CA capability with 7 DL CCs The supported testable largest aggregated CA bandwidth combinations for 7CCs for each CA capability are listed in Table 8.1.2.2-12. Table 8.1.2.2-12: Supported largest aggregated CA bandwidth combinations for different CA capability with 7 CCs For test cases with more than one component carrier, "Fraction of Maximum Throughput" in the performance requirement refers to the ratio of the sum of throughput values of all component carriers to the sum of the nominal maximum throughput values of all component carriers, unless otherwise stated. | 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.1.2.2 |
2,558 | 7.6 Reliable Delivery of Signalling Messages | Retransmission requirements in the current clause do not apply to the Initial messages that do not have Triggered messages. Reliable delivery in GTPv2 messages is accomplished by retransmission of these messages. A message shall be retransmitted if and only if a reply is expected for that message and the reply has not yet been received. There may be limits placed on the total number of retransmissions to avoid network overload. Initial messages and their Triggered messages, as well as Triggered messages and their Triggered Reply messages are matched based on the Sequence Number and the IP address and port rules in clause 4.2 "Protocol stack". Therefore, an Initial message and its Triggered message, as well as a Triggered message and its Triggered Reply message shall have exactly the same Sequence Number value. A retransmitted GTPv2 message (an Initial or a Triggered) has the exact same GTPv2 message content, including the GTP header, UDP ports, source and destination IP addresses as the originally transmitted GTPv2 message. For each triplet of local IP address, local UDP port and remote peer's IP address a GTP entity maintains a sending queue with signalling messages to be sent to that peer. The message at the front of the queue shall be sent with a Sequence Number, and if the message has an expected reply, it shall be held in a list until a reply is received or until the GTP entity has ceased retransmission of that message. The Sequence Number shall be unique for each outstanding Initial message sourced from the same IP/UDP endpoint. A node running GTP may have several outstanding messages waiting for replies. Not counting retransmissions, a single GTP message with an expected reply shall be answered with a single GTP reply, regardless whether it is per UE, per APN, or per bearer A piggybacked initial message (such as a Create Bearer Request message or Modify Bearer Request message) shall contain a Sequence Number that is assigned by sending GTP entity and the message shall be held in a list until a response is received. The response message to a piggybacked initial message may arrive without piggybacking (e.g., Create Bearer Response at PGW). The Sequence Number in the GTP header of the triggered response message shall be copied from the respective request message. If a request message (e.g., Create Session Request) triggers piggybacking (i.e., Create Bearer Request piggybacked on Create Session Response), re-transmission of the request message shall also trigger piggybacking. A Sequence Number used for a Command message shall have the most significant bit set to 1. A Sequence Number in a message, which was triggered by a Command message, as well as respective Triggered Reply message shall have the same Sequence Number as the Command message (i.e. shall also have the most significant bit set to 1). This setting of the most significant bit of the Sequence Number is done to avoid potential clashes between the Sequence Number selected for a Command message, and the Sequence Number selected by a GTPv2 peer for a Request message, which was not triggered by a Command message. A Sequence Number used for a Request message, which was not triggered by a Command message shall have the most significant bit set to 0. A timer, denoted T3-RESPONSE, shall be started when a signalling message (for which a reply is expected) is sent. A signalling message or the triggered message has probably been lost if a reply has not been received before the T3-RESPONSE timer expires. Once the T3-RESPONSE timer expires, the message corresponding to the T3-RESPONSE timer is then retransmitted if the total number of retry attempts is less than N3-REQUESTS times. The expiry of the timer for piggybacked request messages shall result in re-transmission of the original IP/UDP packet containing both the triggered response message and the piggybacked initial message. T3-RESPONSE timer and N3-REQUESTS counter setting is implementation dependent. That is, the timers and counters may be configurable per procedure. Multileg communications (e.g. Create Session Requests and Responses) however require longer timer values and possibly a higher number of retransmission attempts compared to single leg communication. All received GTPv2 messages with an expected reply shall be replied to and all reply messages associated with a certain message shall always include the same information. Duplicated reply messages shall be discarded by the receiver unless the reply needs a reply. A received reply message without a matching outstanding message that is waiting for a reply should be discarded. If a GTPv2 node is not successful with the transfer of a non-Echo signalling message, e.g. a Create Bearer Request message, it shall inform the upper layer of the unsuccessful transfer so that the controlling upper entity may take the necessary measures. NOTE: At failure of sending a GTPv2 message after retransmissions, some information included in the message may be lost, e.g. Secondary RAT data usage report. | 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.6 |
2,559 | 6.1.5 MAC PDU (Random Access Response) | A MAC PDU consists of a MAC header and zero or more MAC Random Access Responses (MAC RAR) and optionally padding as described in figure 6.1.5-4. The MAC header is of variable size. A MAC PDU header consists of one or more MAC PDU subheaders; each subheader corresponding to a MAC RAR except for the Backoff Indicator subheader. If included, the Backoff Indicator subheader is only included once and is the first subheader included within the MAC PDU header. A MAC PDU subheader consists of the three header fields E/T/RAPID (as described in figure 6.1.5-1) but for the Backoff Indicator subheader which consists of the five header field E/T/R/R/BI (as described in figure 6.1.5-2). A MAC RAR consists of the following fields R/Timing Advance Command/UL Grant/(R/ER)/Temporary C-RNTI (as described in figures 6.1.5-3, 6.1.5-3a, 6.1.5-3b and 6.1.5-3c). For BL UEs and UEs in enhanced coverage in enhanced coverage level 2 or 3 (see clause 6.2 in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2]) the MAC RAR in figure 6.1.5-3a is used, for NB-IoT UEs (see clause 16.3.3 in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2]) the MAC RAR in figure 6.1.5-3b is used, except for NB-IoT UEs using preamble format 2, the MAC RAR in figure 6.1.5-3c is used. Otherwise the MAC RAR in figure 6.1.5-3 is used. Padding may occur after the last MAC RAR. Presence and length of padding is implicit based on TB size, size of MAC header and number of RARs. Figure 6.1.5-1: E/T/RAPID MAC subheader Figure 6.1.5-2: E/T/R/R/BI MAC subheader Figure 6.1.5-3: MAC RAR Figure 6.1.5-3a: MAC RAR for PRACH enhanced coverage level 2 or 3 Figure 6.1.5-3b: MAC RAR for NB-IoT UEs Figure 6.1.5-3c: MAC RAR for NB-IoT UEs using PRACH preamble format 2 Figure 6.1.5-4: Example of MAC PDU consisting of a MAC header and MAC RARs | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.1.5 |
2,560 | – VarAppLayerPLMN-LisConfig | The UE variable VarAppLayerPLMN-ListConfig includes the PLMNs to which application layer measurement reports and application layer measurement configurations are allowed to be sent. VarAppLayerPLMN-ListConfig UE variable -- ASN1START -- TAG-VARAPPLAYERPLMN-LISTCONFIG-START VarAppLayerPLMN-ListConfig-r18-IEs ::= SEQUENCE { plmnConfigList-r18 SEQUENCE (SIZE (1..maxNrofAppLayerMeas-r17)) OF VarAppLayerPLMN-List-r18 } VarAppLayerPLMN-List-r18 ::= SEQUENCE { measConfigAppLayerId-r18 MeasConfigAppLayerId-r17, plmn-IdentityList-r18 PLMN-IdentityList2-r16 } -- TAG-VARAPPLAYERPLMN-LISTCONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,561 | 9.11.3.102 Non-3GPP path switching information | The purpose of the Non-3GPP path switching information information element is to request from the network to keep using the user plane resources of the old non-3GPP access during path switching to the new non-3GPP access. The Non-3GPP path switching information information element is coded as shown in figure 9.11.3.102.1 and table 9.11.3.102.1. The Non-3GPP path switching information is a type 4 information element with a length of 3 octets. Figure 9.11.3.102.1: Non-3GPP path switching information information element Table 9.11.3.102.1: Non-3GPP path switching information information element | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.11.3.102 |
2,562 | 5.2.6.35.4 Nnef_TrafficInfluenceData_Notify service operation | Service operation name: Nnef_TrafficInfluenceData_Notify Description: NEF notifies NF consumer(s) about AF traffic influence request information, when receives notification of AF traffic influence request information from UDR. Inputs, Required: Notification Correlation ID, Data Set Identifier as defined in clause 5.2.12.2.1, Target of Event Reporting as defined in clause 5.2.12.2, AF traffic influence request information. Inputs, Optional: None. Outputs, Required: Result Indication. Outputs, Optional: None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.6.35.4 |
2,563 | B.2.1.2.2 EAP TLS with subscription identifier privacy | For EAP TLS, if the operator determines to provide subscription identifier privacy for the UE in TLS layer, the the EAP TLS server needs to support privacy either inherently (e.g., in TLS 1.3) or via separate privacy option (e.g., in TLS 1.2). If privacy is an option in TLS layer, then the operator needs to configure UE with the information that privacy-on-TLS layer is enabled. Further, following considerations need to be taken. In Step 1 of Figure B.2.1-1, it is important that calculation of SUCI, which is sent in NAS layer, is done using schemes other than "null-scheme". Otherwise, the subscription identifier protection provided by TLS layer becomes ineffective privacy-wise. Nevertheless, the "null-scheme" could be used in NAS layer while still preserving subscription identifier privacy, by omitting the username part from NAI as described in RFC 4282 clause 2.3 [y]. It would be analogous to using anonymous identifier in EAP, meaning that only realm part from NAI is included in SUCI which is sent in NAS layer. Thus formed SUCI can still be used to route the authentication request to AUSF. In Step 13 and 14 of Figure B.2.1-1, when TLS 1.2 is used, the UE would need to behave as described in "Section 2.1.4. Privacy" of RFC 5216 [38] where instead of sending the client certificate in cleartext over the air, the UE first sends TLS certificate (no cert) and only later sends TLS certificate after a TLS is setup. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | B.2.1.2.2 |
2,564 | 5.6.2 Scenario | Police respond to a nuisance complaint about a UAV. Network coverage is not good in this area, and so before attempting to query the UTM to see if any have a live UAV in the area the police responding to the report in the local area uses handheld equipment to scan for any UAS broadcasting their identities in the local area. Once such a UAS is found, the police may use the received ID to query the UTM for more information, or the police may use information in the ID message itself to trace the source of the messages (either a UAV of a UAV controller). This could lead to a further request for more data to attempt to make visual contact with (a) the UAV, and (b) the UAV operator. | 3GPP TS 22.825 | Study on Remote Identification of Unmanned Aerial Systems (UAS) | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 5.6.2 |
2,565 | 13.1.2 Protection between SEPPs | TLS shall be used for N32-c connections between the SEPPs. The SEPP shall maintain a set of trust anchors, each consisting of a list of trusted root certificates and a list of corresponding PLMN-IDs. Any given PLMN-ID shall appear in at most one trust anchor. During N32-c connection setup, the SEPP shall map the PLMN-ID of the remote SEPP leaf (server or client) certificate to the associated trust anchor for the purposes of certificate chain verification. Only the root certificates in the associated list shall be treated as trusted during certificate chain verification. If the remote SEPP certificate contains multiple PLMN-IDs that are mapped to different trust anchors, then that certificate shall be rejected. Operator Group Roaming Hubs SEPPs are equivalent to a network operator SEPP when they are in the same security domain and are not considered IPX providers as detailed in this clause. The communication between a group network operator's SBA network border element and the Operator Group Roaming Hub SEPP is out of scope of the present document. If there are no IPX providers between the SEPPs, TLS shall be used for N32-f connections between the SEPPs. Different TLS connections are used for N32-c and N32-f. If there are IPX providers which only offer IP routing service between SEPPs, either TLS or PRINS (application layer security) shall be used for protection of N32-f connections between the SEPPs. PRINS is specified in clause 5.9.3 (requirements) and clause 13.2 (procedures). If TLS is selected, the SEPP shall correlate the N32-f TLS connection with the N32-c connection. If the peer network is a PLMN, the SEPP compares the PLMN-IDs contained in the SEPP TLS certificates used to establish the N32-c and N32-f connections. Specifically, if the certificate used for N32-f contains one or more PLMN-IDs that are not contained in the TLS certificate used for the corresponding N32-c, the N32-f certificate shall be rejected. If the peer network is an SNPN, the SEPP compares the SNPN-ID contained in the SEPP TLS certificates used to establish the N32-c and N32-f connections. If there are IPX providers which, in addition to IP routing, offer other services that require modification or observation of the information and/or additions to the information sent between the SEPPs, PRINS shall be used for protection of N32-f connections between the SEPPs. NOTE 1a: The procedure specified in clause 13.5 for security mechanism selection between SEPPs allows SEPPs to negotiate which security mechanism to use for protecting NF service-related signalling over N32, and provides robustness and future-proofness, e.g. in case new algorithms are introduced in the future. If PRINS is used on the N32-f interface, one of the following additional transport protection methods should be applied between SEPP and IPX provider for confidentiality and integrity protection: - NDS/IP as specified in TS 33.210[ Network Domain Security (NDS); IP network layer security ] [3] and TS 33.310[ Network Domain Security (NDS); Authentication Framework (AF) ] [5], or - TLS VPN with mutual authentication following the profile given in clause 6.2 of TS 33.210[ Network Domain Security (NDS); IP network layer security ] [3] and clause clause 6.1.3a of TS 33.310[ Network Domain Security (NDS); Authentication Framework (AF) ] [5]. The identities in the end entity certificates shall be used for authentication and policy checks, with the restriction that it shall be compliant with the profile given by HTTP/2 as defined in RFC 7540 [47]. NOTE 1: Void NOTE 2: Void. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 13.1.2 |
2,566 | 10.5.4.24 SS Version Indicator | The purpose of the SS version indicator information element is to aid the decoding of the Facility information element as described in 3GPP TS 24.010[ Mobile radio interface layer 3; Supplementary services specification; General aspects ] [21]. Within the scope of 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] the contents of the SS Version information field is an array of one or more octets. The usage of the SS version information field is defined in 3GPP TS 24.080[ Mobile radio interface layer 3 supplementary services specification; Formats and coding ] [24]. The SS version indicator information element is coded as shown in figure 10.5.113/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The SS version indicator is a type 4 information element with a minimum length of 2 octets. No upper length limit is specified except for that given by the maximum number of octets in a L3 message (see 3GPP TS 44.006[ None ] [19]). Figure 10.5.113/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] NOTE: Usually, this information element has only one octet of content. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.4.24 |
2,567 | 6.8.1.1.2.3 Full native 5G NAS security context not available | If in the process described in clause 6.8.1.1.2.2, there is no full native 5G NAS security context available in the AMF (i.e. either the UE has sent an unprotected Registration Request message or the UE has protected the Registration Request message with a current native 5G security context which no longer is stored in the AMF) a primary authentication run is required. If there is a full native 5G NAS security context available in the AMF, then the AMF may (according to AMF policy) decide to run a new primary authentication and a NAS SMC procedure (which activates the new 5G NAS security context based on the KAMF derived during the primary authentication run) after the Registration Request. If the Registration Request was with "PDU session(s) to be re-activated", the NAS SMC procedure is executed before the corresponding AS SMC. The NAS (uplink and downlink) COUNTs are set to start values, and the start value of the uplink NAS COUNT shall be used as freshness parameter in the KgNB/KeNB derivation from the fresh KAMF (after primary authentication) when UE receives AS SMC the KgNB/KeNB is derived from the current 5G NAS security context, i.e., the fresh KAMF is used to derive the KgNB/KeNB. The KDF as specified in clause Annex A shall be used to derive the KgNB/KeNB. NOTE: Using the start value for the uplink NAS COUNT in this case cannot lead to the same combination of KAMF and NAS COUNT being used twice. This is guaranteed by the fact that the first integrity protected NAS message the UE sends to the AMF after primary authentication is the NAS SMC complete message. The NAS SMC complete message shall include the start value of the uplink NAS COUNT that is used as freshness parameter in the KgNB/KeNB derivation and the KAMF is fresh. After a primary authentication, a NAS SMC needs to be sent from the AMF to the UE in order to take the new NAS keys into use. Both NAS SMC and NAS SMC Complete messages are protected with the new NAS keys. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.8.1.1.2.3 |
2,568 | 9.9.3.66 Paging restriction | The purpose of the Paging restriction information element is to request the network to restrict paging. The Paging restriction information element is coded as shown in figure 9.9.3.66.1, figure 9.9.3.66.2 and table 9.9.3.66.1. The Paging restriction is a type 4 information element with a minimum length of 3 octets and a maximum length of 5 octets. Figure 9.9.3.66.1: Paging restriction information element for Paging restriction type = "All paging is restricted" and for Paging restriction type = "All paging is restricted except voice" Figure 9.9.3.66.2: Paging restriction information element for Paging restriction type = "All paging is restricted except for specified PDN connection(s)" and for Paging restriction type = "All paging is restricted except for voice service and specified PDN connection(s)" Table 9.9.3.66.1: Paging restriction information element | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.9.3.66 |
2,569 | 16.4 AAA Server triggered Network Slice-Specific Re-authentication and Re-authorization procedure | Figure 16.4-1: AAA Server initiated Network Slice-Specific Re-authentication and Re-authorization procedure 0. The UE is registered in 5GC via an AMF. The AMF ID is stored in the UDM. 1. The AAA-S requests the re-authentication and re-authorization for the Network Slice specified by the S-NSSAI/ENSI in the Re-Auth Request message, for the UE identified by the GPSI in this message. This message is sent to an AAA-P, if the AAA-P is used (e.g. the AAA Server belongs to a third party), otherwise it may be sent directly to the NSSAAF. If an AAA-P is present, the AAA-P relays the Reauthentication Request to the NSSAAF. 2. The NSSAAF checks whether the AAA-S is authorized to request the re-authentication and re-authorization by checking the local configuration of AAA-S address per S-NSSAI. If success,the NSSAAF requests UDM for the AMF serving the UE using the Nudm_UECM_Get (GPSI, AMF Registration) service operation. The UDM provides the NSSAAF with the AMF ID of the AMF serving the UE. 3. The NSSAAF provides an acknowledgement to the AAA protocol Re-Auth Request message. If the AMF is not registered in UDM the procedure is stopped here. 4. If the AMF is registered in UDM, the NSSAAF requests the relevant AMF to re-authenticate/re-authorize the S-NSSAI for the UE using the Nnssaaf_NSSAA_Re-authenticationNotification service operation. The AMF is implicitly subscribed to receive Nnssaaf_NSSAA_Re-authenticationNotification service operations. The NSSAAF may discover the Callback URI for the Nnssaaf_NSSAA_Re-authenticationNotification service operation exposed by the AMF via the NRF. The AMF acknowledges the notification of Re-authentication request. 5. If the UE is registered with the S-NSSAI in the Mapping Of Allowed NSSAI, the AMF triggers the NSSAA procedure defined in clause 16.3 for the UE identified by the GPSI and the Network Slice identified by the S-NSSAI received from the NSSAAF. If the UE is registered but the S-NSSAI is not in the Mapping Of Allowed NSSAI, the AMF removes any status of the corresponding S-NSSAI subject to Network Slice-Specific Authentication and Authorization in the UE context it may have kept, so that an NSSAA is executed next time the UE requests to register with the S-NSSAI. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 16.4 |
2,570 | 6.1.3.5 Timing Advance Command MAC Control Element | The Timing Advance Command MAC control element is identified by MAC PDU subheader with LCID as specified in table 6.2.1-1. It has a fixed size and consists of a single octet defined as follows (figure 6.1.3.5-1): - TAG Identity (TAG Id): This field indicates the TAG Identity of the addressed TAG. The TAG containing the SpCell has the TAG Identity 0. The length of the field is 2 bits; - Timing Advance Command: This field indicates the index value TA (0, 1, 2… 63) used to control the amount of timing adjustment that MAC entity has to apply (see clause 4.2.3 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2]). The length of the field is 6 bits. Figure 6.1.3.5-1: Timing Advance Command MAC control element | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.1.3.5 |
2,571 | 5.6.4.3 Network initiated transport of NAS messages | Upon request from an application to send a message encapsulated in the generic transport of NAS message, the EMM entity in the MME initiates the procedure by sending a DOWNLINK GENERIC NAS TRANSPORT message including the corresponding message in the generic message container IE. The application may also request additional information to be included in the DOWNLINK GENERIC NAS TRANSPORT message in the Additional information IE. The content, coding and interpretation of this information element are dependent on the particular application. The MME shall indicate the application protocol using the generic transport in the corresponding generic message container type. When receiving the DOWNLINK GENERIC NAS TRANSPORT message, the EMM entity in the UE shall provide the contents of the generic message container IE and the generic message container type IE to the corresponding application. If included, the EMM entity in the UE shall also provide the contents of the Additional information IE. | 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.6.4.3 |
2,572 | 8.2.2.3.4 Minimum Requirement 2 Tx Antenna Port (demodulation subframe overlaps with aggressor cell ABS and CRS assistance information are configured) | The requirements for non-MBSFN ABS are specified in Table 8.2.2.3.4-2, with the addition of parameters in Table 8.2.2.3.4-1. The purpose is to verify the performance of large delay CDD with 2 transmitter antennas if the PDSCH transmission in the serving cell takes place in subframes that overlap with ABS [9] of the aggressor cell with CRS assistance information. In Table 8.2.2.3.4-1, Cell 1 is the serving cell, and Cell 2 and Cell3 are the aggressor cells. The downlink physical channel setup for Cell 1 is according to Annex C.3.2 and for Cell 2 and Cell 3 is according to Annex C.3.3, respectively. The CRS assistance information [7] includes Cell 2 and Cell 3. Table 8.2.2.3.4-1: Test Parameters for Large Delay CDD (FRC) – Non-MBSFN ABS Table 8.2.2.3.4-2: Minimum Performance Large Delay CDD (FRC) – Non-MBSFN ABS | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.2.2.3.4 |
2,573 | 4.2 High level common architecture 4.2.1 General | The architectural differences between the domains (e.g. PS), services (e.g. MMS) and subsystems (e.g. the IMS) affect the way in which the charging functions are embedded within the different domains, services and subsystems. However, the functional requirements for charging are always the same across all domains, services and subsystems. This clause describes a common approach for the definition of the logical charging functions, which provides a ubiquitous logical charging architecture for all 3GPP network domains, subsystems and services that are relevant for charging standardisation. It should be noted that this common charging architecture provides only a common logical view and the actual domain / service / subsystem specific charging architecture depends on the domain / service / subsystem in question. The physical mapping of the common logical architecture onto each domain, subsystem or service is described in the respective middle tier TS, i.e. the TS 32.25[ None ] x, TS 32.26[ None ] xand TS 32.27[ None ] x number ranges. Figure 4.2.1.1 provides an overview of the logical ubiquitous charging architecture and the information flows for offline and online charging, in both referent points and service based interface variants, respectively further detailed in clause 4.2.2 and clause 4.2.3. The common architecture for Network Slice Charging is provided in clause 4.2.4 The common charging functions are detailed further for the reference points variant, in clauses 4.3.1 for offline charging, and clause 4.3.2 for online charging, and for the service based interface variant in clause 4.3.3 for converged online and offline charging. The reference points are further specified in clause 4.4. The service based interface is further specified in clause 4.2.3. Figure 4.2.1.1: Logical ubiquitous charging architecture and information flows | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.2 |
2,574 | 5.5.2.10a RSSI measurement timing configuration | The UE shall setup the RSSI measurement timing configuration (RMTC) in accordance with the received rmtc-Periodicity and, if configured, with rmtc-SubframeOffset i.e. the first symbol of each RMTC occasion occurs at first symbol of an SFN and subframe of the NR SpCell meeting the following condition: SFN mod T = FLOOR(rmtc-SubframeOffset/10); subframe = rmtc-SubframeOffset mod 10; with T = rmtc-Periodicity/10; On the frequency configured by rmtc-Frequency, the UE shall not consider RSSI measurements outside the configured RMTC occasion which lasts for measDurationSymbols for RSSI and channel occupancy measurements. The UE derives the RSSI measurement duration from a combination of measDurationSymbols and ref-SCS-CP. At least for RSSI measurement confined within the active DL BWP, the UE performs RSSI measurement using the numerology of the active DL BWP during the derived measurement duration. Otherwise, the numerology used by the UE for measurements is up to UE implementation. If configured, the UE performs RSSI measurements on a bandwidth in accordance with the received rmtc-Bandwidth. If configured, the UE performs RSSI measurements according to the TCI state configured by tci-StateId in the reference BWP configured by ref-BWPId of the reference serving cell configured by ref-ServCellId (see TS 38.133[ NR; Requirements for support of radio resource management ] [14], clause 9.2A.7 and clause 9.3A.8).If the UE has no serving cell in FR2-2 and configured with inter-frequency RSSI measurement in FR2-2, it is up to the UE implementation how to determine the spatial domain filter for the inter-frequency RSSI measurement in FR2-2. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.5.2.10a |
2,575 | 6.5.4 UE requested bearer resource modification procedure 6.5.4.1 General | The purpose of the UE requested bearer resource modification procedure is for a UE to: a) request a modification; b) release of bearer resources for a traffic flow aggregate; c) modify a traffic flow aggregate by replacing packet filters or adding packet filters; d) re-negotiate header compression configuration associated to an EPS bearer context; e) indicate a change of 3GPP PS data off UE status for a PDN connection; f) transmit information for the C2 authorization for the UAS services; or g) provide a UE policy container with the length of two octets containing the UE STATE INDICATION message (see 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] annex D). When requesting a modification of bearer resources for a traffic flow aggregate or a modification of a traffic flow aggregate, the UE can modify the existing GBR. If accepted by the network, this procedure invokes a dedicated EPS bearer context activation procedure (see clause 6.4.2), an EPS bearer context modification procedure (see clause 6.4.3), or an EPS bearer context deactivation procedure (see clause 6.4.4). If there is a PDN connection for emergency bearer services established, the UE shall not request a modification of bearer resources for this PDN connection. When the UE requested bearer resource modification procedure is used to indicate a change of 3GPP PS data off UE status for a PDN connection (see clause 6.3.10), the UE shall initiate the UE requested bearer resource modification procedure even if the timer T3396 or the back-off timer is running or is deactivated. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.5.4 |
2,576 | 5.2.8.3.2 Nsmf_EventExposure_Notify service operation | Service operation name: Nsmf_EventExposure_Notify Description: Report UE PDU Session related event(s) to the NF which has subscribed to the event report service. Input Required: Event ID, Notification Correlation Information, UE ID(s) (SUPI(s) and if available GPSI(s)), PDU Session ID(s), time stamp. SMF reports multiple PDU Sessions events when those happen at the same time and as indicated in the time stamp. The SMF reports the PDU Session ID, SUPI and if available GPSI(s) per each PDU Session event. Input, Optional: Event specific parameter list as described in clause 5.2.8.3.1, capability of supporting EAS IP replacement in 5GC. Output Required: Result Indication. Output, Optional: Redirection information. When the SMF detects the event subscribed by the NF consumer, the SMF reports the subscribed event together with the Notification Target Address (+ Notification Correlation ID) to the Event Receiving NF. The optional event specific parameter list provides the values that matched for generating the event notification. The parameter values to match are specified during the event subscription (see clause 5.2.8.3.3). See clause 4.3.6.3 for details on usage of this service operation toward Application Function. If the NF consumer is AMF and the result of the service operation fails, the AMF shall set corresponding cause value in result indication which can be used by the SMF for further action. If the related UE is not served by the AMF and the AMF knows which AMF is serving the UE, the AMF provides redirection information which can be used by the SMF to resend UE related message to the AMF that serves the UE. NOTE: In the case of UP plane path, as described in clause 4.3.6.2, this notification can be the result of an implicit subscription of the NEF/AF by the PCF as part of setting PCC rule(s) via the Npcf_SMPolicyControl service (see clause 5.2.5.4). | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.8.3.2 |
2,577 | – CFR-ConfigMCCH-MTCH | The IE CFR-ConfigMCCH-MTCH is used to configure the common frequency resource used for MCCH and MTCH reception. CFR-ConfigMCCH-MTCH information element -- ASN1START -- TAG-CFR-CONFIGMCCH-MTCH-START CFR-ConfigMCCH-MTCH-r17 ::= SEQUENCE { locationAndBandwidthBroadcast-r17 LocationAndBandwidthBroadcast-r17 OPTIONAL, -- Need S pdsch-ConfigMCCH-r17 PDSCH-ConfigBroadcast-r17 OPTIONAL, -- Need S commonControlResourceSetExt-r17 ControlResourceSet OPTIONAL -- Cond NotSIB1CommonControlResource } LocationAndBandwidthBroadcast-r17 ::= CHOICE { sameAsSib1ConfiguredLocationAndBW NULL, locationAndBandwidth INTEGER (0..37949) } -- TAG-CFR-CONFIGMCCH-MTCH-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,578 | 4.1.1.4 Core Network System Information for GMM (Iu mode only) 4.1.1.4.1 General | In the network broadcast system information some of the system information is used by GMM. At reception of new system information, the RRC layer in the MS delivers the contents of the CN common system information and the PS domain specific system information to the GMM layer in the MS. The Core Network system information is included in specific information elements within some RRC messages sent to MS (see 3GPP TS 25.331[ None ] [23c] and 3GPP TS 44.118[ None ] [111]). In the Core Network system information the Common system information part and the PS domain specific system information part contains settings of parameters controlling GMM functionality. No GMM messages contain the Core Network System Information. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.1.1.4 |
2,579 | 6.2.2 SMF | The Session Management function (SMF) includes the following functionality. Some or all of the SMF functionalities may be supported in a single instance of a SMF: - Session Management e.g. Session Establishment, modify and release, including tunnel maintain between UPF and AN node. - UE IP address allocation & management (including optional Authorization). The UE IP address may be received from a UPF or from an external data network. - DHCPv4 (server and client) and DHCPv6 (server and client) functions. - Functionality to respond to Address Resolution Protocol (ARP) requests and / or IPv6 Neighbour Solicitation requests based on local cache information for the Ethernet PDUs. The SMF responds to the ARP and / or the IPv6 Neighbour Solicitation Request by providing the MAC address corresponding to the IP address sent in the request. - Selection and control of UP function, including controlling the UPF to proxy ARP or IPv6 Neighbour Discovery, or to forward all ARP/IPv6 Neighbour Solicitation traffic to the SMF, for Ethernet PDU Sessions. - Configures traffic steering at UPF to route traffic to proper destination. - 5G VN group management, e.g. maintain the topology of the involved PSA UPFs, establish and release the N19 tunnels between PSA UPFs, configure traffic forwarding at UPF to apply local switching, N6-based forwarding or N19-based forwarding, manage traffic forwarding in the case that a SMF Set or multiple SMF Sets are serving a 5G VN. - Termination of interfaces towards Policy control functions. - Lawful intercept (for SM events and interface to LI System). - Support for charging. - Control and coordination of charging data collection at UPF. - Termination of SM parts of NAS messages. - Downlink Data Notification. - Initiator of AN specific SM information, sent via AMF over N2 to AN. - Determine SSC mode of a session. - Support for Control Plane CIoT 5GS Optimisation. - Support of header compression. - Act as I-SMF in deployments where I-SMF can be inserted, removed and relocated. - Provisioning of external parameters (Expected UE Behaviour parameters or Network Configuration parameters). - Support P-CSCF discovery for IMS services. - Act as V-SMF with following roaming functionalities: - Handle local enforcement to apply QoS SLAs (VPLMN). - Charging (VPLMN). - Lawful intercept (in VPLMN for SM events and interface to LI System). - Support for interaction with external DN for transport of signalling for PDU Session authentication/authorization by external DN. - Instructs UPF and NG-RAN to perform redundant transmission on N3/N9 interfaces. - Generation of the TSC Assistance Information based on the TSC Assistance Container received from the PCF. - Support for RAN feedback for BAT offset and adjusted periodicity as defined in clause 5.27.2.5. NOTE: Not all of the functionalities are required to be supported in an instance of a Network Slice. In addition to the functionalities of the SMF described above, the SMF may include policy related functionalities as described in clause 6.2.2 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. In addition to the functionality of the SMF described above, the SMF may include the following functionality to support monitoring in roaming scenarios: - Normalization of reports according to roaming agreements between VPLMN and HPLMN; and - Generation of charging information for Monitoring Event Reports that are sent to the HPLMN. The SMF may also include following functionalities to support Edge Computing enhancements (further defined in TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [130]): - Selection of EASDF and provision of its address to the UE as the DNS Server for the PDU session; - Usage of EASDF services as defined in TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [130]; - For supporting the Application Layer Architecture defined in TS 23.558[ Architecture for enabling Edge Applications ] [134]: Provision and updates of ECS Address Configuration Information to the UE. The SMF and SMF+ PGW-C may also include following functionalities to support Network Slice Admission Control: - Support of NSAC for maximum number of PDU sessions as defined in clauses 5.15.11.2, 5.15.11.3 and 5.15.11.5. - Support of NSAC for maximum number of UEs as defined in clauses 5.15.11.3 and 5.15.11.5. - Support of PDU Set based QoS handling as described in clause 5.37.5. The SMF may also include following functionalities: - Providing per-QoS flow Non-3GPP QoS assistance information to the UE (e.g. PEGC) and formulation of the CN PDB based on non-3GPP delay budget from UE (e.g. PEGC) as described in clause 5.44.3.4. In addition to the functionalities of the SMF described above, the SMF may also include functionalities to support Network Slice Replacement as described in clause 5.15.19. The SMF may also include functionalities to support indirect UPF event exposure service subscription on behalf of the consumer NF(s) as described in clause 4.15.4.5 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.2.2 |
2,580 | 5.4.4 Identification procedure 5.4.4.1 General | The identification procedure is used by the network to request a particular UE to provide specific identification parameters, e.g. the International Mobile Subscriber Identity (IMSI) or the International Mobile Equipment Identity (IMEI). IMEI and IMSI definition and structure are specified in 3GPP TS 23.003[ Numbering, addressing and identification ] [2]. For mobile device supporting both 3GPP access and cdma2000® access a single IMEI is used to identify the device as specified in 3GPP TS 22.278[ Service requirements for the Evolved Packet System (EPS) ] [1C]. If the UE is a MUSIM UE, the UE uses a separate IMEI for each USIM the UE operates. | 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.4.4 |
2,581 | 9.3.8.1.2 TDD | For the parameters specified in Table 9.3.8.1.2-1, and using the downlink physical channels specified in Annex C, the minimum requirements are specified in 9.3.8.1.2-2 and by the following a) the ratio of the throughput obtained when transmitting the transport format indicated by each reported wideband CQI index subject to interference sources with NeighCellsInfo-r12 configured and that obtained when transmitting the transport format indicated by each reported wideband CQI index subject to interference sources without NeighCellsInfo-r12 configured shall be ≥ ; Table 9.3.8.1.2-1 Fading test for TDD Table 9.3.8.1.2-2 Minimum requirement (TDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.3.8.1.2 |
2,582 | 6.1 Overview | The smallest time-frequency unit for downlink transmission is denoted a resource element and is defined in clause 6.2.2. A subset of the downlink subframes in a radio frame can be configured as MBSFN subframes by higher layers. For the MBSFN region is defined as one slot of 3 ms. Except for , each MBSFN subframe is divided into a non-MBSFN region and an MBSFN region. - For subframes using , the non-MBSFN region spans the first one or two OFDM symbols in an MBSFN subframe where the length of the non-MBSFN region is given according to Clause 6.7. - For subframes using , , , or slots using , the non-MBSFN region is of zero size. - The MBSFN region in an MBSFN subframe is defined as the OFDM symbols not used for the non-MBSFN region. For an MBMS-dedicated cell, subframes where PSS/SSS/PBCH or PDSCH carrying system information are transmitted with are non-MBSFN subframes. For frame structure type 3, MBSFN configuration shall not be applied to downlink subframes in which at least one OFDM symbol is not occupied or discovery signal is transmitted. Unless otherwise specified, transmission in each downlink subframe shall use the same cyclic prefix length as used for downlink subframe #0. | 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.1 |
2,583 | 5.2.6.7.4A Nnef_TrafficInfluence_Get operation | Service operation name: Nnef_TrafficInfluence_Get Description: Get the current traffic influence parameters. Inputs, Required: AF Transaction Id. The AF Transaction Id refers to the request. Inputs, Optional: The address (IP or Ethernet) of the UE if available, GPSI if available, DNN if available, S-NSSAI if available, External Group Identifier if available, External Application Identifier or traffic filtering information, AF-Service-Identifier, a list of DNAI(s) and corresponding routing profile ID(s) or N6 traffic routing information. Outputs, Required: Operation execution result indication, requested data. Outputs, Optional: None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.6.7.4A |
2,584 | 5.17.7.2.3 Relaying | The AMF performs relaying between N2 and N26 messages as described in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [34] and TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [101]. The MME performs relaying between S1 and N26 message as described in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [100] and TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [101]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.17.7.2.3 |
2,585 | 9.11.3.86 Extended CAG information list | The purpose of the Extended CAG information list information element is to provide "CAG information list" or to delete the "CAG information list" at the UE. The Extended CAG information list information element is coded as shown in figures 9.11.3.86.1, figure 9.11.3.86.2, figure 9.11.3.86.3, figure 9.11.3.86.4, figure 9.11.3.86.5 and table 9.11.3.86.1. The Extended CAG information list is a type 6 information element, with a minimum length of 3 octets. Figure 9.11.3.86.1: Extended CAG information list information element NOTE: The field is placed immediately after the last present preceding field. Figure 9.11.3.86.2: Entry n Figure 9.11.3.86.3: CAG-ID with additional information list NOTE: The field is placed immediately after the last present preceding field. Figure 9.11.3.86.4: CAG-ID with additional information Figure 9.11.3.86.5: Time validity infomation Table 9.11.3.86.1: Extended 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.86 |
2,586 | 4.7.2 Protocol Stacks | Fig. 4.7.2-1 shows the protocol stack for F1-U and Fig. 4.7.2-2 shows the protocol stack for F1-C between IAB-DU and IAB-donor-CU. In these figures, F1-U and F1-C are carried over two backhaul hops. F1-U and F1-C use an IP transport layer between IAB-DU and IAB-donor-CU as defined in TS 38.470[ NG-RAN; F1 general aspects and principles ] [32]. F1-U and F1-C need to be security-protected as described in TS 33.501[ Security architecture and procedures for 5G System ] [5] (the security layer is not shown in the Figures 4.7.2-1/2). On the wireless backhaul, the IP layer is carried over the Backhaul Adaptation Protocol (BAP) sublayer, which enables routing over multiple hops. The IP layer can also be used for non-F1 traffic, such as OAM traffic as defined in TS 38.401[ NG-RAN; Architecture description ] [4]. On each backhaul link, the BAP PDUs are carried by BH RLC channels. Multiple BH RLC channels can be configured on each BH link to allow traffic prioritization and QoS enforcement. The BH-RLC-channel mapping for BAP PDUs is performed by the BAP entities on each IAB-node and the IAB-donor-DU. Protocol stacks for an IAB-donor with split gNB architecture are specified in TS 38.401[ NG-RAN; Architecture description ] [4]. Fig. 4.7.2-1: Protocol stack for the support of F1-U protocol Fig. 4.7.2-2: Protocol stack for the support of F1-C protocol The IAB-MT further establishes SRBs (carrying RRC and NAS) with the IAB-donor-CU. For IAB-nodes operating in EN-DC, the IAB-MT establishes one or more DRBs with the eNB and one or more DRBs with the IAB-donor-CU, which can be used, e.g., to carry OAM traffic. For SA mode, the establishment of DRBs is optional. These SRBs and DRBs are transported between the IAB-MT and its parent node over Uu access channel(s). The protocol stacks for the SRB is shown in Fig. 4.7.2-3. Figure 4.7.2-3: Protocol stack for the support of IAB-MT's RRC and NAS connections | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 4.7.2 |
2,587 | 9.3.2.1.2 TDD | For the parameters specified in Table 9.3.2.1.2-1, and using the downlink physical channels specified in Annex C.3.2, the minimum requirements are specified in Table 9.3.2.1.2-2 and by the following a) a CQI index not in the set {median CQI -1, median CQI, median CQI +1} shall be reported at least % of the time; b) the ratio of the throughput obtained when transmitting the transport format indicated by each reported wideband CQI index and that obtained when transmitting a fixed transport format configured according to the wideband CQI median shall be ≥ ; c) when transmitting the transport format indicated by each reported wideband CQI index, the average BLER for the indicated transport formats shall be greater or equal to 0.02. Table 9.3.2.1.2-1 Fading test for single antenna (TDD) Table 9.3.2.1.2-2 Minimum requirement (TDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.3.2.1.2 |
2,588 | 4.16.8.6 CHF report the removal of the subscriber | This clause describes the signalling flow for the CHF to report the removal of the subscriber. Figure 4.16.8.6-1: CHF report the removal of the subscriber 1. The CHF decides that a subscriber is removed. 2. The CHF sends the Nchf_SpendingLimitControl_Notify Request to H-PCF to notify the removal of the subscriber. The H-PCF removes the subscription to notification of policy counter status from CHF. NOTE: Notification on the removing of a subscriber causes the H-PCF to make the applicable policy decision and act accordingly. 3. The H-PCF responds to CHF using Nchf_SpendingLimitControl_Notify to acknowledge the receiving of the notification. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.16.8.6 |
2,589 | 6.3.1.3.1 PDU EAP result message transport procedure initiation | PDU EAP result message transport procedure is initiated by the SMF if the PDU session authentication and authorization procedure is performed after the PDU session is established and the DN authentication of the UE completes successfully. In order to initiate the PDU EAP result message transport procedure, the SMF shall create a PDU SESSION AUTHENTICATION RESULT message. The SMF shall set the PTI IE of the PDU SESSION AUTHENTICATION RESULT message to "No procedure transaction identity assigned". The SMF shall set the EAP message IE of the PDU SESSION AUTHENTICATION RESULT message to the EAP-success message provided by the DN. The SMF shall send the PDU SESSION AUTHENTICATION RESULT message. Upon receipt of a PDU SESSION AUTHENTICATION RESULT message and a PDU session ID, using the NAS transport procedure as specified in subclause 5.4.5, the UE passes to the upper layers the EAP message received in the EAP message IE of the PDU SESSION AUTHENTICATION RESULT message. Apart from this action, the authentication and authorization procedure initiated by the DN is transparent to the 5GSM layer of the UE. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.3.1.3.1 |
2,590 | 9.6.1.2 TDD | The following requirements apply to UE Category ≥3. For CA with 2 DL CC, for the parameters specified in Table 9.6.1.2-1 and Table 9.6.1.2-2, and using the downlink physical channels specified in tables C.3.2-1 and C.3.2-2 on each cell, the difference between the wideband CQI indices of Pcell and Scell reported shall be such that wideband CQIPcell – wideband CQIScell ≥ 2 for more than 90% of the time. Table 9.6.1.2-1: PUCCH 1-0 static test on multiple cells (TDD, 2 DL CA) Table 9.6.1.2-2: PUCCH 1-0 static test (TDD, 2 DL CA) The following requirements for 3DL CA apply to UE Category ≥5. For CA with 3 DL CC, for the parameters specified in Table 9.6.1.2-3 and Table 9.6.1.2-4, and using the downlink physical channels specified in tables C.3.2-1 and C.3.2-2 on each cell, the difference between the wideband CQI indices of PCell and SCell1 reported, and the difference between the wideband CQI indices of SCell 1 and SCell2 reported shall be such that wideband CQIPCell – wideband CQISCell1 ≥ 2 wideband CQISCell1 – wideband CQISCell2 ≥ 2 for more than 90% of the time. The following requirements for 4DL CA apply to UE Category ≥8. For CA with 4 DL CC, for the parameters specified in Table 9.6.1.2-3 and Table 9.6.1.2-5, and using the downlink physical channels specified in tables C.3.2-1 and C.3.2-2 on each cell, the difference between the wideband CQI indices of PCell and SCell1 reported, and the difference between the wideband CQI indices of SCell 1 and SCell2, and SCell 1 and SCell 3 reported shall be such that wideband CQIPCell – wideband CQISCell1 ≥ 2 wideband CQISCell1 – wideband CQISCell2 ≥ 2 wideband CQISCell1 – wideband CQISCell3 ≥ 2 for more than 90% of the time. Table 9.6.1.2-3: PUCCH 1-0 static test on multiple cells (TDD, 3 and 4 DL CA) Table 9.6.1.2-4: PUCCH 1-0 static test (TDD, 3 DL CA) Table 9.6.1.2-5: PUCCH 1-0 static test (TDD, 4 DL CA) The following requirements for 5DL CA apply to UE Category 8 and ≥11. For CA with 5 DL CC, for the parameters specified in Table 9.6.1.2-6 and Table 9.6.1.2-7, and using the downlink physical channels specified in tables C.3.2-1 and C.3.2-2 on each cell, the difference between the wideband CQI indices of PCell and SCell1 reported, and the difference between the wideband CQI indices of SCell 1 and SCell2, SCell 1 and SCell 3, and SCell 1 and SCell 4 reported shall be such that wideband CQIPCell – wideband CQISCell1 ≥ 2 wideband CQISCell1 – wideband CQISCell2 ≥ 2 wideband CQISCell1 – wideband CQISCell3 ≥ 2 wideband CQISCell1 – wideband CQISCell4 ≥ 2 for more than 90% of the time. Table 9.6.1.2-6: Parameters for PUCCH 1-0 static test on multiple cells (TDD, 5 DL CA) Table 9.6.1.2-7: PUCCH 1-0 static test (TDD, 5 DL CA) The following requirements for 6DL CA apply to UE Category 8 and ≥11. For CA with 6 DL CC, for the parameters specified in Table 9.6.1.2-8 and Table 9.6.1.2-9, and using the downlink physical channels specified in tables C.3.2-1 and C.3.2-2 on each cell, the difference between the wideband CQI indices of PCell and SCell1 reported, and the difference between the wideband CQI indices of SCell 1 and SCell2, SCell 1 and SCell 3, SCell 1 and SCell 4, and SCell 1 and SCell 5 reported shall be such that wideband CQIPCell – wideband CQISCell1 ≥ [2] wideband CQISCell1 – wideband CQISCell2 ≥ [2] wideband CQISCell1 – wideband CQISCell3 ≥ [2] wideband CQISCell1 – wideband CQISCell4 ≥ [2] wideband CQISCell1 – wideband CQISCell5 ≥ [2] for more than 90% of the time. Table 9.6.1.2-8: Parameters for PUCCH 1-0 static test on multiple cells (TDD, 6 DL CA) Table 9.6.1.2-9: PUCCH 1-0 static test (TDD, 6 DL CA) The following requirements for 7DL CA apply to UE Category 8 and ≥11. For CA with 7 DL CC, for the parameters specified in Table 9.6.1.2-10 and Table 9.6.1.2-11, and using the downlink physical channels specified in tables C.3.2-1 and C.3.2-2 on each cell, the difference between the wideband CQI indices of PCell and SCell1 reported, and the difference between the wideband CQI indices of SCell 1 and SCell2, SCell 1 and SCell 3, SCell 1 and SCell 4, SCell 1 and SCell 5, SCell 1 and SCell 6 reported shall be such that wideband CQIPCell – wideband CQISCell1 ≥ [2] wideband CQISCell1 – wideband CQISCell2 ≥ [2] wideband CQISCell1 – wideband CQISCell3 ≥ [2] wideband CQISCell1 – wideband CQISCell4 ≥ [2] wideband CQISCell1 – wideband CQISCell5 ≥ [2] wideband CQISCell1 – wideband CQISCell6 ≥ [2] for more than 90% of the time. Table 9.6.1.2-10: Parameters for PUCCH 1-0 static test on multiple cells (TDD, 7 DL CA) Table 9.6.1.2-11: PUCCH 1-0 static test (TDD, 7 DL CA) | 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.6.1.2 |
2,591 | 6.15a.6.1 Description | This clause addresses requirements to the 5G system that leverage energy-related information (e.g., energy consumption, energy efficiency), amongst others (e.g., network load), as criteria for network internal optimization actions targeting energy savings, within and across operators in a localized (i.e., geographically bound) and/or temporal (i.e., time bound) manner. One of the strategies to save energy within mobile networks is to shut down some RAN nodes at times of low usage. Eventually only one communication service could be used on a local basis among operators at times of low usage, as further energy saving gain to be exploited. Agreements could be put in place between operators so that in the low load periods (e.g., nighttime) only one of multiple mobile networks may be active in an area and will provide communication service to the subscribers of all networks, whereas the other networks can apply cell shutdown of their own infrastructure to obtain network energy savings. Alternatively, based on risks of power outage nation-wide/region-wide, regulators could ask operators to “optimize” their coverage e.g., shutdown some nodes in overlapping coverage areas during energy peak hours and/or in specific geographical areas, whilst still guaranteeing minimum coverage/service (in particular emergency calls). This can also apply between NPN operators and/or with PLMN operators. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.15a.6.1 |
2,592 | 5.8.9.11 Sidelink UE information 5.8.9.11.1 General | Figure 5.8.9.11.1-1: Sidelink UE information procedure This purpose of this procedure is to transfer the UE information in sidelink. The L2 U2U Remote UE informs its end-to-end QoS information to its connected L2 U2U Relay UE in the UEInformationRequestSidelink message, and the L2 U2U Relay UE delivers the split QoS information of the first-hop to the Remote UE in the UEInformationResponseSidelink message. Editor's Note: Whether this message arrangement is optimal can be discussed in maintenance. Whether to cover the case the Relay UE updates the QoS split can be discussed in maintenance. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.9.11 |
2,593 | 10.5.3.10 CTS permission | The purpose of the CTS permission information element is to indicate that the mobile station is allowed to use GSM-Cordless Telephony System in the Location Area. The CTS permission information element is coded as shown in figure 10.5.84a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The CTS permission is a type 2 information element. Figure 10.5.84a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] CTS permission 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.3.10 |
2,594 | 4.7.3.2.3 Combined GPRS attach accepted by the network | Depending on the value of the attach result IE received in the ATTACH ACCEPT message, two different cases can be distinguished: Case 1) The attach result IE value indicates "combined GPRS attach": IMSI attach for GPRS and non-GPRS services have been successful. Case 2) The attach result IE value indicates "GPRS only": IMSI attach for GPRS services has been successful but IMSI attach for non-GPRS services has not been successful. In Iu mode, if the network wishes to prolong the PS signalling connection (for example, if the mobile station has indicated "follow-on request pending" in ATTACH REQUEST message) the network shall indicate the "follow-on proceed" in the ATTACH ACCEPT message. If the network wishes to release the PS signalling connection, the network shall indicate "no follow-on proceed" in the ATTACH ACCEPT message. After that in Iu mode, the mobile station shall act according to the follow-on proceed flag included in the Attach result information element in the ATTACH ACCEPT message (see subclause 4.7.13). 4.7.3.2.3.1 Combined attach successful for GPRS and non-GPRS services The description for IMSI attach for GPRS services as specified in subclause 4.7.3.1.3 shall be followed. In addition, the following description for IMSI attach for non-GPRS services applies. The TMSI reallocation may be part of the combined GPRS attach procedure. The TMSI allocated is then included in the ATTACH ACCEPT message together with the location area identification (LAI). The network shall, in this case, change to state GMM-COMMON-PROCEDURE-INITIATED and shall start timer T3350 as described in subclause 4.7.6. The MS, receiving an ATTACH ACCEPT message, stores the received location area identification, stops timer T3310, reset the location update attempt counter and sets the update status to U1 UPDATED. If the message contains an IMSI, the mobile station is not allocated any TMSI, and shall delete any TMSI accordingly. If the message contains a TMSI, the MS shall use this TMSI as the new temporary identity. The MS shall delete its old TMSI and shall store the new TMSI. In this case, an ATTACH COMPLETE message is returned to the network. If neither a TMSI nor an IMSI has been included by the network in the ATTACH ACCEPT message, the old TMSI, if any available, shall be kept. The new MM state is MM IDLE, the new GMM state is GMM-REGISTERED. If the MS maintains a counter for "SIM/USIM considered invalid for non-GPRS services" events (see subclause 4.1.1.6A), then the MS shall reset this counter. If the network has requested the provision of Inter RAT handover information, the MS shall return an ATTACH COMPLETE message including the Inter RAT handover information IE to the network. If the MS is not configured for NAS signalling low priority then the MS may stop timer T3246 if running. Any timer used for triggering the location update procedure (e.g T3211, T3212) shall be stopped if running. The network receiving an ATTACH COMPLETE message stops timer T3350, changes to state GMM-REGISTERED. NOTE: Upon receiving an ATTACH COMPLETE message, the SGSN sends a BSSAP+-TMSI-REALLOCATION-COMPLETE message as specified in 3GPP TS 29.018[ General Packet Radio Service (GPRS); Serving GPRS Support Node (SGSN) - Visitors Location Register (VLR); Gs interface layer 3 specification ] [149]. 4.7.3.2.3.2 Combined attach successful for GPRS services only Apart from the actions on the routing area updating attempt counter, the description for IMSI attach for GPRS services as specified in subclause 4.7.3.1.3 shall be followed. In addition, the following description for IMSI attach for non-GPRS services applies. The SGSN shall use GMM cause #28 "SMS provided via GPRS in this routing area" in the ATTACH ACCEPT message only if the MS requested "SMS-only service" by including the Additional update type IE in the ATTACH REQUEST message. The MS receiving the ATTACH ACCEPT message takes one of the following actions depending on the GMM cause: # 2 (IMSI unknown in HLR) The MS shall stop timer T3310 if still running and shall reset the routing area updating attempt counter. The MS shall set the update status to U3 ROAMING NOT ALLOWED and shall delete any TMSI, LAI and ciphering key sequence number. The MS shall enter state GMM-REGISTERED.NORMAL-SERVICE. The new MM state is MM IDLE. The SIM/USIM shall be considered as invalid for non-GPRS services until switching off or the SIM/USIM is removed. If the message has been successfully integrity checked by the lower layers and the MS maintains a counter for "SIM/USIM considered invalid for non-GPRS services", then the MS shall set this counter to MS implementation-specific maximum value. # 16 (MSC temporarily not reachable); or # 17 (Network failure) The MS shall stop timer T3310 if still running, and shall enter state MM-IDLE. The routing area updating attempt counter shall be incremented. If the routing area updating attempt counter is less than 5, and the stored RAI is equal to the RAI of the current serving cell and the GMM update status is equal to GU1 UPDATED: - the MS shall keep the GMM update status GU1 UPDATED and changes state to GMM-REGISTERED.ATTEMPTING-TO-UPDATE-MM. The MS shall start timer T3311. When timer T3311 expires the combined routing area update procedure indicating "combined RA/LA updating with IMSI attach" is triggered again. If the routing area updating attempt counter is greater than or equal to 5: - the MS shall start timer T3302 and shall change to state GMM-REGISTERED.ATTEMPTING-TO-UPDATE-MM; - a GPRS MS operating in MS operation mode A shall then proceed with appropriate MM specific procedure; a GPRS MS operating in MS operation mode B may then proceed with appropriate MM specific procedures. The MM sublayer shall act as in network operation mode II as long as the combined GMM procedures are not successful and no new RA is entered. # 22 (Congestion) The MS shall change to state GMM-REGISTERED.ATTEMPTING-TO-UPDATE-MM, shall stop timer T3310 if still running, and shall enter state MM-IDLE. The MS shall set the routing area updating attempt counter to 5 and shall start the timer T3302. # 28 (SMS provided via GPRS in this routing area); The MS shall stop timer T3310 if still running and shall reset the routing area updating attempt counter. The MS shall set the update status to U3 ROAMING NOT ALLOWED and shall delete any TMSI, LAI and ciphering key sequence number. The MS shall enter state GMM-REGISTERED.NORMAL-SERVICE. The new MM state is MM IDLE. The MS stays in the current serving cell and applies the normal cell reselection process. Other GMM causevalues and the case that no GMM cause IE was received are considered as abnormal cases. The combined attach procedure shall be considered as failed for non-GPRS services. The behaviour of the MS in those cases is specified in subclause 4.7.3.2.5. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.3.2.3 |
2,595 | 4.3.17.8.3 Delivery mechanism | 4.3.17.8.3.1 General At each PDN connectivity request, the MME decides which delivery mechanism (SCEF based delivery or SGi based delivery) is used for delivering the Non-IP data between RAN and AS. An indication associated with the used APN determines if SCEF based delivery or SGi based delivery shall be used. 4.3.17.8.3.2 SCEF based delivery When the MME decides to use SCEF based delivery mechanism for Non-IP data, a PDN connection is established towards the selected SCEF. Such a PDN Connection is also known as an "SCEF Connection". The APN used for SCEF based delivery is an FQDN, which either resolves to an SCEF hostname or to an SCEF IP address. The SCEF based delivery is applicable only to the Control Plane CIoT EPS Optimisation (see clause 4.10). The support of Non-IP data via the SCEF is further defined in TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [74]. 4.3.17.8.3.3 SGi based delivery 4.3.17.8.3.3.1 General When support of Non-IP data is provided at the SGi interface, different point-to-point tunnelling techniques may be used. Point-to-point tunnelling by UDP/IP encapsulation can be used as described in clause 4.3.17.8.3.3.2 below. Other techniques as described in clause 4.3.17.8.3.3 below may be used. Support for the SGi based delivery of Non-IP data can be used by any UE. That is, it is independent of support for the User Plane CIoT EPS Optimisation and the Control Plane CIoT EPS Optimisation (see clause 4.10). The P-GW decides at PDN connection establishment based on pre-configuration which point-to-point tunnelling technique is used for the SGi based delivery between the P-GW and the AS. NOTE: The pre-configuration can be done in the P-GW per APN or based on other criterion such as SLA between operator and 3rd party application service provider, etc. 4.3.17.8.3.3.2 SGi PtP tunnelling based on UDP/IP SGi PtP tunnelling based on UDP/IP may be used to deliver Non-IP data to AS via SGi. A point-to-point tunnel is used by the P-GW towards the AS. The tunnel parameters (i.e. destination IP address and UDP port) for SGi PtP tunnelling based on UDP/IP are pre-configured on the P-GW. IP address allocation procedures for PDN connections are performed locally (e.g. without involving the UE) by the P-GW based on APN configuration and according to clause 5.3.1. Only single IP address is used (i.e. both IPv4 and IPv6 addresses are not allocated). The P-GW acts as a transparent forwarding node for the payload between the UE and the AS. For uplink Non-IP data, the P-GW forwards the received data to the AS over the SGi PtP tunnel using UDP/IP encapsulation. When the Reliable Data Service is enabled, the P-GW processes the Reliable Data Service Header. The Reliable Data Service Configuration is pre-configured on the P-GW. The Reliable Data Service Configuration is defined in TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [74]. For downlink Non-IP data, the AS sends the data using UDP/IP encapsulation with the IP address of the UE and the 3GPP defined UDP port for "Non-IP" data. The P-GW decapsulates the received data (i.e. removes the UDP/IP headers) and forwards the data to S-GW on the GTP-U tunnel identified by the IP address of the UE (i.e. PDN connection) for delivery to the UE. When the Reliable Data Service is enabled, the P-GW adds the Reliable Data Service Header. The P-GW performs the IP related operations (e.g. allocates IP address for the PDN connection), but the IP address or IP prefix is not provided to the UE (i.e. SLAAC / Router Advertisements are not performed. DHCP or DHCPv6 are not used). In the case of IPv6 the P-GW assigns an Interface Identifier for the PDN connection. The allocated IP address or IPv6 prefix identifies the PDN connection of the UE. The P-GW shall inform the MME of the assigned IPv4 address or IPv6 prefix and Interface Identifier for a PDN Connection of a given UE. However, the UE is not informed about the assigned IPv6 prefix and Interface Identifier. NOTE: It is recommended to use IPv6 for CIoT. IPv4 based addressing is deprecated for machine type communication used over 3GPP accesses, see TS 23.221[ Architectural requirements ] [27]. 4.3.17.8.3.3.3 Other SGi PtP tunnelling mechanisms SGi PtP tunnelling mechanisms such as PMIPv6/GRE, L2TP, GTP-C/U, etc, may be used to deliver Non-IP data to AS via SGi. The general handling of such delivery mechanisms is as described below. A point-to-point tunnel is established by the P-GW towards the AS. Depending on the type of protocol employed on the SGi PtP tunnel, the SGi PtP tunnel setup may be done at the time of Attach or at the time of first MO datagram being sent by the CIoT UE. The P-GW selects the AS based on the P-GW configuration (e.g. per APN, or per PtP tunnel type etc.). However, IP address allocation procedures for the UE (according to clause 5.3.1) are not performed by the P-GW. NOTE: An AS can be dedicated for handling a specific Non-IP data protocol. The P-GW acts as a transparent forwarding node between the UE and the AS. For uplink Non-IP data, the P-GW forwards the received data to the AS over the established SGi PtP tunnel. For downlink Non-IP data, the AS locates the right SGi PtP tunnel for the UE (using information such as UE identifiers in the Non-IP protocol itself, etc) to forward the data. The AS sends the data to P-GW over the established SGi PtP tunnel. The P-GW in turn sends the data to S-GW on the GTP-U tunnel identified by the associated SGi PtP tunnel for delivery to the UE. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3.17.8.3 |
2,596 | 9.11.3.9 5GS tracking area identity list | The purpose of the 5GS tracking area identity list information element is to transfer a list of tracking areas from the network to the UE. The coding of the information element allows combining different types of lists. The lists of type "00" and "01" allow a more compact encoding, when the different TAIs are sharing the PLMN identity. The 5GS tracking area identity list information element is coded as shown in figure 9.11.3.8.1, figure 9.11.3.8.2, figure 9.11.3.9.3, figure 9.11.3.9.4 and table 9.11.3.9.1. The 5GS tracking area identity list is a type 4 information element, with a minimum length of 9 octets and a maximum length of 114 octets. The list can contain a maximum of 16 different tracking area identities. Figure 9.11.3.9.1: 5GS tracking area identity list information element Figure 9.11.3.9.2: Partial tracking area identity list – type of list = "00" Figure 9.11.3.9.3: Partial tracking area identity list – type of list = "01" Figure 9.11.3.9.4: Partial tracking area identity list – type of list = "10" Table 9.11.3.9.1: Tracking area identity 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.9 |
2,597 | 7B.7.2 Authentication for AUN3 devices not supporting 5G key hierarchy | Figure 7B.7-1 Authentication Procedure for AUN3 devices using EAP-AKA’ 1. The AUN3 device initiates a layer 2 connection with the 5G-RG either via Ethernet or WLAN. If the layer 2 connection is based on Ethernet, steps 20-21 are skipped. 2. The 5G-RG shall initiate the EAP authentication procedure by sending an EAP request/Identity to the AUN3 device in a layer 2 frame (e.g., EAPOL). 3. The AUN3 device shall send back an EAP response/Identity including its Network Access Identifier (NAI) in the form of username@realm. If the AUN3 device supports SUPI privacy, the AUN3 device shall send SUCI in the EAP response/Identity. 4. The 5G-RG shall construct a SUCI using null-scheme from the NAI-based SUPI if the NAI-based SUPI is received from the AUN3 device in step 3. The 5G-RG shall send a NAS Registration Request message to the AMF, including the SUCI of the AUN3 device and an AUN3 device indicator. 5. The AMF/SEAF shall select the AUSF based on the SUCI in the received registration request and send to the AUSF a Nausf_UEAuthentication_Authenticate Request message, including the SUCI of the AUN3 device and the AUN3 device indicator. 6. The AUSF shall send to the UDM a Nudm_UEAuthentication_Get Request message, including the SUCI of the AUN3 device and the AUN3 device indicator. 7. Upon reception of the Nudm_UEAuthentication_Get Request, the UDM shall invoke the SIDF to map the SUCI to the SUPI and select EAP-AKA’ as authentication method based on the SUPI and the AUN3 device indicator. The UDM/ARPF shall generate an authentication vector using the Access Network Identity as the KDF input parameter. 8. The UDM shall send to the AUSF a Nudm_UEAuthentication_Get Response message, including the EAP-AKA’ authentication vector (RAND, AUTN, XRES, CK´ and IK´), the SUPI. According to the AUN3 subscription data, the UDM shall also send the MSK indicator to the AUSF to indicate that the AUN3 device does not support the 5G key hirerachy. 9. The AUSF shall store XRES for future verification. The AUSF shall send the EAP-Request/AKA'-Challenge message to the AMF/SEAF in a Nausf_UEAuthentication_Authenticate Response message. 10. The AMF/SEAF shall send the EAP-Request/AKA'-Challenge message to the 5G-RG in the NAS Authentication Request message. 11. The 5G-RG shall send to the AUN3 device the EAP-Request/AKA'-Challenge message encapsulated in a layer 2 (L2) message. 12. At receipt the EAP-Request/AKA'-Challenge message, the AUN3 device shall verify the message, generate the authentication response, and derive keys as described in RFC 5448[12]. 13. The AUN3 device shall send the EAP-Response/AKA'-Challenge message to the 5G-RG, encapsulated in a layer 2 message. 14. The 5G-RG shall send to the AMF/SEAF the EAP-Response/AKA'-Challenge message in an NAS Authentication Response message. 15. The AMF/SEAF shall send to the AUSF the EAP-Response/AKA'-Challenge message in an Nausf_UEAuthentication_Authenticate Request message. 16. The AUSF shall verify the AKA’-Challenge message as described in RFC 5448[12]. If successful, based on the MSK indicator received in step 8, the AUSF shall generate the MSK as described in RFC 5448[12] and the AUSF shall not generate the KAUSF. 17. The AUSF shall send to the AMF/SEAF an Nausf_UEAuthentication_Authenticate Response message including the EAP-Success, the MSK, and the SUPI. 18. Based on the received MSK, the AMF shall not generate the KAMF. The AMF shall send EAP-Success and MSK to the 5G-RG in N1 message. Step 18 could be NAS Security Mode Command or Authentication Result. If Step 18 is a NAS Security Mode Command, it uses NULL encryption and NULL integrity protection, since the NAS security context is not required in this scenario. 19. The 5G-RG sends to the AUN3 device the the EAP-Success message in a layer 2 frame. 20a-20b. If the layer 2 connection is over WLAN (IEEE 802.11), the AUN3 device and the 5G-RG use the first 256-bit of the MSK as the PMK, from which the WLAN keys are derived. 21. The AUN3 and the 5G-RG performs four-way handshaking to establish WLAN secure connection. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 7B.7.2 |
2,598 | 8.11.1.1.2 Closed-loop spatial multiplexing performance (User-Specific Reference Symbols) | 8.11.1.1.2.1 Single-layer Spatial Multiplexing For single-layer transmission on antenna ports 7 or 8 upon detection of a MPDCCH with DCI format 6-1A, the requirements are specified in Table 8.11.1.1.2.1-2 with the addition of the parameters in Table 8.11.1.1.2.1-1 and the downlink physical channel setup according to Annex C.3.2. The purpose of these tests is to verify rank-1 performance on one of the antenna ports 7 or 8. Table 8.11.1.1.2.1-1: Test Parameters for Testing CDM-multiplexed DM RS (single layer) Table 8.11.1.1.2.1-2: Minimum performance for CDM-multiplexed DM RS (FRC) 8.11.1.1.2.2 (Void) 8.11.1.1.2.3 (Void) | 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.11.1.1.2 |
2,599 | 5.14.1 Architecture Principles for Configuration Transfer | Configuration Transfer between two eNodeBs follows the principles used by RAN Information Management (RIM) procedures (see clause 5.15) between UTRAN, E-UTRAN and GERAN i.e. providing a generic mechanism for the exchange of arbitrary information between applications belonging to the RAN nodes. However Configuration Transfer is only used for intra- E-UTRAN information exchange whereas RIM procedures are designed for inter-RAT information exchange involving GERAN/UTRAN. Such a separate procedure allows avoiding impacts to other RAT access systems when transferred information is added or modified. The information is transferred via the MME core network node(s). In order to make the information transparent for the Core Network, the information is included in an E-UTRAN transparent container that includes source and target eNodeB addresses, which allows the Core Network nodes to route the messages. If the information is to be transferred between a source eNodeB and a target en-gNB via a target eNodeB for Dual Connectivity with E-UTRAN as Master RAN node and NR as Secondary RAN node as defined in TS 37.340[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 ] [85], the source eNodeB indicates the target en-gNB and may indicate the connected target eNodeB as 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], and the target eNode B further transfers the E-UTRAN transparent container to the en-gNB transparently. The mechanism is depicted in figure 5.14 1. An example for such transferred information is the SON information, as specified in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36]. Figure 5.14-1: inter E-UTRAN Configuration Transfer basic network architecture The E-UTRAN transparent containers are transferred from the source E-UTRAN node to the destination E-UTRAN node by use of Configuration Transfer messages. An eNodeB Configuration Transfer message is used from the eNodeB to the MME over S1 interface, a MME Configuration Transfer message is used from the MME to the eNodeB over S1 interface, and a Configuration Transfer Tunnel message is used to tunnel the E-UTRAN transparent container from a source MME to a target MME over the S10 interface. Each Configuration Transfer message carrying the E-UTRAN transparent container is routed and relayed independently by the core network node(s). Any relation between messages is transparent for the MME, i.e. a request/response exchange between applications, for example SON applications, is routed and relayed as two independent messages by the MME. An MME supporting the Configuration Transfer procedures provides addressing, routing and relaying functions. | 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.14.1 |
2,600 | 5.2.5.8.6 Npcf_AMPolicyAuthorization_Subscribe service operation | Service operation name: Npcf_AMPolicyAuthorization_Subscribe Description: provided by the PCF for NF consumers to explicitly subscribe the notification of events. Inputs, Required: Event ID as specified in Npcf_AMPolicyAuthorization_Notify service operation, Event Reporting Information defined in Table 4.15.1-1 (only the Event Reporting mode and the immediate reporting flag when applicable), Notification Target Address. Inputs, Optional: target of PCF event reporting (SUPI or GPSI) in the case of initial event subscription, Subscription Correlation ID (in the case of modification of the event subscription). Outputs, Required: When the subscription is accepted: Subscription Correlation ID. Outputs, Optional: None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.5.8.6 |
Subsets and Splits
No saved queries yet
Save your SQL queries to embed, download, and access them later. Queries will appear here once saved.