Search is not available for this dataset
doc_id
int64 1
6.72k
⌀ | Section
stringlengths 5
247
⌀ | Content
stringlengths 501
147k
⌀ | Source
stringclasses 456
values | Document Title
stringclasses 22
values | Working Group
stringclasses 21
values | Series Subject
stringclasses 9
values | Subclause
stringlengths 1
13
⌀ |
|---|---|---|---|---|---|---|---|
2,401 | 4.5.1.5a MM connection establishment for emergency calls for CS fallback | When the MS is in NO CELL AVAILABLE state, camped on an E-UTRAN cell, and IMSI attached for CS services via EMM combined procedures, as described in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120], the MM sublayer requests EMM to initiate a service request procedure for mobile originating CS fallback emergency call, irrespective of whether timer T3246 is running. The MM connection establishment is delayed until the mobile station changes to a GERAN or UTRAN cell. After this point, the behaviour specified in subclause 4.5.1.5 applies. When the MS is not IMSI attached for CS services via EMM combined procedures, as described in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120], and the MS is camping on an E-UTRAN cell, the MS shall perform any cell selection to GERAN or UTRAN (see 3GPP TS 43.022[ None ] [82] and 3GPP TS 25.304[ None ] [98]). The MM connection establishment is delayed until the MS changes to a GERAN or UTRAN cell. After this point, the behaviour specified in subclause 4.5.1.5 applies. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.5.1.5a |
2,402 | 5.5.4 Advice of Charge | The charging data collected from the network elements may be used to provide tariff information concerning the use of services, by both home and visiting subscribers, within the network. The appropriate tariff information to the network elements is distributed by the Advice of Charge supplementary service. The function is specified in TS 32.280[ Telecommunication management; Charging management; Advice of Charge (AoC) service ] [40]. An alternative mode of AoC can also be used to indicate the occurrence of new charges to the user, e.g. when a monthly allowance is being exceeded, or when a service is requested that is not included in the subscription fees, while others are. This topic is for further study. | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 5.5.4 |
2,403 | 9.11.4.37 Non-3GPP delay budget | The purpose of the Non-3GPP delay budget information element is to indicate the non-3GPP delay budget for the non-3gpp network behind the UE to the network. The Non-3GPP delay budget information element is a type 6 information element with a minimum length of 8 octets. The maximum length for the information element is 65538 octets. The Non-3GPP delay budget information element is coded as shown in figure 9.11.4.37.1. Figure 9.11.4.37.1: Non-3GPP delay budget information element Figure 9.11.4.37.2: Non-3gpp delay budget Table 9.11.4.37.1: Non-3gpp delay budget information element | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.11.4.37 |
2,404 | 4.5 Disabling and re-enabling of UE's E-UTRA capability | The UE shall only disable the E-UTRA capability when in EMM-IDLE mode. When the UE supports both N1 mode and S1 mode then the UE's capability to access the 5GCN via E-UTRA shall not be affected, if the UE's E-UTRA capability is disabled or enabled. When the UE is disabling the E-UTRA capability not due to redirection to 5GCN required, it should proceed as follows: a) select another RAT (GERAN, UTRAN, or NG-RAN if the UE has not disabled its N1 mode capability for 3GPP access as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54]) of the registered PLMN or a PLMN from the list of equivalent PLMNs; b) if another RAT of the registered PLMN or a PLMN from the list of equivalent PLMNs cannot be found, or the UE does not have a registered PLMN, then perform PLMN selection as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. As an implementation option, instead of performing PLMN selection, the UE may select another RAT of the chosen PLMN. If disabling of E-UTRA capability was not due to UE initiated detach procedure for EPS services only, the UE may re-enable the E-UTRA capability for this PLMN selection; or c) if no other allowed PLMN and RAT combinations are available, then the UE may re-enable the E-UTRA capability and remain registered for EPS services in E-UTRAN of the registered PLMN. If the UE chooses this option, then it may periodically attempt to select another PLMN and RAT combination that can provide non-EPS services. How this periodic scanning is done, is UE implementation dependent. When the UE is disabling the E-UTRA capability upon receiving reject cause #31 "Redirection to 5GCN required" as specified in clauses 5.5.1.2.5, 5.5.1.3.5, 5.5.3.2.5, 5.5.3.3.5 and 5.6.1.5, it should proceed as follows: i) If the UE is in NB-S1 mode: 1) if lower layers do not provide an indication that the current E-UTRA cell is connected to 5GCN or lower layers do not provide an indication that the current E-UTRA cell supports CIoT 5GS optimizations that are supported by the UE, search for a suitable NB-IoT cell connected to 5GCN according to 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [21]; 2) if lower layers provide an indication that the current E-UTRA cell is connected to 5GCN and the current E-UTRA cell supports CIoT 5GS optimizations that are supported by the UE then perform a core network selection to select 5GCN as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] clause 4.8.4A.1; or 3) if lower layers cannot find a suitable NB-IoT cell connected to 5GCN or there is no suitable NB-IoT cell connected to 5GCN which supports CIoT 5GS optimizations that are supported by the UE, the UE, as an implementation option, may indicate to lower layers to remain camped in E-UTRA cell connected to EPC, may then start an implementation-specific timer and enter the state EMM-REGISTERED.LIMITED-SERVICE the UE may re-enable the E-UTRA capability for 3GPP access at expiry of the implementation-specific timer, if the timer had been started, and may then, proceed with the appropriate EMM procedure. ii) If the UE is in WB-S1 mode: 1) if lower layers do not provide an indication that the current E-UTRA cell is connected to 5GCN or lower layers do not provide an indication that the current E-UTRA cell supports CIoT 5GS optimizations that are supported by the UE, search for a suitable E-UTRA cell connected to 5GCN according to 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [21]; 2) if lower layers provide an indication that the current E-UTRA cell is connected to 5GCN and the current E-UTRA cell supports CIoT 5GS optimizations that are supported by the UE, then perform a core network selection to select 5GCN as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] clause 4.8.4A.1; or 3) if lower layers cannot find a suitable E-UTRA cell connected to 5GCN or there is no suitable E-UTRA cell connected to 5GCN which supports CIoT 5GS optimizations that are supported by the UE, the UE, as an implementation option, may indicate to lower layers to remain camped in E-UTRA cell connected to EPC, may then start an implementation-specific timer and enter the state EMM-REGISTERED.LIMITED-SERVICE the UE may re-enable the E-UTRA capability for 3GPP access at expiry of the implementation-specific timer, if the timer had been started, and may then, proceed with the appropriate EMM procedure. The UE shall re-enable the E-UTRA capability when performing a PLMN selection unless: - the disabling of E-UTRA capability was due to UE initiated detach procedure for EPS services only; or - the UE has already re-enabled the E-UTRA capability when performing bullets b) or c) above. If due to handover, the UE moves to a new PLMN in A/Gb, Iu, or N1 mode which is not in the list of equivalent PLMNs and not a PLMN memorized by the UE for which E-UTRA capability was disabled, and the disabling of E-UTRA capability was not due to UE initiated detach procedure for EPS services only, the UE shall re-enable the E-UTRA capability after the RR/RRC connection is released. If UE that has disabled its E-UTRA capability due to IMS voice not available and CS fallback not available re-enables it when PLMN selection is performed, then it should memorize the identity of the PLMNs where E-UTRA capability was disabled and use that stored information in subsequent PLMN selections as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. The UE may support "E-UTRA Disabling for EMM cause #15" and implement the following behaviour: - if the "E-UTRA Disabling Allowed for EMM cause #15" parameter as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17] is present and set to enabled; and - if the UE receives an ATTACH REJECT or TRACKING AREA UPDATE REJECT message including both EMM cause #15 "no suitable cells in tracking area" and an Extended EMM cause IE with value "E-UTRAN not allowed"; then the UE shall disable the E-UTRA capability, memorize the identity of the PLMN where the E-UTRA capability was disabled and use that stored information in subsequent PLMN selections as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. When the UE supporting the A/Gb and/or Iu mode together with the S1 mode needs to stay in A/Gb or Iu mode, in order to prevent unwanted handover or cell reselection from UTRAN/GERAN to E-UTRAN, the UE shall disable the E-UTRA capability and: - The UE shall not set the E-UTRA support bits of the MS Radio Access capability IE (see 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13], clause 10.5.5.12a), the E-UTRA support bits of Mobile Station Classmark 3 IE (see 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13], clause 10.5.1.7), the PS inter-RAT HO from GERAN to E-UTRAN S1 mode capability bit and the ISR support bit of the MS network capability IE (see 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13], clause 10.5.5.12) in the ATTACH REQUEST message and the ROUTING AREA UPDATE REQUEST message after it selects GERAN or UTRAN; - the UE shall use the same value of the EPC capability bit of the MS network capability IE (see 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13], clause 10.5.5.12) in the ATTACH REQUEST message and the ROUTING AREA UPDATE REQUEST message; and - the UE NAS layer shall indicate the access stratum layer(s) of disabling of the E-UTRA capability. When the UE supporting N1 mode together with S1 mode needs to stay in N1 mode, in order to prevent unwanted handover or cell reselection from NG-RAN to E-UTRAN, the UE shall disable the E-UTRA capability and: - the UE shall set the S1 mode bit to "S1 mode not supported" in the 5GMM Capability IE of the REGISTRATION REQUEST message (see 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54]); - the UE shall not include the S1 UE network capability IE in the REGISTRATION REQUEST message (see 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54]); and - the UE NAS layer shall indicate the access stratum layer(s) of disabling of the E-UTRA capability. If the UE is disabling its E-UTRA capability before selecting to GERAN, UTRAN or NG-RAN radio access technology, the UE shall not perform the detach procedure of clause 5.5.2.1. If the UE is required to disable the E-UTRA capability and select GERAN, UTRAN or NG-RAN radio access technology, and the UE is in the EMM-CONNECTED mode: - if the UE has a persistent EPS bearer context and the ongoing procedure is not a detach procedure, then the UE shall wait until the radio bearer associated with the persistent EPS bearer context has been released; - otherwise, the UE shall locally release the established NAS signalling connection and enter the EMM-IDLE mode before selecting GERAN, UTRAN or NG-RAN radio access technology. If the E-UTRA capability was disabled due to the attempt to select GERAN or UTRAN radio access technology progressing the CS emergency call establishment (see clause 4.3.1), the criteria to enable the E-UTRA capability again is UE implementation specific. If the E-UTRA capability was disabled due to the UE initiated detach procedure for EPS services only (see clause 5.5.2.2.2), upon request of the upper layers to re-attach for EPS services the UE shall enable the E-UTRA capability again. If the E-UTRA capability was disabled due to receipt of EMM cause #14 "EPS services not allowed in this PLMN", then the UE shall enable the E-UTRA capability when the UE powers off and powers on again or the USIM is removed. If E-UTRA capability was disabled for any other reason, the UE shall enable the E-UTRA capability in the following cases: - the UE mode of operation changes from CS/PS mode 1 of operation to CS/PS mode 2 of operation; - the UE mode of operation changes from PS mode 1 of operation to PS mode 2 of operation; or - the UE powers off and powers on again or the USIM is removed; As an implementation option, the UE may start a timer for enabling E-UTRA when the UE's attach attempt counter or tracking area updating attempt counter reaches 5 and the UE disables E-UTRA capability for cases described in clauses 5.5.1.2.6, 5.5.1.3.4.3, 5.5.1.3.6, 5.5.3.2.6, 5.5.3.3.4.3 and 5.5.3.3.6. The UE should memorize the identity of the PLMNs where E-UTRA capability was disabled. On expiry of this timer: - if the UE is in Iu mode or A/Gb mode and is in idle mode as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13], the UE should enable the E-UTRA capability; - if the UE is in Iu mode or A/Gb mode and an RR connection exists, the UE shall delay enabling E-UTRA capability until the RR connection is released; - if the UE is in Iu mode and a PS signalling connection exists but no RR connection exists, the UE may abort the PS signalling connection before enabling E-UTRA capability; or - if the UE is in N1 mode and is in 5GMM-IDLE mode as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54], the UE should enable the E-UTRA capability; and - if the UE is in N1 mode and is in 5GMM-CONNECTED mode as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54], the UE shall delay enabling the E-UTRA capability until the N1 NAS signalling connection is released. When the UE enables E-UTRA capability, the UE shall delete the PLMN from the memorized identity of the PLMNs where E-UTRA capability was disabled. NOTE 1: As described 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6], if the UE is in automatic PLMN selection mode, the UE does not consider the memorized PLMNs as PLMN selection candidates for E-UTRA access technology till the timer expires. If the UE attempts to establish an emergency bearer service or to access RLOS in a PLMN where the E-UTRA capability was disabled due to the UE's attach attempt counter or tracking area updating attempt counter have reached 5, the UE may enable the E-UTRA capability for that PLMN memorized by the UE. The UE may support being configured for No E-UTRA Disabling In 5GS (see 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [50] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]). If the UE supports being configured for No E-UTRA Disabling in 5GS, No E-UTRA Disabling In 5GS is enabled if the corresponding configuration parameter is present and set to enabled. Otherwise, No E-UTRA Disabling In 5GS is disabled. If No E-UTRA Disabling In 5GS is enabled at the UE and the UE selects an NG-RAN cell in a PLMN where the E-UTRA capability was disabled due to the UE's attach attempt counter or tracking area updating attempt counter having reached 5, the UE shall enable the E-UTRA capability for that PLMN. For other cases, it is up to the UE implementation when to enable the E-UTRA capability. NOTE 2: If the UE is not operating in CS/PS mode 1 operation, the value of the timer for enabling E-UTRA capability is recommended to be not larger than the default value of T3402. | 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.5 |
2,405 | 4.11.1.5.8 Radio Resource Management functions and Information Storage | The following changes are applied to clause 4.3.6 (Radio Resource Management functions) in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13]: - At 5GS to EPS mobility or during inter-MME mobility, if RFSP in Use ValidityTime is received from the AMF or the old MME, the new MME uses the received RFSP Index in use by the time indicated in RFSP in Use ValidityTime. Only when RFSP in Use ValidityTime expires, the MME re-evaluates the RFSP Index in use as in clause 4.3.6 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13]. NOTE: RFSP in Use ValidityTime is the validity time that is sent by the AMF to the MME as specified in clause 5.17.2.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The following new parameter is to be added in Table 5.7.2-1 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13]: Table 5.7.2-1: MME MM and EPS bearer Contexts | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.11.1.5.8 |
2,406 | 4.7.4.2.4 Abnormal cases on the network side | The following abnormal cases can be identified: a) T3322 time-out On the first expiry of the timer, the network shall retransmit the DETACH REQUEST message and shall start timer T3322. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3322, the GPRS detach procedure shall be aborted. If the detach type indicates "IMSI detach", or "re-attach not required" and the cause code is #2 "IMSI unknown in HLR", the network shall not change the current GMM state; otherwise the network shall change state to GMM-DEREGISTERED. b) Low layer failure The GPRS detach procedure is aborted. If the detach type indicates "IMSI detach", or "re-attach not required" and the cause code is #2 "IMSI unknown in HLR", the network shall not change the current GMM state; otherwise the network shall change state to GMM-DEREGISTERED. c) GPRS detach procedure collision If the network receives a DETACH REQUEST message with "switching off" indicated, before the network initiated GPRS detach procedure has been completed, both procedures shall be considered completed. If the network receives a DETACH REQUEST message without "switching off" indicated, before the network initiated GPRS detach procedure has been completed, the network shall send a DETACH ACCEPT message to the MS. d) GPRS detach and GPRS attach procedure collision If the network receives an ATTACH REQUEST message before the network initiated GPRS detach procedure with type of detach 're-attach not required' has been completed, the network shall ignore the ATTACH REQUEST message. If the detach type IE value, sent in the DETACH REQUEST message, indicates "re-attach required" the detach procedure is aborted and the GPRS attach procedure shall be progressed after the PDP contexts and MBMS contexts, if any, have been deleted. If the detach type IE value, sent in the DETACH REQUEST message, indicates "IMSI detach" the detach procedure is aborted and the GPRS attach procedure shall be progressed. e) GPRS detach and routing area updating procedure collision GPRS detach containing detach type "re-attach required" or "re-attach not required": If the network receives a ROUTING AREA UPDATE REQUEST message before the network initiated GPRS detach procedure has been completed, the detach procedure shall be progressed, i.e. the ROUTING AREA UPDATE REQUEST message shall be ignored. If the DETACH REQUEST message contains detach type "re-attach not required" and GMM cause #2 "IMSI unknown in HLR", the network will follow the procedure as described below for the detach type "IMSI detach". GPRS detach containing detach type "IMSI detach": If the network receives a ROUTING AREA UPDATE REQUEST message before the network initiated GPRS detach procedure has been completed, the network shall abort the detach procedure, shall stop T3322 and shall progress the routing area update procedure. f) GPRS detach and service request procedure collision GPRS detach containing detach type "re-attach required" or "re-attach not required": If the network receives a SERVICE REQUEST message before the network initiated GPRS detach procedure has been completed, the network shall progress the detach procedure. If the GPRS Detach Request message contains detach type "re-attach not required" and GMM cause #2 "IMSI unknown in HLR", the network will follow the procedure as described below for the detach type "IMSI detach". GPRS detach containing detach type "IMSI detach": If the network receives a SERVICE REQUEST message before the network initiated GPRS detach procedure has been completed, the network shall progress both procedures. Figure 4.7.4/2 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Network initiated GPRS detach 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.4.2.4 |
2,407 | 16a.3a.1 Authentication, Authorization and Accounting procedures | When a P-GW receives an initial access request (e.g.Create Session Request or Proxy Binding Update) message for a given APN, the P-GW may (depending on the configuration for this APN) send a Diameter AA-Request to a Diameter server. The Diameter server authenticates and authorizes the user. If the Diameter server is also responsible for IPv4 address and/or IPv6 prefix allocation the Diameter server shall return the allocated IPv4 address and/or IPv6 prefix in the AA-Answer message. When PDN type is IPv4v6 and deferred IPv4 addressing via IPv4 address pool in the AAA server is used, the P-GW may intiate Diameter re-authorization procedures after successful initial attach for the purpose of IPv4 address allocation or to renew the lease for a previously allocated IPv4 address. In this case, the P-GW shall set the Session-Id to the value used in the initial access request, the Auth-Request-Type AVP to "AUTHORIZE_ONLY" and the 3GPP-Allocate-IP-Type AVP to the type of IP address to be allocated in the AA-Request message sent to the AAA server. See subclause 16.4.7.2 for the conditions to use 3GPP-Allocate-IP-Type AVP in AA-Request messages. If the P-GW is using DHCPv4 signalling towards the UE and the Diameter server includes the Session-Timeout attribute in the Access-Accept, the P-GW may use the Session-Timeout value as the DHCP lease time. The P-GW shall not set the DHCPv4 lease time value higher than the Session-Timeout value. The P-GW may renew the DHCP lease to the UE without re-authorization towards the AAA server providing that the new lease expiry is no later than the Session-Timeout timer expiry. If the P-GW wishes to extend the lease time beyond the current Session-Timeout expiry, it shall initiate a new AAA re-authorization. Even if the P-GW was not involved in user authentication, it may send a Diameter Accounting-Request (START) message to a Diameter server. If no Diameter session is already open for the same PDN connection a Diameter session needs to be activated, otherwise the existing Diameter session is used to send the Accounting-Request (START). For GTP-based S5/S8/S2a/S2b, if accounting is used per IP-CAN bearer, the EPS bearer ID will identify the particular bearer this accounting message refers to. The Accounting-Request message also indicates to the Diameter server that the user session has started.This message contains parameters, e.g. the tuple which includes the user-id and IPv4 address and/or IPv6 prefix, to be used by application servers (e.g. WAP gateway) in order to identify the user. This message also indicates to the Diameter server that the user session has started. If some external applications require Diameter Accounting Request (START) information before they can process user packets, then the selected APN (P-GW) may be configured in such a way that the P-GW drops user data until an Accounting-Answer (START) indicating success is received from the Diameter server. The P-GW may wait for the Accounting-Answer (START) before sending the initial access response (e.g. Create Session Response or Proxy Binding Acknowledgement). The P-GW may reject the initial access request if the Accounting-Answer (START) is not received. The authentication and accounting servers may be separately configured for each APN. For PDN type IPv4, at IPv4 address allocation via DHCPv4 signalling between the UE and the PDN, no IPv4 address is available at initial access. In that case the P-GW may wait to send the Accounting-Request START message until the UE receives its IPv4 address in a DHCPACK. For PDN type IPv4v6 and deferred IPv4 addressing, when the IPv4 address is allocated or re-allocated, the accounting session that was established for the IPv6 prefix allocation shall be used to inform the accounting server about the allocated IPv4 address by sending Diameter Accounting-Request Interim-Update with the Framed-IP-Address AVP and its value field containing the allocated IPv4 address. When the P-GW receives a message indicating a bearer deactivation request or PDN disconnection request or detach request (e.g. Delete Bearer Command or Proxy Binding Update with lifetime equal 0) and providing a Diameter Accounting-Request START message was sent previously, the P-GW shall send a Diameter Accounting-Request (STOP) message to the Diameter server, which indicates the termination of this particular bearer or user session. The P-GW shall immediately send the corresponding response (e.g. Delete Bearer Request or Proxy Binding Ack with lifetime equal 0) to the peer node (e.g. S-GW) in the Packet Domain, without waiting for an Accounting-Answer (STOP) message from the Diameter server. If the last bearer of an IP-CAN session is deactivated, the P-GW shall additionally send an STR message to the Diameter server. The Diameter server shall reply with an STA and shall deallocate the IPv4 address and/or IPv6 prefix (if any) initially allocated to the subscriber. For PDN type IPv4v6 and deferred IPv4 addressing, when the P-GW receives a message from the UE or the network indicating the release of the IPv4 address (e.g. receiving DHCPRELEASE) or decides to release the IPv4 address on its own (e.g. due to DHCP lease timer expiry for P-GW assigned IPv4 address), the P-GW shall inform the accounting server about the deallocation of the IPv4 address by sending Diameter Accounting-Request Interim-Update without the Framed-IP-Address AVP. The following Figure 25d.1 is an example message flow to show the procedure of Diameter Authentication and Accounting, which is applicable for GTP based S5/S8: NOTE 1: If some external applications require Diameter Accounting request (Start) information before they can process user packets, then the selected APN (P-GW) may be configured in such a way that the P-GW drops user data until the Accounting Answer (START) is received from the Diameter server. The P-GW may wait for the Accounting Answer (START) before sending the Create Session Response. The P-GW may reject the bearer if the Accounting Answer (START) is not received. NOTE 2: Separate accounting and authentication servers may be used. Figure 25d.1: An example of Diameter Authentication and Accounting on Sgi for GTP-based S5/S8 | 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 | 16a.3a.1 |
2,408 | 5.9.2.1 Security Requirements for service registration, discovery and authorization | NF Service based discovery and registration shall support confidentiality, integrity, and replay protection. NRF shall be able to ensure that NF Discovery and registration requests are authorized. NF Service based discovery and registration shall be able to hide the topology of the available / supported NF's in one administrative/trust domain from entities in different trust/administrative domains (e.g. between NFs in the visited and the home networks.) NF Service Request and Response procedure shall support mutual authentication between NF Service Consumer and NF Service Producer. Each NF shall validate all incoming messages. Messages that are not valid according to the protocol specification and network state shall be either rejected or discarded by the NF. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 5.9.2.1 |
2,409 | 6.3.3D Transmit OFF power for ProSe | When UE is configured for E-UTRA ProSe sidelink transmissions non-concurrent with E-UTRA uplink transmissions for E-UTRA ProSe operating bands specified in Table 5.5D-1, the Prose UE shall meet the Transmit OFF power at all times when the UE is not associated with a serving cell on the ProSe carrier and does not have knowledge of its geographical area or is provisioned with pre-configured radio parameters that are not associated with any known Geographical Area. The requirements specified in subclause 6.3.3 shall apply to UE supporting ProSe when - the UE is associated with a serving cell on the ProSe carrier, or - the UE is not associated with a serving cell on the ProSe carrier and is provisioned with the preconfigured radio parameters for ProSe Direct Communications and/or ProSe Direct Discovery that are associated with known Geographical Area, or - the UE is associated with a serving cell on a carrier different than the ProSe carrier, and the radio parameters for ProSe Direct Discovery on the ProSe carrier are provided by the serving cell, or - the UE is associated with a serving cell on a carrier different than the ProSe carrier, and has a non-serving cell selected on the ProSe carrier that supports ProSe Direct Discovery and/or ProSe Direct Communication. When UE is configured for simultaneous E-UTRA ProSe sidelink and E-UTRA uplink transmissions for inter-band E-UTRA ProSe / E-UTRA bands specified in Table 5.5D-2, transmit OFF power is defined as the mean power per component carrier when the transmitter is OFF on all component carriers. During measurement gaps and transmission/reception gaps for ProSe, the UE is not considered to be OFF. Transmit OFF power requirement as specified in subclause 6.3.3 apply per carrier. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.3.3D |
2,410 | 4.7.1.5.1 P-TMSI handling in A/Gb mode | If a new P-TMSI is assigned by the network the MS and the network shall handle the old and the new P-TMSI as follows: Upon receipt of a GMM message containing a new P-TMSI the MS shall consider the new P-TMSI and new RAI and also the old P-TMSI and old RAI as valid in order to react to paging requests and downlink transmission of LLC frames. For uplink transmission of LLC frames the new P-TMSI shall be used. NOTE: For the case of multiple consecutive P-TMSI REALLOCATION COMMAND messages, the old P-TMSI is the latest P-TMSI included by the network in a previous message different from the multiple consecutive P-TMSI REALLOCATION COMMAND messages. The MS shall consider the old P-TMSI and old RAI as invalid as soon as an LLC frame is received with the local TLLI derived from the new P-TMSI. Upon the transmission of a GMM message containing a new P-TMSI the network shall consider the new P-TMSI and new RAI and also the old P-TMSI and old RAI as valid in order to be able to receive LLC frames from the MS. The network shall consider the old P-TMSI and old RAI as invalid as soon as an LLC frame is received with the local TLLI derived from the new P-TMSI. | 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.1.5.1 |
2,411 | – FreqPriorityListDedicatedSlicing | The IE FreqPriorityListDedicatedSlicing provides dedicated cell reselection priorities for slicing in RRCRelease. FreqPriorityListDedicatedSlicing information element -- ASN1START -- TAG-FREQPRIORITYLISTDEDICATEDSLICING-START FreqPriorityListDedicatedSlicing-r17 ::= SEQUENCE (SIZE (1.. maxFreq)) OF FreqPriorityDedicatedSlicing-r17 FreqPriorityDedicatedSlicing-r17 ::= SEQUENCE { dl-ExplicitCarrierFreq-r17 ARFCN-ValueNR, sliceInfoListDedicated-r17 SliceInfoListDedicated-r17 OPTIONAL -- Cond Mandatory } SliceInfoListDedicated-r17 ::= SEQUENCE (SIZE (1..maxSliceInfo-r17)) OF SliceInfoDedicated-r17 SliceInfoDedicated-r17 ::= SEQUENCE { nsag-IdentityInfo-r17 NSAG-IdentityInfo-r17, nsag-CellReselectionPriority-r17 CellReselectionPriority OPTIONAL, -- Need R nsag-CellReselectionSubPriority-r17 CellReselectionSubPriority OPTIONAL -- Need R } -- TAG-FREQPRIORITYLISTDEDICATEDSLICING-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,412 | 5.6F Channel bandwidth for category NB1 and NB2 | Channel bandwidth for Category NB1 and NB2 is 200 kHz. For category NB1 and NB2, requirements in present document are specified for the channel bandwidth listed in Table 5.6F-1. Table 5.6F-1: Transmission bandwidth configuration NRB, Ntone 15kHz and Ntone 3.75kHz in NB1 and NB2 channel bandwidth Figure 5.6F-1 shows the relation between the Category NB1/NB2 channel bandwidth (BWChannel) and the Category NB1 /NB2 transmission bandwidth configuration (Ntone). The channel edges are defined as the lowest and highest frequencies of the carrier separated by the channel bandwidth, i.e. at FC +/- BWChannel /2. Figure 5.6F-1 Definition of Channel Bandwidth and Transmission Bandwidth configuration | 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 | 5.6F |
2,413 | 6.3.6.2a SNPN N3IWF selection | This procedure applies when the UE is accessing the SNPN N3IWF in its subscribed SNPN via a PLMN or directly via untrusted non-3GPP access. The UE shall first determine the country in which it is located. If the UE cannot determine the country in which the UE is located, the UE shall stop N3IWF selection and abort the attempt to access the SNPN via PLMN. NOTE 1: It is up to UE implementation how to determine the country in which the UE is located. The UE is configured with one N3IWF address and the MCC of the country where the configured N3IWF is located as defined in TS 24.502[ Access to the 3GPP 5G Core Network (5GCN) via non-3GPP access networks ] [48]. If the UE determines that it is located in the country where the configured N3IWF is located, then the UE uses the configured N3IWF FQDN to select an N3IWF deployed in the SNPN. If the UE determines that it is located in a country (called the visited country) different from the country where the configured N3IWF is located, then: - The UE shall construct an FQDN consisting of the SNPN ID of the subscribed SNPN and the Visited Country FQDN and indicating the query is for SNPN, as specified in TS 23.003[ Numbering, addressing and identification ] [19] and perform a DNS query for the resulting FQDN. - If the DNS response contains no records, then the UE determines that the visited country does not mandate the selection of an N3IWF in this country for the SNPN identified by the SNPN ID provided by the UE. In this case the UE uses the configured N3IWF FQDN to select an N3IWF deployed in the SNPN. - If no DNS response is received, the UE shall stop the N3IWF selection. NOTE 2: The DNS can be configured to return no records for the visited country regardless of the SNPN ID provided by the UE. This addresses the scenario that the visited country in general does not mandate selection of a local N3IWF. - If the DNS response contains one or more records, then the UE determines that the visited country mandates the selection of an N3IWF in this country. Each record in the DNS response shall contain the identity of an N3IWF of the UE's subscribed SNPN in the visited country which may be used for N3IWF selection. In this case: - The UE shall select an N3IWF included in the DNS response based on its own implementation means. - If the UE cannot select any N3IWF included in the DNS response, then the UE shall stop the N3IWF selection. NOTE 3: Visited countries which mandate the selection of an N3IWF in the country are assumed to configure the DNS as follows: (i) For SNPNs that do not have any dedicated N3IWFs in the country and which are not exempt from the requirement to select an N3IWF in the visited country, the DNS response contains a record that cannot be resolved to an IP address; (ii) for SNPNs that have dedicated N3IWFs in the country, the DNS response contains the identities of the SNPN's N3IWFs in the visited country; (iii) for SNPNs that are exempt from the requirement to select an N3IWF in the visited country, the DNS response contains no records. NOTE 4: Self-assigned NIDs are not supported, since a DNS cannot be properly configured for multiple SNPNs using the same self-assigned NID (i.e. in collision scenarios). If the visited country mandates the selection of an N3IWF in the same country, the NAPTR record(s) associated to the Visited Country FQDN of SNPNs that use a self-assigned NID can be provisioned with the replacement field containing an FQDN that cannot be resolved to an IP address. NOTE 5: The identity of an SNPN's N3IWF in the visited country can be any FQDN, i.e. is not required to include the SNPN ID. NOTE 6: It is assumed that the AMF, SMF, UPF are located in the same country as the N3IWF and belong to the subscribed SNPN of the UE. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.3.6.2a |
2,414 | – FrequencyInfoUL | The IE FrequencyInfoUL provides basic parameters of an uplink carrier and transmission thereon. FrequencyInfoUL information element -- ASN1START -- TAG-FREQUENCYINFOUL-START FrequencyInfoUL ::= SEQUENCE { frequencyBandList MultiFrequencyBandListNR OPTIONAL, -- Cond FDD-OrSUL absoluteFrequencyPointA ARFCN-ValueNR OPTIONAL, -- Cond FDD-OrSUL scs-SpecificCarrierList SEQUENCE (SIZE (1..maxSCSs)) OF SCS-SpecificCarrier, additionalSpectrumEmission AdditionalSpectrumEmission OPTIONAL, -- Need S p-Max P-Max OPTIONAL, -- Need S frequencyShift7p5khz ENUMERATED {true} OPTIONAL, -- Cond FDD-TDD-OrSUL-Optional ..., [[ additionalSpectrumEmission-v1760 AdditionalSpectrumEmission-v1760 OPTIONAL -- Need S ]], [[ additionalSpectrumEmissionAerial-r18 AdditionalSpectrumEmission-r18 OPTIONAL -- Need S ]] } -- TAG-FREQUENCYINFOUL-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,415 | – InvalidSymbolPattern | The IE InvalidSymbolPattern is used to configure one invalid symbol pattern for PUSCH transmission repetition type B applicable for both DCI format 0_1 and 0_2, see TS 38.214[ NR; Physical layer procedures for data ] [19], clause 6.1. InvalidSymbolPattern information element -- ASN1START -- TAG-INVALIDSYMBOLPATTERN-START InvalidSymbolPattern-r16 ::= SEQUENCE { symbols-r16 CHOICE { oneSlot BIT STRING (SIZE (14)), twoSlots BIT STRING (SIZE (28)) }, periodicityAndPattern-r16 CHOICE { n2 BIT STRING (SIZE (2)), n4 BIT STRING (SIZE (4)), n5 BIT STRING (SIZE (5)), n8 BIT STRING (SIZE (8)), n10 BIT STRING (SIZE (10)), n20 BIT STRING (SIZE (20)), n40 BIT STRING (SIZE (40)) } OPTIONAL, -- Need M ... } -- TAG-INVALIDSYMBOLPATTERN-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,416 | – RA-PrioritizationForSlicing | The IE RA-PrioritizationForSlicing is used to configure prioritized random access for slicing. RA-PrioritizationForSlicing information element -- ASN1START -- TAG-RA-PRIORITIZATIONFORSLICING-START RA-PrioritizationForSlicing-r17 ::= SEQUENCE { ra-PrioritizationSliceInfoList-r17 RA-PrioritizationSliceInfoList-r17, ... } RA-PrioritizationSliceInfoList-r17 ::= SEQUENCE (SIZE (1..maxSliceInfo-r17)) OF RA-PrioritizationSliceInfo-r17 RA-PrioritizationSliceInfo-r17 ::= SEQUENCE { nsag-ID-List-r17 SEQUENCE (SIZE (1..maxSliceInfo-r17)) OF NSAG-ID-r17, ra-Prioritization-r17 RA-Prioritization, ... } -- TAG-RA-PRIORITIZATIONFORSLICING-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,417 | 4.3.8.4 SGSN selection function | The SGSN selection function selects an available SGSN to serve a UE. The selection is based on network topology, i.e. the selected SGSN serves the UE's location and for overlapping SGSN service areas, the selection may prefer SGSNs with service areas that reduce the probability of changing the SGSN. When a MME/SGSN selects a target SGSN, the selection function performs a simple load balancing between the possible target SGSNs. In networks that deploy dedicated MMEs/SGSNs for UEs configured for low access priority, the possible target SGSN selected by source MME/SGSN is typically restricted to SGSNs with the same dedication. When a MME/SGSN supporting DCNs selects a target SGSN, the selected target SGSN should be restricted to SGSNs that belong to the same CN. The DNS procedure may be used by the source CN node to select the target SGSN from a given DCN. If both low access priority and UE Usage Type parameter are used for SGSN selection, selection based on UE Usage type parameter overrides selection based on the low access priority indication. | 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.8.4 |
2,418 | 4.2.2.1 Initial Messages | The IP Destination Address of a GTPv2 Initial message shall be an IP address of the destination GTPv2 entity. During the establishment of the GTP tunnel, the GTPv2 entity selects and communicates to the peer GTPv2 entity the IP Destination Address at which it expects to receive subsequent control plane Initial messages related to that GTP tunnel via the: - "Sender F-TEID for Control Plane" IE, - "PGW S5/S8/S2a/S2b F-TEID for PMIP based interface or for GTP based Control Plane interface" IE, - "MSC Server Sv Address for Control Plane" IE, - "S3/S16/S10 Address and TEID for Control Plane" IE, or - "MME/SGSN Sv Address for Control Plane" IE. A Create Session Request shall only include in the Sender F-TEID the same IP address type as the destination address used in the IP header. An IPv4/IPv6 capable SGW and PGW may advertize an IPv4 address and/or an IPv6 address in the F-TEID of the above IEs. Upon a change of MME, SGSN or SGW, the new MME, SGSN or SGW may switch to a different IP address type (e.g. IPv6 address) in the IP header if a different IP address type was advertized by the SGW or PGW earlier. A Modify Bearer Request shall only include in the Sender F-TEID the same IP address type as the destination address used in the IP header. NOTE 1: Advertizing a single IP address type in a Create Session Request or a Modify Bearer Request ensures that both GTP-C peers know without ambiguity the IP address type to be used in subsequent control plane Initial messages in the reverse direction related to that GTP-C tunnel, and it avoids intempestive IP address switching during the establishment of the GTP-C tunnel or during an established communication between two GTP-C peers. NOTE 2: IP switching between IPv4 and IPv6 can occur upon a change of MME/SGSN or SGW in deployments with MME/SGSNs or SGWs with different IPv6 capabilities. EXAMPLE 1: If an MME gets IPv4 addresses from the DNS for the SGW, the MME only includes an IPv4 address in the Sender F-TEID IE of the Create Session Request. In the response, the SGW advertises an IPv4 address and optionally an IPv6 address, and the SGW uses IPv4 addressing in subsequent control plane Initial messages it sends to the MME related to that GTP-C tunnel. EXAMPLE 2: As a continuation of EXAMPLE 1, upon a subsequent change of MMEs, assuming the source MME only supports IPv4 and the target MME supports IPv4 and IPv6, the target MME can switch to IPv6 addressing by sending a Modify Bearer Request to the SGW using the SGW S11 IPv6 address in the IP header and including a Sender F-TEID with an MME S11 IPv6 address only. During the network triggered service restoration procedure (see 3GPP TS 23.007[ Restoration procedures ] [17]), if an MME/S4-SGSN sends a Downlink Data Notification Failure Indication message to the SGW, then the destination address for this message shall be the SGW IP address signalled via the Sender F-TEID for Control Plane IE in the Downlink Data Notification message (if present in the message), otherwise the source IP address of the Downlink Data Notification message received earlier. The IP Source Address of a GTPv2 Initial message shall be an IP address of the source GTPv2 entity from which the Initial message is originating. | 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 | 4.2.2.1 |
2,419 | 4.5.2 Determination of the access identities and access category associated with a request for access for UEs not operating in SNPN access operation mode over 3GPP access | When the UE needs to initiate an access attempt in one of the events listed in subclause 4.5.1, the UE shall determine one or more access identities from the set of standardized access identities, and one access category from the set of standardized access categories and operator-defined access categories, to be associated with that access attempt. The set of the access identities applicable for the request is determined by the UE in the following way: a) for each of the access identities 1, 2, 3, 11, 12, 13, 14 and 15 in table 4.5.2.1, the UE shall check whether the access identity is applicable in the selected PLMN, if a new PLMN is selected, or otherwise if it is applicable in the RPLMN or equivalent PLMN; and b) if none of the above access identities is applicable, then access identity 0 is applicable. Table 4.5.2.1: Access identities The UE uses the MPS indicator bit of the 5GS network feature support IE or the Priority indicator IE to determine if access identity 1 is valid. Processing of the MPS indicator bit of the 5GS network feature support IE in the REGISTRATION ACCEPT message is described in subclause 5.5.1.2.4 and subclause 5.5.1.3.4. Processing of the MPS indicator bit of the Priority indicator IE in the CONFIGURATION UPDATE COMMAND message is described in subclause 5.4.4.3. The UE shall not consider access identity 1 to be valid when the UE is neither in the country of its HPLMN nor in an EHPLMN (if the EHPLMN list is present), until the UE receives the MPS indicator bit of the 5GS network feature support IE in the REGISTRATION ACCEPT message or of the Priority indicator IE in the CONFIGURATION UPDATE COMMAND message being set to "Access identity 1 valid" from the RPLMN or from an equivalent PLMN. When the UE is in the country of its HPLMN or in an EHPLMN (if the EHPLMN list is present), the contents of the USIM file EFUAC_AIC as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [22] and the rules specified in table 4.5.2.1 are used to determine the applicability of access identity 1. When the UE is in the country of its HPLMN or in an EHPLMN (if the EHPLMN list is present), and the USIM file EFUAC_AIC does not indicate the UE is configured for access identity 1, the UE uses the MPS indicator bit of the 5GS network feature support IE in the REGISTRATION ACCEPT message or of the Priority indicator IE in the CONFIGURATION UPDATE COMMAND message to determine if access identity 1 is valid. When the UE is in the country of its HPLMN or in an EHPLMN (if the EHPLMN list is present), and the USIM file EFUAC_AIC indicates the UE is configured for access identity 1, the MPS indicator bit of the 5GS network feature support IE and the Priority indicator IE are not applicable. When the UE is not in the country of its HPLMN or in an EHPLMN (if the EHPLMN list is present), the contents of the USIM file EFUAC_AIC are not applicable. The UE uses the MCS indicator bit of the 5GS network feature support IE to determine if access identity 2 is valid. Processing of the MCS indicator bit of the 5GS network feature support IE in the REGISTRATION ACCEPT message is described in subclause 5.5.1.2.4 and subclause 5.5.1.3.4. The UE shall not consider access identity 2 to be valid when the UE is not in the country of its HPLMN or in an EHPLMN (if the EHPLMN list is present) prior to receiving the MCS indicator bit of the 5GS network feature support IE in the REGISTRATION ACCEPT message being set to "Access identity 2 valid". When the UE is in the country of its HPLMN or in an EHPLMN (if the EHPLMN list is present), the contents of the USIM file EFUAC_AIC as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [22] and the rules specified in table 4.5.2.1 are used to determine the applicability of access identity 2. When the UE is in the country of its HPLMN or in an EHPLMN (if the EHPLMN list is present), and the USIM file EFUAC_AIC does not indicate the UE is configured for access identity 2, the UE uses the MCS indicator bit of the 5GS network feature support IE in the REGISTRATION ACCEPT message to determine if access identity 2 is valid. When the UE is in the country of its HPLMN or in an EHPLMN (if the EHPLMN list is present), and the USIM file EFUAC_AIC indicates the UE is configured for access identity 2, the MCS indicator bit of the 5GS network feature support IE is not applicable. When the UE is not in the country of its HPLMN or in an EHPLMN (if the EHPLMN list is present), the contents of the USIM file EFUAC_AIC are not applicable. The UE checks the conditions specified in subclause 4.4.3.1.1 of 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] to determine if access identity 3 is valid, and the applicability of access identity 3. When the UE is in its HPLMN (if the EHPLMN list is not present or is empty) or in an EHPLMN (if the EHPLMN list is present), the contents of the USIM file EFACC as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [22] and the rules specified in table 4.5.2.1 are used to determine the applicability of access classes 11 and 15. When the UE is not in its HPLMN (if the EHPLMN list is not present or is empty) or in an EHPLMN (if the EHPLMN list is present), access classes 11 and 15 are not applicable. When the UE is in the country of its HPLMN, the contents of the USIM file EFACC as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [22] and the rules specified in table 4.5.2.1 are used to determine the applicability of access classes 12 - 14. When the UE is not in the country of its HPLMN, access classes 12-14 are not applicable. In order to determine the access category applicable for the access attempt, the NAS shall check the rules in table 4.5.2.2, and use the access category for which there is a match for barring check. If the access attempt matches more than one rule, the access category of the lowest rule number shall be selected. If the access attempt matches more than one operator-defined access category definition, the UE shall select the access category from the operator-defined access category definition with the lowest precedence value (see subclause 4.5.3). NOTE: The case when an access attempt matches more than one rule includes the case when multiple events trigger an access attempt at the same time. When multiple events trigger an access attempt at the same time, how the access attempt is checked for multiple events is up to UE implementation. Table 4.5.2.2: Mapping table for access categories | 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.5.2 |
2,420 | 5.2.27.2.8 Ntsctsf_TimeSynchronization_CapsNotify operation | Service operation name: Ntsctsf_TimeSynchronization_CapsNotify Description: Forward the notification for the time synchronization configuration. When the TSCTSF detects an event corresponding to a Subscription, it invokes Ntsctsf_TimeSynchronization_CapsNotify service operation to the NF consumer(s), e.g. a NEF or an AF within the operator's domain, that has subscribed for the event. The following table describes the parameters in the event. Table 5.2.27.2.8-1: Time Synchronization capability event parameters Inputs, Required: Subscription Correlation ID. Inputs, Optional: Time synchronization capabilities as described in Table 5.2.27.2.8-1. Outputs, Required: Operation execution result indication. Outputs, Optional: None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.27.2.8 |
2,421 | 4.2.4.1.2 Other Cases | When the MM state is IDLE, the GMM substate PLMN-SEARCH shall also be entered in the following cases: - when a SIM/USIM is inserted in substate NO-IMSI; - when the user has asked for a PLMN selection in any substate except NO IMSI and NO CELL AVAILABLE ; - when coverage is lost in any substate except NO IMSI and NO CELL AVAILABLE ; - Roaming is denied; - optionally, when the MS is in automatic network selection mode and the maximum allowed number of consecutive unsuccessful attach attempts controlled by the GPRS attach attempt counter (subclause 4.7.3) have been performed. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.2.4.1.2 |
2,422 | 4.3.2.3 Authentication processing in the network | Upon receipt of the AUTHENTICATION RESPONSE message, the network stops the timer T3260 and checks the validity of the response (see 3GPP TS 43.020[ Security related network functions ] [13] in case of a GSM authentication challenge respective 3GPP TS 33.102[ 3G security; Security architecture ] [5a] in case of an UMTS authentication challenge). Upon receipt of the AUTHENTICATION FAILURE message, the network stops the timer T3260. In Synch failure case, the core network may renegotiate with the HLR/AuC and provide the MS with new authentication parameters. | 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.3.2.3 |
2,423 | 5.4.1.5 Abnormal cases in the UE | The following abnormal cases can be identified: a) Transmission failure of GUTI REALLOCATION COMPLETE message indication with TAI change from lower layers If the current TAI is not in the TAI list, the GUTI reallocation procedure shall be aborted and a tracking area updating procedure shall be initiated. If the current TAI is still part of the TAI list, it is up to the UE implementation how to re-run the ongoing procedure that triggered the GUTI reallocation procedure. b) Transmission failure of GUTI REALLOCATION COMPLETE message indication without TAI change from lower layers It is up to the UE implementation how to re-run the ongoing procedure that triggered the GUTI reallocation procedure. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.4.1.5 |
2,424 | 4.3.5.2 Reachability Management for UE in ECM-IDLE state | The location of a UE in ECM-IDLE state is known by the network on a Tracking Area List granularity. All cells of the Tracking Areas in which a UE in ECM-IDLE is currently registered needs to be taken into account for paging. The UE may be registered in multiple Tracking Areas. All the tracking areas in a Tracking Area List to which a UE is registered are served by the same serving MME. An EMM-REGISTERED UE performs periodic Tracking Area Updates with the network after the expiry of the periodic TAU timer. The MME may allocate long periodic TAU timer value to the UE according to clause 4.3.17.3. If the UE is out of E-UTRAN coverage (including the cases when the UE is camped on GERAN/UTRAN cells) when its periodic TAU timer expires, the UE shall: - if ISR is activated, start the E-UTRAN Deactivate ISR timer. After the E-UTRAN Deactivate ISR timer expires the UE shall deactivate ISR by setting its TIN to "P-TMSI". - if ISR is activated and the UE is camping on a GERAN/UTRAN cell (or returns to coverage in GERAN/UTRAN) and the UE is EPS/IMSI attached, perform a LAU procedure in NMO II or a combined RA/LA update procedure in NMO I. - when EMM-REGISTERED, perform a Tracking Area Update when it next returns to E-UTRAN coverage. For UE using a RAN that provides discontinuous coverage (e.g. for satellite access with discontinuous coverage), if the UE knows how the E-UTRAN coverage varies with time based on information defined in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [37] (e.g. from the ephemeris data of a satellite access system that the UE is using) then the UE may deactivate its Access Stratum functions in order to optimise power consumption until coverage returns. Details are specified in TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [34] and TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [46]. If the UE is camped on an E-UTRAN cell or is in ECM-CONNECTED state when the UE's periodic RAU timer expires, the UE shall: - if ISR is activated, start the GERAN/UTRAN Deactivate ISR timer. After the GERAN/UTRAN Deactivate ISR timer expires the UE shall deactivate ISR by setting its TIN to "GUTI". - perform a Routing Area Update when it next returns to GERAN/UTRAN coverage. If the UE is EPS attached only and either camps on an E UTRAN cell or is in ECM CONNECTED state when the UE's periodic LAU timer expires, the UE shall perform a Location Area Update procedure in NMO II or combined RA/LA update in NMO I when it next returns to GERAN/UTRAN coverage. The E-UTRAN Deactivate ISR timer is stopped when the UE performs a successful Tracking Area Update or combined TA/LA Update; and the GERAN/UTRAN Deactivate ISR timer is stopped when the UE performs a successful Routing Area Update or combined RA/LA Update. Expiry of the periodic TAU timer, or, the periodic RAU timer, or, the periodic LAU timer shall not cause the UE to change RAT. The UE's periodic TAU timer is restarted from its initial value whenever the UE enters ECM-IDLE mode and when the UE leaves the E-UTRAN connection due to handover to GERAN/UTRAN. UTRAN RRC state transitions and GERAN GPRS STANDBY/READY state transitions shall have no other impact on the periodic TAU timer. E-UTRAN RRC state transitions shall have no impact on the periodic RAU timer or periodic LAU timer except that handover from GERAN/UTRAN to E-UTRAN shall cause the periodic RAU timer to be started from its initial value. Handover from E-UTRAN to UTRAN/GERAN shall cause the periodic TAU timer to be started from its initial value. Typically, the MME runs a mobile reachable timer. Whenever the UE enters ECM IDLE mode the timer is started with a value similar to the UE's periodic TAU timer. If this timer expires in the MME, the MME can deduce that the UE is not reachable. However, the MME does not know for how long the UE is not reachable, so, the MME shall not immediately delete the UE's bearers. Instead the MME should clear the PPF flag in the MME and start an Implicit Detach timer, with a relatively large value and if ISR is activated, at least slightly larger than the UE's E-UTRAN Deactivate ISR timer. Tracking Area or RAT specific MME configuration can be used to support UEs using a RAN that provides discontinuous coverage (e.g. for satellite access with discontinuous coverage). NOTE 1: For example, if a satellite system only provides coverage to a UE for 20 minutes when a satellite passes, and the maximum time before a satellite passes any point on the earth is 10 hours, the MME could configure the periodic TAU timer and mobile reachable timer to be just greater than 20 minutes and the Implicit Detach timer to be greater than 10 hours to avoid unintended implicit detach due to coverage gap. Such configuration does not require MME to be aware of detailed coverage times for each UE or for different locations. Further enhancements to handle discontinuous coverage for satellite access is provided in clause 4.13.8.2. If MME has allocated an Active Time to the UE, then the MME starts the Active timer with the value of Active Time whenever the UE enters ECM IDLE mode. If this timer expires in the MME, the MME can deduce that the UE is not reachable and should clear the PPF flag in the MME. With the PPF clear, the MME does not page the UE in E-UTRAN coverage and shall send a Downlink Data Notification Reject message to the Serving GW when receiving a Downlink Data Notification message from the Serving GW. If the Implicit Detach timer expires before the UE contacts the network, then the MME can deduce that the UE has been 'out of coverage' for a long period of time and implicitly detach the UE as described in clause 5.3.8.3 "MME-initiated Detach procedure". If the MME is requested to monitor Reachability for Data and the UE enters ECM-CONNECTED, the MME sends a Monitoring Report message to the address that was indicated in the related Monitoring Request as described in TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [74]. When the MME applies General NAS level Mobility Management Congestion Control to a UE, the MME may need to adjust the mobile reachable timer and/or Implicit Detach timer (as clause 4.3.7.4.2.4). NOTE 2: The SGSN has similar functionality as the MME. NOTE 3: Alternative MME implementations are permitted, however, the externally visible MME behaviour should conform to the above description. | 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.5.2 |
2,425 | 5.40.3 Disaster Condition Notification and Determination | The NG-RAN in the PLMN that provides Disaster Roaming service, broadcasts an indication of accessibility for Disaster Roaming service, and optionally, a 'list of one or more PLMN(s) with Disaster Condition for which Disaster Roaming service is offered by the available PLMN' in the impacted area as described in TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [50] and TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [28]. A UE determines the Disaster Condition based on the information broadcasted from the NG-RAN providing Disaster Roaming service, and performs the network selection and the access control for the Disaster Roaming as described in TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [17] and TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]. NOTE 1: How a PLMN is notified that another PLMN is a PLMN with Disaster Condition and how a PLMN is notified of the area where the associated Disaster Condition applies is managed by the government agencies or the authorities, and is out of scope of 3GPP. NOTE 2: The broadcast for Disaster Roaming service from the NG-RAN occurs only during the Disaster Condition. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.40.3 |
2,426 | 9.11.3.100 S-NSSAI location validity information | The purpose of the S-NSSAI location validity information information element is to provide the S-NSSAI location validity information to the UE. The S-NSSAI location validity information information element is coded as shown in figures 9.11.3.100.1, 9.11.3.100.2, 9.11.3.100.3, and 9.11.3.100.4 and table 9.11.3.100.1. The S-NSSAI location validity information information element can contain per-S-NSSAI location validity information for maximum 8 S-NSSAIs. The S-NSSAI location validity information information is a type 6 information element with a minimum length of 25 octets and a maximum length of 19307 octets. Figure 9.11.3.100.1: S-NSSAI location validity information information element Figure 9.11.3.100.2: Per-S-NSSAI location validity information for S-NSSAI Figure 9.11.3.100.3: NS-AoS Figure 9.11.3.100.4: NR CGI Table 9.11.3.100.1: S-NSSAI location validity information information element | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.11.3.100 |
2,427 | .2 Downlink Data Notification Acknowledge | A Downlink Data Notification Acknowledge shall be sent from a MME/SGSN to a SGW in response to Downlink Data Notification with an indication of success, or failure when MME/SGSN has reachability or abnormal conditions. Possible Cause values are specified in Table 8.4-1. Message specific cause values are: - "Unable to page UE". - "Context not found". - "Unable to page UE due to Suspension". - "UE already re-attached". - "Temporarily rejected due to handover/TAU/RAU procedure in progress". - "Rejection due to paging restriction". Table .2-1 specifies the presence of the IEs in the message. Table .2-1: Information Elements in a Downlink Data Notification Acknowledge | 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 | .2 |
2,428 | 4.3.2.1.1 Attempted outgoing inter-RAT handovers per handover cause | This measurement provides the number of attempted outgoing inter-RAT handovers per cause and target cell specific. CC. Transmission of the MobilityFromEUTRACommand message or the HandoverFromEUTRAPreparationRequest message from the serving eNB/RN to the UE indicating the attempt of an outgoing handover from EUTRAN to UTRAN or to GERAN or to CDMA2000 (see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]). Each MobilityFromEUTRACommand message or HandoverFromEUTRAPreparationRequest message transmitted 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 inter-RAT handover events. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first. All IRAT handovers to the neighbouring cells in non-eUTRAN networks are measured. 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.IartOutAtt.Cause where Cause identifies the cause for handover EUtranCellFDD EUtranCellTDD GSMRelation UTRANRelation CDMA2000Relation 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.2.1.1 |
2,429 | – EUTRA-AllowedMeasBandwidth | The IE EUTRA-AllowedMeasBandwidth is used to indicate the maximum allowed measurement bandwidth on a carrier frequency as defined by the parameter Transmission Bandwidth Configuration "NRB" in TS 36.104[ Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) radio transmission and reception ] [33]. The values mbw6, mbw15, mbw25, mbw50, mbw75, mbw100 indicate 6, 15, 25, 50, 75 and 100 resource blocks, respectively. EUTRA-AllowedMeasBandwidth information element -- ASN1START -- TAG-EUTRA-ALLOWEDMEASBANDWIDTH-START EUTRA-AllowedMeasBandwidth ::= ENUMERATED {mbw6, mbw15, mbw25, mbw50, mbw75, mbw100} -- TAG-EUTRA-ALLOWEDMEASBANDWIDTH-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,430 | – SL-DRX-ConfigUC | The IE SL-DRX-ConfigUC is used to configure sidelink DRX related parameters for unicast communication. SL-DRX-ConfigUC information element -- ASN1START -- TAG-DRX-CONFIGUC-START SL-DRX-ConfigUC-r17 ::= SEQUENCE { sl-drx-onDurationTimer-r17 CHOICE { subMilliSeconds INTEGER (1..31), milliSeconds ENUMERATED { ms1, ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30, ms40, ms50, ms60, ms80, ms100, ms200, ms300, ms400, ms500, ms600, ms800, ms1000, ms1200, ms1600, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1} }, sl-drx-InactivityTimer-r17 ENUMERATED { ms0, ms1, ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30, ms40, ms50, ms60, ms80, ms100, ms200, ms300, ms500, ms750, ms1280, ms1920, ms2560, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1}, sl-drx-HARQ-RTT-Timer1-r17 ENUMERATED {sl0, sl1, sl2, sl4, spare4, spare3, spare2, spare1} OPTIONAL, -- Need M sl-drx-HARQ-RTT-Timer2-r17 ENUMERATED {sl0, sl1, sl2, sl4, spare4, spare3, spare2, spare1} OPTIONAL, -- Need M sl-drx-RetransmissionTimer-r17 ENUMERATED { sl0, sl1, sl2, sl4, sl6, sl8, sl16, sl24, sl33, sl40, sl64, sl80, sl96, sl112, sl128, sl160, sl320, spare15, spare14, spare13, spare12, spare11, spare10, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1}, sl-drx-CycleStartOffset-r17 CHOICE { ms10 INTEGER(0..9), ms20 INTEGER(0..19), ms32 INTEGER(0..31), ms40 INTEGER(0..39), ms60 INTEGER(0..59), ms64 INTEGER(0..63), ms70 INTEGER(0..69), ms80 INTEGER(0..79), ms128 INTEGER(0..127), ms160 INTEGER(0..159), ms256 INTEGER(0..255), ms320 INTEGER(0..319), ms512 INTEGER(0..511), ms640 INTEGER(0..639), ms1024 INTEGER(0..1023), ms1280 INTEGER(0..1279), ms2048 INTEGER(0..2047), ms2560 INTEGER(0..2559), ms5120 INTEGER(0..5119), ms10240 INTEGER(0..10239) }, sl-drx-SlotOffset INTEGER (0..31) } -- TAG-SL-DRX-CONFIGUC-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,431 | 5.5.1.3.3 5GMM common procedure initiation | The AMF may initiate 5GMM common procedures, e.g. the identification, authentication and security procedures during the registration procedure, depending on the information received in the REGISTRATION REQUEST message. The AMF may be configured to skip the authentication procedure even if no 5GS security context is available and proceed directly to the execution of the security mode control procedure as specified in subclause 5.4.2, during the registration procedure for mobility and periodic registration update for a UE that has only an emergency PDU session. The AMF shall not initiate a 5GMM authentication procedure before completion of the registration procedure for mobility and periodic registration update, if the following conditions apply: a) the UE initiated the registration procedure for mobility and periodic registration update after handover or inter-system change to N1 mode in 5GMM-CONNECTED mode; b) the target cell is a shared network cell; and c.1) the UE has provided its 5G-GUTI in the 5GS mobile identity IE or the Additional GUTI IE in the REGISTRATION REQUEST message, and the PLMN identity included in the 5G-GUTI is different from the selected PLMN identity of the target cell; or c.2) the UE has included the 5G-GUTI mapped from the 4G-GUTI in the 5GS mobile identity IE and not included an Additional GUTI IE in the REGISTRATION REQUEST message, and the PLMN identity included in the 5G-GUTI is different from the selected PLMN identity of the target cell. | 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.1.3.3 |
2,432 | 10.5.5.19 A&C reference number | The purpose of the A&C reference number information element is to indicate to the network in the AUTHENTICATION AND CIPHERING RESPONSE message which AUTHENTICATION AND CIPHERING REQUEST message the MS is replying to. The A&C reference number is a type 1 information element. The A&C reference number information element is coded as shown in figure 10.5.134/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.152/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.134/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : A&C reference number information element Table 10.5.152/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : A&C reference number 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.19 |
2,433 | 4.7.1.2a.6 Change of security keys | When the network initiates a re-authentication to create a new UMTS security context, the AUTHENTICATION AND CIPHERING REQUEST message and AUTHENTICATION AND CIPHERING RESPONSE message exchanged during the authentication and ciphering procedure are integrity protected with the new UMTS security context at GMM layer by including a MAC. The AUTHENTICATION AND CIPHERING REQUEST message and AUTHENTICATION AND CIPHERING RESPONSE message may be also integrity protected at the LLC layer using the current UMTS security context, if any. Both UE and network shall continue to use the current UMTS security context, until the network initiates a re-authentication in the authentication and ciphering procedure. The AUTHENTICATION AND CIPHERING REQUEST message sent by the network includes the CKSN of the new UMTS security context to be used. The SGSN shall send the AUTHENTICATION AND CIPHERING REQUEST message integrity protected with the new UMTS security context at GMM layer by including a MAC, but unciphered. When the UE responds with an AUTHENTICATION AND CIPHERING RESPONSE message, it shall send the message integrity protected with the new UMTS security context at GMM layer by including a MAC, but unciphered. The UE shall take the new UMTS security context and the indicated integrity algorithm and encryption algorithm received in the AUTHENTICATION AND CIPHERING REQUEST message, into use in the LLC layer after sending the AUTHENTICATION AND CIPHERING RESPONSE message. The network shall take the new UMTS security context and the indicated integrity algorithm and encryption algorithm sent in the AUTHENTICATION AND CIPHERING REQUEST message, into use in the LLC layer in the network after receiving the AUTHENTICATION AND CIPHERING RESPONSE message and a successful check of the RES. | 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.1.2a.6 |
2,434 | 4.4.1.4 N4 Session Release procedure | The N4 session release procedure is used to remove the N4 session context of an existing PDU Session at the UPF. Figure 4.4.1.4-1 N4 Session Release procedure 1. SMF receives the trigger to remove the N4 session context for the PDU Session. 2. The SMF sends an N4 session release request message to the UPF. 3. The UPF identifies the N4 session context to be removed by the N4 Session ID and removes the whole session context. The UPF responds with an N4 session release response message containing any information that the UPF has to provide to the SMF. 4. The SMF interacts with the network entity which triggered this procedure (e.g. AMF or PCF). | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.4.1.4 |
2,435 | 8.143 PC5 QoS Flow | PC5 QoS Flow shall be coded as depicted in Figure 8.14-1. Figure 8.143-1: PC5 QoS Flow If the Range flag, in bit 1 of octet 5, is set to "1", then the Range field shall be present in octet 15, otherwise the octet 15 shall not be present. Octet 6 contains the "5QI" value, as specified in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [82]. The Guaranteed Flow Bit Rate and Maximum Flow Bit Rate fields are encoded as kilobits per second (1 kbps = 1000 bps) in binary value. The Guaranteed Flow Bit Rate and Maximum Flow Bit Rate fields may require converting values in bits per second to kilobits per second when the Guaranteed Flow Bit Rate and Maximum Flow Bit Rate values are received from an interface other than GTPv2 interface. If such conversions result in fractions, then the value of Guaranteed Flow Bit Rate and Maximum Flow Bit Rate fields shall be rounded upwards. For non-GBR PC5 QoS flows, both the Guaranteed Flow Bit Rate and Maximum Flow Bit Rate should be set to zero. The Range field is in the unit of meters, and only used for groupcast communication, as specified in 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [10]. Range field is encoded as a one octet long enumeration. NOTE: 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [10] specifies several enumeration values, i.e. 0 (indicates "m50"), 1 (indicates "m80") and etc. | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 8.143 |
2,436 | 9.11.3.99 Non-3GPP access path switching indication | The purpose of the Non-3GPP access path switching indication information element is to indicate whether the UE supports the non-3GPP access path switching for the PDU session. The Non-3GPP access path switching indication information element is coded as shown in figure 9.11.3.99.1 and table 9.11.3.99.1. The Non-3GPP access path switching indication is a type 4 information element with a length of 3 octets. Figure 9.11.3.99.1: Non-3GPP access path switching indication information element Table 9.11.3.99.1 : Non-3GPP access path switching indication information element | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.11.3.99 |
2,437 | 5.6.12 Use of Network Instance | The SMF may provide a Network Instance to the UPF in FAR and/or PDR via N4 Session Establishment or N4 Modification procedures. NOTE 1: a Network Instance can be defined e.g. to separate IP domains, e.g. when a UPF is connected to 5G-ANs in different IP domains, overlapping UE IP addresses assigned by multiple Data Networks, transport network isolation in the same PLMN, etc. NOTE 2: As the SMF can provide over N2 the Network Instance it has selected for the N3 CN Tunnel Info, the 5G AN does not need to provide Network Instance to the 5GC. The SMF determines the Network Instance based on local configuration. The SMF may determine the Network Instance for N3 and N9 interfaces, taking into account e.g. UE location, registered PLMN ID of UE, S-NSSAI of the PDU Session. The SMF may determine the Network Instance for N6 interface taking into account e.g. (DNN, S-NSSAI) of the PDU Session. The SMF may determine the Network Instance for N19 interface taking into account e.g. the (DNN, S-NSSAI) identifying a 5G VN group. NOTE 3: As an example, the UPF can use the Network Instance included in the FAR, together with other information such as Outer header creation (IP address part) and Destination interface in the FAR, to determine the interface in UPF (e.g. VPN or Layer 2 technology) for forwarding of the traffic. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.6.12 |
2,438 | 4.2.7.2.2 Creating NGAP UE-TNLA-bindings during handovers | During an Xn-based inter NG-RAN node handover, the following applies - If an NGAP UE-TNLA-binding exists for a UE, the source 5G-AN node supplies the target 5G-AN node with the corresponding TNL address of the AMF for the currently used TNL association. - If the target 5G-AN does not have a TNL association towards the TNL address of the AMF received from the source 5G-AN node, the target 5G-AN node establishes a TNL association towards the TNL address received from the source 5G-AN node, creates an NGAP UE-TNLA-binding to this TNL association and sends the N2 Path Switch Request via this TNL association. - Otherwise, the target 5G-AN node creates an NGAP UE-TNLA-binding for the UE by selecting a TNL association from the available TNL associations towards the TNL address, permitted for the initial N2 message for the AMF identified by the UE's GUAMI. - The AMF may decide to use the TNL association selected by the 5G-AN or the AMF may modify the NGAP UE-TNLA-binding by triangular redirection. During an inter NG-RAN node handover without Xn interface (i.e. during an N2 handover) the following applies: - If an NGAP UE-TNLA-binding exists for a UE, the source 5G-AN node sends the N2 Handover Required message using the corresponding TNL address of the AMF. - Otherwise the 5G-AN node creates an NGAP UE-TNLA-binding for the UE by selecting a TNL association from the available TNL associations permitted for the initial N2 message for the AMF identified by the UE's GUAMI. - The target AMF selects a TNL association from the available TNL associations for the target 5G-AN node and sends the N2 Handover Request message via this TNL association. The target 5G-AN node creates an NGAP UE-TNLA-binding for the UE based on the TNL association selected by the target AMF. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2.7.2.2 |
2,439 | 8.9.8 BH RLC channel establishment procedure | NOTE: The general principles and procedures described in this clause does not apply to ng-eNB The BH RLC channel is an RLC channel used for backhauling between IAB-node and IAB-donor-DU, or between different IAB-nodes. The BH RLC channel establishment may be triggered by a UE accessing the network and establishing a DRB. Figure 8.9.8-1: Signalling flow for IAB BH RLC channel establishment procedure 1. The IAB-donor-CU sends to the IAB-donor-DU a UE CONTEXT MODIFICATION REQUEST message for setting up the parent-node IAB-DU side of the BH link between IAB-donor-DU and IAB-node 1. This step is optional and is required only when a new BH RLC channel needs to be established on the BH link between IAB-donor-DU and IAB-node 1. 2. The IAB-donor-DU sends the UE CONTEXT MODIFICATION RESPONSE message to the IAB-donor-CU. 3. The IAB-donor-CU sends to the IAB-donor-DU a DL RRC MESSAGE TRANSFER message encapsulating the RRCReconfiguration message for configuring the IAB-MT of IAB-node 1. This step is optional and is required only when a new BH RLC channel needs to be established on the BH link between IAB-donor-DU and IAB-node 1. 4. The IAB-donor-DU decapsulates and forwards the RRCReconfiguration message to the IAB-MT of IAB-node 1. This step is optional and is required only when a new BH RLC channel needs to be established on the BH link between IAB-donor-DU and IAB-node 1. 5. The IAB-MT of IAB-node 1 sends to the IAB-donor-DU an RRCReconfigurationComplete message destined to the IAB-donor-CU. This step is optional and is required only when a new BH RLC channel needs to be established on the BH link between IAB-donor-DU and IAB-node 1. 6. The IAB-donor-DU sends the UL RRC MESSAGE TRANSFER message encapsulating the RRCReconfigurationComplete message to the IAB-donor-CU. This step is optional and is required only when a new BH RLC channel needs to be established on the BH link between IAB-donor-DU and IAB-node 1. 7. The IAB-donor-CU sends to the IAB-DU of IAB-node 1 a UE CONTEXT MODIFICATION REQUEST message for setting up the parent node IAB-DU side of the BH link between IAB-node 1 and IAB-node 2. This step is optional and is required only when a new BH RLC channel needs to be established on the BH link between IAB-node 1 and IAB-node 2. 8. The IAB-node 1 sends the UE CONTEXT MODIFICATION RESPONSE message to the IAB-donor-CU. 9. The IAB-donor-CU sends to the IAB-DU of IAB-node 1 a DL RRC MESSAGE TRANSFER message encapsulating the RRCReconfiguration message for configuring the IAB-MT of IAB-node 2. This step is optional and is required only when a new BH RLC channel needs to be established on the BH link between IAB-node 1 and IAB-node 2. 10. The IAB-DU of IAB-node 1 decapsulates and forwards the RRCReconfiguration message to the IAB-MT of IAB-node 2. This step is optional and is required only when a new BH RLC channel needs to be established on the BH link between IAB-node 1 and IAB-node 2. 11. The IAB-MT of IAB-node 2 sends to IAB-node 1 an RRCReconfigurationComplete message destined to the IAB-donor-CU. This step is optional and is required only when a new BH RLC channel needs to be established on the BH link between IAB-node 1 and IAB-node 2. 12. IAB-node 1 sends the UL RRC MESSAGE TRANSFER message encapsulating the RRCReconfigurationComplete message to the IAB-donor-CU. This step is optional and is required only when a new BH RLC channel needs to be established on the BH link between IAB-node 1 and IAB-node 2. The IAB-donor-CU uses the existing CU-DU split principles and the UE Context Setup procedure or UE Context Modification procedure to configure the parent IAB-DU side of the BH RLC channel. The IAB-donor-CU uses RRC signaling (which is encapsulated in the DL RRC MESSAGE TRANSFER message terminating at the parent node IAB-DU side of the BH RLC channel) to configure the child node IAB-MT side of the BH RLC channel. The IAB-donor-CU configures the IAB-DU with a mapping to the BH RLC channel to be used for a specific UL F1-U tunnel during the UE Context Setup procedure or the F1-AP UE Context Modification procedure for the UE. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.9.8 |
2,440 | 6.2.3A UE Maximum Output power for modulation / channel bandwidth for CA | For inter-band carrier aggregation with one uplink component carrier assigned to one E-UTRA band, the requirements in subclause 6.2.3 apply. For inter-band carrier aggregation with two uplink contiguous component carrier assigned to one E-UTRA band specified in this clause for intra-band contiguous carrier aggregation apply for that band. For inter-band carrier aggregation with one component carrier per operating band and the uplink active in two E-UTRA bands, the requirements in subclause 6.2.3 apply for each uplink component carrier. For intra-band contiguous carrier aggregation the allowed Maximum Power Reduction (MPR) for the maximum output power in Table 6.2.2A-1due to higher order modulation and contiguously aggregated transmit bandwidth configuration (resource blocks) is specified in Table 6.2.3A-1 for UE power class 3 CA bandwidth classes B and C, in Table 6.2.3A-1a for UE power class 2 CA bandwidth class C, and Table 6.2.3A-2 for UE power class 3 CA bandwidth class D. In case the modulation format is different on different component carriers then the MPR is determined by the rules applied to higher order of those modulations. Table 6.2.3A-1: Maximum Power Reduction (MPR) for Power Class 3 Table 6.2.3A-1a: Maximum Power Reduction (MPR) for Power Class 2 Table 6.2.3A-2: Maximum Power Reduction (MPR) for Class 3 For PUCCH and SRS transmissions, the allowed MPR is according to that specified for PUSCH QPSK modulation for the corresponding transmission bandwidth. For UE power class 3 intra-band contiguous carrier aggregation bandwidth class C with non-contiguous resource allocation, the allowed Maximum Power Reduction (MPR) for the maximum output power in Table -1 is specified as follows MPR = CEIL { min(MA, MIM5), 0.5} Where MA is defined as follows for QPSK, 16 QAM and 64 QAM MA = 8.2 ; 0 ≤ A < 0.025 9.2 - 40A ; 0.025 ≤ A < 0.05 8 – 16A ; 0.05 ≤ A < 0.25 4.83 – 3.33A ; 0.25 ≤ A ≤ 0.4, 3.83 – 0.83A ; 0.4 ≤ A ≤ 1, Where MA is defined as follows for 256 QAM MA = 8.2 ; 0 ≤ A < 0.025 9.2 - 40A ; 0.025 ≤ A < 0.05 8 – 16A ; 0.05 ≤ A < 0.16 5.5 ; 0.16 ≤ A < 1 and MIM5 is defined as follows MIM5 = 4.5 ; IM5 < 1.5 * BWChannel_CA 6.0 ; 1.5 * BWChannel_CA ≤ IM5 < BWChannel_CA/2 + FOOB MA ; IM5 ≥ BWChannel_CA/2 + FOOB For UE power class 2 intra-band contiguous carrier aggregation bandwidth class C with non-contiguous resource allocation, the allowed Maximum Power Reduction (MPR) for the maximum output power in Table -1 is specified as follows MPR = CEIL { min(MA, MIM5), 0.5} Where MA is defined as follows for QPSK, 16 QAM and 64 QAM MA = 8.2 ; 0 ≤ A < 0.04 9.2 - 40A ; 0.04 ≤ A < 0.075 8 – 16A ; 0.075 ≤ A < 0.25 4.83 – 3.33A ; 0.25 ≤ A ≤ 0.4, 3.83 – 0.83A ; 0.4 ≤ A ≤ 1, Where MA is defined FFS for 256 QAM and MIM5 is defined as follows MIM5 = 5.0 ; IM5 < 1.5 * BWChannel_CA 6.0 ; 1.5 * BWChannel_CA ≤ IM5 < BWChannel_CA/2 + FOOB MA ; IM5 ≥ BWChannel_CA/2 + FOOB For UE power class 3 intra-band contiguous carrier aggregation bandwidth class B with non-contiguous resource allocation, the allowed Maximum Power Reduction (MPR) for the maximum output power in Table 6.2.2A-1 is specified as follows MPR = CEIL { MA, 0.5} Where MA is defined as follows for QPSK, 16 QAM and 64 QAM MA = 10.5 – 17.5A ; 0 ≤ A < 0.2 8.5 – 7.5A ; 0.2 ≤ A < 0.6 5.5 – 2.5A ; 0.6 ≤ A ≤ 1 Where MA is defined as follows for 256 QAM MA = 10.5 – 17.5A ; 0 ≤ A < 0.2 8.5 – 7.5A ; 0.2 ≤ A < 0.4 5.5 ; 0.4 ≤ A ≤ 1 Where A = NRB_alloc / NRB_agg. IM5 = max( | FC_agg – (3*Fagg_alloc_low – 2*Fagg_alloc_high) |, | FC_agg – (3*Fagg_alloc_high – 2*Fagg_alloc_low) | ) FC_agg = (Fedge_high + Fedge_low)/2 For UE power class 3 intra-band contiguous carrier aggregation bandwidth class D with non-contiguous resource allocation, the allowed Maximum Power Reduction (MPR) for the maximum output power in Table 6.2.3A-2 is specified as follows MPR = CEIL { min(MA, MIM5), 0.5} Where MA is defined as follows for QPSK, 16 QAM and 64 QAM MA = 8.2 ; 0 ≤ A < 0.025 9.2 - 40A ; 0.025 ≤ A < 0.05 8 – 16A ; 0.05 ≤ A < 0.25 4.0 ; 0.25 ≤ A < 1 Where MA is defined as follows for 256 QAM MA = 8.2 ; 0 ≤ A < 0.025 9.2 - 40A ; 0.025 ≤ A < 0.05 8 – 16A ; 0.05 ≤ A < 0.16 5.5 ; 0.16 ≤ A < 1 and MIM5 is defined as follows MIM5 = 4.5 ; IM5 < 1.5 * BWChannel_CA 6.0 ; 1.5 * BWChannel_CA ≤ IM5 < BWChannel_CA/2 + FOOB MA ; IM5 ≥ BWChannel_CA/2 + FOOB CEIL{MA, 0.5} means rounding upwards to closest 0.5dB, i.e. MPR[3.0, 3.5, 4.0, 4.5, 5.0, 5.5, 6.0, 6.5, 7.0, 7.5, 8.0, 8.5]. For intra-band non-contiguous carrier aggregation with one uplink carrier, the requirements in subclause 6.2.3 apply. For intra-band non-contiguous carrier aggregation with two uplink carriers MPR is specified for E-UTRA CA configurations with a maximum possible WGAP ≤ 35 MHz; the allowed MPR is MPR = CEIL {MN, 0.5} where MN is defined as follows MN= -0.125 N + 18.25 ; 2 ≤ N ≤ 50 -0.0333 N + 13.67 ; 50 < N ≤ 200 where N= NRB_alloc is the number of allocated resource blocks. Clause 6.2.3 does not apply in addition. For intra-band non-contiguous carrier aggregation with two uplink carriers MPR is specified for E-UTRA CA configurations with a maximum possible 35 MHz <WGAP ≤ 100 MHz; the allowed MPR is given in Table 6.2.3A-3: Table 6.2.3A-3 Maximum power reduction (MPR) for power class 3 with dual Tx for intra-band non contiguous CA with 35 MHz <WGAP ≤ 100 MHz For intra-band carrier aggregation, the MPR is evaluated per Teval period specified in table 6.2.3A-3 and given by the maximum value taken over the transmission(s) on all component carriers within that period; the maximum MPR over TREF is then applied for TREF. Table 6.2.3A-4: MPR evaluation period for CA For combinations of intra-band and inter-band carrier aggregation with three uplink component carriers (up to two contiguously aggregated carriers per band), the requirements specified in subclause 6.2.3 apply for the E-UTRA band supporting one component carrier, and for the E-UTRA band supporting two contiguous component carriers the requirements specified in subclause 6.2.3A apply. For the UE maximum output power modified by MPR, the power limits specified in subclause 6.2.5A apply. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.2.3A |
2,441 | Annex N (informative): Satellite coverage availability information | The protocol and format of satellite coverage availability information to be provisioned to the UE via a PDN connection or SMS is not defined in this release of the specification, but this annex provides some examples on the information that constitutes input to the source of satellite coverage availability information e.g. external server and the output it provides to the UE. Satellite coverage availability information can be indicated to the UE by indications corresponding to whether or not coverage is available for a specific satellite RAT Type for a particular location and time, where: - these indications can be Boolean "True" (e.g. coverage available) and "False" (coverage not available); - locations can correspond to grid points in a fixed array (e.g. rectangular, hexagonal); - coverage availability times may occur at fixed periodic intervals; and - coverage availability information is per RAT Type. The information provisioned to the UE can include coverage information on only one PLMN or multiple PLMNs. If Satellite coverage availability information indicates coverage is available then additional information on whether PLMN is allowed to operate in that location can be provided to the UE. In order for the source of satellite coverage availability information to provide accurate information to the UE, a UE might indicate for example the following information to a source of satellite coverage availability information (e.g. an external server): - Serving PLMN ID (if not already known or implied). - One or more satellite RAT Types (where satellite coverage availability information is then expected for these one or more RAT Types). - List of supported satellite frequency bands (if not implied by the particular RAT Types). - Present UE location (e.g. latitude and longitude) for a reference grid point (e.g. the most Southerly and then most Westerly grid point). - Type of Array (e.g. rectangular or hexagonal). - Minimum elevation angle. Based on the above information provided by the UE, satellite coverage availability information could be delivered to the UE as a sequence of time durations for each grid point where each time duration includes an indication of coverage availability or unavailability one example of many alternatives as illustrated below for a particular grid point with N different durations: Satellite coverage availability information at a given grid point = <N> <Binary 0 or 1><Duration 1> <Binary 0 or 1><Duration 2> . . . . <Binary 0 or 1><Duration N> The above would be concatenated for all of the grid points to produce the satellite coverage availability information. When SMS is used to deliver the satellite coverage availability information, the UE input and satellite coverage availability information output can be delivered in a series of concatenated SMS messages using possibly the same format. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | Annex |
2,442 | 8.125 CIoT Optimizations Support Indication | CIoT Optimizations Support Indication is coded as depicted in Figure 8.125-1 below. Figure 8.125-1: CIoT Optimizations Support Indication Octet 5 carries the feature support bits for each of the CIoT optimization as follows: - Bit 8 to Bit 5: Spare, for future use and set to 0. - Bit 4 – IHCSI (IP Header Compression Support Indication): Indicates the support of IP header compression based on ROHC framework (see IETF RFC 4995 [77]) for Control Plane CIoT EPS optimisations, when set to '1'. - Bit 3 – AWOPDN (Attach without PDN Support Indication): Indicates the support of Attach without PDN connection as specified in clause 4.3.5.10 of 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [3], when set to '1'. Here the word "PDN connection" implies both the PDN connection through SGW and PGW and the PDN connection through SCEF. - Bit 2 – SCNIPDN (SCEF Non IP PDN Support Indication): Indicates the support of SCEF Non IP PDN Connection as specified in clause 5.13.1 of 3GPP TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [74], when set to '1'. - Bit 1 – SGNIPDN (SGi Non IP PDN Support Indication): Indicates the support of SGi Non IP PDN Connection as specified in clause 4.3.17.8.3.3 of 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [3] and 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [35], when set to '1'. | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 8.125 |
2,443 | 8.7.12.2 TDD CA in licensed bands | The parameters specified in Table 8.7.12.2-1 are valid for all LAA CA SDR tests unless otherwise stated. Table 8.7.12.2-1: Common Test Parameters For UE not supporting 256QAM, the TB success rate shall be higher than 85% when PDSCH are scheduled with FRC in Table 8.7.12.2-2 with the downlink physical channel setup according to Annex C.3.2. For UE supporting 256QAM, the TB success rate shall be higher than 85% when PDSCH are scheduled with FRC in Table 8.7.12.2-3 with the downlink physical channel setup according to Annex C.3.2. For UE supporting 256QAM, the requirement with 64QAM is not applicable. For LAA SCell, per-CC separate FRCs are defined for different UE capability for endingDwPTS and secondSlotStartingPosition. The TB success rate is defined as 100%*NDL_correct_rx/ (NDL_newtx + NDL_retx), where NDL_newtx is the number of newly transmitted DL transport blocks, NDL_retx is the number of retransmitted DL transport blocks, and NDL_correct_rx is the number of correctly received DL transport blocks. The TB success rate shall be sustained during at least 300 frames. Table 8.7.12.2-2: Per-CC FRC for SDR test (64QAM) Table 8.7.12.2-3: Per-CC FRC for SDR test (256QAM) CA configuration, bandwidth combination and MIMO layer on each CC is determined by following procedure. - Select one CA bandwidth combination among all supported CA configurations with bandwidth combination and MIMO layer on each CC following the equation that leads to largest equivalent aggregated bandwidth among all CA bandwidth combinations supported by UE. Equivalent aggregated bandwidth is defined as where is number of CCs, and is MIMO layer and bandwidth of CC . - When there are multiple sets of {CA configuration, bandwidth combination, MIMO layer} with same largest aggregated bandwidth, select one among sets with largest number of 4 layer CCs. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.7.12.2 |
2,444 | 8.1.2.4 Test coverage for different number of component carriers | For FDD tests specified in 8.2.1.1.1, 8.2.1.3.1, 8.2.1.4.3, and 8.7.1, if corresponding CA tests are tested, the test coverage can be considered fulfilled without executing single carrier tests. For TDD tests specified in 8.2.2.1.1, 8.2.2.3.1, 8.2.2.4.3, and 8.7.2, if corresponding CA tests are tested, the test coverage can be considered fulfilled without executing single carrier tests. For TDD FDD tests specified in 8.2.3.1, 8.2.3.2, 8.2.3.3, 8.2.3.5, and 8.7.5, if corresponding TDD FDD CA tests are tested, the test coverage can be considered fulfilled without executing both FDD and TDD single carrier tests. For FDD CA tests specified in 8.2.1.1.1, 8.2.1.4.3, 8.7.1, 8.13.1.1.1 and 8.13.1.2.1, among all supported CA capabilities, if corresponding CA tests with the largest number of CCs supported by the UE are tested, the test coverage can be considered fulfilled without executing the CA tests with less than the largest number of CCs supported by the UE. For FDD CA tests specified in 8.2.1.3.1, for each supported CA capability, if corresponding CA tests with the largest number of CCs supported by the UE are tested, the test coverage can be considered fulfilled without executing the CA tests with less than the largest number of CCs supported by the UE. For TDD CA tests specified in 8.2.2.1.1, 8.2.2.4.3, 8.7.2, 8.13.2.1.1 and 8.13.2.2.1, among all supported CA capabilities, if corresponding CA tests with the largest number of CCs supported by the UE are tested, the test coverage can be considered fulfilled without executing the CA tests with less than the largest number of CCs supported by the UE. For TDD CA tests specified in 8.2.2.3.1, for each supported CA capability, if corresponding CA tests with the largest number of CCs supported by the UE are tested, the test coverage can be considered fulfilled without executing the CA tests with less than the largest number of CCs supported by the UE. For TDD FDD CA tests specified in 8.2.3.1, 8.2.3.3, 8.7.5, 8.13.3.1 and 8.13.3.2, among all supported CA capabilities, if corresponding CA tests with the largest number of CCs supported by the UE are tested, the test coverage can be considered fulfilled without executing the TDD FDD CA tests with less than the largest number of CCs supported by the UE. For TDD FDD CA tests specified in 8.2.3.2 and 8.2.3.5, for each supported CA capability, if corresponding CA tests with the largest number of CCs supported by the UE are tested, the test coverage can be considered fulfilled without executing the TDD FDD CA tests with less than the largest number of CCs supported by the UE. For FDD CA power imbalance tests specified in 8.2.1.7.1, if they are are tested with FDD intra-band contiguous CA configurations with 2 DL CCs, the test coverage can be considered fulfilled with FDD intra-band contiguous CA configurations with 3 or more DL CCs supported by the UE. For TDD CA power imbalance tests specified in 8.2.2.7.1, if they are are tested with TDD intra-band contiguous CA configurations with 2 DL CCs, the test coverage can be considered fulfilled with TDD intra-band contiguous CA configurations with 3 or more DL CCs supported by the UE. For FDD DC tests specified in 8.2.1.4.3A, 8.7.6 and 8.13.1.1.2, among all supported DC capabilities, if corresponding DC tests with the largest number of CCs supported by the UE are tested, the test coverage can be considered fulfilled without executing the DC tests with less than the largest number of CCs supported by the UE. For TDD DC tests specified in 8.2.2.4.3A, 8.7.7 and 8.13.2.1.2, among all supported DC capabilities, if corresponding DC tests with the largest number of CCs supported by the UE are tested, the test coverage can be considered fulfilled without executing the DC tests with less than the largest number of CCs supported by the UE. For TDD FDD DC tests specified in 8.2.3.4, 8.7.8 and 8.13.3.5, among all supported DC capabilities, if corresponding DC tests with the largest number of CCs supported by the UE are tested, the test coverage can be considered fulfilled without executing the DC tests with less than the largest number of CCs supported by the UE. For LAA SCell(s) with FDD PCell tests specified in 8.2.4.1.1 and 8.3.3.1.1, for each supported CA capability, if corresponding CA with LAA SCell(s) tests with the largest number of CCs supported by the UE are tested, the test coverage can be considered fulfilled without executing the CA with LAA SCell(s) tests with less than the largest number of CCs supported by the UE. For LAA SCell(s) with TDD PCell tests specified in 8.2.4.1.2 and 8.3.3.1.2, for each supported CA capability, if corresponding CA with LAA SCell(s) tests with the largest number of CCs supported by the UE are tested, the test coverage can be considered fulfilled without executing the CA with LAA SCell(s) tests with less than the largest number of CCs supported by the UE. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.1.2.4 |
2,445 | 5.9.2 Scenario | A UAV, remotely controlled by a UAV controller, both of which are connected through cellular network, is flying away from the UAV controller beyond certain range limit which is based on the type, subscription information, or characteristic of the UAV. The UAV and the UAV controller are transmitting their accurate positional information, which may be supplemented by the serving MNO, to the UTM. The UTM notices that the UAV is flying over the range from the UAV controller basing on the information from UAV and UAV controller, as well as may come from network, the UTM decides to send a warning to the UAS operator (via the UAV controller). If UAV has reached certain threshold, the UTM may decide to intervene to force the UAV to fly closer back to the UAV controller or fly back to the area which it is allowed to fly in. If the UAV flies into different roaming area, different or additional charging rule may be applied by the MNO. | 3GPP TS 22.825 | Study on Remote Identification of Unmanned Aerial Systems (UAS) | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 5.9.2 |
2,446 | 4.27 Procedures for Enhanced Coverage Restriction Control via NEF 4.27.1 General | The support for Enhanced Coverage Restriction Control via NEF enables AF to query status of Enhanced Coverage Restriction or enable/disable Enhanced Coverage Restriction per individual UEs. Figure 4.27.1-1 shows the procedure for Enhanced Coverage Restriction Control via NEF. Figure 4.27.1-1: Enhanced Coverage Restriction Control via NEF 1. The AF may enable or disable Enhanced Coverage Restriction or query the status of Enhanced Coverage Restriction by sending the Nnef_ECRestriction_Update Request or Nnef_ECRestriction_Get Request respectively. Both the service operations require GPSI and AF Identifier as required input and optionally MTC Provider Information. 2. Based on operator policies, if the AF is not authorized to perform the request (e.g. if the SLA does not allow for it) or if the AF has exceeded its quota or rate of submitting Enhanced Coverage Requests, the NEF performs Step 8 and provides a cause value appropriately indicating the failure result. 3. The NEF sends the Nudm_ParameterProvision_Update Request to update the subscription data for Enhanced Coverage Restriction. The NEF sends the Nudm_SDM_Get Request service operation to query the status of Enhanced Coverage Restriction. 4. The UDM checks the GPSI and examines whether any included parameters are in the range acceptable by the operator, whether Enhanced Coverage Restriction is supported by the serving NF (i.e. AMF in this case). If this check fails, the UDM provides a cause value indicating the reason for failure condition to the NEF in step 7 In the case of Nudm_ParameterProvision_Update Request, the UDM sets the Enhanced Coverage Restriction information to the appropriate value and procedure continues to step 5. In the case of Nudm_SDM_Get Request, the UDM may retrieve the status of Enhanced Coverage Restriction information from UDR using Nudr_DM_Query Request and skip steps 5 and 6. 5. The UDM sends Nudm_SDM_Notification and provide AMF with updates Enhanced Coverage Restriction information. 6. The AMF updates the Enhanced Coverage Restriction information stored in the UE context. The AMF will transfer Enhanced Coverage Restriction information stored as part of its UE context during AMF change. NOTE: UE is informed of the updated Enhanced Coverage Restriction information at the next Registration procedure or based on the local policy the network can de-register the UE indicating re-registration is required. 7. The UDM sends the Nudm_ParameterProvision_Update Response or Nudm_SDM_Get Response to the NEF. 8. The NEF sends the Nnef_ECRestriction_Update Response or Nnef_ECRestriction_Get Response to the AF. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.27 |
2,447 | 5.3.6.3 In-call modification in the "active" state | The in-call modification procedure as described in subclause 5.3.4.3 shall be used to: - trigger a service change between speech and UDI/RDI multimedia modes, when service change has been agreed at call setup; - trigger a network-initiated service upgrade from speech to UDI/RDI multimedia modes (see 3GPP TS 23.172[ Technical realization of Circuit Switched (CS) multimedia service UDI/RDI fallback and service modification; Stage 2 ] [97]). The network shall initiate this procedure only if the mobile station indicated support of the enhanced network-initiated in-call modification procedure in the Call Control Capabilities IE at call establishment. In this case, the MODIFY message shall include the Network-initiated Service Upgrade indicator IE; or - modify the multimedia bearer capability for an analogue multimedia call (restricted to the network initiated in-call modification only). In this case, the network shall send a MODIFY message including the new Bearer Capability to be changed to. The following bearer capability parameters can be modified with the procedure (see 3GPP TS 29.007[ General requirements on interworking between the Public Land Mobile Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN) ] [38]): - Fixed Network User Rate (analogue multimedia calls only). | 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.6.3 |
2,448 | 5.7.1.1 QoS Flow | The 5G QoS model is based on QoS Flows. The 5G QoS model supports both QoS Flows that require guaranteed flow bit rate (GBR QoS Flows) and QoS Flows that do not require guaranteed flow bit rate (Non-GBR QoS Flows). The 5G QoS model also supports Reflective QoS (see clause 5.7.5). The QoS Flow is the finest granularity of QoS differentiation in the PDU Session. A QoS Flow ID (QFI) is used to identify a QoS Flow in the 5G System. User Plane traffic with the same QFI within a PDU Session receives the same traffic forwarding treatment (e.g. scheduling, admission threshold). The QFI is carried in an encapsulation header on N3 (and N9) i.e. without any changes to the e2e packet header. QFI shall be used for all PDU Session Types. The QFI shall be unique within a PDU Session. The QFI may be dynamically assigned or may be equal to the 5QI (see clause 5.7.2.1). Within the 5GS, a QoS Flow is controlled by the SMF and may be preconfigured, or established via the PDU Session Establishment procedure (see clause 4.3.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]), or the PDU Session Modification procedure (see clause 4.3.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. Any QoS Flow is characterised by: - A QoS profile provided by the SMF to the AN via the AMF over the N2 reference point or preconfigured in the AN; - One or more QoS rule(s) and optionally QoS Flow level QoS parameters (as specified in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]) associated with these QoS rule(s) which can be provided by the SMF to the UE via the AMF over the N1 reference point and/or derived by the UE by applying Reflective QoS control; and - One or more UL and DL PDR(s) provided by the SMF to the UPF. Within the 5GS, a QoS Flow associated with the default QoS rule is required to be established for a PDU Session and remains established throughout the lifetime of the PDU Session. This QoS Flow should be a Non-GBR QoS Flow (further details are described in clause 5.7.2.7). A QoS Flow is associated with QoS requirements as specified by QoS parameters and QoS characteristics. NOTE: The QoS Flow associated with the default QoS rule provides the UE with connectivity throughout the lifetime of the PDU Session. Possible interworking with EPS motivates the recommendation for this QoS Flow to be of type Non-GBR. A QoS Flow may be enabled with PDU Set based QoS handling as described in clause 5.37.5. For such QoS Flows, PDU Set QoS Parameters (see clause 5.7.7) are determined by the PCF and provided by SMF to the NG-RAN as part of the QoS profile. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.7.1.1 |
2,449 | 8.1.3 UE category and UE DL category | UE category and UE DL category refer to ue-Category and ue-CategoryDL define in 4.1 and 4.1A from [12]. A UE that belongs to either a UE category or a UE DL category indicated in UE performance requirements in subclause 8, 9, 10 shall fulfil the corresponding requirements. A UE indicating DL category 13 may indicate category 9 or 10 and shall thereby fulfil all requirements in subclause 8, 9, 10 that are indicated for either cat 9 or DL Cat 13 UEs. For SDR tests in section 8.7 both cat 9 and cat 13 test shall be used for this UE while for the other test only Cat 13 tests needs to be done. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.1.3 |
2,450 | 13.4.1.3.1.2 Without mutual authentication between NF and NRF at the transport layer | When there is no mutual authentication between NF Service Consumer and NRF at the transport layer, the NF Service Consumer performs the following procedure to obtain the access token from NRF and uses it for service access at the NF Service Producer. In this clause, the authentication of NF Service Consumer by the NRF and by the NF Service Producer is based on any of the methods described in clauses 13.3.1.2 and 13.3.2.2. Figure 13.4.1.3.1.2-1: Authorization and service invocation procedure, for indirect communication without delegated discovery, without mutual authentication between NF and NRF at the transport layer 0. Optionally, the NF Service Consumer may discover the NF Service Producer before requesting authorization to invoke the services of the NF Service Producer. 1. The NF Service Consumer sends an access token request (Nnrf_AccessToken_Get Request) to the SCP with parameters as specified in 13.4.1.1. The access token request may additionally include the NF Service Consumer CCA as defined in clause 13.3.8. If the CCA is included, the NF type of the expected audience in CCA shall contain NF type "NRF". 2. The SCP forwards the access token request (Nnrf_AccessToken_Get Request) to the NRF. The request may include the NF Service Consumer CCA if received in step 1. 3. The NRF authenticates the service consumer NF using one of the methods described in clause 13.3.1.2. If the NF Service Consumer authentication is successful and the NF Service Consumer is authorized based on the NRF policy, the NRF issues an access token as described in clause 13.4.1.1. The NRF uses the NF Service Consumer NF Instance ID as the subject of the access token. 4. The NRF sends the access token to the SCP in an access token response (Nnrf_AccessToken_Get Response). 5. The SCP forwards the access token response (Nnrf_AccessToken_Get Response) to the NF Service Consumer, including the access token. 6. The NF Service Consumer sends the service request to the SCP. The service request includes the access token received in Step 5 and may include the NF Service Consumer CCA. If the CCA is included, the NF type of the expected audience in CCA shall contain the NF type of the NF Service Producer . If the NF Service Consumer allows reselection of a target NF Service Producer by the SCP, the expected audience in the CCA shall also contain NF type "NRF". NOTE: In the same deployment, the NF Service Consumer can delegate the reselection of the target NF Service Producer to the SCP for some requests, and not for other requests. 7. The SCP forwards the service request to the NF Service Producer. The service request includes the access token received in step 6, and may include the NF Service Consumer CCA if received in step 6. 8. The NF Service Producer authenticates the NF Service Consumer by one of the methods described in clause 13.3.2.2 and if successful, it validates the access token as described in clause 13.4.1.1. 9. If the validation of the access token is successful, the NF Service Producer sends the service response to the SCP. 10. The SCP forwards the service response to the NF Service Consumer. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 13.4.1.3.1.2 |
2,451 | 7.3.20 ISR Status Indication | A ISR Status Indication message shall be sent on the S3 interface by the MME/SGSN to the ISR associated SGSN/MME as part of the following procedures: - the Restoration of PDN connections after an SGW failure for UEs with ISR as specified in 3GPP TS 23.007[ Restoration procedures ] [17]; - the HSS Based P-CSCF restoration procedure for 3GPP access (for both basic and PCO extension) as specified in 3GPP TS 23.380[ IMS Restoration Procedures ] [61]. Table 7.3.20-1 specifies the presence of the IEs in the message. Table 7.3.20-1: Information Elements in an ISR Status Indication | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 7.3.20 |
2,452 | 9.2.1 Resource grid | A transmitted physical channel or signal in a slot is described by a resource grid of subcarriers and SC-FDMA symbols. The sidelink bandwidth if the S criterion according to [10, clause 5.2.3.2] is fulfilled for a serving cell having the same uplink carrier frequency as the sidelink, otherwise a preconfigured value is used [9]. The sidelink cyclic prefix is configured independently for type 1 discovery, type 2B discovery, sidelink transmission mode 1, sidelink transmission mode 2, control signalling, and PSBCH and synchronization signals. Configuration is per resource pool for discovery, sidelink transmission mode 2, and control signalling. The PSBCH and synchronization signals always use the same cyclic prefix. Only normal cyclic prefix is supported for PSSCH, PSCCH, PSBCH, and synchronization signals for a sidelink configured with transmission mode 3 or 4. The resource grid is illustrated in Figure 5.2.1-1. An antenna port is defined such that the channel over which a symbol on the antenna port is conveyed can be inferred from the channel over which another symbol on the same antenna port is conveyed. There is one resource grid per antenna port. The antenna ports used for transmission of a physical channel or signal are shown in Table 9.2.1-1. Table 9.2.1-1: Antenna ports used for different physical channels and signals | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.2.1 |
2,453 | L.4 C-SGN | The C-SGN (CIoT Serving Gateway Node) is a combined node EPC implementation option that minimizes the number of physical entities by collocating EPS entities in the control and user planes paths (e.g. MME, S-GW, P-GW), which may be preferred in CIoT deployments. The external interfaces of C-SGN implementation option are the interfaces of the respective EPC entity supported by the C-SGN, such as MME, S-GW, and P-GW. A C-SGN supports sub-set and necessary functionalities compared with the existing EPS core network elements and also supports at least some of the following CIoT EPS Optimisations: - Control Plane CIoT EPS Optimisation for small data transmission. - User Plane CIoT EPS Optimisation for small data transmission. - Necessary security procedures for efficient small data transmission. - SMS without combined attach for NB-IoT only UEs. - Paging optimisations for coverage enhancements. - Support for non-IP data transmission via SGi tunnelling and/or SCEF. - Support for Attach without PDN connectivity. | 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") | L.4 |
2,454 | 8.2.2.3 UE – SMF | The NAS-SM supports the handling of Session Management between the UE and the SMF. The SM signalling message is handled, i.e. created and processed, in the NAS-SM layer of UE and the SMF. The content of the SM signalling message is not interpreted by the AMF. The NAS-MM layer handles the SM signalling is as follows: - For transmission of SM signalling: - The NAS-MM layer creates a NAS-MM message, including security header, indicating NAS transport of SM signalling, additional information for the receiving NAS-MM to derive how and where to forward the SM signalling message. - For reception of SM signalling: - The receiving NAS-MM processes the NAS-MM part of the message, i.e. performs integrity check, and interprets the additional information to derive how and where to derive the SM signalling message. The SM message part shall include the PDU Session ID. Legend: - NAS-SM: The NAS protocol for SM functionality supports user plane PDU Session Establishment, modification and release. It is transferred via the AMF, and transparent to the AMF. 5G NAS protocol is defined in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47] Figure 8.2.2.3-1: Control Plane protocol stack between the UE and the SMF | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 8.2.2.3 |
2,455 | 8.14.1.1 Signalling of RLF information from gNB-CU to gNB-DU | The signalling flow for signalling of RLF information from gNB-CU to gNB-DU is shown in Figure 8.14.1.1-1, where the example where NG-RAN nodes exchange the RLF Report via the Xn: FAILURE INDICATION message has been considered. Figure 8.14.1.1-1 Example of signalling of RLF information from gNB-CU to gNB-DU in NG RAN 1. A UE with a logged RLF Report connects to a cell in gNB2 and it signals the RLF Report to gNB2 by means of the RRC UE Information Request/Response procedures. 2. The gNB2 sends an Xn: Failure Indication to gNB1-CU where the UE may have previously been connected prior to the connection failure. This includes also the RLF Report. 3. The gNB1-CU sends the F1: Access and Mobility Indication message to the gNB1-DU, including the RLF Report. It is also possible for the gNB-CU receiving the RLF Report from the UE to signal it directly to the gNB-DU by means of the F1: Access and Mobility Indication procedure. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.14.1.1 |
2,456 | 8.13.1.2.1 Minimum Requirement Dual-Layer Spatial Multiplexing 2 Tx Antenna Port | For CA with 2 DL CCs, for dual-layer transmission on antenna ports 7 and 8 upon detection of a PDCCH with DCI format 2C, the requirements are specified in Table 8.13.1.2.1-3, based on single carrier requirement specified in Table 8.13.1.2.1-2, with the addition of the parameters in Table 8.13.1.2.1-1 and the downlink physical channel setup according to Annex C.3.2. For CA with 3 DL CCs, for dual-layer transmission on antenna ports 7 and 8 upon detection of a PDCCH with DCI format 2C, the requirements are specified in Table 8.13.1.2.1-4, based on single carrier requirement specified in Table 8.13.1.2.1-2, with the addition of the parameters in Table 8.13.1.2.1-1 and the downlink physical channel setup according to Annex C.3.2. For CA with 4 DL CCs, for dual-layer transmission on antenna ports 7 and 8 upon detection of a PDCCH with DCI format 2C, the requirements are specified in Table 8.13.1.2.1-5, based on single carrier requirement specified in Table 8.13.1.2.1-2, with the addition of the parameters in Table 8.13.1.2.1-1 and the downlink physical channel setup according to Annex C.3.2. For CA with 5 DL CCs, for dual-layer transmission on antenna ports 7 and 8 upon detection of a PDCCH with DCI format 2C, the requirements are specified in Table 8.13.1.2.1-6, based on single carrier requirement specified in Table 8.13.1.2.1-2, with the addition of the parameters in Table 8.13.1.2.1-1 and the downlink physical channel setup according to Annex C.3.2. The test coverage for different number of component carriers is defined in 8.1.2.4. Table 8.13.1.2.1-1: Test Parameters for Multi-Layer Spatial Multiplexing (FRC) for CA Table 8.13.1.2.1-2: Single carrier performance for multiple CA configurations Table 8.13.1.2. 1-3: Minimum performance (FRC) based on single carrier performance for CA with 2 DL CCs Table 8.13.1.2.1-4: Minimum performance (FRC) based on single carrier performance for CA with 3 DL CCs Table 8.13.1.2.1-5: Minimum performance (FRC) based on single carrier performance for CA with 4 DL CCs Table 8.13.1.2.1-6: Minimum performance (FRC) based on single carrier performance for CA with 5 DL CCs | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.13.1.2.1 |
2,457 | 5.4.13.2 Coverage availability information provisioning to the UE | A UE may use satellite coverage availability information for satellite access to support discontinuous coverage operations. Satellite coverage availability information can be provided to a UE by an external server via a PDU Session or SMS. The protocol and format of satellite coverage availability information via PDU session or SMS is not defined in this release of the specification, but some examples on possible information that constitutes the satellite coverage availability information is defined in Annex Q. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.4.13.2 |
2,458 | 13.2.4 N32-f connection between SEPPs 13.2.4.1 General | The SEPP receives HTTP/2 request/response messages from the Network Function. It shall perform the following actions on these messages before they are sent on the N32-f interface to the SEPP in the other PLMN: a) It parses the incoming message and, if present, rewrites the telescopic FQDN of the receiving NF to obtain the original FQDN as described in clause 13.1. b) It reformats the message to produce the input to JSON Web Encryption (JWE) [59] as described in clause 13.2.4.3. c) It applies JWE to the input created in b) to protect the reformatted message as described in clause 13.2.4.4. d) It encapsulates the resulting JWE object into a HTTP/2 message (as the body of the message) and sends the HTTP/2 message to the SEPP in the other PLMN over the N32-f interface. The message may be routed via the cIPX and pIPX nodes. These IPX nodes may modify messages as follows: a) The IPX node recovers the cleartext part of the HTTP message from the JWE object, modifies it according to the modification policy, and calculates an "operations" JSON Patch object. It then creates a temporary JSON object with the "operators" JSON Patch object and some other parameters for replay protection etc. as described in clause 13.2.4.5.1. b) The IPX node uses the temporary JSON object as input into JSON Web Signature (JWS) [45] to create a JWS object, as described in clause 13.2.4.5.2. c) The IPX node appends the JWS object to the received message and sends it to the next hop. The JWS objects generated by the two IPX providers form an auditable chain of modifications that to the receiving SEPP shall apply to the parsed message after verifying that the patches conform to the modification policy. Encryption of IEs shall take place end to end between cSEPP and pSEPP. A SEPP shall not include IEs in the clear that are encrypted elsewhere in the JSON object. A SEPP shall verify that an intermediate IPX has not moved or copied an encrypted IE to a location that would be reflected from the producer NF in an IE without encryption. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 13.2.4 |
2,459 | 5.5.1.2.5B Attach for initiating a PDN connection for emergency bearer services not accepted by the network | If the network cannot accept an attach request with attach type not set to "EPS emergency attach" and including a PDN CONNECTIVITY REQUEST message with request type set to "emergency", the UE shall perform the procedures as described in clause 5.5.1.2.5. If the attach request with attach type not set to "EPS emergency attach" for initiating a PDN connection for emergency bearer services fails due to receiving the AUTHENTICATION REJECT message, the UE shall perform the procedures as described in clause 5.4.2.5. Then if the UE is in the same selected PLMN where the last attach request was attempted, the UE shall: a) inform the upper layers of the failure of the procedure; or NOTE 1: This can result in the upper layers requesting establishment of a CS emergency call (if not already attempted in the CS domain) or other implementation specific mechanisms, e.g. procedures specified in 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [13D] can result in the emergency call being attempted to another IP-CAN. b) attempt EPS attach for emergency bearer services including the PDN CONNECTIVITY REQUEST message. If the network cannot accept an attach request with attach type not set to "EPS emergency attach" and including a PDN CONNECTIVITY REQUEST message with request type set to "handover of emergency bearer services", the UE shall perform the procedures as described in clause 5.5.1.2.5. Then if the UE is in the same selected PLMN or equivalent PLMN where the last attach request was attempted, the UE shall attempt EPS attach for emergency bearer services including the PDN CONNECTIVITY REQUEST message. If the attach request with attach type not set to "EPS emergency attach" for initiating a PDN connection for emergency bearer services fails due to abnormal case a) in clause .2.6, the UE shall perform the actions as described in clause 5.5.1.2.6 and inform the upper layers of the failure to access the network. NOTE 2: This can result in the upper layers requesting establishment of a CS emergency call (if not already attempted in the CS domain) or other implementation specific mechanisms, e.g. procedures specified in 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [13D] can result in the emergency call being attempted to another IP-CAN. If the attach request with attach type not set to "EPS emergency attach" and including a PDN CONNECTIVITY REQUEST message with request type set to "emergency" fails due to abnormal cases b), c) or d) as well as l) when the "Extended wait time" is ignored, and la) when the "Extended wait time CP data" is ignored in clause .2.6, the UE shall perform the procedures as described in clause 5.5.1.2.6. Then if the UE is in the same selected PLMN where the last attach request was attempted, the UE shall: a) inform the upper layers of the failure of the procedure; or NOTE 3: This can result in the upper layers requesting establishment of a CS emergency call (if not already attempted in the CS domain) or other implementation specific mechanisms, e.g. procedures specified in 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [13D] can result in the emergency call being attempted to another IP-CAN. b) attempt EPS attach for emergency bearer services including the PDN CONNECTIVITY REQUEST message. If the attach request with attach type not set to "EPS emergency attach" and including a PDN CONNECTIVITY REQUEST message with request type set to "handover of emergency bearer services" fails due to abnormal cases b), c), d) or o) in clause .2.6, the UE shall perform the procedures as described in clause 5.5.1.2.6. Then if the UE is in the same selected PLMN or equivalent PLMN where the last attach request was attempted, the UE shall attempt EPS attach for emergency bearer services including the PDN CONNECTIVITY REQUEST message. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.1.2.5B |
2,460 | 16.14.9 Support for NR NTN coverage enhancements | To improve NR uplink coverage in NTN, the following enhancements are supported: - PUCCH repetition for Msg4 HARQ-ACK configured in system information or dynamically in DCI for Msg4 when multiple repetition factors are configured in the system information: - UEs reports the capability of PUCCH repetition for Msg4 HARQ-ACK in Msg3 PUSCH; - When Msg4 HARQ-ACK is repeated, PUCCH repetition is applied for all PUCCH transmission before dedicated PUCCH resource is provided. - Improved channel estimation by NTN-specific PUSCH DMRS bundling enhancement that enables DMRS bundling in presence of timing drift, where the UE can maintain phase continuity by considering effects of transmission delay variation between the UE and the uplink time synchronization reference point. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.14.9 |
2,461 | 9.8.2.2 TDD | The following requirements apply to UE supporting coverage enhancement. For the parameters specified in Table 9.8.2.2-1, and using the downlink physical channels specified in Annex C.3.2, the minimum requirements are specified in Table 9.8.2.2-2 and by the following a) the ratio of the throughput obtained when transmitting on the best narrowband reported by the UE the corresponding TBS and that obtained when transmitting the TBS indicated by the reported wideband CQI median on a randomly selected narrowband within the set of narrowbands in which MPDCCH is monitored shall be ≥ ; The requirements only apply for subbands of full size and the random scheduling across the subbands is done by selecting a new narrowband in each available downlink transmission instance for TDD. The transport block size TBS (wideband CQI median) is that resulting from the code rate which is closest to that indicated by the wideband CQI median and theentry in Table 7.1.7.2.1-1 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [6] that corresponds to the narrowband size. Table 9.8.2.2-1 Sub-band test for single antenna transmission (TDD) Table 9.8.2.2-2 Minimum requirement (TDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.8.2.2 |
2,462 | C.3.3 Processing on home network side | The ECIES scheme shall be implemented such that for deconcealing a SUCI, the home network shall use the received ECC ephemeral public key of the UE and the private key of the home network. The processing on home network side shall be done according to the decryption operation defined in [29]. with the following changes to Section 3.8 and step 6 and 7 of Section 5.1.4. - generate keying data K of length enckeylen + icblen + mackeylen. - Parse the leftmost enckeylen octets of K as an encryption key EK, the middle icblen octets of K as an ICB, and the rightmost mackeylen octets of K as a MAC key MK. NOTE: Unlike the UE, the home network does not need to perform a fresh ephemeral key pair generation for each decryption. How often the home network generates new public/private key pair and how the public key is provisioned to the UE are out of the scope of this clause. The Figure C.3.3-1 illustrates the home network's steps. Figure C.3.3-1: Decryption based on ECIES at home network | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | C.3.3 |
2,463 | 7.3.10 Forward Access Context Notification | A Forward Access Context Notification message shall be sent from the Old SGSN to the New SGSN over the S16 interface to forward the RNC contexts to the target system, or sent from the Old MME to the New MME over the S10 interface to forward the RNC/eNodeB contexts to the target system. When the old SGSN receives the RANAP message Forward SRNS Context, the old SGSN shall send a Forward Access Context Notification message to the new SGSN. The new SGSN shall forward the message to the target RNC using the corresponding RANAP message. When the old SGSN receives a BSSGP message PS handover Required and the acknowledged peer-to-peer LLC operation is used for the Bearer Context or when "delivery order" is set in the Bearer Context QoS profile, the old SGSN shall send a Forward Access Context Notification message with the PDU Number IE to the new SGSN. The new SGSN shall forward the message to the target RNC/ target BSS using the corresponding RANAP message only for PS handover to Iu mode. When the old SGSN receives a BSSGP message PS handover Required from source BSS/RNC for PS handover to A/Gb mode, the value part of RAB Context IE shall be empty according to its defined minimum length. Table -1 specifics the presence requirements and conditions of the IEs in the message. Table 7.3.10-1: Information Elements in a Forward Access Context Notification | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 7.3.10 |
2,464 | 5.3.5.5.11 BH RLC channel addition/modification | For each BH-RLC-ChannelConfig received in the bh-RLC-ChannelToAddModList IE the IAB-node shall: 1> if the current configuration contains a BH RLC Channel with the received bh-RLC-ChannelID within the same cell group: 2> if reestablishRLC is received: 3> re-establish the RLC entity as specified in TS 38.322[ NR; Radio Link Control (RLC) protocol specification ] [4]; 2> reconfigure the RLC entity or entities in accordance with the received rlc-Config; 2> reconfigure the logical channel in accordance with the received mac-LogicalChannelConfig; 1> else (a backhaul logical channel with the given BH-RLC-ChannelID was not configured before within the same cell group): 2> establish an RLC entity in accordance with the received rlc-Config; 2> configure this MAC entity with a logical channel in accordance to the received mac-LogicalChannelConfig. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.5.5.11 |
2,465 | 12.3.13 Implicit overload control mechanisms | Implicit overload control mechanisms are mechanisms used between GTP-C entities when GTP-C overload control is not supported or not enabled between them, e.g. across PLMN boundary based on operator's policy, to help reducing the overload at the overloaded node: - a GTP-C entity which decides to not process an incoming request message due to overload should still send a reject response message, if possible, indicating the temporary unavailability of the resources, e.g. No resources available; otherwise the GTP-C entity may drop the incoming request message. NOTE: Without a response message, the source GTP-C entity cannot determine whether the request did not reach the target GTP-C entity due to a network error or whether the target GTP-C entity was in overload and not able to process the request and send a response message. This will cause the source GTP-C entity to retransmit the request message and hence will increase further the overload at the target node. - a GTP-C entity in overload may support messages throttling as a self protection mechanism and may apply message prioritization as described in clause 12.3.9.3 when selecting the incoming request messages to be throttled; - based on the number and rate of reject responses indicating temporary unavailability of resources, e.g. No resources available, a source GTP-C entity should try to assess the overload level of the target GTP-C entity and apply correspondingly message throttling as described in clause 12.3.9 to reduce the amount of traffic sent towards the overloaded GTP-C entity. | 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.13 |
2,466 | 5.6.1.7 Abnormal cases in the UE | The following abnormal cases can be identified: a) T3517 expired. The UE shall enter the state 5GMM-REGISTERED. If the UE triggered the service request procedure in 5GMM-IDLE mode sending a: 1) SERVICE REQUEST message and the service type of the SERVICE REQUEST message was not set to "emergency services fallback"; or 2) CONTROL PLANE SERVICE REQUEST message and the control plane service type of the CONTROL PLANE SERVICE REQUEST message was not set to "emergency services fallback"; then the 5GMM sublayer shall increment the service request attempt counter, abort the procedure and release locally any resources allocated for the service request procedure. The service request attempt counter shall not be incremented, if: 1) the service request procedure is initiated to establish an emergency PDU session; 2) the UE has an emergency PDU session established; 3) the UE is a UE configured for high priority access in selected PLMN or SNPN; 4) the service request procedure is initiated in response to paging or notification from the network; or 5) the UE in NB-N1 mode is requested by the upper layer to transmit user data related to an exceptional event and the UE is allowed to use exception data reporting (see the ExceptionDataReportingAllowed leaf of the NAS configuration MO in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [17] or the USIM file EFNASCONFIG in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [22]). If the service request attempt counter is greater than or equal to 5, the UE shall start timer T3525. Additionally, if the service request procedure was initiated for an MO MMTEL voice call or for an MO MMTEL video call or for an MO IMS registration related signalling, a notification that the service request was not initiated due to the UE having started timer T3525 shall be provided to the upper layers. NOTE 1: This can result in the upper layers requesting implementation specific mechanisms, e.g. the MMTEL voice call being attempted to another IP-CAN, or establishment of a CS voice call (if supported and not already attempted in the CS domain). The UE shall not attempt service request until expiry of timer T3525 unless: 1) the service request procedure is initiated in response to paging or notification from the network; 2) the UE is a UE configured for high priority access in selected PLMN or SNPN; 3) the service request procedure is initiated to establish an emergency PDU session; 4) the UE has an emergency PDU session established; 5) the service request procedure is initiated for emergency services fallback; 6) the UE is registered in a new PLMN; NOTE 2: According to Table 10.2.1, when "UE camped on a new PLMN other than the PLMN on which timer started", timer T3525 is stopped, hence this check may be skipped. 7) the UE in NB-N1 mode is requested by the upper layer to transmit user data related to an exceptional event and the UE is allowed to use exception data reporting (see the ExceptionDataReportingAllowed leaf of the NAS configuration MO in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [17] or the USIM file EFNASCONFIG in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [22]); or 8) the UE supports the reconnection to the network due to RAN timing synchronization status change and receives an indication of a change in the RAN timing synchronization status. NOTE 3: The NAS signalling connection can also be released if the UE deems that the network has failed the authentication check as specified in subclause 5.4.1.3.7. If the UE triggered the service request procedure in 5GMM-CONNECTED mode sending a: 1) SERVICE REQUEST message and the service type of the SERVICE REQUEST message was not set to "emergency services fallback"; or 2) CONTROL PLANE SERVICE REQUEST message and the control plane service type of the CONTROL PLANE SERVICE REQUEST message was not set to "emergency services fallback", the 5GMM sublayer shall abort the procedure, and stay in 5GMM-CONNECTED mode. If the service type of the SERVICE REQUEST message was set to "emergency services fallback" or the control plane service type of the CONTROL PLANE SERVICE REQUEST message was set to "emergency services fallback" and: 1) the service request procedure was triggered in 5GMM-IDLE mode, the 5GMM sublayer shall abort the procedure, release locally any resources allocated for the service request procedure; or 2) the service request procedure was triggered in 5GMM-CONNECTED mode, the 5GMM sublayer shall abort the procedure, stay in 5GMM-CONNECTED mode. b) The lower layers indicate that the access attempt is barred. The UE shall not start the service request procedure. The UE stays in the current serving cell and applies the normal cell reselection process. Receipt of the access barred indication shall not trigger the selection of a different core network type (EPC or 5GCN). The service request procedure is started, if still needed, when the lower layers indicate that the barring is alleviated for the access category with which the access attempt was associated. ba) The lower layers indicate that: 1) access barring is applicable for all access categories except categories 0 and 2 and the access category with which the access attempt was associated is other than 0 and 2; or 2) access barring is applicable for all access categories except category 0 and the access category with which the access attempt was associated is other than 0. If the SERVICE REQUEST message or CONTROL PLANE SERVICE REQUEST has not been sent, the UE shall proceed as specified for case b. If the SERVICE REQUEST message or CONTROL PLANE SERVICE REQUEST has been sent: 1) the UE shall abort the service request procedure and stop timer T3517. The UE stays in the current serving cell and applies the normal cell reselection process; and 2) the service request procedure is started, if still needed, when the lower layers indicate that the barring is alleviated for the access category with which the access attempt was associated. For additional UE requirements for both cases see subclause 4.5.5. c) Timer T3346 is running. The UE shall not start the service request procedure unless: 1) the UE receives a paging; 2) the UE receives a NOTIFICATION message over non-3GPP access when the UE is in 5GMM-CONNECTED mode over non-3GPP access and in 5GMM-IDLE mode over 3GPP access; 3) the UE receives a NOTIFICATION message over 3GPP access when the UE is in 5GMM-CONNECTED mode over 3GPP access and in 5GMM-IDLE mode over non-3GPP access; 4) the UE is a UE configured for high priority access in selected PLMN or SNPN; 5) the UE has an emergency PDU session established or is establishing an emergency PDU session; 6) the service request procedure is initiated for emergency services fallback; 7) the service request procedure is initiated for elevated signalling; 8) the UE in NB-N1 mode is requested by the upper layer to transmit user data related to an exceptional event and: - the UE is allowed to use exception data reporting (see the ExceptionDataReportingAllowed leaf of the NAS configuration MO in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [17] or the USIM file EFNASCONFIG in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [22]); and - timer T3346 was not started when N1 NAS signalling connection was established with RRC establishment cause set to "mo-ExceptionData"; or 9) the MUSIM UE is in 5GMM-CONNECTED mode and requests the network to release the NAS signalling connection (see case o in subclause 5.6.1.1). If the UE is in 5GMM-IDLE mode, the UE stays in the current serving cell and applies normal cell reselection process. The service request procedure is started, if still necessary, when timer T3346 expires or is stopped. If the service request procedure was triggered for an MO MMTEL voice call (i.e. access category 4), or for an MO MMTEL video call (i.e. access category 5) or for an MO IMS registration related signalling (i.e. access category 9), a notification that the service request procedure was not initiated due to congestion shall be provided to the upper layers. If the UE receives a paging with access type set to "Non-3GPP access" and the non-3GPP access is available and UE is in 5GMM-REGISTERED.NORMAL SERVICE over non-3GPP access, the UE shall stop timer T3346 and send the SERVICE REQUEST message over non-3GPP access. d) Registration procedure for mobility and periodic registration update is triggered. The UE shall abort the service request procedure, stop timer T3517, if running and perform the registration procedure for mobility and periodic registration update. The Follow-on request indicator in the REGISTRATION REQUEST message shall be handled as specified in subclause 5.5.1.3.2. e) Switch off. If the UE is in state 5GMM-SERVICE-REQUEST-INITIATED at switch off, the de-registration procedure shall be performed. f) De-registration procedure collision. If the UE receives a DEREGISTRATION REQUEST message from the network in state 5GMM-SERVICE-REQUEST-INITIATED, the UE shall progress the DEREGISTRATION REQUEST message and the service request procedure shall be aborted. NOTE 4: The above collision case is valid if the DEREGISTRATION REQUEST message indicates the access type over which the service request procedure is attempted otherwise both the procedures are progressed. g) Transmission failure of SERVICE REQUEST or CONTROL PLANE SERVICE REQUEST message indication with change in the current TAI. If the current TAI is not in the TAI list, UE shall abort the service request procedure to perform the registration procedure for mobility and periodic registration update as specified in subclause 5.5.1.3.2. If the current TAI is part of the TAI list, the UE shall restart the service request procedure unless the service request procedure is initiated for case o) or p) in subclause 5.6.1.1. For case o) and p) in subclause 5.6.1.1 the UE shall abort the service request procedure, enters state 5GMM-REGISTERED, locally release the N1 NAS signalling connection, stop timer T3517 and locally release any resources allocated for the service request procedure. h) Transmission failure of SERVICE REQUEST or CONTROL PLANE SERVICE REQUEST message indication without change in the current TAI. The UE shall restart the service request procedure unless the service request procedure is initiated for case o) or p) in subclause 5.6.1.1. For case o) and p) in subclause 5.6.1.1 the UE shall abort the service request procedure, enters state 5GMM-REGISTERED, locally release the N1 NAS signalling connection, stop timer T3517 and locally release any resources allocated for the service request procedure. i) SERVICE REJECT message received with other 5GMM cause values than those treated in subclause 5.6.1.5, and cases of 5GMM cause values #11, #15, #22, #31, #72, #73, #74, #75, #76, #77 and #78 that are considered as abnormal cases according to subclause 5.6.1.5. The UE shall enter state 5GMM-REGISTERED. The UE shall abort the service request procedure, stop timer T3517 and locally release any resources allocated for the service request procedure. j) The UE in 5GMM-CONNECTED mode with RRC inactive indication over the 3GPP access, and in 5GMM-CONNECTED mode over non-3GPP access, receives a NOTIFICATION message over the non-3GPP access with access type indicating 3GPP access. The UE shall transition from 5GMM-CONNECTED mode with RRC inactive indication to 5GMM-IDLE mode over 3GPP access and initiate the service request procedure over the 3GPP access. k) Timer T3447 is running The UE shall not start any service request procedure unless: 1) the UE in 5GMM-IDLE receives a paging request; 2) the UE is a UE configured for high priority access; 3) the UE has a PDU session for emergency services established or is establishing a PDU session for emergency services; 4) the service request procedure is initiated for emergency services fallback; 5) the UE in 5GMM-CONNECTED mode receives mobile terminated signalling or downlink data over the user-plane; 6) the service request procedure is initiated for elevated signalling; or 7) the MUSIM UE requests the network to release the NAS signalling connection (see case o in subclause 5.6.1.1). The UE stays in the current serving cell and applies the normal cell reselection process. The service request procedure is started, if still necessary, when timer T3447 expires or timer T3447 is stopped. l) Lower layer failure, release of the N1 signalling connection received from lower layers or the lower layers indicate that the RRC connection has been suspended before the service request procedure is completed or SERVICE REJECT message is received. The UE shall abort the service request procedure, stop timer T3517, locally release any resources allocated for the service request procedure and enters state 5GMM-REGISTERED. For case m) in subclause 5.6.1.1 the UE may retry the service request procedure a certain number of times (maximum re-attempts 5). m) Timer T3448 is running The UE in 5GMM-IDLE mode shall not initiate the service request procedure for transport of user data via the control plane unless: 1) the UE is a UE configured for high priority access in selected PLMN; 2) the UE which is only using 5GS services with control plane CIoT 5GS optimization received a paging request; 3) the UE in NB-N1 mode is requested by the upper layer to transmit user data related to an exceptional event and the UE is allowed to use exception data reporting (see the ExceptionDataReportingAllowed leaf of the NAS configuration MO in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [17] or the USIM file EFNASCONFIG in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [22]); or 4) the UE is initiating the service request procedure to request emergency services or emergency services fallback. The UE stays in the current serving cell and applies the normal cell reselection process. The service request procedure is started, if still necessary, when timer T3448 expires. n) Access for localized services in current SNPN is no longer allowed. If the service request procedure is not to request emergency services and there is no PDU session for emergency services, the registered SNPN is an SNPN selected for localized services in SNPN as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] and: - access for localized services in SNPN is disabled; or - the validity information for the selected SNPN is no longer met; then the UE shall reset the service request attempt counter, stop T3517, abort the service request procedure, locally release the NAS signalling connection, if any, and enter state 5GMM-REGISTERED.LIMITED-SERVICE or 5GMM-REGISTERED.PLMN-SEARCH in order to perform SNPN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]. | 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.6.1.7 |
2,467 | 6.2.4B UE maximum output power with additional requirements for UL-MIMO | For UE with two transmit antenna connectors in closed-loop spatial multiplexing scheme, the A-MPR values specified in subclause 6.2.4 shall apply to the maximum output power specified in Table 6.2.2B-1. The requirements shall be met with the UL-MIMO configurations specified in Table 6.2.2B-2. For UE supporting UL-MIMO, the maximum output power is measured as the sum of the maximum output power at each UE antenna connector. Unless stated otherwise, an A-MPR of 0 dB shall be used. For the UE maximum output power modified by A-MPR, the power limits specified in subclause 6.2.5B apply. If UE is configured for transmission on single-antenna port, the requirements in subclause 6.2.4 apply. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.2.4B |
2,468 | B.2.2 Compatibility/Subscription checking of the SETUP message | At the calling side the network shall check that the basic service(s) requested by the calling MS in the Bearer Capability information element(s) match(es) with the basic services provided to that subscriber by the PLMN. If for at least one bearer capability information element contained in the SETUP message a mismatch is detected, then the network shall proceed as follows: - if the SETUP message contained two bearer capability information elements for only one of which a mismatch is detected, the network shall either: - under the conditions specified in 3GPP TS 27.001[ General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS) ] [36] (e.g. TS 61 and TS 62), accept the SETUP message with a CALL PROCEEDING message containing the, possibly negotiated, bearer capability information element for which no mismatch is detected, or - reject the call using one of the causes listed in annex H. - otherwise the network shall reject the call using one of the causes listed in annex H. Network services are described in 3GPP TS 22.002[ Circuit Bearer Services (BS) supported by a Public Land Mobile Network (PLMN) ] [3] and 3GPP TS 22.003[ Circuit Teleservices supported by a Public Land Mobile Network (PLMN) ] [4] as bearer services and teleservices, respectively. | 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 | B.2.2 |
2,469 | 9.4 Security mechanisms for the Xn interface | Xn is the interface connecting NG-RAN nodes. It consists of Xn-C and Xn-U. Xn-C is used to carry signalling and Xn-U user plane data. The transport of control plane data and user data over Xn shall be integrity, confidentiality and replay-protected. In order to protect the traffic on the Xn reference point, it is required to implement IPsec ESP and IKEv2 certificate- based authentication as specified in sub-clause 9.1.2 of the present document with confidentiality, integrity and replay protection. IPsec shall be supported on the gNB and ng-eNB. In addition to IPsec, for the Xn-C interface, DTLS shall be supported as specified in RFC 6083 [58] to provide mutual authentication, integrity protection, replay protection and confidentiality protection. Security profiles for DTLS implementation and usage shall follow the TLS profile given in clause 6.2 of TS 33.210[ Network Domain Security (NDS); IP network layer security ] [3] and the certificate profile given in clause 6.1.3a of TS 33.310[ Network Domain Security (NDS); Authentication Framework (AF) ] [5]. The identities in the end entity certificates shall be used for authentication and policy checks. Mutual authentication shall be supported over the Xn interface between the NG-RAN nodes using DTLS and/or IKEv2. NOTE 1: The use of transport layer security, via DTLS, does not rule out the use of network layer protection according to NDS/IP as specified in TS 33.210[ Network Domain Security (NDS); IP network layer security ] [3]. In fact, IPsec has the advantage of providing topology hiding.. NOTE 2: The use of cryptographic solutions to protect Xn is an operator's decision. In case the NG-RAN node (gNB or ng-eNB) has been placed in a physically secured environment then the 'secure environment' includes other nodes and links beside the NG-RAN node. QoS related aspects are further described in sub-clause 9.1.3 of the present document. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 9.4 |
2,470 | O.5 Handling of unknown, unforeseen, and erroneous protocol data O.5.1 General | The following subclauses specifies procedures for the handling of unknown, unforeseen, and erroneous protocol data by the receiving MS. These procedures are called "error handling procedures", but in addition to providing recovery mechanisms for error situations they define a compatibility mechanism for future extensions of the protocols. Subclauses O.5.2 to O.5.5 shall be applied in order of precedence. For the definition of semantical and syntactical errors see 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [20], subclause 11.4.2. Where the description of information elements in the present document contains bits defined to be "spare bits", these bits shall set to the indicated value (usually 0) by the sending side, and their value shall be ignored by the receiving side. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | O.5 |
2,471 | 6.10.5.3 CSI reference signal subframe configuration | The subframe configuration period and the subframe offset for the occurence of CSI reference signals are listed in Table 6.10.5.3-1. The parameter can be configured separately for CSI reference signals for which the UE shall assume non-zero and zero transmission power. Subframes containing CSI reference signals that do not correspond to either higher layer configured parameter csi-RS-ConfigNZP-ApList or csi-RS-ConfigZP-ApList shall satisfy . Table 6.10.5.3-1: CSI reference signal subframe configuration | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.10.5.3 |
2,472 | 6.3.6.4 PLMN and non-3GPP access node Selection for emergency services 6.3.6.4.1 General | UE initiates PLMN and non-3GPP access node selection for emergency services when it detects a user request for emergency session and determines that untrusted non-3GPP access shall be used for the emergency access. When the UE supports connectivity with N3IWF but does not support connectivity with ePDG, as specified in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [43], the UE shall perform the procedure in clause 6.3.6.4.2 for selecting an N3IWF. When the UE supports connectivity with N3IWF, as well as with ePDG, as specified in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [43], the UE shall perform the procedure in clause 6.3.6.4.3 for selecting either an N3IWF or an ePDG, i.e. for selecting a non-3GPP access node. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.3.6.4 |
2,473 | 6.2.1 MAC header for DL-SCH, UL-SCH and MCH | The MAC header is of variable size and consists of the following fields: - LCID: The Logical Channel ID field identifies the logical channel instance of the corresponding MAC SDU or the type of the corresponding MAC control element or padding as described in tables -1, 6.2.1-2 and 6.2.1-4 for the DL-SCH, UL-SCH and MCH respectively. There is one LCID field for each MAC SDU, MAC control element or padding included in the MAC PDU. In addition to that, one or two additional LCID fields are included in the MAC PDU, when single-byte or two-byte padding is required but cannot be achieved by padding at the end of the MAC PDU. If the LCID field is set to "10000", an additional octet is present in the MAC PDU subheader containing the eLCID field and this additional octet follows the octet containing LCID field. A UE of Category 0, as specified in TS 36.306[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio access capabilities ] [12], except when in enhanced coverage, and unicastFreqHoppingInd-r13 is indicated in the BR version of SI message carrying SystemInformationBlockType2, and UE supports frequency hopping for unicast, as specified in TS 36.306[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio access capabilities ] [12], shall indicate CCCH using LCID "01011", a BL UE with support for frequency hopping for unicast, as specified in TS 36.306[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio access capabilities ] [12], and a UE in enhanced coverage with support for frequency hopping for unicast, as specified in TS 36.306[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio access capabilities ] [12], shall if unicastFreqHoppingInd-r13 is indicated in the BR version of SI message carrying SystemInformationBlockType2 indicate CCCH using LCID "01100", otherwise the UE shall indicate CCCH using LCID "00000". A short DCQR may be included in the MAC PDU subheader with LCID set to "00000", "01011", "01100" or "01101". The LCID field size is 5 bits; - eLCID: The extended Logical Channel ID field identifies the logical channel instance of the corresponding MAC SDU or the type of the corresponding MAC control element as described in tables 6.2.1-1a and 6.2.1-2a for the DL-SCH and UL-SCH respectively. The size of the eLCID field is 6 bits. - L: The Length field indicates the length of the corresponding MAC SDU or variable-sized MAC control element in bytes. There is one L field per MAC PDU subheader except for the last subheader and subheaders corresponding to fixed-sized MAC control elements. The size of the L field is indicated by the F field and F2 field; - F: The Format field indicates the size of the Length field as indicated in table 6.2.1-3. There is one F field per MAC PDU subheader except for the last subheader and subheaders corresponding to fixed-sized MAC control elements and except for when F2 is set to 1. The size of the F field is 1 bit. If the F field is included; if the size of the MAC SDU or variable-sized MAC control element is less than 128 bytes, the value of the F field is set to 0, otherwise it is set to 1; - F2: Except when this field is used for short DCQR, the Format2 field indicates the size of the Length field as indicated in table 6.2.1-3. For short DCQR, the mapping of F2 field to short DCQR value is described in table 6.2.1-5. There is one F2 field per MAC PDU subheader. The size of the F2 field is 1 bit. Except when this field is used for short DCQR, if the size of the MAC SDU or variable-sized MAC control element is larger than 32767 bytes, and if the corresponding subheader is not the last subheader, the value of the F2 field is set to 1, otherwise it is set to 0; - E: The Extension field is a flag indicating if more fields are present in the MAC header or not. The E field is set to "1" to indicate another set of at least R/F2/E/LCID fields. The E field is set to "0" to indicate that either a MAC SDU, a MAC control element or padding starts at the next byte; - R: Except when this field is used for short DCQR, reserved bit, set to "0". For short DCQR, the mapping of R field to short DCQR value is described in table 6.2.1-5. The MAC header and subheaders are octet aligned. Table 6.2.1-1 Values of LCID for DL-SCH Table 6.2.1-1a Values of eLCID for DL-SCH For NB-IoT only the following LCID values for DL-SCH are applicable: CCCH, Identity of the logical channel, DCQR Command, SC-PTM Stop Indication, SC-MCCH/SC-MTCH, UE Contention Resolution Identity, Timing Advance Command, DRX Command, Differential Koffset, GNSS Measurement Command and Padding. Table 6.2.1-2 Values of LCID for UL-SCH Table 6.2.1-2a Values of eLCID for UL-SCH For NB-IoT only the following LCID values for UL-SCH are applicable: CCCH (LCID "00000"), Identity of the logical channel, CCCH and Extended Power Headroom Report, DCQR and AS RAI, SPS confirmation, C-RNTI, Short BSR, Timing Advance Report, GNSS Validity Duration Report and Padding. Table 6.2.1-3 Values of F and F2 fields: Table 6.2.1-4 Values of LCID for MCH Table 6.2.1-5: Values of R and F2 fields for short DCQR | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.2.1 |
2,474 | 6.1 Overview 6.1.1 General | This clause describes the procedures used for EPS session management (ESM) at the radio interface (reference point "LTE-Uu"). The main function of the ESM sublayer is to support the EPS bearer context handling in the UE and in the MME. The ESM comprises procedures for: - the activation, deactivation and modification of EPS bearer contexts; - the request for resources (IP connectivity to a PDN or dedicated bearer resources) by the UE; and - the transport of user data via the control plane between the UE and the MME. Each EPS bearer context represents an EPS bearer between the UE and a PDN. EPS bearer contexts can remain activated even if the radio and S1 bearers constituting the corresponding EPS bearers between UE and MME are temporarily released. An EPS bearer context can be either a default bearer context or a dedicated bearer context. A default EPS bearer context is activated when the UE requests a connection to a PDN. Generally, ESM procedures can be performed only if an EMM context has been established between the UE and the MME, and the secure exchange of NAS messages has been initiated by the MME by use of the EMM procedures described in clause 5. The first default EPS bearer context, however, can be activated during the EPS attach procedure (see clause 4.2). Once the UE is successfully attached, and the first default EPS bearer context has been activated during or after the attach procedure, the UE can request the MME to set up connections to additional PDNs. For each additional connection, the MME will activate a separate default EPS bearer context. A default EPS bearer context remains activated throughout the lifetime of the connection to the PDN. A dedicated EPS bearer context is always linked to a default EPS bearer context and represents additional EPS bearer resources between the UE and the PDN. The network can initiate the activation of dedicated EPS bearer contexts together with the activation of the default EPS bearer context or at any time later, as long as the default EPS bearer context remains activated. However, the network shall not initiate a dedicated bearer context activation procedure for established PDN connection(s) of "non IP" PDN type. Default and dedicated EPS bearer contexts can be modified. Dedicated EPS bearer contexts can be released without affecting the default EPS bearer context. When the default EPS bearer context is released, then all dedicated EPS bearer contexts linked to it are released too. The UE can request the network to allocate, modify or release EPS bearer resources. The network can fulfil such a request from the UE by activating a new dedicated EPS bearer context, modifying an EPS bearer context or deactivating an EPS bearer context. | 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.1 |
2,475 | 8.3.2.4.3 Minimum requirement with Different Cell ID and Colliding CRS (with single NZP CSI-RS resource) | The requirements are specified in Table 8.3.2.4.3-2, with the additional parameters in Table 8.3.2.4.3-1. The purpose of this test is to verify the UE capability of supporting non quasi-colocated antenna ports when the UE receives DCI format 2D in a scenario where the two transmission points have different Cell ID and colliding CRS. In particular the test verifies that the UE, configured with quasi co-location type B, performs correct tracking and compensation of the frequency difference between two transmission points, channel parameters estimation and rate matching behaviour according to the ‘PDSCH RE Mapping and Quasi-Co-Location Indicator’ signalling defined in [6]. In Table 8.3.2.4.3-1, transmission point 1 (TP 1) is serving cell transmitting PDCCH, synchronization signals and PBCH, and transmission point 2 (TP 2) transmits PDSCH with different Cell ID. The downlink physical channel setup for TP 1 is according to Table C.3.4-1 and for TP 2 according to Table C.3.4-2. Table 8.3.2.4.3-1: Test Parameters for quasi co-location type B with different Cell ID and Colliding CRS Table 8.3.2.4.3-2: Performance Requirements for quasi co-location type B with different Cell ID and Colliding CRS | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.3.2.4.3 |
2,476 | 9.3.2 Frequency non-selective scheduling mode | The reporting accuracy of the channel quality indicator (CQI) under frequency non-selective fading conditions is determined by the reporting variance, and the relative increase of the throughput obtained when the transport format transmitted is that indicated by the reported CQI compared to the case for which a fixed transport format configured according to the reported median CQI is transmitted. In addition, the reporting accuracy is determined by a minimum BLER using the transport formats indicated by the reported CQI. The purpose is to verify that the UE is tracking the channel variations and selecting the largest transport format possible according to the prevailing channel state for frequently non-selective scheduling. To account for sensitivity of the input SNR the CQI reporting under frequency non-selective fading conditions is considered to be verified if the reporting accuracy is met for at least one of two SNR levels separated by an offset of 1 dB. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.3.2 |
2,477 | G.2.2 Communication across service mesh boundaries | It is a deployment where a single service mesh covers all functionality within a given deployment or not. In cases of communication across the boundaries of a service mesh, the service mesh routing the outbound message knows neither whether the selected producer is in a service mesh nor the internal topology of the potential service mesh where the producer resides. In such a deployment, as shown in Figure G.2.2.-1, after producer selection is performed, routing policies on the outgoing service mesh are only aware of the next hop. Given a request sent by A, A's Service Agent will perform producer selection based on the received request. If the selected producer endpoint (e.g. D) is determined to be outside of Service Mesh 1, A's Service Agent routes the request to the Egress Proxy. For a successful routing, the Egress Proxy needs to be able to determine the next hop of the request. In this case, this is the Ingress Proxy of Service Mesh 2. The Ingress Proxy of Service Mesh 2 is, based on the information in the received request and its routing policies, able to determine the route for the request. Subsequently, D receives the request. No topology information needs to be exchanged between Service Mesh 1 and Service Mesh 2 besides a general routing rule towards Service Mesh 2 (e.g. a FQDN prefix) and an Ingress Proxy destination for requests targeting endpoints in Service Mesh 2. Figure G.2.2-1: Message routing across service mesh boundaries | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | G.2.2 |
2,478 | 5.3.13.11 Inability to comply with RRCResume | The UE shall: 1> if the UE is unable to comply with (part of) the configuration included in the RRCResume message; 2> perform the actions upon going to RRC_IDLE as specified in 5.3.11 with release cause ′RRC Resume failure′. NOTE 1: The UE may apply above failure handling also in case the RRCResume message causes a protocol error for which the generic error handling as defined in 10 specifies that the UE shall ignore the message. NOTE 2: If the UE is configured (i.e., via SIB1) to send MUSIM temporary capability restriction indication, and if the UE supports MUSIM temporary capability restriction, the UE does not apply above failure handling in case the UE is unable to apply part of the configuration included in RRCResume message due to UE temporary capability restriction for MUSIM operation. It is up to UE implementation how to apply RRCResume message. If UE does not go to RRC_IDLE in this case, UE still considers the received configuration in RRCResume message as the current configuration as the baseline for delta configuration for future reconfigurations. For other cases, if the UE is unable to comply with part of the configuration, it does not apply any part of the configuration, i.e. there is no partial success/failure. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.13.11 |
2,479 | 5.3.3.2.2 CM-IDLE state | A UE in CM-IDLE state has no NAS signalling connection established with the AMF over N1. The UE performs cell selection/cell reselection according to TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [50] and PLMN selection according to TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [17]. There are no AN signalling connection, N2 connection and N3 connections for the UE in the CM-IDLE state. If the UE is both in CM-IDLE state and in RM-REGISTERED state, the UE shall, unless otherwise specified in clause 5.3.4.1: - Respond to paging by performing a Service Request procedure (see clause 4.2.3.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]), unless the UE is in MICO mode (see clause 5.4.1.3); - perform a Service Request procedure when the UE has uplink signalling or user data to be sent (see clause 4.2.3.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]). Specific conditions apply for LADN, see clause 5.6.5. When the UE state in the AMF is RM-REGISTERED, UE information required for initiating communication with the UE shall be stored. The AMF shall be able to retrieve stored information required for initiating communication with the UE using the 5G-GUTI. NOTE: In 5GS there is no need for paging using the SUPI/SUCI of the UE. The UE provides 5G-S-TMSI as part of AN parameters during AN signalling connection establishment as specified in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [28] and TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [51]. The UE shall enter CM-CONNECTED state whenever an AN signalling connection is established between the UE and the AN (entering RRC_CONNECTED state over 3GPP access, or at the establishment of the UE-N3IWF connectivity over untrusted non-3GPP access or the UE-TNGF connectivity over trusted non-3GPP access). The transmission of an Initial NAS message (Registration Request, Service Request or Deregistration Request) initiates the transition from CM-IDLE to CM-CONNECTED state. When the UE states in the AMF are CM-IDLE and RM-REGISTERED, the AMF shall: - perform a network triggered Service Request procedure when it has signalling or mobile-terminated data to be sent to this UE, by sending a Paging Request to this UE (see clause 4.2.3.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]), if a UE is not prevented from responding e.g. due to MICO mode or Mobility Restrictions. The AMF shall enter CM-CONNECTED state for the UE whenever an N2 connection is established for this UE between the AN and the AMF. The reception of initial N2 message (e.g. N2 INITIAL UE MESSAGE) initiates the transition of AMF from CM-IDLE to CM-CONNECTED state. The UE and the AMF may optimize the power efficiency and signalling efficiency of the UE when in CM-IDLE state e.g. by activating MICO mode (see clause 5.4.1.3). | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.3.3.2.2 |
2,480 | 8.13.1.1.1 Minimum Requirement Multi-Layer Spatial Multiplexing 4 Tx Antenna Port | The purpose of these tests is to verify the closed loop rank-two performance with frequency selective precoding. For CA with 2 DL CCs, the requirements are specified in Table 8.13.1.1.1-3, based on single carrier requirement specified in Table 8.13.1.1.1-2, with the addition of the parameters in Table 8.13.1.1.1-1 and the downlink physical channel setup according to Annex C.3.2. For CA with 3 DL CCs, the requirements are specified in Table 8.13.1.1.1-4, based on single carrier requirement specified in Table 8.13.1.1.1-2, with the addition of the parameters in Table 8.13.1.1.1-1 and the downlink physical channel setup according to Annex C.3.2. For CA with 4 DL CCs, the requirements are specified in Table 8.13.1.1.1-5, based on single carrier requirement specified in Table 8.13.1.1.1-2, with the addition of the parameters in Table 8.13.1.1.1-1 and the downlink physical channel setup according to Annex C.3.2. For CA with 5 DL CCs, the requirements are specified in Table 8.13.1.1.1-6, based on single carrier requirement specified in Table 8.13.1.1.1-2, with the addition of the parameters in Table 8.13.1.1.1-1 and the downlink physical channel setup according to Annex C.3.2. The test coverage for different number of component carriers is defined in 8.1.2.4. Table 8.13.1.1.1-1: Test Parameters for Multi-Layer Spatial Multiplexing (FRC) for CA Table 8.13.1.1.1-2: Single carrier performance for multiple CA configurations Table 8.13.1.1.1-3: Minimum performance (FRC) based on single carrier performance for CA with 2 DL CCs Table 8.13.1.1.1-4: Minimum performance (FRC) based on single carrier performance for CA with 3 DL CCs Table 8.13.1.1.1-5: Minimum performance (FRC) based on single carrier performance for CA with 4 DL CCs Table 8.13.1.1.1-6: Minimum performance (FRC) based on single carrier performance for CA with 5 DL CCs | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.13.1.1.1 |
2,481 | 6.8.1.1.2 Transition from RM-DEREGISTERED to RM-REGISTERED 6.8.1.1.2.1 General | When starting the transition away from RM DEREGISTERED state with the intent to eventually transitioning to RM-REGISTERED state, if no current 5G NAS security context is available in the ME, the ME shall retrieve native 5G NAS security context stored on the USIM if the USIM supports RM parameters storage and if the stored native 5G NAS security context on the USIM is marked as valid. If the USIM does not support RM parameters storage the ME shall retrieve stored native 5G NAS security context from its non-volatile memory if the native 5G NAS security context is marked as valid. The ME shall derive the KNASint and KNASenc from the KAMF after retrieving the stored 5G NAS security context; see Annex A on NAS key derivation. The retrieved native 5G NAS security context with the derived KNASint and KNASenc shall then become the current 5G NAS security context. When the ME is transitioning away from RM DEREGISTERED state with the intent to eventually transitioning to RM-REGISTERED state, if the USIM supports RM parameters storage, the ME shall mark the stored 5G NAS security context on the USIM as invalid. If the USIM does not support RM parameters storage, the ME shall mark the stored 5G NAS security context in its non-volatile memory as invalid. If the ME uses a 5G NAS security context to protect NAS messages, the distinct NAS COUNT values together with the NAS connection identifier associated with this access, are updated in the volatile memory of the ME. If the attempt to transition away from RM DEREGISTERED state with the intent to eventually transitioning to RM-REGISTERED state fails, the ME shall store the (possibly updated) 5G NAS security context including the distinct NAS COUNT values together with the NAS connection identifier associated with this access, on the USIM or non-volatile ME memory and mark it as valid. NOTE: The present document only considers the states RM-DEREGISTERED and RM REGISTERED and transitions between these two states. Other documents define additional RM states (see, e.g. 5GMM states in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [35]). When the UE transits from RM-DEREGISTERED to RM-REGISTERED/CM-CONNECTED, there are two cases to consider, either a full native 5G NAS security context exists, or it does not. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.8.1.1.2 |
2,482 | 5.2.2.4.21 Actions upon reception of SIB19 | Upon receiving SIB19 in an NTN cell, the UE in RRC_CONNECTED shall: 1> start or restart T430 for serving cell with the timer value set to ntn-UlSyncValidityDuration for the serving cell from the subframe indicated by epochTime for the serving cell; 1> if SatSwitchWithReSync and t-Service are included, and the UE supports hard satellite switch with resynchronization; 2> if t-ServiceStart is included and the UE supports soft satellite switch with resynchronization: 3> perform the satellite switch with resynchronization as specified in 5.7.19 between the time indicated by t-ServiceStart and the time indicated by t-Service for the serving cell. 2> else: 3> perform the satellite switch with resynchronization as specified in 5.7.19 at the time indicated by t-Service for the serving cell. NOTE: UE should attempt to re-acquire SIB19 before the end of the duration indicated by ntn-UlSyncValidityDuration and epochTime by UE implementation. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.2.2.4.21 |
2,483 | 8.107 Node Identifier | Node Identifier shall be coded as depicted in Figure 8.107-1. Figure 8.107-1: Node Identifier The Node Identifier shall contain the Diameter Identity of the node. If the Node Identifier contains a SGSN Identifier then: - the Node Name shall be coded as the Diameter identity of the SGSN as defined in clause 6.4.13 of 3GPP TS 29.173[ Location Services (LCS); Diameter-based SLh interface for Control Plane LCS ] [57] and; - the Node Realm shall be coded as the Diameter realm identity of the SGSN and as defined in clause 6.4.14 of 3GPP TS 29.173[ Location Services (LCS); Diameter-based SLh interface for Control Plane LCS ] [57] and; - Both the Node Name and the Node Realm shall be present and neither the Length of Node Name nor the Length of Node Realm shall be zero. If the Node Identifier contains a MME Identifier then: - the Node Name shall be coded as the Diameter identity of the MME as defined in clause 6.4.4 of 3GPP TS 29.173[ Location Services (LCS); Diameter-based SLh interface for Control Plane LCS ] [57] and; - the Node Realm shall be coded as the Diameter realm identity of the MME as defined in clause 6.4.12 of 3GPP TS 29.173[ Location Services (LCS); Diameter-based SLh interface for Control Plane LCS ] [57] and; - Both the Node Name and the Node Realm shall be present and neither the Length of Node Name nor the Length of Node Realm shall be zero. If the Node Identifer contains a 3GPP AAA Server Identifier then: - the Node Name shall be coded as the 3GPP-AAA-Server-Name as defined in clause 8.2.3.24 of 3GPP TS 29.273[ Evolved Packet System (EPS); 3GPP EPS AAA interfaces ] [68] and; - the Node Realm shall be coded as the Diameter realm of the 3GPP AAA server in the format of a Diameter identity as defined in IETF RFC 3588 [39]. If the Node Identifier contains an SCEF/IWK-SCEF information, then: - the Node Name shall be coded as the SCEF-ID as defined in clause 8.4.5 of 3GPP TS 29.336[ Home Subscriber Server (HSS) diameter interfaces for interworking with packet data networks and applications ] [69] and; - the Node Realm shall be coded as the Diameter realm of the SCEF as defined in clause 7.3.207 of 3GPP TS 29.272[ Evolved Packet System (EPS); Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol ] [70]. | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 8.107 |
2,484 | 11.1.3 Re-Authentication | Figure 11.1.3-1: EAP Re-Authentication with an external AAA server This procedure concerns both roaming and non-roaming scenarios. In the non-roaming and LBO roaming cases, only one SMF is involved. In the HR roaming case, the V-SMF shall proxy the signalling between the AMF in the VPLMN and the H-SMF in the HPLMN. 1-3 Secondary Authentication has been established according to procedures specified in clause 11.1.2, Initial EAP Authentication with an external AAA server. Secondary Re-authentication may either be initiated by SMF or the external DN/AAA server. If Re-authentication is initiated by SMF, the procedure proceeds with step 4 (skipping steps 4a and 4b). If Re-authentication is initiated by the external DN/AAA server, the procedure proceeds with the alternative steps 4a and 4b. 4. The SMF decides to initiate Secondary Re-Authentication. 4a. The DN AAA server decides to initiate Secondary Re-Authentication. 4b. The DN AAA shall send a Secondary Re-Authentication request to UPF, and the UPF forwards it to SMF. The Secondary Re-authentication request contains the GPSI, if available, and the IP/MAC address of the UE allocated to the PDU Session and the MAC address if the PDU session is of Ethernet PDU type. 5. The SMF shall send an EAP Request/Identity message to the UE. 6. The UE shall respond with an EAP Response/Identity message (with Fast-Reauth Identity). 7. The SMF forwards the EAP Response/Identity to UPF, selected during initial authentication, over N4 interface. This establishes an end-to-end connection between the SMF and the external DN-AAA server for EAP exchange. 8. The UPF shall forward the EAP Response/Identity message to the DN AAA Server. 9. The DN AAA server and the UE shall exchange EAP messages as required by the EAP method. 10. After the completion of the authentication procedure, DN AAA server either sends EAP Success or EAP Failure message to the SMF. 11. This completes the Re-authentication procedure at the SMF. 12-13. If the authentication is successful, EAP-Success shall be sent to UE. 12-14. If authentication is not successful, the SMF notifies failure to UPF. Upon completion of a N4 Session Modification procedure with the selected UPF, SMF sends EAP-Failure to UE via AMF. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 11.1.3 |
2,485 | 4.6.2.2 EMM-REGISTERED | The UE enters the EMM-REGISTERED state by a successful registration with an Attach procedure to either E-UTRAN or GERAN/UTRAN. The MME enters the EMM-REGISTERED state by a successful Tracking Area Update procedure for a UE selecting an E-UTRAN cell from GERAN/UTRAN or by an Attach procedure via E-UTRAN. In the EMM-REGISTERED state, the UE can receive services that require registration in the EPS. NOTE: The UE employs a single combined state machine for EMM and GMM states. The UE location is known in the MME to at least an accuracy of the tracking area list allocated to that UE (excluding some abnormal cases). In the EMM-REGISTERED state, the UE shall: - always have at least one active PDN connection (unless the UE supports "Attach without PDN connectivity"); - setup the EPS security context. After performing the Detach procedure, the state is changed to EMM-DEREGISTERED in the UE and in the MME. Upon receiving the TAU Reject and Attach Reject messages the actions of the UE and MME depend upon the 'cause value' in the reject message, but, in many cases the state is changed to EMM-DEREGISTERED in the UE and in the MME. If all the bearers belonging to a UE that does not support "Attach without PDN connectivity" are released (e.g., after handover from E-UTRAN to non-3GPP access), the MME shall change the MM state of that UE to EMM-DEREGISTERED. If the UE that does not support "Attach without PDN connectivity" camps on E-UTRAN and the UE detects that all of its bearers are released, the UE shall change the MM state to EMM-DEREGISTERED. If all the bearers (PDP contexts) belonging to a UE are released, while the UE camps on GERAN/UTRAN, the UE shall deactivate ISR by setting its TIN to "P-TMSI" as specified in TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7]. This ensures that the UE performs Tracking Area Update when it re-selects E-UTRAN. If the UE switches off its E-UTRAN interface when performing handover to non-3GPP access, the UE shall automatically change its MM state to EMM-DEREGISTERED. The MME may perform an implicit detach any time after the Implicit Detach timer expires. The state is changed to EMM-DEREGISTERED in the MME after performing the implicit detach. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.6.2.2 |
2,486 | 7.10.1A Minimum requirements for CA | Receiver image rejection is a measure of a receiver's ability to receive the E-UTRA signal on one component carrier while it is also configured to receive an adjacent aggregated carrier. Receiver image rejection ratio is the ratio of the wanted received power on a sub-carrier being measured to the unwanted image power received on the same sub-carrier when both sub-carriers are received with equal power at the UE antenna connector. For intra-band contiguous carrier aggregation the UE shall fulfil the minimum requirement specified in Table 7.10.1A-1 for all values of aggregated input signal up to –22 dBm. Table 7.10.1A-1: Receiver image rejection | 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.10.1A |
2,487 | – SearchSpaceId | The IE SearchSpaceId is used to identify Search Spaces. The ID space is used across the BWPs of a Serving Cell. The search space with the SearchSpaceId = 0 identifies the search space configured via PBCH (MIB) and in ServingCellConfigCommon (searchSpaceZero). The number of Search Spaces per BWP is limited to 10 including the common and UE specific Search Spaces. SearchSpaceId information element -- ASN1START -- TAG-SEARCHSPACEID-START SearchSpaceId ::= INTEGER (0..maxNrofSearchSpaces-1) -- TAG-SEARCHSPACEID-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,488 | 4.13 Support of NAS signalling using wireline access network | A 5G-RG, a W-AGF acting on behalf of an FN-RG or a W-AGF acting on behalf of an N5GC device can use wireline access network to access the 5GCN by using NAS signalling procedures as described in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8], 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9] and 3GPP TS 23.316[ Wireless and wireline convergence access support for the 5G System (5GS) ] [6D]. Wireline access is a type of non-3GPP access. A 5G-RG simultaneously connected to the same 5GCN of a PLMN over a 3GPP access and a wireline access is connected to a single AMF. 5G-RG maintains the N1 NAS signalling connection with the AMF over the wireline access network after all the PDU sessions for the 5G-RG over that access have been released or handed over to 3GPP access. The 5G-RG connected to 5GCN via NG-RAN is specified in 3GPP TS 23.316[ Wireless and wireline convergence access support for the 5G System (5GS) ] [6D]. When accessing the 5GCN over 3GPP access, in addition to requirements specified for the 5G-RG in the present document, the 5G-RG shall also perform requirements specified in the present document for a UE accessing 5GCN over 3GPP access. When accessing the 5GCN over wireline access, in addition to requirements specified for the 5G-RG in the present document, the 5G-RG shall also perform requirements specified in the present document for a UE accessing 5GCN over non-3GPP access. If a requirement specified for the 5G-RG in the present document contradicts a requirement specified for the UE in the present document, the 5G-RG shall perform the requirement specified in the present document for the 5G-RG. For the scenario of FN-RG, which does not support N1 mode, the W-AGF acting on behalf of the FN-RG exchanges NAS signalling messages with an AMF. For the scenario of N5GC device, which does not support N1 mode, the W-AGF acting on behalf of the N5GC device exchanges NAS signalling messages with an AMF. For the scenario of AUN3 device, which does not support N1 mode, the 5G-RG acting on behalf of the AUN3 device exchanges NAS signalling messages with an AMF. If the 5G-RG is not registered and connected to the 5GCN over wireline access, the 5G-RG acting on behalf of an AUN3 device shall not initiate the initial registration procedure on behalf of the AUN3 device. NOTE 1: The 5G-RG acting on behalf of an AUN3 device maintains a 5GMM context for each AUN3 device behind it. The AMF maintains a 5GMM context for each AUN3 device. The AMF is not aware of any association between the 5GMM context of the 5G-RG and the 5GMM context of the AUN3 device. When the 5G-RG acting on behalf of an AUN3 device initiates the initial registration procedure on behalf of the AUN3 device, the 5G-RG shall not include the requested NSSAI in the REGISTRATION REQUEST message. For the scenario of NAUN3 device, which does not support N1 mode, the 5G-RG acting on behalf of a connectivity group consisting of one or more NAUN3 devices exchanges NAS signalling messages with an AMF. NOTE 2: It is also possible for 5G-RG that is connected to 5GCN via NG-RAN to act on behalf of a connectivity group consisting of one or more NAUN3 devices as specified in 3GPP TS 23.316[ Wireless and wireline convergence access support for the 5G System (5GS) ] [6D]. In addition to requirements specified for the W-AGF acting on behalf of the FN-RG (or on behalf of the N5GC device) in the present document, the W-AGF acting on behalf of the FN-RG (or on behalf of the N5GC device) shall also perform requirements specified in the present document for a UE accessing 5GCN over non-3GPP access. If a requirement specified for the W-AGF acting on behalf of the FN-RG (or on behalf of the N5GC device) in the present document contradicts a requirement specified for the UE in the present document, the W-AGF acting on behalf of the FN-RG (or on behalf of the N5GC device) shall perform requirement specified in the present document for the W-AGF acting on behalf of the FN-RG (or on behalf of the N5GC device). The PDU session authentication and authorization procedure is not supported in a PDU session established by the W-AGF acting on behalf of the FN-RG or on behalf of the N5GC device. The W-AGF acting on behalf of the N5GC device requests the establishment of a PDU Session on behalf of the N5GC device upon registration. Only one PDU session per N5GC device is supported. The 5G-RG acting on behalf of an AUN3 device requests the establishment of a PDU Session on behalf of the AUN3 device upon registration. Only one PDU session per AUN3 is supported. The 5G-RG acting on behalf of a connectivity group consisting of one or more NAUN3 devices requests the establishment of a PDU Session on behalf of the connectivity group. Only one PDU session per the connectivity group is supported, where all the NAUN3 devices in the connectivity group share the same PDU session. A 5G-RG or an FN-RG provide a non-3GPP access network to UEs. A UE connected to a non-3GPP access network provided by the 5G-RG or the FN-RG can access to the 5GCN via the N3IWF or via the TNGF as described in 3GPP TS 23.316[ Wireless and wireline convergence access support for the 5G System (5GS) ] [6D]. The 5G-RG or the W-AGF acting on behalf of the FN-RG shall indicate "ANDSP not supported by the UE" in the UE policy classmark IE during the UE-initiated UE state indication procedure as specified in subclause D.2.2. The Non-3GPP QoS Assistance Information (N3QAI) is introduced to enable a 5G-RG to perform the QoS differentiation for the UE behind the 5G-RG, the AUN3 device behind the 5G-RG or the NAUN3 device behind the 5G-RG. The network may provide the N3QAI associated with the QoS flow during the PDU session establishment procedure as defined in subclause 6.4.1 or during the PDU session modification procedure as defined in subclause 6.4.2. NOTE 3: How the 5G-RG applies N3QAI is outside the scope of the present document. If the AMF receives an indication from the W-AGF that there is no 5G-RG connected to the same wireline for an AUN3 device as specified in 3GPP TS 23.316[ Wireless and wireline convergence access support for the 5G System (5GS) ] [6D], the AMF shall locally de-register the AUN3 device. | 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.13 |
2,489 | 4.14.2.1 Number of attempted WLAN additions to the LWIP WLAN mobility set | a) This measurement provides the number of attempted WLAN additions to the LWIP WLAN mobility set. b) CC c) On transmission of RRCConnectionReconfiguration message which includes the wlan-ToAddList in the lwip-MobilityConfig of lwip-Configuration information element (see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [18]) by the eNB. d) An integer value e) LWI.LwipWlanAddAtt f) WLANMobilitySet g) Valid for packet switched traffic h) EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.14.2.1 |
2,490 | 21.2.2 QoE Measurement Collection Deactivation | The QoE Measurement Collection deactivation permanently stops all or some of the QoE measurement collection jobs towards a UE, resulting in the release of the corresponding QoE measurement configuration(s) in the UE. The deactivation of QoE measurement collection is supported by using UE-associated signalling. A list of QoE references is used to deactivate the corresponding QoE measurement collection job(s). Upon reception of the QoE release message in an application layer measurement configuration, the UE discards any unsent application layer measurement reports corresponding to the released application layer configuration. The UE discards the reports received from application layer when it has no associated application layer measurement configuration configured. The network can replace a QoE measurement configuration with another one by deactivating an existing QoE measurement configuration and activating another QoE measurement configuration of the same QoE measurement configuration type. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 21.2.2 |
2,491 | 5.3.5B MT-EDT procedure for User Plane CIoT EPS Optimisation | Figure 5.3.5B-1: MT-EDT procedure for User Plane CIoT EPS Optimization 1. Same as step 1 in clause 5.3.4.3. 2. Same as step 2 in clause 5.3.4.3, with the following addition:; The Serving-GW may send the downlink data size to the MME for MT-EDT consideration if the downlink data is applicable for User Plane CIoT EPS Optimisation and MT-EDT is applicable for this PDN connection. 3. Same as step 3 in clause 5.3.4.3, with the following addition; If MT-EDT is applicable for the PDN Connection, the MME may include the downlink data size in the Paging message to assist eNodeB to use MT-EDT. 4. Same as step 4 in cluse 5.3.4.3, with the following addition; If data size is included in Paging message from MME, the eNodeB may decide to use MT-EDT, by adding a MT-EDT indication in the Paging message to the UE. 5-8. Follow the procedure as defined in clause 7.3b.3 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]. 9. SGW delivers downlink data to RAN. 10-11. The eNodeB can decide to use MT-EDT and move the UE to IDLE mode. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.3.5B |
2,492 | P.2 Activation of mobility management for IMS voice termination | An MS activates mobility management for IMS voice termination when: 1) the MS's availability for voice calls in the IMS (see 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120], subclause 3.1) changes from "not available" to "available"; 2) the MS is enabled for mobility management for IMS voice termination; 3) the IMS voice over PS session indicator received for Iu mode has the value - "IMS voice over PS session supported in Iu mode, but not supported in A/Gb mode", or the IMS voice over PS session indicator received for S1 mode has the value - "IMS voice over PS session in S1 mode supported"; and 4) at least one of the two parameters voice domain preference for UTRAN and voice domain preference for E-UTRAN as defined in 3GPP TS 24.167[ 3GPP IMS Management Object (MO); Stage 3 ] [134] is not "CS voice only". The MS deactivates mobility management for IMS voice termination when the MS's availability for voice calls in the IMS (see 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120], subclause 3.1) changes from "available" to "not available". | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | P.2 |
2,493 | 4.2.1.5 Number of additional E-RABs successfully established | a) This measurement provides the number of additional E-RABs successfully established. The measurement is split into subcounters per E-RAB QoS level (QCI). b) CC c) On transmission by the eNodeB/RN of an E-RAB SETUP RESPONSE message, each E-RAB successfully established is added to the relevant measurement per QCI, the possible QCIs are included in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [9]. The sum of all supported per QCI measurements shall equal the total number of additional E-RABs successfully setup. In case only a subset of per QCI measurements is supported, a sum subcounter will be provided first. d) Each measurement is an integer value. The number of measurements is equal to the number of QCIs plus a possible sum value identified by the .sum suffix. e) The measurement name has the form ERAB.EstabAddSuccNbr.QCI where QCI identifies the E-RAB level quality of service class. f) EUtranCellFDD EUtranCellTDD g) Valid for packet switched traffic h) EPS i) This measurement is to support the Accessibility KPI “E-RAB Accessibility” defined [13]. | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.2.1.5 |
2,494 | 4.12.2.3 Emergency Registration for untrusted non-3GPP Access | Emergency Registration procedure is used by UEs requiring to perform emergency services but cannot gain normal services from the network. These UEs are in limited service state as defined in TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [22]. The regular registration procedure described in clause 4.12.2 applies with the following differences: - If the UE has no SUPI and no valid 5G-GUTI, PEI shall be included instead of its encrypted Permanent User ID (SUCI) in the NAS message. - NSSAI shall not be included by the UE. The AMF shall not send the Allowed NSSAI in the Registration Accept message. - If the AMF is not configured to support Emergency Registration, the AMF shall reject any Registration Request that indicates Registration type "Emergency Registration". - If the AMF is configured to support Emergency Registration for unauthenticated UEs and the UE indicated Registration Type "Emergency Registration", the AMF skips the authentication and security setup or the AMF accepts that the authentication may fail and continues the Emergency Registration procedure. - If the authentication is performed successfully, the NAS messages will be protected by the NAS security functions (integrity and ciphering). The AMF shall derive the N3IWF key, per TS 33.501[ Security architecture and procedures for 5G System ] [15] and shall provide it to the N3IWF after the authentication completion using an NGAP Initial Context Setup Request message as in the regular registration procedure. - If the authentication is skipped or authentication fails, the NAS messages will not be protected by the NAS security functions (integrity and ciphering). However, the AMF shall create an N3IWF key and shall provide it to the N3IWF after the authentication completion (whenever authentication has failed or has been skipped) using an NGAP Initial Context Setup Request message. The N3IWF shall use it to complete IKE SA establishment and shall acknowledge the AMF by sending an NGAP Initial Context Setup Response message. NOTE: According to TS 33.501[ Security architecture and procedures for 5G System ] [15], the UE and the AMF independently generate the KAMF (and derived keys) in an implementation defined way and populate the 5G NAS security context with this KAMF to be used when activating a 5G NAS security context." - As in step 14 of figure 4.2.2.2.2-1 for Emergency Registration, if the UE was not successfully authenticated, the AMF shall not update the UDM. Also for an Emergency Registration, the AMF shall not check for access restrictions, regional restrictions or subscription restrictions. - Steps 16 and 21b of figure 4.2.2.2.2-1 are not performed since AM and UE policy for the UE are not required for Emergency Registration. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.12.2.3 |
2,495 | 9.11.3.54 UE security capability | The UE security capability information element is used by the UE and by the network to indicate which security algorithms are supported by the UE in N1 mode for NAS security as well as which security algorithms are supported over NR and E-UTRA connected to 5GCN for AS security. The UE security capability information element is coded as shown in figure 9.11.3.54.1 and table 9.11.3.54.1. The UE security capability is a type 4 information element with a minimum length of 4 octets and a maximum length of 10 octets. Octets 5 to 10 are optional. If octet 5 is included, then also octet 6 shall be included. If the UE does not support any security algorithm for AS security over E-UTRA connected to 5GCN, it shall not include octets 5 and 6. The UE shall not include octets 7 to 10. If the UE does not support any security algorithm for AS security over E-UTRA connected to 5GCN, and if the network includes octets 7 to 10, then the network shall also include octets 5 to 6. If the network includes octet 7, then it shall include also octet 8. If the network includes octet 9, then it shall include also octet 10. Figure 9.11.3.54.1: UE security capability information element Table 9.11.3.54.1: UE security capability information element | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.11.3.54 |
2,496 | 6.44.2.3 Subscription-based routing to a particular core network (e.g. in a different country) | The 5G system shall be able to support a mechanism such that all traffic pertaining to UEs of specific subscribers which is sent to the HPLMN is forwarded to a target PLMN, e.g., to enable further handling of those UEs by the target PLMN. The forwarding mechanism shall minimize traffic in the HPLMN, e.g., by using efficient means to forward traffic from selected UEs. NOTE 1: The above requirement assumes that the HPLMN has an agreement with the target PLMN, and routing policies are in place. NOTE 2: In case of UEs connected via a VPLMN, it is assumed that traffic is forwarded to the target PLMN by the HPLMN. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.44.2.3 |
2,497 | 5.2.2 System information acquisition 5.2.2.1 General UE requirements | Figure 5.2.2.1-1: System information acquisition The UE applies the SI acquisition procedure to acquire the AS, NAS- and positioning assistance data information. The procedure applies to UEs in RRC_IDLE, in RRC_INACTIVE and in RRC_CONNECTED. The UE in RRC_IDLE and RRC_INACTIVE shall ensure having a valid version of (at least) the MIB, SIB1 through SIB4, SIB5 (if the UE supports E-UTRA), SIB11 (if the UE is configured for idle/inactive measurements), SIB12 (if UE is capable of NR sidelink communication/discovery and is configured by upper layers to receive or transmit NR sidelink communication/discovery), and SIB13, SIB14 (if UE is capable of V2X sidelink communication and is configured by upper layers to receive or transmit V2X sidelink communication), SIB15 (if UE is configured by upper layers to report disaster roaming related information), SIB16 (if the UE is capable of slice-based cell reselection and the UE receives NSAG information for cell reselection from upper layer), SIB17 (if the UE is using TRS resources for power saving in RRC_IDLE and RRC_INACTIVE), SIB19 (if UE is accessing NR via NTN access) and SIB22 (for ATG access). The UE capable of MBS broadcast which is receiving or interested to receive MBS broadcast service(s) via a broadcast MRB shall ensure having a valid version of SIB20, regardless of the RRC state the UE is in. The UE shall ensure having a valid version of the posSIB requested by upper layers. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.2.2 |
2,498 | 5.6A.2 Modulation scheme π/2-BPSK | For and π/2-BPSK modulation only 2-of-3 adjacent subcarriers are selected as described in 5.5.2.1A.2. The time-continuous signal in SC-FDMA symbol in an uplink slot is defined by for where , , is given by Table 5.6-1, and and are respectively the modulation value for subcarrier index and for symbol , and the values of used on and are respectively obtained by subtracting from the resulting set of allocated subcarriers as described in Table 8.1.6-1 of [4], and represents the lower subcarrier index among the selected subcarriers and is the subcarrier index adjacent to it. The phase rotation is given by where is the number of transport blocks defined in clause 8.0 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4]. If >1 and interleaving between codewords is applied according to clause 8.0 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4], then the symbol counter is reset at the start of the first PUSCH codeword transmission and incremented for each symbol during the transmission of the PUSCH codewords. For other cases, the symbol counter is reset at the start of each PUSCH codeword transmission and incremented for each symbol during the transmission of the PUSCH codeword. The SC-FDMA symbols in a slot shall be transmitted in increasing order of , starting with , where SC-FDMA symbol starts at time within the slot. | 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.6A.2 |
2,499 | 7.1a Determining trust relationship in the UE | There are various possibilities to determine the trust relationship in the UE as it is described in TS 23.501[ System architecture for the 5G System (5GS) ] [2]. For example, the non-3GPP access networks, which are trusted, can be pre-configured in the UE. If the USIM supports non-3GPP access networks service, the home network operator may configure in the USIM a list of trusted non-3GPP access networks. In case of pre-configured information in the UE, the list of trusted non-3GPP access networks pre-configured by the home network operator in the USIM shall take precedence over information pre-configured in the ME. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 7.1a |
2,500 | 6.8.5 Intersystem handover for CS Services – from GSM BSS to UTRAN | If ciphering has been started when an intersystem handover occurs from GSM BSS to UTRAN, the necessary information (e.g. CK, IK, START value information, supported/allowed UMTS algorithms) is transmitted within the system infrastructure before the actual handover is executed to enable the communication to proceed from the old GSM BSS to the new RNC, and to continue the communication in ciphered mode. The GSM BSS requests the MS to send the UMTS capability information, which includes information on the START values and UMTS security capabilities of the MS. The intersystem handover will imply a change of ciphering algorithm from a GSM A5 to a UEA. The target UMTS RNC includes the selected UMTS ciphering mode in the handover to UTRAN command message sent to the MS via the GSM BSS. The integrity protection of signalling messages shall be started immediately after the intersystem handover from GSM BSS to UTRAN is completed. The Serving RNC will do this by initiating the RRC security mode control procedure when the first RRC message (i.e. the Handover to UTRAN complete message) has been received from the MS. In this case, the RRC security mode control procedure is initiated by the Serving RNC without receipt of a corresponding RANAP security mode control procedure from the MSC/VLR.The UE security capability information, that has been sent from MS to RNC via the GSM radio access and the system infrastructure before the actual handover execution, will be included in the RRC Security mode command message sent to MS and then verified by the MS (i.e. verified that it is equal to the UE security capability information stored in the MS). | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 6.8.5 |
Subsets and Splits
No saved queries yet
Save your SQL queries to embed, download, and access them later. Queries will appear here once saved.