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
⌀ |
|---|---|---|---|---|---|---|---|
1,201 | – SecurityAlgorithmConfig | The IE SecurityAlgorithmConfig is used to configure AS integrity protection algorithm and AS ciphering algorithm for SRBs and DRBs. SecurityAlgorithmConfig information element -- ASN1START -- TAG-SECURITYALGORITHMCONFIG-START SecurityAlgorithmConfig ::= SEQUENCE { cipheringAlgorithm CipheringAlgorithm, integrityProtAlgorithm IntegrityProtAlgorithm OPTIONAL, -- Need R ... } IntegrityProtAlgorithm ::= ENUMERATED { nia0, nia1, nia2, nia3, spare4, spare3, spare2, spare1, ...} CipheringAlgorithm ::= ENUMERATED { nea0, nea1, nea2, nea3, spare4, spare3, spare2, spare1, ...} -- TAG-SECURITYALGORITHMCONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
1,202 | 5.3.1.1 Establishment of the N1 NAS signalling connection | When the UE is in 5GMM-IDLE mode over 3GPP access and needs to transmit an initial NAS message, the UE shall request the lower layer to establish an RRC connection. Upon indication from the lower layers that the RRC connection has been established, the UE shall consider that the N1 NAS signalling connection over 3GPP access is established and enter 5GMM-CONNECTED mode over 3GPP access. When the UE is in 5GMM-IDLE mode over non-3GPP access, and the UE receives an indication from the lower layers of non-3GPP access, that the access stratum connection is established between the UE and the network, the UE shall send an initial NAS message, consider the N1 NAS signalling connection is established and enter 5GMM-CONNECTED mode over non-3GPP access. Initial NAS messages are: a) REGISTRATION REQUEST message; b) DEREGISTRATION REQUEST message; c) SERVICE REQUEST message; and d) CONTROL PLANE SERVICE REQUEST. If the UE is capable of both N1 mode and S1 mode and lower layers provide an indication that the current E-UTRA cell is connected to both EPC and 5GCN, for the routing of the REGISTRATION REQUEST message during the initial registration procedure to the appropriate core network (EPC or 5GCN), the UE NAS provides the lower layers with the selected core network type information. For the routing of the initial NAS message to the appropriate AMF, if the UE holds a 5G-GUTI or 4G-GUTI, the UE NAS provides the lower layers with the UE identity according to the following rules: a) if the registration procedure for mobility and periodic registration update was triggered due to the last CONFIGURATION UPDATE COMMAND message containing the Configuration update indication IE with the Registration bit set to "registration requested" and including: 1) no other parameters; 2) one or both of the Allowed NSSAI IE and the Configured NSSAI IE; or 3) the Network slicing indication IE with the Network slicing subscription change indication set to "Network slicing subscription changed"; the UE NAS shall not provide the lower layers with the 5G-S-TMSI or the registered GUAMI; b) if the service request procedure was initiated over non-3GPP access, the UE NAS shall provide the lower layers with the registered GUAMI, but shall not provide the lower layers with the 5G-S-TMSI; c) if the initial NAS message other than the SERVICE REQUEST or CONTROL PLANE SERVICE REQUEST message was initiated over untrusted non-3GPP access, the UE NAS shall provide the lower layers with the GUAMI of the 5G-GUTI that the UE NAS has selected as specified in the subclause 5.5.1.2.2 and 5.5.1.3.2, but shall not provide the lower layers with the 5G-S-TMSI; if the initial NAS message other than the SERVICE REQUEST or CONTROL PLANE SERVICE REQUEST message was initiated over trusted non-3GPP access, the UE NAS shall provide the lower layers with the 5G-GUTI, if available, otherwise shall provide the lower layers with the SUCI; if the UE is the 5G-RG and the initial NAS message other than the SERVICE REQUEST or CONTROL PLANE SERVICE REQUEST message was initiated over wireline access, the UE NAS shall provide the lower layers with the GUAMI of the 5G-GUTI that the UE NAS has selected as specified in the subclause 5.5.1.2.2 and 5.5.1.3.2, if available, otherwise shall not provide the lower layers with any UE identity; d) if the UE does not hold a 5G-GUTI that was previously assigned by the same PLMN with which the UE is performing the registration procedure and if: 1) the UE operating in the single-registration mode performs a registration procedure for mobility and periodic registration update indicating "mobility registration updating" following an inter-system change from S1 mode to N1 mode; or 2) the UE which was previously registered in S1 mode before entering state EMM-DEREGISTERED, performs an initial registration procedure, the UE has received the interworking without N26 interface indicator set to "interworking without N26 interface not supported" from the network, and the UE holds a 4G-GUTI; then the UE NAS provides the lower layers with a GUAMI part of the 5G-GUTI mapped from 4G-GUTI as specified in 3GPP TS 23.003[ Numbering, addressing and identification ] [4] with an indication that the GUAMI is mapped from EPS; or e) otherwise: 1) if the tracking area of the current cell is in the registration area, the UE NAS shall provide the lower layers with the 5G-S-TMSI, but shall not provide the registered GUAMI to the lower layers; or 2) if the tracking area of the current cell is not in the registration area, the UE NAS shall provide the lower layers with the GUAMI of the 5G-GUTI that the UE NAS has selected as specified in the subclauses 5.5.1.2.2 and 5.5.1.3.2, but shall not provide the lower layers with the 5G-S-TMSI. For 3GPP access, if: a) the UE is operating in single-registration mode, the UE does not hold a 5G-GUTI and the UE does not hold a 4G-GUTI; or b) the UE is operating in dual-registration mode and the UE does not hold a 5G-GUTI; the UE NAS does not provide the lower layers with the 5G-S-TMSI or the registered GUAMI. For untrusted non-3GPP access, if the UE does not hold a 5G-GUTI and the UE does not hold a 4G-GUTI, the UE NAS does not provide the lower layers with the 5G-S-TMSI or the registered GUAMI. For trusted non-3GPP access, if the UE does not hold a 5G-GUTI and the UE does not hold a 4G-GUTI, the UE NAS provides the lower layers with the SUCI. For 3GPP access, if a UE operating as an IAB-node performs a registration procedure or service request procedure (see 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]), the UE NAS shall indicate to the lower layers that the establishment of the NAS signalling connection is for a UE operating as an IAB-node. The UE NAS also provides the lower layers with the identity of the selected PLMN (see 3GPP TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [30]) if the UE is not operating in SNPN access operation mode. If the UE is operating in SNPN access operation mode, the UE NAS provides the lower layers with the SNPN identity of the selected SNPN. In a shared network, the UE shall choose one of the PLMN identity(ies) or SNPN identity(ies) as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] and 3GPP TS 24.502[ Access to the 3GPP 5G Core Network (5GCN) via non-3GPP access networks ] [18]. The UE NAS layer may provide the lower layers with an NSSAI as specified in subclause 4.6.2.3. If the UE performs initial registration for onboarding services in SNPN or is registered for onboarding services in SNPN, the UE NAS layer shall provide the lower layers with an indication that the connection is for onboarding. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.3.1.1 |
1,203 | 6.46.3 Service continuity | For a 5G system with satellite access, the following requirements apply: A 5G system with satellite access shall support service continuity between 5G terrestrial access network and 5G satellite access networks owned by the same operator or owned by different operators having an agreement. Subject to regulatory requirements and operator’s policy, a 5G system with satellite access shall support service continuity (with minimum service interruption) for a UE engaged in an active communication, when the UE changes from a direct network connection via 5G terrestrial access to an indirect network connection via a relay UE (using satellite access) and vice-versa. NOTE: It is assumed that the 5G terrestrial access network and the satellite access network belong to the same operator. Subject to regulatory requirements and operator’s policy, a 5G system with satellite access shall be able to support service continuity (with minimum service interruption) of a UE-Satellite-UE communication when the UE communication path moves between serving satellites (due to the movement of the UE and/or the satellites). Subject to regulatory requirements and operator’s policy, a 5G system with satellite access shall support service continuity (with minimum service interruption) of a UE-Satellite-UE communication when the communication path between UEs extends to additional satellites (through ISLs). | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.46.3 |
1,204 | 4.9.1.3 Inter NG-RAN node N2 based handover 4.9.1.3.1 General | Clause 4.9.1.3 includes details regarding the inter NG-RAN node N2 based handover without Xn interface. The source NG-RAN decides to initiate an N2-based handover to the target NG-RAN. This can be triggered, for example, due to new radio conditions or load balancing, if there is no Xn connectivity to the target NG-RAN, an error indication from the target NG-RAN after an unsuccessful Xn-based handover (i.e. no IP connectivity between T-RAN and S-UPF), or based on dynamic information learnt by the S-RAN. NTN NR supports additional trigger conditions i.e. time-based trigger condition, upon which UE may execute conditional handover to a candidate cell, as defined in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12]. The availability of a direct forwarding path is determined in the source NG-RAN and indicated to the SMFs. If IP connectivity is available between the source and target NG-RAN and security association(s) is in place between them, a direct forwarding path is available. If a direct forwarding path is not available, indirect forwarding may be used. The SMFs use the indication from the source NG-RAN to determine whether to apply indirect forwarding. If both source NG-RAN and source AMF support DAPS the source NG-RAN may decide that some of the DRBs are subject for DAPS handover as defined in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [9]; in this case, the source NG-RAN provides the DAPS information indicating the request concerns a DAPS handover for the DRB as part of the Source to Target (NG-RAN) Transparent Container. If the target NG-RAN accepts that the request concerns DAPS handover and both Target NG-RAN and Target AMF support DAPS, the DAPS handover will be performed and target NG-RAN provides DAPS response information as part of the Target to Source (NG-RAN) Transparent Container. In the case of handover to a shared network, the source NG-RAN determines a PLMN (or PLMN ID and NID, see clause 5.30 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]) to be used in the target network as specified by TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The source NG-RAN shall indicate the selected PLMN ID to be used in the target network to the AMF as part of the Tracking Area sent, or the selected SNPN ID to be used in the target network to the AMF, in the HO Required message. If the AMF generates the N2 downlink signalling during the ongoing handover and receives a rejection to a N2 interface procedure (e.g. DL NAS message transfer; Location reporting control; etc.) from the NG-RAN with an indication that an Inter NG-RAN node handover procedure is in progress, the AMF may reattempt the same N2 interface procedure either when the handover is complete or the handover is deemed to have failed if the AMF is still the serving AMF, when possible. If the Inter NG-RAN node handover changes the serving AMF, the source AMF shall terminate any other ongoing N2 interface procedures except the handover procedure. In order to minimize the number of procedures rejected by NG-RAN, the AMF should pause non-handover related N2 interface procedures (e.g. DL NAS message transfer, Location Report Control, etc.) while a handover is ongoing (i.e. from the time that a Handover Required has been received until either the Handover procedure has succeeded (Handover Notify) or failed (Handover Failure)) and continue them once the Handover procedure has completed if the AMF is still the serving AMF. If during the handover procedure the AMF detects that the AMF needs be changed, the AMF shall reject any SMF initiated N2 request received since handover procedure started and shall include an indication that the request has been temporarily rejected due to handover procedure in progress. Upon reception for an SMF initiated N1 and/or N2 request(s) with an indication either from the NG-RAN (via N2 SM Info) or AMF that the request has been temporarily rejected due to handover procedure in progress, the SMF starts a locally configured guard timer. The SMF should hold any signalling messages targeted towards AMF for a given UE during the handover preparation phase unless it detects that the handover execution is completed or handover has failed/cancelled. The SMF may re-attempt, up to a pre-configured number of times, when either it detects that the handover is completed or has failed using message reception or at expiry of the guard timer. In the case of N2 handover within the VPLMN in a home routed roaming scenario, the SMF in the Inter NG-RAN node N2 based handover procedure (Figure 4.9.1.3.2-1 and Figure 4.9.1.3.3-1) interacting with the S-UPF, T-UPF, S-AMF and T-AMF is the V-SMF and the SMF (Figure 4.9.1.3.3-1) interacting with the UPF (PSA) is the H-SMF. In the case of inter-PLMN N2 handover in a home routed roaming scenario, the procedures in clause 4.23 apply. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.9.1.3 |
1,205 | 4.3.33.2 Connection Release | A Multi-USIM UE may request to be released to ECM-IDLE state for a USIM due to activity on another USIM if both the UE and the network indicate to each other the Connection Release feature is supported. A Multi-USIM UE indicates that it requests to be released to ECM-IDLE state for the USIM by initiating the Service Request procedure (using Extended Service Request message) or a Tracking Area Update procedure if the UE needs to perform Tracking Area Update at the same time with this network (including the case where the Tracking Area Update is performed due to mobility to a Tracking Area outside the current Tracking Area List, i.e. before detecting whether the network supports the feature in the new Tracking Area, provided that the network has already indicated support for Connection Release feature in the current Tracking Area List), by including a Release Request indication. If supported by the UE and network, the UE may also provide, together with the Release Request indication, Paging Restriction Information, as specified in clause 4.3.33.6, which requests the network to restrict paging. NOTE: When there is no PLMN-wide support for the Connection Release feature, it can occur that upon tracking area update with Release Request indication the UE is not released by the network. The UE behaviour, when it detects that the network does not support the feature in a new TA, is outside the scope of this specification. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3.33.2 |
1,206 | A.6.2 Reusability | The following design guidelines are used for specifying NF services to be reusable. - NF service operations are specified such that other NF can potentially invoke them in future, if required. - The service operations may be usable in multiple system procedures specified in clause 4 of this specification. - Using clause 4 of the current document, the system procedures in which the NF service operations can be used are considered and based on that the parameters for the NF service operations are clearly listed. NOTE: It is possible that, when mapping an end to end call flow to service based architecture, one step in the call flow may map to multiple NF service operation invocations. This specification clearly identifies each NF service operation invocation in the call flow. Protocol optimization of multiple NF service operation invocations are left for TS 29.500[ 5G System; Technical Realization of Service Based Architecture; Stage 3 ] [17] consideration. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | A.6.2 |
1,207 | 5.3.5.13.5 Conditional reconfiguration execution | The UE shall: 1> if more than one pair of triggered PCell and associated triggered PSCell exist: 2> select one of the triggered PCell(s) and the associated triggered PSCell(s) as the selected cells for conditional reconfiguration execution; 1> else if only one pair of triggered PCell and associated triggered PSCell exists: 2> consider the triggered PCell and the associated triggered PSCell as the selected cells for conditional reconfiguration execution; 1> else if more than one triggered cell exists: 2> select one of the triggered cells as the selected cell for conditional reconfiguration execution; 1> else: 2> consider the triggered cell as the selected cell for conditional reconfiguration execution; 1> for the selected cell(s) of conditional reconfiguration execution: 2> if the subsequentCondReconfig is included in the entry in VarConditionalReconfig containing the RRCReconfiguration message for the selected cell: 3> perform the actions as specified in 5.3.5.13.8; 2> else: 3> apply the stored condRRCReconfig of the selected cell and perform the actions as specified in 5.3.5.3; NOTE: If multiple NR cells are triggered in conditional reconfiguration execution, it is up to UE implementation which one to select, e.g. the UE considers beams and beam quality to select one of the triggered cells for execution. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.5.13.5 |
1,208 | 4.1.2.3 MM sublayer states on the network side | 1. IDLE The MM sublayer is not active except possibly when the RR sublayer is in Group Receive mode. 2. WAIT FOR RR CONNECTION The MM sublayer has received a request for MM connection establishment from the CM layer. A RR connection to the mobile station is requested from the RR sublayer (i.e. paging is performed). 3. MM CONNECTION ACTIVE The MM sublayer has a RR connection to a mobile station. One or more MM connections are active, or no MM connection is active but an RRLP procedure or LCS procedure over RRC is ongoing. 4. IDENTIFICATION INITIATED The identification procedure has been started by the network. The timer T3270 is running. 5. AUTHENTICATION INITIATED The authentication procedure has been started by the network. The timer T3260 is running. 6. TMSI REALLOCATION INITIATED The TMSI reallocation procedure has been started by the network. The timer T3250 is running. 7. SECURITY MODE INITIATED In Iu mode, the security mode setting procedure has been requested to the RR sublayer. In A/Gb mode, the cipher mode setting procedure has been requested to the RR sublayer. 8a. WAIT FOR MOBILE ORIGINATED MM CONNECTION A CM SERVICE REQUEST message is received and processed, and the MM sublayer awaits the "opening message" of the MM connection. 8b. WAIT FOR NETWORK ORIGINATED MM CONNECTION A CM SERVICE PROMPT message has been sent by the network and the MM sublayer awaits the "opening message" of the MM connection $(CCBS)$. 9. WAIT FOR REESTABLISHMENT The RR connection to a mobile station with one or more active MM connection has been lost. The network awaits a possible re-establishment request from the mobile station. 10. WAIT OF A GROUP CALL Only applicable in case for mobile station supporting VGCS talking. The MM sublayer has received a request for establishing a VGCS from the GCC sublayer. The request for establishing a VGCS channels is given to the RR sublayer. 11. GROUP CALL ACTIVE Only applicable in case of mobile station supporting VGCS talking. A VGCS channel is established by the RR sublayer. An RR connection to the talking mobile station can be established by the RR sublayer on the VGCS channel. The MM sublayer is active but no sending of MM message between the network and the mobile station has occurred. 12. MM CONNECTION ACTIVE (GROUP CALL) Only applicable in case of mobile station supporting VGCS talking. The MM sublayer has a RR connection to the talking mobile station on the VGCS channel. Only one MM connection is active. 13. WAIT FOR BROADCAST CALL Only applicable in case of VBS. The MM sublayer has received a request for a VBS establishment from the BCC sublayer. The request for establishment of VBS channels is given to the RR sublayer. 14. BROADCAST CALL ACTIVE Only applicable in case of VBS. A VBS channel is established by the RR sublayer. The MM sublayer is active but no explicit MM establishment between the Network and the mobile station has occurred. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.1.2.3 |
1,209 | H.2.1 Secondary authentication and authorization by DN-AAA at PDN Connection Establishment | In the figure H.2.1-1, the execution of the secondary authentication and authorization by DN-AAA is specified. The procedure assumes that: - The APN is associated with the selection of a SMF+PGW-C to serve APN(s) that require secondary authentication and authorization by DN-AAA at PDN connection establishment. - The SMF+PGW-C is configured with local policies indicating that the APN requires secondary authentication and authorization by DN-AAA at PDN connection establishment. Figure H.2.1-1: EAP-based secondary authentication and authorization by DN-AAA at PDN connection establishment 0. As steps 1 - 13 of Figure 5.3.2.1-1 in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13] (Attach Request) or as steps 1 to 3 of Figure 5.10.2 in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13] (UE requested PDN connectivity) with following modifications: The UE may indicate in PCO its capability to support EAP-based secondary DN authentication over EPC if the UE included the PDU Session Id in PCO. The UE may also include the DN-specific identity. 1. The SMF+PGW-C gets subscription data from UDM as defined in step 4 of Figure 4.3.2.2.1-1 (not shown in Figure H.2.1-1). The procedure assumes that SMF configuration or subscription data from UDM require EAP-based secondary authentication and authorization by DN-AAA. Secondary DN authorization may be invoked as described in TS 29.561[ 5G System; Interworking between 5G Network and external Data Networks; Stage 3 ] [63]. During this step the DN-AAA may provide an IP address for the UE and other DN authorization data as described in clause 5.6.6 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 2a. If dynamic PCC is to be used for the PDU Session, the SMF+PGW-C performs an SM Policy Association Establishment procedure as defined in clause 4.16.4 and if Secondary DN authorization has been invoked in step 1, provides to the PCF the PDN Connection parameters received from the DN AAA at step 1 as described in step 5 of Figure 4.3.2.3-1. In this step the SMF+PGW-C may retrieve the PDU Session related policy information and the PCC rule(s) from the PCF, e.g. the authorized Session AMBR. 2b. UPF selection and N4 session establishment is executed with the difference that the SMF+PGW-C configures the UPF+PGW-U to block any UE traffic over the PDN Connection (until the Secondary DN authentication and authorization has been done and is successful). 3. Steps 15-24 in Figure 5.3.2.1-1 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13] or steps 5-16 in Figure 5.10.2 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13]. During the Attach procedure, at step 15 in Figure 5.3.2.1-1 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13] or during UE requested PDN connectivity in step 5 in Figure 5.10.2 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13], the SMF+PGW-C includes in PCO, an Indication to the UE that "UpLink Data is NOT ALLOWED" on the PDN connection. The UE shall not send Uplink data to the network, until it receives an indication further from the network that "UpLink Data is ALLOWED". NOTE: How the Indication that Uplink data allowed/not allowed is carried in PCO is defined in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [25]. 4. [Conditional] The PGW-C+SMF initiates EAP-based authentication by sending EAP-Request as described in step 2 of Figure 4.3.2.3-1. 5. Multiple round-trip messages as required by the authentication method used by DN-AAA may follow. The PCO including the authentication message from the DN-AAA is transferred to the UE by the SMF+PGW-C in Update Bearer Request and then over S1 by Downlink NAS Transport (steps 4b-4d). The response from the UE is transferred to the SMF+PGW-C in an Uplink NAS Transport over S1 and Update Bearer Response (steps 4e-4g) over EPS. 6. Secondary authentication and authorization by DN-AAA procedure continues as described in step 4 of Figure 4.3.2.3-1. 7. The SMF+PGW-C updates the N4 rules in the UPF+PGW-U to allow traffic over the PDN Connection. If dynamic PCC is to be used for the PDU Session and the SMF+PGW-C received DN Authorization information from the DN-AAA as part of step 5 or 6 that is different compared to the value received in step 2, the SMF+PGW-C contacts the PCF to update the PDN Connection as described in step 5 of Figure 4.3.2.3-1 8. The SMF+PGW-C updates the UE by invoking the PDN GW initiated bearer modification without QoS update procedure (figure 5.4.3-1 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13]) initiated by sending an Update Bearer Request message to the SGW. The PCO includes an indication that "UpLink Data is ALLOWED". The UE confirms the update (see clause 5.4.3 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13]). If the UE IP address is to be delivered to the UE over user plane (via Router advertisement or DHCP) then the UE IP address is only delivered to the UE after step 8. 9. As in step 6 of Figure 4.3.2.3-1. The DN-AAA Server may revoke the authorization for a PDN connection or update DN authorization data for a PDN connection. According to the request from DN-AAA Server, the SMF+PGW-C may release or update the PDN connection. At any time after the PDN connection establishment, the DN-AAA Server or SMF+PGW-C may initiate Secondary Re-authentication procedure for the PDN connection as described in clause 4.3.2.3. Steps 4a-4h are performed to transfer the Secondary Re-authentication message between the DN-AAA Server and the UE. The Secondary Re-authentication procedure may start from step 4a (DN-AAA initiated Secondary Re-authentication procedure) or step 4b (SMF+PGW-C initiated Secondary Re-authentication procedure). During Secondary Re-authentication, if the SMF+PGW-C receives an indication from the MME that the UE is unreachable then it informs the DN-AAA Server that UE is not reachable for re-authentication. Based on this indication from SMF+PGW-C, the DN-AAA Server may decide to keep the PDN connection or request to release it. DN-AAA may initiate DN-AAA Re-authorization without performing re-authentication based on local policy. DN-AAA Re-authorization procedure may involve steps 5 and 6 of Figure H.2.1-1 above. During Secondary Re-authentication/Re-authorization, if the SMF+PGW-C receives DN Authorization Profile Index and/or DN authorized Session AMBR, the SMF+PGW-C reports the received value(s) to the PCF (as described in TS 23.501[ System architecture for the 5G System (5GS) ] [2]) by triggering the Policy Control Request Trigger as described in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | H.2.1 |
1,210 | 4.4.3.2 Replay protection | Replay protection shall be supported for received NAS messages both in the MME and the UE. However, since the realization of replay protection does not affect the interoperability between nodes, no specific mechanism is required for implementation. Replay protection must assure that one and the same NAS message is not accepted twice by the receiver. Specifically, for a given EPS security context, a given NAS COUNT value shall be accepted at most one time and only if message integrity verifies correctly. Replay protection is not applicable when EIA0 is used. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.4.3.2 |
1,211 | 10.2.1.1 Physical channels | A downlink narrowband physical channel corresponds to a set of resource elements carrying information originating from higher layers and is the interface defined between TS 36.212[ Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and channel coding ] [3] and the present document TS 36.211[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation ] . The following downlink physical channels are defined: - Narrowband Physical Downlink Shared Channel, NPDSCH - Narrowband Physical Broadcast Channel, NPBCH - Narrowband Physical Downlink Control Channel, NPDCCH | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 10.2.1.1 |
1,212 | 5.3.5.13b1 SCG activation without SN message | Upon initiating the procedure, the UE shall: 1> if the SCG was deactivated before the reception of the RRCReconfiguration message or the E-UTRA RRCConnectionReconfiguration message for which the procedure invoking this clause is executed: 2> consider the SCG to be activated; 2> indicate to lower layers that the SCG is activated; 2> resume performing radio link monitoring on the SCG, if previously stopped; 2> indicate to lower layers to resume beam failure detection on the PSCell, if previously stopped; 2> if bfd-and-RLM was not configured to true before the reception of the RRCReconfiguration message or the E-UTRA RRCConnectionReconfiguration message for which the procedure invoking this clause is executed; or 2> if lower layers indicate that a Random Access procedure is needed for SCG activation: 3> initiate the Random Access procedure on the PSCell, as specified in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3]. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.5.13b1 |
1,213 | 5.3.4.4 Abnormal procedures | If a MODIFY, MODIFY COMPLETE or MODIFY REJECT message is received in the "disconnect indication", "disconnect request" (mobile station side only) or "release request" state then the received message shall be discarded and no action shall be taken. If a MODIFY COMPLETE message indicating a call mode which does not correspond to the requested one is received or if a MODIFY REJECT message indicating a call mode which does not correspond to the actual one is received then the received message shall be discarded and no action shall be taken. If a MODIFY message indicating a call mode which does not belong to those negotiated and agreed during the establishment phase of the call, is received, then a MODIFY REJECT message with the actual call mode and with cause # 57 "bearer capability not authorized" shall be sent back. Figure 5.10a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] In-call modification sequence initiated by MS Figure 5.10b/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] In-call modification sequence initiated by network | 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.4 |
1,214 | – FeatureSetDownlinkId | The IE FeatureSetDownlinkId identifies a downlink feature set. The FeatureSetDownlinkId of a FeatureSetDownlink is the index position of the FeatureSetDownlink in the featureSetsDownlink list in the FeatureSets IE. The first element in that list is referred to by FeatureSetDownlinkId = 1. The FeatureSetDownlinkId=0 is not used by an actual FeatureSetDownlink but means that the UE does not support a carrier in this band of a band combination. FeatureSetDownlinkId information element -- ASN1START -- TAG-FEATURESETDOWNLINKID-START FeatureSetDownlinkId ::= INTEGER (0..maxDownlinkFeatureSets) -- TAG-FEATURESETDOWNLINKID-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
1,215 | 8.2.3.3.2 Minimum Requirement for TDD PCell | For TDD FDD CA with TDD PCell and 2DL CCs, the requirements are specified in Table 8.2.3.3.2-4 based on single carrier requirement specified in Table 8.2.3.3.2-2 and Table 8.2.3.3.2-3, with the addition of the parameters in Table 8.2.3.3.2-1 and the downlink physical channel setup according to Annex C.3.2. The purpose of these tests is to verify the closed loop rank-two performance with wideband and frequency selective precoding. For TDD FDD CA with TDD PCell and 3DL CCs, the requirements are specified in Table 8.2.3.3.2-5 based on single carrier requirement specified in Table 8.2.3.3.2-2 and Table 8.2.3.3.2-3, with the addition of the parameters in Table 8.2.3.3.2-1 and the downlink physical channel setup according to Annex C.3.2. The purpose of these tests is to verify the closed loop rank-two performance with wideband and frequency selective precoding. For TDD FDD CA with TDD PCell and 4DL CCs, the requirements are specified in Table 8.2.3.3.2-6 based on single carrier requirement specified in Table 8.2.3.3.2-2 and Table 8.2.3.3.2-3, with the addition of the parameters in Table 8.2.3.3.2-1 and the downlink physical channel setup according to Annex C.3.2. The purpose of these tests is to verify the closed loop rank-two performance with wideband and frequency selective precoding. For TDD FDD CA with TDD PCell and 5DL CCs, the requirements are specified in Table 8.2.3.3.2-7 based on single carrier requirement specified in Table 8.2.3.3.2-2 and Table 8.2.3.3.2-3, with the addition of the parameters in Table 8.2.3.3.2-1 and the downlink physical channel setup according to Annex C.3.2. The purpose of these tests is to verify the closed loop rank-two performance with wideband and frequency selective precoding. For TDD FDD CA with TDD PCell and 6DL CCs, the requirements are specified in Table 8.2.3.3.2-8 based on single carrier requirement specified in Table 8.2.3.3.2-2 and Table 8.2.3.3.2-3, with the addition of the parameters in Table 8.2.3.3.2-1 and the downlink physical channel setup according to Annex C.3.2. The purpose of these tests is to verify the closed loop rank-two performance with wideband and frequency selective precoding. For TDD FDD CA with TDD PCell and 7DL CCs, the requirements are specified in Table 8.2.3.3.2-9 based on single carrier requirement specified in Table 8.2.3.3.2-2 and Table 8.2.3.3.2-3, with the addition of the parameters in Table 8.2.3.3.2-1 and the downlink physical channel setup according to Annex C.3.2. The purpose of these tests is to verify the closed loop rank-two performance with wideband and frequency selective precoding. The test coverage for different number of component carriers is defined in 8.1.2.4. Table 8.2.3.3.2-1: Test Parameters for Multi-Layer Spatial Multiplexing (FRC) for CA Table 8.2.3.3.2-2: Single carrier performance with different bandwidths for multiple CA configurations for FDD SCell (FRC) Table 8.2.3.3.2-3: Single carrier performance with different bandwidths for multiple CA configurations for TDD PCell and SCell (FRC) Table 8.2.3.3.2-4: Minimum performance for multiple CA configurations with 2DL CCs (FRC) Table 8.2.3.3.2-5: Minimum performance for multiple CA configurations with 3DL CCs (FRC) Table 8.2.3.3.2-6: Minimum performance for multiple CA configurations with 4DL CCs (FRC) Table 8.2.3.3.2-7: Minimum performance for multiple CA configurations with 5DL CCs (FRC) Table 8.2.3.3.2-8: Minimum performance for multiple CA configurations with 6DL CCs (FRC) Table 8.2.3.3.2-9: Minimum performance for multiple CA configurations with 7DL CCs (FRC) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.2.3.3.2 |
1,216 | 17.5.11 Session Update Procedure | The BM-SC initiates the MBMS session update procedure when the service area for an ongoing MBMS session shall be modified. This procedure is defined only for MBMS broadcast services. The MBMS session update procedure is initiated towards one or more of the GGSNs in the list of downstream nodes in the BM-SC, according to the changes in the service area. NOTE: In addition, when the MBMS Service Area for an ongoing broadcast session is changed in the BM-SC, then GGSN(s) may be added to, or removed from, the list of downstream nodes in the BM-SC. The BM-SC will initiate MBMS session start procedures or MBMS session stop procedures towards these GGSNs accordingly. The attributes that can be modified by the session update procedure are the MBMS Service Area, and the list of downstream nodes for GGSN. When a session update message is received, GGSN will update its MBMS Bearer Context accordingly and inform its downstream SGSNs of the changed MBMS service area. If a list of downstream SGSNs is included in the session update message, GGSN shall initiate a session start procedure towards the new downstream SGSNs, and a session stop procedure towards the SGSNs that have been removed from the list. Figure 27a: MBMS Session Update procedure 1. The BM-SC sends a RAR message to the GGSNs that need to update its session attributes. 2. GGSN stores the updated session attributes in the MBMS Bearer Context, initiates session start, session stop or session update procedures towards the SGSNs in its list of downstream nodes and sends an RAA message to the BM-SC. An AAR message is not mandated for the Gmb application in response to a RAR-RAA command exchange. | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 17.5.11 |
1,217 | 5.5.4.7 Abnormal cases on the network side | The following abnormal cases on the network side can be identified: a) Lower layer failure before the RELAY KEY AUTHENTICATION RESPONSE message is received. The network shall abort the authentication and key agreement procedure for 5G ProSe UE-to-network relay or 5G ProSe UE-to-UE relay. b) Collision between the authentication and key agreement procedure for 5G ProSe UE-to-network relay or 5G ProSe UE-to-UE relay and de-registration procedure. The network shall abort the authentication and key agreement procedure for 5G ProSe UE-to-network relay or 5G ProSe UE-to-UE relay and proceed with the UE-initiated de-registration procedure. c) Collision between the authentication and key agreement procedure for 5G ProSe UE-to-network relay or 5G ProSe UE-to-UE relay and other 5GMM procedures other than in item b. The network shall progress both procedures. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.4.7 |
1,218 | C.1 Storage of 5GMM information for UEs not operating in SNPN access operation mode | The following 5GMM parameters shall be stored on the USIM if the corresponding file is present: a) 5G-GUTI; b) last visited registered TAI; c) 5GS update status; d) 5G NAS security context parameters from a full native 5G NAS security context (see 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]); e) KAUSF and KSEAF (see 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]); f) SOR counter (see subclause 9.11.3.51); and g) UE parameter update counter (see subclause 9.11.3.53A); 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 first 5G security context of one access shall be stored in record 1 of the 5G NAS Security Context USIM file for that access and the second 5G security context of that access shall be stored in record 2 of the same file. The presence and format of corresponding files on the USIM is specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [22]. If the corresponding file is not present on the USIM, these 5GMM parameters are stored in a non-volatile memory in the ME together with the SUPI from the USIM. These 5GMM parameters can only be used if the SUPI from the USIM matches the SUPI stored in the non-volatile memory; else the UE shall delete the 5GMM parameters. The following 5GMM parameters shall be stored in a non-volatile memory in the ME together with the SUPI from the USIM: - configured NSSAI(s); - NSSRG information; - S-NSSAI time validity information; - S-NSSAI location validity information; - network slice usage control information; - NSSAI inclusion mode(s); - MPS indicator; - MCS indicator; - operator-defined access category definitions; - network-assigned UE radio capability IDs; - "CAG information list", if the UE supports CAG; - signalled URSP (see 3GPP TS 24.526[ User Equipment (UE) policies for 5G System (5GS); Stage 3 ] [19]); - SOR-CMCI; - one or more lists of type "list of PLMN(s) to be used in disaster condition", if the UE supports MINT; - disaster roaming wait range, if the UE supports MINT; - disaster return wait range, if the UE supports MINT; - indication of whether disaster roaming is enabled in the UE; - indication of 'applicability of "lists of PLMN(s) to be used in disaster condition" provided by a VPLMN'; - VPS URSP configuration; and - indication of whether interworking without N26 interface is supported. The following 5GMM parameters should be stored in a non-volatile memory in the ME together with the SUPI from the USIM: - allowed NSSAI(s); and - partially allowed NSSAI(s). Each configured NSSAI consists of S-NSSAI(s) stored together with a PLMN identity, if it is associated with a PLMN. The UE shall store the S-NSSAI(s) of the HPLMN. If the UE is in the VPLMN, the UE shall also store the configured NSSAI for the current PLMN and any necessary mapped S-NSSAI(s). The configured NSSAI(s) can only be used if the SUPI from the USIM matches the SUPI stored in the non-volatile memory of the ME; else the UE shall delete the configured NSSAI(s). A configured NSSAI may be associated with NSSRG information, S-NSSAI location validity information, S-NSSAI time validity information, NSAG information and network slice usage control information. Each NSSAI inclusion mode is associated with a PLMN identity and access type. The NSSAI inclusion mode(s) can only be used if the SUPI from the USIM matches the SUPI stored in the non-volatile memory of the ME; else the UE shall delete the NSSAI inclusion mode(s). The MPS indicator is stored together with a PLMN identity of the PLMN that provided it, and is valid in that RPLMN or equivalent PLMN. The MPS indicator can only be used if the SUPI from the USIM matches the SUPI stored in the non-volatile memory of the ME, else the UE shall delete the MPS indicator. The MCS indicator is stored together with a PLMN identity of the PLMN that provided it, and is valid in that RPLMN or equivalent PLMN. The MCS indicator can only be used if the SUPI from the USIM matches the SUPI stored in the non-volatile memory of the ME, else the UE shall delete the MCS indicator. Operator-defined access category definitions are stored together with a PLMN identity of the PLMN that provided them, and is valid in that PLMN or equivalent PLMN. The operator-defined access category definitions can only be used if the SUPI from the USIM matches the SUPI stored in the non-volatile memory of the ME, else the UE shall delete the operator-defined access category definitions. The maximum number of stored operator-defined access category definitions is UE implementation dependent. Each network-assigned UE radio capability ID is stored together with a PLMN identity of the PLMN that provided it as well as a mapping to the corresponding UE radio configuration, and is valid in that PLMN. A network-assigned UE radio capability ID can only be used if the SUPI from the USIM matches the SUPI stored in the non-volatile memory of the ME, else the UE shall delete the network-assigned UE radio capability ID. The UE shall be able to store at least the last 16 received network-assigned UE radio capability IDs. There shall be only one network-assigned UE radio capability ID stored for a given combination of PLMN identity and UE radio configuration and any existing UE radio capability ID shall be deleted when a new UE radio capability ID is added for the same combination of PLMN identity and UE radio configuration. If the UE receives a network-assigned UE radio capability ID with a Version ID value different from the value included in the network-assigned UE radio capability ID(s) stored at the UE for the serving PLMN, the UE may delete these stored network-assigned UE radio capability ID(s). The allowed NSSAI(s) can be stored in a non-volatile memory in the ME together with the SUPI from the USIM. Allowed NSSAI consists of S-NSSAI(s) stored together with a PLMN identity, if it is associated with a PLMN. If the allowed NSSAI is stored, then the UE shall store the S-NSSAI(s) of the HPLMN. If the UE is in the VPLMN, the UE shall also store the allowed NSSAI for the serving PLMN and any necessary mapping of the allowed NSSAI for the serving PLMN to the S-NSSAI(s) of the HPLMN. The allowed NSSAI(s) can only be used if the SUPI from the USIM matches the SUPI stored in the non-volatile memory of the ME; else the UE shall delete the allowed NSSAI(s). The partially allowed NSSAI(s) can be stored as allowed NSSAI(s) in a non-volatile memory in the ME together with the SUPI from the USIM. Partially allowed NSSAI consists of allowed S-NSSAI(s) and for each S-NSSAI a list of TAs for which the S-NSSAI is allowed, together with a PLMN identity. If the UE is registered for emergency services, the UE shall not store the 5GMM parameters described in this annex on the USIM or in non-volatile memory. Instead the UE shall temporarily store these parameters locally in the ME and the UE shall delete these parameters when the UE is deregistered from emergency services (e.g. before registering for normal service). 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 ] [22], the UE shall not store the 5GMM parameters described in this annex on the USIM or in non-volatile memory. Instead the UE shall temporarily store these parameters locally in the ME and the UE shall delete these parameters when the UE enters 5GMM-DEREGISTERED.eCALL-INACTIVE state, the UE is switched-off or the USIM is removed. The "CAG information list" can only be used if the SUPI from the USIM matches the SUPI stored in the non-volatile memory of the ME; else the UE shall delete the "CAG information list". The handling of the SOR-CMCI stored in the non-volatile memory in the ME is specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]. Each "list of PLMN(s) to be used in disaster condition" is stored together with the PLMN identity of the PLMN that provided it. The stored lists of type "list of PLMN(s) to be used in disaster condition" can only be used if the SUPI from the USIM matches the SUPI stored in the non-volatile memory of the ME; else the UE shall delete the lists of type "list of PLMN(s) to be used in disaster condition". The UE shall store at least the "list of PLMN(s) to be used in disaster condition" provided by the HPLMN or EHPLMN. If the 'applicability of "lists of PLMN(s) to be used in disaster condition" provided by a VPLMN' is set to "true", the UE should also store the "list of PLMN(s) to be used in disaster condition" provided by the VPLMN. The maximum number of stored lists of type "list of PLMN(s) to be used in disaster condition" provided by a PLMN other than the HPLMN or EHPLMN is UE implementation dependent. The disaster roaming wait range can only be used if the SUPI from the USIM matches the SUPI stored in the non-volatile memory of the ME; else the UE shall delete the disaster roaming wait range. The disaster return wait range can only be used if the SUPI from the USIM matches the SUPI stored in the non-volatile memory of the ME; else the UE shall delete the disaster return wait range. The indication of whether disaster roaming is enabled in the UE can only be used if the SUPI from the USIM matches the SUPI stored in the non-volatile memory of the ME; else the UE shall delete the indication of whether disaster roaming is enabled in the UE. The indication of 'applicability of "lists of PLMN(s) to be used in disaster condition" provided by a VPLMN' can only be used if the SUPI from the USIM matches the SUPI stored in the non-volatile memory of the ME; else the UE shall delete the indication of 'applicability of "lists of PLMN(s) to be used in disaster condition" provided by a VPLMN'. | 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 | C.1 |
1,219 | 5.2.6 Downlink Reference Signals and Measurements for Positioning | The DL Positioning Reference Signals (DL PRS) are defined to facilitate support of different positioning methods such as DL-TDOA, DL-AoD, multi-RTT through the following set of UE measurements DL RSTD, DL PRS-RSRP, and UE Rx-Tx time difference respectively 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]. Besides DL PRS signals, UE can use SSB and CSI-RS for RRM (RSRP and RSRQ) measurements for E-CID type of positioning. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.2.6 |
1,220 | 5.30.2.9.3 Credentials Holder using AUSF and UDM for primary authentication and authorization | An SNPN may support primary authentication and authorization of UEs that use credentials from a Credentials Holder using AUSF and UDM. The Credentials Holder may be an SNPN or a PLMN. The Credentials Holder UDM provides to SNPN the subscription data. NOTE 1: A list of functionalities not supported in SNPN is provided in clause 5.30.2.0. Optionally, an SNPN may support network slicing (including Network Slice-Specific Authentication and Authorization, Network Slice Access Control and subscription-based restrictions to simultaneous registration of network slices) for UEs that use credentials from a Credentials Holder using AUSF and UDM. The SNPN retrieves NSSAA and NSSRG information from the UDM of the Credentials Holder. Figure 5.30.2.9.3-1 depicts the 5G System architecture for SNPN with Credentials Holder using AUSF and UDM for primary authentication and authorization and network slicing. NOTE 2: The architecture for SNPN and Credentials Holder using AUSF and UDM is depicted as a non-roaming reference architecture as the UE is not considered to be roaming, even though some of the roaming architecture reference points are also used, e.g. for AMF and SMF in SNPN to register with and retrieve subscription data from UDM of the Credentials Holder. Figure 5.30.2.9.3-1: 5G System architecture with access to SNPN using credentials from Credentials Holder using AUSF and UDM | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.30.2.9.3 |
1,221 | 5.2.2.2.3 Namf_Communication_RegistrationStatusUpdate service operation | Service operation name: Namf_Communication_RegistrationStatusUpdate Description: This service operation is used by the consumer NF to inform the AMF that a prior UE context transfer has resulted in the UE successfully registering with it. The UE context is marked inactive in the AMF. Input, Required: 5G-GUTI, Status. Input, Optional: PDU Session ID(s) (indicates the PDU Session(s) to be released), PCF reselected indicator (indicates that new AMF has selected a new PCF to handle the AM Policy association and/or the UE Policy association). Output, Required: None. Output, Optional: None. See clause 4.2.2.2.2 step 10 for example usage of this service operation. When the AMF receives this request, it marks the UE context information as inactive since the UE context has been successfully transferred to the peer NF and the UE has successfully registered there. The AMF receives information about whether the AM Policy Association Information and/or the UE Policy Association Information in the UE context will be used or not (i.e. new AMF may select a different PCF and then create a new AM Policy Association and/or a new UE Policy Association). The AMF sends a Namf_Communication_RegistrationStatusUpdate response to the consumer NF. NOTE 2: Whether notification Ack need a separate message or be realized in the transport layer will be determined in TS 29.518[ 5G System; Access and Mobility Management Services; Stage 3 ] [18]. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.2.2.3 |
1,222 | N.2.3 Session Management aspects | For session management level information and interactions such as monitoring the PNI-NPN or SNPN performance, and enabling suitable QoS for UE in the PNI-NPN or SNPN for Localized Service, the following non-exhaustive options can be used: - Covered by the SLA between the PNI-NPN or SNPN operator and the Localized Service Provider. - Reuse the existing network exposure procedures as specified in TS 23.502[ Procedures for the 5G System (5GS) ] [3] clause 4.15, where the Localized Service Provider is taking the AF role and utilizing the exposure capability provided by the PNI-NPN or SNPN. - Enable NEF/PCF in the PNI-NPN or SNPN providing access to the Localized Services (via AF of the Localized Service Provider) to receive and forward the validity conditions and QoS requirements of the Localized Services to the AMF/SMF by reusing the existing PCF initiated AM/SM policy association procedures described in TS 23.502[ Procedures for the 5G System (5GS) ] [3] clause 4.16. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | N.2.3 |
1,223 | 4.23.7.3.3 Execution phase | Figure 4.23.7.3.3-1: Inter NG-RAN node N2 based handover, execution phase, with I-SMF insertion/change/removal 1. Steps 1-6 in clause 4.9.1.3.3 are performed with the following change: Step 6a: For PDU sessions in the UE context, if the I-SMF is either to be changed, or to be removed, the T-AMF includes an indication in Namf_Communication_N2InfoNotify to indicate the I-SMF change/removal. Step 6c: The SMF in this step is source I-SMF in the case of I-SMF removal or change, or is SMF in the case of I-SMF insertion. Case: I-SMF insertion, or I-SMF change, step 2~9 are skipped for I-SMF removal case. 2. T-AMF to Target I-SMF: Nsmf_PDUSession_UpdateSMContext Request (Handover Complete indication, (N2 SM Information (Secondary RAT usage data))). Handover Complete indication is sent per each PDU Session to the corresponding Target I-SMF to indicate the success of the N2 Handover. If in step 6b of clause 4.9.1.3.3 the source AMF has provided information for secondary RAT usage reporting the T-AMF propagates this information to the Target I-SMF. Case: I-SMF change, step 3 is skipped for I-SMF insertion. 3a. S-AMF to Source I-SMF: Nsmf_PDUSession_ReleaseSMContext Request (I-SMF only indication). After received N2 handover notify from T-AMF, if indication of I-SMF change/removal has been received, the S-AMF invokes Nsmf_PDUSession_ReleaseSMContext Request to inform the Source I-SMF to release the SM context of the PDU Session. The I-SMF only indication is used to inform the Source I-SMF not to invoke resource release in SMF. The Source I-SMF initiates a timer to release the SM Context of the PDU Session if indirect forwarding tunnel(s) were previously established, or if the Source I-SMF has not received request from Target I-SMF to retrieve SM Context. Otherwise, the Source I-SMF immediately releases the SM Context. 3b. Source I-SMF to S-AMF: Nsmf_PDUSession_ReleaseSMContext Response. 4a. Void. 4b. Void. 5a. Target I-SMF to Target I-UPF: N4 Session Modification Request. The N4 Modification Request indicates DL AN Tunnel Info of T-RAN to UPF. 5b. The Target I-UPF to Target I-SMF: N4 Session Modification Response. 6. Target I-SMF to SMF: In the case of I-SMF change, Nsmf_PDUSession_Update Request (PDU Session ID, DL CN Tunnel Info of Target I-UPF for N9, DNAI(s) supported by the I-SMF, Secondary RAT usage data). In the case of I-SMF insertion, Nsmf_PDUSession_Update Request (PDU Session ID, DL CN Tunnel Info of Target I-UPF for N9, DNAI(s), Secondary RAT usage data, Handover Complete Indication). The SMF initiates a timer to release the resource, i.e. resource for indirect data forwarding tunnel. If the T-AMF has provided information for secondary RAT usage reporting in step 2, the Target I-SMF propagates this information to the SMF. 7a. SMF to UPF (PSA): N4 Session Modification Request. The SMF sends N4 Session Modification Request to UPF PSA, providing the DL CN Tunnel Info of Target I-UPF to the UPF PSA. 7b. UPF (PSA) to SMF: N4 Session Modification Response. 8. SMF to Target I-SMF: In the case of I-SMF change, Nsmf_PDUSession_Update Response. In the case of I-SMF insertion, Nsmf_PDUSession_Create Response. The SMF provides the DNAI(s) of interest for this PDU Session to Target I-SMF. In the case of I-SMF insertion and the PDU session corresponds to a LADN, the SMF shall release the PDU session after the handover procedure is completed. 9. Target I-SMF to T-AMF: Nsmf_PDUSession_UpdateSMContext Response. If indirect data forwarding applies, the Target I-SMF starts an indirect data forwarding timer, to be used to release the resource of indirect data forwarding tunnel. Case: I-SMF removal, step 10~14 are skipped for I-SMF insertion, or I-SMF change case. 10. T-AMF to SMF: Nsmf_PDUSession_UpdateSMContext Request (Handover Complete indication, (N2 SM Information (Secondary RAT usage data))). Handover Complete indication is sent per each PDU Session to the corresponding SMF to indicate the success of the N2 Handover. If in step 6b of clause 4.9.1.3.3 the source AMF has provided information for secondary RAT usage reporting the T-AMF propagates this information to the SMF. 11a. S-AMF to Source I-SMF: Nsmf_PDUSession_ReleaseSMContext Request I-SMF only indication. After received N2 handover notify from T-AMF, if indication of I-SMF change/removal has been received, the S-AMF invokes Nsmf_PDUSession_ReleaseSMContext Request to inform the Source I-SMF to release the SM context of the PDU Session. I-SMF only indication is used to inform the Source I-SMF not to invoke resource release in SMF. The Source I-SMF initiates a timer to release the SM Context of the PDU Session if indirect forwarding tunnel(s) were previously established, otherwise, the Source I-SMF immediately releases the SM Context. 11b. Source I-SMF to S-AMF: Nsmf_PDUSession_ReleaseSMContext Response. 12a. [Conditional]SMF to Target I-UPF: N4 Session Modification Request. If the Target I-UPF is selected by SMF, the SMF to Target I-UPF: N4 Session Modification Request. The N4 Modification Request indicates DL AN Tunnel Info of T-RAN to Target I-UPF. 12b. [Conditional] Target I-UPF to SMF: N4 Session Modification Response 13a. SMF to UPF (PSA): N4 Session Modification Request. The SMF sends N4 Session Modification Request to UPF(PSA). The N4 Modification Request indicates DL AN Tunnel Info of T-RAN to UPF(PSA) if Target I-UPF is not selected by SMF. The N4 Modification Request indicates DL CN Tunnel Info of Target I-UPF if Target I-UPF is selected by SMF. 13b. UPF (PSA) to SMF: N4 Session Modification Response. PDU Session Anchor sends one or more "end marker" packets for each N3/N9 tunnel on the old path immediately after switching the path, the source NG-RAN shall forward the "end marker" packets to the target NG-RAN. 14. SMF to T-AMF: Nsmf_PDUSession_UpdateSMContext Response (PDU Session ID). If indirect data forwarding applies, the SMF starts an indirect data forwarding timer, to be used to release the resource of indirect data forwarding tunnel. 15. Steps 12, 14 in clause 4.9.1.3.3 are performed. During the UE mobility registration procedure, if required, the T-AMF performs I-SMF insertion/change/removal for the PDU session which were not handed over, i.e. the PDU sessions without active UP connections. This takes place as described in clause 4.23.3 with the exception that there is no UE context retrieved from the old AMF and that steps 17a and 17b as described in clause 4.23.4.3 are not applicable. Case: I-SMF insertion, or I-SMF change, step 16~18 are skipped for I-SMF removal case. 16a. [Conditional]Target I-SMF to Target I-UPF: N4 Session Modification Request. After indirect data forwarding timer set in step 9 expires, the Target I-SMF sends an N4 Session Modification Request to Target I-UPF to release the indirect data forwarding resource in Target I-UPF. 16b. [Conditional]Target I-UPF to SMF: N4 Session Modification Response. Case: I-SMF change, step 17 is skipped for I-SMF insertion. 17a. Source I-SMF to Source I-UPF: N4 Session Release Request. Upon the timer set in step 3 expires, the Source I-SMF sends N4 Session Release Request (Release Cause) to Source I-UPF to release the resources for the PDU Session. This message is also used to release the indirect data forwarding resource in Source I-UPF. If the Source I-UPF acts as UL CL and is not co-located with local PSA, the Source I-SMF also sends N4 Session Release Request to the local PSA to release the resources for the PDU Session. 17b. Source I-UPF to Source I-SMF: N4 Session Release Response. The Source I-SMF releases SM Context of the PDU Session. Case: I-SMF insertion, step 18 is skipped for I-SMF change. 18a. SMF to UPF: N4 Session Modification Request. Upon the timer set in step 6 expires, if UPF(PSA) is used for indirect forwarding, the SMF sends an N4 Session Modification Request to UPF(PSA) to release the indirect data forwarding resource in UPF(PSA). If the UPF (PSA) uses different Tunnel Info for N3 and N9, this message is also used to release the N3 Tunnel. If I-UPF is used for indirect forwarding, the SMF sends an N4 Session Modification Request to the I-UPF to release the indirect data forwarding resource. 18b. UPF to SMF: N4 Session Modification Response. If UPF(PSA) is used for indirect forwarding, the UPF (PSA) sends N4 Session Modification Response to SMF. If I-UPF is used for indirect forwarding, the I-UPF sends N4 Session Modification Response to SMF. Case: I-SMF removal, step 19~20 are skipped for I-SMF insertion, I-SMF change case. 19a. The Source I-SMF to Source I-UPF: N4 Session Release Request. Upon the timer set in step 11 expires, the Source I-SMF sends N4 Session Release Request (Release Cause) to Source I-UPF to release the resources for the PDU Session. This message is also used to release the indirect data forwarding resource in Source I-UPF. 19b. Source I-UPF to Source I-SMF: N4 Session Release Response. The Source I-SMF releases SM Context of the PDU Session. 20a. SMF to UPF: N4 Session Modification Request. Upon the timer set in step 14 expires, if UPF(PSA) is used for indirect forwarding, the SMF sends an N4 Session Modification Request to UPF (PSA) to release the indirect forwarding resource in UPF (PSA). If the UPF (PSA) uses different Tunnel Info for N3 and N9, this message is also used to release the N3 Tunnel. If I-UPF is used for indirect forwarding, the SMF sends an N4 Session Modification Request to the I-UPF to release the indirect data forwarding resource. 20b. UPF to SMF: N4 Session Modification Response. If UPF(PSA) is used for indirect forwarding, the UPF (PSA) sends N4 Session Modification Response to SMF. If I-UPF is used for indirect forwarding, the I-UPF sends N4 Session Modification Response to SMF. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.23.7.3.3 |
1,224 | 6.3 UE power headroom related measurements | a) This measurement provides a bin distribution (histogram) of the periodical E-UTRAN UE power headroom measurements received from all of UEs in the measured E-UTRAN cell. To collect this measurement, the eNodeB needs to trigger the periodical UE measurement reports towards all of the UEs in the measured E-UTRAN cell. b) CC c) Receipt by the eNodeB from the UE of Power Headroom Report message indicating a periodical UE measurement POWER_HEADROOM report. This measurement shall be increased for each reported value POWER_HEADROOM (See in 3GPP TS 36.321[ Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification ] [16]). For every one POWER_HEADROOM (s) a separate measurement is defined. (See in 3GPP TS 36.133[ Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for support of radio resource management ] [19]). d) Each measurement is an integer value. e) MR.PowerHeadRoom.y . y is an integer from 00 to 63. Note: 00 of y indicates POWER_HEADROOM_00, namely -23 PH -22, 01 of y indicates POWER_HEADROOM_01, namely -22 PH -21, … 63 of y indicates POWER_HEADROOM_63, namely PH≥40. (See in 3GPP TS36.133[ Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for support of radio resource management ] [19]) f) EUtranCellTDD EUtranCellFDD g) Valid for packet switched traffic. h) EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 6.3 |
1,225 | – PDSCH-ConfigBroadcast | The IE PDSCH-ConfigBroadcast is used to configure parameters for acquiring the PDSCH for MCCH and MTCH. PDSCH-ConfigBroadcast information element -- ASN1START -- TAG-PDSCH-CONFIGBROADCAST-START PDSCH-ConfigBroadcast-r17 ::= SEQUENCE { pdschConfigList-r17 SEQUENCE (SIZE (1..maxNrofPDSCH-ConfigPTM-r17) ) OF PDSCH-ConfigPTM-r17, pdsch-TimeDomainAllocationList-r17 PDSCH-TimeDomainResourceAllocationList-r16 OPTIONAL, -- Need R rateMatchPatternToAddModList-r17 SEQUENCE (SIZE (1..maxNrofRateMatchPatterns)) OF RateMatchPattern OPTIONAL, -- Need R lte-CRS-ToMatchAround-r17 RateMatchPatternLTE-CRS OPTIONAL, -- Need R mcs-Table-r17 ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need S xOverhead-r17 ENUMERATED {xOh6, xOh12, xOh18} OPTIONAL -- Need S } PDSCH-ConfigPTM-r17 ::= SEQUENCE { dataScramblingIdentityPDSCH-r17 INTEGER (0..1023) OPTIONAL, -- Need S dmrs-ScramblingID0-r17 INTEGER (0..65535) OPTIONAL, -- Need S pdsch-AggregationFactor-r17 ENUMERATED {n2, n4, n8} OPTIONAL -- Need S } -- TAG-PDSCH-CONFIGBROADCAST-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
1,226 | 5.5.2 Detach procedure 5.5.2.1 General | The detach procedure is used: - by the UE to detach for EPS services only; - by the UE to disconnect from the last remaining PDN it is connected to if EMM-REGISTERED without PDN connection is not supported by the UE or the MME; - by the UE in CS/PS mode 1 or CS/PS mode 2 of operation to detach for both EPS services and non-EPS services or for non-EPS services only via a combined detach procedure; - by the network to inform the UE that it is detached for EPS services or non-EPS services or both; - by the network to disconnect the UE from the last remaining PDN to which it is connected if EMM-REGISTERED without PDN connection is not supported by the UE or the MME; and - by the network to inform the UE to re-attach to the network and re-establish all PDN connections. NOTE 1: After a successful completion of an inter-system change of the UE from S1 mode to non-3GPP access, if the non-3GPP network provides PDN connectivity to the same EPC and EMM-REGISTERED without PDN connection is not supported by the UE or the MME, the MME performs a local detach of the UE. NOTE 2: If EMM-REGISTERED without PDN connection is supported by the UE and the MME, the detach procedure is not triggered when disconnecting the UE from the last remaining PDN to which it is connected. The detach procedure also applies to the UE which is IMSI attached for "SMS only". The detach procedure with appropriate detach type shall be invoked by the UE if the UE is switched off, the USIM card is removed from the UE, the UE wishes to detach for EPS services, the UE wishes to detach for non-EPS services or as part of the eCall inactivity procedure defined in clause 5.5.4. If the detach procedure is triggered due to USIM removal, the UE shall indicate "switch off" in the detach type IE. When upper layers indicate that emergency bearer services are no longer required, the UE if still attached for emergency bearer services, may perform a detach followed by a re-attach to regain normal services, if the UE is in or moves to a suitable cell. If a detach is requested by the HSS for a UE that has bearers for emergency services, the MME shall not send a DETACH REQUEST message to the UE, and shall follow the procedures in clause 6.4.4.1 for a UE that has bearers for emergency services. If the detach procedure for EPS services is performed, the EPS bearer context(s), if any, for this particular UE are deactivated locally without peer-to-peer signalling between the UE and the MME. If the UE supports A/Gb mode or Iu mode or both, the UE shall store the TIN in the non-volatile memory in the ME, as described in annex C, for a subsequent attach procedure. The UE is allowed to initiate the detach procedure even if the timer T3346 is running. The network proceeds with the detach procedure even if NAS level mobility management congestion control is active. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.2 |
1,227 | 5.7.1.7 UL Traffic | Following characteristics apply for processing of UL traffic: - UE uses the stored QoS rules to determine mapping between UL User Plane traffic and QoS Flows. UE marks the UL PDU with the QFI of the QoS rule containing the matching Packet Filter and transmits the UL PDUs using the corresponding access specific resource for the QoS Flow based on the mapping provided by (R)AN. For NG-RAN, the UL behaviour is specified in clause 10.5.2 of TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27]. - (R)AN transmits the PDUs over N3 tunnel towards UPF. When passing an UL packet from (R)AN to CN, the (R)AN includes the QFI value, in the encapsulation header of the UL PDU, and selects the N3 tunnel. - (R)AN performs transport level packet marking in the UL on a per QoS Flow basis with a transport level packet marking value that is determined based on the 5QI, the Priority Level (if explicitly signalled) and the ARP priority level of the associated QoS Flow. - UPF verifies whether QFIs in the UL PDUs are aligned with the QoS Rules provided to the UE or implicitly derived by the UE in the case of Reflective QoS). - UPF and UE perform Session-AMBR enforcement as specified in clause 5.7.1.8 and the UPF performs counting of packets for charging. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.7.1.7 |
1,228 | 10.6 Activation/Deactivation Mechanism | To enable reasonable UE battery consumption when CA is configured, an activation/deactivation mechanism of Cells is supported. When an SCell is deactivated, the UE does not need to receive the corresponding PDCCH or PDSCH, cannot transmit in the corresponding uplink, nor is it required to perform CQI measurements. Conversely, when an SCell is active, the UE shall receive PDSCH and PDCCH (if the UE is configured to monitor PDCCH from this SCell) and is expected to be able to perform CQI measurements. NG-RAN ensures that while PUCCH SCell (a Secondary Cell configured with PUCCH) is deactivated, SCells of secondary PUCCH group (a group of SCells whose PUCCH signalling is associated with the PUCCH on the PUCCH SCell) should not be activated. NG-RAN ensures that SCells mapped to PUCCH SCell are deactivated before the PUCCH SCell is changed or removed. When reconfiguring the set of serving cells: - SCells added to the set are initially activated or deactivated; - SCells which remain in the set (either unchanged or reconfigured) do not change their activation status (activated or deactivated). At handover, LTM cell switch execution or connection resume from RRC_INACTIVE: - SCells are activated or deactivated. To enable reasonable UE battery consumption when BA is configured, only one UL BWP for each uplink carrier and one DL BWP or only one DL/UL BWP pair can be active at a time in an active serving cell, all other BWPs that the UE is configured with being deactivated. On deactivated BWPs, the UE does not monitor the PDCCH, does not transmit on PUCCH, PRACH and UL-SCH. To enable fast SCell activation when CA is configured, one dormant BWP can be configured for an SCell. If the active BWP of the activated SCell is a dormant BWP, the UE stops monitoring PDCCH and transmitting SRS/PUSCH/PUCCH on the SCell but continues performing CSI measurements, AGC and beam management, if configured. A DCI is used to control entering/leaving the dormant BWP for one or more SCell(s) or one or more SCell group(s). The dormant BWP is one of the UE's dedicated BWPs configured by network via dedicated RRC signalling. The SpCell and PUCCH SCell cannot be configured with a dormant BWP. To enable fast SCell activation when CA is configured, aperiodic CSI-RS for tracking for fast SCell activation can be configured for an SCell to assist AGC and time/frequency synchronization. A MAC CE is used to trigger activation of one or more SCell(s) and trigger the aperiodic CSI-RS for tracking for fast SCell activation for a (set of) deactivated SCell(s). | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 10.6 |
1,229 | 9.3.24 Start DTMF | This message is sent by the mobile station to the network and contains the digit the network should reconvert back into a DTMF tone which is then applied towards the remote user. See table 9.71/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Message type: START DTMF Significance: local Direction: mobile station to network Table 9.71/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : START DTMF message content | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.3.24 |
1,230 | 10.5.4.9 Calling party BCD number | The purpose of the calling party BCD number information element is to identify the origin of a call. The calling party BCD number information element is coded as shown in figure 10.5.93/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.120/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The calling party BCD number is a type 4 information element. In the network to mobile station direction it has a minimum length of 3 octets and a maximum length of 14 octets. (This information element is not used in the mobile station to network direction.). Figure 10.5.93/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Calling party BCD number information element The contents of octets 3, 4, etc. are coded as shown in table 10.5.118. The coding of octet 3a is defined in table 10.5.120 below. If the calling party BCD number contains an odd number of digits, bits 5 to 8 of the last octet shall be filled with an end mark coded as "1111". Table 10.5.120/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Calling party BCD number | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.4.9 |
1,231 | 8.7.1 FDD (single carrier and CA) | The parameters specified in Table 8.7.1-1 are valid for all FDD tests unless otherwise stated. Table 8.7.1-1: Common Test Parameters (FDD) For UE not supporting 256QAM, the requirements are specified in Table 8.7.1-3, with the addition of the parameters in Table 8.7.1-2 and the downlink physical channel setup according to Annex C.3.2. The test points are applied to UE category and bandwidth combination with maximum aggregated bandwidth as specified inTable 8.7.1-4. The TB success rate shall be sustained during at least 300 frames. For UE supporting 256QAM, the requirements are specified in Table 8.7.1-6, with the addition of the parameters in Table 8.7.1-5 and the downlink physical channel setup according to Annex C.3.2. The test points are applied to UE category and bandwidth combination with maximum aggregated bandwidth as specified in Table 8.7.1-7, the TB success rate shall be sustained during at least 300 frames. For UE supporting 256QAM, the requirement in Table 8.7.1-3 is not applicable. For UE supporting 256QAM and category 9/10 and category 13, the requirements are specified in both Table 8.7.1-3 and Table 8.7.1-6, with the addition of the parameters in Table 8.7.1-2 and in Table 8.7.1-5 respectivly. The downlink physical channel setup according to Annex C.3.2. The test points are applied to UE category and bandwidth combination with maximum aggregated bandwidth as specified inTable 8.7.1-4 and in Table 8.7.1-7 for the category 9/10 and category 13, the TB success rate shall be sustained during at least 300 frames. The test coverage for different number of component carriers is defined in 8.1.2.4. Table 8.7.1-2: test parameters for sustained downlink data rate (FDD 64QAM) Table 8.7.1-3: Minimum requirement (FDD 64QAM) Table 8.7.1-4: Test points for sustained data rate (FRC 64QAM) Table 8.7.1-5: test parameters for sustained downlink data rate (FDD 256QAM) Table 8.7.1-6: Minimum requirement (FDD 256QAM) Table 8.7.1-7: Test points for sustained data rate (FRC 256QAM) | 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.7.1 |
1,232 | 4.11.4.3.6 Use of N10 interface instead of S6b | This clause applies to scnearios when ePDG is connected to SMF+PGW-C and S6b in not used. It is applicable for procedures specified in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [26] including mobility between EPC/ePDG and EPC/EUTRAN and also for mobility between EPC/ePDG and 5GS. When S6b, as specified in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [26], is not deployed between SMF+PGW-C and AAA and the UE creates and deletes a PDN connection via ePDG connected to SMF+PGW-C, the registration and de-registration of PDN GW is performed on the N10 interface instead of the S6b interface. If SMF+PGW-C is selected for a UE that does not support 5GC NAS, the SMF+PGW-C determines the PDU Session ID and S-NSSAI in the same way as for PDN connection via EPC/EUTRAN as specified in clause 4.11.0a.5. For roaming scenario with local-breakout (TS 23.501[ System architecture for the 5G System (5GS) ] [2], Figure 4.3.4.2.1), the use of N10 interface instead of S6b interface may be based on support of this feature from HSS+UDM to SMF+PGW-C on N10 interface. The specific impacts to procedures in clauses 7 and 8 of TS 23.402[ Architecture enhancements for non-3GPP accesses ] [26] are as follows: 7.2.4 Initial Attach with GTP on S2b - Instead of Step C.1 in Figure 7.2.4-1 of TS 23.402[ Architecture enhancements for non-3GPP accesses ] [26], step 16c (Nudm_UECM_Registration with an optional indication that access is from ePDG) from Figure 4.3.2.2.1-1 are performed between the SMF+PGW-C and HSS+UDM. Based on this indication, the HSS+UDM does not send notification of PGW-C assignment on SWx to AAA. 7.2.5 Initial Attach for emergency session (GTP on S2b) - Instead of step 5 in Figure 7.2.5-1 of TS 23.402[ Architecture enhancements for non-3GPP accesses ] [26], step 16c (Nudm_UECM_Registration with an optional indication that access is from ePDG) from Figure 4.3.2.2.1-1 are performed between the SMF+PGW-C and HSS+UDM. Based on this indication, the HSS+UDM does not send notification of PGW-C assignment on SWx to AAA. The indication of access from ePDG is forwarded on the interface between UDM and HSS. 7.4.3 UE/ePDG-initiated Detach Procedure and UE-Requested PDN Disconnection with GTP on S2b 7.4.3.1 Non-Roaming, Home Routed Roaming and Local Breakout Case - Instead of Step A.2 in Figure 7.4.3-1 of TS 23.402[ Architecture enhancements for non-3GPP accesses ] [26], step 12 (Nudm_UECM_Deregistration) from Figure 4.3.4.2-1 is performed between the SMF+PGW-C and HSS+UDM. 7.4.4 HSS/AAA-initiated Detach Procedure with GTP on S2b 7.4.4.1 Non-Roaming, Home Routed Roaming and Local Breakout Case - Instead of step 3 in Figure 7.4.1-1 of TS 23.402[ Architecture enhancements for non-3GPP accesses ] [26] (referenced by Figure 7.4.4-1 of TS 23.402[ Architecture enhancements for non-3GPP accesses ] [26]), Step 12 (Nudm_UECM_Deregistration) from Figure 4.3.4.2-1 is performed between the SMF+PGW-C and HSS+UDM 7.9.2 PDN GW initiated Resource Allocation Deactivation with GTP on S2b - Instead of step 5 in Figure 7.9.2-1 of TS 23.402[ Architecture enhancements for non-3GPP accesses ] [26], Step 12 (Nudm_UECM_Deregistration) from Figure 4.3.4.2-1 is performed between the SMF+PGW-C and HSS+UDM. 8.6.1.1 General Procedure for GTP based S5/S8 for E-UTRAN Access - Step 18 of clause 8.6.1.1 of TS 23.402[ Architecture enhancements for non-3GPP accesses ] [26] refers to clause 7.9.2 of TS 23.402[ Architecture enhancements for non-3GPP accesses ] [26]. The Nudm_UECM_Deregistration in the impacted referenced clause 7.9.2 above is not performed as resources in the SMF+PGW-C are not released. 8.6.2.1 3GPP Access to Untrusted Non-3GPP IP Access Handover with GTP on S2b - In Step B.2 of clause 8.6.2.1 of TS 23.402[ Architecture enhancements for non-3GPP accesses ] [26], if the registration of the SMF+PGW-C in the HSS+UDM is not already done, step 16c (Nudm_UECM_Registration with an optional indication that access is from ePDG) from Figure 4.3.2.2.1-1 is performed between the SMF+PGW-C and HSS+UDM. The impacts to procedure in clause 4.11.4.1 (Handover from EPC/ePDG to 5GS) are as follows: - For step 0, the impacts to clause 7.2.4 of TS 23.402[ Architecture enhancements for non-3GPP accesses ] [26] are captured above. - In step 2, if the Request Type indicates "Existing Emergency PDU Session", the AMF shall use the Emergency Information containing SMF+PGW-C FQDN for the S2b interface and the S NSSAI locally configured in Emergency Configuration Data. - In step 3, the impacts to clause 7.9.2 of TS 23.402[ Architecture enhancements for non-3GPP accesses ] [26] are captured above. Nudm_UECM_Deregistration is not performed by SMF+PGW-C, as resources in the SMF+PGW-C are not released. The impacts to procedures in clause 4.11.4.2 (Handover from 5GS to EPC/ePDG) are as follows: - For step 2, impacts to clause 8.6.2.1 (3GPP Access to Untrusted Non-3GPP IP Access Handover with GTP on S2b) of TS 23.402[ Architecture enhancements for non-3GPP accesses ] [26] are captured above and Step 16c of Figure 4.3.2.2.1-1 is not performed as SMF+PGW-C already registered in the HSS+UDM when the UE is in 5GS. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.11.4.3.6 |
1,233 | 5.32.5.2a Packet Loss Rate Measurements | The UE and the UPF may decide to estimate the Packet Loss Rate (PLR) for an SDF over both accesses. For example, the UE may take this decision when an ATSSS rule in the UE requires the traffic of an SDF to be steered in accordance with a PLR-based threshold condition (e.g. PLR < 2%). The UE and the UPF calculate the PLR for an SDF by exchanging PMF-PLR Report messages, as specified below. A PMF-PLR Report message is sent over 3GPP access or over non-3GPP access, using either the QoS Flow associated with the default QoS rule or a "target" QoS Flow, as specified in clause 5.32.5.1. The calculation of the PLR by the UE and by the UPF is based on the following mechanism. It is assumed that the PLR should be calculated for a target QoS Flow, however, the same mechanism applies when the PLR should be calculated for the QoS Flow associated with the default QoS rule. - The UE requests from UPF to start counting the number of received UL packets by sending a PMF-PLR Count Request message over the target QoS Flow. The UPF starts counting of the received UL packets over the target QoS Flow and over the access network which the PMF-PLR Count Request message was received from. The UE starts counting the transmitted UL packets over the target QoS Flow and access network when it sends a PMF-PLR Count Request message to UPF. - The UE stops the counting and requests from UPF to report the number of counted UL packets by sending a PMF-PLR Report Request message over the target QoS Flow. The UPF stops the counting and sends a PMF-PLR Report Response message over the QoS Flow including the number of UL packets counted since it received the last PMF-PLR Count Request message. NOTE 1: A PMF-PLR Report Request message can also indicate to UPF to start counting packets if the UE wants to measure the Packet Loss Rate again. - The UE calculates the UL packet loss ratio based on the local counting result of the number of transmitted UL packets and reported number of received UL packets in the UPF. - The UPF applies the same procedure for calculating the DL PLR, i.e. it sends to UE a PMF-PLR Count Request message on a target QoS Flow to request from UE to start counting the number of DL packets received on this target QoS Flow. As defined in clause 5.32.5.1, the UE determines which DL packets are received on the target QoS Flow by checking the QFI included in the header of DL packets (e.g. in the SDAP header). If no QFI is included in the header of a DL packet, the UE determines the QFI for this DL packet by applying the Packet Filters for downlink in the QoS Rules received from SMF. - When the UP connection of the MA PDU session is deactivated on an access, no PMF-PLR messages are sent on this access. The PMF in the UPF shall not send PMF-PLR message on this access if the UP connection is not available or after it receives notification from the (H-)SMF to stop sending the PMF-PLR message on this access. - The UE and the UPF derive an estimation of the average PLR per QoS Flow over an access type by averaging the PLR measurements obtained over this access. NOTE 2: The details of the packet loss measurements, including error cases and mechanisms for improving the measurement accuracy, are considered in the Stage 3 specifications. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.32.5.2a |
1,234 | 4.4.10 DeNB | DeNB function is described in more detail in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]. DeNB provides the necessary S/P-GW functions for the operation of RNs connected to the DeNB. In order to provide the Relay Function the DeNB shall support the following P-GW functions: - IP address allocation for the UE functionality of the RN; - Downlink transport level packet mapping between the DSCP value used over S1-U of the UE (which is the SGi interface of the PDN GW function in the DeNB) and the EPS bearers with an appropriate QCI value and optionally ARP priority level value, established between the PDN GW function in the DeNB and the UE function of the RN; - Uplink transport level packet mapping between QCI value and optionally ARP priority level value, of the EPS bearers (established between the PDN GW function in the DeNB and the UE function of the RN) and the DSCP value used over S1-U of the UE (which is the SGi interface of the PDN GW function in the DeNB). In order to provide the Relay Function the DeNB shall support the following S-GW functions: - Termination the S11 session of the MME(RN). S-GW functions related to ECM-IDLE are not required. S-GW functions related to mobility management are not supported. | 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.4.10 |
1,235 | 5.1 Waveform, numerology and frame structure | The downlink transmission waveform is conventional OFDM using a Cyclic Prefix. The uplink transmission waveform is conventional OFDM using a CP with a transform precoding function performing DFT spreading that can be disabled or enabled. For operation with shared spectrum channel access in FR1, the uplink transmission waveform subcarrier mapping can map to subcarriers in one or more PRB interlaces. Figure 5.1-1: Transmitter block diagram for CP-OFDM with optional DFT-spreading The numerology is based on exponentially scalable sub-carrier spacing f = 2µ × 15 kHz with µ={0,1,3,4,5,6} for PSS, SSS and PBCH and µ={0,1,2,3,5,6} for other channels. Normal CP is supported for all sub-carrier spacings, Extended CP is supported for µ=2. 12 consecutive sub-carriers form a Physical Resource Block (PRB). Up to 275 PRBs are supported on a carrier. Table 5.1-1: Supported transmission numerologies. The UE may be configured with one or more bandwidth parts on a given component carrier, of which only one can be active at a time, as described in clauses 7.8 and 6.10 respectively. The active bandwidth part defines the UE's operating bandwidth within the cell's operating bandwidth. For initial access, and until the UE's configuration in a cell is received, initial bandwidth part detected from system information is used. Downlink and uplink transmissions are organized into frames with 10 ms duration, consisting of ten 1 ms subframes. Each frame is divided into two equally-sized half-frames of five subframes each. The slot duration is 14 symbols with Normal CP and 12 symbols with Extended CP, and scales in time as a function of the used sub-carrier spacing so that there is always an integer number of slots in a subframe. Timing Advance TA is used to adjust the uplink frame timing relative to the downlink frame timing. Figure 5.1-2: Uplink-downlink timing relation Operation on both paired and unpaired spectrum is supported. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.1 |
1,236 | 5.28.4 QoS mapping tables for TSN | The mapping tables between the traffic class and 5GS QoS Profile is provisioned and further used to find suitable 5GS QoS profile to transfer TSN traffic over the PDU Session. QoS mapping procedures are performed in two phases: (1) QoS capability report phase as described in clause 5.28.1, and (2) QoS configuration phase as in clause 5.28.2 (1) The TSN AF shall be pre-configured (e.g. via OAM) with a mapping table. The mapping table contains TSN traffic classes, pre-configured bridge delays (i.e. the preconfigured delay between UE and UPF/NW-TT) and priority levels. Once the PDU session has been setup and after retrieving the information related to UE-DS-TT residence time, the TSN AF deduces the port pair(s) in the 5GS bridge and determines the bridge delay per port pair per traffic class based on the pre-configured bridge delay and the UE-DS-TT residence time as described in clause 5.27.5. The TSN AF updates bridge delays per port pair and traffic class and reports the bridge delays and other relevant TSN information such as the Traffic Class Table (clause 12.6.3 in IEEE Std 802.1Q [98]) for every port, according to the IEEE Std 802.1Q [98] to the CNC. (2) CNC may distribute PSFP information and transmission gate scheduling parameters to 5GS Bridge via TSN AF, which can be mapped to TSN QoS requirements by the TSN AF. The PCF mapping table provides a mapping from TSN QoS information (see clauses 6.2.1.2 and 6.1.3.23 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]) to 5GS QoS profile. Based on trigger from TSN AF, the PCF may trigger PDU session modification procedure to establish a new 5G QoS Flow or use the pre-configured 5QI for 5G QoS Flow for the requested traffic class according to the selected QoS policies and the TSN AF traffic requirements. Figure 5.28.4-1 illustrates the functional distribution of the mapping tables. Figure 5.28.4-1: QoS Mapping Function distribution between PCF and TSN AF The minimum set of TSN QoS-related parameters that are relevant for mapping the TSN QoS requirements are used by the TSN AF: traffic classes and their priorities per port, TSC Burst Size of TSN streams, 5GS bridge delays per port pair and traffic class (independentDelayMax, independentDelayMin, dependentDelayMax, dependentDelayMin), propagation delay per port (txPropagationDelay) and UE-DS-TT residence time. Once the CNC retrieves the necessary information, it proceeds to calculate scheduling and paths. The configuration information is then set in the bridge as described in clauses 5.28.2 and 5.28.3. The most relevant information received is the PSFP information and the schedule of transmission gates for every traffic class and port of the bridge. At this point, it is possible to retrieve the TSN QoS requirements by identifying the traffic class of the TSN stream. The traffic class to TSN QoS and delay requirement (excluding the UE-DS-TT residence time) mapping can be performed using the QoS mapping table in the TSN AF as specified in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. Subsequently in the PCF, the 5G QoS Flow can be configured by selecting a 5QI as specified in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. This feedback approach uses the reported information to the CNC and the feedback of the configuration information coming from the CNC to perform the mapping and configuration in the 5GS. If the Maximum Burst Size of the aggregated TSC streams in the traffic class is provided by CNC via TSN AF to PCF, PCF can derive the required MDBV taking the Maximum Burst Size as input. If the default MDBV associated with a standardized 5QI or a pre-configured 5QI in the QoS mapping table cannot satisfy the aggregated TSC Burst Size, the PCF provides the derived MDBV in the PCC rule and then the SMF performs QoS Flow binding as specified in clause 6.1.3.2.4 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. Maximum Flow Bit Rate is calculated over StreamGateAdminCycleTime as described in Annex I and provided by the TSN AF to the PCF. The PCF sets the GBR and MBR values to the Maximum Flow Bitrate value. The Maximum Flow Bit Rate is adjusted according to Averaging Window associated with a pre-configured 5QI in the QoS mapping table or another selected 5QI (as specified in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]) to obtain GBR of the 5GS QoS profile. GBR is then used by SMF to calculate the GFBR per QoS Flow. QoS mapping table in the PCF between TSN parameters and 5GS parameters should match the delay, aggregated TSC burst size and priority, while preserving the priorities in the 5GS. An operator enabling TSN services via 5GS can choose up to eight traffic classes to be mapped to 5GS QoS profiles. Once the 5QIs to be used for TSN streams are identified by the PCF as specified in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45], then it is possible to enumerate as many bridge port traffic classes as the number of selected 5QIs. When PSFP information is not available to the TSN AF for a given TSN stream (e.g. because of lack of PSFP support in the DS-TTs or the NW-TTs, or exceeding the number of supported table entries for PSFP functions, or because CNC does not provide PSFP information), the 5GS can support the TSN streams using pre-configured mapping from stream priority (i.e. PCP as defined in IEEE Std 802.1Q [98]) to QoS Flows. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.28.4 |
1,237 | 4.2.3 Service Request procedures 4.2.3.1 General | The Service Request procedure is used by a UE in CM-IDLE state or the 5GC to request the establishment of a secure connection to an AMF. The Service Request procedure is also used both when the UE is in CM-IDLE and in CM-CONNECTED to activate a User Plane connection for an established PDU Session. The Service Request procedure is also used to release the connection to an AMF. For Home routed PDU sessions, by replacing the I-SMF with V-SMF and SMF with H-SMF the same procedure as defined in clause 4.23.4 is reused. The UE shall not initiate a Service Request procedure if there is an ongoing Service Request procedure. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2.3 |
1,238 | 10.5.5.23 Network feature support | The purpose of the network feature support information element is to indicate whether certain features are supported by the network. If this IE is not included then the respective features are not supported. The network feature support is a type 1 information element. The network feature support information element is coded as shown in figure 10.5.135c/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.153c/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.135c/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Network feature support information element Table 10.5.153c/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Network feature support information element | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.5.23 |
1,239 | 5.14.2.2.1 Sidelink HARQ Entity | For each carrier, there is one Sidelink HARQ Entity at the MAC entity for reception of the SL-SCH, which maintains a number of parallel Sidelink processes. Each Sidelink process is associated with SCI in which the MAC entity is interested. If SCI includes the Group Destination ID, this interest is as determined by the Group Destination ID of the SCI. The Sidelink HARQ Entity directs HARQ information and associated TBs received on the SL-SCH to the corresponding Sidelink processes. The number of Receiving Sidelink processes associated with the Sidelink HARQ Entity is defined in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]. For each subframe of the SL-SCH, the Sidelink HARQ Entity shall: - for each SCI valid in this subframe: - allocate the TB received from the physical layer and the associated HARQ information to a Sidelink process, associate this Sidelink process with this SCI and consider this transmission to be a new transmission. - for each Sidelink process: - if this subframe corresponds to retransmission opportunity for the Sidelink process according to its associated SCI: - allocate the TB received from the physical layer and the associated HARQ information to the Sidelink process and consider this transmission to be a retransmission. | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.14.2.2.1 |
1,240 | A.5 Guidelines regarding inclusion of transaction identifiers in RRC messages | The following rules provide guidance on which messages should include a Transaction identifier 1: DL messages on CCCH that move UE to RRC-Idle should not include the RRC transaction identifier. 2: All network initiated DL messages by default should include the RRC transaction identifier. 3: All UL messages that are direct response to a DL message with an RRC Transaction identifier should include the RRC Transaction identifier. 4: All UL messages that require a direct DL response message should include an RRC transaction identifier. 5: All UL messages that are not in response to a DL message nor require a corresponding response from the network should not include the RRC Transaction identifier. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | A.5 |
1,241 | 5.1.3.3 EPS update status | In order to describe the detailed UE behaviour, the EPS update (EU) status pertaining to a specific subscriber is defined. The EPS update status is stored in a non-volatile memory in the USIM if the corresponding file is present in the USIM, else in the non-volatile memory in the ME, as described in annex C. The EPS update status value is changed only after the execution of an attach or combined attach, network initiated detach, authentication, tracking area update or combined tracking area update, service request or paging for EPS services using IMSI procedure or due to change in TAI which is not part of TAI list while timer T3346 is running. EU1: UPDATED The last attach or tracking area updating attempt was successful. EU2: NOT UPDATED The last attach, service request or tracking area updating attempt failed procedurally, e.g. no response or reject message was received from the MME. EU3: ROAMING NOT ALLOWED The last attach, service request or tracking area updating attempt was correctly performed, but the answer from the MME was negative (because of roaming or subscription restrictions). | 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.1.3.3 |
1,242 | 5.17.7.1 Architecture Principles for Configuration Transfer between NG-RAN and E-UTRAN | The purpose of the Configuration Transfer between NG-RAN and E-UTRAN is to enable the transfer the RAN configuration information between the gNB and eNodeB via MME and AMF. In order to make the information transparent for the MME and AMF, the information is included in a transparent container. The source and target RAN node addresses, which allows the Core Network nodes to route the messages. The mechanism depicted in Figure 5.17.7.1-1. Figure 5.17.7.1-1: Configuration Transfer between gNB and E-UTRAN basic network architecture The NG-RAN transparent containers are transferred from the source NG-RAN node to the destination E-UTRAN node and vice versa by use of Configuration Transfer messages. An ENB Configuration Transfer message is used from the E-UTRAN node to the MME over S1 interface as described in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [100], the destination RAN node includes the en-gNB Identifier and may include a TAI associated with the en-gNB. If MME is aware that the en-gNB serves cells which provide access to 5GC, the MME relays the request towards a suitable AMF via inter-system signalling based on a broadcast 5G TAC. An AMF Configuration Transfer message is used from the AMF to the NG-RAN over N2 interface. A Configuration Transfer message is used by the gNB node to the AMF over N2 interface for the reply, and a Configuration Transfer Tunnel message is used to tunnel the transparent container from AMF to MME over the N26 interface. MME relays this reply to the target eNB using a MME CONFIGURATION TRANSFER message. Transport of the RAN containers in E-UTRAN is specified in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [26]. Each Configuration Transfer message carrying the transparent container is routed and relayed independently by the core network node(s). Any relation between messages is transparent for the AMF and MME, i.e. a request/response exchange between applications, for example SON applications, is routed and relayed as two independent messages by the AMF and MME. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.17.7.1 |
1,243 | 4.3.21.4 Wake Up Signal Assistance 4.3.21.4.1 General | The RAN and UE may use a Wake Up Signal (WUS) to reduce the UE's idle mode power consumption. The RAN sends the WUS shortly before the UE's paging occasion. The WUS feature enables UEs to determine that in the paging occasions immediately following their WUS occasion they will not be paged if their WUS is not transmitted, or that they might be paged if their WUS is transmitted (see TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [34]). To avoid waking up UEs due to an MME paging other UEs across multiple cells (e.g. due to frequent UE mobility and/or for low paging latency services such as VoLTE), the use of WUS by the eNodeB and the UE is restricted to the last used cell, i.e. the cell in which the UE's RRC connection was last released. To support this: a) WUS-capable eNodeBs should provide the Recommended Cells for Paging IE in the Information On Recommended Cells And eNodeBs For Paging IE (see TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36]) to the MME in the S1 UE Context Release Complete or UE Context Suspend Request messages; b) if received during the last S1 UE Context Release Complete or UE Context Suspend Request message, the MME provides (without modification) the Recommended Cells for Paging as Assistance Data for Recommended Cells IE in the S1-AP Paging message to the RAN (see also TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36]); and c) the MME shall delete (or mark as invalid) the Information On Recommended Cells And eNodeBs For Paging when a new S1-AP association is established for the UE. In the S1-AP Paging message, the last used cell ID is sent in the Assistance Data for Recommended Cells IE in the Assistance Data for Paging IE (see TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36]). When receiving an S1-AP Paging message for a WUS-capable UE that also includes the Assistance Data for Recommended Cells IE then a WUS-capable eNodeB shall only broadcast the WUS on the cell that matches the last used cell ID. | 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.21.4 |
1,244 | 5.3.5.6.7 Multicast MRB addition/modification | The UE shall for each element in the order of entry in the list mrb-ToAddModList: 1> if mrb-Identity value included in the mrb-ToAddModList is part of the UE configuration: 2> if mrb-Identity value included in the mrb-ToAddModList for which mrb-IdentityNew is included (i.e., multicast MRB ID change): 3> update the mrb-Identity to the value mrb-IdentityNew; 2> if the reestablishPDCP is set: 3> if drb-ContinueROHC is included in pdcp-Config: 4> indicate to lower layer that drb-ContinueROHC is configured; 3> if drb-ContinueEHC-DL is included in pdcp-Config: 4> indicate to lower layer that drb-ContinueEHC-DL is configured; 3> re-establish the PDCP entity of this multicast MRB as specified in TS 38.323[ NR; Packet Data Convergence Protocol (PDCP) specification ] [5], clause 5.1.2; 2> else, if the recoverPDCP is set: 3> trigger the PDCP entity of this MRB to perform data recovery as specified in TS 38.323[ NR; Packet Data Convergence Protocol (PDCP) specification ] [5]; 2> if the pdcp-Config is included: 3> reconfigure the PDCP entity in accordance with the received pdcp-Config; 1> else if mrb-Identity value included in the mrb-ToAddModList is not part of the UE configuration (i.e., multicast MRB establishment including the case when full configuration option is used): 2> establish a PDCP entity and configure it in accordance with the received pdcp-Config; 2> associate the established multicast MRB with the corresponding mbs-SessionId; 2> if an SDAP entity with the received mbs-SessionId does not exist: 3> establish an SDAP entity 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.1; 3> if an SDAP entity with the received mbs-SessionId did not exist prior to receiving this reconfiguration: 4> indicate the establishment of the user plane resources for the mbs-SessionId to upper layers. NOTE 1: When setting the reestablishPDCP flag for a radio bearer, the network ensures that the RLC receiver entities do not deliver old PDCP PDUs to the re-established PDCP entity. The network does that e.g. by triggering a reconfiguration with sync of the cell group hosting the old RLC entity or by releasing the old RLC entity. NOTE 2: In this specification, UE configuration refers to the parameters configured by NR RRC unless otherwise stated. NOTE 3: When updating the mrb-Identity, the network ensures new MRBs are listed at the end of the mrb-ToAddModList if they have the same MRB ID as in the existing UE configuration. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.5.6.7 |
1,245 | 5.5.2.11 Measurement gap sharing configuration | The UE shall: 1> if gapSharingFR1 is set to setup: 2> if an FR1 measurement gap sharing configuration configured by gapSharingFR1 is already setup: 3> release the FR1 measurement gap sharing configuration configured by gapSharingFR1; 2> setup the FR1 measurement gap sharing configuration indicated by the measGapSharingConfig in accordance with the received gapSharingFR1 as defined in TS 38.133[ NR; Requirements for support of radio resource management ] [14]; 1> else if gapSharingFR1 is set to release: 2> release the FR1 measurement gap sharing configuration configured by gapSharingFR1; 1> if gapSharingFR2 is set to setup: 2> if an FR2 measurement gap sharing configuration configured by gapSharingFR2 is already setup: 3> release the FR2 measurement gap sharing configuration configured by gapSharingFR2; 2> setup the FR2 measurement gap sharing configuration indicated by the measGapSharingConfig in accordance with the received gapSharingFR2 as defined in TS 38.133[ NR; Requirements for support of radio resource management ] [14]; 1> else if gapSharingFR2 is set to release: 2> release the FR2 measurement gap sharing configuration configured by gapSharingFR2. 1> if gapSharingUE is set to setup: 2> if a per UE measurement gap sharing configuration configured by gapSharingUE is already setup: 3> release the per UE measurement gap sharing configuration configured by gapSharingUE; 2> setup the per UE measurement gap sharing configuration indicated by the measGapSharingConfig in accordance with the received gapSharingUE as defined in TS 38.133[ NR; Requirements for support of radio resource management ] [14]; 1> else if gapSharingUE is set to release: 2> release the per UE measurement gap sharing configuration configured by gapSharingUE. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.5.2.11 |
1,246 | 5.5.4.5 UE-initiated authentication and key agreement procedure not accepted by the network | If the UE-initiated authentication and key agreement procedure is not accepted by the network, the AMF shall: a) create a RELAY KEY REJECT message; b) set the PRTI IE of the RELAY KEY REJECT message to the PRTI value of the received RELAY KEY REQUEST message if the network decides to reject the RELAY KEY REQUEST message; or NOTE: The network decides to reject the RELAY KEY REQUEST message when e.g. the CP-PRUK is not found in the network. set the PRTI IE of the RELAY KEY REJECT message to the PRTI value of the received RELAY AUTHENTICATION RESPONSE message and include the EAP message IE set with EAP-failure message if the AMF receives an EAP-failure message from the AUSF; and c) send the RELAY KEY REJECT message to the UE. Upon receiving the RELAY KEY REJECT message, the UE shall consider the authentication has failed and perform the PC5 signalling protocol procedure as specified in subclause 7.2.2.5 of 3GPP 24.554 [19E]. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.4.5 |
1,247 | 4.3.1 Cell Identity (CI) and Cell Global Identification (CGI) | The BSS and cell within the BSS are identified within a location area or routeing area by adding a Cell Identity (CI) to the location area or routeing area identification, as shown in figure 5. The CI is of fixed length with 2 octets and it can be coded using a full hexadecimal representation. The Cell Global Identification is the concatenation of the Location Area Identification and the Cell Identity. Cell Identity shall be unique within a location area. Figure 5: Structure of Cell Global Identification | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3.1 |
1,248 | 4.4.2.1.3 UE entering state 5GMM-DEREGISTERED | If the UE is capable of registration over a single access only, the UE shall store the current native 5G NAS security context on the USIM or in the non-volatile memory and mark it as valid only when the UE enters state 5GMM-DEREGISTERED from any other state except 5GMM-NULL or when the UE aborts the initial registration procedure without having left 5GMM-DEREGISTERED. If the UE is capable of registration over both 3GPP access and non-3GPP access and is registered on the same PLMN over both 3GPP access and the non-3GPP access, the UE shall store the current native 5G NAS security contexts of the 3GPP access and the non-3GPP access as specified in annex C and mark them as valid only when the UE enters state 5GMM-DEREGISTERED from any other state except 5GMM-NULL over both the 3GPP access and non-3GPP access or only when the UE aborts the initial registration procedure without having left 5GMM-DEREGISTERED over both the 3GPP access and non-3GPP access. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.4.2.1.3 |
1,249 | 4.1.1 Common MR-DC principles | Multi-Radio Dual Connectivity (MR-DC) is a generalization of the Intra-E-UTRA Dual Connectivity (DC) 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 ] [2], where a multiple Rx/Tx capable UE may be configured to utilise resources provided by two different nodes connected via non-ideal backhaul, one providing NR access and the other one providing either E-UTRA or NR access. One node acts as the MN and the other as the SN. The MN and SN are connected via a network interface and at least the MN is connected to the core network. The MN and/or the SN can be operated with shared spectrum channel access. All functions specified for a UE may be used for an IAB-MT unless otherwise stated. Similar as specified for UE, the IAB-MT can access the network using either one network node or using two different nodes with EN-DC and NR-DC architectures. In EN-DC, the backhauling traffic over the E-UTRA radio interface is not supported. NOTE 1: MR-DC is designed based on the assumption of non-ideal backhaul between the different nodes but can also be used in case of ideal backhaul. NOTE 2: All MR-DC normative text and procedures in this version of the specification show the aggregated node case. The details about non-aggregated node for MR-DC operation are described in TS 38.401[ NG-RAN; Architecture description ] [7]. | 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 | 4.1.1 |
1,250 | 6.38.1 Description | Personal IoT Networks (PINs) and Customer Premises Networks (CPNs) provide local connectivity between UEs and/or non-3GPP devices. The CPN via an eRG, or PIN Elements via a PIN Element with Gateway Capability can provide access to 5G network services for the UEs and/or non-3GPP devices on the CPN or PIN. CPNs and PINs have in common that in general they are owned, installed and/or (at least partially) configured by a customer of a public network operator. A Customer Premises Network (CPN) is a network located within a premises (e.g. a residence, office or shop). Via an evolved Residential Gateway (eRG), the CPN provides connectivity to the 5G network. The eRG can be connected to the 5G core network via wireline, wireless, or hybrid access. A Premises Radio Access Station (PRAS) is a base station installed in a CPN. Through the PRAS, UEs can get access to the CPN and/or 5G network services. The PRAS can be configured to use licensed, unlicensed, or both frequency bands. Connectivity between the eRG and the UE, non-3GPP Device, or PRAS can use any suitable non-3GPP technology (e.g. Ethernet, optical, WLAN). A Personal IoT Network (PIN) consists of PIN Elements that communicate using PIN Direct Connection or direct network connection and is managed locally (using a PIN Element with Management Capability). Examples of PINs include networks of wearables and smart home / smart office equipment. Via a PIN Element with Gateway Capability, PIN Elements have access to the 5G network services and can communicate with PIN Elements that are not within range to use PIN Direct Connection. A PIN includes at least one PIN Element with Gateway Capability and at least one PIN Element with Management Capability. A PIN Element with Management Capability is a PIN Element that provides a means for an authorised administrator to configure and manage a PIN. The requirements as described in 3GPP TS 22.101[ Service aspects; Service principles ] [6] clause 26a can also apply to Personal IoT Networks and Customer Premises Networks. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.38.1 |
1,251 | 10.10.2 MR-DC with 5GC | The RRC Transfer procedure is used to deliver an RRC message, encapsulated in a PDCP PDU between the MN and the SN (and vice versa) so that it may be forwarded to/from the UE using split SRB. The RRC transfer procedure is also used for: - providing a SN measurement report, failure information report, SN UE assistance information or intra-SN CPC execution completion from the UE to the SN. If UE is IAB-MT, providing NR IAB other information from the IAB-MT to the SN when the IAB-donor is the SN; - providing MCG failure information from the UE to the MN via the SN and an RRC reconfiguration, or release, or an inter-RAT handover command from the MN to the UE via the SN; - providing F1-C traffic from an IAB-node to the MN via the SN, or F1-C traffic from the MN to an IAB-node via the SN. Additional details of the RRC transfer procedure are defined in TS 38.423[ NG-RAN; Xn Application Protocol (XnAP) ] [5]. Split SRB: Figure 10.10.2-1: RRC Transfer procedure for split SRB (DL operation) Figure 10.10.2-1 shows an example signaling flow for DL RRC Transfer in case of the split SRB: 1. The MN, when it decides to use the split SRBs, starts the procedure by initiating the RRC Transfer procedure. The MN encapsulates the RRC message in a PDCP PDU and ciphers with own keys. NOTE: The usage of the split SRBs shall be indicated in the Secondary Node Addition procedure or Modification procedure. 2. The SN forwards the RRC message to the UE. 3. The SN may send PDCP delivery acknowledgement of the RRC message forwarded in step 2. Figure 10.10.2-2: RRC Transfer procedure for split SRB (UL operation) Figure 10.10.2-2 shows an example signaling flow for UL RRC Transfer in case of the split SRB: 1. When the UE provides response to the RRC message, it sends it to the SN. 2. The SN initiates the RRC Transfer procedure, in which it transfers the received PDCP PDU with encapsulated RRC message. SN measurement report, failure information report, SN UE assistance information, intra-SN CPC execution completion or IAB other information: Figure 10.10.2-3: RRC Transfer procedure for SN measurement report, failure information report, SN UE assistance information, intra-SN CPC execution completion or IAB other information Figure 10.10.2-3 shows an example signaling flow for RRC Transfer in case of the forwarding of the SN measurement report, failure information report, SN UE assistance information, intra-SN CPC execution completion or IAB other information from the UE: 1. When the UE sends an SN measurement report, failure information report, SN UE assistance information, intra-SN CPC execution completion or IAB other information it sends it to the MN in a container called ULInformationTransferMRDC message as specified in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [4]. 2. The MN initiates the RRC Transfer procedure, in which it transfers the received SN measurement report, failure information, SN UE assistance information, intra-SN CPC execution completion or IAB other information as an octet string. MCG failure information and RRC Reconfiguration / RRC Release / inter-RAT handover command over SRB3: Figure 10.10.2-4: RRC Transfer procedure for MCG failure information Figure 10.10.2-4 shows an example signaling flow for RRC Transfer in case of the forwarding of the MCG failure information from the UE: 1. When the UE sends MCGFailureInformation message over SRB3, it sends it to the SN in a container called ULInformationTransferMRDC message as specified in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [4]. 2. The SN initiates the RRC Transfer procedure, in which it transfers the received MCGFailureInformation message as an octet string. 3. The MN initiates the RRC Transfer procedure, in which it transfers the RRCConnectionReconfiguration message, or RRCReconfiguration message, or RRCConnectionRelease message, or RRCRelease message, or MobilityFromNRCommand message, or MobilityFromEUTRACommand message as an octet string. 4. The SN sends the received RRC message to the UE in a container called DLInformationTransferMRDC message, as specified in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [4]. F1-C traffic transfer: Figure 10.10.2-5: Scenario 2: F1-C Traffic Transfer procedure between IAB-MT and MN (F1-terminating node) in NR-DC 1. The IAB-MT sends a F1-AP message encapsulated in SCTP/IP or F1-C related (SCTP/)IP packet to the SN (non-F1-terminating IAB-donor) via split SRB2 in a container within ULInformationTransfer message encapsulated in a PDCP PDU as specified in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [4]. 2. The SN initiates the RRC Transfer procedure, in which it transfers the received PDCP PDU (ULInformationTransfer message) including F1-AP message. 3. When the MN (F1-terminating IAB-donor) sends a F1-AP message encapsulated in SCTP/IP or F1-C related (SCTP/)IP packet, it starts the procedure by initiating the RRC Transfer procedure, if split SRB2 is determined to be used and usage of SCG path is determined. The MN sends the F1-AP message to the SN in a container within DLInformationTransfer message encapsulated in a PDCP PDU specified in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [4]. 4. The SN forwards the encapsulated DLInformationTransfer message in a PDCP PDU as specified in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [4] to IAB-MT. | 3GPP TS 37.340 | Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 | RAN2 | 3GPP Series : 37 , Multiple radio access technology aspects | 10.10.2 |
1,252 | 7.3 Reference sensitivity power level | The reference sensitivity power level REFSENS is the minimum mean power applied to each one of the UE antenna ports for all UE categories except category 0, category M1, category M2, and category 1bis, or to the single antenna port for UE category 0, UE category M1, category M2, and UE category 1bis, at which the throughput shall meet or exceed the requirements for the specified reference measurement channel. The throughput for the REFSENS test is measured based on the Transmission Mode 1 unless specified otherwise. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 7.3 |
1,253 | 9.7.2.1 FDD and half-duplex FDD | For the parameters specified in Table 9.7.2.1-1, and using the downlink physical channels specified in Annex C.3.2, the minimum requirements are specified in Table 9.7.2.1-2 and by the following a) a sub-band differential CQI offset level of 0 shall be reported at least % of the time but less than % for each sub-band; b) the ratio of the throughput obtained when transmitting on a randomly selected sub-band among the sub-bands with the highest differential CQI offset level the corresponding TBS and that obtained when transmitting the TBS indicated by the reported wideband CQI median on a randomly selected sub-band in set S shall be ≥ ; c) when transmitting on a randomly selected sub-band among the sub-bands with the highest differential CQI offset level the corresponding TBS, the average BLER for the indicated transport formats shall be greater or equal to 0.05. The requirements only apply for sub-bands of full size and the random scheduling across the sub-bands is done by selecting a new sub-band in each TTI for FDD and in each available downlink transmission instance for half-duplex FDD. Table 9.7.2.1-1 Sub-band test for single antenna transmission (FDD and half-duplex FDD) Table 9.7.2.1-2 Minimum requirement (FDD and half-duplex FDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.7.2.1 |
1,254 | 12.3.5.3 Limit on maximum number of instances | A GTP-C entity may signal one or multiple instances of the OCI IE, each instance providing overload control information for a different scope. The receiver shall handle all these instances, from each of the peer GTP-C entities, by processing, storing and acting upon the same foroverload control. In order to limit the processing of the message on the receiver side and the size of the message, the number of overload control information instances shall be limited: - at message level: there shall be at most one instance of node-level Overload Control Information IE per node and at most 10 APN-level instances. - at node level: the maximum number of instances of the OCI IE which may be provided across multiple messages by a given node shall be the same as the maximum number of instances of the OCI IE at message level. | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 12.3.5.3 |
1,255 | 4.3.1.1.2 Successful outgoing intra-eNB/RN handovers per handover cause | This measurement provides the number of successful outgoing intra-eNB/RN handovers per handover cause. CC. Receipt of a RRC message RRCConnectionReconfigurationComplete sent from the UE to the target (=source) eNB/RN, indicating a successful outgoing intra-eNB/RN handover (see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]). Each RRCConnectionReconfigurationComplete message transimtted is added to the relevant per handover cause measurement, the possible causes are included in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [9]. The sum of all supported per cause measurements shall equal the total number of outgoing intra-eNB/RN handover events. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first. Each measurement is an integer value. The number of measurements is equal to the number of causes supported plus a possible sum value identified by the .sum suffix HO.IntraEnbOutSucc.Cause where Cause identifies the cause for handover. EUtranCellFDD EUtranCellTDD Valid for packet switched traffic EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.3.1.1.2 |
1,256 | – FrequencyInfoDL-SIB | The IE FrequencyInfoDL-SIB provides basic parameters of a downlink carrier and transmission thereon. FrequencyInfoDL-SIB information element -- ASN1START -- TAG-FREQUENCYINFODL-SIB-START FrequencyInfoDL-SIB ::= SEQUENCE { frequencyBandList MultiFrequencyBandListNR-SIB, offsetToPointA INTEGER (0..2199), scs-SpecificCarrierList SEQUENCE (SIZE (1..maxSCSs)) OF SCS-SpecificCarrier } FrequencyInfoDL-SIB-v1760 ::= SEQUENCE { frequencyBandList-v1760 MultiFrequencyBandListNR-SIB-v1760 } FrequencyInfoDL-SIB-v1800 ::= SEQUENCE { frequencyBandListAerial-r18 MultiFrequencyBandListNR-Aerial-SIB-r18 } -- TAG-FREQUENCYINFODL-SIB-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
1,257 | A.10 Monitor of paging performance | In EUTRAN, Paging is under the control of the MME. When the MME wants to page a UE it has to page it in all cells that belong to the TA(s) to which the UE is registered. The paging load per cell is an important measure for the operator as it allows the operator to properly dimension the resources for paging in the E-UTRAN Cell . At an E-UTRAN Cell it makes sense to measure the number of discarded paging messages if this is due to some problem in the eNodeB, such as paging occasion overflow. In that scenario the periodicity of paging occasions can be reconfigured in order to ensure that all paging messages are transmitted by the eNodeB in the first available paging occasion, thereby avoiding paging delays and extended call setup delay. Operators need to know when such an event occurs, in order to identify if the problem is at the E-UTRAN cell level or not. In addition to discarded paging records measurement, it is important to know total paging records received so that discarded paging records ratio can be derived. Total number of paging records received is important in the sense that, it may be fine if the discarded paging records are high if discarded paging records ratio is small. On the other hand, it may be problematic if discarded paging records are low, if discarded paging records ratio turn out to be high. | 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 | A.10 |
1,258 | O.2 Multiple PDU Sessions for different groups | In the case that the UE Application sends individual copies of data to different receivers, 5GS allows UE to simultaneously send data to different groups with different QoS policy via the following: - If different groups (IP or Ethernet multicast groups) are associated to different DNN and S-NSSAI combinations used for different 5G VN groups, then different PDU Sessions are used to transfer the data copy sent to different groups. As a result, the UE sends the same data to different groups using the QoS Flow of the respective PDU Sessions. Figure O.2-1 shows multiple PDU sessions used for different groups as an example. - Group1 (G1): a group of multicast address 1 with members UE1 and UE2 is associated with 5GVN.1 group. The QoS for multicast address 1 is set to QoS1. For G1, its members, multicast address 1 and corresponding QoS1 are provisioned as part of the AF requested QoS information as described in clause 6.1.3.28 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. - Group2 (G2): a group of multicast address 2 with members UE1 and UE3 is associated with 5GVN.2 group. The QoS for multicast address 2 is set to QoS2. For G2, its members, multicast address 2 and corresponding QoS2 are provisioned as part of the AF requested QoS information as described in clause 6.1.3.28 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. - During establishment or modification procedure for PDU Sessions targeting to DNN and S-NSSAI for 5GVN.1 group, or upon detection of the UE joining a multicast address, the SMF and PCF can jointly use the AF requested QoS information for 5GVN.1 group to set up the QoS flow in respective member's PDU Session. During establishment or modification procedure for PDU Sessions targeting to DNN and S-NSSAI for 5GVN.2 group, or upon detection of the UE joining a multicast address, the SMF and PCF can jointly use the AF requested QoS information for 5GVN.2 group to set up the QoS flow in respective member's PDU Session. As a result: - There will have two PDU Sessions for UE1: one PDU Session is targeting to DNN and S-NSSAI for 5GVN.1 group and there will have one QoS flow setup to carry data destined to multicast address 1 with QoS1; the other PDU Session is targeting to DNN and S-NSSAI for 5GVN.2 group and there will have one QoS flow setup to carry data destined to multicast address 2 with QoS2. - There will have one PDU Session for UE2: this PDU Session is targeting to DNN and S-NSSAI for 5GVN.1 group and there will have one QoS flow setup to carry data destined to multicast address 1 with QoS1. - There will have one PDU Session for UE3: this PDU Session is targeting to DNN and S-NSSAI for 5GVN.2 group and there will have one QoS flow setup to carry data destined to multicast address 2 with QoS2. - UE1 sends data with multicast address 1 (MA.1) to a UPF via the QoS Flow of UE1's PDU session for 5GVN.1 group. The UPF forwards the packet to UE2 as it is a member of multicast group represented by multicast address 1 via the QoS Flow of UE2's PDU Session for 5GVN.1 group. - UE1 also sends the same data with multicast address 2 (MA.2) to the UPF via the QoS Flow of UE1's PDU Session for 5GVN.2 group. The UPF forwards the packet to UE3 as it is a member of multicast group represented by multicast address 2 via the QoS Flow of UE3's PDU Session for 5GVN.2 group. Figure O.2-1: Multiple PDU Sessions for different groups | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | O.2 |
1,259 | 15.5.4 UE History Information from the UE | The source NG-RAN node collects and stores the UE History Information for as long as the UE stays in one of its cells. The UE may report the UE history information when connecting to a cell of the NG-RAN node, consisting of PCell and PSCell mobility history information, as specified in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12]. When information needs to be discarded because the list is full, such information will be discarded in order of its position in the list, starting with the oldest cell record. If the list is full, and the UE history information from the UE is available, the UE history information from the UE should also be discarded. The resulting information is then used in subsequent handover preparations by means of the Handover Preparation procedures over the NG and XN interfaces, which provide the target NG-RAN node with a list of previously visited cells and associated (per-cell) information elements. The Handover Preparation procedures also trigger the target NG-RAN node to start collection and storage of UE history Information and thus to propagate the collected information. In case of CHO, the target NG-RAN node updates the time UE stayed in cell of the latest PCell entry (i.e. the source cell) when the UE successfully accesses a candidate cell of the target NG-RAN node. The updated value of the time UE stayed in the source cell is equal to the value received from the source NG-RAN node during the Handover Preparation plus the time from receiving the Handover Request message from the source NG-RAN node to receiving the RRC Reconfiguration Complete message from the UE. When the target NG-RAN node receives the SCG UHI from the source NG-RAN node via the Handover Request message, the target NG-RAN node also updates the time UE stayed in cell of the latest PSCell entry (i.e. the source PSCell) as specified in TS 37.340[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 ] [21]. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 15.5.4 |
1,260 | 5.5.1.2.5C Attach for access to RLOS not accepted by the network | If the attach request for access to RLOS is received by the network and the UE requesting attach is not in limited service state, the MME shall reject the UE's attach request. If the attach request for access to RLOS cannot be accepted by the network, the MME shall send an ATTACH REJECT message to the UE including EMM cause #35 "Requested service option not authorized in this PLMN" or one of the EMM cause values as described in clause 5.5.1.2.5. Upon receiving the ATTACH REJECT message including EMM cause #35, the UE shall enter the state EMM-DEREGISTERED.PLMN-SEARCH and perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6] to attempt EPS attach for access to RLOS via another PLMN. Upon receiving the ATTACH REJECT message including one of the other EMM cause values, the UE shall perform the actions as described in clause 5.5.1.2.5. along with the following conditions: a) if the action for the reject involves searching for a suitable cell in E-UTRAN radio access technology, the UE shall proceed with the action and shall attempt to attach for access to RLOS in the new tracking area, if found; and b) if the action for the reject involves attempting to select GERAN or UTRAN radio access technology or disabling the E-UTRA capability, the UE shall skip the action for as long as access to RLOS is still needed. NOTE: How long the UE attempts to access RLOS is up to UE implementation. Then if the UE is in the same selected PLMN where the last attach procedure was attempted and rejected and if timer T3346 is not running, perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6] to attempt EPS attach for access to RLOS via another PLMN. If the attach request for access to RLOS fails due to abnormal cases b), c) or d) in clause 5.5.1.2.6, the UE shall perform the procedures as described in clause 5.5.1.2.6 with the exception that the UE shall skip actions that involve attempting to select GERAN or UTRAN radio access technology and actions that involve disabling the E-UTRA capability, for as long as access to RLOS is still needed. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.1.2.5C |
1,261 | 8.2.2 Control Plane Protocol Stacks between the UE and the 5GC 8.2.2.1 General | A single N1 NAS signalling connection is used for each access to which the UE is connected. The single N1 termination point is located in AMF. The single N1 NAS signalling connection is used for both Registration Management and Connection Management (RM/CM) and for SM-related messages and procedures for a UE. The NAS protocol on N1 comprises a NAS-MM and a NAS-SM components. There are multiple cases of protocols between the UE and a core network function (excluding the AMF) that need to be transported over N1 via NAS-MM protocol. Such cases include: - Session Management Signalling. - SMS. - UE Policy. - LCS. RM/CM NAS messages in NAS-MM and other types of NAS messages (e.g. SM), as well as the corresponding procedures, are decoupled. The NAS-MM supports generic capabilities: - NAS procedures that terminate at the AMF. This includes: - Handles Registration Management and Connection Management state machines and procedures with the UE, including NAS transport; the AMF supports following capabilities: - Decide whether to accept the RM/CM part of N1 signalling during the RM/CM procedures without considering possibly combined other non NAS-MM messages (e.g. SM) in the same NAS signalling contents; - Know if one NAS message should be routed to another NF (e.g. SMF), or locally processed with the NAS routing capabilities inside during the RM/CM procedures; - Provide a secure NAS signalling connection (integrity protection, ciphering) between the UE and the AMF, including for the transport of payload; - Provide access control if it applies; - It is possible to transmit the other type of NAS message (e.g. NAS SM) together with an RM/CM NAS message by supporting NAS transport of different types of payload or messages that do not terminate at the AMF, i.e. NAS-SM, SMS, UE Policy and LCS between the UE and the AMF. This includes: - Information about the Payload type; - Additional Information for forwarding purposes - The Payload (e.g. the SM message in the case of SM signalling); - There is a Single NAS protocol that applies on both 3GPP and non-3GPP access. When an UE is served by a single AMF while the UE is connected over multiple (3GPP/Non 3GPP) accesses, there is a N1 NAS signalling connection per access. Security of the NAS messages is provided based on the security context established between the UE and the AMF. Figure 8.2.2.1-1 depicts NAS transport of SM signalling, SMS, UE Policy and LCS. Figure 8.2.2.1-1 NAS transport for SM, SMS, UE Policy and LCS | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 8.2.2 |
1,262 | 5.2.2 Resource elements | Each element in the resource grid is called a resource element and is uniquely defined by the index pair in a slot where and are the indices in the frequency and time domains, respectively. Resource element on antenna port corresponds to the complex value . When there is no risk for confusion, or no particular antenna port is specified, the index may be dropped. Quantities corresponding to resource elements not used for transmission of a physical channel or a physical signal in a slot shall be set to zero. | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.2.2 |
1,263 | – MeasTriggerQuantityEUTRA | The IE MeasTriggerQuantityEUTRA is used to configure the trigger quantity and reporting range for E-UTRA measurements. The RSRP, RSRQ and SINR ranges correspond to RSRP-Range, RSRQ-Range and RS-SINR-Range in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10], respectively. MeasTriggerQuantityEUTRA information element -- ASN1START -- TAG-MEASTRIGGERQUANTITYEUTRA-START MeasTriggerQuantityEUTRA::= CHOICE { rsrp RSRP-RangeEUTRA, rsrq RSRQ-RangeEUTRA, sinr SINR-RangeEUTRA } RSRP-RangeEUTRA ::= INTEGER (0..97) RSRQ-RangeEUTRA ::= INTEGER (0..34) SINR-RangeEUTRA ::= INTEGER (0..127) -- TAG-MEASTRIGGERQUANTITYEUTRA-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
1,264 | 8.23.1 Migration of mobile IAB-MT via Xn handover | The mobile IAB-MT can be migrated from a source RRC-terminating IAB-donor-CU to a target RRC-terminating IAB-donor-CU using the Xn handover procedure. During this migration, the mobile IAB-DU co-located with the mobile IAB-MT is connected to an F1-terminating IAB-donor-CU, which may be the same as the source RRC-terminating IAB-donor-CU or the target RRC-terminating IAB-donor-CU, or it can be different from both the source and the target RRC-terminating IAB-donor-CU. Figure 8.23.1-1 shows an example of mobile IAB-MT migration via Xn handover. In this example, the mobile IAB-MT is connected to the source RRC-terminating IAB-donor-CU via a source path of an IAB topology before the migration, and it is connected to the target RRC-terminating IAB-donor-CU via a target path of a different IAB topology after the migration. Figure 8.23.1-1: Procedure for Xn-based migration of mobile IAB-MT 1. Steps 1-14 of the topology adaptation procedure in clause 8.17.3.1 are performed to conduct Xn handover of the mobile IAB-MT from the source parent IAB-node connected to the source RRC-terminating IAB-donor-CU to the target parent IAB-node connected to the target RRC-terminating IAB-donor-CU. In these steps, the mobile IAB-node corresponds to the migrating IAB-node in clause8.17.3.1, and the mobile IAB-MT’s source and target RRC-terminating IAB-donor-CUs correspond to the respective source and target IAB-donor-CUs of clause8.17.3.1. The source RRC-terminating IAB-donor-CU should retain the UE XnAP IDs allocated for the mobile IAB-MT as long as the mobile IAB-MT is connected. 2. Same as step 15 of the topology adaptation procedure in clause8.17.3.1, where the F1-C connection between the co-located mobile IAB-DU and its F1-terminating IAB-donor-CU is switched to the target path using the new TNL address information of the IAB-MT. In this step, the mobile IAB-node corresponds to the migrating IAB-node, and the F1-terminating IAB-donor-CU corresponds to the source IAB-donor-CU. 3. The mobile IAB-DU passes to the F1-terminating IAB-donor-CU via F1AP the gNB ID of the target RRC-terminating IAB-donor-CU and the mobile IAB-node’s BAP address allocated by the target RRC-terminating IAB-donor-CU. In case the migration of the mobile IAB-MT occurs during DU migration, each logical mobile IAB-DU passes this information to its respective F1-terminating IAB-donor-CU. The F1-terminating IAB-donor-CU retains the UE XnAP ID that it allocated to the mobile IAB-MT as long as the co-located mobile IAB-DU connects to this CU, and retains the UE XnAP ID allocated for the mobile IAB-MT by the source RRC-terminating IAB-donor-CU until the present step (step 3). 4. Steps 16-20 of the topology adaptation procedure in clause 8.17.3.1, where the F1-terminating IAB-donor-CU initiates the IAB Transport Migration Management procedure towards the target RRC-terminating IAB-donor-CU to provide the context of the offloaded traffic. The target RRC-terminating IAB-donor-CU reconfigures the BAP sublayer and/or BH RLC channels on the target path accordingly, and provides the UL BH information for UL BH reconfigurations to be conducted by the F1-terminating IAB-donor-CU on the mobile IAB-node. Then, the F1-U connections of the mobile IAB-node are migrated to the target path. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.23.1 |
1,265 | 17.5.6 De-registration procedure (BM-SC initiated) | This MBMS de-registration procedure is initiated by BM-SC when the specific multicast MBMS bearer service is terminated. This procedure tears down the distribution tree for the delivery of session attributes and MBMS data. This procedure results in releasing of all MBMS Bearer Contexts. Figure 31: MBMS De-Registration procedure BM-SC initiated 1. The BM-SC sends a ASR message to all GGSNs contained in the "list of downstream nodes" parameter of the corresponding MBMS Bearer Context to indicate that a specific MBMS bearer service is terminated. 2. The GGSN returns a ASA message to the BM-SC. The BM-SC releases all MBMS UE Contexts and removes the identifier of the GGSN from the "list of downstream nodes" parameter of the corresponding MBMS Bearer context. | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 17.5.6 |
1,266 | 14.8 Emergency Realm and Emergency NAI for Emergency Cases | The emergency realm shall be of the form of a home network realm as described in clause 14.2 prefixed with the label "sos." at the beginning of the domain name. An example of a WLAN emergency NAI realm is: IMSI in use: 234150999999999; Where: MCC = 234; MNC = 15; MSIN = 0999999999 Which gives the home network domain name: sos.wlan.mnc015.mcc234.3gppnetwork.org. The NAI for emergency cases shall be of the form as specified in clauses 14.3 and 14.4, with the addition of the emergency realm as described above for PLMNs where the emergency realm is supported. When UE is using I-WLAN as the access network for IMS emergency calls and IMSI is not available, the Emergency NAI shall be an NAI compliant with IETF RFC 4282 [53] consisting of username and realm, either constructed with IMEI or MAC address, as specified in 3GPP TS 33.234[ 3G security; Wireless Local Area Network (WLAN) interworking security ] [55]. The exact format shall be: imei<IMEI>@sos.wlan.mnc<visitedMNC>.mcc<visitedMCC>.3gppnetwork.org or if IMEI is not available, mac<MAC>@sos.wlan.mnc<visitedMNC>.mcc<visitedMCC>.3gppnetwork.org The realm part of the above NAI consists of the realm built using the PLMN ID (visitedMCC + visitedMNC) of the PLMN selected as a result of the network selection procedure, as specified in clause 5.2.5.4 of the 3GPP TS 24.234[ 3GPP system to Wireless Local Area Network (WLAN) interworking; WLAN User Equipment (WLAN UE) to network protocols; Stage 3 ] [48]. The MNC and MCC shall be with 3 digits coded. If there are only 2 significant digits in the MNC, one "0" digit shall be inserted at the left side to fill the 3 digits coding of MNC in the realm of the NAI. For example, if the IMEI is 219551288888888, and the selected PLMN is with MCC 345 and MNC 12, the Emergency NAI then takes the form of [email protected]. For example, if the MAC address is 44-45-53-54-00-AB, and the selected PLMN is with MCC 345 and MNC 12, the Emergency NAI then takes the form of [email protected], where the MAC address is represented in hexadecimal format without separators. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 14.8 |
1,267 | 8.3.1.1I 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.1.1I-1, with the addition of the parameters in Table 8.3.1.1I-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 on 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.1.1I-1: Test Parameters for Minimun Performance Requirement - Single-layer Spatial Multiplexing with assistance information for simultaneous transmition interfering PDSCH (FRC) Table 8.3.1.1I-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.1.1I |
1,268 | 4.3.4.2 Roaming architectures | Figure 4.3.4.2-1 represents the Roaming architecture with local breakout and Figure 4.3.4.2-2 represents the Roaming architecture with home-routed traffic for interworking between ePDG/EPC and 5GS. Figure 4.3.4.2-1: Local breakout roaming architecture for interworking between ePDG/EPC and 5GS NOTE 1: The details of the interfaces between the UE and the ePDG, and between EPC nodes (i.e. SWm, SWd, SWx, S2b and S6b), are documented in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [43]. NOTE 2: Interworking with ePDG is only supported with GTP based S2b. S6b interface is optional (see clause 4.11.4.3.6 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]). Figure 4.3.4.2-2: Home-routed roaming architecture for interworking between ePDG/EPC and 5GS NOTE 1: The details of the interfaces between the UE and the ePDG, and between EPC nodes (i.e. SWm, SWd, SWx, S2b and S6b), are documented in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [43]. NOTE 2: Interworking with ePDG is only supported with GTP based S2b. S6b interface is optional (see clause 4.11.4.3.6 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]). | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3.4.2 |
1,269 | 4.3.12.6 PCC for Emergency Services | Dynamic PCC is used for UEs establishing emergency service, the procedures are as described in TS 23.203[ Policy and charging control architecture ] [6]. When establishing emergency bearer services with a PDN GW, according to clause 4.7.5, the PCRF provides the PDN GW with the QoS parameters, including an ARP value reserved for the emergency bearers to prioritize the bearers when performing admission control. Dynamic PCC shall be used to manage IMS emergency sessions when an operator allows IMS emergency sessions. NOTE: For IMS emergency services prior to this Release of this specification, dynamic PCC support was not required in the specifications. According to clause 4.7.5, when solely using voice/GTT, local configuration of static policy functions is also allowed prior to this Release of this specification and is not subject to standardization. The PCRF ensures that the emergency PDN connection is used only for IMS emergency sessions. The PCRF rejects an IMS session established via the emergency PDN connection if the AF (i.e. P-CSCF) does not provide an emergency indication to the PCRF. | 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.12.6 |
1,270 | A.1 Monitor of call(/session) setup performance | Call(/session) setup is one of most important step to start delivering services by the networks to users. The success or failure of a call(/session) setup directly impacts the quality level for delivering the service by the networks, and also the feeling of the end user. So the success or failure of call(/session) setup needs be monitored, this can be achieved by the calculation of call setup success rate which gives a direct view to evaluate the call setup performance, and the analysis of the specific reason causing the failure to find out the problem and ascertain the solutions. In addition, the time duration of the call(/session) setup need to be monitored as it impacts the end user experience, and by comparison with operator’s benchmark requirements, the optimization may be required according the performance. And due to different priority and tolerance for different service type with different OoS level in the networks, the monitor needs to be opened on each service type and OoS level. To complete the call(/session) setup procedure, E-UTRAN is mainly responsible for the establishment of radio and S1 signaling connection and service bearer by the RRC connection establishment (See 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]), RRC connection reestablishment after RRC connection dropped due to some reasons like radio link failure or handover failure etc (See 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]) E-RAB setup (See 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [9]) and Initial UE Context Setup (See 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [9]) procedure. To support the monitor of success or failure of the call(/session) setup, the performance measurements related to RRC connection establishment (See 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]), RRC connection reestablishment (See 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]) procedure, and the performance measurements related to E-RAB setup (See 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [9]) and Initial UE Context Setup (See 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [9]) procedure for each QoS level are required To support the monitor of time duration of setup call(/session) setup, the performance measurements related to RRC connection setup time and E-RAB setup time are required. | 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 | A.1 |
1,271 | 4.3.7.1a.1 GTP-C Load Control | GTP-C Load Control feature is an optional feature which allows a GTP control plane node to send its Load Control Information to a peer GTP control plane node which the receiving GTP control plane peer node uses to augment existing GW selection procedure (i.e. as described in "PDN GW Selection" and "Serving GW Selection" according to clauses 4.3.8.1, and 4.3.8.2 respectively). Load Control Information reflects the operating status of the resources of the originating GTP control plane node. NOTE 1: How a node computes its Load Control Information is implementation dependent. Where certain pre-condition as described in clause 12.2.4.1 of TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [43], is applicable, an optional feature APN level load control may be supported and activated in the network. If this feature is activated, the PDN GW may convey the Load Control Information at APN level (reflecting the operating status of the resources at the APN level), besides at node level. GTP-C Load Control feature allows the Serving GW to send its Load Control Information to the MME/SGSN. GTP-C Load Control feature also allows the PDN GW to send its Load Control Information to the MME/SGSN via a Serving GW. Upon receiving Load Control Information the MME/SGSN supporting GTP-C Load Control feature uses it according to clauses 4.3.8.1, and 4.3.8.2 for "PDN GW Selection" and "Serving GW Selection" respectively. A node supporting GTP-C Load Control feature sends Load Control Information in any GTP control plane request or response message such that exchange of Load Control Information does not trigger extra signalling. A node supporting GTP-C Load Control feature sends Load Control Information to a peer GTP control node based on whether local configuration allows for it. A node supporting GTP-C Load Control feature may decide to send different values of Load Control Information on inter-network (roaming) and on intra-network (non-roaming) interfaces based on local configuration. Local configuration may allow the VPLMN to decide whether or not to act upon Load Control Information sent from a peer GTP control plane node in the HPLMN. NOTE 2: Refer to clause 12 of TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [43] for the details, such as exact format of the Load Control Information, mechanisms to discover the support of the feature by the peer node, interfaces for which this feature is applicable, APN level load control, etc. | 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.7.1a.1 |
1,272 | 19.10 Presence Reporting Area Identifier (PRA ID) | The Presence Reporting Area Identifier (PRA ID) is used to identify a Presence Reporting Area (PRA). PRAs can be used for reporting changes of UE presence in a PRA, e.g. for policy control or charging decisions. See 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [72], 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [3] and 3GPP TS 23.203[ Policy and charging control architecture ] [107]. A PRA is composed of a short list of TAs/RAs, or eNBs and/or cells/SAs in a PLMN. A PRA can be: - either a "UE-dedicated PRA", defined in the subscriber profile; - or a "Core Network predefined PRA", pre-configured in MME/S4-SGSN. PRA IDs used to identify "Core Network predefined PRAs" shall not be used for identifying "UE-dedicated PRAs". The same PRA ID may be used for different UEs to identify different "UE-dedicated PRAs", i.e. PRA IDs may overlap between different UEs, while identifying different "UE-dedicated PRAs". The PRA ID shall be encoded as an integer on 3 octets. The most significant bit of the PRA ID shall be set to 0 for UE-dedicated PRA and shall be to 1 for Core Network predefined PRA. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 19.10 |
1,273 | 6.4.1.6 Abnormal cases on the network side | The following abnormal cases can be identified: a) Expiry of timer T3485: On the first expiry of the timer T3485, the MME shall resend the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST and shall reset and restart timer T3485. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3485, the MME shall release possibly allocated resources for this activation and shall abort the procedure. b) Lower layer indicates that the HeNB rejected the establishment of the default bearer (see 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [23]) for a LIPA PDN connection or SIPTO at the local network PDN connection due to a triggered handover: The MME shall enter the state BEARER CONTEXT INACTIVE, stop timer T3485 and reject the PDN connectivity request procedure including the ESM cause value #34 "service option temporarily out of order" in the PDN CONNECTIVITY REJECT message. The MME shall release possibly allocated resources for this activation. | 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.1.6 |
1,274 | 8.1 Overview | This clause defines the structure of the messages of the Layer 3 (L3) protocols defined in the present document. These are standard L3 messages as defined in 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [12]. Each definition given in the present clause includes: a) a brief description of the message direction and use, including whether the message has: 1. Local significance, i.e. relevant only on the originating or terminating access; 2. Access significance, i.e. relevant in the originating and terminating access, but not in the network; 3. Dual significance, i.e. relevant in either the originating or terminating access and in the network; or 4. Global significance, i.e. relevant in the originating and terminating access and in the network. b) a table listing the Information Elements (IE) known in the message and the order of their appearance in the message. All IEs that may be repeated are explicitly indicated (The V, LV and LV-E formatted IEs, which compose the imperative part of the message, occur before the T, TV, TLV and TLV-E formatted IEs which compose the non-imperative part of the message, see 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [12]). In a (maximal) sequence of consecutive IEs with half octet length, the first IE with half octet length occupies bits 1 to 4 of octet N, the second IE bits 5 to 8 of octet N, the third IE bits 1 to 4 of octet N+1 etc. Such a sequence always has an even number of elements. For each information element the table indicates: 1. The Information Element Identifier (IEI), in hexadecimal notation, if the IE has format T, TV, TLV or TLV-E. If the IEI has half octet length, it is specified by a notation representing the IEI as a hexadecimal digit followed by a "-" (example: B-). NOTE: The same IEI can be used for different information element types in different messages of the same protocol. 2. The name of the information element (which may give an idea of the semantics of the element). The name of the information element followed by "IE" or "information element" is used in this technical report as reference to the information element within a message. 3. The name of the type of the information element (which indicates the coding of the value part of the IE), and generally, the referenced clause of clause 9 of the present document describing the value part of the information element. 4. The presence requirement indication (M, C, or O) for the IE as defined in 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [12]. 5. The format of the information element (T, V, TV, LV, TLV, LV-E or TLV-E) as defined in 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [12]. 6. The length of the information element (or permissible range of lengths), in octets, in the message, where "?" means that the maximum length of the IE is only constrained by link layer protocol. This indication is non-normative. c) clauses specifying, where appropriate, conditions for IEs with presence requirement C or O in the relevant message which together with other conditions specified in the present document define when the information elements shall be included or not, what non-presence of such IEs means, and – for IEs with presence requirement C – the static conditions for presence or non-presence of the IEs or for both cases (see 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [12]). | 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 | 8.1 |
1,275 | 4.13.3.6 MT SMS over NAS in CM-IDLE state and RRC_INACTIVE with CN based MT communication state via 3GPP access | Figure 4.13.3.6-1: MT SMS over NAS in CM-IDLE and RRC_INACTIVE state via 3GPP access 1-3 MT SMS interaction between SC/SMS-GMSC/UDM follow the procedure as defined in TS 23.040[ Technical realization of the Short Message Service (SMS) ] [7] or TS 23.540[ 5G System: Technical realization of Service Based Short Message Service; Stage 2 ] [84]. If there are two AMFs serving the UE, one is for 3GPP access and another is for non-3GPP access, there are two SMSF addresses stored in UDM/UDR. The UDM shall return both SMSF addresses. 4. The SMSF checks the SMS management subscription data. If SMS delivery is allowed, SMSF invokes Namf_MT_EnableUEReachability service operation to AMF. AMF pages the UE using the procedure defined in clause 4.2.3.3. The UE responds to the page with Service Request procedure. If the AMF indicates SMSF that UE is not reachable (including the cases that UE applies power saving enhancement as described in clause 5.31.7 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]), the procedure of the unsuccessful Mobile terminating SMS delivery described in clause 4.13.3.9 is performed and the following steps are skipped. In the case of power saving enhancement, the AMF further stores the information received in the Namf_MT_EnableUEReachability request and pages the UE when UE is considered reachable. If the UE access to the AMF via both 3GPP access and non-3GPP access, the AMF determines the Access Type to transfer the MT-SMS based on operator local policy. 5a-5b. SMSF forward the SMS message to be sent as defined in TS 23.040[ Technical realization of the Short Message Service (SMS) ] [7] (i.e. the SMS message consists of CP-DATA/RP-DATA/TPDU/SMS-DELIVER parts) to AMF by invoking Namf_Communication_N1N2MessageTransfer service operation. The AMF transfers the SMS message to the UE. 5c-5d. The UE acknowledges receipt of the SMS message to the SMSF. For uplink unitdata message toward the SMSF, the AMF invokes Nsmsf_SMService_UplinkSMS service operation to forward the message to SMSF. In order to permit the SMSF to create an accurate charging record, the AMF also includes IMEISV, the current UE Location Information (ULI) of the UE as defined in clause 5.6.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] and if the SMS is delivered to the UE via 3GPP access, the local time zone. 6a-6b. The UE returns a delivery report as defined in TS 23.040[ Technical realization of the Short Message Service (SMS) ] [7]. The delivery report is encapsulated in an NAS message and sent to the AMF which is forwarded to SMSF by invoking Nsmsf_SMService_UplinkSMS service operation. 6c-6d. The SMSF acknowledges receipt of the delivery report to the UE. The SMSF uses Namf_Communication_N1N2MessageTransfer service operation to send SMS CP ack message to the AMF. The AMF encapsulates the SMS message via a NAS message to the UE. If SMSF has more than one SMS to send, the SMSF and the AMF forwards subsequent SMS /SMS ack/ delivery report the same way as described in step 4-6c. If the SMSF knows the SMS CP ack is the last message to be transferred for UE, the SMSF shall include a last message indication in the Namf_Communication_N1N2MessageTransfer service operation so that the AMF knows no more SMS data is to be forwarded to UE. NOTE: The behaviour of AMF based on the "last message indication" is implementation specific. 7. In parallel to steps 6c and 6d, the SMSF delivers the delivery report to SC as defined in TS 23.040[ Technical realization of the Short Message Service (SMS) ] [7] or TS 23.540[ 5G System: Technical realization of Service Based Short Message Service; Stage 2 ] [84]. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.13.3.6 |
1,276 | 5.2.2.3.2 Receipt of CALL CONFIRMED and ALERTING by the network | The call control entity of the network in the "call present" state, shall, upon receipt of a CALL CONFIRMED message: stop timer T303, start timer T310 and enter the "mobile terminating call confirmed" state. In Iu mode, network shall include the SI received in the CALL CONFIRMED message into the RABid and send it back to the mobile station. For RABid see 3GPP TS 25.413[ UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling ] [19c] and 3GPP TS 44.118[ None ] [111]. If the network receives the CALL CONFIRMED message with no SI, the network shall set the SI value to 1. For speech calls, if the CALL CONFIRMED message contains a Supported Codec List information element, the network shall use this list to select the codec for UTRAN. If no Supported Codec List information element is received, then for UTRAN the network shall select the default UMTS speech codec according to subclause 5.2.1.11. Codecs for GERAN shall be selected from the codecs indicated in the Supported Codec List information element or in the Bearer Capability information element. If neither a Supported Codec List information element nor a Bearer Capability information element is received, then for GERAN the network shall select GSM full rate speech version 1. Codec information that does not apply to the currently serving radio access shall be used by the network if an inter-system change occurs. The call control entity of the mobile station having entered the "mobile terminating call confirmed" state, if the call is accepted at the called user side, the mobile station proceeds as described in subclause 5.2.2.5. Otherwise, if the signal information element was present in the SETUP message user alerting is initiated at the mobile station side; if the signal information element was not present in the SETUP message, user alerting is initiated when an appropriate channel is available. Here, initiation of user alerting means: - the generation of an appropriate tone or indication at the mobile station; and - sending of an ALERTING message by the call control entity of the MS to its peer entity in the network and entering the "call received" state. The call control entity of the network in the "mobile terminated call confirmed" state shall, upon receipt of an ALERTING message: send a corresponding ALERTING indication to the calling user; stop timer T310; start timer T301, and enter the "call received" state. In the "mobile terminating call confirmed" state or the "call received" state, if the user of a mobile station is User Determined User Busy then a DISCONNECT message shall be sent with cause #17 "user busy". In the "mobile terminating call confirmed" state, if the user of a mobile station wishes to reject the call then a DISCONNECT message shall be sent with cause #21 "call rejected". | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.2.2.3.2 |
1,277 | K.1 Common information elements. | For the common information elements types listed below, the default coding of information element identifier bits is summarized in table K.1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Table K.1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Default information element identifier coding for common information elements NOTE 1: These values were allocated but never used in earlier phases of the protocol. NOTE 2: For GPRS common information elements no default values are defined: | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | K.1 |
1,278 | 16.12.5.6 Paging | When both L2 U2N Relay UE and L2 U2N Remote UE are in RRC IDLE or RRC INACTIVE, the L2 U2N Relay UE monitors paging occasions of its connected L2 U2N Remote UE(s). When a L2 U2N Relay UE needs to monitor paging for a L2 U2N Remote UE, the L2 U2N Relay UE should monitor all POs of the L2 U2N Remote UE. When L2 U2N Relay UE is in RRC_CONNECTED and L2 U2N Remote UE(s) is in RRC_IDLE or RRC_INACTIVE, there are two options for paging delivery: - The L2 U2N Relay UE monitors POs of its connected L2 U2N Remote UE(s) if the active DL BWP of the L2 U2N Relay UE is configured with common search space including paging search space; - The delivery of the L2 U2N Remote UE's paging can be performed through a dedicated RRC message from the gNB to the L2 U2N Relay UE. The dedicated RRC message for delivering L2 U2N Remote UE paging to the RRC_CONNECTED L2 U2N Relay UE may contain one or more Remote UE IDs (5G-S-TMSI or I-RNTI). It is up to network implementation to decide which of the above two options to use. The L2 U2N Relay UE in RRC_CONNECTED, if configured with paging search space, can determine whether to monitor POs for a L2 U2N Remote UE based on the indication within the PC5-RRC signalling received from the L2 U2N Remote UE. The L2 U2N Remote UE in RRC_IDLE provides 5G-S-TMSI and UE specific DRX cycle (if configured by upper layer) to the L2 U2N Relay UE for requesting to perform PO monitoring. The L2 U2N Remote UE in RRC_INACTIVE provides the minimum value of two UE specific DRX cycles (if configured respectively by upper layer and NG-RAN), 5G-S-TMSI and I-RNTI to the L2 U2N Relay UE for PO monitoring. The L2 U2N Relay UE in RRC_CONNECTED can notify the L2 U2N Remote UE information (i.e. 5G-S-TMSI/I-RNTI) to the gNB via the SidelinkUEInformationNR message for paging delivery purpose. The L2 U2N Relay UE receives paging messages to check the 5G-S-TMSI/I-RNTI and sends relevant paging record to the L2 U2N Remote UE accordingly. The L2 U2N Relay UE uses unicast signalling to send paging to the L2 U2N Remote UE via PC5. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.12.5.6 |
1,279 | 8.19.1 Remote UE initial access | The signalling flow for Remote UE Initial access is shown in Figure 8.19.1-1. Figure 8.19.1-1: Remote UE Initial Access procedure 1. The U2N Remote UE and the U2N Relay UE perform discovery procedure, and establish PC5 connection using NR ProSe procedure. 2. The U2N Remote UE sends an RRCSetupRequest message to the U2N Relay UE via PC5 Relay RLC Channel. 3. The U2N Relay UE withholds the received RRC message and sends the SidelinkUEInformationNR message to the gNB-DU. Before that, if the U2N Relay UE is in RRC_IDLE/RRC_INACTIVE state, it should trigger the RRC establishment/resume procedure to enter RRC_CONNECTED state and gNB may configure the U2N Relay UE with Uu Relay RLC channel(s) for relaying of U2N Remote UE’s SRB0/1. 4. The gNB-DU sends the UL RRC MESSAGE TRANSFER message of the U2N Relay UE by encapsulating the SidelinkUEInformationNR message to gNB-CU, and gNB-CU allocates the local ID of U2N Remote UE. 5. The gNB-CU sends the UE CONTEXT MODIFICATION REQUEST message of the U2N Relay UE to gNB-DU. Such message may request the establishment of Uu Relay RLC channel(s) for the transmission of U2N Remote UE’s SRB0/1 if not configured yet. 6. The gNB-DU sends the UE CONTEXT MODIFICATION RESPONSE message of the U2N Relay UE to gNB-CU. 7. The gNB-CU sends the DL RRC MESSAGE TRANSFER message of the U2N Relay UE to gNB-DU by encapsulating the RRCReconfiguration message, which contains the local ID allocated to the U2N Remote UE. The RRCReconfiguration message shall also contain the Uu Relay RLC channel(s) configuration if not configured and bearer mapping for relaying of U2N Remote UE’s SRB0/1. 8. The gNB-DU sends the RRCReconfiguration message to the U2N Relay UE to configure the local ID of the U2N Remote UE, the Uu Relay RLC channel(s) configuration and bearer mapping for relaying of U2N Remote UE’s SRB0/1. 9. The U2N Relay UE sends the RRCReconfigurationComplete message to gNB-DU. 10. The gNB-DU sends the UL RRC MESSAGE TRANSFER message of the U2N Relay UE by encapsulating the RRCReconfigurationComplete message to gNB-CU. 11. After receiving the local ID of the U2N Remote UE and the Uu Relay RLC channel(s) configuration and bearer mapping for relaying of U2N Remote UE’s SRB0, the U2N Relay UE sends the RRCSetupRequest message of the U2N Remote UE to gNB-DU. The local ID of the U2N Remote UE and RB ID for SRB0 are conveyed in the SRAP header. 12. The gNB-DU allocates a C-RNTI and a gNB-DU UE F1AP ID for the U2N Remote UE and sends the INITIAL UL RRC MESSAGE TRANSFER message to gNB-CU by encapsulating the RRCSetupRequest message of the U2N Remote UE. In addition, the local ID of the U2N Remote UE , the gNB-DU UE F1AP ID of the U2N Relay UE and the sidelink configuration container for at least the PC5 Relay RLC channel configuration for relaying of U2N Remote UE’s SRB1 are included in the INITIAL UL RRC MESSAGE TRANSFER message. 13. The gNB-CU allocates a gNB-CU UE F1AP ID for the U2N Remote UE and generates a RRCSetup message towards the U2N Remote UE. The RRC message is encapsulated in the DL RRC MESSAGE TRANSFER message, and includes the configurations of PC5 Relay RLC channel and bearer mapping at least for the transmission of U2N Remote UE’s SRB1. 14. The gNB-DU sends the RRCSetup message to the U2N Remote UE via the U2N Relay UE. 15. The gNB-CU configures the U2N Relay UE with PC5 Relay RLC channel, Uu Relay RLC channel and bearer mapping for relaying of U2N Remote UE’s SRB1. According to the configuration from gNB-CU, the U2N Relay UE establishes a PC5 Relay RLC channel for relaying of U2N Remote UE’s SRB1 over PC5 and establishes a Uu Relay RLC channel for relaying of U2N Remote UE’s SRB1 towards gNB-DU if not configured yet. NOTE 1: This step may be performed earlier, e.g., via steps 5~8. 16. The U2N Remote UE sends the RRCSetupComplete message to the gNB-DU via the U2N Relay UE. 17. The gNB-DU encapsulates the RRC message in the UL RRC MESSAGE TRANSFER message and sends it to the gNB-CU. 18. Upon receiving the RRCSetupComplete message of U2N Remote UE, the gNB-CU sends the INITIAL UE MESSAGE message to the AMF. 19. The AMF sends the INITIAL CONTEXT SETUP REQUEST message to the gNB-CU. 20. The gNB-CU sends the UE CONTEXT SETUP REQUEST message to establish the U2N Remote UE context in the gNB-DU. Such message may request the configuration of PC5 Relay RLC channels for the transmission of U2N Remote UE’s SRB2 and DRBs, and may also encapsulate the SecurityModeCommand message. 21. The gNB-DU sends the SecurityModeCommand message to the U2N Remote UE via U2N Relay UE. 22. The gNB-DU sends the UE CONTEXT SETUP RESPONSE message of the U2N Remote UE to the gNB-CU, which contains the configuration of PC5 Relay RLC channels for the transmission of U2N Remote UE’s SRB2 and DRBs. 23. The U2N Remote UE responds with the SecurityModeComplete message. 24. The gNB-DU encapsulates the RRC message in the UL RRC MESSAGE TRANSFER message and sends it to the gNB-CU. 25. The gNB-CU generates the RRCReconfiguration message for U2N Remote UE and encapsulates it in the DL RRC MESSAGE TRANSFER message. The RRCReconfiguration message contains the configuration of PC5 Relay RLC channels and bearer mapping for the transmission of U2N Remote UE’s SRB2 and DRBs. 26. The gNB-DU sends RRCReconfiguration message to the U2N Remote UE via the U2N Relay UE. 27. The U2N Remote UE sends RRCReconfigurationComplete message to the gNB-DU via the U2N Relay UE. 28. The gNB-DU encapsulates the RRC message in the UL RRC MESSAGE TRANSFER message and send it to the gNB-CU. 29. The gNB-CU sends the INITIAL CONTEXT SETUP RESPONSE message to the AMF. 30. The gNB-CU configures additional Uu Relay RLC channels between the gNB-DU and the U2N Relay UE, and additional PC5 Relay RLC channels for the U2N Relay UE for relaying of U2N Remote UE’s DRBs and SRBs. Also, such step may configure the bearer mapping between U2N Remote UE’s DRB/SRB and PC5/Uu Relay RLC channel at the U2N Relay UE. NOTE 2: This step may be performed earlier. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.19.1 |
1,280 | 4.4.2 MME | MME functions include: - NAS signalling; - NAS signalling security; - Inter CN node signalling for mobility between 3GPP access networks (terminating S3); - UE Reachability in ECM-IDLE state (including control, execution of paging retransmission and optionally Paging Policy Differentiation); - Tracking Area list management; - Mapping from UE location (e.g. TAI) to time zone, and signalling a UE time zone change associated with mobility, - PDN GW and Serving GW selection; - MME selection for handovers with MME change; - SGSN selection for handovers to 2G or 3G 3GPP access networks; - Roaming (S6a towards home HSS); - Authentication; - Authorization; - Bearer management functions including dedicated bearer establishment; - Lawful Interception of signalling traffic; - Warning message transfer function (including selection of appropriate eNodeB); - UE Reachability procedures; - Support Relaying function (RN Attach/Detach); - Change of UE presence in Presence Reporting Area reporting upon PCC request, - in the case of Change of UE presence in Presence Reporting Area reporting, management of Core Network pre-configured Presence Reporting Areas. - For the Control Plane CIoT EPS Optimisation: a) transport of user data (IP, Non-IP and Ethernet)); b) local Mobility Anchor point; c) header compression (for IP user data); d) ciphering and integrity protection of user data; e) Lawful Interception of user traffic not transported via the Serving GW (e.g. traffic using T6a). NOTE: The Serving GW and the MME may be implemented in one physical node or separated physical nodes. For CIoT EPS Optimisation, the Serving GW and the MME can be implemented in one physical node (e.g. C-SGN) or separated physical nodes. The C-SGN can also encompass the PDN GW function. The MME shall signal a change in UE Time Zone only in the case of mobility and in the case of UE triggered Service Request, PDN Disconnection and UE Detach. If the MME cannot determine whether the UE Time Zone has changed (e.g. the UE Time Zone is not sent by the old MME during MME relocation), the MME should not signal a change in UE Time Zone. A change in UE Time Zone caused by a regulatory mandated time change (e.g. daylight saving time or summer time change) shall not trigger the MME to initiate signalling procedures due to the actual change. Instead the MME shall wait for the UE's next mobility event or Service Request procedure and then use these procedures to update the UE Time Zone information in the PDN GW. | 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.4.2 |
1,281 | 6.4.3.5 Abnormal cases in the UE | The following abnormal cases can be identified: a) Expiry of timer T3582. The UE shall, on the first expiry of the timer T3582, retransmit the PDU SESSION RELEASE REQUEST message and the PDU session information which was transported together with the initial transmission of the PDU SESSION RELEASE REQUEST message and shall reset and start timer T3582. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3582, the UE shall abort the procedure, release the allocated PTI, perform a local release of the PDU session, and perform the registration procedure for mobility and periodic registration update by sending a REGISTRATION REQUEST message including the PDU session status IE over each access that user plane resources have been established if the PDU session is an MA PDU session, or over the access the PDU session is associated with if the PDU session is a single access PDU session. If there is one or more multicast MBS sessions associated with the PDU session, the UE shall locally leave the associated multicast MBS sessions. b) Collision of UE-requested PDU session release procedure and network-requested PDU session modification procedure. When the UE receives a PDU SESSION MODIFICATION COMMAND message during the UE-requested PDU session release procedure, and the PDU session indicated in PDU SESSION MODIFICATION COMMAND message is the PDU session that the UE had requested to release, the UE shall ignore the PDU SESSION MODIFICATION COMMAND message and proceed with the PDU session release procedure. c) Collision of UE-requested PDU session release procedure and network-requested PDU session release procedure. When the UE receives a PDU SESSION RELEASE COMMAND message with the PTI IE set to "No procedure transaction identity assigned" during the UE-requested PDU session release procedure, the PDU session indicated in the PDU SESSION RELEASE COMMAND message is the same as the PDU session that the UE requests to release: - if the Access type IE is included in the PDU SESSION RELEASE COMMAND message and the PDU session is an MA PDU session and having user-plane resources established on the access different from the access indicated in the Access type IE in the PDU SESSION RELEASE COMMAND message, the UE shall proceed both the UE-requested PDU session release procedure and network-requested PDU session release procedure; or - otherwise, the UE shall abort the UE-requested PDU session release procedure and shall stop the timer T3582 and proceed with the network-requested PDU session release procedure. NOTE 1: Whether the UE ignores the 5GSM cause #39 "reactivation requested" if received in the PDU SESSION RELEASE COMMAND is up to the UE implementation. d) Receipt of an indication that the 5GSM message was not forwarded due to routing failure Upon receiving an indication that the 5GSM message was not forwarded due to routing failure along with a PDU SESSION RELEASE REQUEST message with the PDU session ID IE set to the same value as the PDU session ID that was sent by the UE, the UE shall stop timer T3582, abort the procedure, release the allocated PTI, perform a local release of the PDU session, and perform the registration procedure for mobility and periodic registration update by sending a REGISTRATION REQUEST message including the PDU session status IE over each access that user plane resources have been established if the PDU session is an MA PDU session, or over the access the PDU session is associated with if the PDU session is a single access PDU session. If there is one or more multicast MBS sessions associated with the released PDU session, the UE shall locally leave the associated multicast MBS sessions. e) PDU session release signalling restricted due to service area restriction The UE may delay the release of the PDU session until the UE is not restricted by service area restrictions, or it may release the allocated PTI, perform a local release of the PDU session, and include the PDU session status IE over each access that user plane resources have been established if the PDU session is an MA PDU session, or over the access the PDU session is associated with if the PDU session is a single access PDU when performing the next registration procedure. If the UE performs the local release of the PDU session and there is one or more multicast MBS sessions associated with the released PDU session, the UE shall locally leave the associated multicast MBS sessions. f) Collision of UE-requested PDU session release procedure and N1 NAS signalling connection release The UE may immediately retransmit the PDU SESSION RELEASE REQUEST message and stop, reset and restart timer T3582, if the following conditions apply: 1) The original UE-requested PDU session release procedure was initiated over an existing N1 NAS signalling connection; and 2) the previous transmission of the PDU SESSION RELEASE REQUEST message was not initiated due to timer T3582 expiry. g) Receipt of an indication that the 5GSM message was not forwarded due to the PLMN is not allowed to operate at the present UE location Upon receiving an indication that the 5GSM message was not forwarded because the UE accessing via a satellite NG-RAN cell is informed that the PLMN is not allowed to operate at the present UE location along with a PDU SESSION RELEASE REQUEST message with the PDU session ID IE set to the same value as the PDU session ID that was sent by the UE, the UE shall stop timer T3582, abort the procedure and locally release the PDU session. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.4.3.5 |
1,282 | 12.3.9.3.4 Based on the Message Priority signalled in the GTP-C message | Message prioritization may be performed by an overloaded node, when handling incoming messages during an overloaded condition, based on the relative GTP-C message priority signalled in the GTP-C header (see clauses 5.4 and 5.5). A GTP-C entity shall determine whether to set and use the message priority in GTP-C signalling within the PLMN and/or across the PLMN boundaries, based on operator policy and roaming agreements. The following requirements shall apply if being used. A sending GTP-C entity shall determine the relative message priority to signal in the message according to the principles specified in clause 12.3.9.3.1. If the message affects multiple bearers (e.g. Modify Bearer Request), the relative message priority should be determined considering the highest priority ARP among all the bearers. A GTP-C entity should set the same message priority in a Triggered message or Triggered Reply message as received in the corresponding Initial message or Triggered message respectively. The message priority values sent on intra-network interfaces may differ from the values sent on inter-network interfaces. When messages cross PLMN boundaries, the Message Priority in the GTP-C header may be stripped or modified in these messages. NOTE : This is to take into account that the priority definitions can vary between PLMNs and avoid messages from a foreign PLMN to gain unwarranted preferential treatment. For incoming GTP-C messages that do not have a message priority in the GTP-C header, the receiving GTP-C entity: - shall apply a default priority, if the incoming message is an Initial message; - should apply the message priority sent in the Initial message or Triggered message, if the incoming message is a Triggered or Triggered Reply message (respectively). This feature should be supported homogenously across the nodes in the network, otherwise an overloaded node will process initial messages received from the non-supporting nodes according to the default priority while initial messages received from supporting nodes will be processed according to the message priority signalled in the GTP-C message. | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 12.3.9.3.4 |
1,283 | 5.3.5.6.3 SRB addition/modification | The UE shall: 1> If any DAPS bearer is configured, for each SRB: 2> establish a PDCP entity for the target cell group as specified in TS 38.323[ NR; Packet Data Convergence Protocol (PDCP) specification ] [5], with the same configuration as the PDCP entity for the source cell group; 2> if the masterKeyUpdate is received: 3> configure the PDCP entity with the security algorithms according to securityConfig and apply the keys (KRRCenc and KRRCint) associated with the master key (KgNB); 2> else: 3> configure the PDCP entity for the target cell group with state variables continuation as specified in TS 38.323[ NR; Packet Data Convergence Protocol (PDCP) specification ] [5], and with the same security configuration as the PDCP entity for the source cell group; 1> for each srb-Identity value included in the srb-ToAddModList that is not part of the current UE configuration (SRB establishment or reconfiguration from E-UTRA PDCP to NR PDCP): 2> establish a PDCP entity; 2> if AS security has been activated: 3> if target RAT of handover is E-UTRA/5GC; or 3> if the UE is connected to E-UTRA/5GC: 4> if the UE is capable of E-UTRA/5GC, but not capable of NGEN-DC: 5> configure the PDCP entity with the security algorithms and keys (KRRCenc and KRRCint) configured/derived as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10]; 4> else (i.e., UE capable of NGEN-DC): 5> configure the PDCP entity with the security algorithms according to securityConfig and apply the keys (KRRCenc and KRRCint) associated with the master key (KeNB) or secondary key (S-KgNB) as indicated in keyToUse, if applicable; 3> else (i.e., UE connected to NR or UE connected to E-UTRA/EPC): 4> configure the PDCP entity with the security algorithms according to securityConfig and apply the keys (KRRCenc and KRRCint) associated with the master key (KeNB/ KgNB) or secondary key (S-KgNB) as indicated in keyToUse, if applicable; 2> if the current UE configuration as configured by E-UTRA in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10] includes an SRB identified with the same srb-Identity value: 3> associate the E-UTRA RLC entity and DCCH of this SRB with the NR PDCP entity; 3> release the E-UTRA PDCP entity of this SRB; 2> if the pdcp-Config is included: 3> configure the PDCP entity in accordance with the received pdcp-Config; 2> else: 3> configure the PDCP entity in accordance with the default configuration defined in 9.2.1 for the corresponding SRB; 1> if any DAPS bearer is configured, for each srb-Identity value included in the srb-ToAddModList that is part of the current UE configuration: 2> if the pdcp-Config is included: 3> reconfigure the PDCP entity for the target cell group in accordance with the received pdcp-Config; 1> else, for each srb-Identity value included in the srb-ToAddModList that is part of the current UE configuration: 2> if the reestablishPDCP is set: 3> if target RAT of handover is E-UTRA/5GC; or 3> if the UE is connected to E-UTRA/5GC: 4> if the UE is capable of E-UTRA/5GC, but not capable of NGEN-DC: 5> configure the PDCP entity to apply the integrity protection algorithm and KRRCint key configured/derived as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10], i.e. the integrity protection configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure; 5> configure the PDCP entity to apply the ciphering algorithm and KRRCenc key configured/derived as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10], i.e. the ciphering configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure; 4> else (i.e., a UE capable of NGEN-DC): 5> configure the PDCP entity to apply the integrity protection algorithm and KRRCint key associated with the master key (KeNB) or secondary key (S-KgNB), as indicated in keyToUse, i.e. the integrity protection configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure; 5> configure the PDCP entity to apply the ciphering algorithm and KRRCenc key associated with the master key (KeNB) or secondary key (S-KgNB) as indicated in keyToUse, i.e. the ciphering configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure; 3> else (i.e., UE connected to NR or UE in EN-DC): 4> configure the PDCP entity to apply the integrity protection algorithm and KRRCint key associated with the master key (KeNB/KgNB) or secondary key (S-KgNB), as indicated in keyToUse , i.e. the integrity protection configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure; 4> configure the PDCP entity to apply the ciphering algorithm and KRRCenc key associated with the master key (KeNB/KgNB) or secondary key (S-KgNB) as indicated in keyToUse, i.e. the ciphering configuration shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure; 3> re-establish the PDCP entity of this SRB as specified in TS 38.323[ NR; Packet Data Convergence Protocol (PDCP) specification ] [5]; 2> else, if the discardOnPDCP is set: 3> trigger the PDCP entity to perform SDU discard as specified in TS 38.323[ NR; Packet Data Convergence Protocol (PDCP) specification ] [5]; 2> if the pdcp-Config is included: 3> reconfigure the PDCP entity in accordance with the received pdcp-Config. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.5.6.3 |
1,284 | 4.15.4 User plane node management | A 5G system (5GS) can act as a user plane node of an external network (e.g. IEEE TSN bridge) or a 5GS can be independently used to enable TSC. For these purposes, information available at a UE is provided to the network and port management information containers are exchanged between a DS-TT and a TSN AF or a TSCTSF (see 3GPP TS 24.539[ 5G System (5GS); Network to TSN translator (TT) protocol aspects; Stage 3 ] [19BA]). During a UE-requested PDU session establishment procedure, if the UE supports transfer of port management information containers, then the UE indicates that transfer of port management information container is supported and the UE provides a DS-TT Ethernet port MAC address (if the PDU session type is Ethernet), port management information container, and a UE-DS-TT residence time (if available) to the network (see subclause 6.4.1.2). Once the UE has successfully established a PDU session and the UE has indicated that transfer of port management information container is supported during the UE-requested PDU session establishment procedure (see subclause 6.4.1.2), then port management information containers are exchanged via a UE-requested PDU session modification procedure and a network-requested PDU session modification procedure (see subclauses 6.3.2 and 6.4.2). The UE receiving a port management information container from the network shall forward the port management information container to the DS-TT. The SMF receiving a port management information container from the UE shall operate as described in 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9]. | 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.15.4 |
1,285 | Annex H (informative): Interworking between Network Operators and Application Providers for localized services | This clause illustrates examples of scenarios applicable for interworking between hosting network operators (PLMN or NPN) and data applications based on service agreements for localized services among network operators and application/service providers: Hosting network operator owns the 5G network which provides access and IP connectivity to serving UEs. Network operator owned application layer entities, e.g., including Service Hosting Environment, or IMS network. Application platforms in third party domain can be owned by third party application/service providers, or home/other network operators. The Application platforms could be application servers (e.g., Video on Demand Server, Cloud gaming server, etc.), 3rd party software development platforms, and third party/operator Service Hosting Environments. The following figures show the collaborative relationship in three domains including network operators providing access and IP connectivity, network operators providing services via IMS/application platforms, and application/service providers providing services via application platforms or applications. The dashed line between visited hosting network operator and Home network operator is based on service level localized service agreement and the horizontal line represents the demarcation between the network operator domains and the 3rd party domain. In an operator network, the application layer entities can include IMS network, Application platforms, and API Gateway for third party applications developed using APIs (e.g., REST, GSMA OneAPI). Figure H-1 provides the home operator owned/collaborative interworking scenarios where traffic is routed to home network operator and applications are delivered by the home operator via interworking agreements between network operators. Figure H-1: Home Operator owned/collaborative interworking scenario Home Routed NOTE: The other network operators and service/application operators in 3rd party domain provides collaborative services in application platforms to Home operator. The arrow solid line represents the traffics routed over domains within home operator network while the arrow dash lines represent the traffics routed over domains outside of home operator network. Figure H-2 provides hosting network operator owned and collaborative interworking scenarios between visited hosting network operator and operators in 3rd party domains where traffic is routed to application from the hosting network to 1) hosting network owned application platforms, 2) collaborative home network owned application platforms, and 3) third parties via interworking agreements between visited hosting network operator and home/other network operators, and between hosting network operator and other application/service providers. Figure H-2: Hosting Network Operator owned/collaborative interworking scenario Local Breakout NOTE: The other network operators and application/service operators in 3rd party domain provides collaborative services in application platform to hosting network operator and/or home network operator. The arrow solid lines represent the traffics routed over domains within hosting network while the arrow dash lines represent the traffics routed over domains outside of hosting operator network. Other interworking scenarios are not excluded. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | Annex |
1,286 | 10.5.6.5 Quality of service | The purpose of the quality of service information element is to specify the QoS parameters for a PDP context. The QoS IE is defined to allow backward compatibility to earlier version of Session Management Protocol. The quality of service is a type 4 information element with a minimum length of 14 octets and a maximum length of 22 octets. The QoS requested by the MS shall be encoded both in the QoS attributes specified in octets 3-5 and in the QoS attributes specified in octets 6-14. In the MS to network direction and in the network to MS direction the following applies: - Octets 15-22 are optional. If octet 15 is included, then octet 16 shall also be included, and octets 17-22may be included. - If octet 17 is included, then octet 18 shall also be included and octets 19-22 may be included. - If octet 19 is included, then octet 20 shall also be included, and octets 21 and 22 may be included. - If octet 21 is included, then octet 22 shall also be included. - A QoS IE received without octets 6-22, without octets 14-22, without octets 15-22, without octets 17-22, without octets 19-22 or without octets 21-22 shall be accepted by the receiving entity. NOTE: This behavior is required for interworking with entities supporting an earlier version of the protocol, or when the Maximum bit rate for downlink or for downlink and uplink is negotiated to a value lower than 8700 kbps. The quality of service information element is coded as shown in figure 10.5.138/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.156/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.138/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Quality of service information element Table 10.5.156/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Quality of service information element Reliability class, octet 3 (see 3GPP TS 23.107[ Quality of Service (QoS) concept and architecture ] [81]) Bits 3 2 1 In MS to network direction: 0 0 0 Subscribed reliability class In network to MS direction: 0 0 0 Reserved In MS to network direction and in network to MS direction: 0 0 1 Unused. If received, it shall be interpreted as '010' (Note) 0 1 0 Unacknowledged GTP; Acknowledged LLC and RLC, Protected data 0 1 1 Unacknowledged GTP and LLC; Acknowledged RLC, Protected data 1 0 0 Unacknowledged GTP, LLC, and RLC, Protected data 1 0 1 Unacknowledged GTP, LLC, and RLC, Unprotected data 1 1 1 Reserved All other values are interpreted as Unacknowledged GTP and LLC; Acknowledged RLC, Protected data in this version of the protocol. If network supports EPS, then it should not assign Reliability class value '010’. NOTE: this value was allocated in earlier versions of the protocol. Delay class, octet 3 (see 3GPP TS 22.060[ General Packet Radio Service (GPRS); Service description; Stage 1 ] [73] and 3GPP TS 23.107[ Quality of Service (QoS) concept and architecture ] [81]) Bits 6 5 4 In MS to network direction: 0 0 0 Subscribed delay class In network to MS direction: 0 0 0 Reserved In MS to network direction and in network to MS direction: 0 0 1 Delay class 1 0 1 0 Delay class 2 0 1 1 Delay class 3 1 0 0 Delay class 4 (best effort) 1 1 1 Reserved All other values are interpreted as Delay class 4 (best effort) in this version of the protocol. Bit 7 and 8 of octet 3 are spare and shall be coded all 0. Precedence class, octet 4 (see 3GPP TS 23.107[ Quality of Service (QoS) concept and architecture ] [81]) Bits 3 2 1 In MS to network direction: 0 0 0 Subscribed precedence In network to MS direction: 0 0 0 Reserved In MS to network direction and in network to MS direction: 0 0 1 High priority 0 1 0 Normal priority 0 1 1 Low priority 1 1 1 Reserved All other values are interpreted as Normal priority in this version of the protocol. Bit 4 of octet 4 is spare and shall be coded as 0. Peak throughput, octet 4 (see 3GPP TS 23.107[ Quality of Service (QoS) concept and architecture ] [81]) This field is the binary representation of the Peak Throughput Class (1 to 9). The corresponding peak throughput to each peak throughput class is indicated. Bits 8 7 6 5 In MS to network direction: 0 0 0 0 Subscribed peak throughput In network to MS direction: 0 0 0 0 Reserved In MS to network direction and in network to MS direction: 0 0 0 1 Up to 1 000 octet/s 0 0 1 0 Up to 2 000 octet/s 0 0 1 1 Up to 4 000 octet/s 0 1 0 0 Up to 8 000 octet/s 0 1 0 1 Up to 16 000 octet/s 0 1 1 0 Up to 32 000 octet/s 0 1 1 1 Up to 64 000 octet/s 1 0 0 0 Up to 128 000 octet/s 1 0 0 1 Up to 256 000 octet/s 1 1 1 1 Reserved All other values are interpreted as Up to 1 000 octet/s in this version of the protocol. Mean throughput, octet 5 (see 3GPP TS 23.107[ Quality of Service (QoS) concept and architecture ] [81]) This field is the binary representation of the Mean Throughput Class (1 to 18; mean throughput class 30 is reserved and 31 is best effort). The corresponding mean throughput to each mean throughput class is indicated. Bits 5 4 3 2 1 In MS to network direction: 0 0 0 0 0 Subscribed mean throughput In network to MS direction: 0 0 0 0 0 Reserved In MS to network direction and in network to MS direction: 0 0 0 0 1 100 octet/h 0 0 0 1 0 200 octet/h 0 0 0 1 1 500 octet/h 0 0 1 0 0 1 000 octet/h 0 0 1 0 1 2 000 octet/h 0 0 1 1 0 5 000 octet/h 0 0 1 1 1 10 000 octet/h 0 1 0 0 0 20 000 octet/h 0 1 0 0 1 50 000 octet/h 0 1 0 1 0 100 000 octet/h 0 1 0 1 1 200 000 octet/h 0 1 1 0 0 500 000 octet/h 0 1 1 0 1 1 000 000 octet/h 0 1 1 1 0 2 000 000 octet/h 0 1 1 1 1 5 000 000 octet/h 1 0 0 0 0 10 000 000 octet/h 1 0 0 0 1 20 000 000 octet/h 1 0 0 1 0 50 000 000 octet/h 1 1 1 1 0 Reserved 1 1 1 1 1 Best effort The value Best effort indicates that throughput shall be made available to the MS on a per need and availability basis. All other values are interpreted as Best effort in this version of the protocol. Bits 8 to 6 of octet 5 are spare and shall be coded all 0. Delivery of erroneous SDUs, octet 6 (see 3GPP TS 23.107[ Quality of Service (QoS) concept and architecture ] [81]) Bits 3 2 1 In MS to network direction: 0 0 0 Subscribed delivery of erroneous SDUs In network to MS direction: 0 0 0 Reserved In MS to network direction and in network to MS direction: 0 0 1 No detect ('-') 0 1 0 Erroneous SDUs are delivered ('yes') 0 1 1 Erroneous SDUs are not delivered ('no') 1 1 1 Reserved The network shall map all other values not explicitly defined onto one of the values defined in this version of the protocol. The network shall return a negotiated value which is explicitly defined in this version of this protocol. The MS shall consider all other values as reserved. Delivery order, octet 6 (see 3GPP TS 23.107[ Quality of Service (QoS) concept and architecture ] [81]) Bits 5 4 3 In MS to network direction: 0 0 Subscribed delivery order In network to MS direction: 0 0 Reserved In MS to network direction and in network to MS direction: 0 1 With delivery order ('yes') 1 0 Without delivery order ('no') 1 1 Reserved Traffic class, octet 6 (see 3GPP TS 23.107[ Quality of Service (QoS) concept and architecture ] [81]) Bits 8 7 6 In MS to network direction: 0 0 0 Subscribed traffic class In network to MS direction: 0 0 0 Reserved In MS to network direction and in network to MS direction: 0 0 1 Conversational class 0 1 0 Streaming class 0 1 1 Interactive class 1 0 0 Background class 1 1 1 Reserved The network shall map all other values not explicitly defined onto one of the values defined in this version of the protocol. The network shall return a negotiated value which is explicitly defined in this version of this protocol. The MS shall consider all other values as reserved. Maximum SDU size, octet 7 (see 3GPP TS 23.107[ Quality of Service (QoS) concept and architecture ] [81]) In MS to network direction: 0 0 0 0 0 0 0 0 Subscribed maximum SDU size 1 1 1 1 1 1 1 1 Reserved In network to MS direction: 0 0 0 0 0 0 0 0 Reserved 1 1 1 1 1 1 1 1 Reserved In MS to network direction and in network to MS direction: For values in the range 00000001 to 10010110 the Maximum SDU size value is binary coded in 8 bits, using a granularity of 10 octets, giving a range of values from 10 octets to 1500 octets. Values above 10010110 are as below: 1 0 0 1 0 1 1 1 1502 octets 1 0 0 1 1 0 0 0 1510 octets 1 0 0 1 1 0 0 1 1520 octets The network shall map all other values not explicitly defined onto one of the values defined in this version of the protocol. The network shall return a negotiated value which is explicitly defined in this version of this protocol. The MS shall consider all other values as reserved. Maximum bit rate for uplink, octet 8 Bits 8 7 6 5 4 3 2 1 In MS to network direction: 0 0 0 0 0 0 0 0 Subscribed maximum bit rate for uplink In network to MS direction: 0 0 0 0 0 0 0 0 Reserved In MS to network direction and in network to MS direction: 0 0 0 0 0 0 0 1 The maximum bit rate is binary coded in 8 bits, using a granularity of 1 kbps 0 0 1 1 1 1 1 1 giving a range of values from 1 kbps to 63 kbps in 1 kbps increments. 0 1 0 0 0 0 0 0 The maximum bit rate is 64 kbps + ((the binary coded value in 8 bits –01000000) * 8 kbps) 0 1 1 1 1 1 1 1 giving a range of values from 64 kbps to 568 kbps in 8 kbps increments. 1 0 0 0 0 0 0 0 The maximum bit rate is 576 kbps + ((the binary coded value in 8 bits –10000000) * 64 kbps) 1 1 1 1 1 1 1 0 giving a range of values from 576 kbps to 8640 kbps in 64 kbps increments. 1 1 1 1 1 1 1 1 0kbps If the sending entity wants to indicate a Maximum bit rate for uplink higher than 8640 kbps, it shall set octet 8 to "11111110", i.e. 8640 kbps, and shall encode the value for the Maximum bit rate in octet 17. The network shall map all other values not explicitly defined onto one of the values defined in this version of the protocol. The network shall return a negotiated value which is explicitly defined in this version of the protocol. Maximum bit rate for downlink, octet 9 (see 3GPP TS 23.107[ Quality of Service (QoS) concept and architecture ] [81]) Coding is identical to that of Maximum bit rate for uplink. If the sending entity wants to indicate a Maximum bit rate for downlink higher than 8640 kbps, it shall set octet 9 to "11111110", i.e. 8640 kbps, and shall encode the value for the Maximum bit rate in octet 15. The network shall map all other values not explicitly defined onto one of the values defined in this version of the protocol. The network shall return a negotiated value which is explicitly defined in this version of the protocol. In this version of the protocol, for messages specified in the present document, the sending entity shall not request 0 kbps for both the Maximum bitrate for downlink and the Maximum bitrate for uplink at the same time. Any entity receiving a request for 0 kbps in both the Maximum bitrate for downlink and the Maximum bitrate for uplink shall consider that as a syntactical error (see clause 8). Residual Bit Error Rate (BER), octet 10 (see 3GPP TS 23.107[ Quality of Service (QoS) concept and architecture ] [81]) Bits 8 7 6 5 In MS to network direction: 0 0 0 0 Subscribed residual BER In network to MS direction: 0 0 0 0 Reserved In MS to network direction and in network to MS direction: The Residual BER value consists of 4 bits. The range is from 5*10-2 to 6*10-8. 0 0 0 1 5*10-2 0 0 1 0 1*10-2 0 0 1 1 5*10-3 0 1 0 0 4*10-3 0 1 0 1 1*10-3 0 1 1 0 1*10-4 0 1 1 1 1*10-5 1 0 0 0 1*10-6 1 0 0 1 6*10-8 1 1 1 1 Reserved The network shall map all other values not explicitly defined onto one of the values defined in this version of the protocol. The network shall return a negotiated value which is explicitly defined in this version of the protocol. The MS shall consider all other values as reserved. SDU error ratio, octet 10 (see 3GPP TS 23.107[ Quality of Service (QoS) concept and architecture ] [81]) Bits 4 3 2 1 In MS to network direction: 0 0 0 0 Subscribed SDU error ratio In network to MS direction: 0 0 0 0 Reserved In MS to network direction and in network to MS direction: The SDU error ratio value consists of 4 bits. The range is is from 1*10-1 to 1*10-6. 0 0 0 1 1*10-2 0 0 1 0 7*10-3 0 0 1 1 1*10-3 0 1 0 0 1*10-4 0 1 0 1 1*10-5 0 1 1 0 1*10-6 0 1 1 1 1*10-1 1 1 1 1 Reserved The network shall map all other values not explicitly defined onto one of the values defined in this version of the protocol. The network shall return a negotiated value which is explicitly defined in this version of the protocol. The MS shall consider all other values as reserved. Traffic handling priority, octet 11 (see 3GPP TS 23.107[ Quality of Service (QoS) concept and architecture ] [81]) Bits 2 1 In MS to network direction: 0 0 Subscribed traffic handling priority In network to MS direction: 0 0 Reserved In MS to network direction and in network to MS direction: 0 1 Priority level 1 1 0 Priority level 2 1 1 Priority level 3 The Traffic handling priority value is ignored if the Traffic Class is Conversational class, Streaming class or Background class. Transfer delay, octet 11 (See 3GPP TS 23.107[ Quality of Service (QoS) concept and architecture ] [81]) Bits 8 7 6 5 4 3 In MS to network direction: 0 0 0 0 0 0 Subscribed transfer delay In network to MS direction: 0 0 0 0 0 0 Reserved In MS to network direction and in network to MS direction: 0 0 0 0 0 1 The Transfer delay is binary coded in 6 bits, using a granularity of 10 ms 0 0 1 1 1 1 giving a range of values from 10 ms to 150 ms in 10 ms increments 0 1 0 0 0 0 The transfer delay is 200 ms + ((the binary coded value in 6 bits – 010000) * 50 ms) 0 1 1 1 1 1 giving a range of values from 200 ms to 950 ms in 50ms increments 1 0 0 0 0 0 The transfer delay is 1000 ms + ((the binary coded value in 6 bits – 100000) * 100 ms) 1 1 1 1 1 0 giving a range of values from 1000 ms to 4000 ms in 100ms increments 1 1 1 1 1 1 Reserved The Transfer delay value is ignored if the Traffic Class is Interactive class or Background class. Guaranteed bit rate for uplink, octet 12 (See 3GPP TS 23.107[ Quality of Service (QoS) concept and architecture ] [81]) Coding is identical to that of Maximum bit rate for uplink. If the sending entity wants to indicate a Guaranteed bit rate for uplink higher than 8640 kbps, it shall set octet 12 to "11111110", i.e. 8640 kbps, and shall encode the value for the Guaranteed bit rate in octet 18. The network shall map all other values not explicitly defined onto one of the values defined in this version of the protocol. The network shall return a negotiated value which is explicitly defined in this version of the protocol. The Guaranteed bit rate for uplink value is ignored if the Traffic Class is Interactive class or Background class, or Maximum bit rate for uplink is set to 0 kbps. Guaranteed bit rate for downlink, octet 13(See 3GPP TS 23.107[ Quality of Service (QoS) concept and architecture ] [81]) Coding is identical to that of Maximum bit rate for uplink. If the sending entity wants to indicate a Guaranteed bit rate for downlink higher than 8640 kbps, it shall set octet 13 to "11111110", i.e. 8640 kbps, and shall encode the value for the Guaranteed bit rate in octet 16. The network shall map all other values not explicitly defined onto one of the values defined in this version of the protocol. The network shall return a negotiated value which is explicitly defined in this version of the protocol. The Guaranteed bit rate for downlink value is ignored if the Traffic Class is Interactive class or Background class, or Maximum bit rate for downlink is set to 0 kbps. Source Statistics Descriptor, octet 14 (see 3GPP TS 23.107[ Quality of Service (QoS) concept and architecture ] [81]) Bits 4 3 2 1 In MS to network direction 0 0 0 0 unknown 0 0 0 1 speech The network shall consider all other values as unknown. In network to MS direction Bits 4 to 1 of octet 14 are spare and shall be coded all 0. The Source Statistics Descriptor value is ignored if the Traffic Class is Interactive class or Background class. Signalling Indication, octet 14 (see 3GPP TS 23.107[ Quality of Service (QoS) concept and architecture ] [81]) Bit 5 In MS to network direction and in network to MS direction: 0 Not optimised for signalling traffic 1 Optimised for signalling traffic If set to '1' the QoS of the PDP context is optimised for signalling The Signalling Indication value is ignored if the Traffic Class is Conversational class, Streaming class or Background class. Bits 8 to 6 of octet 14 are spare and shall be coded all 0. Maximum bit rate for downlink (extended), octet 15 Bits 8 7 6 5 4 3 2 1 In MS to network direction and in network to MS direction: 0 0 0 0 0 0 0 0 Use the value indicated by the Maximum bit rate for downlink in octet 9. For all other values: Ignore the value indicated by the Maximum bit rate for downlink in octet 9 and use the following value: 0 0 0 0 0 0 0 1 The maximum bit rate is 8600 kbps + ((the binary coded value in 8 bits) * 100 kbps), 0 1 0 0 1 0 1 0 giving a range of values from 8700 kbps to 16000 kbps in 100 kbps increments. 0 1 0 0 1 0 1 1 The maximum bit rate is 16 Mbps + ((the binary coded value in 8 bits - 01001010) * 1 Mbps), 1 0 1 1 1 0 1 0 giving a range of values from 17 Mbps to 128 Mbps in 1 Mbps increments. 1 0 1 1 1 0 1 1 The maximum bit rate is 128 Mbps + ((the binary coded value in 8 bits - 10111010) * 2 Mbps), 1 1 1 1 1 0 1 0 giving a range of values from 130 Mbps to 256 Mbps in 2 Mbps increments. If the sending entity wants to indicate a Maximum bit rate for downlink higher than 256 Mbps, it shall set octet 15 to "11111010", i.e. 256 Mbps, and shall encode the value for the maximum bit rate in octet 19. The network shall map all other values not explicitly defined onto one of the values defined in this version of the protocol. The network shall return a negotiated value which is explicitly defined in this version of the protocol. Guaranteed bit rate for downlink (extended), octet 16 Bits 8 7 6 5 4 3 2 1 In MS to network direction and in network to MS direction: 0 0 0 0 0 0 0 0 Use the value indicated by the Guaranteed bit rate for downlink in octet 13. For all other values: Ignore the value indicated by the Guaranteed bit rate for downlink in octet 9 and use the following value: 0 0 0 0 0 0 0 1 The guaranteed bit rate is 8600 kbps + ((the binary coded value in 8 bits) * 100 kbps), 0 1 0 0 1 0 1 0 giving a range of values from 8700 kbps to 16000 kbps in 100 kbps increments. 0 1 0 0 1 0 1 1 The guaranteed bit rate is 16 Mbps + ((the binary coded value in 8 bits - 01001010) * 1 Mbps), 1 0 1 1 1 0 1 0 giving a range of values from 17 Mbps to 128 Mbps in 1 Mbps increments. 1 0 1 1 1 0 1 1 The guaranteed bit rate is 128 Mbps + ((the binary coded value in 8 bits - 10111010) * 2 Mbps), 1 1 1 1 1 0 1 0 giving a range of values from 130 Mbps to 256 Mbps in 2 Mbps increments. If the sending entity wants to indicate a Guaranteed bit rate for downlink higher than 256 Mbps, it shall set octet 16 to "11111010", i.e. 256 Mbps, and shall encode the value for the guaranteed bit rate in octet 20. The network shall map all other values not explicitly defined onto one of the values defined in this version of the protocol. The network shall return a negotiated value which is explicitly defined in this version of the protocol. Maximum bit rate for uplink (extended), octet 17 This field is an extension of the Maximum bit rate for uplink in octet 8. The coding is identical to that of the Maximum bit rate for downlink (extended). If the sending entity wants to indicate a Maximum bit rate for uplink higher than 256 Mbps, it shall set octet 17 to "11111010", i.e. 256 Mbps, and shall encode the value for the maximum bit rate in octet 21. The network shall map all other values not explicitly defined onto one of the values defined in this version of the protocol. The network shall return a negotiated value which is explicitly defined in this version of the protocol. Guaranteed bit rate for uplink (extended), octet 18 This field is an extension of the Guaranteed bit rate for uplink in octet 12. The coding is identical to that of the Guaranteed bit rate for downlink (extended). If the sending entity wants to indicate a Guaranteed bit rate for uplink higher than 256 Mbps, it shall set octet 18 to "11111010", i.e. 256 Mbps, and shall encode the value for the guaranteed bit rate in octet 22. The network shall map all other values not explicitly defined onto one of the values defined in this version of the protocol. The network shall return a negotiated value which is explicitly defined in this version of the protocol. Maximum bit rate for downlink (extended-2), octet 19 Bits 8 7 6 5 4 3 2 1 In MS to network direction and in network to MS direction: 0 0 0 0 0 0 0 0 Use the value indicated by the Maximum bit rate for downlink in octet 9 and octet 15. For all other values: Ignore the value indicated by the Maximum bit rate for downlink in octet 9 and octet 15 and use the following value: 0 0 0 0 0 0 0 1 The maximum bit rate is 256 Mbps + ((the binary coded value in 8 bits) * 4 Mbps), 0 0 1 1 1 1 0 1 giving a range of values from 260 Mbps to 500 Mbps in 4 Mbps increments. 0 0 1 1 1 1 1 0 The maximum bit rate is 500 Mbps + ((the binary coded value in 8 bits - 00111101) * 10 Mbps), 1 0 1 0 0 0 0 1 giving a range of values from 510 Mbps to 1500 Mbps in 10 Mbps increments. 1 0 1 0 0 0 1 0 The maximum bit rate is 1500 Mbps + ((the binary coded value in 8 bits - 10100001) * 100 Mbps), 1 1 1 1 0 1 1 0 giving a range of values from 1600 Mbps to 10 Gbps in 100 Mbps increments. If the sending entity wants to indicate a Maximum bit rate for downlink higher than 10 Gbps, it shall set octet 19 to "11110110", i.e. 10 Gbps, and shall encode the value for the maximum bit rate in the extended quality of service information element specified in subclause 10.5.6.5B. The network shall map all other values not explicitly defined onto one of the values defined in this version of the protocol. The network shall return a negotiated value which is explicitly defined in this version of the protocol. The MS shall map all other values not explicitly defined onto the maximum value defined in this version of the protocol. Guaranteed bit rate for downlink (extended-2), octet 20 Bits 8 7 6 5 4 3 2 1 In MS to network direction and in network to MS direction: 0 0 0 0 0 0 0 0 Use the value indicated by the Maximum bit rate for downlink in octet 13 and octet 16. For all other values: Ignore the value indicated by the Maximum bit rate for downlink in octet 13 and octet 16 and use the following value: 0 0 0 0 0 0 0 1 The guaranteed bit rate is 256 Mbps + ((the binary coded value in 8 bits) * 4 Mbps), 0 0 1 1 1 1 0 1 giving a range of values from 260 Mbps to 500 Mbps in 4 Mbps increments. 0 0 1 1 1 1 1 0 The guaranteed bit rate is 500 Mbps + ((the binary coded value in 8 bits - 00111101) * 10 Mbps), 1 0 1 0 0 0 0 1 giving a range of values from 510 Mbps to 1500 Mbps in 10 Mbps increments. 1 0 1 0 0 0 1 0 The guaranteed bit rate is 1500 Mbps + ((the binary coded value in 8 bits - 10100001) * 100 Mbps), 1 1 1 1 0 1 1 0 giving a range of values from 1600 Mbps to 10 Gbps in 100 Mbps increments. If the sending entity wants to indicate a Guaranteed bit rate for downlink higher than 10 Gbps, it shall set octet 20 to "11110110", i.e. 10 Gbps, and shall encode the value for the guaranteed bit rate in the extended quality of service information element specified in subclause 10.5.6.5B. The network shall map all other values not explicitly defined onto one of the values defined in this version of the protocol. The network shall return a negotiated value which is explicitly defined in this version of the protocol. The MS shall map all other values not explicitly defined onto the maximum value defined in this version of the protocol. Maximum bit rate for uplink (extended-2), octet 21 This field is an extension of the Maximum bit rate for uplink in octet 17. The coding is identical to that of the Maximum bit rate for downlink (extended 2). If the sending entity wants to indicate a Maximum bit rate for uplink higher than 10 Gbps, it shall set octet 21 to "11110110", i.e. 10 Gbps, and shall encode the value for the maximum bit rate in the extended quality of service information element specified in subclause 10.5.6.5B. The network shall map all other values not explicitly defined onto one of the values defined in this version of the protocol. The network shall return a negotiated value which is explicitly defined in this version of the protocol. The MS shall map all other values not explicitly defined onto the maximum value defined in this version of the protocol. Guaranteed bit rate for uplink (extended-2), octet 22 This field is an extension of the Guaranteed bit rate for uplink in octet 18. The coding is identical to that of the Guaranteed bit rate for downlink (extended-2). If the sending entity wants to indicate a Guaranteed bit rate for uplink higher than 10 Gbps, it shall set octet 22 to "11110110", i.e. 10 Gbps, and shall encode the value for the guaranteed bit rate in the extended quality of service information element specified in subclause 10.5.6.5B. The network shall map all other values not explicitly defined onto one of the values defined in this version of the protocol. The network shall return a negotiated value which is explicitly defined in this version of the protocol. The MS shall map all other values not explicitly defined onto the maximum value defined in this version of the protocol. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.6.5 |
1,287 | 13 Detection and handling of late arriving requests 13.1 General | The procedures specified in this clause aim at handling more efficiently requests which may arrive late at upstreams entities, e.g. in networks experiencing processing or transport delays. These procedures are optional to support. When supported, the use of these procedures is dependent on operator policy. The procedure specified in clause 13.2 may be used with or without the procedure specified in clause 13.3. The procedure specified in clause 13.3 shall only be used in conjunction with the procedure specified in clause 13.2. | 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 | 13 |
1,288 | 9.3.1.1.4 TDD (CSI measurements in case two CSI subframe sets are configured and with CRS assistance information) | For the parameters specified in Table 9.3.1.1.4-1, and using the downlink physical channels specified in Annex C.3.2, the minimum requirements are specified in Table 9.3.1.1.4-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 in ABS subframes 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 in ABS subframes for the indicated transport formats shall be greater than or equal to ε. 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.4-1: Sub-band test for single antenna transmission (TDD) Table 9.3.1.1.4-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.4 |
1,289 | 2.1.2 Vocabulary | For the purposes of the present document, the following terms and definitions apply: - A GSM security context is established and stored in the MS and the network as a result of a successful execution of a GSM authentication challenge. The GSM security context for the CS domain consists of the GSM ciphering key and the ciphering key sequence number. The GSM security context for the PS domain consists of the GPRS GSM ciphering key and the GPRS ciphering key sequence number. - A UMTS security context is established and stored in the MS and the network as a result of a successful execution of a UMTS authentication challenge. The UMTS security context for the CS domain consists of the UMTS ciphering key, the UMTS integrity key, the GSM ciphering key, the ciphering key sequence number and the GSM Kc128 (if an A5 ciphering algorithm that requires a 128-bit ciphering key is in use). The UMTS security context for the PS domain consists of the GPRS UMTS ciphering key, the GPRS UMTS integrity key, the GPRS GSM ciphering key, the GPRS ciphering key sequence number, the GPRS GSM Kc128 (if a GEA ciphering algorithm that requires a 128-bit ciphering key is in use) and the GPRS GSM Kint (if a GIA integrity algorithm that requires a 128-bit integrity key is in use). - An MS is attached for emergency bearer services if it has successfully completed an attach for emergency bearer services or if it has only a PDN connection for emergency bearer services established. - idle mode: In this mode, the mobile station is not allocated any dedicated channel; it listens to the CCCH and the BCCH; - group receive mode: (Only applicable for mobile stations supporting VGCS listening or VBS listening) In this mode, the mobile station is not allocated a dedicated channel with the network; it listens to the downlink of a voice broadcast channel or voice group call channel allocated to the cell. Occasionally, the mobile station has to listen to the BCCH of the serving cell as defined in 3GPP TS 43.022[ None ] [82] and 3GPP TS 45.008[ None ] [34]; - dedicated mode: In this mode, the mobile station is allocated at least two dedicated channels, only one of them being a SACCH; - EAB: Extended Access Barring, see 3GPP TS 22.011[ Service accessibility ] [138]. - group transmit mode: (Only applicable for mobile stations supporting VGCS talking) In this mode, one mobile station of a voice group call is allocated two dedicated channels, one of them being a SACCH. These channels can be allocated to one mobile station at a time but to different mobile stations during the voice group call; - packet idle mode: (only applicable for mobile stations supporting GPRS) In this mode, mobile station is not allocated any radio resource on a packet data physical channel; it listens to the BCCH and the CCCH, see 3GPP TS 44.060[ None ] [76]. - packet transfer mode: (only applicable for mobile stations supporting GPRS) In this mode, the mobile station is allocated radio resource on one or more packet data physical channels for the transfer of LLC PDUs. - main DCCH: In dedicated mode and group transmit mode, only two channels are used as DCCH, one being a SACCH, the other being a SDCCH or a FACCH; the SDCCH or FACCH is called here "the main DCCH"; - A channel is activated if it can be used for transmission, in particular for signalling, at least with UI frames. On the SACCH, whenever activated, it must be ensured that a contiguous stream of layer 2 frames is sent; - A TCH is connected if circuit mode user data can be transferred. A TCH cannot be connected if it is not activated. A TCH which is activated but not connected is used only for signalling, i.e. as a DCCH; - The data link of SAPI 0 on the main DCCH is called the main signalling link. Any message specified to be sent on the main signalling link is sent in acknowledged mode except when otherwise specified; - The term "to establish" a link is a short form for "to establish the multiframe mode" on that data link. It is possible to send UI frames on a data link even if it is not established as soon as the corresponding channel is activated. Except when otherwise indicated, a data link layer establishment is done without an information field. - "channel set" is used to identify TCHs that carry related user information flows, e.g., in a multislot configuration used to support circuit switched connection(s), which therefore need to be handled together. - A temporary block flow (TBF) is a physical connection used by the two RR peer entities to support the uni-directional transfer of LLC PDUs on packet data physical channels, see 3GPP TS 44.060[ None ] [76]. - RLC/MAC block: A RLC/MAC block is the protocol data unit exchanged between RLC/MAC entities, see 3GPP TS 44.060[ None ] [76]. - A GMM context is established when a GPRS attach procedure is successfully completed. - Network operation mode The network operation modes I and II are defined in 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [74]. The network operation mode shall be indicated as system information. For proper operation, the network operation mode should be the same in each cell of one routing area. - GAN mode: See 3GPP TS 43.318[ None ] [75a]. - GPRS MS operation mode The three different GPRS MS operation modes A, B, and C are defined in 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [74]. - RR connection: A RR connection is a dedicated physical circuit switched domain connection used by the two RR or RRC peer entities to support the upper layers' exchange of information flows. - PS signalling connection is a peer to peer Iu mode connection between MS and CN packet domain node. - Inter-system change is a change of an MS from A/Gb mode to Iu mode of operation or vice versa, or from S1 mode to A/Gb mode or Iu mode of operation. - GPRS: Packet services for systems which operate the Gb or Iu-PS interfaces. - GSM ciphering key: A 64-bit CS GSM ciphering key - GSM Kc128: A 128-bit CS GSM ciphering key - GPRS GSM ciphering key: A 64-bit PS GSM ciphering key - GPRS GSM Kc128: A 128-bit PS GSM ciphering key - GPRS GSM Kint: A 128-bit PS GSM integrity key. - The label (A/Gb mode only) indicates this section or paragraph applies only to a system which operates in A/Gb mode, i.e. with a functional division that is in accordance with the use of an A or a Gb interface between the radio access network and the core network. For multi system case this is determined by the current serving radio access network. - The label (Iu mode only) indicates this section or paragraph applies only to a system which operates in UTRAN Iu mode , i.e. with a functional division that is in accordance with the use of an Iu-CS or Iu-PS interface between the radio access network and the core network. For multi system case this is determined by the current serving radio access network. - In A/Gb mode,... Indicates this paragraph applies only to a system which operates in A/Gb mode. For multi system case this is determined by the current serving radio access network. - In Iu mode,... Indicates this paragraph applies only to a system which operates in UTRAN Iu mode. For multi system case this is determined by the current serving radio access network. - In A/Gb mode and GERAN Iu mode,... Indicates this paragraph applies only to a system which operates in A/Gb mode or GERAN Iu mode. For multi system case this is determined by the current serving radio access network. - In UTRAN Iu mode,... Indicates this paragraph applies only to a system which operates in UTRAN Iu mode. For multi system case this is determined by the current serving radio access network. - In a shared network,... Indicates this paragraph applies only to a shared network. For the definition of shared network see 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14]. NOTE: A shared network is applicable to GERAN and UTRAN, however, according to this definition, a multi-operator core network (MOCN) with common GERAN is not considered a shared network in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14] and in the present specification. - Multi-Operator Core Network (MOCN) with common GERAN: a network in which different core network operators are connected to a shared GERAN broadcasting only a single, common PLMN identity. - Chosen PLMN: The same as selected PLMN as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14]. - A default PDP context is a PDP context activated by the PDP context activation procedure that establishes a PDN connection. The default PDP context remains active during the lifetime of the PDN connection. - A PDP context for emergency bearer services is a default PDP context which was activated with request type "emergency", or any secondary PDP contexts associated to this default PDP context. - Non-emergency PDP context: Any PDP context which is not a PDP context for emergency bearer services. - SIM, Subscriber Identity Module (see 3GPP TS 42.017[ Subscriber Identity Module (SIM); Functional characteristics ] [7]). - USIM, Universal Subscriber Identity Module (see 3GPP TS 21.111[ USIM and IC card requirements ] [101]). - MS, Mobile Station. The present document makes no distinction between MS and UE. - MS configured for dual priority: An MS which provides dual priority support is configured for NAS signalling low priority and also configured to override the NAS signalling low priority indicator (see 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [135], 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [112]). - Cell Notification is an (optimised) variant of the Cell Update Procedure which uses the LLC NULL frame for cell change notification which does not trigger the restart of the READY timer - DTM: Dual Transfer Mode, see 3GPP TS 44.018[ None ] [84] and 3GPP TS 43.055[ None ] [87] - The term "eCall only" applies to a mobile station which is in the eCall only mode, as described in 3GPP TS 22.101[ Service aspects; Service principles ] [8]. - "removal of eCall only restriction" means that all the limitations as described in 3GPP TS 22.101[ Service aspects; Service principles ] [8] for the eCall only mode do not apply any more. - "SMS-only service": A subset of services which includes only short message service. The MS can request "SMS-only service" in order to obtain SMS. - Access domain selection: The process to select whether the CS domain or the IMS/IP-CAN is used to transmit the call control signalling between MS and core network. Definition derived from 3GPP TS 23.221[ Architectural requirements ] [131]. - APN based congestion control: Congestion control in session management where the network can reject session management requests from MSs or deactivate PDP contexts when the associated APN is congested. - NAS level mobility management congestion control: Congestion control mechanism in the network in mobility management. "NAS level mobility management congestion control" consists of "subscribed APN based congestion control" and "general NAS level mobility management congestion control". - General NAS level mobility management congestion control: The type of congestion control that is applied at a general overload or congestion situation in the network, e.g. lack of processing resources. - Group specific session management congestion control: Type of congestion control at session management level that is applied to reject session management requests from MSs belonging to a particular group when one or more group congestion criteria as specified in 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [74] are met. - Subscribed APN based congestion control: Congestion control in mobility management where the network can reject attach requests from MSs with a certain APN in the subscription. - Mapped P-TMSI: A P-TMSI which is mapped from a GUTI previously allocated to the MS by an . Mapping rules are defined in 3GPP TS 23.003[ Numbering, addressing and identification ] [10]. Definition derived from 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [122]. - Native P-TMSI: A P-TMSI previously allocated by an SGSN. Definition derived from 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [122]. - Valid LAI: A LAI that is not deleted LAI. - EMM Combined UE Waiting Flag: See 3GPP TS 29.018[ General Packet Radio Service (GPRS); Serving GPRS Support Node (SGSN) - Visitors Location Register (VLR); Gs interface layer 3 specification ] [149]. - Power Saving Mode: Power saving mode allows the MS to reduce its power consumption. When power saving mode is active in the MS, the MS is registered to the network and in PMM-IDLE mode (in Iu mode), EMM-IDLE mode (in S1 mode) or the READY timer is not running (in A/Gb mode) but the AS layer is deactivated. Definition derived from 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [74] and 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [122]. - ACDC: Application specific Congestion control for Data Communication, see 3GPP TS 22.011[ Service accessibility ] [138]. - Highest ranked ACDC category: The ACDC category with the lowest value as defined in 3GPP TS 24.105[ Application specific Congestion control for Data Communication (ACDC) Management Object (MO) ] [154]. - Extended idle-mode DRX cycle: Extended idle-mode DRX cycle allows the MS to reduce its power consumption in PMM-IDLE mode (in Iu mode) or when the READY timer is not running (in A/Gb mode) or in EMM-IDLE mode (in S1 mode). Extended idle-mode DRX cycle is associated with the eDRX cycle value. Definition derived from 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [74] and 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [122]. - EC-GSM-IoT: Extended coverage in GSM for IoT is a feature which enables extended coverage operation. See 3GPP TS 43.064[ None ] [159]. For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [122], subclause 3.2, apply: DCN-ID Globally Unique MME Identifier (GUMMEI) Globally Unique Temporary Identity (GUTI) Idle Mode Signalling Reduction (ISR) M-Temporary Mobile Subscriber Identity (M-TMSI) NarrowBand-IoT PDN connection Tracking Area Identity (TAI) Temporary Identity used in Next update (TIN) For the purposes of the present document, the following terms and definitions given in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] apply: CSG cell CSG ID CSG selection EMM EMM-IDLE mode EPS ESM In NB-S1 mode In WB-S1 mode LIPA PDN connection MO MMTEL voice call is started MO MMTEL video call is started MO SMSoIP is started MS configured to use AC11 – 15 in selected PLMN: see UE configured to use AC11 – 15 in selected PLMN PDN connection for emergency bearer services S1 mode SIPTO at the local network PDN connection SIPTO at the local network PDN connection with collocated L-GW SIPTO at the local network PDN connection with stand-alone GW For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.272[ Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2 ] [133] apply: CS fallback SMS over SGs For the purposes of the present document, the following terms and definitions given in 3GPP TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [123] apply: Current EPS security context Mapped security context eKSI CK' and IK' NAS downlink COUNT NAS uplink COUNT For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.251[ Network sharing; Architecture and functional description ] [109] apply: Multi-Operator Core Network (MOCN) Network Sharing non-supporting MS: see non-supporting UE. Network Sharing supporting MS: see supporting UE. For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14] apply: Country EHPLMN HPLMN Suitable Cell VPLMN For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.216[ Single Radio Voice Call Continuity (SRVCC); Stage 2 ] [126] apply: SRVCC vSRVCC CS to PS SRVCC For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.251[ Network sharing; Architecture and functional description ] [109] and 3GPP TS 44.018[ None ] [84] apply: Common PLMN For the purposes of the present document, the following terms and definitions given in 3GPP TS 44.018[ None ] [84] apply: Additional PLMN Network sharing For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.003[ Numbering, addressing and identification ] [10] apply: Local Home Network Identifier For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.161[ Network-Based IP Flow Mobility (NBIFOM); Stage 2 ] [155] apply: RAN rules handling parameter For the purposes of the present document, the following terms and definitions given in 3GPP TS 24.302[ Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networks; Stage 3 ] [156] apply: move-traffic-to-WLAN indication move-traffic-from-WLAN indication For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [74] apply: Dedicated core network For the purposes of the present document, the following terms and definitions given in 3GPP TS 24.161[ Network-Based IP Flow Mobility (NBIFOM); Stage 3 ] [158] apply: NBIFOM multi-access PDN connection For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.167[ IP Multimedia Subsystem (IMS) emergency sessions ] [160] apply: eCall over IMS For the purposes of the present document, the following terms and definitions given in 3GPP TS 22.101[ Service aspects; Service principles ] [8] apply: Minimum Set of Data (MSD) For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [166] apply: NG-RAN For the purposes of the present document, the following terms and definitions given in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [167] apply: 5GCN 5GMM 5GS 5GSM DNN DNN based congestion control In NB-N1 mode In WB-N1 mode N1 mode Service-level-AA For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.221[ Architectural requirements ] [131] apply: Restricted local operator services For the purposes of the present document, the following terms and definitions given in 3GPP TS 23.038[ Alphabets and language-specific information ] [8b] apply: <CR> | 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 | 2.1.2 |
1,290 | 5.2.3.5.2 Nudm_EventExposure_Subscribe service operation | Service operation name: Nudm_EventExposure_Subscribe Description: The NF consumer subscribes to receive an event. NF Consumers: NEF, SMS-GMSC. Inputs, Required: Target of Event Reporting: UE(s) ID (SUPI or GPSI, Internal Group Identifier or External Group Identifier, or indication that any UE is targeted), Event filter containing the Event Id(s) (see clause 4.15.3.1) and Event Reporting Information defined in Table 4.15.1-1. Inputs, Optional: Expiry time, DNN, S-NSSAI, traffic descriptor identifying the source of the downlink IP or Ethernet traffic (for Availability after DDN Failure and downlink data delivery status events), MTC Provider Information, list of group member UE(s) whose subscription to event notification(s) are removed or added for a group-based event notification subscription, operation indication (cancellation or addition), Idle Status Indication request (if UE reachability or Availability after DDN failure reporting is requested). For configuration of monitoring events applicable to both EPC and 5GC, a combined SCEF+NEF indicates that the monitoring event is also applicable to EPC (i.e. the event must be reported both by 5GC and EPC) and may include a SCEF address (i.e. if the event needs to be configured in a serving node in the EPC and the corresponding notification needs to be sent directly to the SCEF). Outputs, Required: Operation execution result indication. When the subscription is accepted: Subscription Correlation ID, Expiry time (required if the subscription can be expired based on the operator's policy). Outputs, Optional: First corresponding event report is included, if corresponding information is available (see clause 4.15.1), Number of UE if the External Group Identifier and Maximum Number of Reports are included in the inputs. Number of UEs indicates the number of UEs within the group identified by the External Group Identifier. The NEF uses this value to determine whether the monitoring event has been reported for all group member UEs. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.3.5.2 |
1,291 | 9.9.4.1.1 FDD | The minimum performance requirement in Table 9.9.4.1.1-2 is defined as a) The ratio of the throughput obtained when transmitting based on UE reported RI and that obtained when transmitting with fixed rank 1 shall be ≥ ; b) 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.9.4.1.1-1, and using the downlink physical channels specified in Annex C.3.2, the minimum requirements are specified in Table 9.9.4.1.1-2. Table 9.9.4.1.1-1: RI Test (FDD) Table 9.9.4.1.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.9.4.1.1 |
1,292 | 6.38.2.6 Security | The 5G system shall provide user privacy; location privacy, identity protection and communication confidentiallity for non-3GPP devices and UEs that are using the PIN Element with Gateway Capability, eRG or PRAS. NOTE 1: Privacy protection should not block differentiated routing and QoS for different destinations and services for the UE(s). The 5G system shall support a mechanism to minimize the security risk of communications using an eRG. The 5G system shall enable the network operator associated with an eRG to control the security policy of an eRG. The 5G system shall support a mechanism to minimize the security risk of communications via a PRAS. The PRAS (and its associated backhaul connectivity) shall provide a level of security equivalent to regular 5G base stations. The 5G system shall enable the network operator associated with the Premises Radio Access Station (PRAS) to control the security policy of the PRAS. The 5G system shall support authentication of a UE with 3GPP credentials for communication with entities (UEs, non-3GPP devices) in a CPN. NOTE 2: To support this functionality the CPN needs to be connected with the 5G core network. The 5G system shall provide support for a network operator to authenticate a PRAS. The 5G system shall provide support for a network operator to authorize a PRAS for its use in a CPN. The 5G system shall support a PIN Element using non operator managed credentials (e.g. provided by a third party) for performing communications within the PIN when those communications use PIN direct connections. The 5G system shall support a mechanism to mitigate repeated and unauthorized attempts to access PIN Elements (e.g. mitigate a malicious flood of messages). | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.38.2.6 |
1,293 | 5.4.4.2.2 Clearing when the network indicates that "CCBS activation is possible" | When Activation of CCBS is possible, the call control entity of the network may initiate clearing by sending a DISCONNECT message containing the Allowed Actions IE with an indication that "Activation of CCBS is possible" and starting T338. Optionally, progress indicator #8 "in-band information or appropriate pattern now available" may also be contained in the DISCONNECT message (in which case, T338 shall not be greater than T306). 5.4.4.2.2.1 Receipt of a DISCONNECT Relative to the current state the following procedures apply: - The call control entity of the MS in the "null" state, the "disconnect indication" state and the "release request" state, shall, upon receipt of a DISCONNECT message react as described in clause 8. - The call control entity of the MS in the "disconnect request" state, shall, upon receipt of a DISCONNECT message: - stop all running call control timers; - send a RELEASE message; - start timer T308; and - enter the "release request" state. - The call control entity of the MS in any other states, shall, upon receipt of a DISCONNECT message with an Allowed Actions IE indicating "Activation of CCBS is possible" pass the "Activation of CCBS is possible" indication to the upper layer, enter the "disconnect indication" state, stop all running call control timers and await a response from the upper layers. If the DISCONNECT message contained the progress indicator #8 "in-band information or appropriate pattern now available" and an appropriate speech traffic channel is connected, then the MS shall attach the user connection for speech if it is not yet attached. If the DISCONNECT message did not contain the progress indicator #8 "in-band information or appropriate pattern now available" any connected speech traffic channel shall be disconnected. Response from the upper layers: i) If the upper layers request the clearing of the call, the call control entity of the MS shall: - stop all running call control timers; - send a RELEASE message; - start timer T308; and - enter the "release request" state. ii) If the upper layers request that the "CCBS activation is to be attempted" then the MS shall - send a RELEASE message containing a Facility IE including an - Invoke=CCBSRequest to the network; - stop all running call control timers; - start timer T308; and - enter the "release request" state. If an appropriate speech traffic channel is connected, transmission of this RELEASE message shall not cause it to be disconnected. 5.4.4.2.2.2 Expiry of timer T338 The call control entity of the network, having entered the "disconnect indication" state after sending a DISCONNECT message with an Allowed Actions IE indicating "Activation of CCBS is possible" shall, upon expiry of timer T338, continue clearing by sending a RELEASE message with the cause number originally contained in the DISCONNECT message; starting timer T308; and entering the "release request" state. | 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.4.4.2.2 |
1,294 | 4.7.3.1.6 Abnormal cases on the network side | The following abnormal cases can be identified: a) Lower layer failure If a low layer failure occurs before the message ATTACH COMPLETE has been received from the MS and a new P-TMSI (or a new P-TMSI and a new P-TMSI signature) has been assigned, the network shall consider both the old and new P-TMSI each with its corresponding P-TMSI-signature as valid until the old P-TMSI can be considered as invalid by the network (see subclause 4.7.1.5) or the GMM context which has been marked as detached in the network is released, and shall not resent the message ATTACH ACCEPT. During this period the network may: - use the identification procedure followed by a P-TMSI reallocation procedure if the old P-TMSI is used by the MS in a subsequent message. b) Protocol error If the ATTACH REQUEST message is received with a protocol error, the network shall return an ATTACH REJECT message with one of the following reject causes: #96: Mandatory information element error; #99: Information element non-existent or not implemented; #100: Conditional IE error; #111: Protocol error, unspecified. c) T3350 time-out On the first expiry of the timer, the network shall retransmit the ATTACH ACCEPT message and shall reset and restart timer T3350. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3350, the GPRS attach procedure shall be aborted. If a new P-TMSI or a new P-TMSI together with a new P-TMSI signature were allocated in the ATTACH ACCEPT message, the network shall consider both the old and new P-TMSI each together with the corresponding P-TMSI signatures as valid until the old P-TMSI can be considered as invalid by the network (see subclause 4.7.1.5) or the GMM context which has been marked as detached in the network is released. During this period the network acts as specified for case a. d.1) ATTACH REQUEST received after the ATTACH ACCEPT message has been sent and before the ATTACH COMPLETE message is received - If one or more of the information elements in the ATTACH REQUEST message differ from the ones received within the previous ATTACH REQUEST message, the previously initiated GPRS attach procedure shall be aborted if the ATTACH COMPLETE message has not been received and the new GPRS attach procedure shall be progressed, or - If the information elements do not differ, then the ATTACH ACCEPT message shall be resent and the timer T3350 shall be restarted if an ATTACH COMPLETE message is expected. In that case, the retransmission counter related to T3350 is not incremented. d.2) More than one ATTACH REQUEST received and no ATTACH ACCEPT or ATTACH REJECT message has been sent - If one or more of the information elements in the ATTACH REQUEST message differs from the ones received within the previous ATTACH REQUEST message, the previously initiated GPRS attach procedure shall be aborted and the new GPRS attach procedure shall be progressed; - If the information elements do not differ, then the network shall continue with the previous attach procedure and shall not treat any further this ATTACH REQUEST message. e) ATTACH REQUEST received in state GMM-REGISTERED If an ATTACH REQUEST message is received in state GMM-REGISTERED the network may initiate the GMM common procedures; if it turned out that the ATTACH REQUEST message was send by an MS that has already been attached, the GMM context, PDP contexts and MBMS contexts, if any, are deleted and the new ATTACH REQUEST is progressed. f) ROUTING AREA UPDATE REQUEST message received before ATTACH COMPLETE message. Timer T3350 shall be stopped. The allocated P-TMSI shall be considered as valid and the routing area updating procedure shall be progressed as described in subclause 4.7.5. g) DETACH REQUEST message received before ATTACH COMPLETE message. The network shall abort the attach procedure and shall progress the detach procedure as described in subclause 4.7.4.1. Figure 4.7.3/1 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : GPRS attach procedure and combined GPRS attach 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.3.1.6 |
1,295 | 5.6.5a Supporting LADN per DNN and S-NSSAI | The 5GS may support LADN per DNN and S-NSSAI, and the functions specified in clause 5.6.5 are used (with the extension to apply per DNN and S-NSSAI whenever applicable) with the following enhancements: - The UE indicates the support of LADN per DNN and S-NSSAI in the UE MM Core Network Capability of the Registration Request message. - The LADN service area can be provisioned for a group (e.g. 5G VN group) or an individual subscriber using UDM/NEF parameter provisioning service triggered by AF request as described in clause 4.15.6 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. - LADN service area per DNN and S-NSSAI may be configured in the AMF. The LADN service area may also be provided to AMF as part of the subscription data from UDM. - The LADN Service Area Information provided to the UE is determined by AMF, based on the Registration Area that the AMF assigns to the UE and either the local configured LADN service area or the LADN service area received from UDM. In case there is both a configured LADN service area and a LADN service area received from UDM, the AMF decides based on operator configuration which one takes precedence. - If the UE indicates support of LADN per DNN and S-NSSAI, the AMF may provide the LADN Service Area Information per LADN DNN and S-NSSAI to the UE. - If the UE does not indicate support of LADN per DNN and S-NSSAI and the AMF has a LADN service area for the DNN as well as a LADN service area for the DNN and S-NSSAI, the AMF may determine the LADN Service Area Information per LADN DNN sent to UE using the LADN service area for the DNN as described in clause 5.6.5. - If the UE does not indicate support of LADN per DNN and S-NSSAI and the AMF has no LADN service area for the DNN but there is a LADN service area for the DNN and S-NSSAI, then the AMF may determine the LADN Service Area Information per LADN DNN sent to UE using this LADN service area for the DNN and S-NSSAI as the LADN service area for that DNN as described in clause 5.6.5 if the UE is not subscribed to the same DNN for multiple S-NSSAI(s) (i.e. the UE is subscribed to the DNN for a single S-NSSAI only). NOTE 1: In order to serve the UEs that do not support LADN per DNN and S-NSSAIs, the operator can avoid using the same DNN for multiple S-NSSAIs if LADN service area is configured per DNN and S-NSSAI. - If the UE does not indicate support of LADN per DNN and S-NSSAI and the AMF neither has a LADN service area for the DNN nor has a LADN service area for the DNN and S-NSSAI, the AMF shall not provide any LADN Information to the UE. - The AMF enforces the LADN Service Area per LADN DNN and S-NSSAI in the same way as is described in clause 5.6.5 with the difference that the LADN service area is defined per DNN and S-NSSAI. - The UE enforces the LADN Service Area per LADN DNN and S-NSSAI, if received from the AMF, in the same way as is described in clause 5.6.5 with the difference that the LADN service area is defined per DNN and S-NSSAI. - If the AMF enforces the LADN Service Area per LADN DNN and S-NSSAI for the UE, the AMF indicates to the SMF during PDU Session Establishment that the PDU Session is subject to LADN per LADN DNN and S-NSSAI. - If indicated by AMF at PDU Session Establishment that PDU Session is subject to LADN per LADN DNN and S-NSSAI, the SMF configures the DNN of PDU Session as LADN DNN. The SMF shall subscribe to "UE mobility event notification" for reporting UE presence in Area of Interest by providing LADN DNN and S-NSSAI to the AMF as described in clauses 5.6.11 and 5.3.4.4. The SMF handles the PDU session in the same way as described in clause 5.6.5. NOTE 2: If the UE has overlapping areas between LADN service area configured per DNN & S-NSSAI, Partial network slice support area, or any combination of them, then the evaluation of Partial network slice support area take precedence over the evaluation of LADN service area configured per DNN and S-NSSAI. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.6.5a |
1,296 | 5.2.5.2.5 Npcf_AMPolicyControl_Update service operation | Service operation name: Npcf_AMPolicyControl_Update. Description: NF Service Consumer, e.g. AMF can request the update of the AM Policy Association to receive updated access and mobility related policy information for the UE context when the Policy Control Request Trigger is met or the AMF is relocated due to the UE mobility and the old PCF is selected. Inputs, Required: AM Policy Association ID. Inputs, Optional: Information on the Policy Control Request Trigger condition that has been met as defined in clause 6.1.2.5 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20], GUAMI(s) (if NF Type is AMF), list of NWDAF instance Ids and corresponding Analytics ID(s), Target NSSAI. Outputs, Required: Success or not. Outputs, Optional: Access and mobility related policy information for the UE context as defined in clause 6.5 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20] and Policy Control Request Trigger(s) of AM Policy Association as defined in clause 6.1.2.5 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. See clause 4.16.2.1 for the usage of this service operation. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.5.2.5 |
1,297 | 5.4.2.7 Abnormal cases on the network side | The following abnormal cases can be identified: a) Lower layer failure before the SECURITY MODE COMPLETE or SECURITY MODE REJECT message is received. The network shall abort the security mode control procedure. b) Expiry of timer T3560. The network shall, on the first expiry of the timer T3560, retransmit the SECURITY MODE COMMAND message and shall reset and start timer T3560. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3560, the procedure shall be aborted. c) Collision between security mode control procedure and registration, service request or de-registration procedure not indicating switch off. The network shall abort the security mode control procedure and proceed with the UE initiated procedure. d) Collision between security mode control procedure and other 5GMM procedures than in item c. The network shall progress both procedures. e) Lower layers indication of non-delivered NAS PDU due to handover: If the SECURITY MODE COMMAND message could not be delivered due to an intra AMF handover and the target TA is included in the TAI list, then upon successful completion of the intra AMF handover the AMF shall retransmit the SECURITY MODE COMMAND message. If a failure of the handover procedure is reported by the lower layer and the N1 signalling connection exists, the AMF shall retransmit the SECURITY MODE COMMAND message. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.4.2.7 |
1,298 | 10.5.5.33 Message authentication code | The purpose of the Message authentication code information element is to protect the integrity of a NAS message. The Message authentication code is a type 3 information element with 6 octets length. The Message authentication code information element is coded as shown in figure 10.5.5.33-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.5.33-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.5.33-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Message authentication code information element Table 10.5.5.33-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Message authentication code information element | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.5.33 |
1,299 | 6.7.3.3 Intra-gNB-CU handover/intra-ng-eNB handover | It is not required to change the AS security algorithms during intra-gNB-CU/intra-ng-eNB handover. If the UE does not receive an indication of new AS security algorithms during an intra-gNB-CU/intra-ng-eNB handover, the UE shall continue to use the same algorithms as before the handover (see TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [22] for gNB and TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [69] for ng-eNB). | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.7.3.3 |
1,300 | 5.5.4.12 Event C2 (The NR sidelink channel busy ratio is below a threshold) | The UE shall: 1> consider the entering condition for this event to be satisfied when condition C2-1, as specified below, is fulfilled; 1> consider the leaving condition for this event to be satisfied when condition C2-2, as specified below, is fulfilled; Inequality C2-1 (Entering condition) Inequality C2-2 (Leaving condition) The variables in the formula are defined as follows: Ms is the measurement result of channel busy ratio of the transmission resource pool, not taking into account any offsets. Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigNR-SL for this event). Thresh is the threshold parameter for this event (i.e. c2-Threshold as defined within reportConfigNR-SL for this event). Ms is expressed in decimal from 0 to 1 in steps of 0.01. Hys is expressed is in the same unit as Ms. Thresh is expressed in the same unit as Ms. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.5.4.12 |
Subsets and Splits