Search is not available for this dataset
doc_id
int64 1
6.72k
⌀ | Section
stringlengths 5
247
⌀ | Content
stringlengths 501
147k
⌀ | Source
stringclasses 456
values | Document Title
stringclasses 22
values | Working Group
stringclasses 21
values | Series Subject
stringclasses 9
values | Subclause
stringlengths 1
13
⌀ |
|---|---|---|---|---|---|---|---|
1,501 | 19.4.2.2.1 Structure | The Access Point Name FQDN (APN-FQDN) is derived from an APN as follows. The APN consists of an APN Network Identifier (APN-NI) and an APN Operator Identifier (APN-OI), which are as defined in clause 9.1.1 and 9.1.2 of the present document. If an APN is constructed using the default APN-OI, the APN-FQDN shall be obtained from the APN by inserting the labels "apn.epc." between the APN-NI and the default APN - OI, and by replacing the label ".gprs" at the end of the default APN-OI with the labels ".3gppnetwork.org". EXAMPLE1: For an APN of internet.mnc015.mcc234.gprs, the derived APN-FQDN is internet.apn.epc.mnc015.mcc234.3gppnetwork.org If an APN is constructed using the APN-OI Replacement field (as defined in 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [3] and 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [72]), the APN-FQDN shall be obtained from the APN by inserting the labels "apn.epc." between the label "mnc<MNC>" and its preceding label, and by replacing the label ".gprs" at the end of the APN-OI Replacement field with the labels ".3gppnetwork.org". EXAMPLE 2: If an APN-OI Replacement field is province1.mnc015.mcc234.gprs and an APN-NI is internet, the derived APN-FQDN is internet. province1.apn.epc.mnc015.mcc234.3gppnetwork.org | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 19.4.2.2.1 |
1,502 | 6.7.1.1 Initial NAS security context establishment | Each AMF shall be configured via network management with lists of algorithms which are allowed for usage. There shall be one list for NAS integrity algorithms, and one for NAS ciphering algorithms. These lists shall be ordered according to a priority decided by the operator. To establish the NAS security context, the AMF shall choose one NAS ciphering algorithm and one NAS integrity protection algorithm. The AMF shall then initiate a NAS security mode command procedure, and include the chosen algorithm and UE security capabilities (to detect modification of the UE security capabilities by an attacker) in the message to the UE (see sub-clause 6.7.2 of the present document). The AMF shall select the NAS algorithm which have the highest priority according to the ordered lists. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.7.1.1 |
1,503 | 13.4.1.1.3 Access token requests in deployments with several NRFs | As described in clause 6.2.6.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [1], an operator network can deploy multiple NRFs, for example due to network slicing or network segmentation. An NF Service Consumer shall send its access token requests to the NRF where it is registered as OAuth 2.0 client. The NRF authenticates the NF Service Consumer, and may verify the input parameters in the access token request as described under Step 1 in clause 13.4.1.1.2. After successful authentication and verification of the input parameters, the NRF may forward the access token request to another NRF. If an NRF receives an access token request for an NF Service Producer that is not registered at this NRF, the NRF determines the target NRF where the NF Service Producer is registered as specified in TS 29.510[ 5G System; Network function repository services; Stage 3 ] [68] clause 5.4.2.2.2 step 2a, and forwards the access token request to the target NRF. There can also be several hops of NRFs between the NRF that receives the access token request from the NF Service Consumer and the target NRF where the NF Service Producer is registered. One possible hierarchical NRF deployment is the local NRF deployment. An NF Service Producer’s local NRF is the NRF where the NF Service Producer registered its NF profile. In the local NRF deployment, the NF Service Producer is configured with the public key which corresponds to the private key that its local NRF uses for signing the access token. Thus, when the local NRF receives an access token request from an NF Service Consumer, the local NRF checks if the NF Service Consumer is authorized to receive the requested service and, if yes, issues and signs the access token. In the case when the access token request from the NF Service Consumer was forwarded by another NRF, the local NRF of the NF Service Producer needs to trust the NRF which forwarded the access token request. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 13.4.1.1.3 |
1,504 | 8.7 Interworking without N26 interface in single-registration mode | When the UE supports single-registration mode and network supports interworking procedure without N26 interface: - For mobility from 5GC to EPC, if the UE has a current EPS NAS security context, the UE shall start using the EPS security context as defined in TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [10]. - For mobility from EPC to 5GC, if the UE has a current 5G NAS security context, the UE shall start using the 5G NAS security context as defined in the present document. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 8.7 |
1,505 | – ReferenceTimeInfo | The IE ReferenceTimeInfo contains timing information for 5G internal system clock used for, e.g., time stamping, see TS 23.501[ System architecture for the 5G System (5GS) ] [32], clause 5.27.1.2. ReferenceTimeInfo information element -- ASN1START -- TAG-REFERENCETIMEINFO-START ReferenceTimeInfo-r16 ::= SEQUENCE { time-r16 ReferenceTime-r16, uncertainty-r16 INTEGER (0..32767) OPTIONAL, -- Need S timeInfoType-r16 ENUMERATED {localClock} OPTIONAL, -- Need S referenceSFN-r16 INTEGER (0..1023) OPTIONAL -- Cond RefTime } ReferenceTime-r16 ::= SEQUENCE { refDays-r16 INTEGER (0..72999), refSeconds-r16 INTEGER (0..86399), refMilliSeconds-r16 INTEGER (0..999), refTenNanoSeconds-r16 INTEGER (0..99999) } -- TAG-REFERENCETIMEINFO-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
1,506 | 13.3.8.3 Verification of Client credentials assertion | The verification of the CCA shall be performed by the receiving node, i.e., NRF or NF Service Producer in the following way: It validates the signature of the JWS as described in RFC 7515 [45]. It validates the timestamp (iat) and/or the expiration time (exp) as specified in RFC 7519 [44]. If the receiving node is the NRF, the NRF validates the timestamp (iat) and the expiration time (exp). If the receiving node is the NF Service Producer, the NF Service Producer validates the expiration time and it may validate the timestamp. It checks that the audience claim in the the CCA matches its own type. It verifies that the NF instance ID of the NFc in the CCA matches the NF instance ID in the public key certificate used for signing the CCA. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 13.3.8.3 |
1,507 | 2.2A Subscription Permanent Identifier (SUPI) | The SUPI is a globally unique 5G Subscription Permanent Identifier allocated to each subscriber in the 5G System. It is defined in clause 5.9.2 of 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [119]. The SUPI is defined as: - a SUPI type: in this release of the specification, it may indicate an IMSI, a Network Specific Identifier (NSI), a Global Line Identifier (GLI) or a Global Cable Identifier (GCI); and - dependent on the value of the SUPI type: - an IMSI as defined in clause 2.1; - a Network Specific Identifier (NSI), taking the form of a Network Access Identifier (NAI) as defined in clause 28.7.2; - a Global Cable Identifier (GCI) taking the form of a NAI as defined in clause 28.15.2; - a Global Line Identifier (GLI) taking the form of an NAI as defined in clause 28.16.2. NOTE: Depending on the protocol used to convey the SUPI, the SUPI type can take different formats. See clauses 4.7.2, 4.7.3 and 4.7.4 of 3GPP TS 23.316[ Wireless and wireline convergence access support for the 5G System (5GS) ] [131] for details on which types of SUPI are supported by 5G-BRG, FN-BRG, 5G-CRG and FN-CRG. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 2.2A |
1,508 | 8.3.1.3.3 Minimum requirement with Different Cell ID and Colliding CRS (with single NZP CSI-RS resource) | The requirements are specified in Table 8.3.1.3.3-2, with the additional parameters in Table 8.3.1.3.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.1.3.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.1.3.3-1: Test Parameters for quasi co-location type B with different Cell ID and Colliding CRS Table 8.3.1.3.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.1.3.3 |
1,509 | 9.2.1.7 FDD (Modulation and TBS index Table 2 and 4-bit CQI Table 2 are used) | The following requirements apply to UE Category 11-12 and DL Category ≥11. For the parameters specified in Table 9.2.1.7-1, and using the downlink physical channels specified in tables C.3.2-1 and C.3.2-2, the reported CQI value according to RC.1A FDD in Table A.4-1 shall be in the range of ±1 of the reported median more than 90% of the time. If the PDSCH BLER using the transport format indicated by median CQI is less than or equal to 0.1, the BLER using the transport format indicated by the (median CQI + 1) shall be greater than 0.1, or the BLER using the transport format indicated by the (median CQI + 1) shall be less than or equal to 0.1 when the highest MCS value of the test case has reached. If the PDSCH BLER using the transport format indicated by the median CQI is greater than 0.1, the BLER using transport format indicated by (median CQI – 1) shall be less than or equal to 0.1. In this test, 4-bit CQI Table 2 in Table 7.2.3-2 in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [6], and Modulation and TBS index table 2 in Table 7.1.7.1-1A for PDSCH in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [6] are applied. Table 9.2.1.7-1: PUCCH 1-0 static test (FDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.2.1.7 |
1,510 | – SystemInformation | The SystemInformation message is used to convey one or more System Information Blocks or Positioning System Information Blocks. All the SIBs or posSIBs included are transmitted with the same periodicity. Signalling radio bearer: N/A RLC-SAP: TM Logical channels: BCCH Direction: Network to UE SystemInformation message -- ASN1START -- TAG-SYSTEMINFORMATION-START SystemInformation ::= SEQUENCE { criticalExtensions CHOICE { systemInformation SystemInformation-IEs, criticalExtensionsFuture-r16 CHOICE { posSystemInformation-r16 PosSystemInformation-r16-IEs, criticalExtensionsFuture SEQUENCE {} } } } SystemInformation-IEs ::= SEQUENCE { sib-TypeAndInfo SEQUENCE (SIZE (1..maxSIB)) OF CHOICE { sib2 SIB2, sib3 SIB3, sib4 SIB4, sib5 SIB5, sib6 SIB6, sib7 SIB7, sib8 SIB8, sib9 SIB9, ..., sib10-v1610 SIB10-r16, sib11-v1610 SIB11-r16, sib12-v1610 SIB12-r16, sib13-v1610 SIB13-r16, sib14-v1610 SIB14-r16, sib15-v1700 SIB15-r17, sib16-v1700 SIB16-r17, sib17-v1700 SIB17-r17, sib18-v1700 SIB18-r17, sib19-v1700 SIB19-r17, sib20-v1700 SIB20-r17, sib21-v1700 SIB21-r17, sib22-v1800 SIB22-r18, sib23-v1800 SIB23-r18, sib24-v1800 SIB24-r18, sib25-v1800 SIB25-r18 }, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } -- TAG-SYSTEMINFORMATION-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
1,511 | 5.11 Handling of unknown, unforeseen and erroneous protocol data | When a MAC entity receives a MAC PDU for the MAC entity's C-RNTI or Semi-Persistent Scheduling C-RNTI, or by the configured downlink assignment, containing reserved or invalid values, the MAC entity shall: - discard the received PDU. When a MAC entity receives a MAC PDU on MCH containing reserved values, or on DL-SCH containing reserved values for G-RNTI or SC-RNTI, or on SL-SCH, the MAC entity shall: - ignore the MAC PDU subheaders containing reserved values and the corresponding MAC SDUs; - in the MAC control elements, ignore the fields containing reserved values and the fields associated with the fields containing reserved values. | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.11 |
1,512 | 6.2.4A.2 A-MPR for CA_NS_02 for CA_1C | If the UE is configured to CA_1C and it receives IE CA_NS_02 the allowed maximum output power reduction applied to transmission on the PCC and the SCC for contiguously aggregated signals is specified in Table 6.2.4A.2-1. Table 6.2.4A.2-1: Contiguous allocation A-MPR for CA_NS_02 If the UE is configured to CA_1C and it receives IE CA_NS_02 the allowed maximum output power reduction applied to transmissions on the PCell and the SCell with non-contiguous resource allocation is defined as follows: A-MPR = CEIL {MA, 0.5} Where MA is defined as follows MA = -22.5 A + 17 ; 0 ≤ A < 0.20 -11.0 A + 14.7 ; 0.20 ≤ A < 0.70 -1.7 A + 8.2 ; 0.70 ≤ A ≤ 1 Where A = NRB_alloc / NRB_agg. | 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.4A.2 |
1,513 | 16.12.5.2 Radio Link Failure | The L2 U2N Remote UE in RRC_CONNECTED suspends Uu RLM (as described in clause 9.2.7) when connected to the gNB via a L2 U2N Relay UE. The L2 U2N Relay UE declares Uu Radio Link Failure (RLF) following the same criteria as described in clause 9.2.7. After Uu RLF is declared, the L2 U2N Relay UE takes the following action on top of the actions described in clause 9.2.7: - a PC5-RRC message can be used for sending an indication to its connected L2 U2N Remote UE(s), which may trigger RRC connection re-establishment for L2 U2N Remote UE; or - indicating to upper layer to trigger PC5 unicast link release. Upon detecting PC5 RLF, the L2 U2N Remote UE may trigger RRC connection re-establishment. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.12.5.2 |
1,514 | 6.1.3.2.2.2 Handling of network rejection due to SM cause #26 | If the SM cause value is #26 "insufficient resources" and the Back-off timer value IE is included, the MS shall ignore the Re-attempt indicator IE provided by the network, if any, and take different actions depending on the timer value received for timer T3396 in the Back-off timer value IE (if the MS is configured for dual priority, exceptions are specified in subclause 6.1.3.12; if the MS is an MS configured to use AC11 – 15 in selected PLMN, exceptions are specified in subclause 6.1.3.11): i) if the timer value indicates neither zero nor deactivated, the MS shall stop timer T3396 associated with the corresponding APN, if it is running. The MS shall then start timer T3396 with the value provided in the Back-off timer value IE and not send another ACTIVATE PDP CONTEXT REQUEST, ACTIVATE SECONDARY PDP CONTEXT REQUEST or MODIFY PDP CONTEXT REQUEST message with exception of those identified in subclause 6.1.3.3, for the same APN until timer T3396 expires or timer T3396 is stopped. If the MS did not send an APN for the establishment of the PDN connection and the request type was different from "emergency", the MS shall stop timer T3396 associated with no APN, if it is running. The MS shall then start timer T3396 with the value provided in the Back-off timer value IE and not send another ACTIVATE PDP CONTEXT REQUEST without an APN and with request type different from "emergency", or another ACTIVATE SECONDARY PDP CONTEXT REQUEST or MODIFY PDP CONTEXT REQUEST message with exception of those identified in subclause 6.1.3.3, for a non-emergency PDN connection established without an APN sent by the MS, until timer T3396 expires or timer T3396 is stopped. The MS shall not stop timer T3396 upon a PLMN change or inter-system change; ii) if the timer value indicates that this timer is deactivated, the MS shall not send another ACTIVATE PDP CONTEXT REQUEST, ACTIVATE SECONDARY PDP CONTEXT REQUEST or MODIFY PDP CONTEXT REQUEST message with exception of those identified in subclause 6.1.3.3, for the same APN until the MS is switched off or the SIM/USIM is removed or the MS receives a REQUEST PDP CONTEXT ACTIVATION, REQUEST SECONDARY PDP CONTEXT ACTIVATION or MODIFY PDP CONTEXT REQUEST message for the same APN or a DEACTIVATE PDP CONTEXT REQUEST message including SM cause #39 "reactivation requested" for a PDP context which was activated by the MS for the same APN from the network. If the MS did not send an APN for the establishment of the PDN connection and the request type was different from "emergency", the MS shall not send another ACTIVATE PDP CONTEXT REQUEST without an APN and with request type different from "emergency", or another ACTIVATE SECONDARY PDP CONTEXT REQUEST or MODIFY PDP CONTEXT REQUEST with exception of those identified in subclause 6.1.3.3, for a non-emergency PDN connection established without an APN sent by the MS, until the MS is switched off or the SIM/USIM is removed or the MS receives any of the following messages: a REQUEST PDP CONTEXT ACTIVATION without an APN, a REQUEST SECONDARY PDP CONTEXT ACTIVATION or MODIFY PDP CONTEXT REQUEST message for a non-emergency PDN connection established without an APN sent by the MS, or a DEACTIVATE PDP CONTEXT REQUEST message including SM cause #39 "reactivation requested" for a PDP context which was activated by the MS for a non-emergency PDN connection established without an APN sent by the MS. The timer T3396 remains deactivated upon a PLMN change or inter-system change; or iii) if the timer value indicates that this timer is zero, the MS: - shall stop timer T3396 associated with the corresponding APN, if running, and may send an ACTIVATE PDP CONTEXT REQUEST, ACTIVATE SECONDARY PDP CONTEXT REQUEST or MODIFY PDP CONTEXT REQUEST message for the same APN; and - if the MS did not send an APN for the establishment of the PDN connection and the request type was different from "emergency", the MS shall stop timer T3396 associated with no APN, if running, and may send an ACTIVATE PDP CONTEXT REQUEST message without an APN, or another ACTIVATE SECONDARY PDP CONTEXT REQUEST or MODIFY PDP CONTEXT REQUEST message for a non-emergency PDN connection established without an APN sent by the MS. If the Back-off timer value IE is not included, the MS may send an ACTIVATE PDP CONTEXT REQUEST, ACTIVATE SECONDARY PDP CONTEXT REQUEST or MODIFY PDP CONTEXT REQUEST message for the same APN. If the timer T3396 is running when the MS enters state GMM-DEREGISTERED, the MS remains switched on, and the SIM/USIM in the MS remains the same, then timer T3396 is kept running until it expires or it is stopped. If the MS is switched off when the timer T3396 is running, and if the SIM/USIM in the MS remains the same when the MS is switched on, the MS behaves as follows: - let t1 be the time remaining for T3396 timeout at switch off and let t be the time elapsed between switch off and switch on. If t1 is greater than t, then the timer shall be restarted with the value t1 – t. If t1 is equal to or less than t, then the timer need not be restarted. If the MS is not capable of determining t, then the MS shall restart the timer with the value t1; and - if prior to switch off, timer T3396 was running because an ACTIVATE PDP CONTEXT REQUEST, ACTIVATE SECONDARY PDP CONTEXT REQUEST, MODIFY PDP CONTEXT REQUEST or ACTIVATE MBMS CONTEXT REQUEST message containing the low priority indicator set to "MS is configured for NAS signalling low priority" was rejected with a timer value for timer T3396, and if timer T3396 is restarted at switch on, then the MS configured for dual priority shall handle session management requests as indicated in subclause 6.1.3.12. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.1.3.2.2.2 |
1,515 | 15.3.4 Xn-C TNL address discovery | If the NG-RAN node is aware of the RAN node ID of the candidate NG-RAN node (e.g. via the ANR function) but not of a TNL address suitable for SCTP connectivity, then the NG-RAN node can utilize the 5GC (an AMF it is connected to) to determine the TNL address as follows: - The NG-RAN node sends the UPLINK RAN CONFIGURATION TRANSFER message to the AMF to request the TNL address of the candidate NG-RAN node, and includes relevant information such as the source and target RAN node ID; - The AMF relays the request by sending the DOWNLINK RAN CONFIGURATION TRANSFER message to the candidate NG-RAN node identified by the target RAN node ID; - The candidate NG-RAN node responds by sending the UPLINK RAN CONFIGURATION TRANSFER message containing one or more TNL addresses to be used for SCTP connectivity with the initiating NG-RAN node, and includes other relevant information such as the source and target RAN node ID; - The AMF relays the response by sending the DOWNLINK CONFIGURATION TRANSFER message to the initiating NG-RAN node identified by the target RAN node ID. NOTE: Void. The NG-RAN node may determine the gNB ID length of the candidate gNB based on, e.g. OAM configuration or UE reporting in ANR function. If the NG-RAN node is not able to make this determination, it may include the NR cell identifier in the UPLINK RAN CONFIGURATION TRANSFER message to the AMF. The AMF may, if supported, determine the target gNB ID by matching the NR cell identifier with a gNB ID of a gNB it connects to. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 15.3.4 |
1,516 | 4.1.3.1.1 Main states | 4.1.3.1.1.1 GMM-NULL The GPRS capability is disabled in the MS. No GPRS mobility management function shall be performed in this state. 4.1.3.1.1.2 GMM-DEREGISTERED The GPRS capability has been enabled in the MS, but no GMM context has been established. In this state, the MS may establish a GMM context by starting the GPRS attach or combined GPRS attach procedure. 4.1.3.1.1.3 GMM-REGISTERED-INITIATED A GPRS attach or combined GPRS attach procedure has been started and the MS is awaiting a response from the network. 4.1.3.1.1.4 GMM-REGISTERED A GMM context has been established, i.e. the GPRS attach or combined GPRS attach procedure has been successfully performed. In this state, the MS may activate PDP contexts, MBMS contexts, may send and receive user data and signalling information and may reply to a page request. Furthermore, cell and routing area updating are performed. 4.1.3.1.1.5 GMM-DEREGISTERED-INITIATED The MS has requested release of the GMM context by starting the GPRS detach or combined GPRS detach procedure. This state is only entered if the MS is not being switched off at detach request. 4.1.3.1.1.6 GMM-ROUTING-AREA-UPDATING-INITIATED A routing area updating procedure has been started and the MS is awaiting a response from the network. 4.1.3.1.1.7 GMM-SERVICE-REQUEST-INITIATED (Iu mode only) A service request procedure has been started and the MS is awaiting a response from the network. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.1.3.1.1 |
1,517 | – SL-BWP-PRS-PoolConfig | The IE SL-BWP-PRS-PoolConfig is used to configure UE specific NR sidelink PRS dedicated resource pool. SL-BWP-PRSPoolConfig information element -- ASN1START -- TAG-SL-BWP-PRS-POOLCONFIG-START SL-BWP-PRS-PoolConfig-r18 ::= SEQUENCE { sl-PRS-RxPool-r18 SEQUENCE (SIZE (1..maxNrofRXPool-r16)) OF SL-PRS-ResourcePool-r18 OPTIONAL, -- Cond HO sl-PRS-TxPoolSelectedNormal-r18 SL-PRS-TxPoolDedicated-r18 OPTIONAL, -- Need M sl-PRS-TxPoolScheduling-r18 SL-PRS-TxPoolDedicated-r18 OPTIONAL, -- Need N sl-PRS-TxPoolExceptional-r18 SL-PRS-ResourcePoolConfig-r18 OPTIONAL -- Need R } SL-PRS-TxPoolDedicated-r18 ::= SEQUENCE { sl-PRS-PoolToReleaseList-r1 SEQUENCE (SIZE (1..maxNrofSL-PRS-TxPool-r18)) OF SL-PRS-ResourcePoolID-r18 OPTIONAL, -- Need N sl-PRS-PoolToAddModList-r18 SEQUENCE (SIZE (1..maxNrofSL-PRS-TxPool-r18)) OF SL-PRS-ResourcePoolConfig-r18 OPTIONAL -- Need N } SL-PRS-ResourcePoolConfig-r18 ::= SEQUENCE { sl-PRS-ResourcePoolID-r18 SL-PRS-ResourcePoolID-r18, sl-PRS-ResourcePool-r18 SL-PRS-ResourcePool-r18 OPTIONAL -- Need M } SL-PRS-ResourcePoolID-r18 ::= INTEGER (1.. maxNrofSL-PRS-TxPool-r18) -- TAG-SL-BWP-PRS-POOLCONFIG-STOP -- ASN1STOP Editor's Note: FFS If sl-PRS-TxPoolExceptional is used for SL positioning. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
1,518 | 5.3.2.2.3 RM-REGISTERED state | In the RM-REGISTERED state, the UE is registered with the network. In the RM-REGISTERED state, the UE can receive services that require registration with the network. In the RM-REGISTERED state, the UE shall: - perform Mobility Registration Update procedure if the current TAI of the serving cell (see TS 37.340[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 ] [31]) is not in the list of TAIs that the UE has received from the network in order to maintain the registration and enable the AMF to page the UE; NOTE: Additional considerations for Mobility Registration Update in case of NR satellite access are provided in clause 5.4.11.6. - perform Periodic Registration Update procedure triggered by expiration of the periodic update timer to notify the network that the UE is still active. - perform a Mobility Registration Update procedure to update its capability information or to re-negotiate protocol parameters with the network; - perform Deregistration procedure (see clause 4.2.2.3.1 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]), and enter RM-DEREGISTERED state, when the UE needs to be no longer registered with the PLMN. The UE may decide to deregister from the network at any time. - enter RM-DEREGISTERED state when receiving a Registration Reject message or a Deregistration message. The actions of the UE depend upon the cause value' in the Registration Reject or Deregistration message. See clause 4.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. When the UE RM state in the AMF is RM-REGISTERED, the AMF shall: - perform Deregistration procedure (see clauses 4.2.2.3.2, 4.2.2.3.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]), and enter RM-DEREGISTERED state for the UE, when the UE needs to be no longer registered with the PLMN. The network may decide to deregister the UE at any time; - perform Implicit Deregistration at any time after the Implicit Deregistration timer expires. The AMF shall enter RM-DEREGISTERED state for the UE after Implicit Deregistration; - when applicable, accept or reject Registration Requests or Service Requests from the UE. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.3.2.2.3 |
1,519 | 4.4.2.2 Establishment of a mapped 5G NAS security context during inter-system change from S1 mode to N1 mode in 5GMM-CONNECTED mode | In order for the UE operating in single-registration mode in a network supporting N26 interface to derive a mapped 5G NAS security context for an inter-system change from S1 mode to N1 mode in 5GMM-CONNECTED mode, the AMF shall construct a mapped 5G NAS security context from the EPS security context received from the source MME as indicated in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. The AMF shall select the 5G NAS security algorithms and derive the 5G NAS keys (i.e. KNASenc and KNASint). The AMF shall define an ngKSI for the newly derived K'AMF key such that the value field is taken from the eKSI of the KASME key and the type field is set to indicate a mapped security context and associate this ngKSI with the newly created mapped 5G NAS security context. The AMF shall then include the message authentication code, selected NAS algorithms, NCC and generated ngKSI in the S1 mode to N1 mode NAS transparent container IE (see subclause 9.11.2.9). When the UE operating in single-registration mode in a network supporting N26 interface receives the command to perform inter-system change to N1 mode in 5GMM-CONNECTED mode, the UE shall derive a mapped K'AMF, as indicated in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24], using the KASME from the EPS security context. Furthermore, the UE shall also derive the 5G NAS keys from the mapped K'AMF using the selected NAS algorithm identifiers included in the S1 mode to N1 mode NAS transparent container IE and associate this mapped 5G NAS security context with the ngKSI value received. The UE shall then verify the received NAS MAC. In case the received NAS MAC is not verified successfully (see subclause 4.4.3.3) the UE shall discard the content of the received S1 mode to N1 mode NAS transparent container IE and inform the lower layers that the received S1 mode to N1 mode NAS transparent container is invalid. When the UE operating in single-registration mode in a network supporting N26 interface has a PDN connection for emergency bearer services and has no current EPS security context, the AMF shall set 5G-IA0 and 5G-EA0 as the selected 5G NAS security algorithms in the S1 mode to N1 mode NAS transparent container IE. The AMF shall create a locally generated K'AMF. The AMF shall set the ngKSI value of the associated security context to "000" and the type of security context flag to "mapped security context" in the S1 mode to N1 mode NAS transparent container IE. When the UE operating in single-registration mode in a network supporting N26 interface receives the command to perform inter-system change to N1 mode in 5GMM-CONNECTED mode (see 3GPP TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [30]) and has a PDN connection for emergency bearer services, if 5G-IA0 and 5G-EA0 as the selected 5G NAS security algorithms are included in the S1 mode to N1 mode NAS transparent container IE, the UE shall create a locally generated K'AMF. Furthermore, the UE shall set the ngKSI value of the associated security context to the KSI value received. After the new mapped 5G NAS security context is taken into use for the 3GPP access following a successful inter system change from S1 mode to N1 mode in 5GMM-CONNECTED mode and the UE is registered with the same PLMN over the 3GPP access and non-3GPP access: a) if a native 5G NAS security context is used on the non-3GPP access and: 1) the UE is in 5GMM-IDLE mode over non-3GPP access, then the AMF and the UE shall activate and take into use the new mapped 5G NAS security context on the 3GPP access for the non-3GPP access as described in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24] after the AMF sends or the UE receives the REGISTRATION ACCEPT message respectively. The UE and AMF shall keep the native 5G NAS security context which was used on the non-3GPP access and make it a non-current native 5G NAS security context. The non-current native 5G NAS security context may be re-activated later using the security mode control procedure; or 2) the UE is in 5GMM-CONNECTED mode over non-3GPP access, in order to activate the native 5G NAS security context over the 3GPP access that is active on the non-3GPP access the AMF shall send the SECURITY MODE COMMAND message over the 3GPP access as described in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. The SECURITY MODE COMMAND message shall include the same ngKSI to identify the native 5G NAS security context that is used on the non-3GPP access; or b) if a mapped 5G NAS security context is used on the non-3GPP access and: 1) the UE is in 5GMM-IDLE mode over non-3GPP access, the AMF and the UE shall activate and take into use the new mapped 5G NAS security context active on the 3GPP access for the non-3GPP access as described in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24] after the AMF sends or the UE receives the REGISTRATION ACCEPT message respectively; or 2) the UE is in 5GMM-CONNECTED mode over non-3GPP access, in order to activate the same mapped 5G NAS security context over one access that is used on the other access the AMF shall send the SECURITY MODE COMMAND message over one-access as described in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. The SECURITY MODE COMMAND message shall include the same ngKSI to identify the mapped 5G NAS security context that is used over the other access. If the inter-system change from S1 mode to N1 mode in 5GMM-CONNECTED mode is not completed successfully, the AMF and the UE operating in single-registration mode in a network supporting N26 interface shall delete the new mapped 5G NAS security context. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.4.2.2 |
1,520 | 5.10.2.2 Initiation | If configured to receive MBS multicast services in RRC_INACTIVE, a UE applies the multicast MCCH information acquisition procedure for PTM configuration update and upon reselection to a new cell providing SIB24. A UE that is receiving MBS multicast data in RRC_INACTIVE shall apply the multicast MCCH information acquisition procedure upon receiving a notification that the multicast MCCH information has changed. NOTE: It is up to UE implementation how to address a possibility of the UE missing a multicast MCCH change notification. Unless explicitly stated otherwise in the procedural specification, the multicast MCCH information acquisition procedure overwrites any stored multicast MCCH information, i.e. delta configuration is not applicable for multicast MCCH information and the UE discontinues using a field if it is absent in multicast MCCH information. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.10.2.2 |
1,521 | 10.3.2.3 FPBI class B | This class is reserved for more complex private installation such as multi-cell PABXs. bit No 19 1 +-------------------------------------+ |0 1| | +-------------------+ Type| CNN + FPN + RPN | FPBI 19 bits <-------------------------------------> Figure 16: Structure of FPBI class B The FPBI class B is composed of the following elements: - FPBI Class B Type. Its length is 2 bits and its value is 01; - CTS Network Number (CNN). Its length is defined by the manufacturer or the system installer; - Fixed Part Number (FPN). Its length is defined by the manufacturer or the system installer; - Radio Part Number (RPN) assigned by the CTS manufacturer or system installer. Its length is defined by the manufacturer or the system installer. NOTE: RPN is used to separate a maximum of 2RPN length different cells from each other. This defines a cluster of cells supporting intercell handover. RPN length is submitted to a CTS-MS as a result of a successful attachment. The FPBI Length Indicator shall be set to (2 + CNN Length) for a class B FPBI. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 10.3.2.3 |
1,522 | – CarrierAggregationVariant | The IE CarrierAggregationVariant informs the network about supported "placement" of the SpCell in an NR cell group. CarrierAggregationVariant information element -- ASN1START -- TAG-CARRIERAGGREGATIONVARIANT-START CarrierAggregationVariant ::= SEQUENCE { fr1fdd-FR1TDD-CA-SpCellOnFR1FDD ENUMERATED {supported} OPTIONAL, fr1fdd-FR1TDD-CA-SpCellOnFR1TDD ENUMERATED {supported} OPTIONAL, fr1fdd-FR2TDD-CA-SpCellOnFR1FDD ENUMERATED {supported} OPTIONAL, fr1fdd-FR2TDD-CA-SpCellOnFR2TDD ENUMERATED {supported} OPTIONAL, fr1tdd-FR2TDD-CA-SpCellOnFR1TDD ENUMERATED {supported} OPTIONAL, fr1tdd-FR2TDD-CA-SpCellOnFR2TDD ENUMERATED {supported} OPTIONAL, fr1fdd-FR1TDD-FR2TDD-CA-SpCellOnFR1FDD ENUMERATED {supported} OPTIONAL, fr1fdd-FR1TDD-FR2TDD-CA-SpCellOnFR1TDD ENUMERATED {supported} OPTIONAL, fr1fdd-FR1TDD-FR2TDD-CA-SpCellOnFR2TDD ENUMERATED {supported} OPTIONAL } -- TAG-CARRIERAGGREGATIONVARIANT-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
1,523 | 4.3.6.1 MM information procedure initiation by the network | The MM information procedure consists only of the MM INFORMATION message sent from the network to the mobile station. During an RR connection, the network shall send none, one, or more MM INFORMATION messages to the mobile station. If more than one MM INFORMATION message is sent, the messages need not have the same content. NOTE: The network may be able to select particular instants where it can send the MM INFORMATION message without adding delay to, or interrupting, any CM layer transaction, e.g. immediately after the AUTHENTICATION REQUEST message. | 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.6.1 |
1,524 | 7.4.1A Minimum requirements for CA | For inter-band carrier aggregation with one component carrier per operating band and the uplink assigned to one E-UTRA band the maximum input level is defined with the uplink active on the band(s) other than the band whose downlink is being tested. For E-UTRA CA configurations including an operating band without uplink band or an operating band with an unpaired DL part, the requirements for all downlinks shall be met with the single uplink carrier active in each band capable of UL operation. The UE shall meet the requirements specified in subclause 7.4.1 for each component carrier while all downlink carriers are active. For intra-band contiguous carrier aggregation maximum input level is defined as the powers received at the UE antenna port over the Transmission bandwidth configuration of each CC, at which the specified relative throughput shall meet or exceed the minimum requirements for the specified reference measurement channel over each component carrier. The downlink SCC(s) shall be configured at nominal channel spacing to the PCC. For FDD the PCC shall be configured closest to the uplink band. All downlink carriers shall be active throughout the test. The uplink output power shall be set as specified in Table 7.4.1A-1 with the uplink configuration set according to Table 7.3.1A-1 for the applicable carrier aggregation configuration. For UE(s) supporting one uplink carrier, the uplink configuration of the PCC shall be in accordance with Table 7.3.1-2. The throughput shall be ≥ 95% of the maximum throughput of the reference measurement channels over each component carrier as specified in Annexes A.2.2, A.2.3 and A.3.2 (with one sided dynamic OCNG Pattern OP.1 FDD/TDD as described in Annex A.5.1.1/A.5.2.1) with parameters specified in Table 7.4.1A-1. For operating bands with an unpaired DL part (as noted in Table 5.5-1), the requirements also apply for an SCC assigned in the unpaired part with parameters specified in Table 7.4.1A-1. For intra-band non-contiguous carrier aggregation with one uplink carrier and two or more downlink sub-blocks, each larger than or equal to 5 MHz, the maximum input level requirements are defined with the uplink configuration in accordance with Table 7.3.1A-3. For this uplink configuration, the UE shall meet the requirements for each sub-block as specified in Table 7.4.1-1 and Table 7.4.1A-1 for one component carrier and two component carriers per sub-block, respectively. The throughput of each downlink component carrier shall be ≥ 95% of the maximum throughput of the specified reference measurement channel as specified in Annexes A.2.2, A.2.3 and A.3.2 (with one sided dynamic OCNG Pattern OP.1 FDD/TDD as described in Annex A.5.1.1/A.5.2.1). The requirements apply with all downlink carriers active. Table 7.4.1A-1: Maximum input level for intra-band contiguous CA For combinations of intra-band and inter-band carrier aggregation and one uplink assigned to one E-UTRA band, the requirement is defined with the uplink active in a band other than that supporting the downlink(s) under test. The uplink configuration shall be in accordance with Table 7.3.1A-3 when the uplink is active in the band supporting two or more non-contiguous component carriers, Table 7.3.1A-1 when the uplink is active in a band supporting two contiguous component carriers and in accordance with Table 7.3.1-2 when the uplink is active in a band supporting one carrier per band. The downlink PCC shall be configured closer to the uplink operating band than the downlink SCC(s) when the uplink is active in band(s) supporting contiguous aggregation. For these uplink configurations, the UE shall meet the maximum input-level requirements for intra-band non-contiguous carrier aggregation of two or more downlink sub-blocks, the requirements for intra-band contiguous carrier aggregation for the contiguously aggregated downlink carriers and for any remaining component carrier(s) the the requirements specified in subclause 7.4.1. All downlink carriers shall be active throughout the tests and the requirements for the downlinks shall be met with the single uplink carrier active in each band capable of UL operation. | 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.4.1A |
1,525 | – RemoteUEInformationSidelink | The RemoteUEInformationSidelink message is used to request SIB(s) or provide paging related information as specified in clause 5.8.9.8.1. Signalling radio bearer: SL-SRB3 RLC-SAP: AM Logical channel: SCCH Direction: L2 U2N Remote UE to L2 U2N Relay UE RemoteUEInformationSidelink message -- ASN1START -- TAG-REMOTEUEINFORMATIONSIDELINK-START RemoteUEInformationSidelink-r17 ::= SEQUENCE { criticalExtensions CHOICE { remoteUEInformationSidelink-r17 RemoteUEInformationSidelink-r17-IEs, criticalExtensionsFuture SEQUENCE {} } } RemoteUEInformationSidelink-r17-IEs ::= SEQUENCE { sl-RequestedSIB-List-r17 SetupRelease { SL-RequestedSIB-List-r17} OPTIONAL, -- Need M sl-PagingInfo-RemoteUE-r17 SetupRelease { SL-PagingInfo-RemoteUE-r17} OPTIONAL, -- Need M lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension RemoteUEInformationSidelink-v1800-IEs OPTIONAL } RemoteUEInformationSidelink-v1800-IEs ::= SEQUENCE { sl-RequestedPosSIB-List-r18 SetupRelease { SL-RequestedPosSIB-List-r18 } OPTIONAL, -- Need M sl-SFN-DFN-OffsetRequested-r18 ENUMERATED { true } OPTIONAL, -- Need R connectionForMP-r18 ENUMERATED {true} OPTIONAL, -- Need N lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } SL-RequestedSIB-List-r17 ::= SEQUENCE (SIZE (maxSIB-MessagePlus1-r17)) OF SL-SIB-ReqInfo-r17 SL-PagingInfo-RemoteUE-r17 ::= SEQUENCE { sl-PagingIdentityRemoteUE-r17 SL-PagingIdentityRemoteUE-r17, sl-PagingCycleRemoteUE-r17 PagingCycle OPTIONAL -- Need M } SL-SIB-ReqInfo-r17 ::= ENUMERATED { sib1, sib2, sib3, sib4, sib5, sib6, sib7, sib8, sib9, sib10, sib11, sib12, sib13, sib14, sib15, sib16, sib17, sib18, sib19, sib20, sib21, sibNotReq11, sibNotReq10, sibNotReq9, sibNotReq8, sibNotReq7, sibNotReq6, sibNotReq5, sibNotReq4, sibNotReq3, sibNotReq2, sibNotReq1, ... } SL-RequestedPosSIB-List-r18 ::= SEQUENCE (SIZE (1..maxSIB)) OF SL-PosSIB-ReqInfo-r18 SL-PosSIB-ReqInfo-r18 ::= SEQUENCE { gnss-id-r18 GNSS-ID-r16 OPTIONAL, -- Need R sbas-id-r18 SBAS-ID-r16 OPTIONAL, -- Cond GNSS-ID-SBAS posSibType-r18 ENUMERATED { posSibType1-1, posSibType1-2, posSibType1-3, posSibType1-4, posSibType1-5, posSibType1-6, posSibType1-7, posSibType1-8, posSibType1-9, posSibType1-10, posSibType2-1, posSibType2-2, posSibType2-3, posSibType2-4, posSibType2-5, posSibType2-6, posSibType2-7, posSibType2-8, posSibType2-9, posSibType2-10, posSibType2-11, posSibType2-12, posSibType2-13, posSibType2-14, posSibType2-15, posSibType2-16, posSibType2-17, posSibType2-18, posSibType2-19, posSibType2-20, posSibType2-21, posSibType2-22, posSibType2-23, posSibType2-24, posSibType2-25, posSibType3-1, posSibType4-1, posSibType5-1,posSibType6-1, posSibType6-2, posSibType6-3,posSibType6-4, posSibType6-5, posSibType6-6,... } } -- TAG-REMOTEUEINFORMATIONSIDELINK-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
1,526 | 4.12a.6 UE or network Requested PDU Session Modification via Trusted non-3GPP access | The UE or network requested PDU Session Modification procedure via trusted non-3GPP access is the same procedure as the one specified in clause 4.12.6 for untrusted non-3GPP access, with the following modifications: - The N3IWF in Figure 4.12.6-1 should be substituted with a TNGF and the Untrusted non-3GPP access should be substituted with a Trusted non-3GPP Access Point (TNAP). - The IKEv2 Create Child SA Request sent by the TNGF in step 4a, in order to create new QoS flow(s) for the PDU Session, shall include the Additional QoS Information defined in clause 4.12a.5. If the UE decides to reserve QoS resources over non-3GPP access for the QoS flows associated with the Child SA but fails to reserve these resources, the UE shall reject the IKEv2 Child SA Request. Based on operator policy, the network may reattempt to establish the Child SA without the Additional QoS Information. - The IKEv2 Informational Request sent by the TNGF in step 4b shall include the Additional QoS Information defined in clause 4.12a.5, when the IKEv2 Informational Request is sent to modify one or more existing QoS flows. If the UE decides to reserve QoS resources over non-3GPP access for the QoS flows associated with the Child SA but fails to reserve these resources, the UE shall indicate the failure in the IKEv2 Informational Response. The TNGF includes the list of QoS flows which are failed to setup in step 5. Based on operator policy, the network may reattempt to modify the failed QoS Flows without the Additional QoS Information. - The IKEv2 Informational Request sent by the TNGF in step 4c to release an existing IKEv2 Child SA shall trigger the UE to release the resources reserved over non-3GPP access for this IKEv2 Child SA. - If, after the PDU Session establishment, the UE determines that the QoS resources reserved over non-3GPP access for the QoS flows associated with a Child SA are released, then the UE shall initiate an INFORMATIONAL exchange, as specified in RFC 7296 [3], to delete the Child SA. After the Child SA is deleted, the TNGF initiates PDU Session Modification procedure as described in step 1e, in clause 4.3.3.2, including the list of QoS flows, which are released. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.12a.6 |
1,527 | 5.5.3.1.1 Sequence generation for basic SRS | The sounding reference signal sequence is defined by clause 5.5.1, where is the sequence-group number defined in clause 5.5.1.3, is the base sequence number defined in clause 5.5.1.4, and . The cyclic shift of the sounding reference signal is given as , where is configured separately for periodic and each configuration of aperiodic sounding by the higher-layer parameters cyclicShift and cyclicShift-ap, respectively, for each UE and is the number of antenna ports used for sounding reference signal transmission. The parameter if , otherwise . The parameter is given by the higher layer parameter transmissionCombNum if configured, otherwise . | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.5.3.1.1 |
1,528 | 4.25 Support of MUSIM features | A network and a MUSIM UE may support one or more of the MUSIM features (i.e. the N1 NAS signalling connection release, the paging indication for voice services, the reject paging request, the paging restriction and the paging timing collision control). If MUSIM UE supports one or more MUSIM features, the UE indicates support of one or more MUSIM features (except for the paging timing collision control) during the registration procedure. If the UE has indicated support of the N1 NAS signalling connection release or the reject paging request or both and the UE supports the paging restriction, the UE indicates support of the paging restriction. If the UE indicates support of one or more MUSIM features and the network decides to accept one or more MUSIM features, the network indicates the support of one or more MUSIM features during the registration procedure. The network only indicates the support of the paging restriction together with the support of either N1 NAS signalling connection release or the reject paging request. The network does not indicate support for any MUSIM feature to the UE during the registration for emergency services. If the UE is not currently registered for emergency service and the UE receives the CONFIGURATION UPDATE COMMAND message with the 5GS registration result IE value set to "Registered for emergency services", then UE shall behave as if the network did not indicate support for any MUSIM feature in the last registration procedure. If the network has sent CONFIGURATION UPDATE COMMAND message with the 5GS registration result IE value set to "Registered for emergency services", then network shall behave as if it did not indicate support for any MUSIM feature in the last registration procedure. If a UE stops fulfilling the condition to be considered a MUSIM UE as defined in subclause 3.1, and the UE has negotiated support of one or more MUSIM features, then the UE shall initiate a registration procedure for mobility and periodic registration update to indicate that all the MUSIM features are not supported (except for the paging timing collision control) as specified in subclause 5.5.1.3. A MUSIM UE operating in NB-N1 mode or in WB-N1 mode CE mode B does not indicate the support for paging indication for voice services during the registration procedure towards the network. | 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.25 |
1,529 | 5.3.7.3a Actions following relay selection while T311 is running | Upon selecting a suitable L2 U2N Relay UE, the L2 U2N Remote UE shall: 1> indicate to upper layer to trigger the PC5 unicast link establishment with the selected L2 U2N Relay UE, if a new L2 U2N Relay UE is selected; 1> ensure having valid and up to date essential system information as specified in clause 5.2.2.2; 1> stop timer T311; 1> if T390 is running: 2> stop timer T390 for all access categories; 2> perform the actions as specified in 5.3.14.4; 1> stop the cell selection procedure, if ongoing; 1> start timer T301; 1> release the RLC entity for SRB0, if any; 1> establish a SRAP entity as specified in TS 38.351[ NR; Sidelink Relay Adaptation Protocol (SRAP) Specification ] [66], if no SRAP entity has been established; 1> apply the specified configuration of SL-RLC0 as specified in 9.1.1.4; 1> apply the SDAP configuration and PDCP configuration as specified in 9.1.1.2 for SRB0; 1> initiate transmission of the RRCReestablishmentRequest message in accordance with 5.3.7.4. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.7.3a |
1,530 | B.3 Derivation of CK’CS|| IK’CS from CKPS||IKPS | This input string is used for UMTS subscribers when there is a need to derive CK’CS|| IK’CS from CKPS||IKPS during mapping the security contexts from HSPA to UTRAN/GERAN. The Key is the concatenation of CKPS||IKPS (which are 128 bits each), and the output is CK’CS||IK’CS (which are 128 bits each). - FC = 0x30 - P0 = NONCE - L0 = length of NONCE (i.e. 0x00 0x10) Further, the GSM Kc’ used in GERAN shall be derived from CK’CS||IK’CS using the key conversion function c3 defined in this specification. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | B.3 |
1,531 | 8.11.2.1.3 CE Mode A with TM9 interference model | The requirements are specified in Table 8.11.2.1.3-2, with the addition of parameters in Table 8.11.2.1.3-1. In Table 8.11.2.1.3-2, Cell 1 is the serving cell, and Cell 2 and Cell 3 are the aggressor cells. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1, Cell 2 and Cell 3, respectively. The CRS assistance information [7] is provided to the UE and includes information on Cell 2 and Cell 3. The purpose of the test is to verify the MPDCCH performance under assumption that UE applies CRS interference mitigation in the scenario with 2 CRS antenna ports in the serving and aggressor cells. Table 8.11.2.1.3-1: Test Parameters for MPDCCH Table 8.11.2.1.3-2: Minimum performance CE Mode A MPDCCH | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.11.2.1.3 |
1,532 | 9.11.4.13 QoS rules | The purpose of the QoS rules information element is to indicate a set of QoS rules to be used by the UE, where each QoS rule is a set of parameters as described in subclause 6.2.5.1.1.2: a) for classification and marking of uplink user traffic; and b) for identification of a QoS flow which the network is to use for a particular downlink user traffic. NOTE: The UE needs to be aware of a QoS flow which the network is to use for a particular downlink user traffic e.g. to determine whether a resource is available for downlink media of a media stream of an SDP media description provided by the UE in an IMS session. The QoS rules may contain a set of packet filters consisting of zero or more packet filters for UL direction, zero or more packet filters for DL direction, zero or more packet filters for both UL and DL directions or any combinations of these. The set of packet filters determine the traffic mapping to QoS flows. The QoS rules information element is a type 6 information element with a minimum length of 7 octets. The maximum length for the information element is 65538 octets. The QoS rules information element is coded as shown in figure 9.11.4.13.1, figure 9.11.4.13.2, figure 9.11.4.13.3, figure 9.11.4.13.4 and table 9.11.4.13.1. Figure 9.11.4.13.1: QoS rules information element Figure 9.11.4.13.2: QoS rule (u=m+2) Figure 9.11.4.13.3: Packet filter list when the rule operation is "modify existing QoS rule and delete packet filters" (m=N+7) Figure 9.11.4.13.4: Packet filter list when the rule operation is "create new QoS rule", or "modify existing QoS rule and add packet filters" or "modify existing QoS rule and replace all packet filters" Table 9.11.4.13.1: QoS rules 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.13 |
1,533 | 4.13.8.2 Mobility Management and UE Power Saving Optimization | For satellite access that provides discontinuous network coverage, and in case both the UE and the network support Enhanced Discontinuous Coverage, then the Mobility Management and UE Power Saving Optimization functionality may be used. If both the UE and the network indicate support for "Enhanced Discontinuous Coverage Support" and if the UE determines it will lose coverage and will become unavailable, and decides to remain in no service during that time, then: - The UE may be able to determine, including considering current and expected future locations of the UE, a Start of Unavailability Period and/or Unavailability Period Duration for when it expects to be out of coverage. NOTE 1: A UE, based on implementation, can combine successive periods of no satellite coverage into a single continuous period that is notified to the network if the UE does not require network access during this period. NOTE 2: UE informing the network of coverage gaps would increase signalling and UE power consumption if coverage gaps are more frequent than UE's communication period. - The UE triggers a TAU procedure and includes an indication of upcoming loss of coverage in the TAU Request message to the MME. If the UE is able to determine a Start of Unavailability Period and/or Unavailability Period Duration it also includes them in the TAU Request message. - The UE should trigger the TAU procedure early enough such that the procedure, under normal conditions, is able to complete before the start of the unavailability period. - The UE and the MME re-negotiate unavailability at every TAU procedure, if it is required. If Start of Unavailability Period and/or Unavailability Period Duration is not included in a TAU Request message any pending loss of coverage configuration stored in the UE context at MME is discarded. - If the UE determines an upcoming loss of coverage to the network no longer applies or determines a new Start of Unavailability Period or Unavailability Period Duration related to the upcoming loss of coverage, the UE sends a new TAU Request to the MME to update the Start of Unavailabililty Period and/or Unavailability Period Duration. Upon receiving a TAU Request message from the UE including an indication of upcoming loss of coverage: - If the UE did not include a Start of Unavailability Period, the MME considers implicitly the Start of Unavailability Period to be the time at which it has received the TAU Request message from the UE. If the UE included a Start of Unavailability Period, the Start of Unavailability Period indicates the time at which the UE determines it expects to lose coverage, i.e. time until which the UE determines it is available. - The MME may determine, if not provided by the UE, or update the Unavailability Period Duration and/or the Start of Unavailability Period. If the MME knows an Unavailability Period Duratio and/or the Start of Unavailability Periodn (e.g. based on information available to the MME as described in clause 4.13.8.4) for the UE, and the UE not include an Unavailability Period Duration and/or the Start of Unavailability Period or included an Unavailability Period Duration and/or the Start of Unavailability Period different to the Unavailability Period Duration and/or the Start of Unavailability Period known to the MME, the MME may use either the Unavailability Period Duration and/or the Start of Unavailability Period known to the MME or the Unavailability Period Duration and/or the Start of Unavailability Period from the UE as the Unavailability Period Duration and/or the Start of Unavailability Period. The MME should include the Unavailability Period Duration and/or the Start of Unavailability Period known to the MME in the TAU Accept. How the UE treats the MME provided Unavailability Period Duration and/or the Start of Unavailability Period is up to UE implementation e.g. to help to determine when to return to coverage after a discontinuous coverage period, whether to listen to paging in eDRX, not to initiate any NAS signalling (including Service Request for MO data) within the discontinuous coverage period in case of any UL signalling/data request or the UE may deactivate its Access Stratum functions for satellite access in order to optimise power consumption until coverage returns, etc. The MME indicates to the UE in the Attach Accept or TAU Accept whether the UE is not required to perform a TAU procedure when the unavailability period has ended. - The MME stores the information that the UE is unavailable at the Start of Unavailability Period in the UE context, and considers the UE is unreachable from then until the UE enters ECM_CONNECTED state. If the UE requests power saving features the MME uses procedures defined in other clauses to provide the UE with timers (e.g. periodic TAU timer, extended idle mode DRX (see clause 5.13a), and PSM mode configuration (see clause 4.3.22)), and may also consider the Unavailability Period Duration (if available) and Start of Unavailability Period (if available). Unless the MME indicated that the UE is not required to perform a TAU procedure when the unavailability period has ended, then once the event which makes the UE unavailable is completed in the UE, the UE triggers a TAU procedure. If the event which makes the UE unavailable is delayed to a future time or cancelled or unavailability period deviates from negotiated value in the UE, the UE triggers TAU procedure. The MME should adjust the mobile reachable timer or Implicit Detach timer or both such that the MME does not implicitly detach the UE while the UE is out of coverage, see clause 3,4.2. Features described for High latency communication in clause 4.3.14.7 may be used to handle mobile terminated (MT) communication with UEs being unreachable due to satellite access with discontinuous coverage and the Unavailability Period Duration (if available) and Start of Unavailability Period (if available) may be used when determining the Estimated Maximum Wait Time. The UE may send Tracking Area Update request message to inform the network of its UE unavailability period even if Mobility Management back-off timer is running. | 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.13.8.2 |
1,534 | 9.11.4.10 PDU address | The purpose of the PDU address information element is to assign to the UE: - an IPv4 address associated with a PDU session; - an interface identifier for the IPv6 link local address associated with the PDU session; or - an IPv4 address and an interface identifier for the IPv6 link local address, associated with the PDU session. This purpose of the PDU address information element is also to enable the W-AGF acting on behalf of the FN-RG to provide an interface identifier for the IPv6 link local address associated with the PDU session suggested to be allocated to the FN-RG, and to enable the SMF to provide SMF's IPv6 link local address to the W-AGF acting on behalf of the FN-RG. The PDU address information element is coded as shown in figure 9.11.4.10.1 and table 9.11.4.10.1. The PDU address is a type 4 information element with minimum length of 7 octets and a maximum length of 31 octets. Figure 9.11.4.10.1: PDU address information element Table 9.11.4.10.1: PDU address 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.10 |
1,535 | – UE-CapabilityRequestFilterNR | The IE UE-CapabilityRequestFilterNR is used to request filtered UE capabilities. UE-CapabilityRequestFilterNR information element -- ASN1START -- TAG-UE-CAPABILITYREQUESTFILTERNR-START UE-CapabilityRequestFilterNR ::= SEQUENCE { frequencyBandListFilter FreqBandList OPTIONAL, -- Need N nonCriticalExtension UE-CapabilityRequestFilterNR-v1540 OPTIONAL } UE-CapabilityRequestFilterNR-v1540 ::= SEQUENCE { srs-SwitchingTimeRequest ENUMERATED {true} OPTIONAL, -- Need N nonCriticalExtension UE-CapabilityRequestFilterNR-v1710 OPTIONAL } UE-CapabilityRequestFilterNR-v1710 ::= SEQUENCE { sidelinkRequest-r17 ENUMERATED {true} OPTIONAL, -- Need N nonCriticalExtension SEQUENCE {} OPTIONAL } -- TAG-UE-CAPABILITYREQUESTFILTERNR-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
1,536 | 5.2.26.2.2 Nupf_EventExposure_Notify service operation | Service operation name: Nupf_EventExposure_Notify Description: This service operation reports the event and information to the consumer that has subscribed implicitly. Input Required: Event ID, UE address (i.e. IP address or MAC address). Notification Correlation Information. Input, Optional: UE ID, Event specific parameter as described in clause 5.2.26.2.1, time stamps for the measures, Application Id and Packet Filter Set, Achieved sampling ratio. Output Required: Result Indication. Output, Optional: None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.26.2.2 |
1,537 | 4.23.7.2.2 Preparation phase | Compared to the procedure in clause 4.9.1.3.2, the SMF interacting with the S-UPF, T-UPF, S-AMF and T-AMF is the I-SMF. The difference is following: - Step 3: The N14 context exchanged between S-AMF and T-AMF contains the SM Context ID at I-SMF, or SM Context ID at SMF if I-SMF is not applicable before. - Step 4: The T-AMF determines whether Target I-SMF needs to be selected based on UE location and service area of the SMF. In this case no I-SMF change or removal is needed. - Step 5: The I-SMF checks whether I-UPF needs to be reallocated, i.e. select a T-UPF. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.23.7.2.2 |
1,538 | 6.2.3 Service continuity requirements | The 5G system shall enable packet loss to be minimized during inter- and/or intra- access technology changes for some or all connections associated with a UE. The 5G system shall minimize interruption time during inter- and/or intra- access technology mobility for some or all connections associated with a UE. NOTE: The interruption time includes all delays which have impact on service continuity. For applications that require the same IP address during the lifetime of the session, the 5G system shall enable maintaining the IP address assigned to a UE when moving across different cells and access technologies for connections associated with a UE. The 5G system shall enable minimizing impact to the user experience (e.g. minimization of interruption time) when changing the IP address and IP anchoring point for some or all connections associated with a UE. The 5G system shall support service continuity for a remote UE, when the remote UE changes from a direct network connection to an indirect network connection and vice-versa. The 5G system shall support service continuity for a remote UE, when the remote UE changes from one relay UE to another and both relay UEs use 3GPP access to the 5G core network. Satellite access related service continuity requirements are covered in clause 6.46.3. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.2.3 |
1,539 | 6.2.24 DCCF | The Data Collection Coordination Function (DCCF) supports the following functionality: - Determining Data Sources that can provide data for a received data request. - Determining whether data is already being collected from a data source. - Instructing a Messaging Framework to send data to consumers or notification endpoints. - Instructing a Messaging Framework to do formatting and processing of the data sent via the Messaging Framework. - Formatting and processing of data. - Sending data to consumers or notification endpoints. - Registering NWDAFs and ADRFs that are already receiving data from a Data Source. The DCCF functionality is specified in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [86]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.2.24 |
1,540 | 4.15.6.14 Procedures for AF requested QoS for a UE or group of UEs not identified by a UE address | Figure 4.15.6.14-1: Procedure for AF requested QoS for a UE or group of UEs not identified by a UE address 0. When a new PDU Session is established, based on local configuration associated with the DNN/S-NSSAI, the PCF determines if the PDU Session needs involvement of TSCTSF. If the TSCTSF is used the PCF invokes Npcf_PolicyAuthorization_Notify service operation to the TSCTSF discovered and selected as described in clause 6.3.24 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The Npcf_PolicyAuthorization_Notify service operation includes the UE address of the PDU Session and DNN/S-NSSAI. If the TSCTSF is not used, the PCF subscribes to notifications for Application Data from UDR. NOTE: In the case of private IPv4 address being used for the UE, the DNN and S-NSSAI are required for session binding in the PCF. The PCF registers to BSF as described in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. When the TSCTSF is used, the TSCTSF invokes a Npcf_PolicyAuthorization_Create request message to the PCF and stores the DNN, S-NSSAI and IP address as received from PCF and SUPI as received from BSF and associates them with the AF-session. 1. The AF sends a request to reserve resources using Nnef_AF_Request_QoS_Create request message (GPSI or External Group ID, AF Identifier, Flow description(s) or External Application Identifier, QoS reference or individual QoS parameters, Alternative Service Requirements (as described in clause 6.1.3.22 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]), DNN, S-NSSAI) to the NEF. Optionally, a period of time or a traffic volume for the requested QoS can be included in the AF request. The AF may, instead of a QoS Reference, provide the individual QoS parameters. Regardless, whether the AF request is formulated using a QoS Reference or Individual QoS paramaters, the AF may also provide one or more of the parameters that describe the traffic characteristics as described in clause 6.1.3.23 or 6.1.3.23a of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. The optional Alternative Service Requirements provided by the AF shall either contain QoS References or Requested Alternative QoS Parameter Set(s) in a prioritized order as described in clause 6.1.3.22 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. 2. This step is the same as step 2 in clause 4.15.6.6. 3. This step is the same as steps 2-4 in clause 4.15.6.10. The NEF determines whether to invoke the TSCTSF or not, as described in step 3 in clause 4.15.6.6. If the NEF determines to invoke TSCTSF, steps 4-9 are executed and steps 10-12 are skipped. Otherwise steps 4-9 are skipped and steps 10-12 are executed. The procedure then continues in step 13. 4. This step is the same as step 3a in clause 4.15.6.6 with the difference that Internal Group ID or SUPI is provided instead of UE address. 5. The TSCTSF determines the individual group members using Nudm SDM Group Identifier translation service. The TSCTSF also determines which of these group members have active PDU Sessions matching the DNN/S-NSSAI and determines the relevant UE address. The TSCTSF manages the AF request QoS information targeting for a group as defined in TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 6. For each PDU Session, the TSCTSF invokes Npcf_PolicyAuthorization service. This step is the same as step 3b in clause 4.15.6.6. 7. The PCF replies to the TSCTSF. This step is the same as step 4a in clause 4.15.6.6. 8. The TSCTSF replies to the NEF. This step is the same as step 4b in clause 4.15.6.6. 9. This step is the same as step 6 in clause 4.15.6.6 with the difference that it is executed for all PDU Sessions identified in step 6 above. 10. If the NEF determines to not invoke the TSCTSF, the NEF uses the Nudr_DM service to store the information related to the Internal Group ID or SUPI in UDR. The information is stored as Application Data in UDR. If the AF requested for notifications of Resource allocation status or other events, the NEF includes the information required for reporting the event, including the Notification Target Address pointing to the NEF or AF and the Notification Correlation ID containing the AF Transaction Internal ID. 11. The UDR notifies the PCF(s) that have subscribed. 12. The PCF(s) identifies the active PDU Sessions associated with the data received from UDR. The PCF(s) manages the AF request QoS information targeting for a group as defined in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. 13. The NEF replies to the AF. This step is the same as step 8 in clause 4.15.6.6. 14. When an event condition is met, e.g. that the establishment of the transmission resources corresponding to the QoS update succeeded or failed, the PCF sends a notification to TSCTSF or NEF as applicable. This step is the same as steps 7-8 in clause 4.15.6.6. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.6.14 |
1,541 | 5.2.6.28.3 Nnef_ASTI_Update operation | Service operation name: Nnef_ASTI_Update Description: The consumer requests to update the 5G access stratum time distribution configuration, for which the NEF authorizes the request and invokes the corresponding service operation with TSCTSF (clause 5.2.27.4.3). Inputs, Required: As specified in clause 5.2.27.4.3. Inputs, Optional: As specified in clause 5.2.27.4.3. Outputs, Required: Operation execution result indication and in the case of successful operation, any outputs as specified in clause 5.2.27.4.3. Outputs, Optional: As specified in clause 5.2.27.4.3. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.6.28.3 |
1,542 | 9.9.3.35 UE radio capability information update needed | The purpose of the UE radio capability information update needed information element is to indicate whether the MME shall delete the stored UE radio capability information, if any. The UE radio capability information update needed information element is coded as shown in figure 9.9.3.35.1and table 9.9.3.35.1. The UE radio capability information update needed is a type 1 information element. Figure 9.9.3.35.1: UE radio capability information update needed information element Table 9.9.3.35.1: UE radio capability information update needed information element | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.9.3.35 |
1,543 | 16.1.4 CQI and MCS | For channel state reporting, a CQI table for target block error rate 10-5 is introduced. For scheduling data packets with higher reliability, 64QAM MCS tables containing entries with lower spectral efficiency are introduced for both downlink and uplink. The tables are different for CP-OFDM and DFT-s-OFDM. The MCS tables can be configured semi-statically or dynamically. The dynamic signalling of MCS table is supported by configuring UE with MCS-C-RNTI, where the scrambling of DCI CRC by MCS-C-RNTI indicates the 64QAM MCS tables with entries of lower spectral efficiency. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.1.4 |
1,544 | 5.5.1.1 Calling party charging | This applies to calling party pays in charged party principals defined in TS 22.115[ Service aspects; Charging and billing ] [101]. For subscription related chargeable events the charging information shall indicate the charged party is normally the calling party. It should be possible for multiple leg calls (e.g. forwarded, conference or roamed) to be charged to each party as if each leg was separately initiated. However, in certain types of call, the originating party may wish/be obliged to pay for other legs (e.g. may also pay for the MT leg.). It shall be possible to change the chargeable party at the call set-up. | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 5.5.1.1 |
1,545 | 6.4.5 Security mode set-up procedure | This section describes one common procedure for both ciphering and integrity protection set-up. It is mandatory to start integrity protection of signalling messages by use of this procedure at each new signalling connection establishment between MS and VLR/SGSN. The five exceptions when it is not mandatory to start integrity protection are: - If the only purpose with the signalling connection establishment and the only result is periodic location registration, i.e. no change of any registration information. - If there is no MS-VLR/SGSNsignalling after the initial L3 signalling message sent from MS to VLR/SGSN, i.e. in the case of deactivation indication sent from the MS followed by connection release. - If the only MS-VLR/SGSN signalling after the initial L3 signalling message sent from MS to VLR/SGSN, and possible user identity request and authentication (see below), is a reject signalling message followed by a connection release. However, it shall be mandatory for the VLR/SGSN to start integrity protection before sending a reject signalling message that causes the CSG list on the UE to be modified. - If the call is an emergency call teleservice as defined in TS 22.003[ Circuit Teleservices supported by a Public Land Mobile Network (PLMN) ] , see section 6.4.9.2 below. - If the PS connection establishment is for an emergency session, see clause 6.4.9.2 below. When the integrity protection shall be started, the only procedures between MS and VLR/SGSN that are allowed after the initial connection request (i.e. the initial Layer 3 message sent to VLR/SGSN) and before the security mode set-up procedure are the following: - Identification by a permanent identity (i.e. request for IMSI, IMEI or IMEISV), and - Authentication and key agreement. The message sequence flow below describes the information transfer at initial connection establishment, possible authentication and start of integrity protection and possible ciphering. Figure 14: Local authentication and connection set-up NOTE 1: The network must have the "UE security capability" information before the integrity protection can start, i.e. the "UE security capability" must be sent to the network in an unprotected message. Returning the "UE security capability" later on to the UE in a protected message will give UE the possibility to verify that it was the correct "UE security capability" that reached the network. Detailed description of the flow above: 1. RRC connection establishment includes the transfer from MS to RNC of the ME security capability optionally the GSM Classmarks 2 and 3 and the START values for the CS service domain respective the PS service domain. The UE security capability information includes the ciphering capabilities (UEAs) and the integrity capabilities (UIAs) of the MS. The START values and the UE security capability information are stored in the SRNC. If the GSM Clasmarks 2 and 3 are transmitted during the RRC Connection establishment, the RNC must store the GSM ciphering capability of the UE (see also message 7). 2. The MS sends the Initial L3 message (Location update request, CM service request, Routing area update request, attach request, paging response etc.) to the VLR/SGSN. This message contains e.g. the user identity and the KSI. The included KSI (Key Set Identifier) is the KSI allocated by the CS service domain or PS service domain at the last authentication for this CN domain. 3. User identity request may be performed (see 6.2). Authentication of the user and generation of new security keys (IK and CK) may be performed (see 6.3.3). A new KSI will then also be allocated. 4. The VLR/SGSN determines which UIAs and UEAs that are allowed to be used in order of preference. 5. The VLR/SGSN initiates integrity and ciphering by sending the RANAP message Security Mode Command to SRNC. This message contains an ordered list of allowed UIAs in order of preference, and the IK to be used. If ciphering shall be started, it contains the ordered list of allowed UEAs in order of preference, and the CK to be used. If a new authentication and security key generation has been performed (see 3 above), this shall be indicated in the message sent to the SRNC. The indication of new generated keys implies that the START value to be used shall be reset (i.e. set to zero) at start use of the new keys. Otherwise, it is the START value already available in the SRNC that shall be used (see 1. above). VLR/SGSN shall treat the keyset as "new" only if the authentication and security key generation was performed while in UTRAN, and the keyset has not been used for this UE in a previous successful RANAP Security Mode Control, BSSMAP Cipher Mode Control procedure or in a successful Handover/Relocation, otherwise the keyset shall be considered to be "old". 6. The SRNC decides which algorithms to use by selecting the highest preference algorithm from the list of allowed algorithms that matches any of the algorithms supported by the MS (see 6.4.2). The SRNC generates a random value FRESH and initiates the downlink integrity protection. If the requirements received in the Security mode command can not be fulfilled, the SRNC sends a SECURITY MODE REJECT message to the requesting VLR/SGSN. The further actions are described in 6.4.2. 7. The SRNC generates the RRC message Security mode command. The message includes the ME security capability, optionally the GSM ciphering capability (if received during RRC Connection establishment), the UIA and FRESH to be used and if ciphering shall be started also the UEA to be used. Additional information (start of ciphering) may also be included. Because of that the MS can have two ciphering and integrity key sets, the network must indicate which key set to use. This is obtained by including a CN type indicator information in the Security mode command message. Before sending this message to the MS, the SRNC generates the MAC-I (Message Authentication Code for Integrity) and attaches this information to the message. 8. At reception of the Security mode command message, the MS controls that the "UE security capability" received is equal to the "UE security capability" sent in the initial message. The same applies to the GSM ciphering capability if it was included in the RRC Connection Establishment. The MS computes XMAC-I on the message received by using the indicated UIA, COUNT-I generated from the stored START and the received FRESH parameter. The MS verifies the integrity of the message by comparing the received MAC-I with the generated XMAC-I. 9. If all controls are successful, the MS compiles the RRC message Security mode complete and generates the MAC-I for this message. If any control is not successful, the procedure ends in the MS. 10. At reception of the response message, the SRNC computes the XMAC-I on the message. The SRNC verifies the data integrity of the message by comparing the received MAC-I with the generated XMAC-I. 11. The transfer of the RANAP message Security Mode Complete response, including the selected algorithms, from SRNC to the VLR/SGSN ends the procedure. The Security mode command to MS starts the downlink integrity protection, i.e. this and all following downlink messages sent to the MS are integrity protected using the new integrity configuration. The Security mode complete from MS starts the uplink integrity protection, i.e. this and all following messages sent from the MS are integrity protected using the new integrity configuration. When ciphering shall be started, the Ciphering Activation time information that is exchanged between SRNC and MS during the Security mode set-up procedure sets the RLC Sequence Number/Connection Frame Number when to start ciphering in Downlink respective Uplink using the new ciphering configuration. Mechanisms are defined to allow networks to overcome early UE implementation faults [22]. A potential early UE implementation fault could be a faulty UEA1 implementation. To allow networks to handle early UEs which have faulty UEA1 implementations, the SGSN/VLR may configure the security mode command based on the UE’s IMEISV so that certain UEs which claim to support UEA1 shall have security established without ciphering (i.e. with UEA0), while other UEs which claim to support UEA1 shall have security established with ciphering (i.e. with UEA1). This procedure shall involve the SGSN/VLR retrieving the IMEISV from the UE before the security mode set-up procedure has started. If the above procedure to handle UEs which have faulty UEA1 implementations is implemented and the security mode set-up procedure results in security being established without ciphering (i.e. with UEA0) then the SGSN/VLR shall request the IMEISV from the UE for a second time immediately after the security mode set-up procedure has been completed. This second IMEISV request is integrity protected. If the IMEISV request is not successful, or if the second IMEISV received is different from the IMEISV received before the security mode set-up procedure was started then the connection shall be released. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 6.4.5 |
1,546 | 6.26.2.9 Service exposure | Based on MNO policy, the 5G network shall provide suitable APIs to allow a trusted third-party to create/remove a 5G LAN-VN. Based on MNO policy, the 5G network shall provide suitable APIs to allow a trusted third-party to manage a 5G LAN-VN dedicated for the usage by the trusted third-party, including the address allocation. Based on MNO policy, the 5G network shall provide suitable APIs to allow a trusted third-party to authorize/deauthorize UEs to access a specific 5G LAN-VN managed by the trusted third-party. Based on MNO policy, the 5G network shall provide suitable APIs to allow a trusted third-party to add/remove an authorized UE to/from a specific 5G LAN-VN managed by the trusted third-party. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.26.2.9 |
1,547 | 9.3.4.2.2 TDD | For the parameters specified in Table 9.3.4.2.2-1, and using the downlink physical channels specified in Annex C.3.2, the minimum requirements are specified in Table 9.3.4.2.2-2 and by the following a) the ratio of the throughput obtained when transmitting on subbands 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 subband in set S shall be ≥ ; The requirements only apply for subbands of full size and the random scheduling across the subbands is done by selecting a new subband 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 subband size. Table 9.3.4.2.2-1 Sub-band test for single antenna transmission (TDD) Table 9.3.4.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.3.4.2.2 |
1,548 | 4.11.0a.2 Interaction with PCC | When interworking with 5GS is supported and a "SMF+PGW-C" is selected for a PDN connection, policy interactions between PDN GW and PCRF specified in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13] are replaced by equivalent interactions between SMF+PGW-C and PCF as follows: - IP-CAN Session Establishment procedure defined in TS 23.203[ Policy and charging control architecture ] [24] is replaced by SM Policy Association Establishment Procedure as described in clause 4.16.4.The SMF+PGW-C includes the information elements received in Create Session Request message into the Npcf_SMPolicyControl_Create Service as follows: the SUPI contains the IMSI, the DNN contains the APN, the PEI contains either the IMEISV or IMEI, the Session AMBR contains the APN-AMBR and the default QoS information that contains the default EPS bearer QoS, note that QCI values are mapped into 5QI values. The SMF+PGW-C may receive PCC Rules and PDU Session Policy Information, 5G QoS information in the PCC Rule and in PDU Session Policy Information are mapped into EPS QoS information as defined in clause 4.11.1.1 and Annex C. - (PCEF-initiated) IP-CAN Session Modification procedure defined in TS 23.203[ Policy and charging control architecture ] [24] is replaced by SM Policy Association Modification procedure as described in clause 4.16.5.1. The Policy Control Request Triggers are specified in clause 6.1.3.5 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. - The SMF+PGW-C includes the QoS related information elements received in Modify Bearer Request or Modify Bearer Command message into the Npcf_SMPolicyControl_Update Service with the following modifications, the subscribed Session AMBR includes the subscribed APN-AMBR and subscribed default QoS information includes the default EPS bearer QoS, note that QCI values are mapped into 5QI values. The SMF+PGW-C may receive PCC Rules and PDU Session Policy Information, 5G QoS information in the PCC Rule and in PDU Session Policy Information are mapped into EPS QoS information as defined in clause 4.11.1.1 and Annex C. - The SMF+PGW-C includes the location related information received in Modify Bearer Request (as specified in clause 5.9.2 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13]) into Npcf_SMPolicyControl_Update if the corresponding Policy Control Request Triggers (i.e. Location change, Change of UE presence in Presence Reporting Area) are provisioned. - The SMF+PGW-C includes the information elements received in Delete Bearer Command message into the Npcf_SMPolicyControl_Update Service. - (PCRF-initiated) IP-CAN Session Modification procedure defined in TS 23.203[ Policy and charging control architecture ] [24] is replaced by SM Policy Association Modification procedure as described in clause 4.16.5.2. The SMF+PGW-C may receive PCC Rules and PDU Session Policy Information, 5G QoS information in the PCC Rule and in PDU Session Policy Information are mapped into EPS QoS information as defined in clause 4.11.1.1 and Annex C. - IP-CAN Session Termination procedure defined in TS 23.203[ Policy and charging control architecture ] [24] is replaced by SM Policy Association Termination procedure as described in clause 4.16.6. The SMF+PGW-C includes the information elements received in Delete Session Request message by the SMF+PGW-C into the Npcf_SMPolicyControl_Delete Service. URSP provisioning may be supported in EPS and the procedures are specified in clause 4.11.0a.2a. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.11.0a.2 |
1,549 | D.5 Support for keeping UE in CM-CONNECTED state in overlay network when accessing services via NWu | When UE is accessing the overlay network via the underlay network as described in clause D.3, it is possible to keep the UE in CM-CONNECTED state in the overlay network: - UE maintains at least one PDU Session in underlay network, from where the N3IWF of the overlay network is reachable via the DN of the PDU Session in underlay network. In this case, the UE is considered as successfully connected to the non-3GPP access of the overlay network, thus UE always attempts to transit to CM-CONNECTED state from CM-IDLE, as described in NOTE 3 in clause 5.5.2. - IKEv2 liveness check procedure initiated either by UE or N3IWF as defined in clause 7.8 and clause 7.9 of TS 24.502[ Access to the 3GPP 5G Core Network (5GCN) via non-3GPP access networks ] [48] can be utilized to ensure the signalling connection between UE and N3IWF is still valid when UE stays in CM-CONNECTED state. Adjusting the time interval of the liveness check to avoid the deletion of the IKEv2 SA due to inactivity, on both endpoints of the SA. - If NAT is used, so as to avoid a timeout of the NAT entries between the UPF in the underlay network and the N3IWF in the overlay network, NAT-Traversal mechanisms described in RFC 7296 [60] and NAT-Keepalive described in RFC 3948 [138] are recommended. - AMF in overlay network keeps the UE in CM-CONNECTED state unless UE or N3IWF triggers the release. - The NG-RAN node in the underlay network can use the existing information to decide an appropriate RRC state for the UE (e.g. whether release a UE to RRC_INACTIVE). | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | D.5 |
1,550 | 5.4.4 Scheduling Request | The Scheduling Request (SR) is used for requesting UL-SCH resources for new transmission. When an SR is triggered, it shall be considered as pending until it is cancelled. All pending SR(s) shall be cancelled and sr-ProhibitTimer and ssr-ProhibitTimer shall be stopped when a MAC PDU is assembled and this PDU includes a BSR which contains buffer status up to (and including) the last event that triggered a BSR (see clause 5.4.5), or, if all pending SR(s) are triggered by Sidelink BSR, when a MAC PDU is assembled and this PDU includes a Sidelink BSR which contains buffer status up to (and including) the last event that triggered a Sidelink BSR (see clause 5.14.1.4), or, if all pending SR(s) are triggered by Sidelink BSR, when upper layers configure autonomous resource selection, or when the UL grant(s) can accommodate all pending data available for transmission. If the MAC entity has resources for SR configured on only one of SPUCCH and PUCCH, that SR resource is valid for all logical channels. If the MAC entity has resources for SR configured on both PUCCH and SPUCCH, MAC entity shall consider all logical channels that have triggered an SR (and at retxBSR-Timer expiry, MAC entity shall consider all logical channels, belonging to a LCG, with data available for transmission): - PUCCH resources for SR are valid if logicalChannelSr-Restriction is not configured, or if logicalChannelSr-Restriction allows SR on PUCCH, for any of the logical channels; - SPUCCH resources for SR are valid if logicalChannelSr-Restriction is not configured, or if logicalChannelSr-Restriction allows SR on SPUCCH, for any of the logical channels. If an SR is triggered and there is no other SR pending, the MAC entity shall set the SR_COUNTER and the SSR_COUNTER to 0. As long as one SR is pending, the MAC entity shall for each TTI: - if no UL-SCH resources are available for a transmission in this TTI: - Except for NB-IoT: - if the MAC entity has no valid PUCCH nor valid SPUCCH resource for SR configured in any TTI: - if the MAC entity is a MCG MAC entity and rach-Skip is not configured; or - if the MAC entity is a SCG MAC entity and rach-SkipSCG is not configured: - initiate a Random Access procedure (see clause 5.1) on the corresponding SpCell and cancel all pending SRs; - else if this TTI is not part of a measurement gap or Sidelink Discovery Gap for Transmission, and if transmission of V2X sidelink communication is not prioritized in this TTI as described in clause 5.14.1.2.2: - if the MAC entity has at least one valid SPUCCH resource for SR configured for this TTI and if ssr-ProhibitTimer is not running: - if SSR_COUNTER < dssr-TransMax: - increment SSR_COUNTER by 1; - instruct the physical layer to signal the SR on one valid SPUCCH resource for SR; - start the ssr-ProhibitTimer. - else: - notify RRC to release SPUCCH for all serving cells; - if the MAC entity has no valid PUCCH resource for SR configured in any TTI: - notify RRC to release PUCCH for all serving cells; - notify RRC to release SRS for all serving cells; - clear any configured downlink assignments and uplink grants; - initiate a Random Access procedure (see clause 5.1) on the SpCell and cancel all pending SRs. - if the MAC entity has at least one valid PUCCH resource for SR configured for this TTI and if sr-ProhibitTimer is not running: - if SR_COUNTER < dsr-TransMax: - increment SR_COUNTER by 1; - instruct the physical layer to signal the SR on one valid PUCCH resource for SR; - start the sr-ProhibitTimer. - else: - notify RRC to release PUCCH and SPUCCH for all serving cells; - notify RRC to release SRS for all serving cells; - clear any configured downlink assignments and uplink grants; - initiate a Random Access procedure (see clause 5.1) on the SpCell and cancel all pending SRs. - For NB-IoT: - if the MAC entity has no valid resource for SR together with acknowledgement of the data in this TTI and no valid PRACH resource for SR configured in any TTI: - initiate a Random Access Procedure (see clause 5.1), and cancel all pending SRs in the first subframe containing PRACH for preamble transmission. - else: - if the MAC entity has valid resource for SR together with acknowledgement of the data in this TTI: - instruct the physical layer to signal the SR together with acknowledgement of the data. - cancel, if any, initiated Random Access Procedure for SR. - else: - if the MAC entity has valid PRACH resource for SR configured in this TTI and sr-ProhibitTimer is not running: - instruct the physical layer to signal the SR on one valid PRACH resource for SR. - start the sr-ProhibitTimer in the subframe containing the last repetition of the corresponding SR transmission. NOTE 1: The selection of which valid PUCCH/SPUCCH resource for SR to signal SR on when the MAC entity has more than one valid PUCCH/SPUCCH resource for SR in one TTI or overlapping TTIs is left to UE implementation. NOTE 2: SR_COUNTER is incremented for each SR bundle. sr-ProhibitTimer is started in the first TTI of an SR bundle. | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.4.4 |
1,551 | 7.2.1 Authentication for Untrusted non-3GPP Access | This clause specifies how a UE is authenticated to 5G network via an untrusted non-3GPP access network. It uses a vendor-specific EAP method called "EAP-5G", utilizing the "Expanded" EAP type and the existing 3GPP Vendor-Id, registered with IANA under the SMI Private Enterprise Code registry. The "EAP-5G" method is used between the UE and the N3IWF and is utilized for encapsulating NAS messages. If the UE needs to be authenticated by the 3GPP home network, any of the authentication methods as described in clause 6.1.3 can be used. The method is executed between the UE and AUSF as shown below. When possible, the UE shall be authenticated by reusing the existing UE NAS security context in AMF. Figure 7.2.1-1: Authentication for untrusted non-3GPP access 1. The UE connects to an untrusted non-3GPP access network with procedures outside the scope of 3GPP. When the UE decides to attach to 5GC network, the UE selects an N3IWF in a 5G PLMN, as described in TS 23.501[ System architecture for the 5G System (5GS) ] [2] clause 6.3.6. 2. The UE proceeds with the establishment of an IPsec Security Association (SA) with the selected N3IWF by initiating an IKE initial exchange according to RFC 7296 [25]. After step 2 all subsequent IKE messages are encrypted and integrity protected by using the IKE SA established in this step. 3. The UE shall initiate an IKE_AUTH exchange by sending an IKE_AUTH request message. The AUTH payload is not included in the IKE_AUTH request message, which indicates that the IKE_AUTH exchange shall use EAP signalling (in this case EAP-5G signalling). As per the RFC 7296 [25], in the IDi the UE shall set the ID type as ID_KEY-ID in this message and set its value equal to any random number. The UE shall not use its GUTI/SUCI/SUPI as the Id in this step. If the UE is provisioned with the N3IWF root certificate, it shall include the CERTREQ payload within the IKE_AUTH request message to request N3IWF’s certificate. 4. The N3IWF responds with an IKE_AUTH response message which includes the N3IWF identity, the AUTH payload to protect the previous message it sent to the UE (in the IKE_SA_INIT exchange) and an EAP-Request/5G-Start packet. The EAP-Request/5G-Start packet informs the UE to initiate an EAP-5G session, i.e. to start sending NAS messages encapsulated within EAP-5G packets. If the UE has sent a CERTREQ payload in step 3, the N3IWF shall also include the CERT payload including N3IWF certificate. 5. The UE shall validate the N3IWF certificate and shall confirm that the N3IWF identity matches the N3IWF selected by the UE. An absence of the certificate from the N3IWF if the UE had requested the certificate or unsuccessful identity confirmation shall result in a connection failure. The UE shall send an IKE_AUTH request which includes an EAP-Response/5G-NAS packet that contains a Registration Request message containing UE security capabilities and the SUCI. If UE is already with the 5GC over 3GPP access and there is an available security context, the UE shall integrity protect the Registration Request message and shall send the 5G-GUTI instead of SUCI. The N3IWF shall refrain from sending an EAP-Identity request. The UE may ignore an EAP Identity request or respond with the SUCI it sent in the Registration Request. If the UE has registered to the same AMF through 3GPP access, and if this is the first time that the UE connects to the 5GC through non-3GPP access, the value of corresponding UL NAS COUNT used for integrity protection is 0; else it can use the existing non-3GPP specific UL NAS COUNT for integrity protection NOTE: The N3IWF does not send an EAP-Identity request because the UE includes its identity in the IKE_AUTH request in message 5. This is in line with RFC 7296 [25], clause 3.16. 6. The N3IWF shall select an AMF as specified in TS 23.501[ System architecture for the 5G System (5GS) ] [2], clause 6.5.3. The N3IWF forwards the Registration Request received from the UE to the AMF. 7. If the AMF receives a 5G-GUTI and the Registration is integrity protected, it may use the security context to verify the integrity protection as describe in clause 6.4.6. If the UE has registered to the same AMF through 3GPP access, and if this is the first time that the AMF receives UE’s NAS signalling through non-3GPP access, the value of corresponding UL NAS COUNT used for integrity verification is 0; else it can use the existing non-3GPP specific UL NAS COUNT for integrity verification. If integrity is verified successfully, it indicates that UE is authenticated by AMF.If integrity is verified successfully and no newer security context has been activated over the 3GPP access, then step 8 to step 11 may be skipped. If integrity is verified successfully and a newer security context has been activated over the 3GPP access then authentication may be skipped but the AMF shall activate the newer context with a NAS SMC procedure as described in step 8 and onwards. Otherwise, the AMF shall authenticate the UE. If the AMF decides to authenticate the UE, it shall use one of the methods from clause 6.1.3. In this case, the AMF shall send a key request to the AUSF. The AUSF may initiate an authentication procedure as specified in clause 6.1.3. Between AMF and UE, the authentication packets are encapsulated within NAS authentication messages and the NAS authentication messages are carried in N2 signalling between the AMF and N3IWF, and then are encapsulated within EAP-5G/5G-NAS packets between the N3IWF and the UE. In the final authentication message from the home network, the AUSF shall send the anchor key KSEAF derived from KAUSF to the SEAF. The SEAF shall derive the KAMF from KSEAF and send it to the AMF which is used by the AMF to derive NAS security keys. If EAP-AKA' is used for authentication as described in clause 6.1.3.1, then the AUSF shall include the EAP-Success. The UE also derives the anchor key KSEAF and from that key it derives the KAMF followed by NAS security keys. The NAS COUNTs associated with NAS connection identifier "0x02" are set at the UE and AMF. 8. The AMF shall send a Security Mode Command (SMC) to the UE in order to activate NAS security associated with NAS connection identifier "0x02". This message is first sent to N3IWF (within an N2 message). If EAP-AKA' is used for authentication, the AMF shall encapsulate the EAP-Success received from AUSF within the SMC message. 9. The N3IWF shall forward the NAS SMC to UE within an EAP-Request/5G-NAS packet. 10. The UE completes the authentication (if initiated in step 7) and creates a NAS security context or activates another one based on the received ngKSI in the NAS SMC. UE shall respond to the NAS SMC it received from the AMF based on the selected algorithms and parameters as described in clause 6.7.2. The UE shall encapsulate the NAS SMC Complete in the EAP-5G Response. 11. The N3IWF shall forward the NAS packet containing NAS SMC Complete to the AMF over the N2 interface. 12. The AMF upon reception of the NAS SMC Complete from the UE or upon success of integrity protection verification, initiates the NGAP procedure to set up the AN context. AMF shall compute the N3IWF key, KN3IWF, using the uplink NAS COUNT associated with NAS connection identifier "0x02" as defined in Annex A.9 for the establishment of the IPsec SA between the UE and the N3IWF and shall include it in the NGAP Initial Context Setup Request sent to the N3IWF. 13. N3IWF sends an EAP-Success/EAP-5G to the UE upon reception of the NGAP Initial Context Setup Request containing the N3IWF key, KN3IWF. This completes the EAP-5G session and no further EAP-5G packets are exchanged. If the N3IWF does not receive the KN3IWF from AMF, the N3IWF shall respond with an EAP-Failure 14. The IPsec SA is established between the UE and N3IWF by using the N3IWF key KN3IWF that was created in the UE using the uplink NAS COUNT associated with NAS connection identifier "0x02" as defined in Annex A.9 and was received by N3IWF from the AMF in step 12. 15. Upon successful establishment of the IPsec SA between the UE and the N3IWF, the N3IWF shall send the NGAP Initial Context Setup Response message to the AMF. 15a. The AMF may determine whether the N3IWF is appropriate for the slice selected as defined in clause 4.12.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [8]. If it is compatible with the selected N3IWF, then proceed with step 16 and step 17. Otherwise, the AMF shall proceed with step 18 to step 20, and step 16 to 17 are skipped. Case a): 16. When NGAP Initial Context Setup Response for the UE is received by the AMF, AMF shall send the NAS Registration Accept message for the UE over the N2 towards the N3IWF. 17. Upon receiving the NAS Registration Accept message from the AMF, the N3IWF shall forward it to the UE over the established IPsec SA. All further NAS messages between the UE and the N3IWF shall be sent over the established IPsec SA. Case b): 18. The AMF may trigger the UE policy update procedure and update the UE policy as defined in step 15 and step 16 in clause 4.12.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [8]. 19. The AMF shall send a Registration Reject message via N3IWF to the UE as defined in step 17 in clause 4.12.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [8]. The Registration Reject message is ciphered and integrity protected, and a new 5G-GUTI is provided to the UE. 20. The UE shall decipher and verify the integrity of the Registration Reject message. If verification is successful, then the UE proceeds with step 18 in clause 4.12.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [8], and sends an integrity protected Registration request message to the AMF via a new selected N3IWF. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 7.2.1 |
1,552 | 10.5.7.4 GPRS Timer 2 | The purpose of the GPRS timer 2 information element is to specify GPRS specific timer values, e.g. for the timer T3302 or timer T3319. The GPRS timer 2 is a type 4 information element with 3 octets length. The GPRS timer 2 information element is coded as shown in figure 10.5.147/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.163/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.147/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : GPRS Timer 2 information element Table 10.5.163/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : GPRS Timer 2 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.7.4 |
1,553 | Annex D (normative): Interoperation with Gn/Gp SGSNs D.1 General Considerations | This annex specifies interworking between the EPS and 3GPP 2G and/or 3G SGSNs, which provide only Gn and Gp interfaces but no S3, S4 or S5/S8 interfaces, i.e. these Gn/Gp SGSNs provide no functionality that is introduced specifically for the EPS or for interoperation with the E-UTRAN. Interoperation scenarios for operating E-UTRAN with a PLMN maintaining Gn/Gp SGSNs are supported only with a GTP-based S5/S8. NOTE: PMIP-based S5/S8 may be used, but does not support handovers between the Gn/Gp SGSN and MME/S-GW. The S5/S8 interface for the Operator with Gn/Gp SGSNs will be GTP-based, but can be changed to PMIP-based S5/S8 when the Gn/Gp SGSNs evolve to S4 SGSNs. For these interoperation scenarios the GERAN/UTRAN has to support interoperation with E-UTRAN. TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [74] defines the Monitoring Events feature, and TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7] specifies that the Monitoring Events feature for the Gn/Gp SGSN is not supported. Therefore, during interoperation with Gn/Gp SGSNs Monitoring Event information shall not be expected by the MME/S4-SGSN from a Gn/Gp SGSN, nor shall the MME/S4-SGSN or the HSS transfer Monitoring Event information to a Gn/Gp SGSN. This applies to all operations defined in this annex. | 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 |
1,554 | 6.3.1 PDU session authentication and authorization procedure 6.3.1.1 General | The purpose of the PDU session authentication and authorization procedure is to enable the DN: a) to authenticate the upper layers of the UE, when establishing the PDU session; b) to authorize the upper layers of the UE, when establishing the PDU session; c) both of the above; or d) to re-authenticate the upper layers of the UE after establishment of the PDU session. The PDU session authentication and authorization procedure can be performed only during or after the UE-requested PDU session procedure establishing a non-emergency PDU session. The PDU session authentication and authorization procedure shall not be performed during or after the UE-requested PDU session establishment procedure establishing an emergency PDU session. The upper layers store the association between a DNN and corresponding credentials, if any, for the PDU session authentication and authorization. If the UE is registered for onboarding services in SNPN the SMF may initiate the PDU session authentication and authorization procedure based on local policy with a DCS as specified in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24] subclause I.9.2.4.1 or a DN-AAA server as specified in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24] subclause I.9.2.4.2. If the UE is registered for onboarding services in SNPN and the network initiates the PDU session authentication and authorization procedure, the UE shall use the default UE credentials for secondary authentication for the PDU session authentication and authorization procedure. The network authenticates the UE using the Extensible Authentication Protocol (EAP) as specified in IETF RFC 3748 [34]. EAP has defined four types of EAP messages: a) an EAP-request message; b) an EAP-response message; c) an EAP-success message; and d) an EAP-failure message. The EAP-request message is transported from the network to the UE using the PDU SESSION AUTHENTICATION COMMAND message of the PDU EAP message reliable transport procedure. The EAP-response message to the EAP-request message is transported from the UE to the network using the PDU SESSION AUTHENTICATION COMPLETE message of the PDU EAP message reliable transport procedure. If the PDU session authentication and authorization procedure is performed during the UE-requested PDU session establishment procedure: a) and the DN authentication of the UE completes successfully, the EAP-success message is transported from the network to the UE as part of the UE-requested PDU session establishment procedure in the PDU SESSION ESTABLISHMENT ACCEPT message. b) and the DN authentication of the UE completes unsuccessfully, the EAP-failure message is transported from the network to the UE as part of the UE-requested PDU session establishment procedure in the PDU SESSION ESTABLISHMENT REJECT message. If the PDU session authentication and authorization procedure is performed after the UE-requested PDU session establishment procedure: a) and the DN authentication of the UE completes successfully, the EAP-success message is transported from the network to the UE using the PDU SESSION AUTHENTICATION RESULT message of the PDU EAP result message transport procedure. b) and the DN authentication of the UE completes unsuccessfully, the EAP-failure message is transported from the network to the UE using the PDU SESSION RELEASE COMMAND message of the network-requested PDU session release procedure. There can be several rounds of exchange of an EAP-request message and a related EAP-response message for the DN to complete the authentication and authorization of the request for a PDU session (see example in figure 6.3.1.1). The SMF shall set the authenticator retransmission timer specified in IETF RFC 3748 [34] subclause 4.3 to infinite value. NOTE: The PDU session authentication and authorization procedure provides a reliable transport of EAP messages and therefore retransmissions at the EAP layer of the SMF do not occur. Figure 6.3.1.1: PDU session authentication and authorization procedure | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.3.1 |
1,555 | A.2 KAUSF derivation function | This clause applies to 5G AKA only. When deriving a KAUSF from CK, IK and the serving network name when producing authentication vectors, and when the UE computes KAUSF during 5G AKA, the following parameters shall be used to form the input S to the KDF: - FC = 0x6A; - P0 = serving network name; - L0 = length of the serving network name (variable length as specified in 24.501 [35]); - P1 = SQN AK, - L1 = length of SQN AK (i.e. 0x00 0x06). The XOR of the Sequence Number (SQN) and the Anonymity Key (AK) is sent to the UE as a part of the Authentication Token (AUTN), see TS 33.102[ 3G security; Security architecture ] . If AK is not used, AK shall be treated in accordance with TS 33.102[ 3G security; Security architecture ] , i.e. as 000…0. The serving network name shall be constructed as specified in clause 6.1.1.4. The input key KEY shall be equal to the concatenation CK || IK of CK and IK. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | A.2 |
1,556 | 9.13.1.2.2 TDD | The following requirements apply to UE Category 8 and DL Category 14, 17~20, ≥22. For the parameters specified in table 9.13.1.2.2-1, and using the downlink physical channels specified in tables C.3.2-1 and C.3.2-2, the reported offset level of the wideband spatial differential CQI for codeword #1 (Table 7.2-2 in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [6]) shall be used to determine the wideband CQI index for codeword #1 as wideband CQI1 = wideband CQI0 – Codeword 1 offset level The wideband CQI1 shall be within the set {median CQI1 -1, median CQI1, median CQI1 +1} for more than 90% of the time, where the resulting wideband values CQI1 shall be used to determine the median CQI values for codeword #1. For both codewords #0 and #1, the PDSCH BLER using the transport format indicated by the respective median CQI0 – 1 and median CQI1 – 1 shall be less than or equal to 0.1. Furthermore, for both codewords #0 and #1, the PDSCH BLER using the transport format indicated by the respective median CQI0 + 1 and median CQI1 + 1 shall be greater than or equal to 0.1. Table 9.13.1.2.2-1: PUCCH 1-1 static test 4x8 (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.13.1.2.2 |
1,557 | 5.5.4 Authentication and key agreement procedure for 5G ProSe UE-to-network relay and 5G ProSe UE-to-UE relay 5.5.4.1 General | The purpose of the authentication and key agreement procedure: a) for 5G ProSe UE-to-network relay, is to perform the authentication for 5G ProSe remote UE initiated by the 5G ProSe UE-to-network relay UE and to agree on the KAUSF_P and KNR_ProSe when the security for 5G ProSe communication via 5G ProSe UE-to-network relay is performed over control plane as specified in 3GPP TS 33.503[ Security Aspects of Proximity based Services (ProSe) in the 5G System (5GS) ] [56]; or b) for 5G ProSe UE-to-UE relay, is to perform the authentication for 5G ProSe end UE initiated by the 5G ProSe UE-to-UE relay UE and to agree on the KAUSF_P and KNR_ProSe when the security for 5G ProSe communication via 5G ProSe UE-to-UE relay is performed over control plane as specified in 3GPP TS 33.503[ Security Aspects of Proximity based Services (ProSe) in the 5G System (5GS) ] [56]. The procedure as shown in figure 5.5.4.1.1 is initiated by the UE when the UE receives the ProSe direct link establishment request including the SUCI or the CP-PRUK ID of: a) the 5G ProSe remote UE from the 5G ProSe remote UE; or b) the 5G ProSe end UE from the 5G ProSe end UE, for establishing secure PC5 unicast link as specified in 3GPP TS 24.554[ Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3 ] [19E]. If the network decides to process the relay key request message, the EAP based authentication and key agreement procedure is initiated and controlled by the network. The exchanges of EAP messages between: a) the 5G ProSe remote UE and the network; or b) the 5G ProSe end UE and the network, are relayed by the UE. Figure 5.5.4.1.1: Authentication and key agreement procedure for 5G ProSe UE-to-network relay and 5G ProSe UE-to-UE relay | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.4 |
1,558 | 8.96 H(e)NB Information Reporting | H(e)NB number Information Reporting is coded as depicted in Figure 8.96-1. Figure 8.96-1: H(e)NB Information Reporting The following bits within Octet 5 shall indicate: - Bit 1 – FTI: When set to "1", shall indicate to start reporting H(e)NB local IP address and UDP port number information change when the UE moves from (e)NB to H(e)NB, from H(e)NB to another H(e)NB with a fixed network backhaul change, or from H(e)NB to (e)NB. The bit 1 shall be set to 0 to stop reporting H(e)NB local IP address and UDP port number information change. | 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.96 |
1,559 | 5.3.12 Extended idle-mode DRX cycle | The UE may request the use of extended idle-mode DRX cycle (eDRX) during an attach or tracking area updating procedure by including the extended DRX parameters IE (see 3GPP TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [11A] and 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10]). The UE shall not request the use of eDRX during: - an attach for emergency bearer services procedure; - a tracking area updating procedure for the UE attached for emergency bearer services; or - an attach for access to RLOS. The UE and the network may negotiate eDRX parameters during a tracking area updating procedure when the UE has a PDN connection for emergency bearer services. The network accepts the request to use the eDRX by providing the extended DRX parameters IE when accepting the attach or the tracking area updating procedure. The UE shall use eDRX only if it received the extended DRX parameters IE during the last attach or tracking area updating procedure and the UE does not have a PDN connection for emergency bearer services. NOTE: If the UE wants to keep using eDRX, the UE includes the extended DRX parameters IE in each attach or tracking area updating procedure. If the UE received the extended DRX parameters IE during the last attach or tracking area updating procedure, upon successful completion of the PDN disconnect procedure of the PDN connection for emergency bearer services or EPS bearer context deactivation procedure of the EPS bearer context for emergency, the UE shall resume eDRX. If the network has provided the extended DRX parameters IE during the last attach or tracking area updating procedure, upon successful completion of the PDN disconnect procedure of the PDN connection for emergency bearer services or EPS bearer context deactivation procedure of the EPS bearer context for emergency, the network shall resume eDRX. If the UE or the network locally releases the PDN connection for emergency bearer service, the UE or the network shall not use eDRX until the UE receives eDRX parameters during a tracking area updating procedure with EPS bearer context synchronization or upon successful completion of a service request procedure. If the UE did not receive the extended eDRX parameters IE, or if the UE has a PDN connection for emergency bearer services, the UE shall use the stored UE specific DRX parameter, if available. If the network did not accept the request to use eDRX, or if the UE has a PDN connection for emergency bearer services, the network shall use the stored UE specific DRX parameter, if available. If the network provided the extended DRX parameters IE and also assigned a new GUTI for the UE as described in clause 5.5.3.2.4 during the last tracking area updating procedure, the network shall use the stored UE specific DRX parameter, if available, with the old GUTI and use the eDRX provided by the network with the new GUTI until the old GUTI can be considered as invalid by the network (see clause 5.4.1.4). | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.3.12 |
1,560 | 5.30.3.3 UE configuration, subscription aspects and storage | To use CAG, the UE, that supports CAG as indicated as part of the UE 5GMM Core Network Capability, may be pre-configured or (re)configured with the following CAG information, included in the subscription as part of the Mobility Restrictions: - an Allowed CAG list i.e. a list of CAG Identifiers the UE is allowed to access; and - each entry of the Allowed CAG list may be associated with time validity information; and - optionally, a CAG-only indication whether the UE is only allowed to access 5GS via CAG cells (see TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [50] for how the UE identifies whether a cell is a CAG cell); The HPLMN may configure or re-configure a UE with the above CAG information using the UE Configuration Update procedure for access and mobility management related parameters described in clause 4.2.4.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. The above CAG information is provided by the HPLMN on a per PLMN basis. In a PLMN the UE shall only consider the CAG information provided for this PLMN. The entries of the Allowed CAG list with validity condition are provided to the UE only if the UE indicates support of CAG with validity information. NOTE 1: If the UE supports CAG but not CAG with validity information and there are entries of the Allowed CAG list that are associated with validity information in the subscription data, the CAG Identifier of the corresponding entry in subscription data can be provided to the UE without validity information when the validity condition is evaluated as true and removed when the evaluation changes to false. It is up to AMF local policy whether to provide such CAG Identifier to the UE. In case the AMF does not support CAG with validity information e.g. in the case of roaming, the UDM provides CAG information to the AMF without entries including validity information. When the subscribed CAG information changes, UDM sets a CAG information Subscription Change Indication and sends it to the AMF. The AMF shall provide the UE with the CAG information when the UDM indicates that the CAG information within the Access and Mobility Subscription data has been changed. When AMF receives the indication from the UDM that the CAG information within the Access and Mobility Subscription has changed, the AMF uses the CAG information received from the UDM to update the UE. Once the AMF updates the UE and obtains an acknowledgment from the UE, the AMF informs the UDM that the update was successful and the UDM clears the CAG information Subscription Change Indication flag. The AMF may update the UE using either the UE Configuration Update procedure after registration procedure is completed, or by including the new CAG information in the Registration Accept or in the Registration Reject or in the Deregistration Request or in the Service Reject. When the UE is roaming and the Serving PLMN provides CAG information, the UE shall update only the CAG information provided for the Serving PLMN while the stored CAG information for other PLMNs are not updated. When the UE is not roaming and the HPLMN provides CAG information, the UE shall update the CAG information stored in the UE with the received CAG information for all the PLMNs. The UE shall store the latest available CAG information for every PLMN for which it is provided and keep it stored when the UE is de-registered or switched off, as described in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]. The CAG information is only applicable with 5GS. NOTE 2: CAG information has no implication on whether and how the UE accesses 5GS over non-3GPP access. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.30.3.3 |
1,561 | 5.18.2 Broadcast system information for network sharing | If a shared NG-RAN is configured to indicate available networks (PLMNs and/or SNPNs) for selection by UEs, each cell in the shared radio access network shall in the broadcast system information include available core network operators in the shared network. The Broadcast System Information broadcasts a set of PLMN IDs and/or PLMN IDs and NIDs and one or more additional set of parameters per PLMN e.g. cell-ID, Tracking Areas, CAG Identifiers. All 5G System capable UEs that connect to NG-RAN support reception of multiple PLMN IDs and per PLMN specific parameters. All SNPN-enabled UEs support reception of multiple combinations of PLMN ID and NID and SNPN-specific parameters. The available core network operators (PLMNs and/or SNPNs) shall be the same for all cells of a Tracking Area in a shared NG-RAN network. UEs not set to operate in SNPN access mode decode the broadcast system information and take the information concerning available PLMN IDs into account in PLMN and cell (re-)selection procedures. UEs set to operate in SNPN access mode decode the broadcast system information and take the information concerning available PLMN IDs and NIDs into account in network and cell (re-)selection procedures. Broadcast system information is specified in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [28] for NR, TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [51] for E-UTRA and related UE access stratum idle mode procedures in TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [50] for NR and TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [52] for E-UTRA. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.18.2 |
1,562 | 2.3 Allocation and assignment principles | IMSI shall consist of decimal digits (0 through 9) only. The number of digits in IMSI shall not exceed 15. The allocation and assignment of Mobile Country Codes (MCCs) is administered by the ITU. The current assignment is available on ITU web site (https://www.itu.int/en/ITU-T/inr/Pages/default.aspx). The assignment of Mobile network Codes (MNC) is the responsibility of each national numbering plan administrator. MNCs under MCC ranges 90x are administered by the ITU. The MSIN is the third field of the IMSI, and is administered by the relevant MNC assignee to identify individual subscriptions. If more than one PLMN exists in a country, the same Mobile Network Code should not be assigned to more than one PLMN. The allocation of IMSIs should be such that not more than the digits MCC + MNC of the IMSI have to be analysed in a foreign PLMN for information transfer. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 2.3 |
1,563 | 4.22.10.3 UE or network requested MA PDU Session Release (home-routed roaming) | The signalling flow for a MA PDU Session Release when the UE is registered to the same VPLMN over 3GPP access and non-3GPP access and the PDU Session Anchor (PSA) is located in the HPLMN, is based on the signalling flow in Figure 4.3.4.3-1 with the following differences and clarifications: - In step 1, if the V-AMF needs to release the MA PDU Session over a single access, the V-AMF may invoke the Nsmf_PDUSession_UpdateSMContext service operation to request the release of the MA PDU Session over a single access. In this case, the AMF shall include in which access the MA PDU Session should be released. The V-SMF invokes Nsmf_PDUSession_Update service operation to request the release of the MA PDU Session over a single access. The V-SMF shall include in which access the MA PDU Session should be released. NOTE: When the H-SMF received the release request from the V-SMF, the H-SMF decides whether the MA PDU Session is released or released over a single access based on its local policy. - In step 1, if the V-AMF needs to release the MA PDU Session (e.g. locally released when the UE is CM-IDLE), the AMF invokes the Nsmf_PDUSession_ReleaseSMContext service operation to request the release of the MA PDU Session. The V-SMF invokes Nsmf_PDUSession_Release service operation to request the release of the MA PDU Session. - In steps 2a-2b, if the SMF releases the MA PDU Session over a single access, these steps are the same as steps 2a-2b in clause 4.22.10.2. - In step 3a, the H-SMF invokes Nsmf_PDUSession_Update service operation towards the V-SMF to release the MA PDU session over a single access (either 3GPP access or non-3GPP access) or both accesses. - In step 5, the V-SMF sends the PDU Session Release Command message to release the MA PDU session over a single access (either 3GPP access or non-3GPP access) or both accesses. - In step 5, if the V-SMF releases the MA PDU Session over a single Access Network, the V-SMF shall not include "skip indicator" in the Namf_Communication_N1N2MessageTransfer service. - In step 5, if the V-SMF releases the MA PDU Session over both accesses and user plane resources are established in both accesses, the V-SMF includes both N1 SM container (PDU Session Release Command) and N2 SM Resource Release request together in the Nsmf_PDUSession_UpdateSMContext or Namf_Communication_N1N2MessageTransfer service so that the UE does not request to activate user plane resources. The V-SMF releases user plane resources of the other access by including N2 SM Resource Release only in Namf_Communication_N1N2MessageTransfer service. - In step 5, when the V-SMF provides N1 SM container and/or N2 SM information, the V-SMF includes access type in the Namf_Communication_N1N2MessageTransfer to provide routing information to the V-AMF. - In step 16, the H-SMF triggers Nsmf_PDUSession_StatusNotify service only when the MA PDU Session is released in both accesses. The V-SMF triggers Nsmf_PDUSession_SMContextStatusNotify service only when the MA PDU Session is released in both accesses. The signalling flow for a MA PDU Session Release when the UE is registered to the different PLMNs over 3GPP access and non-3GPP access and the PDU Session Anchor (PSA) is located in the HPLMN, is based on the above procedure with the following differences and clarifications: - In step 1a, the (V-)AMF can trigger the MA PDU session release over a single access or over both accesses as described in step 1 of clause 4.22.10.2. - In step 3a, the H-SMF invokes Nsmf_PDUSession_Update service operation towards the V-SMF to release the MA PDU Session over a single access (either 3GPP access or non-3GPP access) or both accesses. If the UE is registered to the HPLMN via an access and the H-SMF releases MA PDU Session over the access, the H-SMF invokes Namf_Communication_N1N2MessageTransfer. - In step 5, the V-SMF releases the MA PDU Session over the access the H-SMF indicated in step 3a. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.22.10.3 |
1,564 | 5.7.1.2 QoS Profile | A QoS Flow may either be 'GBR' or 'Non-GBR' depending on its QoS profile. The QoS profile of a QoS Flow is sent to the (R)AN and it contains QoS parameters as described below (details of QoS parameters are described in clause 5.7.2): - For each QoS Flow, the QoS profile shall include the QoS parameters: - 5G QoS Identifier (5QI); and - Allocation and Retention Priority (ARP). - For each QoS Flow, the QoS profile may also include the QoS parameters: - PDU Set QoS Parameters (described in clause 5.7.7). - For each Non-GBR QoS Flow only, the QoS profile may also include the QoS parameter: - Reflective QoS Attribute (RQA). - For each GBR QoS Flow only, the QoS profile shall also include the QoS parameters: - Guaranteed Flow Bit Rate (GFBR) - UL and DL; and - Maximum Flow Bit Rate (MFBR) - UL and DL; and - In the case of a GBR QoS Flow only, the QoS profile may also include one or more of the QoS parameters: - Notification control; - Maximum Packet Loss Rate - UL and DL. NOTE: In this Release of the specification, the Maximum Packet Loss Rate (UL, DL) is only provided for a GBR QoS Flow belonging to voice media. Each QoS profile has one corresponding QoS Flow identifier (QFI) which is not included in the QoS profile itself. The usage of a dynamically assigned 5QI for a QoS Flow requires in addition the signalling of the complete 5G QoS characteristics (described in clause 5.7.3) as part of the QoS profile. When a standardized or pre-configured 5QI is used for a QoS Flow, some of the 5G QoS characteristics may be signalled as part of the QoS profile (as described in clause 5.7.3). | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.7.1.2 |
1,565 | 9.2.2.1 FDD | The following requirements apply to UE Category ≥2. For the parameters specified in table 9.2.2.1-1, and using the downlink physical channels specified in tables C.3.2-1 and C.3.2-2, the reported offset level of the wideband spatial differential CQI for codeword #1 (Table 7.2-2 in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [6]) shall be used to determine the wideband CQI index for codeword #1 as wideband CQI1 = wideband CQI0 – Codeword 1 offset level The wideband CQI1 shall be within the set {median CQI1 -1, median CQI1, median CQI1 +1} for more than 90% of the time, where the resulting wideband values CQI1 shall be used to determine the median CQI values for codeword #1. For both codewords #0 and #1, the PDSCH BLER using the transport format indicated by the respective median CQI0 – 1 and median CQI1 – 1 shall be less than or equal to 0.1. Furthermore, for both codewords #0 and #1, the PDSCH BLER using the transport format indicated by the respective median CQI0 + 1 and median CQI1 + 1 shall be greater than or equal to 0.1. Table 9.2.2.1-1: PUCCH 1-1 static test (FDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.2.2.1 |
1,566 | 5.3.3.4 Support of a UE connected over both 3GPP and Non-3GPP access | The AMF manages two CM states for an UE: a CM state for 3GPP access and a CM state for Non-3GPP access. An N2 interface can serve the UE for either 3GPP access or for Non 3GPP access. UE connected over both 3GPP and Non-3GPP has got two N2 interfaces, one for each access. A UE may be in any combination of the CM states between 3GPP and Non-3GPP access, e.g. a UE may be CM-IDLE for one access and CM-CONNECTED for the other access, CM-IDLE for both accesses or CM-CONNECTED for both accesses. When the UE CM state in the AMF is CM-IDLE for 3GPP access and CM-CONNECTED for Non-3GPP access, the AMF shall perform a network triggered Service Request procedure, when it has downlink data to be sent to this UE for 3GPP access, by sending either the Paging Request via 3GPP access or the NAS notification via Non-3GPP access to this UE (see clause 4.2.3.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]). Connection Management over Non-3GPP access is further defined in clause 5.5.2. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.3.3.4 |
1,567 | D.2 GTP-C interfaces not supporting Overload Control | Overload Control has been designed as a generic mechanism possibly applicable to any GTP-C based interface and any direction. However for the reasons clarified below, in the current release, Overload Control is not supported for the following GTP-C based interfaces: - S3, S10, S16 (see considerations below, to minimize impact to MME and S4-SGSN); - most of the S3 traffic would remain internal to the combo-node with the deployment of combo-MME/S4-SGSN nodes. The traffic over S10/S16 is also reduced with the deployment of MME and SGSN pools. It is therefore not essential to throttle the traffic on these interfaces when an MME or S4-SGSN experiences overload; - throttling signalling on these interfaces resulting from a user's mobility (inter-MME/S4-SGSN TAU, RAU and Handover) would result in bad end user's perception (handover failure, loss of PDN connections) and so needs to be avoided as far as possible; - an MME or S4-SGSN in overload may drop locally incoming RIM messages without causing GTP-C retransmissions (although this may cause the RAN to retransmit the message). - S11/S4 (from an MME/S4-SGSN to an SGW, with SGW as consumer; see consideration below); - by allowing the SGW to throttle DDN requests for normal priority traffic, the overload control of the messages originated by the SGW towards the MME/S4-SGSN is covered and hence, an SGW performing overload control towards the MME/S4-SGSN using Overload Control Information would be redundant. - S5/S8 (from a PGW to an SGW, with the SGW as a consumer; no signalling message, originated by the SGW towards the PGW, that is identified as requiring overload control); - Sm, Sn (no overload scenario identified, limited GTP-C traffic, to avoid impact to the MBMS GW); - Sv (no overload scenario identified, to avoid impact to the legacy CS products); - S101, S121 (no overload scenario identified, to avoid impact to the legacy HRPD products); - Gn/Gp (to avoid impact to the legacy Gn-SGSN/GGSN products and GTPv1-C protocol); | 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 | D.2 |
1,568 | 5.7.2.1 5QI | A 5QI is a scalar that is used as a reference to 5G QoS characteristics defined in clause 5.7.4, i.e. access node-specific parameters that control QoS forwarding treatment for the QoS Flow (e.g. scheduling weights, admission thresholds, queue management thresholds, link layer protocol configuration, etc.). Standardized 5QI values have one-to-one mapping to a standardized combination of 5G QoS characteristics as specified in Table 5.7.4-1. The 5G QoS characteristics for pre-configured 5QI values are pre-configured in the AN. Standardized or pre-configured 5G QoS characteristics, are indicated through the 5QI value, and are not signalled on any interface, unless certain 5G QoS characteristics are modified as specified in clauses 5.7.3.3, 5.7.3.4, 5.7.3.6, and 5.7.3.7. The 5G QoS characteristics for QoS Flows with dynamically assigned 5QI are signalled as part of the QoS profile. NOTE: On N3, each PDU (i.e. in the tunnel used for the PDU Session) is associated with one 5QI via the QFI carried in the encapsulation header. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.7.2.1 |
1,569 | 5.19.1 NAS Message Redirection Procedure | When DCNs are used, these steps are used to reroute a NAS message (and thereby a UE) from one CN node to another CN node during Attach, TAU or RAU procedure. These steps are also used by the MME/SGSN or HSS initiated Dedicated Core Network Reselection procedure in clause 5.19.3. Figure 5.19.1-1: NAS Message Redirection Procedure The procedure is started when a first new MME/SGSN decides to move the handling of an Attach Request, TAU Request or RAU Request to another CN node. 1. The first new MME/SGSN sends a Reroute NAS Message Request (original RAN message, reroute parameters, Additional GUTI/P-TMSI, UE Usage Type, and optionally the IMSI) to the RAN Node. The reroute parameter is a MMEGI (for E-UTRAN) or Null-NRI/SGSN Group ID (for UTRAN/GERAN) corresponding to the DCN that corresponds to the UE Usage Type. A UE provided Additional GUTI/P-TMSI (if available) from the NAS Request message is included. The MME/SGSN may determine the MMEGI or Null-NRI/SGSN Group ID corresponding to the DCN using DNS procedures. The original RAN message is the complete PDU received from the RAN which contains the original NAS Request message and all RAN IEs. The UE Usage Type shall be included, if available. For the condition to include the IMSI, see step 6 in clause 5.19.2. 2. The RAN node's NNSF selects a new MME/SGSN based on the MMEGI or Null-NRI/SGSN Group ID and possibly also based on an Additional GUTI/P-TMSI. If Additional GUTI/P-TMSI identifies an MME/SGSN within the set of valid nodes identified by MMEGI or Null-NRI/SGSN Group ID, it should be the selected node. Otherwise a valid CN node corresponding to the MMEGI or Null-NRI/SGSN Group ID will be selected. If no valid MME/SGSN is available within the set of valid nodes identified by MMEGI or Null-NRI/SGSN Group ID, the RAN node selects an MME/SGSN from the default DCN or selects the MME/SGSN that sent the Reroute Request, based on operator configuration. The MME/SGSN is selected from the network corresponding to the selected CN operator. 3. Dependent on RAT, the eNodeB/RNC sends the Initial UE message to the selected MME/SGSN or the BSC sends the UL-Unitdata message to the selected SGSN. The initial UE message/UL-Unitdata message includes the NAS Request message, the MMEGI or Null-NRI/SGSN Group ID, UE Usage Type and the IMSI if received from the first SGSN/MME in step 1. The MMEGI or Null-NRI/SGSN Group ID indicates that the message is a rerouted message and the second new MME/SGSN shall not reroute the NAS message. The UE Usage Type shall be included if received in the Reroute NAS Message Request to be used by the second new MME/SGSN to select SGW and PDN GW (see clauses 4.3.8.1 and 4.3.8.2). | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.19.1 |
1,570 | 8.11.1.2.3 Transmit diversity performance (Cell-Specific Reference Symbols) | 8.11.1.2.3.1 Minimum Requirement 2 Tx Antenna Port supporting narrowband transmission The requirements are specified in Table 8.11.1.2.3.1-2, with the addition of the parameters in Table 8.11.1.2.3.1-1 and Table 8.11.1.2.3.1-1a, and the downlink physical channel setup according to Annex C.3.2. The purpose is to verify the performance of transmit diversity (SFBC) with 2 transmitter antennas. Table 8.11.1.2.3.1-1: Test Parameters for Transmit diversity performance (FRC) Table 8.11.1.2.3.1-1a: Test Parameters for Transmit diversity performance (FRC) Table 8.11.1.2.3.1-2: Minimum performance Transmit Diversity (FRC) 8.11.1.2.3.2 Minimum Requirement 2 Tx Antenna Port supporting wideband transmission The requirements are specified in Table 8.11.1.2.3.2-2, with the addition of the parameters in Table 8.11.1.2.3.2-1 and the downlink physical channel setup according to Annex C.3.2. The purpose is to verify the performance of transmit diversity (SFBC) with 2 transmitter antennas. Table 8.11.1.2.3.2-1: Test Parameters for Transmit diversity performance (FRC) Table 8.11.1.2.3.2-2: Minimum performance Transmit Diversity (FRC) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.11.1.2.3 |
1,571 | 8.79 CSG Membership Indication (CMI) | CSG Membership Indication is coded as depicted in Figure 8.79-1. Figure 8.79-1: CSG Membership Indication Table 8.79-1: void CSG Membership Indication (CMI) values are specified in Table 8.79-2. Table 8.79-2: CSG Membership indication (CMI) NOTE: Due to a specification oversight, the CMI values in the above table are reversed from the values of the CSG-Membership-Indication AVP in 3GPP TS 32.299[ Telecommunication management; Charging management; Diameter charging applications ] [54], as well as from the values of the CMI in the UCI IE (see clause 8.75). Therefore, when the above CMI values are sent over the charging interface, the values are encoded as specified in 3GPP TS 32.299[ Telecommunication management; Charging management; Diameter charging applications ] [54]. | 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.79 |
1,572 | 6.2.3 PDU session management | The SMF is responsible for the session management functions to provide the PDU connectivity service to the UE via the 5GSM signalling between UE and SMF. The session management procedures includes: a) the UE-requested PDU session establishment procedure; b) the PDU session authentication and authorization procedure; c) the UE-requested PDU session modification procedure; d) the network-requested PDU session modification procedure; e) the UE-requested PDU session release procedure; and f) the network-requested PDU session release procedure. A UE may establish multiple PDU sessions, to the same data network or to different data networks, via 3GPP access and via non-3GPP access at the same time. It is not required for a UE to initiate the PDU session release procedure to release a PDU session associated with another access, if any, due to the reason that the UE initiates the registration procedure or PDU session establishment procedure over the current access. NOTE: PDU session is managed independently between 3GPP access and non-3GPP access. The session management messages between UE and SMF are transferred via AMF as specified in subclause 8.3. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.2.3 |
1,573 | 5.10 Semi-Persistent Scheduling | Except for NB-IoT, multiple UL Semi-Persistent Scheduling configurations are supported per Serving Cell. For NB-IoT, UL Semi-Persistent Scheduling configuration is only supported for BSR per Serving Cell. On one Serving Cell, multiple UL configurations can be active simultaneously only for the same TTI length. Multiple UL/DL configurations can also be active simultaneously on different Serving Cells. When Semi-Persistent Scheduling is enabled by RRC, the following information is provided, as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]: - Semi-Persistent Scheduling C-RNTI or UL Semi-Persistent Scheduling V-RNTI; - Uplink Semi-Persistent Scheduling interval semiPersistSchedIntervalUL if short TTI in UL for the SpCell is not configured or semiPersistSchedIntervalUL-sTTI in UL for the SpCell if short TTI is configured and number of empty transmissions before implicit release implicitReleaseAfter, if Semi-Persistent Scheduling with Semi-Persistent Scheduling C-RNTI is enabled for the uplink; - Uplink Semi-Persistent Scheduling interval semiPersistSchedIntervalUL and number of empty transmissions before implicit release implicitReleaseAfter for each SPS configuration, if Semi-Persistent Scheduling with UL Semi-Persistent Scheduling V-RNTI is enabled for the uplink; - Whether twoIntervalsConfig is enabled or disabled for uplink, only for TDD; - Downlink Semi-Persistent Scheduling interval semiPersistSchedIntervalDL if short TTI in DL for the SpCell is not configured or semiPersistSchedIntervalDL-sTTI if short TTI in DL for the SpCell is configured and number of configured HARQ processes for Semi-Persistent Scheduling numberOfConfSPS-Processes, if Semi-Persistent Scheduling is enabled for the downlink; - sTTIStartTimeDl if short TTI in DL for the SpCell is configured and sTTIStartTimeUl if short TTI in UL for the SpCell is configured; When Semi-Persistent Scheduling for uplink or downlink is disabled by RRC, the corresponding configured grant or configured assignment shall be discarded. Semi-Persistent Scheduling is not supported for RN communication with the E-UTRAN in combination with an RN subframe configuration. NOTE: When eIMTA is configured, if a configured uplink grant or a configured downlink assignment occurs on a subframe that can be reconfigured through eIMTA L1 signalling, then the UE behaviour is left unspecified. | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.10 |
1,574 | 10.2.2.3 Key generation for Unauthenticated IMS Emergency Sessions 10.2.2.3.1 General | An unauthenticated UE does not share a complete 5G NAS security context with the network as there has been no successful primary authentication run between the UE and the AMF. When the UE and the AMF does not share the security context the only possibility for an AMF that allows unauthenticated IMS Emergency Sessions is to run with the NULL integrity algorithm NIA0 and the NULL ciphering algorithm NEA0. When there has been no successful run of Primary authentication of the UE, the UE and the AMF independently generate the KAMF 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. All key derivations proceed as if they were based on a KAMF generated from a successful Primary authentication run. Even if no confidentiality or integrity protection is provided by NIA0 and NEA0, the UE and the network treat the 5G security context with the independently generated KAMF as if it contained a normally generated KAMF. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 10.2.2.3 |
1,575 | 4.12.8 Mobility from a non-geographically selected AMF to a geographically selected AMF | This procedure describes the AMF change that takes place when an UE initially served via non-3GPP access by an AMF selected based on non-geographical criteria (e.g. because the UE had no 3GPP access coverage or because only non-geographically selectable N3IWF are deployed) gets 3GPP access and is now to be served by an AMF selected in the same PLMN by the NG-RAN based on geographical criteria. Figure 4.12.8-1: Mobility from a non-geographically selected AMF to a geographically selected AMF 1. The UE registers over non-3GPP access, as described in clause 4.12.2. During this procedure: a An AMF (source AMF) is selected by the N3IWF in step 6a, based on non-geographical criteria (e.g. because the UE has no 3GPP access coverage or because only non-geographically selectable N3IWF are deployed). b The UE receives, within the Registration Accept message, a 5G-GUTI containing a GUAMI of the non-geographically selected AMF. The UE also receives an Allowed NSSAI and optionally Mapping Of Allowed NSSAI. 2. The UE may activate PDU Sessions over non-3GPP access, as described in clause 4.12.5. 3. The UE gets 3GPP access and issues a Registration Request over 3GPP access as defined in step 1 of Figure 4.2.2.2.2-1, providing its 5G-GUTI. If the 5G-GUTI does not indicate an AMF of the same Region ID as that of the NG-RAN, the NG-RAN selects an AMF Set and an AMF in the AMF Set as described in clause 6.3.5 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. Steps 3 to 22 of Figure 4.2.2.2.2-1 take place including following aspects: - step 4 of Figure 4.2.2.2.2-1 takes place i.e. the new AMF invokes the Namf_Communication_UEContextTransfer service operation on the old AMF to request the UE's SUPI and MM Context. - in step 5 of Figure 4.2.2.2.2-1, the old AMF includes information about active NGAP association to N3IWF. - in step 18 of Figure 4.2.2.2.2-1, the new AMF modifies the NGAP association toward N3IWF. - in step 21 of Figure 4.2.2.2.2-1, the Registration Accept message shall include the updated 5G-GUTI that the UE will use to update its 3GPP and non-3GPP registration contexts. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.12.8 |
1,576 | 5.8.9.3 Sidelink radio link failure related actions | The UE shall: 1> upon indication from sidelink RLC entity that the maximum number of retransmissions for a specific destination has been reached; or 1> upon T400 expiry for a specific destination; or 1> upon indication from MAC entity that the maximum number of consecutive HARQ DTX for a specific destination has been reached; or 1> upon integrity check failure indication from sidelink PDCP entity concerning SL-SRB2 or SL-SRB3 for a specific destination; or 1> upon indication of consistent sidelink LBT failures for all RB sets for a specific destination from MAC entity; or 1> upon reception of NotificationMessageSidelink indicating PC5 RLF from the L2 U2U Relay UE for a specific destination based on the received sl-DestinationIdentity: 2> consider sidelink radio link failure to be detected for this destination; 2> release the DRBs of this destination, according to clause 5.8.9.1a.1; 2> release the SRBs of this destination, according to clause 5.8.9.1a.3; 2> release the PC5 Relay RLC channels of this destination if configured, in according to clause 5.8.9.7.1; 2> discard the NR sidelink communication related configuration of this destination; 2> reset the sidelink specific MAC of this destination, except for L2 U2U Relay operation; 2> consider the PC5-RRC connection is released for the destination; 2> indicate the release of the PC5-RRC connection to the upper layers for this destination (i.e. PC5 is unavailable); 2> if UE is in RRC_CONNECTED: 3> if the UE is acting as L2 U2N Remote UE for the destination: 4> initiate the RRC connection re-establishment procedure as specified in 5.3.7. 3> else: 4> perform the sidelink UE information for NR sidelink communication procedure, as specified in 5.8.3.3; Editor's Note: FFS whether additional procedure for L2 U2U PC5 RLF initiation. NOTE: It is up to UE implementation on whether and how to indicate to upper layers to maintain the keep-alive procedure [55]. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.9.3 |
1,577 | 8.23.2 Migration of mobile IAB-MT via NG handover | The mobile IAB-MT can be migrated from a source RRC-terminating IAB-donor-CU to a target RRC-terminating IAB-donor-CU using the NG handover procedure. During this migration, the mobile IAB-DU co-located with the mobile IAB-MT is connected to an F1-terminating IAB-donor-CU, which may be the same as the source RRC-terminating IAB-donor-CU or the target RRC-terminating IAB-donor-CU, or it can be different from both the source and the target RRC-terminating IAB-donor-CU. Figure 8.23.2-1 shows an example of mobile IAB-MT migration via NG handover. In this example, the mobile IAB-MT is connected to the source RRC-terminating IAB-donor-CU via a source path of an IAB topology before the migration, and it is connected to the target RRC-terminating IAB-donor-CU via a target path of a different IAB topology after the migration. Figure 8.23.2-1: Procedure for NG-based migration of mobile IAB-MT 1. Similar to Step 1-14 in clause 8.17.3.1, where the NG-based handover procedure as defined in clauses 4.9.1.3.2 and 4.9.1.3.3 in TS 23.502[ Procedures for the 5G System (5GS) ] [32] is used instead of Xn-based handover procedure. 2. Same as step 2 to step 4 in clause 8.23.1. NOTE How to perform the IAB Transport Migration Management/Modification procedures and the IAB Resource Coordination procedure between the F1-terminating IAB-donor-CU and the target RRC-terminating IAB-donor-CU without Xn interface is up to implementation. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.23.2 |
1,578 | 6.3.1A.2 Service-level authentication and authorization procedure initiation | In order to initiate the service-level authentication and authorization procedure, the SMF shall create a SERVICE-LEVEL AUTHENTICATION COMMAND message. The SMF shall set the PTI IE of the SERVICE-LEVEL AUTHENTICATION COMMAND message to "No procedure transaction identity assigned". The SMF shall set the service-level-AA payload in the Service-level-AA container IE of the SERVICE-LEVEL AUTHENTICATION COMMAND message to the payload provided by the DN via the NEF. If a payload type associated with the payload is provided by the DN via the NEF, the SMF shall set the service-level-AA payload type with the value set to the payload type. NOTE: In case of UUAA, the service-level-AA payload is provided by the DN via the UAS-NF. The SMF shall send the SERVICE-LEVEL AUTHENTICATION COMMAND message, and the SMF shall start timer T3594 (see example in figure 6.3.1A.1-1). Upon receipt of a SERVICE-LEVEL AUTHENTICATION COMMAND message and a PDU session ID, using the NAS transport procedure as specified in subclause 5.4.5, the UE passes to the upper layers the service-level-AA payload received in the Service-level-AA container IE of the SERVICE-LEVEL AUTHENTICATION COMMAND message. Apart from this action, the service-level authentication and authorization procedure initiated by the DN is transparent to the 5GSM layer of the UE. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.3.1A.2 |
1,579 | 4 Elementary procedures for Mobility Management 4.1 General | This clause describes the procedures used for mobility management for non-GPRS services and for GPRS-services at the radio interface (Reference Point Um and Uu). The main function of the Mobility Management sublayer is to support the mobility of user terminals, such as informing the network of its present location and providing user identity confidentiality. A further function of the MM sublayer is to provide connection management services to the different entities of the upper Connection Management (CM) sublayer (see 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [20]). There are two sets of procedures defined in this chapter: - MM procedures for non-GPRS services (performed by the MM entity of the MM sublayer); and - GMM procedures for GPRS services (performed by the GMM entity of the MM sublayer), see 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [20]. All the MM procedures described in this clause can only be performed if a RR connection has been established between the MS and the network. Else, the MM sublayer has to initiate the establishment of a RR connection (see 3GPP TS 44.018[ None ] [84] subclause 3.3 and 3GPP TS 25.331[ None ] [23c]). In A/Gb mode, the GMM procedures described in this clause, use services provided by the RR sublayer without prior RR connection establishment. In Iu mode: all the GMM procedures described in this clause can only be performed if a PS signalling connection has been established between the MS and the network. Else, the GMM sublayer has to initiate the establishment of a PS signalling connection (see 3GPP TS 25.331[ None ] [23c]). GMM procedures are mandatory and applicable only for GPRS MSs and networks supporting those MSs. For GPRS MSs which are IMSI attached for both GPRS and non-GPRS services, some MM procedures are replaced by GMM combined procedures provided that the network operates in network operation mode I, i.e. is supporting combined GMM procedures. GMM combined procedures are not applicable for the GPRS MS operation mode C but are mandatory for the GPRS MS operation modes A and B and networks supporting network operation mode I, see 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [74]. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4 |
1,580 | 4.16.8.2 Initial Spending Limit Retrieval | This clause describes the signalling flow for the PCF to retrieve the status of the policy counters available at the CHF and to subscribe to spending limit reporting (i.e. to notifications of policy counter status changes) by the CHF. If the PCF provides the list of policy counter identifier(s), the CHF returns the policy counter status per policy counter identifier provided by the PCF. If the PCF does not provide the list of policy counter identifier(s), the CHF returns the policy counter status of all policy counter(s), which are available for this subscriber. The Initial Spending Limit Report Retrieval includes all subscriber Identifiers associated with the UE available at the PCF. NOTE: If the CHF returns the status of all available policy counters some of these might not be relevant for a policy decision (e.g. those used in a policy decision only when roaming). Figure 4.16.8.2.1: Initial Spending Limit Report Retrieval 1. The PCF retrieves subscription information that indicates that policy decisions depend on the status of policy counter(s) held at the CHF and optionally the list of policy counter identifier(s). 2. The PCF sends Nchf_SpendingLimitControl_Subscribe if this is the first time policy counter status information is requested for the user identified by a SUPI. It includes: the subscriber ID (e.g. SUPI), the EventId "policy counter status change" and optionally, the list of policy counter identifier(s) as Event Filter, the Notification Target Address, Event Reporting Information (continuous reporting). The CHF responds to the Nchf_SpendingLimitControl_Subscribe service operation including the Subscription Correlation Id) and as Event Information provides a policy counter status and optionally pending policy counter statuses and their activation times, per required policy counter identifier and stores the PCF's subscription to spending limit reports for these policy counters. If no policy counter identifier(s) was provided the CHF returns the list of the policy counter status, optionally including pending policy counter statuses and their activation times, for all policy counter(s), which are available for this subscriber and stores the PCF's subscription to spending limit reports of all policy counters provided to the PCF. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.16.8.2 |
1,581 | 5.7.1.4 QoS Rules | The UE performs the classification and marking of UL User plane traffic, i.e. the association of UL traffic to QoS Flows, based on QoS rules. These QoS rules may be explicitly provided to the UE (i.e. explicitly signalled QoS rules using the PDU Session Establishment/Modification procedure), pre-configured in the UE or implicitly derived by the UE by applying Reflective QoS (see clause 5.7.5). A QoS rule contains the QFI of the associated QoS Flow, a Packet Filter Set (see clause 5.7.6) and a precedence value (see clause 5.7.1.9). An explicitly signalled QoS rule contains a QoS rule identifier which is unique within the PDU Session and is generated by SMF. There can be more than one QoS rule associated with the same QoS Flow (i.e. with the same QFI). When the UE informs the network about the number of supported Packet Filters for signalled QoS rules for the PDU Session (during the PDU Session Establishment procedure or using the PDU Session Modification procedure as described in clause 5.17.2.2.2 after the first inter-system change from EPS to 5GS for a PDU Session established in EPS and transferred from EPS with N26 interface), the SMF shall ensure that the sum of the Packet Filters used by all signalled QoS rules for a PDU Session does not exceed the number indicated by the UE. A default QoS rule is required to be sent to the UE for every PDU Session establishment and it is associated with a QoS Flow. For IP type PDU Session or Ethernet type PDU Session, the default QoS rule is the only QoS rule of a PDU Session which may contain a Packet Filter Set that allows all UL packets, and in this case, the highest precedence value shall be used for the QoS rule. NOTE 2: How the UE evaluates UL packets against the Packet Filter Set in a QoS rule is described in clause 5.7.1.5. NOTE 3: The QoS rule pre-configured in the UE is only used together with option 1a for control QoS Flows as described in clause 5.7.1.3. How to keep the consistency of QFI and Packet Filter Set between UE and network is out of scope in this release of the specification. For Unstructured type PDU Session, the default QoS rule does not contain a Packet Filter Set, and in this case the default QoS rule defines the treatment of all packets in the PDU Session. As long as the default QoS rule does not contain a Packet Filter Set or contains a Packet Filter Set that allows all UL packets, Reflective QoS should not be applied for the QoS Flow which the default QoS rule is associated with and the RQA should not be sent for this QoS Flow. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.7.1.4 |
1,582 | 4.2 Behaviour of the MS in MM Idle state, GMM-DEREGISTERED state and GMM-REGISTERED state | In this subclause, the detailed behaviour of the MS in the main states MM IDLE, GMM-DEREGISTERED and GMM-REGISTERED is described. Subclauses 4.2.1 to 4.2.3 refer to the state MM IDLE, whereas subclauses 4.2.4 and 4.2.5 refer to the states GMM-DEREGISTERED and GMM-REGISTERED, respectively. The MM IDLE state is entered when none of the MM procedures are running and no RR connection exists. It is left when one of the MM procedures are triggered or a RR connection is established. The specific behaviour in the MM IDLE state depends on the service state of the mobile station as described in subclause 4.1.2.1.2. The service state depends in particular on the update status which is defined in subclause 4.1.2.2. How an appropriate service state is chosen after power on is described in subclause 4.2.1, and the specific behaviour of the mobile station in MM IDLE state is described in subclause 4.2.2. The service state chosen when the MM IDLE state is returned to from any state except NULL state is described in subclause 4.2.3. It should be noted that transitions between the various MM idle states are caused by (e.g.): - results of procedures on RR connected mode (see subclause 4.2.3); - insertion or removal of the SIM/USIM; - cell selection/reselection (see also 3GPP TS 43.022[ None ] [82] and 3GPP TS 25.304[ None ] [98]); - PLMN search; - loss of coverage. How various MM procedures affects the service state and the update status is described in the detailed descriptions of the procedures in subclauses 4.3 to 4.5. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.2 |
1,583 | 5.6.1.4.1 UE is not using EPS services with control plane CIoT EPS optimization | If EMM-REGISTERED without PDN connection is supported by the UE and the MME and the MME has no active EPS bearer contexts for the UE, for cases a, b, c and o in clause 5.6.1.1, upon receipt of the SERVICE REQUEST message or the EXTENDED SERVICE REQUEST message for packet services, after completion of the EMM common procedures according to clause 5.6.1.3, if any, the MME shall send a SERVICE ACCEPT message. If EMM-REGISTERED without PDN connection is supported by the UE and the MME and the UE has no active EPS bearer contexts, for cases a, b, c and o in clause 5.6.1.1, the UE shall treat the receipt of a SERVICE ACCEPT message as successful completion of the procedure. Otherwise, for cases a, b, c, h, k, l and o in clause 5.6.1.1, the UE shall treat the indication from the lower layers that the user plane radio bearer is set up as successful completion of the procedure. The UE shall reset the service request attempt counter, stop the timer T3417 and enter the state EMM-REGISTERED. If the service type information element in the EXTENDED SERVICE REQUEST message indicates "mobile terminating CS fallback or 1xCS fallback" and the CSFB response IE, if included, indicates "CS fallback accepted by the UE", or if the service type information element in the EXTENDED SERVICE REQUEST message indicates "mobile originating CS fallback or 1xCS fallback" or "mobile originating CS fallback emergency call or 1xCS fallback emergency call", the network initiates CS fallback or 1xCS fallback procedures. If the EPS bearer context status IE is included in the EXTENDED SERVICE REQUEST message, the network shall deactivate all those EPS bearer contexts locally (without peer-to-peer signalling between the network and the UE) which are active on the network side but are indicated by the UE as being inactive. If a default EPS bearer context is marked as inactive in the EPS bearer context status IE included in the EXTENDED SERVICE REQUEST message, and this default bearer is not associated with the last remaining PDN connection of the UE in the MME, the MME shall locally deactivate all EPS bearer contexts associated to the PDN connection with the default EPS bearer context without peer-to-peer ESM signalling to the UE. If the default bearer is associated with the last remaining PDN connection of the UE in the MME, and EMM-REGISTERED without PDN connection is supported by the UE and the MME, the MME shall locally deactivate all EPS bearer contexts associated to the PDN connection with the default EPS bearer context without peer-to-peer ESM signalling to the UE. If the default EPS bearer context of a PDN connection established as a user-plane resource of an MA PDU session as specified in clause 5.3 of 3GPP TS 24.193[ 5G System;Access Traffic Steering, Switching and Splitting (ATSSS); Stage 3 ] [61] is deactivated locally and the MA PDU session does not have user plane resources established on non-3GPP access in N1 mode, the network shall perform a local release of the MA PDU session. If the SERVICE REQUEST message or the EXTENDED SERVICE REQUEST message for packet services, was sent in a CSG cell and the CSG subscription has expired or was removed for a UE, but the UE has a PDN connection for emergency bearer services established, the network shall accept the SERVICE REQUEST message or the EXTENDED SERVICE REQUEST message for packet services and deactivate all non-emergency EPS bearers locally. The emergency EPS bearers shall not be deactivated. For cases d in clause 5.6.1.1, and for case e in clause 5.6.1.1 when the CSFB response was set to "CS fallback accepted by the UE", the UE shall treat the indication from the lower layers that the inter-system change from S1 mode to A/Gb or Iu mode is completed as successful completion of the procedure. The EMM sublayer in the UE shall indicate to the MM sublayer that the CS fallback procedure has succeeded. The UE shall stop the timer T3417ext or T3417ext-mt, respectively, and enter the state EMM-REGISTERED.NO-CELL-AVAILABLE. If the service request procedure was initiated in EMM-IDLE mode and an EXTENDED SERVICE REQUEST message was sent in a CSG cell and the CSG subscription has expired or was removed for the UE, the network need not perform CSG access control if the service type information element indicates "mobile originating CS fallback emergency call or 1xCS fallback emergency call". For cases f and g in clause 5.6.1.1: - if the UE receives the indication from the lower layers that the signalling connection is released with the redirection indication to cdma2000® 1x access network or the indication from the lower layers that a change to cdma2000® 1x access network for 1xCS fallback has started (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]), the UE shall consider the service request procedure successfully completed, stop timer T3417 and enter the state EMM-REGISTERED.NO-CELL-AVAILABLE; - if the UE receives the dual Rx/Tx redirection indication from the lower layers (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]), the UE shall select cdma2000® 1x access network for 1xCS fallback, consider the service request procedure successfully completed, stop timer T3417 and enter the state EMM-REGISTERED.NORMAL-SERVICE; and - if the UE receives a cdma2000® signalling message indicating 1xCS fallback rejection by cdma2000® 1x access network, the UE shall abort the service request procedure, stop timer T3417 and enter the state EMM-REGISTERED.NORMAL-SERVICE. For cases i and j in clause 5.6.1.1, if the UE receives the indication from the lower layers that the signalling connection is released, the UE shall consider the service request procedure successfully completed, stop timer T3417 and enter the state EMM-REGISTERED.NO-CELL-AVAILABLE. For cases o, p and q in clause 5.6.1.1, when the MUSIM UE in the EXTENDED SERVICE REQUEST message sets the Request type to "NAS signalling connection release" or to "Rejection of paging" in the UE request type IE, the UE shall treat the receipt of SERVICE ACCEPT message as the successful completion of the procedure and the UE shall reset the service request attempt counter, stop timer T3417 and enter the state EMM-REGISTERED. If the SERVICE REQUEST message or an EXTENDED SERVICE REQUEST message for packet services was used, the UE shall locally deactivate the EPS bearer contexts that do not have a user plane radio bearer established upon successful completion of the service request procedure, except for the case when the MUSIM UE in the EXTENDED SERVICE REQUEST message sets the Request type to "NAS signalling connection release" or to "Rejection of paging" in the UE request type IE. If the EXTENDED SERVICE REQUEST message is for CS fallback or 1xCS fallback and radio bearer establishment takes place during the procedure, the UE shall locally deactivate the EPS bearer contexts that do not have a user plane radio bearer established upon receiving a lower layer indication of radio bearer establishment. The UE does not perform local deactivation of EPS bearer contexts upon receiving an indication of inter-system change from lower layers. If the EXTENDED SERVICE REQUEST message is for CS fallback or 1xCS fallback and radio bearer establishment does not take place during the procedure, the UE does not perform local deactivation of the EPS bearer context. The UE does not perform local deactivation of EPS bearer contexts upon receiving an indication of inter-system change from lower layers. If a service request is received from a UE with a LIPA PDN connection, and if: - a GW Transport Layer Address IE value identifying a L-GW is provided by the lower layer together with the service request, and the P-GW address included in the EPS bearer context of the LIPA PDN connection is different from the provided GW Transport Layer Address IE value (see 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [23]); or - no GW Transport Layer Address is provided together with the service request by the lower layer; then the MME shall locally deactivate all EPS bearer contexts associated with any LIPA PDN connection. Furthermore, if no active EPS bearer contexts remain for the UE, the MME shall not accept the service request as specified in clause 5.6.1.5. If a service request is received from a UE with a SIPTO at the local network PDN connection, and if the PDN connection is a: 1) SIPTO at the local network PDN connection with stand-alone GW, and if: - a LHN-ID value is provided by the lower layer together with the service request, and the LHN-ID value stored in the EPS bearer context of the SIPTO at the local network PDN connection is different from the provided LHN-ID value (see 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [23]); or - no LHN-ID value is provided together with the service request by the lower layer; or 2) SIPTO at the local network PDN connection with collocated L-GW, and if: - a SIPTO L-GW Transport Layer Address IE value identifying a L-GW is provided by the lower layer together with the service request, and the P-GW address included in the EPS bearer context of the SIPTO at the local network PDN connection is different from the provided SIPTO L-GW Transport Layer Address IE value (see 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [23]); or - no SIPTO L-GW Transport Layer Address is provided together with the service request by the lower layer; then, the MME takes one of the following actions: - if all the remaining PDN connections are SIPTO at the local network PDN connections, the MME shall not accept the service request as specified in clause 5.6.1.5; and - if a PDN connection remains that is not SIPTO at the local network PDN connection and the network decides to set up the S1 and radio bearers, the MME shall upon completion of the setup of the S1 bearers initiate an EPS bearer context deactivation procedure with ESM cause #39 "reactivation requested" for the default EPS bearer context of each SIPTO at the local network PDN connection (see clause 6.4.4.2). NOTE: For some cases of CS fallback or 1x CS fallback the network can decide not to set up any S1 and radio bearers. Upon receipt of the SERVICE REQUEST message, the MME shall delete any stored paging restriction for the UE and stop restricting paging. If the MUSIM UE does not include the Paging restriction IE in the EXTENDED SERVICE REQUEST message, the MME shall delete any stored paging restriction for the UE and stop restricting paging. For cases p and q in clause 5.6.1.1 when the MUSIM UE sets the Request type to "NAS signalling connection release" or to "Rejection of paging" in the UE request type IE in the EXTENDED SERVICE REQUEST message and if the UE requests restriction of paging by including the Paging restriction IE, the MME: - if accepts the paging restriction, shall include the EPS additional request result IE in the SERVICE ACCEPT message and set the Paging restriction decision to "paging restriction is accepted". The MME shall store the paging restriction of the UE and enforce these restrictions in the paging procedure as described in clause 5.6.2; or - if rejects the paging restriction, shall include the EPS additional request result IE in the SERVICE ACCEPT message and set the Paging restriction decision to "paging restriction is rejected", and shall discard the received paging restriction. The MME shall delete any stored paging restriction for the UE and stop restricting paging; and - shall initiate the release of the NAS signalling connection after the completion of the service request procedure. When the E-UTRAN fails to establish radio bearers for one or more EPS bearer contexts, then the MME shall locally deactivate the EPS bearer contexts corresponding to the failed radio bearers based on the lower layer indication from the E-UTRAN, without notifying the UE. If the UE is not using EPS services with control plane CIoT EPS optimization, the network shall consider the service request procedure successfully completed in the following cases: - when it receives an indication from the lower layer that the user plane is setup, if radio bearer establishment is required; - otherwise when it receives an indication from the lower layer that the UE has been redirected to the other RAT (GERAN or UTRAN in CS fallback, or cdma2000® 1x access network for 1xCS fallback). | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.6.1.4.1 |
1,584 | 6.2.5D Configured transmitted 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 configured maximum output power PCMAX,c and power boundary requirement specified in subclause 6.2.5 shall apply to UE supporting ProSe, where - MPRc is specified in subclause 6.2.3D; - A-MPRc is specified in subclause 6.2.4D; - TProSe = 0.1 dB. For and, PEMAX,c is the value given by IE P-Max for serving cell c, defined by [7], when present. PEMAX,c is the value given by IE maxTxPower, defined by [7], when the UE is not associated with a serving cell on the ProSe carrier . For, PEMAX,c is the value given by the IE discMaxTxPower in [7]. For, PEMAX,c is the value given by the IE maxTxPower in [7] when the ProSe UE is not associated with a serving cell on the ProSe carrier. When the UE is associated with a serving cell, then PEMAX,c is the value given by the IE P-Max when PSBCH/SLSS transmissions is triggered for ProSe Direct communication as specified in [7], and is the value given by the IE discMaxTxPower in [7] otherwise. For, the value is as calculated for and applying the MPR for SSSS as specified in Section 6.2.3D. When a 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, the UE is allowed to set its configured maximum output power PCMAX,c,E-UTRA and PCMAX,c,ProSe for the configured E-UTRA uplink carrier and the configured E-UTRA ProSe carrier, respectively, and its total configured maximum output power PCMAX,c. The configured maximum output power PCMAX c,E-UTRA(p) in subframe p for the configured E-UTRA uplink carrier shall be set within the bounds: PCMAX_L,c,E-UTRA (p) ≤ PCMAX,c,E-UTRA (p) ≤ PCMAX_H,c,E-UTRA (p) where PCMAX_L,c,E-UTRA and PCMAX_H,c,E-UTRA are the limits for a serving cell c as specified in subclause 6.2.5. The configured maximum output power PCMAX c,ProSe (q) in subframe q for the configured E-UTRA ProSe carrier shall be set within the bounds: PCMAX,c,ProSe (q) ≤ PCMAX_H,c,ProSe (q) where PCMAX_H,c,ProSe is the limit as specified in subclause 6.2.5D. The total UE configured maximum output power PCMAX (p,q) in a subframe p of an E-UTRA uplink carrier and a subframe q of an E-UTRA ProSe sidelink that overlap in time shall be set within the following bounds for synchronous and asynchronous operation unless stated otherwise: PCMAX_L (p,q) ≤ PCMAX (p,q) ≤ PCMAX_H (p,q) with PCMAX_L (p,q) = PCMAX_L,c,E-UTRA (p) PCMAX_H (p,q) = MIN {10 log10 [pCMAX_H,c,E-UTRA (p) + pCMAX_H,c,ProSe (q)], PPowerClass} where pCMAX_H,c,ProSe and pCMAX_H,c,E-UTRA are the limits PCMAX_H,c,ProSe (q) and PCMAX_H,c,E-UTRA (p) expressed in linear scale. The measured total maximum output power PUMAX over both the E-UTRA uplink and E-UTRA ProSe carriers is PUMAX = 10 log10 [pUMAX,c,E-UTRA + pUMAX,c,ProSe], where pUMAX,c,E-UTRA denotes the measured output power of serving cell c for the configured E-UTRA uplink carrier, and pUMAX,c,ProSe denotes the measured output power for the configured E-UTRA ProSe carrier expressed in linear scale. When a UE is configured for synchronous ProSe and uplink transmissions, PCMAX_L(p, q) – TLOW (PCMAX_L(p, q)) ≤ PUMAX ≤ PCMAX_H(p, q) + THIGH (PCMAX_H(p, q)) where PCMAX_L (p,q) and PCMAX_H (p,q) are the limits for the pair (p,q) and with the tolerances TLOW(PCMAX) and THIGH(PCMAX) for applicable values of PCMAX specified in Table 6.2.5C-1. PCMAX_L may be modified for any overlapping portion of subframes (p, q) and (p +1, q+1). When a UE is configured for asynchronous ProSe and uplink transmissions, the carrier configured for uplink transmission is taken as the reference. If subframe p for the E-UTRA uplink carrier and subframe q for the E-UTRA ProSe carrier overlap in time and 1. if uplink carrier leads in time over q, then p is the reference subframe and, the (p,q) and (p,q-1) pairs are considered for determining the PCMAX tolerance 2. if ProSe carrier leads in time over p, then p is the reference subframe and, the (p,q) and (p,q+1) pairs are considered for determining the PCMAX tolerance For the reference subframe p duration when uplink carrier leads: P'CMAX_L = PCMAX_L,,cE-UTRA (p) P'CMAX_H = MAX {PCMAX_H (p,q-1) , PCMAX_H (p,q)} For the reference subframe p duration when ProSe carrier leads: P'CMAX_L = PCMAX_L,cE-UTRA (p) P'CMAX_H = MAX {PCMAX_H (p,q) , PCMAX_H (p,q+1)} where PCMAX_L,,cE-UTRA (p) and PCMAX_H are the applicable limits for each overlapping subframe pairs (p,q) , (p, q+1) , (p, q-1). The measured total configured maximum output power PUMAX shall be within the following bounds: P’CMAX_L – TLOW (P’CMAX_L) ≤ PUMAX ≤ P’CMAX_H + THIGH (P’CMAX_H) with the tolerances TLOW(PCMAX) and THIGH(PCMAX) for applicable values of PCMAX specified in Table 6.2.5C-1. | 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.5D |
1,585 | 5.27.2.4 TSCAI determination based on TSC Assistance Container | The SMF determines the TSCAI (defined in Table 5.27.2-1) for the QoS Flow based on the TSC Assistance Container of the PCC rule bound to the QoS Flow. This clause is applicable irrespective of whether the TSC Assistance Container is determined by the TSN AF or by the TSCTSF. The Burst Arrival Time and Periodicity component of the TSCAI that the SMF sends to the 5G-AN are specified with respect to the 5G clock. The SMF is responsible for mapping the Burst Arrival Time and Periodicity in the TSC Assistance Container from an external clock to the 5G clock based on the time offset and cumulative rateRatio (when available) between external time and 5GS time as measured and reported by the UPF. The SMF may correct the TSCAI based on the UPF report for time offset and cumulative rateRatio between external PTP time and 5GS time as measured and reported by the UPF. The TSCAI parameter determination in SMF is done as follows: - For traffic in downlink direction, the SMF corrects the Burst Arrival Time in the TSC Assistance Container based on the latest received time offset measurement from the UPF and sets the TSCAI Burst Arrival Time as the sum of the corrected value and CN PDB as described in clause 5.7.3.4, representing the latest possible time when the first packet of the data burst arrives at the AN. - For traffic in uplink direction, the SMF corrects the Burst Arrival Time in the TSC Assistance Container based on the latest received time offset measurement from the UPF and sets the TSCAI Burst Arrival Time as the sum of the corrected value and UE-DS-TT Residence Time, representing the latest possible time when the first packet of the data burst arrives at the egress of the UE. How the SMF corrects the Burst Arrival Time if the UE-DS-TT Residence Time has not been provided by the UE is up to SMF implementation. - The SMF corrects the Periodicity in the TSC Assistance Container using the cumulative rateRatio if the cumulative rateRatio was previously received from the UPF and sets the TSCAI Periodicity as the corrected value. Otherwise, the SMF sets the received Periodicity in the TSCAI without any correction. - The SMF sets the TSCAI Flow Direction as the Flow Direction in the TSC Assistance Container. - If Survival Time is provided in terms of maximum number of messages, the SMF converts maximum number of messages into time units by multiplying its value by the TSCAI Periodicity, and sets the TSCAI Survival Time to the calculated value. If Survival Time is provided in time units, the SMF corrects the Survival Time using the cumulative rateRatio if the cumulative rateRatio was previously received from the UPF and sets the TSCAI Survival Time to the corrected value. Otherwise, SMF sets the TSCAI Survival Time without correction. - If the TSC Assistance Container contains a BAT Window, the SMF sets and corrects the indicated earliest and latest possible arrival time of the first packet in the same way it is described for the correction of the Burst Arrival Time above. - If the TSC Assistance Container contains a Capability for BAT adaptation, the SMF sets the Capability for BAT adaptation in the TSCAI. When the SMF determines that the TSCAI contains the Capability for BAT adaptation without a BAT, the SMF enables notification control for the QoS Flow in order to receive the BAT offset along with the "GFBR can no longer be guaranteed" notification described in clause 5.7.2.4. - If the TSC Assistance Container contains a Periodicity Range, the SMF sets and corrects the Periodicity Range in the same way it is described for the correction of the Periodicity above. Depending on whether the Time Domain is provided in the TSC Assistance container, SMF may perform the following: - the SMF provisions the UPF/NW-TT to report the clock drifting between 5G clock and the external GM clock for the (g)PTP time domain number that is configured to the NW-TT. - the SMF provisions the UPF/NW-TT to report the clock drifting between 5G clock and the external GM clock for the given Time Domain number. The SMF uses the N4 Association Setup or Update procedures as described in clause 4.4.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] to provision the UPF to report the clock drifting. If the SMF has clock drift information for a Time Domain and if the Time Domain matches with the Time Domain in the TSC Assistance Container (i.e. clock drift between 5G timing and AF supplied Time Domain determined based on UPF reporting), or Time Domain information is not provided in the TSC Assistance Container, then the SMF may adjust the TSCAI information so that it reflects the 5GS Clock as described in clause 5.27.2.1. If the SMF does not have synchronization information for a requested Time Domain in the TSC Assistance Container, or the Time Domain in the TSC Assistance Container is set to a value = "5GS", then the TSCAI information will be used without adjustment. In the case of drift between external GM clock and 5G clock, the UPF updates the offset to SMF using the N4 Report Procedure as defined in clause 4.4.3.4 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. If the cumulative rateRatio is available and in the case of change of cumulative rateRatio between external PTP time and 5G time, the UPF updates the cumulative rateRatio to SMF using the N4 Report Procedure as defined in clause 4.4.3.4 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. The SMF may then trigger a PDU Session Modification as defined in clause 4.3.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] in order to update the TSCAI to the NG-RAN without requiring AN or N1 specific signalling exchange with the UE. NOTE 4: In order to prevent frequent updates from the UPF, the UPF sends the offset or the cumulative rateRatio only when the difference between the current measurement and the previously reported measurement is larger than a threshold as described in clause 4.4.3.4 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.27.2.4 |
1,586 | 5.3.4B.2 Mobile Originated Data Transport in Control Plane CIoT EPS Optimisation with P-GW connectivity | Figure 5.3.4B.2-1: MO Data transport in NAS PDU 0. The UE is ECM-IDLE. 1. The UE establishes a RRC connection or sends the RRCEarlyDataRequest message as defined in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5] and sends as part of it an integrity protected NAS PDU. The NAS PDU carries the EPS Bearer ID and encrypted Uplink Data. For IP PDN type PDN connections configured to support Header Compression, the UE shall apply header compression before encapsulating data into the NAS message. The UE may also indicate in a NAS Release Assistance Information in the NAS PDU whether no further Uplink or Downlink Data transmissions are expected, or only a single Downlink data transmission (e.g. Acknowledgement or response to Uplink data) subsequent to this Uplink Data transmission is expected. 1b. In the NB-IoT case, the eNodeB, based on configuration, may retrieve the EPS negotiated QoS profile from the MME, if not previously retrieved. The MME Code within the S-TMSI in the RRCConnectionRequest message is used to identify the MME. In the case of network sharing, the MME Codes shall be unique within the area of overlapping MME pools of the participating operators. The eNodeB may apply prioritisation between requests from different UEs before triggering step 2 and throughout the RRC connection. The eNodeB may retrieve additional parameters (e.g., UE Radio Capabilities - see TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36]). 2. The NAS PDU sent in step 1 is relayed to the MME by the eNodeB using a S1-AP Initial UE message. If the RRCEarlyDataRequest message was received in step 1, the eNodeB includes the "EDT Session" indication in the S1-AP Initial UE message. To assist Location Services, the eNodeB indicates the UE's Coverage Level to the MME. If the NAS Release Assistance Information is received from the UE it overrides the Traffic Profile (see TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [74]) and the MME does not send the Traffic Profile to the eNodeB. 3. If there is a Service Gap timer running in the MME MM Context for the UE and the MME is not waiting for a MT paging response from the UE, the MME rejects the request by discarding the NAS data PDU and sending a Service Reject message to the UE with an appropriate cause. The MME may also provide UE with a Mobility Management Back-off timer set to the remaining value of Service Gap timer, followed by executing step 15. The MME checks the integrity of the incoming NAS PDU and decrypts the data it contains. When the ROHC is configured to be used, the MME shall decompress the IP header if header compression applies to the PDN connection. The MME performs (and the UE responds to) any EMM or ESM procedures if necessary, e.g. the security related procedures. Steps 4 to 9 can continue in parallel to this, however, steps 10 and 11 shall await completion of all the EMM and ESM procedures. 4a. If the S11-U connection is not established, the MME sends a Modify Bearer Request message (MME address, MME TEID DL, Delay Downlink Packet Notification Request, RAT Type, LTE-M RAT type reporting to PGW flag, MO Exception data counter) for each PDN connection to the Serving GW. The Serving GW is now able to transmit downlink data towards the UE. The usage of the Delay Downlink Packet Notification Request Information Element is specified in clause 5.3.4.2 with reference to the UE initiated service request procedure, but it equally applies in this case. The MME shall indicate S11-U tunnelling of NAS user data and send its own S11-U IP address and MME DL TEID for DL data forwarding by the SGW. Also, regardless of whether the S11-U was already established: - If the PDN GW requested UE's location and/or User CSG information and the UE's location and/or User CSG information has changed, the MME shall send the Modify Bearer Request message and also includes the User Location Information IE and/or User CSG Information IE in this message. - If the Serving Network IE has changed compared to the last reported Serving Network IE then the MME shall send the Modify Bearer Request message and also includes the Serving Network IE in this message. - If the UE Time Zone has changed compared to the last reported UE Time Zone then the MME shall send the Modify Bearer Request message and include the UE Time Zone IE in this message. If the RAT type currently used is NB-IOT this shall be reported as different from other E-UTRA flavours. If the UE is using the LTE-M RAT type and the PDN GW expects the LTE-M RAT type reporting as specified in clause 5.11.5, the MME also includes the LTE-M RAT type reporting to PGW flag to indicate to the Serving GW to forward the LTE-M RAT type to the PDN GW. The MME only includes MO Exception data counter if the RRC establishment cause is set to "MO exception data" and the UE is accessing via the NB-IoT RAT. The Serving GW indicates each use of this RRC establishment cause by the related counter on its CDR. The MME maintains the MO Exception Data Counter for Serving PLMN Rate Control purposes (see clause 4.7.7.2). The MME may immediately send the MO Exception Data Counter to the Serving GW. Alternatively, in order to reduce signalling, the MME may send the MO Exception Data Counter to the Serving GW as indicated in TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [43]. 4b If the S11-U connection is established and the UE is accessing via the NB-IoT RAT with the RRC establishment cause set to "MO exception data", the MME should notify the Serving Gateway. The MME maintains the MO Exception Data Counter for Serving PLMN Rate Control purposes (see clause 4.7.7.2). The MME may immediately send the MO Exception Data Counter to the Serving GW. Alternatively, in order to reduce signalling, the MME may send the MO Exception Data Counter to the Serving GW as indicated in TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [43]. 5. If the RAT Type has changed compared to the last reported RAT Type or if the UE's Location and/or Info IEs and/or UE Time Zone and Serving Network id are present in step 4, the Serving GW shall send the Modify Bearer Request message (RAT Type, MO Exception data counter) to the PDN GW. User Location Information IE and/or User CSG Information IE and/or Serving Network IE and/or UE Time Zone are also included if they are present in step 4. If LTE-M RAT type and the LTE-M RAT type reporting to PGW flag were received at step 4a, the Serving GW shall include the LTE-M RAT type in the Modify Bearer Request message to the PGW. Otherwise the Serving GW includes RAT type WB-E-UTRAN. If the Modify Bearer Request message is not sent because of above reasons and the PDN GW charging is paused, then the SGWS-GW shall send a Modify Bearer Request message with PDN Charging Pause Stop Indication to inform the PDN GW that the charging is no longer paused. Other IEs are not included in this message. If the Modify Bearer Request message is not sent because of above reasons but the MME indicated MO Exception data counter, then the Serving Gateway should notify the PDN GW that this RRC establishment cause has been used by the indication of the MO Exception Data Counter (see TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [43]). The Serving GW indicates each use of this RRC establishment cause by the related counter on its CDR. 6. The PDN GW sends the Modify Bearer Response to the Serving GW. The PDN GW indicates each use of the RRC establishment cause "MO Exception Data" by the related counter on its CDR. 7. If a Modify Bearer Request message was sent at step 4 the Serving GW shall return a Modify Bearer Response (Serving GW address and TEID for uplink traffic) to the MME as a response to a Modify Bearer Request message. The Serving GW address for S11-U User Plane and Serving GW TEID are used by the MME to forward UL data to the SGW. 8. The MME sends Uplink data to the P-GW via the S-GW. 9. If no Downlink Data are expected based on the NAS Release Assistance Information from the UE in step 1, this means that all application layer data exchanges have completed with the UL data transfer, and if the MME is not aware of pending MT traffic and S1-U bearers are not established, step 10 is skipped and step 11 applies. Otherwise, Downlink data may arrive at the P-GW and the P-GW sends them to the MME via the S-GW. If no data is received steps10-12 are skipped and the eNodeB may trigger step 14 after step 13 detects no activity. While the RRC connection is active, the UE may still send Uplink data and may receive Downlink data in NAS PDUs that are carried in a S1AP Uplink or (respectively) Downlink messages (not shown in the figure). At any time the UE has no user plane bearers established it may provide NAS Release Assistance Information with the Uplink data. In this case, to assist Location Services, the eNodeB may indicate, if needed, the UE's Coverage Level to the MME. 10. If Downlink data are received in step 9, the MME encrypts and integrity protects the Downlink data. 11. If step 10 is executed then Downlink data are encapsulated in a NAS PDU and sent to the eNodeB in a S1-AP Downlink NAS Message. If the configuration in the MME indicates that the eNodeB supports acknowledgements of downlink NAS data PDUs and if acknowledgements of downlink NAS data PDUs are enabled in the subscription information for the UE, the MME indicates in the S1-AP Downlink NAS message that acknowledgment is requested from the eNodeB. For IP PDN type PDN connections configured to support Header Compression, the MME shall apply header compression before encapsulating data into the NAS message. If step 10 is not executed, or NAS Service Accept message is not to be sent, the MME sends Connection Establishment Indication message to the eNodeB to complete the establishment of the UE-associated logical S1-connection. The UE Radio Capability may be provided from the MME to the eNodeB in the DL NAS Transport message or Connection Establishment Indication message, and the eNodeB shall store the received UE Radio Capability information as specified in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]. If the NAS Release Assistance Information was received with Uplink data and it indicated that Downlink data was expected, it means that the next downlink packet following the sending of the NAS Release Assistance Information is the last packet of the application layer data exchange, then for this case, unless the MME is aware of additional pending MT traffic and unless S1-U bearers are established, the MME sends a S1 UE Context Release Command immediately after the S1-AP message including the Downlink data encapsulated in NAS PDU as an indication that the eNodeB shall release the RRC connection promptly after successfully sending data to the UE. Alternatively, if "EDT Session" indication was received in step 2, the MME may include End Indication for no further data in the S1-AP message including the Downlink data encapsulated in NAS PDU. If the MME includes the End Indication indicating no further data and if the eNodeB does not proceed with RRC connection establishment, then the eNodeB skips step 12a and initiates step 12b. If the NAS Release Assistance Information was received indicating no Downlink Data expected, it means that all application layer data exchanges have completed with the UL data transfer, then for this case, unless the MME is aware of additional pending MT traffic and unless S1-U bearers are established: - the MME sends S1AP UE Context Release Command either: - immediately after the S1AP DL NAS TRANSPORT (NAS Service Accept), in which case steps 12b and 14 are skipped, or - immediately after S1AP CONNECTION ESTABLISHMENT INDICATION, in which case steps 12a, 12b, 13, and 14 are skipped. - Alternatively, if the MME received "EDT Session" indication from the eNodeB in step 2, the MME should include End Indication with no further data in S1AP DL NAS TRANSPORT (NAS Service Accept) or S1AP CONNECTION ESTABLISHMENT INDICATION. If the eNodeB does not proceed with RRC connection establishment, the eNodeB skips step 12a and initiates stop 12b. If the UE is accessing via an NB-IoT cell, or if it is accessing via an WB-E-UTRAN cell and is capable of CE mode B, to determine the NAS PDU retransmission strategy the MME should take into account the transmission delay of the NAS PDU and the CE mode B Restricted parameter stored in the MME's MM context and, if applicable, the CE mode, i.e. set the NAS timers long enough according to the worst transmission delay (see TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [46]). 12a. The eNodeB sends a RRC Downlink data message including the Downlink data encapsulated in NAS PDU. If in step 11 the S1-AP message with the NAS DATA PDU was followed by an S1 UE Context Release Command, step 15 is completed promptly after the Downlink Data transmission of the NAS PDU to the UE and the acknowledgement to MME in step 13 have been completed at the eNodeB, and the eNodeB does not need to enter step 14. If header compression was applied to the PDN, the UE would perform header decompression to rebuild the IP header. 12b. If End Indication with no further data is received in S1AP message from the MME, the eNodeB may send the RRCEarlyDataComplete message with any NAS payload received from step 11 (either NAS data PDU or NAS service accept) as defined 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]. Step 14 is skipped in this case. 13. The eNodeB sends a NAS Delivery indication to the MME if requested. If the eNodeB reports an unsuccessful delivery with an S1-AP NAS Non Delivery Indication, the MME should wait for some time until the UE has potentially changed cell and re-established contact with the MME, by which MME should resend the Downlink S1-AP message to the eNodeB, otherwise the MME reports an unsuccessful delivery to the SCEF in the case of T6a procedure (see TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [74], clause 5.13.3). If the eNodeB reports a successful delivery with an S1-AP NAS Delivery Indication and if the Downlink data was received over the T6a interface, the MME should respond to the SCEF (see TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [74], clause 5.13.3). If the eNodeB does not support S1-AP NAS delivery indications, the MME indicates a cause code 'Success Unacknowledged Delivery' to the SCEF otherwise 'Success Acknowledged Delivery', for the SCEF to know if reliable delivery was possible or not. 14. If no NAS PDU activity exists for a while, the eNodeB starts an S1 release in step 15. 15. An S1 release procedure according to clause 5.3.5 triggered by the eNodeB or MME. Alternatively, if the MME in step 11 sent S1 UE Context Release Command then the procedure starts with step 5 in clause 5.3.5, or Connection Suspend Procedure defined in clause 5.3.4A. The UE and the MME shall store the ROHC configuration and context for the uplink/downlink data transmission when entering ECM_CONNECTED state next time. | 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.4B.2 |
1,587 | 6 Security procedures between UE and 5G network functions 6.0 General | When the UE is capable of connecting to 5GC and EPC and connected to an ng-eNB which is connected to both EPC and 5GC, the UE has the ability to select which core network to connect to as described in clause 4.8.4 in TS24.501[35]. If the UE selects the EPC, the UE shall use security procedure as in TS33.401[10]. Otherwise, if the UE selects 5GC, the UE shall use the security procedures as per this document. For an ng-eNB which can connect to EPC and 5GC, the ng-eNB shall choose the corresponding security procedures based on the UE selected type of core netowrk, i.e., when EPC is selected, the ng-eNB shall use security procedures as described in TS33.401[10]. On the other hand, when 5GC is selected, the ng-eNB shall use security procedures as described in this document. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6 |
1,588 | 20.2A MBMS heartbeat | The MBMS heartbeat procedure enables the BM-SC and MBMS GW to detect an SGmb path failure or the restart of the peer MBMS node, as specified in 3GPP TS 23.007[ Restoration procedures ] [104]. The use of this procedure shall be negotiated between the BM-SC and MBMS GW upon contacting the peer node for the first time. NOTE: The MBMS Heartbeat procedure however applies per (BM-SC, MBMS GW) pair, i.e. not per MBMS session. When this procedure is applied, the BM-SC and MBMS GW shall detect an SGmb path failure or the restart of the peer MBMS node as specified in clause 29 of 3GPP TS 23.007[ Restoration procedures ] [104]. The BM-SC and MBMS GW shall maintain a local restart counter which shall be incremented monotonically whenever the MBMS node restarts with loss of previous states. The MBMS heartbeat message shall include the Restart Counter AVP set to the local restart counter of the sending node. The Restart-Counter AVP may also be included in any other SGmb messages e.g. if contacting the peer node for the first time or if the local restart counter has been incremented. | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 20.2A |
1,589 | 5.2.2.2.2 SI change indication and PWS notification | A modification period is used, i.e. updated SI message (other than SI message for ETWS, CMAS, positioning assistance data, and some NTN-specific information as specified in the field descriptions ) is broadcasted in the modification period following the one where SI change indication is transmitted. The modification period boundaries are defined by SFN values for which SFN mod m = 0, where m is the number of radio frames comprising the modification period. The modification period is configured by system information. If H-SFN is provided in SIB1, and UE is configured with eDRX, modification period boundaries are defined by SFN values for which (H-SFN * 1024 + SFN) mod m = 0. For UEs in RRC_IDLE or RRC_INACTIVE configured to use an IDLE eDRX cycle longer than the modification period, an eDRX acquisition period is defined. The boundaries of the eDRX acquisition period are determined by H-SFN values for which H-SFN mod 1024 = 0. The UE receives indications about SI modifications and/or PWS notifications using Short Message transmitted with P-RNTI over DCI (see clause 6.5). Repetitions of SI change indication may occur within preceding modification period or within preceding eDRX acquisition period. SI change indication is not applicable for SI messages containing posSIBs. UEs in RRC_IDLE or in RRC_INACTIVE while SDT procedure is not ongoing shall monitor for SI change indication in its own paging occasion(s) that the UE monitors as specified in TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [20]. UEs in RRC_CONNECTED shall monitor for SI change indication in any paging occasion at least once per modification period if the UE is provided with common search space, including pagingSearchSpace, searchSpaceSIB1 and searchSpaceOtherSystemInformation, on the active BWP to monitor paging, as specified in TS 38.213[ NR; Physical layer procedures for control ] [13], clause 13. UEs in RRC_INACTIVE while SDT procedure is ongoing shall monitor for SI change indication in any paging occasion at least once per modification period, if the initial downlink BWP on which the SDT procedure is ongoing is associated with a CD-SSB. During a modification period where ETWS or CMAS transmission is started or stopped, the SI messages carrying the posSIBs scheduled in posSchedulingInfoList may change, so the UE might not be able to successfully receive those posSIBs in the remainder of the current modification period and next modification period according to the scheduling information received prior to the change. ETWS or CMAS capable UEs in RRC_IDLE or in RRC_INACTIVE while SDT procedure is not ongoing shall monitor for indications about PWS notification in its own paging occasion(s) that the UE monitors as specified in TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [20]. ETWS or CMAS capable UEs in RRC_CONNECTED shall monitor for indication about PWS notification in any paging occasion at least once every defaultPagingCycle if the UE is provided with common search space, including pagingSearchSpace, searchSpaceSIB1 and searchSpaceOtherSystemInformation, on the active BWP to monitor paging. ETWS or CMAS capable UEs in RRC_INACTIVE while SDT procedure is ongoing shall monitor for indication about PWS notification in any paging occasion at least once every defaultPagingCycle, if the initial downlink BWP on which the SDT procedure is ongoing is associated with a CD-SSB. For Short Message reception in a paging occasion, the UE monitors the PDCCH monitoring occasion(s) for paging as specified in TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [20] and TS 38.213[ NR; Physical layer procedures for control ] [13]. A L2 U2N Remote UE is not required to monitor paging occasion for SI modifications and/or PWS notifications. It obtains the updated system information and SIB6/7/8 from the connected L2 U2N Relay UE as defined in clause 5.8.9.9.3. If the UE receives a Short Message, the UE shall: 1> if the UE is ETWS capable or CMAS capable, the etwsAndCmasIndication bit of Short Message is set, and the UE is provided with searchSpaceSIB1 and searchSpaceOtherSystemInformation on the active BWP or the initial BWP: 2> immediately re-acquire the SIB1; 2> if the UE is ETWS capable and si-SchedulingInfo includes scheduling information for SIB6: 3> acquire SIB6, as specified in clause 5.2.2.3.2, immediately; 2> if the UE is ETWS capable and si-SchedulingInfo includes scheduling information for SIB7: 3> acquire SIB7, as specified in clause 5.2.2.3.2, immediately; 2> if the UE is CMAS capable and si-SchedulingInfo includes scheduling information for SIB8: 3> acquire SIB8, as specified in clause 5.2.2.3.2, immediately; NOTE: In case SIB6, SIB7, or SIB8 overlap with a measurement gap it is left to UE implementation how to immediately acquire SIB6, SIB7, or SIB8. 1> if the UE does not operate an IDLE eDRX cycle longer than the modification period and the systemInfoModification bit of Short Message is set: 2> apply the SI acquisition procedure as defined in clause 5.2.2.3 from the start of the next modification period; 1> if the UE operates an IDLE eDRX cycle longer than the modification period and the systemInfoModification-eDRX bit of Short Message is set: 2> apply the SI acquisition procedure as defined in clause 5.2.2.3 from the start of the next eDRX acquisition period boundary. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.2.2.2.2 |
1,590 | 6.31.1 Description | A mobile network can fail to provide service in the event of a disaster (for example a fire.) The requirements listed in this clause provide the 5GS with the capability to mitigate interruption of service. UEs can obtain service in the event of a disaster, if there are PLMN operators prepared to offer service. The minimization of service interruption is constrained to a particular time and place. To reduce the impact to the 5G System and EPS of supporting Disaster Roaming, the potential congestion resulting from an influx or outflux of Disaster Inbound Roamers is taken into account. Scenarios where network failures render the network subject to a disaster unable to authenticate its subscribers are excluded. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.31.1 |
1,591 | 5.5.7.5 Sequencing of subsequent start DTMF requests by the mobile station | If the network is generating DTMF tones it shall ensure that the minimum length of tone and the minimum gap between two subsequent tones (according to ETSI ES 201 235-2 [12a]) is achieved. NOTE 1: In ETSI ES 201 235-2 [12a] the minimum duration of a DTMF tone is 65ms. NOTE 2: In ETSI ES 201 235-2 [12a] the minimum gap between DTMF tones is 65ms. There is no defined maximum length to the tone, which will normally cease when a STOP DTMF message is received from the MS. However, the operator may choose to put a pre-defined time limit on the duration of tones sent. The appropriate sequencing of DTMF control messages is shown in figures 5.8 and 5.9. NOTE 3: The network may implement the time limit option where the DTMF tone duration is controlled by the network irrespective of the receipt of a STOP DTMF message from the mobile station. Figure 5.8/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Single DTMF transmission Figure 5.9/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Multiple DTMF transmission | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.7.5 |
1,592 | 9.3.7.2 TDD | For the parameters specified in Table 9.3.7.2-1, and using the downlink physical channels specified in Annex C.3.2, the minimum requirements are specified in Table 9.3.7.2-2 and by the following. a) the ratio of the throughput obtained when transmitting based on UE PUSCH 3-2 reported wideband CQI and subband PMI and that obtained when transmitting based on PUSCH 3-1 reported wideband CQI and wideband PMI shall be ≥ b) The ratio of the throughput obtained when transmitting on a randomly selected sub-band among the sub-bands with the highest differential CQI offset level the corresponding TBS based on UE PUSCH3-2 reported subband CQI and subband PMI and that obtained when transmitting on a randomly selected sub-band in set S based on PUSCH 1-2 reported wideband CQI and subband PMI shall be ≥ The transport block sizes TBS for wideband CQI and subband CQI are selected according to RC.17 TDD for test 1 and RC.18 TDD for test 2. Table 9.3.7.2-1 Sub-band test for TDD Table 9.3.7.2-2 Minimum requirement (TDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.3.7.2 |
1,593 | 12.3.7 Updating the PGW with overload control information of the target MME/S4-SGSN | During inter-MME/S4-SGSN mobility without SGW change scenarios, the SGW shall forward the MME/S4-SGSN's overload control information over the S5/S8 interface only if the Modify Bearer Request message needs to be sent over the S5/S8 for another reason, e.g. if the ULI, CGI, Serving Network, needs to be reported to the PGW, i.e. the SGW shall not generate a Modify Bearer Request message over the S5/S8 interface for the sole purpose of reporting the MME/S4-SGSN's overload control information. This avoids generating extra signalling over the S5/S8 interface. NOTE: If the MME/S4-SGSN provides overload control information during the scenarios which do not result in S5/S8 signaling, e.g. during an inter MME/S4-SGSN and intra SGW mobility, when no other information such as: the ULI, CGI or Serving Network, needs to be reported to the PGW, the overload information will not be relayed on to the PGW. Hence, the MME/S4-SGSN needs consider this when including overload control information. | 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.7 |
1,594 | 5.3.5.16 L2 U2N or U2U Remote UE configuration | The network configures the L2 U2N or U2U Remote UE with relay operation related configurations, e.g. SRAP configuration. The L2 U2N Remote UE shall: 1> if sl-L2RemoteUE-Config is set to setup or received from RRCSetup message: 2> if the sl-L2RemoteUE-Config contains the sl-SRAP-ConfigRemote: 3> if no SRAP entity has been established: 4> establish a SRAP entity as specified in TS 38.351[ NR; Sidelink Relay Adaptation Protocol (SRAP) Specification ] [66]; 3> configure the parameters to SRAP entity in accordance with the sl-SRAP-ConfigRemote; 3> if SRB1 is included in sl-MappingToAddModList, and sl-EgressRLC-ChannelPC5 is configured: 4> release SL-RLC1, if established; 4> associate the PC5 Relay RLC channel as indicated by sl-EgressRLC-ChannelPC5 with SRB1; 3> else: (i.e. SRB1 is not included in sl-MappingToAddModList, or SRB1 is included in sl-MappingToAddModList, but sl-EgressRLC-ChannelPC5 is not configured) 4> if SL-RLC1 is not established: 5> apply the default configuration of SL-RLC1 as specified in clause 9.2.4 and associate it with the SRB1; 2> if the sl-L2RemoteUE-Config contains the sl-UEIdentityRemote: 3> use the value of the sl-UEIdentityRemote as the C-RNTI in the PCell. 1> else if sl-L2RemoteUE-Config is set to release: 2> release the relay operation related configurations. The L2 U2U Remote UE shall: 1> if sl-L2RemoteUE-Config is set to setup: 2> if the sl-L2RemoteUE-Config contains the sl-U2U-RelayUE-ToReleaseList: 3> perform the L2 U2U Relay UE release as specified in 5.3.5.16.1; 2> if the sl-L2RemoteUE-Config contains the sl-U2U-RelayUE-ToAddModList: 3> perform the L2 U2U Relay UE addition/modification as specified in 5.3.5.16.2; 1> else if sl-L2RemoteUE-Config is set to release: 2> release the related configurations. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.5.16 |
1,595 | 4.15.7 Network status reporting | This clause contains the detailed description and the procedures for the network status reporting capability. An AF may request for being notified about the network status, in a specific geographical area or for a specific UE. The following methods are supported: - The AF requests to be informed, one-time, about the network status. This procedure is referred to as one-time network status request; - The AF requests to be informed, continuously, about the network status. This procedure is referred to as continuous network status request; The procedure as described in clause 6.1.1.2 or clause 6.1.2.2 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50] is used by an AF to retrieve Network Status Result (NSR) from the network for a specific geographical area or for a specific UE. After receiving the request for network status notification from the AF, the NEF retrieves user data congestion analytics information from NWDAF, as defined in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]. Based on the user data congestion analytics information the NEF receives from the NWDAF, the NEF derives and reports the network status for the geographical area or for the UE as Network Status Result (NSR) to the AF. When reporting to the AF, the NSR shall not include any 3GPP location information. NOTE 1: Either exact values for congestion status, as reported by NWDAF to NEF or abstracted values e.g. (High, Medium, Low) can be reported by the NEF to the AF. The calculation and the reporting of the NSR to the AF depends on operator configuration (e.g. SLAs, usage etc.). When an AF requests one-time Network Status from the NEF, the NEF can optionally provide a time interval at which the AF is allowed to re-issue the same request for network status. NOTE 2: The time interval provided by NEF can be ignored by the AF if the subsequent request on network status is considerably different with regards to the geographical area or the UE. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.7 |
1,596 | 4.3.25.2 Considerations for Roaming | In the case of roaming, if the HPLMN of the visiting UE does not support DCNs, i.e. doesn't provide the UE Usage Type, the serving MME/SGSN may select the DCN that serves the UE using operator specific policies based on other subscription or UE provided information. In the case of roaming, if the HPLMN provides the UE Usage Type parameter to the VPLMN, this parameter is provided irrespective of its value (standardized or operator specific). The handling of the UE Usage Type parameter in the VPLMN is based on operator policies, e.g. roaming agreements. If the UE assisted DCN selection feature is supported: - If the UE has a DCN-ID for the VPLMN the UE shall send that PLMN specific DCN-ID to the RAN, and - If the UE has no PLMN specific DCN-ID for this VPLMN and if the UE has a pre-provisioned default standardized DCN-ID it shall send the pre-provisioned default standardized DCN-ID to the RAN. | 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.25.2 |
1,597 | 6.9.2.2 Services and Service Continuity | A 5G system shall be able to support all types of traffic e.g. voice, data, IoT small data, multimedia, MCX for indirect network connection mode. The 5G system shall be able to support QoS for a user traffic session between the remote UE and the network using 3GPP access technology. The 5G system shall be able to provide indication to a remote UE (alternatively, an authorized user) on the quality of currently available indirect network connection paths. The 5G system shall be able to maintain service continuity of indirect network connection for a remote UE when the communication path to the network changes (i.e. change of one or more of the relay UEs, change of the gNB). NOTE: It does not apply to a traffic flow of a remote UE using different indirect network connection paths. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.9.2.2 |
1,598 | 12.2.5.1.2 Parameters | 12.2.5.1.2.1 Load Control Sequence Number The Load Control Sequence number contains a value that indicates the sequence number associated with the LCI IE. This sequence number shall be used to differentiate any two LCI IEs generated at two different instances by the same GTP-C entity. The Load Control Sequence Number shall be supported (if load control is supported) and shall always be present in the LCI IE. The GTP-C entity generating this information shall increment the Load Control Sequence Number whenever modifying some information in the Load Control Information IE. The Load Control Sequence Number shall not be incremented otherwise. The node may use the time, represented in an unsigned integer format, of the generation of the Load Control Information to populate the Load Control Sequence Number. When multiple instances of the LCI IE are provided in a message by a given GTP-C node, each of them shall contain the same Load Control Sequence Number value. This parameter shall be used by the receiver of the Load Control Information IE to properly collate out-of-order load control information, e.g. due to GTP-C retransmissions. This parameter shall also be used by the receiver of the LCI IE to determine whether the newly received load control information has changed compared to load control information previously received from the same node earlier. NOTE: The GTP-C sequence number cannot be used for collating out-of-order load control information as e.g. load control information may be sent in both GTP-C requests and responses, using independent GTP-C sequence numbering. If the receiving entity has already received and stored load control information from the peer GTP-C entity, the receiving entity shall update its load control information only if the Load Control Sequence Number received in the new load control information is higher than the stored value of the Load Control Sequence Number associated with the peer GTP-C entity. However due to roll-over of the Load Control Sequence Number or restart of the node, the Load Control Sequence Number may be reset to an appropriate base value by the peer GTP-C entity, hence the receiving entity shall be prepared to receive (and process) a Load Control Sequence Number parameter whose value is less than the previous value. 12.2.5.1.2.2 Load Metric The Load Metric parameter shall indicate the current load level of the originating node. The computation of the Load Metric is left to implementation. The node may consider various aspects, such as: the used capacity of the node based on activated bearers in relationship to maximum number of bearers the node can handle, the load that these active bearers produce in the node (e.g. memory/CPU usage in relationship to the total memory/CPU available, etc.). The Load Metric represents the current load level of the sending node as a percentage within the range of 0 to100, where 0 means no or 0% load and 100 means maximum or 100% load reached (i.e. no further load is desirable). The Load Metric shall be supported (if load control is supported). The Load Metric shall always be included in the Load Control Information. Considering the processing requirement of the receiver of the Load Control Information (e.g. handling of the new information, tuning the node selection algorithm to take the new information into account), the sender should refrain from advertising every small variation (e.g. with the granularity of 1 or 2), in the Load Metric which does not result in useful improvement in node selection logic at the receiver. During the typical operating condition of the sender, a larger variation in the Load Metric, e.g. 5 or more units, should be considered as reasonable enough for advertising the new Load Control Information and thus justifying the processing requirement (to handle the new information) of the receiver. NOTE: The range of the Load Metric, i.e. 0 to 100, does not mandate the sender to collect its own load information at every increment/decrement and hence to advertise the change of Load Metric with a granularity of 1%. Based on various implementation specific criteria, such as: the architecture, session and signalling capacity, the current load and so on, the sender is free to define its own logic and periodicity with which its own load information is collected. 12.2.5.1.2.3 List-of-APN_and_Relative Capacity The List-of-APN_and_Relative Capacity parameter contains a list of the tuple (APN, Relative Capacity) and this indicates one or more APNs for which the Load Control Information is applicable. The "APN" contains the name of the APN and the Relative Capacity indicates the resources configured for a given APN, compared to the total resources configured at the target PGW, as a percentage. When present in the LCI IE, the scope of the load information shall be the list of indicated APNs for the PGW that sends the load control information. In that case, the "Load Metric" shall be interpreted as an "APN-Load-Metric" and shall indicate the current resource utilization for the indicated APNs, as a percentage, as compared to the total resources configured for the indicated APNs at the target PGW. Its computation is implementation dependent and it has the same characteristics as "Load Metric". Only one instance of the List-Of-APN_and_Relative Capacity IE may be included within one Load Control Information instance. NOTE 1: The maximum number of tuples (APN, Relative Capacity) in the List-of-APN_and_Relative Capacity IE is set to 10. More than 10 occurrences of (APN, Relative Capacity), within one single instance of the List-of-APN_and_Relative Capacity IE is treated as protocol error by the receiver. If the List-of-APN_and_Relative Capacity IE has not been included, the scope of the Load Control Information shall be the entire PGW node (unless restricted by other parameters in the LCI IE). This parameter may be supported (if load control is supported) and shall be supported when APN level load control is supported. The receiver shall handle this parameter, when it is received, if it supports APN level load control. The receiver shall ignore a Load Control Information instance applicable for an APN, if it does not support APN level load control. NOTE 2: The PGW encodes the APN level load information and node level load information using different instance numbers in the message, so that the receiver will ignore the APN level load information, if it does not support the APN level load control feature. The maximum number of APNs, for which the PGW may advertise the Load Control Information, shall be limited to 10, i.e. the maximum number of occurrences of the tuple (APN, Relative Capacity) within and across various instances of the LCI IE shall be limited to 10, for a given PGW. Hence, if the PGW supports more than 10 APNs, it shall advertise the load control information for at most 10 of the most important APNs. In future, if needed, this limit may be increased to allow the PGW to advertise the load information for more APNs. In that case, the receiver not supporting the higher limit shall handle the first 10 APNs and shall ignore the load information for the remaining APNs. NOTE 3: The limit of the number of APN's takes into account various aspects such as: the processing and storage requirements at the overloaded node and the receiver, the number of important APNs for which load control advertisement will be necessary and interoperability between the nodes. When including load control information for some APN(s), the PGW shall also provide node level load control information by providing one instance of the Load Control Information without the List-of-APN_and_Relative Capacity parameter. A node selecting a PGW for a given APN shall apply the APN level load information, if available for that APN. If this parameter is not received for a given APN but it has been received for other APN(s) from the same PGW, then for this given APN, the node performing PGW selection shall calculate the load metric, as described in 3GPP TS 29.303[ Domain Name System Procedures; Stage 3 ] [32], for the target PGW. | 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.2.5.1.2 |
1,599 | 4.2.4.3 Substate when back to state GMM-DEREGISTERED from another GMM state | When returning to state GMM-DEREGISTERED, the MS shall select a cell as specified in 3GPP TS 43.022[ None ] [82] and 3GPP TS 25.304[ None ] [98]. The substate depends on the result of the cell selection procedure, the outcome of the previously performed GMM specific procedures, on the GPRS update status of the MS, on the location area data stored in the MS and on the presence of the SIM/USIM: - if no cell has been found, the substate is NO-CELL-AVAILABLE, until a cell is found; - if no SIM/USIM is present or if the inserted SIM/USIM is considered invalid by the MS, the substate shall be NO-IMSI; - if a suitable cell supporting GPRS has been found and the PLMN or LA is not in the forbidden list, the substate shall be NORMAL-SERVICE; - if a GPRS attach shall be performed (e.g. network requested reattach), the substate shall be ATTEMPTING-TO-ATTACH; - if a PLMN reselection (according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14]) is needed, the substate shall be PLMN SEARCH; - if the selected cell is known not to be able to provide normal service, the substate shall be LIMITED-SERVICE. | 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.3 |
1,600 | 8.13.1.3.1 Minimum Requirement Single-Layer Spatial Multiplexing 2 Tx Antenna Port with TM4 interference model (Cell-Specific Reference Symbols) | The purpose of these tests is to verify the closed loop rank-one performance with wideband precoding with two transmit antennas when the PDSCH transmission in the serving cell is interfered by PDSCH of one dominant interfering cell applying transmission mode 4 interference model defined in clause B.5.3. In Table 8.13.1.3.1-1, Cell 1 is the serving cell, and Cell 2 is the interfering cell. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1 and Cell 2, respectively. For CA with 2 DL CCs, the requirements are specified in Table 8.13.1.3.1-3, based on single carrier requirement specified in Table 8.13.1.3.1-2, with the addition of the parameters in Table 8.13.1.3.1-1 and the downlink physical channel setup according to Annex C.3.2. Table 8.13.1.3.1-1: Test Parameters for Single-Layer Spatial Multiplexing (FRC) with TM4 interference model for CA Table 8.13.1.3.1-2: Single carrier performance for multiple CA configurations Enhanced Performance Requirement Type A Table 8.13.1.3.1-3: Minimum performance (FRC) based on single carrier performance for CA with 2 DL CCs | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.13.1.3.1 |
Subsets and Splits