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,301 | – MUSIM-GapInfo | The IE MUSIM-GapInfo is used to indicate MUSIM gap parameters. MUSIM-GapInfo information element -- ASN1START -- TAG-MUSIM-GAPINFO-START MUSIM-GapInfo-r17 ::= SEQUENCE { musim-Starting-SFN-AndSubframe-r17 MUSIM-Starting-SFN-AndSubframe-r17 OPTIONAL, -- Cond aperiodic musim-GapLength-r17 ENUMERATED {ms3, ms4, ms6, ms10, ms20} OPTIONAL, -- Cond gapSetup musim-GapRepetitionAndOffset-r17 CHOICE { ms20-r17 INTEGER (0..19), ms40-r17 INTEGER (0..39), ms80-r17 INTEGER (0..79), ms160-r17 INTEGER (0..159), ms320-r17 INTEGER (0..319), ms640-r17 INTEGER (0..639), ms1280-r17 INTEGER (0..1279), ms2560-r17 INTEGER (0..2559), ms5120-r17 INTEGER (0..5119), ... } OPTIONAL -- Cond periodic } MUSIM-Starting-SFN-AndSubframe-r17 ::= SEQUENCE { starting-SFN-r17 INTEGER (0..1023), startingSubframe-r17 INTEGER (0..9) } -- TAG-MUSIM-GAPINFO-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,302 | 6.4.4.4 Abnormal cases in the UE | The following abnormal case can be identified: a) UE is requested to deactivate a default EPS bearer context of the last PDN connection: If EMM-REGISTERED without PDN connection is not supported by the UE or the MME, and the UE determines that the EPS bearer indicated in the DEACTIVATE EPS BEARER CONTEXT REQUEST message is the default EPS bearer of the last PDN connection that the UE has, then the UE shall respond by performing a detach procedure. Additionally, the UE should perform an attach procedure. If EMM-REGISTERED without PDN connection is supported by the UE and the MME, the UE shall proceed with the deactivation procedure as specified in clause 6.4.4.3. NOTE: User interaction is necessary in some cases when the UE cannot re-activate the EPS bearer(s), if any, automatically. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.4.4.4 |
2,303 | 8.9.1.1.3 Closed-loop spatial multiplexing performance (User-Specific Reference Symbols) | 8.9.1.1.3.1 Single-layer Spatial Multiplexing For single-layer transmission on antenna ports 7 or 8 upon detection of a PDCCH with DCI format 2C, the requirements are specified in Table 8.9.1.1.3.1-2 with the addition of the parameters in Table 8.9.1.1.3.1-1 and the downlink physical channel setup according to Annex C.3.2. The purpose of these tests is to verify rank-1 performance on one of the antenna ports 7 or 8, and to verify rate matching with multiple CSI reference symbol configurations with non-zero and zero transmission power. Table 8.9.1.1.3.1-1: Test Parameters for Testing CDM-multiplexed DM RS (single layer) with multiple CSI-RS configurations Table 8.9.1.1.3.1-2: Minimum performance for CDM-multiplexed DM RS (FRC) with multiple CSI-RS configurations 8.9.1.1.3.2 Single-layer Spatial Multiplexing with CRS assistance information The requirements are specified in Table 8.9.1.1.3.2-2, with the addition of parameters in Table 8.9.1.1.3.2-1. In Table 8.9.1.1.3.2-1, Cell 1 is the serving cell, and Cell 2 and Cell 3 are the aggressor cells. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1, Cell 2 and Cell 3, respectively. The CRS assistance information [7] is provided to the UE and includes information on Cell 2 and Cell 3. The purpose of the test is to verify the single-layer spatial multiplexing TM9 performance under assumption that UE applies CRS interference mitigation in the scenario with 2 CRS antenna ports in the serving and aggressor cells. Table 8.9.1.1.3.2-1: Test Parameters Table 8.9.1.1.3.2-2: Minimum Performance | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.9.1.1.3 |
2,304 | 9.11 Other information elements 9.11.1 General | The different formats (V, LV, T, TV, TLV, LV-E, TLV-E) and the five categories of information elements (type 1, 2, 3, 4 and 6) are defined in 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [11]. The first octet of an information element in the non-imperative part contains the IEI of the information element. If this octet does not correspond to an IEI known in the message, the receiver shall determine whether this IE is of type 1 or 2 (i.e. it is an information element of one octet length) or an IE of type 4 or 6 (i.e. that the next octet is the length indicator or, for a type 6 IE, the next 2 octets are the length indicator indicating the length of the remaining of the information element) (see 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [11]). NOTE: This requirement for the receiver is not applicable for information elements included in a Type 6 IE container information element. Any IE in the Type 6 IE container information element is of type 6 with format TLV-E; therefore, the rules for the IEI value encoding defined in 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [11], subclause 11.2.4, are not applicable. This allows the receiver to jump over unknown information elements and to analyse any following information elements of a particular message. The definitions of information elements which are: a) common for the 5GMM and 5GSM protocols; b) used by access stratum protocols; or c) sent to upper layers are described in subclause 9.11.2. The information elements of the 5GMM or 5GSM protocols can be defined by reference to an appropriate specification which provides the definition of the information element, e.g., "see subclause 10.5.6.3A in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [12]". | 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 |
2,305 | 5.3.6 Uplink Reference Signals and Measurements for Positioning | The periodic, semipersistent and aperiodic transmission of Rel-15 SRS is defined for gNB UL RTOA, UL SRS-RSRP, UL-AoA measurements to facilitate support of UL TDOA and UL AoA positioning methods as described in TS 38.305[ NG Radio Access Network (NG-RAN); Stage 2 functional specification of User Equipment (UE) positioning in NG-RAN ] [42]. The periodic, semipersistent and aperiodic transmission of SRS for positioning is defined for gNB UL RTOA, UL SRS-RSRP, UL-AoA, gNB Rx-Tx time difference measurements to facilitate support of UL TDOA, UL AoA and multi-RTT positioning methods as described in TS 38.305[ NG Radio Access Network (NG-RAN); Stage 2 functional specification of User Equipment (UE) positioning in NG-RAN ] [42]. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.6 |
2,306 | 8.13.1.1.3 Minimum Requirement Multi-Layer Spatial Multiplexing 4 Tx Antenna Port with 256QAM | The purpose of these tests is to verify the closed loop rank-two performance with frequency selective precoding with 256QAM under CA. For CA with 2 DL CCs, the requirements are specified in Table 8.13.1.1.3-3, based on single carrier requirement specified in Table 8.13.1.1.3-2, with the addition of the parameters in Table 8.13.1.1.3-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.1.1.3-1: Test Parameters for Multi-Layer Spatial Multiplexing (FRC) for CA Table 8.13.1.1.3-2: Single carrier performance for multiple CA configurations Table 8.13.1.1.3-3: Minimum performance (FRC) based on single carrier performance for CA with 2 DL CCs | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.13.1.1.3 |
2,307 | 5.5.5.2 Reporting of beam measurement information | For beam measurement information to be included in a measurement report the UE shall: 1> if reportType is set to eventTriggered or reportOnScellActivation: 2> consider the trigger quantity as the sorting quantity if available, otherwise RSRP as sorting quantity if available, otherwise RSRQ as sorting quantity if available, otherwise SINR as sorting quantity; 1> if reportType is set to periodical: 2> if a single reporting quantity is set to true in reportQuantityRS-Indexes; 3> consider the configured single quantity as the sorting quantity; 2> else: 3> if rsrp is set to true; 4> consider RSRP as the sorting quantity; 3> else: 4> consider RSRQ as the sorting quantity; 1> set rsIndexResults to include up to maxNrofRS-IndexesToReport SS/PBCH block indexes or CSI-RS indexes in order of decreasing sorting quantity as follows: 2> if the measurement information to be included is based on SS/PBCH block: 3> include within resultsSSB-Indexes the index associated to the best beam for that SS/PBCH block sorting quantity and if absThreshSS-BlocksConsolidation is included in the VarMeasConfig for the measObject associated to the cell for which beams are to be reported, the remaining beams whose sorting quantity is above absThreshSS-BlocksConsolidation; 3> if includeBeamMeasurements is set to true, include the SS/PBCH based measurement results for the quantities in reportQuantityRS-Indexes for each SS/PBCH block index; 2> else if the beam measurement information to be included is based on CSI-RS: 3> include within resultsCSI-RS-Indexes the index associated to the best beam for that CSI-RS sorting quantity and, if absThreshCSI-RS-Consolidation is included in the VarMeasConfig for the measObject associated to the cell for which beams are to be reported, the remaining beams whose sorting quantity is above absThreshCSI-RS-Consolidation; 3> if includeBeamMeasurements is set to true, include the CSI-RS based measurement results for the quantities in reportQuantityRS-Indexes for each CSI-RS index. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.5.5.2 |
2,308 | 8.5.2.2.8 Enhanced Downlink Control Channel Performance Requirement Type B - 2 Tx Antenna Ports with Non-Colliding CRS Dominant Interferer | For the parameters specified in Table 8.5.2-1 and Table 8.5.2.2.8-1, the average probability of a miss-detecting ACK for NACK (Pm-an) shall be below the specified value in Table 8.5.2.2.8-2. The purpose of this test is to verify the PHICH performance with 2 transmit antennas when the serving cell PHICH transmission is interfered by two interfering cells with the dominant interferer having the non-colliding CRS pattern and applying interference model defined in clause B.7.1. In Table 8.5.2.2.8-1, Cell 1 is the serving cell, and Cell 2 and Cell 3 are the aggressor cells. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1, Cell 2 and Cell 3, respectively. The CRS assistance information [7] is provided and includes Cell 2 and Cell 3. Table 8.5.2.2.8-1: Test Parameters for PHICH Table 8.5.2.2.8-2: Minimum performance PHICH for Enhanced Downlink Control Channel Performance Requirement Type B | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.5.2.2.8 |
2,309 | – VarConnEstFailReport | The UE variable VarConnEstFailReport includes the connection establishment failure and/or connection resume failure information. VarConnEstFailReport UE variable -- ASN1START -- TAG-VARCONNESTFAILREPORT-START VarConnEstFailReport-r16 ::= SEQUENCE { connEstFailReport-r16 ConnEstFailReport-r16, network-Identity-r18 CHOICE { plmn-Identity-r18 PLMN-Identity, snpn-Identity-r18 SNPN-Identity-r18 } } SNPN-Identity-r18 ::= SEQUENCE { plmn-Identity-r18 PLMN-Identity, nid-r18 NID-r16 } -- TAG-VARCONNESTFAILREPORT-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,310 | 5.2.1.3 Transfer of CDR files via Bx | The CGF is responsible for persistent CDR storage, for preparing CDR files and transferring them to the BD via the Bx reference point. To this end, the CGF provides one or more files on which to store the CDRs after potential reformatting to comply with the Bx file format specified in TS 32.297[ Telecommunication management; Charging management; Charging Data Record (CDR) file format and transfer ] [52]. The CDRs may be routed to one of several simultaneously open files inside the CGF depending on certain CDR parameters, such as CDR type, or on other criteria such as the originating CDF. CDR files are closed on the CGF based on certain operator configured parameters, for example: - file size limit, - file duration (time) limit, - time of day, - maximum number of CDRs. This implies that the closure of a CDR file occurs asynchronously to the reception of CDRs on the CGF. When a CDR file is closed, the CGF must assure that a new CDR file is available to store incoming CDRs in line with the CDR routing facility described above. Once CDR files are closed, they are ready for transfer to the BD. The CGF shall support both "push" transfer mode (i.e. CGF triggers and controls file transfer to BD) and "pull" transfer mode (i.e. BD triggers and controls file transfer). In push mode, the CGF uploads the files to the BD according to operator specified parameters, such as time of day, number of available files, etc. In pull mode, the BD may request the files from the CGF at any point in time at the discretion of the BD. For all procedures involved in CDR reception, processing and storing, the CGF shall be capable of complying with near real-time requirements. Details on the protocol application for the open Bx interface and the functionality of the CGF can be found in TS 32.297[ Telecommunication management; Charging management; Charging Data Record (CDR) file format and transfer ] [52]. The semantics and formal description of the CDR parameters are specified in TS 32.298[ Telecommunication management; Charging management; Charging Data Record (CDR) parameter description ] [51]. | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 5.2.1.3 |
2,311 | 12.2 PDN Interworking Model | The interworking point is at the Gi reference point. The GGSN for interworking with the ISP/PDN is the access point of the Packet Domain (see figure 13). The GGSN will either terminate the PPP connection towards the MS or may further relay PPP frames to the PDN. The PPP frames may be tunnelled in e.g. L2TP. Figure 13: The protocol stacks for the Gi PPP reference point In case the external PDN is an IP based network and the GGSN terminates PPP the same description applies as specified in subclause 11.2. In case the GGSN tunnels PPP frames to the PDN, the GGSN may behave like a LAC towards the external network. | 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 | 12.2 |
2,312 | 9.3.1.1.2 TDD | For the parameters specified in Table 9.3.1.1.2-1, and using the downlink physical channels specified in Annex C.3.2, the minimum requirements are specified in Table 9.3.1.1.2-2 and by the following a) a sub-band differential CQI offset level of 0 shall be reported at least % of the time but less than % for each sub-band; b) the ratio of the throughput obtained when transmitting on a randomly selected sub-band among the sub-bands with the highest differential CQI offset level the corresponding TBS and that obtained when transmitting the TBS indicated by the reported wideband CQI median on a randomly selected sub-band in set S shall be ≥ ; c) when transmitting on a randomly selected sub-band among the sub-bands with the highest differential CQI offset level the corresponding TBS, the average BLER for the indicated transport formats shall be greater or equal to 0.05. The requirements only apply for sub-bands of full size and the random scheduling across the sub-bands is done by selecting a new sub-band in each TTI for FDD, each available downlink transmission instance for TDD. Table 9.3.1.1.2-1 Sub-band test for single antenna transmission (TDD) Table 9.3.1.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.1.1.2 |
2,313 | D.8.3.1 Procedure transaction identity | The following network procedures shall apply for handling an unknown, erroneous, or unforeseen PTI received in a UPDS message: a) In case the network receives a MANAGE UE POLICY COMPLETE message or MANAGE UE POLICY COMMAND REJECT message in which the PTI value is an assigned or unassigned value that does not match any PTI in use, the network shall ignore the UPDS message. b) In case the network receives a UPDS message in which the PTI value is a reserved value, the network shall ignore the UPDS message. The following UE procedures shall apply for handling an unknown, erroneous, or unforeseen PTI received in a UPDS message: a) In case the UE receives a UPDS message in which the PTI value is a reserved value, the UE shall ignore the UPDS message. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | D.8.3.1 |
2,314 | 5.9.4.5 Setting of the contents of MBS Interest Indication | The UE shall set the contents of the MBS Interest Indication as follows: 1> if the UE has a valid version of SIB21 for the PCell; and 1> if the set of MBS frequencies of interest, determined in accordance with 5.9.4.3, is not empty: 2> include mbs-FreqList and set it to include the MBS frequencies of interest sorted by decreasing order of interest, using the absoluteFrequencySSB for serving frequency, if applicable, and the ARFCN-ValueNR(s) as included in SIB21 or in USD (for neighbouring frequencies); 2> include mbs-Priority if the UE prioritises reception of all indicated MBS frequencies above reception of any of the unicast bearers and multicast MRBs; NOTE 1: If the UE prioritises MBS broadcast reception and unicast/multicast data cannot be supported because of congestion on the MBS carrier(s), NG-RAN may for example initiate release of unicast bearers/multicast MRBs. 2> if SIB20 is provided for the PCell or for the SCell: 3> include mbs-ServiceList and set it to indicate the set of MBS services of interest sorted by decreasing order of interest determined in accordance with 5.9.4.4. NOTE 2: The mbs-ServiceList is not required to be used by the NG-RAN to determine the frequency on which to enable MBS broadcast reception for the UE. 1> if nonServingCellMII is included in SIB1 for the PCell; and 1> if the set of MBS frequencies for MBS broadcast reception on non-serving cell, determined in accordance with 5.9.4.3, is not empty: 2> include freqInfoMBS; 2> if the UE has acquired cfr-InfoMBS and subcarrierSpacing for MBS broadcast reception on the non-serving cell: 3> include cfr-InfoMBS and subcarrierSpacing; | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.9.4.5 |
2,315 | 5.5.3.2.2 STATUS message with compatible state | A STATUS message may be received indicating a compatible call state but containing one of the following causes: # 95 "semantically incorrect message"; or # 96 "invalid mandatory information"; or # 97 "message type non-existent or not implemented"; or # 98 "message type not compatible with protocol state"; or # 99 "information element non-existent or not implemented"; or # 100 "conditional IE error". This indicates that the transmitter of the STATUS message was unable to accept some information sent by the recipient of the STATUS message. This allow the recipient to retransmit some or all of the information. Other actions are possible and are implementation dependent; they may include releasing the call. In the case the MS receives a STATUS message with the cause #100 due to the presence of a Repeat Indicator with the value "service change and fallback" in a SETUP message, it may then resend a new SETUP message with a single BC-IE (no Repeat Indicator is included). The actual behaviour is dependent on the implementation. In the case the network receives a STATUS message with the cause #100 due to the presence of a Repeat Indicator with the value "service change and fallback" in a SETUP message, it shall then resend a new SETUP message, with either the BC-IE of the preferred service or the speech BC-IE (fallback to speech) as the only BC (no Repeat Indicator is included). The preferred behaviour is decided by configuration. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.3.2.2 |
2,316 | 9.5.1.2 TDD | The minimum performance requirement in Table 9.5.1.2-2 is defined as The ratio of the throughput obtained when transmitting based on UE reported RI and that obtained when transmitting with fixed rank 1 shall be ≥ ; The ratio of the throughput obtained when transmitting based on UE reported RI and that obtained when transmitting with fixed rank 2 shall be ≥ ; For the parameters specified in Table 9.5.1.2-1, and using the downlink physical channels specified in Annex C.3.2, the minimum requirements are specified in Table 9.5.1.2-2. Table 9.5.1.2-1: RI Test (TDD) Table 9.5.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.5.1.2 |
2,317 | 7.5 RACH Optimisation Function | The RACH Optimization Function in non-split gNB case is specified in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [2]. In case of split gNB architecture, RACH configuration conflict detection and resolution function is located at the gNB-DU. To perform RACH optimisation at gNB-DU, gNB-CU sends the RA Report retrieved from the UE(s) to gNB-DU via F1AP signalling. The gNB-DU signals the PRACH configuration per-cell to gNB-CU. The gNB-CU may forward a limited set of neighbour cell’s PRACH configurations received from neighbour gNBs and other gNB-DUs to the gNB-DU to resolve the configuration conflict. RA Report retrieval When a UE performs successful random access attempts which are only known by the gNB-DU (e.g., beam failure recovery, UL synchronization issue, scheduling request failure, no PUCCH resource available), the gNB-DU may inform the gNB-CU about the occurrences of successful random access procedures in the gNB-DU via a RACH indication. The gNB-CU may then retrieve the RA Report from the UE(s) based on the RACH indication received via F1AP signalling from the gNB-DU. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 7.5 |
2,318 | 13.2.2.4.3 N32-f security context | The N32-c initial handshake described in clause 13.2.2.2 establishes session keys, IVs and negotiated cipher suites. Counters are used for replay protection. Modification policies are identified by modification policy IDs, to be able to verify received messages that have undergone IPX modifications. The N32-f security context shall consist of the following parameters: - Session keys - Negotiated cipher suites - Data type encryption policy IDs - Modification policy list (if IPXs are used) - Modification policy IDs - IPX provider identifier - Counters - IVs - List of security information of the IPX providers connected to the SEPPs (IPX security information list) - IPX provider identifier - List of raw public keys or certificates for that IPX | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 13.2.2.4.3 |
2,319 | 6.3.12 Trusted Non-3GPP Access Network selection 6.3.12.1 General | Clause 6.3.12 specifies how a UE, which wants to establish connectivity via trusted non-3GPP access and is not operating in SNPN access mode, selects a PLMN and a trusted non-3GPP access network (TNAN) to connect to. NOTE: For UE operating in SNPN access mode refer to clause 5.30.2.13. How the UE decides to use trusted non-3GPP access is not specified in this document. As an example, a UE may decide to use trusted non-3GPP access for connecting to 5GC in a specific PLMN based on: - the UE implementation-specific criteria; or - the UE configuration, e.g. the UE may be configured to try first the trusted non-3GPP access procedures; or - the UE capabilities, e.g. the UE may support only the trusted non-3GPP access procedures; or - the advertised capabilities of the discovered non-3GPP access networks, e.g. one or more available non-3GPP access networks advertise support of trusted connectivity to 5GC in a specific PLMN. An example deployment scenario is schematically illustrated in Figure 6.3.12.1-1 below. In this scenario, the UE has discovered five non-3GPP access networks, which are WLAN access networks. These WLANs advertise information about the PLMNs they interwork with, e.g. by using the ANQP protocol, as defined in the HS2.0 specification [85]. Each WLAN may support "S2a connectivity" and/or "5G connectivity" to one or more PLMNs. Before establishing connectivity via trusted non-3GPP access, the UE needs to select (a) a PLMN, (b) a non-3GPP access network that provide trusted connectivity this this PLMN, and (c) a connectivity type, i.e. either "5G connectivity" or "S2a connectivity". Each non-3GPP access network may advertise one or more of the following PLMN lists: 1) A PLMN List-1, which includes PLMNs with which "AAA connectivity" is supported. A non-3GPP access network supports "AAA connectivity" with a PLMN when it deploys an AAA function that can connect with a 3GPP AAA Server/Proxy in this PLMN, via an STa interface (trusted WLAN to EPC), or via an SWa interface (untrusted WLAN to EPC); see TS 23.402[ Architecture enhancements for non-3GPP accesses ] [43]. 2) A PLMN List-2, which includes PLMNs with which "S2a connectivity" is supported. A non-3GPP access network supports "S2a connectivity" with a PLMN when it deploys a TWAG function that can connect with a PGW in this PLMN, via an S2a interface; see clause 16 of TS 23.402[ Architecture enhancements for non-3GPP accesses ] [43]. 3) A PLMN List-3, which includes PLMNs with which "5G connectivity" is supported. A non-3GPP access network supports "5G connectivity" with a PLMN when it deploys a TNGF function that can connect with an AMF function and an UPF function in this PLMN via N2 and N3 interfaces, respectively; see clause 4.2.8. When the UE wants to discover the PLMN List(s) supported by a non-3GPP access network and the non-3GPP access network supports ANQP, the UE shall send an ANQP query to the non-3GPP access network requesting "3GPP Cellular Network" information. If the non-3GPP access network supports interworking with one or more PLMNs, the response received by the UE includes a "3GPP Cellular Network" information element containing one or more of the above three PLMN Lists. The PLMN List-1 and the PLMN List-2 are specified in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [43] and indicate support of interworking with EPC in one or more PLMNs. The PLMN List-3 is a list used to indicate support of interworking with 5GC in one or more PLMNs. When the non-3GPP access network does not support ANQP, how the UE discovers the PLMN List(s) supported by the non-3GPP access network is not defined in the present specification. The UE determines if a non-3GPP access network supports "trusted connectivity" to a specific PLMN by receiving the PLMN List-2 and the PLMN List-3 advertised by this access network. If this PLMN is not included in any of these lists, then the non-3GPP access network can only support connectivity to an ePDG or N3IWF in the PLMN (i.e. "untrusted connectivity"). Figure 6.3.12.1-1: Example deployment scenario for trusted Non-3GPP access network selection | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.3.12 |
2,320 | – AppLayerIdleInactiveConfig | The IE AppLayerIdleInactiveConfig indicates parameters specific to application layer measurements applicable to RRC_IDLE/RRC_INACTIVE. AppLayerIdleInactiveConfig information element -- ASN1START -- TAG-APPLAYERIDLEINACTIVECONFIG-START AppLayerIdleInactiveConfig-r18 ::= SEQUENCE { configForRRC-IdleInactive-r18 ENUMERATED {true} OPTIONAL, -- Need M qoe-Reference-r18 OCTET STRING (SIZE (6)) OPTIONAL, -- Need R qoe-MeasurementType-r18 ENUMERATED {sbased, mbased} OPTIONAL, -- Need R qoe-AreaScope-r18 Qoe-AreaScope-r18 OPTIONAL, -- Need R mce-Id-r18 OCTET STRING (SIZE (1)) OPTIONAL, -- Need R availableRAN-VisibleMetrics-r18 AvailableRAN-VisibleMetrics-r18 OPTIONAL, -- Need R ... } Qoe-AreaScope-r18 ::= CHOICE { cellGlobalIdList CellGlobalIdList-r16, trackingAreaCodeList TrackingAreaCodeList-r16, trackingAreaIdentityList TrackingAreaIdentityList-r16, plmn-IdentityList PLMN-IdentityList2-r16, ... } AvailableRAN-VisibleMetrics-r18 ::= SEQUENCE { appLayerBufferLevelList-r18 ENUMERATED {true} OPTIONAL, -- Need N playoutDelayForMediaStartup-r18 ENUMERATED {true} OPTIONAL, -- Need N ... } -- TAG-APPLAYERIDLEINACTIVECONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,321 | 5.2.17.2.2 Nchf_SpendingLimitControl Subscribe service operation | Service operation name: Nchf_SpendingLimitControl_Subscribe Description: Subscribe to notification of changes in the status of the policy counters available at the CHF and retrieval of the status of the policy counters for which subscription is accepted by CHF. Inputs, Required: SUPI (for the Initial Spending Limit request), SubscriptionCorrelationId (for the Intermediate Spending Limit report), Event Id "policy counter status change", Event Filter Information "List of policy counter identifier (s)". Inputs, Optional: Notification Correlation Target (required for the Initial Spending Limit request), Event Filter Information "List of policy counter identifier (s)", Event Reporting Information (continuous reporting). Outputs, Required: Status of the requested subscribed policy counters to the subscriber in the Event Information. Outputs, Optional: Pending policy counter statuses and their activation times, for all policy counter(s) available for this subscriber. If list of policy counter identifier(s) was provided, the CHF returns only the pending policy counter statuses and their activation times, per required policy counter identifier in the Event Information, SubscriptionCorrelationId. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.17.2.2 |
2,322 | – PowSav-Parameters | The IE PowSav-Parameters is used to convey the capabilities supported by the UE for the power saving preferences. PowSav-Parameters information element -- ASN1START -- TAG-POWSAV-PARAMETERS-START PowSav-Parameters-r16 ::= SEQUENCE { powSav-ParametersCommon-r16 PowSav-ParametersCommon-r16 OPTIONAL, powSav-ParametersFRX-Diff-r16 PowSav-ParametersFRX-Diff-r16 OPTIONAL, ... } PowSav-Parameters-v1700 ::= SEQUENCE { powSav-ParametersFR2-2-r17 PowSav-ParametersFR2-2-r17 OPTIONAL, ... } PowSav-ParametersCommon-r16 ::= SEQUENCE { drx-Preference-r16 ENUMERATED {supported} OPTIONAL, maxCC-Preference-r16 ENUMERATED {supported} OPTIONAL, releasePreference-r16 ENUMERATED {supported} OPTIONAL, -- R1 19-4a: UE assistance information minSchedulingOffsetPreference-r16 ENUMERATED {supported} OPTIONAL, ... } PowSav-ParametersFRX-Diff-r16 ::= SEQUENCE { maxBW-Preference-r16 ENUMERATED {supported} OPTIONAL, maxMIMO-LayerPreference-r16 ENUMERATED {supported} OPTIONAL, ... } PowSav-ParametersFR2-2-r17 ::= SEQUENCE { maxBW-Preference-r17 ENUMERATED {supported} OPTIONAL, maxMIMO-LayerPreference-r17 ENUMERATED {supported} OPTIONAL, ... } -- TAG-POWSAV-PARAMETERS-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,323 | 6.1.6 MAC PDU (SL-SCH) | A MAC PDU consists of a MAC header, one or more MAC Service Data Units (MAC SDU), and optionally padding; as described in Figure 6.1.6-4. Both the MAC header and the MAC SDUs are of variable sizes. A MAC PDU header consists of one SL-SCH subheader, one or more MAC PDU subheaders; each subheader except SL-SCH subheader corresponds to either a MAC SDU or padding. The SL-SCH subheader consists of the seven header fields V/R/R/R/R/SRC/DST. A MAC PDU subheader consists of the six header fields R/R/E/LCID/F/L but for the last subheader in the MAC PDU. The last subheader in the MAC PDU consists solely of the four header fields R/R/E/LCID. A MAC PDU subheader corresponding to padding consists of the four header fields R/R/E/LCID. Figure 6.1.6-1: R/R/E/LCID/F/L MAC subheader Figure 6.1.6-2: R/R/E/LCID MAC subheader Figure 6.1.6-3: SL-SCH MAC subheader for V ="0001" and "0010" Figure 6.1.6-3a: SL-SCH MAC subheader for V="0011" MAC PDU subheaders have the same order as the corresponding MAC SDUs and padding. Padding occurs at the end of the MAC PDU, except when single-byte or two-byte padding is required. Padding may have any value and the MAC entity shall ignore it. When padding is performed at the end of the MAC PDU, zero or more padding bytes are allowed. When single-byte or two-byte padding is required, one or two MAC PDU subheaders corresponding to padding are placed after the SL-SCH subheader and before any other MAC PDU subheader. A maximum of one MAC PDU can be transmitted per TB. Figure 6.1.6-4: Example of MAC PDU consisting of MAC header, MAC SDUs and padding | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.1.6 |
2,324 | 5.5.2.1 Use of credit pooling | Credit fragmentation can occur when it is necessary to grant separate quotas. Granting each quota causes some of the user's credit to be reserved at the Server. It is then possible that all the user's credit may be reserved when the user wishes to start using a new service. The new service may then be denied, despite the fact that there remains unused credit in the user's account. To avoid such credit fragmentation and unnecessary load on the server, it is possible for multiple quotas provided to be linked into a credit pool. The client may then consider the quotas to form a single pool of credit, from which all services draw units. The reference to a credit pool includes a translation factor derived from the rating parameter, which translates from units of a specific type (time/volume) to the abstract units in the pool. The use of credit pooling is described in IETF RFC 4006 [402]. | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 5.5.2.1 |
2,325 | 6.26.2.8 Indirect communication mode | The 5G system shall support 5G LAN-type service for authorized UEs using indirect network connection or direct network connection. The 5G network shall be able to provide a remote UE using 5G LAN-type service with same level of service as if the remote UE would be using a direct network connection (i.e. provide required QoS for the Ethernet packets transferred between remote UE and relay UE if they are using 3GPP access). The 5G network shall be able to support service continuity for the private communication between a remote UE with other member UEs of the same 5G LAN-VN, when the remote UE changes from one relay UE to another or when the UE changes between direct and indirect network connection. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.26.2.8 |
2,326 | 8.31 Trace Information | Trace Information is coded as depicted in Figure 8.31-1. See 3GPP TS 32.422[ Telecommunication management; Subscriber and equipment trace; Trace control and configuration management ] [18] for details on trace related information. Figure 8.31-1: Trace Information Octets 5 to 10 represent the Trace Reference parameter as defined in clause 5.6 of 3GPP TS 32.422[ Telecommunication management; Subscriber and equipment trace; Trace control and configuration management ] [18]. Triggering Events shall be encoded as the first 9 octets in clause 5.1 of 3GPP TS 32.422[ Telecommunication management; Subscriber and equipment trace; Trace control and configuration management ] [18]. List of NE Types, Session Trace Depth and IP Address of Trace Collection Entity are specified in 3GPP TS 32.422[ Telecommunication management; Subscriber and equipment trace; Trace control and configuration management ] [18]. List of Interfaces shall be encoded as the first 12 octets in clause 5.5 of 3GPP TS 32.422[ Telecommunication management; Subscriber and equipment trace; Trace control and configuration management ] [18]. See 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [5], clause 10.5.1.4, Mobile Identity, for the coding of MCC and MNC, whose values are obtained from the serving PLMN that the EM/NM is managing. If MNC is 2 digits long, bits 5 to 8 of octet 6 are coded as "1111". NOTE: During a 5GS to EPS mobility, the MME derives the information to be sent in the Trace Information IE over S11 from the Extended Trace Information IE received from the AMF, if an SGW trace is activated; the PGW(+SMF) derives relevant trace information from the Trace Data that it received earlier (at the SMF), if a PGW trace is to be activated. | 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.31 |
2,327 | 5.21.3 Network Reliability support with Sets 5.21.3.1 General | A Network Function instance can be deployed such that several network function instances are present within an NF Set to provide distribution, redundancy and scalability together as a Set of NF instances. The same is also supported for NF Services. This can be achieved when the equivalent NFs and NF Services share the same context data or by Network Function/NF Service Context Transfer procedures as specified in clause 4.26 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. NOTE: A NF can be replaced by an alternative NF within the same NF Set in the case of scenarios such as failure, load balancing, load re-balancing. Such a network reliability design shall work in both communication modes, i.e. Direct Communication and Indirect Communication. In the Direct Communication mode, the NF Service consumer is involved in the reliability related procedures. In Indirect Communication mode, the SCP is involved in the reliability related procedures. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.21.3 |
2,328 | 6.1 MAC Sublayer | In MR-DC, the UE is configured with two MAC entities: one MAC entity for the MCG and one MAC entity for the SCG. The serving cells other than the PCell can be activated/deactivated by RRC or MAC Control Element. For activation/deactivation by MAC Control Element, the serving cells of the MCG other than the PCell can only be activated/deactivated by the MAC Control Element received on MCG, and the serving cells of the SCG other than PSCell can only be activated/ deactivated by the MAC Control Element received on SCG. The MAC entity applies the bitmap for the associated cells of either MCG or SCG. When the SCG is not deactivated, the PSCell is always activated like the PCell (i.e. deactivation timer is not applied to PSCell). With the exception of PUCCH SCell, one deactivation timer is configured per SCell by RRC. In MR-DC, semi-persistent scheduling (SPS) resources and configured grant (CG) resources can be configured on serving cells in both MCG and SCG. In MR-DC, for 4-step RA type, contention based random access (CBRA) procedure is supported on both PCell and PSCell while contention free random access (CFRA) procedure is supported on all serving cells in both MCG and SCG. For 2-step RA type, CBRA can be supported on the PCell, if the MN is a gNB (i.e. for NE-DC and NR-DC) and on the PSCell, if the SN is a gNB (i.e, for EN-DC, NGEN-DC and NR-DC) while CFRA is only supported on the PCell, if the MN is a gNB (i.e. for NE-DC and NR-DC). In (NG)EN-DC and NR-DC, when SCG is deactivated as described in clause 7.13, the TA timer associated with SCG continues running, the UE considers the TA is valid as long as TA timer is running. In case of SCG activation, the UE can be instructed by the network to perform random access towards PSCell even if the TA timer associated with PSCell is running and RLF and beam failure are not declared. Besides, the UE can be instructed by the network to perform SCG activation without performing random access, if the TA timer associated with PSCell is running and RLM and beam failure detection are configured but RLF or beam failure is not declared. In case of network-initiated SCG activation, both CBRA and CFRA on PSCell are supported. For CFRA, the dedicated RACH resources can be provided in the RRC message used to activate SCG. In MR-DC, the BSR configuration, triggering and reporting are independently performed per cell group. For split bearers, the PDCP data is considered in BSR in the cell group(s) configured by RRC. In MR-DC, separate DRX configurations are provided for MCG and SCG. A secondary DRX group can be configured in MR-DC for a cell group that includes cells in different Frequency Ranges as specified in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [4]. In MR-DC, PHR is independently configured per cell group. Events in one cell group can trigger power headroom reporting in both MCG and SCG. Power headroom information for one cell group is also included in a PHR transmitted in the other cell group. While the SCG is deactivated, PHR for SCG is not reported. In MR-DC, consistent LBT failure recovery procedure as described in clause 5.6.1 in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [3] can be configured for both MAC entities of MCG and/or SCG when operating with shared spectrum channel access. In MR-DC, for power saving purpose, the UE can be configured with DCP to be monitored on the PCell, if the MN is a gNB (i.e. for NE-DC and NR-DC) and/or with DCP to be monitored on the PSCell, if the SN is a gNB (i.e. for EN-DC, NGEN-DC and NR-DC). In MR-DC, the UE may be configured with enhanced intra-UE overlapping resources prioritization on MN, if the MN is a gNB (i.e. for NE-DC and NR-DC) and on SN, if the SN is a gNB (i.e. for EN-DC, NGEN-DC and NR-DC). | 3GPP TS 37.340 | Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 | RAN2 | 3GPP Series : 37 , Multiple radio access technology aspects | 6.1 |
2,329 | 8.18 Serving Network | Serving Network is coded as depicted in Figure 8.18-1. Figure 8.18-1: Serving Network If an Administration decides to include only two digits in the MNC, then bits 5 to 8 of octet 6 are coded as "1111". Unless specified otherwise in the specification, this IE contains the serving core network operator ID provided by the MME, S4-SGSN or ePDG, or the PLMN identity of the selected PLMN used for 3GPP-based access authentication provided by the TWAN. NOTE: The serving core network operator ID is the PLMN ID of the MME, S4-SGSN or ePDG which is currently serving the UE. An S4-SGSN/MME which supports multiple PLMN IDs is considered as logically different S4-SGSNs/MMEs. | 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.18 |
2,330 | 5.3.1.2.2 Allocation, renewal and release of the IPv6 default prefix via IPv6 stateless address autoconfiguration | When the PLMN allocates an IPv6 prefix, it is the PDN GW responsibility to allocate and release the IPv6 prefix. The PDN GW may use an internal IPv6 prefix pool in this case. The PDN GW allocates a globally unique /64 IPv6 prefix via Router Advertisement to a given UE. When an IPv6 prefix is allocated from an external PDN, it is the PDN GW responsibility to obtain the IPv6 prefix from the external PDN and to allocate, renew and release the IPv6 prefix. The PDN GW may use DHCPv6 to obtain the IPv6 prefix from the external PDN. In this case, the PDN GW functions as a DHCPv6 client. If RADIUS or Diameter is used towards the external PDN as described in TS 29.061[ Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) ] [38], the IPv6 prefix can be obtained, renewed and released as part of these procedures. If RADIUS is used, the PDN GW functions as the RADIUS Client. If Diameter is used, the PDN GW functions as the Diameter Client. The procedure of stateless IPv6 address autoconfiguration is the following: After default bearer establishment the UE may send a Router Solicitation message to the PDN GW to solicit a Router Advertisement message. The PDN GW sends a Router Advertisement message (solicited or unsolicited) to the UE. The Router Advertisement messages shall contain the same IPv6 prefix as the one provided during default bearer establishment. If the UE receives an IPv6 prefix from a SGSN during the PDP Context activation procedure, it shall ignore it. After the UE has received the Router Advertisement message, it constructs a full IPv6 address via IPv6 Stateless Address autoconfiguration in accordance with RFC 4862 [18]. To ensure that the link-local address generated by the UE does not collide with the link-local address of the PDN GW, the PDN GW shall provide an interface identifier (see RFC 4862 [18]) to the UE and the UE shall use this interface identifier to configure its link-local address. For stateless address autoconfiguration however, the UE can choose any interface identifier to generate IPv6 addresses, other than link-local, without involving the network. However, the UE shall not use any identifiers defined in TS 23.003[ Numbering, addressing and identification ] [9] as the basis for generating the interface identifier. For privacy, the UE may change the interface identifier used to generate full IPv6 address, as defined in TS 23.221[ Architectural requirements ] [27] without involving the network. Any prefix that the PDN GW advertises to the UE is globally unique. The PDN GW shall also record the relationship between the UE's identity (IMSI) and the allocated IPv6 prefix. Because any prefix that the PDN GW advertises to the UE is globally unique, there is no need for the UE to perform Duplicate Address Detection for any IPv6 address configured from the allocated IPv6 prefix. Even if the UE does not need to use Neighbor Solicitation messages for Duplicate Address Detection, the UE may, for example, use them to perform Neighbor Unreachability Detection towards the PDN GW, as defined in RFC 4861 [32]. Therefore, the PDN GW shall respond with a Neighbor Advertisement upon receiving a Neighbor Solicitation message from the UE. In order to renew the allocated IPv6 prefix, the PDN GW sends a Router Advertisement (solicited or unsolicited) to the UE with the same prefix and new non-zero values in preferred and valid lifetime fields. In order to release the allocated IPv6 prefix, the PDN GW shall initiate the PDN connection release procedure. Upon release of the PDN connection, the UE shall implicitly release the prefix for the corresponding PDN connection. NOTE 2: If the PDN type is IPv4v6, when the PDN Connection is released, the IPv4 address is also released. After releasing the IPv6 prefix, the PDN GW should not assign that IPv6 prefix to other user immediately. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.3.1.2.2 |
2,331 | B.2 Handover/Relocation related generic transparent Containers over RANAP, S1-AP and GTP | Handover/Relocation related generic transparent containers are defined in 3GPP TS 25.413[ UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling ] [33] and 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [10] ("Source to Target Transparent Container" IE and "Target to Source Transparent Container" IE) to carry UTRAN, E-UTRAN or GERAN specific information via CN interfaces in a RAT-agnostic way. The encoding of these handover/relocation related generic transparent containers is different in RANAP and S1-AP. See 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [10] Annex C. The difference is that the "Source to Target Transparent Container" IE and "Target to Source Transparent Container" IE are ASN.1 encoded over RANAP as "IE-ID||criticality||OT-LI||octets" (i.e. one length field only for the open type field) and over S1AP as "IE-ID||criticality||OT-LI||OCT-LI||octets" (i.e. with 2 length fields, one for the open type field ("OT-LI"), one for the octet string encoding ("OCT-LI")), while "octets" contain the actual RAT specific handover/relocation information. This gives the following chain of encodings (represented in the notation introduced in the Notes above) end-to-end. LTE to LTE Figure B.2-1: LTE to LTE - Encoding of Generic Transparent Containers In the case of LTE-LTE handover, the "octets" contain the "Source eNB to Target eNB Transparent Container" (defined as an ASN.1 SEQUENCE in 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [10]). The source MME, after decoding the HO REQUIRED message of S1AP, passes transparently the "sequence" to the target MME. The target MME encodes similarly at target side with the same definitions: it feeds the received "sequence" into the S1AP ASN.1 encoder in order to encode the HO REQUEST message towards the target eNB. The "sequence" is then extracted from the S1AP ASN.1 of eNB and given to application part of eNB. LTE to 3G Figure B.2-2: LTE to 3G - Encoding of Generic Transparent Containers At source side, the same encoding is done but for LTE to 3G handover, this time the "octets" on the line is the "Source RNC to Target RNC Transparent Container" (encoded according to the target system RANAP i.e. as an ASN.1 SEQUENCE in 3GPP TS 25.413[ UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling ] [33]). Again the source MME passes transparently the "sequence" to the target MME i.e. the "Source RNC to Target RNC Transparent Container". At the target side, the RANAP RELOCATION REQUEST message was not upgraded: the "sequence" received from the Gn or S3 interface ("Source RNC to Target RNC Transparent Container") is not encoded as an OCTET STRING as on S1, but directly represent the "Source To Target Transparent Container" within the RANAP:RELOCATION REQUEST message, which in case of inter-RAT handover to 3G represent the "Source RNC to Target RNC Transparent Container", transported on the Iu interface as the "IE" part of the "IE container". There is no additional length field added as on the S1 interface ("OCT-LI"). The target side remains therefore fully backwards compatible with UMTS release 7. 3G to LTE Figure B.2-3: 3G to LTE - Encoding of Generic Transparent Containers The RELOCATION REQUIRED message was upgraded from release 8 onwards renaming the previously contained "Source RNC to Target RNC Transparent Container" to "Source to Target Transparent Container", being able to transport also a "Source eNB to Target eNB Transparent Container". Despite being defined as an octet string, in order to not impact the R7 SGSN, the octet string was specified as "to be replaced" by either the UTRAN or E-UTRAN specific container. This fact is explained e.g. within the NOTE in the ASN.1 of 3GPP TS 25.413[ UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling ] [33] ], as shown in this excerpt: Source-ToTarget-TransparentContainer ::= OCTET STRING -- This IE is a transparent container, the IE shall be encoded not as an OCTET STRING but according to the type specifications of the target system. -- Note: In the current version of this specification, this IE may either carry the Source RNC to -- Target RNC Transparent Container or the Source eNB to Target eNB Transparent Container IE as -- defined in [49] By so doing, the Release 7 source SGSN receives only one length field (the "OT-LI") instead of two (the "OT-LI and the "OCT-LI") as if it would receive an "Source RNC to Target RNC Transparent Container" from a Release 7 RNC, ensuring fully Release 7 backwards compatibility as requested by 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [3] Annex D. This is illustrated in Figure B.1-3 above. As explained above, this Release 7 backwards compatibility constraint only applies to RANAP to cope with Release 7 SGSN nodes and does NOT apply to LTE. This is why the note is NOT present in the ASN.1 of 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [10] for LTE i.e. the S1AP octet string does not need "to be replaced". Then "sequence" is passed transparently to the target MME. The target MME encodes the "sequence" within an OCTET STRING resulting in two length fields as expected by target eNB ASN.1 S1AP decoder. | 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 | B.2 |
2,332 | 8.3.2.1J Single-layer Spatial Multiplexing (with assistance information for simultaneous transmition interfering PDSCH) | For single-layer transmission on a DMRS antenna port upon detection of a PDCCH with DCI format 2C, the requirements are specified in Table 8.3.2.1J-1, with the addition of the parameters in Table 8.3.2.1J-2 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 DMRS antenna port with a simultaneous transmission on one of the other DMRS antenna port with or without DMRS enhancement table and 4 orthogonal DMRS ports (dmrs-Enhancements-r13 UE-EUTRA-Capability [7]). Table 8.3.2.1J-1: Test Parameters for Minimun Performance Requirement - Single-layer Spatial Multiplexing with assistance information for simultaneous transmition interfering PDSCH (FRC) Table 8.3.2.1J-2: Minimum performance for Minimun Performance Requirement - Single-layer Spatial Multiplexing with assistance information for simultaneous transmition interfering PDSCH (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.3.2.1J |
2,333 | – DMRS-BundlingPUSCH-Config | The IE DMRS-BundlingPUSCH-Config-r17 is used to configure DMRS bundling for PUSCH. DMRS-BundlingPUSCH-Config information element -- ASN1START -- TAG-DMRS-BUNDLINGPUSCH-CONFIG-START DMRS-BundlingPUSCH-Config-r17 ::= SEQUENCE { pusch-DMRS-Bundling-r17 ENUMERATED {enabled} OPTIONAL, -- Need R pusch-TimeDomainWindowLength-r17 INTEGER (2..32) OPTIONAL, -- Need S pusch-WindowRestart-r17 ENUMERATED {enabled} OPTIONAL, -- Need R pusch-FrequencyHoppingInterval-r17 ENUMERATED {s2, s4, s5, s6, s8, s10, s12, s14, s16, s20} OPTIONAL, -- Need S ... } -- TAG-DMRS-BUNDLINGPUSCH-CONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,334 | 6.29.1 Description | The 5G system is expected to support advanced capabilities and performance of messaging service especially for massive IoT communication which are introduced by the MSGin5G Service [22]. The MSGin5G Service provides one to one, group and broadcast message services for thing-to-thing and person-to-thing communication with low end-to-end latency and high reliability of message delivery, in a resource efficient manner to optimize the resource usage of the both control plane and user plane in the network, and power saving in the user devices. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.29.1 |
2,335 | 5.7.3.5 Packet Error Rate | The Packet Error Rate (PER) defines an upper bound for the rate of PDUs (e.g. IP packets) that have been processed by the sender of a link layer protocol (e.g. RLC in RAN of a 3GPP access) but that are not successfully delivered by the corresponding receiver to the upper layer (e.g. PDCP in RAN of a 3GPP access). Thus, the PER defines an upper bound for a rate of non-congestion related packet losses. The purpose of the PER is to allow for appropriate link layer protocol configurations (e.g. RLC and HARQ in RAN of a 3GPP access). For every 5QI the value of the PER is the same in UL and DL. For GBR QoS Flows with Delay-critical GBR resource type, a packet which is delayed more than PDB is counted as lost, and included in the PER unless the data burst is exceeding the MDBV within the period of PDB or the QoS Flow is exceeding the GFBR. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.7.3.5 |
2,336 | 5.2.2.4 Substate when back to state EMM-DEREGISTERED from another EMM state | When returning to state EMM-DEREGISTERED, the UE shall select a cell as specified in 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [21]. The substate depends on the result of the cell selection procedure, the outcome of the previously performed EMM specific procedures, on the EPS update status of the UE, on the tracking area data stored in the UE, on the presence of the USIM, on the UE configuration and on the reason for moving to EMM-DEREGISTERED: - If no cell has been found, the substate is NO-CELL-AVAILABLE, until a cell is found. - If no USIM is present or if the inserted USIM is considered invalid by the UE, the substate shall be NO-IMSI. - If a suitable cell has been found and the PLMN or tracking area is not in the forbidden list, the substate shall be NORMAL-SERVICE. - If an attach shall be performed (e.g. network requested re-attach), the substate shall be ATTEMPTING-TO-ATTACH. - If a PLMN reselection (according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]) is needed, the substate shall be PLMN-SEARCH. - If the selected cell is known not to be able to provide normal service, the substate shall be LIMITED-SERVICE; - If the selected cell is a non-3GPP cell, the substate shall be NO-CELL-AVAILABLE; and - If the UE is configured for eCall only mode as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17], T3444 and T3445 have expired or are not running, and substate PLMN-SEARCH is not required, the substate shall be eCALL-INACTIVE. | 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.2.2.4 |
2,337 | 6.4.4.2 NAS confidentiality activation | NAS confidentiality shall be activated using the NAS SMC procedure or after an inter-system handover from EPC. Once NAS confidentiality has been activated, NAS messages without confidentiality protection shall not be accepted by the UE or the AMF. Before NAS confidentiality has been activated, NAS messages without confidentiality protection shall only be accepted by the UE or the AMF in certain cases where it is not possible to apply confidentiality protection. NAS confidentiality shall stay activated until the 5G security context is deleted in either the UE or the AMF. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.4.4.2 |
2,338 | K.2.2.4 Configuration for PTP grandmaster function | The following options may be supported (per DS-TT) for the 5GS to generate the Sync, Follow_Up and Announce messages for the Leader ports on the DS-TT: a) NW-TT generates the Sync, Follow_Up and Announce messages on behalf of DS-TT (e.g. if DS-TT does not support this). b) DS-TT generates the Sync, Follow_Up and Announce messages in this DS-TT. TSN AF and TSCTSF may use the elements in port and user plane node management information container to determine the PTP grandmaster functionality supported by DS-TT and NW-TT and may configure the DS-TT and NW-TT ports to operate as in option a) or b) as follows: - The "PTP grandmaster capable" element and the "gPTP grandmaster capable" element in PMIC are used to indicate the support for PTP or gPTP grandmaster capability, respectively, in each DS-TT. If the TSN AF or TSCTSF determines the DS-TT supports grandmaster capability (PTP or gPTP grandmaster capable is TRUE), then either option a) or b) can be used for the PTP instance(s) in the DS-TT. Otherwise, only option a) can be used for the PTP instance(s) in the DS-TT. - To enable option a) for PTP ports in DS-TT, the TSN AF or TSCTSF sets the element "Grandmaster on behalf of DS-TT enabled" TRUE (per PTP instance per DS-TT) in UMIC for the respective DS-TT port, and the TSN AF or TSCTSF sets the element "Grandmaster enabled" FALSE (per PTP instance per DS-TT) in PMIC to the respective DS-TT port. - To enable option b) for PTP ports in DS-TT, the TSN AF or TSCTSF sets the element "Grandmaster on behalf of DS-TT enabled" FALSE in UMIC (per PTP instance per DS-TT) for the respective port, and the TSN AF or TSCTSF sets the element "Grandmaster enabled" TRUE (per PTP instance per DS-TT) in PMIC to the respective DS-TT port. - To enable either option a) or option b) for a PTP instance, the TSN AF or TSCTSF sets the element "Grandmaster candidate enabled" TRUE (per PTP instance) in UMIC. - When option b) is used for one or more PTP ports in DS-TT(s), the TSN AF or TSCTSF shall use the elements in defaultDS in PMIC for the respective DS-TT(s) and in UMIC for NW-TT to ensure that all PTP ports in the DS-TT(s) and NW-TT in particular PTP instance are distributing the same values of grandmasterPriority1, grandmasterClockQuality, grandmasterPriority2, grandmasterIdentity, and timeSource message fields in Announce messages. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | K.2.2.4 |
2,339 | I.1 Determination of traffic pattern information | As described in clause 5.27.2, the calculation of the TSCAI relies upon mapping of information for the TSN stream(s) based upon certain IEEE standard information. Additional traffic pattern parameters such as maximum burst size and maximum flow bitrate can be mapped to MDBV and GFBR. The traffic pattern parameter determination based on PSFP (IEEE Std 802.1Q [98]), when available, is as follows: - Periodicity of a TSN stream is set equal to StreamGateAdminCycleTime if there is only one StreamGateControlEntry with a StreamGateStatesValue set to Open in the StreamGateAdminControlList. If there is more than one StreamGateGateControlEntry with a StreamGateStatesValue set to Open in the StreamGateAdminControlList, then the Periodicity of the TSN Stream is set equal to sum of the timeIntervalValues from the first gate open instance to a next gate open instance in the StreamGateAdminControlList. For aggregated TSN streams with same periodicity and compatible Burst Arrival Times, the periodicity of the aggregated flow of these TSN Streams is set equal to StreamGateAdminCycleTime received from CNC for one of the TSN streams that are aggregated. NOTE 1: Given that only TSN streams that have the same periodicity and compatible Burst Arrival Time can be aggregated, the StreamGateAdminCycleTime for those TSN streams is assumed to be the same. - Burst Arrival time of a TSN stream at the ingress port is determined based on the following conditions: - The Burst Arrival Time of a TSN Stream should be set to StreamGateAdminBaseTime plus the sum of the timeIntervalValues for which the StreamGateStatesValue is Closed in the StreamGateAdminControlList until the first gate open time (i.e. until StreamGateStatesValue set to Open is found). If the StreamGateStatesValue is Open for the first timeIntervalValue, then the Burst Arrival time is set to StreamGateAdminBaseTime. For aggregated TSN streams, the arrival time is calculated similarly, but using the time interval to the first StreamGateStatesValue that is Open from the aggregated TSN streams. - Burst Size of a TSN stream at the ingress port (which is useful to map to MDBV) is determined based on the following conditions: - The Burst Size may be determined from TSN Stream gate control operations in the StreamGateAdminControlList. If in the StreamGateAdminControlList, IntervalOctetMax is provided for a StreamGateControlEntry with an "open" StreamGateStatesValue, the Burst Size is set to the IntervalOctetMax for that control list entry. If IntervalOctetMax is not provided, the Burst Size is set to the timeIntervalValue (converted from ns to s) of the StreamGateControlEntry with an "open" StreamGateStatesValue multiplied by the port bitrate. - When multiple compatible TSN Streams are aggregated, the Burst Size is set to the sum of the Burst Sizes for each TSN stream as determined above. - Maximum Flow Bitrate of a TSN stream (which is useful to map to GBR) is determined as follows: - The Maximum Flow Bitrate of a TSN Stream is equal to the summation of all timeIntervalValue (converted from ns to s) with StreamGateStatesValue = Open, multiplied by the bitrate of the corresponding port, and divided by StreamGateAdminCycleTime. For aggregated TSN streams, the same calculation is performed over the burst of aggregated streams (calculated using superposition, i.e. timeIntervalValue with StreamGateStatesValue = Open of every stream is summed up, as they are assumed to have same periodicity, compatible Burst arrival time, and same traffic class if they are to be aggregated. When CNC configures the PSFP information to the TSN AF, the TSN AF may use local information (e.g. local configuration) to map the PSFP information to an ingress port and/or egress port of the 5GS bridge. NOTE 2: As an example, for the local configuration, the PSFP can use either the destination MAC address and VLAN identifier, or the source MAC address and VLAN identifier for stream identification. The TSN AF is pre-configured with either the MAC address of Ethernet hosts behind a given DS-TT port (identified by the DS-TT port MAC address), or the VLAN identifier used over a given DS-TT port, or both. When the TSN AF determines that one of the known Ethernet host's MAC address appears as a source or destination MAC address, it can identify that the ingress or egress port is the associated DS-TT port. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | I.1 |
2,340 | 5.4.4.4 Generic UE configuration update completion by the network | Upon receipt of the CONFIGURATION UPDATE COMPLETE message, the AMF shall stop the timer T3555. If a new 5G-GUTI was included in the CONFIGURATION UPDATE COMMAND message, the AMF shall consider the new 5G-GUTI as valid and the old 5G-GUTI as invalid. If a new TAI list was included in the CONFIGURATION UPDATE COMMAND message, the AMF shall consider the new TAI list as valid and the old TAI list as invalid. If a new truncated 5G-S-TMSI configuration was included in the CONFIGURATION UPDATE COMMAND message, the AMF shall consider the new truncated 5G-S-TMSI configuration as valid and the old truncated 5G-S-TMSI configuration as invalid. If a new service area list was included in the CONFIGURATION UPDATE COMMAND message, the AMF shall consider the new service area list as valid and the old service area list as invalid. If new allowed NSSAI information was included in the CONFIGURATION UPDATE COMMAND message, the AMF shall consider the new allowed NSSAI information as valid and the old allowed NSSAI information as invalid. If new configured NSSAI information was included in the CONFIGURATION UPDATE COMMAND message, the AMF shall consider the new configured NSSAI information as valid and the old configured information as invalid. If there are active PDU sessions associated with S-NSSAI(s) not included in the new allowed NSSAI, the AMF shall notify the SMF(s) associated with these PDU sessions to initiate the network-requested PDU session release procedure according to subclause 6.3.3 in the present specification and subclause 5.15.5.2.2 in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]. If "registration requested" was indicated in the Registration requested bit of the Configuration update indication IE in the CONFIGURATION UPDATE COMMAND message and: a) the CONFIGURATION UPDATE COMMAND message contained: 1) an allowed NSSAI, a configured NSSAI or both; 2) the Network slicing indication IE with the Network slicing subscription change indication set to "Network slicing subscription changed"; or 3) no other parameters; and b) no emergency PDU session has been established for the UE; then the AMF shall initiate the release of the N1 NAS signalling connection. If an LADN information IE was included in the CONFIGURATION UPDATE COMMAND message, the AMF shall consider the old LADN information as invalid and the new LADN information as valid, if any. If an Extended LADN information IE was included in the CONFIGURATION UPDATE COMMAND message, the AMF shall consider the old extended LADN information as invalid and the new extended LADN information as valid. If a T3447 value was included in the CONFIGURATION UPDATE COMMAND message, the AMF shall consider the T3447 value as valid and if neither zero nor deactivated use the T3447 value with the timer T3447 next time it is started. If the T3447 value included in the CONFIGURATION UPDATE COMMAND message contained an indication that the timer is deactivated or timer value zero, then the AMF shall stop the timer T3447 if running. If a CAG information IE or an Extended CAG information IE was included in the CONFIGURATION UPDATE COMMAND message, the AMF shall consider the new "CAG information list" as valid and the old "CAG information list" as invalid. If a UE radio capability ID IE was included in the CONFIGURATION UPDATE COMMAND message, the AMF shall consider the new UE radio capability ID as valid and the old UE radio capability ID as invalid. If an Updated PEIPS assistance information IE was included in the CONFIGURATION UPDATE COMMAND message, the AMF shall consider the new PEIPS assistance information as valid and the old PEIPS assistance information, if any, as invalid. | 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.4 |
2,341 | 4.3.2.2 Network/Access network selection | It is the means by which a UE selects a PLMN/Access network from which to gain connectivity. The network/access network selection procedure varies for different access technologies. For 3GPP access networks, the network selection principles are described in TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [10]. For 3GPP access networks, the access network selection procedures are described in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5], TS 43.022[ None ] [11] and TS 25.304[ None ] [12]. Architectural impacts stemming from support for network/access network selection procedures for non-3GPP access and between 3GPP access and non-3GPP accesses are described in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [2]. | 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.2.2 |
2,342 | D.1.1 Service area and connection density | The maximum service volume in motion control is currently set by hoisting solutions, i.e. cranes, and by the manipulation of large machine components, e.g. propeller blades of wind-energy generators. Cranes can be rather wide and quite high above the shop floor, even within a factory hall. In addition, they typically travel along an entire factory hall. An approximate dimension of the service area is 100 x 100 x 30 m. Note that production cells are commonly much smaller (< 10 x 10 x 3 m). There are typically about 10 motion-control connections in a production cell, which results in a connection density of up to 105 km-2. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | D.1.1 |
2,343 | 6.3.13.3 Authorization of C2 communication | The network supports C2 communication authorization for pairing of UAV and UAV-C. The pairing of UAV and UAV-C needs to be authorized by USS successfully before the user plane connectivity for C2 communication (over Uu or over NR-PC5) is enabled. The UE supporting UAS services may provide the network with an identification information of UAV-C to pair with, if available, via the protocol configuration options as follows: - If the UE uses a common PDN connectivity for both USS communication and C2 communication with a UAV-C, the C2 communication with the UAV-C can be authorized using UUAA-SM procedure during the PDN connectivity procedure or during the bearer resource modification procedure. If the pairing of UAV and UAV-C is revoked, the network shall disable C2 communication for the PDN connection. NOTE 1: The network can disable C2 communication for the PDN connection e.g., by removing the packet filter(s) allocated for C2 communication during EPS bearer context modification procedure as specified in clause 6.4.3 or by deactivating the EPS bearer context for C2 communication during EPS bearer context deactivation procedure as specified in clause 6.4.4. - If the UE uses separate PDN connectivity for, respectively, USS communication and C2 communication with a UAV-C, the C2 communication with the UAV-C is authorized using UUAA-SM during the PDN connectivity procedure. If the pairing of UAV and UAV-C is revoked, the PDN connectivity or C2 communication shall be released by the network. The authorization of direct C2 communication can be performed during the C2 communication authorization procedure. NOTE 2: The C2 authorization payload in the service-level-AA payload, sent to the network via the protocol configuration options, can include an indication of the request for direct C2 communication and pairing information for direct C2 communication (see subclauses 6.4.3.3 and 6.5.1.2). The authorization of UAV flight can also be performed during the C2 communication authorization procedure. The UE supporting UAS services provides flight authorization information to the network via the protocol configuration options if the flight authorization information is already available in the UE. | 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.3.13.3 |
2,344 | 5.8.9.1a.1 Sidelink DRB release | 5.8.9.1a.1.1 Sidelink DRB release conditions For NR sidelink communication, a sidelink DRB release is initiated in the following cases: 1> for groupcast, broadcast and unicast, if slrb-Uu-ConfigIndex (if any) of the sidelink DRB is included in sl-RadioBearerToReleaseList in sl-ConfigDedicatedNR; or 1> for groupcast and broadcast, if no sidelink QoS flow with data indicated by upper layers is mapped to the sidelink DRB for transmission, which is (re)configured by receiving SIB12 or SidelinkPreconfigNR; or 1> for groupcast, broadcast and unicast, if SL-RLC-BearerConfigIndex (if any) of the associated RLC entity(ies) (i.e., including the additional sidelink RLC bearer if applicable) for the sidelink DRB is included in sl-RLC-BearerToReleaseList/sl-RLC-BearerToReleaseListSizeExt in sl-ConfigDedicatedNR; or 1> for unicast, if no sidelink QoS flow with data indicated by upper layers is mapped to the sidelink DRB for transmission, which is (re)configured by receiving SIB12 or SidelinkPreconfigNR, and if no sidelink QoS flow mapped to the sidelink DRB, which is (re)configured by receiving RRCReconfigurationSidelink, has data; or 1> for unicast, if SLRB-PC5-ConfigIndex (if any) of the sidelink DRB is included in slrb-ConfigToReleaseList in RRCReconfigurationSidelink or if sl-ResetConfig is included in RRCReconfigurationSidelink; or 1> for unicast, when the corresponding PC5-RRC connection is released due to sidelink RLF being detected, according to clause 5.8.9.3; or 1> for unicast, when the corresponding PC5-RRC connection is released due to upper layer request according to clause 5.8.9.5. 5.8.9.1a.1.2 Sidelink DRB release operations For each sidelink DRB, whose sidelink DRB release conditions are met as in clause 5.8.9.1a.1.1, the UE capable of NR sidelink communication that is configured by upper layers to perform NR sidelink communication shall: 1> for groupcast and broadcast; or 1> for unicast, if the sidelink DRB release was triggered after the reception of the RRCReconfigurationSidelink message; or 1> for unicast, after receiving the RRCReconfigurationCompleteSidelink message, if the sidelink DRB release was triggered due to the configuration received within the sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR or indicated by upper layers: 2> release the PDCP entity for NR sidelink communication associated with the sidelink DRB; 2> if SDAP entity for NR sidelink communication associated with this sidelink DRB is configured: 3> indicate the release of the sidelink DRB to the SDAP entity associated with this sidelink DRB (TS 37.324[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Service Data Adaptation Protocol (SDAP) specification ] [24], clause 5.3.3); 2> release SDAP entities for NR sidelink communication, if any, that have no associated sidelink DRB as specified in TS 37.324[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Service Data Adaptation Protocol (SDAP) specification ] [24] clause 5.1.2; 1> for groupcast and broadcast; or 1> for unicast, after receiving the RRCReconfigurationCompleteSidelink message, if the sidelink DRB release was triggered due to the configuration received within the sl-ConfigDedicatedNR: 2> for each sl-RLC-BearerConfigIndex included in the received sl-RLC-BearerToReleaseList/sl-RLC-BearerToReleaseListSizeExt that is part of the current UE sidelink configuration: 3> release the RLC entity and the corresponding logical channel for NR sidelink communication, associated with the sl-RLC-BearerConfigIndex. 1> for unicast, if the sidelink DRB release was triggered due to the reception of the RRCReconfigurationSidelink message; or 1> for unicast, after receiving the RRCReconfigurationCompleteSidelink message, if the sidelink DRB release was triggered due to the configuration received within the SIB12, SidelinkPreconfigNR or indicated by upper layers: 2> release the RLC entity and the corresponding logical channel for NR sidelink communication associated with the sidelink DRB; 2> perform the sidelink UE information procedure in clause 5.8.3 for unicast if needed. 1> if the sidelink radio link failure is detected for a specific destination: 2> release the PDCP entity, RLC entity and the logical channel of the sidelink DRB for the specific destination. Editor's Note: FFS on how to release SL DRB on E2E and hop configuration for U2U relay. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.9.1a.1 |
2,345 | 7.5.3 EPS session management | The following UE procedures shall apply for handling an error encountered with a mandatory information element in an ESM message: a) If the message is an ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST, an ACTIVATE DEFAULT EPS BEARER CONTEXT REJECT message with ESM cause #96 "invalid mandatory information", shall be returned. b) If the message is an ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST, an ACTIVATE DEDICATED EPS BEARER CONTEXT REJECT message with ESM cause #96 "invalid mandatory information", shall be returned. c) If the message is a MODIFY EPS BEARER CONTEXT REQUEST, a MODIFY EPS BEARER CONTEXT REJECT message with ESM cause #96 "invalid mandatory information", shall be returned. d) If the message is a DEACTIVATE EPS BEARER CONTEXT REQUEST, a DEACTIVATE EPS BEARER CONTEXT ACCEPT message shall be returned. All resources associated with that EPS bearer shall be released. The following network procedures shall apply for handling an error encountered with a mandatory information element in an ESM message: a) If the message is a PDN CONNECTIVITY REQUEST, a PDN CONNECTIVITY REJECT message with ESM cause #96 "invalid mandatory information", shall be returned. b) If the message is a PDN DISCONNECT REQUEST, a PDN DISCONNECT REJECT message with ESM cause #96 "invalid mandatory information", shall be returned. c) If the message is a BEARER RESOURCE ALLOCATION REQUEST, a BEARER RESOURCE ALLOCATION REJECT message with ESM cause #96 "invalid mandatory information", shall be returned. d) If the message is a BEARER RESOURCE MODIFICATION REQUEST, a BEARER RESOURCE MODIFICATION REJECT message with ESM cause #96 "invalid mandatory information", shall be returned. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 7.5.3 |
2,346 | 8.11.2 Initial Registration – separate PLMN signalling | The signalling flow for Initial Registration for network sharing with multiple cell-ID broadcast with separate per-PLMN signalling is shown in Figure 8.11.2-1. In this example message flow - the UE is assumed to not provide an ue-Identity from which the DU is able to deduce the PLMN ID. - each F1-C interface instance uses a separate signalling transport or share signalling transport with other F1-C interface instances. - the gNB-DUA/B entity shown in Figure 8.11.2-1 is a simplified representation of the gNB-DUA of PLMN A, the gNB DUB of PLMN B and respective radio resources of the shared cell. Figure 8.11.2-1: UE Initial Access procedure and network sharing with multiple cell-ID broadcast NOTE: Steps 1-5 are defined in clause 8.1. Note, that the selectedPLMN-Identity is provided in step 5. 6. The gNB-DUA sends the F1AP UE CONTEXT RELEASE REQUEST message to the gNB-CUA. including a Cause set to "PLMN not served by the CU". 7. The gNB-DUB sends the F1AP INITIAL UL RRC MESSAGE to the gNB-CUB. including the NR CGI associated with PLMNB, the C-RNTI indicated by the gNB-DUA at step 2, and the RRC-Container IE and the RRC-Container-RRCSetupComplete IE with the RRC message received in step1 and step 5 respectively. The RRC-Container-RRCSetupComplete IE are included in the INITIAL UL RRC MESSAGE TRANSFER for the case of network sharing and shall contain the RRC messages received via the RRC UL-DCCH-Message IE from the UE, but never previously sent to the gNB-CUB. 8. The gNB-CUA sends the UE CONTEXT RELEASE COMMAND message to the gNB-DU. 9. The gNB-DU sends the UE CONTEXT RELEASE COMPLETE message to the gNB-CUA. NOTE: Initiating procedures from gNB-DUA towards gNB-CUA and from gNB-DUB to gNB-CUB in parallel is not precluded. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.11.2 |
2,347 | 4.4.2.5 Establishment of secure exchange of NAS messages | Secure exchange of NAS messages via a NAS signalling connection is usually established by the AMF during the registration procedure by initiating a security mode control procedure. After successful completion of the security mode control procedure, all NAS messages exchanged between the UE and the AMF are sent integrity protected using the current 5G security algorithms, and except for the messages specified in subclause 4.4.5, all NAS messages exchanged between the UE and the AMF are sent ciphered using the current 5G security algorithms. During inter-system change from S1 mode to N1 mode in 5GMM-CONNECTED mode, secure exchange of NAS messages is established between the AMF and the UE by: a) the transmission of NAS security related parameters encapsulated in the AS signalling from the AMF to the UE triggering the inter-system change in 5GMM-CONNECTED mode (see 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]). The UE uses these parameters to generate the mapped 5G NAS security context (see subclause 8.6.2 of 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]); and b) after the inter-system change in 5GMM-CONNECTED mode, the transmission of a REGISTRATION REQUEST message from the UE to the AMF. The UE shall send this message integrity protected using the mapped 5G NAS security context and further protect this message as specified in subclause 4.4.6 and subclause 5.5.1.3.2. After the AMF receives the REGISTRATION REQUEST message: 1) if the AMF decides to take the native 5G NAS security context into use, the security mode control procedure is performed. From this time onward, all NAS messages exchanged between the UE and the AMF are sent integrity protected using the native 5G NAS security context, and except for the messages specified in subclause 4.4.5, all NAS messages exchanged between the UE and the AMF are sent ciphered using the native 5G NAS security context; or 2) if the AMF decides to take the mapped 5G NAS security context into use, from this time onward, all NAS messages exchanged between the UE and the AMF are sent integrity protected using the mapped 5G NAS security context, and except for the messages specified in subclause 4.4.5, all NAS messages exchanged between the UE and the AMF are sent ciphered using the mapped 5G NAS security context. During inter-system change from S1 mode to N1 mode in 5GMM-IDLE mode, if the UE is operating in single-registration mode and: a) if the UE has a valid native 5G NAS security context, the UE shall transmit a REGISTRATION REQUEST message integrity protected with the native 5G NAS security context. The UE shall include the ngKSI indicating the native 5G NAS security context value in the REGISTRATION REQUEST message. After receiving the REGISTRATION REQUEST message including the ngKSI indicating a native 5G NAS security context value, the AMF shall check whether the ngKSI included in the REGISTRATION REQUEST message belongs to a 5G NAS security context available in the AMF, and shall verify the MAC of the REGISTRATION REQUEST message. If the verification is successful, the AMF deletes the EPS security context received from the source MME if any, and the AMF re-establishes the secure exchange of NAS messages by either: 1) replying with a REGISTRATION ACCEPT message that is integrity protected and ciphered using the native 5G NAS security context. From this time onward, all NAS messages exchanged between the UE and the AMF are sent integrity protected and except for the messages specified in subclause 4.4.5, all NAS messages exchanged between the UE and the AMF are sent ciphered; or 2) initiating a security mode control procedure. This can be used by the AMF to take a non-current 5G NAS security context into use or to modify the current 5G NAS security context by selecting new NAS security algorithms. b) if the UE has no valid native 5G NAS security context, the UE shall send the REGISTRATION REQUEST message without integrity protection and encryption. After receiving the REGISTRATION REQUEST message without integrity protection and encryption: 1) if N26 interface is supported: i) if an EPS security context received from the source MME does not include the NAS security algorithms set to EIA0 and EEA0, the AMF shall either create a fresh mapped 5G NAS security context (see subclause 8.6.2 of 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]) or trigger a primary authentication and key agreement procedure to create a fresh native 5G NAS security context; or ii) if an EPS security context received from the source MME includes the NAS security algorithms set to EIA0 and EEA0, the AMF shall trigger a primary authentication and key agreement procedure to create a fresh native 5G NAS security context; or 2) if N26 interface is not supported, the AMF shall trigger a primary authentication and key agreement procedure. The newly created 5G NAS security context is taken into use by initiating a security mode control procedure and this context becomes the current 5G NAS security context in both the UE and the AMF. This re-establishes the secure exchange of NAS messages. During an N1 mode to N1 mode handover, secure exchange of NAS messages is established between the AMF and the UE by: - the transmission of NAS security related parameters encapsulated in the AS signalling from the target AMF to the UE triggering the N1 mode to N1 mode handover (see 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]). The UE uses these parameters to create a new 5G NAS security context. The secure exchange of NAS messages shall be continued after N1 mode to N1 mode handover. It is terminated after inter-system change from N1 mode to S1 mode in 5GMM-CONNECTED mode or when the NAS signalling connection is released. When a UE in 5GMM-IDLE mode establishes a new NAS signalling connection and has a valid current 5G NAS security context, the UE shall transmit the initial NAS message integrity protected with the current 5G NAS security context and further protect this message as specified in subclause 4.4.6. The UE shall include the ngKSI indicating the current 5G NAS security context value in the initial NAS message. The AMF shall check whether the ngKSI included in the initial NAS message belongs to a 5G NAS security context available in the AMF, and shall verify the MAC of the NAS message. If the verification is successful, the AMF may re-establish the secure exchange of NAS messages: a) by replying with a NAS message that is integrity protected and ciphered using the current 5G NAS security context. From this time onward, all NAS messages exchanged between the UE and the AMF are sent integrity protected and except for the messages specified in subclause 4.4.5, all NAS messages exchanged between the UE and the AMF are sent ciphered; or b) by initiating a security mode control procedure. This can be used by the AMF to take a non-current 5G NAS security context into use or to modify the current 5G NAS security context by selecting new NAS security algorithms. When a UE attempts multiple registrations in the same or different serving network, both the AMF and the UE shall follow the behavior specified in subclause 6.3.2 of 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. The UE may support multiple records of NAS security context storage for multiple registration (see 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [22]). If the UE supports multiple records of NAS security context storage for multiple registration, the UE can select the appropriate one among the stored 5G security contexts to protect the initial NAS message (see 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]). NOTE: For the case when the UE has two records of NAS security context stored and is attempting registration to the PLMN associated with the 5G-GUTI (or an equivalent PLMN) for that access, the UE uses the first NAS security context of that access to protect the initial NAS message. For the case when the UE has two records of NAS security context stored and is attempting registration to the PLMN associated with the second record (or an equivalent PLMN) of that access, the UE uses the second NAS security context of that access to protect the initial NAS message. For other cases when the UE has two records of NAS security context stored and is attempting registration to a PLMN which is not associated with any NAS security context record, the UE uses either record of the NAS security context of that access to protect the initial NAS message. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.4.2.5 |
2,348 | 4.2.5 Data Storage architectures | As depicted in Figure 4.2.5-1, the 5G System architecture allows any NF to create/read/update/delete its unstructured data in a UDSF (e.g. UE contexts). If such an NF is using UDSF is part of an NF set, then any of the NF instance within this NF set may read/update/delete the unstructured data that was created by this NF. The UDSF belongs to the same PLMN where the network function is located. CP NFs/NF Sets may share a UDSF for storing their respective unstructured data or may each have their own UDSF (e.g. a UDSF may be located close to the respective NF). NOTE 1: Structured data in this specification refers to data for which the structure is defined in 3GPP specifications. Unstructured data refers to data for which the structure is not defined in 3GPP specifications. NOTE 2: If a NF Set has its own UDSF, it is up to UDSF implementation and deployment that only the NF instance within the set can access the data created by another NF instance within the NF set. If a UDSF is shared between several NFs not part of the same set or is shared between several NF sets, it is up to UDSF implementation and deployment to make sure that only NFs that are authorized can access the data. For further information about Guidelines and Principles for Compute-Storage Separation see Annex C. Figure 4.2.5-1: Data Storage Architecture for unstructured data from any NF NOTE 3: 3GPP will specify (possibly by referencing) the N18/Nudsf interface. As depicted in Figure 4.2.5-2, the 5G System architecture allows the UDM, PCF and NEF to store data in the UDR, including subscription data and policy data by UDM and PCF, structured data for exposure and application data (including Packet Flow Descriptions (PFDs) for application detection, AF request information for multiple UEs) by the NEF. UDR can be deployed in each PLMN and it can serve different functions as follows: - UDR accessed by the NEF belongs to the same PLMN where the NEF is located. - UDR accessed by the UDM belongs to the same PLMN where the UDM is located if UDM supports a split architecture. - UDR accessed by the PCF belongs to the same PLMN where the PCF is located. NOTE 4: The UDR deployed in each PLMN can store application data for roaming subscribers. Figure 4.2.5-2: Data Storage Architecture NOTE 5: There can be multiple UDRs deployed in the network, each of which can accommodate different data sets or subsets, (e.g. subscription data, subscription policy data, data for exposure, application data) and/or serve different sets of NFs. Deployments where a UDR serves a single NF and stores its data, and, thus, can be integrated with this NF, can be possible. NOTE 6: The internal structure of the UDR in figure 4.2.5-2 is shown for information only. The Nudr interface is defined for the network functions (i.e. NF Service Consumers), such as UDM, PCF and NEF, to access a particular set of the data stored and to read, update (including add, modify), delete, and subscribe to notification of relevant data changes in the UDR. Each NF Service Consumer accessing the UDR, via Nudr, shall be able to add, modify, update or delete only the data it is authorised to change. This authorisation shall be performed by the UDR on a per data set and NF service consumer basis and potentially on a per UE, subscription granularity. The following data in the UDR sets exposed via Nudr to the respective NF service consumer and stored shall be standardized: - Subscription Data, - Policy Data, - Structured Data for exposure, - Application data: Packet Flow Descriptions (PFDs) for application detection and AF request information for multiple UEs, as defined in clause 5.6.7. The service based Nudr interface defines the content and format/encoding of the 3GPP defined information elements exposed by the data sets. In addition, it shall be possible to access operator specific data sets by the NF Service Consumers from the UDR as well as operator specific data for each data set. NOTE 7: The content and format/encoding of operator specific data and operator specific data sets are not subject to standardization. NOTE 8: The organization of the different data stored in the UDR is not to be standardized. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2.5 |
2,349 | 6.3.14 Handling of URSP provisioning | The UE can perform the UE requested PDN connectivity procedure to transport the URSP provisioning in EPS support indicator as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] from the UE to the network and a related URSP provisioning in EPS support indicator from the network to the UE. The successful exchange of the URSP provisioning in EPS support indicators, if the extended protocol configuration options is supported by the network and the UE end-to-end for the PDN connection as specified in subclause 6.6.1.1, enables the UE to thereafter perform the UE requested bearer resource modification procedure to transport a UE policy container with the length of two octets as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] from the UE to the network to transfer the UE STATE INDICATION message as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] annex D. Thereafter, the network can initiate the EPS bearer context modification procedure or the dedicated EPS bearer context activation procedure to transport UE policy container with the length of two octets as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] from the network to the UE. The UE can transport UE policy container with the length of two octets from the UE to the network using the EPS bearer context modification procedure or the dedicated EPS context activation procedure. The UE policy container with the length of two octets enable the transfer of the messages specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] annex D. If the UE while in N1 mode has indicated support for URSP provisioning in EPS as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] annex D, the UE performs inter-system change from N1 mode to S1 mode, the UE has not yet provided a UE policy container with the length of two octets to the network as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] during the dedicated EPS bearer context activation procedure, or EPS bearer context modification procedure, then the network can send a UE policy container with the length of two octets to the UE as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] during the dedicated EPS bearer context activation procedure, or EPS bearer context modification procedure on any PDN connection. | 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.3.14 |
2,350 | 6.8.6.1 UMTS security context | A UMTS security context in UTRAN is only established for UMTS subscribers. At the network side, four cases are distinguished: a) In case of an intersystem change to a GSM BSS controlled by the same SGSN, the SGSN derives the 64-bit GSM cipher key Kc from the UMTS cipher/integrity keys CK and IK agreed during the latest UMTS AKA procedure (using the conversion function c3) and applies it if the selected GEA ciphering algorithm requires a 64-bit key. b) In case of an intersystem change to a GSM BSS controlled by another R99+ SGSN, the initial SGSN sends the UMTS cipher/integrity keys CK and IK agreed during the latest UMTS AKA procedure to the new SGSN. The new SGSN stores the keys, derives the 64-bit GSM cipher key Kc and applies the latter. The new SGSN becomes the new anchor point for the service. c) In case of an intersystem change to a GSM BSS controlled by a R98- SGSN, the initial SGSN derives the GSM cipher key Kc from the UMTS cipher/integrity keys CK and IK agreed during the latest UMTS AKA procedure and sends the GSM cipher key Kc to the new SGSN. The new SGSN stores the GSM cipher key Kc and applies it. The new SGSN becomes the new anchor point for the service. d) In case of a handover to another Rel-9+ SGSN, the initial SGSN sends the UMTS cipher/integrity keys CK and IK agreed at the latest UMTS AKA procedure to the new SGSN. The new SGSN derives the 64-bit Kc. The new SGSN stores the keys. If the new SGSN selects a GEA ciphering algorithm requiring a 128-bit key, the new SGSN shall compute Kc128 from the CK/IK and shall apply it. If the new SGSN selects a GEA ciphering algorithm requiring a 64-bit key then Kc shall be applied. The new SGSN becomes the new anchor point for the service. At the user side, in all cases, the ME applies the derived 64-bit GSM cipher key Kc received from the USIM during the latest UMTS AKA procedure if the selected GEA ciphering algorithm requires a 64-bit key. If the selected GEA ciphering algorithm requires a 128-bit key, the ME shall derive 128-bit GSM cipher key Kc128 from the CK and IK agreed during the latest UMTS AKA and apply it. In case the current UMTS security context is mapped from an EPS security context and there has been no UMTS AKA run since the current UMTS security context was mapped, the CK , IK and Kc belonging to the mapped UMTS security context shall be considered to be the keys from the latest AKA. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 6.8.6.1 |
2,351 | 8.9.11 IAB-node OAM | NOTE: The general principles and procedures described in this clause does not apply to ng-eNB. The IAB-node receives commands, configuration data and software downloads (e.g. for equipment software upgrades) from its OAM system. The IAB-node can also send alarms and traffic counter information to its OAM system. The transport connection between the IAB-node and its OAM, using IP, is provided by the IAB-MT’s PDU session via 5G network, or the IAB-MT’s PDN connection via LTE network when IAB-MT uses EN-DC. NOTE: The transport connection between the IAB-node and its OAM may also be provided using the Backhaul IP layer by implementation. Alarms in the IAB generate bursts of high-priority traffic, to be transported in real time. Traffic counters generate bursts of traffic, but their transport need not be real-time. Configuration messages from OAM to the IAB will also generate small bursts of traffic, possibly with lower priority than alarms but still delay-sensitive: when a configuration is committed on the OAM, the time interval between the commitment and the effect on the equipment shall be small. Alarm messages and commands should be transported on a high-priority bearer, while counters may be transported on a lower priority bearer. OAM software download to the IAB may generate larger amounts of data, but both the required data rate and the priority of this kind of traffic are much lower than in the case of alarms, commands and counters. For different types of OAM traffic, it is necessary to use different DRBs between the IAB-MT and the serving DU, and different BH RLC channels for intermediate hops, with different QoS parameters. Aggregation of F1-U traffic for OAM with other F1-U traffic on the same BH RLC channels is not precluded. The QoS parameters are provided to the IAB-donor during the IAB-MT’s PDU session establishment, or the IAB-MT’s PDN connection establishment when IAB-MT uses EN-DC. NOTE: When the transport connection between the IAB-node and its OAM is provided by the Backhaul IP layer, the OAM traffic may be aggregated with other traffic types on the same BH RLC channel. The QoS for OAM is ensured by implementation. The continuity of OAM connectivity needs to be ensured as the mobile IAB-node moves across the mobile network. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.9.11 |
2,352 | 6.1.3.15 Hibernation MAC Control Elements | The Hibernation MAC control element of one octet is identified by a MAC PDU subheader with LCID as specified in table 6.2.1-1. It has a fixed size and consists of a single octet containing seven C-fields and one R-field. The Hibernation MAC control element with one octet is defined as follows (figure 6.1.3.15-1). The Hibernation MAC control element of four octets is identified by a MAC PDU subheader with LCID as specified in table 6.2.1-1. It has a fixed size and consists of a four octets containing 31 C-fields and one R-field. The Hibernation MAC control element of four octets is defined as follows (figure 6.1.3.15-2). For the case with no serving cell with a ServCellIndex (TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]) larger than 7, Hibernation MAC control element of one octet is applied, otherwise Hibernation MAC control element of four octets is applied. For the case that Hibernation MAC control element is received and Activation/Deactivation MAC control element is not received: - Ci: if there is an SCell configured with SCellIndex i as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8], this field indicates the dormant/activated status of the SCell with SCellIndex i, else the MAC entity shall ignore the Ci field. The Ci field is set to "1" to indicate that the SCell with SCellIndex i shall enter dormant state. When the Ci field is set to "0", the SCell with SCellIndex i shall be activated if it is in already activated state or dormant state, otherwise the Ci field set to "0" shall be ignored. - R: Reserved bit, set to "0". For the case that both Activation/Deactivation MAC control element and Hibernation MAC control element are received: - R: Reserved bit, set to "0". - Ci: if there is an SCell configured with SCellIndex i as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8], these fields indicate possible state transitions of the SCell with SCellIndex i, else the MAC entity shall ignore the Ci fields. The Ci fields of the two MAC control elements are interpreted according to Table 6.1.3.15-1. Figure 6.1.3.15-1: Hibernation MAC control element of one octet Figure 6.1.3.15-2: Hibernation MAC control element of four octets Table 6.1.3.15-1: MAC control elements for SCell state transitions | 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.15 |
2,353 | 5.3.1.2.3 IPv6 parameter configuration via stateless DHCPv6 | The UE may use stateless DHCPv6 for additional parameter configuration. The PDN GW acts as the DHCP server. When PLMN based parameter configuration is used, the PDN GW provides the requested parameters from locally provisioned database. When external PDN based parameter configuration is used, the PDN GW obtains the requested configuration parameters from the external PDN as described in the previous clauses. When the PDN GW acts as a DHCPv6 server towards the UE, the PDN GW may act as DHCPv6 client towards the external PDN to request the configuration parameters for the UE. If RADIUS or Diameter is used towards the external PDN as described in TS 29.061[ Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) ] [38], the requested configuration parameters can be fetched as part of these procedures. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.3.1.2.3 |
2,354 | 4.6.2.1 EMM-DEREGISTERED | In the EMM-DEREGISTERED state, the EMM context in MME holds no valid location or routing information for the UE. The UE is not reachable by a MME, as the UE location is not known. In the EMM-DEREGISTERED state, some UE context can still be stored in the UE and MME, e.g. to avoid running an AKA procedure during every Attach procedure. During the successful Inter-RAT TAU/RAU/handover procedure and ISR activated is not indicated to the UE, the old S4 SGSN/old MME changes the EMM state of the UE to GPRS-IDLE/PMM-DETACHED/EMM-DEREGISTERED. | 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.6.2.1 |
2,355 | 6.5 UE requested ESM procedures 6.5.0 General | The UE's maximum number of active EPS bearer contexts in a PLMN is determined by whichever is the lowest of the maximum number of EPS bearer identities allowed by the protocol (as specified in 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [12] clause 11.2.3.1.5), the PLMN's maximum number of EPS bearer contexts in S1 mode and the UE's implementation-specific maximum number of EPS bearer contexts. NOTE 1: Clauses 6.5.1.4 and 6.5.3.4 specify how the UE determines the PLMN's maximum number of EPS bearer contexts in S1 mode. In earlier versions of the protocol, the maximum number of simultaneously active EPS bearer contexts was limited by lower layer protocols to 8. In the present version of the protocol, the UE and the network may support a maximum number of 15 EPS bearer contexts. A UE supporting signalling for a maximum number of 15 EPS bearer contexts shall support the extended range or EPS bearer identities from 0 to 15 (as specified in 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [12] clause 11.2.3.1.5). The UE indicates support of signalling for a maximum number of 15 EPS bearer contexts by setting the 15 bearers bit in the UE Network Capability IE. A network supporting signalling for a maximum number of 15 EPS bearer contexts shall support the extended range or EPS bearer identities from 0 to 15 (as specified in 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [12] clause 11.2.3.1.5). The network indicates support of signalling for a maximum number of 15 EPS bearer contexts by setting the 15 bearers bit in the EPS network feature support IE. NOTE 2: A UE and a network not supporting signalling for a maximum number of 15 EPS bearer contexts will treat the EPS bearer identity values 1 to 4 as 'reserved' values. For a UE in NB-S1 mode, the UE's implementation-specific maximum number of active user plane radio bearers is 2 (as defined in 3GPP TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [20]) when the UE sets the Multiple DRB support bit to "Multiple DRB supported" during attach or tracking area updating procedures, and 1 otherwise. Upon an inter-system change from N1 mode to NB-S1 mode in EMM-IDLE mode for the UE operating in single-registration mode, if: a) the number of active default EPS bearer contexts in the UE is larger than the UE's implementation-specific maximum number of active user plane radio bearers; and b) the UE is using user plane CIoT EPS optimization; the UE shall locally deactivate at least one default EPS bearer context such that the total number of active default EPS bearer contexts that remained does not exceed the UE's implementation-specific maximum number of active user plane radio bearers. In this case, choosing which EPS bearer context to deactivate is implementation specific. The UE shall then include the EPS bearer context status IE in the TRACKING AREA UPDATE REQUEST message. Upon the inter-system change from A/Gb mode or Iu mode to S1 mode, for any PDN connection that has been transferred, if the PDN connection is not associated with a PDU session ID and the UE supporting N1 mode decides to enable the transfer of the PDN connection from S1 mode to N1 mode, the UE may first initiate the UE requested PDN disconnection procedure and then the UE requested PDN connectivity procedure for such PDN connection(s). As an implementation option, the UE may deactivate all EPS bearer contexts for such PDN connection(s) locally, and if the last PDN connection is not deactivated or the UE supports EMM-REGISTERED without PDN connection, the UE shall include the EPS bearer context status IE in the TRACKING AREA UPDATE REQUEST message of the tracking area updating procedure upon inter-system change from A/Gb mode or Iu mode to S1 mode, and then initiate UE requested PDN connectivity procedure for such PDN connection(s). NOTE 3: Upon the inter-system change from A/Gb mode or Iu mode to S1 mode, if a PDN connection does not support interworking with 5GS and the UE determines that the PLMN or the APN cannot support interworking with 5GS, it is recommended that a UE does not release and re-establish the PDN connection in order to enable interworking with 5GS for the PDN connection. Whether and how the UE determines the PLMN or the APN can support interworking with 5GS is implementation specific. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.5 |
2,356 | 6.8.2.1 Security handling at transitions between RRC_INACTIVE and RRC_CONNECTED states 6.8.2.1.1 General | In 5G, the RRC_INACTIVE state allows gNB/ng-eNB to suspend the UE's RRC connection while the gNB/ng-eNB and the UE continue to maintain the UE 5G AS security context. The UE RRC connection can be resumed at a later time by allowing the UE to transition into RRC__CONNECTED state. The UE may transition from RRC_INACTIVE state to RRC_CONNECTED state to the same last serving gNB/ng-eNB which sent the UE into RRC_INACTIVE state or to a different gNB/ng-eNB. While the UE is in RRC_INACTIVE state, the UE and last serving gNB/ng-eNB store the UE 5G AS security context which can be reactivated when the UE transitions from RRC_INACTIVE to RRC_CONNECTED. The gNB/ng-eNB and the UE shall behave as defined in following sub-clauses. The ng-eNB connected to 5GC shall also support the same security handling at RRC state transitions. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.8.2.1 |
2,357 | 5.3.4.2.2 Mobile Terminating Establishment | The service is indicated to the called mobile station by a SETUP message coded in the same manner as in the mobile originating call establishment. As specified for normal terminating call establishment, the service may be indicated by the called mobile station in the CALL CONFIRMED message. The destination mobile station shall perform the compatibility checking as defined in Annex B for both required modes if indicated in the SETUP message. If as a result of compatibility checking the mobile station decides to reject the call, the mobile station shall initiate call clearing according to the procedures of subclause 5.4 with one of the following causes: a) #57 "bearer capability not authorized"; b) #58 "bearer capability not presently available"; c) #65 "bearer service not implemented"; d) #88 "incompatible destination". The mobile station may accept the call if the first mode indicated is free irrespective of whether the other mode is free or busy. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.3.4.2.2 |
2,358 | 8.1.2.3E Applicability and test rules for SDR tests for 8Rx capable UEs | UE with support of 8Rx RF bands is required to fulfill the specified SDR tests for 8Rx test in section 8.7.17. For single carrier or CA SDR tests, CA configuration, bandwidth combination and MIMO layer on each CC is determined by following procedure. Select the set(s) of {CA configuration, bandwidth combination, MIMO layer} among all the supported CA configurations that leads to the largest equivalent aggregated bandwidth which does not cause the transport block bits within a TTI to exceed the capability of the category of UE under test when the defined reference channel applies on each CC. The equivalent aggregated bandwidth is defined as where is the number of CCs, and are MIMO layer and bandwidth of CC , and for and for - The procedure applies also for single carrier using operating band instead of CA configuration, and bandwidth instead of bandwidth combination. | 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.3E |
2,359 | Annex B (informative): Drafting Rules for Information flows | The following drafting rules are recommended for information flows specified in this specification in order to ensure that the Control Plane network functions can be supported with service based interfaces: 1. Information flows should describe the end to end functionality. NF services in clause 5 shall only be derived from the information flows in clause 4. 2. Information flows should strive to use type of interactions such as REQUEST/RESPONSE (e.g. location request, location response), SUBSCRIBE/NOTIFY between Core CP NFs. Any other type of interactions described should have justifications for its use. 3. Information flows should also ensure readability thus the semantics of the REQUEST/RESPONSE should still be maintained (for instance, we need to indicate PDU Session request, PDU Session response and Subscribe for UE location reporting/Notify UE location reporting) for readers and developers to understand the need for a certain transaction. NOTE: As stated in TS 23.501[ System architecture for the 5G System (5GS) ] [2], service based interface is not supported for N1, N2, N4. Thus, the rules are not meant for those interfaces. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | Annex |
2,360 | 5.2.4.2a Call activation for vSRVCC | If the MS supports vSRVCC, the MS has a voice media stream and a video media stream of a single session previously in S1 mode carried over the PS domain that are handed over to the CS domain via vSRVCC, the session associated with these media streams is in the "confirmed" state (defined in IETF RFC 3261 [137]), and the call control entity in "null" state receives indication "MM connection establishment due to vSRVCC handover", then the call control entity of the MS shall enter the "active" state, set the auxiliary state (defined in 3GPP TS 24.083[ Call Waiting (CW) and Call Hold (HOLD) supplementary services; Stage 3 ] [27]) to "idle", set the multi party auxiliary state (defined in 3GPP TS 24.084[ Multi Party (MPTY) supplementary service; Stage 3 ] [28]) to "idle" and indicate the call establishment is due to vSRVCC handover to the upper layers. The MS and the network shall locally set the TI value of the call to "000" and the TI flag value as in mobile terminated call. If the MS supports single radio PS to CS access transfer for calls in alerting state as specified in 3GPP TS 24.237[ IP Multimedia (IM) Core Network (CN) subsystem IP Multimedia Subsystem (IMS) service continuity; Stage 3 ] [136] subclause 12.2.3B, and the MS has a single voice media stream and a single video media stream carried over the PS domain that is handed over to the CS domain via vSRVCC, and the call control entity of the MS in the "null" state receives indication "MM connection establishment due to vSRVCC handover" then: - the call control entity shall indicate to the upper layers that call establishment is due to vSRVCC handover; - if the upper layers indicate that the media stream(s) is/are associated with a mobile originated session in the "early" state (defined in IETF RFC 3261 [137]) according to the conditions specified in 3GPP TS 24.237[ IP Multimedia (IM) Core Network (CN) subsystem IP Multimedia Subsystem (IMS) service continuity; Stage 3 ] [136] subclause 12.2.3B.3.2, the call control entity of the MS shall enter the "call delivered" state for this transaction. The MS and the network shall locally set the TI value of the call to "000" and the TI flag value as in mobile terminated call; and - if the upper layers indicate that the media stream(s) is/are associated with a mobile terminating session in the "early" state (defined in IETF RFC 3261 [137]) according to the conditions specified in 3GPP TS 24.237[ IP Multimedia (IM) Core Network (CN) subsystem IP Multimedia Subsystem (IMS) service continuity; Stage 3 ] [136] subclause 12.2.3B.3.1, the call control entity of the MS shall enter the "call received" state for this transaction. The MS and the network shall locally set the TI value of the call to "000" and the TI flag value as in mobile terminated call. If the MS supports single radio PS to CS SRVCC for originating calls in pre-alerting phase as specified in 3GPP TS 24.237[ IP Multimedia (IM) Core Network (CN) subsystem IP Multimedia Subsystem (IMS) service continuity; Stage 3 ] [136] subclause 12.2.3B, and the MS has a single voice media stream and a single video media stream carried over the PS domain that is handed over to the CS domain via vSRVCC, and the call control entity of the MS in the "null" state receives indication "MM connection establishment due to vSRVCC handover" then: - the call control entity shall indicate to the upper layers that call establishment is due to vSRVCC handover; and - if the upper layers indicate that the media stream(s) is/are associated with a mobile originated session in the "early" state (defined in IETF RFC 3261 [137]) according to the conditions specified in 3GPP TS 24.237[ IP Multimedia (IM) Core Network (CN) subsystem IP Multimedia Subsystem (IMS) service continuity; Stage 3 ] [136] subclause 12.2.3B.3.3, the call control entity of the MS shall enter the "mobile originating call proceeding" state for this transaction. The MS and the network shall locally set the TI value of the call to "000" and the TI flag value as in mobile terminated call. If the MS supports single radio PS to CS SRVCC for terminating calls in pre-alerting phase as specified in 3GPP TS 24.237[ IP Multimedia (IM) Core Network (CN) subsystem IP Multimedia Subsystem (IMS) service continuity; Stage 3 ] [136] subclause 12.2.3B, and the MS has a single voice media stream and a single video media stream carried over the PS domain that is handed over to the CS domain via vSRVCC, and the call control entity of the MS in the "null" state receives indication "MM connection establishment due to vSRVCC handover" then: - the call control entity shall indicate to the upper layers that call establishment is due to vSRVCC handover; and - if the upper layers indicate that the media stream(s) is/are associated with a mobile originated session in the "early" state (defined in IETF RFC 3261 [137]) according to the conditions specified in 3GPP TS 24.237[ IP Multimedia (IM) Core Network (CN) subsystem IP Multimedia Subsystem (IMS) service continuity; Stage 3 ] [136] subclause 12.2.3B.3.2, the call control entity of the MS shall enter the "call present" state for this transaction. The MS and the network shall locally set the TI value of the call to "000" and the TI flag value as in mobile terminated call. NOTE: As the MS is entering "call present" state, it must send a CALL CONFIRMED message to the network, even even the call context (including codecs) is already available at the MSC in order to enter "mobile terminating call confirmed" state. If the MS supports multicall, the MS shall locally set SI value to "1" and the MS shall assume that the network does not support multicall. The network shall also locally set SI value to "1".If the MS has a mobile originating session in the "early" state (as defined in IETF RFC 3261 [137]) and is providing an internally generated alerting indication to the user prior to the vSRVCC handover, then after transitioning from the PS domain, the MS shall continue to provide the internal alerting indication to the user. The alerting indication is stopped when the user connection is attached. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.2.4.2a |
2,361 | 6.6.2F.2.1 Minimum requirement (network signalled value "NS_02") | 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_02" is indicated in the cell, the NB-IoT channel is deployed in the lower 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.1 |
2,362 | 10.5.1.12.1 CN Common GSM-MAP NAS system information | The purpose of the CN Common GSM-MAP NAS system information element is to provide the MS with actual parameter settings of parameters relevant for both MM and GMM functionality. The coding of the information element identifier and length information is defined in the 3GPP TS 25.331[ None ] [23c]. Only the coding of the content is in the scope of the present document. The content of the CN common GSM-MAP NAS system information element is coded as shown in figure 10.5.1.12.1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.1.12.1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The length of this element content is two octets. The MS shall ignore any additional octets received. Figure 10.5.1.12.1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Common system information element Table 10.5.1.12.1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Common system information element | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.1.12.1 |
2,363 | 6.2.2.1 Keys in network entities | Keys in the ARPF The ARPF shall process the long-term key K and any other sensitive data only in its secure environment. The key K shall be 128 bits or 256 bits long. During an authentication and key agreement procedure, the ARPF shall derive CK' and IK' from K in case EAP-AKA' is used and derive KAUSF from K in case 5G AKA is used. The ARPF shall forward the derived keys to the AUSF. The ARPF holds the Home Network Private Key that is used by the SIDF to deconceal the SUCI and reconstruct the SUPI. The generation and storage of this key material is out of scope of the present document. Keys in the AUSF In case EAP-AKA' is used as authentication method, the AUSF shall derive a key KAUSF from CK' and IK' for EAP-AKA' as specified in clause 6.1.3.1. In case that 5G AKA is used as authentication method, the UDM/ARPF shall generate the KAUSF as specified in clause 6.1.3.2. The KAUSF may be stored in the AUSF between two subsequent authentication and key agreement procedures. When the AUSF stores the KAUSF, the AUSF shall store the latest KAUSF generated after successful completion of the latest primary authentication. The authentication is considered as successful and the AUSF shall store the latest KAUSF or replace the old KAUSF with the new KAUSF (if the AMF(s) end up selecting the same AUSF instance for (re)authentication of the UE): - in case 5G AKA is used as authentication method, when the RES* and the XRES* are equal (see clause 6.1.3.2.0, Step 11). - in case EAP-AKA' is used as authentication method, when the AUSF sends an EAP-Success message to the SEAF (see clause 6.1.3.1, Step 10). The AUSF shall generate the anchor key, also called KSEAF, from the authentication key material received from the ARPF during an authentication and key agreement procedure. Keys in the SEAF The SEAF receives the anchor key, KSEAF, from the AUSF upon a successful primary authentication procedure in each serving network. The SEAF shall never transfer KSEAF to an entity outside the SEAF. Once KAMF is derived KSEAF shall be deleted. The SEAF shall generate KAMF from KSEAF immediately following the authentication and key agreement procedure and hands it to the AMF. NOTE 1: This implies that a new KAMF, along with a new KSEAF, is generated for each run of the authentication and key agreement procedure. NOTE 2: The SEAF is co-located with the AMF. Keys in the AMF The AMF receives KAMF from the SEAF or from another AMF. The AMF shall, based on policy, derive a key KAMF' from KAMF for transfer to another AMF in inter-AMF mobility. The receiving AMF shall use K'AMF as its key KAMF. NOTE 3: The precise rules for key handling in inter-AMF mobility can be found in clause 6.9.3. The AMF shall generate keys KNASint and KNASenc dedicated to protecting the NAS layer. The AMF shall generate access network specific keys from KAMF. In particular, - the AMF shall generate KgNB and transfer it to the gNB. - the AMF shall generate NH and transfer it to the gNB, together with the corresponding NCC value. The AMF may also transfer an NH key, together with the corresponding NCC value, to another AMF, cf. clause 6.9. - the AMF shall generate KN3IWF and transfer it to the N3IWF when KAMF is received from SEAF, or when KAMF' is received from another AMF. Keys in the NG-RAN The NG-RAN (i.e., gNB or ng-eNB) receives KgNB and NH from the AMF. The ng-eNB uses KgNB as KeNB. The NG-RAN (i.e., gNB or ng-eNB) shall generate all further access stratum (AS) keys from KgNB and /or NH. Keys in the N3IWF The N3IWF receives KN3IWF from the AMF. The N3IWF shall use KN3IWF as the key MSK for IKEv2 between UE and N3IWF in the procedures for untrusted non-3GPP access, cf. clause 11. Figure 6.2.2-1 shows the dependencies between the different keys, and how they are derived from the network nodes point of view. Figure 6.2.2-1: Key distribution and key derivation scheme for 5G for network nodes NOTE 4: The key derivation and distribution scheme for standalone non-public networks, when an authentication method other than 5G AKA or EAP-AKA' is used, is given in Annex I.2.3. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.2.2.1 |
2,364 | 9.5.16a Notification | This message is sent by the network to inform the MS about events which are relevant for the upper layer using the PDP context or having requested a session management procedure. See table 9.5.16a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Message type: NOTIFICATION Significance: local Direction: network to MS Table 9.5.16a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : NOTIFICATION 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.5.16a |
2,365 | 9.2.1.9 FDD (Modulation and TBS index Table 3 and 4-bit CQI Table 4 are used) | The following requirements apply to UE DL Category 20 and DL Category ≥22. For the parameters specified in Table 9.2.1.9-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.X FDD in Table A.4-1 shall be in the range of ±1 of the reported median more than 90% of the time. If the PDSCH BLER using the transport format indicated by median CQI is less than or equal to 0.1, the BLER using the transport format indicated by the (median CQI + 1) shall be greater than 0.1. If the PDSCH BLER using the transport format indicated by the median CQI is greater than 0.1, the BLER using transport format indicated by (median CQI – 1) shall be less than or equal to 0.1. In this test, 4-bit CQI Table 4 in Table 7.2.3-4 in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [6], and Modulation and TBS index table 3 in Table 7.1.7.1-1B for PDSCH in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [6] are applied. Table 9.2.1.9-1: PUCCH 1-0 static test (FDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.2.1.9 |
2,366 | 4.2.5.1.4 Substate, ATTEMPTING-TO-UPDATE | The MS: - shall not send any user data; - shall initiate routing area updating procedure on the expiry of timers T3311, T3302 or T3346; - shall initiate routing area updating procedure when entering a new PLMN, if timer T3346 is running and the new PLMN is not equivalent to the PLMN where the MS started timer T3346, the PLMN identity of the new cell is not in one of the forbidden PLMN lists and the location area this cell is belonging to is not in one of the lists of forbidden LAs; - shall initiate routing area updating procedure when the routing area of the serving cell has changed, if timer T3346 is not running, the PLMN identity of the new cell is not in one of the forbidden PLMN lists and the location area this cell is belonging to is not in one of the lists of forbidden LAs; - shall, if entry into this state was caused by b) or d) with cause "Retry upon entry into a new cell" of subclause 4.7.5.1.5, initiate routing area updating procedure when a new cell is entered; - shall, if entry into this state was caused by c) or d) with cause different from "Retry upon entry into a new cell" of subclause 4.7.5.1.5, not initiate routing area updating procedure when a new cell is entered; - shall use request for non-GPRS services from CM layers to trigger the combined routing area updating procedure, if timer T3346 is not running and the network operates in network operation mode I. Depending on which of the timers T3311 or T3302 is running the MS shall stop the relevant timer and act as if the stopped timer has expired; - may use a request for an MMTEL voice call or MMTEL video call from the upper layers to initiate routing area updating procedure (Iu mode only), if timer T3346 is not running; - may initiate routing area updating procedure upon request of the upper layers to establish a PDN connection for emergency bearer services (UTRAN Iu mode only); - shall initiate routing area updating procedure upon request of the upper layers to establish a PDN connection without the NAS signalling low priority indication as specified in subclause 4.7.5.1.5, item j), if timer T3346 is running due to a NAS request message (ROUTING AREA UPDATE REQUEST or SERVICE REQUEST) which contained the low priority indicator set to "MS is configured for NAS signalling low priority" and timer T3302 and timer T3311 are not running; - may detach locally and initiate GPRS attach for emergency bearer services even if timer T3346 is running; - shall initiate routing area updating procedure in response to paging; and - shall not initiate the signalling procedure for GPRS detach unless the routing area of the current cell is same as the stored routing area. Optionally, the MS may perform local GPRS detach. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.2.5.1.4 |
2,367 | 5.3.5A Connection Resume procedure | This procedure is used by the UE to resume the ECM-connection if the UE and the network support User Plane CIoT EPS Optimisation and the UE has stored the necessary information to conduct the Connection Resume procedure (see TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]) otherwise the Service Request procedures are used, see clause 5.3.4. Figure 5.3.5A-1: UE initiated Connection Resume procedure 1. The UE triggers the Random Access procedure to the eNodeB, see TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]. 2. The UE triggers the RRC Connection Resume procedure including information needed by the eNodeB to access the UE's stored AS context, see 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 E-UTRAN performs security checks. EPS bearer state synchronization is performed between the UE and the network, i.e. the UE shall locally remove any EPS bearer for which no radio bearer is setup and which is not a Control Plane CIoT EPS bearer. If the radio bearer for a default EPS bearer is not established, the UE shall locally deactivate all EPS bearers associated to that default EPS bearer. 3. The eNodeB notifies the MME that the UE's RRC connection is resumed in the S1-AP UE Context Resume Request message which includes an RRC resume cause. If the eNodeB is not able to admit all suspended bearers, the eNodeB shall indicate this in the list of rejected EPS bearers, see TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36]. When the UE attempts to establish a signalling connection and the following conditions are met: the eNodeB serves more than one country (e.g. it supports E-UTRA satellite access); and - the eNodeB knows in what country the UE is located; and - the eNodeB is connected to MMEs serving different PLMNs of different countries; and - the UE provides an S-TMSI or GUMMEI, which indicates an MME serving a different country to where the UE is currently located; and - the eNodeB is configured to enforce selection of the MME based on the country the UE is currently located; then the eNodeB shall select an MME serving a PLMN corresponding to the UE's current location and send the S1-AP UE Context Resume Request message to that MME (this is intended to cause the resume procedure to fail). If there is a Service Gap timer running in the MME for the UE and the MME is not waiting for a MT paging response from the UE and the RRC Connection Establishment Cause for the Connection Resume Request is not 'mo-Signalling', the MME rejects the resume request by sending a S1-AP UE Context Resume Reject message to eNodeB. NOTE: If the UE then sends a subsequent Service Request while the Service Gap timer is running, the MME will send a Service Reject NAS message to the UE with a Mobility Management back-off timer corresponding to the remaining time of the current Service Gap timer (see procedure in clause 5.3.4). The MME enters the ECM-CONNECTED state. The MME identifies that the UE returns at the eNodeB for which MME has stored data related to the S1AP association, UE Context and bearer context including the DL TEID(s), necessary to resume the connection, see Connection Suspend procedure in clause 5.3.4A. If a default EPS bearer is not accepted by the eNodeB, all the EPS bearers associated to that default bearer shall be treated as non-accepted bearers. The MME releases the non-accepted and non-established bearers by triggering the bearer release procedure as specified in clause 5.4.4.2. To assist Location Services, the eNodeB indicates the UE's Coverage Level to the MME. 3a. If the S1-U connection is resumed and the UE is accessing via the NB-IoT RAT with the RRC resume cause set to "MO exception data", the MME should notify the Serving Gateway of each use of this establishment cause by the MO Exception Data Counter. The MME maintains the MO Exception Data Counter and sends it to the Serving GW as indicated in TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [43]. 3b. The Serving Gateway should notify the PDN GW if the RRC establishment cause "MO Exception Data" has been used by the MO Exception Data Counter (see TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [43]). The Serving GW indicates each use of this RRC establishment cause by the related counter on its CDR. 3c. The PDN GW indicates each use of the RRC establishment cause "MO Exception Data" by the related counter on its CDR. 4. MME acknowledges the connection resumption in S1-AP UE Context Resume Response message. If the MME is not able to admit all suspended E-RABs the MME shall indicate this in the E-RABs Failed To Resume List IE. 5. If the MME included in step 4 a list of E-RABs failed to resume, the eNodeB reconfigures the radio bearers. 6. The uplink data from the UE can now be forwarded by eNodeB to the Serving GW. The eNodeB sends the uplink data to the Serving GW address and TEID stored during the Connection Suspend procedure, see clause 5.3.4A. The Serving GW forwards the uplink data to the PDN GW. 7. The MME sends a Modify Bearer Request message (eNodeB address, S1 TEID(s) (DL) for the accepted EPS bearers, Delay Downlink Packet Notification Request, RAT Type) per PDN connection to the Serving GW. If the Serving GW supports Modify Access Bearers Request procedure and if there is no need for the Serving GW to send the signalling to the PDN GW, the MME may send Modify Access Bearers Request (eNodeB address(es) and TEIDs for downlink user plane for the accepted EPS bearers, Delay Downlink Packet Notification Request) per UE to the Serving GW to optimise the signalling. The Serving GW is now able to transmit downlink data towards the UE. The MME and the Serving GW clears the DL Data Buffer Expiration Time in their UE contexts if it was set, to remember that any DL data buffered for a UE using power saving functions has been delivered and to avoid any unnecessary user plane setup in conjunction with a later TAU. 8. The Serving GW shall return a Modify Bearer Response (Serving GW address and TEID for uplink traffic) to the MME as a response to a Modify Bearer Request message, or a Modify Access Bearers Response (Serving GW address and TEID for uplink traffic) as a response to a Modify Access Bearers Request message. If the Serving GW cannot serve the MME Request in the Modify Access Bearers Request message without S5/S8 signalling other than to unpause charging in the PDN GW or without corresponding Gxc signalling when PMIP is used over the S5/S8 interface, it shall respond to the MME with indicating that the modifications are not limited to S1-U bearers, and the MME shall repeat its request using a Modify Bearer Request message per PDN connection. If SIPTO at the Local Network is active for a PDN connection with stand-alone GW deployment and the Local Home Network ID for stand-alone accessed by the UE differs from the Local Home Network ID where the UE initiated the SIPTO@LN PDN Connection, the MME shall request disconnection of the SIPTO at the local network PDN connection(s) with the "reactivation requested" cause value according to clause 5.10.3. If the UE has no other PDN connection, the MME initiated "explicit detach with reattach required" procedure according to clause 5.3.8.3. If SIPTO at the Local Network is active for a PDN connection with collocated LGW deployement and the L-GW CN address of the cell accessed by the UE differs from the L-GW CN address of the cell where the UE initiated the SIPTO at the Local Network PDN Connection, the MME shall request disconnection of the SIPTO at the local network PDN connection(s) with the "reactivation requested" cause value according to clause 5.10.3. If the UE has no other PDN connection, the MME initiated "explicit detach with reattach required" procedure according to clause 5.3.8.3. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.3.5A |
2,368 | 4.7.6.4 Abnormal cases on the network side | The following abnormal cases can be identified: a) Lower layer failure If a lower layer failure is detected before the P-TMSI REALLOCATION COMPLETE message is received, the network shall consider both the old and the new P-TMSI as occupied until the old P-TMSI can be considered as invalid (see subclause 4.7.1.5). During this period the network: - may first use the old P-TMSI for paging for an implementation dependent number of paging attempts in the case of network-originated transactions. Upon response from the MS, the network may re-initiate the P-TMSI reallocation procedure. If no response is received to the paging attempts, the network may use the new P-TMSI for paging for an implementation dependent number of paging attempts. Upon response from the MS, the network shall consider the new P-TMSI as valid and the old P-TMSI as invalid. If no response is received to the paging attempts, the network may use the IMSI for paging for an implementation dependent number of paging attempts; NOTE: Paging with IMSI causes the MS to re-attach as described in subclause 4.7.9.1. - shall consider the new P-TMSI as valid if it is used by the MS (see subclause 4.7.1.5); or - may use the identification procedure followed by a new P-TMSI reallocation, if the MS uses the old P-TMSI. b) Expiry of timer T3350 The P-TMSI reallocation procedure is supervised by the timer T3350 (see example in figure 4.7.6/1). On the first expiry of timer T3350, the network shall reset and restart timer T3350 and shall retransmit the P-TMSI REALLOCATION COMMAND message. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3350, the network shall abort the P-TMSI reallocation procedure and shall follow the rules for case a as described above. c) P-TMSI reallocation and GPRS attach procedure collision If the network receives an ATTACH REQUEST message before the ongoing P-TMSI reallocation procedure has been completed, the network shall proceed with the GPRS attach procedure after deletion of the GMM context. d) P-TMSI reallocation and an MS initiated GPRS detach procedure collision If the network receives a DETACH REQUEST message before the ongoing P-TMSI reallocation procedure has been completed, the network shall abort the P-TMSI reallocation procedure and shall progress the GPRS detach procedure. e) P-TMSI reallocation and a routing area updating procedure collision If the network receives a ROUTING AREA UPDATE REQUEST message before the ongoing P-TMSI reallocation procedure has been completed, the network shall abort the P-TMSI reallocation procedure and shall progress the routing area updating procedure. The network may then perform a new P-TMSI reallocation. f) P-TMSI reallocation and a service request procedure collision If the network receives a SERVICE REQUEST message before the ongoing P-TMSI reallocation procedure procedure has been completed, the network shall progress both procedures. Figure 4.7.6/1 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : P-TMSI reallocation procedure | 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.6.4 |
2,369 | 6.43.2 Requirements | The 5G system shall enable an authorized 3rd party to provide policy(ies) for flows associated with an application. The policy may contain e.g. the set of UEs and data flows, the expected QoS handling and associated triggering events, other coordination information. The 5G system shall support a means to apply 3rd party provided policy(ies) for flows associated with an application. The policy may contain e.g. the set of UEs and data flows, the expected QoS handling and associated triggering events, other coordination information. NOTE: The policy can be used by a 3rd party application for coordination of the transmission of multiple UEs’ flows (e.g., haptic, audio and video) of a multi-modal communication session. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.43.2 |
2,370 | A.1 Causes related to UE identification | Cause #2 – IMSI unknown in HSS This EMM cause is sent to the UE if the UE is not known (registered) in the HSS or if the UE has packet only subscription. This EMM cause does not affect operation of the EPS service, although it may be used by an EMM procedure. Cause #3 – Illegal UE This EMM cause is sent to the UE when the network refuses service to the UE either because an identity of the UE is not acceptable to the network or because the UE does not pass the authentication check, i.e. the RES received from the UE is different from that generated by the network. Cause #6 – Illegal ME This EMM cause is sent to the UE if the ME used is not acceptable to the network, e.g. on the prohibited list. Cause #9 – UE identity cannot be derived by the network. This EMM cause is sent to the UE when the network cannot derive the UE's identity from the GUTI/S-TMSI/P-TMSI and RAI e.g. no matching identity/context in the network or failure to validate the UE's identity due to integrity check failure of the received message. Cause #10 – Implicitly detached This EMM cause is sent to the UE either if the network has implicitly detached the UE, e.g. after the implicit detach timer has expired, or if the EMM context data related to the subscription does not exist in the MME e.g. because of a MME restart, or because of a periodic tracking area update request routed to a new MME. | 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 | A.1 |
2,371 | 5.7.6.2 IP Packet Filter Set | For IP PDU Session Type, the Packet Filter Set shall support Packet Filters based on at least any combination of: - Source/destination IP address or IPv6 prefix. - Source / destination port number. - Protocol ID of the protocol above IP/Next header type. - Type of Service (TOS) (IPv4) / Traffic class (IPv6) and Mask. - Flow Label (IPv6). - Security parameter index. - Packet Filter direction. NOTE 1: A value left unspecified in a Packet Filter matches any value of the corresponding information in a packet. NOTE 2: An IP address or Prefix may be combined with a prefix mask. NOTE 3: Port numbers may be specified as port ranges. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.7.6.2 |
2,372 | 12 Processing delay requirements for RRC procedures | The UE performance requirements for procedures are specified in the following tables. The performance requirement is expressed as the time in [ms] from the end of reception of the network -> UE message on the UE physical layer up to when the UE shall be ready for the reception of uplink grant for the UE -> network response message with no access delay other than the TTI-alignment (e.g. excluding delays caused by scheduling, the random access procedure or physical layer synchronisation). In case the RRC procedure triggers BWP switching, the RRC procedure delay is the value defined in the following table plus the BWP switching delay defined in TS 38.133[ NR; Requirements for support of radio resource management ] [14], clause 8.6.3. Figure 12.1-1: Illustration of RRC procedure delay Table 12.1-1: UE performance requirements for procedures for UEs | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 12 |
2,373 | 5.3.8.2.2 UE-initiated Detach procedure for GERAN/UTRAN with ISR activated | Figure 5.3.8.2-2 shows the case when UE with ISR Activated camps on GERAN/UTRAN and Detach Request is sent to SGSN. Refer to clause 6.6.1 of TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7] for the UE-initiated Detach procedure when ISR is not activated. Figure 5.3.8.2-2: UE-Initiated Detach Procedure - UE camping on GERAN/UTRAN, ISR activated 1. The UE sends NAS message Detach Request (Detach Type, P-TMSI, P-TMSI-Signature, Switch Off) to the SGSN. Detach Type indicates which type of detach is to be performed, i.e. GPRS Detach only, IMSI Detach only or combined GPRS and IMSI Detach. Switch Off indicates whether detach is due to a switch off situation or not. The Detach Request message includes P-TMSI and P-TMSI Signature. P-TMSI Signature is used to check the validity of the Detach Request message. If P-TMSI Signature is not valid or is not included, the authentication procedure should be performed. If the SGSN receives a Detach Request via a CSG cell with Switch Off parameter indicating that detach is not due to a switch off situation, and the CSG subscription for this CSG ID and associated PLMN is absent or expired, the SGSN shall trigger a SGSN-initiated Detach procedure as specified in clause 5.3.8.3A. 2. The active EPS Bearers in the Serving GW regarding this particular UE are deactivated by the SGSN sending Delete Session Request (LBI, User Location Information (CGI/SAI)) per PDN connection to the Serving GW. Because ISR is activated, then the Serving GW shall not release the Control Plan TEID allocated for MME/SGSN until it receives the Delete Session Request message in step 5. If the UE Time Zone has changed, the SGSN includes the UE Time Zone IE in this message. 3. Because the Serving GW receives this message in ISR activated state, the Serving GW deactivates ISR and acknowledges with Delete Session Response (Cause). 4. Because ISR is activated, the SGSN sends Detach Notification (Cause) message to the associated MME. Cause indicates complete detach. 5. The active PDP contexts in the Serving GW regarding this particular UE are deactivated by the MME sending Delete Session Request (LBI, ECGI) per PDN connection to the Serving GW. If the UE Time Zone has changed, the MME includes the UE Time Zone IE in this message. 6. Serving GW deactivates ISR and sends Delete Session Request (LBI, User Location Information (ECGI or CGI/SAI)) per PDN connection to the PDN GW. If ISR is not activated, this step shall be triggered by step 2. This message indicates that all bearers belonging to that PDN connection shall be released. If the MME and/or SGSN sends UE's Location Information and/or UE Time Zone Information in step 2 and/or step 5, the S-GW includes the User Location Information and/or UE Time Zone with the least age in this message. 7. The PDN GW acknowledges with Delete Session Response (Cause). 8. The PDN GW employs a PCEF initiated IP CAN Session Termination Procedure as defined in TS 23.203[ Policy and charging control architecture ] [6] with the PCRF to indicate to the PCRF that EPS Bearer is released if PCRF is applied in the network. If requested by the PCRF the PDN GW indicates User Location Information and/or UE Time Zone Information to the PCRF as defined in TS 23.203[ Policy and charging control architecture ] [6]. 9. The Serving GW acknowledges with Delete Session Response (Cause). 10. The MME sends Detach Acknowledge message to the SGSN. 11. If Switch Off indicates that detach is not due to a switch off situation, the SGSN sends a Detach Accept to the UE. 12. If the MS was GPRS detached, then the 3G SGSN releases the PS signalling connection. | 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.8.2.2 |
2,374 | 7.4 Unknown or unforeseen message type | If UE receives a 5GMM message or 5GSM message with message type not defined for the extended protocol discriminator (EPD) or not implemented by the receiver, it shall return a status message (5GMM STATUS or 5GSM STATUS depending on the EPD) with cause #97 "message type non-existent or not implemented". If the network receives a 5GMM or 5GSM message with message type not defined for the EPD or not implemented by the receiver in a protocol state where reception of an unsolicited message with the given EPD from the UE is not foreseen in the protocol, the network actions are implementation dependent. Otherwise, if the network receives a message with message type not defined for the EPD or not implemented by the receiver, it shall ignore the message except that it should return a status message (5GMM STATUS or 5GSM STATUS depending on the EPD) with cause #97 "message type non-existent or not implemented". NOTE: A message type not defined for the EPD in the given direction is regarded by the receiver as a message type not defined for the EPD, see 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [11]. If the UE receives a message not compatible with the protocol state, the UE shall return a status message (5GMM STATUS or 5GSM STATUS depending on the EPD) with cause #98 "message type not compatible with protocol state". If the network receives a message not compatible with the protocol state, the network actions are implementation dependent. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 7.4 |
2,375 | 5.4.1.3.3 Authentication response by the UE | The UE shall respond to an AUTHENTICATION REQUEST message. With the exception of the cases described in subclause 5.4.1.3.6 and 5.4.1.3.7 case l, the UE shall process the 5G authentication challenge data and respond with an AUTHENTICATION RESPONSE message to the network. Upon a successful 5G authentication challenge, the UE shall determine the PLMN identity to be used for the calculation of the new KAMF from the 5G authentication challenge data according to the following rules: a) When the UE moves from 5GMM-IDLE mode to 5GMM-CONNECTED mode, until the first handover, the UE shall use the PLMN identity of the selected PLMN; and b) After handover or inter-system change to N1 mode in 5GMM-CONNECTED mode, 1) if the target cell is not a shared network cell, the UE shall use the PLMN identity received as part of the broadcast system information; 2) if the target cell is a shared network cell and the UE has a valid 5G-GUTI, the UE shall use the PLMN identity that is part of the 5G-GUTI; and 3) if the target cell is a shared network cell and the UE has a valid 4G-GUTI, but not a valid 5G-GUTI, the UE shall use the PLMN identity that is part of the 4G-GUTI. Upon a successful 5G authentication challenge, the new KAMF calculated from the 5G authentication challenge data shall be stored in a new 5G NAS security context in the volatile memory of the ME. The USIM will compute the authentication response (RES) using the 5G authentication challenge data received from the ME, and pass RES to the ME. From the RES, RES* is then generated according to Annex A of 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. In order to avoid a synchronisation failure, when the UE receives an AUTHENTICATION REQUEST message, the UE shall store the received RAND together with the RES*, in the volatile memory of the ME. When the UE receives a subsequent AUTHENTICATION REQUEST message, if the stored RAND value is equal to the new received value in the AUTHENTICATION REQUEST message, then the ME shall not pass the RAND to the USIM, but shall send the AUTHENTICATION RESPONSE message with the stored RES*. If there is no valid stored RAND in the ME or the stored RAND is different from the new received value in the AUTHENTICATION REQUEST message, the ME shall pass the RAND to the USIM, shall override any previously stored RAND and RES* with the new ones and start, or reset and restart timer T3516. The RAND and RES* values stored in the ME shall be deleted and timer T3516, if running, shall be stopped: a) upon receipt of a 1) SECURITY MODE COMMAND message, 2) SERVICE REJECT message, 3) REGISTRATION REJECT message, 4) REGISTRATION ACCEPT message, 5) AUTHENTICATION REJECT message, or 6) SERVICE ACCEPT message; b) upon expiry of timer T3516; c) if the UE enters the 5GMM state 5GMM-DEREGISTERED or 5GMM-NULL; or d) if the UE enters 5GMM-IDLE mode. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.4.1.3.3 |
2,376 | 10.1.4.1.1 Reference signal sequence for | The reference signal sequence for is defined by where the binary sequence is defined by clause 7.2 and shall be initialised with at the start of the NPUSCH transmission. The quantity is given by Table 10.1.4.1.1-1 where for NPUSCH format 2, and for NPUSCH format 1if group hopping is not enabled, and by clause 10.1.4.1.3 if group hopping is enabled for NPUSCH format 1. Table 10.1.4.1.1-1: Definition of The reference signal sequence for NPUSCH format 1 is given by: The reference signal sequence for NPUSCH format 2 is given by where is defined in Table 5.5.2.2.1-2 with the sequence index chosen according to with . For frame structure type 1, . For frame structure type 2, for and for . | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 10.1.4.1.1 |
2,377 | 5.2.6.22.6 Nnef_AMPolicyAuthorization_Subscribe service operation | Service operation name: Nnef_AMPolicyAuthorization_Subscribe Description: provided by the NEF for NF consumers to explicitly subscribe the notification of events, triggering an Npcf_AMPolicyAuthorization_Subscribe. Inputs, Required: Event ID as specified in Nnef_AMPolicyAuthorization_Notify service operation, SUPI, 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: 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.6.22.6 |
2,378 | Annex Q (informative): Satellite coverage availability information | The protocol and format of satellite coverage availability information to be provisioned to the UE via PDU session or SMS is not defined in this release of the specification, but this annex provides some examples on the information that constitutes input to the source of satellite coverage availability information e.g. external server and the output it provides to the UE. Satellite coverage availability information can be indicated to the UE by indications corresponding to whether or not coverage is available for a specific satellite RAT Type for a particular location and time, where: - These indications can be Boolean "True" (e.g. coverage available) and "False" (coverage not available); - locations can correspond to grid points in a fixed array (e.g. rectangular, hexagonal); - Coverage availability times may occur at fixed periodic intervals; and - Coverage availability information is per RAT Type. The information provisioned to the UE can include coverage information on only one PLMN or multiple PLMNs. If Satellite coverage availability information indicates coverage is available then additional information on whether PLMN is allowed to operate in that location can be provided to the UE. In order for the source of satellite coverage availability information to provide accurate information to the UE, a UE might indicate for example the following information to a source of satellite coverage availability information (e.g. an external server): - Serving PLMN ID (if not already known or implied). - One or more satellite RAT Types (where satellite coverage availability information is then expected for these one or more RAT Types). - List of supported satellite frequency bands (if not implied by the particular RAT Types). - Present UE location (e.g. latitude and longitude) for a reference grid point (e.g. the most Southerly and then most Westerly grid point). - Type of Array (e.g. rectangular or hexagonal). - Minimum elevation angle. Based on the above information provided by the UE, satellite coverage availability information could be delivered to the UE as a sequence of time durations for each grid point where each time duration includes an indication of coverage availability or unavailability one example of many alternatives as illustrated below for a particular grid point with N different durations: Satellite coverage availability information at a given grid point = <N> <Binary 0 or 1><Duration 1> <Binary 0 or 1><Duration 2> . . . . <Binary 0 or 1><Duration N> The above would be concatenated for all of the grid points to produce the satellite coverage availability information. When SMS is used to deliver the satellite coverage availability information, the UE input and satellite coverage availability information output can be delivered in a series of concatenated SMS messages using possibly the same format. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | Annex |
2,379 | 8.1.2.6.5 Applicability rule and antenna connection for CA and DC tests with 4Rx | All tests specified in 8.13 with FDD CA/DC, TDD CA/DC and TDD-FDD CA/DC are tested with 4 Rx capable UEs. Within the CA/DC configuration if any of the PCell and/or the SCells/PSCell is a 2Rx supported RF band, 2 out of the 4Rx should be connected with data source from system simulator, and the other 2Rx are connected with zero input, depending on UE’s declaration and AP configuration. Within the CA/DC configuration if any of the PCell and/or the SCells is a 4Rx supported RF band, all 4Rx should be connected with data source from system simulator. For 4Rx capable UEs supporting different CA/DC configurations and bandwidth combination sets, the applicability and test rules are defined in Table 8.1.2.6.5-1 for FDD CA/DC, TDD CA/DC and TDD-FDD CA/DC. For simplicity, CA/DC configuration below refers to combination of CA/DC configuration and bandwidth combination set. Table 8.1.2.6.5-1: Applicability and test rules for CA/DC/TDD-FDD CA UE demodulation tests For 4Rx capable UEs, if corresponding tests listed from the 4Rx CA/DC test lists from Table 8.1.2.6.5-2 are tested, the test coverage can be considered fulfilled without executing the corresponding tests listed from the 2Rx CA/DC test lists from Table 8.1.2.6.5-2. Table 8.1.2.6.5-2: Test lists for applicability rules for CA/DC/TDD-FDD CA tests with 4Rx | 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.6.5 |
2,380 | 8.8 Multiple TNLAs for F1-C | In the following, the procedure for managing multiple TNLAs for F1-C is described. Figure 8.8-1: Managing multiple TNLAs for F1-C. 1. The gNB-DU establishes the first TNLA with the gNB-CU using a configured TNL address. NOTE: The gNB-DU may use different source and/or destination IP end point(s) if the TNL establishment towards one IP end point fails. How the gNB-DU gets the remote IP end point(s) and its own IP address are outside the scope of this specification. 2-3. Once the TNLA has been established, the gNB-DU initiates the F1 Setup procedure to exchange application level configuration data. 4-6. The gNB-CU may add additional TNL Endpoint(s) to be used for F1-C signalling between the gNB-CU and the gNB-DU pair using the gNB-CU Configuration Update procedure. The gNB-CU Configuration Update procedure also allows the gNB-CU to request the gNB-DU to modify or release TNLA(s). 7-9. The gNB-DU may add additional TNL association(s) to be used for F1-C signalling using a gNB-CU endpoint already in use for existing TNL associations between the gNB-CU and the gNB-DU pair. The gNB-DU CONFIGURATION UPDATE message including the gNB-DU ID shall be the first F1AP message sent on an additional TNLA of an already setup F1-C interface instance after the TNL association has become operational. The F1AP UE TNLA binding is a binding between a F1AP UE association and a specific TNL association for a given UE. After the F1AP UE TNLA binding is created, the gNB-CU can update the UE TNLA binding by sending the F1AP message for the UE to the gNB-DU via a different TNLA. The gNB-DU shall update the F1AP UE TNLA binding with the new TNLA. The gNB-DU Configuration Update procedure also allows the gNB-DU to inform the gNB-CU that the indicated TNLA(s) will be removed by the gNB-DU. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.8 |
2,381 | 19.3 Mz messages | This clause defines the Mz interface Diameter messages. The Diameter messages used in the Mz protocol, are the same as specified for Gmb interface described in Clause 17 of the present specification: AAR Command (clause 17.6.1), AAA Command (clause 17.6.2), STR Command (clause 17.6.3), STA Command (clause 17.6.4), Abort-Session-Request Command (clause 17.6.7) and Abort-Session-Answer Command (17.6.8). To route Diameter messages from the visited PLMN to the home PLMN, the BM-SC in the visited PLMN shall derive the realm of the home PLMN from the user’s IMSI. The way to derive the realm of the home PLMN from IMSI is specified in 3GPP TS 23.003[ Numbering, addressing and identification ] [40] subclause 15.4. The derived realm of the home PLMN shall be filled in the Destination-Realm AVP of messages sent from the visited PLMN to the home PLMN, i.e. AAR command, STR command. | 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 | 19.3 |
2,382 | 6.8.11 Handling of the START value in intersystem mobility cases | The START values (see clause 6.4.8) shall be kept in the volatile memory of the ME in the following cases: - Intersystem idle mobility for CS Services – from UTRAN to GSM BSS; - Intersystem handover for CS Services – from UTRAN to GSM BSS; - Intersystem change for PS Services – from UTRAN to GSM BSS; - PS handover from Iu to Gb mode; - SRVCC – from HSPA to UTRAN/GERAN; NOTE: The handling of mobility from UTRAN to E-UTRAN is described in TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [28]. Hence, also the corresponding handling of START is described there. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 6.8.11 |
2,383 | 8.2.1 Control Plane Protocol Stacks between the 5G-AN and the 5G Core: N2 8.2.1.1 General | NOTE 1: N2 maps to NG-C as defined in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [34]. Following procedures are defined over N2: - Procedures related with N2 Interface Management and that are not related to an individual UE, such as for Configuration or Reset of the N2 interface. These procedures are intended to be applicable to any access but may correspond to messages that carry some information only on some access (such as information on the default Paging DRX used only for 3GPP access). - Procedures related with an individual UE: - Procedures related with NAS Transport. These procedures are intended to be applicable to any access but may correspond to messages that for UL NAS transport carry some access dependent information such as User Location Information (e.g. Cell-Id over 3GPP access or other kind of User Location Information for Non-3GPP access). - Procedures related with UE context management. These procedures are intended to be applicable to any access. The corresponding messages may carry: - some information only on some access (such as Mobility Restriction List used only for 3GPP access). - some information (related e.g. with N3 addressing and with QoS requirements) that is to be transparently forwarded by AMF between the 5G-AN and the SMF. - Procedures related with resources for PDU Sessions. These procedures are intended to be applicable to any access. They may correspond to messages that carry information (related e.g. with N3 addressing and with QoS requirements) that is to be transparently forwarded by AMF between the 5G-AN and the SMF. - Procedures related with Hand-Over management. These procedures are intended for 3GPP access only. The Control Plane interface between the 5G-AN and the 5G Core supports: - The connection of multiple different kinds of 5G-AN (e.g. 3GPP RAN, N3IWF for Un-trusted access to 5GC) to the 5GC via a unique Control Plane protocol: A single NGAP protocol is used for both the 3GPP access and non-3GPP access; - There is a unique N2 termination point in AMF per access for a given UE regardless of the number (possibly zero) of PDU Sessions of the UE; - The decoupling between AMF and other functions such as SMF that may need to control the services supported by 5G-AN(s) (e.g. control of the UP resources in the 5G-AN for a PDU Session). For this purpose, NGAP may support information that the AMF is just responsible to relay between the 5G-AN and the SMF. The information can be referred as N2 SM information in TS 23.502[ Procedures for the 5G System (5GS) ] [3] and this specification. NOTE 2: The N2 SM information is exchanged between the SMF and the 5G-AN transparently to the AMF. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 8.2.1 |
2,384 | 5.8.9.2.4 Actions related to reception of the UECapabilityEnquirySidelink by the UE | The peer UE shall set the contents of UECapabilityInformationSidelink message as follows: 1> include UE radio access capabilities for sidelink within ue-CapabilityInformationSidelink; 1> compile a list of "candidate band combinations" only consisting of bands included in frequencyBandListFilterSidelink, and prioritized in the order of frequencyBandListFilterSidelink (i.e. first include band combinations containing the first-listed band, then include remaining band combinations containing the second-listed band, and so on). 1> include into supportedBandCombinationListSidelinkNR as many band combinations as possible from the list of "candidate band combinations", starting from the first entry; 1> include the received frequencyBandListFilterSidelink in the field appliedFreqBandListFilter of the requested UE capability; 1> submit the UECapabilityInformationSidelink message to lower layers for transmission. NOTE: If the UE cannot include all band combinations due to message size or list size constraints, it is up to UE implementation which band combinations it prioritizes. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.9.2.4 |
2,385 | 6.3.25 AF Discovery and Selection | The NF consumers (e.g. NWDAF) may utilize the NRF to discover AF instance(s) in the MNO domain, i.e. trusted AF(s), unless AF information is available by other means, e.g. locally configured in NF consumers. The NRF provides NF profile(s) of AF instance(s) to the NF consumers. The following factors may be considered for AF discovery and selection: - One or multiple combination(s) of the S-NSSAI and DNN corresponding to an AF. - Supported Application Id(s). - Event ID(s) Supported by an AF. - Internal-Group Identifier. The NF consumer (e.g. NWDAF) may select an AF instance, in the MNO domain, considering one or multiple combination(s) of the S-NSSAI and DNN corresponding to an AF and the EventID(s) supported by an AF to provide the input data required for generation of analytics. The NF consumer (e.g. NWDAF) may consider the supported Application Id(s), if the input data is required only for those applications. The NF consumer (e.g. NWDAF) may consider the Internal-Group Identifier supported by the AF if the input data is required for a particular group of UEs. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.3.25 |
2,386 | 4.16.1.2 AM Policy Association Establishment with new Selected PCF | Figure 4.16.1.2-1: AM Policy Association Establishment with new Selected PCF This procedure concerns both roaming and non-roaming scenarios. In the non-roaming case the role of the V-PCF is performed by the PCF. For the roaming scenarios, the V-PCF interacts with the AMF. 1. Based on local policies, the AMF decides to establish AM Policy Association with the (V-)PCF then steps 2 to 3 are performed under the conditions described below. 2. [Conditional] If the AMF has not yet obtained access and mobility related policy information for the UE or if the access and mobility related policy information in the AMF is no longer valid, the AMF requests the PCF to apply operator policies for the UE from the PCF. The AMF sends Npcf_AMPolicyControl_Create to the (V-)PCF to establish an AM Policy Association with the (V-)PCF. The request includes the following information: SUPI, Internal Group (see clause 5.9.7 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]), subscription notification indication and if available, Service Area Restrictions, RFSP index, Subscribed UE-AMBR, List of Subscribed UE-Slice-MBR, the Allowed NSSAI, Partially Allowed NSSAI, S-NSSAI(s) rejected partially in the RA, Rejected S-NSSAI(s) for the RA, Pending NSSAI, Target NSSAI (see clause 5.3.4.3.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]), Network Slice Replacement supported for the UE (see clause 5.15.19 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]), GPSI, which are retrieved from the UDM during the update location procedure and may include Access Type and RAT Type, PEI, ULI, UE time zone and Serving Network (PLMN ID, or PLMN ID and NID, see clause 5.34 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]). When AMF utilizes an NWDAF, it may add the NWDAF serving the UE identified by the NWDAF instance ID. Per NWDAF service instance the Analytics ID(s) are also included. 3. In non-roaming case, if the PCF determines that the policy decision depends on the status of the policy counters available at the CHF and such reporting is not established for the subscriber, the PCF initiates an Initial Spending Limit Report Retrieval as defined in clause 4.16.8.2. If policy counter status reporting is already established for the subscriber and the PCF determines that the status of additional policy counters is required, the PCF initiates an Intermediate Spending Limit Report Retrieval as defined in clause 4.16.8.3. The (V)-PCF responds to the Npcf_AMPolicyControl_Create service operation. The (V)-PCF provides access and mobility related policy information (e.g. Service Area Restrictions) as defined in clause 6.5 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. In addition, (V)-PCF can provide Policy Control Request Trigger of AM Policy Association to AMF. In the non-roaming case, the PCF may subscribe to Analytics from NWDAF as defined in clause 6.1.1.3 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. The AMF is implicitly subscribed in the (V-)PCF to be notified of changes in the policies. The (V-)PCF may register to the BSF as the PCF that handles the AM Policy Association for this UE. This is performed by using the Nbsf_Management_Register operation, providing as inputs the UE SUPI/GPSI and the PCF identity. 4. [Conditional] The AMF deploys the access and mobility related policy information which includes storing the Service Area Restrictions and Policy Control Request Trigger(s) of the AM Policy Association, provisioning Service Area Restrictions to the UE and provisioning the RFSP index, the UE-AMBR, List of UE-Slice-MBR, Service Area Restrictions to the NG-RAN as defined in TS 23.501[ System architecture for the 5G System (5GS) ] [2] and request for notification of SM Policy association establishment and termination to a list of (DNN, S-NSSAI)(s) together with PCF for the UE binding information. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.16.1.2 |
2,387 | 16.2.1.1 RAN-assisted codec adaptation | RAN-assisted codec adaptation provides a means for the gNB to send codec adaptation indication with recommended bit rate to assist the UE to select or adapt to a codec rate for MMTEL voice or MMTEL video. The RAN-assisted codec adaptation mechanism supports the uplink/downlink bit rate increase or decrease. For a bearer associated with configuration of MBR greater than GBR, the recommended uplink/downlink bit rate is within boundaries set by the MBR and GBR of the concerned bearer. For uplink or downlink bit rate adaptation, gNB may send a recommended bit rate to the UE to inform the UE on the currently recommended transport bit rate on the local uplink or downlink, which the UE may use in combination with other information to adapt the bit rate, e.g. the UE may send a bit rate request to the peer UE via application layer messages as specified in TS 26.114[ IP Multimedia Subsystem (IMS); Multimedia telephony; Media handling and interaction ] [24], which the peer UE may use in combination with other information to adapt the codec bit rate. The recommended bit rate is in kbps at the physical layer at the time when the decision is made. The recommended bit rate for UL and DL is conveyed as a MAC Control Element (CE) from the gNB to the UE as outlined in Figure 16.2.1.1-1. Figure 16.2.1.1-1: UL or DL bit rate recommendation Based on the recommended bit rate from the gNB, a UE may initiate an end-to-end bit rate adaptation with its peer (UE or MGW). The UE may also send a query message to its local gNB to check if a bit rate recommended by its peer can be provided by the gNB. The UE is not expected to go beyond the recommended bit rate from the gNB. The recommended bit rate query message is conveyed as a MAC CE from the UE to the gNB as outlined in Figure 16.2.1.1-2. Figure 16.2.1.1-2: UL or DL bit rate recommendation query A prohibit timer can be configured per logical channel by the network to limit UEs sending frequent query MAC CEs. Independent prohibit timers are used for each direction (uplink and downlink) to prohibit the UE from retransmitting exactly the same query MAC CE to the gNB during the configured time. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.2.1.1 |
2,388 | S.3.1 5G NSWO co-existence with EPS NSWO | An HPLMN that supports 5G NWSO and wants the UE to use 5G NSWO shall configure the UE to use 5G NSWO. This configuration shall be either on the USIM or ME, with configuration on the USIM taking precedence over the ME. A UE that supports 5G NSWO and is configured to use 5G NSWO shall always use 5G NSWO as described in clause S.3.2 (i.e., it shall not use EPS NSWO defined in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [97]). Otherwise, the UE may use EPS NSWO (e.g., UE does not support 5G NSWO or not configured to use 5G NSWO). NOTE: Such a configuration ensures that the UE supporting 5G NSWO cannot be downgraded to use EPS NSWO. The network may support both 5G NSWO and EPS NSWO. In such a case, the routing of the AAA messages is determined by the network based on the realm part of the UE Identity (e.g., realm contains epc.mnc<MNC>.mcc<MCC>.3gppnetwork.org (EPS NSWO) or 5gc-nswo.mnc<MNC>.mcc<MCC>.3gppnetwork.org (5G NSWO)). Which entities in the network perform this routing decision is dependent on the network configuration. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | S.3.1 |
2,389 | 5.2.8.2.2 Nsmf_PDUSession_Create service operation | Service operation name: Nsmf_PDUSession_Create. Description: Create a new PDU Session in the H-SMF or SMF or create an association with an existing PDN connection in the home SMF+PGW-C. Input, Required: SUPI, V-SMF ID or I-SMF ID, V-SMF SM Context ID or I-SMF SM Context ID, DNN, V-CN Tunnel Info or I-UPF Tunnel Info, addressing information allowing the H-SMF to request the V-SMF to issue further operations about the PDU Session or addressing information allowing the SMF to request the I-SMF to issue further operations about the PDU Session, Serving Network (PLMN ID, or PLMN ID and NID, see clause 5.18 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]). Input, Optional: S-NSSAI, Alternative S-NSSAI, PCO, Requested PDU Session Type, 5GSM Core Network Capability, Requested SSC mode, PDU Session ID, Number Of Packet Filters, UE location information, subscription get notified of PDU Session status change, PEI, GPSI, AN type, PCF ID, PCF Group ID, DNN Selection Mode, UE's Routing Indicator optionally with Home Network Public Key identifier or UDM Group ID for the UE, Always-on PDU Session Requested, Control Plane CIoT 5GS Optimisation Indication, information provided by V-SMF related to charging in home routed scenario (see TS 32.255[ Telecommunication management; Charging management; 5G data connectivity domain charging; Stage 2 ] [45]), AMF ID, EPS Bearer Status, extended NAS-SM timer indication, DNAI list supported by I-SMF (from I-SMF to SMF), HO Preparation Indication. MA PDU request indication, MA PDU Network-Upgrade Allowed indication, Indication on whether the UE is registered in both accesses; QoS constraints from the VPLMN (as defined in clause 5.7.1.11 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]), Satellite backhaul category, Notification of the SM Policy Association Establishment and Termination, PCF binding information, Disaster Roaming service indication, HR-SBO request indication, VPLMN EASDF address, [ECS Address Configuration Information associated with PLMN ID of visited network], Indication of UE supports non-3GPP access path switching. Output, Required: Result Indication and if success a SM Context ID and in addition: QFI(s), QoS Profile(s), Session-AMBR, QoS Rule(s), QoS Flow level QoS parameters if any for the QoS Flow(s) associated with the QoS rule(s), H-CN Tunnel Info or PSA UPF Tunnel Info, Enable pause of charging indication, Selected PDU Session Type and SSC mode. Output, Optional: PDU Session ID, S-NSSAI, Cause, PCO, UE IP address, IPv6 Prefix allocated to the PDU Session, information needed by V-SMF in the case of EPS interworking such as the PDN Connection Type, EPS bearer context(s), linked EBI, Reflective QoS Timer, Always-on PDU Session Granted, information provided by H-SMF related to charging in home routed scenario (see TS 32.255[ Telecommunication management; Charging management; 5G data connectivity domain charging; Stage 2 ] [45]), DNAI(s) of interest for this PDU Session (from SMF to I-SMF), indication of multi-homing support (from SMF to I-SMF). MA PDU session Accepted indication, Indication on whether Small Data Rate Control applies or not, HR-SBO authorization result, VPLMN Specific Offloading Information for HR-SBO, HPLMN DNS Server address, HPLMN address information (e.g. H-UPF IP address on N6), Internal Group Identifier(s). The V-SMF SM Context ID in the Input provides addressing information allocated by the V-SMF (to be used for service operations towards the V-SMF for this PDU Session). The I-SMF SM Context ID in the Input provides addressing information allocated by the I-SMF (to be used for service operations towards the I-SMF for this PDU Session). See clause 4.3.2.2.2 clause 4.11.1.2.2 clause 4.11.1.3.3 and clause 4.24 for details on the usage of this service operation. See clauses 4.22.2.2 and 4.22.3 for detailed usage of this service operation for ATSSS. See clause 6.7 of TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [74] for HR-SBO request indication, HR-SBO authorization result, VPLMN EASDF address, VPLMN Specific Offloading Information for HR-SBO, HPLMN DNS Server address, HPLMN address information. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.8.2.2 |
2,390 | D.3 UE policy re-assembly at the UE | When the UE needs to apply ANDSP as specified in 3GPP TS 24.502[ Access to the 3GPP 5G Core Network (5GCN) via non-3GPP access networks ] [18], the UE shall consider all UE policy parts with ANDSP contents currently stored at the UE. When the UE needs to apply URSP as specified in 3GPP TS 24.526[ User Equipment (UE) policies for 5G System (5GS); Stage 3 ] [19], the UE shall consider all UE policy parts with URSP contents currently stored at the UE. a) if the UE supports VPS URSP then: 1) the UE shall consider as VPS URSP of the RPLMN all UE policy parts with URSP contents currently stored at the UE, which are a part of one or more UE policy sections identified by a UPSI: i) with the PLMN ID part indicating the HPLMN; and ii) with UPSC indicated in a tuple of the stored VPS URSP configuration, such that the tuple contains the network descriptor with a network descriptor entry containing: A) the network descriptor entry type field set to "one or more VPLMNs" and the network descriptor entry value field containing PLMN ID of the RPLMN of an access, if the UE is registered via one or both accesses and the RPLMN of each access is a VPLMN; B) the network descriptor entry type field set to "one or more MCCs" and the network descriptor entry value field containing MCC of the PLMN ID of the RPLMN of an access, if the UE is registered via one or both accesses and the RPLMN of each access is a VPLMN; or C) the network descriptor entry type field set to "any VPLMN", if the UE is registered via one or both accesses and the RPLMN of each access is a VPLMN; 2) the UE shall consider as VPS URSP of the equivalent PLMN of the RPLMN all UE policy parts with URSP contents currently stored at the UE, which are a part of one or more UE policy sections identified by a UPSI: i) with the PLMN ID part indicating the HPLMN; and ii) with UPSC indicated in a tuple of the stored VPS URSP configuration, such that the tuple contains the network descriptor with a network descriptor entry containing: A) the network descriptor entry type field set to "one or more VPLMNs" and the network descriptor entry value field containing PLMN ID of an equivalent PLMN, if the UE is registered via one or both accesses, the RPLMN of each access is a VPLMN and the equivalent PLMN is a VPLMN; B) the network descriptor entry type field set to "one or more MCCs" and the network descriptor entry value field containing MCC of the PLMN ID of an equivalent PLMN, if the UE is registered via one or both accesses, the RPLMN of each access is a VPLMN and the equivalent PLMN is a VPLMN; or C) the network descriptor entry type field set to "any VPLMN", if the UE is registered via one or both accesses, the RPLMN of each access is a VPLMN and an equivalent PLMN is a VPLMN; and 3) the UE shall consider as PG URSP all UE policy parts with URSP contents currently stored at the UE except zero or more UE policy parts, if any, which are a part of one or more UE policy sections identified by a UPSI: i) with the PLMN ID part indicating the HPLMN; and ii) with UPSC indicated in any tuple of the stored VPS URSP configuration; and b) the UE shall consider all UE policy parts with URSP contents currently stored at the UE as the signalled URSP. When the UE needs to apply V2XP as specified in 3GPP TS 24.588[ Vehicle-to-Everything (V2X) services in 5G System (5GS); User Equipment (UE) policies; Stage 3 ] [19C], the UE shall consider all UE policy parts with V2XP contents currently stored at the UE. When the UE needs to apply ProSeP as specified in 3GPP TS 24.555[ Proximity-services (ProSe) in 5G System (5GS); User Equipment (UE) policies; Stage 3 ] [19F], the UE shall consider all UE policy parts with ProSeP contents currently stored at the UE. When the UE needs to apply A2XP as specified in 3GPP TS 24.578[ Aircraft-to-Everything (A2X) services in 5G System (5GS); UE policies ] [61], the UE shall consider all UE policy parts with A2XP contents currently stored at the UE. When the UE needs to apply RSLPP as specified in 3GPP TS 24.514[ Ranging based services and sidelink positioning in 5G system(5GS); Stage 3 ] [62], the UE shall consider all UE policy parts with RSLPP contents currently stored at 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 | D.3 |
2,391 | 9.3.8.2.1 FDD | For the parameters specified in Table 9.3.8.2.1-1, and using the downlink physical channels specified in Annex C, the minimum requirements are specified in Table 9.3.8.2.1-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.2.1-1 Fading test for FDD Table 9.3.8.2.1-2 Minimum requirement (FDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.3.8.2.1 |
2,392 | 8.3.2.1C Single-layer Spatial Multiplexing (demodulation subframe overlaps with aggressor cell ABS and CRS assistance information are configured) | The requirements are specified in Table 8.3.2.1C-2, with the addition of parameters in Table 8.3.2.1C-1. The purpose is to verify the performance of the antenna ports 7 or 8 without a simultaneous transmission on the other antenna port in the serving cell 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.3.2.1C-1, Cell 1 is the serving cell, and Cell 2 and Cell 3 are the aggressor cells. The downlink physical channel setup for Cell 1 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.3.2.1C-1: Test parameters of TM9-Single-Layer (2 CSI-RS ports) – Non-MBSFN ABS Table 8.3.2.1C-2: Minimum Performance of TM9-Single-Layer (2 CSI-RS ports) – 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.3.2.1C |
2,393 | 9.1.1.4.2 Applicability rule and antenna connection for CA tests with 2Rx | All tests specified in 9.6 with 2Rx with CA and TDD-FDD CA are tested with 4 Rx capable UEs by connecting all 4Rx with data source from system simulator with the following change on the power level in the test configurations listed in Table 9.1.1.4.2-1 and by scheduling the PDSCH for user data based on the Reference measurement channel RC.1 FDD according to Table A.4-1 with one sided dynamic OCNG Pattern OP.1 FDD as described in Annex A.5.1.1 for FDD cells and Reference measurement channel RC.1 TDD according to Table A.4-1 with one sided dynamic OCNG Pattern OP.1 TDD as described in Annex A.5.2.1 for TDD cells. Table 9.1.1.4.2-1: Power level for 4Rx capable UE to verify CA tests with 2Rx Within the CA configuration if any of the PCell and/or the SCells is a 2Rx supported RF band, keep the same power level listed in Table 9.1.1.4.2-1. Within the CA configuration if any of the PCell and/or the SCells is a 4Rx supported RF band, configure the power level 3 dB smaller than the number listed in Table 9.1.1.4.2-1. Same requirements specified with 2Rx should be applied. Same applicability rules defined in 9.1.1.2, 9.1.1.2A for CA and TDD-FDD CA applied for different CA configurations and bandwidth combination sets should be applied for 4 Rx capable UEs. | 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.1.1.4.2 |
2,394 | 4.4.8.1 Time Period the Requested IP throughput of GBR services Cannot be Achieved in the Cell | a) This measurement provides time period the requested IP throughput cannot be achieved in the cell. The measurement is split into sub-counters per QoS class level (QCI). Concerning operator specific QCIs their definition is vendor specific. b) CC c) This measurement is obtained by summing up the pre-defined sampling intervals during which the requested IP throughput cannot be achieved in the cell and reporting accumulated value at the end of measurement period. The IP throughput defined in TS 36.314[ Evolved Universal Terrestrial Radio Access (E-UTRA); Layer 2 - Measurements ] is used to evaluate time period during which the QoS is not satisfied by comparing the IP throughput with the guaranteed bit rate of the GBR services. The measurement period and number of samples during one measurement period are provided by the operator. d) Each measurement is an integer value (Unit: ms). e) The measurement name has the form Cell.ReqThpNotAchieved.QCI where QCI identifies the E-RAB level quality of service class. f) EUtranCellFDD EUtranCellTDD g) Valid for packet switched traffic. h) EPS. i) In case the duration interval provided with this measurement is followed with the on restricting the UEs for network access to the cell policy executed via ACB as mentioned in A.5 then this measurement provides “Time period in Active ACB triggered via requested QoS cannot be achieved”. The measurement can be executed with grouping of couple of QCIs to a common monitoring to distinguish between voice and data services. The IP throughput measurements is used as a reference on how to evaluate the quality of provided services to end user in observed cell. They shall be obtained directly in the eNB as internal measurements during each sampling period. | 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.8.1 |
2,395 | 5.43.3.2 Local switch with PSA UPF deployed on satellite | If SMF selects the UPF deployed on satellite as PSA of UE's PDU Session, the SMF configures the UE's N4 session to forward/detect packet to/from the internal interface as specified for the configuration for the 5GVN group member's N4 Session in clause 5.8.2.13.1 (Support for unicast traffic forwarding of a 5G VN). SMF may reuse the mechanism described in clause 5.8.2.13.1 to configure group-level N4 session rules for each N19 tunnel. For establishing N19 tunnel between the PSA UPFs onboard the satellite, the PSA UPFs are controlled by the same SMF. - To process packets between UE and servers residing in DN, SMF configures rules to route traffic via N6 as described in clause 5.8.2.13.1. The group-level N4 session is per DNN and S-NSSAI. The SMF can create, update or delete the group-level N4 Session, i.e. add or delete N4 rules, allocate or release the N19 tunnel resources based on operator deployment, e.g. based on GEO satellite's planned obsolescence or new GEO satellite setup. N6 may be used for carrying traffic between PSA UPFs deployed on different satellites. If N6 is used, SMF configures corresponding N4 rules for processing traffic to/from N6. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.43.3.2 |
2,396 | 19.6 E-UTRAN Cell Identity (ECI) and E-UTRAN Cell Global Identification (ECGI) | The E-UTRAN Cell Global Identification (ECGI) shall be composed of the concatenation of the PLMN Identifier (PLMN-Id) and the E-UTRAN Cell Identity (ECI) as shown in figure 19.6-1 and shall be globally unique: Figure 19.6-1: Structure of E-UTRAN Cell Global Identification The ECI shall be of fixed length of 28 bits and shall be coded using full hexadecimal representation. The exact coding of the ECI is the responsibility of each PLMN operator. For more details on ECI and ECGI, see 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [84]. NOTE: In the 5G Core Network protocols, when the ECGI needs to be identified in the context of Standalone Non-Public Networks (SNPN), the Network Identifier (NID) of the SNPN is included as part of the ECGI Information Element (see 3GPP TS 29.571[ 5G System; Common Data Types for Service Based Interfaces; Stage 3 ] [129]); this is a protocol aspect that does not imply any change on the system-wide definition of the ECGI. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 19.6 |
2,397 | 6.31.2.3 Disaster Roaming | The 3GPP system shall be able to provide means to enable a UE to access PLMNs in a forbidden PLMN list if a Disaster condition applies and no other PLMN is available except for PLMNs in the forbidden PLMN list. The 3GPP system shall provide means to enable that a Disaster Condition applies to UEs of a specific PLMN. The 3GPP system shall be able to provide a resource efficient means for a PLMN to indicate to potential Disaster Inbound Roamers whether they can access the PLMN or not. Disaster Inbound Roamers shall perform network reselection when a Disaster Condition has ended. The 3GPP system shall minimize congestion caused by Disaster Roaming. The 5G system and EPS shall support a mechanism for the HPLMN to control whether a UE, with HPLMN subscription, should apply Disaster Roaming when a Disaster Condition arises (in the HPLMN or a VPLMN). 3GPP system shall be able to collect charging information for a Disaster Inbound Roamer with information about the applied disaster condition. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.31.2.3 |
2,398 | 7.3.2 EPS bearer identity | The following network procedures shall apply for handling an unknown, erroneous, or unforeseen EPS bearer identity received in the header of an ESM message (specified as the header of a standard L3 message, see 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [12]): a) If the network receives a PDN CONNECTIVITY REQUEST message which includes an assigned or reserved EPS bearer identity value, the network shall respond with a PDN CONNECTIVITY REJECT message including ESM cause #43 "invalid EPS bearer identity". b) If the network receives a PDN DISCONNECT REQUEST message which includes an assigned or reserved EPS bearer identity value, the network shall respond with a PDN DISCONNECT REJECT message including ESM cause #43 "invalid EPS bearer identity". c) If the network receives a BEARER RESOURCE ALLOCATION REQUEST message which includes an assigned or reserved EPS bearer identity value, the network shall respond with a BEARER RESOURCE ALLOCATION REJECT message including ESM cause #43 "invalid EPS bearer identity". d) If the network receives a BEARER RESOURCE MODIFICATION REQUEST message which includes an assigned or reserved EPS bearer identity value, the network shall respond with a BEARER RESOURCE MODIFICATION REJECT message including ESM cause #43 "invalid EPS bearer identity". e) If the network receives an ESM INFORMATION RESPONSE message which includes an assigned or reserved EPS bearer identity value, the network shall ignore the message. f) If the network receives an ESM DATA TRANSPORT message which includes a reserved EPS bearer identity value or an assigned value that does not match an existing EPS bearer context, the network shall respond with an ESM STATUS message including ESM cause #43 "invalid EPS bearer identity". g) If the network receives an ESM message other than those listed in items a through e above in which the message includes a reserved EPS bearer identity value or an assigned value that does not match an existing EPS bearer context, the network shall ignore the message. The following UE procedures shall apply for handling an unknown, erroneous, or unforeseen EPS bearer identity received in the header of an ESM message: a) If the UE receives a PDN CONNECTIVITY REJECT message which includes an assigned or reserved EPS bearer identity value, the UE shall ignore the message. b) If the UE receives a PDN DISCONNECT REJECT message which includes an assigned or reserved EPS bearer identity value, the UE shall ignore the message. c) If the UE receives a BEARER RESOURCE ALLOCATION REJECT message which includes an assigned or reserved EPS bearer identity value, the UE shall ignore the message. d) If the UE receives a BEARER RESOURCE MODIFICATION REJECT message which includes an assigned or reserved EPS bearer identity value, the UE shall ignore the message. e) If the UE receives an ESM INFORMATION REQUEST message which includes an assigned or reserved EPS bearer identity value, the UE shall respond with an ESM STATUS message including ESM cause #43 "invalid EPS bearer identity". f) If the UE receives a NOTIFICATION message which includes a reserved EPS bearer identity value, an assigned EPS bearer identity value that does not match an existing EPS bearer context, or the combination of an unassigned PTI value and an unassigned EPS bearer identity value, the UE shall respond with an ESM STATUS message including ESM cause #43 "invalid EPS bearer identity". g) If the UE receives an ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message which includes an unassigned or reserved EPS bearer identity value, the UE shall respond with an ACTIVATE DEFAULT EPS BEARER CONTEXT REJECT message including ESM cause #43 "invalid EPS bearer identity". h) If the UE receives an ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message which includes an unassigned or reserved EPS bearer identity value, the UE shall respond with an ACTIVATE DEDICATED EPS BEARER CONTEXT REJECT message including ESM cause #43 "invalid EPS bearer identity". i) If the UE receives a MODIFY EPS BEARER CONTEXT REQUEST message which includes an unassigned or reserved EPS bearer identity value or an assigned EPS bearer identity value that does not match an existing EPS bearer context, the UE shall respond with a MODIFY EPS BEARER CONTEXT REJECT message including ESM cause #43 "invalid EPS bearer identity". j) If the UE receives a DEACTIVATE EPS BEARER CONTEXT REQUEST message which includes an unassigned or reserved EPS bearer identity value or an assigned EPS bearer identity value that does not match an existing EPS bearer context, the UE shall respond with a DEACTIVATE EPS BEARER CONTEXT ACCEPT message with the EPS bearer identity set to the received EPS bearer identity. k) If the UE receives an ESM DATA TRANSPORT message which includes a reserved EPS bearer identity value or an assigned value that does not match an existing EPS bearer context, the UE shall respond with an ESM STATUS message including ESM cause #43 "invalid EPS bearer identity". l) If the UE receives an ESM message other than those listed in items a through j in which the message includes an unassigned or reserved EPS bearer identity value or a value that does not match an EPS bearer context of an established PDN connection, the UE shall ignore the message. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 7.3.2 |
2,399 | M.3 IAB-node Integration Procedure M.3.1 General | IAB-node, consists of a UE function (referred to as IAB-UE) and gNB-DU function [2]. IAB integration procedure consists of 3 phases detailed in TS 38.401[ NG-RAN; Architecture description ] [78]. Phase-1: IAB-UE part setup: The IAB-UE performs registration procedure to the network as a UE as described in TS 23.501[ System architecture for the 5G System (5GS) ] [2] and TS 23.502[ Procedures for the 5G System (5GS) ] [8] in order to register to the 5GC and consequently, the NAS and AS security are established between the IAB-node and 5GC. Phase-2: BH RLC channel establishment and routing update: The BH RLC channels and the BAP layer are established and configured in the IAB-node by the IAB-donor using the secured RRC signalling to support routing between the IAB-node and the IAB-donor. Phase-3: gNB -DU part setup: F1 security establishment for IAB is performed over the RLC channel. The Phase-1 results in IAB-UE registration and consequently, AS security establishment between the IAB donor and IAB-node, Phase-2 results in configuration of the IAB-node securely using the established AS security and Phase-3 results in the establishment of secure F1 interface between the IAB-donor and IAB-node. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | M.3 |
2,400 | 9.4.3 Attach complete | This message is sent by the MS to the network if at least one of the following conditions is fulfilled: - a P-TMSI and/or a TMSI was included within the attach accept message; or - the network has requested the MS to provide feature-related information. See table 9.4.3/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Message type: ATTACH COMPLETE Significance: dual Direction: MS to network Table 9.4.3/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : ATTACH COMPLETE 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.4.3 |
Subsets and Splits
No saved queries yet
Save your SQL queries to embed, download, and access them later. Queries will appear here once saved.